[install-guide] Hey, we don't need to recommend any third party tools to verify checksums on Windows systems!
by pbokoc
commit e1ac8ffe7ab979c5fb41e08a71358c59358efe48
Author: Pete Travis <immanetize(a)fedoraproject.org>
Date: Sun Nov 16 20:12:57 2014 -0700
Hey, we don't need to recommend any third party tools to verify checksums on Windows systems!
en-US/Preparing_for_Installation.xml | 70 +++++++++++++++++++++++++++++++++-
1 files changed, 69 insertions(+), 1 deletions(-)
---
diff --git a/en-US/Preparing_for_Installation.xml b/en-US/Preparing_for_Installation.xml
index 37ce705..8ad04de 100644
--- a/en-US/Preparing_for_Installation.xml
+++ b/en-US/Preparing_for_Installation.xml
@@ -65,8 +65,76 @@
Because transmission errors or other problems may corrupt the Fedora image you have downloaded, it is imporant to verify the file's integrity. After the images are created, an operation is performed on the file that produces a value called a <literal>checksum</literal> using a complex mathematical algorithm. The operation is sufficiently complex that <emphasis>any change</emphasis> to the original file will produce a different checksum.
</para>
<para>
- By calculating the image's <literal>checksum</literal> on your own computer and comparing it to the original <literal>checksum</literal>, you can verify the image has not been tampered with or corrupted. The original checksum values are provided at <ulink url="https://fedoraproject.org/verify" />, and are <command>gpg</command> signed to show that even the checksum values have not been tampered with.
+ By calculating the image's <literal>checksum</literal> on your own computer and comparing it to the original <literal>checksum</literal>, you can verify the image has not been tampered with or corrupted. The original checksum values are provided at <ulink url="https://fedoraproject.org/verify" />, and are <command>gpg</command> signed to demonstrate their integrity.
</para>
+ <procedure>
+ <title>Verifying checksums on Windows systems</title>
+ <step>
+ <para>
+ Download the Fedora image of your choice from <ulink url="https://fedoraproject.org/get-fedora" /> and the corresponding checksum file from <ulink url="https://fedoraproject.org/verify " />
+ </para>
+ </step>
+ <step>
+ <para>
+ Open a <command>powershell</command> session.
+ </para>
+ </step>
+ <step>
+ <para>
+ Change to the directory containing the downloaded files.
+ </para>
+ <programlisting>
+<prompt>></prompt> <command>cd $HOME\Downloads\</command>
+<prompt>></prompt> <command>ls</command>
+<![CDATA[
+ Directory: C:\Users\Pete\Downloads
+
+Mode LastWriteTime Length Name
+---- ------------- ------ ----
+-a--- 11/25/2014 12:39 PM 272 Fedora-Server-21-x86_64-CHECKSUM
+-a--- 11/25/2014 12:39 PM 2047868928 Fedora-Server-DVD-x86_64-21.iso
+]]>
+ </programlisting>
+ </step>
+ <step>
+ <para>
+ Load the resources required to calculate the checksum.
+ </para>
+ <screen>
+<command><prompt>></prompt> $image = "Fedora-Server-DVD-x86_64-21.iso"</command>
+<command><prompt>></prompt> $checksum_file = "Fedora-Server-21-x86_64-CHECKSUM"</command>
+<command><prompt>></prompt> $sha256 = New-Object -TypeName System.Security.Cryptography.sha256CryptoServiceProvider</command>
+<command><prompt>></prompt> $exepected_checksum = ((Get-Content $checksum_file | Select-String -Pattern $image) -split " ")[0]</command>
+ </screen>
+ </step>
+ <step>
+ <para>
+ Calculate the downloaded image's checksum. This will take a while!
+ </para>
+ <screen>
+<command><prompt>></prompt> $download_checksum = [System.BitConverter]::ToString($sha256.ComputeHash([System.IO.File]::ReadAllBytes($PWD\$image)))</command>
+ </screen>
+ </step>
+ <step>
+ <para>
+ Compare the calculated checksum to the expected checksum.
+ </para>
+ <programlisting>
+<prompt>></prompt> if ( $download_checksum -replace '-', '' -eq "$expected_checksum" ) {
+ echo "Checksum test passed!"
+} else {
+ echo "Checksum test failed."
+ }
+ </programlisting>
+ </step>
+ </procedure>
+
+
+
+
+
+
+
</section>
<section id="sect-preparing-installation-methods">
9 years, 6 months
[install-guide/f21-branch] Adding Recommended Scheme to CustomSpoke
by pbokoc
commit 40e1962450eaf562e79f18f77ac139393272143c
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Mon Nov 17 16:26:24 2014 +0100
Adding Recommended Scheme to CustomSpoke
en-US/CustomSpoke_RecommendedScheme.xml | 150 ++++++++++++++++++++++++++++++-
1 files changed, 149 insertions(+), 1 deletions(-)
---
diff --git a/en-US/CustomSpoke_RecommendedScheme.xml b/en-US/CustomSpoke_RecommendedScheme.xml
index 430fcb9..c9afcf0 100644
--- a/en-US/CustomSpoke_RecommendedScheme.xml
+++ b/en-US/CustomSpoke_RecommendedScheme.xml
@@ -6,6 +6,154 @@
<section id="sect-installation-gui-manual-partitioning-recommended">
<title>Recommended Partitioning Scheme</title>
<para>
- text
+ In most cases, at least the following partitions should always be created:
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term><filename class="directory">/boot</filename> - 500 MB</term>
+ <listitem>
+ <para>
+ This partition contains the operating system kernel, which allows &PRODUCT; to boot. It also contains other files used during the bootstrap process. Due to the limitations of most firmwares, creating a small partition to hold these is recommended. In most scenarios, a 500 MB <filename class="directory">/boot</filename> partition is adequate.
+ </para>
+ <important>
+ <para>
+ If your system has a hardware RAID controller, be aware that some BIOS types do not support booting from the it. In that case, the <filename class="directory">/boot</filename> partition must be created on a partition outside of the RAID array, such as on a separate hard drive.
+ </para>
+ </important>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><filename class="directory">/</filename> (root) - 10 GB</term>
+ <listitem>
+ <para>
+ 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, <filename class="directory">/boot</filename> or <filename class="directory">/home</filename>). If you follow the recommended scheme described in this section, this will be the partition where most software packages will be installed.
+ </para>
+ <para>
+ 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.
+ </para>
+ <note>
+ <para>
+ Do not confuse the <filename class="directory">/</filename> directory with the <filename class="directory">/root</filename> directory. The latter is the home directory of the <systemitem class="username">root</systemitem> user, and is sometimes referred to as "<emphasis>slash root</emphasis>" to distinguish it from <filename class="directory">/</filename>.
+ </para>
+ </note>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><filename class="directory">/home</filename> - at least 1 GB</term>
+ <listitem>
+ <para>
+ To store user data separately from system data, create a dedicated partition within a volume group 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 <filename class="directory">/home</filename> partition will be created if there is 50 GB or more free space for your &PRODUCT; installation.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>swap - based on your system parameters</term>
+ <listitem>
+ <para>
+ 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.
+ </para>
+ <para>
+ 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 <systemitem>mkswap(8)</systemitem> man page.
+ </para>
+ <para>
+ 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.
+ </para>
+ <table frame="all">
+ <title>Recommended System Swap Space</title>
+ <tgroup align="left" cols="3" colsep="1" rowsep="1">
+ <colspec colname="col1" colnum="1"></colspec>
+ <colspec colname="col2" colnum="2"></colspec>
+ <colspec colname="col3" colnum="3"></colspec>
+ <thead>
+ <row>
+ <entry>
+ Amount of RAM in the system
+ </entry>
+ <entry>
+ Recommended swap space
+ </entry>
+ <entry>
+ Recommended swap space if allowing for hibernation
+ </entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>
+ ⩽ 2 GB
+ </entry>
+ <entry>
+ 2 times the amount of RAM
+ </entry>
+ <entry>
+ 3 times the amount of RAM
+ </entry>
+ </row>
+ <row>
+ <entry>
+ > 2 GB - 8 GB
+ </entry>
+ <entry>
+ Equal to the amount of RAM
+ </entry>
+ <entry>
+ 2 times the amount of RAM
+ </entry>
+ </row>
+ <row>
+ <entry>
+ > 8 GB - 64 GB
+ </entry>
+ <entry>
+ 0.5 times the amount of RAM
+ </entry>
+ <entry>
+ 1.5 times the amount of RAM
+ </entry>
+ </row>
+ <row>
+ <entry>
+ more than 64 GB
+ </entry>
+ <entry>
+ workload dependent
+ </entry>
+ <entry>
+ hibernation not recommended
+ </entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ <para>
+ At the border between each range listed above (for example, a system with 2 GB, 8 GB, or 64 GB of system RAM), discretion can be exercised with regard to chosen swap space and hibernation support. If your system resources allow for it, increasing the swap space may lead to better performance.
+ </para>
+ <para>
+ Distributing swap space over multiple storage devices - particularly on systems with fast drives, controllers and interfaces - also improves swap space performance.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>BIOS Boot (1 MB) or EFI System Partition (200 MB), based on your system firmware and disks</term>
+ <listitem>
+ <para>
+ Depending on your system's firmware, you may be required to create a small special partition in order for your system to be bootable. This partition must be an unencrypted, standard partition with a special file system. During automatic partitioning, these partitions are created as needed; during a manual process, you need to remember to create them, but you will be warned if you forget. For an explanation of the requirements and how they relate to your system, see <xref linkend="sect-installation-gui-storage-partitioning-bootloader" />.
+ </para>
+ <para>
+ Also note that you will only be created a BIOS Boot or an EFI System Partition file system if your system actually requires it. Otherwise, they will not be available in the
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ <para>
+ Many systems have more partitions than the minimum listed above. Choose partitions based on your particular needs. See <xref linkend="" /> for additional information and advice.
+ </para>
+ <note>
+ <para>
+ Only assign storage capacity to those partitions you require immediately. You may allocate free space at any time, to meet needs as they occur. <remark>TODO: xref to the LVM appendix</remark>
+ </para>
+ </note>
+ <para>
+ 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 linkend="sect-installation-gui-storage-partitioning" />.
</para>
</section>
9 years, 6 months
[install-guide/f21-branch] usb media creation, with GNOME disks
by Pete Travis
commit 27b7f55b2f7e5265b3eb6ea6e3909b5ea77f74c3
Author: Pete Travis <immanetize(a)fedoraproject.org>
Date: Sun Nov 16 23:43:20 2014 -0700
usb media creation, with GNOME disks
en-US/Preparing_for_Installation.xml | 29 ++++++++++++++++++++++++++++-
1 files changed, 28 insertions(+), 1 deletions(-)
---
diff --git a/en-US/Preparing_for_Installation.xml b/en-US/Preparing_for_Installation.xml
index 084f565..4c01be1 100644
--- a/en-US/Preparing_for_Installation.xml
+++ b/en-US/Preparing_for_Installation.xml
@@ -192,10 +192,37 @@ Mode LastWriteTime Length Name
</step>
<step>
<para>
- Continue with media creation using the appropriate button. After a few minutes, it will report the process is complete and your installation media will be read to use.
+ Continue with media creation using the appropriate button. After a few minutes, it will report the process is complete and your installation media will be ready to use.
</para>
</step>
</procedure>
+
+ <procedure>
+ <title>
+ Creating USB media with <application>GNOME Disks</application>
+ </title>
+ <step>
+ <para>
+ On a system with <application>GNOME</application>, or with the <package>gnome-disk-utility</package> package installed, open <guilabel>Disks</guilabel> using the system menu.
+ </para>
+ </step>
+ <step>
+ <para>
+ Click your USB device in the left column.
+ </para>
+ </step>
+ <step>
+ <para>
+ Click the menu icon in the upper right corner of the window, and choose the <guimenuitem>Restore Disk Image</guimenuitem> option.
+ </para>
+ </step>
+ <step>
+ <para>
+ Navigate to your image file and click <guilabel>Start Restoring</guilabel>. After a few minutes, it will report the process is complete and your installation media will be ready to use.
+ </para>
+ </step>
+ </procedure>
+
9 years, 6 months
[install-guide/f21-branch] obigatory warning about universal usb tools
by Pete Travis
commit 25d899f1aaf495e336f0ce2de0bf3c732c16a74e
Author: Pete Travis <immanetize(a)fedoraproject.org>
Date: Sun Nov 16 23:19:43 2014 -0700
obigatory warning about universal usb tools
en-US/Preparing_for_Installation.xml | 17 +++++++++++++++--
1 files changed, 15 insertions(+), 2 deletions(-)
---
diff --git a/en-US/Preparing_for_Installation.xml b/en-US/Preparing_for_Installation.xml
index 5015944..084f565 100644
--- a/en-US/Preparing_for_Installation.xml
+++ b/en-US/Preparing_for_Installation.xml
@@ -147,12 +147,25 @@ Mode LastWriteTime Length Name
<section id="sect-preparing-boot-media">
<title>Preparing Boot Media</title>
<para>
- TODO
+ Fedora images are <literal>Hybrid ISOs</literal> and can be used to create installation media with both optical and USB disks, for booting on both BIOS and UEFI systems.
</para>
+ <important>
+ <title>Note on Universal USB Creators</title>
+ <para>
+ Universal USB creation tools such as <application>Unetbootin</application> are a historically popular way to create USB installers from ISOs intended for optical media. They typically function by creating a filesystem on the USB drive, extracting files from the image, and writing <application>syslinux</application> bootloader to the device.
+ </para>
+ <para>
+ These methods circumvent the bootloader configuration built into Fedora images, which are pre-partitioned and designed to boot on UEFI systems with SecureBoot enabled as well as BIOS systems. They do not produce a consistent result with Fedora's images, especially for use with UEFI systems.
+ </para>
+ <para>
+ Utilities that use a direct write method, and do not modify the Fedora image, will produce the most consistently successful results.
+ </para>
+ </important>
+
<warning>
<title>Be sure you choose the right device!</title>
<para>
- This media creation method is destructive. Ensure you do not need any data on the USB stick, and double check you have chosen the correct device before continuing.
+ Most media creation methods in this section are destructive. Ensure you do not need any data on the USB stick, and double check you have chosen the correct device before continuing.
</para>
</warning>
<procedure>
9 years, 6 months
[install-guide/f21-branch] Windows USB media creation.
by Pete Travis
commit 949c3cd5d58cb394fa260bc890a7e88e02d314e3
Author: Pete Travis <immanetize(a)fedoraproject.org>
Date: Sun Nov 16 22:33:50 2014 -0700
Windows USB media creation.
en-US/Preparing_for_Installation.xml | 37 ++++++++++++++++++++++++++++++++++
1 files changed, 37 insertions(+), 0 deletions(-)
---
diff --git a/en-US/Preparing_for_Installation.xml b/en-US/Preparing_for_Installation.xml
index 8ad04de..5015944 100644
--- a/en-US/Preparing_for_Installation.xml
+++ b/en-US/Preparing_for_Installation.xml
@@ -149,6 +149,43 @@ Mode LastWriteTime Length Name
<para>
TODO
</para>
+ <warning>
+ <title>Be sure you choose the right device!</title>
+ <para>
+ This media creation method is destructive. Ensure you do not need any data on the USB stick, and double check you have chosen the correct device before continuing.
+ </para>
+ </warning>
+ <procedure>
+ <title>Creating USB Media on Windows</title>
+ <step>
+ <para>
+ Download the Fedora image of your choice from <ulink url="https://fedoraproject.org/get-fedora" /> and the corresponding checksum file from <ulink url="https://fedoraproject.org/verify " />.
+ </para>
+ </step>
+ <step>
+ <para>
+ Download and run the <ulink url="https://github.com/downloads/openSUSE/kiwi/ImageWriter.exe"><application>SUSE Studio ImageWriter</application></ulink> or <ulink url="http://www.netbsd.org/~martin/rawrite32/"><application>Rawrite32</application></ulink>.
+ </para>
+ </step>
+ <step>
+ <para>
+ Choose the downloaded Fedora image. You may have to change the file selection dialog's options to view ISO or all file types.
+ </para>
+ </step>
+ <step>
+ <para>
+ Choose the USB device you wish to convert to installation media.
+ </para>
+ </step>
+ <step>
+ <para>
+ Continue with media creation using the appropriate button. After a few minutes, it will report the process is complete and your installation media will be read to use.
+ </para>
+ </step>
+ </procedure>
+
+
+
</section>
<section id="sect-preparing-installation-sources">
9 years, 6 months
[install-guide/f21-branch] Hey, we don't need to recommend any third party tools to verify checksums on Windows systems!
by Pete Travis
commit 5d617c05f1b14d2c7012e80037478d43d2278d4c
Author: Pete Travis <immanetize(a)fedoraproject.org>
Date: Sun Nov 16 20:12:57 2014 -0700
Hey, we don't need to recommend any third party tools to verify checksums on Windows systems!
en-US/Preparing_for_Installation.xml | 70 +++++++++++++++++++++++++++++++++-
1 files changed, 69 insertions(+), 1 deletions(-)
---
diff --git a/en-US/Preparing_for_Installation.xml b/en-US/Preparing_for_Installation.xml
index 37ce705..8ad04de 100644
--- a/en-US/Preparing_for_Installation.xml
+++ b/en-US/Preparing_for_Installation.xml
@@ -65,8 +65,76 @@
Because transmission errors or other problems may corrupt the Fedora image you have downloaded, it is imporant to verify the file's integrity. After the images are created, an operation is performed on the file that produces a value called a <literal>checksum</literal> using a complex mathematical algorithm. The operation is sufficiently complex that <emphasis>any change</emphasis> to the original file will produce a different checksum.
</para>
<para>
- By calculating the image's <literal>checksum</literal> on your own computer and comparing it to the original <literal>checksum</literal>, you can verify the image has not been tampered with or corrupted. The original checksum values are provided at <ulink url="https://fedoraproject.org/verify" />, and are <command>gpg</command> signed to show that even the checksum values have not been tampered with.
+ By calculating the image's <literal>checksum</literal> on your own computer and comparing it to the original <literal>checksum</literal>, you can verify the image has not been tampered with or corrupted. The original checksum values are provided at <ulink url="https://fedoraproject.org/verify" />, and are <command>gpg</command> signed to demonstrate their integrity.
</para>
+ <procedure>
+ <title>Verifying checksums on Windows systems</title>
+ <step>
+ <para>
+ Download the Fedora image of your choice from <ulink url="https://fedoraproject.org/get-fedora" /> and the corresponding checksum file from <ulink url="https://fedoraproject.org/verify " />
+ </para>
+ </step>
+ <step>
+ <para>
+ Open a <command>powershell</command> session.
+ </para>
+ </step>
+ <step>
+ <para>
+ Change to the directory containing the downloaded files.
+ </para>
+ <programlisting>
+<prompt>></prompt> <command>cd $HOME\Downloads\</command>
+<prompt>></prompt> <command>ls</command>
+<![CDATA[
+ Directory: C:\Users\Pete\Downloads
+
+Mode LastWriteTime Length Name
+---- ------------- ------ ----
+-a--- 11/25/2014 12:39 PM 272 Fedora-Server-21-x86_64-CHECKSUM
+-a--- 11/25/2014 12:39 PM 2047868928 Fedora-Server-DVD-x86_64-21.iso
+]]>
+ </programlisting>
+ </step>
+ <step>
+ <para>
+ Load the resources required to calculate the checksum.
+ </para>
+ <screen>
+<command><prompt>></prompt> $image = "Fedora-Server-DVD-x86_64-21.iso"</command>
+<command><prompt>></prompt> $checksum_file = "Fedora-Server-21-x86_64-CHECKSUM"</command>
+<command><prompt>></prompt> $sha256 = New-Object -TypeName System.Security.Cryptography.sha256CryptoServiceProvider</command>
+<command><prompt>></prompt> $exepected_checksum = ((Get-Content $checksum_file | Select-String -Pattern $image) -split " ")[0]</command>
+ </screen>
+ </step>
+ <step>
+ <para>
+ Calculate the downloaded image's checksum. This will take a while!
+ </para>
+ <screen>
+<command><prompt>></prompt> $download_checksum = [System.BitConverter]::ToString($sha256.ComputeHash([System.IO.File]::ReadAllBytes($PWD\$image)))</command>
+ </screen>
+ </step>
+ <step>
+ <para>
+ Compare the calculated checksum to the expected checksum.
+ </para>
+ <programlisting>
+<prompt>></prompt> if ( $download_checksum -replace '-', '' -eq "$expected_checksum" ) {
+ echo "Checksum test passed!"
+} else {
+ echo "Checksum test failed."
+ }
+ </programlisting>
+ </step>
+ </procedure>
+
+
+
+
+
+
+
</section>
<section id="sect-preparing-installation-methods">
9 years, 6 months
[install-guide/f21-branch] Adding structure to CustomSpoke and adding Advice on Partitions
by pbokoc
commit c582e809b2d7cdce4fd771ceb3d465958623a6b7
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Sun Nov 16 21:40:10 2014 +0100
Adding structure to CustomSpoke and adding Advice on Partitions
en-US/CustomSpoke.xml | 9 ++++
en-US/CustomSpoke_AddBtrfs.xml | 11 +++++
en-US/CustomSpoke_AddLVM.xml | 11 +++++
en-US/CustomSpoke_AddPhysical.xml | 11 +++++
en-US/CustomSpoke_FileSystems.xml | 11 +++++
en-US/CustomSpoke_PartitioningAdvice.xml | 73 ++++++++++++++++++++++++++++++
en-US/CustomSpoke_RecommendedScheme.xml | 11 +++++
en-US/CustomSpoke_SoftwareRAID.xml | 11 +++++
prepare_anaconda_help_content.py | 7 +++
9 files changed, 155 insertions(+), 0 deletions(-)
---
diff --git a/en-US/CustomSpoke.xml b/en-US/CustomSpoke.xml
index 7a3b3af..a59eb4d 100644
--- a/en-US/CustomSpoke.xml
+++ b/en-US/CustomSpoke.xml
@@ -8,4 +8,13 @@
<para>
text
</para>
+
+ <xi:include href="CustomSpoke_AddPhysical.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="CustomSpoke_SoftwareRAID.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="CustomSpoke_AddLVM.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="CustomSpoke_AddBtrfs.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="CustomSpoke_FileSystems.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="CustomSpoke_RecommendedScheme.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="CustomSpoke_PartitioningAdvice.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+
</section>
diff --git a/en-US/CustomSpoke_AddBtrfs.xml b/en-US/CustomSpoke_AddBtrfs.xml
new file mode 100644
index 0000000..613e479
--- /dev/null
+++ b/en-US/CustomSpoke_AddBtrfs.xml
@@ -0,0 +1,11 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="sect-installation-gui-manual-partitioning-btrfs">
+ <title>Creating a Btrfs Layout</title>
+ <para>
+ text
+ </para>
+</section>
diff --git a/en-US/CustomSpoke_AddLVM.xml b/en-US/CustomSpoke_AddLVM.xml
new file mode 100644
index 0000000..934b029
--- /dev/null
+++ b/en-US/CustomSpoke_AddLVM.xml
@@ -0,0 +1,11 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="sect-installation-gui-manual-partitioning-lvm">
+ <title>Creating a Logical Volume Managament (LVM) Layout</title>
+ <para>
+ text
+ </para>
+</section>
diff --git a/en-US/CustomSpoke_AddPhysical.xml b/en-US/CustomSpoke_AddPhysical.xml
new file mode 100644
index 0000000..c553e94
--- /dev/null
+++ b/en-US/CustomSpoke_AddPhysical.xml
@@ -0,0 +1,11 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="sect-installation-gui-manual-partitioning-physical">
+ <title>Creating Physical Partitions</title>
+ <para>
+ text
+ </para>
+</section>
diff --git a/en-US/CustomSpoke_FileSystems.xml b/en-US/CustomSpoke_FileSystems.xml
new file mode 100644
index 0000000..13d2894
--- /dev/null
+++ b/en-US/CustomSpoke_FileSystems.xml
@@ -0,0 +1,11 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="sect-installation-gui-manual-partitioning-filesystems">
+ <title>Device and File System Types</title>
+ <para>
+ text
+ </para>
+</section>
diff --git a/en-US/CustomSpoke_PartitioningAdvice.xml b/en-US/CustomSpoke_PartitioningAdvice.xml
new file mode 100644
index 0000000..5c101c7
--- /dev/null
+++ b/en-US/CustomSpoke_PartitioningAdvice.xml
@@ -0,0 +1,73 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="sect-installation-gui-manual-partitioning-advice">
+ <title>Advice on Partitions</title>
+ <para>
+ There is no best way to partition every system; the optimal setup depends on how you plan to use the system being installed. However, the following tips may help you find the optimal layout for your needs:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Consider encrypting any partitions and volumes which might contain sensitive data. Encryption prevents unauthorized people from accessing the data on the partitions, even if they have access to the physical storage device. In most cases, you should at least encrypt the <filename class="directory">/home</filename> partition, which contains user data.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ In some cases, creating separate mount points for directories other than <filename class="directory">/</filename>, <filename class="directory">/boot</filename> and <filename class="directory">/home</filename> may be useful; for example, on a server running a <application>MySQL</application> database, having a separate mount point for <filename class="directory">/var/lib/mysql</filename> will allow you to preserve the database during a reinstallation without having to restore it from backup afterwards. However, having unnecessary separate mount points will make storage administration more difficult.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Some special restrictions apply to certain directories with regards on which partitioning layouts can they be placed. Notably, the <filename class="directory">/boot</filename> directory must always be on a physical partition (not on an LVM volume or a Btrfs subvolume), and <filename class="directory">/usr</filename> can not be on a Btrfs subvolume.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ If you are new to Linux, consider reviewing the <citetitle>Linux Filesystem Hierarchy Standard</citetitle> at <ulink url="http://refspecs.linuxfoundation.org/FHS_2.3/fhs-2.3.html" /> for information about various system directories and their contents.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Each kernel installed on your system requires approximately 20 MB on the <filename class="directory">/boot</filename> partition. The default partition size of 500 MB for <filename class="directory">/boot</filename> should suffice for most common uses; increase the size of this partition if you plan to keep many kernels installed at the same time.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The <filename class="directory">/var</filename> directory holds content for a number of applications, including the <application>Apache</application> web server, and is used by the <application>Yum</application> package manager to temporarily store downloaded package updates. Make sure that the partition or volume containing <filename class="directory">/var</filename> has at least 3 GB.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The <filename class="directory">/usr</filename> directory holds the majority of software on a typical &PRODUCT; installation. The partition or volume containing this directory should therefore be at least 5 GB for minimal installations, and at least 10 GB for installations with a graphical environment.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Consider leaving a portion of the space in an LVM volume group unallocated. This unallocated space gives you flexibility if your space requirements change but you do not wish to remove data from other volumes. You can also select the <guilabel>Thin provisioning</guilabel> device type for the partition to have the unused space handled automatically by the volume.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The size of an <systemitem>XFS</systemitem> file system can not be reduced - if you need to make a partition or volume with this file system smaller, you must back up your data, destroy the file system, and create a new, smaller one in its place. Therefore, if you expect needing to manipulate your partitioning layout later, you should use the <systemitem>ext4</systemitem> file system instead.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Use Logical Volume Management (LVM) if you anticipate expanding your storage by adding more hard drives after the installation. With LVM, you can create physical volumes on the new drives, and then assign them to any volume group and logical volume as you see fit - for example, you can easily expand your system's <filename class="directory">/home</filename> (or any other directory residing on a logical volume).
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Creating a BIOS Boot partition or an EFI System Partition may be necessary, depending on your system's firmware, boot drive size, and boot drive disk label. See <xref linkend="sect-installation-gui-storage-partitioning-bootloader" /> for information about these partitions. Note that the graphical installer will not let you create a BIOS Boot or EFI System Partition if your system does <emphasis>not</emphasis> require one - in that case, they will be hidden from the menu.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ If you need to make any changes to your storage configuration after the installation, &PRODUCT; repositories offer several different tools which can help you do this. If you prefer a command line tool, try <package>system-storage-manager</package>. <remark>TODO: recommend a GUI tool? blivet-gui, maybe?</remark>
+ </para>
+ </listitem>
+ </itemizedlist>
+</section>
diff --git a/en-US/CustomSpoke_RecommendedScheme.xml b/en-US/CustomSpoke_RecommendedScheme.xml
new file mode 100644
index 0000000..430fcb9
--- /dev/null
+++ b/en-US/CustomSpoke_RecommendedScheme.xml
@@ -0,0 +1,11 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="sect-installation-gui-manual-partitioning-recommended">
+ <title>Recommended Partitioning Scheme</title>
+ <para>
+ text
+ </para>
+</section>
diff --git a/en-US/CustomSpoke_SoftwareRAID.xml b/en-US/CustomSpoke_SoftwareRAID.xml
new file mode 100644
index 0000000..b8f8aa9
--- /dev/null
+++ b/en-US/CustomSpoke_SoftwareRAID.xml
@@ -0,0 +1,11 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="sect-installation-gui-manual-partitioning-swraid">
+ <title>Creating Software RAID</title>
+ <para>
+ text
+ </para>
+</section>
diff --git a/prepare_anaconda_help_content.py b/prepare_anaconda_help_content.py
index 19ff72a..21ad7ff 100755
--- a/prepare_anaconda_help_content.py
+++ b/prepare_anaconda_help_content.py
@@ -29,6 +29,13 @@ ANACONDA_HELP_FILES = [
"Installation_Guide.ent",
"LangSupportSpoke.xml",
"CustomSpoke.xml",
+ "CustomSpoke_AddPhysical.xml",
+ "CustomSpoke_SoftwareRAID.xml",
+ "CustomSpoke_AddLVM.xml",
+ "CustomSpoke_AddBtrfs.xml",
+ "CustomSpoke_FileSystems.xml",
+ "CustomSpoke_RecommendedScheme.xml",
+ "CustomSpoke_PartitioningAdvice.xml",
"NetworkSpoke.xml",
"NetworkSpoke_VirtualInterfaces.xml",
"NetworkSpoke_EditConnection.xml",
9 years, 6 months
[install-guide/f21-branch] Adding the Add FCoE SAN section to FilterSpoke
by pbokoc
commit 4e568e8a25d98f51ca847f3733ed0ed233622ca0
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Sun Nov 16 19:48:18 2014 +0100
Adding the Add FCoE SAN section to FilterSpoke
en-US/FilterSpoke_AddFCoE.xml | 43 ++++++++++++++++++++++++++++++++++++++++-
1 files changed, 42 insertions(+), 1 deletions(-)
---
diff --git a/en-US/FilterSpoke_AddFCoE.xml b/en-US/FilterSpoke_AddFCoE.xml
index 92ad22d..f3c64e2 100644
--- a/en-US/FilterSpoke_AddFCoE.xml
+++ b/en-US/FilterSpoke_AddFCoE.xml
@@ -6,6 +6,47 @@
<section id="sect-installation-gui-installation-destination-add-fcoe">
<title>Add FCoE SAN</title>
<para>
- text
+ The following procedure explains how to add <firstterm>Fibre Channel over Ethernet</firstterm> (FCoE) storage devices and make them available during the installation:
</para>
+ <procedure id="proc-installation-gui-installation-destination-add-fcoe">
+ <title>Add FCoE Target</title>
+ <step>
+ <para>
+ Click the <guilabel>Add FCoE SAN</guilabel> button in the bottom right corner of <xref linkend="sect-installation-gui-installation-destination" />. A new dialog window will open.
+ </para>
+ </step>
+ <step>
+ <para>
+ Select the network interface (<guilabel>NIC</guilabel>) which is connected to your FCoE switch from the drop-down menu. Note that this network interface must be configured and connected - see <xref linkend="sect-installation-gui-network-configuration" />.
+ </para>
+ </step>
+ <step>
+ <para>
+ Below the <guilabel>NIC</guilabel> drop-down menu are two choices:
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term>Use DCB</term>
+ <listitem>
+ <para>
+ <firstterm>Data Center Bridging</firstterm> (DCB) is a set of enhancements to the Ethernet protocols designed to increase the efficiency of Ethernet connections in storage networks and clusters. This option should only be enabled for network interfaces that require a host-based DCBX client. Configurations on interfaces that implement a hardware DCBX client should leave this check box empty.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Use auto vlan</term>
+ <listitem>
+ <para>
+ This option indicates whether VLAN discovery should be performed. If this box is checked, then the <firstterm>FCoE Initiation Protocol</firstterm> (FIP) VLAN discovery protocol will run on the Ethernet interface once the link configuration has been validated. If they are not already configured, network interfaces for any discovered FCoE VLANs will be automatically created and FCoE instances will be created on the VLAN interfaces. This option is enabled by default.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </step>
+ <step>
+ <para>
+ After you select which interface and options to use, click <guilabel>Add FCoE Disk(s)</guilabel>. Discovered FCoE storage devices will be displayed under the <guilabel>Other SAN Devices</guilabel> tab in <xref linkend="sect-installation-gui-installation-destination" />.
+ </para>
+ </step>
+ </procedure>
</section>
9 years, 6 months
[install-guide: 4/4] checksum introduction
by pbokoc
commit 234e4d86eb39ad618a6009a5969a5c5d46304a13
Author: Pete Travis <immanetize(a)fedoraproject.org>
Date: Sun Nov 16 13:47:01 2014 -0700
checksum introduction
en-US/Preparing_for_Installation.xml | 10 +++++++++-
1 files changed, 9 insertions(+), 1 deletions(-)
---
diff --git a/en-US/Preparing_for_Installation.xml b/en-US/Preparing_for_Installation.xml
index dcd1c23..37ce705 100644
--- a/en-US/Preparing_for_Installation.xml
+++ b/en-US/Preparing_for_Installation.xml
@@ -60,7 +60,15 @@
</para>
</section>
<section id="sect-verifying-images">
- <title>
+ <title>Verifying the Downloaded Image</title>
+ <para>
+ Because transmission errors or other problems may corrupt the Fedora image you have downloaded, it is imporant to verify the file's integrity. After the images are created, an operation is performed on the file that produces a value called a <literal>checksum</literal> using a complex mathematical algorithm. The operation is sufficiently complex that <emphasis>any change</emphasis> to the original file will produce a different checksum.
+ </para>
+ <para>
+ By calculating the image's <literal>checksum</literal> on your own computer and comparing it to the original <literal>checksum</literal>, you can verify the image has not been tampered with or corrupted. The original checksum values are provided at <ulink url="https://fedoraproject.org/verify" />, and are <command>gpg</command> signed to show that even the checksum values have not been tampered with.
+ </para>
+ </section>
+
<section id="sect-preparing-installation-methods">
<title>Choosing an Installation Method</title>
<para>
9 years, 6 months
[install-guide: 3/4] Adding structure to CustomSpoke and adding Advice on Partitions
by pbokoc
commit eb06ae07a1a324b70b000401d92c74acb9fe6789
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Sun Nov 16 21:40:10 2014 +0100
Adding structure to CustomSpoke and adding Advice on Partitions
en-US/CustomSpoke.xml | 9 ++++
en-US/CustomSpoke_AddBtrfs.xml | 11 +++++
en-US/CustomSpoke_AddLVM.xml | 11 +++++
en-US/CustomSpoke_AddPhysical.xml | 11 +++++
en-US/CustomSpoke_FileSystems.xml | 11 +++++
en-US/CustomSpoke_PartitioningAdvice.xml | 73 ++++++++++++++++++++++++++++++
en-US/CustomSpoke_RecommendedScheme.xml | 11 +++++
en-US/CustomSpoke_SoftwareRAID.xml | 11 +++++
prepare_anaconda_help_content.py | 7 +++
9 files changed, 155 insertions(+), 0 deletions(-)
---
diff --git a/en-US/CustomSpoke.xml b/en-US/CustomSpoke.xml
index 7a3b3af..a59eb4d 100644
--- a/en-US/CustomSpoke.xml
+++ b/en-US/CustomSpoke.xml
@@ -8,4 +8,13 @@
<para>
text
</para>
+
+ <xi:include href="CustomSpoke_AddPhysical.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="CustomSpoke_SoftwareRAID.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="CustomSpoke_AddLVM.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="CustomSpoke_AddBtrfs.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="CustomSpoke_FileSystems.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="CustomSpoke_RecommendedScheme.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="CustomSpoke_PartitioningAdvice.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+
</section>
diff --git a/en-US/CustomSpoke_AddBtrfs.xml b/en-US/CustomSpoke_AddBtrfs.xml
new file mode 100644
index 0000000..613e479
--- /dev/null
+++ b/en-US/CustomSpoke_AddBtrfs.xml
@@ -0,0 +1,11 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="sect-installation-gui-manual-partitioning-btrfs">
+ <title>Creating a Btrfs Layout</title>
+ <para>
+ text
+ </para>
+</section>
diff --git a/en-US/CustomSpoke_AddLVM.xml b/en-US/CustomSpoke_AddLVM.xml
new file mode 100644
index 0000000..934b029
--- /dev/null
+++ b/en-US/CustomSpoke_AddLVM.xml
@@ -0,0 +1,11 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="sect-installation-gui-manual-partitioning-lvm">
+ <title>Creating a Logical Volume Managament (LVM) Layout</title>
+ <para>
+ text
+ </para>
+</section>
diff --git a/en-US/CustomSpoke_AddPhysical.xml b/en-US/CustomSpoke_AddPhysical.xml
new file mode 100644
index 0000000..c553e94
--- /dev/null
+++ b/en-US/CustomSpoke_AddPhysical.xml
@@ -0,0 +1,11 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="sect-installation-gui-manual-partitioning-physical">
+ <title>Creating Physical Partitions</title>
+ <para>
+ text
+ </para>
+</section>
diff --git a/en-US/CustomSpoke_FileSystems.xml b/en-US/CustomSpoke_FileSystems.xml
new file mode 100644
index 0000000..13d2894
--- /dev/null
+++ b/en-US/CustomSpoke_FileSystems.xml
@@ -0,0 +1,11 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="sect-installation-gui-manual-partitioning-filesystems">
+ <title>Device and File System Types</title>
+ <para>
+ text
+ </para>
+</section>
diff --git a/en-US/CustomSpoke_PartitioningAdvice.xml b/en-US/CustomSpoke_PartitioningAdvice.xml
new file mode 100644
index 0000000..5c101c7
--- /dev/null
+++ b/en-US/CustomSpoke_PartitioningAdvice.xml
@@ -0,0 +1,73 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="sect-installation-gui-manual-partitioning-advice">
+ <title>Advice on Partitions</title>
+ <para>
+ There is no best way to partition every system; the optimal setup depends on how you plan to use the system being installed. However, the following tips may help you find the optimal layout for your needs:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Consider encrypting any partitions and volumes which might contain sensitive data. Encryption prevents unauthorized people from accessing the data on the partitions, even if they have access to the physical storage device. In most cases, you should at least encrypt the <filename class="directory">/home</filename> partition, which contains user data.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ In some cases, creating separate mount points for directories other than <filename class="directory">/</filename>, <filename class="directory">/boot</filename> and <filename class="directory">/home</filename> may be useful; for example, on a server running a <application>MySQL</application> database, having a separate mount point for <filename class="directory">/var/lib/mysql</filename> will allow you to preserve the database during a reinstallation without having to restore it from backup afterwards. However, having unnecessary separate mount points will make storage administration more difficult.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Some special restrictions apply to certain directories with regards on which partitioning layouts can they be placed. Notably, the <filename class="directory">/boot</filename> directory must always be on a physical partition (not on an LVM volume or a Btrfs subvolume), and <filename class="directory">/usr</filename> can not be on a Btrfs subvolume.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ If you are new to Linux, consider reviewing the <citetitle>Linux Filesystem Hierarchy Standard</citetitle> at <ulink url="http://refspecs.linuxfoundation.org/FHS_2.3/fhs-2.3.html" /> for information about various system directories and their contents.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Each kernel installed on your system requires approximately 20 MB on the <filename class="directory">/boot</filename> partition. The default partition size of 500 MB for <filename class="directory">/boot</filename> should suffice for most common uses; increase the size of this partition if you plan to keep many kernels installed at the same time.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The <filename class="directory">/var</filename> directory holds content for a number of applications, including the <application>Apache</application> web server, and is used by the <application>Yum</application> package manager to temporarily store downloaded package updates. Make sure that the partition or volume containing <filename class="directory">/var</filename> has at least 3 GB.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The <filename class="directory">/usr</filename> directory holds the majority of software on a typical &PRODUCT; installation. The partition or volume containing this directory should therefore be at least 5 GB for minimal installations, and at least 10 GB for installations with a graphical environment.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Consider leaving a portion of the space in an LVM volume group unallocated. This unallocated space gives you flexibility if your space requirements change but you do not wish to remove data from other volumes. You can also select the <guilabel>Thin provisioning</guilabel> device type for the partition to have the unused space handled automatically by the volume.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The size of an <systemitem>XFS</systemitem> file system can not be reduced - if you need to make a partition or volume with this file system smaller, you must back up your data, destroy the file system, and create a new, smaller one in its place. Therefore, if you expect needing to manipulate your partitioning layout later, you should use the <systemitem>ext4</systemitem> file system instead.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Use Logical Volume Management (LVM) if you anticipate expanding your storage by adding more hard drives after the installation. With LVM, you can create physical volumes on the new drives, and then assign them to any volume group and logical volume as you see fit - for example, you can easily expand your system's <filename class="directory">/home</filename> (or any other directory residing on a logical volume).
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Creating a BIOS Boot partition or an EFI System Partition may be necessary, depending on your system's firmware, boot drive size, and boot drive disk label. See <xref linkend="sect-installation-gui-storage-partitioning-bootloader" /> for information about these partitions. Note that the graphical installer will not let you create a BIOS Boot or EFI System Partition if your system does <emphasis>not</emphasis> require one - in that case, they will be hidden from the menu.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ If you need to make any changes to your storage configuration after the installation, &PRODUCT; repositories offer several different tools which can help you do this. If you prefer a command line tool, try <package>system-storage-manager</package>. <remark>TODO: recommend a GUI tool? blivet-gui, maybe?</remark>
+ </para>
+ </listitem>
+ </itemizedlist>
+</section>
diff --git a/en-US/CustomSpoke_RecommendedScheme.xml b/en-US/CustomSpoke_RecommendedScheme.xml
new file mode 100644
index 0000000..430fcb9
--- /dev/null
+++ b/en-US/CustomSpoke_RecommendedScheme.xml
@@ -0,0 +1,11 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="sect-installation-gui-manual-partitioning-recommended">
+ <title>Recommended Partitioning Scheme</title>
+ <para>
+ text
+ </para>
+</section>
diff --git a/en-US/CustomSpoke_SoftwareRAID.xml b/en-US/CustomSpoke_SoftwareRAID.xml
new file mode 100644
index 0000000..b8f8aa9
--- /dev/null
+++ b/en-US/CustomSpoke_SoftwareRAID.xml
@@ -0,0 +1,11 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<section id="sect-installation-gui-manual-partitioning-swraid">
+ <title>Creating Software RAID</title>
+ <para>
+ text
+ </para>
+</section>
diff --git a/prepare_anaconda_help_content.py b/prepare_anaconda_help_content.py
index 19ff72a..21ad7ff 100755
--- a/prepare_anaconda_help_content.py
+++ b/prepare_anaconda_help_content.py
@@ -29,6 +29,13 @@ ANACONDA_HELP_FILES = [
"Installation_Guide.ent",
"LangSupportSpoke.xml",
"CustomSpoke.xml",
+ "CustomSpoke_AddPhysical.xml",
+ "CustomSpoke_SoftwareRAID.xml",
+ "CustomSpoke_AddLVM.xml",
+ "CustomSpoke_AddBtrfs.xml",
+ "CustomSpoke_FileSystems.xml",
+ "CustomSpoke_RecommendedScheme.xml",
+ "CustomSpoke_PartitioningAdvice.xml",
"NetworkSpoke.xml",
"NetworkSpoke_VirtualInterfaces.xml",
"NetworkSpoke_EditConnection.xml",
9 years, 6 months