Hi,
We dont run DHCP in our environment where I build our servers, is it required to get a first IP address to hit my kickstart server running on my xandros debian laptop? Just been a couple years since I last did some kickstart builds and I dont have system-config-kickstart running on a machine here in my home lab.
I can turn on DHCP on my linux laptop perhaps, but just wanted to check in here before I over-engineer something.
I have a line in the kickstart file that gives the machine it's network addressing like this (fictional IPs):
network --device eth0 --bootproto *static* --*ip* 192.168.25.4 --netmask 255.255.255.0 --gateway 192.168.25.1 --nameserver 192.168.25.2,192.168.25.3 --hostname myhost4.mydomain.com
it's right under these: (#question, it does go at the end, in the position I have it in right?) ----snip---------- # KICKSTART FOR STANDARD SERVER install cdrom
lang en_US.UTF-8 langsupport --default=en_US.UTF-8 en_US.UTF-8 keyboard us
# what's this for? I found it in an example file. # %include /tmp/netconfig
firewall --disabled selinux --disabled
# what's this for? Also found in example file. %include /tmp/authconfig
# xconfig --startxonboot # #####Question: Do I just leave this 'xconfig' statement out completely since I dont run X?
timezone --utc America/Los_Angeles bootloader --location=mbr --append="rhgb quiet"
###################################################################### ## DISK CONFIGURATION # Partitioning # Using the default partition table.
clearpart --all --initlabel # can I add the '--drives=sda' sda section to the end of the above line? i got from example file wanted to combine with initlabel statement.. # clearpart --all --drives=sda
part / --fstype "ext3" --size=1012 --ondisk=sda # do i need to call the sda scsi disk out if there are no IDE drives? part /boot --fstype "ext3" --size=256 --ondisk=sda part swap --size=8192 --ondisk=sda
part /home --fstype "ext3" --size=8192 --ondisk=sda part /var --fstype "ext3" --size=8192 --ondisk=sda
part /tmp --fstype "ext3" --size=1012 --ondisk=sda part /usr --fstype "ext3" --size=4096 --ondisk=sda part /var --fstype "ext3" --size=40960 --grow --ondisk=sda
###################################################################### ## PACKAGES %packages
## Standard packages @base @development-tools kernel
network --device eth0 --bootproto *static* --*ip* 192.168.25.4 --netmask 255.255.255.0 --gateway 192.168.25.1 --nameserver 192.168.25.2,192.168.25.3 --hostname myhost.mydomain.com
Elrako X. Harkonnen wrote:
network --device eth0 --bootproto *static* --*ip* 192.168.25.4 --netmask 255.255.255.0 --gateway 192.168.25.1 --nameserver 192.168.25.2,192.168.25.3 --hostname myhost4.mydomain.com
it's right under these: (#question, it does go at the end, in the position I have it in right?)
It's in the wrong place. It doesn't belong to %packages section. It should be in the first (main) section (before %packages, %post or %pre).
On Mon, 25 Dec 2006 at 12:15pm, Elrako X. Harkonnen wrote
We dont run DHCP in our environment where I build our servers, is it required to get a first IP address to hit my kickstart server running on my xandros debian laptop? Just been a couple years since I last did some kickstart builds and I dont have system-config-kickstart running on a machine here in my home lab.
I can turn on DHCP on my linux laptop perhaps, but just wanted to check in here before I over-engineer something.
You can put the initial ip address settings in the anaconda boot line, e.g.:
linux ks=http://path/to/your/ks/file/server-and-file ip=$INITIAL_IP_ADDRESS netmask=255.255.255.0 gateway=$GATEWAY_ADDRESS dns=$DNS_SERVER_ADDRESS
This is documented in /usr/share/doc/anaconda-10.1.1.46/command-line.txt (on my centos-4 system, at least).
I have a line in the kickstart file that gives the machine it's network addressing like this (fictional IPs):
Well, obviously, it can't get the kickstart file from the server without being on the network first.
-
Aleksandar Milivojevic -
Elrako X. Harkonnen -
Joshua Baker-LePain