On Tue, Sep 30, 2003 at 01:30:25AM -0700, David S. Miller wrote:
> On Tue, 30 Sep 2003 09:26:38 +0100
> David Woodhouse <dwmw2@xxxxxxxxxxxxx> wrote:
> > Why would he run 'make'? He'll only run 'make modules' since he only
> > enabled one extra module, and then he expects to be able to load it
> > without a reboot.
> If 'make modules' doesn't check if the config change has hit a
> dependency that requires the core kernel image to be rebuilt, we need
> to fix that. 'make modules' depends upon the kernel image.
If a module depends on core kernel functionality, that module option
should not be visible in the config until the core kernel functionality
has been turned on. Otherwise, maybe that core kernel functionality
should also be a module.
> At the very least, it should refuse to build the modules and tell the
> user what he needs to do first.
That would also work.
> All you've shown me is a bug in the build system, not a fundamental
> issue with module enables creating changes to the main kernel image.
slainte mhath, RGB
Richard Guy Briggs -- ~\ Auto-Free Ottawa! Canada
<www.TriColour.net> -- \@ @ <www.flora.org/afo/>
No Internet Wiretapping! -- _\\/\%___\\/\% Vote! -- <Green.ca>