[OpenIndiana-discuss] Solaris 11 Express available

[Kyle McDonald]

On 11/17/2010 2:50 AM, Nikola M wrote:
> Gabriel de la Cruz wrote:
>> Ummm S11 can upgrade from Opensolaris... maybe OpenIndiana could
>> upgrade
>>
> As it could be read, it seems unsecured to install SolarisExpress
> at all, since it kills ALL other boot environments for starting
> from GRUB.
>
> It cleans all Be's and have only itself in GRUB and one another
> previous BE.
>
If you do a fresh install this is definitely true. All releases of
OpenSolaris did the same thing.
Open Indiana will do the same if you do a fresh install. The Installer
program doesn't have a feature to install from scratch into a new BE.

If you have b134 on your machine, and configure the pkg(5) command to
use the new S11 Express repository, then you can 'upgrade' to S11
Express with the pkg image-update command and it will be installed in
a new BE, and your older b134 BE will remain. At least that's my
understanding.

If you want oi147 also, you can upgrade to that from your b134 BE
(either before installing S11exp or by rolling back to to the 134BE
and then upgrading to oi147.)

It remains to be seen if you can go from b134 to oi147 and then
directly to s11exp.

> I can't call this a normal bug, more like trying to kill forever
> previous installations from booting and have only SolarisExpress on
> boot menu, intentionally!
>
The bug below doesn't seem to remove entries from older BE's. It just
doesn't clone them all forward to the new BE.
>>
>> Only the First GRUB menu.lst Entry of the Source Boot
>> Environment Is Created When You Create a New Boot Environment
>> (4061)
>>
>> When a new boot environment is created, it has only one entry in
>> the GRUB menu.lst file regardless of how many entries the source
>> boot environment has. The source boot environment's first
>> menu.lst entry is used to create the entry for the new boot
>> environment. All other entries are ignored. This issue occurs
>> when you create the new boot environment either through the beadm
>> command or the pkg update command.
>>
>> If you need other entries for the new boot environment, they are
>> not available.
>>
>> *Workaround:* Edit the /rpool/boot/grub/menu.lst file and copy
>> the desired entries from the original boot environment. Replace
>> the boot environment name in the source entries with the name of
>> the target boot environment.
>>
This description basically says, if you are currently using a BE (say
for b134) where you've added entries for:

1) boot Osol b134 with the graphical splash screen
2) boot Osol b134 with no graphics
3) boot Osol b134 with a serial console
4) boot Osol b134 with a screen reader
5) boot Osol b134 with a screen reader

Then the new BE created during the the image-update will have all your
entries for the *old* BE, but it will only have 1 new entry for the
new BE which will be 'cloned' from the first entry in your old BE. The
bug is that they won't automatically clone all the entries.

So if the list above were what you had setup, then after the upgrade
you'd see somthing like  this:

1) boot S11 Exp b151a with the graphical splash screen
2) boot Osol b134 with the graphical splash screen
3) boot Osol b134 with no graphics
4) boot Osol b134 with a serial console
5) boot Osol b134 with a screen reader
6) boot Osol b134 with a screen reader

and not this:


1) boot S11 Exp b151a with the graphical splash screen
3) boot S11 Exp b151a with no graphics
3) boot S11 Exp b151a with a serial console
4) boot S11 Exp b151a with a screen reader
5) boot S11 Exp b151a with a screen reader
6) boot Osol b134 with the graphical splash screen
7) boot Osol b134 with no graphics
8) boot Osol b134 with a serial console
9) boot Osol b134 with a screen reader
10) boot Osol b134 with a screen reader


That just sounds like an ordinary bug to me.

 -Kyle


>
>
> _______________________________________________ OpenIndiana-discuss
> mailing list OpenIndiana-discuss at openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss