From owner-freebsd-current Sun Jan 3 12:46:00 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA05848 for freebsd-current-outgoing; Sun, 3 Jan 1999 12:45:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp05.wxs.nl (smtp05.wxs.nl [195.121.6.57]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA05835 for ; Sun, 3 Jan 1999 12:45:40 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.57.15]) by smtp05.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA5359; Sun, 3 Jan 1999 21:45:10 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199901031749.TAA04737@ceia.nordier.com> Date: Sun, 03 Jan 1999 21:52:21 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Robert Nordier Subject: Re: Bootblocks / Bootloader Cc: mike@smith.net.au, current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 03-Jan-99 Robert Nordier wrote: > I've put up some brief instructions on updating the boot blocks at > > http://www.freebsd.org/~rnordier/boot.txt OK, that helped... > I'd suggest just redoing the steps mentioned there, and you'll > probably pick up where things went wrong. > > 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... --- 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 BSD & picoBSD: The Power to Serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message