From d2e36c1c1d99b9a309c840e96f8ddc7278d74540 Mon Sep 17 00:00:00 2001 From: Brian (bex) Exelbierd Date: Nov 21 2017 21:45:11 +0000 Subject: Fixing Double Headers --- diff --git a/Common_Content/Feedback.adoc b/Common_Content/Feedback.adoc index d11787f..f438831 100644 --- a/Common_Content/Feedback.adoc +++ b/Common_Content/Feedback.adoc @@ -1,7 +1,7 @@ :experimental: -=== We want feedback +== We want feedback indexterm:[feedback,contact information for this manual] If you find errors or have suggestions for improvement, we want your advice. Submit a report in Bugzilla against the product `{PRODUCT}` and the component `{BOOKID}`. The following link automatically loads this information for you: {BZURL}. diff --git a/en-US/Downloading_Fedora.adoc b/en-US/Downloading_Fedora.adoc index ec0c5f3..2085bc0 100644 --- a/en-US/Downloading_Fedora.adoc +++ b/en-US/Downloading_Fedora.adoc @@ -3,7 +3,7 @@ include::en-US/entities.adoc[] [[chap-downloading-fedora]] -== Downloading Fedora += Downloading Fedora .Fedora Editions Fedora provides three primary Editions tailored for some specific use cases. link:++https://getfedora.org++[] offers Fedora Cloud for scalable infrastructure, Fedora Server for organizational infrastructure, and Fedora Workstation for the developer and desktop user. diff --git a/en-US/Introduction.adoc b/en-US/Introduction.adoc index d23e8f2..0f68e05 100644 --- a/en-US/Introduction.adoc +++ b/en-US/Introduction.adoc @@ -3,30 +3,30 @@ include::en-US/entities.adoc[] [[chap-introduction]] -== Introduction += Introduction This guide covers installation of Fedora, a Linux distribution built on free and open source software. This manual helps you install Fedora on desktops, laptops, and servers. The installation system is easy to use even if you lack previous knowledge of Linux or computer networks. If you select default options, Fedora provides a complete desktop operating system, including productivity applications, Internet utilities, and desktop tools. This document details the full range of installation options, including those that apply only in limited or unusual circumstances. Understanding of all topics described in this document is not necessary to successfully perform the installation in most cases. [[sect-introduction-background]] -=== Background +== Background [[sect-introduction-about]] -==== About Fedora +=== About Fedora To find out more about {PRODUCT}, visit the link:++http://fedoraproject.org/++[{PRODUCT} Project Website]. Other documentation describing additional topics related to {PRODUCT} is available at link:++http://docs.fedoraproject.org/++[{PRODUCT} Documentation]. Also see the link:++https://fedoraproject.org/wiki/Fedora_Project_Wiki++[{PRODUCT} Project Wiki]. [[sect-introduction-additional-help]] -==== Getting Additional Help +=== Getting Additional Help If you encounter any problems which are not described in documentation, you might get help from members of the community - developers, users, and others. There are many ways to get help: the Ask Fedora website, mailing lists, forums, or IRC. For a summary of available resources, see the link:++https://fedoraproject.org/wiki/Communicating_and_getting_help++[Communicating and Getting Help] page on the {PRODUCT} wiki. [[sect-introduction-about-document]] -=== About This Document +== About This Document [[sect-introduction-goals]] -==== Goals +=== Goals This guide helps a reader: @@ -46,6 +46,6 @@ This guide does not cover *use* of {PRODUCT}. To learn how to use an installed { ==== [[sect-introduction-target-audience]] -==== Target Audience +=== Target Audience This guide is intended for {PRODUCT} users of all levels of experience. However, it describes the installation process and its many options in far greater detail than most users are likely to require. You do not need to read and understand this entire document to install {PRODUCT} on a computer. This document is most likely to help experienced users perform advanced and unusual installations. diff --git a/en-US/Preface.adoc b/en-US/Preface.adoc index ee457a0..332613c 100644 --- a/en-US/Preface.adoc +++ b/en-US/Preface.adoc @@ -2,10 +2,10 @@ :experimental: include::en-US/entities.adoc[] -== Preface += Preface include::Common_Content/Feedback.adoc[] -=== Acknowledgments +== Acknowledgments Certain portions of this text first appeared in the [citetitle]_Red Hat Enterprise Linux Installation Guide_, copyright © 2014 Red Hat, Inc. and others, published by Red Hat at link:++https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/++[]. diff --git a/en-US/Revision_History.adoc b/en-US/Revision_History.adoc index 8f95b9c..31fd609 100644 --- a/en-US/Revision_History.adoc +++ b/en-US/Revision_History.adoc @@ -2,7 +2,7 @@ :experimental: [[appe-Publican-Revision_History]] -== Revision History += Revision History Note that revision numbers relate to the edition of this manual, not to version numbers of Fedora. diff --git a/en-US/advanced/Boot_Options.adoc b/en-US/advanced/Boot_Options.adoc index 6f9dc75..1c046e2 100644 --- a/en-US/advanced/Boot_Options.adoc +++ b/en-US/advanced/Boot_Options.adoc @@ -3,7 +3,7 @@ include::en-US/entities.adoc[] [[chap-anaconda-boot-options]] -=== Boot Options += Boot Options The [application]*Anaconda* installer includes a range of boot options for administrators, which modify the default behavior of the installation program by enabling or disabling certain functions. To use one or more boot options, you either have to boot from installation media and append these options at the boot menu (see xref:../install/Booting_the_Installation.adoc#sect-boot-menu[The Boot Menu]), or you must add them into your PXE server configuration file if you are booting from a network (see xref:Network_based_Installations.adoc#chap-pxe-server-setup[Setting Up an Installation Server]). @@ -25,17 +25,17 @@ 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 +== Configuring the Installation System at the Boot Menu The exact way to specify custom boot options is differs based on your system's architecture, firmware and the method you use to boot the installation. If you are booting from local media, you can specify options in the boot menu, before you begin the installation; if you are booting from a network using a PXE server, you must add boot options into the boot loader configuration file before you boot the installation system. For specific instructions, see xref:../install/Booting_the_Installation.adoc#sect-boot-menu[The Boot Menu] if you are booting from local media, and xref: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 +== Available Boot Options The following options are available in {PRODUCT}: [[sect-boot-options-sources]] -===== Specifying the Installation Source +=== Specifying the Installation Source [option]#inst.repo=#:: Specifies the installation source - that is, a location where the installation program can find the images and packages it requires. For example: + @@ -112,7 +112,7 @@ Normally, when you first enter the `Installation Summary` screen, the installer Using this option will leave the installation source configuration in an error state - you must manually specify a source in the `Installation Source` screen to proceed with the installation. Alternatively, you can use the [option]#inst.repo=# option described above to configure a specific source directly in the boot menu. [[sect-boot-options-kickstart]] -===== Kickstart Boot Options +=== Kickstart Boot Options [option]#inst.ks=#:: Gives the location of a Kickstart file to be used to automate the installation. Locations can be specified using any of the formats valid for [option]#inst.repo=#. See xref:Boot_Options.adoc#tabl-boot-options-sources[Installation Sources] for valid formats. + @@ -151,7 +151,7 @@ This can be useful when using [option]#inst.ks=http# to provision systems. ---- [[sect-boot-options-display]] -===== Console, Environment and Display Options +=== Console, Environment and Display Options [option]#console=#:: This kernel option specifies a device to be used as the primary console. For example, to use a console on the first serial port, use [option]#console=ttyS0#. This option should be used along with the [option]#inst.text# option. + @@ -212,7 +212,7 @@ During the installation, the `root` account has no password by default. You can ==== [[sect-boot-options-network]] -===== Network Boot Options +=== Network Boot Options Initial network initialization is handled by [application]*dracut*. This section only lists some of the more commonly used options; for a complete list, see the `dracut.cmdline(7)` man page. Additional information on networking is also available in the [citetitle]_{PRODUCT} Networking Guide_, available at link:++http://docs.fedoraproject.org/++[]. @@ -314,7 +314,7 @@ Using this option without any parameters will assume [option]#bond=bond0:eth0,et ---- [[sect-boot-options-advanced]] -===== Advanced Installation Options +=== Advanced Installation Options [option]#inst.multilib#:: Configure the system for multilib packages (that is, to allow installing 32-bit packages on a 64-bit x86 system) and install packages specified in this section as such. + @@ -353,7 +353,7 @@ By default, swap on zRAM is enabled on systems with 2 GB or less RAM, and disabl [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 +=== Enabling Remote Access Using VNC 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. @@ -388,7 +388,7 @@ Password: [option]#inst.vncconnect=#:: Connect to a listening `VNC` client at a specified host and port once the installation starts. The correct syntax is [option]#inst.vncconnect=pass:attributes[{blank}]_host_:pass:attributes[{blank}]_port_pass:attributes[{blank}]#. The _port_ parameter is optional - if you do not specify one, the installation program will use `5900`. [[sect-boot-options-debug]] -===== Debugging and Troubleshooting +=== 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 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`. @@ -401,7 +401,7 @@ Possible values for this option from the lowest to highest level are: `debug`, ` [option]#inst.virtiolog=#:: Specifies a `virtio` port (a character device at `/dev/virtio-ports/pass:attributes[{blank}]_name_pass:attributes[{blank}]`) to be used for forwarding logs. The default value is `org.fedoraproject.anaconda.log.0`pass:attributes[{blank}]; if this port is present, it will be used. [[sect-boot-options-deprecated]] -==== Deprecated Boot Options +== Deprecated Boot Options Options in this list are *deprecated*. They will still work, but there are other options which offer the same functionality and should be preferred. Using deprecated options is not recommended and they are expected to be removed in future releases. @@ -456,7 +456,7 @@ modprobe.blacklist=firewire_ohci ---- [[sect-boot-options-removed]] -==== Removed Boot Options +== Removed Boot Options The following options are removed. They were present in previous releases of {PRODUCT}, but they cannot be used anymore. @@ -489,10 +489,10 @@ The following options are removed. They were present in previous releases of {PR [option]#inst.dnf#:: Used to enable [application]*DNF* to handle package installation and dependency resolution in {PRODUCT} 21. [application]*DNF* is now used by default and this option has been replaced with [option]#inst.nodnf#, which reverts back to [application]*Yum*. [[sect-boot-options-maintenance]] -==== Using the Maintenance Boot Modes +== Using the Maintenance Boot Modes [[sect-boot-options-memtest]] -===== Loading the Memory (RAM) Testing Mode +=== Loading the Memory (RAM) Testing Mode Faults in memory (RAM) modules may cause your system to freeze or crash unpredictably. In some cases, memory faults may only cause errors with particular combinations of software. For this reason, you should test the memory of a computer before you install {PRODUCT} for the first time, even if it has previously run other operating systems. @@ -538,14 +538,14 @@ To halt the tests and reboot your computer, press the kbd:[Esc] key at any time. For more information about using [application]*Memtest86+*, see the official website at link:++http://www.memtest.org/++[]. A `README` file is also located in `/usr/share/doc/memtest86+-_version_pass:attributes[{blank}]/` on {PRODUCT} systems with the [package]*memtest86+* package installed. [[sect-boot-options-mediacheck]] -===== Verifying Boot Media +=== Verifying Boot Media You can test the integrity of an ISO-based installation source before using it to install {PRODUCT}. These sources include DVDs and ISO images stored on a local hard drive or NFS server. Verifying that the ISO images are intact before you attempt an installation helps to avoid problems that are often encountered during installation. To test the integrity of an ISO image, append the [option]#rd.live.check# to the boot loader command line. Note that this option is used automatically if you select the default installation option from the boot menu (`Test this media & install Fedora`). [[sect-boot-options-rescue]] -===== Booting Your Computer in Rescue Mode +=== Booting Your Computer in Rescue Mode You may boot a command-line Linux system from an installation disc without actually installing {PRODUCT} on the computer. This enables you to use the utilities and functions of a running Linux system to modify or repair already installed operating systems. diff --git a/en-US/advanced/Kickstart_Installations.adoc b/en-US/advanced/Kickstart_Installations.adoc index 60d5acb..eeaff40 100644 --- a/en-US/advanced/Kickstart_Installations.adoc +++ b/en-US/advanced/Kickstart_Installations.adoc @@ -3,14 +3,14 @@ include::en-US/entities.adoc[] [[chap-kickstart-installations]] -=== Automating the Installation with Kickstart += Automating the Installation with Kickstart Kickstart installations offer a means to automate the installation process, either partially or fully. Kickstart files contain answers to all questions normally asked by the installation program, such as what time zone do you want the system to use, how should the drives be partitioned or which packages should be installed. Providing a prepared Kickstart file when the installation begins therefore allows the you to perform the installation automatically, without need for any intervention from the user. This is especially useful when deploying {PRODUCT} on a large number of systems at once. All Kickstart scripts and the log files of their execution are stored in the `/tmp` directory to assist with debugging installation issues. [[sect-kickstart-howto]] -==== How to Perform a Kickstart Installation +== How to Perform a Kickstart Installation Kickstart installations can be performed using a local DVD, a local hard drive, or via NFS, FTP, HTTP, or HTTPS. @@ -27,7 +27,7 @@ To use Kickstart, you must: This chapter explains these steps in detail. [[sect-kickstart-file-create]] -===== Creating a Kickstart File +=== Creating a Kickstart File 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. @@ -55,7 +55,7 @@ The [command]#%packages#, [command]#%pre# and [command]#%post# sections must end * Omitting any required item results in the installation program prompting the user for an answer to the related item, just as the user would be prompted during a typical installation. Once the answer is given, the installation will continue. Note that if the system you are installing has no display, you will not be able to see the prompt, and the installation will appear to have failed. [[sect-kickstart-verify]] -===== Verifying the Kickstart File +=== Verifying the Kickstart File When creating or customizing your kickstart file, it is useful to verify that it is valid before attempting to use it in an installation. {PRODUCT} includes the [application]*ksvalidator* command line utility which can be used to do this. This tool is a part of the [package]*pykickstart* package. To install this package, execute the following command: @@ -83,7 +83,7 @@ Keep in mind that the validation tool has its limitations. The Kickstart file ca ==== [[sect-kickstart-making-available]] -===== Making the Kickstart File Available +=== Making the Kickstart File Available Once you create a Kickstart file, you can place it in one of the following locations: @@ -98,6 +98,6 @@ Normally, a Kickstart file is copied to removable media or a hard drive, or made 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 +=== 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 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 6ad1fb4..649f1bc 100644 --- a/en-US/advanced/Network_based_Installations.adoc +++ b/en-US/advanced/Network_based_Installations.adoc @@ -3,7 +3,7 @@ include::en-US/entities.adoc[] [[chap-pxe-server-setup]] -=== Setting Up an Installation Server += Setting Up an Installation Server [NOTE] ==== @@ -13,7 +13,7 @@ This appendix is intended for users with previous Linux experience. If you are a ==== [[pxe-overview]] -==== PXE Installation Overview +== PXE Installation Overview Preboot Execution Environment, or PXE, is a techonology that allows computers to boot directly from resources provided over the network. Installing Fedora over the network means you don't have to create media, and you can install to multiple computers or virtual machine simultaneously. The process involves a number of components and features working together to provide the resources required. @@ -38,7 +38,7 @@ A Fedora repository must be available for the installation. The example in this //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 [[pxe-dhcpd]] -==== DHCP Server Configuration +== DHCP Server Configuration //Needs adminition about static IP, reference out to Networking Guide. Example assumes 192.168.1.2 for server. @@ -104,7 +104,7 @@ next-server 192.168.1.2; ---- [[pxe-tftpd]] -==== Installing the tftp server +== Installing the tftp server .Installing the tftp server . Install the tftp server package. @@ -122,7 +122,7 @@ next-server 192.168.1.2; ---- [[pxe-bootloader]] -==== Providing and configuring bootloaders for PXE clients +== Providing and configuring bootloaders for PXE clients .Getting the bootloader files . Get the [package]*syslinux* bootloader for BIOS clients. @@ -224,7 +224,7 @@ menuentry 'Rescue installed system' --class fedora --class gnu-linux --class gn ---- [[pxe-kernel]] -==== Getting the kernel and initrd +== Getting the kernel and initrd .Downloading the kernel and initrd . Create a directory for the files. @@ -249,14 +249,14 @@ menuentry 'Rescue installed system' --class fedora --class gnu-linux --class gn ---- [[pxe-repositories]] -==== Providing repositories +== Providing repositories The examples in this section use the public Fedora mirrors as the package source. For faster installations, installing to many systems, or more isolated environments, you may wish to maintain a local repository. Fedora Infrastructure maintains instructions for a configuring a local mirror at link:++https://fedoraproject.org/wiki/Infrastructure/Mirroring++[]. The preferred method for providing repositories is via HTTP, and you can refer to the [citetitle]_Fedora System Administrator's Guide_, available at link:++http://docs.fedoraproject.org/++[], to configure `httpd`. [[sect-install-server-cobbler]] -==== Advanced network installations with Cobbler +== Advanced network installations with Cobbler For more complex environments, {PRODUCT} offers the [package]*cobbler* installation server. Tasks like managing kickstart configurtations, coordinating repositories, maintaining dns records, dhcp servers, and even puppet manifests are effectively automated by [package]*cobbler*. diff --git a/en-US/advanced/Upgrading_Your_Current_System.adoc b/en-US/advanced/Upgrading_Your_Current_System.adoc index 1764d7d..cfe61d6 100644 --- a/en-US/advanced/Upgrading_Your_Current_System.adoc +++ b/en-US/advanced/Upgrading_Your_Current_System.adoc @@ -3,7 +3,7 @@ include::en-US/entities.adoc[] [[chap-upgrading]] -=== Upgrading Your Current System += Upgrading Your Current System This chapter explains how to upgrade your existing {PRODUCT} installation to the current release. There are two basic ways to do so: @@ -19,6 +19,6 @@ Always back up your data before performing an upgrade or reinstalling your syste ==== [[sect-upgrading-fedora-manual-reinstall]] -==== Manual System Upgrade or Reinstallation +== 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 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 cdf7295..0550de4 100644 --- a/en-US/advanced/VNC_Installations.adoc +++ b/en-US/advanced/VNC_Installations.adoc @@ -3,7 +3,7 @@ include::en-US/entities.adoc[] [[chap-vnc-installations]] -=== Installing Using VNC += Installing Using VNC The graphical installation interface is the recommended method of installing {PRODUCT}. However, in some cases, accessing the graphical interface directly is difficult or impossible. Some systems lack the capability to connect a display and a keyboard, making VNC a necessity for manual (non-Kickstart) installations. @@ -12,7 +12,7 @@ To allow manual installations on _headless systems_ (systems without a directly This chapter provides instructions on activating VNC mode on the installation system and connecting to it using a VNC viewer. [[sect-vnc-installations-viewer]] -==== Installing a VNC Viewer +== Installing a VNC Viewer Performing a VNC installation requires a VNC viewer running on your workstation or another terminal computer. VNC viewers are available in the repositories of most Linux distributions; free VNC viewers are also available for other operating systems such as Windows. On Linux systems, use your package manager to search for a viewer for your distribution. @@ -41,7 +41,7 @@ Procedures in this chapter assume you are using [application]*TigerVNC* as your ==== [[sect-vnc-installations-anaconda-modes]] -==== Performing a VNC Installation +== Performing a VNC Installation The [application]*Anaconda* installation program offers two modes for VNC installation: _Direct mode_ and _Connect mode_. The modes differ in the way the connection between the server and viewer is established. After you successfully connect, the installation will progress the same way regardless of the mode you used. @@ -50,7 +50,7 @@ Direct Mode:: In this mode, [application]*Anaconda* is configured to start the Connect Mode:: In this mode, the VNC viewer is started on the remote system in _listening mode_. The VNC viewer waits for an incoming connection on a specified port. Then, [application]*Anaconda* is started and the host name/IP address and port number of the viewer are provided using a boot option or a Kickstart command. When the installation begins, the installation program establishes a connection with the listening VNC viewer using the specified host name/IP address and port number. Connect mode is therefore easier to use on systems with no local display or console, but it also may require additional preparation, because the viewer system must be able to accept incoming connections on the specified port, which usually requires changing firewall settings. [[sect-vnc-installations-choosing-mode]] -===== Choosing a VNC Installation Mode +=== Choosing a VNC Installation Mode * Visual and Interactive access to the system + @@ -63,7 +63,7 @@ Connect Mode:: In this mode, the VNC viewer is started on the remote system in ** If the remote system running the VNC viewer is not allowed incoming connections by a firewall, then you must use Direct Mode, or disable the firewall. Disabling a firewall may have security implications. [[sect-vnc-installations-direct-mode]] -===== Installing in VNC Direct Mode +=== Installing in VNC Direct Mode VNC Direct Mode is when the VNC viewer initiates a connection to the system being installed. [application]*Anaconda* will tell you when to initiate this connection. @@ -108,7 +108,7 @@ When the connection is successfully established, a new window will open on the s 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 +=== Installing in VNC Connect Mode VNC connect mode is when the system being installed initiates a connection to the VNC viewer running on a remote system. Before you start, make sure the remote system is configured to accept incoming connection on the port you want to use for VNC. The exact way to make sure the connection will not be blocked depends on your network and on your workstation's configuration. Information about configuring the firewall in {PRODUCT} is available in the [citetitle]_{PRODUCT} Security{nbsp}Guide_, available at link:++http://docs.fedoraproject.org/++[]. @@ -160,12 +160,12 @@ When the connection is successfully established, a new window will open on the s You can then proceed with xref:../install/Installing_Using_Anaconda.adoc#chap-installing-using-anaconda[Installing Using Anaconda]. [[sect-vnc-kickstart-considerations]] -==== 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 xref:../appendixes/Kickstart_Syntax_Reference.adoc#appe-kickstart-syntax-reference[Kickstart Syntax Reference]. [[sect-vnc-headless-considerations]] -==== Considerations for Headless Systems +== 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 xref:../appendixes/Kickstart_Syntax_Reference.adoc#appe-kickstart-syntax-reference[Kickstart Syntax Reference]. The general process for an interactive VNC installation is described below. diff --git a/en-US/appendixes/Disk_Partitions.adoc b/en-US/appendixes/Disk_Partitions.adoc index 3f3a89a..8c08834 100644 --- a/en-US/appendixes/Disk_Partitions.adoc +++ b/en-US/appendixes/Disk_Partitions.adoc @@ -3,7 +3,7 @@ include::en-US/entities.adoc[] [[appe-disk-partitions-overview]] -=== An Introduction to Disk Partitions += An Introduction to Disk Partitions [NOTE] ==== @@ -17,7 +17,7 @@ This section discusses basic disk concepts, disk repartitioning strategies, the 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 +== Hard Disk Basic Concepts Hard disks perform a very simple function - they store data and reliably retrieve it on command. @@ -31,7 +31,7 @@ xref:Disk_Partitions.adoc#figu-partitions-unused-drive[An Unused Disk Drive], sh image::partitions/unused-drive.png[Image of an unused disk drive.] [[sect-disk-partitions-file-systems]] -===== File Systems +=== File Systems To store data on a disk drive, it is necessary to _format_ the disk drive first. Formatting (usually known as "making a _file system_pass:attributes[{blank}]") writes information to the drive, creating order out of the empty space in an unformatted drive. @@ -66,7 +66,7 @@ As xref:Disk_Partitions.adoc#figu-partitions-drive-with-data[Disk Drive with Dat 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. [[sect-disk-partitions-basics]] -===== Partitions: Turning One Drive Into Many +=== Partitions: Turning One Drive Into Many Disk drives can be divided into _partitions_. Each partition can be accessed as if it was a separate disk. This is done through the addition of a _partition table_. @@ -144,7 +144,7 @@ The single partition in this example is labeled as `DOS`. This label shows the * |=== [[sect-disk-partitions-extended]] -===== Partitions Within Partitions - An Overview of Extended Partitions +=== Partitions Within Partitions - An Overview of Extended Partitions 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". @@ -158,7 +158,7 @@ image::partitions/extended-partitions.png[Image of a disk drive with an extended As this figure implies, there is a difference between primary and logical partitions - there can only be four primary partitions, but there is no fixed limit to the number of logical partitions that can exist. However, due to the way in which partitions are accessed in Linux, no more than 12 logical partitions should be defined on a single disk drive. [[sect-disk-partitioning-guid-partition-table]] -===== GUID Partition Table (GPT) +=== GUID Partition Table (GPT) GUID Partition Table (*GPT*) is a newer partitioning scheme based on using Globally Unique Identifiers (*GUID*). *GPT* was developed to cope with limitations of the *MBR* partition table, especially with the limited maximum addressable storage space of a disk. Unlike *MBR*, which is unable to address storage space larger than 2.2 terabytes, *GPT* can be used with hard disks larger than this; the maximum addressable disk size is 2.2 zettabytes. In addition, *GPT* by default supports creating up to 128 primary partitions. This number could be extended by allocating more space to the partition table. @@ -182,7 +182,7 @@ There must be a BIOS boot partition for the boot loader to be installed successf ==== [[sect-disk-partitions-making-room]] -==== Strategies for Disk Repartitioning +== Strategies for Disk Repartitioning There are several different ways that a disk can be repartitioned. This section discusses the following possible approaches: @@ -202,7 +202,7 @@ Keep in mind that the following illustrations are simplified in the interest of ==== [[sect-disk-partitions-using-free-space]] -===== Using Unpartitioned 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. xref:Disk_Partitions.adoc#figu-partitions-unused-space[Disk Drive with Unpartitioned Free Space], shows what this might look like. @@ -218,7 +218,7 @@ An unused hard disk also falls into this category. The only difference is that * 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 +=== Using Space from an Unused Partition 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. @@ -232,7 +232,7 @@ In the above example, `1` represents an unused partition and `2` represents real In this situation, you can use the space allocated to the unused partition. You first must delete the partition and then create the appropriate Linux partition(s) in its place. You can delete the unused partition and manually create new partitions during the installation process. [[sect-disk-partitions-active-partition]] -===== Using Free Space from an Active Partition +=== Using Free Space from an Active Partition This is the most common situation. It is also, unfortunately, the hardest to handle. The main problem is that, even if you have enough free space, it is presently allocated to a partition that is already in use. If you purchased a computer with pre-installed software, the hard disk most likely has one massive partition holding the operating system and data. @@ -276,7 +276,7 @@ While the process of non-destructive repartitioning is rather straightforward, t Each step is described further in more detail. [[sect-disk-partitions-compress-data]] -====== Compress Existing Data +==== Compress Existing Data As the following figure shows, the first step is to compress the data in your existing partition. The reason for doing this is to rearrange the data such that it maximizes the available free space at the "end" of the partition. @@ -290,7 +290,7 @@ In the above example, `1` represents before and `2` represents after. This step is crucial. Without it, the location of the data could prevent the partition from being resized to the extent desired. Note also that, for one reason or another, some data cannot be moved. If this is the case (and it severely restricts the size of your new partition(s)), you may be forced to destructively repartition your disk. [[sect-disk-partitions-resize-existing]] -====== Resize the Existing Partition +==== Resize the Existing 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. @@ -304,7 +304,7 @@ In the above example, `1` represents before and `2` represents after. It is important to understand what the resizing software you use does with the newly freed space, so that you can take the appropriate steps. In the case illustrated here, it would be best to delete the new DOS partition and create the appropriate Linux partition(s). [[sect-disk-partitions-create-new]] -====== Create new partition(s) +==== 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. xref:Disk_Partitions.adoc#figu-partitions-final-configuration[Disk Drive with Final Partition Configuration], shows this being done. @@ -316,12 +316,12 @@ image::partitions/nondestruct-fin.png[Image of a disk drive with final partition In the above example, `1` represents before and `2` represents after. [[sect-partitioning-naming-schemes-and-mount-points]] -==== Partition Naming Schemes and Mount Points +== Partition Naming Schemes and Mount Points A common source of confusion for users unfamiliar with Linux is the matter of how partitions are used and accessed by the Linux operating system. In DOS/Windows, it is relatively simple: Each partition gets a "drive letter." You then use the correct drive letter to refer to files and directories on its corresponding partition. This is entirely different from how Linux deals with partitions and, for that matter, with disk storage in general. This section describes the main principles of partition naming scheme and the way how partitions are accessed in {PRODUCT}. [[sect-disk-partitions-naming-scheme]] -===== Partition Naming Scheme +=== Partition Naming Scheme Linux uses a naming scheme that is file-based, with file names in the form of `/dev/pass:attributes[{blank}]_xxyN_pass:attributes[{blank}]`. @@ -343,7 +343,7 @@ Even if your system can identify and refer to all types of disk partitions, it m ==== [[sect-disk-partitions-mount-points]] -===== Disk Partitions and Mount Points +=== Disk Partitions and Mount Points Each partition is used to form part of the storage necessary to support a single set of files and directories. This is done by associating a partition with a directory through a process known as _mounting_. Mounting a partition makes its storage available starting at the specified directory (known as a _mount point_). @@ -352,7 +352,7 @@ For example, if partition `/dev/sda5` is mounted on `/usr/`, that would mean tha Continuing the example, it is also possible that one or more directories below `/usr/` would be mount points for other partitions. For instance, a partition (say, `/dev/sda7`) could be mounted on `/usr/local/`, meaning that `/usr/local/man/whatis` would then reside on `/dev/sda7` rather than `/dev/sda5`. [[sect-disk-partitions-how-many]] -===== How Many Partitions? +=== How Many Partitions? At this point in the process of preparing to install {PRODUCT}, you should give some consideration to the number and size of the partitions to be used by your new operating system. However, there is no one right answer to this question. It depends on your needs and requirements. diff --git a/en-US/appendixes/Kickstart_Syntax_Reference.adoc b/en-US/appendixes/Kickstart_Syntax_Reference.adoc index 7a0df60..c0c9bc2 100644 --- a/en-US/appendixes/Kickstart_Syntax_Reference.adoc +++ b/en-US/appendixes/Kickstart_Syntax_Reference.adoc @@ -3,7 +3,7 @@ include::en-US/entities.adoc[] [[appe-kickstart-syntax-reference]] -=== Kickstart Syntax Reference += Kickstart Syntax Reference 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]. @@ -49,12 +49,12 @@ In the following sections, if an option is followed by an equals mark (`=`), a v ==== [[sect-kickstart-commands-installation]] -==== Installation Methods and Sources +== Installation Methods and Sources The following commands control the way Fedora will be installed. [[sect-kickstart-commands-device]] -===== device (optional) - Install Extra Device Drivers +=== device (optional) - Install Extra Device Drivers On most PCI systems, the installation program will automatically detect Ethernet and SCSI cards. However, on older systems and some PCI systems, Kickstart requires a hint to find the proper devices. The [command]#device# command, which tells the installation program to install extra modules, uses the following format: @@ -72,7 +72,7 @@ device i2c_piix4 --opts="aic152x=0x340 io=11" ---- [[sect-kickstart-commands-driverdisk]] -===== driverdisk (optional) - Use a Driver Disk +=== driverdisk (optional) - Use a Driver Disk Driver disks can be used during Kickstart installations to provide additional drivers not included by default. You must copy the driver disks's contents to the root directory of a partition on the system's hard drive. Then, you must use the [command]#driverdisk# command to specify that the installation program should look for a driver disk and its location. @@ -108,7 +108,7 @@ _partition_:: Search for the driver disk image on a local partition. Replace _p [option]#--biospart=#:: BIOS partition containing the driver disk (for example, `82p2`). [[sect-kickstart-commands-install]] -===== install (required) - Configure Installation Method +=== install (required) - Configure Installation Method The default installation mode. You must specify the type of installation from `cdrom`, `harddrive`, `nfs`, `liveimg`, or `url`. The [command]#install# command and the installation method command must be on separate lines. For example: @@ -195,12 +195,12 @@ This command also supports installation from tar archives of the root file syste [option]#--noverifyssl#::: Disable SSL verification when connecting to an `HTTPS` server. [[sect-kickstart-commands-mediacheck]] -===== mediacheck (optional) - Verify Installation Media Integrity +=== 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 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 +=== ostreesetup (optional) - Install from an OSTree Used for OSTree installations. See link:++https://wiki.gnome.org/action/show/Projects/OSTree++[] for more information about OSTree. Available options are: @@ -215,7 +215,7 @@ Used for OSTree installations. See link:++https://wiki.gnome.org/action/show/Pro [option]#--nogpg#:: Disable GPG key verification (optional). [[sect-kickstart-commands-repo]] -===== repo (optional) - Configure Additional Repositories +=== repo (optional) - Configure Additional Repositories Configures additional [application]*DNF* repositories that may be used as sources for package installation. This command can be used multiple times in a single Kickstart file. @@ -249,12 +249,12 @@ Repositories used for installation must be stable. The installation may fail if [option]#--noverifyssl#:: Disable SSL verification when connecting to an `HTTPS` server. [[sect-kickstart-commands-storage]] -==== Storage and Partitioning +== Storage and Partitioning Commands in this section are used to determine your system's storage options and partitioning. [[sect-kickstart-commands-autopart]] -===== autopart (optional) - Automatic Partitioning +=== autopart (optional) - Automatic Partitioning Automatically creates partitions: a root (`/`) partition (1 GB or larger), a `swap` partition, and an appropriate `/boot` partition for the architecture. On large enough drives (50{nbsp}GB and larger), this also creates a `/home` partition. @@ -292,7 +292,7 @@ The created partitioning scheme will follow the recommended scheme described at [option]#--cipher=#:: Specifies which type of encryption will be used if the [application]*Anaconda* default `aes-xts-plain64` is not satisfactory. You must use this option together with the [option]#--encrypted# option; by itself it has no effect. Available types of encryption are listed in the [citetitle]_Fedora Security Guide_, available at link:++http://docs.fedoraproject.org/++[]. Using either `aes-xts-plain64` or `aes-cbc-essiv:sha256` is strongly recommended. [[sect-kickstart-commands-bootloader]] -===== bootloader (required) - Configure Boot Loader +=== bootloader (required) - Configure Boot Loader Specifies how the boot loader should be installed. @@ -385,7 +385,7 @@ To generate an encrypted password, use the [command]#grub2-mkpasswd-pbkdf2# comm [option]#--nombr#:: Install the boot loader configuration and support files, but do not modify the MBR. [[sect-kickstart-commands-btrfs]] -===== btrfs (optional) - Create Btrfs Volume or Subvolume +=== btrfs (optional) - Create Btrfs Volume or Subvolume Create a Btrfs volume or subvolume. For a volume, the syntax is: @@ -445,7 +445,7 @@ The following example shows how to create a Btrfs volume from member partitions ==== [[sect-kickstart-commands-clearpart]] -===== clearpart (optional) - Remove All Existing Partitions +=== clearpart (optional) - Remove All Existing Partitions Removes partitions from the system, prior to creation of new partitions. By default, no partitions are removed. @@ -524,7 +524,7 @@ Using the [command]#clearpart --all# command in a Kickstart file to remove all e ==== [[sect-kickstart-commands-fcoe]] -===== fcoe (optional) - Configure Fibre Channel Over Ethernet Devices +=== fcoe (optional) - Configure Fibre Channel Over Ethernet Devices Specify which FCoE devices should be activated automatically in addition to those discovered by _Enhanced Disk Drive Services_ (EDD). @@ -540,7 +540,7 @@ Specify which FCoE devices should be activated automatically in addition to thos [option]#--autovlan#:: Discover VLANs automatically. [[sect-kickstart-commands-ignoredisk]] -===== ignoredisk (optional) - Ignore Specified Disks +=== ignoredisk (optional) - Ignore Specified Disks Causes the installation program to ignore the specified disks. This is useful if you use autopartition and want to be sure that some disks are ignored. For example, without [command]#ignoredisk#, attempting to deploy on a SAN cluster the Kickstart would fail, as the installation program detects passive paths to the SAN that return no partition table. @@ -609,7 +609,7 @@ To include a multipath device that uses LVM: [option]#--interactive#:: Allows you to manually navigate the advanced storage screen. [[sect-kickstart-commands-iscsi]] -===== iscsi (optional) - Configure iSCSI Devices +=== 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 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. @@ -639,7 +639,7 @@ If you must use the [command]#iscsi# command, make sure that networking is activ [option]#--reverse-password=#:: Password that corresponds with the user name specified for the initiator. [[sect-kickstart-commands-iscsiname]] -===== iscsiname (optional) - Assign Name to iSCSI Device +=== iscsiname (optional) - Assign Name to iSCSI Device 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#. @@ -649,7 +649,7 @@ Assigns a name to an iSCSI node specified by the [command]#iscsi# command (xref: ---- [[sect-kickstart-commands-logvol]] -===== logvol (optional) - Create LVM Logical Volume +=== logvol (optional) - Create LVM Logical Volume Create a logical volume for Logical Volume Management (LVM) with the syntax: @@ -785,7 +785,7 @@ Create one or more partitions first using xref:Kickstart_Syntax_Reference.adoc#s ---- [[sect-kickstart-commands-part]] -===== part (required) - Create Physical Partition +=== part (required) - Create Physical Partition Creates a partition on the system. @@ -958,7 +958,7 @@ This option can only be used for partitions which result in a file system such a [option]#--backuppassphrase#:: Add a randomly-generated passphrase to each encrypted partition. Store these passphrases in separate files in `/root`, encrypted using the X.509 certificate specified with [option]#--escrowcert#. This option is only meaningful if [option]#--escrowcert# is specified. [[sect-kickstart-commands-raid]] -===== raid (optional) - Create Software RAID +=== raid (optional) - Create Software RAID Assembles a software RAID device. This command is of the form: @@ -1035,7 +1035,7 @@ The following example shows how to create a RAID level 1 partition for `/`, and ==== [[sect-kickstart-commands-reqpart]] -===== reqpart (optional) - Create Required Partitions +=== reqpart (optional) - Create Required Partitions Automatically create partitions required by your hardware platform. These include a `/boot/efi` for x86_64 and Aarch64 systems with UEFI firmware, `biosboot` for x86_64 systems with BIOS firmware and GPT (GUID Partition Table), and `PRePBoot` for IBM Power Systems. @@ -1054,7 +1054,7 @@ This command can not be used together with [command]#autopart#, because [command [option]#--add-boot#:: Create a separate `/boot` partition in addition to the platform-specific partition created by the base command. [[sect-kickstart-commands-volgroup]] -===== volgroup (optional) - Create LVM Volume Group +=== volgroup (optional) - Create LVM Volume Group Creates a Logical Volume Management (LVM) volume group. @@ -1096,7 +1096,7 @@ Create one or more partitions first using xref:Kickstart_Syntax_Reference.adoc#s ---- [[sect-kickstart-commands-zerombr]] -===== zerombr (optional) - Reinitialize Partition Tables +=== zerombr (optional) - Reinitialize Partition Tables If [command]#zerombr# is specified, any invalid partition tables found on disks are initialized. This destroys all of the contents of disks with invalid partition tables. This command is required when performing an unattended installation on a system with previously initialized disks. @@ -1112,7 +1112,7 @@ If [command]#zerombr# is not specified and there is at least one unformatted DAS ==== [[sect-kickstart-commands-zfcp]] -===== zfcp (optional) - Configure Fibre Channel Device +=== zfcp (optional) - Configure Fibre Channel Device Define a Fibre channel device. This option only applies on IBM System{nbsp}z. All of the options described below must be specified. @@ -1135,12 +1135,12 @@ For example: ---- [[sect-kickstart-commands-network-configuration]] -==== Network Configuration +== Network Configuration Commands in this chapter are used for network configuration. [[sect-kickstart-commands-firewall]] -===== firewall (optional) - Configure Firewall +=== firewall (optional) - Configure Firewall Specify the firewall configuration for the installed system. @@ -1179,7 +1179,7 @@ _incoming_:: Replace with one or more of the following to allow the specified s Valid options are anything recognized by the [application]*firewall-offline-cmd* program in the [package]*firewalld* package. If `firewalld` is running, [command]#firewall-cmd --get-services# will provide a list of known service names. [[sect-kickstart-commands-network]] -===== network (optional) - Configure Network Interfaces +=== network (optional) - Configure Network Interfaces Configures network information for the target system and activates network devices in the installation environment. The device specified in the first [command]#network# command is activated automatically. Activation of the device can be also explicitly required by the [option]#--activate# option. @@ -1362,12 +1362,12 @@ See also the [option]#--teamconfig=# option. [option]#--bridgeopts=#:: An optional comma-separated list of parameters for the bridged interface. Available values are `stp`, `priority`, `forward-delay`, `hello-time`, `max-age`, and `ageing-time`. For information about these parameters, see the [citetitle]_bridge setting_ table in the `nm-settings(5)` man page or at link:++https://developer.gnome.org/NetworkManager/0.9/ref-settings.html++[]. Also see the [citetitle]_{PRODUCT} Networking Guide_, available at link:++http://docs.fedoraproject.org/++[], for general information about network bridging. [[sect-kickstart-commands-environment]] -==== Console and Environment +== Console and Environment The following commands control the environment of the system after the installation finishes - language, keyboard layouts, or the graphical interface. [[sect-kickstart-commands-keyboard]] -===== keyboard (optional) - Configure Keyboard Layouts +=== keyboard (optional) - Configure Keyboard Layouts Sets one or more available keyboard layouts for the system. @@ -1393,7 +1393,7 @@ keyboard --xlayouts=us,'cz (qwerty)' --switch=grp:alt_shift_toggle ---- [[sect-kickstart-commands-lang]] -===== lang (optional) - Configure Language During Installation +=== lang (optional) - Configure Language During Installation Sets the language to use during installation and the default language to use on the installed system. @@ -1413,7 +1413,7 @@ lang en_US --addsupport=cs_CZ,de_DE,en_UK ---- [[sect-kickstart-commands-services]] -===== services (optional) - Configure Services +=== services (optional) - Configure Services Modifies the default set of services that will run under the default [application]*systemd* target. The list of disabled services is processed before the list of enabled services - therefore, if a service appears on both lists, it will be enabled. @@ -1441,7 +1441,7 @@ The above will disable only the `auditd` service. To disable all four services, [option]#--enabled=#:: Enable the services given in the comma separated list. [[sect-kickstart-commands-skipx]] -===== skipx (optional) - Do Not Configure X Window System +=== skipx (optional) - Do Not Configure X Window System If present, [application]*X* will not be configured on the installed system. @@ -1453,7 +1453,7 @@ If you install a display manager among your package selection options, this pack ==== [[sect-kickstart-commands-timezone]] -===== timezone (optional) - Configure Time Zone +=== timezone (optional) - Configure Time Zone Sets the system time zone to _timezone_. To view a list of available time zones, use the [command]#timedatectl list-timezones# command. @@ -1471,7 +1471,7 @@ Every option, including actually specifying a time zone, is optional starting wi [option]#--ntpservers=#:: Specify a list of NTP servers to be used as a comma-separated list without spaces. [[sect-kickstart-commands-xconfig]] -===== xconfig (optional) - Configure X Window System +=== xconfig (optional) - Configure X Window System Configures the [application]*X Window System*. If you install the [application]*X Window System* with a Kickstart file that does not include the [command]#xconfig# command, you must provide the [application]*X* configuration manually during installation. @@ -1482,12 +1482,12 @@ Do not use this command in a Kickstart file that does not install the [applicati [option]#--startxonboot#:: Use a graphical login on the installed system. [[sect-kickstart-commands-users-groups]] -==== Users, Groups and Authentication +== Users, Groups and Authentication The commands below are used to control user accounts, groups, and related areas. [[sect-kickstart-commands-auth]] -===== auth or authconfig (optional) - Configure Authentication +=== auth or authconfig (optional) - Configure Authentication Sets up the authentication options for the system using the [command]#authconfig# command, which can also be run on a command line after the installation finishes. See the `authconfig(8)` manual page and the [command]#authconfig --help# command for more details. Passwords are shadowed by default. @@ -1545,7 +1545,7 @@ To look up users and groups by number, make `501.uid` a CNAME for `jim.passwd`, [option]#--passalgo=#:: Specify [option]#sha256# to set up the SHA-256 hashing algorithm or [option]#sha512# to set up the SHA-512 hashing algorithm. [[sect-kickstart-commands-group]] -===== group (optional) - Create User Group +=== group (optional) - Create User Group Creates a new user group on the system. If a group with the given name or GID already exists, this command will fail. In addition, the [command]#user# command can be used to create a new group for the newly created user. @@ -1559,7 +1559,7 @@ Creates a new user group on the system. If a group with the given name or GID al [option]#--gid=#:: The group ID (GID). If not provided, defaults to the next available non-system GID. [[sect-kickstart-commands-pwpolicy]] -===== pwpolicy (optional) - Change the Default Password Policy +=== pwpolicy (optional) - Change the Default Password Policy This command can be used to set custom requirements (policy) such as length and strength for passwords set during the installation - the `root` password, user passwords and LUKS (disk encryption) password. @@ -1609,7 +1609,7 @@ An example use of the [command]#pwpolicy# command is below: ---- [[sect-kickstart-commands-realm]] -===== realm (optional) - Join an Active Directory or IPA Domain +=== realm (optional) - Join an Active Directory or IPA Domain Join an Active Directory or IPA domain. For more information about this command, see the [command]#join# section of the `realm(8)` man page. @@ -1631,7 +1631,7 @@ Join an Active Directory or IPA domain. For more information about this command, [option]#--membership-software=#:: Use this software when joining the realm. Valid values include `samba` and `adcli`. Not all realms support all values. By default, the membership software is chosen automatically. [[sect-kickstart-commands-rootpw]] -===== rootpw (required) - Set Root Password +=== rootpw (required) - Set Root Password Sets the system's root password to the _password_ argument. @@ -1654,7 +1654,7 @@ This will generate a SHA512 crypt of your password using your provided salt. [option]#--lock#:: If this option is present, the root account is locked by default. This means that the root user will not be able to log in from the console. [[sect-kickstart-commands-selinux]] -===== selinux (optional) - Configure SELinux +=== selinux (optional) - Configure SELinux Sets the state of SELinux on the installed system. The default policy is `enforcing`. For more information regarding SELinux in {PRODUCT}, see the [citetitle]_{PRODUCT} SELinux User's and Administrator's Guide_, available at link:++http://docs.fedoraproject.org/++[]. @@ -1670,7 +1670,7 @@ Sets the state of SELinux on the installed system. The default policy is `enforc [option]#--disabled#:: Disables SELinux completely. [[sect-kickstart-commands-sshkey]] -===== sshkey (optional) - Add an Authorized SSH Key +=== 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 xref:Kickstart_Syntax_Reference.adoc#sect-kickstart-commands-user[user (optional) - Create User Account]. @@ -1683,7 +1683,7 @@ The _ssh_key_ must be a full `SSH` key fingerprint, and it must be enclosed in q [option]#--username=#:: The name of the user account to which you want to install the `SSH` key. [[sect-kickstart-commands-user]] -===== user (optional) - Create User Account +=== user (optional) - Create User Account Creates a new user on the system. @@ -1722,12 +1722,12 @@ This will generate a SHA512 crypt of your password using your provided salt. [option]#--gid=#:: The _GID_ (Group ID) to be used for the user's default group. If not provided, this defaults to the next available non-system group ID. [[sect-kickstart-commands-installation-environment]] -==== Installation Environment +== Installation Environment The following commands control how the system will behave during the installation. [[sect-kickstart-commands-autostep]] -===== autostep (optional) - Go Through Every Screen +=== autostep (optional) - Go Through Every Screen Normally, Kickstart installations skip unnecessary screens. This option makes the installation program step through every screen, displaying each briefly. This option should not be used when deploying a system because it may disrupt package installation. @@ -1741,7 +1741,7 @@ Normally, Kickstart installations skip unnecessary screens. This option makes th Each screen is only captured right before the installer switches to the next one. This is important, because if you do not use all required Kickstart options and the installation therefore does not begin automatically, you can go to the screens which were not automatically configured, perform any configuration you want. Then, when you press `Done` to continue, the screen will be captured including the configuration you just provided. [[sect-kickstart-commands-cmdline]] -===== cmdline (optional) - Perform Installation in Command Line Mode +=== cmdline (optional) - Perform Installation in Command Line Mode Perform the installation in a completely non-interactive command line mode. Any prompts for interaction halts the install. This mode is useful on IBM System{nbsp}z systems with the x3270 terminal. @@ -1753,7 +1753,7 @@ For a fully automatic installation, you must either specify one of the available ==== [[sect-kickstart-commands-graphical]] -===== graphical (optional) - Perform Installation in Graphical Mode +=== graphical (optional) - Perform Installation in Graphical Mode Perform the installation in graphical mode. This is the default. This command takes no options. @@ -1765,7 +1765,7 @@ For a fully automatic installation, you must either specify one of the available ==== [[sect-kickstart-commands-logging]] -===== logging (optional) - Configure Error Logging During Installation +=== logging (optional) - Configure Error Logging During Installation Controls the error logging of [application]*Anaconda* during installation. It has no effect on the installed system. @@ -1781,7 +1781,7 @@ Controls the error logging of [application]*Anaconda* during installation. It ha [option]#--level=#:: Specify the minimum level of messages that appear on virtual console 3 (`tty3`). This only affects messages printed to the console; log files will contain messages of all levels. Possible values are `debug`, `info`, `warning`, `error`, or `critical`. [[sect-kickstart-commands-rescue]] -===== rescue (optional) - Rescue Mode +=== rescue (optional) - Rescue Mode Automatically enters the installation program's rescue mode. This gives you a chance to repair the system in case of any problems. @@ -1793,7 +1793,7 @@ Automatically enters the installation program's rescue mode. This gives you a ch [option]#--nomount# or [option]#--romount#:: Controls how the installed system is mounted in the rescue environment. By default, the installation program will find your system and mount it in read-write mode, telling you where it has performed this mount. You may optionally choose to not mount anything (the [option]#--nomount# option) or mount in read-only mode (the [option]#--romount# option). Only one of these two options may be used. [[sect-kickstart-commands-sshpw]] -===== sshpw (optional) - Restrict ssh Access During Installation +=== sshpw (optional) - Restrict ssh Access During Installation During the installation, you can interact with the installation program and monitor its progress over an `SSH` connection. Use the [command]#sshpw# command to create temporary accounts through which to log on. Each instance of the command creates a separate account that exists only in the installation environment. These accounts are not transferred to the installed system. @@ -1837,7 +1837,7 @@ This will generate a SHA512 crypt of your password using your provided salt. [option]#--lock#:: If this option is present, this account is locked by default. This means that the user will not be able to log in from the console. [[sect-kickstart-commands-text]] -===== text (optional) - Perform Installation in Text Mode +=== text (optional) - Perform Installation in Text Mode Perform the Kickstart installation in text mode. Kickstart installations are performed in graphical mode by default. @@ -1849,12 +1849,12 @@ For a fully automatic installation, you must either specify one of the available ==== [[sect-kickstart-commands-unsupported_hardware]] -===== unsupported_hardware (optional) - Suppress Unsupported Hardware Alerts +=== unsupported_hardware (optional) - Suppress Unsupported Hardware Alerts Suppress the `Unsupported Hardware Detected` alert. If this command is not included and unsupported hardware is detected, the installation will stall at this alert. [[sect-kickstart-commands-vnc]] -===== vnc (optional) - Configure VNC Access +=== vnc (optional) - Configure VNC Access Allows the graphical installation to be viewed remotely via VNC. This method is usually preferred over text mode, as there are some size and language limitations in text installations. With no additional options, this command will start a VNC server on the installation system with no password and will display the details required to connect to it. @@ -1872,7 +1872,7 @@ For more information about VNC installations, including instructions on how to c [option]#--password=#:: Set a password which must be provided to connect to the VNC session. This is optional, but recommended. [[sect-kickstart-commands-after]] -==== After the Installation +== After the Installation This section contains commands which control the system's behavior immediately after the installation finishes. @@ -1912,7 +1912,7 @@ If you enable [application]*Kdump* and do not specify the [option]#--reserve-mb= [option]#--enablefadump#:: Enable firmware-assisted dumping on systems which allow it (notably IBM Power{nbsp}Systems servers). [[sect-kickstart-commands-firstboot]] -===== firstboot (optional) - Enable or Disable Initial Setup +=== 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 xref:../install/After_Installation.adoc#sect-initial-setup[Initial Setup]. @@ -1928,14 +1928,14 @@ Determine whether the [application]*Initial Setup* application starts the first [option]#--reconfig#:: [application]*Initial Setup* will start after the reboot in reconfiguration mode. This mode enables the language, mouse, keyboard, root password, security level, time zone and networking configuration options in addition to the default ones. [[sect-kickstart-commands-halt]] -===== halt (optional) - Halt System After Installation +=== halt (optional) - Halt System After Installation Halt the system after the installation has successfully completed. This is similar to a manual installation, where after the installation finishes, the installer displays a message and waits for the user to press a key before rebooting. During a Kickstart installation, if no completion method is specified, this option is used as the default. For other completion methods, see the [command]#poweroff#, [command]#reboot#, and [command]#shutdown# commands. [[sect-kickstart-commands-poweroff]] -===== poweroff (optional) - Power Off After Installation +=== poweroff (optional) - Power Off After Installation Shut down and power off the system after the installation has successfully completed. @@ -1949,7 +1949,7 @@ The [command]#poweroff# command is highly dependent on the system hardware in us For other completion methods, see the [command]#halt#, [command]#reboot#, and [command]#shutdown# Kickstart commands. [[sect-kickstart-commands-reboot]] -===== reboot (optional) - Reboot After Installation +=== 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 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. @@ -1967,7 +1967,7 @@ Use of the [command]#reboot# command *may* result in an endless installation loo [option]#--kexec#:: Use this option to reboot into the new system using the `kexec` kernel switching mechanism instead of a full reboot, bypassing the BIOS/Firmware and boot loader. [[sect-kickstart-commands-shutdown]] -===== shutdown (optional) - Shut Down After Installation +=== shutdown (optional) - Shut Down After Installation Shut down the system after the installation has successfully completed. @@ -2250,10 +2250,10 @@ with [option]#--nochroot#: 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 +== Example Kickstart Configurations [[sect-kickstart-example-advanced-partitioning]] -===== Advanced Partitioning Example +=== Advanced Partitioning Example The following is an integrated example showing the [command]#clearpart#, [command]#zerombr#, [command]#part#, [command]#raid#, [command]#volgroup#, and [command]#logvol# Kickstart options in action: @@ -2311,7 +2311,7 @@ The above example uses identifiers `hda` and `hdc` to identify disk drives. You ==== [[sect-kickstart-example-pre-script]] -===== Example Pre-installation Script +=== Example Pre-installation Script The following is an example [command]#%pre# section: @@ -2370,7 +2370,7 @@ The partitioning commands selected in the script will be used. ==== [[sect-kickstart-example-post-script]] -===== Example Post-installation Script +=== Example Post-installation Script The following is an example [command]#%post# section: diff --git a/en-US/appendixes/Understanding_LVM.adoc b/en-US/appendixes/Understanding_LVM.adoc index 4a82193..70f97a1 100644 --- a/en-US/appendixes/Understanding_LVM.adoc +++ b/en-US/appendixes/Understanding_LVM.adoc @@ -2,7 +2,7 @@ :experimental: [[appe-lvm-overview]] -=== Understanding LVM += Understanding LVM LVM (Logical Volume Management) partitions provide a number of advantages over standard partitions. LVM partitions are formatted as _physical volumes_. One or more physical volumes are combined to form a _volume group_. Each volume group's total storage is then divided into one or more _logical volumes_. The logical volumes function much like standard partitions. They have a file system type, such as `ext4`, and a mount point. diff --git a/en-US/install/After_Installation.adoc b/en-US/install/After_Installation.adoc index d079550..6467d0b 100644 --- a/en-US/install/After_Installation.adoc +++ b/en-US/install/After_Installation.adoc @@ -3,7 +3,7 @@ include::en-US/entities.adoc[] [[chap-after-installation]] -=== After the Installation += After the Installation This chapter describes the initial setup tools which open after you finish the installation, reboot the system, and log in for the first time. @@ -14,7 +14,7 @@ Both of these tools will allow you to configure user-specific settings which hav include::en-US/install/InitialSetupHub.adoc[] [[sect-gnome-initial-setup]] -==== GNOME Initial Setup +== GNOME Initial Setup The [application]*GNOME Initial Setup* utility will be displayed after you log in for the first time with any user account, as long as your first login is in the [application]*GNOME* desktop environment. @@ -27,7 +27,7 @@ This utility allows you to configure several user-specific settings, such as sys After you finish configuring all screens, click `Start using Fedora` to exit the utility. After that, the `Getting Started` page from GNOME help will be displayed, and you can either browse the help content, or close it and start using your desktop. [[sect-common-post-installation-tasks]] -==== Common Post-installation Tasks +== Common Post-installation Tasks 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. diff --git a/en-US/install/Booting_the_Installation.adoc b/en-US/install/Booting_the_Installation.adoc index 7f75820..3ccb4d4 100644 --- a/en-US/install/Booting_the_Installation.adoc +++ b/en-US/install/Booting_the_Installation.adoc @@ -3,12 +3,12 @@ include::en-US/entities.adoc[] [[chap-booting-the-installation]] -=== Booting the Installation += Booting the Installation This chapter will explain how to boot the installer from local media or a network server as well as how to navigate the boot menu and use custom options. [[sect-preparing-boot]] -==== Preparing to Boot +== Preparing to Boot 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. @@ -56,7 +56,7 @@ On Mac hardware, hold down the kbd:[Option] key to enter the boot media selectio . Wait until the boot menu is displayed. The boot menu is described further in this chapter. [[sect-boot-menu]] -==== The Boot Menu +== The Boot Menu In most cases, when you boot the {PRODUCT} installer from your prepared boot media or server, the boot menu will be the first thing that appears. From this menu, you can either start the actual installation, or you can use the boot media to rescue an existing system. diff --git a/en-US/install/CustomSpoke.adoc b/en-US/install/CustomSpoke.adoc index eaf86ee..9855518 100644 --- a/en-US/install/CustomSpoke.adoc +++ b/en-US/install/CustomSpoke.adoc @@ -2,7 +2,7 @@ :experimental: [[sect-installation-gui-manual-partitioning]] -===== Manual Partitioning +=== Manual Partitioning The `Manual Partitioning` screen allows you to create a storage configuration for your {PRODUCT} system manually, giving you a greater control over your system's storage. diff --git a/en-US/install/CustomSpoke_AddBtrfs.adoc b/en-US/install/CustomSpoke_AddBtrfs.adoc index 4100ba7..1f57e81 100644 --- a/en-US/install/CustomSpoke_AddBtrfs.adoc +++ b/en-US/install/CustomSpoke_AddBtrfs.adoc @@ -2,7 +2,7 @@ :experimental: [[sect-installation-gui-manual-partitioning-btrfs]] -====== Creating a Btrfs Layout +==== Creating a Btrfs Layout _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. diff --git a/en-US/install/CustomSpoke_AddLVM.adoc b/en-US/install/CustomSpoke_AddLVM.adoc index 97ef3ee..422a21e 100644 --- a/en-US/install/CustomSpoke_AddLVM.adoc +++ b/en-US/install/CustomSpoke_AddLVM.adoc @@ -2,7 +2,7 @@ :experimental: [[sect-installation-gui-manual-partitioning-lvm]] -====== Creating a Logical Volume Managament (LVM) Layout +==== Creating a Logical Volume Managament (LVM) Layout _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. diff --git a/en-US/install/CustomSpoke_AddPhysical.adoc b/en-US/install/CustomSpoke_AddPhysical.adoc index 5468d5d..fc5a643 100644 --- a/en-US/install/CustomSpoke_AddPhysical.adoc +++ b/en-US/install/CustomSpoke_AddPhysical.adoc @@ -2,7 +2,7 @@ :experimental: [[sect-installation-gui-manual-partitioning-standard]] -====== Creating Standard Partitions +==== Creating Standard Partitions _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. diff --git a/en-US/install/CustomSpoke_FileSystems.adoc b/en-US/install/CustomSpoke_FileSystems.adoc index 01e3977..ef9ce13 100644 --- a/en-US/install/CustomSpoke_FileSystems.adoc +++ b/en-US/install/CustomSpoke_FileSystems.adoc @@ -2,7 +2,7 @@ :experimental: [[sect-installation-gui-manual-partitioning-filesystems]] -====== Device, File System and RAID Types +==== Device, File System and RAID Types {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. diff --git a/en-US/install/CustomSpoke_PartitioningAdvice.adoc b/en-US/install/CustomSpoke_PartitioningAdvice.adoc index 9e152eb..9d6306e 100644 --- a/en-US/install/CustomSpoke_PartitioningAdvice.adoc +++ b/en-US/install/CustomSpoke_PartitioningAdvice.adoc @@ -2,7 +2,7 @@ :experimental: [[sect-installation-gui-manual-partitioning-advice]] -====== Advice on Partitions +==== Advice on Partitions There is no best way to partition every system; the optimal setup depends on how you plan to use the system being installed. However, the following tips may help you find the optimal layout for your needs: diff --git a/en-US/install/CustomSpoke_RecommendedScheme.adoc b/en-US/install/CustomSpoke_RecommendedScheme.adoc index c3b1af1..f30c35f 100644 --- a/en-US/install/CustomSpoke_RecommendedScheme.adoc +++ b/en-US/install/CustomSpoke_RecommendedScheme.adoc @@ -2,7 +2,7 @@ :experimental: [[sect-installation-gui-manual-partitioning-recommended]] -====== Recommended Partitioning Scheme +==== Recommended Partitioning Scheme In most cases, at least the following mount points should always be created: diff --git a/en-US/install/CustomSpoke_SoftwareRAID.adoc b/en-US/install/CustomSpoke_SoftwareRAID.adoc index a2aa3bd..7a3f2fe 100644 --- a/en-US/install/CustomSpoke_SoftwareRAID.adoc +++ b/en-US/install/CustomSpoke_SoftwareRAID.adoc @@ -2,7 +2,7 @@ :experimental: [[sect-installation-gui-manual-partitioning-swraid]] -====== Creating Software RAID +==== 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 xref:Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-filesystems[Device, File System and RAID Types] a description of different kinds of RAIDs. diff --git a/en-US/install/DateTimeSpoke.adoc b/en-US/install/DateTimeSpoke.adoc index 4ba42de..d319837 100644 --- a/en-US/install/DateTimeSpoke.adoc +++ b/en-US/install/DateTimeSpoke.adoc @@ -2,7 +2,7 @@ :experimental: [[sect-installation-gui-date-and-time]] -===== Date & 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 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. diff --git a/en-US/install/FilterSpoke.adoc b/en-US/install/FilterSpoke.adoc index 8b63586..82e7277 100644 --- a/en-US/install/FilterSpoke.adoc +++ b/en-US/install/FilterSpoke.adoc @@ -2,7 +2,7 @@ :experimental: [[sect-installation-gui-installation-destination]] -===== Installation Destination - Specialized & Network Disks +=== 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 xref:Installing_Using_Anaconda.adoc#sect-installation-gui-storage-partitioning[Installation Destination]. diff --git a/en-US/install/FilterSpoke_AddFCoE.adoc b/en-US/install/FilterSpoke_AddFCoE.adoc index d6fdf2b..0466df7 100644 --- a/en-US/install/FilterSpoke_AddFCoE.adoc +++ b/en-US/install/FilterSpoke_AddFCoE.adoc @@ -2,7 +2,7 @@ :experimental: [[sect-installation-gui-installation-destination-add-fcoe]] -====== Add FCoE SAN +==== Add FCoE SAN The following procedure explains how to add _Fibre Channel over Ethernet_ (FCoE) storage devices and make them available during the installation: diff --git a/en-US/install/FilterSpoke_AddiSCSI.adoc b/en-US/install/FilterSpoke_AddiSCSI.adoc index 886c196..4e087a7 100644 --- a/en-US/install/FilterSpoke_AddiSCSI.adoc +++ b/en-US/install/FilterSpoke_AddiSCSI.adoc @@ -2,7 +2,7 @@ :experimental: [[sect-installation-gui-installation-destination-add-iscsi]] -====== Add iSCSI Target +==== Add iSCSI Target To use iSCSI storage devices, the installer must be able to discover them as _iSCSI targets_ and be able to create an iSCSI session to access them. Both of these steps may require a user name and password for _Challenge Handshake Authentication Protocol_ (CHAP) authentication. diff --git a/en-US/install/InitialSetupHub.adoc b/en-US/install/InitialSetupHub.adoc index bc96236..0a4955d 100644 --- a/en-US/install/InitialSetupHub.adoc +++ b/en-US/install/InitialSetupHub.adoc @@ -2,7 +2,7 @@ :experimental: [[sect-initial-setup]] -==== Initial Setup +== Initial Setup The `Initial Setup` screen is shown after the installation finishes and the installed system boots for the first time, before the first login, assuming the following conditions have been met: diff --git a/en-US/install/Installing_Using_Anaconda.adoc b/en-US/install/Installing_Using_Anaconda.adoc index 4e1b66c..82f754a 100644 --- a/en-US/install/Installing_Using_Anaconda.adoc +++ b/en-US/install/Installing_Using_Anaconda.adoc @@ -3,7 +3,7 @@ include::en-US/entities.adoc[] [[chap-installing-using-anaconda]] -=== Installing Using Anaconda += Installing Using Anaconda This chapter provides step-by-step instructions for installing {PRODUCT} using the [application]*Anaconda* installer. The bulk of this chapter describes installation using the graphical user interface. A text mode is also available for systems with no graphical display, but this mode is limited in certain aspects (for example, custom partitioning is not possible in text mode). @@ -14,7 +14,7 @@ If your system does not have the ability to use the graphical mode, you can: * 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 +== Introduction to Anaconda The {PRODUCT} installer, [application]*Anaconda*, is different from most other operating system installation programs due to its parallel nature. Most installers follow a fixed path: you must choose your language first, then you configure network, then installation type, then partitioning, etc. There is usually only one way to proceed at any given time. @@ -25,12 +25,12 @@ Some screens will be automatically configured depending on your hardware and the Additional differences appear in certain screens; notably the custom partitioning process is very different from other Linux distributions. These differences are described in each screen's subsection. [[sect-consoles-logs-during-installation]] -==== Consoles and Logging During the Installation +== Consoles and Logging During the Installation The following sections describe how to access logs and an interactive shell during the installation. This is useful when troubleshooting problems, but should not be necessary in most cases. [[sect-installation-consoles]] -===== Accessing Consoles +=== Accessing Consoles The {PRODUCT} installer uses the [application]*tmux* terminal multiplexer to display and control several windows you can use in addition to the main interface. Each of these windows serves a different purpose - they display several different logs, which can be used to troubleshoot any issues during the installation, and one of the windows provides an interactive shell prompt with `root` privileges, unless this prompt was specifically disabled using a boot option or a Kickstart command. @@ -70,14 +70,14 @@ You can also use kbd:[Ctrl + b] kbd:[n] and kbd:[Ctrl + b] kbd:[p] to switch to 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 +=== 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 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 +== 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. @@ -100,7 +100,7 @@ Limits of interactive text mode installation include: 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 +== Installing in the Graphical User Interface The graphical installation interface is the preferred method of manually installing {PRODUCT}. It allows you full control over all available settings, including custom partitioning and advanced storage configuration, and it is also localized to many languages other than English, allowing you to perform the entire installation in a different language. The graphical mode is used by default when you boot the system from local media (a CD, DVD or a USB flash drive). diff --git a/en-US/install/KdumpSpoke.adoc b/en-US/install/KdumpSpoke.adoc index 6031669..8c79472 100644 --- a/en-US/install/KdumpSpoke.adoc +++ b/en-US/install/KdumpSpoke.adoc @@ -2,7 +2,7 @@ :experimental: [[sect-installation-gui-kdump]] -===== Kdump +=== Kdump [NOTE] ==== diff --git a/en-US/install/KeyboardSpoke.adoc b/en-US/install/KeyboardSpoke.adoc index c549405..f027353 100644 --- a/en-US/install/KeyboardSpoke.adoc +++ b/en-US/install/KeyboardSpoke.adoc @@ -2,7 +2,7 @@ :experimental: [[sect-installation-gui-keyboard-layout]] -===== 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 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. diff --git a/en-US/install/LangSupportSpoke.adoc b/en-US/install/LangSupportSpoke.adoc index 1ecd289..a0c332e 100644 --- a/en-US/install/LangSupportSpoke.adoc +++ b/en-US/install/LangSupportSpoke.adoc @@ -2,7 +2,7 @@ :experimental: [[sect-installation-gui-language-support]] -===== 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 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. diff --git a/en-US/install/NetworkSpoke.adoc b/en-US/install/NetworkSpoke.adoc index da78574..f0b93e8 100644 --- a/en-US/install/NetworkSpoke.adoc +++ b/en-US/install/NetworkSpoke.adoc @@ -2,7 +2,7 @@ :experimental: [[sect-installation-gui-network-configuration]] -===== Network & Hostname +=== Network & Hostname The `Network & Hostname` screen is used to configure network interfaces. Options selected here will be available both during the installation (if needed for tasks such as downloading packages from a remote location) and on the installed system. diff --git a/en-US/install/NetworkSpoke_EditConnection.adoc b/en-US/install/NetworkSpoke_EditConnection.adoc index af0d0e1..cf6bf90 100644 --- a/en-US/install/NetworkSpoke_EditConnection.adoc +++ b/en-US/install/NetworkSpoke_EditConnection.adoc @@ -2,7 +2,7 @@ :experimental: [[sect-installation-gui-network-configuration-advanced]] -====== Editing Network Interface Configuration +==== Editing Network Interface Configuration 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/++[]. diff --git a/en-US/install/NetworkSpoke_VirtualInterfaces.adoc b/en-US/install/NetworkSpoke_VirtualInterfaces.adoc index 917d73d..8dda47d 100644 --- a/en-US/install/NetworkSpoke_VirtualInterfaces.adoc +++ b/en-US/install/NetworkSpoke_VirtualInterfaces.adoc @@ -2,7 +2,7 @@ :experimental: [[sect-installation-gui-network-configuration-virtual-interface]] -====== Adding a Virtual Network Interface +==== Adding a Virtual Network Interface To add a virtual network interface, click the `+` button at the bottom of the interface list. A new window will open, prompting you to select one of the three available types of virtual interfaces: diff --git a/en-US/install/PasswordSpoke.adoc b/en-US/install/PasswordSpoke.adoc index 0dfdfda..4ed6f21 100644 --- a/en-US/install/PasswordSpoke.adoc +++ b/en-US/install/PasswordSpoke.adoc @@ -2,7 +2,7 @@ :experimental: [[sect-installation-gui-root-password]] -===== Root Password +=== Root Password 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. diff --git a/en-US/install/Preparing_for_Installation.adoc b/en-US/install/Preparing_for_Installation.adoc index b523a80..049c35a 100644 --- a/en-US/install/Preparing_for_Installation.adoc +++ b/en-US/install/Preparing_for_Installation.adoc @@ -3,12 +3,12 @@ include::en-US/entities.adoc[] [[chap-preparing-for-installation]] -=== Preparing for Installation += Preparing for Installation This chapter describes the steps you need take before you begin the installation. Not every step must be strictly followed - for example, if you plan to use the default installation settings, you do not need to gather system information such as disk device labels/UUIDs or network information such as the system's IP address. However, you should still go through this chapter, as it also describes the available types of installation media and how to prepare boot media and installation sources. [[sect-preparing-upgrade-or-install]] -==== Upgrade or Install? +== Upgrade or Install? If you already have Fedora installed and want to upgrade your installation to the current version, there are two basic ways to do so: @@ -22,7 +22,7 @@ Always back up your data before performing an upgrade or reinstalling your syste ==== [[sect-preparing-obtaining-images]] -==== Downloading Boot and Installation 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 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. @@ -31,14 +31,14 @@ Read more about Fedora Workstation, Fedora Cloud, Fedora Server and the availabl You can also choose a Fedora _Spin_ featuring favorite alternative desktops or tools for specialized tasks at link:++http://spins.fedoraproject.org++[]. [[sect-verifying-images]] -==== Verifying the Downloaded Image +== Verifying the Downloaded Image Because transmission errors or other problems may corrupt the Fedora image you have downloaded, it is important to verify the file's integrity. After the images are created, an operation is performed on the file that produces a value called a `checksum` using a complex mathematical algorithm. The operation is sufficiently complex that *any change* to the original file will produce a different checksum. By calculating the image's `checksum` on your own computer and comparing it to the original `checksum`, you can verify the image has not been tampered with or corrupted. The original checksum values are provided at link:++https://fedoraproject.org/verify++[], and are [command]#gpg# signed to demonstrate their integrity. [[sect-verifying-windows]] -===== Verifying checksums on Windows systems +=== Verifying checksums on Windows systems .Verifying checksums on Windows systems . Download the Fedora image of your choice from link:++https://fedoraproject.org/get-fedora++[] and the corresponding checksum file from link:++https://fedoraproject.org/verify ++[] @@ -90,7 +90,7 @@ echo "Checksum test failed." ---- [[sect-verifying-nix]] -===== Verifying checksums on Linux and OSX systems +=== Verifying checksums on Linux and OSX systems .Verifying checksums on Linux and OSX systems . Download the Fedora image of your choice from link:++https://fedoraproject.org/get-fedora++[] and the corresponding checksum file from link:++https://fedoraproject.org/verify ++[] @@ -119,7 +119,7 @@ $ shasum -a 256 -c *CHECKSUM ---- [[sect-preparing-boot-media]] -==== Preparing Boot Media +== Preparing Boot Media Fedora images are `Hybrid ISOs` and can be used to create installation media with both optical and USB disks, for booting on both BIOS and UEFI systems. diff --git a/en-US/install/ProgressHub.adoc b/en-US/install/ProgressHub.adoc index 6b27332..be99af5 100644 --- a/en-US/install/ProgressHub.adoc +++ b/en-US/install/ProgressHub.adoc @@ -2,7 +2,7 @@ :experimental: [[sect-installation-gui-installation-progress]] -===== Configuration and Installation Progress +=== Configuration and Installation Progress 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. diff --git a/en-US/install/SoftwareSpoke.adoc b/en-US/install/SoftwareSpoke.adoc index 95f7247..96ea6ae 100644 --- a/en-US/install/SoftwareSpoke.adoc +++ b/en-US/install/SoftwareSpoke.adoc @@ -2,7 +2,7 @@ :experimental: [[sect-installation-gui-software-selection]] -===== Software Selection +=== Software Selection 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. diff --git a/en-US/install/SourceSpoke.adoc b/en-US/install/SourceSpoke.adoc index 393d49b..ba3aca8 100644 --- a/en-US/install/SourceSpoke.adoc +++ b/en-US/install/SourceSpoke.adoc @@ -2,7 +2,7 @@ :experimental: [[sect-installation-gui-installation-source]] -===== Installation Source +=== Installation Source The `Installation Source` screen allows you to specify a location (local or on the network) from which packages will be downloaded and installed on your system. This screen will be configured automatically in most cases, but you can change your settings or add additional sources. diff --git a/en-US/install/StorageSpoke.adoc b/en-US/install/StorageSpoke.adoc index eca6277..361d24d 100644 --- a/en-US/install/StorageSpoke.adoc +++ b/en-US/install/StorageSpoke.adoc @@ -2,7 +2,7 @@ :experimental: [[sect-installation-gui-storage-partitioning]] -===== Installation Destination +=== Installation Destination 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. diff --git a/en-US/install/StorageSpoke_BootLoader.adoc b/en-US/install/StorageSpoke_BootLoader.adoc index b9a6e51..15bfaa5 100644 --- a/en-US/install/StorageSpoke_BootLoader.adoc +++ b/en-US/install/StorageSpoke_BootLoader.adoc @@ -2,7 +2,7 @@ :experimental: [[sect-installation-gui-storage-partitioning-bootloader]] -====== Boot Loader Installation +==== Boot Loader Installation {PRODUCT} uses [application]*GRUB2* (GRand Unified Bootloader version 2) as its boot loader. The boot loader is the first program that runs when the computer starts and is responsible for loading and transferring control to an operating system. [application]*GRUB2* can boot any compatible operating system (including Microsoft Windows) and can also use chain loading to transfer control to other boot loaders for unsupported operating systems. diff --git a/en-US/install/SummaryHub.adoc b/en-US/install/SummaryHub.adoc index 70a37be..f029d8d 100644 --- a/en-US/install/SummaryHub.adoc +++ b/en-US/install/SummaryHub.adoc @@ -2,7 +2,7 @@ :experimental: [[sect-installation-gui-installation-summary]] -===== Installation Summary +=== Installation Summary The `Installation Summary` screen is the central location for setting up an installation. Most of the options which can be configured during the installation can be accessed from here. diff --git a/en-US/install/Troubleshooting.adoc b/en-US/install/Troubleshooting.adoc index f48d352..207b3d1 100644 --- a/en-US/install/Troubleshooting.adoc +++ b/en-US/install/Troubleshooting.adoc @@ -3,12 +3,12 @@ include::en-US/entities.adoc[] [[chap-troubleshooting]] -=== Troubleshooting += Troubleshooting This chapter offers some pointers on how to get help when something goes wrong. It also discusses some common installation problems and their solutions. [[sect-troubleshooting-getting-help]] -==== Getting Help +== Getting Help There are many places on the internet which can help you when you encounter a problem not described in this chapter: discussion boards, blogs, IRC, and more. Some of the more popular places where you can find help include: @@ -32,7 +32,7 @@ Before you open a new discussion or ask anyone for help on IRC, you should alway When you ask for help troubleshooting problems related to the installation, you may be asked to provide log files generated by the installer. The sections below explain which files are generated, what their contents are, and how to transfer them from the installation system. [[sect-troubleshooting-log-files]] -===== Log Files Generated During the Installation +=== Log Files Generated During the Installation For debugging purposes, [application]*Anaconda* logs installation actions into files in the `/tmp` directory. These files are listed in the following table. @@ -52,12 +52,12 @@ For debugging purposes, [application]*Anaconda* logs installation actions into f If the installation fails, the messages from these files are consolidated into `/tmp/anaconda-tb-_identifier_pass:attributes[{blank}]`, where _identifier_ is a random string. [[sect-troubleshooting-transferring-logs]] -===== Transferring Log Files from the Installation System +=== Transferring Log Files from the Installation System 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 +==== Transferring Log Files Onto a USB Drive . On the system you are installing, press kbd:[Ctrl + Alt + F2] to access a shell prompt. You will be logged into a root account and you will have access to the installation program's temporary file system. @@ -113,7 +113,7 @@ You can now verify that you mounted the correct device and partition by accessin The log files from the installation are now saved on the USB flash drive. [[sect-troubleshooting-transferring-logs-network]] -====== Transferring Log Files Over the Network +==== Transferring Log Files Over the Network . On the system you are installing, press kbd:[Ctrl + Alt + F2] to access a shell prompt. You will be logged into a root account and you will have access to the installation program's temporary file system. @@ -154,9 +154,9 @@ Type `yes` and press kbd:[Enter] to continue. Then, provide a valid password whe The log files from the installation are now permanently saved on the target system and available for review. [[sect-troubleshooting-problems-beginning-installation]] -==== Trouble Beginning the Installation +== Trouble Beginning the Installation -===== Problems with Booting into the Graphical Installation +=== Problems with Booting into the Graphical Installation 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. @@ -177,17 +177,17 @@ 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 xref:../advanced/VNC_Installations.adoc#chap-vnc-installations[Installing Using VNC]. -===== Serial Console Not Detected +=== 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 xref:../advanced/Boot_Options.adoc#chap-anaconda-boot-options[Boot Options] for more details. [[sect-troubleshooting-problems-during-installation]] -==== Trouble During the Installation +== Trouble During the Installation [[sect-trouble-during-no-target]] -===== No Disks Detected +=== No Disks Detected In the `Installation Destination` screen, the following error message may appear at the bottom: `No disks detected. Please shut down the computer, connect at least one disk, and restart to complete installation`. @@ -200,10 +200,10 @@ If you are installing into one or more iSCSI devices and there is no local stora If you made sure you have a connected and properly configured storage device and the message still appears after you reboot the system and start the installation again, it means that the installation program failed to detect the storage. In most cases this message appears when you attempt to install on an SCSI device which has not been recognized by the installation program. [[sect-troubleshooting-problems-after-installation]] -==== Problems After Installation +== Problems After Installation [[sect-trouble-after-reset-root-password]] -===== Resetting the Root Password +=== Resetting the Root Password If you lost the root password to the system and you have access to the boot loader, you can reset the password by editing the GRUB2 configuration. @@ -261,7 +261,7 @@ sh4.2# mount -o remount,ro / . Reboot the system. From now on, you will be able to log in as the root user using the new password set up during this procedure. [[sect-trouble-after-raid]] -===== Are You Unable to Boot With Your RAID Card? +=== Are You Unable to Boot With Your RAID Card? If you have performed an installation and cannot boot your system properly, you may need to reinstall and partition your system's storage differently. @@ -270,7 +270,7 @@ Some BIOS types do not support booting from RAID cards. After you finish the ins 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 +=== Trouble With the Graphical Boot Sequence After you finish the installation and reboot your system for the first time, it is possible that the system stops responding during the graphical boot sequence, requiring a reset. In this case, the boot loader is displayed successfully, but selecting any entry and attempting to boot the system results in a halt. This usually means a problem with the graphical boot sequence; to solve this issue, you must disable graphical boot. To do this, temporarily alter the setting at boot time before changing it permanently. @@ -319,7 +319,7 @@ After you finish this procedure, you can reboot your computer. {PRODUCT} will no See the [citetitle]_{PRODUCT} System Administrator's Guide_, available at link:++http://docs.fedoraproject.org/++[], for more information about working with the [application]*GRUB2* boot loader. [[sect-trouble-after-graphical-login]] -===== Booting into a Graphical Environment +=== Booting into a Graphical Environment If you have installed the [application]*X Window System* and a desktop environment such as [application]*GNOME*, but are not seeing a graphical desktop environment once you log into your system, you can start it manually using the [command]#startx# command. Note, however, that this is just a one-time fix and does not change the log in process for future log ins. @@ -345,13 +345,13 @@ Graphical login is now enabled by default - you will be presented with a graphic For more information about targets in [application]*systemd*, see the [citetitle]_{PRODUCT} System Administrator's Guide_, available at link:++http://docs.fedoraproject.org/++[]. [[sect-trouble-after-no-gui]] -===== No Graphical User Interface Present +=== No Graphical User Interface Present If you are having trouble getting [application]*X* (the [application]*X Window System*) to start, it is possible that it has not been installed. Some of the pre-set base environments you can select during the installation, such as `Minimal install` or `Web Server`, do not include a graphical interface - it has to be installed manually. If you want [application]*X*, you can install the necessary packages after the installation using the [application]*DNF* package manager. For example, to install [application]*GNOME*, use [command]#dnf install gnome-shell# as `root`. -===== X Server Crashing After User Logs In +=== X Server Crashing After User Logs In If you are having trouble with the [application]*X* server crashing when a user logs in, one or more of your file systems may be full (or nearly full). To verify that this is the problem you are experiencing, execute the following command: @@ -381,7 +381,7 @@ In the above example, you can see that the `/home` partition is full, which caus For additional information about [command]#df# and an explanation of the options available (such as the [option]#-h# option used in this example), see the `df(1)` man page. [[sect-trouble-after-missing-ram]] -===== Is Your RAM Not Being Recognized? +=== 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 xref:../advanced/Boot_Options.adoc#sect-boot-options-memtest[Loading the Memory (RAM) Testing Mode] for details. diff --git a/en-US/install/UserSpoke.adoc b/en-US/install/UserSpoke.adoc index e19e09f..c768f2b 100644 --- a/en-US/install/UserSpoke.adoc +++ b/en-US/install/UserSpoke.adoc @@ -2,7 +2,7 @@ :experimental: [[sect-installation-gui-create-user]] -===== Create User +=== Create User The `Create User` screen can be used to create and configure one normal (non-`root`) user account during the installation. Only one user account can be configured here; if you require more accounts, wait until the installation completes, reboot your system and then create other accounts using either the [command]#useradd# command in a terminal, or a graphical utility for managing user accounts (for example, the `Users` screen in the Settings menu in [application]*GNOME*). @@ -44,7 +44,7 @@ See the [citetitle]_{PRODUCT} Security Guide_, available at the link:++http://do To additional settings, click the `Advanced` button below the password input fields. A new dialog window titled `Advanced User Configuration` will open. This dialog is described in the following section. [[sect-installation-gui-create-user-advanced]] -====== Advanced User Configuration +==== Advanced User Configuration The `Advanced User Configuration` dialog allows you to change the following settings for the new user account. diff --git a/en-US/install/WelcomeSpoke.adoc b/en-US/install/WelcomeSpoke.adoc index 8b768ca..0c283e8 100644 --- a/en-US/install/WelcomeSpoke.adoc +++ b/en-US/install/WelcomeSpoke.adoc @@ -2,7 +2,7 @@ :experimental: [[sect-installation-gui-welcome]] -===== Welcome Screen and Language Selection +=== Welcome Screen and Language Selection The first screen displayed immediately after the graphical installer starts is the Welcome screen.