Date: Thu, 31 Dec 1998 19:15:36 -0500 (EST) From: Brian Feldman <green@unixhelp.org> To: Julian Elischer <julian@whistle.com> Cc: Robert Nordier <rnordier@nordier.com>, Peter Wemm <peter@netplex.com.au>, current@FreeBSD.ORG Subject: Re: HEADS UP: FLAG DAY COMING (was Re: New aout-to-elf build failures.) Message-ID: <Pine.BSF.4.05.9812311912480.3621-100000@janus.syracuse.net> In-Reply-To: <Pine.BSF.3.95.981231081116.23049A-100000@current1.whistle.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 31 Dec 1998, Julian Elischer wrote: > 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'. Why make such a facetious change? OpenBSD renamed the kernel to bsd, NetBSD to NetBSD, why make such a change ourselves? It's simply unnecessary. Kernel is self-explanatory. You suggesting BTX (of course, what we'd use for a 3rd stage loader) as /kernel is a hack anyway, /boot/loader isn't quite a kenrel. > > > 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 > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ 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?Pine.BSF.4.05.9812311912480.3621-100000>