similar to: [PATCH] Load the ext2 module so mkinitrd works on RHEL 3

RHEL 4's mkinitrd will fail to recognise that root is on LVM when running on a recent kernel/udev due to changes in naming. This patch detects LVM root for RHEL 4, and uses a dirty hack to frig mkinitrd if required. Fixes RHBZ#580461 --- lib/Sys/VirtV2V/GuestOS/RedHat.pm | 21 +++++++++++++++++++-- 1 files changed, 19 insertions(+), 2 deletions(-) diff --git

RHEL 3 doesn't have a dynamic /dev. kmod-virtio creates devices nodes for vdX block devices based on what the major number of virtblk was at the time it was installed. This is, in turn, based on the order the modules were loaded in initrd. To try to preserve this precarious state of affairs, when adding virtio drivers to a new initrd we always load the same drivers as kmod-virtio in the same

Couple of notes: (1) You may need to 'make clean' after applying this patch. There is some missing dep so it seems the appliance isn't fully rebuilt. (2) [Comment mainly directed to Matt] This is not a candidate to be automatically added to the stable 1.2 branch. It's far too large of a change for a stable release. Since this change may be required for V2V, please clone

This patch series adds support for outputing an ext2-based appliance from febootstrap-supermin-helper. The usage is very simple, you just add '-f ext2' flag and the name of the appliance file that you want to write to. The implementation uses libext2fs, which is a very low level way to create ext2 filesystems from scratch. We'd like to use libguestfs, but that's an obvious

From: Pino Toscano <ptoscano at redhat.com> Complementary fix of commit 2d25872df3619a3077006ad0f91c029602db6780. On SLES 11 SP4 with kdump enabled mkinitrd calls mkdumprd which calls mkinitrd, but mkdumprd doesn't have any clue of the root device. Call mkinitrd with rootdev environment variable to tell them all what device to use as root. Tested-By: C?dric Bosdonnat <cbosdonnat at

CentOS Errata and Bugfix Advisory 2013:0863 Upstream details at : https://rhn.redhat.com/errata/RHBA-2013-0863.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 01cf0a69042bfd510f083b8a37d0a716a32109d97c1363c5370ac8f2a5b8759f libbdevid-python-5.1.19.6-80.el5_9.i386.rpm

CentOS Errata and Bugfix Advisory 2013:1288 Upstream details at : https://rhn.redhat.com/errata/RHBA-2013-1288.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 83dc958013d4095db5c63ba7762e0aebf9897e1247190b7fa2ae370ec525ad97 libbdevid-python-5.1.19.6-81.el5_9.i386.rpm

CentOS Errata and Bugfix Advisory 2014:1224 Upstream details at : https://rhn.redhat.com/errata/RHBA-2014-1224.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 1559bd365056b02f9ce4b36c074d0fab4d6f35fc4f29fa4a1cd2db016a8aaf48 libbdevid-python-5.1.19.6-82.el5.i386.rpm

How should mkinitrd integrate with the initramfs that comes with the kernel? At the moment, mkinitrd can simply provide an /init script and take over with the contents of its own cpio file available. /init then loads some modules, plays with mdadm, lvm, cryptsetup, creates some device nodes, mounts a filesystem, switch root, done. Integration is not an issue. That changes when more of the

Hey all, Just thought I'd give a quick shout out across the mailing list that it looks like Extlinux support got merged into Fedora's mkinitrd, which I believe is in time for Fedora 11. This apparently isn't my full patch series (which if anyone cares can be found at: http://git.kernel.org/?p=boot/warthog9/mkinitrd-syslinux.git;a=summary ) since it's missing the Extlinux

CentOS Errata and Bugfix Advisory 2010:0541 Upstream details at : https://rhn.redhat.com/errata/RHBA-2010-0541.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) x86_64: 6f8738af03c0d05c42c48041dbdf6468 libbdevid-python-5.1.19.6-61.el5_5.2.x86_64.rpm 3c175e1a4fadf26cd43802c3247e6707 mkinitrd-5.1.19.6-61.el5_5.2.i386.rpm

CentOS Errata and Bugfix Advisory 2009:1088 Upstream details at : https://rhn.redhat.com/errata/RHBA-2009-1088.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) x86_64: ad97a9b68f62b35fd7e6f77ef05650e9 libbdevid-python-5.1.19.6-44.1.x86_64.rpm f346c56dac3b271704e042db9c6d8566 mkinitrd-5.1.19.6-44.1.i386.rpm

CentOS Errata and Bugfix Advisory 2010:0390 Upstream details at : https://rhn.redhat.com/errata/RHBA-2010-0390.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) x86_64: 8f1264771eedc4a03b58bf3ba27359d3 libbdevid-python-5.1.19.6-61.el5_5.1.x86_64.rpm 1cfe374721dddec433a22d7a19845537 mkinitrd-5.1.19.6-61.el5_5.1.i386.rpm

CentOS Errata and Bugfix Advisory 2011:0430 Upstream details at : https://rhn.redhat.com/errata/RHBA-2011-0430.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) x86_64: 417f12dc9dc222e52ca47cfb89c0f3d0 libbdevid-python-5.1.19.6-68.el5_6.1.x86_64.rpm 537de4c2e2b04cb2810af4d23bfbea79 mkinitrd-5.1.19.6-68.el5_6.1.i386.rpm

CentOS Errata and Bugfix Advisory 2011:1017 Upstream details at : https://rhn.redhat.com/errata/RHBA-2011-1017.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) x86_64: d22854d09eb003bfbde5fa1772bfec31 libbdevid-python-5.1.19.6-71.el5.x86_64.rpm b3b302ab2382937f5a74406f2e89de25 mkinitrd-5.1.19.6-71.el5.i386.rpm

CentOS Errata and Bugfix Advisory 2011:1491 Upstream details at : https://rhn.redhat.com/errata/RHBA-2011-1491.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) x86_64: ac1ade89ac44a8f5438edd73e605d201 libbdevid-python-5.1.19.6-71.el5_7.1.x86_64.rpm 266231e55634d55ae026c24e2356de6d mkinitrd-5.1.19.6-71.el5_7.1.i386.rpm

While using mkinitrd on debian sarge, it gives the following error: mkinitrd -v -f --with=aacraid --with=sd_mod --with=scsi_mod initrd-2.6.16-xen.img 2.6.16-xen /usr/sbin/mkinitrd: illegal option -- v $Id: mkinitrd,v 1.201 2004/05/16 22:00:48 herbert Exp $ Usage: /usr/sbin/mkinitrd [OPTION]... <-o outfile> [version] Options: -d confdir Specify an alternative configuration directory.

I need to be able to install CentOS 5.2 on a machine with software RAID (and LVM) setup. I discovered (the hard way!) that there is a bug in the mkinitrd package that causes it to enter an endless loop when there are /dev/mapper/ devices present during the install process. There is a patch to mkinitrd, which I applied and created a new rpm for mkinitrd with this patch applied. I'd like to

Hi: I am installing Xen on Suse Linux Enterprise Server 10 SP2, when I try to make initrd img as README descirbed, but it tells me: #depmod 2.6.16.29-xen #mkinitrd -v -f --with=aacraid --with=sd_mod --with=scsi_mod initrd-2.6.16-xen.img 2.6.16-xen Unknown option: -v Try mkinitrd -h Then I added the "aacraid, sd_mod, scsi_mod" to "INITRD_MODULES" section in

mkinitrd in SLE guests < 12 tries to get the root device by scanning the fstab: this will fail, since v2v already remapped the devices from hd*/sd* to vd* in the guest (including in its fstab). Since we know what is the root device in the appliance, pass it to mkinitrd directly, so it does not have to do guesswork. Thanks to: Cédric Bosdonnat, for reporting the issue, and testing the fix. ---