Kickstart Installs of FC2

[MW Mike Weiner (5028)]

List readers - 

I am trying to setup a PXE/Kickstart box so that I can do some
unattended installs remotely. What I have setup so far is:

1) a yum repository serving up my RPMS
2) the fc2 install base shared via nfs
3) a dhcp server dishing out the private Ips and paths to pxelinux.0
4) a tftp server serving up the pxelinux.0 bootloader and related kernel

I have it successfully pulling the pxelinux.0 and according to the
message log it appears to read the pxelinux.cfg/default file which has
the following contents:

[root at yum1 pxelinux.cfg]# cat 0A
DEFAULT linux
SERIAL 0,38400n8
LABEL linux
KERNEL vmlinuz-fc2
APPEND ksdevice=eth0 console=tty0 console=ttyS0,38400 load_ramdisk=1
initrd=initrd-fc2.img network ip=dhcp
ks=nfs:10.10.232.54:/tftp/ks-fc2.cfg

Which also seems to work, but what isnt working properly is the ks=nfs
statement. All services are running on the same box, and everything is
served up via tftp and nfs, as in the following:

ls -la /tftpboot
lrwxrwxrwx   1 root root      10 Jun 17 08:22 10.10.232.54-kickstart ->
ks-fc2.cfg
-rw-r--r--   1 root root 2443013 Jun 16 09:56 initrd-fc2.img
-rw-r--r--   1 root root       0 Jun 16 10:18 Kickstart_end
drwxr-xr-x   2 root root    4096 Jun 16 19:08 ks
-rw-r--r--   1 root root    1411 Jun 17 08:22 ks-fc2.cfg
-rw-r--r--   1 root root   12952 Jun 16 10:08 pxelinux.0
drwxr-xr-x   2 root root    4096 Jun 17 10:12 pxelinux.cfg
-rw-r--r--   1 root root 1209805 Jun 16 09:56 vmlinuz-fc2

And ls -la /tftpboot/pxelinux.cfg/
lrwxrwxrwx  1 root root   15 Jun 17 09:59 0A -> default.netboot
lrwxrwxrwx  1 root root   15 Jun 17 09:59 0A0A -> default.netboot
-rw-r--r--  1 root root   40 Jun 17 08:29 default
lrwxrwxrwx  1 root root   19 Jun 17 09:59 default.netboot ->
default.netboot-fc2
-rw-r--r--  1 root root  216 Jun 17 10:12 default.netboot-fc2

I can see the server actually loading the bootloader and I can see this
in the messages log now:

Jun 16 14:11:48 yum1 rpc.mountd: authenticated mount request from
10.10.232.80:750 for /repo/fedora/linux/core/2/i386/os (/repo)

But I am unsure if it is able to find my kickstart config file. The
/repo above is of course the install base (Fedora/images/etc under the
OS tree). Here is my current ks-fc2.cfg file for completeness:

# Kickstart file automatically generated.
install
nfs --server=10.10.232.54 --dir=/repo/fedora/linux/core/2/i386/os
lang en_US.UTF-8
langsupport --default en_US.UTF-8 en_US.UTF-8 keyboard us skipx network
--device eth0 --bootproto dhcp --hostname ag800 network --device eth1
--bootproto dhcp --hostname ag800 rootpw --iscrypted
$1$.pio2F.qewfj0iy2342^
firewall --disabled
selinux --disabled
authconfig --enableshadow --enablemd5
timezone America/New_York
bootloader --location=mbr --append rhgb quiet 
# The following is the partition information you requested 
# Note that any partitions you deleted are not expressed 
# here so unless you clear all partitions first, this is 
# not guaranteed to work 
clearpart --linux 
part /boot --fstype ext3 --size=101 
part /disk2 --fstype ext3 --size=12289 
part / --fstype ext3 --size=12289 
part swap --size=2048 
part /weblog --fstype ext3 --size=1 --grow

%packages --resolvedeps
@ web-server
@ mail-server
@ dns-server
@ dialup
@ network-server
@ sql-server
@ editors
@ admin-tools
@ system-tools
@ news-server
@ smb-server
@ authoring-and-publishing
@ sound-and-video
@ server-cfg
@ graphics
@ ftp-server
@ development-tools
@ engineering-and-scientific
@ text-internet
kernel-smp
grub
e2fsprogs

%post
# The Last Thing happening in Kickstart:
# get a file via TFTP which indicates we are done.
echo "get Kickstart_end" | /usr/bin/tftp 10.10.232.54

Now, when I rebooted this test box this morning, it grabs an IP from the
dhcp server, is able to receive and load the pxelinux bootloader, but in
the virtual console 3 I see the following after it runs through and
loads the kernel:

* NFS install method detected will use Rhupdates/
* Running anaconda script /usr/bin/anaconda
* Display mode=t
* Method = nfs://mnt/source/ .
* ddcprobe returned bogus values:
ID
Name
HorizSync
VertSync
* anaconda floppy devices is fd0
* Running kickstart %pre scripts
* All kickstart %pre scripts have been run

Which confuses me a little bit as I don't quite understand where its
getting the nfs methof pointing to Rhupdates and some of the other
stuff. 

Does anyone have any ideas? 

Thanks for any help in advance.
Michael Weiner