From owner-freebsd-stable@FreeBSD.ORG Tue Nov 30 12:17:00 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CB0FE16A4CE for ; Tue, 30 Nov 2004 12:17:00 +0000 (GMT) Received: from cenn.mc.mpls.visi.com (cenn.mc.mpls.visi.com [208.42.156.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id 925E343D2F for ; Tue, 30 Nov 2004 12:17:00 +0000 (GMT) (envelope-from seahawk@visi.com) Received: from isis.visi.com (isis.visi.com [209.98.98.8]) by cenn.mc.mpls.visi.com (Postfix) with ESMTP id 11DF38588 for ; Tue, 30 Nov 2004 06:16:56 -0600 (CST) Received: by isis.visi.com (Postfix, from userid 20347) id DD08376C69; Tue, 30 Nov 2004 06:16:55 -0600 (CST) Received: from localhost (localhost [127.0.0.1]) by isis.visi.com (Postfix) with ESMTP id D093476C56 for ; Tue, 30 Nov 2004 06:16:55 -0600 (CST) Date: Tue, 30 Nov 2004 06:16:55 -0600 (CST) From: Seahawk To: stable@freebsd.org In-Reply-To: <41ABA0D9.3090106@jim-liesl.org> Message-ID: References: <41AA785C.5020304@math.missouri.edu> <20041129084934.GA800@gicco.homeip.net> <41AAEBD9.9010705@gmx.net> <20041129095954.GA1282@gicco.homeip.net> <41AB9006.2040303@gmx.net> <41ABA0D9.3090106@jim-liesl.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: Beastie X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 12:17:00 -0000 On Mon, 29 Nov 2004, secmgr wrote: > Michael Nottebrock wrote: > > > Hanspeter Roth wrote: > > > >> The problem here is, that the Beastie picture is disabled by > >> default. This is obviously not compatible with the majority of > >> people. > > > > You're not up-to-date with the latest events, the beasty menu was > > completely nuked from CVS yesterday after the most recent complaints > > and we're now stuck again with the plain old loader prompt. > > Why nuke the menu? I can understand (although not agree with) taking > out beastie, but the menu was handy, and added useful (to me at least) > functionality. Is there some way to tweak it back in? > > thanks > jim I'd hope that this is only a temporary measure until someone can get around to rewriting the boot menu to load minus beastie as the default, and I'd hope there's the option to enable loading with beastie enabled in either b&w or color. I'd think it would be just easier to remove the "boring-beastie" and "technicolor-beastie" ascii art sections from the beastie.4th file so that we could still have the menu until a final fix to this issue can be made.