Bug#518412: initramfs-tools: must support relative paths in modules.dep
On Thursday 19 March 2009, maximilian attems wrote:
> thanks for quick feedback.
> On Thu, Mar 19, 2009 at 05:15:06PM +0100, Frans Pop wrote:
> > You have to build a kernel from source while having the new m-i-t
> > installed. And then install that kernel *without* running depmod
> > (which is currently also not done by i-t).
> well linux-2.6 images postinst and even k-p do this,
> so this quite arguiably a bug in make deb-pkg.
No. deb-pkg CANNOT do this because it is executed on the system building
the kernel and the extra depmod would need to be run on the system where
the kernel is installed.
So *at most* my custom hook scripts that get executed when the kernel is
installed would be at fault for not doing the extra depmod (and I could
easily change them to do that, but that would be only solving the problem
for me and not for everybody else).
However, IMO a modules.dep file created by the upstream kernel Makefile
using an official version of m-i-t should be assumed to be valid and
should thus be supported by i-t.
If the file is not valid, then there would be a bug in m-i-t, but Marco
has argued that it is not.
> > You can probably also reproduce it by running the following sequence
> > of commands, which should emulate the way the upstream kernel
> > Makefile calls depmod (using any kernel version you have installed
> > for <kvers>): # kvers=<kvers>
> > # mkdir -p /tmp/lib/modules
> > # cp -r /lib/modules/$kvers /tmp/lib/modules/
> > # rm /tmp/lib/modules/$kvers/modules.*
> > # depmod -ae -F /boot/System.map-$kvers -b /tmp/ -r $kvers
> > The file /tmp/lib/modules/<kvers>/modules.dep should then show the
> > problem.
> copied over that file and saw still no sign of a trouble:
> mkinitramfs -v -o /tmp/foo | head -n 12
Are you sure you have the new version of m-i-t installed? Did you check
the contents of the generated modules.dep file?
Maybe my command was broken though. I did not check it as I've put m-i-t
on hold on all my machines. I'll check the actual command executed by the
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org