From owner-freebsd-advocacy Thu Mar 23 12:12:51 2000 Delivered-To: freebsd-advocacy@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 696AA37B5D1 for ; Thu, 23 Mar 2000 12:12:47 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (dcs@p21-dn03kiryunisiki.gunma.ocn.ne.jp [210.232.224.150]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id FAA14056; Fri, 24 Mar 2000 05:12:42 +0900 (JST) Message-ID: <38DA7A60.B7C23121@newsguy.com> Date: Fri, 24 Mar 2000 05:11:12 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Michael Lucas Cc: advocacy@FreeBSD.ORG Subject: Re: New article References: <200003231326.IAA24776@blackhelicopters.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-advocacy@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Michael Lucas wrote: > > > Alas, we have been evolving to allow mostly dispensing with a kernel > > configuration file altogether. > > Then where are we going? MMMmmmm... PnP, PCI, modules, devfs, load on demand, etc. IIRC, you don't need to compile in some of the network cards anymore. They'll be loaded on demand by ifconfig. The same has always applied for filesystems, though you used to need to compile the one used for / in the kernel (you can now use loader to load the module). There is general interest in being able to load a module, probe, and then unload it if the probe fails. Legacy hardware will still need to be hand configured (though not necessarily built in the kernel), and some kernel options are probably unavoidable. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@zurichgnomes.bsdconspiracy.net One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-advocacy" in the body of the message