similar to: Extlinux support makes Fedora's mkinitrd

> > Message: 5 > Date: Sat, 28 Apr 2007 11:37:51 -0700 > From: "J.H." <warthog19 at eaglescrag.net> > Subject: Re: [syslinux] USB stick meets ISO system > To: Geert Stappers <stappers at stappers.nl> > Cc: syslinux at zytor.com > Message-ID: <1177785471.25140.29.camel at localhost.localdomain> > Content-Type: text/plain > > On Sat,

On Sat, Jan 3, 2015 at 12:53 PM, John 'Warthog9' Hawley <warthog19 at eaglescrag.net> wrote: > On 01/03/2015 08:56 AM, Gene Cumm wrote: >> On Fri, Jan 2, 2015 at 3:43 PM, Geert Stappers <stappers at stappers.nl> wrote: >>> On Sat, Dec 27, 2014 at 05:07:04PM +0100, Geert Stappers wrote: >>>> On Mon, Dec 22, 2014 at 11:06:58AM +0200, Ady wrote:

Hey I would be happy to maintain such a thing but I would need someone as a backup. Cheers Didi ---------- Forwarded message ---------- From: J.H. <warthog19 at eaglescrag.net> Date: Mon, Oct 19, 2009 at 9:51 PM Subject: Re: [BKO] CentOS for boot.kernel.org To: Geerd-Dietger Hoffmann <ribalba at gmail.com> Cc: bko at hera.kernel.org Didi, I assume you mean with respect to the

On 01/03/2015 08:56 AM, Gene Cumm wrote: > On Fri, Jan 2, 2015 at 3:43 PM, Geert Stappers <stappers at stappers.nl> wrote: >> On Sat, Dec 27, 2014 at 05:07:04PM +0100, Geert Stappers wrote: >>> On Mon, Dec 22, 2014 at 11:06:58AM +0200, Ady wrote: >>>>> On Sun, Dec 21, 2014 at 12:21:32PM -0800, Patrick Masotta wrote: >>>>>> [ ... Failed to

This isn't an esp urgent issue, but I'd like to use a certain RAM diagnostic (Doc Mem) which I've already posted a note about a couple of months ago. Simply won't work booting the floppy disk image via MEMDISK. In the interim, I've tried to resolve this by changing things on my side. I'm pretty sure it's a XMS incompatibility, as it fails differently depending on

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.

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

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

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

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

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. ---

Hi all, I have a Opteron-machine with the MPT SCSI-controller (Symbios 53c1030). At least in i386-mode, mkinitrd does not seem to build a usable initrd for 2.6.13.x (.3 tested) with this kernel. With 2.6.12.6 it works fine. I have not tested this in x86_64 -mode yet. The symptom is that mptbase and mptscsih load, but mptscsih does not discover any controllers nor drives, and things like

I''ve compiled xen without any problems. but now i have to create an initrd file. When i use the command mkinitrd (without any options) the i''ve got some errors: # mkinitrd Root device: /dev/sda3 (mounted on / as reiserfs) Module list: ata_piix mptbase mptscsih qla2300 reiserfs Kernel image: /boot/vmlinuz-2.6.11.12-xen0 Initrd image: /boot/initrd-2.6.11.12-xen0 Shared

mkinitrd needs to mount files using loop. loop might be a module, so try to load it first. --- lib/Sys/VirtV2V/GuestOS/RedHat.pm | 7 +++++++ 1 files changed, 7 insertions(+), 0 deletions(-) diff --git a/lib/Sys/VirtV2V/GuestOS/RedHat.pm b/lib/Sys/VirtV2V/GuestOS/RedHat.pm index 0e469f5..08027b6 100644 --- a/lib/Sys/VirtV2V/GuestOS/RedHat.pm +++ b/lib/Sys/VirtV2V/GuestOS/RedHat.pm @@ -1114,6

We are happily running xen on a server which uses a SATA driver (thank you all you xenists for producing such a great product). However, we are creating a custom kernel for a domU. When we attempt to run mkinitrd we get: No module ata_piix found for kernel 2.6.11.12-xenUIPSec, aborting. This is the SATA driver. In the past (xen 2.0.5), we simply ran make ARCH=xen menuconfig and told it to

Hi, The latest fedora kernel already has the CONNMARK support. I'd like to use it in my centos 4.2 server. I know it is not as stable as the 2.6.9.x the comes with centos but it is an alternative to using the vanilla kernel. I've managed to rebuild the rpm of the FC4 kernel in my Centos server but when trying to install I get Failed dependencies: mkinitrd >= 4.2.15-1 is

I've just updated one machine from 4.0 to 4.2. The trouble is, the new kernel doesn't want to boot (2.6.9-22.EL, also tested 2.6.9.22.0.2.EL). Usually, manually recreating initrd file solved this problem in the past for me. But not this time. Playing around, I also noticed that if I rebuild initrd for the old kernel, then it also fails to boot. The only way to boot it up is

--- appliance/init | 3 +++ 1 files changed, 3 insertions(+), 0 deletions(-) diff --git a/appliance/init b/appliance/init index fe135b4..053ef36 100755 --- a/appliance/init +++ b/appliance/init @@ -39,6 +39,9 @@ fi modprobe dm_mod ||: +# For mkinitrd on RHEL 3 +modprobe ext2 + ifconfig lo 127.0.0.1 ifconfig eth0 10.0.2.10 route add default gw 10.0.2.2 -- 1.6.2.5

Afternoon everyone, I thought I'd let you all know I've just finished up the first initial release of PXE Knife, a utility that makes use of Syslinux to provide a bunch of utilities that (mostly) come on floppy disks and are a true pain to try and deal with. The goal is to try and give a normal sysadmin enough good tools within a pxe boot environment be able to deal with a number of

It looks like there's a bug in menu.c32, specifically dealing with the number of times you change menu pages. When a total (including the default load) of 28-29 loads of menu.c32 occurs the whole system will hang (ctrl+alt+del doesn't do anything). Looks like it's a problem concerning the number of file handles or something along those lines. The easiest way to duplicate the