From f324292e63040842b9170c2f87239706b960a33b Mon Sep 17 00:00:00 2001 From: linux-modder Date: May 05 2016 11:52:07 +0000 Subject: [PATCH 1/5] Minor typo corrections info updates (Boot_Options) \n Version Bump (Book_Info) \n Generallookover (Booting_the_Installation) --- diff --git a/en-US/Book_Info.xml b/en-US/Book_Info.xml index be05904..1b5bd2b 100644 --- a/en-US/Book_Info.xml +++ b/en-US/Book_Info.xml @@ -20,7 +20,7 @@ Installation Guide Installing &PRODUCT; &PRODVER; on 32 and 64-bit AMD and Intel Fedora - 23 + 24 1 0 diff --git a/en-US/Boot_Options.xml b/en-US/Boot_Options.xml index 8b044ce..19275a4 100644 --- a/en-US/Boot_Options.xml +++ b/en-US/Boot_Options.xml @@ -74,7 +74,7 @@ - an ISO image of the full &PRODUCT; installation DVD, placed on a hard drive or a network location accessible from the installation system + an ISO image of the full &PRODUCT; installation DVD, placed on a hard drive or a network location accessible from the installation system, including USB Drives. @@ -107,7 +107,7 @@ - Specific CD/DVD drive + Specific CD/DVD drive/USB Drive @@ -172,7 +172,7 @@ - File system label, for example LABEL=Flash or LABEL=RHEL7 + File system label, for example LABEL=Flash or LABEL=FEDORA\x2024 @@ -211,7 +211,7 @@ - You should never attempt to perform a driver update during the installation unless a missing our faulty driver is preventing you from completing the installation. Updating drivers which are not essential during the installation should always be performed after the system is installed. + You should never attempt to perform a driver update during the installation unless a missing or faulty driver is preventing you from completing the installation. Updating drivers which are not essential during the installation should always be performed after the system is installed. @@ -335,7 +335,7 @@ - Sets the language to be used during the installation. Language codes are the same as the ones used in the lang Kickstart command as described in . On systems where the system-config-language package is installed, a list of valid values can also be find in /usr/share/system-config-language/locale-list. + Sets the language to be used during the installation. Language codes are the same as the ones used in the lang Kickstart command as described in . On systems where the system-config-language package is installed, a list of valid values can also be found 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. @@ -656,9 +656,9 @@ Sets up a Virtual LAN (VLAN) device on a specified interface with a given name. The syntax is . For example: - + - The above will set up a VLAN device named vlan5 on the em1 interface. The name can take the following forms: + The above will set up a VLAN device named vlan1 on the em1 interface. The name can take the following forms: VLAN Device Naming Conventions @@ -681,7 +681,7 @@ VLAN_PLUS_VID - vlan0005 + vlan.0001 @@ -689,7 +689,7 @@ VLAN_PLUS_VID_NO_PAD - vlan5 + vlan1 @@ -697,7 +697,7 @@ DEV_PLUS_VID - em1.0005. + em1.0001. @@ -705,7 +705,7 @@ DEV_PLUS_VID_NO_PAD - em1.5. + em1.1. @@ -761,7 +761,7 @@ - Force the installation program to install partition information into a GUID Partition Table (GPT) instead of a Master Boot Record (MBR). This option is meaningless on UEFI-based systems, unless they are in BIOS compatibility mode. + Force the installation program to install partition information into a GUID Partition Table (GPT) instead of a Master Boot Record (MBR). This option is meaningless on UEFI-based systems, unless they are in BIOS compatibility mode. Commonly (marked as UEFI+CSM or (marked as LEGACY)). 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. @@ -775,10 +775,10 @@ - This option controls the usage of zRAM swap during the installation. It creates a compressed block device inside the system RAM and uses it for swap space instead of the hard drive. This allows the installer to essentially increase the amount of memory available, which makes the installation faster on systems with low memory. + This option controls the usage of zRAM swap during the installation. It creates a compressed block device inside the system RAM and uses it for swap space instead of the hard drive. This allows the installer to essentially increase the amount of memory available, which makes the installation faster on systems with low memory. This will inherit to the installed system as well, however in disable state on systemc with > 2G RAM - By default, swap on zRAM is enabled on systems with 2 GB or less RAM, and disabled on systems with more than 2 GB of memory. You can use this option to change this behavior - on a system with more than 2 GB RAM, use to enable it, and on systems with 2 GB or less memory, use to disable this feature. + By default, swap on zRAM is enabled on systems with 2 GB or less RAM, and disabled on systems with more than 2 GB of memory. You can use this option to change this behavior - on a system with more than 2 GB RAM, use to enable it. @@ -802,7 +802,7 @@ - Turns the Kdump installer add-on on or off (the add-on is off by default). If you use , a new screen, which allows you to configure the Kdump kernel crash dumping mechanism, will appear in the main menu of the graphical or text interface (see ). Enabling this add-on is also necessary to use the Kickstart command. + Turns the Kdump installer add-on on or off (the add-on is off by default). If you use , a new screen, which allows you to configure the Kdump kernel crash dumping mechanism, will appear in the main menu of the graphical or text interface, default kdump store is 128Mb. (see ). Enabling this add-on is also necessary to use the Kickstart command. @@ -884,7 +884,7 @@ Password: - Once the installation starts, this option sends log messages to the syslog process on the specified host. The remote syslog process must be configured to accept incoming connections. + Once the installation starts, this option sends log messages to the syslog process on the specified host. The remote syslog process must be configured to accept incoming connections. @@ -1024,16 +1024,6 @@ Password: -
- - - When performing a Kickstart installation, booting from local media and having the Kickstart file on local media as well, the network will not be initialized. This means that any other Kickstart options requiring network access, such as pre-installation or post-installation scripts accessing a network location, will cause the installation to fail. This is a known issue; see BZ#1085310 for details. - - - To work around this issue, either use the boot option, or add the option to the network command in your Kickstart file. - - - @@ -1187,11 +1177,7 @@ Password: &PRODUCT; includes the Memtest86+ memory testing application. To start memory testing mode, choose Troubleshooting > Memory test at the boot menu. Testing will begin immediately. By default, Memtest86+ carries out ten tests in every pass; a different configuration can be specified by accessing the configuration screen using the c key. After the first pass completes, a message will appear at the bottom informing you of the current status, and another pass will start automatically. - - - Memtest86+ only works on systems with BIOS firmware. Support for UEFI systems is currently unavailable. - - +
Memory Check Using Memtest86+ diff --git a/en-US/Booting_the_Installation.xml b/en-US/Booting_the_Installation.xml index 0989bb0..f36be53 100644 --- a/en-US/Booting_the_Installation.xml +++ b/en-US/Booting_the_Installation.xml @@ -50,7 +50,7 @@ Some older systems may not support choosing a boot device at startup. In that case, enter the system's SETUP (BIOS), and change the default boot order so that your boot media (CD, DVD, USB or network) has higher priority than internal hard drives. - On Mac hardware, hold down the Option key to enter the boot media selection menu. + On Mac hardware, hold down the Option C keys to enter the boot media selection menu. On newer macs (Built after 2011) C is usually sufficient. @@ -87,13 +87,13 @@ Editing boot options in GRUB2 (on UEFI systems) will display the entire configuration for the selected entry. Actual boot options are configured on the line which starts with the linux (or linux16 or linuxefi) keyword. Do not modify any other lines in the configuration. - + On systems with BIOS firmware, only the actual boot options are displayed when you press Tab. - When editing the default set of options, you can change the existing ones as well as append additional ones. Once you finish, press Enter on BIOS or CtrlX on UEFI to boot the installer using your customized options. + When editing the default set of options, you can change the existing ones as well as append additional ones. Once you finish, press Enter on BIOS or F10 on UEFI to boot the installer using your customized options.
Editing boot options on a system with BIOS firmware From ec56f7c2dbacc8305f4a1fad9ec0cd7a49d025af Mon Sep 17 00:00:00 2001 From: linux-modder Date: May 05 2016 13:46:01 +0000 Subject: [PATCH 2/5] Basic Review --- diff --git a/en-US/Downloading_Fedora.xml b/en-US/Downloading_Fedora.xml index fc2118d..7341927 100644 --- a/en-US/Downloading_Fedora.xml +++ b/en-US/Downloading_Fedora.xml @@ -82,7 +82,7 @@ The netinstall image boots directly into the installation environment, and uses the online Fedora package repositories as the installation source. With a netinstall image, you can select a wide variety of packages to create a customized installation of Fedora. - The Fedora Server netinstall image is a universal one, and can be used to install any Fedora flavor or your own set of favorite packages. + The Fedora Server netinstall image is a universal one, and can be used to install any Fedora flavor or your own set of favorite packages. By Default, requires a Ethernet connection / NFS --Unlike the live optionn this option DOES NOT have wifi installed by default. @@ -115,7 +115,7 @@ Boot Images - The tiny images at are written to CDs, USB drives, or even floppy disks. The BFO image loads installation media from Fedora's servers and directly loads an installation environment, like the netinstall ISO. + The tiny images at are written to CDs, USB drives. The BFO image loads installation media from Fedora's servers and directly loads an installation environment, like the netinstall ISO. BFO images work like PXE deployments, without having to set up a server. From 9b9513ad59926d6266e86608be2e89337dd1c72b Mon Sep 17 00:00:00 2001 From: linux-modder Date: May 05 2016 16:04:08 +0000 Subject: [PATCH 3/5] Basic edits --- diff --git a/en-US/CustomSpoke.xml b/en-US/CustomSpoke.xml index 33e96e2..63c50e8 100644 --- a/en-US/CustomSpoke.xml +++ b/en-US/CustomSpoke.xml @@ -75,7 +75,7 @@ - The Rescan Disks dialog, showing a completed scan. Pressing OK now will take you back to the Installation Destination screen. + The Rescan Disks dialog, showing a completed scan. Pressing OK now will take you back to the Installation Destination screen. This process CAN take awkile depending on disk(s) layouts and size(s). @@ -84,7 +84,7 @@ After you finish configuring your system storage, press Done in the top left corner to save the configuration and return to the Installation Summary screen. At this point, the installer will check if your storage configuration is valid. If an error was detected, a message will be displayed at the bottom of the screen. Click the message to open a dialog window explaining what kind of error has been detected (for example, you put /boot on a Btrfs subvolume, or you did not create a BIOS Boot partition when your system requires one). - If such a message is displayed, go back and fix any issues found by the installer; otherwise you will not be able to proceed with the installation. You can also press Done again to return to the Installation Summary anyway, but a storage configuration error will prevent you from starting the actual installation process. + If such a message is displayed, go back and fix any issues found by the installer; otherwise you will not be able to proceed with the installation. You can also press Done again to return to the Installation Summary anyway, but a storage configuration error will prevent you from starting the actual installation process. The only exception is for the swap partition. If no error message is displayed and if you made any changes since the last time you have visited this screen, a summary dialog will appear, displaying a detailed list of the changes you made. Review the list and click Accept Changes to proceed with , or click Cancel & Return to Custom Partitioning if you want to make any more changes. diff --git a/en-US/CustomSpoke_AddLVM.xml b/en-US/CustomSpoke_AddLVM.xml index 188951a..545eff4 100644 --- a/en-US/CustomSpoke_AddLVM.xml +++ b/en-US/CustomSpoke_AddLVM.xml @@ -79,7 +79,7 @@ - The configuration dialog does not allow you to specify the size of the volume group's physical extents. The size will always be set to the default value of 4 MiB. If you want to create a volume group with different physical extents, create it manually by switching to an interactive shell and using the vgcreate command, or use a Kickstart file with the volgroup --pesize=size command. + The configuration dialog does not allow you to specify the size of the volume group's physical extents. The size will always be set to the default value of 4 MiB. If you want to create a volume group with different physical extents, create it manually by switching to an interactive shell(Ctrl+ Alt+F2 ) and using the vgcreate command, or use a Kickstart file with the volgroup --pesize=size command. diff --git a/en-US/CustomSpoke_AddPhysical.xml b/en-US/CustomSpoke_AddPhysical.xml index 5a00a5a..3e9fdab 100644 --- a/en-US/CustomSpoke_AddPhysical.xml +++ b/en-US/CustomSpoke_AddPhysical.xml @@ -54,12 +54,12 @@ - In the Device(s) section on the right side of the screen, you can see that the partition has been assigned to one or more hard drives. Click the Modify button to configure on which drive this partition will be created. + In the Device(s) section on the right side of the screen, you can see that the partition has been assigned to your hard drive(s). Click the Modify button to configure on which drive this partition will be created. - In the Configure Mount Point dialog, you can specify which physical devices (disks) this volume may reside on. You can select one or more disks which will be used to hold this volume by holding down Ctrl and clicking each disk in the list. If you select multiple disks here, Anaconda will determine where exactly the partition should be created based on how you configured the rest of the installation. If you want to make sure that this partition is placed on a specific hard drive, select only that drive and unselect all others. + In the Configure Mount Point dialog, you can specify which physical devices (disks) this volume may reside on. You can select any one of your disks which will be used to hold this volume.. If you select multiple disks here, Anaconda will determine where exactly the partition should be created based on how you configured the rest of the installation. If you want to make sure that this partition is placed on a specific hard drive, select only that drive and unselect all others. After you finish configuring the partition's location, click Save to return to the main Manual Partitioning screen. diff --git a/en-US/CustomSpoke_FileSystems.xml b/en-US/CustomSpoke_FileSystems.xml index 9b0846b..84b162c 100644 --- a/en-US/CustomSpoke_FileSystems.xml +++ b/en-US/CustomSpoke_FileSystems.xml @@ -28,7 +28,7 @@ - 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. + 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. (Still experimental-- not recommended for mission critical production systems) @@ -38,7 +38,7 @@ - BTRFS - Btrfs is a file system with several device-like features. It is capable of addressing and managing more files, larger files, and larger volumes than the ext2, ext3, and ext4 file systems. See for more information about creating Btrfs volumes. + BTRFS - Btrfs is a file system with several device-like features. It is capable of addressing and managing more files, larger files, and larger volumes than the ext2, ext3, and ext4 file systems. See for more information about creating Btrfs volumes. (Still experimental-- not recommended for mission critical production systems) @@ -60,17 +60,18 @@ + - swap - Swap partitions are used to support virtual memory. In other words, data is written to a swap partition when there is not enough RAM to store the data your system is processing. A swap partition should always be created; see for details such as the recommended size. + swap - Swap partitions are used to support virtual memory. In other words, data is written to a swap partition when there is not enough RAM to store the data your system is processing. A swap partition should always be created on systems with < 2Gb RAM; see for details such as the recommended size. - xfs - XFS is a highly scalable, high-performance file system that supports file systems up to 16 exabytes (approximately 16 million terabytes), files up to 8 exabytes (approximately 8 million terabytes), and directory structures containing tens of millions of entries. XFS also supports metadata journaling, which facilitates quicker crash recovery. The maximum supported size of a single XFS file system is 500 TB. Starting with &PRODUCT; 22, XFS is the default and recommended file system on &PRODUCT; Server. + xfs - XFS is a highly scalable, high-performance file system that supports file systems up to 16 exabytes (approximately 16 million terabytes), files up to 8 exabytes (approximately 8 million terabytes), and directory structures containing tens of millions of entries. XFS also supports metadata journaling, which facilitates quicker crash recovery. The maximum supported size of a single XFS file system is 500 TB. Starting with &PRODUCT; 24, XFS is the default and recommended file system on &PRODUCT; Server. - Note that the size of an XFS file system can not currently be reduced without destroying and recreating the file system. If you expect that you will need to adjust the sizes of your file systems often, using XFS is not recommended, as it makes administration substantially more time-consuming. + Note that the size of an XFS file system can not currently be reduced without destroying and recreating the file system. If you expect that you will need to adjust the sizes of your file systems often, using XFS is not recommended, as it makes administration substantially more time-consuming. However XFS filesystems can be 'grown' aka increased while mounted and active. diff --git a/en-US/CustomSpoke_PartitioningAdvice.xml b/en-US/CustomSpoke_PartitioningAdvice.xml index 2204e76..62069e9 100644 --- a/en-US/CustomSpoke_PartitioningAdvice.xml +++ b/en-US/CustomSpoke_PartitioningAdvice.xml @@ -21,7 +21,7 @@ - Some special restrictions apply to certain directories with regards on which partitioning layouts can they be placed. Notably, the /boot directory must always be on a physical partition (not on an LVM volume or a Btrfs subvolume), and /usr can not be on a Btrfs subvolume. + Some special restrictions apply to certain directories with regards to which partitioning layouts can they be placed. Notably, the /boot directory must always be on a physical partition (not on an LVM volume or a Btrfs subvolume), and /usr can not be on a Btrfs subvolume. @@ -31,7 +31,7 @@ - Each kernel installed on your system requires approximately 20 MB on the /boot partition. The default partition size of 500 MB for /boot should suffice for most common uses; increase the size of this partition if you plan to keep many kernels installed at the same time. + Each kernel installed on your system requires approximately 20 MB on the /boot partition. The default partition size of 500 MB for /boot should suffice for most common uses; increase the size of this partition if you plan to keep many kernels installed at the same time, or you use debug kernel as the debug symbols can get massive. @@ -41,7 +41,7 @@ - The contents of the /var directory usually change very often. This may cause problems with older solid state drives (SSDs), as they can handle a lower number of read/write cycles before becoming unusable. If your system root is on an SSD, consider creating a separate mount point for /var on a classic (platter) HDD. + The contents of the /var directory usually change very often. This may cause problems with older solid state drives (SSDs), as they can only handle a lower number of read/write cycles before becoming unusable. If your system root is on an SSD, consider creating a separate mount point for /var on a classic (platter) HDD. diff --git a/en-US/CustomSpoke_RecommendedScheme.xml b/en-US/CustomSpoke_RecommendedScheme.xml index ca2dcb7..4db217c 100644 --- a/en-US/CustomSpoke_RecommendedScheme.xml +++ b/en-US/CustomSpoke_RecommendedScheme.xml @@ -22,6 +22,10 @@ Also note that the /boot directory can not be placed on a LVM logical volume or a Btrfs subvolume. Use a standard partition. + + Also note that the /boot/efi directory can not be placed on a LVM logical volume or a Btrfs subvolume. Use a standard partition, but is needed for UEFI / EFI systems. 50MB to 100MB is suffiecient for most common uses. + + @@ -32,7 +36,7 @@ This is where the root directory is located. The root directory is the top level of the directory structure. By default, all files are written to this partition unless a different partition is mounted in the path being written to (for example, /boot or /home). If you follow the recommended scheme described in this section, this will be the partition where most software packages will be installed. - For a minimal installation, a 5 GB root partition will be sufficient. However, for most common installations which include extra packages and a graphical user interface, the root partition should be at least 10 GB; with 20 GB being sufficient for most common use cases. + For a minimal installation, a 5 GB root partition will be sufficient. However, for most common installations which include extra packages and a graphical user interface, the root partition should be at least 10 GB; with 20 GB being sufficient for most common use cases. If using the auto partioner, it will select 50Gb for / unless available disk space disallows it. @@ -45,7 +49,7 @@ /home - at least 10 GB - To store user data separately from system data, create a dedicated mount point for the /home directory. This partition should be sized based on the amount of data that will be stored locally, number of users, and so on. This will allow you to upgrade or reinstall &PRODUCT; without erasing user data files. During the installation, a separate /home partition will be created if there are 50 GB or more free space for your &PRODUCT; installation. + To store user data separately from system data, create a dedicated mount point for the /home directory. This partition should be sized based on the amount of data that will be stored locally, number of users, and so on. This will allow you to upgrade or reinstall &PRODUCT; without erasing user data files. During the installation, a separate /home partition will be created if there are 50 GB or more free space for your &PRODUCT; installation, and will by default will use the balance of space available after /, /boot, and any other selected partitions. When using &PRODUCT; as a workstation for normal use with a graphical environment, this mount point should have the most disk space assigned to it, as it will likely hold the most data (user settings, images, videos, etc). @@ -59,7 +63,7 @@ Swap partitions support virtual memory; data is written to them when there is not enough RAM to store the data your system is processing. This partition's size is a function of system memory workload, not total system memory, and therefore is not equal to the total system memory size. Therefore, it is important to analyze what applications a system will be running and the load those applications will serve in order to determine the system memory workload. Application providers and developers should be able to provide some guidance. - When the system runs out of swap space, the kernel terminates processes as the system RAM memory is exhausted. Configuring too much swap space results in storage devices being allocated but idle and is a poor use of resources. Too much swap space can also hide memory leaks. The maximum size for a swap partition and other additional information can be found in the mkswap(8) man page. + When the system runs out of swap space, the kernel terminates processes as the system RAM memory is exhausted. Configuring too much swap space results in storage devices being allocated but idle and is a poor use of resources. Too much swap space can also hide memory leaks. The maximum size for a swap partition and other additional information can be found in the mkswap(8) man page. While less effective zRAM may be used for a more 'dynamic' use of available disk space (in luie of, or addition to a swap space. The table below provides the recommended size of a swap partition depending on the amount of RAM in your system and whether you want sufficient memory for your system to hibernate. If you let the installation program partition your system automatically, the swap partition size will be established using these guidelines. Automatic partitioning setup assumes hibernation is not in use, and the maximum size of the swap partition is limited to 10% of the total size of the hard drive. If you want to set up enough swap space to allow for hibernation, or if you want to set the swap partition size to more than 10% of the system's storage space, you must edit the partitioning layout manually. From 5e6416d3751ac8f29600d87ff475796fdfd38586 Mon Sep 17 00:00:00 2001 From: linux-modder Date: May 06 2016 21:53:45 +0000 Subject: [PATCH 4/5] Edits --- diff --git a/en-US/Disk_Partitions.xml b/en-US/Disk_Partitions.xml index 598833c..4ca6fe0 100644 --- a/en-US/Disk_Partitions.xml +++ b/en-US/Disk_Partitions.xml @@ -66,7 +66,7 @@ - A small percentage of the driver's available space is used to store file system-related data and can be considered as overhead. + A small percentage of the drive's available space is used to store file system-related data and can be considered as overhead. @@ -81,7 +81,7 @@ - Note that there is no single, universal file system. As , shows, a disk drive may have one of many different file systems written on it. Different file systems tend to be incompatible; that is, an operating system that supports one file system (or a handful of related file system types) may not support another. However, &PRODUCT; supports a wide variety of file systems (including many commonly used by other operating systems such as Microsoft Windows), making data interchange between different file systems easy. + Note that there is no single, universal file system. As , shows, a disk drive may have one of many different file systems written on it. Different file systems tend to be incompatible; that is, an operating system that supports one file system (or a handful of related file system types) may not support another. However, &PRODUCT; supports a wide variety of file systems (including many commonly used by other operating systems such as Microsoft Windowsntfs and Mac OSX hfs/hfs+ ), making data interchange between different file systems easy.
Disk Drive with a Different File System @@ -131,7 +131,7 @@ - Logical separation of the operating system data from the user data + Logical separation of the operating system data from the user data (Makes backup / restore easier) @@ -141,7 +141,7 @@ - Ability to run multiple operating systems on one machine + Ability to run multiple operating systems on one machine (Dual / Multi Booting) @@ -586,7 +586,7 @@ - There must be a BIOS boot partition for the boot loader to be installed successfully onto a disk that contains a GPT (GUID Partition Table). This includes disks initialized by Anaconda. If the disk already contains a BIOS boot partition, it can be reused. + There must be a BIOS boot partition for the boot loader to be installed successfully onto a disk that contains a GPT (GUID Partition Table). This includes disks initialized by Anaconda. If the disk already contains a BIOS boot partition, it can be reused. For EFI systems BIOS Boot is replaced by /boot/efi. @@ -658,7 +658,7 @@ In this case, maybe you have one or more partitions that you do not use any longer. , illustrates such a situation. -
+
q Disk Drive with an Unused Partition diff --git a/en-US/Installation_Guide.ent b/en-US/Installation_Guide.ent index d845691..1a893cf 100644 --- a/en-US/Installation_Guide.ent +++ b/en-US/Installation_Guide.ent @@ -1,9 +1,9 @@ - - - + + + - + https://bugzilla.redhat.com" > '> diff --git a/en-US/Installing_Using_Anaconda.xml b/en-US/Installing_Using_Anaconda.xml index 9bd0aef..7276959 100644 --- a/en-US/Installing_Using_Anaconda.xml +++ b/en-US/Installing_Using_Anaconda.xml @@ -88,7 +88,7 @@ - Ctrlb 1 + CtrlAlt 1 Main installation program window. Contains text-based prompts (during text mode installation or if you use VNC direct mode), and also some debugging information. @@ -96,7 +96,7 @@ - Ctrlb 2 + CtrlAlt 2 Interactive shell prompt with root privileges. @@ -104,7 +104,7 @@ - Ctrlb 3 + CtrlAlt 3 Installation log; displays messages stored in /tmp/anaconda.log. @@ -112,7 +112,7 @@ - Ctrlb 4 + CtrlAlt 4 Storage log; displays messages related storage devices from kernel and system services, stored in /tmp/storage.log. @@ -120,7 +120,7 @@ - Ctrlb 5 + CtrlAlt 5 Program log; displays messages from other system utilities, stored in /tmp/program.log. @@ -176,7 +176,7 @@ - The installer will always use the English language and the US English keyboard layout. You can configure your language and keyboard settings, but these settings will only apply to the installed system, not to the installation. + The installer will always use the English language and the US English keyboard layout. You can configure your language and keyboard settings, but these settings will only apply to the installed system, not to the installation system (aka Live Media) diff --git a/en-US/KdumpSpoke.xml b/en-US/KdumpSpoke.xml index 14ca8fb..3cd7778 100644 --- a/en-US/KdumpSpoke.xml +++ b/en-US/KdumpSpoke.xml @@ -21,7 +21,7 @@ - The Kdump configuration screen, showing 128 MB reserved + The Kdump configuration screen, showing 128 MB reserved. (Default reservation) @@ -30,13 +30,13 @@ Kdump is a kernel crash dumping mechanism which, in the event of a system crash, captures the contents of the system memory at the moment of failure. This captured memory can then be analyzed to find the cause of the crash. If Kdump is enabled, it must have a small portion of the system's memory (RAM) reserved to itself. This reserved memory will not be accessible to the main kernel. - To enable Kdump on the installed system, check Enabled. Then, select either Automatic or Manual memory reservation settings, and if you selected Manual, enter the amount of memory to be reserved in megabytes into the Memory to be reserved field. + To enable Kdump on the installed system, check Enabled. Then enter the amount of memory to be reserved in megabytes into the Memory to be reserved field. - The amount of memory which you should reserve is determined based on your system's architecture (AMD64 and Intel 64 will have different requirements than IBM Power, for example) as well as the total amount of system memory. In most cases, automatic reservation will be satisfactory. If you insist on manual settings, see the Red Hat Enterprise Linux 7 Kernel Crash Dump Guide for guidelines. This document also contains more in-depth information about how Kdump works, how to configure additional settings, and how to analyze a saved crash dump. + The amount of memory which you should reserve is determined based on your system's architecture (AMD64 and Intel 64 will have different requirements than IBM Power, for example) as well as the total amount of system memory. In most cases, the default reservation will be satisfactory. If you insist on manual settings, see the Red Hat Enterprise Linux 7 Kernel Crash Dump Guide for guidelines. This document also contains more in-depth information about how Kdump works, how to configure additional settings, and how to analyze a saved crash dump. - The Usable System Memory readout below the reservation input field shows how much memory will be accessible to your main system once your selected amount of RAM is reserved. + The Usable System Memory readout below the reservation input field shows how much memory will be accessible to your main system once your selected amount of RAM is reserved. On low RAM systems this is something to watch out for. Too much kdump reservation could leave the system crippling slow or unusable. diff --git a/en-US/KeyboardSpoke.xml b/en-US/KeyboardSpoke.xml index 97c0ad3..2117f83 100644 --- a/en-US/KeyboardSpoke.xml +++ b/en-US/KeyboardSpoke.xml @@ -51,8 +51,9 @@ - The up and down buttons can be used to move the highlighted layout up or down in the list. - + The up and down buttons can be used to move the highlighted layout up or down in the list. Topmost selection will be defaul +t on the installed system . + diff --git a/en-US/Kickstart_Installations.xml b/en-US/Kickstart_Installations.xml index 63aea45..0bef830 100644 --- a/en-US/Kickstart_Installations.xml +++ b/en-US/Kickstart_Installations.xml @@ -6,7 +6,7 @@ Automating the Installation with Kickstart - Kickstart installations offer a means to automate the installation process, either partially or fully. Kickstart files contain answers to all questions normally asked by the installation program, such as what time zone do you want the system to use, how should the drives be partitioned or which packages should be installed. Providing a prepared Kickstart file when the installation begins therefore allows the you to perform the installation automatically, without need for any intervention from the user. This is especially useful when deploying &PRODUCT; on a large number of systems at once. + Kickstart installations offer a means to automate the installation process, either partially or fully. Kickstart files contain answers to all questions normally asked by the installation program, such as what time zone do you want the system to use, how should the drives be partitioned or which packages should be installed. Providing a prepared Kickstart file when the installation begins therefore allows the user to perform the installation automatically, without need for any intervention from the user. This is especially useful when deploying &PRODUCT; on a large number of systems at once. All Kickstart scripts and the log files of their execution are stored in the /tmp directory to assist with debugging installation issues. @@ -72,7 +72,7 @@ The command section which contains actual Kickstart commands and options as listed in . Note that some commands, such as install, are mandatory, but most commands are optional. - + The %packages section which contains a list of packages and package groups to be installed. See for details. @@ -107,7 +107,7 @@ After installing the package, you can validate a Kickstart file using the following command: - $ ksvalidator /path/to/kickstart.ks + $ python3-krsvalidator /path/to/kickstart.ks Replace /path/to/kickstart.ks with the path to the Kickstart file you want to verify. From 83adc14e70c9d6d8b6677a1f8e868d6a08d1a6f1 Mon Sep 17 00:00:00 2001 From: linux-modder Date: May 07 2016 19:25:38 +0000 Subject: [PATCH 5/5] Edits --- diff --git a/en-US/Kickstart_Syntax_Reference.xml b/en-US/Kickstart_Syntax_Reference.xml index ea267ef..9f06e72 100644 --- a/en-US/Kickstart_Syntax_Reference.xml +++ b/en-US/Kickstart_Syntax_Reference.xml @@ -18,14 +18,15 @@ part / --fstype=xfs --onpart=/dev/disk/by-path/pci-0000:00:05.0-scsi-0:0:0:0-part1 -part / --fstype=xfs --onpart=/dev/disk/by-id/ata-ST3160815AS_6RA0C882-part1 +part / --fstype=xfs --onpart=/dev/disk/by-id/ata-ST3160815AS_6RA0C882-part1i +part / --fstype=xfs --onpart=/dev/disk/by-uuid/ba555f30-1708-4015-9477-64d65a59f3e9-part1 This provides a consistent way to refer to disks that is more meaningful than just sda. This is especially useful in large storage environments. - While the general principles of Kickstart installations tend to stay the same, the commands and options can change between major releases. You can use the ksverdiff command to display the differences between two versions of the Kickstart syntax. This is useful when updating an existing Kickstart file to be used with a new release. To display a list of changes in syntax between Fedora &PREVVER; and &PRODVER;, use the following command: + While the general principles of Kickstart installations tend to stay the same, the commands and options can change between major releases. You can use the ksverdiff command to display the differences between two versions of the Kickstart syntax.(Requires python3-ksvalidator) This is useful when updating an existing Kickstart file to be used with a new release. To display a list of changes in syntax between Fedora &PREVVER; and &PRODVER;, use the following command: $ ksverdiff -f F&PREVVER; -t F&PRODVER; @@ -39,73 +40,8 @@ In the following sections, if an option is followed by an equals mark (=), a value must be specified after it. In the example commands, options in square brackets ([ ]) are optional arguments for the command. -
- Installation Methods and Sources - - The following commands control the way Fedora will be installed. - - -
- device (optional) - Install Extra Device Drivers - - On most PCI systems, the installation program will automatically detect Ethernet and SCSI cards. However, on older systems and some PCI systems, Kickstart requires a hint to find the proper devices. The device command, which tells the installation program to install extra modules, uses the following format: - - device moduleName [--opts=] - - Replace moduleName with the name of the kernel module which should be installed. - - - - - - - Options to pass to the installed kernel module. For example: - - device i2c_piix4 --opts="aic152x=0x340 io=11" - - - -
- -
- driverdisk (optional) - Use a Driver Disk - - Driver disks can be used during Kickstart installations to provide additional drivers not included by default. You must copy the driver disks's contents to the root directory of a partition on the system's hard drive. Then, you must use the driverdisk command to specify that the installation program should look for a driver disk and its location. - - driverdisk partition | --source= | --biospart= - - - partition - - - Search for the driver disk image on a local partition. Replace partition with the name of the partition containing the driver disk. Note that the partition must be specified as a full path. For example: - - driverdisk /dev/sdb1 - - - - - - - Search for the driver disk in a network location instead of a local partition. For example: - - driverdisk --source=ftp://path/to/dd.img - driverdisk --source=http://path/to/dd.img - driverdisk --source=nfs:hostname:/path/to/dd.img - - - - - - - BIOS partition containing the driver disk (for example, 82p2). - - - - -
- -
+ +
install (required) - Configure Installation Method The default installation mode. You must specify the type of installation from cdrom, harddrive, nfs, liveimg, or url. The install command and the installation method command must be on separate lines. For example: @@ -464,7 +400,7 @@
autopart (optional) - Automatic Partitioning - Automatically creates partitions: a root (/) partition (1 GB or larger), a swap partition, and an appropriate /boot partition for the architecture. On large enough drives (50 GB and larger), this also creates a /home partition. + Automatically creates partitions: a root (/) partition (10 GB -15GB), a swap partition,(on systems with less than 8GB RAM) and an appropriate /boot and / or /boot/efipartition for the architecture, a /home partition is created filling the remaining free space (unless 'I want to leave free space' option is 'checked' On large drives this /home is generally 50 GB or more. @@ -535,6 +471,12 @@ Provides a default system-wide passphrase for all encrypted devices. + + + The ommision of --passphrase will prompt the user for a passphrase. This will not work if inst.commandline or inst.text are used at grub menu. + + + @@ -551,13 +493,19 @@ Adds a randomly-generated passphrase to each encrypted volume. Store these passphrases in separate files in /root, encrypted using the X.509 certificate specified with . This option is only meaningful if is specified. + important> + + The ommision of --backuppassphrase will prompt the user for a passphrase. This will not work if inst.commandline or inst.text are used at grub menu. + + +rsvalidator /pat - Specifies which type of encryption will be used if the Anaconda default aes-xts-plain64 is not satisfactory. You must use this option together with the option; by itself it has no effect. Available types of encryption are listed in the Fedora Security Guide, available at . Using either aes-xts-plain64 or aes-cbc-essiv:sha256 is strongly recommended. + Specifies which type of encryption will be used if the Anaconda default aes-xts-plain64 is not satisfactory. You must use this option together with the option; by itself it has no effect. Available types of encryption are listed in the Fedora Security Guide, available at . Using aes-xts-plain64 is strongly recommended. @@ -593,19 +541,6 @@ - - - - Specifies which drive the boot loader should be written to, and therefore which drive the computer will boot from. If you use a multipath device as the boot drive, specify only one member of the device. - - - - The option is currently being ignored in &PRODUCT; installations on IBM System z systems using the zipl boot loader. When zipl is installed, it determines the boot drive on its own. - - - - - @@ -695,41 +630,6 @@ - - - - - Sets the default boot image in the boot loader configuration. - - - - - - - - Use the extlinux boot loader instead of GRUB2. This option only works on systems supported by extlinux. - - - - - - - - Do not attempt to install a boot loader. This option overrides all other boot loader configuration; all other boot loader options will be ignored and no boot loader packages will be installed. - - - - - - - - Install the boot loader configuration and support files, but do not modify the MBR. - - - - -
-
btrfs (optional) - Create Btrfs Volume or Subvolume @@ -1248,18 +1148,8 @@ - - - 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 . - - - - This option can only be used for partitions which result in a file system such as the /boot partition and swap space. It can not be used to create partitionsm, LVM physical or logical volumes or RAID members. - - - + - @@ -1269,9 +1159,8 @@ - - Specifies that this logical volume should be encrypted, using the passphrase provided in the option. If you do not specify a passphrase, the installation program will use the default, system-wide passphrase set with the autopart --passphrase command, or stop the installation and prompt you to provide a passphrase if no default is set. +This option requires a value for --passphrase, whether it is in the kickstart file or asked of the user during install. @@ -1287,12 +1176,12 @@ - Specifies which type of encryption will be used if the Anaconda default aes-xts-plain64 is not satisfactory. You must use this option together with the option; by itself it has no effect. Available types of encryption are listed in the Fedora Security Guide, available at . Using either aes-xts-plain64 or aes-cbc-essiv:sha256 is strongly recommended. + Specifies which type of encryption will be used if the Anaconda default aes-xts-plain64 is not satisfactory. You must use this option together with the option; by itself it has no effect. Available types of encryption are listed in the Fedora Security Guide, available at . Using aes-xts-plain64 is strongly recommended. - +### Store data encryption keys of all encrypted volumes as files in /root, encrypted using the X.509 certificate from the URL specified with URL_of_X.509_certificate. The keys are stored as a separate file for each encrypted volume. This option is only meaningful if is specified. @@ -2648,7 +2537,7 @@ auth [--enablenis | --nisdomain= | --nisserver= | --enableshadow | --enableldap | --enableldapauth | --ldapserver= | --ldapbasedn= | --enableldaptls | --disableldaptls | --enablekrb5 | --krb5realm= | --krb5kdc= | --krb5adminserver= | --enablehesiod | --hesiodlhs= | --hesiodrhs= | --enablesmbauth | --smbservers= | --smbworkgroup= | --enablecache | --passalgo=] - + @@ -2855,7 +2744,7 @@
pwpolicy (optional) - Change the Default Password Policy - This command can be used to set custom requirements (policy) such as length and strength for passwords set during the installation - the root password, user passwords and LUKS (disk encryption) password. + This command can be used to set custom requirements (policy) such as length and strength for passwords set during the installation - the root password, user passwords and LUKS (disk encryption) password. For LUKS Passwords these cahnges are ONLY for future changes / inputs, the previously set one (previous install or earlier in Kickstart file) will be unaffected by this option unless --changesok is used. pwpolicy name [--minlen=length] [--minquality=quality] [--strict|nostrict] [--emptyok|noempty] [--changesok|nochanges] @@ -3085,7 +2974,7 @@
sshkey (optional) - Add an Authorized SSH Key - Use this command to add a specified SSH key to an user's authorized_keys file. The specified user must either be root, or it must be created in the Kickstart file - either automatically by an installed package, or using . + Use this command to add a specified SSH key to any user's authorized_keys file. The specified user must either be root, or it must be created in the Kickstart file - either automatically by an installed package, or using . sshkey --username=user "ssh_key" @@ -3101,7 +2990,7 @@ -
+
t
user (optional) - Create User Account @@ -3224,10 +3113,7 @@ - Take a screenshot at every step during installation. These screenshots are stored in /tmp/anaconda-screenshots during the installation, and after the installation finishes you can find them in /root/anaconda-screenshots. - - - Each screen is only captured right before the installer switches to the next one. This is important, because if you do not use all required Kickstart options and the installation therefore does not begin automatically, you can go to the screens which were not automatically configured, perform any configuration you want. Then, when you press Done to continue, the screen will be captured including the configuration you just provided. + Take a screenshot at every step during installation. These screenshots are stored in /tmp/anaconda-screenshots during the installation, and after the installation finishes you can find them in /root/anaconda-screenshots.Each screen is only captured right before the installer switches to the next one. @@ -3237,13 +3123,8 @@
cmdline (optional) - Perform Installation in Command Line Mode - Perform the installation in a completely non-interactive command line mode. Any prompts for interaction halts the install. This mode is useful on IBM System z systems with the x3270 terminal. + Perform the installation in a completely non-interactive command line mode. Any prompts for interaction halts the install. This mode is useful on IBM System z systems with the x3270 terminal and large scale deployments with ansible-ized post install host master configuration. - - - For a fully automatic installation, you must either specify one of the available modes (graphical, text, or cmdline) in the Kickstart file, or you must use the boot option as described in . Otherwise the system will halt and ask you to choose a mode. - -
@@ -3445,9 +3326,6 @@ Kdump is a kernel crash dumping mechanism that allows you to save the contents of the system's memory for later analysis. It relies on kexec, which can be used to start a Linux kernel from the context of another kernel without rebooting the system and preserve the contents of the first kernel memory that would otherwise be lost. - In case of a system crash, kexec starts a second kernel (a capture kernel). This capture kernel resides in a reserved part of the system memory that is inaccessible to the main kernel. Kdump then captures the contents of the crashed kernel's memory (a crash dump) and saves it to a specified location. This location can not be configured using Kickstart; it must be specified after the installation by editing the /etc/kdump.conf configuration file. - - Available options are: @@ -3485,16 +3363,7 @@ - - - - - Enable firmware-assisted dumping on systems which allow it (notably IBM Power Systems servers). - - - - -
+
firstboot (optional) - Enable or Disable Initial Setup @@ -3535,39 +3404,20 @@ Halt the system after the installation has successfully completed. This is similar to a manual installation, where after the installation finishes, the installer displays a message and waits for the user to press a key before rebooting. During a Kickstart installation, if no completion method is specified, this option is used as the default. - - For other completion methods, see the poweroff, reboot, and shutdown commands. - -
+
poweroff (optional) - Power Off After Installation Shut down and power off the system after the installation has successfully completed. - - - The poweroff command is highly dependent on the system hardware in use. Specifically, certain hardware components such as the BIOS, APM (advanced power management), and ACPI (advanced configuration and power interface) must be able to interact with the system kernel. Consult your hardware documentation for more information on you system's APM/ACPI abilities. - - - - For other completion methods, see the halt, reboot, and shutdown Kickstart commands. - -
+
reboot (optional) - Reboot After Installation - Reboot after the installation is successfully completed. If you are installing &PRODUCT; on IBM System z in command line mode (using ), this command is necessary for a fully automated installation. + Reboot after the installation is successfully completed. - - For other completion methods, see the halt, poweroff, and shutdown Kickstart options. - - - - Use of the reboot command may result in an endless installation loop, depending on the installation media and method. - - @@ -3577,15 +3427,7 @@ - - - - - Use this option to reboot into the new system using the kexec kernel switching mechanism instead of a full reboot, bypassing the BIOS/Firmware and boot loader. - - - - +
@@ -3593,35 +3435,12 @@ Shut down the system after the installation has successfully completed. - - For other completion methods, see the halt, poweroff, and reboot Kickstart options. - -
- -
- -
- %addon (optional) - Include an Anaconda Add-on - - You can expand the basic Anaconda and Kickstart functionality by using custom add-ons specified using the %addon section. - - - To use an add-on in your Kickstart file, add the %addon addon_name options command. The section must be closed with an %end statement. For example, to use the Kdump add-on, which is included by default on some installations, use the following block: - - %addon com_redhat_kdump --enable --reserve-mb=128%end - - - The %addon section does not have any options of its own; all options depend on the add-on being used. - - - For more information about Anaconda add-ons, see the Fedora Anaconda Addon Development Guide. -
%anaconda (optional) - Additional Anaconda Configuration - This section, introduced in &PRODUCT; 22, is used to specify additional configuration options for the installer. Commands inside this section only control the behavior during installation, not on the installed system. The only command currently available inside this section is . The %anaconda section must end with %end. + This section, originally introduced in &PRODUCT; 22, is used to specify additional configuration options for the installer. Commands inside this section only control the behavior during installation, not on the installed system. The only command currently available inside this section is . The %anaconda section must end with %end. In interactive installations (using the graphical or text interface), the /usr/share/anaconda/interactive-defaults.ks file contains the default %anaconda section. To change the defaults, you must create a product.img file with a Kickstart file replacing the default one, and pass this file to Anaconda using a boot option. @@ -3700,9 +3519,9 @@ %packages -@X Window System -@Desktop -@Sound and Video +@^X Window System +@^Desktop +@^Sound and Video %end @@ -3740,7 +3559,7 @@ docbook* %packages --@Graphical Internet +-@^Graphical Internet -autofs -ipa*fonts %end @@ -3750,7 +3569,7 @@ docbook* - Installing all available packages using only * in a Kickstart file is not supported, even if you exclude the @Conflicts (variant) group. + Installing all available packages using only * in a Kickstart file is not supported, even if you exclude the @^Conflicts (variant) group. diff --git a/en-US/LangSupportSpoke.xml b/en-US/LangSupportSpoke.xml index 8b07307..e911cca 100644 --- a/en-US/LangSupportSpoke.xml +++ b/en-US/LangSupportSpoke.xml @@ -6,16 +6,7 @@
Language Support - The Language Support screen allows you to configure language settings for your system. The default language is determined by your selection in and support for this language can not be removed. You can only add additional languages, which will be available on the installed system - not during the installation. - - - If you want to change the default language, or the language used during the installation, you must reboot your system, start the installer again, and select a different language in . - - - - Adding support for another language does not automatically configure the corresponding keyboard layout. Layouts are a separate setting configured in . - - + The Language Support screen allows you to configure language settings for your system. The default language is determined by your selection in and support for this language can not be removed. You can only add additional languages, which will be available on the installed system and during the installation. This requires using the language switcher after adding the additional language(s).
Language Support @@ -30,7 +21,7 @@
- The left panel contains a list of available language groups such as English or Bulgarian. If at least one language from a group is selected, a check mark will be displayed next to the group, and the list entry will be highlighted. This allows you to easily see which languages you have configured support for. + The left panel contains a list of available language groups such as English or Bulgarian. If at least one language from a group is selected, a check mark will be displayed next to the group, and the list entry will be highlighted. This allows you to easily see which languages you have configured support for. Move the desired default language to the top (even if not highlighted) the topmost language is made the default on the installed system. To add support for one or more additional languages, click a group in the left panel, and then select one or more regional variations in the right panel using check boxes next to list entries. Repeat this process for all languages you want to install support for. diff --git a/en-US/Network_based_Installations.xml b/en-US/Network_based_Installations.xml index c388918..a82c69a 100644 --- a/en-US/Network_based_Installations.xml +++ b/en-US/Network_based_Installations.xml @@ -9,19 +9,7 @@ This appendix is intended for users with previous Linux experience. If you are a new user, you may want to install using minimal boot media or the distribution DVD instead. - - -
+
PXE Installation Overview Preboot Execution Environment, or PXE, is a techonology that allows computers to boot directly from resources provided over the network. Installing Fedora over the network means you don't have to create media, and you can install to multiple computers or virtual machine simultaneously. The process involves a number of components and features working together to provide the resources required. @@ -62,7 +50,11 @@ 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 boot option; see 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 + Examples: + inst.repo=http://mirrors.fedoraproject.org/mirrorlist?repo=fedora-$arch=$basearch + inst.repo=nfs://192.168.1.100/fedora/linux//23/Live/x86_64/os + inst.repo=ftp://mirror.cc.vt.edu/fedora/linux/releases/24/x86_64/Server/os +
DHCP Server Configuration @@ -194,7 +186,7 @@ next-server 192.168.1.2; mkdir -p /var/lib/tftpboot/uefi -cp /tmp/fedora/boot/efi/EFI/fedora/{shim.efi,grubx64.efi} /var/lib/tftpboot/uefi/ +cp /tmp/fedora/boot/efi/EFI/fedora/{shim,efi,grubx64.efi} /var/lib/tftpboot/uefi/ @@ -304,7 +296,7 @@ append f&PRODVER;/initrd=initrd.img root=live:http://download.fedoraproject.org/ For more complex environments, &PRODUCT; offers the cobbler installation server. Tasks like managing kickstart configurtations, coordinating repositories, maintaining dns records, dhcp servers, and even puppet manifests are effectively automated by cobbler. - While levaraging all of the features provided by cobbler can be relatively simple, the full functionality of this powerful tool is too broad to be documented in this guide. The cobbler community provides excellent documentation at to accompany the packages in the Fedora repository. + While leveraging all of the features provided by cobbler can be relatively simple, the full functionality of this powerful tool is too broad to be documented in this guide. The cobbler community provides excellent documentation at to accompany the packages in the Fedora repository.