Free Trial

Safari Books Online is a digital library providing on-demand subscription access to thousands of learning resources.

Share this Page URL
Help

Chapter 8. Network Installs > Automating Kickstart - Pg. 228

228 Hands-on Guide to the Red Hat ® Exams: RHCSA TM and RHCE ® Cert Guide and Lab Manual # Carve out the disk with Logical Volumes logvol / --fstype ext3 --name=LogVol00 --vgname=VolGroup00 --size=5000 logvol /home --fstype ext3 --name=LogVol01 --vgname=VolGroup00 --size=1000 logvol /var/log --fstype ext3 --name=LogVol02 --vgname=VolGroup00 ­size=1000 logvol swap --fstype swap --name=LogVol03 --vgname=VolGroup00 --size=1024 Although this example might seem similar to the basic partitions, you must define the Physical Volume, Volume Group, and Logical Volumes in this order; other- wise, you get errors (which are not always the best in kickstart). A nice trick for creating a kickstart file without having to manually type one out is to walk through an installation normally. As you may remember from the first chapter in the book, when you finish installing a system, a file called anaconda-ks.cfg is created in the root user's home directory. This file is actually a kickstart file of all the actions you took during the installation of the system. You can copy it over to your kickstart server, and voila, you're done. Suppose you don't want to go through the process of reinstalling a server every time you need a reference machine. Luckily, there is also a GUI tool that enables you to build kickstart files much more easily. You could use this tool instead of building the kickstart files from the command line. However, you need a desktop manager (be-