Creating a boot image that is using a remote kickstart file to install Red Hat

News Kickstart Recommended Books Recommended Links Modifying ISO image to include kickstart file Minimization of boot ISO  VNC-based Installation in Anaconda
Creating a boot image that is using a remote kickstart file to Install a system Modifying ISO image to include kickstart file Installation of Red Hat from a USB drive Installing RHEL via HTTP Installing via NFS   Loopback filesystem
  Administration Networking Move config files from one server to another Kickstart Pre- and Postinstall Scripts Humor Etc

Introduction

With UEFI boot, Red Hat 7, and HP ILO 4 things became way too complex.  The traditional BIOS can only boot from drives of 2.1 TB or less. If you have drives larger then that your only option is UEFI.  Other then that you can simplify you life sticking to traditional BIOS, unless you use some fancy options and UEFI provide advantages in this area.

There is no free lunch. while a more capable booting system, UEFI introduces additional complexity including, but not limited to,  a special 200MB UEFI partition which should be formatted as FAT. That's throws a monkey wrench into some operations related to kickstart, specifically to the modification of ISO disk to include reference to remote kickstart file in the boot menu. This is not fatal, but still if can aviod those troubles you should.  also incase of UEFI boot manager installed in the boot partition, but most server hardware is able to deal with this non-standard situation and boot correctly even if boot loader is located incorrectly.

RHEL 7 is another story of adding complexity to already very complex system. For booting, most of this complexity is related to use of systemd instead of initd and replated changes of how you work with networking. "What if we just don't do any of that bullshit?" is indeed a great question to ask in this case. May be you need to simplify a system not to make it more complex.

Combination of several complex, poorly understood (due to excessive complexity and the fact that installation represents only a tiny chunk of sysadmin workload)  subsystems lead to the  situation when everything became kind of brittle as in "one step left or one step right and guards shout without warning". Kind of electronic gulag for system administrators ;-). In other words, when you are using Kickstart for servers with UEFI boot,  you are walking of eggshells.  that actually means that for servers that still have disks less then 2TB good old MBR might still be a better option ;-).  What is interesting that with identical blades and identical kickstart files RHEL 6.9 Anaconda it gave me several different error messages during the installation.  Also it does not like hard drive that was not initialized and asks for confirmation. That can be suppressed via option --initlabel in clearpart statement of you ks.cfg. .

Kickstart used to work pretty well probably up to RHEL 6.5. Not any more.  

The key idea for using kickstart for unattended installation of multiple severs is creating  modified boot image of RHEL which included modified isolinux.cfg. Which in turn specify the location of the kickstart file and the necessary network information. It should be simple and well documented. But it is neither. And recently I need to install Red Hat on 12 servers and I spend more than 20 hours trying to make it work on RHEL 6.8, which helped slight improve this page (note this was not even 7.x  with  its own set of warts ;-).

If I just did it manually I probably could save half of this time, doing several installations in parallel  ;-).   Of course HP hardware presents its own can of worms, but I digress.

In any case the best way to access kickstart file is to put it on HTTP server, if you know this staff. If not then NFS is another option. After that comes FTP.   

Highlights of this process

Preliminary steps

  1. Install the required packages to create ISO9660 images, as follows:
    yum install -y genisoimage
  2. Mount the boot image
    mount -o loop /path/to/rhel-server-boot-image.iso /mnt
  3. Copy the required files  preserving attributed

STEP 1: First you need to modify specific line in the fist (default) item of boot menu in  isolinux.cfg

Modify append line in the first section of boot option in the isolinux.cfg file assign as a minimum location of ks.cfg on HTTP server and what Ethernet interface should be used (servers usually have multiple Ethernet interfaces. Two ports are minimal. for posts are common.  In case of static IP you need also provide the usual troika (IP/netmask/default router). 

STEP 2: You need to verify the files on you HTTP sever has right permission and are assessable.

STEP 3:  You need to modify your prototype kickstart file obtained from the server. Kickstart file generated by anaconda for your first server (the one that you installed manually) has directives for creating partitions commented out. you need to uncomment and correct them.

STEP 4: Verify parts of kickstart file using Kickstart Configurator and, if necessary make some corrections.  Please note that Kickstart Configurator is completely broken and after you load your kickstart file into it will never produce correct modified file. But some sections of generated file can be re-used to modify your initial file ks.cfg file manually. One useful feature is more precise selection of packages. If you experience errors, of if it crashes when you attempt to save file you can try first to preview you modified kickstart file and then save it. sometimes this work. If not you can select all area in preview using Ctrl-A and  copy it to your text editor window. See  Chapter 29. Kickstart Configurator

STEP 5:  Put back the modified file in image and test resulting image. It should be bootable. Recently this part became most difficult part due to existence of  UEFI boot partition

Possible further minimization of boot image

If you work via VPN and do not have Advanced license on HP server (you can get trial licence for 30 days from HP for free; that's usually enough for initial installation of OS)  further minimization of image can be important for you.

  1. You can copy only /isolinux folder. It is enough for this purpose. For example
    mkdir -p /root/iso
    cp -r /mnt/isolinux /root/iso
    umount /mnt
  2. You can minimize boot  menu to just two items, deleting the rest.  this does not make much sense, but there is such possibility if you like to experiment :-) The content above the first  label linux statement is not critical to the task in hand.
    rm -f /root/iso/isolinux/isolinux.cfg
    The resulting "tail" of  "standard"  isolinux.cfg file might look as following"
    label linux
      menu label ^Install Red Hat Enterprise Linux 6.8
      kernel vmlinuz
      append initrd=initrd.img ks=10.10.10.19/kickstart.ks ksdevice=eth0 ip=dhcp
    label local
      menu label Boot from ^local drive
      localboot 0xffff
    
    menu end

Creation of modified ISO file

Now we need to create the ISO. There are two different situations here

  1. You use traditional BIOS. In this case you  just need to rebuild ISO using mkisofs
    cd /location_of_file_tree_created_from_boot_cd # for example /svr/www/Boot
    mkisofs -o ../myboot.iso -b isolinux/isolinux.bin -c isolinux/boot.cat --no-emul-boot --boot-load-size 4 --boot-info-table -J -R -V disks .

    Also works

    mkisofs -o ../myboot.iso -b isolinux/isolinux.bin -c isolinux/boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table -J -r .

    The resulting ISO image should be bootable and should pick up the necessary ks.cfg file.

    NOTE: mkisofs command in the form above is suitable only for legacy boot (MBR based) --  it does not create UEFI boot partition in the following example. As the result the resulting  image will be much smaller then the original and will not boot:
     

  2. You have UEFI BIOS.

    In case you server uses UEFI boot it is easier to said then done, because UEFI partition if FAT-based.

    mkisofs -o /tmp/efiboot.iso -b isolinux/isolinux.bin -c isolinux/boot.cat --no-emul-boot --boot-load-size 4 \
    --boot-info-table -eltorito-alt-boot -e images/efiboot.img \
    -graft_points EFI/BOOT=/mnt/EFI/BOOT images/efiboot.img=/mnt/images/efiboot.img \
    -no-emul-boot -J -R -V disks .

    (assuming you boot image is mounted on /mnt )

    After that you need to run

    isohybrid --uefi efiboot.iso

     Quoting from How can we create a customized Golden Image or RHEL ISO with kickstart file:

    Rebuild the DVD iso image
        # cd /rhel
        # mkisofs -o /tmp/new.iso -b isolinux/isolinux.bin -c isolinux/boot.cat  --no-emul-boot --boot-load-size 4 --boot-info-table -J -R -V disks .
    

    NOTE: In RHEL7, please make sure that you specify the volume id with -V option, and it's same as Volume_ID in step 6.

    8. Boot the machine from this ISO

    Kickstart has detailed documentation in the Installation Guide

    Important Note:

    • The image which will be created using the steps above won't be UEFI enabled. So to have an UEFI enabled image, use the following extra options.
    
    
    • And the graft point as follows.
    EFI/BOOT={0}/EFI/BOOT images/efiboot.img={0}/images/efiboot.img
    
    • Where {0} is replaced by the location where the existing DVD is mounted/extracted.
    • One should also run isohybrid on it so that it can be booted by both BIOS and UEFI:
    isohybrid --uefi boot.iso 

    but this truncated ISO image might still be bootable if your server has legacy boot option.

    More information on the options used with the mkisofs command can be found in the man pages for mkisofs(1).

    Google is also you friend but it does not provide useful references in this case.  Opening Red hat ticket is another option and if you are perssisten anough they might even help, not just bounce you to some semi-useless documents that they found by searching their database for relevant keywords.

Note of UEFI issues with USB sticks

Here is an exchange from microsoft Technet forum that explains the problem: Creating a bootable USB stick - differences between UEFI-BIOS and GPT-MBR

EckiS August 02, 2016
When it were true that a different USB stick was needed for different Bios, then the Windows Installation media could never boot on all Bios versions. But it can.

Maybe you formatted the USB stick with NTFS? On the page you linked:

If your server platform supports Unified Extensible Firmware Interface (UEFI), you should format the USB flash drive as FAT32 rather than as NTFS. To format the partition as FAT32, type format fs=fat32 quick, and then click ENTER.

....

XXX

Thanks, Ecki,

that's exactly my point of view.

In the forum a user claimed that that'd be true for DVDs but not for USB sticks. Now I want to make sure. And I want to make clear for every user out there that there is no peculiarity to UEFI except for a requirement of "\efi\boot\bootx64.efi" existing on the boot media.

... ...

XXX

From what I read (and from what I tested): UEFI can not boot from NTFS:

https://en.wikipedia.org/wiki/EFI_system_partition#Overview

https://github.com/pbatard/rufus/issues/589

https://blogs.technet.microsoft.com/askcore/2013/03/20/creating-bootable-usb-drive-for-uefi-computers/

XXX
Last week I received a Microsoft OEM Windows 10 Recovery USB stick from HP. That stick is formatted in NTFS (hell knows why, as it doesn't work with UEFI).

Trying to copy its contents to my USB stick (which I formatted FAT32) failed, because HP added a file larger than 4GB.

Now this is really getting difficult. I guess I'll need to use Rufus now in order to create a USB Stick layout having two partitions: The Active one using FAT, containing just the NTFS drivers and the UEFI boot loader, and a second partition using NTFS containing the contents from the HP/Microsoft OEM Windows 10 Recovery USB stick.

Gee ... Did no one at Microsoft/HP think of testing their USB stick when buring data to it?

RUFUS

Rufus - Create bootable USB drives the easy way

Create bootable USB drives the easy way
[rufus screenshot]

Rufus is a utility that helps format and create bootable USB flash drives, such as USB keys/pendrives, memory sticks, etc.

It can be especially useful for cases where:

 

Despite its small size, Rufus provides everything you need!

Oh, and Rufus is fast. For instance it's about twice as fast as UNetbootin, Universal USB Installer or Windows 7 USB download tool, on the creation of a Windows 7 USB installation drive from an ISO. It is also marginally faster on the creation of Linux bootable USB from ISOs. (1)
A non exhaustive list of Rufus supported ISOs is also provided at the bottom of this page.

Notes on ISO Support:

All versions of Rufus since v1.1.0 allow the creation of a bootable USB from an ISO image (.iso).

Creating an ISO image from a physical disc or from a set of files is very easy to do however, through the use of a CD burning application, such as the freely available CDBurnerXP or ImgBurn.

Notes on UEFI & GPT support:

Since version 1.3.2, Rufus support UEFI as well as GPT for installation media, meaning that it will allow you to install Windows 7, Windows 8 or Linux in full EFI mode.
However, Windows Vista or later is required for full UEFI/GPT support. Because of OS limitations, Windows XP restricts the creation of UEFI bootable drives to MBR mode.

 


Heelo
Top Visited
Switchboard
Latest
Past week
Past month


NEWS CONTENTS

Old News ;-)

[Aug 10, 2017] Kickstart Problem with --initlabel

Notable quotes:
"... Last edited by phatrik; 08-07-2012 at 11:17 AM . Reason: prefixed with solved ..."
Aug 07, 2012 | www.linuxquestions.org
phatrik
Kickstart: Problem with --initlabel

I'm having a problem when using kickstart to deploy CentOS 6.3 KVM guest OS and no one seems to know why so I figured I'd ask in the KVM SF :-) Details:

- Tyring to install CentOS 6.3
- Doing a netinstall using a FTP site
- The installation is for a guest OS (KVM).

The install is being launched with:

virt-install -n server1.example.com -r 768 -l /media/netinstall -x "ks=ftp://192.168.100.2/pub/ks.cfg"

The install starts and gets to the point where I see "Error processing drive. This device may need to be re-initialized." The relevant part of my KS file:

clearpart --initlabel --all

# Disk partitioning information

part /boot --fstype="ext4" --size=500
part /home --fstype="ext4" --size=2048
part swap --fstype="swap" --size=2048
part / --fstype="ext4" --grow --size=1

When I switch to the 3rd terminal for information, here's what I see:

required disklable type for sda (1) is None
default diskalbel type for sda is msdos
selecting msdos diskalbel for sda based on size

Based on "required diskalbel type for sda (1) is none" I decided to remove the --initlabel parm, however I still face the same problem (prompted to initialize the disk).

TIA

Erik


Last edited by phatrik; 08-07-2012 at 11:17 AM . Reason: prefixed with solved
dyasny 08-07-2012 Registered: Dec 2007 Location: Canada Distribution: RHEL,Fedora Posts: 995
I'd just abandon virt-install and deploy VMs from a template instead. Much faster and easier to do
phatrik 08-07-2012, 08:14

Thank you for your reply, but that's obviously not the answer I'm looking for. Yes I know virt-clone could be used but what I'm truly interested in is getting at the bottom of this problem.

wungad

From RedHat Knowledge base
Issue

The 'clearpart --initlabel' option in a kickstart no longer initializes drives in RHEL 6.3.

Environment
Red Hat Enterprise Linux 6.3
Anaconda (kickstart)

Resolution

Use the 'zerombr' option in the kickstart to initialize disks and create a new partition table.

Use the 'ignoredisk' option in the kickstart to limit which disks are initialized by the 'zerombr' option. The following example will limit initialization to the 'vda' disk only:
zerombr
ignoredisk --only-use=vda

phatrik

Thank you for your reply, that's exactly what I was looking for.

Quote:

Originally Posted by wungad View Post Issue
The 'clearpart --initlabel' option in a kickstart no longer initializes drives in RHEL 6.3.

Environment

Red Hat Enterprise Linux 6.3
Anaconda (kickstart)

Resolution

Use the 'zerombr' option in the kickstart to initialize disks and create a new partition table.
Use the 'ignoredisk' option in the kickstart to limit which disks are initialized by the 'zerombr' option. The following example will limit initialization to the 'vda' disk only:
zerombr
ignoredisk --only-use=vda

[Aug 08, 2017] Kickstart option to set GRUB drive location?

Notable quotes:
"... ignoredisk --drives=sdb ..."
Aug 08, 2017 | www.centos.org

andersbiro " 2010/03/04 12:36:32

Hello, I have successfully created a Centos USB stick installation with an automated kickstart configuration according to the instructions at http://wiki.centos.org/HowTos/InstallFromUSBkey .

Everything works flawlessly with the exception that the installation writes the GRUB Boot Loaders on the USB stick instead of the destination hard drive and hence can only be booted from the USB stick.

Afterwards I can solve this manually by editing grub.conf to point to the hard drive and using the grub utility I can nstall the Grub loader on the hard drive MBR instead and then it boots normally.

The aim is however to create a fully automated installation since the end users in question are expected to be technically proficient so my question is if there is a kickstart option to explicitly write GRUB correctly to the hard drive from the very beginning?

There seems to be a kickstart "bootloader" option but I can not really see any flags that would explicitly set the GRUB on a specified hard drive? Top


AlanBartlett
Forum Moderator
Posts: 9310
Joined: 2007/10/22 11:30:09
Location: ~/Earth/UK/England/Suffolk
Contact: Contact AlanBartlett Website
Re: Kickstart option to set GRUB drive location?

Post by AlanBartlett " 2010/03/04 18:52:16

In the CentOS wiki article that you reference, under the heading Notes , there is a [color=ff1480]cherry-red[/color] block of text. Isn't that appropriate?

If not, do you have any suggestions for improvement to the article? Top


pschaff
Retired Moderator
Posts: 18276
Joined: 2006/12/13 20:15:34
Location: Tidewater, Virginia, North America
Contact: Contact pschaff Website
Kickstart option to set GRUB drive location?

Post by pschaff " 2010/03/04 21:36:41

andersbiro wrote:
...
There seems to be a kickstart "bootloader" option but I can not really see any flags that would explicitly set the GRUB on a specified hard drive?

How about Kickstart Options : Code: Select all

bootloader (required)
Specifies how the boot loader should be installed. This option is required for both installations and upgrades.

* --append= ? Specifies kernel parameters. To specify multiple parameters, separate them with spaces. For example:

bootloader --location=mbr --append="hdd=ide-scsi ide=nodma"

* --driveorder ? Specify which drive is first in the BIOS boot order. For example:

bootloader --driveorder=sda,hda

* --location= ? Specifies where the boot record is written. Valid values are the following: mbr (the default),
partition (installs the boot loader on the first sector of the partition containing the kernel), or
none (do not install the boot loader).

Still can't guarantee that a totally automated approach is possible, unless the hardware is identical, as the devices and ordering will be system-dependent. :-( Top


andersbiro
Posts: 12
Joined: 2010/02/22 10:07:54
Re: Kickstart option to set GRUB drive location?

Post by andersbiro " 2010/03/08 08:48:17

AlanBartlett wrote:
In the CentOS wiki article that you reference, under the heading Notes , there is a [color=ff1480]cherry-red[/color] block of text. Isn't that appropriate?

If not, do you have any suggestions for improvement to the article?

To my understanding this specific part of the text refers to an interactive installation but since I deal with a fully automatic installation I do not think that part is appropriate so that is why I am looking for corresponding kickstart options to achieve the same thing.
To be fair it also mentions the line bootloader --driveorder=cciss/c0d0,sda --location=mbr" that might be appropriate but since I am not very proficient with completely comprehending the parameters. Top


andersbiro
Posts: 12
Joined: 2010/02/22 10:07:54
Re: Kickstart option to set GRUB drive location?

Post by andersbiro " 2010/03/08 08:58:16

pschaff wrote:
andersbiro wrote:
...
There seems to be a kickstart "bootloader" option but I can not really see any flags that would explicitly set the GRUB on a specified hard drive?

How about Kickstart Options : Code: Select all

bootloader (required)
Specifies how the boot loader should be installed. This option is required for both installations and upgrades.

* --append= ? Specifies kernel parameters. To specify multiple parameters, separate them with spaces. For example:

bootloader --location=mbr --append="hdd=ide-scsi ide=nodma"

* --driveorder ? Specify which drive is first in the BIOS boot order. For example:

bootloader --driveorder=sda,hda

* --location= ? Specifies where the boot record is written. Valid values are the following: mbr (the default),
partition (installs the boot loader on the first sector of the partition containing the kernel), or
none (do not install the boot loader).

I was aware of these parameters but I am not fully sure about how to apply them... the "--location" flag seemed easy enough and also driveorder but the "append" kernel parameters eludes me but perhaps this is not required.

I know that the kernel and Grub part should reside on the first partition of disk "sda" and the USB stick on "sdb" so would setting the "--driveorder=sda,sdb" insure that grub.conf points to the sda disk?

Also, would that automatically write the GRUB loader on "sda" as well or do you need to use the "partition flag" for that? Top


andersbiro
Posts: 12
Joined: 2010/02/22 10:07:54
Re: Kickstart option to set GRUB drive location?

Post by andersbiro " 2010/03/08 12:04:09

As a matter of fact I tried the --driveorder flag and that actually worked as it now can boot directly without USB stick which is a great step forward.
The only remaining obstacle is that somehow the FAT32 partition disappear from the USB stick so it cannot be used for future installations.
This can however be fixed by using FDISK to create a new FAT32 partition in the same space and somehow this also restores the previous file in the partition.

Since the GRUB bootloader seems to be written to the destination disk I must say that I cannot understand at all why the FAT32 partition disappears?
Are additional flags required to prevent this from happening? Top


pschaff
Retired Moderator
Posts: 18276
Joined: 2006/12/13 20:15:34
Location: Tidewater, Virginia, North America
Contact: Contact pschaff Website
Re: Kickstart option to set GRUB drive location?

Post by pschaff " 2010/03/08 12:51:41

andersbiro wrote:
...
Since the GRUB bootloader seems to be written to the destination disk I must say that I cannot understand at all why the FAT32 partition disappears?
Are additional flags required to prevent this from happening?

I have not seen that happen. You have both FAT32 and ext3 partitions, and the FAT32 one is gone after the install? I'd check the kickstart file carefully to be sure it is not inadvertently messing with the USB drive.

Thanks for reporting back, and please keep us posted. Any recommendations for the Wiki article appreciated. Top


andersbiro
Posts: 12
Joined: 2010/02/22 10:07:54
Re: Kickstart option to set GRUB drive location?

Post by andersbiro " 2010/03/08 14:49:12

I managed to solve the issue by adding the "ignoredisk --drives=sdb" parameter for the USB drive and now the installer leaves the USB stick intact and the installation works flawlessly.
I however still do not know why the installer affected the disk in the first place but this flag did at any rate solve the problem for me. Top
pschaff
Retired Moderator
Posts: 18276
Joined: 2006/12/13 20:15:34
Location: Tidewater, Virginia, North America
Contact: Contact pschaff Website
Re: Kickstart option to set GRUB drive location?

Post by pschaff " 2010/03/08 14:53:40

Thanks for the additional info. Still seems that a general solution is elusive, as there's no guarantee that on a different set of hardware the USB drive will show up as /dev/sdb. Top
nektoid
Posts: 1
Joined: 2012/04/03 17:00:26
Re: Kickstart option to set GRUB drive location?

Post by nektoid " 2012/04/03 17:06:27

Hi. I ran into this recently kickstarting both 5.5 and 6.2 hosts. Kickstarts worked one day and the next the bootloader wanted to be on the usb key, odd. This is was an example of what worked for me with 5.5 where the usb key was consistently seen as sdb. Both at their respective parts in the preamble section of ks.cfg.

#stop writing bootloader to usb
bootloader --driveorder=sda,sdb --location=mbr

#stop erasing my usb stick
ignoredisk --drives=sdb

How can we create a customized Golden Image or RHEL ISO with kickstart file

Rebuild the DVD iso image
Raw
    # cd /rhel
    # mkisofs -o /tmp/new.iso -b isolinux/isolinux.bin -c isolinux/boot.cat --no-emul-boot --boot-load-size 4 --boot-info-table -J -R -V disks .

NOTE: In RHEL7, please make sure that you specify the volume id with -V option, and it's same as Volume_ID in step 6.

8. Boot the machine from this ISO

Kickstart has detailed documentation in the Installation Guide

Important Note:

  • The image which will be created using the steps above won't be UEFI enabled. So to have an UEFI enabled image, use the following extra options.
Raw
-eltorito-alt-boot -e images/efiboot.img -no-emul-boot
  • And the graft point as follows.
Raw
EFI/BOOT={0}/EFI/BOOT images/efiboot.img={0}/images/efiboot.img
  • Where {0} is replaced by the location where the existing DVD is mounted/extracted.
  • One should also run isohybrid on it so that it can be booted by both BIOS and UEFI:
Raw
isohybrid --uefi boot.iso 

To use a Kickstart file to install a system:

  1. Boot the system from a bootable medium or from a network installation server that supports PXE client installation. If you need to modify the boot command, press Esc to access the command line. Note, however, that the boot configuration might not allow you to modify the boot command.

    For PXE clients, it is usual to specify the Kickstart parameters in the boot loader configuration. For example, the following example configures a Kickstart installation for a PXE client that boots using pxelinux:

    prompt 0
    default ol6u6
    timeout 0
    
    label ol6u6
    kernel vmlinuz-OL6u6
    append initrd=initrd-OL6u6.img ksdevice=eth0 kssendmac ks=http://10.0.0.11/ksfiles/ol6u6_cfg.ks

    The ksdevice=eth0 parameter specifies the interface to be used for network installation. If a system has multiple network interfaces, this prevents the installation from prompting you to choose an interface. Alternatively, you could specify ksdevice=bootif and add an ipappend 2 entry after the append entry:

    prompt 0
    default ol6u6
    timeout 0
    
    label ol6u6
    kernel vmlinuz-OL6u6
    append initrd=initrd-OL6u6.img ksdevice=bootif kssendmac ks=http://10.0.0.11/ksfiles/ol6u6_cfg.ks
    ipappend 2

    This configuration also prevents you from being prompted to choose a network interface but it does not control which interface is selected.

    The next example configures a Kickstart installation for a PXE client that boots using GRUB:

    default=0
    hiddenmenu
    splashimage=(nd)/splash.xpm.gz
    timeout=0
    title Oracle Linux 6 Update 6 Installation
        root (nd)
        kernel /vmlinuz-OL6u6 ksdevice=eth0 kssendmac ks=http://10.0.0.11/ksfiles/ol6u6_cfg.ks
        initrd /initrd-OL6u6.img
    NOTE:
    1. If you have not customized the boot configuration to use Kickstart, you can use the ks option to specify the location of the Kickstart file.
    2. The following boot command specifies that the Kickstart file is on the boot CD:
    boot: linux ks=cdrom:/ks.cfg
    1. If the Kickstart file is located on an NFS server, you might use a boot command such as the following:
    boot: linux ksdevice=eth0 ip=dhcp ks=nfs:10.0.0.11:/ksfiles/ks.cfg

    where ksdevice=eth0 specifies the network interface and ip=dhcp specifies that DHCP should be used to configure this interface.

    For more information, see Section 2.2, “Installation Boot Options”.

Hands-Off Fedora Installs with Kickstart - O'Reilly Media

Creating the Kickstart Config File, ks.cfg

ks.cfg makes unattended installs possible. It holds canned responses to the questions posed during an interactive install. The examples assume you've saved this file under the web server's document root as kickstart/ks.cfg.

There are several ways to create ks.cfg. (I did warn you that Kickstart was flexible.) If you're plotting a clone farm, build one machine to your specs and use /root/anaconda-ks.cfg on that host as a starting point for the others.

Barring that, use the redhat-config-kickstart GUI (from the redhat-config-kickstart package). This tool doesn't support LVM for disk layout, but is a valuable learning tool nonetheless. You can hand-edit the generated ks.cfg to use LVM (described below).

You can also create or edit ks.cfg using any text editor, provided you know the directives. Here's a walk through the directives in the sample ks.cfg.

You probably already have the redhat-config-language, hwdata, and tzdata RPMs installed already. They are not required, but include files that simplify hand-editing ks.cfg.

Installation Type

The first entries are the installation type and source.

install
url --url http://kickstart-server/FC1-install

The type may be install or upgrade. The url directive specifies an HTTP installation and indicates the URL of the install media. (The directory Fedora, from the install media, must be a subdirectory of the URI part of the URL.) Other installation sources include cdrom for swapping CDs or DVDs, nfs for mounting the install media from an NFS share, and the self-explanatory ftp.

Recommended Links

Softpanorama hot topic of the month

Softpanorama Recommended

Editor's note: Ethan has collected this series and other information into Managing RPM-Based Systems with Kickstart and Yum. This series continues in Advanced Linux Installations and Upgrades with Kickstart and Pre-patched Kickstart Installs.

Chapter 28. Kickstart Installations

Unattended Installation of Red Hat Enterprise Linux 7 ...



Etc

FAIR USE NOTICE This site contains copyrighted material the use of which has not always been specifically authorized by the copyright owner. We are making such material available in our efforts to advance understanding of environmental, political, human rights, economic, democracy, scientific, and social justice issues, etc. We believe this constitutes a 'fair use' of any such copyrighted material as provided for in section 107 of the US Copyright Law. In accordance with Title 17 U.S.C. Section 107, the material on this site is distributed without profit exclusivly for research and educational purposes.   If you wish to use copyrighted material from this site for purposes of your own that go beyond 'fair use', you must obtain permission from the copyright owner. 

ABUSE: IPs or network segments from which we detect a stream of probes might be blocked for no less then 90 days. Multiple types of probes increase this period.  

Society

Groupthink : Two Party System as Polyarchy : Corruption of Regulators : Bureaucracies : Understanding Micromanagers and Control Freaks : Toxic Managers :   Harvard Mafia : Diplomatic Communication : Surviving a Bad Performance Review : Insufficient Retirement Funds as Immanent Problem of Neoliberal Regime : PseudoScience : Who Rules America : Neoliberalism  : The Iron Law of Oligarchy : Libertarian Philosophy

Quotes

War and Peace : Skeptical Finance : John Kenneth Galbraith :Talleyrand : Oscar Wilde : Otto Von Bismarck : Keynes : George Carlin : Skeptics : Propaganda  : SE quotes : Language Design and Programming Quotes : Random IT-related quotesSomerset Maugham : Marcus Aurelius : Kurt Vonnegut : Eric Hoffer : Winston Churchill : Napoleon Bonaparte : Ambrose BierceBernard Shaw : Mark Twain Quotes

Bulletin:

Vol 25, No.12 (December, 2013) Rational Fools vs. Efficient Crooks The efficient markets hypothesis : Political Skeptic Bulletin, 2013 : Unemployment Bulletin, 2010 :  Vol 23, No.10 (October, 2011) An observation about corporate security departments : Slightly Skeptical Euromaydan Chronicles, June 2014 : Greenspan legacy bulletin, 2008 : Vol 25, No.10 (October, 2013) Cryptolocker Trojan (Win32/Crilock.A) : Vol 25, No.08 (August, 2013) Cloud providers as intelligence collection hubs : Financial Humor Bulletin, 2010 : Inequality Bulletin, 2009 : Financial Humor Bulletin, 2008 : Copyleft Problems Bulletin, 2004 : Financial Humor Bulletin, 2011 : Energy Bulletin, 2010 : Malware Protection Bulletin, 2010 : Vol 26, No.1 (January, 2013) Object-Oriented Cult : Political Skeptic Bulletin, 2011 : Vol 23, No.11 (November, 2011) Softpanorama classification of sysadmin horror stories : Vol 25, No.05 (May, 2013) Corporate bullshit as a communication method  : Vol 25, No.06 (June, 2013) A Note on the Relationship of Brooks Law and Conway Law

History:

Fifty glorious years (1950-2000): the triumph of the US computer engineering : Donald Knuth : TAoCP and its Influence of Computer Science : Richard Stallman : Linus Torvalds  : Larry Wall  : John K. Ousterhout : CTSS : Multix OS Unix History : Unix shell history : VI editor : History of pipes concept : Solaris : MS DOSProgramming Languages History : PL/1 : Simula 67 : C : History of GCC developmentScripting Languages : Perl history   : OS History : Mail : DNS : SSH : CPU Instruction Sets : SPARC systems 1987-2006 : Norton Commander : Norton Utilities : Norton Ghost : Frontpage history : Malware Defense History : GNU Screen : OSS early history

Classic books:

The Peter Principle : Parkinson Law : 1984 : The Mythical Man-MonthHow to Solve It by George Polya : The Art of Computer Programming : The Elements of Programming Style : The Unix Hater’s Handbook : The Jargon file : The True Believer : Programming Pearls : The Good Soldier Svejk : The Power Elite

Most popular humor pages:

Manifest of the Softpanorama IT Slacker Society : Ten Commandments of the IT Slackers Society : Computer Humor Collection : BSD Logo Story : The Cuckoo's Egg : IT Slang : C++ Humor : ARE YOU A BBS ADDICT? : The Perl Purity Test : Object oriented programmers of all nations : Financial Humor : Financial Humor Bulletin, 2008 : Financial Humor Bulletin, 2010 : The Most Comprehensive Collection of Editor-related Humor : Programming Language Humor : Goldman Sachs related humor : Greenspan humor : C Humor : Scripting Humor : Real Programmers Humor : Web Humor : GPL-related Humor : OFM Humor : Politically Incorrect Humor : IDS Humor : "Linux Sucks" Humor : Russian Musical Humor : Best Russian Programmer Humor : Microsoft plans to buy Catholic Church : Richard Stallman Related Humor : Admin Humor : Perl-related Humor : Linus Torvalds Related humor : PseudoScience Related Humor : Networking Humor : Shell Humor : Financial Humor Bulletin, 2011 : Financial Humor Bulletin, 2012 : Financial Humor Bulletin, 2013 : Java Humor : Software Engineering Humor : Sun Solaris Related Humor : Education Humor : IBM Humor : Assembler-related Humor : VIM Humor : Computer Viruses Humor : Bright tomorrow is rescheduled to a day after tomorrow : Classic Computer Humor

The Last but not Least


Copyright © 1996-2016 by Dr. Nikolai Bezroukov. www.softpanorama.org was created as a service to the UN Sustainable Development Networking Programme (SDNP) in the author free time. This document is an industrial compilation designed and created exclusively for educational use and is distributed under the Softpanorama Content License.

The site uses AdSense so you need to be aware of Google privacy policy. You you do not want to be tracked by Google please disable Javascript for this site. This site is perfectly usable without Javascript.

Original materials copyright belong to respective owners. Quotes are made for educational purposes only in compliance with the fair use doctrine.

FAIR USE NOTICE This site contains copyrighted material the use of which has not always been specifically authorized by the copyright owner. We are making such material available to advance understanding of computer science, IT technology, economic, scientific, and social issues. We believe this constitutes a 'fair use' of any such copyrighted material as provided by section 107 of the US Copyright Law according to which such material can be distributed without profit exclusively for research and educational purposes.

This is a Spartan WHYFF (We Help You For Free) site written by people for whom English is not a native language. Grammar and spelling errors should be expected. The site contain some broken links as it develops like a living tree...

You can use PayPal to make a contribution, supporting development of this site and speed up access. In case softpanorama.org is down you can use the at softpanorama.info

Disclaimer:

The statements, views and opinions presented on this web page are those of the author (or referenced source) and are not endorsed by, nor do they necessarily reflect, the opinions of the author present and former employers, SDNP or any other organization the author may be associated with. We do not warrant the correctness of the information provided or its fitness for any purpose.

Last modified: August, 13, 2017