From 6136c495802b607327745611fb201add7670235c Mon Sep 17 00:00:00 2001 From: Robert Krátký Date: Aug 10 2017 07:52:21 +0000 Subject: Switch to hardcoded xrefs. --- diff --git a/en-US/advanced/Boot_Options.adoc b/en-US/advanced/Boot_Options.adoc index aacfd30..6f9dc75 100644 --- a/en-US/advanced/Boot_Options.adoc +++ b/en-US/advanced/Boot_Options.adoc @@ -5,7 +5,7 @@ include::en-US/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 <>), or you must add them into your PXE server configuration file if you are booting from a network (see <>). +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: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. @@ -27,7 +27,7 @@ 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 <> if you are booting from local media, and <> 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: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 @@ -80,7 +80,7 @@ Disk device names may be specified using the following formats: + Non-alphanumeric characters must be represented as `\xpass:attributes[{blank}]_NN_pass:attributes[{blank}]`, where _NN_ is the hexadecimal representation of the character. For example, `\x20` is a white space (""). -[option]#inst.stage2=#:: Specifies the location of the installation program runtime image to be loaded. The syntax is the same as in <>. This option expects a path to a directory containing a valid `.treeinfo` file; the location of the runtime image will be read from this file if found. If a `.treeinfo` file is not available, [application]*Anaconda* will try to load the image from `LiveOS/squashfs.img`. +[option]#inst.stage2=#:: Specifies the location of the installation program runtime image to be loaded. The syntax is the same as in xref:Boot_Options.adoc#tabl-boot-options-sources[Installation Sources]. This option expects a path to a directory containing a valid `.treeinfo` file; the location of the runtime image will be read from this file if found. If a `.treeinfo` file is not available, [application]*Anaconda* will try to load the image from `LiveOS/squashfs.img`. + [NOTE] ==== @@ -89,7 +89,7 @@ By default, this boot option is used on the installation media and set to a spec ==== -[option]#inst.dd=#:: If you need to perform a driver update during the installation, use the [option]#inst.dd=# option. It can be used multiple times. The location of a driver RPM package can be specified using any of the formats described in <>. With the exception of the [option]#inst.dd=cdrom# option, the device name must always be specified. For example: +[option]#inst.dd=#:: If you need to perform a driver update during the installation, use the [option]#inst.dd=# option. It can be used multiple times. The location of a driver RPM package can be specified using any of the formats described in xref:Boot_Options.adoc#tabl-boot-options-sources[Installation Sources]. With the exception of the [option]#inst.dd=cdrom# option, the device name must always be specified. For example: + [subs="quotes, macros"] ---- @@ -114,7 +114,7 @@ Using this option will leave the installation source configuration in an error s [[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 <> 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:Boot_Options.adoc#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: + @@ -159,7 +159,7 @@ You can use this option multiple times. In that case, the boot message will be d [option]#noshell#:: Disables access to the root shell during the installation. This is useful with automated (Kickstart) installations - if you use this option, a user can watch the installation progress, but they cannot interfere with it by accessing the root shell by pressing kbd:[Ctrl + Alt + F2]. -[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 <>. 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`. +[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. @@ -180,9 +180,9 @@ The _value_ parameter can be any of the following: + If this option is not specified, [application]*Anaconda* will use `provider_fedora_geoip`. -[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 <>. +[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#appe-kickstart-syntax-reference[Kickstart Syntax Reference]. -[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 <>. +[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:Boot_Options.adoc#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. @@ -207,7 +207,7 @@ modprobe.blacklist=ahci,firewire_ohci [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 <>. +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]. ==== @@ -326,7 +326,7 @@ This only applies to packages directly specified in the `%packages` section. If + 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 <> for more information about GPT and MBR, and <> for more general information about GPT, MBR and disk partitioning in general. +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: + @@ -350,12 +350,12 @@ By default, swap on zRAM is enabled on systems with 2 GB or less RAM, and disabl [option]#inst.nodnf#:: Use the older [application]*Yum* backend for package installation and dependency resolution instead of [application]*DNF*. See the [citetitle]_{PRODUCT} System Administrator's Guide_, available at link:++https://docs.fedoraproject.org/++[], 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 <>). Enabling this add-on is also necessary to use the <> 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 <> for more details. +The following options are necessary to configure [application]*Anaconda* for remote graphical installation. See xref: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. + @@ -390,7 +390,7 @@ Password: [[sect-boot-options-debug]] ===== Debugging and Troubleshooting -[option]#inst.updates=#:: Specifies the location of the `updates.img` file to be applied to the installation program runtime. The syntax is the same as in the [option]#inst.repo# option - see <> for details. In all formats, if you do not specify a file name but only a directory, the installation program will look for a file named `updates.img`. +[option]#inst.updates=#:: Specifies the location of the `updates.img` file to be applied to the installation program runtime. The syntax is the same as in the [option]#inst.repo# option - see xref:Boot_Options.adoc#tabl-boot-options-sources[Installation Sources] for details. In all formats, if you do not specify a file name but only a directory, the installation program will look for a file named `updates.img`. [option]#inst.loglevel=#:: Specifies the minimum level for messages to be logged on a terminal. This only concerns real-time logging in a terminal; log files will always contain messages of all levels. + @@ -482,7 +482,7 @@ The following options are removed. They were present in previous releases of {PR [option]#noipv6#:: Used to disable IPv6 support in the installation program. IPv6 is now built into the kernel so the driver cannot be blacklisted; however, it is possible to disable IPv6 using the [option]#ipv6.disable# option. -[option]#upgradeany#:: Upgrades are done in a different way in current {PRODUCT} releases. For more information about upgrading your system, see <>. +[option]#upgradeany#:: Upgrades are done in a different way in current {PRODUCT} releases. For more information about upgrading your system, see xref: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. diff --git a/en-US/advanced/Kickstart_Installations.adoc b/en-US/advanced/Kickstart_Installations.adoc index 4be902b..e6f1ff9 100644 --- a/en-US/advanced/Kickstart_Installations.adoc +++ b/en-US/advanced/Kickstart_Installations.adoc @@ -29,7 +29,7 @@ This chapter explains these steps in detail. [[sect-kickstart-file-create]] ===== Creating a Kickstart File -The Kickstart file itself is a plain text file, containing keywords listed in <>, which serve as directions for the installation. Any text editor able to save files as ASCII text (such as [application]*Gedit* or [application]*vim* on Linux systems or [application]*Notepad* on Windows systems) can be used to create and edit Kickstart files. +The Kickstart file itself is a plain text file, containing keywords listed in xref:../appendixes/Kickstart_Syntax_Reference.adoc#appe-kickstart-syntax-reference[Kickstart Syntax Reference], which serve as directions for the installation. Any text editor able to save files as ASCII text (such as [application]*Gedit* or [application]*vim* on Linux systems or [application]*Notepad* on Windows systems) can be used to create and edit Kickstart files. The recommended approach to creating Kickstart files is to perform a manual installation on one system first. After the installation completes, all choices made during the installation are saved into a file named `anaconda-ks.cfg`, located in the `/root/` directory on the installed system. You can then copy this file, make any changes you need, and use the resulting configuration file in further installations. @@ -39,11 +39,11 @@ When creating a Kickstart file, keep in mind the following: * Sections must be specified *in order*. Items within the sections do not have to be in a specific order unless otherwise specified. The correct section order is: + -** The command section which contains actual Kickstart commands and options as listed in <>. Note that some commands, such as [command]#install#, are mandatory, but most commands are optional. +** The command section which contains actual Kickstart commands and options as listed in xref:../appendixes/Kickstart_Syntax_Reference.adoc#appe-kickstart-syntax-reference[Kickstart Syntax Reference]. Note that some commands, such as [command]#install#, are mandatory, but most commands are optional. + -** The [command]#%packages# section which contains a list of packages and package groups to be installed. See <> for details. +** The [command]#%packages# section which contains a list of packages and package groups to be installed. See xref:../appendixes/Kickstart_Syntax_Reference.adoc#sect-kickstart-packages[%packages (required) - Package Selection] for details. + -** The [command]#%pre# and [command]#%post# sections, containing a pre-installation and post-installation scripts. These two sections can be in any order and are not mandatory. See <> and <> for details. +** The [command]#%pre# and [command]#%post# sections, containing a pre-installation and post-installation scripts. These two sections can be in any order and are not mandatory. See xref:../appendixes/Kickstart_Syntax_Reference.adoc#sect-kickstart-preinstall[%pre (optional) - Pre-installation Script] and xref:../appendixes/Kickstart_Syntax_Reference.adoc#sect-kickstart-postinstall[%post (optional) - Post-installation Script] for details. + [IMPORTANT] ==== @@ -95,9 +95,9 @@ Once you create a Kickstart file, you can place it in one of the following locat Normally, a Kickstart file is copied to removable media or a hard drive, or made available on the network. Placing the file in a network location complements the usual approach to Kickstart installations, which is also network-based: the system is booted using a PXE server, the Kickstart file is downloaded from a network share, and software packages specified in the file are downloaded from remote repositories. -<> offers some additional information about preparing for a network-based installation. +xref:Network_based_Installations.adoc#chap-pxe-server-setup[Setting Up an Installation Server] offers some additional information about preparing for a network-based installation. [[sect-kickstart-installation-starting]] ===== Starting the Kickstart Installation -Once you have everything ready - you have created a valid Kickstart file and you have either local boot media or a PXE server available, you can start the Kickstart installation. You need to use the [option]#inst.ks=# boot option either in the boot menu (when booting from local media), or add this option to your PXE server configuration. For information about boot options used in Kickstart installations, see <>. +Once you have everything ready - you have created a valid Kickstart file and you have either local boot media or a PXE server available, you can start the Kickstart installation. You need to use the [option]#inst.ks=# boot option either in the boot menu (when booting from local media), or add this option to your PXE server configuration. For information about boot options used in Kickstart installations, see xref:Boot_Options.adoc#sect-boot-options-kickstart[Kickstart Boot Options]. diff --git a/en-US/advanced/Network_based_Installations.adoc b/en-US/advanced/Network_based_Installations.adoc index 5ed6348..2c1e4ff 100644 --- a/en-US/advanced/Network_based_Installations.adoc +++ b/en-US/advanced/Network_based_Installations.adoc @@ -33,7 +33,7 @@ Because the job of booting an operating system is too complex for the pre-boot e The kernel is the core of any Linux operating system, and the initramfs provides the kernel with required tools and resources. These files are also provided by tftp. .Package repository -A Fedora repository must be available for the installation. The example in this section uses the public Fedora mirrors as the repository source, but you can also use a repo on the local network provided by NFS, FTP, or HTTP. Repositories can be configured using the [option]#inst.repo=# boot option; see <> for details. +A Fedora repository must be available for the installation. The example in this section uses the public Fedora mirrors as the repository source, but you can also use a repo on the local network provided by NFS, FTP, or HTTP. Repositories can be configured using the [option]#inst.repo=# boot option; see xref:Boot_Options.adoc#sect-boot-options-sources[Specifying the Installation Source] for details. //A link to mirrormanager and some instructions to other guides too. All the elaboration on installation methods might be going to far, but we can ref. --Pete diff --git a/en-US/advanced/Upgrading_Your_Current_System.adoc b/en-US/advanced/Upgrading_Your_Current_System.adoc index 1c83095..1764d7d 100644 --- a/en-US/advanced/Upgrading_Your_Current_System.adoc +++ b/en-US/advanced/Upgrading_Your_Current_System.adoc @@ -9,7 +9,7 @@ This chapter explains how to upgrade your existing {PRODUCT} installation to the Automatic upgrade using [application]*dnf system upgrade*:: The preferred way to upgrade your system is an automatic upgrade using the [application]*dnf system upgrade* utility. For information on performing an automatic upgrade, see link:++https://fedoraproject.org/wiki/DNF_system_upgrade++[Fedora Wiki DNF system upgrade]. -Manual Reinstallation:: You can upgrade to the latest version of Fedora manually instead of relying on [application]*dnf system upgrade*. This involves booting the installer as if you were performing a clean installation, letting it detect your existing Fedora system, and overwriting the root partition while preserving data on other partitions and volumes. The same process can also be used to reinstall the system, if you need to. For detailed information, see <>. +Manual Reinstallation:: You can upgrade to the latest version of Fedora manually instead of relying on [application]*dnf system upgrade*. This involves booting the installer as if you were performing a clean installation, letting it detect your existing Fedora system, and overwriting the root partition while preserving data on other partitions and volumes. The same process can also be used to reinstall the system, if you need to. For detailed information, see xref:Upgrading_Your_Current_System.adoc#sect-upgrading-fedora-manual-reinstall[Manual System Upgrade or Reinstallation]. [WARNING] ==== @@ -21,4 +21,4 @@ Always back up your data before performing an upgrade or reinstalling your syste [[sect-upgrading-fedora-manual-reinstall]] ==== Manual System Upgrade or Reinstallation -Unfortunately, we have not written this chapter yet, and there is no dedicated documentation about a manual reinstall on the Wiki, either. In the meantime before we fix this, you can try to start the installation normally (from a boot CD/DVD/USB), select manual partitioning in your installer, and reuse existing partitions instead of destroying them and creating new ones. The instructions at <> should in most cases be easy to adapt for this. +Unfortunately, we have not written this chapter yet, and there is no dedicated documentation about a manual reinstall on the Wiki, either. In the meantime before we fix this, you can try to start the installation normally (from a boot CD/DVD/USB), select manual partitioning in your installer, and reuse existing partitions instead of destroying them and creating new ones. The instructions at xref:../install/Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning[Manual Partitioning] should in most cases be easy to adapt for this. diff --git a/en-US/advanced/VNC_Installations.adoc b/en-US/advanced/VNC_Installations.adoc index 457ca6f..5a64e24 100644 --- a/en-US/advanced/VNC_Installations.adoc +++ b/en-US/advanced/VNC_Installations.adoc @@ -69,14 +69,14 @@ VNC Direct Mode is when the VNC viewer initiates a connection to the system bein [[proc-vnc-installations-direct-mode]] .Starting VNC in Direct Mode -. Open the VNC viewer (for example, [application]*TigerVNC*) on the workstation you will be using to connect to the system being installed. A window similar to <> will be displayed with an input field allowing you to specify an IP address. +. Open the VNC viewer (for example, [application]*TigerVNC*) on the workstation you will be using to connect to the system being installed. A window similar to xref:VNC_Installations.adoc#figu-vnc-installations-connection-details[TigerVNC Connection Details] will be displayed with an input field allowing you to specify an IP address. + [[figu-vnc-installations-connection-details]] .TigerVNC Connection Details + image::vnc/connection-details.png[TigerVNC after startup, showing the Connection Details dialog] -. Boot the installation system and wait for the boot menu to appear. In the menu, edit boot options (see <>) and append the [option]#inst.vnc# option to the end of the command line. +. Boot the installation system and wait for the boot menu to appear. In the menu, edit boot options (see xref:../install/Booting_the_Installation.adoc#sect-boot-menu[The Boot Menu]) and append the [option]#inst.vnc# option to the end of the command line. + Optionally, if you want to restrict VNC access to the installation system, add the [option]#inst.vncpassword=pass:attributes[{blank}]_PASSWORD_pass:attributes[{blank}]# boot option as well. Replace _PASSWORD_ with the password you want to use for the installation. The VNC password must be between 6 and 8 characters long. + @@ -105,7 +105,7 @@ Note the IP address and port number (in the above example, `192.168.100.131:5901 When the connection is successfully established, a new window will open on the system running the VNC viewer, displaying the installation menu. This window will provide full remote access to the installer until the installation finishes and the system reboots for the first time. -You can then proceed with <>. +You can then proceed with xref:../install/Installing_Using_Anaconda.adoc#chap-installing-using-anaconda[Installing Using Anaconda]. [[sect-vnc-installations-connect-mode]] ===== Installing in VNC Connect Mode @@ -146,7 +146,7 @@ main: Listening on port 5901 + When this message is displayed, the VNC viewer is ready and waiting for an incoming connection from the installation system. -. Boot the installation system and wait for the boot menu to appear. In the menu, edit boot options (see <>) and append the following options to the end of the command line: +. Boot the installation system and wait for the boot menu to appear. In the menu, edit boot options (see xref:../install/Booting_the_Installation.adoc#sect-boot-menu[The Boot Menu]) and append the following options to the end of the command line: + [subs="quotes, macros"] ---- @@ -159,20 +159,20 @@ Replace _HOST_ with the IP address of the system running the listening VNC viewe + When the connection is successfully established, a new window will open on the system running the VNC viewer, displaying the installation menu. This window will provide full remote access to the installer until the installation finishes and the system reboots for the first time. -You can then proceed with <>. +You can then proceed with xref:../install/Installing_Using_Anaconda.adoc#chap-installing-using-anaconda[Installing Using Anaconda]. [[sect-vnc-kickstart-considerations]] ==== Kickstart Considerations -Commands for using a VNC installation are also available in Kickstart installations. Using just the [command]#vnc# command will set up an installation using Direct Mode. Options are available to set up an installation using Connect Mode. For more information about the [command]#vnc# command and options used in Kickstart files, see <>. +Commands for using a VNC installation are also available in Kickstart installations. Using just the [command]#vnc# command will set up an installation using Direct Mode. Options are available to set up an installation using Connect Mode. For more information about the [command]#vnc# command and options used in Kickstart files, see xref:../appendixes/Kickstart_Syntax_Reference.adoc#appe-kickstart-syntax-reference[Kickstart Syntax Reference]. [[sect-vnc-headless-considerations]] ==== Considerations for Headless Systems -When installing headless systems, the only choices are an automated Kickstart installation or an interactive VNC installation using connect mode. For more information about automated Kickstart installation, see <>. The general process for an interactive VNC installation is described below. +When installing headless systems, the only choices are an automated Kickstart installation or an interactive VNC installation using connect mode. For more information about automated Kickstart installation, see xref:../appendixes/Kickstart_Syntax_Reference.adoc#appe-kickstart-syntax-reference[Kickstart Syntax Reference]. The general process for an interactive VNC installation is described below. -. Set up a PXE server that will be used to start the installation. Information about installing and performing basic configurating of a PXE server can be found in <>. +. Set up a PXE server that will be used to start the installation. Information about installing and performing basic configurating of a PXE server can be found in xref:Network_based_Installations.adoc#chap-pxe-server-setup[Setting Up an Installation Server]. -. Configure the PXE server to use the boot options for a connect mode VNC installation. For information on these boot options, see <>. +. Configure the PXE server to use the boot options for a connect mode VNC installation. For information on these boot options, see xref:VNC_Installations.adoc#sect-vnc-installations-connect-mode[Installing in VNC Connect Mode]. -. Follow the procedure for a VNC Installation using connect mode as described in the <>. However, when directed to boot the system, boot it from the PXE server. +. Follow the procedure for a VNC Installation using connect mode as described in the xref:VNC_Installations.adoc#proc-vnc-installations-connect-mode[Starting VNC in Connect Mode]. However, when directed to boot the system, boot it from the PXE server. diff --git a/en-US/appendixes/Disk_Partitions.adoc b/en-US/appendixes/Disk_Partitions.adoc index 7c3bb0d..3f3a89a 100644 --- a/en-US/appendixes/Disk_Partitions.adoc +++ b/en-US/appendixes/Disk_Partitions.adoc @@ -14,7 +14,7 @@ This appendix is not necessarily applicable to architectures other than AMD64 an This section discusses basic disk concepts, disk repartitioning strategies, the partition naming scheme used by Linux systems, and related topics. -If you are comfortable with disk partitions, you can skip ahead to <> for more information on the process of freeing up disk space to prepare for a {PRODUCT} installation. +If you are comfortable with disk partitions, you can skip ahead to xref:Disk_Partitions.adoc#sect-disk-partitions-making-room[Strategies for Disk Repartitioning] for more information on the process of freeing up disk space to prepare for a {PRODUCT} installation. [[sect-disk-partitions-basic-concepts]] ==== Hard Disk Basic Concepts @@ -23,7 +23,7 @@ Hard disks perform a very simple function - they store data and reliably retriev When discussing issues such as disk partitioning, it is important to have a understanding of the underlying hardware; however, since the theory is very complicated and expansive, only the basic concepts will be explained here. This appendix uses a set of simplified diagrams of a disk drive to help explain what is the process and theory behind partitions. -<>, shows a brand-new, unused disk drive. +xref:Disk_Partitions.adoc#figu-partitions-unused-drive[An Unused Disk Drive], shows a brand-new, unused disk drive. [[figu-partitions-unused-drive]] .An Unused Disk Drive @@ -40,14 +40,14 @@ To store data on a disk drive, it is necessary to _format_ the disk drive first. image::partitions/formatted-drive.png[Image of a formatted disk drive.] -As <>, implies, the order imposed by a file system involves some trade-offs: +As xref:Disk_Partitions.adoc#figu-partitions-formatted-drive[Disk Drive with a File System], implies, the order imposed by a file system involves some trade-offs: * A small percentage of the driver's available space is used to store file system-related data and can be considered as overhead. * A file system splits the remaining space into small, consistently-sized segments. For Linux, these segments are known as _blocks_. footnote:[Blocks really *are* consistently sized, unlike our illustrations. Keep in mind, also, that an average disk drive contains thousands of blocks. The picture is simplified for the purposes of this discussion.] -Note that there is no single, universal file system. As <>, shows, a disk drive may have one of many different file systems written on it. Different file systems tend to be incompatible; that is, an operating system that supports one file system (or a handful of related file system types) may not support another. However, {PRODUCT} supports a wide variety of file systems (including many commonly used by other operating systems such as Microsoft Windows), making data interchange between different file systems easy. +Note that there is no single, universal file system. As xref:Disk_Partitions.adoc#figu-partitions-different-file-system[Disk Drive with a Different File System], shows, a disk drive may have one of many different file systems written on it. Different file systems tend to be incompatible; that is, an operating system that supports one file system (or a handful of related file system types) may not support another. However, {PRODUCT} supports a wide variety of file systems (including many commonly used by other operating systems such as Microsoft Windows), making data interchange between different file systems easy. [[figu-partitions-different-file-system]] .Disk Drive with a Different File System @@ -61,7 +61,7 @@ Writing a file system to disk is only the first step. The goal of this process i image::partitions/used-formatted-drive.png[Image of a disk drive with data written to it.] -As <>, shows, some of the previously-empty blocks are now holding data. However, by just looking at this picture, we cannot determine exactly how many files reside on this drive. There may only be one file or many, as all files use at least one block and some files use multiple blocks. Another important point to note is that the used blocks do not have to form a contiguous region; used and unused blocks may be interspersed. This is known as _fragmentation_. Fragmentation can play a part when attempting to resize an existing partition. +As xref:Disk_Partitions.adoc#figu-partitions-drive-with-data[Disk Drive with Data Written to It], shows, some of the previously-empty blocks are now holding data. However, by just looking at this picture, we cannot determine exactly how many files reside on this drive. There may only be one file or many, as all files use at least one block and some files use multiple blocks. Another important point to note is that the used blocks do not have to form a contiguous region; used and unused blocks may be interspersed. This is known as _fragmentation_. Fragmentation can play a part when attempting to resize an existing partition. As with most computer-related technologies, disk drives changed over time after their introduction. In particular, they got bigger. Not larger in physical size, but bigger in their capacity to store information. And, this additional capacity drove a fundamental change in the way disk drives were used. @@ -78,7 +78,7 @@ There are several reasons for allocating disk space into separate disk partition * Ability to run multiple operating systems on one machine -There are currently two partitioning layout standards for physical hard disks: Master Boot Record (*MBR*) and GUID Partition Table (*GPT*). *MBR* is an older method of disk partitioning used with BIOS-based computers. *GPT* is a newer partitioning layout that is a part of the Unified Extensible Firmware Interface (*UEFI*). This section and <> mainly describe the _Master Boot Record_ (*MBR*) disk partitioning scheme. For information about the _GUID Partition Table_ (*GPT*) partitioning layout, see <>. +There are currently two partitioning layout standards for physical hard disks: Master Boot Record (*MBR*) and GUID Partition Table (*GPT*). *MBR* is an older method of disk partitioning used with BIOS-based computers. *GPT* is a newer partitioning layout that is a part of the Unified Extensible Firmware Interface (*UEFI*). This section and xref:Disk_Partitions.adoc#sect-disk-partitions-extended[Partitions Within Partitions - An Overview of Extended Partitions] mainly describe the _Master Boot Record_ (*MBR*) disk partitioning scheme. For information about the _GUID Partition Table_ (*GPT*) partitioning layout, see xref:Disk_Partitions.adoc#sect-disk-partitioning-guid-partition-table[GUID Partition Table (GPT)]. [NOTE] ==== @@ -92,7 +92,7 @@ While the diagrams in this chapter show the partition table as being separate fr image::partitions/unused-partitioned-drive.png[Image of an unused disk drive with a partition table.] -As <> shows, the partition table is divided into four sections or four _primary_ partitions. A primary partition is a partition on a hard drive that can contain only one logical drive (or section). Each section can hold the information necessary to define a single partition, meaning that the partition table can define no more than four partitions. +As xref:Disk_Partitions.adoc#figu-partitions-partition-table[Disk Drive with Partition Table] shows, the partition table is divided into four sections or four _primary_ partitions. A primary partition is a partition on a hard drive that can contain only one logical drive (or section). Each section can hold the information necessary to define a single partition, meaning that the partition table can define no more than four partitions. Each partition table entry contains several important characteristics of the partition: @@ -106,7 +106,7 @@ The starting and ending points define the partition's size and location on the d The type is a number that identifies the partition's anticipated usage. Some operating systems use the partition type to denote a specific file system type, to flag the partition as being associated with a particular operating system, to indicate that the partition contains a bootable operating system, or some combination of the three. -See <> for an example of a disk drive with single partition. +See xref:Disk_Partitions.adoc#figu-partitions-single-part[Disk Drive With Single Partition] for an example of a disk drive with single partition. [[figu-partitions-single-part]] .Disk Drive With Single Partition @@ -148,7 +148,7 @@ The single partition in this example is labeled as `DOS`. This label shows the * In case four partitions are insufficient for your needs, you can use _extended partitions_ to create up additional partitions. You do this by setting the type of a partition to "Extended". -An extended partition is like a disk drive in its own right - it has its own partition table which points to one or more partitions (now called _logical partitions_, as opposed to the four _primary partitions_) contained entirely within the extended partition itself. <>, shows a disk drive with one primary partition and one extended partition containing two logical partitions (along with some unpartitioned free space). +An extended partition is like a disk drive in its own right - it has its own partition table which points to one or more partitions (now called _logical partitions_, as opposed to the four _primary partitions_) contained entirely within the extended partition itself. xref:Disk_Partitions.adoc#figu-partitions-extended[Disk Drive With Extended Partition], shows a disk drive with one primary partition and one extended partition containing two logical partitions (along with some unpartitioned free space). [[figu-partitions-extended]] .Disk Drive With Extended Partition @@ -204,7 +204,7 @@ Keep in mind that the following illustrations are simplified in the interest of [[sect-disk-partitions-using-free-space]] ===== Using Unpartitioned Free Space -In this situation, the partitions already defined do not span the entire hard disk, leaving unallocated space that is not part of any defined partition. <>, shows what this might look like. +In this situation, the partitions already defined do not span the entire hard disk, leaving unallocated space that is not part of any defined partition. xref:Disk_Partitions.adoc#figu-partitions-unused-space[Disk Drive with Unpartitioned Free Space], shows what this might look like. [[figu-partitions-unused-space]] .Disk Drive with Unpartitioned Free Space @@ -215,12 +215,12 @@ In the above example, `1` represents an undefined partition with unallocated spa An unused hard disk also falls into this category. The only difference is that *all* the space is not part of any defined partition. -In any case, you can create the necessary partitions from the unused space. Unfortunately, this scenario, although very simple, is not very likely (unless you have just purchased a new disk just for {PRODUCT}). Most pre-installed operating systems are configured to take up all available space on a disk drive (see <>). +In any case, you can create the necessary partitions from the unused space. Unfortunately, this scenario, although very simple, is not very likely (unless you have just purchased a new disk just for {PRODUCT}). Most pre-installed operating systems are configured to take up all available space on a disk drive (see xref:Disk_Partitions.adoc#sect-disk-partitions-active-partition[Using Free Space from an Active Partition]). [[sect-disk-partitions-unused-partition]] ===== Using Space from an Unused Partition -In this case, maybe you have one or more partitions that you do not use any longer. <>, illustrates such a situation. +In this case, maybe you have one or more partitions that you do not use any longer. xref:Disk_Partitions.adoc#figu-partitions-unused-partition[Disk Drive with an Unused Partition], illustrates such a situation. [[figu-partitions-unused-partition]] .Disk Drive with an Unused Partition @@ -247,7 +247,7 @@ If an operating system was installed on that partition, it must be reinstalled i ==== + -After creating a smaller partition for your existing operating system, you can reinstall software, restore your data, and start the installation. <> shows this being done. +After creating a smaller partition for your existing operating system, you can reinstall software, restore your data, and start the installation. xref:Disk_Partitions.adoc#figu-partitions-destructive-repartitioning[Disk Drive Being Destructively Repartitioned] shows this being done. + [[figu-partitions-destructive-repartitioning]] .Disk Drive Being Destructively Repartitioned @@ -292,7 +292,7 @@ This step is crucial. Without it, the location of the data could prevent the par [[sect-disk-partitions-resize-existing]] ====== Resize the Existing Partition -<> shows the actual resizing process. While the actual result of the resizing operation varies depending on the software used, in most cases the newly freed space is used to create an unformatted partition of the same type as the original partition. +xref:Disk_Partitions.adoc#figu-partitions-resize-existing[Disk Drive with Partition Resized] shows the actual resizing process. While the actual result of the resizing operation varies depending on the software used, in most cases the newly freed space is used to create an unformatted partition of the same type as the original partition. [[figu-partitions-resize-existing]] .Disk Drive with Partition Resized @@ -306,7 +306,7 @@ It is important to understand what the resizing software you use does with the n [[sect-disk-partitions-create-new]] ====== Create new partition(s) -As the previous step implied, it may or may not be necessary to create new partitions. However, unless your resizing software is Linux-aware, it is likely that you must delete the partition that was created during the resizing process. <>, shows this being done. +As the previous step implied, it may or may not be necessary to create new partitions. However, unless your resizing software is Linux-aware, it is likely that you must delete the partition that was created during the resizing process. xref:Disk_Partitions.adoc#figu-partitions-final-configuration[Disk Drive with Final Partition Configuration], shows this being done. [[figu-partitions-final-configuration]] .Disk Drive with Final Partition Configuration @@ -358,4 +358,4 @@ At this point in the process of preparing to install {PRODUCT}, you should give Unless you have a reason for doing otherwise, you should *at least* create a `/boot` partition and a `/` (root) partition. Depending on your system's hardware specifications, additional partitions may be necessary, such as `/boot/efi` for 64-bit AMD and Intel systems with UEFI firmware, a `biosboot` partition for AMD and Intel systems with a GUID Partition Table (GPT) label on the system disk, or a `PReP Boot` partition on IBM Power Systems servers. -See <> for more information about the recommended partitioning scheme. +See xref:../install/Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-recommended[Recommended Partitioning Scheme] for more information about the recommended partitioning scheme. diff --git a/en-US/appendixes/Kickstart_Syntax_Reference.adoc b/en-US/appendixes/Kickstart_Syntax_Reference.adoc index 60c1b56..4797975 100644 --- a/en-US/appendixes/Kickstart_Syntax_Reference.adoc +++ b/en-US/appendixes/Kickstart_Syntax_Reference.adoc @@ -5,7 +5,7 @@ include::en-US/entities.adoc[] [[appe-kickstart-syntax-reference]] === Kickstart Syntax Reference -This appendix describes commands and options available in Kickstart installations. For general information about Kickstart, see <>. +This appendix describes commands and options available in Kickstart installations. For general information about Kickstart, see xref:../advanced/Kickstart_Installations.adoc#chap-kickstart-installations[Automating the Installation with Kickstart]. [IMPORTANT] ==== @@ -197,7 +197,7 @@ This command also supports installation from tar archives of the root file syste [[sect-kickstart-commands-mediacheck]] ===== mediacheck (optional) - Verify Installation Media Integrity -This command will force the installation program to perform a media check before starting the installation, similarly to the [option]#rd.live.check# boot option (see <>. This command requires that installations be attended, so it is disabled by default. +This command will force the installation program to perform a media check before starting the installation, similarly to the [option]#rd.live.check# boot option (see xref:../advanced/Boot_Options.adoc#sect-boot-options-mediacheck[Verifying Boot Media]. This command requires that installations be attended, so it is disabled by default. [[sect-kickstart-commands-ostreesetup]] ===== ostreesetup (optional) - Install from an OSTree @@ -275,7 +275,7 @@ The [command]#autopart# option cannot be used together with the [command]#part/p + ** `thinp`: The LVM Thin Provisioning partitioning scheme. + -The created partitioning scheme will follow the recommended scheme described at <>. +The created partitioning scheme will follow the recommended scheme described at xref:../install/Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-recommended[Recommended Partitioning Scheme]. [option]#--fstype=#:: Specify a supported file system (such as `ext4` or `xfs`) to replace the default when doing automatic partitioning. @@ -306,7 +306,7 @@ You should always use a password to protect your boot loader. An unprotected boo [IMPORTANT] ==== -Some systems require a special partition for installing the boot loader. The type and size of this partition depends on whether the disk you are installing the boot loader to uses the _Master Boot Record_ (MBR) or a _GUID Partition Table_ (GPT) schema. For more information, see <>. +Some systems require a special partition for installing the boot loader. The type and size of this partition depends on whether the disk you are installing the boot loader to uses the _Master Boot Record_ (MBR) or a _GUID Partition Table_ (GPT) schema. For more information, see xref:../install/Installing_Using_Anaconda.adoc#sect-installation-gui-storage-partitioning-bootloader[Boot Loader Installation]. ==== @@ -396,7 +396,7 @@ Create a Btrfs volume or subvolume. For a volume, the syntax is: ---- -One or more partitions can be specified in _partitions_. When specifying more than one partitions, the entries must be separated by a single space. See <> for a demonstration. +One or more partitions can be specified in _partitions_. When specifying more than one partitions, the entries must be separated by a single space. See xref:Kickstart_Syntax_Reference.adoc#exam-kickstart-create-btrfs[Creating Btrfs Volumes and Subvolumes] for a demonstration. For a subvolume, the syntax is: @@ -456,7 +456,7 @@ If the [command]#clearpart# command is used, then the [command]#part --onpart# c ==== -For a detailed example of partitioning including the [command]#clearpart# command, see <>. +For a detailed example of partitioning including the [command]#clearpart# command, see xref:Kickstart_Syntax_Reference.adoc#sect-kickstart-example-advanced-partitioning[Advanced Partitioning Example]. [option]#--all#:: Erases all partitions from the system. + @@ -611,7 +611,7 @@ To include a multipath device that uses LVM: [[sect-kickstart-commands-iscsi]] ===== iscsi (optional) - Configure iSCSI Devices -Specifies additional iSCSI storage to be attached during installation. If you use the [command]#iscsi# command, you must also assign a name to the iSCSI node, using the [command]#iscsiname# command (see <>. The [command]#iscsiname# command must appear before the [command]#iscsi# command in the Kickstart file. +Specifies additional iSCSI storage to be attached during installation. If you use the [command]#iscsi# command, you must also assign a name to the iSCSI node, using the [command]#iscsiname# command (see xref:Kickstart_Syntax_Reference.adoc#sect-kickstart-commands-iscsiname[iscsiname (optional) - Assign Name to iSCSI Device]. The [command]#iscsiname# command must appear before the [command]#iscsi# command in the Kickstart file. You should configure iSCSI storage in the system BIOS or firmware (iBFT for Intel systems) rather than use the [command]#iscsi# command if possible. If you do so, [application]*Anaconda* automatically detects and uses disks configured in BIOS or firmware and no special configuration is necessary in the Kickstart file. @@ -641,7 +641,7 @@ If you must use the [command]#iscsi# command, make sure that networking is activ [[sect-kickstart-commands-iscsiname]] ===== iscsiname (optional) - Assign Name to iSCSI Device -Assigns a name to an iSCSI node specified by the [command]#iscsi# command (<>). This command is mandatory if you use the [command]#iscsi# command, and it must be specified *before* you use [command]#iscsi#. +Assigns a name to an iSCSI node specified by the [command]#iscsi# command (xref:Kickstart_Syntax_Reference.adoc#sect-kickstart-commands-iscsi[iscsi (optional) - Configure iSCSI Devices]). This command is mandatory if you use the [command]#iscsi# command, and it must be specified *before* you use [command]#iscsi#. [subs="quotes, macros"] ---- @@ -667,7 +667,7 @@ This limitation only applies to newly created logical volume and volume group na ==== -For a detailed example of [command]#logvol# in action, see <>. +For a detailed example of [command]#logvol# in action, see xref:Kickstart_Syntax_Reference.adoc#sect-kickstart-example-advanced-partitioning[Advanced Partitioning Example]. _mntpoint_:: Replace with the volume's mount point. This name can take the following forms: + @@ -691,7 +691,7 @@ To determine the size of the swap partition automatically but also allow extra s + The size assigned will be equivalent to the swap space assigned by [option]#--recommended# plus the amount of RAM on your system. + -For the swap sizes assigned by these commands, see the section describing swap in <>. +For the swap sizes assigned by these commands, see the section describing swap in xref:../install/Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-recommended[Recommended Partitioning Scheme]. + `none`::: Used only when creating a thin pool volume. @@ -699,7 +699,7 @@ For the swap sizes assigned by these commands, see the section describing swap i [option]#--useexisting#:: Use an existing logical volume and format it. -[option]#--fstype=#:: Sets the file system type for the logical volume. Valid values are `xfs`, `ext2`, `ext3`, `ext4`, `swap`, and `vfat`. See <> for information about available file systems. +[option]#--fstype=#:: Sets the file system type for the logical volume. Valid values are `xfs`, `ext2`, `ext3`, `ext4`, `swap`, and `vfat`. See xref:../install/Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-filesystems[Device, File System and RAID Types] for information about available file systems. [option]#--fsoptions=#:: Specifies a free form string of options to be used when mounting the filesystem. This string will be copied into the `/etc/fstab` file of the installed system and should be enclosed in quotes. For example: + @@ -727,7 +727,7 @@ When creating a new logical volume, you must either specify its size statically [option]#--maxsize=#:: The maximum size in megabytes when the logical volume is set to grow. Specify an integer value here such as `500` (do not include the unit). -[option]#--recommended#:: Use this option when creating a `swap` logical volume to determine the size of this volume automatically, based on your system's hardware. For details about the recommended scheme, see <>. +[option]#--recommended#:: Use this option when creating a `swap` logical volume to determine the size of this volume automatically, based on your system's hardware. For details about the recommended scheme, see xref:../install/Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-recommended[Recommended Partitioning Scheme]. + [IMPORTANT] ==== @@ -773,7 +773,7 @@ The [option]#--cachepvs=#, [option]#--cachesize=#, and [option]#--cachemode=# op ==== -Create one or more partitions first using <>, create the logical volume group (<>), and then create logical volumes. For example: +Create one or more partitions first using xref:Kickstart_Syntax_Reference.adoc#sect-kickstart-commands-part[part (required) - Create Physical Partition], create the logical volume group (xref:Kickstart_Syntax_Reference.adoc#sect-kickstart-commands-volgroup[volgroup (optional) - Create LVM Volume Group]), and then create logical volumes. For example: [subs="quotes, macros"] ---- @@ -789,7 +789,7 @@ Create one or more partitions first using <>, crea Creates a partition on the system. -For a detailed example of [command]#part# in action, see <>. +For a detailed example of [command]#part# in action, see xref:Kickstart_Syntax_Reference.adoc#sect-kickstart-example-advanced-partitioning[Advanced Partitioning Example]. [subs="quotes, macros"] ---- @@ -836,22 +836,22 @@ To determine the size of the swap partition automatically but also allow extra s + The size assigned will be equivalent to the swap space assigned by [option]#--recommended# plus the amount of RAM on your system. + -For the swap sizes assigned by these commands, see the section describing swap in <>. +For the swap sizes assigned by these commands, see the section describing swap in xref:../install/Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-recommended[Recommended Partitioning Scheme]. + `raid._id_pass:attributes[{blank}]`::: The partition is used for software RAID (see [command]#raid#). + -`pv._id_pass:attributes[{blank}]`::: The partition is used for LVM (see <>). +`pv._id_pass:attributes[{blank}]`::: The partition is used for LVM (see xref:Kickstart_Syntax_Reference.adoc#sect-kickstart-commands-part[part (required) - Create Physical Partition]). + -`biosboot`::: The partition will be used for a BIOS Boot partition. A 1 MB BIOS boot partition is necessary on BIOS-based systems using a _GUID Partition Table_ (GPT); the boot loader will be installed into it. It is not necessary on UEFI systems. Also see <>. +`biosboot`::: The partition will be used for a BIOS Boot partition. A 1 MB BIOS boot partition is necessary on BIOS-based systems using a _GUID Partition Table_ (GPT); the boot loader will be installed into it. It is not necessary on UEFI systems. Also see xref:Kickstart_Syntax_Reference.adoc#sect-kickstart-commands-part[part (required) - Create Physical Partition]. + -`/boot/efi`::: An EFI System Partition. An EFI partition at least 50 MB in size is necessary on UEFI-based systems; the recommended size is 200 MB. It is not necessary on BIOS systems. Also see <>. +`/boot/efi`::: An EFI System Partition. An EFI partition at least 50 MB in size is necessary on UEFI-based systems; the recommended size is 200 MB. It is not necessary on BIOS systems. Also see xref:Kickstart_Syntax_Reference.adoc#sect-kickstart-commands-part[part (required) - Create Physical Partition]. [option]#--size=#:: The minimum partition size in megabytes. Specify an integer value here such as `500` (do not include the unit). + [IMPORTANT] ==== -If the [option]#--size# value is too small, the installation will fail. Set the [option]#--size# value as the minimum amount of space you require. For size recommendations, see <>. +If the [option]#--size# value is too small, the installation will fail. Set the [option]#--size# value as the minimum amount of space you require. For size recommendations, see xref:../install/Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-recommended[Recommended Partitioning Scheme]. ==== @@ -919,11 +919,11 @@ part --onpart=sd*|hd*|vda,/dev/vdc + The above will match either of `sd*`, `hd*`, *or* `vda` *and* `/dev/vdc`. Variants are processed from left to right, and at least one of them must match for the command to succeed. -[option]#--asprimary#:: Forces the partition to be allocated as a *primary* partition. If the partition cannot be allocated as primary (usually due to too many primary partitions being already allocated), the partitioning process will fail. This option only makes sense when the disk uses a Master Boot Record (MBR); for GUID Partition Table (GPT)-labeled disks this option has no meaning. For information about primary (and extended) partitions, see <>. +[option]#--asprimary#:: Forces the partition to be allocated as a *primary* partition. If the partition cannot be allocated as primary (usually due to too many primary partitions being already allocated), the partitioning process will fail. This option only makes sense when the disk uses a Master Boot Record (MBR); for GUID Partition Table (GPT)-labeled disks this option has no meaning. For information about primary (and extended) partitions, see xref:../install/Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-recommended[Recommended Partitioning Scheme]. [option]#--fsprofile=#:: Specifies a _usage type_ to be passed to the program that makes a filesystem on this partition. A usage type defines a variety of tuning parameters to be used when making a filesystem. For this option to work, the filesystem must support the concept of usage types and there must be a configuration file that lists valid types. For `ext2`, `ext3`, `ext4`, this configuration file is `/etc/mke2fs.conf`. -[option]#--fstype=#:: Sets the file system type for the partition. Valid values are `xfs`, `ext2`, `ext3`, `ext4`, `swap`, `vfat`, `efi` and `biosboot`. For information about supported file systems, see <>. +[option]#--fstype=#:: Sets the file system type for the partition. Valid values are `xfs`, `ext2`, `ext3`, `ext4`, `swap`, `vfat`, `efi` and `biosboot`. For information about supported file systems, see xref:../install/Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-filesystems[Device, File System and RAID Types]. [option]#--fsoptions=#:: Specifies a free form string of options to be used when mounting the filesystem. This string will be copied into the `/etc/fstab` file of the installed system and should be enclosed in quotes. For example: + @@ -936,7 +936,7 @@ The above will match either of `sd*`, `hd*`, *or* `vda` *and* `/dev/vdc`. Varian [option]#--label=#:: Assign a label to an individual partition. -[option]#--recommended#:: Determine the size of the partition automatically. For details about the recommended scheme, see <>. +[option]#--recommended#:: Determine the size of the partition automatically. For details about the recommended scheme, see xref:../install/Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-recommended[Recommended Partitioning Scheme]. + [IMPORTANT] ==== @@ -968,11 +968,11 @@ raid mntpoint --level=level --device=mddevice partitions* ---- -For a detailed example of [command]#raid# in action, see <>. +For a detailed example of [command]#raid# in action, see xref:Kickstart_Syntax_Reference.adoc#sect-kickstart-example-advanced-partitioning[Advanced Partitioning Example]. _mntpoint_:: Location where the RAID file system is mounted. If it is `/`, the RAID level must be 1 unless a boot partition (`/boot`) is present. If a boot partition is present, the `/boot` partition must be level 1 and the root (`/`) partition can be any of the available types. The _partitions*_ (which denotes that multiple partitions can be listed) lists the RAID identifiers to add to the RAID array. -[option]#--level=#:: RAID level to use (`0`, `1`, `4`, `5`, `6`, or `10`). See <> for information about various RAID types and their requirements. +[option]#--level=#:: RAID level to use (`0`, `1`, `4`, `5`, `6`, or `10`). See xref:../install/Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-filesystems[Device, File System and RAID Types] for information about various RAID types and their requirements. [option]#--device=#:: Name of the RAID device to use. As of {PRODUCT}{nbsp}{PRODVER}, RAID devices are no longer referred to by names like `md0`. If you have an old (v0.90 metadata) array that you cannot assign a name to, you can specify the array by a filesystem label or UUID (for example, [option]#--device=rhel7-root --label=rhel7-root#). @@ -980,7 +980,7 @@ _mntpoint_:: Location where the RAID file system is mounted. If it is `/`, the [option]#--fsprofile=#:: Specifies a _usage type_ to be passed to the program that makes a filesystem on this partition. A usage type defines a variety of tuning parameters to be used when making a filesystem. For this option to work, the filesystem must support the concept of usage types and there must be a configuration file that lists valid types. For `ext2`, `ext3`, `ext4`, this configuration file is `/etc/mke2fs.conf`. -[option]#--fstype=#:: Sets the file system type for the partition. Valid values are `xfs`, `ext2`, `ext3`, `ext4`, `swap`, `vfat`, `efi` and `biosboot`. For information about supported file systems, see <>. +[option]#--fstype=#:: Sets the file system type for the partition. Valid values are `xfs`, `ext2`, `ext3`, `ext4`, `swap`, `vfat`, `efi` and `biosboot`. For information about supported file systems, see xref:../install/Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-filesystems[Device, File System and RAID Types]. [option]#--fsoptions=#:: Specifies a free form string of options to be used when mounting the filesystem. This string will be copied into the `/etc/fstab` file of the installed system and should be enclosed in quotes. For example: + @@ -1072,7 +1072,7 @@ This limitation only applies to newly created logical volume and volume group na ==== -For a detailed partitioning example including [command]#volgroup#, see <>. +For a detailed partitioning example including [command]#volgroup#, see xref:Kickstart_Syntax_Reference.adoc#sect-kickstart-example-advanced-partitioning[Advanced Partitioning Example]. [option]#--noformat#:: Use an existing volume group and do not format it. @@ -1084,7 +1084,7 @@ For a detailed partitioning example including [command]#volgroup#, see <>, create the logical volume group (<>), and then create logical volumes. For example: +Create one or more partitions first using xref:Kickstart_Syntax_Reference.adoc#sect-kickstart-commands-part[part (required) - Create Physical Partition], create the logical volume group (xref:Kickstart_Syntax_Reference.adoc#sect-kickstart-commands-volgroup[volgroup (optional) - Create LVM Volume Group]), and then create logical volumes. For example: [subs="quotes, macros"] ---- @@ -1575,7 +1575,7 @@ The `libpwquality` library is used to check minimum password requirements (lengt [IMPORTANT] ==== -This command must be used inside the [command]#%anaconda# section. See <> for details. +This command must be used inside the [command]#%anaconda# section. See xref:Kickstart_Syntax_Reference.adoc#sect-kickstart-commands-anaconda[%anaconda (optional) - Additional Anaconda Configuration] for details. ==== @@ -1672,7 +1672,7 @@ Sets the state of SELinux on the installed system. The default policy is `enforc [[sect-kickstart-commands-sshkey]] ===== sshkey (optional) - Add an Authorized SSH Key -Use this command to add a specified `SSH` key to an user's `authorized_keys` file. The specified user must either be `root`, or it must be created in the Kickstart file - either automatically by an installed package, or using <>. +Use this command to add a specified `SSH` key to an user's `authorized_keys` file. The specified user must either be `root`, or it must be created in the Kickstart file - either automatically by an installed package, or using xref:Kickstart_Syntax_Reference.adoc#sect-kickstart-commands-user[user (optional) - Create User Account]. ---- sshkey --username=user "ssh_key" @@ -1696,7 +1696,7 @@ Creates a new user on the system. [option]#--gecos=#:: Provides the GECOS information for the user. This is a string of various system-specific fields separated by a comma. It is frequently used to specify the user's full name, office number, etc. See the `passwd(5)` man page for more details. -[option]#--groups=#:: In addition to the default group, a comma separated list of group names the user should belong to. The groups must exist before the user account is created. See <>. +[option]#--groups=#:: In addition to the default group, a comma separated list of group names the user should belong to. The groups must exist before the user account is created. See xref:Kickstart_Syntax_Reference.adoc#sect-kickstart-commands-group[group (optional) - Create User Group]. [option]#--homedir=#:: The home directory for the user. If not provided, this defaults to `/home/pass:attributes[{blank}]_username_pass:attributes[{blank}]`. @@ -1748,7 +1748,7 @@ Perform the installation in a completely non-interactive command line mode. Any [IMPORTANT] ==== -For a fully automatic installation, you must either specify one of the available modes ([command]#graphical#, [command]#text#, or [command]#cmdline#) in the Kickstart file, or you must use the [option]#console=# boot option as described in <>. Otherwise the system will halt and ask you to choose a mode. +For a fully automatic installation, you must either specify one of the available modes ([command]#graphical#, [command]#text#, or [command]#cmdline#) in the Kickstart file, or you must use the [option]#console=# boot option as described in xref:../advanced/Boot_Options.adoc#sect-boot-options-display[Console, Environment and Display Options]. Otherwise the system will halt and ask you to choose a mode. ==== @@ -1760,7 +1760,7 @@ Perform the installation in graphical mode. This is the default. This command ta [IMPORTANT] ==== -For a fully automatic installation, you must either specify one of the available modes ([command]#graphical#, [command]#text#, or [command]#cmdline#) in the Kickstart file, or you must use the [option]#console=# boot option as described in <>. Otherwise the system will halt and ask you to choose a mode. +For a fully automatic installation, you must either specify one of the available modes ([command]#graphical#, [command]#text#, or [command]#cmdline#) in the Kickstart file, or you must use the [option]#console=# boot option as described in xref:../advanced/Boot_Options.adoc#sect-boot-options-display[Console, Environment and Display Options]. Otherwise the system will halt and ask you to choose a mode. ==== @@ -1805,7 +1805,7 @@ During the installation, you can interact with the installation program and moni [IMPORTANT] ==== -By default, the `ssh` server is not started during the installation. To make `ssh` available during the installation, boot the system with the kernel boot option [option]#inst.sshd#. See <> for details. +By default, the `ssh` server is not started during the installation. To make `ssh` available during the installation, boot the system with the kernel boot option [option]#inst.sshd#. See xref:../advanced/Boot_Options.adoc#sect-boot-options-display[Console, Environment and Display Options] for details. ==== @@ -1844,7 +1844,7 @@ Perform the Kickstart installation in text mode. Kickstart installations are per [IMPORTANT] ==== -For a fully automatic installation, you must either specify one of the available modes ([command]#graphical#, [command]#text#, or [command]#cmdline#) in the Kickstart file, or you must use the [option]#console=# boot option as described in <>. Otherwise the system will halt and ask you to choose a mode. +For a fully automatic installation, you must either specify one of the available modes ([command]#graphical#, [command]#text#, or [command]#cmdline#) in the Kickstart file, or you must use the [option]#console=# boot option as described in xref:../advanced/Boot_Options.adoc#sect-boot-options-display[Console, Environment and Display Options]. Otherwise the system will halt and ask you to choose a mode. ==== @@ -1863,7 +1863,7 @@ Allows the graphical installation to be viewed remotely via VNC. This method is [command]#vnc [--host=pass:attributes[{blank}]_hostname_pass:attributes[{blank}]] [--port=pass:attributes[{blank}]_port_pass:attributes[{blank}]] [--password=pass:attributes[{blank}]_password_pass:attributes[{blank}]]# ---- -For more information about VNC installations, including instructions on how to connect to the installation system, see <>. +For more information about VNC installations, including instructions on how to connect to the installation system, see xref:../advanced/VNC_Installations.adoc#chap-vnc-installations[Installing Using VNC]. [option]#--host=#:: Connect to a VNC viewer listening on the given hostname. @@ -1884,7 +1884,7 @@ This command configures the [application]*kdump* kernel crash dumping mechanism. [NOTE] ==== -The syntax for this command is unusual because it is an add-on rather than a built-in Kickstart command. For more information about add-ons, see <>. +The syntax for this command is unusual because it is an add-on rather than a built-in Kickstart command. For more information about add-ons, see xref:Kickstart_Syntax_Reference.adoc#sect-kickstart-commands-addon[%addon (optional) - Include an Anaconda Add-on]. ==== @@ -1916,7 +1916,7 @@ If you enable [application]*Kdump* and do not specify the [option]#--reserve-mb= [[sect-kickstart-commands-firstboot]] ===== firstboot (optional) - Enable or Disable Initial Setup -Determine whether the [application]*Initial Setup* application starts the first time the system is booted. If enabled, the [package]*initial-setup* package must be installed. If not specified, this option is disabled by default. For more information about [application]*Initial Setup*, see <>. +Determine whether the [application]*Initial Setup* application starts the first time the system is booted. If enabled, the [package]*initial-setup* package must be installed. If not specified, this option is disabled by default. For more information about [application]*Initial Setup*, see xref:../install/After_Installation.adoc#sect-initial-setup[Initial Setup]. [subs="quotes, macros"] ---- @@ -1953,7 +1953,7 @@ For other completion methods, see the [command]#halt#, [command]#reboot#, and [c [[sect-kickstart-commands-reboot]] ===== reboot (optional) - Reboot After Installation -Reboot after the installation is successfully completed. If you are installing {PRODUCT} on IBM System{nbsp}z in command line mode (using <>), this command is necessary for a fully automated installation. +Reboot after the installation is successfully completed. If you are installing {PRODUCT} on IBM System{nbsp}z in command line mode (using xref:Kickstart_Syntax_Reference.adoc#sect-kickstart-commands-cmdline[cmdline (optional) - Perform Installation in Command Line Mode]), this command is necessary for a fully automated installation. For other completion methods, see the [command]#halt#, [command]#poweroff#, and [command]#shutdown# Kickstart options. @@ -1994,7 +1994,7 @@ For more information about [application]*Anaconda* add-ons, see the link:++https [[sect-kickstart-commands-anaconda]] ==== %anaconda (optional) - Additional Anaconda Configuration -This section, introduced in {PRODUCT} 22, is used to specify additional configuration options for the installer. Commands inside this section only control the behavior during installation, not on the installed system. The only command currently available inside this section is <>. The [command]#%anaconda# section must end with `%end`. +This section, introduced in {PRODUCT} 22, is used to specify additional configuration options for the installer. Commands inside this section only control the behavior during installation, not on the installed system. The only command currently available inside this section is xref:Kickstart_Syntax_Reference.adoc#sect-kickstart-commands-pwpolicy[pwpolicy (optional) - Change the Default Password Policy]. The [command]#%anaconda# section must end with `%end`. In interactive installations (using the graphical or text interface), the `/usr/share/anaconda/interactive-defaults.ks` file contains the default [command]#%anaconda# section. To change the defaults, you must create a `product.img` file with a Kickstart file replacing the default one, and pass this file to [application]*Anaconda* using a boot option. @@ -2008,7 +2008,7 @@ Use the [command]#%include _/path/to/file_pass:attributes[{blank}]# command to i [[sect-kickstart-commands-ksappend]] ==== %ksappend (optional) - Append Contents of Another File -The [command]#%ksappend _url_pass:attributes[{blank}]# directive is very similar to <> in that it is used to include the contents of additional files as though they were at the location of the [command]#%ksappend# command. The difference is in when the two directives are processed. +The [command]#%ksappend _url_pass:attributes[{blank}]# directive is very similar to xref:Kickstart_Syntax_Reference.adoc#sect-kickstart-commands-include[%include (optional) - Include Contents of Another File] in that it is used to include the contents of additional files as though they were at the location of the [command]#%ksappend# command. The difference is in when the two directives are processed. [command]#%ksappend# is processed in an initial pass, before any other part of the Kickstart file. Then, this expanded Kickstart file is passed to the rest of [application]*Anaconda* where all [command]#%pre# scripts are handled, and then finally the rest of the Kickstart file is processed in order, which includes [command]#%include# directives. @@ -2035,7 +2035,7 @@ To install a 32-bit package on a 64-bit system, you will need to append the pack [IMPORTANT] ==== -[application]*Initial Setup* does not run after a system is installed from a Kickstart file unless a desktop environment and the [application]*X Window System* were included in the installation and graphical login was enabled. This means that by default, no users except for `root` will be created. You can either create a user with the [option]#user# option in the Kickstart file before installing additional systems from it (see <> for details) or log into the installed system with a virtual console as `root` and add users with the [command]#useradd# command. +[application]*Initial Setup* does not run after a system is installed from a Kickstart file unless a desktop environment and the [application]*X Window System* were included in the installation and graphical login was enabled. This means that by default, no users except for `root` will be created. You can either create a user with the [option]#user# option in the Kickstart file before installing additional systems from it (see xref:Kickstart_Syntax_Reference.adoc#sect-kickstart-commands-user[user (optional) - Create User Account] for details) or log into the installed system with a virtual console as `root` and add users with the [command]#useradd# command. ==== @@ -2184,7 +2184,7 @@ The following options can be used to change the behavior of pre-installation scr [command]#%pre --log=/mnt/sysimage/root/ks-pre.log# ---- -For an example of a pre-installation script, see <>. +For an example of a pre-installation script, see xref:Kickstart_Syntax_Reference.adoc#sect-kickstart-example-pre-script[Example Pre-installation Script]. [[sect-kickstart-postinstall]] ==== %post (optional) - Post-installation Script @@ -2249,7 +2249,7 @@ with [option]#--nochroot#: [command]#%post --nochroot --log=/mnt/sysimage/root/ks-post.log# ---- -For an example of a post-installation script, see <>. +For an example of a post-installation script, see xref:Kickstart_Syntax_Reference.adoc#sect-kickstart-example-post-script[Example Post-installation Script]. [[sect-kickstart-examples]] ==== Example Kickstart Configurations diff --git a/en-US/appendixes/Understanding_LVM.adoc b/en-US/appendixes/Understanding_LVM.adoc index c9fb1dc..4a82193 100644 --- a/en-US/appendixes/Understanding_LVM.adoc +++ b/en-US/appendixes/Understanding_LVM.adoc @@ -11,7 +11,7 @@ LVM (Logical Volume Management) partitions provide a number of advantages over s The boot loader cannot read LVM volumes. You must make a standard, non-LVM disk partition for your `/boot` partition. -By default, the installation process always creates the `/` and `swap` partitions within LVM volumes, with a separate `/boot` on a standard partition. See <> for details. +By default, the installation process always creates the `/` and `swap` partitions within LVM volumes, with a separate `/boot` on a standard partition. See xref:../install/Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-recommended[Recommended Partitioning Scheme] for details. ==== diff --git a/en-US/install/After_Installation.adoc b/en-US/install/After_Installation.adoc index 79b1486..d079550 100644 --- a/en-US/install/After_Installation.adoc +++ b/en-US/install/After_Installation.adoc @@ -31,9 +31,9 @@ After you finish configuring all screens, click `Start using Fedora` to exit the After you finish the installation and go through one of the initial setup utilities described above, your system is ready for use. However, other administrative tasks not covered by the installer or the initial setup utilities may still be necessary, depending on how you plan to use your system. The list below describes some of the more common tasks usually performed immediately after a new installation. -Recover a lost `root` password:: The `root` password, which is configured during the installation, is required for accessing the system as the `root` user. Without this password you will not be able to configure your system or install additional software. If you lost or forgot your `root` password, you can reset it by following the steps described in <>. +Recover a lost `root` password:: The `root` password, which is configured during the installation, is required for accessing the system as the `root` user. Without this password you will not be able to configure your system or install additional software. If you lost or forgot your `root` password, you can reset it by following the steps described in xref:Troubleshooting.adoc#sect-trouble-after-reset-root-password[Resetting the Root Password]. -Configure the network:: In most cases, network access is configured during the installation process, either in the [application]*Anaconda* installation program (see <>) or in a Kickstart file (see <>). For information on configuring the network after the installation, see the [citetitle]_{PRODUCT} Networking Guide_, available at link:++http://docs.fedoraproject.org/++[]. +Configure the network:: In most cases, network access is configured during the installation process, either in the [application]*Anaconda* installation program (see xref:Installing_Using_Anaconda.adoc#sect-installation-gui-network-configuration[Network & Hostname]) or in a Kickstart file (see xref:../appendixes/Kickstart_Syntax_Reference.adoc#sect-kickstart-commands-network[network (optional) - Configure Network Interfaces]). For information on configuring the network after the installation, see the [citetitle]_{PRODUCT} Networking Guide_, available at link:++http://docs.fedoraproject.org/++[]. Perform an initial system update:: If you installed {PRODUCT} from a full installation ISO image (such as the Workstation live image or full Server DVD), it is recommended to perform an initial system update, because your installation media likely contained older versions of software packages. During the initial update, all installed packages are updated to their latest available versions. Updates to packages provide security fixes, bug fixes and enhancements. + @@ -47,8 +47,8 @@ Configure additional repositories:: New software is installed from _package rep + For information about configuring additional software repositories, see the [citetitle]_{PRODUCT} System Administrator's Guide_, available at link:++http://docs.fedoraproject.org/++[]. -Install additional packages:: You can control which packages will be installed by selecting an environment in the `Software Selection` dialog in the graphical installation (see <>). This dialog does not provide a way to choose individual packages, only predefined sets. However, you can use the [application]*DNF* package manager to install additional packages after the installation. See the [citetitle]_{PRODUCT} System Administrator's Guide_, available at link:++http://docs.fedoraproject.org/++[], for more information. +Install additional packages:: You can control which packages will be installed by selecting an environment in the `Software Selection` dialog in the graphical installation (see xref:Installing_Using_Anaconda.adoc#sect-installation-gui-software-selection[Software Selection]). This dialog does not provide a way to choose individual packages, only predefined sets. However, you can use the [application]*DNF* package manager to install additional packages after the installation. See the [citetitle]_{PRODUCT} System Administrator's Guide_, available at link:++http://docs.fedoraproject.org/++[], for more information. Switch to a graphical login:: Depending on the options you chose during the installation process, it is possible that your system does not have a graphical interface, instead offering only a text-based prompt. If this is the case and you wish to enable a graphical desktop after the installation, you must install the [application]*X Window System* and your preferred desktop environment (either [application]*GNOME* or [application]*KDE*). + -As with all other software, these packages can be installed using the [application]*DNF* package manager. For information about using [application]*DNF* to install new packages, see the [citetitle]_{PRODUCT} System Administrator's Guide_, available at link:++http://docs.fedoraproject.org/++[]. For information on how to enable graphical login by default, see <>. \ No newline at end of file +As with all other software, these packages can be installed using the [application]*DNF* package manager. For information about using [application]*DNF* to install new packages, see the [citetitle]_{PRODUCT} System Administrator's Guide_, available at link:++http://docs.fedoraproject.org/++[]. For information on how to enable graphical login by default, see xref:Troubleshooting.adoc#sect-trouble-after-graphical-login[Booting into a Graphical Environment]. \ No newline at end of file diff --git a/en-US/install/Booting_the_Installation.adoc b/en-US/install/Booting_the_Installation.adoc index 2684182..7f75820 100644 --- a/en-US/install/Booting_the_Installation.adoc +++ b/en-US/install/Booting_the_Installation.adoc @@ -10,7 +10,7 @@ This chapter will explain how to boot the installer from local media or a networ [[sect-preparing-boot]] ==== Preparing to Boot -After you have made a bootable USB flash drive or a CD or DVD using the steps described in <>, you are ready to boot the installation. Note that the steps described below are generic and the exact steps will vary somewhat depending on your system - particularly on your motherboard manufacturer. +After you have made a bootable USB flash drive or a CD or DVD using the steps described in xref:Preparing_for_Installation.adoc#sect-preparing-boot-media[Preparing Boot Media], you are ready to boot the installation. Note that the steps described below are generic and the exact steps will vary somewhat depending on your system - particularly on your motherboard manufacturer. [WARNING] ==== @@ -83,4 +83,4 @@ When editing the default set of options, you can change the existing ones as wel image::boot/boot-menu.png[The boot menu.] -All available [application]*Anaconda* boot options are described in <>. \ No newline at end of file +All available [application]*Anaconda* boot options are described in xref:../advanced/Boot_Options.adoc#sect-boot-options-available[Available Boot Options]. \ No newline at end of file diff --git a/en-US/install/CustomSpoke.adoc b/en-US/install/CustomSpoke.adoc index 8ac1460..eaf86ee 100644 --- a/en-US/install/CustomSpoke.adoc +++ b/en-US/install/CustomSpoke.adoc @@ -13,7 +13,7 @@ In most other installers for both Linux and other operating systems, disk partit [NOTE] ==== -No permanent changes will be made to your disks during the actual partitioning process. The configuration you have selected will only be written to your system after you press the `Begin installation` button in <>. +No permanent changes will be made to your disks during the actual partitioning process. The configuration you have selected will only be written to your system after you press the `Begin installation` button in xref:Installing_Using_Anaconda.adoc#sect-installation-gui-installation-summary[Installation Summary]. ==== @@ -21,9 +21,9 @@ No permanent changes will be made to your disks during the actual partitioning p image::anaconda/CustomSpoke.png[The Manual Partitioning screen. At this point, no partitioning has been configured. The left column shows an option to automatically create a pre-defined layout. An existing Linux system has been detected also and is displayed below the automatic configuration selection. The right side of the screen shows available options for the currently selected mount point.] -When you first open the `Manual Partitioning` screen, the column on the left side will display all previously existing partitions on all drives which you selected as installation targers in <>. If none of the selected drives contain any existing partitions, then a message informing you that no mount points currently exist will appear. +When you first open the `Manual Partitioning` screen, the column on the left side will display all previously existing partitions on all drives which you selected as installation targers in xref:Installing_Using_Anaconda.adoc#sect-installation-gui-storage-partitioning[Installation Destination]. If none of the selected drives contain any existing partitions, then a message informing you that no mount points currently exist will appear. -Here, you can choose a partitioning scheme such as `LVM` or `BTRFS` and click the `Click here to create them automatically` to prompt the installer to create a basic partitioning layout; this layout follows the guidelines described in <>. The created layout is a basic layout where partition/volume sizes are determined automatically based on the total amount of available space. +Here, you can choose a partitioning scheme such as `LVM` or `BTRFS` and click the `Click here to create them automatically` to prompt the installer to create a basic partitioning layout; this layout follows the guidelines described in xref:Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-recommended[Recommended Partitioning Scheme]. The created layout is a basic layout where partition/volume sizes are determined automatically based on the total amount of available space. Click the `+` button to add a mount point. In the dialog window that opens, choose a mount point such as `/` or `/home`, and the desired capacity for the mount point (such as `10GB` or `500MB`). Note that specifying the mount point is mandatory, but you do not have to specify the capacity at this point; this is useful when adding a mount point which you want to make larger than the current available space permits. Then, click `Add mount point` to add it to the list using the default settings, which means it will be created as a logical volume, and a new volume group will be created for it unless one already exists. @@ -32,21 +32,21 @@ Then, select the newly created mount point in the list on the left side. A set o [NOTE] ==== -For a description of available device and file system types, see <>. +For a description of available device and file system types, see xref:Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-filesystems[Device, File System and RAID Types]. ==== To remove a mount point, select it in the list and press the `-` button below. -The exact steps for configuring your storage depend on your specific needs and your system configuration. Procedures for creating specific layouts are described further in this chapter. Before you start, you should also review <> and <> for a list of requirements and tips for partitioning your disks for {PRODUCT}. +The exact steps for configuring your storage depend on your specific needs and your system configuration. Procedures for creating specific layouts are described further in this chapter. Before you start, you should also review xref:Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-recommended[Recommended Partitioning Scheme] and xref:Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-advice[Advice on Partitions] for a list of requirements and tips for partitioning your disks for {PRODUCT}. Below the list of existing mount points are two fields, showing you how much free space is left on your storage devices and how much total space they have. -Click the `pass:attributes[{blank}]_X_ storage devices selected` to view a summary of currently selected storage devices; this may help you with orientation in more complicated storage schemas. Devices displayed here are the ones you have selected in <>. If you want to add or remove any storage devices from your configuration, return to that screen and change your selection. +Click the `pass:attributes[{blank}]_X_ storage devices selected` to view a summary of currently selected storage devices; this may help you with orientation in more complicated storage schemas. Devices displayed here are the ones you have selected in xref:Installing_Using_Anaconda.adoc#sect-installation-gui-storage-partitioning[Installation Destination]. If you want to add or remove any storage devices from your configuration, return to that screen and change your selection. You can press the `Reset All` button in the bottom right corner at any time to reset the storage configuration to the state it was in when you last opened the `Manual Partitioning` screen. This means that if you modify the storage configuration, leave the screen, and then come back, the Reset button will reset the configuration back to the already modified state, discarding only the changes you have made recently, not all changes to the storage configuration since you booted the installer. -To discard all changes, and to also detect any new drives which have not been detected when the installer started (usually when you attached a new drive after you started), press the button marked by a circular arrow in the set of controls below the list of mount points on the left side of the screen. In the dialog window that opens, press `Rescan Disks` and wait until the scanning process completes. Then, press `OK` to return to <>; all detected disks including any new ones will be displayed in the `Local Standard Disks` section. +To discard all changes, and to also detect any new drives which have not been detected when the installer started (usually when you attached a new drive after you started), press the button marked by a circular arrow in the set of controls below the list of mount points on the left side of the screen. In the dialog window that opens, press `Rescan Disks` and wait until the scanning process completes. Then, press `OK` to return to xref:Installing_Using_Anaconda.adoc#sect-installation-gui-storage-partitioning[Installation Destination]; all detected disks including any new ones will be displayed in the `Local Standard Disks` section. .Rescan Disks @@ -56,7 +56,7 @@ After you finish configuring your system storage, press `Done` in the top left c If such a message is displayed, go back and fix any issues found by the installer; otherwise you will not be able to proceed with the installation. You can also press `Done` again to return to the `Installation Summary` anyway, but a storage configuration error will prevent you from starting the actual installation process. -If no error message is displayed and if you made any changes since the last time you have visited this screen, a summary dialog will appear, displaying a detailed list of the changes you made. Review the list and click `Accept Changes` to proceed with <>, or click `Cancel & Return to Custom Partitioning` if you want to make any more changes. +If no error message is displayed and if you made any changes since the last time you have visited this screen, a summary dialog will appear, displaying a detailed list of the changes you made. Review the list and click `Accept Changes` to proceed with xref:Installing_Using_Anaconda.adoc#sect-installation-gui-installation-summary[Installation Summary], or click `Cancel & Return to Custom Partitioning` if you want to make any more changes. include::CustomSpoke_AddPhysical.adoc[] diff --git a/en-US/install/CustomSpoke_AddBtrfs.adoc b/en-US/install/CustomSpoke_AddBtrfs.adoc index 0d49a92..4100ba7 100644 --- a/en-US/install/CustomSpoke_AddBtrfs.adoc +++ b/en-US/install/CustomSpoke_AddBtrfs.adoc @@ -6,12 +6,12 @@ _Btrfs_ is a type of file system, but it has several features characteristic of a storage device. It is designed to make the file system tolerant of errors, and to facilitate the detection and repair of errors when they occur. It uses checksums to ensure the validity of data and metadata, and maintains snapshots of the file system that can be used for backup or repair. -Creating a Btrfs layout is somewhat similar to LVM (described in <>) with slightly different terminology. A Btrfs _volume_ is the equivalent of an LVM volume group, and a Btrfs _subvolume_ is similar to a LVM logical volume. An important difference to note is how [application]*Anaconda* reports sizes for separate mount points: For LVM, the exact size of each logical volume is shown next to each mount point in the left pane, while with Btrfs, the total size of the entire volume is shown next to each subvolume. +Creating a Btrfs layout is somewhat similar to LVM (described in xref:Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-lvm[Creating a Logical Volume Managament (LVM) Layout]) with slightly different terminology. A Btrfs _volume_ is the equivalent of an LVM volume group, and a Btrfs _subvolume_ is similar to a LVM logical volume. An important difference to note is how [application]*Anaconda* reports sizes for separate mount points: For LVM, the exact size of each logical volume is shown next to each mount point in the left pane, while with Btrfs, the total size of the entire volume is shown next to each subvolume. [WARNING] ==== -Some partition types - notably the `/boot` and `/usr` directories and the BIOS Boot and EFI partitions - can not be placed on Btrfs subvolumes. Use standard physical volumes for them (or an LVM logical volume for `/usr`). See <> for more information. +Some partition types - notably the `/boot` and `/usr` directories and the BIOS Boot and EFI partitions - can not be placed on Btrfs subvolumes. Use standard physical volumes for them (or an LVM logical volume for `/usr`). See xref:Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-recommended[Recommended Partitioning Scheme] for more information. ==== @@ -37,7 +37,7 @@ When creating a mount point for swap on Btrfs, specify the mount point as `swap` . In the `Volume` menu, you can see that the subvolume has been assigned to an automatically created volume, which is named after the {PRODUCT} variant you are installing (for example, `fedora-server00`. Click the `Modify` button under the drop-down menu to access the volume settings. -. In the `Configure Volume` dialog, you can change the volume's name, its `RAID level` (see <> for information about available RAID types), and you can also specify which physical devices (disks) this volume should reside on. You can select one or more disks which will be used to hold this volume by holding down kbd:[Ctrl] and clicking each disk in the list. +. In the `Configure Volume` dialog, you can change the volume's name, its `RAID level` (see xref:Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-filesystems[Device, File System and RAID Types] for information about available RAID types), and you can also specify which physical devices (disks) this volume should reside on. You can select one or more disks which will be used to hold this volume by holding down kbd:[Ctrl] and clicking each disk in the list. + [NOTE] ==== diff --git a/en-US/install/CustomSpoke_AddLVM.adoc b/en-US/install/CustomSpoke_AddLVM.adoc index 4ac86bb..97ef3ee 100644 --- a/en-US/install/CustomSpoke_AddLVM.adoc +++ b/en-US/install/CustomSpoke_AddLVM.adoc @@ -6,12 +6,12 @@ _Logical Volume Management_ (LVM) presents a simple logical view of underlying physical storage space, such as hard drives or LUNs. Partitions on physical storage are represented as _physical volumes_ that can be grouped together into _volume groups_. Each volume group can be divided into multiple _logical volumes_, each of which is analogous to a standard disk partition. Therefore, LVM logical volumes function as partitions which can span multiple physical disks. -See <> for additional information about the concepts behind Logical Volume Management. +See xref:../appendixes/Understanding_LVM.adoc#appe-lvm-overview[Understanding LVM] for additional information about the concepts behind Logical Volume Management. [WARNING] ==== -Some partition types - notably the `/boot` directory and the BIOS Boot and EFI partitions - can not be placed on logical volumes. Use standard physical volumes for them. See <> for more information. +Some partition types - notably the `/boot` directory and the BIOS Boot and EFI partitions - can not be placed on logical volumes. Use standard physical volumes for them. See xref:Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-recommended[Recommended Partitioning Scheme] for more information. ==== @@ -37,7 +37,7 @@ When creating a mount point for swap on LVM, specify the mount point as `swap`. . In the `Volume Group` menu, you can see that the volume has been assigned to an automatically created volume group, which is named after the {PRODUCT} variant you are installing (for example, `fedora-server`. Click the `Modify` button under the drop-down menu to access the volume group settings. -. In the `Configure Volume Group` dialog, you can change the volume group's name, its `RAID level` (see <> for information about available RAID types), and you can also specify which physical devices (disks) this volume group should reside on. You can select one or more disks which will be used to hold this volume group by holding down kbd:[Ctrl] and clicking each disk in the list. +. In the `Configure Volume Group` dialog, you can change the volume group's name, its `RAID level` (see xref:Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-filesystems[Device, File System and RAID Types] for information about available RAID types), and you can also specify which physical devices (disks) this volume group should reside on. You can select one or more disks which will be used to hold this volume group by holding down kbd:[Ctrl] and clicking each disk in the list. + [NOTE] ==== diff --git a/en-US/install/CustomSpoke_AddPhysical.adoc b/en-US/install/CustomSpoke_AddPhysical.adoc index 5b5b80e..5468d5d 100644 --- a/en-US/install/CustomSpoke_AddPhysical.adoc +++ b/en-US/install/CustomSpoke_AddPhysical.adoc @@ -6,7 +6,7 @@ _Standard partitions_ are the most common type of partition, with the widest support across operating systems. For example, Microsoft Windows uses exclusively physical partitions and can not natively work with LVM or Btrfs. Most {PRODUCT} partitioning setups will also require at least one standard partition for the `/boot` directory, and possibly also another standard partition with the BIOS Boot or EFI System file system to store the boot loader. -See <> for additional information about the concepts behind physical partitions. +See xref:../appendixes/Disk_Partitions.adoc#appe-disk-partitions-overview[An Introduction to Disk Partitions] for additional information about the concepts behind physical partitions. .Create Standard Partition @@ -24,7 +24,7 @@ Follow the procedure below to create mount points on standard physical partition When creating a swap partition, specify the mount point as `swap`. For a BIOS Boot partition, use `biosboot`. For an EFI System Partition, use `/boot/efi`. -For information about these partition types, see <>. +For information about these partition types, see xref:Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-recommended[Recommended Partitioning Scheme]. ==== diff --git a/en-US/install/CustomSpoke_FileSystems.adoc b/en-US/install/CustomSpoke_FileSystems.adoc index 6f605d3..01e3977 100644 --- a/en-US/install/CustomSpoke_FileSystems.adoc +++ b/en-US/install/CustomSpoke_FileSystems.adoc @@ -6,21 +6,21 @@ {PRODUCT} supports multiple types of devices and file systems. The lists below offer a short description of each available device, file system and RAID type and notes on their usage. -To select a device type or a file system of a partition or a logical volume, select it in the list in <> and select a `Device Type` and a `File System` from their respective drop-down menus on the right side of the screen. Then, click `Update Settings` and repeat this process for all mount points you want to modify. +To select a device type or a file system of a partition or a logical volume, select it in the list in xref:Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning[Manual Partitioning] and select a `Device Type` and a `File System` from their respective drop-down menus on the right side of the screen. Then, click `Update Settings` and repeat this process for all mount points you want to modify. -To configure software RAID, make sure that you have enough physical hard drives selected as installation targets (the number of separate drives required for each type of RAID is noted in its description). Then, choose a RAID level when creating or modifying a Btrfs volume or LVM volume group, or select `Software RAID` as the device type to create software RAID with standard partitions. For detailed instructions, see <>, <>, and <> as needed. +To configure software RAID, make sure that you have enough physical hard drives selected as installation targets (the number of separate drives required for each type of RAID is noted in its description). Then, choose a RAID level when creating or modifying a Btrfs volume or LVM volume group, or select `Software RAID` as the device type to create software RAID with standard partitions. For detailed instructions, see xref:Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-btrfs[Creating a Btrfs Layout], xref:Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-lvm[Creating a Logical Volume Managament (LVM) Layout], and xref:Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-swraid[Creating Software RAID] as needed. .Device Types -* `Standard Partition` - A standard partition can contain a file system or swap space. Standard partitions are most commonly used for `/boot` and the BIOS Boot and EFI System partitions. LVM logical volumes or Btrfs subvolumes are recommended for most other uses. See <> for additional information about the concepts behind physical partitions. +* `Standard Partition` - A standard partition can contain a file system or swap space. Standard partitions are most commonly used for `/boot` and the BIOS Boot and EFI System partitions. LVM logical volumes or Btrfs subvolumes are recommended for most other uses. See xref:../appendixes/Disk_Partitions.adoc#appe-disk-partitions-overview[An Introduction to Disk Partitions] for additional information about the concepts behind physical partitions. -* `LVM` - Choosing `LVM` as the `Device Type` creates an LVM logical volume and a volume group to contain it (unless one already exists, in which case the new volume is assigned to the existing group). LVM can improve performance when using physical disks and allows you to use multiple disks for a single mount point. For information on how to create a logical volume, see <>. Also see <> for some additional information about LVM in general. +* `LVM` - Choosing `LVM` as the `Device Type` creates an LVM logical volume and a volume group to contain it (unless one already exists, in which case the new volume is assigned to the existing group). LVM can improve performance when using physical disks and allows you to use multiple disks for a single mount point. For information on how to create a logical volume, see xref:Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-lvm[Creating a Logical Volume Managament (LVM) Layout]. Also see xref:../appendixes/Understanding_LVM.adoc#appe-lvm-overview[Understanding LVM] for some additional information about LVM in general. * `LVM Thin Provisioning` - Using thin provisioning, you can manage a storage pool of free space, known as a _thin pool_, which can be allocated to an arbitrary number of devices when needed by applications. The thin pool can be expanded dynamically when needed for cost-effective allocation of storage space. -* `RAID` - Creating two or more software RAID partitions allows you to create a software RAID device. One RAID partition is assigned to each disk on the system. See <> for instructions on creating software RAID. +* `RAID` - Creating two or more software RAID partitions allows you to create a software RAID device. One RAID partition is assigned to each disk on the system. See xref:Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-swraid[Creating Software RAID] for instructions on creating software RAID. -* `BTRFS` - Btrfs is a file system with several device-like features. It is capable of addressing and managing more files, larger files, and larger volumes than the ext2, ext3, and ext4 file systems. See <> for more information about creating Btrfs volumes. +* `BTRFS` - Btrfs is a file system with several device-like features. It is capable of addressing and managing more files, larger files, and larger volumes than the ext2, ext3, and ext4 file systems. See xref:Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-btrfs[Creating a Btrfs Layout] for more information about creating Btrfs volumes. .File Systems @@ -30,7 +30,7 @@ To configure software RAID, make sure that you have enough physical hard drives * `ext2` - An ext2 file system supports standard Unix file types, including regular files, directories, or symbolic links. It provides the ability to assign long file names, up to 255 characters. -* `swap` - Swap partitions are used to support virtual memory. In other words, data is written to a swap partition when there is not enough RAM to store the data your system is processing. A swap partition should always be created; see <> for details such as the recommended size. +* `swap` - Swap partitions are used to support virtual memory. In other words, data is written to a swap partition when there is not enough RAM to store the data your system is processing. A swap partition should always be created; see xref:Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-recommended[Recommended Partitioning Scheme] for details such as the recommended size. * `xfs` - XFS is a highly scalable, high-performance file system that supports file systems up to 16 exabytes (approximately 16 million terabytes), files up to 8 exabytes (approximately 8 million terabytes), and directory structures containing tens of millions of entries. XFS also supports metadata journaling, which facilitates quicker crash recovery. The maximum supported size of a single XFS file system is 500 TB. Starting with {PRODUCT}{nbsp}22, XFS is the default and recommended file system on {PRODUCT} Server. + @@ -43,9 +43,9 @@ Note that the size of an XFS file system can not currently be reduced without de * `vfat` - The VFAT file system is a Linux file system that is compatible with Microsoft Windows long file names on the FAT file system. -* `BIOS Boot` - A very small partition required for booting from a device with a GUID partition table (GPT) on BIOS systems and UEFI systems in BIOS compatibility mode. See <> for details. +* `BIOS Boot` - A very small partition required for booting from a device with a GUID partition table (GPT) on BIOS systems and UEFI systems in BIOS compatibility mode. See xref:Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-recommended[Recommended Partitioning Scheme] for details. -* `EFI System Partition` - A small partition required for booting a device with a GUID partition table (GPT) on a UEFI system. See <> for details. +* `EFI System Partition` - A small partition required for booting a device with a GUID partition table (GPT) on a UEFI system. See xref:Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-recommended[Recommended Partitioning Scheme] for details. .Software RAID Types diff --git a/en-US/install/CustomSpoke_PartitioningAdvice.adoc b/en-US/install/CustomSpoke_PartitioningAdvice.adoc index 4e425df..9e152eb 100644 --- a/en-US/install/CustomSpoke_PartitioningAdvice.adoc +++ b/en-US/install/CustomSpoke_PartitioningAdvice.adoc @@ -32,6 +32,6 @@ This limitation only applies to `/usr` or `/var`, not to directories below them. * Use Logical Volume Management (LVM) if you anticipate expanding your storage by adding more hard drives after the installation. With LVM, you can create physical volumes on the new drives, and then assign them to any volume group and logical volume as you see fit - for example, you can easily expand your system's `/home` (or any other directory residing on a logical volume). -* Creating a BIOS Boot partition or an EFI System Partition may be necessary, depending on your system's firmware, boot drive size, and boot drive disk label. See <> for information about these partitions. Note that the graphical installer will not let you create a BIOS Boot or EFI System Partition if your system does *not* require one - in that case, they will be hidden from the menu. +* Creating a BIOS Boot partition or an EFI System Partition may be necessary, depending on your system's firmware, boot drive size, and boot drive disk label. See xref:Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-recommended[Recommended Partitioning Scheme] for information about these partitions. Note that the graphical installer will not let you create a BIOS Boot or EFI System Partition if your system does *not* require one - in that case, they will be hidden from the menu. * If you need to make any changes to your storage configuration after the installation, {PRODUCT} repositories offer several different tools which can help you do this. If you prefer a command line tool, try [package]*system-storage-manager*. diff --git a/en-US/install/CustomSpoke_RecommendedScheme.adoc b/en-US/install/CustomSpoke_RecommendedScheme.adoc index 4b836ce..c3b1af1 100644 --- a/en-US/install/CustomSpoke_RecommendedScheme.adoc +++ b/en-US/install/CustomSpoke_RecommendedScheme.adoc @@ -64,7 +64,7 @@ Systems with BIOS firmware and UEFI systems in BIOS compatibility mode::: If th [NOTE] ==== -You can force the installer to use GPT on disks smaller than 2 TB by using the [option]#inst.gpt# boot option as described in <>. However, the opposite is not possible - you can not use MBR on disks larger than 2 TB. +You can force the installer to use GPT on disks smaller than 2 TB by using the [option]#inst.gpt# boot option as described in xref:../advanced/Boot_Options.adoc#chap-anaconda-boot-options[Boot Options]. However, the opposite is not possible - you can not use MBR on disks larger than 2 TB. ==== + @@ -83,7 +83,7 @@ Also note that if your system does not require any of these partitions, they wil ==== -Many systems have more partitions than the minimum listed above. Choose partitions based on your particular needs. See <> for additional information and advice. +Many systems have more partitions than the minimum listed above. Choose partitions based on your particular needs. See xref:Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-advice[Advice on Partitions] for additional information and advice. [NOTE] ==== @@ -92,4 +92,4 @@ Only assign storage capacity to those partitions you require immediately. You ma ==== -If you are not sure how best to configure the partitions for your computer, accept the automatic default partition layout provided by the installation program as described in <>. +If you are not sure how best to configure the partitions for your computer, accept the automatic default partition layout provided by the installation program as described in xref:Installing_Using_Anaconda.adoc#sect-installation-gui-storage-partitioning[Installation Destination]. diff --git a/en-US/install/CustomSpoke_SoftwareRAID.adoc b/en-US/install/CustomSpoke_SoftwareRAID.adoc index a43a587..a2aa3bd 100644 --- a/en-US/install/CustomSpoke_SoftwareRAID.adoc +++ b/en-US/install/CustomSpoke_SoftwareRAID.adoc @@ -4,14 +4,14 @@ [[sect-installation-gui-manual-partitioning-swraid]] ====== Creating Software RAID -_Redundant arrays of independent disks_ (RAIDs) are constructed from multiple storage devices that are arranged to provide increased performance and, in some configurations, greater fault tolerance. See <> a description of different kinds of RAIDs. +_Redundant arrays of independent disks_ (RAIDs) are constructed from multiple storage devices that are arranged to provide increased performance and, in some configurations, greater fault tolerance. See xref:Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-filesystems[Device, File System and RAID Types] a description of different kinds of RAIDs. A RAID device is created in one step, and disks are added or removed as necessary. One RAID partition per physical disk is allowed for each device, so the number of disks available to the installation program determines which levels of RAID device are available to you. For example, if your system has two hard drives, the installation program will not allow you to create a RAID10 device, which requires 4 separate partitions. [IMPORTANT] ==== -This section only explains how to create software RAID with standard (physical) partitions. However, you can also configure LVM volume groups and Btrfs volumes to use RAID and place their logical volumes or Btrfs subvolumes on top of this RAID array. See <> and <> for instructions on creating RAID in LVM and Btrfs. +This section only explains how to create software RAID with standard (physical) partitions. However, you can also configure LVM volume groups and Btrfs volumes to use RAID and place their logical volumes or Btrfs subvolumes on top of this RAID array. See xref:Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-lvm[Creating a Logical Volume Managament (LVM) Layout] and xref:Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-btrfs[Creating a Btrfs Layout] for instructions on creating RAID in LVM and Btrfs. ==== @@ -22,7 +22,7 @@ image::anaconda/CustomSpoke_SoftwareRAID.png[The Manual Partitioning screen, sho [NOTE] ==== -RAID configuration options are only visible if you have selected two or more disks for installation. At least two disks are required to create a RAID device, and some RAID layouts will require more. Requirements for different types of RAID are described in <>. +RAID configuration options are only visible if you have selected two or more disks for installation. At least two disks are required to create a RAID device, and some RAID layouts will require more. Requirements for different types of RAID are described in xref:Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-filesystems[Device, File System and RAID Types]. ==== @@ -42,7 +42,7 @@ When creating a mount point for swap on software RAID, specify the mount point a . The mount point has now been created using the default settings, which means it has been created as an LVM logical volume. Select the newly created mount point in the left pane to configure it further, and convert it to a software RAID partition by changing the `Device Type` option to `RAID`. -. Choose a RAID type from the `RAID Level` drop-down menu. Available RAID types and their requirements are described in <>. +. Choose a RAID type from the `RAID Level` drop-down menu. Available RAID types and their requirements are described in xref:Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-filesystems[Device, File System and RAID Types]. . In the `Device(s)` section on the right side of the screen, you can see that the partition has been assigned to several physical disks. Click the `Modify` button to configure on which drives this partition will be created. diff --git a/en-US/install/DateTimeSpoke.adoc b/en-US/install/DateTimeSpoke.adoc index bf4ce7b..4ba42de 100644 --- a/en-US/install/DateTimeSpoke.adoc +++ b/en-US/install/DateTimeSpoke.adoc @@ -4,7 +4,7 @@ [[sect-installation-gui-date-and-time]] ===== Date & Time -The `Date & Time` screen allows you to configure time and date-related settings for your system. This screen is automatically configured based on the settings you selected in <>, but you can change your date, time and location settings before you begin the installation. +The `Date & Time` screen allows you to configure time and date-related settings for your system. This screen is automatically configured based on the settings you selected in xref:Installing_Using_Anaconda.adoc#sect-installation-gui-welcome[Welcome Screen and Language Selection], but you can change your date, time and location settings before you begin the installation. .Date & Time @@ -29,4 +29,4 @@ image::anaconda/DateTimeSpoke_AddNTP.png[A dialog window allowing you to add or If you disable network time synchronization, the controls at the bottom of the screen will become active, and you will be able to set the current time and date manually. -After configuring your time and date settings, press the `Done` button in the top left corner to return to <>. +After configuring your time and date settings, press the `Done` button in the top left corner to return to xref:Installing_Using_Anaconda.adoc#sect-installation-gui-installation-summary[Installation Summary]. diff --git a/en-US/install/FilterSpoke.adoc b/en-US/install/FilterSpoke.adoc index ea2dc55..8b63586 100644 --- a/en-US/install/FilterSpoke.adoc +++ b/en-US/install/FilterSpoke.adoc @@ -4,7 +4,7 @@ [[sect-installation-gui-installation-destination]] ===== Installation Destination - Specialized & Network Disks -This part of the `Installation Destination` screen allows you to configure non-local storage devices, namely iSCSI and FCoE storage. This section will mostly be useful to advanced users who have a need for networked disks. For instructions on setting up local hard drives, see <>. +This part of the `Installation Destination` screen allows you to configure non-local storage devices, namely iSCSI and FCoE storage. This section will mostly be useful to advanced users who have a need for networked disks. For instructions on setting up local hard drives, see xref:Installing_Using_Anaconda.adoc#sect-installation-gui-storage-partitioning[Installation Destination]. [IMPORTANT] ==== @@ -19,7 +19,7 @@ image::anaconda/FilterSpoke.png[A list of currently configured network storage d The screen contains a list of all currently available (discovered) network storage devices. When the screen is opened for the first time, the list will be empty in most cases because no network storage has been discovered - the installer makes no attempt at discovering this unless you configure network disks using a Kickstart file. -To add one or more storage devices to the screen so you can search them and use them in the installation, click `Add iSCSI Target` or `Add FCoE SAN` in the bottom right corner of the screen, and follow the instructions in <> or <>, depending on which type of network storage you want to add. +To add one or more storage devices to the screen so you can search them and use them in the installation, click `Add iSCSI Target` or `Add FCoE SAN` in the bottom right corner of the screen, and follow the instructions in xref:Installing_Using_Anaconda.adoc#sect-installation-gui-installation-destination-add-iscsi[Add iSCSI Target] or xref:Installing_Using_Anaconda.adoc#sect-installation-gui-installation-destination-add-fcoe[Add FCoE SAN], depending on which type of network storage you want to add. Network storage devices successfully discovered and configured by the installer will then be displayed in the main list, along with identifying information such as `Name`, `WWID`, `Model` and `Target`. To sort the list by a specific column (for example `WWID`), click the column's heading. @@ -47,7 +47,7 @@ Other SAN Devices:: Devices available on a Storage Area Network (SAN). Depending on the tab you are currently in, you can filter the discovered devices by using the `Filter By` field. Some of the filtering options are automatically populated based on discovered devices (for example, if you select `Filter By:` `Vendor`, another drop-down menu will appear showing all vendors of all discovered devices). Other filters require your input (for example when filtering by WWID), and present you with a text input field instead of a drop-down menu. -In the list (regardless of how it is filtered), each device is presented on a separate row, with a check box to its left. Mark the check box to make the device available during the installation process; this will cause this device (node) to be shown in the `Specialized & Network Disks` section in <>. There, you can select the disk as an installation target and proceed with either manual or automatic partitioning. +In the list (regardless of how it is filtered), each device is presented on a separate row, with a check box to its left. Mark the check box to make the device available during the installation process; this will cause this device (node) to be shown in the `Specialized & Network Disks` section in xref:Installing_Using_Anaconda.adoc#sect-installation-gui-storage-partitioning[Installation Destination]. There, you can select the disk as an installation target and proceed with either manual or automatic partitioning. [NOTE] ==== @@ -56,7 +56,7 @@ Devices that you select here are not automatically wiped by the installation pro ==== -When you have selected the storage devices to make available during installation, click `Done` to return to <>. +When you have selected the storage devices to make available during installation, click `Done` to return to xref:Installing_Using_Anaconda.adoc#sect-installation-gui-storage-partitioning[Installation Destination]. include::FilterSpoke_AddiSCSI.adoc[] diff --git a/en-US/install/FilterSpoke_AddFCoE.adoc b/en-US/install/FilterSpoke_AddFCoE.adoc index 00c2ba1..d6fdf2b 100644 --- a/en-US/install/FilterSpoke_AddFCoE.adoc +++ b/en-US/install/FilterSpoke_AddFCoE.adoc @@ -8,9 +8,9 @@ The following procedure explains how to add _Fibre Channel over Ethernet_ (FCoE) [[proc-installation-gui-installation-destination-add-fcoe]] .Add FCoE Target -. Click the `Add FCoE SAN` button in the bottom right corner of <>. A new dialog window will open. +. Click the `Add FCoE SAN` button in the bottom right corner of xref:Installing_Using_Anaconda.adoc#sect-installation-gui-installation-destination[Installation Destination - Specialized & Network Disks]. A new dialog window will open. -. Select the network interface (`NIC`) which is connected to your FCoE switch from the drop-down menu. Note that this network interface must be configured and connected - see <>. +. Select the network interface (`NIC`) which is connected to your FCoE switch from the drop-down menu. Note that this network interface must be configured and connected - see xref:Installing_Using_Anaconda.adoc#sect-installation-gui-network-configuration[Network & Hostname]. . Below the `NIC` drop-down menu are two choices: + @@ -18,4 +18,4 @@ The following procedure explains how to add _Fibre Channel over Ethernet_ (FCoE) + `Use auto vlan`:: This option indicates whether VLAN discovery should be performed. If this box is checked, then the _FCoE Initiation Protocol_ (FIP) VLAN discovery protocol will run on the Ethernet interface once the link configuration has been validated. If they are not already configured, network interfaces for any discovered FCoE VLANs will be automatically created and FCoE instances will be created on the VLAN interfaces. This option is enabled by default. -. After you select which interface and options to use, click `Add FCoE Disk(s)`. Discovered FCoE storage devices will be displayed under the `Other SAN Devices` tab in <>. \ No newline at end of file +. After you select which interface and options to use, click `Add FCoE Disk(s)`. Discovered FCoE storage devices will be displayed under the `Other SAN Devices` tab in xref:Installing_Using_Anaconda.adoc#sect-installation-gui-installation-destination[Installation Destination - Specialized & Network Disks]. \ No newline at end of file diff --git a/en-US/install/FilterSpoke_AddiSCSI.adoc b/en-US/install/FilterSpoke_AddiSCSI.adoc index 51ec8aa..886c196 100644 --- a/en-US/install/FilterSpoke_AddiSCSI.adoc +++ b/en-US/install/FilterSpoke_AddiSCSI.adoc @@ -12,7 +12,7 @@ Follow the procedure below to add an iSCSI storage target to your system. [[proc-installation-gui-installation-destination-add-iscsi]] .Add iSCSI Target -. Click the `Add iSCSI Target` button in the bottom right corner of the <> screen. A new dialog window titled `Add iSCSI Storage Target` will open. +. Click the `Add iSCSI Target` button in the bottom right corner of the xref:Installing_Using_Anaconda.adoc#sect-installation-gui-installation-destination[Installation Destination - Specialized & Network Disks] screen. A new dialog window titled `Add iSCSI Storage Target` will open. . Enter the IP address of the iSCSI target in the `Target IP Address` field. @@ -54,6 +54,6 @@ If the discovery was successful, you will see a list of all discovered nodes. . Select one or more nodes you want to log in to by marking or unmarking the check box next to each node discovered on the target. Below the list, select again the type of authentication you want to use; you can also select the `Use the credentials from discovery` option if the CHAP/reverse CHAP user name and password you used to discover the target are also valid for logging in to it. + -After selecting all nodes you want to use, click `Log In` to initiate an iSCSI session. [application]*Anaconda* will attempt to log in to all selected nodes. If the login process is succesful, the `Add iSCSI Storage Target` dialog will close, and all nodes you have configured will now be shown in the list of network disks in <>. +After selecting all nodes you want to use, click `Log In` to initiate an iSCSI session. [application]*Anaconda* will attempt to log in to all selected nodes. If the login process is succesful, the `Add iSCSI Storage Target` dialog will close, and all nodes you have configured will now be shown in the list of network disks in xref:Installing_Using_Anaconda.adoc#sect-installation-gui-installation-destination[Installation Destination - Specialized & Network Disks]. You can repeat this procedure to discover additional iSCSI targets, or to add more nodes from a previously configured target. However, note that once you click the `Start Discovery` button for the first time, you will not be able to change the `iSCSI Initiator Name`. If you made an error when configuring the initiator name, you must restart the installation. \ No newline at end of file diff --git a/en-US/install/InitialSetupHub.adoc b/en-US/install/InitialSetupHub.adoc index 2d3a56d..149d189 100644 --- a/en-US/install/InitialSetupHub.adoc +++ b/en-US/install/InitialSetupHub.adoc @@ -8,7 +8,7 @@ The `Initial Setup` screen is shown after the installation finishes and the inst * Your software selection contained a graphical environment (for example, you installed the system using a {PRODUCT} Workstation live image). -* The graphical environment you have installed is *not* [application]*GNOME Desktop Environment* (it provides its own initial setup utility which is described in <>). +* The graphical environment you have installed is *not* [application]*GNOME Desktop Environment* (it provides its own initial setup utility which is described in xref:After_Installation.adoc#sect-gnome-initial-setup[GNOME Initial Setup]). * The [package]*initial-setup* package has been installed. @@ -36,7 +36,7 @@ It is possible to configure [application]*Initial Setup* to display all availabl ---- -The [option]#--reconfig# option specifies that all options should be displayed. See <> for information about Kickstart installations. +The [option]#--reconfig# option specifies that all options should be displayed. See xref:../advanced/Kickstart_Installations.adoc#chap-kickstart-installations[Automating the Installation with Kickstart] for information about Kickstart installations. ==== diff --git a/en-US/install/Installing_Using_Anaconda.adoc b/en-US/install/Installing_Using_Anaconda.adoc index 2ac4a28..4e1b66c 100644 --- a/en-US/install/Installing_Using_Anaconda.adoc +++ b/en-US/install/Installing_Using_Anaconda.adoc @@ -9,9 +9,9 @@ This chapter provides step-by-step instructions for installing {PRODUCT} using t If your system does not have the ability to use the graphical mode, you can: -* Use Kickstart to automate the installation as described in <> +* Use Kickstart to automate the installation as described in xref:../advanced/Kickstart_Installations.adoc#chap-kickstart-installations[Automating the Installation with Kickstart] -* Perform the graphical installation remotely by connecting to the installation system from another computer with a graphical display using the _VNC_ (Virtual Network Computing) protocol - see <> +* Perform the graphical installation remotely by connecting to the installation system from another computer with a graphical display using the _VNC_ (Virtual Network Computing) protocol - see xref:../advanced/VNC_Installations.adoc#chap-vnc-installations[Installing Using VNC] [[sect-installation-new-users]] ==== Introduction to Anaconda @@ -67,21 +67,21 @@ You can also use kbd:[Ctrl + b] kbd:[n] and kbd:[Ctrl + b] kbd:[p] to switch to |kbd:[Ctrl + b] kbd:[5]|Program log; displays messages from other system utilities, stored in `/tmp/program.log`. |=== -In addition to displaying diagnostic information in [application]*tmux* windows, [application]*Anaconda* also generates several log files, which can be transferred from the installation system. These log files are described in <>, and directions for transferring them from the installation system are available in <>. +In addition to displaying diagnostic information in [application]*tmux* windows, [application]*Anaconda* also generates several log files, which can be transferred from the installation system. These log files are described in xref:Troubleshooting.adoc#sect-troubleshooting-log-files[Log Files Generated During the Installation], and directions for transferring them from the installation system are available in xref:Troubleshooting.adoc#sect-troubleshooting-transferring-logs[Transferring Log Files from the Installation System]. [[sect-installation-screenshots]] ===== Saving Screenshots You can press kbd:[Shift + Print Screen] at any time during the graphical installation to capture the current screen. These screenshots are saved to `/tmp/anaconda-screenshots`. -Additionally, you can use the [command]#autostep --autoscreenshot# command in a Kickstart file to capture and save each step of the installation automatically. See <> for details. +Additionally, you can use the [command]#autostep --autoscreenshot# command in a Kickstart file to capture and save each step of the installation automatically. See xref:../appendixes/Kickstart_Syntax_Reference.adoc#sect-kickstart-commands-autostep[autostep (optional) - Go Through Every Screen] for details. [[sect-installation-text-mode]] ==== Installing in Text Mode Text mode installation offers an interactive, non-graphical interface for installing {PRODUCT}. This may be useful on systems with no graphical capabilities; however, you should always consider the available alternatives before starting a text-based installation. Text mode is limited in the amount of choices you can make during the installation. -There are two alternatives to text mode which can both be used even if the installation system does not have a graphical display. You can either connect to the installation system using VNC and perform an interactive graphical installation remotely (see <>), or you can create a Kickstart file to perform the installation automatically (see <>). +There are two alternatives to text mode which can both be used even if the installation system does not have a graphical display. You can either connect to the installation system using VNC and perform an interactive graphical installation remotely (see xref:../advanced/VNC_Installations.adoc#chap-vnc-installations[Installing Using VNC]), or you can create a Kickstart file to perform the installation automatically (see xref:../advanced/Kickstart_Installations.adoc#chap-kickstart-installations[Automating the Installation with Kickstart]). .Text Mode Installation @@ -97,7 +97,7 @@ Limits of interactive text mode installation include: * It is not possible to configure custom partitioning; you must use one of the automatic partitioning settings. You also cannot configure where the boot loader will be installed. -To start a text mode installation, boot the installation with the [option]#inst.text# boot option used either at the boot command line in the boot menu, or in your PXE server configuration. See <> for information about booting and using boot options. +To start a text mode installation, boot the installation with the [option]#inst.text# boot option used either at the boot command line in the boot menu, or in your PXE server configuration. See xref:Booting_the_Installation.adoc#chap-booting-the-installation[Booting the Installation] for information about booting and using boot options. [[sect-installation-graphical-mode]] ==== Installing in the Graphical User Interface @@ -112,7 +112,7 @@ You can also control the graphical installer with your keyboard. Use kbd:[Tab] a Additionally, elements in each screen can be toggled using their respective shortcuts. These shortcuts are highlighted (underlined) when you hold down the kbd:[Alt] key; to toggle that element, press kbd:[Alt + _X_pass:attributes[{blank}]], where _X_ is the highlighted letter. -Your current keyboard layout is displayed in the top right hand corner. Only one layout is configured by default; if you configure more than layout in the `Keyboard Layout` screen (<>), you can switch between them by clicking the layout indicator. +Your current keyboard layout is displayed in the top right hand corner. Only one layout is configured by default; if you configure more than layout in the `Keyboard Layout` screen (xref:Installing_Using_Anaconda.adoc#sect-installation-gui-keyboard-layout[Keyboard Layout]), you can switch between them by clicking the layout indicator. include::en-US/install/WelcomeSpoke.adoc[] diff --git a/en-US/install/KdumpSpoke.adoc b/en-US/install/KdumpSpoke.adoc index 6e38803..6031669 100644 --- a/en-US/install/KdumpSpoke.adoc +++ b/en-US/install/KdumpSpoke.adoc @@ -7,7 +7,7 @@ [NOTE] ==== -This screen is disabled by default. To enable it during the installation, you must use the [option]#inst.kdump_addon=on# option at the boot menu. See <> for details, and <> for instructions on using custom boot options. +This screen is disabled by default. To enable it during the installation, you must use the [option]#inst.kdump_addon=on# option at the boot menu. See xref:../advanced/Boot_Options.adoc#sect-boot-options-advanced[Advanced Installation Options] for details, and xref:Booting_the_Installation.adoc#sect-boot-menu[The Boot Menu] for instructions on using custom boot options. ==== @@ -32,4 +32,4 @@ Additional settings, such as the location where kernel crash dumps will be saved ==== -After configuring [application]*Kdump* settings, click btn:[Done] in the top left corner to return to <>. +After configuring [application]*Kdump* settings, click btn:[Done] in the top left corner to return to xref:Installing_Using_Anaconda.adoc#sect-installation-gui-installation-summary[Installation Summary]. diff --git a/en-US/install/KeyboardSpoke.adoc b/en-US/install/KeyboardSpoke.adoc index 0139163..c549405 100644 --- a/en-US/install/KeyboardSpoke.adoc +++ b/en-US/install/KeyboardSpoke.adoc @@ -4,7 +4,7 @@ [[sect-installation-gui-keyboard-layout]] ===== Keyboard Layout -The `Keyboard Layout` screen allows you to set up one or more keyboard layouts for your system and a way to switch between them. One keyboard layout is configured automatically based on your selection in <>, but you can change this layout and add additional ones before you begin the installation. +The `Keyboard Layout` screen allows you to set up one or more keyboard layouts for your system and a way to switch between them. One keyboard layout is configured automatically based on your selection in xref:Installing_Using_Anaconda.adoc#sect-installation-gui-welcome[Welcome Screen and Language Selection], but you can change this layout and add additional ones before you begin the installation. Keyboard layouts are a separate setting from system languages, and these two settings can be mixed as you see fit. @@ -42,4 +42,4 @@ If you use a layout that cannot accept Latin characters, such as `Russian`, you You can also optionally configure a keyboard switch which can be used to cycle between available layouts. To do so, click the `Options` button on the right side of the screen. The `Layout Switching Options` dialog will open, allowing you to configure one or more keys or key combinations for switching. Select one or more key combinations using the check boxes next to them, and click `OK` to confirm your selection. -After you finish configuring keyboard layouts and switches, click `Done` in the top left corner to return to <>. \ No newline at end of file +After you finish configuring keyboard layouts and switches, click `Done` in the top left corner to return to xref:Installing_Using_Anaconda.adoc#sect-installation-gui-installation-summary[Installation Summary]. \ No newline at end of file diff --git a/en-US/install/LangSupportSpoke.adoc b/en-US/install/LangSupportSpoke.adoc index 40115b4..1ecd289 100644 --- a/en-US/install/LangSupportSpoke.adoc +++ b/en-US/install/LangSupportSpoke.adoc @@ -4,14 +4,14 @@ [[sect-installation-gui-language-support]] ===== Language Support -The `Language Support` screen allows you to configure language settings for your system. The default language is determined by your selection in <> and support for this language can not be removed. You can only add additional languages, which will be available on the installed system - not during the installation. +The `Language Support` screen allows you to configure language settings for your system. The default language is determined by your selection in xref:Installing_Using_Anaconda.adoc#sect-installation-gui-welcome[Welcome Screen and Language Selection] and support for this language can not be removed. You can only add additional languages, which will be available on the installed system - not during the installation. -If you want to change the default language, or the language used during the installation, you must reboot your system, start the installer again, and select a different language in <>. +If you want to change the default language, or the language used during the installation, you must reboot your system, start the installer again, and select a different language in xref:Installing_Using_Anaconda.adoc#sect-installation-gui-welcome[Welcome Screen and Language Selection]. [NOTE] ==== -Adding support for another language does not automatically configure the corresponding keyboard layout. Layouts are a separate setting configured in <>. +Adding support for another language does not automatically configure the corresponding keyboard layout. Layouts are a separate setting configured in xref:Installing_Using_Anaconda.adoc#sect-installation-gui-keyboard-layout[Keyboard Layout]. ==== @@ -26,8 +26,8 @@ To add support for one or more additional languages, click a group in the left p [NOTE] ==== -Enabling support for some languages (typically languages which use non-Latin script) will install additional packages - for example, enabling support for one or more languages from the `Arabic` group will also install the `arabic-support` package group. For more information about packages, see <>. +Enabling support for some languages (typically languages which use non-Latin script) will install additional packages - for example, enabling support for one or more languages from the `Arabic` group will also install the `arabic-support` package group. For more information about packages, see xref:Installing_Using_Anaconda.adoc#sect-installation-gui-software-selection[Software Selection]. ==== -Once you have made your selections, click `Done` in the top left corner to return to <>. \ No newline at end of file +Once you have made your selections, click `Done` in the top left corner to return to xref:Installing_Using_Anaconda.adoc#sect-installation-gui-installation-summary[Installation Summary]. \ No newline at end of file diff --git a/en-US/install/NetworkSpoke.adoc b/en-US/install/NetworkSpoke.adoc index eb416cb..da78574 100644 --- a/en-US/install/NetworkSpoke.adoc +++ b/en-US/install/NetworkSpoke.adoc @@ -19,9 +19,9 @@ image::anaconda/NetworkSpoke.png[The Network & Hostname screen. In the left pane Locally accessible interfaces are automatically detected by the installation program and cannot be manually added or deleted. All detected interfaces are listed on the left side of the screen. Click an interface in the list to display its current configuration (such as IP and DNS address); the details are displayed on the right side of the screen. -Below the list of interfaces are two buttons. Use the `+` button to add a virtual network interface (Team, Bond or VLAN) as described in <>. To remove a previously created virtual interface, select it in the list and click the `-` button. +Below the list of interfaces are two buttons. Use the `+` button to add a virtual network interface (Team, Bond or VLAN) as described in xref:Installing_Using_Anaconda.adoc#sect-installation-gui-network-configuration-virtual-interface[Adding a Virtual Network Interface]. To remove a previously created virtual interface, select it in the list and click the `-` button. -To change settings such as IP addresses, DNS servers, or routing configuration for an existing interface (both virtual and physical), select the interface in the left pane and click `Configure` in the bottom right corner of the screen. Available settings are described in <>. +To change settings such as IP addresses, DNS servers, or routing configuration for an existing interface (both virtual and physical), select the interface in the left pane and click `Configure` in the bottom right corner of the screen. Available settings are described in xref:Installing_Using_Anaconda.adoc#sect-installation-gui-network-configuration-advanced[Editing Network Interface Configuration]. Use the `ON`pass:attributes[{blank}]/pass:attributes[{blank}]`OFF` switch in the top right corner to enable or disable the currently selected interface. diff --git a/en-US/install/NetworkSpoke_EditConnection.adoc b/en-US/install/NetworkSpoke_EditConnection.adoc index d6d93f8..af0d0e1 100644 --- a/en-US/install/NetworkSpoke_EditConnection.adoc +++ b/en-US/install/NetworkSpoke_EditConnection.adoc @@ -6,7 +6,7 @@ This section only details the most important settings for a typical wired connection used during installation. Many of the available options do not have to be changed in most installation scenarios and are not carried over to the installed system. Configuration of other types of networks is broadly similar, although the specific configuration parameters may be different. To learn more about network configuration after installation, see the [citetitle]_{PRODUCT} Networking{nbsp}Guide_, available at link:++http://docs.fedoraproject.org/++[]. -To configure a network connection manually, select that connection in the list on the left side of the screen, and click the `Configure` button. A dialog will appear that allows you to configure the selected connection. The configuration options presented depends on the connection type - the available options will be slightly different depending on whether it is a physical interface (wired or wireless network interface controller) or a virtual interface (Bond, Team or Vlan) which you previously configured in <>.. A full description of all configuration settings for all connection types is beyond the scope of this document; see the [citetitle]_Networking Guide_ for details. +To configure a network connection manually, select that connection in the list on the left side of the screen, and click the `Configure` button. A dialog will appear that allows you to configure the selected connection. The configuration options presented depends on the connection type - the available options will be slightly different depending on whether it is a physical interface (wired or wireless network interface controller) or a virtual interface (Bond, Team or Vlan) which you previously configured in xref:Installing_Using_Anaconda.adoc#sect-installation-gui-network-configuration-virtual-interface[Adding a Virtual Network Interface].. A full description of all configuration settings for all connection types is beyond the scope of this document; see the [citetitle]_Networking Guide_ for details. The most common and useful options in the configuration dialog are: @@ -46,4 +46,4 @@ Select `Use this connection only for resources on its network` to prevent this c + When you finish configuring the interface's routing settings, click `OK` to return to the configuration dialog. -Once you finish configuring the interface, click `Save` in the configuration window's bottom right corner to save your settings and return to <>. +Once you finish configuring the interface, click `Save` in the configuration window's bottom right corner to save your settings and return to xref:Installing_Using_Anaconda.adoc#sect-installation-gui-network-configuration[Network & Hostname]. diff --git a/en-US/install/NetworkSpoke_VirtualInterfaces.adoc b/en-US/install/NetworkSpoke_VirtualInterfaces.adoc index a4ebf29..917d73d 100644 --- a/en-US/install/NetworkSpoke_VirtualInterfaces.adoc +++ b/en-US/install/NetworkSpoke_VirtualInterfaces.adoc @@ -12,7 +12,7 @@ To add a virtual network interface, click the `+` button at the bottom of the in * `Vlan` (_Virtual LAN_) - A method to create multiple distinct broadcast domains which are mutually isolated. -Select the interface type you want to add, and click `Add`. Another dialog window will open, allowing you to edit any available settings for your chosen interface type. For information about available settings, see the respective sections of the [citetitle]_{PRODUCT} Networking{nbsp}Guide_, available at link:++http://docs.fedoraproject.org/++[]. Basic documentation is also available in <>. +Select the interface type you want to add, and click `Add`. Another dialog window will open, allowing you to edit any available settings for your chosen interface type. For information about available settings, see the respective sections of the [citetitle]_{PRODUCT} Networking{nbsp}Guide_, available at link:++http://docs.fedoraproject.org/++[]. Basic documentation is also available in xref:Installing_Using_Anaconda.adoc#sect-installation-gui-network-configuration-advanced[Editing Network Interface Configuration]. [NOTE] ==== diff --git a/en-US/install/PasswordSpoke.adoc b/en-US/install/PasswordSpoke.adoc index 3ceb285..0dfdfda 100644 --- a/en-US/install/PasswordSpoke.adoc +++ b/en-US/install/PasswordSpoke.adoc @@ -6,7 +6,7 @@ The `Root Password` screen is used to configure the `root` password for your system. This password will be used to log into the administrator (also known as superuser) account, which is used for system administration tasks such as installing and updating software packages and changing system-wide configuration such as network and firewall settings, storage options and adding or modifying users, groups and file permissions. -The `root` account will always be created during the installation. However, you should always also create a normal user accont in <> and use that account to log in to the system. Only switch to the administrator account only when you need to perform a task which requires administrator access. +The `root` account will always be created during the installation. However, you should always also create a normal user accont in xref:Installing_Using_Anaconda.adoc#sect-installation-gui-create-user[Create User] and use that account to log in to the system. Only switch to the administrator account only when you need to perform a task which requires administrator access. [WARNING] ==== @@ -30,4 +30,4 @@ As you enter the password, it will be evaluated and the installer will determine If a message similar to the above appears, it is highly recommended to choose a different, stronger password. -Once you configure the superuser password, click `Done` in the top left corner to return to <>. If you selected a weak password, you must press the button twice. +Once you configure the superuser password, click `Done` in the top left corner to return to xref:Installing_Using_Anaconda.adoc#sect-installation-gui-installation-progress[Configuration and Installation Progress]. If you selected a weak password, you must press the button twice. diff --git a/en-US/install/Preparing_for_Installation.adoc b/en-US/install/Preparing_for_Installation.adoc index c57f495..a13e45b 100644 --- a/en-US/install/Preparing_for_Installation.adoc +++ b/en-US/install/Preparing_for_Installation.adoc @@ -14,7 +14,7 @@ If you already have Fedora installed and want to upgrade your installation to th Automatic upgrade using [application]*dnf system upgrade*:: The preferred way to upgrade your system is an automatic upgrade using the [application]*dnf system upgrade* utility. For information on performing an automatic upgrade, see link:++https://fedoraproject.org/wiki/DNF_system_upgrade++[Fedora Wiki dnf system upgrade]. -Manual Reinstallation:: You can upgrade to the latest version of Fedora manually instead of relying on [application]*dnf system upgrade*. This involves booting the installer as if you were performing a clean installation, letting it detect your existing Fedora system, and overwriting the root partition while preserving data on other partitions and volumes. The same process can also be used to reinstall the system, if you need to. For detailed information, see <>. +Manual Reinstallation:: You can upgrade to the latest version of Fedora manually instead of relying on [application]*dnf system upgrade*. This involves booting the installer as if you were performing a clean installation, letting it detect your existing Fedora system, and overwriting the root partition while preserving data on other partitions and volumes. The same process can also be used to reinstall the system, if you need to. For detailed information, see xref:../advanced/Upgrading_Your_Current_System.adoc#sect-upgrading-fedora-manual-reinstall[Manual System Upgrade or Reinstallation]. [WARNING] ==== @@ -26,9 +26,9 @@ Always back up your data before performing an upgrade or reinstalling your syste [[sect-preparing-obtaining-images]] ==== Downloading Boot and Installation Images -The Fedora Project offers different Editions tailored for some specific use cases. Choose the Fedora Edition best for you, or you can build your own by customizing after the installation, or by using a kickstart file as described in <>. Kickstart installation requires the `netinstall` media type, or a direct installation booting method such as PXE; kickstarts are not supported with live images. +The Fedora Project offers different Editions tailored for some specific use cases. Choose the Fedora Edition best for you, or you can build your own by customizing after the installation, or by using a kickstart file as described in xref:../advanced/Kickstart_Installations.adoc#sect-kickstart-file-create[Creating a Kickstart File]. Kickstart installation requires the `netinstall` media type, or a direct installation booting method such as PXE; kickstarts are not supported with live images. -Read more about Fedora Workstation, Fedora Cloud, Fedora Server and the available media types in <>. +Read more about Fedora Workstation, Fedora Cloud, Fedora Server and the available media types in xref:../Downloading_Fedora.adoc#chap-downloading-fedora[Downloading Fedora]. You can also choose a Fedora _Spin_ featuring favorite alternative desktops or tools for specialized tasks at link:++http://spins.fedoraproject.org++[]. diff --git a/en-US/install/ProgressHub.adoc b/en-US/install/ProgressHub.adoc index 02873e3..6b27332 100644 --- a/en-US/install/ProgressHub.adoc +++ b/en-US/install/ProgressHub.adoc @@ -4,7 +4,7 @@ [[sect-installation-gui-installation-progress]] ===== Configuration and Installation Progress -The `Configuration` screen is displayed after you finish configuring all required items in <> and press the `Begin installation` button. After this point, the installation process actually starts and changes are being made to your selected disks. It is not possible to go back to the `Installation Summary` and change any settings configured there; if you need to do so, you must wait for the installation process to finish, reboot your system, log in and change your settings on the installed system. +The `Configuration` screen is displayed after you finish configuring all required items in xref:Installing_Using_Anaconda.adoc#sect-installation-gui-installation-summary[Installation Summary] and press the `Begin installation` button. After this point, the installation process actually starts and changes are being made to your selected disks. It is not possible to go back to the `Installation Summary` and change any settings configured there; if you need to do so, you must wait for the installation process to finish, reboot your system, log in and change your settings on the installed system. .Configuration and Installation Progress diff --git a/en-US/install/SoftwareSpoke.adoc b/en-US/install/SoftwareSpoke.adoc index 62b420b..95f7247 100644 --- a/en-US/install/SoftwareSpoke.adoc +++ b/en-US/install/SoftwareSpoke.adoc @@ -6,12 +6,12 @@ The `Software Selection` screen allows you to choose a _Base Environment_ and _Add-ons_. These options control which software packages will be installed on your system during the installation process. -This screen is only available if <> is properly configured and only after the installer has downloaded package metadata from the source. +This screen is only available if xref:Installing_Using_Anaconda.adoc#sect-installation-gui-installation-source[Installation Source] is properly configured and only after the installer has downloaded package metadata from the source. [NOTE] ==== -It is not possible to select specific packages during a manual installation. You can only select pre-defined environments and add-ons. If you need to control exactly which packages are installed, you must use a Kickstart file and define the packages in the [command]#%packages# section. See <> for information about Kickstart installations. +It is not possible to select specific packages during a manual installation. You can only select pre-defined environments and add-ons. If you need to control exactly which packages are installed, you must use a Kickstart file and define the packages in the [command]#%packages# section. See xref:../advanced/Kickstart_Installations.adoc#chap-kickstart-installations[Automating the Installation with Kickstart] for information about Kickstart installations. ==== @@ -25,6 +25,6 @@ To configure your software selection, first choose an environment on the left si The list of add-ons is divided into two parts by a horizontal line. Add-ons above this line are defined as part of your chosen environment; if you select a different environment, the add-ons available here will change. The add-ons displayed below the separator are not specific to your chosen environment. -Environments and add-ons are defined using a `comps.xml` file in your installation source (for example, in the `repodata/` directory on the full Fedora{nbsp}Server installation DVD). Review this file to see exactly which packages will be installed as part of a certain environment or add-on. For more information about the `comps.xml` file, see <>. +Environments and add-ons are defined using a `comps.xml` file in your installation source (for example, in the `repodata/` directory on the full Fedora{nbsp}Server installation DVD). Review this file to see exactly which packages will be installed as part of a certain environment or add-on. For more information about the `comps.xml` file, see xref:../appendixes/Kickstart_Syntax_Reference.adoc#sect-kickstart-packages[%packages (required) - Package Selection]. -After you finish configuring your software selection, click `Done` in the top left corner to return to <>. +After you finish configuring your software selection, click `Done` in the top left corner to return to xref:Installing_Using_Anaconda.adoc#sect-installation-gui-installation-summary[Installation Summary]. diff --git a/en-US/install/SourceSpoke.adoc b/en-US/install/SourceSpoke.adoc index 3105f95..393d49b 100644 --- a/en-US/install/SourceSpoke.adoc +++ b/en-US/install/SourceSpoke.adoc @@ -9,7 +9,7 @@ The `Installation Source` screen allows you to specify a location (local or on t [NOTE] ==== -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 some time, especially if the default source is a network mirror. If you plan to use a custom installation source, use the [option]#inst.askmethod# boot option to skip the initial configuration; this will allow you to enter this screen immediately. See <> for information about boot options. +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 some time, especially if the default source is a network mirror. If you plan to use a custom installation source, use the [option]#inst.askmethod# boot option to skip the initial configuration; this will allow you to enter this screen immediately. See xref:../advanced/Boot_Options.adoc#sect-boot-options-sources[Specifying the Installation Source] for information about boot options. ==== @@ -45,10 +45,10 @@ To configure a proxy for an HTTP or HTTPS source, click the btn:[Proxy setup] bu + If your HTTP or HTTPS URL refers to a repository mirror list, mark the check box under the address field. -You can also specify additional repositories in the `Additional repositories` section to gain access to more installation environments and software add-ons. All environments and add-ons will be available for selection in <> once you finish configuring the sources. +You can also specify additional repositories in the `Additional repositories` section to gain access to more installation environments and software add-ons. All environments and add-ons will be available for selection in xref:Installing_Using_Anaconda.adoc#sect-installation-gui-software-selection[Software Selection] once you finish configuring the sources. To add a repository, click the btn:[+] button. To delete a repository, select one in the list and click the btn:[-] button. Click the arrow icon to revert to the previous list of repositories, i.e. to replace current entries with those that were present at the time you entered the `Installation Source` screen. To activate or deactivate a repository, click the check box in the `Enabled` column at each entry in the list. You can name your additional repository and configure it the same way as the primary repository on the network using the input fields on the right side of the section. -Once you have selected your installation source, click `Done` in the top left corner to return to <>. +Once you have selected your installation source, click `Done` in the top left corner to return to xref:Installing_Using_Anaconda.adoc#sect-installation-gui-installation-summary[Installation Summary]. diff --git a/en-US/install/StorageSpoke.adoc b/en-US/install/StorageSpoke.adoc index 8752f6e..eca6277 100644 --- a/en-US/install/StorageSpoke.adoc +++ b/en-US/install/StorageSpoke.adoc @@ -6,7 +6,7 @@ The `Installation Destination` screen allows you to configure storage options - namely, which disks will be used as the installation target for your {PRODUCT} installation. At least one disk must always be selected for the installation to proceed. -For information about the theory and concepts behind disk partitioning in Linux, see <>. +For information about the theory and concepts behind disk partitioning in Linux, see xref:Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-recommended[Recommended Partitioning Scheme]. [WARNING] ==== @@ -21,9 +21,9 @@ image::anaconda/StorageSpoke.png[The Installation Destination screen. There are In the top part of the screen, all locally available storage devices (SATA, IDE and SCSI hard drives, USB flash drives, etc.) are displayed in the `Local Standard Disks` section. Local disks are detected when the installer starts - any storage devices connected after the installation has started will not be shown. -If you need to configure additional local storage devices, select `I will configure partitioning` and press `Done` to move to <>. Then, connect any new hard drives you want to make available during the installation, and press the button marked by a circular arrow in the set of controls below the list of mount points on the left side of the screen. In the dialog window that opens, press `Rescan Disks` and wait until the scanning process completes. Then, press `OK` to return to <>; all detected disks including any new ones will be displayed in the `Local Standard Disks` section. +If you need to configure additional local storage devices, select `I will configure partitioning` and press `Done` to move to xref:Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning[Manual Partitioning]. Then, connect any new hard drives you want to make available during the installation, and press the button marked by a circular arrow in the set of controls below the list of mount points on the left side of the screen. In the dialog window that opens, press `Rescan Disks` and wait until the scanning process completes. Then, press `OK` to return to xref:Installing_Using_Anaconda.adoc#sect-installation-gui-storage-partitioning[Installation Destination]; all detected disks including any new ones will be displayed in the `Local Standard Disks` section. -The `Specialized & Network Disks` section below shows advanced network storage (such as iSCSI and FCoE disks) currently configured. When you first open this screen, no such devices will be displayed because they can not be automatically detected; to search for network storage devices `Add a disk` button and proceed with <>. Any network storage you configure will then show up in the `Specialized & Network Disks` the same way local disks are shown above. +The `Specialized & Network Disks` section below shows advanced network storage (such as iSCSI and FCoE disks) currently configured. When you first open this screen, no such devices will be displayed because they can not be automatically detected; to search for network storage devices `Add a disk` button and proceed with xref:Installing_Using_Anaconda.adoc#sect-installation-gui-installation-destination[Installation Destination - Specialized & Network Disks]. Any network storage you configure will then show up in the `Specialized & Network Disks` the same way local disks are shown above. All storage devices which will be used to install {PRODUCT} have a black circle icon with a white check mark on them. Disks not marked by this icon will not be used during the installation - they will be ignored if you choose automatic partitioning, and they will not be available in manual partitioning. @@ -44,18 +44,18 @@ After you select all disks you want to install {PRODUCT}, select one of the two + With automatic partitioning, you can also select the `I would like to make additional space available` option below. Use this option if you want to reclaim space from an existing partitioning layout - for example, if a disk you want to use already contains a different operating system, and you want to make this system's partitions smaller to allow more room for {PRODUCT}. The `Reclaim space` dialog which opens if this option is selected is described later in this section. -* `I will configure partitioning` - Select this option and press `Done` in the top left corner of the screen to configure your system's partitioning layout manually. This requires some knowledge of the theory behind disk partitions and related concepts, but gives you full control over the way the system will be installed. For instructions for manual partitioning, see <>. +* `I will configure partitioning` - Select this option and press `Done` in the top left corner of the screen to configure your system's partitioning layout manually. This requires some knowledge of the theory behind disk partitions and related concepts, but gives you full control over the way the system will be installed. For instructions for manual partitioning, see xref:Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning[Manual Partitioning]. Additionally, you can select `Encrypt my data`pass:attributes[{blank}]; this will encrypt all partitions except the ones needed to boot the system (such as `/boot`) using _Linux Unified Key Setup_ (LUKS). Encrypting your hard drive is recommended. For detailed information about LUKS encryption, see the [citetitle]_{PRODUCT} Security{nbsp}Guide_, available at link:++http://docs.fedoraproject.org/++[]. [WARNING] ==== -If you lose the LUKS passphrase, any encrypted partitions and the data on them will become completely inaccessible. There is no way to recover a lost passphrase. However, if you perform a Kickstart installation, you can save encryption passphrases and create backup encryption passphrases during the installation. See <> for information about Kickstart installations. +If you lose the LUKS passphrase, any encrypted partitions and the data on them will become completely inaccessible. There is no way to recover a lost passphrase. However, if you perform a Kickstart installation, you can save encryption passphrases and create backup encryption passphrases during the installation. See xref:../advanced/Kickstart_Installations.adoc#chap-kickstart-installations[Automating the Installation with Kickstart] for information about Kickstart installations. ==== -To control which one of your selected storage devices will contain the _boot loader_, click the `Full disk summary and bootloader` link in the bottom left corner of the screen, and follow the instructions in <>. Note that while in most cases it is sufficient to leave the boot loader in the default location, some configurations (for example, systems which require _chain loading_ from another boot loader) will require the boot drive to be specified manually. +To control which one of your selected storage devices will contain the _boot loader_, click the `Full disk summary and bootloader` link in the bottom left corner of the screen, and follow the instructions in xref:Installing_Using_Anaconda.adoc#sect-installation-gui-storage-partitioning-bootloader[Boot Loader Installation]. Note that while in most cases it is sufficient to leave the boot loader in the default location, some configurations (for example, systems which require _chain loading_ from another boot loader) will require the boot drive to be specified manually. After you select storage devices, choose between automatic and manual partitioning, configure encryption and boot loader location, press `Done` in the top left corner of the screen. Then, depending on your settings, the following will happen: @@ -77,10 +77,10 @@ After you free enough space for your {PRODUCT} installation, press `Reclaim spac [NOTE] ==== -No changes to any disks will be made until you press `Begin Installation` in <>. The `Reclaim Space` dialog only *marks* partitions for resizing or deletion, but no such action is performed immediately. +No changes to any disks will be made until you press `Begin Installation` in xref:Installing_Using_Anaconda.adoc#sect-installation-gui-installation-summary[Installation Summary]. The `Reclaim Space` dialog only *marks* partitions for resizing or deletion, but no such action is performed immediately. ==== -* If you selected the `I will configure partitioning` option, pressing `Done` will open the `Manual Partitioning` screen. See <> for further instructions. +* If you selected the `I will configure partitioning` option, pressing `Done` will open the `Manual Partitioning` screen. See xref:Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning[Manual Partitioning] for further instructions. include::StorageSpoke_BootLoader.adoc[] diff --git a/en-US/install/StorageSpoke_BootLoader.adoc b/en-US/install/StorageSpoke_BootLoader.adoc index 9f0dbe4..b9a6e51 100644 --- a/en-US/install/StorageSpoke_BootLoader.adoc +++ b/en-US/install/StorageSpoke_BootLoader.adoc @@ -32,4 +32,4 @@ If you choose not to install a boot loader for any reason, you will not be able ==== -The boot loader may also require a special partition to be created, depending on whether your system uses BIOS or UEFI firmware and also depending on whether the boot drive has a _GUID Partition Table_ (GPT) or a `Master Boot Record` (MBR, also known as msdos) label. If you use automatic partitioning, the installer will create this partition if needed. For details, see <>. +The boot loader may also require a special partition to be created, depending on whether your system uses BIOS or UEFI firmware and also depending on whether the boot drive has a _GUID Partition Table_ (GPT) or a `Master Boot Record` (MBR, also known as msdos) label. If you use automatic partitioning, the installer will create this partition if needed. For details, see xref:Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-recommended[Recommended Partitioning Scheme]. diff --git a/en-US/install/SummaryHub.adoc b/en-US/install/SummaryHub.adoc index 3327e30..70a37be 100644 --- a/en-US/install/SummaryHub.adoc +++ b/en-US/install/SummaryHub.adoc @@ -37,4 +37,4 @@ Each screen also has an explanatory text below its title, showing settings curre image::anaconda/SummaryHub_Mouseover.png[An entry in the Installation Summary shows a truncated description and a tooltip with full text.] -Once you configure everything required for the installation, you can press the `Begin Installation` button to start installing {PRODUCT}. This will take you to <>. Note that as the text below this button says, nothing will be written to your hard drive before you press this button. You can press `Quit` at any point; this will discard all changes you made in the installer so far and reboot the system. +Once you configure everything required for the installation, you can press the `Begin Installation` button to start installing {PRODUCT}. This will take you to xref:Installing_Using_Anaconda.adoc#sect-installation-gui-installation-progress[Configuration and Installation Progress]. Note that as the text below this button says, nothing will be written to your hard drive before you press this button. You can press `Quit` at any point; this will discard all changes you made in the installer so far and reboot the system. diff --git a/en-US/install/Troubleshooting.adoc b/en-US/install/Troubleshooting.adoc index 8f9eaa7..d651960 100644 --- a/en-US/install/Troubleshooting.adoc +++ b/en-US/install/Troubleshooting.adoc @@ -54,7 +54,7 @@ If the installation fails, the messages from these files are consolidated into ` [[sect-troubleshooting-transferring-logs]] ===== Transferring Log Files from the Installation System -All of the files described in <> reside in the installation program's RAM disk, which means they are not saved permamently and will be lost once the system is powered down. To store them permanently, copy those files to another system on the network using [command]#scp# on the system running the installation program, or copy them to a mounted storage device (such as an USB flash drive). Details on how to transfer the log files are below. Note that if you use an USB flash drive or other removable media, you should make sure to back up any data on it before starting the procedure. +All of the files described in xref:Troubleshooting.adoc#sect-troubleshooting-log-files[Log Files Generated During the Installation] reside in the installation program's RAM disk, which means they are not saved permamently and will be lost once the system is powered down. To store them permanently, copy those files to another system on the network using [command]#scp# on the system running the installation program, or copy them to a mounted storage device (such as an USB flash drive). Details on how to transfer the log files are below. Note that if you use an USB flash drive or other removable media, you should make sure to back up any data on it before starting the procedure. [[sect-troubleshooting-transferring-logs-usb]] ====== Transferring Log Files Onto a USB Drive @@ -160,7 +160,7 @@ The log files from the installation are now permanently saved on the target syst Systems with some video cards have trouble booting into the graphical installation program. If the installation program does not run using its default settings, it attempts to run in a lower resolution mode. If that still fails, the installation program attempts to run in text mode. -There are several possible solutions to display issues, most of which involve specifying custom boot options. For more information, see <>. +There are several possible solutions to display issues, most of which involve specifying custom boot options. For more information, see xref:../advanced/Boot_Options.adoc#sect-boot-options-installer[Configuring the Installation System at the Boot Menu]. Use the basic graphics mode:: You can attempt to perform the installation using the basic graphics driver. To do this, edit the installation program's boot options and append [option]#inst.xdriver=vesa# at the end of the command line. @@ -175,13 +175,13 @@ If specifying a custom video driver solves your problem, you should report it as ==== -Perform the installation using VNC:: If the above options fail, you can use a separate system to access the graphical installation over the network, using the _Virtual Network Computing_ (VNC) protocol. For details on installing using VNC, see <>. +Perform the installation using VNC:: If the above options fail, you can use a separate system to access the graphical installation over the network, using the _Virtual Network Computing_ (VNC) protocol. For details on installing using VNC, see xref:../advanced/VNC_Installations.adoc#chap-vnc-installations[Installing Using VNC]. ===== Serial Console Not Detected In some cases, attempting to install in text mode using a serial console will result in no output on the console. This happens on systems which have a graphics card, but no monitor connected. If [application]*Anaconda* detects a graphics card, it will attempt to use it for a display, even if no display is connected. -If you want to perform a text-based installation on a serial console, use the [option]#inst.text# and [option]#console=# boot options. See <> for more details. +If you want to perform a text-based installation on a serial console, use the [option]#inst.text# and [option]#console=# boot options. See xref:../advanced/Boot_Options.adoc#chap-anaconda-boot-options[Boot Options] for more details. [[sect-troubleshooting-problems-during-installation]] ==== Trouble During the Installation @@ -267,7 +267,7 @@ If you have performed an installation and cannot boot your system properly, you Some BIOS types do not support booting from RAID cards. After you finish the installation and reboot the system for the first time, a text-based screen showing the boot loader prompt (for example, `grub>`) and a flashing cursor may be all that appears. If this is the case, you must repartition your system and move your `/boot` partition and the boot loader outside the RAID array. The `/boot` partition and the boot loader must be on the same drive. -Once these changes have been made, you should be able to finish your installation and boot the system properly. For more information about partitioning, see <>. +Once these changes have been made, you should be able to finish your installation and boot the system properly. For more information about partitioning, see xref:Installing_Using_Anaconda.adoc#sect-installation-gui-storage-partitioning[Installation Destination]. [[sect-trouble-after-graphical-boot]] ===== Trouble With the Graphical Boot Sequence @@ -383,7 +383,7 @@ For additional information about [command]#df# and an explanation of the options [[sect-trouble-after-missing-ram]] ===== Is Your RAM Not Being Recognized? -In some cases the kernel does not recognize all of your memory (RAM), which causes the system to use less memory than is installed. You can find out how much RAM is being utilized using the [command]#free -m# command. If the displayed total amount of memory does not match your expectations, it is likely that at least one of your memory modules is faulty. On BIOS-based systems, you can use the [application]*Memtest86+* utility to test your system's memory - see <> for details. +In some cases the kernel does not recognize all of your memory (RAM), which causes the system to use less memory than is installed. You can find out how much RAM is being utilized using the [command]#free -m# command. If the displayed total amount of memory does not match your expectations, it is likely that at least one of your memory modules is faulty. On BIOS-based systems, you can use the [application]*Memtest86+* utility to test your system's memory - see xref:../advanced/Boot_Options.adoc#sect-boot-options-memtest[Loading the Memory (RAM) Testing Mode] for details. [NOTE] ==== diff --git a/en-US/install/WelcomeSpoke.adoc b/en-US/install/WelcomeSpoke.adoc index f434c21..8b768ca 100644 --- a/en-US/install/WelcomeSpoke.adoc +++ b/en-US/install/WelcomeSpoke.adoc @@ -16,7 +16,7 @@ The language you select on this screen will be used during the installation, and One language is pre-selected by default on top of the list. If network access is configured at this point (for example, if you booted from a network server instead of local media), the pre-selected language will be determined based on automatic location detection using the GeoIP module. Alternatively, if you used the [option]#inst.lang=# option on the boot command line or in your PXE server configuration, this language will be selected by default, but you will still be able to change it. -After you select your language and locale, click `Continue` to confirm your selection and proceed to <>. +After you select your language and locale, click `Continue` to confirm your selection and proceed to xref:Installing_Using_Anaconda.adoc#sect-installation-gui-installation-summary[Installation Summary]. [NOTE] ====