Re: [RELEASE] New Boot-Loader Menu bugs?
Hi Doug, On Jul 17, 2011, at 5:08 PM, Doug Barton wrote: > There also seems to be a bug with the new boot loader that if you bounce > out to the prompt and do 'boot kernel.other' the kern.module_path sysctl > is not updated. It still lists /boot/kernel first; but that should be > replaced by /boot/kernel.other. I had a chance to try this out in a VM. I just tested this in FreeBSD 8.1-RELEASE with my loader_menu applied (exactly what's available from rev 222417). The results I get are actually what you describe should happen. Here's the steps I took: 1. Made sure all "kernel=" and "module_path=" lines were commented out in loader.conf(5) 2. Moved my kernel to /boot/kernel/kernel 3. Made a copy of my kernel to /boot/kernel2/kernel 4. Rebooted. Didn't touch anything. Verified that when I came up, `sysctl -n kern.bootfile' was /boot/kernel/kernel. Good. We have a baseline operation that things are working as-expected without interrupting the boot-process (that is to say, that loader(8) loaded the kernel in it's default location). 5. Reboot again. This time, I press Escape to the drop to the loader(8) prompt. 6. I took "boot /boot/kernel2" 7. I see the new kernel being loaded. 8. The kernel executes. 9. My system boots as-expected. 10. The value of sysctl kern.module_path produces (drum roll): /boot/kernel2;/boot/kernel;/boot/modules What release are you running? I can't replicate the bug in 8.1-RELEASE with the new loader menu applied. It's possible that the bug was introduced some other way. -- 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. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: [RELEASE] New Boot-Loader Menu bugs?
On Jul 17, 2011, at 5:08 PM, Doug Barton wrote: > There also seems to be a bug with the new boot loader that if you bounce > out to the prompt and do 'boot kernel.other' Hmmm... The last change to the FICL word "boot" was 10 years, 9 months ago, by dcs in version 1.19 of sys/boot/forth/loader.4th. I know that I haven't touched that word, but I'll have to double-check to see if I'm overriding it in any way. I can see by the code in loader.4th that "boot" will automatically call "unload" for you if/when an argument is present (e.g., "boot kernel.other"). I personally have never used that syntax (I've always said "unload" before-hand), but I will take it from the code that this is supposed to work. > the kern.module_path sysctl > is not updated. If you want to change module_path for loader(8), you should set it in loader.conf(5). The FICL word "start" (as seen in /boot/loader.rc) will: (a) read loader.conf(5) and then (b) take your customized module_path and (c) search for a suitable kernel in those directories NOTE: that is, if "kernel" was not already set -- which it is, by default, to "/boot/kernel" sysctl(8) is not (and, IIRC, cannot be) influenced by loader environment variables. However, you can retrieve the loader(8) variables via kenv(1). If you wanted to, you could create an rc.d or RCNG script to use kenv(1) to do things with the loader(8) variables (such as drop them into loader.conf(5) or sysctl.conf(5)). Be careful though. > It still lists /boot/kernel first; but that should be > replaced by /boot/kernel.other. I'm not familiar with the latter behavior. -- 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. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: FW: [RELEASE] New Boot-Loader Menu bugs?
There also seems to be a bug with the new boot loader that if you bounce out to the prompt and do 'boot kernel.other' the kern.module_path sysctl is not updated. It still lists /boot/kernel first; but that should be replaced by /boot/kernel.other. -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
FW: [RELEASE] New Boot-Loader Menu bugs?
-Original Message- From: Devin Teske [mailto:dte...@vicor.com] Sent: Sunday, July 17, 2011 4:45 PM To: 'Andrey Fesenko'; 'freebsd-hackers@freebsd.org' Cc: Julian Elischer; Teske, Devin (devin.te...@fisglobal.com) Subject: RE: [RELEASE] New Boot-Loader Menu bugs? > -Original Message- > From: Andrey Fesenko [mailto:f0and...@gmail.com] > Sent: Sunday, July 17, 2011 12:33 AM > To: freebsd-hackers@freebsd.org; dte...@vicor.com > Subject: [RELEASE] New Boot-Loader Menu bugs? > > Last Changed Rev: 224125 Are you sure that's the right rev? That rev (by dougb) appears to be related to default empty zones in `/etc/namedb/named.conf', and completely unrelated to my rev 222417 (which you appear to be referencing below). > Not update share/examples/bootforth/* any files old version loader. > > file sys/boot/forth/loader.conf > ## > ### Loader settings > ## > > not actual logo list > #loader_logo="fbsdbw" # Desired logo: fbsdbw, beastiebw, > beastie, none > need > #loader_logo="orbbw" # Desired logo: orb, orbbw, fbsdbw, beastiebw, > beastie, none > > maybe over loader option. It took me awhile, but I think I see what you're saying. That the following patch needs to be applied to head/sys/boot/forth/loader.conf to be consistent with the changes that were made against head/sys/boot/forth/loader.conf.5 (in rev 222417): --- loader.conf.origSun Jul 17 16:37:35 2011 +++ loader.conf Sun Jul 17 16:38:09 2011 @@ -47,7 +47,8 @@ # escape to the loader prompt, set to # "NO" to disable autobooting #beastie_disable="NO" # Turn the beastie boot menu on and off -#loader_logo="fbsdbw" # Desired logo: fbsdbw, beastiebw, beastie, none +#loader_logo="orbbw" # Desired logo: orb, orbbw, fbsdbw, beastiebw, + # beastie, none #comconsole_speed="9600" # Set the current serial console speed #console="vidconsole" # A comma separated list of console(s) #currdev="disk1s1a"# Set the current device Does anybody object to the above patch? -- 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. _ ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
[RELEASE] New Boot-Loader Menu bugs?
Last Changed Rev: 224125 Not update share/examples/bootforth/* any files old version loader. file sys/boot/forth/loader.conf ## ### Loader settings ## not actual logo list #loader_logo="fbsdbw" # Desired logo: fbsdbw, beastiebw, beastie, none need #loader_logo="orbbw"# Desired logo: orb, orbbw, fbsdbw, beastiebw, beastie, none maybe over loader option. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
