Anaconda Boot Options

For more information on using Anaconda options, refer to "Appendix A. Boot Options" in the Fedora Installation Guide. For example, the version: http://docs.fedoraproject.org/en-US/Fedora//html/Installation_Guide/ch-Boot-x86.html#s2-x86-starting-bootopts


 * 
 * Do not automatically use the CD-ROM as the install source if we detect installation media in your CD-ROM drive.


 * 
 * Prompt for network configuration in the first stage of installation regardless of installation method.


 * 
 * Advance to the next screen automatically. This is mostly useful for debugging.


 * 
 * Do not automatically load module, even if the hardware exists on the system.


 * 
 * Force command line install mode. This mode simply prints out text and does not allow any interactivity.  All options must be specified either in a kickstart file or on the command line.


 * 
 * Use a driver disk.


 * 
 * See dd


 * 
 * Add a debug button to the UI that allows dropping into a python debugger.


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


 * 
 * Stop attempting to get a DHCP lease after seconds.


 * 
 * Sets the $DISPLAY environment variable.


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


 * 
 * Connect to the wireless network given by for a network installation. If used without  or , unencrypted connection is created.


 * 
 * Specify certain additional network device settings. Valid options are duplex={full,half} and speed={1000,100,10}.  Multiple options may be given as a string separated by spaces and surrounded by double quotes.


 * 
 * Gateway to use for a network installation.


 * 
 * Run gdbserver in loader, attached to IP:PORT (eg. gdb=0.0.0.0:2345)
 * On the host you need the anaconda-debuginfo package's contents to properly debug the binary. Run  and then specify the loader source directory with the   command. Connect to the remote target with.


 * 
 * 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).


 * 
 * Specify that the machine being installed onto does not have any display hardware, and that anaconda should not probe for it.


 * 
 * IP to use for a network installation, use 'dhcp' for DHCP.


 * 
 * IPv6 address to use for a network installation. This can be the static address in form, 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.


 * 
 * Keyboard layout to use. Valid values are those which can be used for the   kickstart command.


 * 
 * Gives the location of the kickstart file to be used for installation. If only   is given, the file is assumed to be on NFS.  The ks parameter may take these other forms:
 * If no path is given,  is used by default.
 * (path = 'fd0/ks.cfg', for example)
 * (dev = 'hda1', for example)
 * (biosdev = '80p1', for example, note this does not work for BIOS RAID sets)
 * (biosdev = '80p1', for example, note this does not work for BIOS RAID sets)
 * (biosdev = '80p1', for example, note this does not work for BIOS RAID sets)
 * (biosdev = '80p1', for example, note this does not work for BIOS RAID sets)


 * 
 * 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


 * 
 * 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".


 * 
 * 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".


 * 
 * Language to use for the installation. This should be a language which is valid to be used with the   kickstart command.


 * 
 * Check the network device for a link every second for seconds.


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


 * 
 * In Fedora 10 and earlier, force GUI installer to run at 640x480. This will not resize the interface, so some UI elements will likely be offscreen (although still active through keyboard navigation).


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


 * 
 * This option is deprecated in favor of repo=. For now, it does the same thing as repo= but will be removed at a later date.


 * 
 * 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.


 * 
 * Netmask to use for a network installation.


 * 
 * Sleep for seconds before trying again to bring up the network.


 * 
 * Disable support for dmraid.


 * 
 * Do not load support for firewire devices.


 * 
 * Do not create GPT disklabels.


 * 
 * Disable IPv4 networking during installation.


 * 
 * Disable IPv6 networking during installation.


 * 
 * A debugging option that prevents anaconda from terminating all running programs when a fatal error occurs.


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


 * 
 * Disable support for multipath devices.


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


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


 * 
 * Disable SELinux on the installed system.


 * 
 * Do not put a shell on tty2 during install.


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


 * 
 * Prevents Anaconda from verifying the ssl certificate for all https connections with an exception of the additional kickstart repos (where --noverifyssl can be set per repo).


 * 
 * Use the given proxy settings when performing an HTTP/HTTPS/FTP installation.


 * 
 * This option tells anaconda where to find the packages for installation. This option must point to a valid yum repository.  It is analagous 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   (whereas kickstart command   is used for additional repositories).  As of Anaconda 16.12 you can (optionally) add a specific .iso file to the path.


 * The following forms are accepted for repo=:
 * 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=.
 * Look for ISO images on the NFS volume with the given server and path. These should be ISO images, not loopback mounted.
 * 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=.
 * Look for ISO images on the NFS volume with the given server and path. These should be ISO images, not loopback mounted.
 * 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=.
 * Look for ISO images on the NFS volume with the given server and path. These should be ISO images, not loopback mounted.
 * Look for ISO images on the NFS volume with the given server and path. These should be ISO images, not loopback mounted.
 * Look for ISO images on the NFS volume with the given server and path. These should be ISO images, not loopback mounted.


 * 
 * Run rescue environment.


 * 
 * Run installer in mode specified, '1024x768' for example.


 * 
 * Disables selinux entirely. Defaults to on.


 * 
 * Turns on serial console support.


 * 
 * 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.


 * 
 * Once installation is up and running, send log messages to the syslog process on, and optionally, on TCP port . Requires the remote syslog process to accept incoming connections.


 * 
 * Force text mode install. This will install only base packages for a minimal system and implies that the installed system will boot up in runlevel 3 instead of to the graphical login screen.


 * 
 * Since Fedora 17. Raise exception in the GUI (for testing purposes). DO NOT USE THIS IF YOU WANT TO INSTALL THE SYSTEM.


 * 
 * Prompt for removable media containing updates (bug fixes).


 * 
 * Image containing updates over FTP or HTTP.


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


 * 
 * Use the framebuffer X driver instead of attempting to use a hardware-specific one.


 * 
 * Set the TERM variable to vt100.


 * 
 * Forward logs through the character device at /dev/virtio-ports/. See also Anaconda/Logging.


 * 
 * 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.


 * 
 * Once installation is up and running, connect to the vnc client named, and optionally use port.


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


 * 
 * Use as the wireless key when doing a network installation via a wireless network. Requires use of.


 * 
 * Use as the X driver to use during installation as well as on the installed system.