Implementing Custom Linux System: Kickstart Configuration

For this assessment, you will be given a specific set of requirements to implement a custom Linux system. For example you may be asked to build a deployable server to run an e-commerce server. You will analyse the requirements and propose a Linux implementation to meet the needs of the application. You should be looking to deliver optimum performance for the scenario. Your final system will need to be customised in terms of:

• Packages installed and running
• Kernel options included
• Run level or operating mode
• Custom scripts to automate administration functions
• Security and firewall settings

To be able to reliably build and implement your solution on a new Linux instance you should provide:

• Kickstart configuration files to install the specific packages needed for your solutions
• A shell script containing any post-install customisation settings needed for your system (such as SELinux settings or configuration files) [Ideally this is done in the %post section of your anaconda ks file]
• Instructions for any customisation that cannot be automated
• Documentation to discuss the choices you have made for the system justifying the packages and features you have implemented and those you left out

You are required to setup a deployment service to allow new instances of Centos 8 linux to be installed over the network using the kickstart system. There are three specific target installations you will need to prepare a kickstart configuration file for:

Centos Minimal
A basic installation of Centos without a graphical user interface. Only the default packages for a base install need to be present

Centos Desktop Graphical
Build a version of Centos which installs a graphical user interface such as Xfce. You should not use Gnome. This platform should include appropriate packages to be compatible with Windows Server including Windows shared network drives. You should also install appropriate desktop productivity software.

Moodle Server
A server-based Centos system with built-in support for the Moodle VLE platform. Web server and database packages can be pre-installed using kickstart but you will need to script the installation of Moodle. Final setup must be documented in your report. Your Moodle server will need some setup and security steps such as firewall settings performing at part of the setup. This third server tests your scripting ingenuity – ultimately some interactive steps may not be possible. If you cannot get a necessary step to complete in the install you should document the additional tasks that need to be performed.

These kickstart configurations are intended to be used for unattended installs. The test interface would be preferable and steps like accepting licence agreements should be automated.

When you are building your systems you can either use a downloaded iso image or one of the versions available from

Use the TFTP boot method we used in class with VirtualBox for your test environment.

A test kickstart server is provided at where you can upload test config files and link to them in your pxelinux.cfg/default menu. You can login to this server using your regular login and your student number as your password. If you don’t have an account Adam can create one for you. Do not share your account.

Bundle these four files as a zip file and upload them using the link provided on Moodle labelled “Configuration Files”. You can also include a README file in your zip if you feel there is any information you need to include so that your setup can be tested.

Secondly write a short report to explain:

• The changes you made to the kickstart file for each system
• The reason for your changes
• Discussion of the process of integrating Windows and Linux systems and whether this is preferable to just using one or the other
• Any appropriate sources or references you used in each case

Upload this using the turn-it-in link on Moodle labelled “assignment 1 report”.