Date: Thu, 15 Nov 2012 18:47:30 -0800 From: Devin Teske <devin.teske@fisglobal.com> To: Devin Teske <dteske@freebsd.org> Cc: Daniel Eischen <deischen@freebsd.org>, Adrian Chadd <adrian@freebsd.org>, freebsd-arch@freebsd.org Subject: Re: HEADS-UP: Boot Loader Interface Fixes Message-ID: <8225B7E0-B153-4511-9CFB-841C5FA8B327@fisglobal.com> In-Reply-To: <8706EBE6-0068-49F5-9654-D0F3EE050331@fisglobal.com> References: <9643EC52-E905-43FB-8B18-5EF052271725@fisglobal.com> <Pine.GSO.4.64.1211152135010.14282@sea.ntplx.net> <8706EBE6-0068-49F5-9654-D0F3EE050331@fisglobal.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Nov 15, 2012, at 6:45 PM, Devin Teske wrote: >=20 > On Nov 15, 2012, at 6:38 PM, Daniel Eischen wrote: >=20 >> On Thu, 15 Nov 2012, Devin Teske wrote: >>=20 >>> Hi All, >>>=20 >>> I'm back with more changes to the boot loader menu. >>>=20 >>> First, don't panic! >>>=20 >>> Second, calm down! >>>=20 >>> Let's go over where we've been so-far so we don't repeat it here. >>>=20 >>> 1. Changing the order of items should be avoided as it "moves the goal = posts" >>>=20 >>> Agreed. This is not always avoidable, but should be avoided if possible. >>>=20 >>> 2. Hiding "Single User" mode behind a submenu is bad. >>>=20 >>> Agreed. It's been suggested, "why can't it be an action item?" I've tho= ught about it and it doesn't seem right to be an action item because it's a= setting in loader.conf(5). However, nobody said it can't be both an action= item _and_ a boolean option. >>>=20 >>> =3D=3D=3D >>>=20 >>> Now that we've covered those basics, let me explain the current situati= on: >>>=20 >>> If you are a proponent of the "goal posts" argument, then you may find = yourself astonished one day to find that the following procedure does not w= ork: >>>=20 >>> + Boot to beastie menu >>> + Press V to enable verbosity >>> + Press Enter to boot >>>=20 >>> The reason the above may fail and violate POLA is because of the improv= ements made in SVN r241523. Since r241523, adding something like: >>>=20 >>> boot_verbose=3D"YES" >>>=20 >>> to loader.conf(5) will not cause the boot menu to display a default ON-= status for the Verbose boot option. In this case, booting and pressing V wi= ll disable verbose boot. >>>=20 >>> Given that all boot options in the menu are dynamically-initializing an= d will inherit the states of their respective options from loader.conf(5), = a new problem emerges: >>>=20 >>> Q. How does one go about restoring the defaults in the event that a sy= stem doesn't boot? >>>=20 >>> Furthermore, the person may not know what the defaults are. >>>=20 >>> The need arises to have a "Load Defaults" option. >>>=20 >>> However, the introduction of this new menu item would both crowd the ma= in menu and (unless appended to the end) violate the first rule of not re-o= rdering items (which we just argued that it doesn't matter if you memorize = the numbers, their initial state may be negated from what the user expects). >>>=20 >>> The latter arguments of crowded main-menu and that the memorization of = numbers is broken right now brings up the good idea of utilizing submenus (= reasoning that if we have to make a change, best to make a change that can = last). >>>=20 >>> =3D=3D=3D >>>=20 >>> I want to move the boot options into a submenu. This submenu will have = all the boot options you see today on the main menu. >>>=20 >>> At the same time, add a "Load Defaults" action item for resetting the v= arious boot options to their hard-coded defaults (overriding loader.conf(5)= inheritance). >>>=20 >>> =3D=3D=3D >>>=20 >>> While proposing this, I realize that we need an easy way to get to sing= le-user mode. So in-addition to be able to access SUM as a boolean option i= n the "Boot Options" submenu, I propose adding a new "alternate boot" menu = item to the main menu. >>>=20 >>> At the same time, I've recognized the need to have more feedback in the= "Boot" option. For example, it would be nice if setting boot_single=3D"YES= " in loader.conf(5) that the first menu item said "Boot Single User [Enter]= " -- vociferating the default boot action. Meanwhile, the "Alternate Boot" = (not actually titled that) gives a quick and easy way of booting Multi-User= in the case of boot_single=3D"YES" or vice-versa. >>=20 >> I always disliked adding the large FreeBSD logo and beastie >> to the boot screen. Nearly 3/4 of the real-estate is that. >>=20 >=20 > echo "loader_logo=3Dnone" >> /boot/loader.conf Documented in beastie.4th(8) > echo "loader_brand=3Dnone" >> /boot/loader.conf Documented in brand.4th(8) > --=20 > Devin >=20 >=20 >> I'd rather put all the information on one screen and do >> away with the large logo and beastie. Perhaps there >> should be an option to "6: Show Large Logo and Beastie" ;-) >>=20 >> --=20 >> DE >=20 > _____________ > The information contained in this message is proprietary and/or confident= ial. 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 awa= re that any message addressed to our domain is subject to archiving and rev= iew by persons other than the intended recipient. Thank you. _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8225B7E0-B153-4511-9CFB-841C5FA8B327>