From: Martin Schlemmer <azarah@gentoo.org>
To: Andrey Borzenkov <arvidjaar@mail.ru>
Cc: KML <linux-kernel@vger.kernel.org>,
Rusty Russell <rusty@rustcorp.com.au>, Greg KH <greg@kroah.com>
Subject: Re: devfsd/2.6.0-test1
Date: 21 Jul 2003 00:48:56 +0200 [thread overview]
Message-ID: <1058741336.19817.147.camel@nosferatu.lan> (raw)
In-Reply-To: <200307202117.32753.arvidjaar@mail.ru>
[-- Attachment #1: Type: text/plain, Size: 1861 bytes --]
On Sun, 2003-07-20 at 19:17, Andrey Borzenkov wrote:
> > Well, it implements probeall in another fashion. Also, you might
> > try /sbin/generate-modprobe.conf to convert a modules.conf to
> > modprobe.conf syntax.
>
> modprobe.conf syntax is easy to implement but unfortunately PITA to use.
> Exactly probe and probeall have been very helful in tracking module
> dependencies. Now you have arbitrary shell line that is near to impossible to
> parse in general.
>
True.
> I added half-hearted support to mkinitrd and initscripts for Mandrake but it
> will never be complete given the current situation.
>
> Also I fixed devfsd to correctly use modprobe.devfs or modules.devfs depending
> on which kernel it runs on; patch has been sent both to lkml and devfs list
> and is included in current Mandrake devfsd.
>
As I have it in Gentoo, it is done modprobe side, but only because its
less patches (as Rusty already added the changes to his hack, plus the
modprobe.devfs I sent him).
> actually adding probe and probeall is trivial enough, I did not want to base
> Mandrake packages on that to avoid incompatibility.
>
Have you checked with Rusty yet if he will accept probe/probeall patches
for module-init-tools ? I (IMHO) do not see why it should not be
possible to add if its done cleanly, and do not break anything else.
> > Also, read the threads on the list about udev/hotplug - apparently
> > devfsd is going out ...
>
> as long as you have memory-based /dev you need devfsd even if it is called
> differently.
>
I have not looked at it myself, but as far as I have it, you do not
mount /dev, and just need udev/hotplug/libsysfs (not sure on libsysfs).
Currently udev still call mknod, but I think Greg said he will fix that
in the future.
Regards,
--
Martin Schlemmer
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-07-20 22:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-20 17:17 devfsd/2.6.0-test1 Andrey Borzenkov
2003-07-20 22:48 ` Martin Schlemmer [this message]
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
[not found] <200307172145.14681.arvidjaar@mail.ru>
2003-07-18 10:49 ` devfsd/2.6.0-test1 Mark Watts
-- 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:
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=1058741336.19817.147.camel@nosferatu.lan \
--to=azarah@gentoo.org \
--cc=arvidjaar@mail.ru \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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).