netdev
[Top] [All Lists]

Re: RFC: [2.6 patch] disallow modular IPv6

To: David Woodhouse <dwmw2@xxxxxxxxxxxxx>
Subject: Re: RFC: [2.6 patch] disallow modular IPv6
From: "David S. Miller" <davem@xxxxxxxxxx>
Date: Tue, 30 Sep 2003 01:30:25 -0700
Cc: bunk@xxxxxxxxx, acme@xxxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx, pekkas@xxxxxxxxxx, lksctp-developers@xxxxxxxxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx
In-reply-to: <1064910398.21551.41.camel@xxxxxxxxxxxxxxxxxxxxxxxxxx>
References: <20030928225941.GW15338@xxxxxxxxx> <20030928231842.GE1039@xxxxxxxxxxxxxxxx> <20030928232403.GX15338@xxxxxxxxx> <20030929220916.19c9c90d.davem@xxxxxxxxxx> <1064903562.6154.160.camel@xxxxxxxxxxxxxxxxxxxx> <20030930000302.3e1bf8bb.davem@xxxxxxxxxx> <1064907572.21551.31.camel@xxxxxxxxxxxxxxxxxxxxxxxxxx> <20030930010855.095c2c35.davem@xxxxxxxxxx> <1064910398.21551.41.camel@xxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
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.

At the very least, it should refuse to build the modules and tell the
user what he needs to do first.

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.

<Prev in Thread] Current Thread [Next in Thread>