On Wed, 9 Jul 2008 11:44:08 -0400 "Joe_Wulf" <Joe_Wulf@xxxxxxxxx> wrote: Or you could customize the kernel and rebuild initrd. There are good documents on the internet on how to do that. > Very doubtful... pxelinux.0 is the engine that gets the vmlinux, > initrd.img and the isolinux.cfg files over to the target for booting. > You'd still be transfering those RHEL4.0 files over. > > what might work is addiing the driver into the kickstart process via the > 'driverdisk' option. > > > R, > -Joe Wulf, CISSP, USN(RET) > Senior IA Engineer > ProSync Technology Group, LLC > www.prosync.com > > > _____ > > From: kickstart-list-bounces@xxxxxxxxxx > [mailto:kickstart-list-bounces@xxxxxxxxxx] On Behalf Of Al Alder > Sent: Wednesday, July 09, 2008 10:57 > To: kickstart-list@xxxxxxxxxx > Subject: mixing RHEL 4.0 and 4.6 boot > > > We have an HP Proliant server. This server has SATA drives. We are > required by our customer to install > RHEL 4.0. The kickstart that we use is done via PXE boot. The 4.0 does > not have the driver for the SATA drives. > RHEL 4.6 does have the drive. Will replacing the kickstart 4.0 > pxelinux.0 on the kickstart machine with the 4.6 > pxelinux.0 cause the server to boot with the right driver and then > continue to install 4.0? > -- Open Systems Development Peter M. Groen Klipperwerf 12 2317 DZ Leiden Telef : +31-71-5216317 Mobiel : +31-6-29563390 Email : pgroen@xxxxxxxx WWW : http://www.osdev.nl Skype : peter_m_groen _______________________________________________ Kickstart-list mailing list Kickstart-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/kickstart-list
