Date: Sun, 14 Jan 2001 15:35:37 -0800 From: Peter Wemm <peter@netplex.com.au> To: Jordan Hubbard <jkh@winston.osd.bsdi.com> Cc: Poul-Henning Kamp <phk@critter.freebsd.dk>, Wilko Bulte <wkb@freebie.demon.nl>, John Baldwin <jhb@FreeBSD.org>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/i386/conf GENERIC Message-ID: <200101142335.f0ENZbQ92706@mobile.wemm.org> In-Reply-To: <64239.979497114@winston.osd.bsdi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Jordan Hubbard wrote: > > It would be trivial to add i386 to the install kernel, and > > probably worthwhile. > > Both the installation AND the bindist kernel, right? Otherwise you > could install, but you wouldn't be able to boot the installed system. > That basically argues for putting it back into GENERIC, which > is (I believe) the item in contention here. If somebody wants to make an i386-capable installation, what we should do is something like this: 1: have a boot floppy with an i386 specific kernel. That means no PCI, no pci drivers, more of the older ISA drivers reactivated, kernel tuned down for low memory, etc. 2: Have the bindist have a kernel.i386 or something that is built similarly. 3: Have sysinstall "activate" the kernel.i386 instead of kernel.GENERIC Then installing on an i386 becomes a matter of booting a different set of floppies (remember, no CDROM boot support on i386 and most i486), and letting sysinstall detect the i386 support and set the boot kernel on the installed system appropriately. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 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?200101142335.f0ENZbQ92706>