From owner-freebsd-current Sun Jan 3 12:56:21 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA06901 for freebsd-current-outgoing; Sun, 3 Jan 1999 12:56:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles317.castles.com [208.214.167.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA06896 for ; Sun, 3 Jan 1999 12:56:19 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id MAA07318; Sun, 3 Jan 1999 12:52:45 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901032052.MAA07318@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Jeroen Ruigrok/Asmodai cc: Robert Nordier , mike@smith.net.au, current@FreeBSD.ORG Subject: Re: Bootblocks / Bootloader In-reply-to: Your message of "Sun, 03 Jan 1999 21:52:21 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 03 Jan 1999 12:52:44 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Bear in mind that, most of the time, the new boot blocks simply > > pass control to /boot/loader. You can use *recent* versions of > > the old boot blocks to start /boot/loader as well. > > Weird thing is that the first time it displayed the FreeBSD/i386 Boot > message and after I rm'ed /boot.config I never saw it again, and I rebooted > two/three times... That's normal; the "old" help is only displayed in "compatibility" mode. Without a /boot.config, the bootblocks try to be as quiet as possible. You may notice the spinner stop for a couple of seconds; if you hit a key at that point, you'll drop back into "compatibility" mode again. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message