On Nov 5, 2013, at 9:06 AM, Kurt Lidl wrote: > >> You can try enabling the beastie menu on sparc64 by editing >> /boot/loader.rc: >> >> === Change #1 in /boot/loader.rc to enable beastie menu === >> >> Find: >> \ Reads and processes loader.conf variables >> \ NOTE: Change to `initialize' if you enable the below boot menu >> start >> >> Change "start" to "initialize" as shown below: >> \ Reads and processes loader.conf variables >> \ NOTE: Change to `initialize' if you enable the below boot menu >> initialize >> >> === Change #2 in [same file] to enable beastie menu === >> >> Find: >> \ Uncomment to enable boot menu >> \ include /boot/beastie.4th >> \ beastie-start >> >> Uncomment "beastie-start" as shown below: >> \ Uncomment to enable boot menu >> \ include /boot/beastie.4th >> beastie-start >> >> ====== >> >> If you find that making those two trivial changes, that you are able to load >> the menu... then maybe it's time for us to start thinking about enabling the >> beastie menu by-default for the sparc64 architecture. > > Seems to work just fine. I tested by booting, toggling through the > different kernel choices (/boot/kernel/kernel /boot/kernel.old/kernel) > and both worked correctly. > > (Although I uncommented the "include /boot/beastie.4th" line too.) > Oops, heh, good eye ;D and sorry if that caused any pain for you. >> Does anybody else have any thoughts on enabling it for sparc64? > > Well, I'd probably be in support of this change - it sure beats having > to interrupt the normal boot sequence and typing: > unload > load /boot/kernel.old/kernel > load /boot/kernel.old/opensolaris.ko > load /boot/kernel.old/zfs.ko > boot > When I need to get back to the prior version of the kernel. > We'll have to draw up a clean patch to draw this in for sparc64. For i386 and amd64, they have a dedicated separate loader.rc stashed in sys/boot/i386/loader/ Not sure of the cleanest way to do this for sparc64 (dup the loader.rc and make sparc64 drop it's own? or perhaps make sparc64 drop the i386 loader.rc? I think amd64 does the latter). -- Devin _____________ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you.
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:44 UTC