Problem with NFS install
James_Martin at ao.uscourts.gov
James_Martin at ao.uscourts.gov
Mon Jul 12 14:50:58 UTC 2004
There is a ksdevice option you can add in your pxelinux.cfg.. that would
tell it to use eth2 as your kickstart device. Are you assigning eth2
statically? I'm also assuming that you are getting your pxelinux.cfg file
from tftp? If you are doing it from a floppy you can use:
"""
--device=
Used to select a specific Ethernet device for installation. Note that
using --device= will not be effective unless the kickstart file is a local
file (such as ks=floppy), since the installation program will configure
the network to find the kickstart file. For example:
network --bootproto=dhcp --device=eth2
""
James
James S. Martin, RHCE
Contractor
Administrative Office of the United States Courts
Washington, DC
(202) 502-2394
kickstart-list-bounces at redhat.com wrote on 07/12/2004 10:40:24 AM:
> Hi, I'm installing a RHEL3 with kickstart in nfs mode.
> I boot pxe with my eth0 card via a server dhcp on 10.0.0.0 network.
>
> I have multiple network interface and my server nfs is via eth2 on
> 20.0.0.0 network.
>
> Is there a way to tell the kickstart file I want to use my eth2 card
> for nfs ???
>
> Here is the line in ks.cfg :
> nfs --server=20.0.0.78 --dir=/releaseBAS2/RHEL3U2
>
> I'm looking for an option like : nfs --server=20.0.0.78 --
> dir=/releaseBAS2/RHEL3U2 --device=eth2
> but it doesn't exist !!
>
> Thank you all !_______________________________________________
> Kickstart-list mailing list
> Kickstart-list at redhat.com
> https://www.redhat.com/mailman/listinfo/kickstart-list
More information about the Kickstart-list
mailing list