Check out http://www.redhat.com/docs/manuals/enterprise/RHEL-3-Manual/sysadmin-gui de/index.html for kickstart. Here's a couple of example lines. network --device eth0 --bootproto static --ip nnn.nnn.nnn.nnn --netmask 255.255.248.0 --gateway nnn.nnn.nnn.nnn --nameserver nnn.nnn.nnn.nnn --hostname george03 authconfig --enableshadow --enablemd5 --enablenis --nisdomain kmgep --nisserver nnn.nnn.nnn.nnn Post install scripts can do the rest for you. I defer to the experts fot update methods. However, since you are RHEL 3, I assume that your applications are release sensitive. Could be worth dedicating a test machine. Local satillite servers, etc., will take more admin. Use more Google. Good luck, Leo -----Original Message----- From: kickstart-list-bounces@xxxxxxxxxx [mailto:kickstart-list-bounces@xxxxxxxxxx] On Behalf Of Joe Van Dyk Sent: Monday, February 13, 2006 9:55 PM To: Discussion list about Kickstart Subject: static ips and automation Hi, Is there some obvious way that I'm missing to easily give a computer a static IP address (and gateway/nameserver) during an automated kickstart installation? Each computer has their own IP and some are on multiple networks (i.e. more than NIC). Currently, the kickstart installation gives each one a DHCP address, then after the installation is complete and the computer reboots, someone then has to go through the redhat GUI and enter in its networking information. (And then run a script that nfs mounts a directory and installs some additional rpms that depend on it being networked correctly.) And say I've got twenty computers all set up (with RHEL 3). Would I use up2date on them to keep them err, up to date? That involves me setting up a server somewhere with updated RPMs? Sorry for the silly questions. I'm not a system administrator at all and I have no idea why I'm the one doing this. Joe _______________________________________________ Kickstart-list mailing list Kickstart-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/kickstart-list
