From owner-freebsd-arch@FreeBSD.ORG Sun Oct 7 17:51:42 2012 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BD6B11065787; Sun, 7 Oct 2012 17:51:42 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) by mx1.freebsd.org (Postfix) with ESMTP id 7F3678FC1B; Sun, 7 Oct 2012 17:51:42 +0000 (UTC) Received: from smtp.fisglobal.com ([10.132.206.15]) by ltcfislmsgpa01.fnfis.com (8.14.4/8.14.4) with ESMTP id q97Hpdsb011521 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Sun, 7 Oct 2012 12:51:39 -0500 Received: from [10.0.0.103] (10.14.152.61) by smtp.fisglobal.com (10.132.206.15) with Microsoft SMTP Server (TLS) id 14.2.309.2; Sun, 7 Oct 2012 12:51:38 -0500 MIME-Version: 1.0 (Apple Message framework v1283) From: Devin Teske In-Reply-To: <86k3v21qsx.fsf@ds4.des.no> Date: Sun, 7 Oct 2012 10:51:37 -0700 Message-ID: <3EB58454-7820-43C4-911E-7DEF2D02C880@fisglobal.com> References: <0655B56F-AD43-402B-872C-568378E650F9@fisglobal.com> <86k3v21qsx.fsf@ds4.des.no> To: =?iso-8859-1?Q?Dag-Erling_Sm=F8rgrav?= X-Mailer: Apple Mail (2.1283) X-Originating-IP: [10.14.152.61] X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.7.7855, 1.0.431, 0.0.0000 definitions=2012-10-07_05:2012-10-06, 2012-10-07, 1970-01-01 signatures=0 Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Devin Teske , freebsd-arch@freebsd.org Subject: Re: New Boot Loader Menu X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Devin Teske List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Oct 2012 17:51:42 -0000 On Oct 7, 2012, at 4:10 AM, Dag-Erling Sm=F8rgrav wrote: > Devin Teske writes: >> What does everybody think? >=20 > I think it's a terrible idea. >=20 > What problem are you trying to solve, exactly? >=20 Many in-fact: 1. Growth issue. There's a ceiling to how many menu items a menu can have. + iX affiliates have come to me requesting accommodations for a submenu. + Adding said proposed submenu to the main menu (seen here: http://twitpic.= com/b1pkll/full) would leave practically no room for any further additions. 2. Exploring that last statement ("no room for any further additions")=85 + Practical and technical limitations prevent us from having more than 9 me= nu items. Coding around this is non-trivial (it goes all the way down to th= e raw ASCII codes that are generated when an associative keycode is pressed= ). + Due to the aforementioned technical/practical limitations, there's little= point in exploring the thought of: "what if we just got rid of Beastie to = make more room for the menu". Yielding more screen real estate for the menu= would not lift the technical limitations still limiting each menu from hav= ing at-maximum 9 items. 3. A bug is actually present in the current menu system. + Setting boot_verbose=3D"YES" in loader.conf(5) and rebooting, the current= menu system will not reflect this and the menu comes up saying "Verbose...= .. No". Although it is not and was not necessary to move the options to a s= ubmenu to fix this (in truth, the "dynamic menuitems" enhancement will fix = that and does not require the use of submenus), it was easier for *me* to t= est the dynamic menuitem initialization (aka constructor call-back) feature= enhancement if the option was in a submenu (since *re*-visiting a submenu = is akin to rebooting had I not moved the items off the main menu). + gnn was the one that reported this bug to me in early September. That was= a busy month because shortly thereafter, avg came at me with the request t= o accommodate submenus. I immediately recognized that these two requests (b= ugfix + enhancement) could be rolled into the same patchset (related featur= es). --=20 Devin _____________ 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.