From owner-freebsd-current@FreeBSD.ORG Tue Nov 5 17:28:59 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 41BA5F19 for ; Tue, 5 Nov 2013 17:28:59 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from anacreon.physics.wisc.edu (unknown [IPv6:2607:f388:101c:0:216:cbff:fe39:3fae]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 05B2427EB for ; Tue, 5 Nov 2013 17:28:58 +0000 (UTC) Received: from anacreon.physics.wisc.edu (localhost [IPv6:::1]) by anacreon.physics.wisc.edu (8.14.7/8.14.7) with ESMTP id rA5HSvuo023648; Tue, 5 Nov 2013 11:28:58 -0600 (CST) (envelope-from nwhitehorn@freebsd.org) Message-ID: <52792AD9.2010200@freebsd.org> Date: Tue, 05 Nov 2013 11:28:57 -0600 From: Nathan Whitehorn User-Agent: Mozilla/5.0 (X11; FreeBSD powerpc; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: Kurt Lidl , freebsd-current@freebsd.org Subject: Re: [CFT] Kernel-Selection Enhancemnt to Boot Menu References: <62E3FA11-E6E1-4072-9226-993FF83EBC0D@fisglobal.com> <5279258F.8030000@pix.net> In-Reply-To: <5279258F.8030000@pix.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Nov 2013 17:28:59 -0000 On 11/05/13 11:06, Kurt Lidl wrote: > >> You can try enabling the beastie menu on sparc64 by editing >> /boot/loader.rc: >> >> === Change #1 in /boot/loader.rc to enable beastie menu === >> >> Find: >> \ Reads and processes loader.conf variables >> \ NOTE: Change to `initialize' if you enable the below boot menu >> start >> >> Change "start" to "initialize" as shown below: >> \ Reads and processes loader.conf variables >> \ NOTE: Change to `initialize' if you enable the below boot menu >> initialize >> >> === Change #2 in [same file] to enable beastie menu === >> >> Find: >> \ Uncomment to enable boot menu >> \ include /boot/beastie.4th >> \ beastie-start >> >> Uncomment "beastie-start" as shown below: >> \ Uncomment to enable boot menu >> \ include /boot/beastie.4th >> beastie-start >> >> ====== >> >> If you find that making those two trivial changes, that you are able >> to load >> the menu... then maybe it's time for us to start thinking about >> enabling the >> beastie menu by-default for the sparc64 architecture. > > Seems to work just fine. I tested by booting, toggling through the > different kernel choices (/boot/kernel/kernel /boot/kernel.old/kernel) > and both worked correctly. > > (Although I uncommented the "include /boot/beastie.4th" line too.) > >> Does anybody else have any thoughts on enabling it for sparc64? > > Well, I'd probably be in support of this change - it sure beats having > to interrupt the normal boot sequence and typing: > unload > load /boot/kernel.old/kernel > load /boot/kernel.old/opensolaris.ko > load /boot/kernel.old/zfs.ko > boot > When I need to get back to the prior version of the kernel. Is there a way to make this work even without the beastie menu? A way to interrupt the boot before kernel load (even holding down a key) would be really valuable, even on systems that do not support fancy terminals with colors and such. -Nathan