On 03/07/2010 08:36 PM, Rand All wrote:
Hmmm... I hadn't thought of making a separate BE. That seems pretty awkward,
but as you said, Solaris is kinda clunky like that, so there may not be a
better way.
No no.... no need to make another BE!!
Just simply if your boot environment say is: opensolaris
Under /rpool/ROOT/boot/grub/menu.lst
I mean to do this if you excuse my Linux example:
[code]
title Ubuntu 9.04, kernel 2.6.28-17-generic
uuid 55843420-b5c7-4fa9-9a14-2f7e8ceb6084
kernel /boot/vmlinuz-2.6.28-17-generic
root=UUID=55843420-b5c7-4fa9-9a14-2f7e8ceb6084 ro quiet splash
initrd /boot/initrd.img-2.6.28-17-generic
quiet
title Ubuntu 9.04, kernel 2.6.28-17-generic (recovery mode)
uuid 55843420-b5c7-4fa9-9a14-2f7e8ceb6084
kernel /boot/vmlinuz-2.6.28-17-generic
root=UUID=55843420-b5c7-4fa9-9a14-2f7e8ceb6084 ro single
initrd /boot/initrd.img-2.6.28-17-generic
[/code]
This is gona confuse the heck out of everyone so am gona say now, DO NOT
USE THIS IN SOLARIS!!!
This is an example only to show what I mean!
Basically what we have here copied over from my current Linux config is
normal startup and text startup.
The difference is under the kernel line where on the boot instance named
(recovery mode) it has the single user statement under the kernel. What
I am trying to illustrate with this is that no boot environment needs to
be set as with Linux there is no such thing and the same or at least
similar principle applies to Solaris.
Mirror your instance named: opensolaris or opensolaris-1 or whatever....
.....then once done that: change the name if opensolaris to opensolaris
text for the *NEW* mirrored version. Then comment out the graphic and
splash stuff on the *NEW* version and that's it!!!
Same kernel, same ZFS pool, same BE. The only thing that changed was the
parameters being issues to boot the BE. Kinda like opening a swing door
by pushing it one way or pulling it the other way. It's still the same
door but the approach is slightly altered.
I hope that helps and hasn't confused anyone too much if it does let me
know and I will boot up my Solaris instance aaaaaand connect my CAT6
cable to get onto my network which should be wireless but due to a
driver bug means that my notebook sees the 802.11 network as encrypted
when it's totally open :-( - HELP!! Someone... lol ok.
Anyhow if still don't get then I will illustrate!
Regards,
Kaya
_______________________________________________
opensolaris-help mailing list
[email protected]
