December 2014 - docs-commits - Fedora Mailing-Lists

[install-guide/f21-branch] Removing an invalid xref

by pbokoc

commit d9bd8948e871ca442ace358f73040b6d94fa7297 Author: Petr Bokoc <pbokoc(a)redhat.com> Date: Mon Dec 8 18:02:57 2014 +0100 Removing an invalid xref en-US/SourceSpoke.xml | 5 ----- 1 files changed, 0 insertions(+), 5 deletions(-) --- diff --git a/en-US/SourceSpoke.xml b/en-US/SourceSpoke.xml index 5b99f05..2e211e1 100644 --- a/en-US/SourceSpoke.xml +++ b/en-US/SourceSpoke.xml @@ -8,11 +8,6 @@ <para> The <guilabel>Installation Source</guilabel> screen allows you to specify a location (local or on the network) from which packages will be downloaded and installed on your system. This screen will be configured automatically in most cases, but you can change your settings or add additional sources. </para> - <note> - <para> - Some preparation may be necessary to create an installation source. See <xref linkend="sect-preparing-installation-sources" /> for instructions. - </para> - </note> <figure> <title>Installation Source</title> <mediaobject>

9 years, 6 months

1
0
0 / 0

[install-guide/f21-branch] Small fix in Preparing for Installation

by pbokoc

commit ee58ae15f54dfc0e07791428b001a3e849c4ebe0 Author: Petr Bokoc <pbokoc(a)redhat.com> Date: Mon Dec 8 17:36:56 2014 +0100 Small fix in Preparing for Installation en-US/Preparing_for_Installation.xml | 18 ++---------------- 1 files changed, 2 insertions(+), 16 deletions(-) --- diff --git a/en-US/Preparing_for_Installation.xml b/en-US/Preparing_for_Installation.xml index 4e26e58..2ae9d3a 100644 --- a/en-US/Preparing_for_Installation.xml +++ b/en-US/Preparing_for_Installation.xml @@ -48,7 +48,7 @@ Read more about Fedora Workstation, Fedora Cloud, Fedora Server and the available media types in <xref linkend="chap-downloading-fedora" />. </para> <para> - You can also choose a Fedora <literal>Spin</literal> featuring favorite alternative desktops or tools for specialized tasks at <ulink url="http://spins.fedoraproject.org" /> + You can also choose a Fedora <firstterm>Spin</firstterm> featuring favorite alternative desktops or tools for specialized tasks at <ulink url="http://spins.fedoraproject.org" />. </para> </section> @@ -159,13 +159,6 @@ Mode LastWriteTime Length Name </procedure> </section> - <section id="sect-preparing-installation-methods"> - <title>Choosing an Installation Method</title> - <para> - TODO - </para> - </section> - <section id="sect-preparing-boot-media"> <title>Preparing Boot Media</title> <para> @@ -305,13 +298,6 @@ Mode LastWriteTime Length Name </step> </procedure> - </section> - - <section id="sect-preparing-installation-sources"> - <title>Preparing Installation Sources</title> - <para> - TODO - </para> - </section> + </section> </chapter>

9 years, 6 months

1
0
0 / 0

[install-guide/f21-branch] Adding a basic procedure for creating bootable CD/DVD

by pbokoc

commit 4da8db39e3869da66a7f00c5ff5aeb6935bfd1b6 Author: Petr Bokoc <pbokoc(a)redhat.com> Date: Mon Dec 8 17:26:27 2014 +0100 Adding a basic procedure for creating bootable CD/DVD en-US/Preparing_for_Installation.xml | 37 +++++++++++++++++++++++++++++++-- 1 files changed, 34 insertions(+), 3 deletions(-) --- diff --git a/en-US/Preparing_for_Installation.xml b/en-US/Preparing_for_Installation.xml index bbddba2..4e26e58 100644 --- a/en-US/Preparing_for_Installation.xml +++ b/en-US/Preparing_for_Installation.xml @@ -215,9 +215,7 @@ Mode LastWriteTime Length Name </procedure> <procedure> - <title> - Creating USB media with <application>GNOME Disks</application> - </title> + <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. @@ -274,6 +272,39 @@ Mode LastWriteTime Length Name </screen> </step> </procedure> + + <procedure> + <title>Creating a Boot CD or DVD</title> + <para> + In addition to creating a bootable USB flash drive, you can also use the provided ISO images to create bootable optical media (a CD or DVD). This approach may be necessary when installing &PRODUCT; on an older system which can not boot from USB. + </para> + <note> + <para> + The exact steps you need to take to burn a bootable CD or DVD from an ISO image will vary depending on what disc burning software you use. This procedure only offers a general overview. + </para> + </note> + <step> + <para> + Insert a blank CD or DVD into your system's CD or DVD burner. + </para> + </step> + <step> + <para> + Open your system's burning software - for example, <application>Brasero</application> on &PRODUCT; systems with <application>GNOME</application> desktop environment, or <application>Nero</application> on Windows systems. In the software's main menu, find an option which lets you burn an ISO image to a disc. For example, in <application>Brasero</application>, this option is <guilabel>Burn image</guilabel> in the main menu on the left side of the window. + </para> + </step> + <step> + <para> + When prompted, select the ISO image of &PRODUCT; to be burned, and the CD or DVD burner with a blank disc inside (if you have more than one drive). + </para> + </step> + <step> + <para> + Confirm your selection, and wait for the disc to be burned. + </para> + </step> + </procedure> + </section> <section id="sect-preparing-installation-sources">

9 years, 6 months

1
0
0 / 0

[install-guide/f21-branch] No upgrade docs at this time, sorry

by pbokoc

commit f9a4864641d32c28535b7790a4d27d716e3db30c Author: Petr Bokoc <pbokoc(a)redhat.com> Date: Mon Dec 8 16:16:20 2014 +0100 No upgrade docs at this time, sorry en-US/Preparing_for_Installation.xml | 2 +- en-US/Upgrading_Your_Current_System.xml | 29 ++++++++++++++++++++++++++--- 2 files changed, 27 insertions(+), 4 deletions(-) --- diff --git a/en-US/Preparing_for_Installation.xml b/en-US/Preparing_for_Installation.xml index dce6a1a..bbddba2 100644 --- a/en-US/Preparing_for_Installation.xml +++ b/en-US/Preparing_for_Installation.xml @@ -16,7 +16,7 @@ </para> <variablelist> <varlistentry> - <term>Automatic upgrade using FedUp</term> + <term>Automatic upgrade using <application>FedUp</application></term> <listitem> <para> The preferred way to upgrade your system is an automatic upgrade using the <application>FedUp</application> utility. For information on performing an automatic upgrade, see <xref linkend="sect-upgrading-fedora-fedup" />. diff --git a/en-US/Upgrading_Your_Current_System.xml b/en-US/Upgrading_Your_Current_System.xml index 3b3ceea..899e6c7 100644 --- a/en-US/Upgrading_Your_Current_System.xml +++ b/en-US/Upgrading_Your_Current_System.xml @@ -6,20 +6,43 @@ <chapter id="chap-upgrading"> <title>Upgrading Your Current System</title> <para> - intro text + This chapter explains how to upgrade your existing &PRODUCT; installation to the current release. There are two basic ways to do so: </para> + <variablelist> + <varlistentry> + <term>Automatic upgrade using <application>FedUp</application></term> + <listitem> + <para> + The preferred way to upgrade your system is an automatic upgrade using the <application>FedUp</application> utility. For information on performing an automatic upgrade, see <xref linkend="sect-upgrading-fedora-fedup" />. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term>Manual Reinstallation</term> + <listitem> + <para> + You can upgrade to the latest version of Fedora manually instead of relying on <application>FedUp</application>. This involves booting the installer as if you were performing a clean installation, letting it detect your existing Fedora system, and overwriting the root partition while preserving data on other partitions and volumes. The same process can also be used to reinstall the system, if you need to. For detailed information, see <xref linkend="sect-upgrading-fedora-manual-reinstall" />. + </para> + </listitem> + </varlistentry> + </variablelist> + <warning> + <para> + Always back up your data before performing an upgrade or reinstalling your system, no matter which method you choose. + </para> + </warning> <section id="sect-upgrading-fedora-fedup"> <title>Automatic System Upgrade Using FedUp</title> <para> - text + Unfortunately, we have not written this chapter yet. In the meantime before we fix this, you can follow the instructions at <ulink url="https://fedoraproject.org/wiki/FedUp" />. </para> </section> <section id="sect-upgrading-fedora-manual-reinstall"> <title>Manual System Upgrade or Reinstallation</title> <para> - text + Unfortunately, we have not written this chapter yet, and there is no dedicated documentation about a manual reinstall on the Wiki, either. In the meantime before we fix this, you can try to start the installation normally (from a boot CD/DVD/USB), select manual partitioning in your installer, and reuse existing partitions instead of destroying them and creating new ones. The instructions at <xref linkend="sect-installation-gui-manual-partitioning" /> should in most cases be easy to adapt for this. </para> </section>

9 years, 6 months

1
0
0 / 0

[securityguide] Removed SELinux guide authors from list of authors.

by Bara Ančincová

commit 1af417ac2a1046eeb8679b53aac3bca640ac5b07 Author: Barbora Ancincova <bancinco(a)redhat.com> Date: Mon Dec 8 17:56:53 2014 +0100 Removed SELinux guide authors from list of authors. en-US/Author_Group.xml | 24 ++++++++++++------------ 1 files changed, 12 insertions(+), 12 deletions(-) --- diff --git a/en-US/Author_Group.xml b/en-US/Author_Group.xml index 0407f55..b342c77 100644 --- a/en-US/Author_Group.xml +++ b/en-US/Author_Group.xml @@ -52,7 +52,7 @@ </affiliation> <email>agent86(a)fedoraproject.org</email> </author> - <author> +  +  +  +  +  +  </authorgroup>

9 years, 6 months

1
0
0 / 0

[securityguide] Commented-out SELinux content.

by Bara Ančincová

commit 0a8ee8654101fa822468d52c9d5e03a166a579cc Author: Barbora Ancincova <bancinco(a)redhat.com> Date: Sun Oct 12 19:51:37 2014 +0200 Commented-out SELinux content. en-US/Security_Guide.xml | 6 +++--- en-US/Security_Introduction.xml | 6 ++++-- 2 files changed, 7 insertions(+), 5 deletions(-) --- diff --git a/en-US/Security_Guide.xml b/en-US/Security_Guide.xml index ba9b989..a651133 100644 --- a/en-US/Security_Guide.xml +++ b/en-US/Security_Guide.xml @@ -17,7 +17,7 @@ <title>Yubikey</title> <xi:include href="Yubikey_Neo.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> </chapter> - <chapter> +  +  <xi:include href="Encryption_Standards.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> <xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> </book> diff --git a/en-US/Security_Introduction.xml b/en-US/Security_Introduction.xml index dfcc009..3c8b5eb 100644 --- a/en-US/Security_Introduction.xml +++ b/en-US/Security_Introduction.xml @@ -127,12 +127,14 @@ </section> </section> +  <section id="sect-Security_Guide-Introduction_to_Security-Security_Controls"> <title>Security Controls</title> <para>

9 years, 6 months

1
0
0 / 0

[install-guide/f21-branch] Adding the LVM appendix + removing more TODOs

by pbokoc

commit 83bdc4b0c488d7d3e96798f6a8f6c8afdd6b8f27 Author: Petr Bokoc <pbokoc(a)redhat.com> Date: Mon Dec 8 15:08:13 2014 +0100 Adding the LVM appendix + removing more TODOs en-US/CustomSpoke_FileSystems.xml | 2 +- en-US/CustomSpoke_RecommendedScheme.xml | 2 +- en-US/Disk_Partitions.xml | 2 +- en-US/Installation_Guide.xml | 1 + en-US/Understanding_LVM.xml | 28 ++++++++++++++++++++++++++++ 5 files changed, 32 insertions(+), 3 deletions(-) --- diff --git a/en-US/CustomSpoke_FileSystems.xml b/en-US/CustomSpoke_FileSystems.xml index a9f4424..e28c539 100644 --- a/en-US/CustomSpoke_FileSystems.xml +++ b/en-US/CustomSpoke_FileSystems.xml @@ -23,7 +23,7 @@ </listitem> <listitem> <para> - <guilabel>LVM</guilabel> - Choosing <guilabel>LVM</guilabel> as the <guilabel>Device Type</guilabel> creates an LVM logical volume and a volume group to contain it (unless one already exists, in which case the new volume is assigned to the existing group). LVM can improve performance when using physical disks and allows you to use multiple disks for a single mount point. For information on how to create a logical volume, see <xref linkend="sect-installation-gui-manual-partitioning-lvm" />. <remark>TODO: xref to the LVM appendix</remark> + <guilabel>LVM</guilabel> - Choosing <guilabel>LVM</guilabel> as the <guilabel>Device Type</guilabel> creates an LVM logical volume and a volume group to contain it (unless one already exists, in which case the new volume is assigned to the existing group). LVM can improve performance when using physical disks and allows you to use multiple disks for a single mount point. For information on how to create a logical volume, see <xref linkend="sect-installation-gui-manual-partitioning-lvm" />. Also see <xref linkend="appe-lvm-overview" /> for some additional information about LVM in general. </para> </listitem> <listitem> diff --git a/en-US/CustomSpoke_RecommendedScheme.xml b/en-US/CustomSpoke_RecommendedScheme.xml index b103fed..ca5796c 100644 --- a/en-US/CustomSpoke_RecommendedScheme.xml +++ b/en-US/CustomSpoke_RecommendedScheme.xml @@ -199,7 +199,7 @@ </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> + Only assign storage capacity to those partitions you require immediately. You may allocate free space at any time, to meet needs as they occur. </para> </note> <para> diff --git a/en-US/Disk_Partitions.xml b/en-US/Disk_Partitions.xml index e5250af..b917bd3 100644 --- a/en-US/Disk_Partitions.xml +++ b/en-US/Disk_Partitions.xml @@ -1,5 +1,5 @@ <?xml version='1.0' encoding='utf-8' ?> -<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +<!DOCTYPE appendix 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; ]> diff --git a/en-US/Installation_Guide.xml b/en-US/Installation_Guide.xml index 0c4b2d4..d92c565 100644 --- a/en-US/Installation_Guide.xml +++ b/en-US/Installation_Guide.xml @@ -47,6 +47,7 @@ </partintro> <xi:include href="Kickstart_Syntax_Reference.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> <xi:include href="Disk_Partitions.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="Understanding_LVM.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> </part> <xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> diff --git a/en-US/Understanding_LVM.xml b/en-US/Understanding_LVM.xml new file mode 100644 index 0000000..16bcfd0 --- /dev/null +++ b/en-US/Understanding_LVM.xml @@ -0,0 +1,28 @@ +<?xml version='1.0' encoding='utf-8' ?> +<!DOCTYPE appendix 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; +]> +<appendix id="appe-lvm-overview"> + <title>Understanding LVM</title> + <para> + LVM (Logical Volume Management) partitions provide a number of advantages over standard partitions. LVM partitions are formatted as <firstterm>physical volumes</firstterm>. One or more physical volumes are combined to form a <firstterm>volume group</firstterm>. Each volume group's total storage is then divided into one or more <firstterm>logical volumes</firstterm>. The logical volumes function much like standard partitions. They have a file system type, such as <systemitem class="filesystem">ext4</systemitem>, and a mount point. + </para> + <important> + <para> + The boot loader cannot read LVM volumes. You must make a standard, non-LVM disk partition for your <filename class="partition">/boot</filename> partition. + </para> + <para> + By default, the installation process always creates the <filename class="partition">/</filename> and <filename class="partition">swap</filename> partitions within LVM volumes, with a separate <filename>/boot</filename> on a standard partition. See <xref linkend="sect-installation-gui-manual-partitioning-recommended" /> for details. + </para> + </important> + <para> + To understand LVM better, imagine the physical volume as a pile of <firstterm>blocks</firstterm>. A block is a storage unit used to store data. Several piles of blocks can be combined to make a much larger pile, just as physical volumes are combined to make a volume group. The resulting pile can be subdivided into several smaller piles of arbitrary size, just as a volume group is allocated to several logical volumes. + </para> + <para> + An administrator may grow or shrink logical volumes without destroying data, unlike standard disk partitions. If the physical volumes in a volume group are on separate drives or RAID arrays then administrators may also spread a logical volume across the storage devices. + </para> + <para> + You may lose data if you shrink a logical volume to a smaller capacity than the data on the volume requires. To ensure maximum flexibility, create logical volumes to meet your current needs, and leave excess storage capacity unallocated. You may safely grow logical volumes to use unallocated space, as your needs dictate. + </para> +</appendix> \ No newline at end of file

9 years, 6 months

1
0
0 / 0

[install-guide/f21-branch] Small fixes in Preparing for Installation

by pbokoc

commit a8b62932f187eeb4c53b83bb642d38f84f6c101d Author: Petr Bokoc <pbokoc(a)redhat.com> Date: Mon Dec 8 15:07:57 2014 +0100 Small fixes in Preparing for Installation en-US/Preparing_for_Installation.xml | 55 ++++++++------------------------- 1 files changed, 14 insertions(+), 41 deletions(-) --- diff --git a/en-US/Preparing_for_Installation.xml b/en-US/Preparing_for_Installation.xml index d3d9b51..dce6a1a 100644 --- a/en-US/Preparing_for_Installation.xml +++ b/en-US/Preparing_for_Installation.xml @@ -9,13 +9,6 @@ This chapter describes the steps you need take before you begin the installation. Not every step must be strictly followed - for example, if you plan to use the default installation settings, you do not need to gather system information such as disk device labels/UUIDs or network information such as the system's IP address. However, you should still go through this chapter, as it also describes the available types of installation media and how to prepare boot media and installation sources. </para> - <section id="sect-preparing-supported-hardware"> - <title>Supported Hardware</title> - <para> - TODO - </para> - </section> - <section id="sect-preparing-upgrade-or-install"> <title>Upgrade or Install?</title> <para> @@ -46,23 +39,16 @@ </warning> </section> - <section id="sect-preparing-system-information"> - <title>Gathering System Information</title> - <para> - TODO - </para> - </section> - <section id="sect-preparing-obtaining-images"> <title>Downloading Boot and Installation Images</title> <para> - The Fedora Project offers different flavors for tailored for some specific use cases. Choose the Fedora flavor best for you, or you can build your own by customizing after the installation, or by using a kickstart file as described in <xref linkend="sect-kickstart-file-create" />. + The Fedora Project offers different flavors for tailored for some specific use cases. Choose the Fedora flavor best for you, or you can build your own by customizing after the installation, or by using a kickstart file as described in <xref linkend="sect-kickstart-file-create" />. </para> <para> - Read more about Fedora Workstation, Fedora Cloud, Fedora Server and the available media types in <xref linkend="chap-downloading-fedora" />. + Read more about Fedora Workstation, Fedora Cloud, Fedora Server and the available media types in <xref linkend="chap-downloading-fedora" />. </para> <para> - You can also choose a Fedora <literal>Spin</literal> featuring favorite alternative desktops or tools for specialized tasks at <ulink url="http://spins.fedoraproject.org" /> + You can also choose a Fedora <literal>Spin</literal> featuring favorite alternative desktops or tools for specialized tasks at <ulink url="http://spins.fedoraproject.org" /> </para> </section> @@ -171,15 +157,7 @@ Mode LastWriteTime Length Name </itemizedlist> </step> </procedure> - - - - - - - - - </section> + </section> <section id="sect-preparing-installation-methods"> <title>Choosing an Installation Method</title> @@ -205,13 +183,13 @@ Mode LastWriteTime Length Name 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> - 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> + <warning> + <title>Be sure you choose the right device!</title> + <para> + 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> <title>Creating USB Media on Windows</title> <step> @@ -229,7 +207,7 @@ Mode LastWriteTime Length Name Choose the USB device you wish to convert to installation media. </para> </step> - <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 ready to use. </para> @@ -292,16 +270,11 @@ Mode LastWriteTime Length Name Use the <command>dd</command> utility to write the image. <emphasis>Make sure you have the right drive!</emphasis> </para> <screen> - <prompt># </prompt>dd if=<replaceable>/path/to/Fedora-Live-Security-x86_64-21.iso</replaceable> of=<replaceable>/dev/sdd</replaceable> +<prompt>#</prompt> <command>dd if=<replaceable>/path/to/Fedora-Live-Security-x86_64-21.iso</replaceable> of=<replaceable>/dev/sdd</replaceable></command> </screen> </step> </procedure> - - - - - - </section> + </section> <section id="sect-preparing-installation-sources"> <title>Preparing Installation Sources</title>

9 years, 6 months

1
0
0 / 0

[install-guide/f21-branch] Adding the disk partitioning appendix + removing most TODOs

by pbokoc

commit d83856fc540893361d7a6978ea328f9c2c732651 Author: Petr Bokoc <pbokoc(a)redhat.com> Date: Mon Dec 8 14:58:47 2014 +0100 Adding the disk partitioning appendix + removing most TODOs en-US/Boot_Options.xml | 4 +- en-US/CustomSpoke_AddLVM.xml | 2 +- en-US/CustomSpoke_AddPhysical.xml | 2 +- en-US/CustomSpoke_FileSystems.xml | 2 +- en-US/Disk_Partitions.xml | 923 ++++++++++++++++++++ en-US/Installation_Guide.xml | 1 + en-US/Kickstart_Syntax_Reference.xml | 2 +- en-US/StorageSpoke.xml | 2 +- en-US/images/partitions/compression.png | Bin 0 -> 2460 bytes en-US/images/partitions/dos-single-partition.png | Bin 0 -> 1194 bytes en-US/images/partitions/dstrct-reprt.png | Bin 0 -> 3257 bytes en-US/images/partitions/extended-partitions.png | Bin 0 -> 3752 bytes en-US/images/partitions/formatted-drive.png | Bin 0 -> 292 bytes en-US/images/partitions/nondestruct-fin.png | Bin 0 -> 3059 bytes en-US/images/partitions/other-formatted-drive.png | Bin 0 -> 689 bytes en-US/images/partitions/part-resize.png | Bin 0 -> 2557 bytes en-US/images/partitions/unpart-space.png | Bin 0 -> 3052 bytes en-US/images/partitions/unused-drive.png | Bin 0 -> 190 bytes en-US/images/partitions/unused-partition.png | Bin 0 -> 3302 bytes .../images/partitions/unused-partitioned-drive.png | Bin 0 -> 775 bytes en-US/images/partitions/used-formatted-drive.png | Bin 0 -> 421 bytes 21 files changed, 931 insertions(+), 7 deletions(-) --- diff --git a/en-US/Boot_Options.xml b/en-US/Boot_Options.xml index cedb998..e3f3070 100644 --- a/en-US/Boot_Options.xml +++ b/en-US/Boot_Options.xml @@ -760,9 +760,9 @@ <para> 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. </para> -  + </para> </listitem> </varlistentry> <varlistentry> diff --git a/en-US/CustomSpoke_AddLVM.xml b/en-US/CustomSpoke_AddLVM.xml index 5b2cb6c..e383b9a 100644 --- a/en-US/CustomSpoke_AddLVM.xml +++ b/en-US/CustomSpoke_AddLVM.xml @@ -9,7 +9,7 @@ <firstterm>Logical Volume Management</firstterm> (LVM) presents a simple logical view of underlying physical storage space, such as hard drives or LUNs. Partitions on physical storage are represented as <firstterm>physical volumes</firstterm> that can be grouped together into <firstterm>volume groups</firstterm>. Each volume group can be divided into multiple <firstterm>logical volumes</firstterm>, each of which is analogous to a standard disk partition. Therefore, LVM logical volumes function as partitions which can span multiple physical disks. </para> <para> - <remark>TODO: xref to the LVM appendix</remark> + <remark>See  for additional information about the concepts behind physical partitions.</remark> </para> <warning> <para> diff --git a/en-US/CustomSpoke_AddPhysical.xml b/en-US/CustomSpoke_AddPhysical.xml index 923046a..8f44062 100644 --- a/en-US/CustomSpoke_AddPhysical.xml +++ b/en-US/CustomSpoke_AddPhysical.xml @@ -9,7 +9,7 @@ <firstterm>Standard partitions</firstterm> are the most common type of partition, with the widest support across operating systems. For example, Microsoft Windows uses exclusively physical partitions and can not natively work with LVM or Btrfs. Most &PRODUCT; partitioning setups will also require at least one standard partition for the <filename class="directory">/boot</filename> directory, and possibly also another standard partition with the BIOS Boot or EFI System file system to store the boot loader. </para> <para> - <remark>TODO: xref to the partitioning appendix</remark> + See <xref linkend="appe-disk-partitions-overview" /> for additional information about the concepts behind physical partitions. </para> <figure> <title>Create Standard Partition</title> diff --git a/en-US/CustomSpoke_FileSystems.xml b/en-US/CustomSpoke_FileSystems.xml index bc49335..a9f4424 100644 --- a/en-US/CustomSpoke_FileSystems.xml +++ b/en-US/CustomSpoke_FileSystems.xml @@ -18,7 +18,7 @@ <title>Device Types</title> <listitem> <para> - <guilabel>Standard Partition</guilabel> - A standard partition can contain a file system or swap space. Standard partitions are most commonly used for <filename class="directory">/boot</filename> and the BIOS Boot and EFI System partitions. LVM logical volumes or Btrfs subvolumes are recommended for most other uses. <remark>TODO: xref to the disk partitioning appendix</remark> + <guilabel>Standard Partition</guilabel> - A standard partition can contain a file system or swap space. Standard partitions are most commonly used for <filename class="directory">/boot</filename> and the BIOS Boot and EFI System partitions. LVM logical volumes or Btrfs subvolumes are recommended for most other uses. See <xref linkend="appe-disk-partitions-overview" /> for additional information about the concepts behind physical partitions. </para> </listitem> <listitem> diff --git a/en-US/Disk_Partitions.xml b/en-US/Disk_Partitions.xml new file mode 100644 index 0000000..e5250af --- /dev/null +++ b/en-US/Disk_Partitions.xml @@ -0,0 +1,923 @@ +<?xml version='1.0' encoding='utf-8' ?> +<!DOCTYPE chapter 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; +]> +<appendix id="appe-disk-partitions-overview"> + <title>An Introduction to Disk Partitions</title> + <note> + <para> + This appendix is not necessarily applicable to architectures other than AMD64 and Intel 64. However, the general concepts mentioned here may apply. + </para> + </note> + <para> + This section discusses basic disk concepts, disk repartitioning strategies, the partition naming scheme used by Linux systems, and related topics. + </para> + <para> + If you are comfortable with disk partitions, you can skip ahead to <xref linkend="sect-disk-partitions-making-room" /> for more information on the process of freeing up disk space to prepare for a &PRODUCT; installation. + </para> + + <section id="sect-disk-partitions-basic-concepts"> + <title>Hard Disk Basic Concepts</title> + <para> + Hard disks perform a very simple function - they store data and reliably retrieve it on command. + </para> + <para> + When discussing issues such as disk partitioning, it is important to have a understanding of the underlying hardware; however, since the theory is very complicated and expansive, only the basic concepts will be explained here. This appendix uses a set of simplified diagrams of a disk drive to help explain what is the process and theory behind partitions. + </para> + <para> + <xref linkend="figu-partitions-unused-drive" />, shows a brand-new, unused disk drive. + </para> + <figure id="figu-partitions-unused-drive"> + <title>An Unused Disk Drive</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/partitions/unused-drive.png" format="PNG" /> + </imageobject> + <textobject> + <para> + Image of an unused disk drive. + </para> + </textobject> + </mediaobject> + </figure> + + <section id="sect-disk-partitions-file-systems"> + <title>File Systems</title> + <para> + To store data on a disk drive, it is necessary to <firstterm>format</firstterm> the disk drive first. Formatting (usually known as "making a <firstterm>file system</firstterm>") writes information to the drive, creating order out of the empty space in an unformatted drive. + </para> + <figure id="figu-partitions-formatted-drive"> + <title>Disk Drive with a File System</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/partitions/formatted-drive.png" format="PNG" /> + </imageobject> + <textobject> + <para> + Image of a formatted disk drive. + </para> + </textobject> + </mediaobject> + </figure> + <para> + As <xref linkend="figu-partitions-formatted-drive" />, implies, the order imposed by a file system involves some trade-offs: + </para> + <itemizedlist> + <listitem> + <para> + A small percentage of the driver's available space is used to store file system-related data and can be considered as overhead. + </para> + </listitem> + <listitem> + <para> + A file system splits the remaining space into small, consistently-sized segments. For Linux, these segments are known as <firstterm>blocks</firstterm>. + <footnote> + <para> + Blocks really <emphasis>are</emphasis> consistently sized, unlike our illustrations. Keep in mind, also, that an average disk drive contains thousands of blocks. The picture is simplified for the purposes of this discussion. + </para> + </footnote> + </para> + </listitem> + </itemizedlist> + <para> + Note that there is no single, universal file system. As <xref linkend="figu-partitions-different-file-system" />, shows, a disk drive may have one of many different file systems written on it. Different file systems tend to be incompatible; that is, an operating system that supports one file system (or a handful of related file system types) may not support another. However, &PRODUCT; supports a wide variety of file systems (including many commonly used by other operating systems such as Microsoft Windows), making data interchange between different file systems easy. + </para> + <figure id="figu-partitions-different-file-system"> + <title>Disk Drive with a Different File System</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/partitions/other-formatted-drive.png" format="PNG" /> + </imageobject> + <textobject> + <para> + Image of a disk drive with a different file system. + </para> + </textobject> + </mediaobject> + </figure> + <para> + Writing a file system to disk is only the first step. The goal of this process is to actually <emphasis>store</emphasis> and <emphasis>retrieve</emphasis> data. The figure below shows a drive disk after some data have been written to it: + </para> + <figure id="figu-partitions-drive-with-data"> + <title>Disk Drive with Data Written to It</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/partitions/used-formatted-drive.png" format="PNG" /> + </imageobject> + <textobject> + <para> + Image of a disk drive with data written to it. + </para> + </textobject> + </mediaobject> + </figure> + <para> + As <xref linkend="figu-partitions-drive-with-data" />, shows, some of the previously-empty blocks are now holding data. However, by just looking at this picture, we cannot determine exactly how many files reside on this drive. There may only be one file or many, as all files use at least one block and some files use multiple blocks. Another important point to note is that the used blocks do not have to form a contiguous region; used and unused blocks may be interspersed. This is known as <firstterm>fragmentation</firstterm>. Fragmentation can play a part when attempting to resize an existing partition. + </para> + <para> + As with most computer-related technologies, disk drives changed over time after their introduction. In particular, they got bigger. Not larger in physical size, but bigger in their capacity to store information. And, this additional capacity drove a fundamental change in the way disk drives were used. + </para> + </section> + + <section id="sect-disk-partitions-basics"> + <title>Partitions: Turning One Drive Into Many</title> + <para> + Disk drives can be divided into <firstterm>partitions</firstterm>. Each partition can be accessed as if it was a separate disk. This is done through the addition of a <firstterm>partition table</firstterm>. + </para> + <para> + There are several reasons for allocating disk space into separate disk partitions, for example: + </para> + <itemizedlist> + <listitem> + <para> + Logical separation of the operating system data from the user data + </para> + </listitem> + <listitem> + <para> + Ability to use different file systems + </para> + </listitem> + <listitem> + <para> + Ability to run multiple operating systems on one machine + </para> + </listitem> + </itemizedlist> + <para> + There are currently two partitioning layout standards for physical hard disks: Master Boot Record (<acronym>MBR</acronym>) and GUID Partition Table (<acronym>GPT</acronym>). <acronym>MBR</acronym> is an older method of disk partitioning used with BIOS-based computers. <acronym>GPT</acronym> is a newer partitioning layout that is a part of the Unified Extensible Firmware Interface (<acronym>UEFI</acronym>). This section and <xref linkend="sect-disk-partitions-extended" /> mainly describe the <firstterm>Master Boot Record</firstterm> (<acronym>MBR</acronym>) disk partitioning scheme. For information about the <firstterm>GUID Partition Table</firstterm> (<acronym>GPT</acronym>) partitioning layout, see <xref linkend="sect-disk-partitioning-guid-partition-table" />. + </para> + <note> + <para> + While the diagrams in this chapter show the partition table as being separate from the actual disk drive, this is not entirely accurate. In reality, the partition table is stored at the very start of the disk, before any file system or user data. But for clarity, they are separate in our diagrams. + </para> + </note> + <figure id="figu-partitions-partition-table"> + <title>Disk Drive with Partition Table</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/partitions/unused-partitioned-drive.png" format="PNG" /> + </imageobject> + <textobject> + <para> + Image of an unused disk drive with a partition table. + </para> + </textobject> + </mediaobject> + </figure> + <para> + As <xref linkend="figu-partitions-partition-table" /> shows, the partition table is divided into four sections or four <firstterm>primary</firstterm> partitions. A primary partition is a partition on a hard drive that can contain only one logical drive (or section). Each section can hold the information necessary to define a single partition, meaning that the partition table can define no more than four partitions. + </para> + <para> + Each partition table entry contains several important characteristics of the partition: + </para> + <itemizedlist> + <listitem> + <para> + The points on the disk where the partition starts and ends + </para> + </listitem> + <listitem> + <para> + Whether the partition is "active" + </para> + </listitem> + <listitem> + <para> + The partition's type + </para> + </listitem> + </itemizedlist> + <para> + The starting and ending points define the partition's size and location on the disk. The "active" flag is used by some operating systems' boot loaders. In other words, the operating system in the partition that is marked "active" is booted. + </para> + <para> + The type is a number that identifies the partition's anticipated usage. Some operating systems use the partition type to denote a specific file system type, to flag the partition as being associated with a particular operating system, to indicate that the partition contains a bootable operating system, or some combination of the three. + </para> + <para> + See <xref linkend="figu-partitions-single-part" /> for an example of a disk drive with single partition. + </para> + <figure id="figu-partitions-single-part"> + <title>Disk Drive With Single Partition</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/partitions/dos-single-partition.png" format="PNG" /> + </imageobject> + <textobject> + <para> + Image of a disk drive with a single partition. + </para> + </textobject> + </mediaobject> + </figure> + <para> + The single partition in this example is labeled as <literal>DOS</literal>. This label shows the <emphasis>partition type</emphasis>, with <literal>DOS</literal> being one of the most common ones. The table below shows a list of some of the commonly used partition types and hexadecimal numbers used to represent them. + </para> + <table id="tabl-partition-types"> + <title>Partition Types</title> + <tgroup cols="4"> + <colspec colnum="1" colwidth="2*"></colspec> + <colspec colnum="2" colwidth="1*"></colspec> + <colspec colnum="3" colwidth="2*"></colspec> + <colspec colnum="4" colwidth="1*"></colspec> + <thead> + <row> + <entry> + Partition Type + </entry> + <entry> + Value + </entry> + <entry> + Partition Type + </entry> + <entry> + Value + </entry> + </row> + </thead> + <tbody> + <row> + <entry> + Empty + </entry> + <entry> + 00 + </entry> + <entry> + Novell Netware 386 + </entry> + <entry> + 65 + </entry> + </row> + <row> + <entry> + DOS 12-bit FAT + </entry> + <entry> + 01 + </entry> + <entry> + PIC/IX + </entry> + <entry> + 75 + </entry> + </row> + <row> + <entry> + XENIX root + </entry> + <entry> + 02 + </entry> + <entry> + Old MINIX + </entry> + <entry> + 80 + </entry> + </row> + <row> + <entry> + XENIX usr + </entry> + <entry> + 03 + </entry> + <entry> + Linux/MINUX + </entry> + <entry> + 81 + </entry> + </row> + <row> + <entry> + DOS 16-bit <=32M + </entry> + <entry> + 04 + </entry> + <entry> + Linux swap + </entry> + <entry> + 82 + </entry> + </row> + <row> + <entry> + Extended + </entry> + <entry> + 05 + </entry> + <entry> + Linux native + </entry> + <entry> + 83 + </entry> + </row> + <row> + <entry> + DOS 16-bit >=32 + </entry> + <entry> + 06 + </entry> + <entry> + Linux extended + </entry> + <entry> + 85 + </entry> + </row> + <row> + <entry> + OS/2 HPFS + </entry> + <entry> + 07 + </entry> + <entry> + Amoeba + </entry> + <entry> + 93 + </entry> + </row> + <row> + <entry> + AIX + </entry> + <entry> + 08 + </entry> + <entry> + Amoeba BBT + </entry> + <entry> + 94 + </entry> + </row> + <row> + <entry> + AIX bootable + </entry> + <entry> + 09 + </entry> + <entry> + BSD/386 + </entry> + <entry> + a5 + </entry> + </row> + <row> + <entry> + OS/2 Boot Manager + </entry> + <entry> + 0a + </entry> + <entry> + OpenBSD + </entry> + <entry> + a6 + </entry> + </row> + <row> + <entry> + Win95 FAT32 + </entry> + <entry> + 0b + </entry> + <entry> + NEXTSTEP + </entry> + <entry> + a7 + </entry> + </row> + <row> + <entry> + Win95 FAT32 (LBA) + </entry> + <entry> + 0c + </entry> + <entry> + BSDI fs + </entry> + <entry> + b7 + </entry> + </row> + <row> + <entry> + Win95 FAT16 (LBA) + </entry> + <entry> + 0e + </entry> + <entry> + BSDI swap + </entry> + <entry> + b8 + </entry> + </row> + <row> + <entry> + Win95 Extended (LBA) + </entry> + <entry> + 0f + </entry> + <entry> + Syrinx + </entry> + <entry> + c7 + </entry> + </row> + <row> + <entry> + Venix 80286 + </entry> + <entry> + 40 + </entry> + <entry> + CP/M + </entry> + <entry> + db + </entry> + </row> + <row> + <entry> + Novell + </entry> + <entry> + 51 + </entry> + <entry> + DOS access + </entry> + <entry> + e1 + </entry> + </row> + <row> + <entry> + PReP Boot + </entry> + <entry> + 41 + </entry> + <entry> + DOS R/O + </entry> + <entry> + e3 + </entry> + </row> + <row> + <entry> + GNU HURD + </entry> + <entry> + 63 + </entry> + <entry> + DOS secondary + </entry> + <entry> + f2 + </entry> + </row> + <row> + <entry> + Novell Netware 286 + </entry> + <entry> + 64 + </entry> + <entry> + BBT + </entry> + <entry> + ff + </entry> + </row> + </tbody> + </tgroup> + </table> + </section> + + <section id="sect-disk-partitions-extended"> + <title>Partitions Within Partitions - An Overview of Extended Partitions</title> + <para> + In case four partitions are insufficient for your needs, you can use <firstterm>extended partitions</firstterm> to create up additional partitions. You do this by setting the type of a partition to "Extended". + </para> + <para> + An extended partition is like a disk drive in its own right - it has its own partition table which points to one or more partitions (now called <firstterm>logical partitions</firstterm>, as opposed to the four <firstterm>primary partitions</firstterm>) contained entirely within the extended partition itself. <xref linkend="figu-partitions-extended" />, shows a disk drive with one primary partition and one extended partition containing two logical partitions (along with some unpartitioned free space). + </para> + <figure id="figu-partitions-extended"> + <title>Disk Drive With Extended Partition</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/partitions/extended-partitions.png" format="PNG" /> + </imageobject> + <textobject> + <para> + Image of a disk drive with an extended partition. + </para> + </textobject> + </mediaobject> + </figure> + <para> + As this figure implies, there is a difference between primary and logical partitions - there can only be four primary partitions, but there is no fixed limit to the number of logical partitions that can exist. However, due to the way in which partitions are accessed in Linux, no more than 12 logical partitions should be defined on a single disk drive. + </para> + </section> + + <section id="sect-disk-partitioning-guid-partition-table"> + <title>GUID Partition Table (GPT)</title> + <para> + GUID Partition Table (<acronym>GPT</acronym>) is a newer partitioning scheme based on using Globally Unique Identifiers (<acronym>GUID</acronym>). <acronym>GPT</acronym> was developed to cope with limitations of the <acronym>MBR</acronym> partition table, especially with the limited maximum addressable storage space of a disk. Unlike <acronym>MBR</acronym>, which is unable to address storage space larger than 2.2 terabytes, <acronym>GPT</acronym> can be used with hard disks larger than this; the maximum addressable disk size is 2.2 zettabytes. In addition, <acronym>GPT</acronym> by default supports creating up to 128 primary partitions. This number could be extended by allocating more space to the partition table. + </para> + <para> + <acronym>GPT</acronym> disks use logical block addressing (LBA) and the partition layout is as follows: + </para> + <itemizedlist> + <listitem> + <para> + To preserve backward compatibility with MBR disks, the first sector (<acronym>LBA</acronym> 0) of <acronym>GPT</acronym> is reserved for <acronym>MBR</acronym> data and it is called <quote>protective MBR</quote>. + </para> + </listitem> + <listitem> + <para> + The <firstterm>primary <acronym>GPT</acronym> header</firstterm> begins on the second logical block (<acronym>LBA</acronym> 1) of the device. The header contains the disk GUID, the location of the primary partition table, the location of the secondary GPT header, and CRC32 checksums of itself and the primary partition table. It also specifies the number of partition entries of the table. + </para> + </listitem> + <listitem> + <para> + The <firstterm>primary <acronym>GPT</acronym> table</firstterm> includes, by default, 128 partition entries, each with an entry size 128 bytes, its partition type GUID and unique partition GUID. + </para> + </listitem> + <listitem> + <para> + The <firstterm>secondary <acronym>GPT</acronym> table</firstterm> is identical to the primary <acronym>GPT</acronym> table. It is used mainly as a backup table for recovery in case the primary partition table is corrupted. + </para> + </listitem> + <listitem> + <para> + The <firstterm>secondary <acronym>GPT</acronym> header</firstterm> is located on the last logical sector of the disk and it can be used to recover <acronym>GPT</acronym> information in case the primary header is corrupted. It contains the disk GUID, the location of the secondary partition table and the primary <acronym>GPT</acronym> header, CRC32 checksums of itself and the secondary partition table, and the number of possible partition entries. + </para> + </listitem> + </itemizedlist> + <important> + <para> + 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 <application>Anaconda</application>. If the disk already contains a BIOS boot partition, it can be reused. + </para> + </important> + </section> + + </section> + + <section id="sect-disk-partitions-making-room"> + <title>Strategies for Disk Repartitioning</title> + <para> + There are several different ways that a disk can be repartitioned. This section discusses the following possible approaches: + </para> + <itemizedlist> + <listitem> + <para> + Unpartitioned free space is available + </para> + </listitem> + <listitem> + <para> + An unused partition is available + </para> + </listitem> + <listitem> + <para> + Free space in an actively used partition is available + </para> + </listitem> + </itemizedlist> + <para> + Note that this section discusses the aforementioned concepts only theoretically and it does not include any procedures showing how to perform disk repartitioning step-by-step. Such detailed information are beyond the scope of this document. + </para> + <note> + <para> + Keep in mind that the following illustrations are simplified in the interest of clarity and do not reflect the exact partition layout that you encounter when actually installing &PRODUCT;. + </para> + </note> + + <section id="sect-disk-partitions-using-free-space"> + <title>Using Unpartitioned Free Space</title> + <para> + In this situation, the partitions already defined do not span the entire hard disk, leaving unallocated space that is not part of any defined partition. <xref linkend="figu-partitions-unused-space" />, shows what this might look like. + </para> + <figure id="figu-partitions-unused-space"> + <title>Disk Drive with Unpartitioned Free Space</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/partitions/unpart-space.png" format="PNG" width="444" /> + </imageobject> + <textobject> + <para> + Image of a disk drive with unpartitioned free space, where <wordasword>1</wordasword> represents an undefined partition with unallocated space and <wordasword>2</wordasword> represents a defined partition with allocated space. + </para> + </textobject> + </mediaobject> + </figure> + <para> + In the above example, <wordasword>1</wordasword> represents an undefined partition with unallocated space and <wordasword>2</wordasword> represents a defined partition with allocated space. + </para> + <para> + An unused hard disk also falls into this category. The only difference is that <emphasis>all</emphasis> the space is not part of any defined partition. + </para> + <para> + In any case, you can create the necessary partitions from the unused space. Unfortunately, this scenario, although very simple, is not very likely (unless you have just purchased a new disk just for &PRODUCT;). Most pre-installed operating systems are configured to take up all available space on a disk drive (see <xref linkend="sect-disk-partitions-active-partition" />). + </para> + </section> + + <section id="sect-disk-partitions-unused-partition"> + <title>Using Space from an Unused Partition</title> + <para> + In this case, maybe you have one or more partitions that you do not use any longer. <xref linkend="figu-partitions-unused-partition" />, illustrates such a situation. + </para> + <figure id="figu-partitions-unused-partition"> + <title>Disk Drive with an Unused Partition</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/partitions/unused-partition.png" format="PNG" width="444" /> + </imageobject> + <textobject> + <para> + Image of a disk drive with an unused partition, where <wordasword>1</wordasword> represents an unused partition and <wordasword>2</wordasword> represents reallocating an unused partition for Linux. + </para> + </textobject> + </mediaobject> + </figure> + <para> + In the above example, <wordasword>1</wordasword> represents an unused partition and <wordasword>2</wordasword> represents reallocating an unused partition for Linux. + </para> + <para> + In this situation, you can use the space allocated to the unused partition. You first must delete the partition and then create the appropriate Linux partition(s) in its place. You can delete the unused partition and manually create new partitions during the installation process. + </para> + </section> + + <section id="sect-disk-partitions-active-partition"> + <title>Using Free Space from an Active Partition</title> + <para> + This is the most common situation. It is also, unfortunately, the hardest to handle. The main problem is that, even if you have enough free space, it is presently allocated to a partition that is already in use. If you purchased a computer with pre-installed software, the hard disk most likely has one massive partition holding the operating system and data. + </para> + <para> + Aside from adding a new hard drive to your system, you have two choices: + </para> + <variablelist> + <varlistentry> + <term><emphasis>Destructive Repartitioning</emphasis></term> + <listitem> + <para> + In this case, the single large partition is deleted and several smaller ones are created instead. Any data held in the original partition is destroyed. This means that making a complete backup is necessary. It is highly recommended to make two backups, use verification (if available in your backup software), and try to read data from the backup <emphasis>before</emphasis> deleting the partition. + </para> + <warning> + <para> + If an operating system was installed on that partition, it must be reinstalled if you want to use that system as well. Be aware that some computers sold with pre-installed operating systems may not include the installation media to reinstall the original operating system. You should check whether this applies to your system is <emphasis>before</emphasis> you destroy your original partition and its operating system installation. + </para> + </warning> + <para> + After creating a smaller partition for your existing operating system, you can reinstall software, restore your data, and start the installation. <xref linkend="figu-partitions-destructive-repartitioning" /> shows this being done. + </para> + <figure id="figu-partitions-destructive-repartitioning"> + <title>Disk Drive Being Destructively Repartitioned</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/partitions/dstrct-reprt.png" format="PNG" width="444" /> + </imageobject> + <textobject> + <para> + Image of a disk drive being destructively repartitioned, where <wordasword>1</wordasword> represents before and <wordasword>2</wordasword> represents after. + </para> + </textobject> + </mediaobject> + </figure> + <para> + In the above example, <wordasword>1</wordasword> represents before and <wordasword>2</wordasword> represents after. + </para> + <warning> + <para> + Any data previously present in the original partition is lost. + </para> + </warning> + </listitem> + </varlistentry> + <varlistentry> + <term><emphasis>Non-Destructive Repartitioning</emphasis></term> + <listitem> + <para> + With non-destructive repartitioning you execute a program that makes a big partition smaller without losing any of the files stored in that partition. This method is usually reliable, but can be very time-consuming on large drives. + </para> + <para> + While the process of non-destructive repartitioning is rather straightforward, there are three steps involved: + </para> + <orderedlist> + <listitem> + <para> + Compress and backup existing data + </para> + </listitem> + <listitem> + <para> + Resize the existing partition + </para> + </listitem> + <listitem> + <para> + Create new partition(s) + </para> + </listitem> + </orderedlist> + </listitem> + </varlistentry> + </variablelist> + <para> + Each step is described further in more detail. + </para> + + <section id="sect-disk-partitions-compress-data"> + <title>Compress Existing Data</title> + <para> + As the following figure shows, the first step is to compress the data in your existing partition. The reason for doing this is to rearrange the data such that it maximizes the available free space at the "end" of the partition. + </para> + <figure id="figu-partitions-compress-data"> + <title>Disk Drive Being Compressed</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/partitions/compression.png" format="PNG" width="444" /> + </imageobject> + <textobject> + <para> + Image of a disk drive being compressed, where <wordasword>1</wordasword> represents before and <wordasword>2</wordasword> represents after. + </para> + </textobject> + </mediaobject> + </figure> + <para> + In the above example, <wordasword>1</wordasword> represents before and <wordasword>2</wordasword> represents after. + </para> + <para> + This step is crucial. Without it, the location of the data could prevent the partition from being resized to the extent desired. Note also that, for one reason or another, some data cannot be moved. If this is the case (and it severely restricts the size of your new partition(s)), you may be forced to destructively repartition your disk. + </para> + </section> + + <section id="sect-disk-partitions-resize-existing"> + <title>Resize the Existing Partition</title> + <para> + <xref linkend="figu-partitions-resize-existing" /> shows the actual resizing process. While the actual result of the resizing operation varies depending on the software used, in most cases the newly freed space is used to create an unformatted partition of the same type as the original partition. + </para> + <figure id="figu-partitions-resize-existing"> + <title>Disk Drive with Partition Resized</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/partitions/part-resize.png" format="PNG" width="444" /> + </imageobject> + <textobject> + <para> + Image of a disk drive with a resized partition, where <wordasword>1</wordasword> represents before and <wordasword>2</wordasword> represents after. + </para> + </textobject> + </mediaobject> + </figure> + <para> + In the above example, <wordasword>1</wordasword> represents before and <wordasword>2</wordasword> represents after. + </para> + <para> + It is important to understand what the resizing software you use does with the newly freed space, so that you can take the appropriate steps. In the case illustrated here, it would be best to delete the new DOS partition and create the appropriate Linux partition(s). + </para> + </section> + + <section id="sect-disk-partitions-create-new"> + <title>Create new partition(s)</title> + <para> + As the previous step implied, it may or may not be necessary to create new partitions. However, unless your resizing software is Linux-aware, it is likely that you must delete the partition that was created during the resizing process. <xref linkend="figu-partitions-final-configuration" />, shows this being done. + </para> + <figure id="figu-partitions-final-configuration"> + <title>Disk Drive with Final Partition Configuration</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/partitions/nondestruct-fin.png" format="PNG" width="444" /> + </imageobject> + <textobject> + <para> + Image of a disk drive with final partition configuration, where <wordasword>1</wordasword> represents before and <wordasword>2</wordasword> represents after. + </para> + </textobject> + </mediaobject> + </figure> + <para> + In the above example, <wordasword>1</wordasword> represents before and <wordasword>2</wordasword> represents after. + </para> + </section> + + </section> + + </section> + + <section id="sect-partitioning-naming-schemes-and-mount-points"> + <title>Partition Naming Schemes and Mount Points</title> + <para> + A common source of confusion for users unfamiliar with Linux is the matter of how partitions are used and accessed by the Linux operating system. In DOS/Windows, it is relatively simple: Each partition gets a "drive letter." You then use the correct drive letter to refer to files and directories on its corresponding partition. This is entirely different from how Linux deals with partitions and, for that matter, with disk storage in general. This section describes the main principles of partition naming scheme and the way how partitions are accessed in &PRODUCT;. + </para> + + <section id="sect-disk-partitions-naming-scheme"> + <title>Partition Naming Scheme</title> + <para> + Linux uses a naming scheme that is file-based, with file names in the form of <filename>/dev/<replaceable>xxyN</replaceable></filename>. + </para> + <para> + Device and partition names consist of the following: + </para> + <variablelist> + <varlistentry> + <term><filename>/dev/</filename></term> + <listitem> + <para> + This is the name of the directory in which all device files reside. Because partitions reside on hard disks, and hard disks are devices, the files representing all possible partitions reside in <filename>/dev/</filename>. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term><filename><replaceable>xx</replaceable></filename></term> + <listitem> + <para> + The first two letters of the partition name indicate the type of device on which the partition resides, usually <filename>sd</filename>. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term><filename><replaceable>y</replaceable></filename></term> + <listitem> + <para> + This letter indicates which device the partition is on. For example, <filename>/dev/sda</filename> for the first hard disk, <filename>/dev/sdb</filename> for the second, and so on. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term><filename><replaceable>N</replaceable></filename></term> + <listitem> + <para> + The final number denotes the partition. The first four (primary or extended) partitions are numbered <filename>1</filename> through <filename>4</filename>. Logical partitions start at <filename>5</filename>. So, for example, <filename>/dev/sda3</filename> is the third primary or extended partition on the first hard disk, and <filename>/dev/sdb6</filename> is the second logical partition on the second hard disk. + </para> + </listitem> + </varlistentry> + </variablelist> + <note> + <para> + Even if your system can identify and refer to all types of disk partitions, it might not be able to <emphasis>read</emphasis> the file system and therefore access stored data on every partition type. However, in many cases, it is possible to successfully access data on a partition dedicated to another operating system. + </para> + </note> + </section> + + <section id="sect-disk-partitions-mount-points"> + <title>Disk Partitions and Mount Points</title> + <para> + Each partition is used to form part of the storage necessary to support a single set of files and directories. This is done by associating a partition with a directory through a process known as <firstterm>mounting</firstterm>. Mounting a partition makes its storage available starting at the specified directory (known as a <firstterm>mount point</firstterm>). + </para> + <para> + For example, if partition <filename>/dev/sda5</filename> is mounted on <filename>/usr/</filename>, that would mean that all files and directories under <filename>/usr/</filename> physically reside on <filename>/dev/sda5</filename>. So the file <filename>/usr/share/doc/FAQ/txt/Linux-FAQ</filename> would be stored on <filename>/dev/sda5</filename>, while the file <filename>/etc/gdm/custom.conf</filename> would not. + </para> + <para> + Continuing the example, it is also possible that one or more directories below <filename>/usr/</filename> would be mount points for other partitions. For instance, a partition (say, <filename>/dev/sda7</filename>) could be mounted on <filename>/usr/local/</filename>, meaning that <filename>/usr/local/man/whatis</filename> would then reside on <filename>/dev/sda7</filename> rather than <filename>/dev/sda5</filename>. + </para> + </section> + + <section id="sect-disk-partitions-how-many"> + <title>How Many Partitions?</title> + <para> + At this point in the process of preparing to install &PRODUCT;, you should give some consideration to the number and size of the partitions to be used by your new operating system. However, there is no one right answer to this question. It depends on your needs and requirements. + </para> + <para> + Unless you have a reason for doing otherwise, you should <emphasis>at least</emphasis> create the following partitions: <filename>swap</filename>, <filename>/boot/</filename>, and <filename>/</filename> (root). + </para> + <para> + See <xref linkend="sect-installation-gui-manual-partitioning-recommended" /> for more information about the recommended partitioning scheme. + </para> + </section> + + </section> + +</appendix> diff --git a/en-US/Installation_Guide.xml b/en-US/Installation_Guide.xml index df7a254..0c4b2d4 100644 --- a/en-US/Installation_Guide.xml +++ b/en-US/Installation_Guide.xml @@ -46,6 +46,7 @@ </para> </partintro> <xi:include href="Kickstart_Syntax_Reference.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="Disk_Partitions.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> </part> <xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> diff --git a/en-US/Kickstart_Syntax_Reference.xml b/en-US/Kickstart_Syntax_Reference.xml index 3b6a943..0e791a2 100644 --- a/en-US/Kickstart_Syntax_Reference.xml +++ b/en-US/Kickstart_Syntax_Reference.xml @@ -1520,7 +1520,7 @@ <term><option>--asprimary</option></term> <listitem> <para> - Forces the partition to be allocated as a <emphasis>primary</emphasis> partition. If the partition cannot be allocated as primary (usually due to too many primary partitions being already allocated), the partitioning process will fail. This option only makes sense when the disk uses a Master Boot Record (MBR); for GUID Partition Table (GPT)-labeled disks this option has no meaning. For information about primary (and extended) partitions, see <remark>TODO: xref to an appendix about partitions or something like that</remark> + Forces the partition to be allocated as a <emphasis>primary</emphasis> partition. If the partition cannot be allocated as primary (usually due to too many primary partitions being already allocated), the partitioning process will fail. This option only makes sense when the disk uses a Master Boot Record (MBR); for GUID Partition Table (GPT)-labeled disks this option has no meaning. For information about primary (and extended) partitions, see <xref linkend="sect-installation-gui-manual-partitioning-recommended" />. </para> </listitem> </varlistentry> diff --git a/en-US/StorageSpoke.xml b/en-US/StorageSpoke.xml index c286e21..5b3ee6c 100644 --- a/en-US/StorageSpoke.xml +++ b/en-US/StorageSpoke.xml @@ -9,7 +9,7 @@ The <guilabel>Installation Destination</guilabel> screen allows you to configure storage options - namely, which disks will be used as the installation target for your &PRODUCT; installation. At least one disk must always be selected for the installation to proceed. </para> <para> - For information about the theory and concepts behind disk partitioning in Linux, see <remark>TODO: xref to the disk partitioning appendix</remark>. + For information about the theory and concepts behind disk partitioning in Linux, see <xref linkend="sect-installation-gui-manual-partitioning-recommended" />. </para> <warning> <para> diff --git a/en-US/images/partitions/compression.png b/en-US/images/partitions/compression.png new file mode 100644 index 0000000..690614a Binary files /dev/null and b/en-US/images/partitions/compression.png differ diff --git a/en-US/images/partitions/dos-single-partition.png b/en-US/images/partitions/dos-single-partition.png new file mode 100644 index 0000000..0220cf8 Binary files /dev/null and b/en-US/images/partitions/dos-single-partition.png differ diff --git a/en-US/images/partitions/dstrct-reprt.png b/en-US/images/partitions/dstrct-reprt.png new file mode 100644 index 0000000..cb6fb5c Binary files /dev/null and b/en-US/images/partitions/dstrct-reprt.png differ diff --git a/en-US/images/partitions/extended-partitions.png b/en-US/images/partitions/extended-partitions.png new file mode 100644 index 0000000..61ec9de Binary files /dev/null and b/en-US/images/partitions/extended-partitions.png differ diff --git a/en-US/images/partitions/formatted-drive.png b/en-US/images/partitions/formatted-drive.png new file mode 100644 index 0000000..52139e0 Binary files /dev/null and b/en-US/images/partitions/formatted-drive.png differ diff --git a/en-US/images/partitions/nondestruct-fin.png b/en-US/images/partitions/nondestruct-fin.png new file mode 100644 index 0000000..c1bc2f4 Binary files /dev/null and b/en-US/images/partitions/nondestruct-fin.png differ diff --git a/en-US/images/partitions/other-formatted-drive.png b/en-US/images/partitions/other-formatted-drive.png new file mode 100644 index 0000000..9675179 Binary files /dev/null and b/en-US/images/partitions/other-formatted-drive.png differ diff --git a/en-US/images/partitions/part-resize.png b/en-US/images/partitions/part-resize.png new file mode 100644 index 0000000..d8debc8 Binary files /dev/null and b/en-US/images/partitions/part-resize.png differ diff --git a/en-US/images/partitions/unpart-space.png b/en-US/images/partitions/unpart-space.png new file mode 100644 index 0000000..7bdebe8 Binary files /dev/null and b/en-US/images/partitions/unpart-space.png differ diff --git a/en-US/images/partitions/unused-drive.png b/en-US/images/partitions/unused-drive.png new file mode 100644 index 0000000..08ccd68 Binary files /dev/null and b/en-US/images/partitions/unused-drive.png differ diff --git a/en-US/images/partitions/unused-partition.png b/en-US/images/partitions/unused-partition.png new file mode 100644 index 0000000..9622aba Binary files /dev/null and b/en-US/images/partitions/unused-partition.png differ diff --git a/en-US/images/partitions/unused-partitioned-drive.png b/en-US/images/partitions/unused-partitioned-drive.png new file mode 100644 index 0000000..8a6925d Binary files /dev/null and b/en-US/images/partitions/unused-partitioned-drive.png differ diff --git a/en-US/images/partitions/used-formatted-drive.png b/en-US/images/partitions/used-formatted-drive.png new file mode 100644 index 0000000..e7ae5c2 Binary files /dev/null and b/en-US/images/partitions/used-formatted-drive.png differ

9 years, 6 months

1
0
0 / 0

[install-guide/f21-branch] Adding a screenshot with VNC boot options

by pbokoc

commit 7ffec4b99f996a8322304ecb7a43c9324c0b6dcc Author: Petr Bokoc <pbokoc(a)redhat.com> Date: Mon Dec 8 14:58:26 2014 +0100 Adding a screenshot with VNC boot options en-US/VNC_Installations.xml | 4 ++-- en-US/images/boot/vnc-options.png | Bin 0 -> 4493 bytes 2 files changed, 2 insertions(+), 2 deletions(-) --- diff --git a/en-US/VNC_Installations.xml b/en-US/VNC_Installations.xml index fb5ff89..dca125a 100644 --- a/en-US/VNC_Installations.xml +++ b/en-US/VNC_Installations.xml @@ -156,11 +156,11 @@ <title>Adding VNC Boot Options</title> <mediaobject> <imageobject> - <imagedata fileref="images/vnc/boot-options.png" format="PNG" /> + <imagedata fileref="images/boot/vnc-options.png" format="PNG" /> </imageobject> <textobject> <para> - Editing boot options to activate VNC  + Editing boot options to activate VNC </para> </textobject> </mediaobject> diff --git a/en-US/images/boot/vnc-options.png b/en-US/images/boot/vnc-options.png new file mode 100644 index 0000000..741f04f Binary files /dev/null and b/en-US/images/boot/vnc-options.png differ

9 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

docs-commits December 2014