Skip to main content

Kickstart Post Installation Steps in ks.cfg

Installing linux with kickstart server, post installation script can be used in order to make specific changes or install additional softwares.This can be done by adding commands after %post section in ks.cfg file.


#platform=x86, AMD64, or Intel EM64T
# System authorization information
auth  -useshadow  -enablemd5
# System bootloader configuration
bootloader -location=mbr
# Clear the Master Boot Record
zerombr
# Partition clearing information
clearpart -all -initlabel
# Use graphical install
graphical
# Firewall configuration
firewall -disabled
# Run the Setup Agent on first boot
firstboot -disable
# System keyboard
keyboard trq
# System language
lang en_US
# Installation logging level
logging -level=info
# Use network installation
url -url=ftp://<kickstart-server-ip>/pub/RH5-64
# Network information
network -bootproto=static -device=eth0 -gateway=<gateway-ip> -ip=<host-server-ip> -nameserver=<dns-server-ip> -netmask=<netmask> -onboot=on -hostname <hostname>
# Reboot after installation
reboot
#Root password
rootpw -iscrypted cwooefjw93>>1$£#gfhlffghk//54sd4
# SELinux configuration
selinux -disabled
# System timezone
timezone -isUtc Europe/Istanbul
# Install OS instead of upgrade
install
# X Window System configuration information
xconfig  -defaultdesktop=GNOME –depth=8 -resolution=1024×768
%packages
@base
@development-libs
@legacy-software-development
@text-internet
@editors
@legacy-software-support
@mysql

%post
sed -i 's/id:5:initdefault:/id:3:initdefault:/' /etc/inittab
chkconfig sendmail off
chkconfig cups off
cd /root
wget –mirror -nH –cut-dirs=1 ftp:// <kickstart-server-ip>/pub/jboss-installation
chmod 755 /root/jboss-installation/jboss-inst.sh
/root/jboss-installation/jboss-inst.sh
cat >> /etc/profile <<EOF
alias dp='cd /opt/jboss/jboss/server/default/deploy'
alias serverxml='vi /home/jboss//server/default/deploy/jboss-web.deployer/server.xml'
alias jlog='tail -f /opt/jboss/jboss/server/default/log/server.log'
EOF
reboot

Comments

Popular posts from this blog

Creating Multiple VLANs over Bonding Interfaces with Proper Routing on a Centos Linux Host

In this post, I am going to explain configuring multiple VLANs on a bond interface. First and foremost, I would like to describe the environment and give details of the infrastructure. The server has 4 Ethernet links to a layer 3 switch with names: enp3s0f0, enp3s0f1, enp4s0f0, enp4s0f1 There are two bond interfaces both configured as active-backup bond0, bond1 enp4s0f0 and enp4s0f1 interfaces are bonded as bond0. Bond0 is for making ssh connections and management only so corresponding switch ports are not configured in trunk mode. enp3s0f0 and enp3s0f1 interfaces are bonded as bond1. Bond1 is for data and corresponding switch ports are configured in trunk mode. Bond0 is the default gateway for the server and has IP address 10.1.10.11 Bond1 has three subinterfaces with VLAN 4, 36, 41. IP addresses are 10.1.3.11, 10.1.35.11, 10.1.40.11 respectively. Proper communication with other servers on the network we should use routing tables. There are three

Listing Zimbra Accounts with Some Details

Recently I have to export the user list for a particular domain. Luckily Zimbra has Admin GUI with a search feature. When you search accounts, you can download search results as a comma-separated csv file. So I did a search and download the result file, but the result did not have all the columns I need and also there is no option for customizing columns for search results. So I had to write a bash script to get the desired list. Here is the bash script ( It can be customized by adding or removing field names. Run it under zimbra user like ./zimbra_account_list.sh <domain_name_here> ):