On Tue, Feb 21, 2006 at 12:27:07AM -0800, Steve Langasek wrote: > On Tue, Feb 21, 2006 at 09:19:29AM +0100, Bastian Blank wrote: > > On Mon, Feb 20, 2006 at 07:49:42PM -0800, Steve Langasek wrote: > > > Um. How does this "break unrelated software"? > > > Yes. The kernel image depends on both. So yaird is unrelated to > > initramfs-tools. > > > > It doesn't respect the > > > policy set in /etc/kernel-img.conf, and it overwrites the initrd image > > > without asking, but what *broke*? > > > It breaks booting of all images. > > *How*? Nothing in this report has described actual breakage. If using > initramfs-tools to generate initramfs images prevents the system from > booting, that is indeed a critical bug, but that's not the bug that Jonas > filed.
initramfs-tools breaks the ramdisk generating policy, or more probably the kernel or k-p generated scripts do so, so it is at least serious severity.. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
