Re: Make modules_install doesn't create /lib/modules/$version

[Mikael Pettersson]

Martin Schlemmer writes:
 > On Fri, 2003-09-19 at 04:25, Rusty Russell wrote:
 > > In message <20030918091511.276309a6.rddunlap@xxxxxxxx> you write:
 > > > On Thu, 18 Sep 2003 03:21:40 -0400 Rob Landley <rob@xxxxxxxxxxx> wrote:
 > > > 
 > > > | I've installed -test3, -test4, and now -test5, and each time make 
 > > > | modules_install died with the following error:
 > > > | 
 > > > | Kernel: arch/i386/boot/bzImage is ready
 > > > | sh arch/i386/boot/install.sh 2.6.0-test5 arch/i386/boot/bzImage System.map ""
 > > > | /lib/modules/2.6.0-test5 is not a directory.
 > > 
 > > Looks like arch/i386/boot/install.sh is calling ~/bin/installkernel or
 > > /sbin/installkernel, which is not creating the directory.
 > > 
 > > Should depmod create the directory?  It can, of course, but AFAICT the
 > > old one didn't.
 > > 
 > > Maybe a RedHat issue?
 > > 
 > 
 > Likely, it works fine here with the one we are using
 > from debianutils.

So how come it's never been a problem on my RH boxes?
(Currently RH9 + module-init-tools but none of Arjan's .rpms)

I basically do
make bzImage modules |& tee /tmp/log
grep Warning /tmp/log
su
make modules_install
make install

Creating the /lib/modules/<version> directory is the kernel's
job, not installkernel (it's never done that before).
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/