archive mirror
 help / color / mirror / Atom feed
From: Rusty Russell <>
Cc: Andrey Borzenkov <>
Cc: KML <>, Greg KH <>
Subject: Re: devfsd/2.6.0-test1
Date: Mon, 21 Jul 2003 21:09:24 +1000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: Your message of "21 Jul 2003 00:48:56 +0200." <1058741336.19817.147.camel@nosferatu.lan>

In message <1058741336.19817.147.camel@nosferatu.lan> you write:
> > 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.

Sure.  But probe and probeall isn't enough.  You'll also want
conditionals in the parsing of the config file, so you can do
different things on different architectures or different kernel
levels.  You're going to lose, here, if you try to be general 8(

We already have one hook to do arbitrary things, and I think it's
quite neat:

	# Sound is complex.
	install sound-slot-0 /sbin/configure-sound

Now, if you want to implement a meta-language that does all this,
great!  But I'm resisting new features in the base, because I have to
support them, and I'm incredibly lazy.

Modules already have their own hard and soft dependencies.  If you
have an incredibly complex modprobe.conf, it's worth asking whether
the correct solution is to make modprobe.conf's syntax more powerful,
or look at making a more fundamental change...

Hope that clarifies,
  Anyone who quotes me in their sig is an idiot. -- Rusty Russell.

  reply	other threads:[~2003-07-21 10:58 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 ` devfsd/2.6.0-test1 Martin Schlemmer
2003-07-21 11:09   ` Rusty Russell [this message]
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] <>
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:

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