-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi all,
I usually use DHCP to install CentOS boxes via kickstart. For a first install, I boot the machine on the CentOS first CD, I type "linux ks" at the prompt and the rest is automatic. I have already use USB pen to boot some servers that don't have CD-ROM drive and all went well with the diskboot.img of CentOS 5.1.
But the diskboot.img of CentOS 5.2 seems to be unable to deal with the kickstart parameters passed by DHCP. The embedded DHCP client does not get the "filename" option value and seems to have problems with the DNS server (even if the "next-server" is correctly resolved). The installer fails at the moment of getting the kickstart file and asks me to enter a alternate location. There is a warning about the DNS server on the console, and it shows that the "filename" is set to "(null)".
All went well with the 5.1 diskboot.img, with the same hardware, same DHCP configuration, and the same kickstart configuration (but with a 5.1 install tree).
Anyone having the same problem ? Did I miss something ?
Many thanks,
3.14r