On Thu, Feb 01, 2007 at 12:22:28AM +0530, K T Ligesh wrote:
mkinitrd has a major issue. It doesn't give error if the module we
specify in the --with= doesn't exist. I gave mkintrd --with=gobble.kkk
and it accepted it very happily and proceeded to create a initrd.
What kind of initrd does this create? In fact, the initrd has no error
checking whatsoever. The problem is that the xenblk.ko is not there
in the initrd. It should actually be compiled into the kernel, at
least the xen kernel. And I am completely confused why it isn't done so.
The xenblk driver is perfectly capable of living as a kernel module. All
standard FC6 guest installs will have an initrd with xenblk as a module
# cd /tmp
# mkdir initrd
# cd initrd
# gunzip -c < /boot/initrd-2.6.18-1.2849.1dan2tbxen.img | cpio -idmv
# find | grep xenblk
./lib/xenblk.ko
Dan
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=|
|=- Perl modules:
http://search.cpan.org/~danberr/ -=|
|=- Projects:
http://freshmeat.net/~danielpb/ -=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|