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"
