From owner-freebsd-current Thu Dec 31 08:19:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA15670 for freebsd-current-outgoing; Thu, 31 Dec 1998 08:19:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA15661 for ; Thu, 31 Dec 1998 08:18:58 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id IAA19678; Thu, 31 Dec 1998 08:16:14 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdX19668; Thu Dec 31 16:16:05 1998 Date: Thu, 31 Dec 1998 08:16:02 -0800 (PST) From: Julian Elischer To: Robert Nordier cc: Peter Wemm , current@FreeBSD.ORG Subject: Re: HEADS UP: FLAG DAY COMING (was Re: New aout-to-elf build failures.) In-Reply-To: <199812311212.OAA17631@ceia.nordier.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG as long as the old (2.0) Bootblocks can load a new a.out encoded boot loader, We are ok, but if it can't then I guess I'll need to be spending time to figure out why and fix it.. asking our clients to replace the bootblocks is not an option, but supplying a 3rd stage loader called 'kernel' will work for us.. It would REALLY be nice if FreeBSD would now with this change, do what NetBSD did, and make the kernel name /FreeBSD rather than 'kernel'. On Thu, 31 Dec 1998, Robert Nordier wrote: > Peter Wemm wrote: > > > === INCOMPLETE DRAFT === > > > - The new bootblocks default to /boot/loader, but there are some problems > > for some people still. This needs to be fixed, and either the new > > bootblocks need fixing or the old bootblocks need a cutdown and > > modified to fire up /boot/loader by default. > > Since early November (and up to and including an issue reported on > -current yesterday), all apparent show-stopping problems with the > new bootblocks have turned out to be due to configuration and/or > pilot errors: where it has been possible to get further details. > > So if anyone still can't use the new bootblocks, there's almost > certainly some simple and painless solution which doesn't require > code fixes to sort out; and anyone who needs help is more than > welcome to contact me. > > -- > Robert Nordier > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message