On Wed, 13 Feb 2002, Daniel Phillips wrote:
> > A module can get displaced as easily as a plain text file, and the wrong
> > "configutarion module" version won't do any good in any case.
>
> Not necessarily, check out the work on bootfs, I think this can be adapted to
> suit the purpose. If the config is in a module then we'd normally want that
> module to be one of the modules that is included in the boot image.
It should not be in the boot image, or at least it should be usable
elsewhere, because it isn't used at boot. It is only used in a running
system (not necessarily booted from the kernel in question, but running as
opposed to needed by lilo/grub).
> There is no good way to know where you have put those things. We're looking
> for a tight coupling between the kernel image and metadata that describes
> what's in it - like a label on an electronic component: stuck right on it,
> not filed away in a filing cabinet.
But that tight coupling has a cost, and the reason for compressed kernel
is to make it small to fit {places}, which is one of the benefits of
modules. Putting it in the kernel or nowhere is not optimal, most people
can manage to find documentation which isn't bound that tightly. If it's
available as a module it's useful in all the ways people currently use
things they may or may not want in the kernel, even if "in the kernel"
only means "stuck to the boot image."
-- bill davidsen <davidsen@tmr.com> CTO, TMR Associates, Inc Doing interesting things with little computers since 1979.- 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 : Fri Feb 15 2002 - 21:00:58 EST