Re: modifying initrd.img for kickstarting RH9
From: Cedric MARSOT (Cedric.Marsot_at_free.fr)
To: email@example.com, Paul Armor <firstname.lastname@example.org> Date: Wed, 27 Aug 2003 16:10:21 +0200
With Redhat 9, you have to modifiy isolinux/isolinux.bin and it will work.
And then burn a CDROM ...
If you are using floppy, modify initrd.img in bootdisk.img.
-- Cedric Selon Paul Armor <email@example.com>: > Hi all, > please pardon the cross-post of the re-post. I'm wondering if anyone has > any experience and can offer any pointers on modifying initrd.img. We've > been using a modified initrd.img with a modified init in versions up to > 7.3 with no problem. But when trying to follow the same process with RH9 > I get mixed results, none of them what I want :-(. Any help would be > appreciated! > > Cheers, > Paul > > > ---------- Forwarded message ---------- > Date: Tue, 26 Aug 2003 13:16:03 -0500 (CDT) > From: Paul Armor <firstname.lastname@example.org> > Reply-To: email@example.com > To: firstname.lastname@example.org > Subject: modifying initrd for kickstarting RH9 > > Hi, > sorry if this has been covered, or I'm posting to the wrong list (if so, > could you point me in the right direction?). We use Red Hat on a cluster, > and I'm currently trying to modify how we've done things with 7.3 to work > with 9; but I'm stuck and am not sure how best to proceed. We use a > modified init and have been able to just unzip the ramdisk, mount it, fill > it up with libs and other goodies, change the size of the ramdisk, etc in > the past. > > I've hit a point though where if I make more than just minimal changes to > the footprint of the zipped .img (adding more than just a couple of /libs > or executables), the anaconda will fail saying that the install tree is > invalid. Or in another case ignore the ks.cfg I feed it; it won't mount > the directory from which it's served. > > I initially tried just making a bigger image (~1.5M larger than default, > compressed), populating it with the libs and executables I wanted, and > serving that much larger .img. Then I tried telling it to use the same > .img, but allow for a larger ramdisk on the options fed to the booting > from the dhcp/tftp server. This yielded the invalid install tree msg. > > Then I tried pairing down what I needed to fit into the original image. > This caused it to ignore the ks.cfg (ignoring the mount to the location of > the ks.cfg). > > Can anyone offer any suggestions? > > Cheers, > Paul > > > -- > redhat-list mailing list > unsubscribe mailto:email@example.com?subject=unsubscribe > https://www.redhat.com/mailman/listinfo/redhat-list > > > > -- > redhat-list mailing list > unsubscribe mailto:firstname.lastname@example.org?subject=unsubscribe > https://www.redhat.com/mailman/listinfo/redhat-list > _______________________________________________ Redhat-install-list mailing list Redhatemail@example.com https://www.redhat.com/mailman/listinfo/redhat-install-list To Unsubscribe Go To ABOVE URL or send a message to: firstname.lastname@example.org Subject: unsubscribe -- redhat-list mailing list unsubscribe mailto:email@example.com?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list