> CC: indiana-discuss@opensolaris.org
> Enviado: jueves, 17 de julio, 2008 19:01:37
> Asunto: Re: [indiana-discuss] How to Remove a Boot Environment
>
> * W. Wayne Liauh <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>
> [2008-07-17 02:36]:
> > Thanks. I need to do
+1 to that, definitely. I *always* type that one the linux way...
- Mensaje original
De: Stephen Hahn <[EMAIL PROTECTED]>
Para: W. Wayne Liauh <[EMAIL PROTECTED]>
CC: indiana-discuss@opensolaris.org
Enviado: jueves, 17 de julio, 2008 19:01:37
Asunto: Re: [indiana-dis
Michael Schuster wrote:
> Stephen Hahn wrote:
>> * W. Wayne Liauh <[EMAIL PROTECTED]> [2008-07-17 02:36]:
>>> Thanks. I need to do the "UNmount" command first. I keep typing
>>> beadm umount opensolaris-2 (using the "umount" command). Old habits
>>> don't die. They don't even fade away. :-)
>
Stephen Hahn wrote:
> * W. Wayne Liauh <[EMAIL PROTECTED]> [2008-07-17 02:36]:
>> Thanks. I need to do the "UNmount" command first. I keep typing
>> beadm umount opensolaris-2 (using the "umount" command). Old habits
>> don't die. They don't even fade away. :-)
>
> "beadm umount" as a synon
* W. Wayne Liauh <[EMAIL PROTECTED]> [2008-07-17 02:36]:
> Thanks. I need to do the "UNmount" command first. I keep typing
> beadm umount opensolaris-2 (using the "umount" command). Old habits
> don't die. They don't even fade away. :-)
"beadm umount" as a synonym for "beadm unmount" seems
Well, finally the bug tracking this defect has been moved to resolved
state - http://defect.opensolaris.org/bz/show_bug.cgi?id=1249 (another
related here - http://defect.opensolaris.org/bz/show_bug.cgi?id=1735)
Hopefully, going forward - with build 94 or 95, this issue should not
happen.
Now,
> On Wed, Jul 16, 2008 at 9:21 PM, W. Wayne Liauh
> <[EMAIL PROTECTED]> wrote:
> > Every time a pkg install failed, a new boot
> environment would be added. This time, I was trying
> to install SUNWscim packages from an alternative
> authority, but failed twice. My beadm list now
> shows:
> >
> >
2008 at 9:21 PM, W. Wayne Liauh
> <[EMAIL PROTECTED]> wrote:
> > Every time a pkg install failed, a new boot
> environment would be added. This time, I was trying
> to install SUNWscim packages from an alternative
> authority, but failed twice. My beadm list now
> shows:
> >
> > BEAct
beadm destroy? BTW, on my system, pkg image-update would create new boot
env, but pkg install should not.
W. Wayne Liauh wrote:
> Every time a pkg install failed, a new boot environment would be added. This
> time, I was trying to install SUNWscim packages from an alternative
> authority, but
W. Wayne Liauh <> wrote:
> Every time a pkg install failed, a new boot environment would be added. This
> time, I was trying to install SUNWscim packages from an alternative
> authority, but failed twice. My beadm list now shows:
>
> BEActive Active on Mountpoint Space
> Name
On Wed, Jul 16, 2008 at 9:21 PM, W. Wayne Liauh <[EMAIL PROTECTED]> wrote:
> Every time a pkg install failed, a new boot environment would be added. This
> time, I was trying to install SUNWscim packages from an alternative
> authority, but failed twice. My beadm list now shows:
>
> BE
Every time a pkg install failed, a new boot environment would be added. This
time, I was trying to install SUNWscim packages from an alternative authority,
but failed twice. My beadm list now shows:
BEActive Active on Mountpoint Space
Name reboot
12 matches
Mail list logo
