On Nov 4, 2013, at 2:43 PM, Kurt Lidl wrote: >> On Nov 2, 2013, at 1:45 AM, Sam Fourman Jr. wrote: >>> On Sat, Nov 2, 2013 at 7:09 AM, Teske, Devin <Devin.Teske at fisglobal.com> wrote: >>> Hi all, >>> >>> Here's a chance to test out the kernel selection menu enhancements >>> to the boot loader menu before they go into HEAD. >>> >>> Discussion welcome, feedback desired. >>> >>> No recompile needed, just drop the new forth files onto a HEAD or >>> stable/9 box and reboot. >>> -- >>> Cheers, >>> Devin >>> >>> where are the forth files in question? >>> >> >> D'Oh! >> >> Here they are: >> >> http://druidbsd.cvs.sf.net/viewvc/druidbsd/forth_zfs/ >> >> Supplied as patches to either stable/9 or head. >> -- >> Devin > > Hmmm. I saw no appreciable changes to behavior when I patched all > the files in /boot with these versions. This was on a sparc64 host > running 10-BETA3 (compile this morning). > Excellent! Thank you for testing. NB: That's what *should* happen on sparc64 since that architecture doesn't actually enable the beastie menu (sad, I know... I wish that the beastie menu was active on all platforms by default). > Notably, the kernel and modules still loaded before presenting me > with the option to tell it which kernel to load: > > Executing last command: boot /pci_at_1f,0/pci_at_1/scsi_at_8/disk_at_0,0:a > Boot device: /pci_at_1f,0/pci_at_1/scsi_at_8/disk_at_0,0:a File and args: > > >> FreeBSD/sparc64 ZFS boot block > Boot path: /pci_at_1f,0/pci_at_1/scsi_at_8/disk_at_0,0:a > Consoles: Open Firmware console > \ > FreeBSD/sparc64 ZFS enabled bootstrap loader, Revision 1.0 > (root_at_snap.freebsd.org, Sun Oct 27 07:20:42 UTC 2013) > bootpath="zfs:sys/ROOT/default:" > Loading /boot/defaults/loader.conf > /boot/kernel/kernel data=0x8d54c0+0x66180 syms=[0x8+0x954f0+0x8+0x8d7ef] > /boot/kernel/zfs.ko text=0x223328 data=0xa4e0+0x17fc0 syms=[0x8+0x197b8+0x8+0x143f8] > loading required module 'opensolaris' > /boot/kernel/opensolaris.ko text=0x3130 data=0x2c8+0x2030 syms=[0x8+0xd98+0x8+0x929] > /boot/kernel/geom_mirror.ko text=0x38430 data=0x5b0+0x20 syms=[0x8+0x16b0+0x8+0x119e] > > Hit [Enter] to boot immediately, or any other key for command prompt. > Booting [/boot/kernel/kernel] in 9 seconds... > 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. Does anybody else have any thoughts on enabling it for sparc64? -- 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