I'm trying to boot/install a server using RHEL4 and I've created my ks.cfg file based on a anaconda-ks.cfg file from a previously successful build.

The following 2 configurations work perfectly:

1. ks.cfg is located on a floppy:
boot: linux text ks=floppy

2. All identification information is provided at the boot: prompt:
boot: linux text ks=nfs:1.2.3.4:/path/ks.cfg ip=2.3.4.1 \
netmask=255.255.255.0 gateway=3.4.1.2 nameserver=4.1.2.3 \
hostname=myhostname

The following configuration (with no indentification information given) does NOT work:

3. ks.cfg file located on NFS share (on same subnet)
boot: linux ks=nfs:1.2.3.4:/path/ks.cfg

When I try to boot the server using method 3, there appears to be some sort of problem that prevents the server from obtaining its identification information and the install launches into interactive mode with the "Dynamic IP" screen prompting for identification information.

My problem is that even with the correct information in the ks.cfg file, the boot process can't seem to get the identification information (if I ommit it from the boot: prompt command line) from the nfs location and launches into interactive mode. I know that the NFS information is reachable because configurations 1 & 2 both load and install RHEL4 successfully from that same NFS server as where the ks.cfg file resides.

Why can't I run the install such that all the identification information ALSO is loaded from my ks.cfg file from the NFS server?

Essentailly, I want a completely hands-off install after the ks.cfg file is initially configured.

This what is in my ks.cfg file:

install
nfs --server=1.2.3.4 --dir=/images/kickstart/ISO
lang en_US.UTF-8
langsupport --default=en_GB.UTF-8 en_GB.UTF-8
keyboard uk
skipx
network --device eth0 --bootproto static --ip 2.3.4.1 --netmask 255.255.255.0 --gateway 3.4.1.2 --nameserver 4.1.2.3 --hostname jstart01
rootpw --iscrypted some_encrypted_string_here
firewall --disabled
selinux --disabled
authconfig --enableshadow --enablemd5
timezone --utc Europe/London
bootloader --location=mbr
clearpart --all --initlabel
part /boot --fstype "ext3" --size=100 --asprimary
part pv.100000 --size=100 --grow --asprimary
volgroup vg00 --pesize=32768 pv.100000
logvol /usr --fstype ext3 --name=usr --vgname=vg00 --size=2048
logvol / --fstype ext3 --name=root --vgname=vg00 --size=512
logvol swap --fstype swap --name=swap --vgname=vg00 --size=1024
logvol /opt --fstype ext3 --name=opt --vgname=vg00 --size=1024
logvol /var --fstype ext3 --name=var --vgname=vg00 --size=2048
... snip ...

- CDM

I had the same question - why must Kickstart get a dynamic IP when it already has one.

The dynamic IP request should time out eventually, and anaconda should proceed on to the kickstart install. As you found out, if all identifying information is supplied to the kernel, it will skip the dynamic IP request. The following configs work for me (Fedora Core 6):

Pxelinux.cfg (the kernel and append lines are all one long line each):

label linux
kernel FC6/vmlinuz
append text ksdevice=eth0 console=tty0 load_ramdisk=1 initrd=FC6/initrd.
img network ks=nfs:10.10.20.41:/kickstart/server.ks
# (skip dynamic request) append text ksdevice=eth0 console=tty0 load_ramdisk=1 initrd=FC6/initrd.
img network ks=nfs:10.10.20.41:/kickstart/server.ks ip=10.10.20.250 netma
sk=255.255.255.0 gateway=10.10.20.1 nameserver=127.0.0.1 hostname=xxx


server.ks file (watch for line wraps) WARNING: Be sorta careful - if a host comes up on the net, and it goes straight into Kickstart, it could wipe out a hosts' disk with a fresh install!):

# Kickstart file automatically generated by anaconda.

install
nfs --server=10.10.20.41 --dir=/os/FC6
lang en_US.UTF-8
keyboard us
xconfig --driver "i810" --resolution 800x600 --depth 24
network --device eth0 --bootproto static --ip 10.10.20.250 --netmask 255.255.255.0 --gateway 10.10.20.1 --nameserver 127.0.0.1 --hostname xxx
rootpw --iscrypted $1$borkborkborkborkbork
firewall --disabled
authconfig --enableshadow --enablemd5
selinux --permissive
timezone --utc America/Los_Angeles
bootloader --location=mbr --driveorder=hda
# 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 / --fstype ext3 --size=0 --grow
part swap --size=1024

%packages
@admin-tools
@base
@core
@development-tools
@dial-up
@dns-server
@editors
@java
@system-tools
@web-server
comps-extras
cracklib-dicts
gnome-mime-data
kernel-headers
nash
php-common
rmt
tzdata