Linux- Kickstart Based Installation

KickStart provides a way for users to automate a Red Hat Enterprise Linux installation.

Here are simple steps:


1.Install Apache.

[root@ranjith ~]# rpm -qa |grep -i httpd

[root@ranjith ~]# yum -y install httpd
[root@ranjith ~]# lsof -i tcp:80
COMMAND   PID   USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
httpd   10787   root    4u  IPv6 223062      0t0  TCP *:http (LISTEN)
httpd   10789 apache    4u  IPv6 223062      0t0  TCP *:http (LISTEN)
httpd   10790 apache    4u  IPv6 223062      0t0  TCP *:http (LISTEN)

2. Create a install root where we gonna installing the contents of the cdrom to, We can use under default document root in /var/www/html.


[root@ranjith ~]# cd /var/www/html/

[root@ranjith html]# mkdir centos5

[root@ranjith html]# cd centos5/

[root@ranjith centos5]# pwd
/var/www/html/centos5

3. Download and mount the centos ISO file from: centos.org

Here i download: CentOS-6.4-x86_64

4. Mount the iso you downloaded to a mount point.

[root@ranjith mnt]# mount -o loop CentOS-6.4-x86_64-bin-DVD1.iso /mnt

[root@ranjith mnt]# du -sch /mnt
4.1G    /mnt
4.1G    total


5. Copy the contents of the iso into the directory you created.

[root@ranjith mnt]# cp -var /mnt/* /var/www/html/centos5/

6. Create a directory to house your kickstart configurations under Apache’s default document root of /var/www/html


[root@ranjith html]# mkdir kstart

[root@ranjith html]# cd kstart/

[root@ranjith kstart]# pwd
/var/www/html/kstart

7. Create the kickstart configuration file, kstart.cfg under kstart directroy. In kstart.cfg file kindlly place the below code.


#text-based insatllation.
text
install
url --url http://YOUR-SERVER-IP/centos5 // server-IP here
lang en_US.UTF-8
keyboard us
langsupport --default=en_US.UTF-8 en_US.UTF-8
network --device eth0 --bootproto dhcp
rootpw --iscrypted $1$/ABCabcABC/ // Password here
firewall --disabled
selinux --disabled
authconfig --enableshadow --enablemd5
timezone America/New_York
bootloader --location=mbr --append="console=xvc0"

# basic root, boot, swap partitioning here

zerombr yes
clearpart --all
part /boot --asprimary --fstype="ext3" --size=100 --bytes-per-inode=4096
part swap --asprimary --fstype="swap" --recommended --bytes-per-inode=4096
part / --asprimary --fstype="ext3" --grow --size=1 --bytes-per-inode=4096
reboot

# Utilities here

%packages --nobase
authconfig
crontabs
kbd
kudzu
man
ntp
openssh-clients
openssh-server
passwd
pciutils
rootfiles
rpm
system-config-securitylevel-
tui
traceroute
yum
yum-updatesd
vim-minimal
vixie-cron
which
wget
unzip
kudzu
man
ntp
openssh-clients
openssh-server
passwd
pciutils
rootfiles
rpm
system-config-securitylevel-tui
traceroute
yum
yum-updatesd
vim-minimal
vixie-cron
which
wget
unzip
sudo
%post
(
chkconfig --level 3 ip6tables off
chkconfig --level 3 kudzu off
chkconfig --level 3 netfs off
chkconfig --level 3 yum-updatesd off
#
useradd -p 'webmaster' someotheruser
)  2>&1 | tee /root/post-install.log

8. Use the dvd you downloaded or grab a copy of the boot.iso from the install root. You can either use the install DVD iso you or use the 10MB boot.iso located in centos5/images/boot.iso I choose to use the boot.iso since its 10MB and is easily distributable.

9. start the web-server.

[root@ranjith html]# /etc/init.d/httpd start
Starting httpd:                                            [  OK  ]
10. Boot the system with boot.iso or install DVD. On the boot prompt enter:

linux ks=http://your_kickstart_ip/kstart/kstart.cfg

cheers!!!

Comments

Post a Comment

Popular posts from this blog

Resolved: DOCKER: Error response from daemon: Could not attach to network / rpc error: code = 7 desc = network not manually attachable.

Image
I got this error: 'docker: Error response from daemon: Could not attach to network <nw-name>: rpc error: code = 7 desc = network <nw-name> not manually attachable.' when i try to create the container on the overlay network on swarm mode enabled, In docker 1.12 with swarm mode enabled, "Swarm" scoped networks (see the "SCOPE" column) cannot be used for docker run, only for services and now it has been rectified. I'm using updated version of docker, but still why i'm experiencing the error ? because the network just created but not manually attachable. To fix the issue we gonna use --attachable flag while creating network. [ --attachable             Enable manual container attachment ] (Need to create service on the overlay network, so that the overlay network will available / list on the worker node) docker inspect attnw (attnw is our test network)should show your own c
Read more

yum failed 6 times. Cannot continue!

Error while cPanel installation: (ERROR): - ssystem [EXIT_CODE] '/usr/bin/yum' exited with 1 (ignored) (DEBUG): - ssystem [END] (FATAL): yum failed 6 times. Cannot continue! fix: It looks like you have some name resolution issues on the server. Just run the following commands on your server and it will resolve the name resolution issues. #echo "nameserver 8.8.8.8" >> /etc/resolv.conf #echo "nameserver 8.8.4.4" >> /etc/resolv.conf if it is not working properly still facing same error, then here we go, # rpm -e --nodeps bind-chroot # rpm -e --nodeps bind # yum install bind
Read more

unexpectedly shrunk window (repaired) in dmesg log - TCP Peer

Don't Panic, This normally occurs when a client decides to reduce its TCP window size, without the server expecting it. This can be the case when fragmentation is an issue, or when the client is using an embedded device with very little NIC buffer memory. This is a completely normal behaviour, and you’re likely to see quite a few such packets in your log. The messages are informational only, and are used to debug networking issues. I’d be worried if you saw hundreds of thousands of these packets, since there are attacks that involve packet fragmentation and small window sizes, but otherwise it’s just the normal sort of noise you should expect to see on any internet-facing network. In fact, the “repaired” part of your message is showing that your network driver fixed the issue, which is usually done by concatenating the payloads of two fragmented packets together. Shouldn’t be an issue at all. … … … … … … … … … … … … … … … … … … … … … … … … … … … … … … … 
Read more