Archive for the ‘Linux Boot’ Category


Linux Install options in Fedora

June 23, 2006

A commonly asked question among new users and some experienced users is how do I do get this or that during the installation of Fedora Core Linux. Below is a list of command line options that can be used when you first boot from your Fedora distro media–taken from Anaconda-10.0:


Boot time command args:

expert          Turns on special features:
- allows partitioning of removable media
- prompts for driver disk

noshell         Do not put a shell on tty2 during install.

lowres          Force GUI installer to run at 640x480.

resolution=<mode> Run installer in mode specified, '1024x768' for example.

nousb           Do not load USB support (helps if install hangs
early sometimes).

nofb            Do not load the VGA16 framebuffer required for doing
text-mode installation in some languages

nofirewire      Do not load support for firewire devices

askmethod       Do not automatically use the CD-ROM as the install
source if we detect a Red Hat Linux CD in your CD-ROM drive.

nousbstorage    Do not load usbstorage module in loader.  May help with
device ordering on SCSI systems.

noparport       Do not attempt to load support for parallel ports

noprobe         Do not attempt to detect hw, prompts user instead.

nopcmcia        Ignore PCMCIA controller in system.

skipddc         Skips DDC probe of monitor, may help if its handing system.

graphical       Force graphical install. Required to have ftp/http use GUI.

text            Force text mode install.

vnc             Enable vnc-based installation. You will need to connect
to the machine using a vnc client application.

vncpassword=<password>  Enable a password for the vnc connection. This will
prevent someone from inadvertantly connecting to the
vnc-based installation.

Requires 'vnc' option to be specified as well.

vncconnect=<host>[:<port>]   Once installation is up and running, connect to
the vnc client named <host>, and optionally use port <port>.

Requires 'vnc' option to be specified as well.

updates         Prompt for floppy containing updates (bug fixes).

isa             Prompt user for ISA devices configuration.

dd              Use a driver disk.

driverdisk      Same as 'dd'.

mediacheck      Activates loader code to give user option of testing integrity
of install source (if an ISO-based method).

rescue          Run rescue environment.

nomount         Don't automatically mount any installed Linux partitions
in rescue mode.

nopass          Don't pass keyboard/mouse info to stage 2 installer, good for
testing keyboard and mouse config screens in stage2 installer
during network installs.

serial          Turns on serial console support.

ksdevice        Takes an argument like 'eth0', tells install what network
device to use for kickstart from network.

ks              Kickstart over NFS.

ks=cdrom:       Kickstart from CDROM

ks=nfs:<path>   Kickstart from NFS.

ks=<url>        Kickstart via HTTP.

ks=hd:<dev>     Kickstart via harddrive (dev = 'hda1', for example)

ks=file:<path>  Kickstart from a file (path = 'fd0/ks.cfg')

ks=ftp://<path> Kickstart from FTP.

ks=http://<path> Kickstart from HTTP.

kssendmac       Adds HTTP headers to ks=http:// request that can be helpful
for provisioning systems.  Includes MAC address of all nics in
a CGI environment variable of the form
all nics.

dhcpclass=<class> Sends a custom DHCP vendor class identifier. ISC's dhcpcd can
inspect this value using "option vendor-class-identifier".

upgradeany      Don't require an /etc/redhat-release that matches the
expected syntax to upgrade.

lang=<lang>     Language to use for the installation.  This should be a
language which is valid to be used with the 'lang' kickstart

keymap=<keymap> Keyboard layout to use.  Valid values are those which can be
used for the 'keyboard' kickstart command.

ip=<ip>         IP to use for a network installation, use 'dhcp' for DHCP.

netmask=<nm>    Netmask to use for a network installation.

gateway=<gw>    Gateway to use for a network installation.

dns=<dns>       Comma separated list of nameservers to use for a network

method=nfs:<path> Use <path> for an NFS installation.

method=http://<path> Use <path> for an HTTP installation

method=ftp://<path> Use <path> for an FTP installation

method=hd://<dev>/<path> Use <path> on <dev> for a hard drive installation

method=cdrom    Do a CDROM based installation.

vnc             Do graphical installation via VNC.  Instead of
starting a normal X server, vncserver will be started
and you can then connect remotely to do the

vncpassword=<password>  Set a password for the vnc session.

vncconnect=<host>[:<port>]   Once installation is up and running, connect to
the vnc client named <host>, and optionally, on port <port>.
Requires 'vnc' option to be specified as well.

Below is a list of undocumented commands that I found contained in the anaconda source:


debug           Start up pdb immediately
nofallback      If GUI fails exit
rootpath=       Where to install packages (default /mnt/sysimage)
pcic=           Specify pcmcia controller
overhead=       Override LVM overhead calculation
traceonly       Don't run, just list modules we use
kickstart=      Set serial install and kickstart file
kbdtype=        Set the type of keyboard
module=         Load additional kernel modules
class=          Choose install class to use
autostep        Make kickstart non-interactive
noselinux       Disable Security Enhanced Linux
selinux         Enable Security Enhanced Linux
cmdline         Use command line installer
headless        Automate install for machines with no display
xfs             Allows the creation of a xfs filesystem
reiserfs        Allows the creation of a reiserfs filesystem
jfs             Allows the creation of a jfs filesystem



create Logical Volume Manager (LVM) partitions using kickstart

June 3, 2006

How to create Logical Volume Manager (LVM) partitions using kickstart?


The following options are required under 'Disk Partition Information' section in ks.cfg file, for creating the Logical Volume Manager (LVM) partitions using kickstart.

#Disk partitioning information
part pv.<id> 
volgroup <name> <partition>
logvol <mountpoint> --vgname=<volume_group_name> --size=<size> --name=<name>

The options should be used in the sequence as they are mentioned. Physical Volume should be created first then Volume Group and then Logical Volume(s).

Two physical partitions should be created for Boot and Swap partitions and the rest of the space should be allocated using LVM.

Partition Size Name
/boot 150MB /boot
swap 1GB swap
/ 8GB lv_root
/var 4GB lv_var
/tmp 2GB lv_tmp
/spare remaining space lv_spare

The following entries are required in ks.cfg file, as per the above requirements:

#Disk partitioning information
part /boot --fstype ext3 --size=150
part swap --size=1024
part pv.01 --size=1 --grow
volgroup vg_root pv.01
logvol  /  --vgname=vg_root  --size=8192  --name=lv_root
logvol  /var  --vgname=vg_root  --size=4096  --name=lv_var
logvol  /tmp  --vgname=vg_root  --size=2048  --name=lv_tmp
logvol  /spare  --vgname=vg_root  --size=1  --grow  --name=lv_spare

Further Reading:

The information provided in this document is for your information only. The origin of this information may be internal or external to Red Hat. While Red Hat attempts to verify the validity of this information before it is posted, Red Hat makes no express or implied claims to its validity.

© 2003-2006 Red Hat, Inc. All rights reserved. This article is made available for copying and use under the Open Publication License, v1.0 which may be found at