Date: Thu, 7 Jan 1999 12:49:13 -0800 (PST) From: Julian Elischer <julian@whistle.com> To: Nate Williams <nate@mt.sri.com> Cc: Peter Wemm <peter@FreeBSD.ORG>, cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/sys/i386/conf Makefile.i386 Message-ID: <Pine.BSF.3.95.990107124507.3875I-100000@current1.whistle.com> In-Reply-To: <199901072037.NAA22536@mt.sri.com>
next in thread | previous in thread | raw e-mail | index | archive | help
changing the bootblocks is not always an option. And you can't change the bootblocks until you have installed the new stuff, by which time it's too late because you have replaced the kernel and you can no longer boot. You can sidestep this but I still think it's a complication.. I certainly can't replace the bootblocks on the many thousands of Interjets out there so WE will be doing what I have suggested. I just think that it would be a wise thing anyhow (to have an aout format elf loader called /kernel) On Thu, 7 Jan 1999, Nate Williams wrote: > > I strongly believe that the elf kernel should have a different name.. > > e.g. /FreeBSD > > *sigh* > > > this will ensure that only new bootblocks will find it and old bootblocks > > will find the old kernel lying about. > > this may save some people some grief. > > The bootblocks are fully capable of figuring out what kind of kernel it > is by looking at the magic # at the front of the kernel. > > Changing the kernel name is silly, and there is no technical reason to > do so. > > > Nate > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" 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.3.95.990107124507.3875I-100000>