Re: [PATCH] Re: [ANNOUNCE] hotplug-ng 002 release

[Rusty Russell]

On Wed, 2005-05-11 at 03:11 +0200, Erik van Konijnenburg wrote:
> Here's an alternative approach that should cover these interests:
> - add a keyword 'blacklist' to the configuration language,
>   that will be interpreted after alias expansion, but before
>   searching modules.dep.

This makes "blacklist X" equivalent to "install X /bin/true" right?  i.e
"ignore it".

> Advantages:
> - it needs a lot less code
> - distributions can decide whether blacklists work always,
>   never, or only for the kernel simply by playing with which
>   configuration file is used
> - my initramfs builder does not have to be special cased
>   to know that some install directives really are blacklist
>   directives.

Well, a module mentioned in hotplug's blacklist file would be a pretty
good candidate for exclusion from your initramfs builder.  Existing
install commands are already trouble for initramfs building, since they
can do arbitrary things...

How about I allow "--config=-" and hotplug can use the existing
blacklists and 'sed'?

Rusty.
-- 
A bad analogy is like a leaky screwdriver -- Richard Braakman

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/