[install-guide/f21-branch] Moving info about biosboot/efi on gpt/mbr into Recommended Partitioning Scheme
by pbokoc
commit 66927148fe4abab26820b99ea0e20c6a378f08a6
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Mon Nov 17 17:00:59 2014 +0100
Moving info about biosboot/efi on gpt/mbr into Recommended Partitioning Scheme
en-US/Boot_Options.xml | 2 +-
en-US/CustomSpoke_PartitioningAdvice.xml | 2 +-
en-US/CustomSpoke_RecommendedScheme.xml | 54 +++++++++++++++++++++++++--
en-US/StorageSpoke_BootLoader.xml | 59 ++----------------------------
4 files changed, 55 insertions(+), 62 deletions(-)
---
diff --git a/en-US/Boot_Options.xml b/en-US/Boot_Options.xml
index 5595b27..1b99614 100644
--- a/en-US/Boot_Options.xml
+++ b/en-US/Boot_Options.xml
@@ -761,7 +761,7 @@
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>
<!-- TODO <para>
- See <xref linkend="sect-bootloader-mbr-gpt-x86" /> for more information about GPT and MBR, and <xref linkend="sect-disk-partitioning-guid-partition-table" /> for more general information about GPT, MBR and disk partitioning in general.
+ See <xref linkend="sect-installation-gui-manual-partitioning-recommended" /> for more information about GPT and MBR, and <xref linkend="sect-disk-partitioning-guid-partition-table" /> for more general information about GPT, MBR and disk partitioning in general.
</para> -->
</listitem>
</varlistentry>
diff --git a/en-US/CustomSpoke_PartitioningAdvice.xml b/en-US/CustomSpoke_PartitioningAdvice.xml
index 5c101c7..b453371 100644
--- a/en-US/CustomSpoke_PartitioningAdvice.xml
+++ b/en-US/CustomSpoke_PartitioningAdvice.xml
@@ -61,7 +61,7 @@
</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.
+ 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-manual-partitioning-recommended" /> 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>
diff --git a/en-US/CustomSpoke_RecommendedScheme.xml b/en-US/CustomSpoke_RecommendedScheme.xml
index 1195176..9fcbd27 100644
--- a/en-US/CustomSpoke_RecommendedScheme.xml
+++ b/en-US/CustomSpoke_RecommendedScheme.xml
@@ -80,7 +80,7 @@
<tbody>
<row>
<entry>
- ⩽ 2 GB
+ less than 2 GB
</entry>
<entry>
2 times the amount of RAM
@@ -91,7 +91,7 @@
</row>
<row>
<entry>
- > 2 GB - 8 GB
+ 2 GB - 8 GB
</entry>
<entry>
Equal to the amount of RAM
@@ -102,7 +102,7 @@
</row>
<row>
<entry>
- > 8 GB - 64 GB
+ 8 GB - 64 GB
</entry>
<entry>
0.5 times the amount of RAM
@@ -137,8 +137,54 @@
<term>BIOS Boot (1 MB) or EFI System Partition (200 MB)</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" />.
+ The <application>GRUB2</application> boot loader can be installed either in the <firstterm>Master Boot Record</firstterm> (MBR) or the <firstterm>GUID Partition Table</firstterm> (GPT) of the boot device. In order to determine which of these methods to use, the installation program considers the following variations:
</para>
+ <variablelist>
+ <varlistentry>
+ <term>Systems with BIOS firmware and UEFI systems in BIOS compatibility mode</term>
+ <listitem>
+ <para>
+ If the disk is already formatted, the partitioning scheme is retained. If the disk is not formatted, or you have erased all existing partitions from the disk, the installer will choose the following:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ MBR if the size of the disk is less than 2 TB (terabytes)
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ GPT if the size of the disk is more than 2 TB
+ </para>
+ </listitem>
+ </itemizedlist>
+ <note>
+ <para>
+ You can force the installer to use GPT on disks smaller than 2 TB by using the <option>inst.gpt</option> boot option as described in <xref linkend="chap-anaconda-boot-options" />. However, the opposite is not possible - you can not use MBR on disks larger than 2 TB.
+ </para>
+ </note>
+ <para>
+ You need to create a <firstterm>BIOS Boot</firstterm> partition with a size of 1 MB to install on a system with BIOS firmware if the disk containing the boot loader uses GPT. If the disk uses a MBR, no special partition is necessary on a BIOS system.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Systems with UEFI firmware</term>
+ <listitem>
+ <para>
+ Only GPT is allowed on UEFI systems. In order to install on a formatted disk with a MBR, it must be reformated and relabeled. All data currently on the disk will be lost.
+ </para>
+ <para>
+ UEFI-based systems require an <firstterm>EFI System Partition</firstterm> at least 50 MB in size (recommended size is 200 MB), regardless of the partitioning scheme.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ <important>
+ <para>
+ If your system requires either a BIOS Boot partition or an EFI System Partition based on the requirements detailed above, this partition must be created as a standard physical partition. It can not reside on a LVM volume or a Btrfs subvolume.
+ </para>
+ </important>
<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>
diff --git a/en-US/StorageSpoke_BootLoader.xml b/en-US/StorageSpoke_BootLoader.xml
index d3ebaa6..72bdf81 100644
--- a/en-US/StorageSpoke_BootLoader.xml
+++ b/en-US/StorageSpoke_BootLoader.xml
@@ -33,61 +33,8 @@
If you choose not to install a boot loader for any reason, you will not be able to boot the system directly, and you must use another boot method, such as a stand-alone commercial boot loader application. Use this option only if you are sure you have another way to boot your system.
</para>
</warning>
-
- <section id="sect-installation-gui-storage-partitioning-mbr-gpt">
- <title>MBR and GPT Considerations</title>
- <para>
- <application>GRUB2</application> can be installed either in the <firstterm>Master Boot Record</firstterm> (MBR) or the <firstterm>GUID Partition Table</firstterm> (GPT) of the boot device. In order to determine which of these methods to use, the installation program considers the following variations:
- </para>
- <variablelist>
- <varlistentry>
- <term>Systems with BIOS firmware and UEFI systems in BIOS compatibility mode</term>
- <listitem>
- <para>
- If the disk is already formatted, the partitioning scheme is retained.
- </para>
- <para>
- If the disk is not formatted, or you have erased all existing partitions from the disk, the installer choose the following:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- MBR if the size of the disk is less than 2 TB (terabytes)
- </para>
- </listitem>
- <listitem>
- <para>
- GPT if the size of the disk is more than 2 TB
- </para>
- </listitem>
- </itemizedlist>
- <note>
- <para>
- You can force the installer to use GPT on disks smaller than 2 TB by using the <option>inst.gpt</option> boot option as described in <xref linkend="chap-anaconda-boot-options" />. However, the opposite is not possible - you can not use MBR on disks larger than 2 TB.
- </para>
- </note>
- <para>
- You need to create a <firstterm>BIOS Boot</firstterm> partition with a size of 1 MB to install on a system with BIOS firmware if the disk containing the boot loader uses GPT. If the disk uses a MBR, no special partition is necessary on a BIOS system.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Systems with UEFI firmware</term>
- <listitem>
- <para>
- Only GPT is allowed on UEFI systems. In order to install on a formatted disk with a MBR, it must be reformated and relabeled. All data currently on the disk will be lost.
- </para>
- <para>
- UEFI-based systems require an <firstterm>EFI System Partition</firstterm> at least 50 MB in size (recommended size is 200 MB), regardless of the partitioning scheme.
- </para>
- </listitem>
- </varlistentry>
- </variablelist>
- <important>
- <para>
- If your system requires either a BIOS Boot partition or an EFI System Partition based on the requirements detailed above, this partition must be created as a standard physical partition. It can not reside on a LVM volume or a Btrfs subvolume.
- </para>
- </important>
- </section>
+ <para>
+ The boot loader may also require a special partition to be created, depending on whether your system uses BIOS or UEFI firmware and also depending on whether the boot drive has a <firstterm>GUID Partition Table</firstterm> (GPT) or a <guilabel>Master Boot Record</guilabel> (MBR, also known as msdos) label. If you use automatic partitioning, the installer will create this partition if needed. For details, see <xref linkend="sect-installation-gui-manual-partitioning-recommended" />.
+ </para>
</section>
9 years, 7 months
[install-guide] (10 commits) ...Merge branch 'master' into f21-branch
by pbokoc
Summary of changes:
07910a3... checksum introduction (*)
4e568e8... Adding the Add FCoE SAN section to FilterSpoke (*)
c582e80... Adding structure to CustomSpoke and adding Advice on Partit (*)
5d617c0... Hey, we don't need to recommend any third party tools to ve (*)
949c3cd... Windows USB media creation. (*)
25d899f... obigatory warning about universal usb tools (*)
27b7f55... usb media creation, with GNOME disks (*)
40e1962... Adding Recommended Scheme to CustomSpoke (*)
8bb90c7... Fixing a bad xref and a typo (*)
6d4ddcd... Merge branch 'master' into f21-branch (*)
(*) This commit already existed in another branch; no separate mail sent
9 years, 7 months
[install-guide/f21-branch] (10 commits) ...Merge branch 'master' into f21-branch
by pbokoc
Summary of changes:
168fe01... Adding the Add FCoE SAN section to FilterSpoke (*)
eb06ae0... Adding structure to CustomSpoke and adding Advice on Partit (*)
234e4d8... checksum introduction (*)
e1ac8ff... Hey, we don't need to recommend any third party tools to ve (*)
6b35c40... Windows USB media creation. (*)
5f49853... obigatory warning about universal usb tools (*)
8cff0bb... usb media creation, with GNOME disks (*)
0c186f3... Adding Recommended Scheme to CustomSpoke (*)
254e2c6... Fixing a bad xref and a typo (*)
6d4ddcd... Merge branch 'master' into f21-branch
(*) This commit already existed in another branch; no separate mail sent
9 years, 7 months
[install-guide/f21-branch] Fixing a bad xref and a typo
by pbokoc
commit 8bb90c762e6de70a3a23b62c6cf72ee04abf10ff
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Mon Nov 17 16:32:45 2014 +0100
Fixing a bad xref and a typo
en-US/CustomSpoke_RecommendedScheme.xml | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
---
diff --git a/en-US/CustomSpoke_RecommendedScheme.xml b/en-US/CustomSpoke_RecommendedScheme.xml
index c9afcf0..1195176 100644
--- a/en-US/CustomSpoke_RecommendedScheme.xml
+++ b/en-US/CustomSpoke_RecommendedScheme.xml
@@ -134,7 +134,7 @@
</listitem>
</varlistentry>
<varlistentry>
- <term>BIOS Boot (1 MB) or EFI System Partition (200 MB), based on your system firmware and disks</term>
+ <term>BIOS Boot (1 MB) or EFI System Partition (200 MB)</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" />.
@@ -146,7 +146,7 @@
</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.
+ Many systems have more partitions than the minimum listed above. Choose partitions based on your particular needs. See <xref linkend="sect-installation-gui-manual-partitioning-advice" /> for additional information and advice.
</para>
<note>
<para>
9 years, 7 months
[install-guide] Fixing a bad xref and a typo
by pbokoc
commit 254e2c68c2e31151b5d03efc80a4d6fdb7f887fd
Author: Petr Bokoc <pbokoc(a)redhat.com>
Date: Mon Nov 17 16:32:45 2014 +0100
Fixing a bad xref and a typo
en-US/CustomSpoke_RecommendedScheme.xml | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
---
diff --git a/en-US/CustomSpoke_RecommendedScheme.xml b/en-US/CustomSpoke_RecommendedScheme.xml
index c9afcf0..1195176 100644
--- a/en-US/CustomSpoke_RecommendedScheme.xml
+++ b/en-US/CustomSpoke_RecommendedScheme.xml
@@ -134,7 +134,7 @@
</listitem>
</varlistentry>
<varlistentry>
- <term>BIOS Boot (1 MB) or EFI System Partition (200 MB), based on your system firmware and disks</term>
+ <term>BIOS Boot (1 MB) or EFI System Partition (200 MB)</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" />.
@@ -146,7 +146,7 @@
</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.
+ Many systems have more partitions than the minimum listed above. Choose partitions based on your particular needs. See <xref linkend="sect-installation-gui-manual-partitioning-advice" /> for additional information and advice.
</para>
<note>
<para>
9 years, 7 months
[install-guide] Adding Recommended Scheme to CustomSpoke
by pbokoc
commit 0c186f347eaacb5218ae9c9654a4053a860b5ee2
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, 7 months
[install-guide] usb media creation, with GNOME disks
by pbokoc
commit 8cff0bbdc2ab8d79f600d61a553f36c046176e28
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, 7 months
[install-guide] obigatory warning about universal usb tools
by pbokoc
commit 5f49853b98ca88c2b26050359e0d875115e18610
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, 7 months
[install-guide] Windows USB media creation.
by pbokoc
commit 6b35c409b9b7d56351ffe0ba9e47437520e3cd09
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, 7 months