In message <email@example.com> 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
# 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. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to firstname.lastname@example.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Jul 23 2003 - 22:00:42 EST