The translation is temporarily closed for contributions due to maintenance, please come back later.
English
You should never attempt to perform a driver update during the installation unless a missing our faulty driver is preventing you from completing the installation. Updating drivers which are not essential during the installation should always be performed after the system is installed.
You may boot a command-line Linux system from an installation disc without actually installing {PRODUCT} on the computer. This enables you to use the utilities and functions of a running Linux system to modify or repair already installed operating systems.
You can use this option multiple times. In that case, the boot message will be displayed on all specified consoles, but only the last one will be used by the installation program afterwards. For example, if you specify [option]#console=ttyS0 console=ttyS1#, the installation program will only use `ttyS1`.
You can use multiple options at the same time; in that case, separate them by a single space.
You can test the integrity of an ISO-based installation source before using it to install {PRODUCT}. These sources include DVDs and ISO images stored on a local hard drive or NFS server. Verifying that the ISO images are intact before you attempt an installation helps to avoid problems that are often encountered during installation.
`X-System-Serial-Number: _R8VA23D_pass:attributes[{blank}]`
`X-RHN-Provisioning-MAC-0: eth0 01:23:45:67:89:ab`
With this boot option, the stage 2 image will be fetched from HTTP, HTTPS and FTP locations which are specified using the [option]#inst.stage2=# option sequentially in the order they are specified, until the image is successfully fetched. All other locations will be ignored.
With this boot option, the Kickstart file will be fetched from HTTP, HTTPS and FTP locations which are specified using the [option]#inst.ks=# option sequentially in the order they are specified, until the file is successfully fetched. All other locations will be ignored.
When performing a Kickstart installation, booting from local media and having the Kickstart file on local media as well, the network will not be initialized. This means that any other Kickstart options requiring network access, such as pre-installation or post-installation scripts accessing a network location, will cause the installation to fail. This is a known issue; see BZ#link:++https://bugzilla.redhat.com/show_bug.cgi?id=1085310++[1085310] for details.
`VNC` server used by the installation program. Any `VNC` client attempting to connect to the system will have to provide the correct password to gain access. For example, [option]#inst.vncpassword=pass:attributes[{blank}]_testpwd_pass:attributes[{blank}]# will set the password to `testpwd`. The password must be between 6 and 8 characters long.
VNC password must be six to eight characters long.
Please enter a new one, or leave blank for no password.
VLAN Device Naming Conventions
Verifying Boot Media
Verified the installation media before starting the installation. Replaced with the [option]#rd.live.check# option.
|Value|Current behavior
|Not present|All devices are attempted to be activated using `dhcp`, unless desired device and configuration is specified by [option]#ip=# option and/or the [option]#BOOTIF# option.
|[option]#ksdevice=link#|Similar to the above, with the difference that network will always be activated in the initramfs, whether it is needed or not. The supported [option]#rd.neednet# option (provided by [application]*dracut*) should be used instead.
|[option]#ksdevice=bootif#|Ignored (the BOOTID= option is used by default when specified)
|[option]#ksdevice=ibft#|Replaced with the [option]#ip=ibft# option
|[option]#ksdevice=pass:attributes[{blank}]_MAC_pass:attributes[{blank}]#|Replaced with [option]#BOOTIF=pass:attributes[{blank}]_MAC_pass:attributes[{blank}]#
|[option]#ksdevice=pass:attributes[{blank}]_device_pass:attributes[{blank}]#|Replaced by specifying the device name using the [option]#ip=# option.
Valid Values for the inst.geoloc Option
Using this option without any parameters will assume [option]#bond=bond0:eth0,eth1:mode=balance-rr#.
Using this option without any parameters (only as [option]#inst.dd#) will prompt the installation program to ask you for a driver update disk with an interactive menu.
Using this option will leave the installation source configuration in an error state - you must manually specify a source in the `Installation Source` screen to proceed with the installation. Alternatively, you can use the [option]#inst.repo=# option described above to configure a specific source directly in the boot menu.