On Sun, Dec 04, 2005 at 10:38:37AM +0200, Jari Aalto wrote: > Erik van Konijnenburg <[EMAIL PROTECTED]> writes: > | -- hack /usr/sbin/mkinitrd.yaird to echo the yaird command line > | and its own arguments to some scratch file, then do > | dpkg-reconfigure linux-image-2.6.14-2-686 > | and see if there's a difference from the yaird call you did > | just now. > > Hm. That worked? [4] > > Hope the logs help to solve this. If you need more information, I can > try more tests.
Looks like the bug silently went away: if I understand your mail correctly, when you dpkg-reconfigure a kernel, you get a new /boot/initrd.img and you have the sh -x output to prove it. Lets close this bug report. Just to be safe, you may want to keep the 'set -x' in your mkinitrd.yaird: that way you can show detailed debug info if the issue should reappear. Regards, Erik -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
