Product SiteDocumentation Site

8.3. Deprecated Boot Options

Options in this list are deprecated. They will still work, but there are other options which offer the same functionality and should be preferred. Using deprecated options is not recommended and they are expected to be removed in future releases.


Note that as described in the introduction to this chapter, options specific to the installation program now use the inst. prefix. For example, the vnc= option is considered deprecated and replaced by the inst.vnc= option. However, these changes are not listed here.
Used to specify that the machine being installed onto does not have any display hardware, and to prevent the installer from trying to detect a display.
Configured the installation method. Use the inst.repo= option instead.
In NFS installations, specified that the target is an ISO image located on an NFS server instead of an installable tree. The difference is now detected automatically, which means this option is the same as inst.repo=nfs:server:/path.
Configured the Domain Name Server (DNS). Use the nameserver= option instead.
netmask=, gateway=, hostname=, ip=, ipv6=
These options have been consolidated under the ip= option.
Select network device to be used at early stage of installation. Different values have been replaced with different options; see the table below.
Table 8.7. Automatic Interface Configuration Methods
Value Current behavior
Not present All devices are attempted to be activated using dhcp, unless desired device and configuration is specified by ip= option and/or the BOOTIF 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 rd.neednet option (provided by dracut) should be used instead.
ksdevice=bootif Ignored (the BOOTID= option is used by default when specified)
ksdevice=ibft Replaced with the ip=ibft option
ksdevice=MAC Replaced with BOOTIF=MAC
ksdevice=device Replaced by specifying the device name using the ip= option.


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#1085310 for details.
To work around this issue, either use the ksdevice=link boot option, or add the --device=link option to the network command in your Kickstart file.
Used to disable specified drivers. This is now handled by the modprobe.blacklist= option.
Disabled support for the FireWire interface. You can disable the FireWire driver (firewire_ohci) by using the modprobe.blacklist= option instead: