Bug#257510: modules loaded from build area instead of /lib/modules

[Graham Knap <graham.knap@rogers.com>]

Package: kernel-source-2.6.7
Version: 2.6.7-2

After building a custom kernel via make-kpkg and installing it, I am 
finding that modules do not get loaded on boot.

In previous versions, modprobe would look in /lib/modules/<version>/kernel
but with this new kernel it's looking in /lib/modules/<version>/build

Now as you know, "build" is a symlink to the kernel source directory. 
This might be okay on some systems but, if you were to delete the source 
tree, it would NOT be okay... unless you know something I don't :-)

On my system, I haven't deleted the source, but /usr/src is on a 
separate partition (ie., not on the root volume) ... so modules won't 
load on boot, because S20modutils runs before S35mountall.

Have I just overlooked something? Or is there a bug here?

thanks

-- graham