Fix a bunch of xrefs
This commit is contained in:
parent
6bba65ef36
commit
d7a8d7cc58
29 changed files with 96 additions and 96 deletions
|
|
@ -21,7 +21,7 @@ No permanent changes will be made to your disks during the actual partitioning p
|
|||
|
||||
image::anaconda/CustomSpoke.png[The Manual Partitioning screen. At this point, no partitioning has been configured. The left column shows an option to automatically create a pre-defined layout. An existing Linux system has been detected also and is displayed below the automatic configuration selection. The right side of the screen shows available options for the currently selected mount point.]
|
||||
|
||||
When you first open the `Manual Partitioning` screen, the column on the left side will display all previously existing partitions on all drives which you selected as installation targers in xref:Installing_Using_Anaconda.adoc#sect-installation-gui-storage-partitioning[Installation Destination]. If none of the selected drives contain any existing partitions, then a message informing you that no mount points currently exist will appear.
|
||||
When you first open the `Manual Partitioning` screen, the column on the left side will display all previously existing partitions on all drives which you selected as installation targers in xref:install/Installing_Using_Anaconda.adoc#sect-installation-gui-storage-partitioning[Installation Destination]. If none of the selected drives contain any existing partitions, then a message informing you that no mount points currently exist will appear.
|
||||
|
||||
Here, you can choose a partitioning scheme such as `LVM` or `BTRFS` and click the `Click here to create them automatically` to prompt the installer to create a basic partitioning layout; this layout follows the guidelines described in xref:Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-recommended[Recommended Partitioning Scheme]. The created layout is a basic layout where partition/volume sizes are determined automatically based on the total amount of available space.
|
||||
|
||||
|
|
@ -42,11 +42,11 @@ The exact steps for configuring your storage depend on your specific needs and y
|
|||
|
||||
Below the list of existing mount points are two fields, showing you how much free space is left on your storage devices and how much total space they have.
|
||||
|
||||
Click the `pass:attributes[{blank}]_X_ storage devices selected` to view a summary of currently selected storage devices; this may help you with orientation in more complicated storage schemas. Devices displayed here are the ones you have selected in xref:Installing_Using_Anaconda.adoc#sect-installation-gui-storage-partitioning[Installation Destination]. If you want to add or remove any storage devices from your configuration, return to that screen and change your selection.
|
||||
Click the `pass:attributes[{blank}]_X_ storage devices selected` to view a summary of currently selected storage devices; this may help you with orientation in more complicated storage schemas. Devices displayed here are the ones you have selected in xref:install/Installing_Using_Anaconda.adoc#sect-installation-gui-storage-partitioning[Installation Destination]. If you want to add or remove any storage devices from your configuration, return to that screen and change your selection.
|
||||
|
||||
You can press the `Reset All` button in the bottom right corner at any time to reset the storage configuration to the state it was in when you last opened the `Manual Partitioning` screen. This means that if you modify the storage configuration, leave the screen, and then come back, the Reset button will reset the configuration back to the already modified state, discarding only the changes you have made recently, not all changes to the storage configuration since you booted the installer.
|
||||
|
||||
To discard all changes, and to also detect any new drives which have not been detected when the installer started (usually when you attached a new drive after you started), press the button marked by a circular arrow in the set of controls below the list of mount points on the left side of the screen. In the dialog window that opens, press `Rescan Disks` and wait until the scanning process completes. Then, press `OK` to return to xref:Installing_Using_Anaconda.adoc#sect-installation-gui-storage-partitioning[Installation Destination]; all detected disks including any new ones will be displayed in the `Local Standard Disks` section.
|
||||
To discard all changes, and to also detect any new drives which have not been detected when the installer started (usually when you attached a new drive after you started), press the button marked by a circular arrow in the set of controls below the list of mount points on the left side of the screen. In the dialog window that opens, press `Rescan Disks` and wait until the scanning process completes. Then, press `OK` to return to xref:install/Installing_Using_Anaconda.adoc#sect-installation-gui-storage-partitioning[Installation Destination]; all detected disks including any new ones will be displayed in the `Local Standard Disks` section.
|
||||
|
||||
.Rescan Disks
|
||||
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@
|
|||
|
||||
_Logical Volume Management_ (LVM) presents a simple logical view of underlying physical storage space, such as hard drives or LUNs. Partitions on physical storage are represented as _physical volumes_ that can be grouped together into _volume groups_. Each volume group can be divided into multiple _logical volumes_, each of which is analogous to a standard disk partition. Therefore, LVM logical volumes function as partitions which can span multiple physical disks.
|
||||
|
||||
See xref:../appendixes/Understanding_LVM.adoc#appe-lvm-overview[Understanding LVM] for additional information about the concepts behind Logical Volume Management.
|
||||
See xref:appendixes/Understanding_LVM.adoc#appe-lvm-overview[Understanding LVM] for additional information about the concepts behind Logical Volume Management.
|
||||
|
||||
[WARNING]
|
||||
====
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@
|
|||
|
||||
_Standard partitions_ are the most common type of partition, with the widest support across operating systems. For example, Microsoft Windows uses exclusively physical partitions and can not natively work with LVM or Btrfs. Most {PRODUCT} partitioning setups will also require at least one standard partition for the `/boot` directory, and possibly also another standard partition with the BIOS Boot or EFI System file system to store the boot loader.
|
||||
|
||||
See xref:../appendixes/Disk_Partitions.adoc#appe-disk-partitions-overview[An Introduction to Disk Partitions] for additional information about the concepts behind physical partitions.
|
||||
See xref:appendixes/Disk_Partitions.adoc#appe-disk-partitions-overview[An Introduction to Disk Partitions] for additional information about the concepts behind physical partitions.
|
||||
|
||||
.Create Standard Partition
|
||||
|
||||
|
|
|
|||
|
|
@ -12,9 +12,9 @@ To configure software RAID, make sure that you have enough physical hard drives
|
|||
|
||||
.Device Types
|
||||
|
||||
* `Standard Partition` - A standard partition can contain a file system or swap space. Standard partitions are most commonly used for `/boot` and the BIOS Boot and EFI System partitions. LVM logical volumes or Btrfs subvolumes are recommended for most other uses. See xref:../appendixes/Disk_Partitions.adoc#appe-disk-partitions-overview[An Introduction to Disk Partitions] for additional information about the concepts behind physical partitions.
|
||||
* `Standard Partition` - A standard partition can contain a file system or swap space. Standard partitions are most commonly used for `/boot` and the BIOS Boot and EFI System partitions. LVM logical volumes or Btrfs subvolumes are recommended for most other uses. See xref:appendixes/Disk_Partitions.adoc#appe-disk-partitions-overview[An Introduction to Disk Partitions] for additional information about the concepts behind physical partitions.
|
||||
|
||||
* `LVM` - Choosing `LVM` as the `Device Type` creates an LVM logical volume and a volume group to contain it (unless one already exists, in which case the new volume is assigned to the existing group). LVM can improve performance when using physical disks and allows you to use multiple disks for a single mount point. For information on how to create a logical volume, see xref:Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-lvm[Creating a Logical Volume Managament (LVM) Layout]. Also see xref:../appendixes/Understanding_LVM.adoc#appe-lvm-overview[Understanding LVM] for some additional information about LVM in general.
|
||||
* `LVM` - Choosing `LVM` as the `Device Type` creates an LVM logical volume and a volume group to contain it (unless one already exists, in which case the new volume is assigned to the existing group). LVM can improve performance when using physical disks and allows you to use multiple disks for a single mount point. For information on how to create a logical volume, see xref:Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-lvm[Creating a Logical Volume Managament (LVM) Layout]. Also see xref:appendixes/Understanding_LVM.adoc#appe-lvm-overview[Understanding LVM] for some additional information about LVM in general.
|
||||
|
||||
* `LVM Thin Provisioning` - Using thin provisioning, you can manage a storage pool of free space, known as a _thin pool_, which can be allocated to an arbitrary number of devices when needed by applications. The thin pool can be expanded dynamically when needed for cost-effective allocation of storage space.
|
||||
|
||||
|
|
|
|||
|
|
@ -64,7 +64,7 @@ Systems with BIOS firmware and UEFI systems in BIOS compatibility mode::: If th
|
|||
[NOTE]
|
||||
====
|
||||
|
||||
You can force the installer to use GPT on disks smaller than 2 TB by using the [option]#inst.gpt# boot option as described in xref:../advanced/Boot_Options.adoc#chap-anaconda-boot-options[Boot Options]. However, the opposite is not possible - you can not use MBR on disks larger than 2 TB.
|
||||
You can force the installer to use GPT on disks smaller than 2 TB by using the [option]#inst.gpt# boot option as described in xref:advanced/Boot_Options.adoc#chap-anaconda-boot-options[Boot Options]. However, the opposite is not possible - you can not use MBR on disks larger than 2 TB.
|
||||
|
||||
====
|
||||
+
|
||||
|
|
@ -92,4 +92,4 @@ Only assign storage capacity to those partitions you require immediately. You ma
|
|||
|
||||
====
|
||||
|
||||
If you are not sure how best to configure the partitions for your computer, accept the automatic default partition layout provided by the installation program as described in xref:Installing_Using_Anaconda.adoc#sect-installation-gui-storage-partitioning[Installation Destination].
|
||||
If you are not sure how best to configure the partitions for your computer, accept the automatic default partition layout provided by the installation program as described in xref:install/Installing_Using_Anaconda.adoc#sect-installation-gui-storage-partitioning[Installation Destination].
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
[[sect-installation-gui-installation-destination]]
|
||||
=== Installation Destination - Specialized & Network Disks
|
||||
|
||||
This part of the `Installation Destination` screen allows you to configure non-local storage devices, namely iSCSI and FCoE storage. This section will mostly be useful to advanced users who have a need for networked disks. For instructions on setting up local hard drives, see xref:Installing_Using_Anaconda.adoc#sect-installation-gui-storage-partitioning[Installation Destination].
|
||||
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:install/Installing_Using_Anaconda.adoc#sect-installation-gui-storage-partitioning[Installation Destination].
|
||||
|
||||
[IMPORTANT]
|
||||
====
|
||||
|
|
@ -47,7 +47,7 @@ Other SAN Devices:: Devices available on a Storage Area Network (SAN).
|
|||
|
||||
Depending on the tab you are currently in, you can filter the discovered devices by using the `Filter By` field. Some of the filtering options are automatically populated based on discovered devices (for example, if you select `Filter By:` `Vendor`, another drop-down menu will appear showing all vendors of all discovered devices). Other filters require your input (for example when filtering by WWID), and present you with a text input field instead of a drop-down menu.
|
||||
|
||||
In the list (regardless of how it is filtered), each device is presented on a separate row, with a check box to its left. Mark the check box to make the device available during the installation process; this will cause this device (node) to be shown in the `Specialized & Network Disks` section in xref:Installing_Using_Anaconda.adoc#sect-installation-gui-storage-partitioning[Installation Destination]. There, you can select the disk as an installation target and proceed with either manual or automatic partitioning.
|
||||
In the list (regardless of how it is filtered), each device is presented on a separate row, with a check box to its left. Mark the check box to make the device available during the installation process; this will cause this device (node) to be shown in the `Specialized & Network Disks` section in xref:install/Installing_Using_Anaconda.adoc#sect-installation-gui-storage-partitioning[Installation Destination]. There, you can select the disk as an installation target and proceed with either manual or automatic partitioning.
|
||||
|
||||
[NOTE]
|
||||
====
|
||||
|
|
@ -56,7 +56,7 @@ Devices that you select here are not automatically wiped by the installation pro
|
|||
|
||||
====
|
||||
|
||||
When you have selected the storage devices to make available during installation, click `Done` to return to xref:Installing_Using_Anaconda.adoc#sect-installation-gui-storage-partitioning[Installation Destination].
|
||||
When you have selected the storage devices to make available during installation, click `Done` to return to xref:install/Installing_Using_Anaconda.adoc#sect-installation-gui-storage-partitioning[Installation Destination].
|
||||
|
||||
include::{partialsdir}/install/FilterSpoke_AddiSCSI.adoc[]
|
||||
|
||||
|
|
|
|||
|
|
@ -10,7 +10,7 @@ The following procedure explains how to add _Fibre Channel over Ethernet_ (FCoE)
|
|||
.Add FCoE Target
|
||||
. Click the `Add FCoE SAN` button in the bottom right corner of xref:Installing_Using_Anaconda.adoc#sect-installation-gui-installation-destination[Installation Destination - Specialized & Network Disks]. A new dialog window will open.
|
||||
|
||||
. Select the network interface (`NIC`) which is connected to your FCoE switch from the drop-down menu. Note that this network interface must be configured and connected - see xref:Installing_Using_Anaconda.adoc#sect-installation-gui-network-configuration[Network & Hostname].
|
||||
. Select the network interface (`NIC`) which is connected to your FCoE switch from the drop-down menu. Note that this network interface must be configured and connected - see xref:install/Installing_Using_Anaconda.adoc#sect-installation-gui-network-configuration[Network & Hostname].
|
||||
|
||||
. Below the `NIC` drop-down menu are two choices:
|
||||
+
|
||||
|
|
|
|||
|
|
@ -31,10 +31,10 @@ It is possible to configure [application]*Initial Setup* to display all availabl
|
|||
|
||||
[subs="quotes, macros"]
|
||||
----
|
||||
# [command]firstboot --enable --reconfig#
|
||||
firstboot --enable --reconfig
|
||||
----
|
||||
|
||||
The [option]#--reconfig# option specifies that all options should be displayed. See xref:../advanced/Kickstart_Installations.adoc#chap-kickstart-installations[Automating the Installation with Kickstart] for information about Kickstart installations.
|
||||
The [option]#--reconfig# option specifies that all options should be displayed. See xref:advanced/Kickstart_Installations.adoc#chap-kickstart-installations[Automating the Installation with Kickstart] for information about Kickstart installations.
|
||||
|
||||
====
|
||||
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@
|
|||
[NOTE]
|
||||
====
|
||||
|
||||
This screen is disabled by default. To enable it during the installation, you must use the [option]#inst.kdump_addon=on# option at the boot menu. See xref:../advanced/Boot_Options.adoc#sect-boot-options-advanced[Advanced Installation Options] for details, and xref:Booting_the_Installation.adoc#sect-boot-menu[The Boot Menu] for instructions on using custom boot options.
|
||||
This screen is disabled by default. To enable it during the installation, you must use the [option]#inst.kdump_addon=on# option at the boot menu. See xref:advanced/Boot_Options.adoc#sect-boot-options-advanced[Advanced Installation Options] for details, and xref:install/Booting_the_Installation.adoc#sect-boot-menu[The Boot Menu] for instructions on using custom boot options.
|
||||
|
||||
====
|
||||
|
||||
|
|
|
|||
|
|
@ -26,7 +26,7 @@ To add support for one or more additional languages, click a group in the left p
|
|||
[NOTE]
|
||||
====
|
||||
|
||||
Enabling support for some languages (typically languages which use non-Latin script) will install additional packages - for example, enabling support for one or more languages from the `Arabic` group will also install the `arabic-support` package group. For more information about packages, see xref:Installing_Using_Anaconda.adoc#sect-installation-gui-software-selection[Software Selection].
|
||||
Enabling support for some languages (typically languages which use non-Latin script) will install additional packages - for example, enabling support for one or more languages from the `Arabic` group will also install the `arabic-support` package group. For more information about packages, see xref:install/Installing_Using_Anaconda.adoc#sect-installation-gui-software-selection[Software Selection].
|
||||
|
||||
====
|
||||
|
||||
|
|
|
|||
|
|
@ -19,9 +19,9 @@ image::anaconda/NetworkSpoke.png[The Network & Hostname screen. In the left pane
|
|||
|
||||
Locally accessible interfaces are automatically detected by the installation program and cannot be manually added or deleted. All detected interfaces are listed on the left side of the screen. Click an interface in the list to display its current configuration (such as IP and DNS address); the details are displayed on the right side of the screen.
|
||||
|
||||
Below the list of interfaces are two buttons. Use the `+` button to add a virtual network interface (Team, Bond or VLAN) as described in xref:Installing_Using_Anaconda.adoc#sect-installation-gui-network-configuration-virtual-interface[Adding a Virtual Network Interface]. To remove a previously created virtual interface, select it in the list and click the `-` button.
|
||||
Below the list of interfaces are two buttons. Use the `+` button to add a virtual network interface (Team, Bond or VLAN) as described in xref:install/Installing_Using_Anaconda.adoc#sect-installation-gui-network-configuration-virtual-interface[Adding a Virtual Network Interface]. To remove a previously created virtual interface, select it in the list and click the `-` button.
|
||||
|
||||
To change settings such as IP addresses, DNS servers, or routing configuration for an existing interface (both virtual and physical), select the interface in the left pane and click `Configure` in the bottom right corner of the screen. Available settings are described in xref:Installing_Using_Anaconda.adoc#sect-installation-gui-network-configuration-advanced[Editing Network Interface Configuration].
|
||||
To change settings such as IP addresses, DNS servers, or routing configuration for an existing interface (both virtual and physical), select the interface in the left pane and click `Configure` in the bottom right corner of the screen. Available settings are described in xref:install/Installing_Using_Anaconda.adoc#sect-installation-gui-network-configuration-advanced[Editing Network Interface Configuration].
|
||||
|
||||
Use the `ON`pass:attributes[{blank}]/pass:attributes[{blank}]`OFF` switch in the top right corner to enable or disable the currently selected interface.
|
||||
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@
|
|||
|
||||
This section only details the most important settings for a typical wired connection used during installation. Many of the available options do not have to be changed in most installation scenarios and are not carried over to the installed system. Configuration of other types of networks is broadly similar, although the specific configuration parameters may be different. To learn more about network configuration after installation, see the [citetitle]_{PRODUCT} Networking{nbsp}Guide_, available at link:++https://docs.fedoraproject.org/++[].
|
||||
|
||||
To configure a network connection manually, select that connection in the list on the left side of the screen, and click the `Configure` button. A dialog will appear that allows you to configure the selected connection. The configuration options presented depends on the connection type - the available options will be slightly different depending on whether it is a physical interface (wired or wireless network interface controller) or a virtual interface (Bond, Team or Vlan) which you previously configured in xref:Installing_Using_Anaconda.adoc#sect-installation-gui-network-configuration-virtual-interface[Adding a Virtual Network Interface].. A full description of all configuration settings for all connection types is beyond the scope of this document; see the [citetitle]_Networking Guide_ for details.
|
||||
To configure a network connection manually, select that connection in the list on the left side of the screen, and click the `Configure` button. A dialog will appear that allows you to configure the selected connection. The configuration options presented depends on the connection type - the available options will be slightly different depending on whether it is a physical interface (wired or wireless network interface controller) or a virtual interface (Bond, Team or Vlan) which you previously configured in xref:install/Installing_Using_Anaconda.adoc#sect-installation-gui-network-configuration-virtual-interface[Adding a Virtual Network Interface].. A full description of all configuration settings for all connection types is beyond the scope of this document; see the [citetitle]_Networking Guide_ for details.
|
||||
|
||||
The most common and useful options in the configuration dialog are:
|
||||
|
||||
|
|
@ -46,4 +46,4 @@ Select `Use this connection only for resources on its network` to prevent this c
|
|||
+
|
||||
When you finish configuring the interface's routing settings, click `OK` to return to the configuration dialog.
|
||||
|
||||
Once you finish configuring the interface, click `Save` in the configuration window's bottom right corner to save your settings and return to xref:Installing_Using_Anaconda.adoc#sect-installation-gui-network-configuration[Network & Hostname].
|
||||
Once you finish configuring the interface, click `Save` in the configuration window's bottom right corner to save your settings and return to xref:install/Installing_Using_Anaconda.adoc#sect-installation-gui-network-configuration[Network & Hostname].
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ To add a virtual network interface, click the `+` button at the bottom of the in
|
|||
|
||||
* `Vlan` (_Virtual LAN_) - A method to create multiple distinct broadcast domains which are mutually isolated.
|
||||
|
||||
Select the interface type you want to add, and click `Add`. Another dialog window will open, allowing you to edit any available settings for your chosen interface type. For information about available settings, see the respective sections of the [citetitle]_{PRODUCT} Networking{nbsp}Guide_, available at link:++https://docs.fedoraproject.org/++[]. Basic documentation is also available in xref:Installing_Using_Anaconda.adoc#sect-installation-gui-network-configuration-advanced[Editing Network Interface Configuration].
|
||||
Select the interface type you want to add, and click `Add`. Another dialog window will open, allowing you to edit any available settings for your chosen interface type. For information about available settings, see the respective sections of the [citetitle]_{PRODUCT} Networking{nbsp}Guide_, available at link:++https://docs.fedoraproject.org/++[]. Basic documentation is also available in xref:install/Installing_Using_Anaconda.adoc#sect-installation-gui-network-configuration-advanced[Editing Network Interface Configuration].
|
||||
|
||||
[NOTE]
|
||||
====
|
||||
|
|
|
|||
|
|
@ -11,7 +11,7 @@ This screen is only available if xref:Installing_Using_Anaconda.adoc#sect-instal
|
|||
[NOTE]
|
||||
====
|
||||
|
||||
It is not possible to select specific packages during a manual installation. You can only select pre-defined environments and add-ons. If you need to control exactly which packages are installed, you must use a Kickstart file and define the packages in the [command]#%packages# section. See xref:../advanced/Kickstart_Installations.adoc#chap-kickstart-installations[Automating the Installation with Kickstart] for information about Kickstart installations.
|
||||
It is not possible to select specific packages during a manual installation. You can only select pre-defined environments and add-ons. If you need to control exactly which packages are installed, you must use a Kickstart file and define the packages in the [command]#%packages# section. See xref:advanced/Kickstart_Installations.adoc#chap-kickstart-installations[Automating the Installation with Kickstart] for information about Kickstart installations.
|
||||
|
||||
====
|
||||
|
||||
|
|
@ -25,6 +25,6 @@ To configure your software selection, first choose an environment on the left si
|
|||
|
||||
The list of add-ons is divided into two parts by a horizontal line. Add-ons above this line are defined as part of your chosen environment; if you select a different environment, the add-ons available here will change. The add-ons displayed below the separator are not specific to your chosen environment.
|
||||
|
||||
Environments and add-ons are defined using a `comps.xml` file in your installation source (for example, in the `repodata/` directory on the full Fedora{nbsp}Server installation DVD). Review this file to see exactly which packages will be installed as part of a certain environment or add-on. For more information about the `comps.xml` file, see xref:../appendixes/Kickstart_Syntax_Reference.adoc#sect-kickstart-packages[%packages (required) - Package Selection].
|
||||
Environments and add-ons are defined using a `comps.xml` file in your installation source (for example, in the `repodata/` directory on the full Fedora{nbsp}Server installation DVD). Review this file to see exactly which packages will be installed as part of a certain environment or add-on. For more information about the `comps.xml` file, see xref:appendixes/Kickstart_Syntax_Reference.adoc#sect-kickstart-packages[%packages (required) - Package Selection].
|
||||
|
||||
After you finish configuring your software selection, click `Done` in the top left corner to return to xref:Installing_Using_Anaconda.adoc#sect-installation-gui-installation-summary[Installation Summary].
|
||||
|
|
|
|||
|
|
@ -9,7 +9,7 @@ The `Installation Source` screen allows you to specify a location (local or on t
|
|||
[NOTE]
|
||||
====
|
||||
|
||||
Normally, when you first enter the `Installation Summary` screen, the installer will attempt to configure an installation source based on the type of media you used to boot. The full {PRODUCT} Server DVD will configure the source as local media, the netinst ISO image will configure the closest network mirror, etc. This process takes some time, especially if the default source is a network mirror. If you plan to use a custom installation source, use the [option]#inst.askmethod# boot option to skip the initial configuration; this will allow you to enter this screen immediately. See xref:../advanced/Boot_Options.adoc#sect-boot-options-sources[Specifying the Installation Source] for information about boot options.
|
||||
Normally, when you first enter the `Installation Summary` screen, the installer will attempt to configure an installation source based on the type of media you used to boot. The full {PRODUCT} Server DVD will configure the source as local media, the netinst ISO image will configure the closest network mirror, etc. This process takes some time, especially if the default source is a network mirror. If you plan to use a custom installation source, use the [option]#inst.askmethod# boot option to skip the initial configuration; this will allow you to enter this screen immediately. See xref:advanced/Boot_Options.adoc#sect-boot-options-sources[Specifying the Installation Source] for information about boot options.
|
||||
|
||||
====
|
||||
|
||||
|
|
@ -45,7 +45,7 @@ To configure a proxy for an HTTP or HTTPS source, click the btn:[Proxy setup] bu
|
|||
+
|
||||
If your HTTP or HTTPS URL refers to a repository mirror list, mark the check box under the address field.
|
||||
|
||||
You can also specify additional repositories in the `Additional repositories` section to gain access to more installation environments and software add-ons. All environments and add-ons will be available for selection in xref:Installing_Using_Anaconda.adoc#sect-installation-gui-software-selection[Software Selection] once you finish configuring the sources.
|
||||
You can also specify additional repositories in the `Additional repositories` section to gain access to more installation environments and software add-ons. All environments and add-ons will be available for selection in xref:install/Installing_Using_Anaconda.adoc#sect-installation-gui-software-selection[Software Selection] once you finish configuring the sources.
|
||||
|
||||
To add a repository, click the btn:[+] button. To delete a repository, select one in the list and click the btn:[-] button. Click the arrow icon to revert to the previous list of repositories, i.e. to replace current entries with those that were present at the time you entered the `Installation Source` screen. To activate or deactivate a repository, click the check box in the `Enabled` column at each entry in the list.
|
||||
|
||||
|
|
|
|||
|
|
@ -20,7 +20,7 @@ image::anaconda/StorageSpoke.png[The Installation Destination screen. There are
|
|||
|
||||
In the top part of the screen, all locally available storage devices (SATA, IDE and SCSI hard drives, USB flash drives, etc.) are displayed in the `Local Standard Disks` section. Local disks are detected when the installer starts - any storage devices connected after the installation has started will not be shown.
|
||||
|
||||
If you need to configure additional local storage devices, select `I will configure partitioning` and press `Done` to move to xref:Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning[Manual Partitioning]. Then, connect any new hard drives you want to make available during the installation, and press the button marked by a circular arrow in the set of controls below the list of mount points on the left side of the screen. In the dialog window that opens, press `Rescan Disks` and wait until the scanning process completes. Then, press `OK` to return to xref:Installing_Using_Anaconda.adoc#sect-installation-gui-storage-partitioning[Installation Destination]; all detected disks including any new ones will be displayed in the `Local Standard Disks` section.
|
||||
If you need to configure additional local storage devices, select `I will configure partitioning` and press `Done` to move to xref:Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning[Manual Partitioning]. Then, connect any new hard drives you want to make available during the installation, and press the button marked by a circular arrow in the set of controls below the list of mount points on the left side of the screen. In the dialog window that opens, press `Rescan Disks` and wait until the scanning process completes. Then, press `OK` to return to xref:install/Installing_Using_Anaconda.adoc#sect-installation-gui-storage-partitioning[Installation Destination]; all detected disks including any new ones will be displayed in the `Local Standard Disks` section.
|
||||
|
||||
The `Specialized & Network Disks` section below shows advanced network storage (such as iSCSI and FCoE disks) currently configured. When you first open this screen, no such devices will be displayed because they can not be automatically detected; to search for network storage devices, press `Add a disk` button and proceed with xref:Installing_Using_Anaconda.adoc#sect-installation-gui-installation-destination[Installation Destination - Specialized & Network Disks]. Any network storage you configure will then show up in the `Specialized & Network Disks` the same way local disks are shown above.
|
||||
|
||||
|
|
@ -50,11 +50,11 @@ Additionally, you can select `Encrypt my data`pass:attributes[{blank}]; this wil
|
|||
[WARNING]
|
||||
====
|
||||
|
||||
If you lose the LUKS passphrase, any encrypted partitions and the data on them will become completely inaccessible. There is no way to recover a lost passphrase. However, if you perform a Kickstart installation, you can save encryption passphrases and create backup encryption passphrases during the installation. See xref:../advanced/Kickstart_Installations.adoc#chap-kickstart-installations[Automating the Installation with Kickstart] for information about Kickstart installations.
|
||||
If you lose the LUKS passphrase, any encrypted partitions and the data on them will become completely inaccessible. There is no way to recover a lost passphrase. However, if you perform a Kickstart installation, you can save encryption passphrases and create backup encryption passphrases during the installation. See xref:advanced/Kickstart_Installations.adoc#chap-kickstart-installations[Automating the Installation with Kickstart] for information about Kickstart installations.
|
||||
|
||||
====
|
||||
|
||||
To control which one of your selected storage devices will contain the _boot loader_, click the `Full disk summary and bootloader` link in the bottom left corner of the screen, and follow the instructions in xref:Installing_Using_Anaconda.adoc#sect-installation-gui-storage-partitioning-bootloader[Boot Loader Installation]. Note that while in most cases it is sufficient to leave the boot loader in the default location, some configurations (for example, systems which require _chain loading_ from another boot loader) will require the boot drive to be specified manually.
|
||||
To control which one of your selected storage devices will contain the _boot loader_, click the `Full disk summary and bootloader` link in the bottom left corner of the screen, and follow the instructions in xref:install/Installing_Using_Anaconda.adoc#sect-installation-gui-storage-partitioning-bootloader[Boot Loader Installation]. Note that while in most cases it is sufficient to leave the boot loader in the default location, some configurations (for example, systems which require _chain loading_ from another boot loader) will require the boot drive to be specified manually.
|
||||
|
||||
After you select storage devices, choose between automatic and manual partitioning, configure encryption and boot loader location, press `Done` in the top left corner of the screen. Then, depending on your settings, the following will happen:
|
||||
|
||||
|
|
|
|||
|
|
@ -5,7 +5,7 @@ include::{partialsdir}/entities.adoc[]
|
|||
[[chap-anaconda-boot-options]]
|
||||
= Boot Options
|
||||
|
||||
The [application]*Anaconda* installer includes a range of boot options for administrators, which modify the default behavior of the installation program by enabling or disabling certain functions. To use one or more boot options, you either have to boot from installation media and append these options at the boot menu (see xref:../install/Booting_the_Installation.adoc#sect-boot-menu[The Boot Menu]), or you must add them into your PXE server configuration file if you are booting from a network (see xref:Network_based_Installations.adoc#chap-pxe-server-setup[Setting Up an Installation Server]).
|
||||
The [application]*Anaconda* installer includes a range of boot options for administrators, which modify the default behavior of the installation program by enabling or disabling certain functions. To use one or more boot options, you either have to boot from installation media and append these options at the boot menu (see xref:install/Booting_the_Installation.adoc#sect-boot-menu[The Boot Menu]), or you must add them into your PXE server configuration file if you are booting from a network (see xref:advanced/Network_based_Installations.adoc#chap-pxe-server-setup[Setting Up an Installation Server]).
|
||||
|
||||
You can use multiple options at the same time; in that case, separate them by a single space.
|
||||
|
||||
|
|
@ -27,7 +27,7 @@ Boot options specific to the installation program always start with `inst.` in t
|
|||
[[sect-boot-options-installer]]
|
||||
== Configuring the Installation System at the Boot Menu
|
||||
|
||||
The exact way to specify custom boot options is differs based on your system's architecture, firmware and the method you use to boot the installation. If you are booting from local media, you can specify options in the boot menu, before you begin the installation; if you are booting from a network using a PXE server, you must add boot options into the boot loader configuration file before you boot the installation system. For specific instructions, see 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.
|
||||
The exact way to specify custom boot options is differs based on your system's architecture, firmware and the method you use to boot the installation. If you are booting from local media, you can specify options in the boot menu, before you begin the installation; if you are booting from a network using a PXE server, you must add boot options into the boot loader configuration file before you boot the installation system. For specific instructions, see xref:install/Booting_the_Installation.adoc#sect-boot-menu[The Boot Menu] if you are booting from local media, and xref:advanced/Network_based_Installations.adoc#chap-pxe-server-setup[Setting Up an Installation Server] if you are booting from a server.
|
||||
|
||||
[[sect-boot-options-available]]
|
||||
== Available Boot Options
|
||||
|
|
@ -163,7 +163,7 @@ You can use this option multiple times. In that case, the boot message will be d
|
|||
|
||||
[option]#noshell#:: Disables access to the root shell during the installation. This is useful with automated (Kickstart) installations - if you use this option, a user can watch the installation progress, but they cannot interfere with it by accessing the root shell by pressing kbd:[Ctrl + Alt + F2].
|
||||
|
||||
[option]#inst.lang=#:: Sets the language to be used during the installation. Language codes are the same as the ones used in the [command]#lang# Kickstart command as described in xref:../appendixes/Kickstart_Syntax_Reference.adoc#sect-kickstart-commands-lang[lang (optional) - Configure Language During Installation]. On systems where the [package]*system-config-language* package is installed, a list of valid values can also be find in `/usr/share/system-config-language/locale-list`.
|
||||
[option]#inst.lang=#:: Sets the language to be used during the installation. Language codes are the same as the ones used in the [command]#lang# Kickstart command as described in xref:appendixes/Kickstart_Syntax_Reference.adoc#sect-kickstart-commands-lang[lang (optional) - Configure Language During Installation]. On systems where the [package]*system-config-language* package is installed, a list of valid values can also be find in `/usr/share/system-config-language/locale-list`.
|
||||
+
|
||||
If you perform the installation interactively, the language you specified using this option will be selected by default, but you will still be able to change it at the beginning of the graphical installation.
|
||||
|
||||
|
|
@ -184,7 +184,7 @@ The _value_ parameter can be any of the following:
|
|||
+
|
||||
If this option is not specified, [application]*Anaconda* will use `provider_fedora_geoip`.
|
||||
|
||||
[option]#inst.keymap=#:: Specifies the keyboard layout to be used by the installation program. Layout codes are the same as the ones used in the [command]#keyboard# Kickstart command as described in xref:../appendixes/Kickstart_Syntax_Reference.adoc#appe-kickstart-syntax-reference[Kickstart Syntax Reference].
|
||||
[option]#inst.keymap=#:: Specifies the keyboard layout to be used by the installation program. Layout codes are the same as the ones used in the [command]#keyboard# Kickstart command as described in xref:appendixes/Kickstart_Syntax_Reference.adoc#appe-kickstart-syntax-reference[Kickstart Syntax Reference].
|
||||
|
||||
[option]#inst.text#:: Forces the installation program to run in text mode instead of graphical mode. The text user interface is limited, for example, it does not allow you to modify the partition layout or set up LVM. When installing a system on a machine with a limited graphical capabilities, it is recommended to use VNC as described in xref:Boot_Options.adoc#sect-boot-options-vnc[Enabling Remote Access Using VNC].
|
||||
|
||||
|
|
@ -213,7 +213,7 @@ modprobe.blacklist=ahci,firewire_ohci
|
|||
[NOTE]
|
||||
====
|
||||
|
||||
During the installation, the `root` account has no password by default. You can set a root password to be used during the installation with the [command]#sshpw# Kickstart command as described in xref:../appendixes/Kickstart_Syntax_Reference.adoc#sect-kickstart-commands-sshpw[sshpw (optional) - Restrict ssh Access During Installation].
|
||||
During the installation, the `root` account has no password by default. You can set a root password to be used during the installation with the [command]#sshpw# Kickstart command as described in xref:appendixes/Kickstart_Syntax_Reference.adoc#sect-kickstart-commands-sshpw[sshpw (optional) - Restrict ssh Access During Installation].
|
||||
|
||||
====
|
||||
|
||||
|
|
@ -334,7 +334,7 @@ This only applies to packages directly specified in the `%packages` section. If
|
|||
+
|
||||
Normally, BIOS-based systems and UEFI-based systems in BIOS compatibility mode will attempt to use the MBR schema for storing partitioning information, unless the disk is larger than 2 TB. Using this option will change this behavior, allowing a GPT to be written even to disks smaller than 2 TB.
|
||||
+
|
||||
See xref:../install/Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-recommended[Recommended Partitioning Scheme] for more information about GPT and MBR, and xref:../appendixes/Disk_Partitions.adoc#sect-disk-partitioning-guid-partition-table[GUID Partition Table (GPT)] for more general information about GPT, MBR and disk partitioning in general.
|
||||
See xref:install/Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-recommended[Recommended Partitioning Scheme] for more information about GPT and MBR, and xref:appendixes/Disk_Partitions.adoc#sect-disk-partitioning-guid-partition-table[GUID Partition Table (GPT)] for more general information about GPT, MBR and disk partitioning in general.
|
||||
|
||||
[option]#inst.nosave=#:: This option controls which Kickstart files and installation logs are saved to the installed system. It can be especially useful to disable saving such data when performing OEM operating system installations, or when generating images using sensitive resources (such as internal repository URLs), as these resources might otherwise be mentioned in kickstart files and/or logs on the image. Possible values for this option are:
|
||||
+
|
||||
|
|
@ -358,12 +358,12 @@ By default, swap on zRAM is enabled on systems with 2 GB or less RAM, and disabl
|
|||
|
||||
[option]#inst.nodnf#:: Use the older [application]*Yum* backend for package installation and dependency resolution instead of [application]*DNF*. See the [citetitle]_{PRODUCT} System Administrator's Guide_, available at link:++https://docs.fedoraproject.org/++[], for details about [application]*DNF*.
|
||||
|
||||
[option]#inst.kdump_addon=#:: Turns the [application]*Kdump* installer add-on `on` or `off` (the add-on is off by default). If you use [option]#inst.kdump_addon=on#, a new screen, which allows you to configure the [application]*Kdump* kernel crash dumping mechanism, will appear in the main menu of the graphical or text interface (see xref:../install/Installing_Using_Anaconda.adoc#sect-installation-gui-kdump[Kdump]). Enabling this add-on is also necessary to use the xref:../appendixes/Kickstart_Syntax_Reference.adoc#sect-kickstart-commands-kdump[%addon com_redhat_kdump (optional) - Configure kdump] Kickstart command.
|
||||
[option]#inst.kdump_addon=#:: Turns the [application]*Kdump* installer add-on `on` or `off` (the add-on is off by default). If you use [option]#inst.kdump_addon=on#, a new screen, which allows you to configure the [application]*Kdump* kernel crash dumping mechanism, will appear in the main menu of the graphical or text interface (see xref:install/Installing_Using_Anaconda.adoc#sect-installation-gui-kdump[Kdump]). Enabling this add-on is also necessary to use the xref:appendixes/Kickstart_Syntax_Reference.adoc#sect-kickstart-commands-kdump[%addon com_redhat_kdump (optional) - Configure kdump] Kickstart command.
|
||||
|
||||
[[sect-boot-options-vnc]]
|
||||
=== Enabling Remote Access Using VNC
|
||||
|
||||
The following options are necessary to configure [application]*Anaconda* for remote graphical installation. See xref:VNC_Installations.adoc#chap-vnc-installations[Installing Using VNC] for more details.
|
||||
The following options are necessary to configure [application]*Anaconda* for remote graphical installation. See xref:advanced/VNC_Installations.adoc#chap-vnc-installations[Installing Using VNC] for more details.
|
||||
|
||||
[option]#inst.vnc#:: Specifies that the installation program's graphical interface should be run in a `VNC` session. If you specify this option, you will need to connect to the system using a `VNC` client application to be able to interact with the installation program. `VNC` sharing is enabled, so multiple clients can connect to the system at the same time.
|
||||
+
|
||||
|
|
@ -490,7 +490,7 @@ The following options are removed. They were present in previous releases of {PR
|
|||
|
||||
[option]#noipv6#:: Used to disable IPv6 support in the installation program. IPv6 is now built into the kernel so the driver cannot be blacklisted; however, it is possible to disable IPv6 using the [option]#ipv6.disable# option.
|
||||
|
||||
[option]#upgradeany#:: Upgrades are done in a different way in current {PRODUCT} releases. For more information about upgrading your system, see xref:Upgrading_Your_Current_System.adoc#chap-upgrading[Upgrading Your Current System].
|
||||
[option]#upgradeany#:: Upgrades are done in a different way in current {PRODUCT} releases. For more information about upgrading your system, see xref:advanced/Upgrading_Your_Current_System.adoc#chap-upgrading[Upgrading Your Current System].
|
||||
|
||||
[option]#vlanid=#:: Used to configure Virtual LAN (802.1q tag) devices. Use the [option]#vlan=# option instead.
|
||||
|
||||
|
|
|
|||
|
|
@ -29,7 +29,7 @@ This chapter explains these steps in detail.
|
|||
[[sect-kickstart-file-create]]
|
||||
=== Creating a Kickstart File
|
||||
|
||||
The Kickstart file itself is a plain text file, containing keywords listed in xref:../appendixes/Kickstart_Syntax_Reference.adoc#appe-kickstart-syntax-reference[Kickstart Syntax Reference], which serve as directions for the installation. Any text editor able to save files as ASCII text (such as [application]*Gedit* or [application]*vim* on Linux systems or [application]*Notepad* on Windows systems) can be used to create and edit Kickstart files.
|
||||
The Kickstart file itself is a plain text file, containing keywords listed in xref:appendixes/Kickstart_Syntax_Reference.adoc#appe-kickstart-syntax-reference[Kickstart Syntax Reference], which serve as directions for the installation. Any text editor able to save files as ASCII text (such as [application]*Gedit* or [application]*vim* on Linux systems or [application]*Notepad* on Windows systems) can be used to create and edit Kickstart files.
|
||||
|
||||
The recommended approach to creating Kickstart files is to perform a manual installation on one system first. After the installation completes, all choices made during the installation are saved into a file named `anaconda-ks.cfg`, located in the `/root/` directory on the installed system. You can then copy this file, make any changes you need, and use the resulting configuration file in further installations.
|
||||
|
||||
|
|
@ -39,11 +39,11 @@ When creating a Kickstart file, keep in mind the following:
|
|||
|
||||
* Sections must be specified *in order*. Items within the sections do not have to be in a specific order unless otherwise specified. The correct section order is:
|
||||
+
|
||||
** The command section which contains actual Kickstart commands and options as listed in xref:../appendixes/Kickstart_Syntax_Reference.adoc#appe-kickstart-syntax-reference[Kickstart Syntax Reference]. Note that some commands, such as [command]#install#, are mandatory, but most commands are optional.
|
||||
** The command section which contains actual Kickstart commands and options as listed in xref:appendixes/Kickstart_Syntax_Reference.adoc#appe-kickstart-syntax-reference[Kickstart Syntax Reference]. Note that some commands, such as [command]#install#, are mandatory, but most commands are optional.
|
||||
+
|
||||
** The [command]#%packages# section which contains a list of packages and package groups to be installed. See xref:../appendixes/Kickstart_Syntax_Reference.adoc#sect-kickstart-packages[%packages (required) - Package Selection] for details.
|
||||
** The [command]#%packages# section which contains a list of packages and package groups to be installed. See xref:appendixes/Kickstart_Syntax_Reference.adoc#sect-kickstart-packages[%packages (required) - Package Selection] for details.
|
||||
+
|
||||
** The [command]#%pre# and [command]#%post# sections, containing a pre-installation and post-installation scripts. These two sections can be in any order and are not mandatory. See xref:../appendixes/Kickstart_Syntax_Reference.adoc#sect-kickstart-preinstall[%pre (optional) - Pre-installation Script] and xref:../appendixes/Kickstart_Syntax_Reference.adoc#sect-kickstart-postinstall[%post (optional) - Post-installation Script] for details.
|
||||
** The [command]#%pre# and [command]#%post# sections, containing a pre-installation and post-installation scripts. These two sections can be in any order and are not mandatory. See xref:appendixes/Kickstart_Syntax_Reference.adoc#sect-kickstart-preinstall[%pre (optional) - Pre-installation Script] and xref:appendixes/Kickstart_Syntax_Reference.adoc#sect-kickstart-postinstall[%post (optional) - Post-installation Script] for details.
|
||||
+
|
||||
[IMPORTANT]
|
||||
====
|
||||
|
|
@ -95,9 +95,9 @@ Once you create a Kickstart file, you can place it in one of the following locat
|
|||
|
||||
Normally, a Kickstart file is copied to removable media or a hard drive, or made available on the network. Placing the file in a network location complements the usual approach to Kickstart installations, which is also network-based: the system is booted using a PXE server, the Kickstart file is downloaded from a network share, and software packages specified in the file are downloaded from remote repositories.
|
||||
|
||||
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.
|
||||
xref:advanced/Network_based_Installations.adoc#chap-pxe-server-setup[Setting Up an Installation Server] offers some additional information about preparing for a network-based installation.
|
||||
|
||||
[[sect-kickstart-installation-starting]]
|
||||
=== Starting the Kickstart Installation
|
||||
|
||||
Once you have everything ready - you have created a valid Kickstart file and you have either local boot media or a PXE server available, you can start the Kickstart installation. You need to use the [option]#inst.ks=# boot option either in the boot menu (when booting from local media), or add this option to your PXE server configuration. For information about boot options used in Kickstart installations, see xref:Boot_Options.adoc#sect-boot-options-kickstart[Kickstart Boot Options].
|
||||
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:advanced/Boot_Options.adoc#sect-boot-options-kickstart[Kickstart Boot Options].
|
||||
|
|
|
|||
|
|
@ -33,7 +33,7 @@ Because the job of booting an operating system is too complex for the pre-boot e
|
|||
The kernel is the core of any Linux operating system, and the initramfs provides the kernel with required tools and resources. These files are also provided by tftp.
|
||||
|
||||
.Package repository
|
||||
A Fedora repository must be available for the installation. The example in this section uses the public Fedora mirrors as the repository source, but you can also use a repo on the local network provided by NFS, FTP, or HTTP. Repositories can be configured using the [option]#inst.repo=# boot option; see xref:Boot_Options.adoc#sect-boot-options-sources[Specifying the Installation Source] for details.
|
||||
A Fedora repository must be available for the installation. The example in this section uses the public Fedora mirrors as the repository source, but you can also use a repo on the local network provided by NFS, FTP, or HTTP. Repositories can be configured using the [option]#inst.repo=# boot option; see xref:advanced/Boot_Options.adoc#sect-boot-options-sources[Specifying the Installation Source] for details.
|
||||
|
||||
//A link to mirrormanager and some instructions to other guides too. All the elaboration on installation methods might be going to far, but we can ref. --Pete
|
||||
|
||||
|
|
|
|||
|
|
@ -21,4 +21,4 @@ Always back up your data before performing an upgrade or reinstalling your syste
|
|||
[[sect-upgrading-fedora-manual-reinstall]]
|
||||
== Manual System Upgrade or Reinstallation
|
||||
|
||||
Unfortunately, we have not written this chapter yet, and there is no dedicated documentation about a manual reinstall on the Wiki, either. In the meantime before we fix this, you can try to start the installation normally (from a boot CD/DVD/USB), select manual partitioning in your installer, and reuse existing partitions instead of destroying them and creating new ones. The instructions at xref:../install/Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning[Manual Partitioning] should in most cases be easy to adapt for this.
|
||||
Unfortunately, we have not written this chapter yet, and there is no dedicated documentation about a manual reinstall on the Wiki, either. In the meantime before we fix this, you can try to start the installation normally (from a boot CD/DVD/USB), select manual partitioning in your installer, and reuse existing partitions instead of destroying them and creating new ones. The instructions at xref:install/Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning[Manual Partitioning] should in most cases be easy to adapt for this.
|
||||
|
|
|
|||
|
|
@ -76,7 +76,7 @@ VNC Direct Mode is when the VNC viewer initiates a connection to the system bein
|
|||
+
|
||||
image::vnc/connection-details.png[TigerVNC after startup, showing the Connection Details dialog]
|
||||
|
||||
. Boot the installation system and wait for the boot menu to appear. In the menu, edit boot options (see xref:../install/Booting_the_Installation.adoc#sect-boot-menu[The Boot Menu]) and append the [option]#inst.vnc# option to the end of the command line.
|
||||
. Boot the installation system and wait for the boot menu to appear. In the menu, edit boot options (see xref:install/Booting_the_Installation.adoc#sect-boot-menu[The Boot Menu]) and append the [option]#inst.vnc# option to the end of the command line.
|
||||
+
|
||||
Optionally, if you want to restrict VNC access to the installation system, add the [option]#inst.vncpassword=pass:attributes[{blank}]_PASSWORD_pass:attributes[{blank}]# boot option as well. Replace _PASSWORD_ with the password you want to use for the installation. The VNC password must be between 6 and 8 characters long.
|
||||
+
|
||||
|
|
@ -105,7 +105,7 @@ Note the IP address and port number (in the above example, `192.168.100.131:5901
|
|||
|
||||
When the connection is successfully established, a new window will open on the system running the VNC viewer, displaying the installation menu. This window will provide full remote access to the installer until the installation finishes and the system reboots for the first time.
|
||||
|
||||
You can then proceed with xref:../install/Installing_Using_Anaconda.adoc#chap-installing-using-anaconda[Installing Using Anaconda].
|
||||
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
|
||||
|
|
@ -144,7 +144,7 @@ main: Listening on port 5901
|
|||
+
|
||||
When this message is displayed, the VNC viewer is ready and waiting for an incoming connection from the installation system.
|
||||
|
||||
. Boot the installation system and wait for the boot menu to appear. In the menu, edit boot options (see xref:../install/Booting_the_Installation.adoc#sect-boot-menu[The Boot Menu]) and append the following options to the end of the command line:
|
||||
. Boot the installation system and wait for the boot menu to appear. In the menu, edit boot options (see xref:install/Booting_the_Installation.adoc#sect-boot-menu[The Boot Menu]) and append the following options to the end of the command line:
|
||||
+
|
||||
[subs="quotes, macros"]
|
||||
----
|
||||
|
|
@ -157,19 +157,19 @@ Replace _HOST_ with the IP address of the system running the listening VNC viewe
|
|||
+
|
||||
When the connection is successfully established, a new window will open on the system running the VNC viewer, displaying the installation menu. This window will provide full remote access to the installer until the installation finishes and the system reboots for the first time.
|
||||
|
||||
You can then proceed with xref:../install/Installing_Using_Anaconda.adoc#chap-installing-using-anaconda[Installing Using Anaconda].
|
||||
You can then proceed with xref:install/Installing_Using_Anaconda.adoc#chap-installing-using-anaconda[Installing Using Anaconda].
|
||||
|
||||
[[sect-vnc-kickstart-considerations]]
|
||||
== Kickstart Considerations
|
||||
|
||||
Commands for using a VNC installation are also available in Kickstart installations. Using just the [command]#vnc# command will set up an installation using Direct Mode. Options are available to set up an installation using Connect Mode. For more information about the [command]#vnc# command and options used in Kickstart files, see xref:../appendixes/Kickstart_Syntax_Reference.adoc#appe-kickstart-syntax-reference[Kickstart Syntax Reference].
|
||||
Commands for using a VNC installation are also available in Kickstart installations. Using just the [command]#vnc# command will set up an installation using Direct Mode. Options are available to set up an installation using Connect Mode. For more information about the [command]#vnc# command and options used in Kickstart files, see xref:appendixes/Kickstart_Syntax_Reference.adoc#appe-kickstart-syntax-reference[Kickstart Syntax Reference].
|
||||
|
||||
[[sect-vnc-headless-considerations]]
|
||||
== Considerations for Headless Systems
|
||||
|
||||
When installing headless systems, the only choices are an automated Kickstart installation or an interactive VNC installation using connect mode. For more information about automated Kickstart installation, see xref:../appendixes/Kickstart_Syntax_Reference.adoc#appe-kickstart-syntax-reference[Kickstart Syntax Reference]. The general process for an interactive VNC installation is described below.
|
||||
When installing headless systems, the only choices are an automated Kickstart installation or an interactive VNC installation using connect mode. For more information about automated Kickstart installation, see xref:appendixes/Kickstart_Syntax_Reference.adoc#appe-kickstart-syntax-reference[Kickstart Syntax Reference]. The general process for an interactive VNC installation is described below.
|
||||
|
||||
. Set up a PXE server that will be used to start the installation. Information about installing and performing basic configurating of a PXE server can be found in xref:Network_based_Installations.adoc#chap-pxe-server-setup[Setting Up an Installation Server].
|
||||
. Set up a PXE server that will be used to start the installation. Information about installing and performing basic configurating of a PXE server can be found in xref:advanced/Network_based_Installations.adoc#chap-pxe-server-setup[Setting Up an Installation Server].
|
||||
|
||||
. Configure the PXE server to use the boot options for a connect mode VNC installation. For information on these boot options, see xref:VNC_Installations.adoc#sect-vnc-installations-connect-mode[Installing in VNC Connect Mode].
|
||||
|
||||
|
|
|
|||
|
|
@ -357,4 +357,4 @@ At this point in the process of preparing to install {PRODUCT}, you should give
|
|||
|
||||
Unless you have a reason for doing otherwise, you should *at least* create a `/boot` partition and a `/` (root) partition. Depending on your system's hardware specifications, additional partitions may be necessary, such as `/boot/efi` for 64-bit AMD and Intel systems with UEFI firmware, a `biosboot` partition for AMD and Intel systems with a GUID Partition Table (GPT) label on the system disk, or a `PReP Boot` partition on IBM Power Systems servers.
|
||||
|
||||
See xref:../install/Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-recommended[Recommended Partitioning Scheme] for more information about the recommended partitioning scheme.
|
||||
See xref:install/Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-recommended[Recommended Partitioning Scheme] for more information about the recommended partitioning scheme.
|
||||
|
|
|
|||
|
|
@ -5,7 +5,7 @@ include::{partialsdir}/entities.adoc[]
|
|||
[[appe-kickstart-syntax-reference]]
|
||||
= Kickstart Syntax Reference
|
||||
|
||||
This appendix describes commands and options available in Kickstart installations. For general information about Kickstart, see xref:../advanced/Kickstart_Installations.adoc#chap-kickstart-installations[Automating the Installation with Kickstart].
|
||||
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].
|
||||
|
||||
toc::[]
|
||||
|
||||
|
|
@ -199,7 +199,7 @@ This command also supports installation from tar archives of the root file syste
|
|||
[[sect-kickstart-commands-mediacheck]]
|
||||
=== mediacheck (optional) - Verify Installation Media Integrity
|
||||
|
||||
This command will force the installation program to perform a media check before starting the installation, similarly to the [option]#rd.live.check# boot option (see 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.
|
||||
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
|
||||
|
|
@ -297,7 +297,7 @@ The [command]#autopart# option cannot be used together with the [command]#part/p
|
|||
+
|
||||
** `thinp`: The LVM Thin Provisioning partitioning scheme.
|
||||
+
|
||||
The created partitioning scheme will follow the recommended scheme described at xref:../install/Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-recommended[Recommended Partitioning Scheme].
|
||||
The created partitioning scheme will follow the recommended scheme described at xref:install/Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-recommended[Recommended Partitioning Scheme].
|
||||
|
||||
[option]#--fstype=#:: Specify a supported file system (such as `ext4` or `xfs`) to replace the default when doing automatic partitioning.
|
||||
|
||||
|
|
@ -342,7 +342,7 @@ You should always use a password to protect your boot loader. An unprotected boo
|
|||
[IMPORTANT]
|
||||
====
|
||||
|
||||
Some systems require a special partition for installing the boot loader. The type and size of this partition depends on whether the disk you are installing the boot loader to uses the _Master Boot Record_ (MBR) or a _GUID Partition Table_ (GPT) schema. For more information, see xref:../install/Installing_Using_Anaconda.adoc#sect-installation-gui-storage-partitioning-bootloader[Boot Loader Installation].
|
||||
Some systems require a special partition for installing the boot loader. The type and size of this partition depends on whether the disk you are installing the boot loader to uses the _Master Boot Record_ (MBR) or a _GUID Partition Table_ (GPT) schema. For more information, see xref:install/Installing_Using_Anaconda.adoc#sect-installation-gui-storage-partitioning-bootloader[Boot Loader Installation].
|
||||
|
||||
====
|
||||
|
||||
|
|
@ -727,7 +727,7 @@ To determine the size of the swap partition automatically but also allow extra s
|
|||
+
|
||||
The size assigned will be equivalent to the swap space assigned by [option]#--recommended# plus the amount of RAM on your system.
|
||||
+
|
||||
For the swap sizes assigned by these commands, see the section describing swap in xref:../install/Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-recommended[Recommended Partitioning Scheme].
|
||||
For the swap sizes assigned by these commands, see the section describing swap in xref:install/Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-recommended[Recommended Partitioning Scheme].
|
||||
+
|
||||
`none`::: Used only when creating a thin pool volume.
|
||||
|
||||
|
|
@ -735,7 +735,7 @@ For the swap sizes assigned by these commands, see the section describing swap i
|
|||
|
||||
[option]#--useexisting#:: Use an existing logical volume and format it.
|
||||
|
||||
[option]#--fstype=#:: Sets the file system type for the logical volume. Valid values are `xfs`, `ext2`, `ext3`, `ext4`, `swap`, and `vfat`. See xref:../install/Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-filesystems[Device, File System and RAID Types] for information about available file systems.
|
||||
[option]#--fstype=#:: Sets the file system type for the logical volume. Valid values are `xfs`, `ext2`, `ext3`, `ext4`, `swap`, and `vfat`. See xref:install/Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-filesystems[Device, File System and RAID Types] for information about available file systems.
|
||||
|
||||
[option]#--fsoptions=#:: Specifies a free form string of options to be used when mounting the filesystem. This string will be copied into the `/etc/fstab` file of the installed system and should be enclosed in quotes. For example:
|
||||
+
|
||||
|
|
@ -763,7 +763,7 @@ When creating a new logical volume, you must either specify its size statically
|
|||
|
||||
[option]#--maxsize=#:: The maximum size in megabytes when the logical volume is set to grow. Specify an integer value here such as `500` (do not include the unit).
|
||||
|
||||
[option]#--recommended#:: Use this option when creating a `swap` logical volume to determine the size of this volume automatically, based on your system's hardware. For details about the recommended scheme, see xref:../install/Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-recommended[Recommended Partitioning Scheme].
|
||||
[option]#--recommended#:: Use this option when creating a `swap` logical volume to determine the size of this volume automatically, based on your system's hardware. For details about the recommended scheme, see xref:install/Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-recommended[Recommended Partitioning Scheme].
|
||||
+
|
||||
[IMPORTANT]
|
||||
====
|
||||
|
|
@ -886,7 +886,7 @@ To determine the size of the swap partition automatically but also allow extra s
|
|||
+
|
||||
The size assigned will be equivalent to the swap space assigned by [option]#--recommended# plus the amount of RAM on your system.
|
||||
+
|
||||
For the swap sizes assigned by these commands, see the section describing swap in xref:../install/Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-recommended[Recommended Partitioning Scheme].
|
||||
For the swap sizes assigned by these commands, see the section describing swap in xref:install/Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-recommended[Recommended Partitioning Scheme].
|
||||
+
|
||||
`raid._id_pass:attributes[{blank}]`::: The partition is used for software RAID (see [command]#raid#).
|
||||
+
|
||||
|
|
@ -901,7 +901,7 @@ For the swap sizes assigned by these commands, see the section describing swap i
|
|||
[IMPORTANT]
|
||||
====
|
||||
|
||||
If the [option]#--size# value is too small, the installation will fail. Set the [option]#--size# value as the minimum amount of space you require. For size recommendations, see xref:../install/Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-recommended[Recommended Partitioning Scheme].
|
||||
If the [option]#--size# value is too small, the installation will fail. Set the [option]#--size# value as the minimum amount of space you require. For size recommendations, see xref:install/Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-recommended[Recommended Partitioning Scheme].
|
||||
|
||||
====
|
||||
|
||||
|
|
@ -969,11 +969,11 @@ part --onpart=sd*|hd*|vda,/dev/vdc
|
|||
+
|
||||
The above will match either of `sd*`, `hd*`, *or* `vda` *and* `/dev/vdc`. Variants are processed from left to right, and at least one of them must match for the command to succeed.
|
||||
|
||||
[option]#--asprimary#:: Forces the partition to be allocated as a *primary* partition. If the partition cannot be allocated as primary (usually due to too many primary partitions being already allocated), the partitioning process will fail. This option only makes sense when the disk uses a Master Boot Record (MBR); for GUID Partition Table (GPT)-labeled disks this option has no meaning. For information about primary (and extended) partitions, see xref:../install/Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-recommended[Recommended Partitioning Scheme].
|
||||
[option]#--asprimary#:: Forces the partition to be allocated as a *primary* partition. If the partition cannot be allocated as primary (usually due to too many primary partitions being already allocated), the partitioning process will fail. This option only makes sense when the disk uses a Master Boot Record (MBR); for GUID Partition Table (GPT)-labeled disks this option has no meaning. For information about primary (and extended) partitions, see xref:install/Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-recommended[Recommended Partitioning Scheme].
|
||||
|
||||
[option]#--fsprofile=#:: Specifies a _usage type_ to be passed to the program that makes a filesystem on this partition. A usage type defines a variety of tuning parameters to be used when making a filesystem. For this option to work, the filesystem must support the concept of usage types and there must be a configuration file that lists valid types. For `ext2`, `ext3`, `ext4`, this configuration file is `/etc/mke2fs.conf`.
|
||||
|
||||
[option]#--fstype=#:: Sets the file system type for the partition. Valid values are `xfs`, `ext2`, `ext3`, `ext4`, `swap`, `vfat`, `efi` and `biosboot`. For information about supported file systems, see xref:../install/Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-filesystems[Device, File System and RAID Types].
|
||||
[option]#--fstype=#:: Sets the file system type for the partition. Valid values are `xfs`, `ext2`, `ext3`, `ext4`, `swap`, `vfat`, `efi` and `biosboot`. For information about supported file systems, see xref:install/Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-filesystems[Device, File System and RAID Types].
|
||||
|
||||
[option]#--fsoptions=#:: Specifies a free form string of options to be used when mounting the filesystem. This string will be copied into the `/etc/fstab` file of the installed system and should be enclosed in quotes. For example:
|
||||
+
|
||||
|
|
@ -986,7 +986,7 @@ The above will match either of `sd*`, `hd*`, *or* `vda` *and* `/dev/vdc`. Varian
|
|||
|
||||
[option]#--label=#:: Assign a label to an individual partition.
|
||||
|
||||
[option]#--recommended#:: Determine the size of the partition automatically. For details about the recommended scheme, see xref:../install/Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-recommended[Recommended Partitioning Scheme].
|
||||
[option]#--recommended#:: Determine the size of the partition automatically. For details about the recommended scheme, see xref:install/Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-recommended[Recommended Partitioning Scheme].
|
||||
+
|
||||
[IMPORTANT]
|
||||
====
|
||||
|
|
@ -1036,7 +1036,7 @@ For a detailed example of [command]#raid# in action, see xref:Kickstart_Syntax_R
|
|||
|
||||
_mntpoint_:: Location where the RAID file system is mounted. If it is `/`, the RAID level must be 1 unless a boot partition (`/boot`) is present. If a boot partition is present, the `/boot` partition must be level 1 and the root (`/`) partition can be any of the available types. The _partitions*_ (which denotes that multiple partitions can be listed) lists the RAID identifiers to add to the RAID array.
|
||||
|
||||
[option]#--level=#:: RAID level to use (`0`, `1`, `4`, `5`, `6`, or `10`). See xref:../install/Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-filesystems[Device, File System and RAID Types] for information about various RAID types and their requirements.
|
||||
[option]#--level=#:: RAID level to use (`0`, `1`, `4`, `5`, `6`, or `10`). See xref:install/Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-filesystems[Device, File System and RAID Types] for information about various RAID types and their requirements.
|
||||
|
||||
[option]#--device=#:: Name of the RAID device to use. As of {PRODUCT}{nbsp}{PRODVER}, RAID devices are no longer referred to by names like `md0`. If you have an old (v0.90 metadata) array that you cannot assign a name to, you can specify the array by a filesystem label or UUID (for example, [option]#--device=rhel7-root --label=rhel7-root#).
|
||||
|
||||
|
|
@ -1044,7 +1044,7 @@ _mntpoint_:: Location where the RAID file system is mounted. If it is `/`, the
|
|||
|
||||
[option]#--fsprofile=#:: Specifies a _usage type_ to be passed to the program that makes a filesystem on this partition. A usage type defines a variety of tuning parameters to be used when making a filesystem. For this option to work, the filesystem must support the concept of usage types and there must be a configuration file that lists valid types. For `ext2`, `ext3`, `ext4`, this configuration file is `/etc/mke2fs.conf`.
|
||||
|
||||
[option]#--fstype=#:: Sets the file system type for the partition. Valid values are `xfs`, `ext2`, `ext3`, `ext4`, `swap`, `vfat`, `efi` and `biosboot`. For information about supported file systems, see xref:../install/Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-filesystems[Device, File System and RAID Types].
|
||||
[option]#--fstype=#:: Sets the file system type for the partition. Valid values are `xfs`, `ext2`, `ext3`, `ext4`, `swap`, `vfat`, `efi` and `biosboot`. For information about supported file systems, see xref:install/Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-filesystems[Device, File System and RAID Types].
|
||||
|
||||
[option]#--fsoptions=#:: Specifies a free form string of options to be used when mounting the filesystem. This string will be copied into the `/etc/fstab` file of the installed system and should be enclosed in quotes. For example:
|
||||
+
|
||||
|
|
@ -1812,7 +1812,7 @@ Perform the installation in a completely non-interactive command line mode. Any
|
|||
[IMPORTANT]
|
||||
====
|
||||
|
||||
For a fully automatic installation, you must either specify one of the available modes ([command]#graphical#, [command]#text#, or [command]#cmdline#) in the Kickstart file, or you must use the [option]#console=# boot option as described in xref:../advanced/Boot_Options.adoc#sect-boot-options-display[Console, Environment and Display Options]. Otherwise the system will halt and ask you to choose a mode.
|
||||
For a fully automatic installation, you must either specify one of the available modes ([command]#graphical#, [command]#text#, or [command]#cmdline#) in the Kickstart file, or you must use the [option]#console=# boot option as described in xref:advanced/Boot_Options.adoc#sect-boot-options-display[Console, Environment and Display Options]. Otherwise the system will halt and ask you to choose a mode.
|
||||
|
||||
====
|
||||
|
||||
|
|
@ -1824,7 +1824,7 @@ Perform the installation in graphical mode. This is the default. This command ta
|
|||
[IMPORTANT]
|
||||
====
|
||||
|
||||
For a fully automatic installation, you must either specify one of the available modes ([command]#graphical#, [command]#text#, or [command]#cmdline#) in the Kickstart file, or you must use the [option]#console=# boot option as described in xref:../advanced/Boot_Options.adoc#sect-boot-options-display[Console, Environment and Display Options]. Otherwise the system will halt and ask you to choose a mode.
|
||||
For a fully automatic installation, you must either specify one of the available modes ([command]#graphical#, [command]#text#, or [command]#cmdline#) in the Kickstart file, or you must use the [option]#console=# boot option as described in xref:advanced/Boot_Options.adoc#sect-boot-options-display[Console, Environment and Display Options]. Otherwise the system will halt and ask you to choose a mode.
|
||||
|
||||
====
|
||||
|
||||
|
|
@ -1869,7 +1869,7 @@ During the installation, you can interact with the installation program and moni
|
|||
[IMPORTANT]
|
||||
====
|
||||
|
||||
By default, the `ssh` server is not started during the installation. To make `ssh` available during the installation, boot the system with the kernel boot option [option]#inst.sshd#. See xref:../advanced/Boot_Options.adoc#sect-boot-options-display[Console, Environment and Display Options] for details.
|
||||
By default, the `ssh` server is not started during the installation. To make `ssh` available during the installation, boot the system with the kernel boot option [option]#inst.sshd#. See xref:advanced/Boot_Options.adoc#sect-boot-options-display[Console, Environment and Display Options] for details.
|
||||
|
||||
====
|
||||
|
||||
|
|
@ -1908,7 +1908,7 @@ Perform the Kickstart installation in text mode. Kickstart installations are per
|
|||
[IMPORTANT]
|
||||
====
|
||||
|
||||
For a fully automatic installation, you must either specify one of the available modes ([command]#graphical#, [command]#text#, or [command]#cmdline#) in the Kickstart file, or you must use the [option]#console=# boot option as described in xref:../advanced/Boot_Options.adoc#sect-boot-options-display[Console, Environment and Display Options]. Otherwise the system will halt and ask you to choose a mode.
|
||||
For a fully automatic installation, you must either specify one of the available modes ([command]#graphical#, [command]#text#, or [command]#cmdline#) in the Kickstart file, or you must use the [option]#console=# boot option as described in xref:advanced/Boot_Options.adoc#sect-boot-options-display[Console, Environment and Display Options]. Otherwise the system will halt and ask you to choose a mode.
|
||||
|
||||
====
|
||||
|
||||
|
|
@ -1927,7 +1927,7 @@ Allows the graphical installation to be viewed remotely via VNC. This method is
|
|||
[command]#vnc [--host=pass:attributes[{blank}]_hostname_pass:attributes[{blank}]] [--port=pass:attributes[{blank}]_port_pass:attributes[{blank}]] [--password=pass:attributes[{blank}]_password_pass:attributes[{blank}]]#
|
||||
----
|
||||
|
||||
For more information about VNC installations, including instructions on how to connect to the installation system, see xref:../advanced/VNC_Installations.adoc#chap-vnc-installations[Installing Using VNC].
|
||||
For more information about VNC installations, including instructions on how to connect to the installation system, see xref:advanced/VNC_Installations.adoc#chap-vnc-installations[Installing Using VNC].
|
||||
|
||||
[option]#--host=#:: Connect to a VNC viewer listening on the given hostname.
|
||||
|
||||
|
|
@ -1978,7 +1978,7 @@ If you enable [application]*Kdump* and do not specify the [option]#--reserve-mb=
|
|||
[[sect-kickstart-commands-firstboot]]
|
||||
=== firstboot (optional) - Enable or Disable Initial Setup
|
||||
|
||||
Determine whether the [application]*Initial Setup* application starts the first time the system is booted. If enabled, the [package]*initial-setup* package must be installed. If not specified, this option is disabled by default. For more information about [application]*Initial Setup*, see xref:../install/After_Installation.adoc#sect-initial-setup[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].
|
||||
|
||||
[subs="quotes, macros"]
|
||||
----
|
||||
|
|
|
|||
|
|
@ -11,7 +11,7 @@ LVM (Logical Volume Management) partitions provide a number of advantages over s
|
|||
|
||||
The boot loader cannot read LVM volumes. You must make a standard, non-LVM disk partition for your `/boot` partition.
|
||||
|
||||
By default, the installation process always creates the `/` and `swap` partitions within LVM volumes, with a separate `/boot` on a standard partition. See xref:../install/Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-recommended[Recommended Partitioning Scheme] for details.
|
||||
By default, the installation process always creates the `/` and `swap` partitions within LVM volumes, with a separate `/boot` on a standard partition. See xref:install/Installing_Using_Anaconda.adoc#sect-installation-gui-manual-partitioning-recommended[Recommended Partitioning Scheme] for details.
|
||||
|
||||
====
|
||||
|
||||
|
|
|
|||
|
|
@ -31,9 +31,9 @@ After you finish configuring all screens, click `Start using Fedora` to exit the
|
|||
|
||||
After you finish the installation and go through one of the initial setup utilities described above, your system is ready for use. However, other administrative tasks not covered by the installer or the initial setup utilities may still be necessary, depending on how you plan to use your system. The list below describes some of the more common tasks usually performed immediately after a new installation.
|
||||
|
||||
Recover a lost `root` password:: The `root` password, which is configured during the installation, is required for accessing the system as the `root` user. Without this password you will not be able to configure your system or install additional software. If you lost or forgot your `root` password, you can reset it by following the steps described in xref:Troubleshooting.adoc#sect-trouble-after-reset-root-password[Resetting the Root Password].
|
||||
Recover a lost `root` password:: The `root` password, which is configured during the installation, is required for accessing the system as the `root` user. Without this password you will not be able to configure your system or install additional software. If you lost or forgot your `root` password, you can reset it by following the steps described in xref:install/Troubleshooting.adoc#sect-trouble-after-reset-root-password[Resetting the Root Password].
|
||||
|
||||
Configure the network:: In most cases, network access is configured during the installation process, either in the [application]*Anaconda* installation program (see xref:Installing_Using_Anaconda.adoc#sect-installation-gui-network-configuration[Network & Hostname]) or in a Kickstart file (see xref:../appendixes/Kickstart_Syntax_Reference.adoc#sect-kickstart-commands-network[network (optional) - Configure Network Interfaces]). For information on configuring the network after the installation, see the [citetitle]_{PRODUCT} Networking Guide_, available at link:++https://docs.fedoraproject.org/++[].
|
||||
Configure the network:: In most cases, network access is configured during the installation process, either in the [application]*Anaconda* installation program (see xref:install/Installing_Using_Anaconda.adoc#sect-installation-gui-network-configuration[Network & Hostname]) or in a Kickstart file (see xref:appendixes/Kickstart_Syntax_Reference.adoc#sect-kickstart-commands-network[network (optional) - Configure Network Interfaces]). For information on configuring the network after the installation, see the [citetitle]_{PRODUCT} Networking Guide_, available at link:++https://docs.fedoraproject.org/++[].
|
||||
|
||||
Perform an initial system update:: If you installed {PRODUCT} from a full installation ISO image (such as the Workstation live image or full Server DVD), it is recommended to perform an initial system update, because your installation media likely contained older versions of software packages. During the initial update, all installed packages are updated to their latest available versions. Updates to packages provide security fixes, bug fixes and enhancements.
|
||||
+
|
||||
|
|
@ -47,8 +47,8 @@ Configure additional repositories:: New software is installed from _package rep
|
|||
+
|
||||
For information about configuring additional software repositories, see the [citetitle]_{PRODUCT} System Administrator's Guide_, available at link:++https://docs.fedoraproject.org/++[].
|
||||
|
||||
Install additional packages:: You can control which packages will be installed by selecting an environment in the `Software Selection` dialog in the graphical installation (see xref:Installing_Using_Anaconda.adoc#sect-installation-gui-software-selection[Software Selection]). This dialog does not provide a way to choose individual packages, only predefined sets. However, you can use the [application]*DNF* package manager to install additional packages after the installation. See the [citetitle]_{PRODUCT} System Administrator's Guide_, available at link:++https://docs.fedoraproject.org/++[], for more information.
|
||||
Install additional packages:: You can control which packages will be installed by selecting an environment in the `Software Selection` dialog in the graphical installation (see xref:install/Installing_Using_Anaconda.adoc#sect-installation-gui-software-selection[Software Selection]). This dialog does not provide a way to choose individual packages, only predefined sets. However, you can use the [application]*DNF* package manager to install additional packages after the installation. See the [citetitle]_{PRODUCT} System Administrator's Guide_, available at link:++https://docs.fedoraproject.org/++[], for more information.
|
||||
|
||||
Switch to a graphical login:: Depending on the options you chose during the installation process, it is possible that your system does not have a graphical interface, instead offering only a text-based prompt. If this is the case and you wish to enable a graphical desktop after the installation, you must install the [application]*X Window System* and your preferred desktop environment (either [application]*GNOME* or [application]*KDE*).
|
||||
+
|
||||
As with all other software, these packages can be installed using the [application]*DNF* package manager. For information about using [application]*DNF* to install new packages, see the [citetitle]_{PRODUCT} System Administrator's Guide_, available at link:++https://docs.fedoraproject.org/++[]. For information on how to enable graphical login by default, see xref:Troubleshooting.adoc#sect-trouble-after-graphical-login[Booting into a Graphical Environment].
|
||||
As with all other software, these packages can be installed using the [application]*DNF* package manager. For information about using [application]*DNF* to install new packages, see the [citetitle]_{PRODUCT} System Administrator's Guide_, available at link:++https://docs.fedoraproject.org/++[]. For information on how to enable graphical login by default, see xref:install/Troubleshooting.adoc#sect-trouble-after-graphical-login[Booting into a Graphical Environment].
|
||||
|
|
@ -10,7 +10,7 @@ This chapter will explain how to boot the installer from local media or a networ
|
|||
[[sect-preparing-boot]]
|
||||
== Preparing to Boot
|
||||
|
||||
After you have made a bootable USB flash drive or a CD or DVD using the steps described in 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.
|
||||
After you have made a bootable USB flash drive or a CD or DVD using the steps described in xref:install/Preparing_for_Installation.adoc#sect-preparing-boot-media[Preparing Boot Media], you are ready to boot the installation. Note that the steps described below are generic and the exact steps will vary somewhat depending on your system - particularly on your motherboard manufacturer.
|
||||
|
||||
[WARNING]
|
||||
====
|
||||
|
|
@ -83,4 +83,4 @@ When editing the default set of options, you can change the existing ones as wel
|
|||
|
||||
image::boot/boot-menu.png[The boot menu.]
|
||||
|
||||
All available [application]*Anaconda* boot options are described in xref:../advanced/Boot_Options.adoc#sect-boot-options-available[Available Boot Options].
|
||||
All available [application]*Anaconda* boot options are described in xref:advanced/Boot_Options.adoc#sect-boot-options-available[Available Boot Options].
|
||||
|
|
@ -9,9 +9,9 @@ This chapter provides step-by-step instructions for installing {PRODUCT} using t
|
|||
|
||||
If your system does not have the ability to use the graphical mode, you can:
|
||||
|
||||
* Use Kickstart to automate the installation as described in xref:../advanced/Kickstart_Installations.adoc#chap-kickstart-installations[Automating the Installation with Kickstart]
|
||||
* Use Kickstart to automate the installation as described in xref:advanced/Kickstart_Installations.adoc#chap-kickstart-installations[Automating the Installation with Kickstart]
|
||||
|
||||
* Perform the graphical installation remotely by connecting to the installation system from another computer with a graphical display using the _VNC_ (Virtual Network Computing) protocol - see xref:../advanced/VNC_Installations.adoc#chap-vnc-installations[Installing Using VNC]
|
||||
* Perform the graphical installation remotely by connecting to the installation system from another computer with a graphical display using the _VNC_ (Virtual Network Computing) protocol - see xref:advanced/VNC_Installations.adoc#chap-vnc-installations[Installing Using VNC]
|
||||
|
||||
[[sect-installation-new-users]]
|
||||
== Introduction to Anaconda
|
||||
|
|
@ -67,21 +67,21 @@ You can also use kbd:[Ctrl + b] kbd:[n] and kbd:[Ctrl + b] kbd:[p] to switch to
|
|||
|kbd:[Ctrl + b] kbd:[5]|Program log; displays messages from other system utilities, stored in `/tmp/program.log`.
|
||||
|===
|
||||
|
||||
In addition to displaying diagnostic information in [application]*tmux* windows, [application]*Anaconda* also generates several log files, which can be transferred from the installation system. These log files are described in 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].
|
||||
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:install/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:install/Troubleshooting.adoc#sect-troubleshooting-transferring-logs[Transferring Log Files from the Installation System].
|
||||
|
||||
[[sect-installation-screenshots]]
|
||||
=== Saving Screenshots
|
||||
|
||||
You can press kbd:[Shift + Print Screen] at any time during the graphical installation to capture the current screen. These screenshots are saved to `/tmp/anaconda-screenshots`.
|
||||
|
||||
Additionally, you can use the [command]#autostep --autoscreenshot# command in a Kickstart file to capture and save each step of the installation automatically. See xref:../appendixes/Kickstart_Syntax_Reference.adoc#sect-kickstart-commands-autostep[autostep (optional) - Go Through Every Screen] for details.
|
||||
Additionally, you can use the [command]#autostep --autoscreenshot# command in a Kickstart file to capture and save each step of the installation automatically. See xref:appendixes/Kickstart_Syntax_Reference.adoc#sect-kickstart-commands-autostep[autostep (optional) - Go Through Every Screen] for details.
|
||||
|
||||
[[sect-installation-text-mode]]
|
||||
== Installing in Text Mode
|
||||
|
||||
Text mode installation offers an interactive, non-graphical interface for installing {PRODUCT}. This may be useful on systems with no graphical capabilities; however, you should always consider the available alternatives before starting a text-based installation. Text mode is limited in the amount of choices you can make during the installation.
|
||||
|
||||
There are two alternatives to text mode which can both be used even if the installation system does not have a graphical display. You can either connect to the installation system using VNC and perform an interactive graphical installation remotely (see xref:../advanced/VNC_Installations.adoc#chap-vnc-installations[Installing Using VNC]), or you can create a Kickstart file to perform the installation automatically (see xref:../advanced/Kickstart_Installations.adoc#chap-kickstart-installations[Automating the Installation with Kickstart]).
|
||||
There are two alternatives to text mode which can both be used even if the installation system does not have a graphical display. You can either connect to the installation system using VNC and perform an interactive graphical installation remotely (see xref:advanced/VNC_Installations.adoc#chap-vnc-installations[Installing Using VNC]), or you can create a Kickstart file to perform the installation automatically (see xref:advanced/Kickstart_Installations.adoc#chap-kickstart-installations[Automating the Installation with Kickstart]).
|
||||
|
||||
.Text Mode Installation
|
||||
|
||||
|
|
@ -97,7 +97,7 @@ Limits of interactive text mode installation include:
|
|||
|
||||
* It is not possible to configure custom partitioning; you must use one of the automatic partitioning settings. You also cannot configure where the boot loader will be installed.
|
||||
|
||||
To start a text mode installation, boot the installation with the [option]#inst.text# boot option used either at the boot command line in the boot menu, or in your PXE server configuration. See xref:Booting_the_Installation.adoc#chap-booting-the-installation[Booting the Installation] for information about booting and using boot options.
|
||||
To start a text mode installation, boot the installation with the [option]#inst.text# boot option used either at the boot command line in the boot menu, or in your PXE server configuration. See xref:install/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
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@ If you already have Fedora installed and want to upgrade your installation to th
|
|||
|
||||
Automatic upgrade using [application]*dnf system upgrade*:: The preferred way to upgrade your system is an automatic upgrade using the [application]*dnf system upgrade* utility. For information on performing an automatic upgrade, see link:++https://fedoraproject.org/wiki/DNF_system_upgrade++[Fedora Wiki dnf system upgrade].
|
||||
|
||||
Manual Reinstallation:: You can upgrade to the latest version of Fedora manually instead of relying on [application]*dnf system upgrade*. This involves booting the installer as if you were performing a clean installation, letting it detect your existing Fedora system, and overwriting the root partition while preserving data on other partitions and volumes. The same process can also be used to reinstall the system, if you need to. For detailed information, see xref:../advanced/Upgrading_Your_Current_System.adoc#sect-upgrading-fedora-manual-reinstall[Manual System Upgrade or Reinstallation].
|
||||
Manual Reinstallation:: You can upgrade to the latest version of Fedora manually instead of relying on [application]*dnf system upgrade*. This involves booting the installer as if you were performing a clean installation, letting it detect your existing Fedora system, and overwriting the root partition while preserving data on other partitions and volumes. The same process can also be used to reinstall the system, if you need to. For detailed information, see xref:advanced/Upgrading_Your_Current_System.adoc#sect-upgrading-fedora-manual-reinstall[Manual System Upgrade or Reinstallation].
|
||||
|
||||
[WARNING]
|
||||
====
|
||||
|
|
@ -152,9 +152,9 @@ If you have downloaded and verified the installation images manually, you still
|
|||
[[sect-preparing-obtaining-images]]
|
||||
==== Downloading Boot and Installation Images
|
||||
|
||||
The Fedora Project offers different Editions tailored for some specific use cases. Choose the Fedora Edition best for you, or you can build your own by customizing after the installation, or by using a kickstart file as described in 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.
|
||||
The Fedora Project offers different Editions tailored for some specific use cases. Choose the Fedora Edition best for you, or you can build your own by customizing after the installation, or by using a kickstart file as described in xref:advanced/Kickstart_Installations.adoc#sect-kickstart-file-create[Creating a Kickstart File]. Kickstart installation requires the `netinstall` media type, or a direct installation booting method such as PXE; kickstarts are not supported with live images.
|
||||
|
||||
Read more about Fedora Workstation, Fedora Cloud, Fedora Server and the available media types in xref:../Downloading_Fedora.adoc#chap-downloading-fedora[Downloading Fedora].
|
||||
Read more about Fedora Workstation, Fedora Cloud, Fedora Server and the available media types in xref:Downloading_Fedora.adoc#chap-downloading-fedora[Downloading Fedora].
|
||||
|
||||
You can also choose a Fedora _Spin_ featuring favorite alternative desktops or tools for specialized tasks at link:++https://spins.fedoraproject.org++[].
|
||||
|
||||
|
|
|
|||
|
|
@ -54,7 +54,7 @@ If the installation fails, the messages from these files are consolidated into `
|
|||
[[sect-troubleshooting-transferring-logs]]
|
||||
=== Transferring Log Files from the Installation System
|
||||
|
||||
All of the files described in 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.
|
||||
All of the files described in xref:install/Troubleshooting.adoc#sect-troubleshooting-log-files[Log Files Generated During the Installation] reside in the installation program's RAM disk, which means they are not saved permamently and will be lost once the system is powered down. To store them permanently, copy those files to another system on the network using [command]#scp# on the system running the installation program, or copy them to a mounted storage device (such as an USB flash drive). Details on how to transfer the log files are below. Note that if you use an USB flash drive or other removable media, you should make sure to back up any data on it before starting the procedure.
|
||||
|
||||
[[sect-troubleshooting-transferring-logs-usb]]
|
||||
==== Transferring Log Files Onto a USB Drive
|
||||
|
|
@ -160,7 +160,7 @@ The log files from the installation are now permanently saved on the target syst
|
|||
|
||||
Systems with some video cards have trouble booting into the graphical installation program. If the installation program does not run using its default settings, it attempts to run in a lower resolution mode. If that still fails, the installation program attempts to run in text mode.
|
||||
|
||||
There are several possible solutions to display issues, most of which involve specifying custom boot options. For more information, see xref:../advanced/Boot_Options.adoc#sect-boot-options-installer[Configuring the Installation System at the Boot Menu].
|
||||
There are several possible solutions to display issues, most of which involve specifying custom boot options. For more information, see xref:advanced/Boot_Options.adoc#sect-boot-options-installer[Configuring the Installation System at the Boot Menu].
|
||||
|
||||
Use the basic graphics mode:: You can attempt to perform the installation using the basic graphics driver. To do this, edit the installation program's boot options and append [option]#inst.xdriver=vesa# at the end of the command line.
|
||||
|
||||
|
|
@ -175,13 +175,13 @@ If specifying a custom video driver solves your problem, you should report it as
|
|||
|
||||
====
|
||||
|
||||
Perform the installation using VNC:: If the above options fail, you can use a separate system to access the graphical installation over the network, using the _Virtual Network Computing_ (VNC) protocol. For details on installing using VNC, see xref:../advanced/VNC_Installations.adoc#chap-vnc-installations[Installing Using VNC].
|
||||
Perform the installation using VNC:: If the above options fail, you can use a separate system to access the graphical installation over the network, using the _Virtual Network Computing_ (VNC) protocol. For details on installing using VNC, see xref:advanced/VNC_Installations.adoc#chap-vnc-installations[Installing Using VNC].
|
||||
|
||||
=== Serial Console Not Detected
|
||||
|
||||
In some cases, attempting to install in text mode using a serial console will result in no output on the console. This happens on systems which have a graphics card, but no monitor connected. If [application]*Anaconda* detects a graphics card, it will attempt to use it for a display, even if no display is connected.
|
||||
|
||||
If you want to perform a text-based installation on a serial console, use the [option]#inst.text# and [option]#console=# boot options. See xref:../advanced/Boot_Options.adoc#chap-anaconda-boot-options[Boot Options] for more details.
|
||||
If you want to perform a text-based installation on a serial console, use the [option]#inst.text# and [option]#console=# boot options. See xref:advanced/Boot_Options.adoc#chap-anaconda-boot-options[Boot Options] for more details.
|
||||
|
||||
[[sect-troubleshooting-problems-during-installation]]
|
||||
== Trouble During the Installation
|
||||
|
|
@ -267,7 +267,7 @@ If you have performed an installation and cannot boot your system properly, you
|
|||
|
||||
Some BIOS types do not support booting from RAID cards. After you finish the installation and reboot the system for the first time, a text-based screen showing the boot loader prompt (for example, `grub>`) and a flashing cursor may be all that appears. If this is the case, you must repartition your system and move your `/boot` partition and the boot loader outside the RAID array. The `/boot` partition and the boot loader must be on the same drive.
|
||||
|
||||
Once these changes have been made, you should be able to finish your installation and boot the system properly. For more information about partitioning, see xref:Installing_Using_Anaconda.adoc#sect-installation-gui-storage-partitioning[Installation Destination].
|
||||
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:install/Installing_Using_Anaconda.adoc#sect-installation-gui-storage-partitioning[Installation Destination].
|
||||
|
||||
[[sect-trouble-after-graphical-boot]]
|
||||
=== Trouble With the Graphical Boot Sequence
|
||||
|
|
@ -383,7 +383,7 @@ For additional information about [command]#df# and an explanation of the options
|
|||
[[sect-trouble-after-missing-ram]]
|
||||
=== Is Your RAM Not Being Recognized?
|
||||
|
||||
In some cases the kernel does not recognize all of your memory (RAM), which causes the system to use less memory than is installed. You can find out how much RAM is being utilized using the [command]#free -m# command. If the displayed total amount of memory does not match your expectations, it is likely that at least one of your memory modules is faulty. On BIOS-based systems, you can use the [application]*Memtest86+* utility to test your system's memory - see xref:../advanced/Boot_Options.adoc#sect-boot-options-memtest[Loading the Memory (RAM) Testing Mode] for details.
|
||||
In some cases the kernel does not recognize all of your memory (RAM), which causes the system to use less memory than is installed. You can find out how much RAM is being utilized using the [command]#free -m# command. If the displayed total amount of memory does not match your expectations, it is likely that at least one of your memory modules is faulty. On BIOS-based systems, you can use the [application]*Memtest86+* utility to test your system's memory - see xref:advanced/Boot_Options.adoc#sect-boot-options-memtest[Loading the Memory (RAM) Testing Mode] for details.
|
||||
|
||||
[NOTE]
|
||||
====
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue