I have successfully set up a very nice kickstart install with the i386
version of CentOS 4.3 and it works great. I am using a custom kickstart
script and the kernel and initrd from disc1/images. But when I try to
duplicate this for a 64 bit setup (changing paths in my tftp server,
ks.cfg, etc to point to the 64 bit stuff) it successfully tftp's
everything just as it should (tethereal output follows):
0.000000 192.168.0.201 -> 192.168.0.7 TFTP Read Request, File:
linux-install/pxelinux.0, Transfer type: octet
0.002503 192.168.0.201 -> 192.168.0.7 TFTP Read Request, File:
linux-install/pxelinux.0, Transfer type: octet
0.039763 192.168.0.201 -> 192.168.0.7 TFTP Read Request, File:
linux-install/pxelinux.cfg/01-00-0c-29-14-3a-c5, Transfer type: octet
0.045674 192.168.0.201 -> 192.168.0.7 TFTP Read Request, File:
linux-install/msgs/boot.msg, Transfer type: octet
0.522788 192.168.0.201 -> 192.168.0.7 TFTP Read Request, File:
linux-install/CentOS4.3/x86_64/vmlinuz, Transfer type: octet
2.487047 192.168.0.201 -> 192.168.0.7 TFTP Read Request, File:
linux-install/CentOS4.3/x86_64/initrd.img, Transfer type: octet
But then it never tries to get the ks.cfg. I am booting it with:
label centos
kernel CentOS4.3/x86_64/vmlinuz
append initrd=CentOS4.3/x86_64/initrd.img ramdisk_size=7000
ksdevice=eth0 ks=http://192.168.0.7/network-install/ks.cfg.x86_64
(that last line should be all one line)
in the /tftpboot/linux-install/pxelinux.cfg/01-00-0c-29-14-3a-c5 config
file which it tftp's so it should know that it needs to get the
ks.cfg.x86_64 file. I have this same setup working for i386 and it seems
to work fine. I would guess there might be some difference in the
initrd's but for some reason /linuxrc is a symlink to sbin/init which is
a binary executable instead of a shell script. Anyone know why it isn't
a shell? And why would my x86_64 kickstart be behaving different from my
i386?
Any help is very much appreciated!
--
Tracy R Reed http://ultraviolet.org
A: Because we read from top to bottom, left to right
Q: Why should I start my reply below the quoted text
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
