I updated the bug report that was posted. Can we use that one to track this bug?
I posted the output of mkinitrd -v -f /tmp/foo.img $(uname -r) to the bug report.
Dwaine.
----- Original Message ----
From: Michal Jaegermann <michal(a)harddata.com>
To: For testers of Fedora Core development releases <fedora-test-list(a)redhat.com>
Sent: Monday, June 26, 2006 12:42:25 AM
Subject: Re: Recent kernels do not generate dm for initrd images
On Sun, Jun 25, 2006 at 08:45:33PM -0400, Jeremy Katz wrote:
On Sat, 2006-06-24 at 09:46 -0700, Dwaine Garden wrote:
> The dm lines are missing on all the initrd images that get generated
> when you update with yum. The dmraid stuff stopped
> getting added to the initrd images when the PAE kernels started coming
> out.
>
Can you file a bug with the output of '/sbin/mkinitrd -v -f /tmp/foo.img
$(uname -r)'? I expect something broke in mkinitrd and the output here
would help a lot in figuring out exactly _what_ :-)
It seems to me that this happened with mkinitrd-5.0.41-1 and over
a month ago. I run into that with another bug and I thought
at that time that this was a deliberate action and some other
mechanism likely will be used. That ommision appeared, in the
context, to be helpful.
See
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=192157
and comments #3 and #4 in particular. It is possible that I am
misinterpreting what showed up at that time.
Michal
--
fedora-test-list mailing list
fedora-test-list(a)redhat.com
To unsubscribe:
https://www.redhat.com/mailman/listinfo/fedora-test-list