Alexander Viro <viro@math.psu.edu>:
> But it still leaves you with tristate - instead of yes/module/no it's
> yes/yes, but don't put it on initramfs/no. However, dependencies become
> simpler - all you need is "I want this, that and that on initramfs" and
> the rest can be found by depmod (i.e. configurator doesn't have to deal
> with "FOO goes on initramfs (== old Y), so BAR and BAZ must go there
> (== can't be M)").
Actually I think we may no longer be in tristate-land. Instead, some
devices have the property "This belongs in initramfs if it's configured
at all" -- specifically, drivers for potential boot devices. Everything
else can dynamic-load after boot time.
In CML2 you can assign a symbol properties, which are written into
trailing comments in the config file on the same line as the symbol
value assignment. One such property, "PRIVATE", is already
interpreted by the postprocessor that generates autoconf.h from the
configuration output; it prevents the symbol from being written to
autoconf.h.
The critical-for-boot property could be interpreted by the same
postprocessor script and turned into a manifest for initramfs. There
would be no need for the inference engine or configurator to know
about this property at all, just as it doesn't need to know anything
about PRIVATE.
-- <a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>"To disarm the people... was the best and most effectual way to enslave them." -- George Mason, speech of June 14, 1788 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.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 : Tue Jan 15 2002 - 21:00:47 EST