archive mirror
 help / color / mirror / Atom feed
From: Mark Watts <>
To: Andrey Borzenkov <>
Cc: Thierry Vignaud <>,
Subject: Re: devfsd/2.6.0-test1
Date: Fri, 18 Jul 2003 11:49:55 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Hash: SHA1

> >> tv@vador ~ $ urpmf /etc/modprobe.devfs
> >> module-init-tools:/etc/modprobe.devfs
> >
> > Interesting, an urpmf for that on my 9.1 box reveals nothing...
> the package is in cooker since today. Get SRPMs for modutils, devfsd and
> module-init-tools, compile and install.

Ok, I've got those and I now have a modules.devfs...
I'm getting the impression that a bunch of modules have changed their names 
(i810_audio for example).
Even though I've changed (or I think I have) these module names in 
modprobe.conf I'm seeing failures for loading the old ones... Is something 
reading modules.conf that shouldn't?



- -- 
Mark Watts
Senior Systems Engineer
QinetiQ TIM
St Andrews Road, Malvern
GPG Public Key ID: 455420ED

Version: GnuPG v1.2.1 (GNU/Linux)


       reply	other threads:[~2003-07-18 10:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2003-07-18 10:49 ` Mark Watts [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
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   ` 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

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:

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

  git send-email \ \ \ \ \ \

* 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).