The boot: line will say what the IP is of the server you are kickstarting, and what the IP/name of the kickstart file you are retrieving (just like your example). The INSTALLATION source is specified in the kickstart file itself, and does not have to be the same as the server you got your ks.cfg file from. Chip -----Original Message----- From: kickstart-list-bounces@xxxxxxxxxx [mailto:kickstart-list-bounces@xxxxxxxxxx] On Behalf Of Jesse Keating Sent: Wednesday, November 02, 2005 3:44 PM To: kickstart-list@xxxxxxxxxx Subject: Re: network kickstart without dhcp server On Wed, 2005-11-02 at 23:37 +0000, Darren Birkett wrote: > Is it possible to have my kickstart file on an nfs mount, the > installation media on another nfs mount, and to use a statically > defined ip address defined with options at the boot prompt. For > example boot> linux ks=nfs:1.2.3.4/my/ks ip=9.9.9.9 gateway=9.9.9.1 > netmask=255.255.255.0 I'm not able to run a dhcp server in my > environment so unless I can define the networking info to my target > machine at the boot prompt, it's not going to be able to access the > kickstart or installation files on the network. Yes it is possible. I fail to remember where these boot options are documented, but there is a method to define the network settings at the boot prompt. -- Jesse Keating RHCE (http://geek.j2solutions.net) Fedora Legacy Team (http://www.fedoralegacy.org) GPG Public Key (http://geek.j2solutions.net/jkeating.j2solutions.pub) Was I helpful? Let others know: http://svcs.affero.net/rm.php?r=jkeating _______________________________________________ Kickstart-list mailing list Kickstart-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/kickstart-list
