Skip to main content

Starting a Kickstart Installation

If you do an installation of a Linux server over the network (called a "network install"), you'll save yourself a lot of time: you don't need to change CDs. You can also automate installation with a so-called "scripted install" using a kickstart file. This will get you an "unattended installation". A sample file anaconda-ks.cfg is saved in /root at the end of every manual install. You can use that as a starting point to create your own.
When doing a network installation of Linux, you can tell Linux to use the kickstart file using a range of options. Please check the Red Hat docs for your favorite options.

How do you do a network installation when booting from a CD (or PXE server)? Simple!
Insert CD 1, or mount that image through DRAC or iLO, at boot the machine. At the first command line of the boot CD type:
linux ks=http://server/path/kickstart_file.cfg url=http://server/path

For instance, 
linux ks=ftp://myserver/default-ks.cfg url=ftp://myserver/

where you have an ftp server running at hostname myserver and you have the CD contents (of ALL CDs) copied in the root of that ftp server. default-ks.cfg contains all your installation options.
Labels:

Comments

Post a Comment

Popular posts from this blog

Tuning the nscd name cache daemon

I've been playing a bit with the nscd now and want to share some tips related to tuning the nscd.conf file. To see how the DNS cache is doing, use nscd -g. nscd configuration: 0 server debug level 26m 57s server runtime 5 current number of threads 32 maximum number of threads 0 number of times clients had to wait yes paranoia mode enabled 3600 restart internal passwd cache: no cache is enabled [other zero output removed] group cache: no cache is enabled [other zero output removed] hosts cache: yes cache is enabled yes cache is persistent yes cache is shared 211 suggested size <==== 216064 total data pool size 1144 used data pool size 3600 seconds time to live for positive entries <==== 20 seconds time to live for negative entries
2 comments
Read more

Preventing PuTTY timeouts

Just found a great tip to prevent timeouts of PuTTY sessions. I'm fine with timeouts by the host, but in our case the firewall kills sessions after 30 minutes of inactivity... When using PuTTY to ssh to your Linux/Unix servers, be sure to use the feature to send NULL packets to prevent a timeout. I've set it to once every 900 seconds, i.e. 15 minutes... See screenshot on the right.
1 comment
Read more

Setting up SR-IOV in RHEL6 on PowerEdge servers

Dell Community : "RHEL 6 provides SR-IOV functionality on supported hardware which provides near native performance for virtualized guests. Single-Root I/O Virtualization (SR-IOV) specification, introduced by PCI-SIG details how a single PCIe device can be shared between various virtualization guests. Devices capable of SR-IOV functionality support multiple virtual functions on top of the physical function. Virtual Function is enabled in hardware as a light weight PCIe function. Operating System cannot discover this function as it does not respond to the PCI bus scan and requires support in the host’s driver. As in PCIe pass-through, a Virtual function of a SR-IOV capable card can be directly assigned to the guest operating system. A virtual function driver running in the guest manages this device."
3 comments
Read more