[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

A suggested patch for update-initramfs: rm update-initramfs

Unpacking linux-image-2.6.18-4-xen-686 (from
.../linux-image-2.6.18-4-xen-686_2.6.18.dfsg.1-10_i386.deb) ...
Setting up linux-image-2.6.18-4-xen-686 (2.6.18.dfsg.1-10) ...
/boot/initrd.img-2.6.18-4-xen-686 does not exist. Cannot update.

That it's even possible for this script to exit like this is a bug.

Looking at update-initramfs, I think it's a flawed concept. Why would
anyone ever update an initramfs? You should generate one each time --
not extract the cpio file, muddle around it it and then ball it back
up again. Just my 2 cents. Not that update-initramfs really does that
AFAICT it just runs mkinitramfs anyway.

I could send a patch, but seriously this script is designed to fail at
ever turn instead of just work. It's got panic() and mild_panic() all
over the place. delete()? How about rm -f <file>. Don't check, don't
panic if it fails. Just run it!

I'm not sure why this script exists at all, but it seems like it
should be replaced with one line:

mkinitramfs -o /boot/initrd.img-${KVER} ${KVER}


Reply to: