Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 14 Jan 2002 17:19:14 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 14 Jan 2002 17:19:04 -0500 Received: from waste.org ([209.173.204.2]:3736 "EHLO waste.org") by vger.kernel.org with ESMTP id ; Mon, 14 Jan 2002 17:19:02 -0500 Date: Mon, 14 Jan 2002 16:18:41 -0600 (CST) From: Oliver Xymoron To: "Eric S. Raymond" cc: Alexander Viro , Alan Cox , "Mr. James W. Laferriere" , Giacomo Catenazzi , Linux Kernel List Subject: Re: Hardwired drivers are going away? In-Reply-To: <20020114151748.B19776@thyrsus.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 14 Jan 2002, Eric S. Raymond wrote: > Alexander Viro : > > But it still leaves you with tristate - instead of yes/module/no it's > > yes/yes, but don't put it on initramfs/no. However, dependencies become > > simpler - all you need is "I want this, that and that on initramfs" and > > the rest can be found by depmod (i.e. configurator doesn't have to deal > > with "FOO goes on initramfs (== old Y), so BAR and BAZ must go there > > (== can't be M)"). > > Actually I think we may no longer be in tristate-land. Instead, some > devices have the property "This belongs in initramfs if it's configured > at all" -- specifically, drivers for potential boot devices. Everything > else can dynamic-load after boot time. The knowledge of what's required to boot can and should be moved out of the kernel to distro land. 'make install' should call the distro's install script that sez /boot and /lib are on ext3 on /dev/sd?, ergo I need to include the ext3 and relevant SCSI modules. -- "Love the dolphins," she advised him. "Write by W.A.S.T.E.." - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/