Today is the third guest article in a row, and is one more article about Kickstart. There will be more Kickstart articles, but we’ll release those in time. This is the third one in a row, so we’ll try to mix it up a bit.
By now, we should all have at least a little familiarity with Kickstart. Frankly, I’ve still not had a chance to use it – but it does seem like it’d be fun to play around with it. If I were an admin of anything major, I’d definitely look to Kickstart as a solution. Again, if you read this on day one, be sure to check back later as the author may suggest some edits.
See the previous articles here:
Guest Article: Kickstart Vol. I
Guest Article: Kickstart Vol. II
Kickstart Vol. III
Now we need to create a menu for your Kickstart, so you can select which OS you want to install.
Shell
Now edit a new file named grub.cfg. It must be named grub.cfg. Here is an example of what it should look like.
Shell
The set-default lets you pick which is the default install, it starts at zero, so the options here would be 0, 1 and 2.
Note the IP address of my Kickstart server is here, the path to my extracted iso directory is here, and the location of my boot kernels is here.You can change all of these to fit your needs.
Now we need the actual anaconda-kickstart.cfg files, this is what actually does all the work.The location of these, is set in the grub.cfg file above. You will want these to be in the extracted iso directory, but not in the “dvd sub-directory.
Here is an example of what one of these would look like. This one is fairly basic.
Shell
Again you see the IP address of my kickstart server here, you see the location of my extracted iso files here.Now there are a few things you will need to know in advance.
What I typically do, is install the OS from a USB the first time.In the case of fedora/redhat/CentOS there will be a file at /root/anaconda.cfg. You can copy this file as a starting template for your kickstart of this OS.
Shell
(Yes I am re-naming the file here.)
Also you will need the password has strings for your users.
Shell
(Or whatever user name you use.)
You will need to know the name of the LAN interface, and you will need to know the size of your hard, and how big the partitions should be.All of these things will be in your anaconda.cfg file
Now change and edit a few things in your fed35srv/fed35.cfg file now.
Change the graphical install to..testskipx This uses a cli interface, not a GUI when installing.
Change the url line to the location of your extracted iso directory in your web server. Note you don’t put the full path, only the path from your webroot.
I like to turn off seLinux, but you can delete that line if you like.
Change your timezone to whatever is appropriate for you.
Using the two example user lines above (those aren’t real hashes, I just typed a bunch of random characters to simulate what it looks like). Edit the user lines to be whatever your values are.
That’s it, you’re don! Now boot your test computer on the kickstart network. A Kickstart menu should appear. Select the appropriate OS.
I’ve found this usually works best with a few settings on the test computer. CSM should be disabled. Network stack should be enabled. Some UEFI settings let you pick PXEboot IPv4 as a boot option. This is preferred. I’ve found it works best with a freshly formatted hard-drive, that way it doesn’t try to boot into the installed OS.
Good luck!
Closure:
And there you have it! You have a guest article, from dos2unix, about Kickstart. There are now three of them and there are a couple of others sitting in the potential queue. We’ll get to them. These few days off have been a very welcomed respite!