On Mar 28, 2011, at 5:04 AM, Andriy Gapon wrote: > > Would also be cool to have an option to boot "something else" (like e.g. > memtest86). Maybe a special directory with loadable binaries and a special > menu > entry to select one of them.
As surprising as this release is, I've actually got plans to one day release our ISOLINUX based boot loader configuration that we use to do this very thing. We use the vesamenu.c32 module to present a menu containing memtest86 and many many other tools and at the top of that menu is our entry for chain-loading to FreeBSD (as a default). > > Probably even better to have a mechanism for pluggable menu entries like a > special > directory that would have .4th files each of which would represent one extra > menu > option. So instead of hacking system .4th files, one could easily extend main > menu with custom entries. My menu.4th module (that I released today -- see druidbsd.sf.net) does provide you with what you need to create not only an extended menu of your own design, but to create multiple menus through a system of separate .4th files. I in-fact actually used it to that very end in one of our custom boot menus. Each .4th file would call "menu-clear" and then set the appropriate "menu_caption[N]" variables, forming an array of values of 1-9 for N (9 is the maximum), before finally calling menu-create (which then read in the variables set in the environment and generating the menu). This is precisely one of the intended designs of my menu. It also has hooks for providing not only toggle-state menu options but cycle-state options (for example, setting "kernel[0]", "kernel[1]", and "kernel[2]", then having a menu item that upon keypress would allow cycling between the three (or more) options. Though these advanced features and topics are not used in the distributed code, I did not remove the underlying functions that are required/used to enable such extended functionality. For example, you'll still find "cycle_menuitem" in menu.4th, though it's not used by anything (waiting for some enterprising soul like yourself to put it to use -- though on a side-note, we're still using these functions in our custom boot menus on our automated installers where we change out the logos, mascots, colors, and use the higher level functions not required in the standard FreeBSD boot process). > > Just a dream... Not a dream. I somehow think you were channeling our progress. That or great minds think alike. -- Devin > -- > Andriy Gapon -- Cheers, Devin Teske -> CONTACT INFORMATION <- Business Solutions Consultant II FIS - fisglobal.com 510-735-5650 Mobile 510-621-2038 Office 510-621-2020 Office Fax 909-477-4578 Home/Fax devin.te...@fisglobal.com -> LEGAL DISCLAIMER <- This message contains confidential and proprietary information of the sender, and is intended only for the person(s) to whom it is addressed. Any use, distribution, copying or disclosure by any other person is strictly prohibited. If you have received this message in error, please notify the e-mail sender immediately, and delete the original message without making a copy. -> END TRANSMISSION <- _____________ 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"
