From 33b9d855372c98cea670752dd4ae1c1b663e5c9b Mon Sep 17 00:00:00 2001 From: Matthew Miller Date: Oct 10 2021 22:23:50 +0000 Subject: A large number of edits from Leslie S Satenstein as changes in a LibreOffice document. I have reformatted the relevant sections as SemBr (see previous commit). This now includes Leslie's suggested changes. --- diff --git a/modules/install-guide/pages/advanced/Boot_Options.adoc b/modules/install-guide/pages/advanced/Boot_Options.adoc index 5ff78b1..9c69121 100644 --- a/modules/install-guide/pages/advanced/Boot_Options.adoc +++ b/modules/install-guide/pages/advanced/Boot_Options.adoc @@ -4,23 +4,26 @@ include::{partialsdir}/entities.adoc[] [[chap-anaconda-boot-options]] = Boot Options +// LS: Is it the software that modified the default behavior, the installation program or the administrator. Three subjects and one conclusion. The [application]*Anaconda* installer includes a range of boot options -for administrators, -which modify the default behavior of the installation program +for administrators. +Administrators may 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 +you either have to boot from the installation media and append these options at the boot menu (see xref:install/Booting_the_Installation.adoc#sect-boot-menu[The Boot Menu]), +// LS: What is “PXE server”? There is no footnote to describe it. 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]). +// LS: When you use see, it should be somewhere else within this document. If the person has to visit a website or view external documentation, then use “refer to” +(refer to +xref: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. +separate each by a single space. There are two basic types of options described in this chapter: @@ -36,12 +39,12 @@ 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. +* Options presented without the "`pass:attributes[{blank}]`=`pass:attributes[{blank}]`" sign are keywords +and they 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, +if this keyword option is present, the check will be performed, and if it is not present, the check will be skipped. @@ -58,18 +61,18 @@ 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 +The exact way to specify custom boot options differs based on your system's architecture, firmware -and the method you use to boot the installation. +and the method you use to boot the installation media. If you are booting from local media, you can specify options in the boot menu, before you begin the installation; +// LS: Refer to earlier comment about PXE server. 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 +For specific instructions, refer to xref:install/Booting_the_Installation.adoc#sect-boot-menu[The Boot Menu] if you are booting from local media, and @@ -93,15 +96,18 @@ The following options are available in {PRODUCT}: + The source must be either: + +// LS: What are repodata and .treeinfo? Need a footnote. ** an installable tree, which is a directory structure containing the installation program's images, packages and repodata as well as a valid `.treeinfo` file + ** a DVD (a physical disk present in the system's DVD drive) + +// LS: USBs are now cheaply available for 16gig sizes. DVDs are not sold individually, but by hundreds and very expensive ** an ISO image of the full {PRODUCT} installation DVD, placed on a hard drive or a network location -accessible from the installation system +//LS: “Installation system”: Do you mean the chosen installation system? +accessible from the chosen installation system + -This option allows for the configuration of different installation methods using different formats. +This option allows the individual to configure different installation methods using different formats. The syntax is described in the table below. + [[tabl-boot-options-sources]] @@ -136,7 +142,7 @@ Non-alphanumeric characters must be represented as `\xpass:attributes[{blank}]_N [NOTE] ==== -By default, this boot option is used on the installation media and set to a specific label (for example, [option]#inst.stage2=hd:LABEL=F21\x20Server.x86_64#). If you modify the default label of the file system containing the runtime image, you must also edit this option to match the new label. +By default, this boot option is used on the installation media and is set to a specific label (for example, [option]#inst.stage2=hd:LABEL=F21\x20Server.x86_64#). If you modify the default label of the file system containing the runtime image, you must also edit this option to match the new label. ==== @@ -149,13 +155,14 @@ By default, this boot option is used on the installation media and set to a spec [option]#inst.dd=hd:/dev/sdb1:/driver.rpm# ---- + +// LS: The word “you” means that you may also include it above 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. + [IMPORTANT] ==== You should never attempt to perform a driver update -during the installation +during the running of the installation unless a missing our faulty driver is preventing you from completing the installation. Updating drivers which are not essential @@ -168,7 +175,7 @@ after the system is installed. + 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. +based on the type of boot media you used. The full {PRODUCT} Server DVD will configure the source as local media, the netinst ISO image will configure the closest network mirror, etc. @@ -176,14 +183,14 @@ 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. +without having to wait for the initial configuration to complete. + 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. +[option]#inst.ks=#:: Provides 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 @@ -221,7 +228,8 @@ 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 +// LS: this “what” +This sendmac option can be useful when using [option]#inst.ks=http# to provision systems. @@ -245,8 +253,8 @@ You can use this option multiple times. In that case, the boot message will be d + 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. +but you will still be able to change it at the very beginning of +the graphical installation phase. [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`. @@ -269,23 +277,26 @@ If this option is not specified, [application]*Anaconda* will use `provider_fedo [option]#inst.text#:: Forces the installation program to run in text mode instead of graphical mode. The text user interface is limited, for example, +// LS: What about BTRFS 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, +// LS: Need Footnote to describe VNC 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, +This mode does not allow any runtime 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. +[option]#inst.resolution=#:: Specifies the screen resolution for the 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`. +// LS: Wayland? [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#. @@ -304,16 +315,17 @@ modprobe.blacklist=ahci,firewire_ohci 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 +For more indepth information about `SSH`, +refer to the 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. +the `root` account, +by default, +has no setup password. You can set a root password to be used during the installation with the [command]#sshpw# Kickstart command @@ -330,7 +342,7 @@ xref:appendixes/Kickstart_Syntax_Reference.adoc#sect-kickstart-commands-sshpw[ss 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 +refer to the `dracut.cmdline(7)` man page. Additional information on networking is also available @@ -356,7 +368,7 @@ The following table lists valid values for this option: footnote:[Brings up the specified interface using the specified method of automatic configuration, such as `dhcp`, but overrides the automatically obtained IP address, gateway, netmask, hostname or other specified parameter. All parameters are optional; only specify the ones you wish to override and automatically obtained values will be used for the others.]|[option]#ip=pass:attributes[{blank}]_ip_::pass:attributes[{blank}]_gateway_:pass:attributes[{blank}]_netmask_:pass:attributes[{blank}]_hostname_:pass:attributes[{blank}]_interface_:pass:attributes[{blank}]_method_:pass:attributes[{blank}]_mtu_pass:attributes[{blank}]# |=== + -The [option]#method# parameter can be any the following: +The [option]#method# parameter can be any of the following: + [[tabl-boot-options-network-autoconf]] .Automatic Interface Configuration Methods @@ -379,7 +391,7 @@ 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, +`IPv6` addresses can be specified by putting them within square brackets, for example, `[2001:DB8::1]`. + @@ -409,8 +421,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 shows a set up a VLAN device named `vlan5` on the `em1` interface. +The _name_ can take one of the following forms: + [[tabl-boot-options-network-vlan-names]] .VLAN Device Naming Conventions @@ -446,9 +458,10 @@ Using this option without any parameters will assume [option]#bond=bond0:eth0,et [option]#inst.multilib#:: Configure the system for multilib packages (that is, to allow installing 32-bit packages on a 64-bit x86 system) and install packages specified in this section as such. + +// LS: 32bit available for ARM or am I wrong. No 32bit support. 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 +This option only applies to packages directly specified in the `%packages` section. If a package is only installed as a dependency, @@ -464,21 +477,26 @@ 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. +This option is meaningless on a UEFI-based system, +unless the system is 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 +Using this “inst.gpt” option will change this behavior, +allowing a GPT entry 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: -+ +// LS: this needs a rewrite. Consider rephrasing as +// ... when: +// Bullet Performing OEM operating systems +// Bullet or generating images using .. +// Bullet and/or longs on the ... +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). + `output_ks` - disables saving of the output Kickstart file generated by Anaconda. @@ -505,7 +523,7 @@ which allows you to configure the 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 +Enabling this add-on is also necessary in order to use the xref:appendixes/Kickstart_Syntax_Reference.adoc#sect-kickstart-commands-kdump[%addon com_redhat_kdump (optional) - Configure kdump] Kickstart command. @@ -516,15 +534,18 @@ The following options are necessary to configure [application]*Anaconda* for rem [option]#inst.vnc#:: Specifies that the installation program's graphical interface should be run in a `VNC` session. If you specify this option, +to interact with the installation program, 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, +// LS: concurrently? so multiple clients can connect to the system at the same time. + [NOTE] ==== -A system installed using `VNC` will start in text mode by default. +By default, +a system installed using `VNC` will start in text mode. ==== @@ -533,14 +554,14 @@ 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. +The password must contain between 6 and 8 characters. + [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: +the installation program will prompt you to specify a new one. [subs="quotes"] ---- @@ -573,9 +594,11 @@ Possible values for this option from the lowest to highest level are: `debug`, ` == 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. +// LS: Are they in or out. When was this paragraph written? Was it for Fedora 19, or later? [NOTE] ==== +// LS: same question about when this paragraph was written 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. ==== @@ -626,16 +649,17 @@ 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 and cannot be used anymore. +They were present in previous releases of {PRODUCT}. [option]#asknetwork#:: The installation program's `initramfs` is now completely non-interactive, -which means that this option are not available anymore. +which means that this option is no longer available. 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. +// LS: obsolete is 1 word, why blah blah blah [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. @@ -655,7 +679,7 @@ Use [option]#ip=# to configure network settings. [option]#upgradeany#:: Upgrades are done in a different way in current {PRODUCT} releases. For more information about upgrading your system, see xref:advanced/Upgrading_Your_Current_System.adoc#chap-upgrading[Upgrading Your Current System]. [option]#vlanid=#:: Used to configure Virtual LAN (802.1q tag) devices. Use the [option]#vlan=# option instead. - +// LS: Fedora 21 – is Yum still relevant? [option]#inst.dnf#:: Used to enable [application]*DNF* to handle package installation and dependency resolution in {PRODUCT} 21. [application]*DNF* is now used by default and this option has been replaced with [option]#inst.nodnf#, which reverts back to [application]*Yum*. [[sect-boot-options-maintenance]] @@ -667,9 +691,10 @@ Use [option]#ip=# to configure network settings. 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. +// LS: What is “the first time”? The {PRODUCT} or the ram.? 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. +before you install {PRODUCT} +even if the ram was previously been used to 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. @@ -677,10 +702,10 @@ before you install {PRODUCT} for the first time, ==== [application]*Memtest86+* only works on systems with BIOS firmware. -Support for UEFI systems is currently unavailable. +Support for UEFI systems is currently unavailable and is therefore not distributed. ==== - +// LS: Does this part need to be here if we are dealing with UEFI systems? .Memory Check Using Memtest86+ image::boot/memtest86.png[Memtest86+ testing the system memory] @@ -708,7 +733,7 @@ In most cases, a single successful pass (that is, a single run of all 10 tests) 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). +(notably the RAM size and processor speed). For example, on a system with 2{nbsp}GB of DDR2 memory at 667{nbsp}MHz, a single pass will take roughly @@ -720,7 +745,7 @@ 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 +refer to the official website at link:++https://www.memtest.org/++[]. A `README` file is also located in `/usr/share/doc/memtest86+-_version_pass:attributes[{blank}]/` @@ -735,17 +760,18 @@ 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. +or a NFS server. Verifying that the ISO images are intact before you attempt an installation helps to avoid problems that are often encountered during installation. +// LS: From my perspective, the memtest should be compulsary for the everything-network iso image and a boot option for all other Fedora Images. 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 +You may boot a command-line Linux system from an installation disk 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.