bbenedetto> I can kickstart RHEL 7.2 with no problems. bbenedetto> And I can kickstart CentOS 7.2 also with no problems. bbenedetto> bbenedetto> But every time I try to kickstart CentOS 6.6, it instead bbenedetto> prompts me to "Choose a Language" and I end up doing a bbenedetto> manual install. During that session I can interactively bbenedetto> go through the menus and point to my CentOS 6.6 repo and bbenedetto> do the install that way which works just fine.
For those of you interested, we have met the enemy and it is us (naturall). My problem was in the initial file in /tftpboot/pxelinux.cfg that says: "here's the kernel and the ramdisk and the kickstart URL". My file looked like this (which works for RHEL/CentOS 7.x, BTW): kernel centos66/vmlinuz append initrd=centos66/initrd.img inst.ks=http://192.168.0.101/centos66/centos66-anaconda-ks.cfg I got that file from an admin in another of our tech centers and it works great with RHEL/CentOS 7.x. So I of course figured it would/should work for CentOS 6.6, right? Wrong. I'm sure that the more eagle-eyed among you have already seen it, but CentOS 6.6 doesn't understand "inst.ks=http://...";. So when it booted vmlinuz and the ramdisk, it never even SAW the kickstart side of the world. I changed "inst.ks=http://..."; to "ks=http://...": kernel centos66/vmlinuz append initrd=centos66/initrd.img ks=http://192.168.0.101/centos66/centos66-anaconda-ks.cfg and, lo and behold, the kickstart was found and read and used. Thank-you all for the suggestions that I got. -- - Bill +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ Bill Benedetto <bbenede...@goodyear.com> The Goodyear Tire & Rubber Co. I don't speak for Goodyear and they don't speak for me. We're both happy. _______________________________________________ Tech mailing list Tech@lists.lopsa.org https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
