From owner-freebsd-current@FreeBSD.ORG Mon May 5 05:23:22 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 3F14937B401 for ; Mon, 5 May 2003 05:23:22 -0700 (PDT) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 70D4543F3F for ; Mon, 5 May 2003 05:23:21 -0700 (PDT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.8/8.12.3) with ESMTP id h45CNHA7042899; Mon, 5 May 2003 06:23:18 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Mon, 05 May 2003 06:22:03 -0600 (MDT) Message-Id: <20030505.062203.30240784.imp@bsdimp.com> To: doconnor@gsoft.com.au From: "M. Warner Losh" In-Reply-To: <200305051222.05046.doconnor@gsoft.com.au> References: <20030504044927.GA13584@pit.databus.com> <3EB55F29.9080706@acm.org> <200305051222.05046.doconnor@gsoft.com.au> X-Mailer: Mew version 2.1 on Emacs 21.2 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org cc: kientzle@acm.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 12:23:22 -0000 In message: <200305051222.05046.doconnor@gsoft.com.au> "Daniel O'Connor" writes: : 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. There's more than just pci ID. Also, there are a couple of drivers that don't base their decision on the pci id, but other things in the headers to attach to all devices of a certain class. This makes autoloading a little harder. : 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 :) devd can do this too. Warner