: Image containing updates over FTP or HTTP. See [[Anaconda/Updates]] for more details.

: Image containing updates over FTP or HTTP. See [[Anaconda/Updates]] for more details.

+

: Accepts either <code>updates=<url></code> or <code>updates=<disk>:<path></code> where <code><disk></code> can be one of <code>sdX, /dev/sdX, LABEL=xxx, UUID=xxx</code> and <code><path></code> defaults to <code>/updates.img</code> if missing.

{{anchor|usefbx}}

{{anchor|usefbx}}

Revision as of 11:10, 29 June 2013

Out-of-dateThe information on this page is out-of-date and some parts may be inaccurate for Fedora 17 and later. There is a draft of updated documentation available here.

Do not automatically use the CD-ROM as the install source if we detect installation media in your CD-ROM drive: instead prompt for a source during the first stage of installation.

Fedora 17 and 18

Has no effect.

Fedora 19 and later

Do not automatically configure the Installation Source spoke, but require the user to enter it and choose an option. If you don't want to wait for the default configuration to be processed before you can enter the spoke and change it, you can pass this option. See Bug #889887.

Comma separated list of nameservers to use for a network installation.

Dracut syntax required in Fedora 17 and laterThe syntax for specifying network configuration which uses the dns, gateway, ip, ipv6, netmask and mtu parameters as described here does not work in Fedora 17. Instead, please use the Dracut ip= syntax.

Dracut syntax required in Fedora 17 and laterThe syntax for specifying network configuration which uses the dns, gateway, ip, ipv6, netmask and mtu parameters as described here does not work in Fedora 17. Instead, please use the Dracut ip= syntax.

Force graphical install. Required to have ftp/http use GUI. A graphical install implies that the installed system will boot up into runlevel 5, using whichever display manager is in use by the default desktop (gdm for GNOME, kdm for KDE).

Dracut syntax required in Fedora 17 and laterThe syntax for specifying network configuration which uses the dns, gateway, ip, ipv6, netmask and mtu parameters as described here does not work in Fedora 17. Instead, please use the Dracut ip= syntax.

IPv6 address to use for a network installation. This can be the static address in form <IPv6 address>[/<prefix length>], e.g. 3ffe:ffff:0:1::1/128 (if prefix is omitted 64 is assumed), "auto" for address assignment based on automatic neighbor discovery, or "dhcp" to use the DHCPv6 protocol.

Dracut syntax required in Fedora 17 and laterThe syntax for specifying network configuration which uses the dns, gateway, ip, ipv6, netmask and mtu parameters as described here does not work in Fedora 17. Instead, please use the Dracut ip= syntax.

Takes one of 4 types of argument which tells install what network device to use for kickstart from network:

An argument like 'eth0' naming a specific interface

An argument like 00:12:34:56:78:9a indicating the MAC address of a specific interface

The keyword 'link' indicating that the first interface with link up

The keyword 'bootif' indicating that the MAC address indicated by the BOOTIF command line option will be used to locate the boot interface. BOOTIF is automagically supplied by pxelinux when you include the option 'IPAPPEND 2' in your pxelinux.cfg file

The keyword 'ibft' - use device configured with MAC address in iBFT

Renamed in Fedora 17This parameter used to be 'ksdevice'. It was renamed in Fedora 17.

Adds HTTP headers to ks=http:// requests that can be helpful for provisioning systems. Includes MAC address of all network interfaces in HTTP headers of the form "X-RHN-Provisioning-MAC-0: eth0 01:23:45:67:89:ab".

Renamed in Fedora 17This parameter used to be 'kssendmac'. It was renamed in Fedora 17.

Adds an HTTP header to ks=http:// requests that can be helpful for provisioning systems. Includes the system's serial number (according to dmidecode) in an HTTP header of the form "X-System-Serial-Number: 1234567890".

Renamed in Fedora 17This parameter used to be 'kssendsn'. It was renamed in Fedora 17.

Boot the drives in their existing order, to override the default of booting into the newly installed drive on Power Systems servers and EFI systems. This is useful for systems that, for example, should network boot first before falling back to a local boot.

Available in Fedora 18 and laterThe leavebootorder option was introduced in Fedora 18.

Set the minimum level required for messages to be logged on a terminal (log files always contain messages of all levels). Values for <level> are debug, info, warning, error, and critical. The default value is info.

Set the MTU (maximum transmission unit) used during network installs to the given number. Uses the network stack default if this option is not specified.

Dracut syntax required in Fedora 17 and laterThe syntax for specifying network configuration which uses the dns, gateway, ip, ipv6, netmask and mtu parameters as described here does not work in Fedora 17. Instead, please use the Dracut ip= syntax.

Dracut syntax required in Fedora 17 and laterThe syntax for specifying network configuration which uses the dns, gateway, ip, ipv6, netmask and mtu parameters as described here does not work in Fedora 17. Instead, please use the Dracut ip= syntax.

Since Fedora 17: Disable the check which usually causes anaconda to abort if a safe minimum amount of memory is not found. Of course, any attempt to install with less than the safe minimum amount of memory may fail and is unsupported.

This option tells anaconda where to find the packages for installation. This option must point to a valid yum repository (or, for some protocols, a Fedora DVD ISO image). It is analogous to the older method= option, but repo= makes it more clear exactly what is meant. This option may appear only once on the command line. It corresponds to the kickstart command install (whereas kickstart command repo is used for additional repositories). As of Fedora 16, you can (optionally) add a specific .iso file to the path. If no inst.root= or inst.stage2= parameter is passed, this location will also be used as the source for the installer runtime image.

The following forms are accepted for repo=:

repo=cdrom:<device>

repo=ftp://[user:password@]<host>/<path>

repo=http://<host>/<path>

repo=hd:<device>:/<path>

Look for ISO images on the hard drive partition given by device (/dev/sda1, for instance). This may not be a partition that will be formatted during installation later. These should be ISO images, not an exploded tree on the hard drive. device can be a device name, LABEL=, or UUID=.

repo=hd:LABEL=<label>:/<path>

repo=hd:UUID=<uuid>:/<path>

As repo=hd:<device>, but you can specify a partition by label or UUID.

repo=nfs[:options]:<server>:/<path>

repo=nfsiso[:options]:<server>:/<path>

Will use either an ISO image or a Fedora tree on the NFS volume with the given server and path as an install repository (in all current supported releases, 'nfs' and 'nfsiso' are synonyms; anaconda will check for either an ISO image or an install tree in the specified location whichever of the two you pass). If an 'inst.root' or 'inst.stage2' parameter is passed - as is the case by default when the installer is booted from the DVD or network install images - the mount will first be tried using the NFSv4 protocol, and if this fails, it will be tried using the NFSv3 protocol. There is a known bug in Fedora 19 Beta which prevents NFSv3 mount attempts from succeeding unless the 'nolock' option is specified. If no 'inst.root' or 'inst.stage2' parameter is passed, and so the NFS repository is being used as the installer runtime image source as well as a package source (which will be the case when booting directly from a kernel pair, for e.g., in a PXE installation, or using virt-install), the NFSv3 protocol only will be used, due to a known bug which affects trying to mount the installation root via the NFSv4 protocol.

Starts up sshd during system installation. You can then ssh in while the installation progresses to debug or monitor. Passwords are controlled via the kickstart sshpw command. By default, the root account has a blank password, so if the sshd option is specified, anyone can login as root and have full access to the machine during installation.

Specifies a path to a repository containing a stage2 (squashfs.img) file instead of to an installation source. Follows the same syntax as repo=. If this parameter is provided, it takes precedence over all other methods of finding the install.img. Otherwise, anaconda will attempt to find the install.img first on any existing CD, and then from the location given by repo=.

If only stage2= is given without repo=, anaconda will use whatever repos the installed system would have enabled by default for installation. For instance, an install of a Fedora release will attempt to use the Fedora mirrorlist given by /etc/yum.repos.d/fedora.repo from that release.

Enable vnc-based installation. You will need to connect to the machine using a vnc client application. A vnc install implies that the installed system will boot up in runlevel 3 instead of to the graphical login screen. The vnc session will be shared. Consider setting a vnc password.

Enable a password for the vnc connection. This will prevent someone from inadvertently connecting to the vnc-based installation. Requires vnc option to be specified as well. If you have specified vncconnect the <password> will not be used unless connection to host is not possible.