From c9d7e9c26dda3238f6293b1a21c06fbde9e76b5e Mon Sep 17 00:00:00 2001 From: Matthew Miller Date: Oct 10 2021 22:17:52 +0000 Subject: I have a LibreOffice document with changes from Leslie S Satenstein. This commit converts the areas he has worked on or has comments on to use SemBr, so that those changes are easier to compare and comment on in subsequent commits. I have confirmed that these changes do not produce any text or visual changes in the rendered output. --- diff --git a/modules/install-guide/pages/advanced/Boot_Options.adoc b/modules/install-guide/pages/advanced/Boot_Options.adoc index fa513f4..5ff78b1 100644 --- a/modules/install-guide/pages/advanced/Boot_Options.adoc +++ b/modules/install-guide/pages/advanced/Boot_Options.adoc @@ -4,15 +4,47 @@ include::{partialsdir}/entities.adoc[] [[chap-anaconda-boot-options]] = Boot Options -The [application]*Anaconda* installer includes a range of boot options for administrators, which modify the default behavior of the installation program by enabling or disabling certain functions. To use one or more boot options, you either have to boot from installation media and append these options at the boot menu (see xref:install/Booting_the_Installation.adoc#sect-boot-menu[The Boot Menu]), or you must add them into your PXE server configuration file if you are booting from a network (see xref:advanced/Network_based_Installations.adoc#chap-pxe-server-setup[Setting Up an Installation Server]). - -You can use multiple options at the same time; in that case, separate them by a single space. +The [application]*Anaconda* installer includes a range of boot options +for administrators, +which modify the default behavior of the installation program +by enabling or disabling certain functions. +To use one or more boot options, +you either have to boot from installation media +and append these options at the boot menu +(see +xref:install/Booting_the_Installation.adoc#sect-boot-menu[The Boot Menu]), +or you must add them into your PXE server configuration file +if you are booting from a network +(see +xref:advanced/Network_based_Installations.adoc#chap-pxe-server-setup[Setting Up an Installation Server]). + +You can use multiple options at the same time; +in that case, +separate them by a single space. There are two basic types of options described in this chapter: -* Options presented as ending with an "`equals`" sign (`=`) require a value to be specified - they cannot be used on their own. For example, the [option]#inst.vncpassword=# option must also contain a value (in this case, a password). The correct form is therefore [option]#inst.vncpassword=pass:attributes[{blank}]_password_pass:attributes[{blank}]#. On its own, without a password specified, the option is invalid. - -* Options presented without the "`pass:attributes[{blank}]`=`pass:attributes[{blank}]`" sign do not accept any values or parameters. For example, the [option]#rd.live.check# option forces [application]*Anaconda* to verify the installation media before starting the installation; if this option is present, the check will be performed, and if it is not present, the check will be skipped. +* Options presented as ending with an "`equals`" sign (`=`) +require a value to be specified - +they cannot be used on their own. +For example, +the [option]#inst.vncpassword=# option +must also contain a value +(in this case, a password). +The correct form is therefore [option]#inst.vncpassword=pass:attributes[{blank}]_password_pass:attributes[{blank}]#. +On its own, +without a password specified, +the option is invalid. + +* Options presented without the "`pass:attributes[{blank}]`=`pass:attributes[{blank}]`" sign +do not accept any values or parameters. +For example, +the [option]#rd.live.check# option forces [application]*Anaconda* to +verify the installation media before starting the installation; +if this option is present, +the check will be performed, +and if it is not present, +the check will be skipped. In addition to the options described in this chapter, the boot prompt also accepts [application]*dracut* kernel options. A list of these options is available as the `dracut.cmdline(7)` man page. @@ -26,7 +58,23 @@ Boot options specific to the installation program always start with `inst.` in t [[sect-boot-options-installer]] == Configuring the Installation System at the Boot Menu -The exact way to specify custom boot options is differs based on your system's architecture, firmware and the method you use to boot the installation. If you are booting from local media, you can specify options in the boot menu, before you begin the installation; if you are booting from a network using a PXE server, you must add boot options into the boot loader configuration file before you boot the installation system. For specific instructions, see xref:install/Booting_the_Installation.adoc#sect-boot-menu[The Boot Menu] if you are booting from local media, and xref:advanced/Network_based_Installations.adoc#chap-pxe-server-setup[Setting Up an Installation Server] if you are booting from a server. +The exact way to specify custom boot options is differs +based on your system's architecture, +firmware +and the method you use to boot the installation. +If you are booting from local media, +you can specify options in the boot menu, +before you begin the installation; +if you are booting from a network using a PXE server, +you must add boot options into the boot loader configuration file +before you boot the installation system. +For specific instructions, +see +xref:install/Booting_the_Installation.adoc#sect-boot-menu[The Boot Menu] +if you are booting from local media, +and +xref:advanced/Network_based_Installations.adoc#chap-pxe-server-setup[Setting Up an Installation Server] +if you are booting from a server. [[sect-boot-options-available]] == Available Boot Options @@ -49,9 +97,12 @@ The source must be either: + ** a DVD (a physical disk present in the system's DVD drive) + -** an ISO image of the full {PRODUCT} installation DVD, placed on a hard drive or a network location accessible from the installation system +** an ISO image of the full {PRODUCT} installation DVD, +placed on a hard drive or a network location +accessible from the installation system + -This option allows for the configuration of different installation methods using different formats. The syntax is described in the table below. +This option allows for the configuration of different installation methods using different formats. +The syntax is described in the table below. + [[tabl-boot-options-sources]] .Installation Sources @@ -103,22 +154,47 @@ Using this option without any parameters (only as [option]#inst.dd#) will prompt [IMPORTANT] ==== -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 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. ==== [option]#inst.askmethod#:: Prevents the installer from trying to automatically configure an installation source. + -Normally, when you first enter the `Installation Summary` screen, the installer will attempt to configure an installation source based on the type of media you used to boot. The full {PRODUCT} Server DVD will configure the source as local media, the netinst ISO image will configure the closest network mirror, etc. This process takes time; therefore, if you plan to use a different source than the default, this option will allow you to enter the `Installation Source` screen immediately without having to wait for the initial configuration to finish. +Normally, when you first enter the `Installation Summary` screen, +the installer will attempt to configure an installation source +based on the type of media you used to boot. +The full {PRODUCT} Server DVD will configure the source as local media, +the netinst ISO image will configure the closest network mirror, +etc. +This process takes time; +therefore, +if you plan to use a different source than the default, +this option will allow you to enter the `Installation Source` screen immediately +without having to wait for the initial configuration to finish. + 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. [[sect-boot-options-kickstart]] === Kickstart Boot Options -[option]#inst.ks=#:: Gives the location of a Kickstart file to be used to automate the installation. Locations can be specified using any of the formats valid for [option]#inst.repo=#. See xref:tabl-boot-options-sources[Installation Sources] for valid formats. +[option]#inst.ks=#:: Gives the location of a Kickstart file to be used to automate the installation. +Locations can be specified using any of the formats valid for +[option]#inst.repo=#. +See +xref:tabl-boot-options-sources[Installation Sources] +for valid formats. + -If you only specify a device and not a path, the installation program will look for the Kickstart file in `/ks.cfg` on the specified device. If you use this option without specifying a device, the installation program will use the following: +If you only specify a device and not a path, +the installation program will look for the Kickstart file +in `/ks.cfg` on the specified device. +If you use this option without specifying a device, +the installation program will use the following: + [subs="quotes, macros"] ---- @@ -145,7 +221,9 @@ In the above example, _next-server_ is the DHCP `next-server` option or the IP a `X-RHN-Provisioning-MAC-0: eth0 01:23:45:67:89:ab` ---- + -This can be useful when using [option]#inst.ks=http# to provision systems. +This can be useful when using +[option]#inst.ks=http# +to provision systems. [option]#inst.ks.sendsn#:: Adds a header to outgoing `HTTP` requests. This header will contain the system's serial number, read from `/sys/class/dmi/id/product_serial`. The header has the following syntax: + @@ -165,7 +243,10 @@ You can use this option multiple times. In that case, the boot message will be d [option]#inst.lang=#:: Sets the language to be used during the installation. Language codes are the same as the ones used in the [command]#lang# Kickstart command as described in xref:appendixes/Kickstart_Syntax_Reference.adoc#sect-kickstart-commands-lang[lang (optional) - Configure Language During Installation]. On systems where the [package]*system-config-language* package is installed, a list of valid values can also be find in `/usr/share/system-config-language/locale-list`. + -If you perform the installation interactively, the language you specified using this option will be selected by default, but you will still be able to change it at the beginning of the graphical installation. +If you perform the installation interactively, +the language you specified using this option will be selected by default, +but you will still be able to change it at the beginning of +the graphical installation. [option]#inst.singlelang#:: Allows you to run the installation in single language mode - in other words, this option disables language selection for the installer and the installed system. If you also use the [option]#inst.lang=# option at the same time, the language you specify will be used. If you do not set the language, [application]*Anaconda* and the installed system will default to `en-US.UTF-8`. @@ -186,14 +267,25 @@ If this option is not specified, [application]*Anaconda* will use `provider_fedo [option]#inst.keymap=#:: Specifies the keyboard layout to be used by the installation program. Layout codes are the same as the ones used in the [command]#keyboard# Kickstart command as described in xref:appendixes/Kickstart_Syntax_Reference.adoc#sect-kickstart-commands-keyboard[keyboard (optional) - Configure Keyboard Layouts]. -[option]#inst.text#:: Forces the installation program to run in text mode instead of graphical mode. The text user interface is limited, for example, it does not allow you to modify the partition layout or set up LVM. When installing a system on a machine with a limited graphical capabilities, it is recommended to use VNC as described in xref:sect-boot-options-vnc[Enabling Remote Access Using VNC]. +[option]#inst.text#:: Forces the installation program to run in text mode instead of graphical mode. +The text user interface is limited, for example, +it does not allow you to modify the partition layout or set up LVM. +When installing a system on a machine with a limited graphical capabilities, + it is recommended to use VNC as described in +xref:sect-boot-options-vnc[Enabling Remote Access Using VNC]. -[option]#inst.cmdline#:: Forces the installation program to run in command line mode. This mode does not allow any interaction, all options must be specified in a Kickstart file or on the command line. +[option]#inst.cmdline#:: Forces the installation program to run in command line mode. +This mode does not allow any interaction, +all options must be specified in a Kickstart file +or on the command line. [option]#inst.graphical#:: Forces the installation program to run in graphical mode. This mode is the default. -[option]#inst.resolution=#:: Specifies the screen resolution in graphical mode. The format is _N_pass:attributes[{blank}]xpass:attributes[{blank}]_M_, where _N_ is the screen width and _M_ is the screen height (in pixels). The lowest supported resolution is `800x600`. - +[option]#inst.resolution=#:: Specifies the screen resolution in graphical mode. +The format is +_N_pass:attributes[{blank}]xpass:attributes[{blank}]_M_, +where _N_ is the screen width and _M_ is the screen height (in pixels). +The lowest supported resolution is `800x600`. [option]#inst.xdriver=#:: Specifies the name of the `X` driver to be used both during the installation and on the installed system. [option]#inst.usefbx#:: Tells the installation program to use the frame buffer `X` driver instead of a hardware-specific driver. This option is equivalent to [option]#inst.xdriver=fbdev#. @@ -208,12 +300,25 @@ Use a comma-separated list to disable multiple drivers. For example: modprobe.blacklist=ahci,firewire_ohci ---- -[option]#inst.sshd#:: Starts the `sshd` service during the installation, which allows you to connect to the system during the installation using `SSH` and monitor its progress. For more information on `SSH`, see the `ssh(1)` man page and the corresponding chapter in the [citetitle]_xref:fedora:system-administrators-guide:index.adoc[{PRODUCT} System Administrator's Guide]_. +[option]#inst.sshd#:: Starts the `sshd` service during the installation, +which allows you to connect to the system during the installation +using `SSH` +and monitor its progress. +For more information on `SSH`, +see the `ssh(1)` man page and the corresponding chapter in the +[citetitle]_xref:fedora:system-administrators-guide:index.adoc[{PRODUCT} System Administrator's Guide]_. + [NOTE] ==== -During the installation, the `root` account has no password by default. You can set a root password to be used during the installation with the [command]#sshpw# Kickstart command as described in xref:appendixes/Kickstart_Syntax_Reference.adoc#sect-kickstart-commands-sshpw[sshpw (optional) - Restrict ssh Access During Installation]. +During the installation, +the `root` account +has no password by default. +You can set a root password to be used during the installation +with the +[command]#sshpw# Kickstart command +as described in +xref:appendixes/Kickstart_Syntax_Reference.adoc#sect-kickstart-commands-sshpw[sshpw (optional) - Restrict ssh Access During Installation]. ==== @@ -222,7 +327,17 @@ During the installation, the `root` account has no password by default. You can [[sect-boot-options-network]] === Network Boot Options -Initial network initialization is handled by [application]*dracut*. This section only lists some of the more commonly used options; for a complete list, see the `dracut.cmdline(7)` man page. Additional information on networking is also available in the [citetitle]_{PRODUCT} Networking Guide_, available at link:++https://docs.fedoraproject.org/++[]. +Initial network initialization is handled by [application]*dracut*. +This section only lists some of the more commonly used options; +for a complete list, +see the +`dracut.cmdline(7)` +man page. +Additional information on networking is also available +in the +[citetitle]_{PRODUCT} Networking Guide_, +available at +link:++https://docs.fedoraproject.org/++[]. [option]#ip=#:: Configures one or more network interfaces. To configure multiple interfaces, use the `ip` option multiple times - once for each interface. If multiple interfaces are configured, you must specify a primary boot interface using the [option]#bootdev# option described below. + @@ -262,7 +377,11 @@ If you use a boot option which requires network access, such as [option]#inst.ks ==== + -In the above tables, the _ip_ parameter specifies the client's IP address. `IPv6` addresses can be specified by putting them in square brackets, for example, `[2001:DB8::1]`. +In the above tables, +the _ip_ parameter specifies the client's IP address. +`IPv6` addresses can be specified by putting them in square brackets, +for example, +`[2001:DB8::1]`. + The _gateway_ parameter is the default gateway. IPv6 addresses are accepted here as well. + @@ -290,7 +409,8 @@ The _hostname_ parameter is the host name of the client system. This parameter i [option]#vlan=vlan5:em1# ---- + -The above will set up a VLAN device named `vlan5` on the `em1` interface. The _name_ can take the following forms: +The above will set up a VLAN device named `vlan5` on the `em1` interface. +The _name_ can take the following forms: + [[tabl-boot-options-network-vlan-names]] .VLAN Device Naming Conventions @@ -328,14 +448,35 @@ Using this option without any parameters will assume [option]#bond=bond0:eth0,et + Normally, on an AMD64 or Intel{nbsp}64 system, only packages for this architecture (marked as `x86_64`) and packages for all architectures (marked as `noarch`) would be installed. When you use this option, packages for 32-bit AMD or Intel systems (marked as `i686`) will be automatically installed as well if available. + -This only applies to packages directly specified in the `%packages` section. If a package is only installed as a dependency, only the exact specified dependency will be installed. For example, if you are installing package [package]*foo* which depends on package [package]*bar*, the former will be installed in multiple variants, while the latter will only be installed in variants specifically required. - -[option]#inst.gpt#:: Force the installation program to install partition information into a GUID Partition Table (GPT) instead of a Master Boot Record (MBR). This option is meaningless on UEFI-based systems, unless they are in BIOS compatibility mode. -+ -Normally, BIOS-based systems and UEFI-based systems in BIOS compatibility mode will attempt to use the MBR schema for storing partitioning information, unless the disk is larger than 2 TB. Using this option will change this behavior, allowing a GPT to be written even to disks smaller than 2 TB. +This only applies to packages directly specified in the +`%packages` +section. +If a package is only installed as a dependency, +only the exact specified dependency will be installed. +For example, +if you are installing package +[package]*foo* +which depends on package +[package]*bar*, +the former will be installed in multiple variants, +while the latter will only be installed in variants specifically required. + +[option]#inst.gpt#:: Force the installation program to install partition information +into a GUID Partition Table (GPT) +instead of a Master Boot Record (MBR). +This option is meaningless on UEFI-based systems, +unless they are in BIOS compatibility mode. ++ +Normally, +BIOS-based systems +and UEFI-based systems in BIOS compatibility mode +will attempt to use the MBR schema for storing partitioning information, +unless the disk is larger than 2 TB. +Using this option will change this behavior, +allowing a GPT to be written +even to disks smaller than 2 TB. + See xref:install/Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-recommended[Recommended Partitioning Scheme] for more information about GPT and MBR, and xref:appendixes/Disk_Partitions.adoc#sect-disk-partitioning-guid-partition-table[GUID Partition Table (GPT)] for more general information about GPT, MBR and disk partitioning in general. - [option]#inst.nosave=#:: This option controls which Kickstart files and installation logs are saved to the installed system. It can be especially useful to disable saving such data when performing OEM operating system installations, or when generating images using sensitive resources (such as internal repository URLs), as these resources might otherwise be mentioned in kickstart files and/or logs on the image. Possible values for this option are: + `input_ks` - disables saving of the input Kickstart file (if any). @@ -354,14 +495,31 @@ Multiple values can be combined as a comma separated list, for example: `input_k [option]#inst.nodnf#:: Use the older [application]*Yum* backend for package installation and dependency resolution instead of [application]*DNF*. See the [citetitle]_xref:fedora:system-administrators-guide:index.adoc[{PRODUCT} System Administrator's Guide]_ for details about [application]*DNF*. -[option]#inst.kdump_addon=#:: Turns the [application]*Kdump* installer add-on `on` or `off` (the add-on is off by default). If you use [option]#inst.kdump_addon=on#, a new screen, which allows you to configure the [application]*Kdump* kernel crash dumping mechanism, will appear in the main menu of the graphical or text interface (see xref:install/Installing_Using_Anaconda.adoc#sect-installation-gui-kdump[Kdump]). Enabling this add-on is also necessary to use the xref:appendixes/Kickstart_Syntax_Reference.adoc#sect-kickstart-commands-kdump[%addon com_redhat_kdump (optional) - Configure kdump] Kickstart command. +[option]#inst.kdump_addon=#:: Turns the [application]*Kdump* installer add-on `on` or `off` +(the add-on is off by default). +If you use +[option]#inst.kdump_addon=on#, +a new screen, +which allows you to configure the +[application]*Kdump* kernel crash dumping mechanism, +will appear in the main menu of the graphical or text interface +(see +xref:install/Installing_Using_Anaconda.adoc#sect-installation-gui-kdump[Kdump]). +Enabling this add-on is also necessary to use the +xref:appendixes/Kickstart_Syntax_Reference.adoc#sect-kickstart-commands-kdump[%addon com_redhat_kdump (optional) - Configure kdump] +Kickstart command. [[sect-boot-options-vnc]] === Enabling Remote Access Using VNC The following options are necessary to configure [application]*Anaconda* for remote graphical installation. See xref:advanced/VNC_Installations.adoc#chap-vnc-installations[Installing Using VNC] for more details. -[option]#inst.vnc#:: Specifies that the installation program's graphical interface should be run in a `VNC` session. If you specify this option, you will need to connect to the system using a `VNC` client application to be able to interact with the installation program. `VNC` sharing is enabled, so multiple clients can connect to the system at the same time. +[option]#inst.vnc#:: Specifies that the installation program's graphical interface should be run in a `VNC` session. +If you specify this option, +you will need to connect to the system using a `VNC` client application + to be able to interact with the installation program. +`VNC` sharing is enabled, +so multiple clients can connect to the system at the same time. + [NOTE] ==== @@ -370,12 +528,19 @@ A system installed using `VNC` will start in text mode by default. ==== -[option]#inst.vncpassword=#:: `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. +[option]#inst.vncpassword=#:: `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. + [NOTE] ==== -If you specify an invalid password (one that is too short or too long), you will be prompted to specify a new one by a message from the installation program: +If you specify an invalid password +(one that is too short or too long), +you will be prompted to specify a new one by a message from the installation program: [subs="quotes"] ---- @@ -384,7 +549,7 @@ VNC password must be six to eight characters long. Please enter a new one, or leave blank for no password. Password: - + ---- ==== @@ -411,7 +576,6 @@ Options in this list are *deprecated*. They will still work, but there are other [NOTE] ==== - Note that as described in the introduction to this chapter, options specific to the installation program now use the `inst.` prefix. For example, the [option]#vnc=# option is considered deprecated and replaced by the [option]#inst.vnc=# option. However, these changes are not listed here. ==== @@ -462,14 +626,16 @@ modprobe.blacklist=firewire_ohci [[sect-boot-options-removed]] == Removed Boot Options -The following options are removed. They were present in previous releases of {PRODUCT}, but they cannot be used anymore. +The following options are removed. +They were present in previous releases of {PRODUCT}, but they cannot be used anymore. -[option]#asknetwork#:: The installation program's `initramfs` is now completely non-interactive, which means that this option are not available anymore. Use [option]#ip=# to configure network settings. +[option]#asknetwork#:: The installation program's `initramfs` is now completely non-interactive, +which means that this option are not available anymore. +Use [option]#ip=# to configure network settings. [option]#serial#:: This option forced [application]*Anaconda* to use the `/dev/ttyS0` console as the output. Use the [option]#console=/dev/ttyS0# (or similar) instead. [option]#updates=#:: Specified the location of updates for the installation program. Use the [option]#inst.updates=# option instead. - [option]#essid=#, [option]#wepkey=#, [option]#wpakey=#:: Configured wireless network access. Network configuration is now being handled by [application]*dracut*, which does not support wireless networking, rendering these options useless. [option]#ethtool=#:: Used in the past to configure additional low-level network settings. All network settings are now handled by the [option]#ip=# option. @@ -498,14 +664,20 @@ The following options are removed. They were present in previous releases of {PR [[sect-boot-options-memtest]] === Loading the Memory (RAM) Testing Mode -Faults in memory (RAM) modules may cause your system to freeze or crash unpredictably. In some cases, memory faults may only cause errors with particular combinations of software. For this reason, you should test the memory of a computer before you install {PRODUCT} for the first time, even if it has previously run other operating systems. +Faults in memory (RAM) modules may cause your system to freeze or crash unpredictably. +In some cases, +memory faults may only cause errors with particular combinations of software. +For this reason, you should test the memory of a computer +before you install {PRODUCT} for the first time, + even if it has previously run other operating systems. {PRODUCT} includes the [application]*Memtest86+* memory testing application. To start memory testing mode, choose Troubleshooting > `Memory test` at the boot menu. Testing will begin immediately. By default, [application]*Memtest86+* carries out ten tests in every pass; a different configuration can be specified by accessing the configuration screen using the kbd:[c] key. After the first pass completes, a message will appear at the bottom informing you of the current status, and another pass will start automatically. [NOTE] ==== -[application]*Memtest86+* only works on systems with BIOS firmware. Support for UEFI systems is currently unavailable. +[application]*Memtest86+* only works on systems with BIOS firmware. +Support for UEFI systems is currently unavailable. ==== @@ -533,25 +705,50 @@ In most cases, a single successful pass (that is, a single run of all 10 tests) [NOTE] ==== -The amount of time it takes to complete a single full pass of [application]*Memtest86+* varies depending on your system's configuration (notably the RAM size and speed). For example, on a system with 2{nbsp}GB of DDR2 memory at 667{nbsp}MHz, a single pass will take roughly 20{nbsp}minutes to complete. +The amount of time it takes to complete a single full pass of +[application]*Memtest86+* +varies depending on your system's configuration +(notably the RAM size and speed). +For example, on a system with +2{nbsp}GB of DDR2 memory at 667{nbsp}MHz, +a single pass will take roughly +20{nbsp}minutes +to complete. ==== To halt the tests and reboot your computer, press the kbd:[Esc] key at any time. -For more information about using [application]*Memtest86+*, see the official website at link:++https://www.memtest.org/++[]. A `README` file is also located in `/usr/share/doc/memtest86+-_version_pass:attributes[{blank}]/` on {PRODUCT} systems with the [package]*memtest86+* package installed. +For more information about using [application]*Memtest86+*, +see the official website at +link:++https://www.memtest.org/++[]. +A `README` file is also located in +`/usr/share/doc/memtest86+-_version_pass:attributes[{blank}]/` +on {PRODUCT} systems with the +[package]*memtest86+* +package installed. [[sect-boot-options-mediacheck]] === Verifying Boot Media -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. +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. To test the integrity of an ISO image, append the [option]#rd.live.check# to the boot loader command line. Note that this option is used automatically if you select the default installation option from the boot menu (`Test this media & install Fedora`). [[sect-boot-options-rescue]] === Booting Your Computer in Rescue Mode -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 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. To load the rescue system with the installation disk or USB drive, choose `Rescue a {PRODUCT} system` from the Troubleshooting submenu in the boot menu, or use the [option]#inst.rescue# boot option.