Just to mirror Brian's comments, HTTP is heavily preferred, because you can more dynamically modify the tree (url=http://blah/), as well as the kickstart files (ks=http://blah.cfg). This is how the great majority of enterprises address this.
And, again, if PXE/TFTP isn't allowed in your organization, you can put the boot.img on a USB stick, with a basic SYSLINUX boot file and/or options, and boot from that, and then access the HTTP setup once Anaconda stage1 is up. That's also how many federal installations that outlaw PXE/TFTP do it. ----- Original Message ----- From: Brian Long <bril...@cisco.com> Sent: Tuesday, November 8, 2011 1:26 PM May I ask why? Why spend weeks trying to get something working on RHEL 5 when it's not supported? Why not set up a PXE / HTTP infrastructure with the exploded ISOs and use that to install your hosts? _______________________________________________ rhelv5-list mailing list rhelv5-list@redhat.com https://www.redhat.com/mailman/listinfo/rhelv5-list
