[multiboot-guide] master: This warning about disabling windows fast restart should probably be repeated, so I'm making it an include (cdee96d)
by Pete Travis
Repository : http://git.fedorahosted.org/cgit/docs/multiboot-guide.git
On branch : master
>---------------------------------------------------------------
commit cdee96dca15c32cb8aa144f1c348227fb962eaa1
Author: Pete Travis <immanetize(a)fedoraproject.org>
Date: Thu Feb 13 22:58:18 2014 -0700
This warning about disabling windows fast restart should probably be repeated, so I'm making it an include
>---------------------------------------------------------------
en-US/fast_reboot_admonition.xml | 17 +++++++++++++++++
1 files changed, 17 insertions(+), 0 deletions(-)
diff --git a/en-US/fast_reboot_admonition.xml b/en-US/fast_reboot_admonition.xml
new file mode 100644
index 0000000..5c803e3
--- /dev/null
+++ b/en-US/fast_reboot_admonition.xml
@@ -0,0 +1,17 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Fedora_Multiboot_Guide.ent">
+%BOOK_ENTITIES;
+]>
+
+<caution>
+ <title>
+ Disable Windows <function>fast reboot</function> feature!
+ </title>
+ <para>
+ Newer versions of Windows use a strategy of suspending some system processes to disk to speed startup times. Modifying a filesystem in this state can corrupt or damage the data, so the linux NTFS drivers will not mount it. If the filesystem were to be mounted, the cached view if the files may differ from the changes you made in Fedora, with the most likely result of loosing your changes - or worse.
+ </para>
+ <para>
+ Before attempting any operation on an NTFS volume from Fedora, make sure you have disabled this feature in Windows.
+ </para>
+</caution>
10 years, 2 months
[multiboot-guide] master: elaborate on the recommendation to use the anaconda resizer during install (8fe82f2)
by Pete Travis
Repository : http://git.fedorahosted.org/cgit/docs/multiboot-guide.git
On branch : master
>---------------------------------------------------------------
commit 8fe82f2c5d9adea0c858ea77bd2edb71ca158db2
Author: Pete Travis <immanetize(a)fedoraproject.org>
Date: Thu Feb 13 22:57:10 2014 -0700
elaborate on the recommendation to use the anaconda resizer during install
>---------------------------------------------------------------
en-US/Free_Space.xml | 11 ++++++++---
1 files changed, 8 insertions(+), 3 deletions(-)
diff --git a/en-US/Free_Space.xml b/en-US/Free_Space.xml
index 54c6f02..29220c7 100644
--- a/en-US/Free_Space.xml
+++ b/en-US/Free_Space.xml
@@ -7,11 +7,15 @@
<section id="freespace">
<title>Making Room for Fedora</title>
<para>
- Fedora requires a volume of <emphasis>unallocated</emphasis> storage space for installation. To make room for Fedora, both the existing filesystem and the partition it resides on must be resized
+ Fedora requires a volume of <emphasis>unallocated</emphasis> storage space for installation. To make room for Fedora, both the existing filesystem and the partition it resides on must be resized.
</para>
<section id="freespace-anaconda">
<title>Using the Fedora Installer to resize partitions</title>
- <para>http://docs.fedoraproject.org/en-US/Fedora/19/html/Installation_Guide/rec...
+ <para>
+ The Fedora installer provides a guided graphical method for resizing partitions and reclaiming space. This method is simpler and easier than the others discussed in this section. For most simple dual boot situations, using the installer to reclaim space will be the most expedient and foolproof method.
+ </para>
+ <para>
+ Resizing partitions with the Fedora installer is covered in the <ulink url="http://docs.fedoraproject.org/en-US/Fedora/19/html/Installation_Guide/rec...">Fedora Installation Guide</ulink>
</para>
<!-- "An introduction to Disk Partitions"
http://docs.fedoraproject.org/en-US/Fedora/19/html/Installation_Guide/ch-...
@@ -23,6 +27,7 @@ http://docs.fedoraproject.org/en-US/Fedora/19/html/Installation_Guide/ch-...
<para>
This section explains using tools provided by Fedora to resize an NTFS partition. A terminal window from a liveCD can be used.
</para>
+ <xi:include href="fast_reboot_admonition.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<procedure>
<title>
Selecting and resizing a partition.
@@ -84,7 +89,7 @@ Please make a test run using both the -n and -s options before real resizing!
</step>
<step>
<para>
- Resize the filesystem. Make sure to balance the available space, a very full filesystem can cause problems for any operating system.
+ Resize the filesystem. Make sure to balance the available space, despite the suggestion from <application>ntfsresize</application> to shrink to the bare minimum. A very full filesystem can cause problems for any operating system.
<screen>
# <command>ntfsresize --size 40G /dev/sda5</command>
ntfsresize v2013.1.13 (libntfs-3g)
10 years, 2 months
[multiboot-guide] master: Minor adjustments to bios/uefi comparison (30e19bd)
by Pete Travis
Repository : http://git.fedorahosted.org/cgit/docs/multiboot-guide.git
On branch : master
>---------------------------------------------------------------
commit 30e19bd6095ef423c87f5ed24c36e9dfd4d290dd
Author: Pete Travis <immanetize(a)fedoraproject.org>
Date: Thu Feb 13 22:06:37 2014 -0700
Minor adjustments to bios/uefi comparison
>---------------------------------------------------------------
en-US/BOOT-BIOS_or_UEFI.xml | 11 ++++++++---
1 files changed, 8 insertions(+), 3 deletions(-)
diff --git a/en-US/BOOT-BIOS_or_UEFI.xml b/en-US/BOOT-BIOS_or_UEFI.xml
index c9b6649..92b565c 100644
--- a/en-US/BOOT-BIOS_or_UEFI.xml
+++ b/en-US/BOOT-BIOS_or_UEFI.xml
@@ -18,7 +18,7 @@
</listitem>
<listitem>
<para>
- 32 bit systems are almost always BIOS.
+ 32 bit systems are almost always BIOS. ( UEFI booting of 32 bit systems is not supported by Fedora )
</para>
</listitem>
<listitem>
@@ -35,7 +35,7 @@
<note>
<title>The term <literal>BIOS</literal> is still used with UEFI systems</title>
<para>
- Because BIOS systems have been around for so long, the term <literal>BIOS</literal> is often used to describe UEFI systems as well. Manufacturers might list system firmware updates as <literal>BIOS updates</literal> or provide directions to <literal>enter the BIOS setup menu</literal>. The word has come to represent the pre-OS menu on your computer as much as the actual software, but it doesn't mean that your system is not UEFI capable.
+ Because BIOS systems have been around for so long, the term <literal>BIOS</literal> is often used to describe UEFI systems as well. Manufacturers might list system firmware updates as <literal>BIOS updates</literal> or provide directions to <literal>enter the BIOS setup menu</literal>. The word has come to represent the pre-OS menu on your computer as much as the actual software, but your system may still be UEFI capable.
</para>
</note>
<itemizedlist>
@@ -57,10 +57,15 @@
</listitem>
<listitem>
<para>
- The system's boot menu gives you the option of booting via UEFI or not, with entries like these:
+ The system's boot menu gives you the option of booting media via UEFI, or has boot options describing operating systems instead of just physical drives. The boot order menu might look like this:
+
<screen>
UEFI: Generic USB Stick
Generic USB Stick
+ UEFI: DVD-RW Drive
+ DVD-RW Drive
+ Fedora
+ Windows
</screen>
</para>
</listitem>
10 years, 2 months
[multiboot-guide] master: Improving some phrasing in the general boot process description (0d84088)
by Pete Travis
Repository : http://git.fedorahosted.org/cgit/docs/multiboot-guide.git
On branch : master
>---------------------------------------------------------------
commit 0d840886302b5320c1b0f43183ed30f14fe61396
Author: Pete Travis <immanetize(a)fedoraproject.org>
Date: Thu Feb 13 21:59:31 2014 -0700
Improving some phrasing in the general boot process description
>---------------------------------------------------------------
en-US/BOOT-general.xml | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/en-US/BOOT-general.xml b/en-US/BOOT-general.xml
index 1c4d562..cff1e18 100644
--- a/en-US/BOOT-general.xml
+++ b/en-US/BOOT-general.xml
@@ -19,7 +19,7 @@
BIOS is short for Basic Input Output System, and the software is indeed very simple. BIOS systems had a number of technical limitations, such as being unable to boot from disks larger than 2 TB and extremely limited interfaces. GUID Partition Table (GPT) partitioning schemes also came with larger drives, overcoming the MBR partitioning scheme's 4 partition limit. To overcome these issues and add new features, a newer firmware implementation was developed, called the Unified Extensible Firmware Interface.
</para>
<para>
- Instead of reading the bootloader from the drive, UEFI systems store some boot information right on the system firmware. Larger bootloaders and small applications such as memory testing utilites are stored on the UEFI system partition. This partition is always a FAT filesystem,has a standardized partition identifier, and is mounted at <filename>/boot/efi</filename>. Each operating system places files required for booting in a dedicated directory of this partition, and the boot entry in the firmware points to these files. UEFI systems will usually also support BIOS style booting for compatibility reasons.
+ Instead of reading the bootloader from the drive, UEFI systems store information about available bootloaders right on the system firmware. The bootloaders themselves and sometimes small applications such as memory testing utilites are stored on the UEFI system partition. This partition is usually a FAT filesystem, has a standardized partition identifier, and is mounted at <filename>/boot/efi</filename>. Each operating system places files required for booting in a dedicated directory of this partition, and the boot entry in the firmware points to these files. UEFI systems will usually also support BIOS style booting for compatibility reasons, using a feature called the Compatibility Support Module (CSM).
</para>
<para>
On Linux systems, the data used by the bootloader is traditionally contained in a <systemitem>boot partition</systemitem>, mounted at and known as <filename>/boot</filename>. The boot partition contains the kernel, a read only filesystem that holds tools used by the kernel during bootup, called an <systemitem>initramfs</systemitem>, and files for the menus and for the bootloader itself. These files were traditionally placed on a different partition because the bootloader did not support complex storage arrangements, and could not read the kernel and initramfs from them. Because a simple, separate boot also allows for easier disaster recovery, the practice has continued to this day.
10 years, 2 months
[system-administrators-guide] Wrong guide was mentioned under "Target Audience"
by stephenw
commit 8079423f9cbde9b5f409f61be4c9cc5a842acbdc
Author: Stephen Wadeley <swadeley(a)redhat.com>
Date: Tue Feb 11 00:14:29 2014 +0100
Wrong guide was mentioned under "Target Audience"
en-US/Preface.xml | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
---
diff --git a/en-US/Preface.xml b/en-US/Preface.xml
index ad5c242..da8a2e9 100644
--- a/en-US/Preface.xml
+++ b/en-US/Preface.xml
@@ -35,7 +35,7 @@
<section id="sect-Preface-Target_Audience">
<title>Target Audience</title>
<para>
- The <citetitle pubwork="book">Deployment Guide</citetitle> assumes you have a basic understanding of the &MAJOROS; operating system. If you need help with the installation of this system, refer to the <ulink url="http://docs.fedoraproject.org/en-US/Fedora/19/html/Installation_Guide/ind...">&MAJOROSVER; Installation Guide</ulink>.
+ The <citetitle pubwork="book">System Administrator's Guide</citetitle> assumes you have a basic understanding of the &MAJOROS; operating system. If you need help with the installation of this system, refer to the <ulink url="http://docs.fedoraproject.org/en-US/Fedora/19/html/Installation_Guide/ind...">&MAJOROSVER; Installation Guide</ulink>.
<!-- &ENTITIES; are stripped from URLs by transifex, so hardcoding is better for now -->
</para>
</section>
10 years, 2 months
[system-administrators-guide] Removing the Consistent Network Device Naming chapter and the link to it from the Preface. It is now
by stephenw
commit b4b9d79c8aaedb7eb269e09ef879e73c461fe9ac
Author: Stephen Wadeley <swadeley(a)redhat.com>
Date: Mon Feb 10 23:59:08 2014 +0100
Removing the Consistent Network Device Naming chapter and the link to it
from the Preface. It is now covered in the Networking Guide.
en-US/Consistent_Network_Device_Naming.xml | 125 ----------------------------
en-US/Preface.xml | 10 +--
2 files changed, 1 insertions(+), 134 deletions(-)
---
diff --git a/en-US/Preface.xml b/en-US/Preface.xml
index a5c8b32..ad5c242 100644
--- a/en-US/Preface.xml
+++ b/en-US/Preface.xml
@@ -162,15 +162,7 @@
</para>
</listitem>
</varlistentry>
- <varlistentry>
- <term><xref linkend="appe-Consistent_Network_Device_Naming" /></term>
- <listitem>
- <para>
- This appendix covers consistent network device naming for network interfaces, a feature that changes the name of network interfaces on a system in order to make locating and differentiating the interfaces easier. Read this appendix to learn more about this feature and how to enable or disable it.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
+ <varlistentry>
<term><xref linkend="ch-RPM" /></term>
<listitem>
<para>
10 years, 2 months
[system-administrators-guide] Removing DHCP chapter and the reference to it from the Preface Its now covered by the Networking Gui
by stephenw
commit 0e92dfe4ac70c7b4f635d17acf64cf32d6d484be
Author: Stephen Wadeley <swadeley(a)redhat.com>
Date: Mon Feb 10 23:57:50 2014 +0100
Removing DHCP chapter and the reference to it from the Preface
Its now covered by the Networking Guide
en-US/DHCP_Servers.xml | 617 ------------------------------------------------
en-US/Preface.xml | 3 -
2 files changed, 0 insertions(+), 620 deletions(-)
---
diff --git a/en-US/Preface.xml b/en-US/Preface.xml
index 3122f30..a5c8b32 100644
--- a/en-US/Preface.xml
+++ b/en-US/Preface.xml
@@ -100,9 +100,6 @@
This part discusses various topics related to servers such as how to set up a Web server or share files and directories over the network.
</para>
<para>
- <xref linkend="ch-DHCP_Servers" /> guides you through the installation of a Dynamic Host Configuration Protocol (DHCP) server and client. Read this chapter if you need to configure DHCP on your system.
- </para>
- <para>
<xref linkend="ch-Web_Servers" /> focuses on the <application>Apache HTTP Server 2.2</application>, a robust, full-featured open source web server developed by the Apache Software Foundation. Read this chapter if you need to configure a web server on your system.
</para>
<para>
10 years, 2 months
[system-administrators-guide] Removing the BIND chapter and the reference to DNS from the Preface This is now covered by the Netwo
by stephenw
commit 7f96d82283eea8d5ca9f5c05ba90e48f06e60865
Author: Stephen Wadeley <swadeley(a)redhat.com>
Date: Mon Feb 10 23:56:32 2014 +0100
Removing the BIND chapter and the reference to DNS from the Preface
This is now covered by the Networking Guide.
en-US/BIND.xml | 2053 -----------------------------------------------------
en-US/Preface.xml | 3 -
2 files changed, 0 insertions(+), 2056 deletions(-)
---
diff --git a/en-US/Preface.xml b/en-US/Preface.xml
index 6dbd314..3122f30 100644
--- a/en-US/Preface.xml
+++ b/en-US/Preface.xml
@@ -103,9 +103,6 @@
<xref linkend="ch-DHCP_Servers" /> guides you through the installation of a Dynamic Host Configuration Protocol (DHCP) server and client. Read this chapter if you need to configure DHCP on your system.
</para>
<para>
- <xref linkend="ch-DNS_Servers" /> introduces you to Domain Name System (DNS), explains how to install, configure, run, and administer the <application>BIND</application> DNS server. Read this chapter if you need to configure a DNS server on your system.
- </para>
- <para>
<xref linkend="ch-Web_Servers" /> focuses on the <application>Apache HTTP Server 2.2</application>, a robust, full-featured open source web server developed by the Apache Software Foundation. Read this chapter if you need to configure a web server on your system.
</para>
<para>
10 years, 2 months
[system-administrators-guide] Removing Network Interfaces chapter (now covered by Networking Guide) Removing its link from the Pre
by stephenw
commit c4abe9f14ab80a0c40c3144573886fe3523a354a
Author: Stephen Wadeley <swadeley(a)redhat.com>
Date: Mon Feb 10 23:54:42 2014 +0100
Removing Network Interfaces chapter (now covered by Networking Guide)
Removing its link from the Preface
en-US/Network_Interfaces.xml | 2739 ------------------------------------------
en-US/Preface.xml | 21 +-
2 files changed, 3 insertions(+), 2757 deletions(-)
---
diff --git a/en-US/Preface.xml b/en-US/Preface.xml
index 40d095b..6dbd314 100644
--- a/en-US/Preface.xml
+++ b/en-US/Preface.xml
@@ -15,14 +15,10 @@
Installing and managing packages using the graphical <application>PackageKit</application> and command line <application>Yum</application> package managers
</para>
</listitem>
+
<listitem>
<para>
- Setting up a network—from establishing an Ethernet connection using <application>NetworkManager</application> to configuring channel bonding interfaces to increase server bandwidth
- </para>
- </listitem>
- <listitem>
- <para>
- Configuring <systemitem class="service">DHCP</systemitem>, <application>BIND</application>, <application>Apache HTTP Server</application>, <application>Postfix</application>, <application>Sendmail</application> and other enterprise-class servers and software
+ Configuring <application>Apache HTTP Server</application>, <application>Postfix</application>, <application>Sendmail</application> and other enterprise-class servers and software
</para>
</listitem>
<listitem>
@@ -80,18 +76,7 @@
</para>
</listitem>
</varlistentry>
- <varlistentry>
- <term><xref linkend="part-Networking" /></term>
- <listitem>
- <para>
- This part describes how to configure the network on &MAJOROS;.
- </para>
- <para>
- <xref linkend="ch-Network_Interfaces" /> explores various interface configuration files, interface control scripts, and network function files located in the <filename class="directory">/etc/sysconfig/network-scripts/</filename> directory. Read this chapter for information how to use these files to configure network interfaces.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
+ <varlistentry>
<term><xref linkend="part-Infrastructure_Services" /></term>
<listitem>
<para>
10 years, 2 months
[system-administrators-guide] Removing NetworkManager chapter (now covered by Networking Guide) Removing its link from the Preface
by stephenw
commit 204a5a9846f2b00d01bf7001be5b2a498abbdbbb
Author: Stephen Wadeley <swadeley(a)redhat.com>
Date: Mon Feb 10 23:52:48 2014 +0100
Removing NetworkManager chapter (now covered by Networking Guide)
Removing its link from the Preface
en-US/NetworkManager.xml | 1733 ----------------------------------------------
en-US/Preface.xml | 3 -
2 files changed, 0 insertions(+), 1736 deletions(-)
---
diff --git a/en-US/Preface.xml b/en-US/Preface.xml
index 5a14469..40d095b 100644
--- a/en-US/Preface.xml
+++ b/en-US/Preface.xml
@@ -87,9 +87,6 @@
This part describes how to configure the network on &MAJOROS;.
</para>
<para>
- <xref linkend="ch-NetworkManager" /> focuses on <application>NetworkManager</application>, a dynamic network control and configuration system that attempts to keep network devices and connections up and active when they are available. Read this chapter for information how to run the <systemitem class="service">NetworkManager</systemitem> daemon, and how to interact with it using the corresponding applet for the notification area.
- </para>
- <para>
<xref linkend="ch-Network_Interfaces" /> explores various interface configuration files, interface control scripts, and network function files located in the <filename class="directory">/etc/sysconfig/network-scripts/</filename> directory. Read this chapter for information how to use these files to configure network interfaces.
</para>
</listitem>
10 years, 2 months