From: Mark Watts <m.watts@eris.qinetiq.com>
To: Thierry Vignaud <tvignaud@mandrakesoft.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: devfsd/2.6.0-test1
Date: Thu, 17 Jul 2003 12:07:24 +0100 [thread overview]
Message-ID: <200307171207.25284.m.watts@eris.qinetiq.com> (raw)
In-Reply-To: <m265m1fp3u.fsf@vador.mandrakesoft.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> Mark Watts <m.watts@eris.qinetiq.com> writes:
> > 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?
>
> tv@vador ~ $ urpmf /etc/modprobe.devfs
> module-init-tools:/etc/modprobe.devfs
>
Interesting, an urpmf for that on my 9.1 box reveals nothing...
Thanks for the pointer...
Mark.
- --
Mark Watts
Senior Systems Engineer
QinetiQ TIM
St Andrews Road, Malvern
GPG Public Key ID: 455420ED
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE/FoNtBn4EFUVUIO0RAtsrAKDv8zNE7UwPttJ50cw5IFT4riRzFACfRQYy
dhUB9kqE4EX3ybdcieLiEbU=
=xA0b
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2003-07-17 10:53 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 ` Mark Watts [this message]
2003-07-17 12:10 ` devfsd/2.6.0-test1 Martin Schlemmer
2003-07-17 22:39 ` devfsd/2.6.0-test1 Bill Davidsen
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=200307171207.25284.m.watts@eris.qinetiq.com \
--to=m.watts@eris.qinetiq.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tvignaud@mandrakesoft.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).