Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S271607AbTGQWdG (ORCPT ); Thu, 17 Jul 2003 18:33:06 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S271604AbTGQWcv (ORCPT ); Thu, 17 Jul 2003 18:32:51 -0400 Received: from tmr-02.dsl.thebiz.net ([216.238.38.204]:58632 "EHLO gatekeeper.tmr.com") by vger.kernel.org with ESMTP id S271603AbTGQWcS (ORCPT ); Thu, 17 Jul 2003 18:32:18 -0400 Date: Thu, 17 Jul 2003 18:39:24 -0400 (EDT) From: Bill Davidsen To: Martin Schlemmer cc: Mark Watts , KML Subject: Re: devfsd/2.6.0-test1 In-Reply-To: <1058443807.13515.1530.camel@workshop.saharacpt.lan> 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 Content-Length: 1441 Lines: 35 On 17 Jul 2003, Martin Schlemmer wrote: > On Thu, 2003-07-17 at 11:17, Mark Watts wrote: > > I'm running devfs on a 2.6.0-test1 box (Mandrake 9.1 with the new kernel) > > > > Every time I boot, it complains that I don't have an /etc/modprobe.devfs. > > If I symlink modules.devfs, I get a wad of errors about 'probeall'. > > What should a modprobe.devfs look like for a 2.5/6 kernel? > > > > The module-init-tools tarball should include one. Agreed, it should. However, the last version I pulled had zero support for probeall, and more importantly for probe, which is somewhat harder to do cleanly without having to rewrite the config file for each kernel you boot. I assume someone will need to write a functional config parser which handles these features before 2.6 is seriously ready for production. Giving up the ability to find the working module for a device would be a step back, and is needed to allow booting with changing configurations, such as docked or not laptops, PCMCIA cards inserted, various hardware such as printers and scanners attached, etc. -- bill davidsen CTO, TMR Associates, Inc Doing interesting things with little computers since 1979. - 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/