NFS using eth1 installation

[Paul VanAllsburg]

Thanks Klaus, It works now... Booted to DVD, ran ks.cfg and iso sourced on 
eth1, I'll set this up with PXE next...

for the record,
boot: linux ks=nfs:192.168.2.100:/data/ks/fc3/i386/computenode/ks.cfg 
ksdevice=eth1

and ks.cfg had:
nfs --server=192.168.2.100 --dir=/data/iso/fc3/i386
and,
network --device eth0 --bootproto dhcp # 192.168.1.101
network --device eth1 --bootproto dhcp # 192.168.2.101

Paul

>===== Original Message From Klaus Steden <klaus.steden at thomson.net> =====
>Paul,
>
>The kickstart option you're looking for is 'ksdevice=', i.e. ksdevice=eth1
>should do the trick.
>
>Klaus
>
>> How do I create a kickstart file that will do a NFS using eth1 
installation?
>>
>> I can successfully do a manual boot: askmethod, specify NFS with eth1, but 
it
>> does not show up in the anaconda-ks.cfg file.  I end up with:
>> nfs --server=192.168.2.100 --dir=/data/iso/fc3/i386
>>
>> When I run a automated install using the anaconda generated script I get 
'That
>> directory could not be mounted from the server'.  I've been able to move 
the
>> NFS share over to a system on eth0 and get it to work but not one on eth1.
>> The network/share on eth1 is functional...
>>
>> Thanks,
>> Paul Van Allsburg
>>
>> _______________________________________________
>> Kickstart-list mailing list
>> Kickstart-list at redhat.com
>> https://www.redhat.com/mailman/listinfo/kickstart-list
>
>--
>Klaus Steden                          |
>Senior Systems Administrator          |
>Technicolor Creative Services         | TODO:
>Toronto                               | 1) Learn to use my new Unix account.
>klaus.steden at thomson.net              | 2) Learn how to change this list.
>Phone: (416) 585-9995                 |
>Fax: (416) 364-1585                   |
>
>_______________________________________________
>Kickstart-list mailing list
>Kickstart-list at redhat.com
>https://www.redhat.com/mailman/listinfo/kickstart-list