Date: Mon, 04 Jan 1999 07:34:36 +0100 (CET) From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl> To: Mike Smith <mike@smith.net.au> Cc: current@FreeBSD.ORG, Robert Nordier <rnordier@nordier.com> Subject: Re: Bootblocks / Bootloader Message-ID: <XFMail.990104073436.asmodai@wxs.nl> In-Reply-To: <199901032052.MAA07318@dingo.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 03-Jan-99 Mike Smith wrote: >> > 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. Well, it struck me as odd after reading Robert's tips about installing the bootblocks. He explicitly referred to the old boot message with the hex adresses in it, and the other consisting only of the message FreeBSD/i386 Boot. Hence I got to wonder about it. Yes I did notice the waiting of the spinner. Is that fallback a permanent one of just one to get through the transition time of a.out > elf? Just in case the bootblocks mess up for people. --- Jeroen Ruigrok van der Werven A veil of smoke is what I am, asmodai(at)wxs.nl I wait and I wait... Network/Security Specialist <http://home.wxs.nl/~asmodai>; BSD & picoBSD: The Power to Serve <http://www.freebsd.org>; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.990104073436.asmodai>