That was what I thought too. Now, like I said, this is my first time
working with Kickstart, so I may be missing something. Basically, I use
the following parameters:
ks=nfs:192.168.201.28:/opt/rhel_image_kickstart/m4b-1-17.ks/ks.cfg
ksdevice=eth0
The installation begins, loads a few modules, states that it is trying
to get a dhcp address for eth0, then tries with eth1. Since the eth1
dhcp fails, as expected, a dialog pops up to ask for user input, either
to try dhcp again, or to put a static IP address in. I put a static
address in, and the installation proceeds exactly as planned.
I guess what I'm saying is that I'm sure you're right that when I
specify the ksdevice that the device I specify will be the only one used
to fetch the ks.cfg, etc. All the evidence seems to support this. The
problem is that, despite this, Kickstart still seems to want to
configure eth1, even though it's totally unnecessary.
As far as your question, I'm pretty sure the machine can locate the nfs
server. I only export the directory on the NFS server to 192.168.201.x
subnet, and I'm putting in a 192.168.2.x address into eth1 by hand. I'm
pretty sure that, since the installation proceeds alright from there on,
that it's working correctly. That, and once the system is up, I can
mount it by hand without any trouble. Since I'm using an IP address for
the nfs server, I don't think resolving the hostname is the issue either.
Thanks,
Lloyd
Harry Mills wrote:
I may well be totally wrong but if you specify the ksdevice then that is the device that will be used to fetch the ks.cfg and no user intervention is required. This is how it seems to work on my set up here.
The only time I am prompted for manual network information is when kickstart can't find the ks.cfg file using the location specification in the 'ks=blah' boot parameter. KS then falls back to manually asking for network details.
Is it possible that the machine cannot locate/mount the NFS server or resolve the hostname?
Harry
On Thu, 25 Aug, Lloyd T Brown wrote:
I'll try that later, but, just for reference, which interface does the
ip=x.x.x.x parameter apply to? Can I specify which one? I can DHCP eth0
just fine. It's eth1 that I either need to set statically or disable
entirely.
Lloyd
EXT / HELICE RIVERA Cedric wrote:
Hi,
Maybe you can try this :
linux ks=nfs:nfs_server:/path/to/ ksdevice=eth0 ip=x.x.x.x
If your kickstart config file is complete and it's name is :
"/path/to/ks/x.x.x.x-kickstart"
then the installation will be completely non-interactive, unless the disk
partition table is clean ...
I hope this helps.
++
-----Message d'origine-----
De : kickstart-list-bounces@xxxxxxxxxx
[mailto:kickstart-list-bounces@xxxxxxxxxx]De la part de Lloyd T Brown
Envoy� : jeudi 25 ao�t 2005 16:23
� : kickstart-list@xxxxxxxxxx
Objet : disabling dhcp for eth1 in kernel
<snip>
_______________________________________________
Kickstart-list mailing list
Kickstart-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/kickstart-list
_______________________________________________
Kickstart-list mailing list
Kickstart-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/kickstart-list
