Re: 2.6.16, udev and scsi devices (fwd)

[Vincent McIntyre <Vince.McIntyre@atnf.csiro.au>]

On Mon, 21 Aug 2006, Christian Mueller wrote:

> If this patch fixes your problem, please let me know because I'll attach
> this to #347720. Or, if you want, just update #347720 yourself.

I've made the change to /usr/sbin/mkinitrd,
but I can't try it for a day or two.

Just to be sure I understand - should I now remake my initrd image?

I thought this kernel used an initramfs rather than an intird image:
 # file /boot/initrd.img-2.6.16-1-686-smp
 /boot/initrd.img-2.6.16-1-686-smp: gzip compressed data, from Unix, max
 compression
 # gzip -dc /boot/initrd.img-2.6.16-1-686-smp |file -
 /dev/stdin: ASCII cpio archive (SVR4 with no CRC)

So I thought I should run
 # update-initramfs -v -u -k 2.6.16-1-686-smp

But I can't see anywhere in the intiramfs-tools scripts that /usr/sbin/mkinitrd 
is called. I checked for similar greedy-globbing
code in mkinitramfs but could not see any.


Perhaps make-kpkg (kernel-package 8.135) is still calling mkinitrd,
when the backport is built? In which case I should make my own
kernel-image package using /boot/config.2.6.16-1-686-smp ?

Should I upgrade to kernel-package-10.052~bpo.1 and use that?

Thanks for your response and suggestions

Vince