Ethan Quach wrote:
>
>
> Jan Setje-Eilers wrote:
>> Hmm, it really should only edit bootenv.rc. IIRC the menu.lst stuff
>> was put in there so that really early kernel failures would go the
>> right place. However I don't really think that the trade-off of having
>> that work vs. the pain of it touching menu.lst for this is what we want.
>
> Yeah I think that's a pretty unexpected side effect of running
> eeprom. Did this recently change?
fyi, eeprom's attempt to update the menu.lst appears to be shunted when
you're booted to a BE whose menu.lst entry is not owned by BOOTADM.
On a system where I've updated many times, and the currently booted
BE's menu.lst entry wasn't created by bootadm, the menu doesn't get
updated:
[equach at ethos]:/> eeprom console=ttya
eeprom: error returned from bootadm: Default /boot/grub/menu.lst
entry is not controlled by bootadm. Exiting
[equach at ethos]:/>
But the bootenv.rc does get appropriately updated.
-ethan
>
>
> -ethan
>
>
>>
>> -jan
>>
>>
>>
>> Ethan Quach wrote:
>>>
>>>
>>> Paul Neary wrote:
>>>> Has anyone seen this unexpected behavior using the eeprom command on
>>>> 111a?
>>>>
>>>> # perform an osol 111a CD install. The menu.lst file after instal is
>>>> ...
>>>> splashimage /boot/grub/splash.xpm.gz
>>>> background 215ECA
>>>> timeout 30
>>>> default 0
>>>> #---------- ADDED BY BOOTADM - DO NOT EDIT ----------
>>>> title OpenSolaris 2009.06
>>>> findroot (pool_rpool,0,a)
>>>> bootfs rpool/ROOT/opensolaris
>>>> splashimage /boot/solaris.xpm
>>>> foreground d25f00
>>>> background 115d93
>>>> kernel$ /platform/i86pc/kernel/$ISADIR/unix -B
>>>> $ZFS-BOOTFS,console=graphics
>>>> module$ /platform/i86pc/$ISADIR/boot_archive
>>>> #---------------------END BOOTADM--------------------
>>>>
>>>> # Now update the console device using "eeprom console=ttya". This
>>>> updates menu.lst via bootadm. The new menu.lst file looks like ...
>>>> splashimage /boot/grub/splash.xpm.gz
>>>> background 215ECA
>>>> timeout 30
>>>> default 1
>>>> #---------- ADDED BY BOOTADM - DO NOT EDIT ----------
>>>> title OpenSolaris 2009.06
>>>> findroot (pool_rpool,0,a)
>>>> bootfs rpool/ROOT/opensolaris
>>>> splashimage /boot/solaris.xpm
>>>> foreground d25f00
>>>> background 115d93
>>>> kernel$ /platform/i86pc/kernel/$ISADIR/unix -B
>>>> $ZFS-BOOTFS,console=graphics
>>>> module$ /platform/i86pc/$ISADIR/boot_archive
>>>> #---------------------END BOOTADM--------------------
>>>> #---------- ADDED BY BOOTADM - DO NOT EDIT ----------
>>>> title Solaris bootenv rc
>>>> findroot pool_rpool
>>>> kernel$ /platform/i86pc/kernel/$ISADIR/unix -B console=ttya
>>>> module$ /platform/i86pc/$ISADIR/boot_archive
>>>> #---------------------END BOOTADM--------------------
>>>> #BOOTADM RC SAVED DEFAULT: 0
>>>>
>>>> The new menu.lst entry becomes the default but the system won't boot
>>>> from this. After adding -B $ZFS-BOOTFS to the kernel line it works
>>>> fine. I was expecting the second entry to be identical to the first
>>>> (except for the modified console=ttya parameter). Is this a bug or
>>>> have I misunderstood?
>>>
>>> The new entry is lacking the bootfs line as well. And I don't see
>>> how that findroot command would find the right dataset to boot if you've
>>> got multiple root datasets.
>>>
>>> I wasn't aware eeprom adds entries to the menu.lst, and makes it the
>>> default no less. This is probably a bug in bootadm, or perhaps eeprom's
>>> usage of it. I've Cc'ed Jan S. He might know something about that.
>>>
>>>
>>> thanks,
>>> -ethan
>>>
>>>>
>>>> -paul
>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------------------
>>>>
>>>>
>>>> _______________________________________________
>>>> caiman-discuss mailing list
>>>> caiman-discuss at opensolaris.org
>>>> http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
>>
> _______________________________________________
> caiman-discuss mailing list
> caiman-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
