From owner-freebsd-current@FreeBSD.ORG Mon May 5 03:22:34 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E446337B401 for ; Mon, 5 May 2003 03:22:34 -0700 (PDT) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7469943F3F for ; Mon, 5 May 2003 03:22:32 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from localhost (metatron.gsoft.com.au [203.38.152.122]) by cain.gsoft.com.au (8.12.9/8.12.6) with ESMTP id h45AMAIW006390; Mon, 5 May 2003 19:52:12 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: kientzle@acm.org, Barney Wolff Date: Mon, 5 May 2003 12:22:04 +0200 User-Agent: KMail/1.5 References: <20030504020700.B3CCA37B401@hub.freebsd.org> <20030504044927.GA13584@pit.databus.com> <3EB55F29.9080706@acm.org> In-Reply-To: <3EB55F29.9080706@acm.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200305051222.05046.doconnor@gsoft.com.au> X-Spam-Score: -0.7 () CARRIAGE_RETURNS,IN_REP_TO,REFERENCES,SPAM_PHRASE_00_01,USER_AGENT X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) cc: freebsd-current@freebsd.org Subject: Re: Floppy Support X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 May 2003 10:22:35 -0000 On Sun, 4 May 2003 20:42, Tim Kientzle wrote: > I suppose it's time to modify the boot loader to > load a single kernel image from multiple floppies. > That, at least, would end the continual release > breakage: the release builder could just create > as many floppy images as necessary. > > I remember the single-floppy installer; I foresee > the 10-floppy installer coming very quickly. ;-) Or use modules.. The vast majority of drivers are loadable as modules. It would be feasible to standardise the PCI ID tables of drivers and then generate a list from it which you can use to load modules for cards you find. Even now you can load arbitary kernel modules in sysinstall without too much hassle. (There is a sysinstall menu for it - I have a patch to this to read description files too :) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 9A8C 569F 685A D928 5140 AE4B 319B 41F4 5D17 FDD5