Also, in 
http://hub.opensolaris.org/bin/view/Community+Group+tools/building_opensolaris

it describes the reboot command as

reboot ~-- kernel-17/amd64/unix

But that actually didn't work, I had to remove the tilde. I read
the manual of reboot command but couldn't find out what that tilde
does. Anyone knows?

Tian


On Fri, Dec 4, 2009 at 12:55 PM, Tian He <hnhetian at gmail.com> wrote:
>
> Thanks for clearing my doubts.
>
> I searched for solutions to this kind of error. It seems that
>
> ?"if a boot environment (BE) is mounted by using the beadm mount command, and 
> the system is rebooted before that BE gets unmounted, selecting that BE from 
> the GRUB menu causes a boot failure."
>
> I wonder how that description fits into my case...
>
> Tian
>
> On Fri, Dec 4, 2009 at 10:26 AM, James Carlson <carlsonj at workingcode.com> 
> wrote:
>>
>> Tian He wrote:
>> > 1. ?By running "hg clone
>> > ssh://anon at hg.opensolaris.org/hg/onnv/onnv-gate opensol", which
>> > version of ON source is downloaded?
>>
>> That grabs the "tip" of the tree, which means the very latest change
>> that someone has integrated.
>>
>> It's a live source base, and you're fetching it while it's being developed.
>>
>> > 2. ?By running "pfexec pkg install developer/opensolaris/osnet", will
>> > the build tool SUNWonbld also be installed? Someone said yes. The
>> > thing is, I didn't know that, so I just used "pfexec pkg install
>> > SUNWonbld" before executing this command. Later on I realized the
>> > build tool SUNWonbld is closely related to the release, I probably
>> > shouldn't have done that. I suspect this the reason for my failure.
>>
>> That doesn't sound related to problems in sysevent.
>>
>> Yes, you should have the newest SUNWonbld available, and for my systems
>> I just build it out of $SRC/tools. ?But not having the newest available
>> usually isn't a serious problem (unless there's been a flag day), and
>> even when it is a problem, it _usually_ causes problems with the build
>> process itself (compiling the software) and not with the installation or
>> running of the product.
>>
>> The one exception to that is bfu. ?Always use the bfu that matches the
>> code you've got. ?It's in $SRC/tools/scripts/bfu.sh.
>>
>> --
>> James Carlson ? ? ? ? 42.703N 71.076W ? ? ? ? <carlsonj at workingcode.com>
>
>
>
> --
> One way leads to another



--
One way leads to another

Reply via email to