linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Martin Schlemmer <azarah@gentoo.org>
Cc: Mark Watts <m.watts@eris.qinetiq.com>,
	KML <linux-kernel@vger.kernel.org>
Subject: Re: devfsd/2.6.0-test1
Date: Thu, 17 Jul 2003 18:39:24 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.3.96.1030717183139.17023B-100000@gatekeeper.tmr.com> (raw)
In-Reply-To: <1058443807.13515.1530.camel@workshop.saharacpt.lan>

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 <davidsen@tmr.com>
  CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.


  reply	other threads:[~2003-07-17 22:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-17  9:17 devfsd/2.6.0-test1 Mark Watts
2003-07-17 10:02 ` devfsd/2.6.0-test1 Thierry Vignaud
2003-07-17 11:07   ` devfsd/2.6.0-test1 Mark Watts
2003-07-17 12:10 ` devfsd/2.6.0-test1 Martin Schlemmer
2003-07-17 22:39   ` Bill Davidsen [this message]
2003-07-20 16:27     ` devfsd/2.6.0-test1 Martin Schlemmer
2003-07-23 21:28       ` devfsd/2.6.0-test1 bill davidsen
     [not found] <200307172145.14681.arvidjaar@mail.ru>
2003-07-18 10:49 ` devfsd/2.6.0-test1 Mark Watts
2003-07-20 17:17 devfsd/2.6.0-test1 Andrey Borzenkov
2003-07-20 22:48 ` devfsd/2.6.0-test1 Martin Schlemmer
2003-07-21 11:09   ` devfsd/2.6.0-test1 Rusty Russell
2003-07-21 14:36   ` devfsd/2.6.0-test1 Greg KH
2003-07-21 14:52     ` devfsd/2.6.0-test1 Martin Schlemmer
2003-07-21 15:02       ` devfsd/2.6.0-test1 Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.3.96.1030717183139.17023B-100000@gatekeeper.tmr.com \
    --to=davidsen@tmr.com \
    --cc=azarah@gentoo.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.watts@eris.qinetiq.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).