The best way to fix this would be to roll back to a prior BE,
figure out what broke you upgrade, fix i, and try again.
On Tue, Dec 10, 2013 at 14:51:11 +0530, Sam M wrote:
> Anyone? Am kind of stuck here.
>
> Thanks.
>
> On 04/12/2013, Sam M wrote:
> > Hello.
> >
> > I'm running OmniOS Bloody.
Anyone? Am kind of stuck here.
Thanks.
On 04/12/2013, Sam M wrote:
> Hello.
>
> I'm running OmniOS Bloody. I was getting an error with visudo so I tried to
> fix this by re-0nstalling the package in question. But I'm unable to. How
> can I fix this? How do I create/modify an alternate boot envir
Hello.
I'm running OmniOS Bloody. I was getting an error with visudo so I tried to
fix this by re-0nstalling the package in question. But I'm unable to. How
can I fix this? How do I create/modify an alternate boot environment?
BTW, I upgraded from Release to Bloody, so I booted into a Release boo
