July 2013 - docs-commits - Fedora Mailing-Lists

[system-administrators-guide/18] Going to use "chrony" with lower case "c" except at the beginning of a sentence.

by jhradile

commit 806a37bf3a1680bace7cee892e9fbec67ee6b8b9 Author: Stephen Wadeley <swadeley(a)redhat.com> Date: Thu Jun 27 20:40:58 2013 +0200 Going to use "chrony" with lower case "c" except at the beginning of a sentence. en-US/Configuring_NTP_using_the_Chrony_suite.xml | 12 ++++++------ 1 files changed, 6 insertions(+), 6 deletions(-) --- diff --git a/en-US/Configuring_NTP_using_the_Chrony_suite.xml b/en-US/Configuring_NTP_using_the_Chrony_suite.xml index 4104a03..a7914a3 100644 --- a/en-US/Configuring_NTP_using_the_Chrony_suite.xml +++ b/en-US/Configuring_NTP_using_the_Chrony_suite.xml @@ -16,9 +16,9 @@ There is a choice between the daemons <systemitem class="daemon">ntpd</systemitem> and <systemitem class="daemon">chronyd</systemitem>, which are available from the repos in the <package>ntp</package> and <package>chrony</package> packages respectively. This section describes the use of the <application>chrony</application> suite of utilities to update the daemon on systems that do not fit into the conventional permanently networked, always on, dedicated server category. </para> <section id="sect-Introduction_to_the_chrony_suite"> - <title>Introduction To The Chrony Suite</title> + <title>Introduction To The chrony Suite</title> <para> - <application>Chrony</application> consists of <systemitem class="daemon">chronyd</systemitem>, a daemon that runs in user space, and <application>chronyc</application>, a command line program for making adjustments to <systemitem class="daemon">chronyd</systemitem>. Systems which are not permanently connected, or not permanently powered up, take a relatively long time to adjust their system clocks using the <systemitem class="protocol">NTP</systemitem> time protocol. This is because many small corrections are made based on observations of the clocks drift and offset. Temperature changes, which may be significant when powering up a system, affect the stability of hardware clocks. Although adjustments begin within a few milliseconds of booting a system, acceptable accuracy may take anything from ten seconds from a warm restart to a number of hours depending on your requirements, operating environment and hardware. <application>Chrony</application> is a different implementat ion of the <systemitem class="protocol">NTP</systemitem> protocol than <systemitem class="daemon">ntpd</systemitem>, it can adjust the system clock more rapidly. + <application>Chrony</application> consists of <systemitem class="daemon">chronyd</systemitem>, a daemon that runs in user space, and <application>chronyc</application>, a command line program for making adjustments to <systemitem class="daemon">chronyd</systemitem>. Systems which are not permanently connected, or not permanently powered up, take a relatively long time to adjust their system clocks using the <systemitem class="protocol">NTP</systemitem> time protocol. This is because many small corrections are made based on observations of the clocks drift and offset. Temperature changes, which may be significant when powering up a system, affect the stability of hardware clocks. Although adjustments begin within a few milliseconds of booting a system, acceptable accuracy may take anything from ten seconds from a warm restart to a number of hours depending on your requirements, operating environment and hardware. <application>chrony</application> is a different implementat ion of the <systemitem class="protocol">NTP</systemitem> protocol than <systemitem class="daemon">ntpd</systemitem>, it can adjust the system clock more rapidly. </para> </section> @@ -114,7 +114,7 @@ Things <systemitem class="daemon">ntpd</systemitem> can do that <systemitem clas <section id="sect-Understanding_chronyd"> <title>Understanding chronyd</title> <para> - The <application>Chrony</application> daemon, <systemitem class="daemon">chronyd</systemitem>, running in user space, makes adjustments to the system clock which is running in the kernel. It does this by consulting external time sources, using the <systemitem class="protocol">NTP</systemitem> protocol, when ever network access allows it to do so. When external references are not available, <systemitem class="daemon">chronyd</systemitem> will use the last calculated drift stored in the drift file. It can also be commanded manually to make corrections, by <application>chronyc</application>. + The <application>chrony</application> daemon, <systemitem class="daemon">chronyd</systemitem>, running in user space, makes adjustments to the system clock which is running in the kernel. It does this by consulting external time sources, using the <systemitem class="protocol">NTP</systemitem> protocol, when ever network access allows it to do so. When external references are not available, <systemitem class="daemon">chronyd</systemitem> will use the last calculated drift stored in the drift file. It can also be commanded manually to make corrections, by <application>chronyc</application>. </para> </section> @@ -175,7 +175,7 @@ Optionally specify a host, subnet, or network from which to allow <systemitem cl <term>cmdallow</term> <listitem> <para> - This is similar to the <command>allow</command> directive (see section allow), except that it allows control access (rather than <systemitem class="protocol">NTP</systemitem> client access) to a particular subnet or host. (By ’control access’ is meant that <application>chronyc</application> can be run on those hosts and successfully connect to <systemitem class="daemon">chronyd</systemitem> on this computer.) The syntax is identical. There is also a <command>cmddeny</command> all directive with similar behaviour to the <command>cmdallow</command> all directive. </para> + This is similar to the <command>allow</command> directive (see section allow), except that it allows control access (rather than <systemitem class="protocol">NTP</systemitem> client access) to a particular subnet or host. (By <quote>control access</quote> is meant that <application>chronyc</application> can be run on those hosts and successfully connect to <systemitem class="daemon">chronyd</systemitem> on this computer.) The syntax is identical. There is also a <command>cmddeny</command> all directive with similar behaviour to the <command>cmdallow</command> all directive. </para> </listitem> </varlistentry> @@ -199,7 +199,7 @@ Optionally specify a host, subnet, or network from which to allow <systemitem cl <term>local</term> <listitem> <para> - The <command>local</command> keyword is used to allow <systemitem class="daemon">chronyd</systemitem> to appear synchronized to real time (from the viewpoint of clients polling it), even if it has no current synchronization source. This option is normally used on computers in an isolated network, where several computers are required to synchronize to one other, this being the "master" which is kept vaguely in line with real time by manual input.</para> + The <command>local</command> keyword is used to allow <systemitem class="daemon">chronyd</systemitem> to appear synchronized to real time (from the viewpoint of clients polling it), even if it has no current synchronization source. This option is normally used on computers in an isolated network, where several computers are required to synchronize to one other, this being the <quote>master</quote> which is kept vaguely in line with real time by manual input.</para> <para> An example of the command is: <screen>local stratum 10</screen> @@ -858,7 +858,7 @@ This is the estimated error bounds on Freq (again in parts per million). </section> <section id="sect-Setting_up_chrony_for_a_system_which_is_infrequently_connected"> - <title>Setting Up Chrony For A System Which Is Infrequently Connected</title> + <title>Setting Up chrony For A System Which Is Infrequently Connected</title> <para> This example is intended for systems which use dial-on-demand connections. The normal configuration should be sufficient for mobile and virtual devices which connect intermittently. First, review and confirm that the default settings in the <filename>/etc/chrony.conf</filename> are similar to the following: <screen>driftfile /var/lib/chrony/drift

10 years, 10 months

1
0
0 / 0

[system-administrators-guide/18] Improving the section headings: Title Case

by jhradile

commit 79a93a2fb0c40508a091248583419b94893113dd Author: Stephen Wadeley <swadeley(a)redhat.com> Date: Thu Jun 27 20:26:28 2013 +0200 Improving the section headings: Title Case en-US/Configuring_NTP_using_the_Chrony_suite.xml | 78 +++++++++++----------- 1 files changed, 39 insertions(+), 39 deletions(-) --- diff --git a/en-US/Configuring_NTP_using_the_Chrony_suite.xml b/en-US/Configuring_NTP_using_the_Chrony_suite.xml index 58a1674..4104a03 100644 --- a/en-US/Configuring_NTP_using_the_Chrony_suite.xml +++ b/en-US/Configuring_NTP_using_the_Chrony_suite.xml @@ -6,7 +6,7 @@  <chapter id="chap-Networking_Guide-Configuring_NTP_using_the_chrony_suite"> - <title>Configuring NTP using the chrony suite</title> + <title>Configuring NTP Using The chrony Suite</title> <para> Accurate time keeping is important for a number of reasons in IT. In networking for example, accurate time stamps in packets and logs are required. In Linux systems, the <systemitem class="protocol">NTP</systemitem> protocol is implemented by a daemon running in user space.</para> <para> @@ -15,15 +15,15 @@ <para> There is a choice between the daemons <systemitem class="daemon">ntpd</systemitem> and <systemitem class="daemon">chronyd</systemitem>, which are available from the repos in the <package>ntp</package> and <package>chrony</package> packages respectively. This section describes the use of the <application>chrony</application> suite of utilities to update the daemon on systems that do not fit into the conventional permanently networked, always on, dedicated server category. </para> -<section id="sect-Networking_Guide-Introduction_to_the_chrony_suite"> - <title>Introduction to the chrony suite</title> +<section id="sect-Introduction_to_the_chrony_suite"> + <title>Introduction To The Chrony Suite</title> <para> <application>Chrony</application> consists of <systemitem class="daemon">chronyd</systemitem>, a daemon that runs in user space, and <application>chronyc</application>, a command line program for making adjustments to <systemitem class="daemon">chronyd</systemitem>. Systems which are not permanently connected, or not permanently powered up, take a relatively long time to adjust their system clocks using the <systemitem class="protocol">NTP</systemitem> time protocol. This is because many small corrections are made based on observations of the clocks drift and offset. Temperature changes, which may be significant when powering up a system, affect the stability of hardware clocks. Although adjustments begin within a few milliseconds of booting a system, acceptable accuracy may take anything from ten seconds from a warm restart to a number of hours depending on your requirements, operating environment and hardware. <application>Chrony</application> is a different implementat ion of the <systemitem class="protocol">NTP</systemitem> protocol than <systemitem class="daemon">ntpd</systemitem>, it can adjust the system clock more rapidly. </para> </section> <section id="sect-differences_between_ntpd_and_chronyd"> - <title>Differences between ntpd and chronyd</title> + <title>Differences Between ntpd And chronyd</title> <para> One of the main differences between <systemitem class="daemon">ntpd</systemitem> and <systemitem class="daemon">chronyd</systemitem> is in the algorithms used to control the computer's clock. Things <systemitem class="daemon">chronyd</systemitem> can do better than <systemitem class="daemon">ntpd</systemitem> are: @@ -96,8 +96,8 @@ Things <systemitem class="daemon">ntpd</systemitem> can do that <systemitem clas </itemizedlist> </section> -<section id="sect-Networking_Guide-Choosing_between_NTP_daemon"> - <title>Choosing between NTP daemons</title> +<section id="sect-Choosing_between_NTP_daemon"> + <title>Choosing Between NTP Daemons</title> <itemizedlist> <listitem> <para> @@ -111,21 +111,21 @@ Things <systemitem class="daemon">ntpd</systemitem> can do that <systemitem clas </listitem> </itemizedlist> </section> -<section id="sect-Networking_Guide-Understanding_chronyd"> +<section id="sect-Understanding_chronyd"> <title>Understanding chronyd</title> <para> The <application>Chrony</application> daemon, <systemitem class="daemon">chronyd</systemitem>, running in user space, makes adjustments to the system clock which is running in the kernel. It does this by consulting external time sources, using the <systemitem class="protocol">NTP</systemitem> protocol, when ever network access allows it to do so. When external references are not available, <systemitem class="daemon">chronyd</systemitem> will use the last calculated drift stored in the drift file. It can also be commanded manually to make corrections, by <application>chronyc</application>. </para> </section> -<section id="sect-Networking_Guide-Understanding_chronyc"> +<section id="sect-Understanding_chronyc"> <title>Understanding chronyc</title> <para> The <application>chrony</application> daemon, <systemitem class="daemon">chronyd</systemitem>, can be controlled by the command line utility <application>chronyc</application>. This utility provides a command prompt which allows entering of a number of commands to make changes to <systemitem class="daemon">chronyd</systemitem>. The default configuration is for <systemitem class="daemon">chronyd</systemitem> to only accept commands from a local instance of <application>chronyc</application>, but <application>chronyc</application> can be used to alter the configuration so that <systemitem class="daemon">chronyd</systemitem> will allow external control. That is to say, <application>chronyc</application> can be run remotely after first configuring <systemitem class="daemon">chronyd</systemitem> to accept remote connections. The IP addresses allowed to connect to <systemitem class="daemon">chronyd</systemitem> should be tightly controlled.</para> </section> - <section id="sect-Networking_Guide-Understanding_the_chrony_configuration_commands"> - <title>Understanding the chrony configuration commands</title> + <section id="sect-Understanding_the_chrony_configuration_commands"> + <title>Understanding The chrony Configuration Commands</title> <para> <systemitem class="daemon">chronyd</systemitem>'s default config file is <filename>/etc/chrony.conf</filename>. The <option>-f</option> option can be used to specify an alternate config file path. Refer to the <systemitem class="daemon">chronyd</systemitem> man page for further options. We present here a selection of configuration options. For a complete list of the directives that can be used see <citetitle pubwork="webpage">http://chrony.tuxfamily.org/manual.html#Configuration-file</citetitle> <variablelist> @@ -403,8 +403,8 @@ Not all real-time clocks are supported as their code system-specific. </para> </section> -<section id="sect-Networking_Guide-Security_with_chronyc"> - <title>Security with chronyc</title> +<section id="sect-Security_with_chronyc"> + <title>Security With chronyc</title> <para> As access to <application>chronyc</application> allows changing <systemitem class="daemon">chronyd</systemitem> just as editing the configuration files would, access to <application>chronyc</application> should be limited. Passwords or their hashes can be specified in the key file, to restrict the use of <application>chronyc</application>. One of the entries is used to restrict the use of operational commands and is referred to as the command key. In the default configuration, a random command key is generated automatically on start. It should not be necessary to specify or alter it manually.</para> <para>Other entries in the key file can be used as <systemitem class="protocol">NTP</systemitem> keys to authenticate packets received from remote <systemitem class="protocol">NTP</systemitem> servers or peers. The two sides need to share a key with identical ID, hash type and password in their key file. This requires manually creating the keys and copying them over a secure medium, such as <systemitem class="protocol">SSH</systemitem>. If the key ID was, for example, 10 then the systems that act as clients must have a line in their configuration files in the following format: @@ -487,8 +487,8 @@ chronyc> <command>password HEX:A6CFC50C9C93AB6E5A19754C246242FC5471BCDF</command  -<section id="sect-Networking_Guide-Checking_if_chrony_is_installed"> - <title>Checking if chrony is installed</title> +<section id="sect-Checking_if_chrony_is_installed"> + <title>Checking If chrony Is Installed</title> <para> To check if <application>chrony</application> is installed, run the following command as root: <screen>~]# yum install chrony</screen> @@ -496,7 +496,7 @@ chronyc> <command>password HEX:A6CFC50C9C93AB6E5A19754C246242FC5471BCDF</command </para> </section> - <section id="sect-Networking_Guide-Installing_chrony"> + <section id="sect-Installing_chrony"> <title>Installing chrony</title> <para> To install <application>chrony</application>, run the following command as root: @@ -507,7 +507,7 @@ To install <application>chrony</application>, run the following command as root: <section id="sect-Checking_the_Status_of_chronyd"> - <title>Checking the Status of chronyd</title> + <title>Checking The Status Of chronyd</title> <para> To check the status of <systemitem class="daemon">chronyd</systemitem>, issue the following command: <screen>~]$ <command>systemctl status chronyd</command> @@ -516,7 +516,7 @@ chronyd.service - NTP client/server Active: active (running) since Wed 2013-06-12 22:23:16 CEST; 11h ago</screen> </para> </section> - <section id="sect-Networking_Guide-Starting_chronyd"> + <section id="sect-Starting_chronyd"> <title>Starting chronyd</title> <para> To start <systemitem class="daemon">chronyd</systemitem>, issue the following command as root: @@ -529,7 +529,7 @@ chronyd.service - NTP client/server <para> </para> </section> - <section id="sect-Networking_Guide-Stopping_chronyd"> + <section id="sect-Stopping_chronyd"> <title>Stopping chronyd</title> <para> To stop <systemitem class="daemon">chronyd</systemitem>, issue the following command as root: @@ -542,14 +542,14 @@ chronyd.service - NTP client/server </section> - <section id="sect-Networking_Guide-Checking_if_chrony_is_synchronized"> - <title>Checking if chrony is Synchronized</title> + <section id="sect-Checking_if_chrony_is_synchronized"> + <title>Checking If chrony Is Synchronized</title> <para> To check if <application>chrony</application> is synchronized, make use of the <command>tracking</command>, <command>sources</command>, and <command>sourcestats</command> commands. </para> - <section id="sect-Networking_Guide-Checking_chrony_tracking"> - <title>Checking chrony tracking</title> + <section id="sect-Checking_chrony_tracking"> + <title>Checking chrony Tracking</title> <para> To check chrony tracking, issue the following command: @@ -666,8 +666,8 @@ This is the total dispersion accumulated through all the computers back to the s </variablelist> </section> - <section id="sect-Networking_Guide-Checking_chrony_sources"> - <title>Checking chrony sources</title> + <section id="sect-Checking_chrony_sources"> + <title>Checking chrony Sources</title> <para> The sources command displays information about the current time sources that <systemitem class="daemon">chronyd</systemitem> is accessing. @@ -754,8 +754,8 @@ This shows the stratum of the source, as reported in its most recently received </para> </section> -<section id="sect-Networking_Guide-Checking_chrony_sourcestats"> - <title>Checking chrony sourcestats</title> +<section id="sect-Checking_chrony_Source_Statistics"> + <title>Checking chrony Source Statistics</title> <para> The <command>sourcestats</command> command displays information about the drift rate and offset estimation process for each of the sources currently being examined by <systemitem class="daemon">chronyd</systemitem>. @@ -841,8 +841,8 @@ This is the estimated error bounds on Freq (again in parts per million). </section> </section> -<section id="sect-Networking_Guide-Adjusting-the-System_Clock"> - <title>Manualy Adjusting the System Clock</title> +<section id="sect-Adjusting-the-System_Clock"> + <title>Manualy Adjusting The System Clock</title> <para> To update, or step, the system clock immediately, bypassing any adjustments in progress by slewing the clock, issue the following commands as root: <screen>~]# <command>chronyc</command> @@ -857,8 +857,8 @@ This is the estimated error bounds on Freq (again in parts per million). </para> </section> -<section id="sect-Networking_Guide-Setting_up_chrony_for_a_system_which_is_infrequently_connected"> - <title>Setting up chrony for a system which is infrequently connected</title> +<section id="sect-Setting_up_chrony_for_a_system_which_is_infrequently_connected"> + <title>Setting Up Chrony For A System Which Is Infrequently Connected</title> <para> This example is intended for systems which use dial-on-demand connections. The normal configuration should be sufficient for mobile and virtual devices which connect intermittently. First, review and confirm that the default settings in the <filename>/etc/chrony.conf</filename> are similar to the following: <screen>driftfile /var/lib/chrony/drift @@ -885,8 +885,8 @@ The <option>offline</option> option can be useful in preventing systems from try </orderedlist> </para> - <section id="sect-Networking_Guide-Configuring_chrony_to_connect_and_disconnect"> - <title>Configuring chrony to Connect and Disconnect</title> + <section id="sect-Configuring_chrony_to_connect_and_disconnect"> + <title>Configuring chrony To Connect And Disconnect</title> <para> Using your editor running as root, add the following to the <filename>/etc/ppp/ip-up</filename> file: <screen> @@ -913,8 +913,8 @@ offline </section> - <section id="sect-Networking_Guide-Setting_up_chrony_for_a_system_in_an_isolated_network"> - <title>Setting up chrony for a System in an Isolated Network</title> + <section id="sect-Setting_up_chrony_for_a_system_in_an_isolated_network"> + <title>Setting Up chrony For A System In An Isolated Network</title> <para> For a network that is never connected to the Internet, one computer is selected to be the master timeserver. The other computers are either direct clients of the master, or clients of clients. On the master, the drift file must be manually set with the average rate of drift of the system clock. If the master is rebooted it will obtain the time from surrounding systems and take an average to set its system clock. Thereafter it resumes applying adjustments based on the drift file. The drift file will be updated automatically when the <command>settime</command> command is used. </para> @@ -950,8 +950,8 @@ Where <systemitem class="ipaddress">192.0.2.123</systemitem> is the address of t </section> -<section id="sect-Networking_Guide-Using_chronyc_chronyc_to_control_cronyd"> - <title>Using chronyc to control cronyd</title> +<section id="sect-Using_chronyc_chronyc_to_control_cronyd"> + <title>Using chronyc To Control cronyd</title> <para> To make changes using the command line utility <application>chronyc</application> in interactive mode, enter the following command as root: <screen>~]# chronyc</screen> @@ -970,8 +970,8 @@ Where <systemitem class="ipaddress">192.0.2.123</systemitem> is the address of t </para> </section> -<section id="sect-Networking_Guide-Using_chronyc_for_remote_administration"> -<title>Using chronyc for remote administration</title> +<section id="sect-Using_chronyc_for_remote_administration"> +<title>Using chronyc For Remote Administration</title> <para> To configure <application>chrony</application> to connect to a remote instance of <systemitem class="daemon">chronyd</systemitem>, issue a command as root in the following format: <screen>~]# <command>chronyc <option>-h</option> <replaceable>hostname</replaceable></command></screen> @@ -1001,7 +1001,7 @@ Note that commands issued at the <application>chrony</application> command promp </section>  - <section id="sect-Networking_Guide-additional_resources"> + <section id="sect-additional_resources"> <title>Additional Resources</title> <para>

10 years, 10 months

1
0
0 / 0

[system-administrators-guide] Added the NetworkManager chapter to the preface.

by jhradile

commit b64281b99642f3f036f330c0f45293999ed53c15 Author: Jaromir Hradilek <jhradilek(a)redhat.com> Date: Mon Jul 1 14:50:50 2013 +0200 Added the NetworkManager chapter to the preface. en-US/Preface.xml | 2 -- 1 files changed, 0 insertions(+), 2 deletions(-) --- diff --git a/en-US/Preface.xml b/en-US/Preface.xml index 9eb64a3..25f1d90 100644 --- a/en-US/Preface.xml +++ b/en-US/Preface.xml @@ -89,11 +89,9 @@ <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>

10 years, 10 months

1
0
0 / 0

[system-administrators-guide] Ensured that the formatting of commands is consistent.

by jhradile

commit 4156430ad8c667dc782f18b9580e560eabb7b54e Author: Jaromir Hradilek <jhradilek(a)redhat.com> Date: Mon Jul 1 14:47:04 2013 +0200 Ensured that the formatting of commands is consistent. en-US/Configuring_NTP_using_the_Chrony_suite.xml | 6 +++--- 1 files changed, 3 insertions(+), 3 deletions(-) --- diff --git a/en-US/Configuring_NTP_using_the_Chrony_suite.xml b/en-US/Configuring_NTP_using_the_Chrony_suite.xml index 48c33fe..10c97d9 100644 --- a/en-US/Configuring_NTP_using_the_Chrony_suite.xml +++ b/en-US/Configuring_NTP_using_the_Chrony_suite.xml @@ -504,7 +504,7 @@ chronyc> <command>password HEX:A6CFC50C9C93AB6E5A19754C246242FC5471BCDF</command <title>Checking if chrony is Installed</title> <para> To check if <application>chrony</application> is installed, run the following command as root: - <screen>~]# yum install chrony</screen> + <screen>~]# <command>yum install chrony</command></screen> The default location for the <application>chrony</application> daemon is <filename>/usr/local/sbin/chronyd</filename>. </para> </section> @@ -513,7 +513,7 @@ chronyc> <command>password HEX:A6CFC50C9C93AB6E5A19754C246242FC5471BCDF</command <title>Installing chrony</title> <para> To install <application>chrony</application>, run the following command as root: - <screen>~]# yum install chrony -y</screen> + <screen>~]# <command>yum install chrony -y</command></screen> The default installation directory is <filename>/usr/local/sbin/</filename> </para> </section> @@ -983,7 +983,7 @@ Where <systemitem class="ipaddress">192.0.2.123</systemitem> is the address of t <title>Using chronyc to Control cronyd</title> <para> To make changes using the command line utility <application>chronyc</application> in interactive mode, enter the following command as root: - <screen>~]# chronyc</screen> + <screen>~]# <command>chronyc</command></screen> <application>chronyc</application> must run as root if some of the restricted commands are to be used. </para> <para>

10 years, 10 months

1
0
0 / 0

[system-administrators-guide] Corrected all titles to follow the same rules.

by jhradile

commit d456e49b25cfba363ebe2fc92557595bb1d8ba4d Author: Jaromir Hradilek <jhradilek(a)redhat.com> Date: Mon Jul 1 14:41:51 2013 +0200 Corrected all titles to follow the same rules. en-US/Configuring_NTP_using_the_Chrony_suite.xml | 32 +++++++++++----------- 1 files changed, 16 insertions(+), 16 deletions(-) --- diff --git a/en-US/Configuring_NTP_using_the_Chrony_suite.xml b/en-US/Configuring_NTP_using_the_Chrony_suite.xml index 0425fec..48c33fe 100644 --- a/en-US/Configuring_NTP_using_the_Chrony_suite.xml +++ b/en-US/Configuring_NTP_using_the_Chrony_suite.xml @@ -6,7 +6,7 @@  <chapter id="chap-Configuring_NTP_Using_the_chrony_Suite"> - <title>Configuring NTP Using The chrony Suite</title> + <title>Configuring NTP Using the chrony Suite</title> <para> Accurate time keeping is important for a number of reasons in IT. In networking for example, accurate time stamps in packets and logs are required. In Linux systems, the <systemitem class="protocol">NTP</systemitem> protocol is implemented by a daemon running in user space.</para> <para> @@ -16,13 +16,13 @@ There is a choice between the daemons <systemitem class="daemon">ntpd</systemitem> and <systemitem class="daemon">chronyd</systemitem>, which are available from the repos in the <package>ntp</package> and <package>chrony</package> packages respectively. This section describes the use of the <application>chrony</application> suite of utilities to update the daemon on systems that do not fit into the conventional permanently networked, always on, dedicated server category. </para> <section id="sect-Introduction_to_the_chrony_suite"> - <title>Introduction To The chrony Suite</title> + <title>Introduction to the chrony Suite</title> <para> <application>Chrony</application> consists of <systemitem class="daemon">chronyd</systemitem>, a daemon that runs in user space, and <application>chronyc</application>, a command line program for making adjustments to <systemitem class="daemon">chronyd</systemitem>. Systems which are not permanently connected, or not permanently powered up, take a relatively long time to adjust their system clocks using the <systemitem class="protocol">NTP</systemitem> time protocol. This is because many small corrections are made based on observations of the clocks drift and offset. Temperature changes, which may be significant when powering up a system, affect the stability of hardware clocks. Although adjustments begin within a few milliseconds of booting a system, acceptable accuracy may take anything from ten seconds from a warm restart to a number of hours depending on your requirements, operating environment and hardware. <application>chrony</application> is a different implementat ion of the <systemitem class="protocol">NTP</systemitem> protocol than <systemitem class="daemon">ntpd</systemitem>, it can adjust the system clock more rapidly. </para> <section id="sect-differences_between_ntpd_and_chronyd"> - <title>Differences Between ntpd And chronyd</title> + <title>Differences Between ntpd and chronyd</title> <para> One of the main differences between <systemitem class="daemon">ntpd</systemitem> and <systemitem class="daemon">chronyd</systemitem> is in the algorithms used to control the computer's clock. Things <systemitem class="daemon">chronyd</systemitem> can do better than <systemitem class="daemon">ntpd</systemitem> are: @@ -112,7 +112,7 @@ Things <systemitem class="daemon">ntpd</systemitem> can do that <systemitem clas </section> </section> <section id="sect-Understanding_chrony_and-its_configuration"> - <title>Understanding chrony And Its Configuration</title> + <title>Understanding chrony and Its Configuration</title> <para> </para> @@ -130,7 +130,7 @@ Things <systemitem class="daemon">ntpd</systemitem> can do that <systemitem clas </section> <section id="sect-Understanding_the_chrony_configuration_commands"> - <title>Understanding The chrony Configuration Commands</title> + <title>Understanding the chrony Configuration Commands</title> <para> <systemitem class="daemon">chronyd</systemitem>'s default config file is <filename>/etc/chrony.conf</filename>. The <option>-f</option> option can be used to specify an alternate config file path. Refer to the <systemitem class="daemon">chronyd</systemitem> man page for further options. We present here a selection of configuration options. For a complete list of the directives that can be used see <citetitle pubwork="webpage">http://chrony.tuxfamily.org/manual.html#Configuration-file</citetitle> <variablelist> @@ -409,7 +409,7 @@ Not all real-time clocks are supported as their code system-specific. </section> <section id="sect-Security_with_chronyc"> - <title>Security With chronyc</title> + <title>Security with chronyc</title> <para> As access to <application>chronyc</application> allows changing <systemitem class="daemon">chronyd</systemitem> just as editing the configuration files would, access to <application>chronyc</application> should be limited. Passwords or their hashes can be specified in the key file, to restrict the use of <application>chronyc</application>. One of the entries is used to restrict the use of operational commands and is referred to as the command key. In the default configuration, a random command key is generated automatically on start. It should not be necessary to specify or alter it manually.</para> <para>Other entries in the key file can be used as <systemitem class="protocol">NTP</systemitem> keys to authenticate packets received from remote <systemitem class="protocol">NTP</systemitem> servers or peers. The two sides need to share a key with identical ID, hash type and password in their key file. This requires manually creating the keys and copying them over a secure medium, such as <systemitem class="protocol">SSH</systemitem>. If the key ID was, for example, 10 then the systems that act as clients must have a line in their configuration files in the following format: @@ -501,7 +501,7 @@ chronyc> <command>password HEX:A6CFC50C9C93AB6E5A19754C246242FC5471BCDF</command <section id="sect-Checking_if_chrony_is_installed"> - <title>Checking If chrony Is Installed</title> + <title>Checking if chrony is Installed</title> <para> To check if <application>chrony</application> is installed, run the following command as root: <screen>~]# yum install chrony</screen> @@ -520,7 +520,7 @@ To install <application>chrony</application>, run the following command as root: <section id="sect-Checking_the_Status_of_chronyd"> - <title>Checking The Status Of chronyd</title> + <title>Checking the Status of chronyd</title> <para> To check the status of <systemitem class="daemon">chronyd</systemitem>, issue the following command: <screen>~]$ <command>systemctl status chronyd</command> @@ -556,7 +556,7 @@ chronyd.service - NTP client/server <section id="sect-Checking_if_chrony_is_synchronized"> - <title>Checking If chrony Is Synchronized</title> + <title>Checking if chrony is Synchronized</title> <para> To check if <application>chrony</application> is synchronized, make use of the <command>tracking</command>, <command>sources</command>, and <command>sourcestats</command> commands. </para> @@ -855,7 +855,7 @@ This is the estimated error bounds on Freq (again in parts per million). </section> <section id="sect-Adjusting-the-System_Clock"> - <title>Manualy Adjusting The System Clock</title> + <title>Manualy Adjusting the System Clock</title> <para> To update, or step, the system clock immediately, bypassing any adjustments in progress by slewing the clock, issue the following commands as root: <screen>~]# <command>chronyc</command> @@ -872,14 +872,14 @@ This is the estimated error bounds on Freq (again in parts per million). </section> <section id="sect-Setting_up_chrony_for_different_environments"> - <title>Setting up chrony For Different Environments</title> + <title>Setting Up chrony for Different Environments</title> <para> </para> <section id="sect-Setting_up_chrony_for_a_system_which_is_infrequently_connected"> - <title>Setting Up chrony For A System Which Is Infrequently Connected</title> + <title>Setting Up chrony for a System Which is Infrequently Connected</title> <para> This example is intended for systems which use dial-on-demand connections. The normal configuration should be sufficient for mobile and virtual devices which connect intermittently. First, review and confirm that the default settings in the <filename>/etc/chrony.conf</filename> are similar to the following: <screen>driftfile /var/lib/chrony/drift @@ -907,7 +907,7 @@ The <option>offline</option> option can be useful in preventing systems from try </para> <section id="sect-Configuring_chrony_to_connect_and_disconnect"> - <title>Configuring chrony To Connect And Disconnect</title> + <title>Configuring chrony to Connect and Disconnect</title> <para> Using your editor running as root, add the following to the <filename>/etc/ppp/ip-up</filename> file: <screen> @@ -935,7 +935,7 @@ offline <section id="sect-Setting_up_chrony_for_a_system_in_an_isolated_network"> - <title>Setting Up chrony For A System In An Isolated Network</title> + <title>Setting Up chrony for a System in an Isolated Network</title> <para> For a network that is never connected to the Internet, one computer is selected to be the master timeserver. The other computers are either direct clients of the master, or clients of clients. On the master, the drift file must be manually set with the average rate of drift of the system clock. If the master is rebooted it will obtain the time from surrounding systems and take an average to set its system clock. Thereafter it resumes applying adjustments based on the drift file. The drift file will be updated automatically when the <command>settime</command> command is used. </para> @@ -980,7 +980,7 @@ Where <systemitem class="ipaddress">192.0.2.123</systemitem> is the address of t <section id="sect-Using_chronyc_chronyc_to_control_cronyd"> - <title>Using chronyc To Control cronyd</title> + <title>Using chronyc to Control cronyd</title> <para> To make changes using the command line utility <application>chronyc</application> in interactive mode, enter the following command as root: <screen>~]# chronyc</screen> @@ -1000,7 +1000,7 @@ Where <systemitem class="ipaddress">192.0.2.123</systemitem> is the address of t </section> <section id="sect-Using_chronyc_for_remote_administration"> -<title>Using chronyc For Remote Administration</title> +<title>Using chronyc for Remote Administration</title> <para> To configure <application>chrony</application> to connect to a remote instance of <systemitem class="daemon">chronyd</systemitem>, issue a command as root in the following format: <screen>~]# <command>chronyc <option>-h</option> <replaceable>hostname</replaceable></command></screen>

10 years, 10 months

1
0
0 / 0

[system-administrators-guide] Updated the description of the Basic System Configuration part.

by jhradile

commit f8acba5200441dddffad6918d47a0b309862bc1a Author: Jaromir Hradilek <jhradilek(a)redhat.com> Date: Mon Jul 1 14:32:37 2013 +0200 Updated the description of the Basic System Configuration part. en-US/System_Administrators_Guide.xml | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) --- diff --git a/en-US/System_Administrators_Guide.xml b/en-US/System_Administrators_Guide.xml index edef757..ecf5a1f 100644 --- a/en-US/System_Administrators_Guide.xml +++ b/en-US/System_Administrators_Guide.xml @@ -11,7 +11,7 @@ <title>Basic System Configuration</title> <partintro> <para> - This part covers basic system administration tasks such as keyboard configuration, date and time configuration, and managing users and groups. + This part covers basic system administration tasks such as keyboard configuration, date and time configuration, installation and initial setup of an NTP server, and managing users and groups. </para> </partintro> <xi:include href="Configuring_the_Language_and_Keyboard.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />

10 years, 10 months

1
0
0 / 0

[system-administrators-guide] Added the Chrony chapter to the Preface.

by jhradile

commit 474ea3276af35cb165cc324c7595e10508149770 Author: Jaromir Hradilek <jhradilek(a)redhat.com> Date: Mon Jul 1 14:28:22 2013 +0200 Added the Chrony chapter to the Preface. en-US/Configuring_NTP_using_the_Chrony_suite.xml | 2 +- en-US/Preface.xml | 7 +++++-- 2 files changed, 6 insertions(+), 3 deletions(-) --- diff --git a/en-US/Configuring_NTP_using_the_Chrony_suite.xml b/en-US/Configuring_NTP_using_the_Chrony_suite.xml index b903cb9..0425fec 100644 --- a/en-US/Configuring_NTP_using_the_Chrony_suite.xml +++ b/en-US/Configuring_NTP_using_the_Chrony_suite.xml @@ -5,7 +5,7 @@ ]>  -<chapter id="chap-Networking_Guide-Configuring_NTP_using_the_chrony_suite"> +<chapter id="chap-Configuring_NTP_Using_the_chrony_Suite"> <title>Configuring NTP Using The chrony Suite</title> <para> Accurate time keeping is important for a number of reasons in IT. In networking for example, accurate time stamps in packets and logs are required. In Linux systems, the <systemitem class="protocol">NTP</systemitem> protocol is implemented by a daemon running in user space.</para> diff --git a/en-US/Preface.xml b/en-US/Preface.xml index 301f160..9eb64a3 100644 --- a/en-US/Preface.xml +++ b/en-US/Preface.xml @@ -53,13 +53,16 @@ <term><xref linkend="part-Basic_System_Configuration" /></term> <listitem> <para> - This part covers basic system administration tasks such as keyboard configuration, date and time configuration, and managing users and groups. + This part covers basic system administration tasks such as keyboard configuration, date and time configuration, installation and initial setup of an NTP server, and managing users and groups. </para> <para> <xref linkend="ch-Configuring_the_Language_and_Keyboard" /> covers basic language and keyboard setup. Read this chapter if you need to configure the language of your desktop, change the keyboard layout, or add the keyboard layout indicator to the panel. </para> <para> - <xref linkend="ch-Configuring_the_Date_and_Time" /> covers the configuration of the system date and time. Read this chapter if you need to change the date and time setup, or configure the system to synchronize the clock with a remote Network Time Protocol (NTP) server. + <xref linkend="ch-Configuring_the_Date_and_Time" /> covers the configuration of the system date and time. Read this chapter if you need to set or change the date and time. + </para> + <para> + <xref linkend="chap-Configuring_NTP_Using_the_chrony_Suite" /> covers the installation and configuration of the chrony suite, a client and a server for the Network Time Protocol (NTP). Read this chapter if you need to configure the system to synchronize the clock with a remote NTP server, or set up an NTP server on this system. </para> <para> <xref linkend="ch-Managing_Users_and_Groups" /> covers the management of users and groups in a graphical user interface and on the command line. Read this chapter if you need to manage users and groups on your system, or enable password aging.

10 years, 10 months

1
0
0 / 0

[system-administrators-guide/18] Prepared the book for a release.

by jhradile

commit 11ced91c719113103c9837332151f93228e5e6e7 Author: Jaromir Hradilek <jhradilek(a)redhat.com> Date: Mon Jul 1 14:18:02 2013 +0200 Prepared the book for a release. en-US/Book_Info.xml | 4 ++-- en-US/Revision_History.xml | 18 ++---------------- en-US/System_Administrators_Guide.ent | 6 +++--- 3 files changed, 7 insertions(+), 21 deletions(-) --- diff --git a/en-US/Book_Info.xml b/en-US/Book_Info.xml index 810ab0d..0e3039f 100644 --- a/en-US/Book_Info.xml +++ b/en-US/Book_Info.xml @@ -5,9 +5,9 @@ <title>System Administrator's Guide</title> <subtitle>Deployment, Configuration, and Administration of &MAJOROSVER;</subtitle> <productname>Fedora</productname> - <productnumber>17</productnumber> + <productnumber>18</productnumber> <edition>1</edition> - <pubsnumber>1</pubsnumber> + <pubsnumber>0</pubsnumber> <abstract> <para> The <citetitle pubwork="book">System Administrator's Guide</citetitle> documents relevant information regarding the deployment, configuration, and administration of &MAJOROSVER;. It is oriented towards system administrators with a basic understanding of the system. diff --git a/en-US/Revision_History.xml b/en-US/Revision_History.xml index ee8d20f..337bdd7 100644 --- a/en-US/Revision_History.xml +++ b/en-US/Revision_History.xml @@ -6,22 +6,8 @@ <simpara> <revhistory> <revision> - <revnumber>1-1</revnumber> - <date>Thu Aug 9 2012</date> - <author> - <firstname>Jaromír</firstname> - <surname>Hradílek</surname> - <email>jhradilek(a)redhat.com</email> - </author> - <revdescription> - <simplelist> - <member>Updated <xref linkend="ch-Network_Interfaces" />.</member> - </simplelist> - </revdescription> - </revision> - <revision> <revnumber>1-0</revnumber> - <date>Tue May 29 2012</date> + <date>Mon 01 Jul 2013</date> <author> <firstname>Jaromír</firstname> <surname>Hradílek</surname> @@ -29,7 +15,7 @@ </author> <revdescription> <simplelist> - <member>Fedora 17 release of the <citetitle>System Administrator's Guide</citetitle>.</member> + <member>Fedora 18 release of the <citetitle pubwork="book">System Administrator's Guide</citetitle>.</member> </simplelist> </revdescription> </revision> diff --git a/en-US/System_Administrators_Guide.ent b/en-US/System_Administrators_Guide.ent index 9e39e38..49d802f 100644 --- a/en-US/System_Administrators_Guide.ent +++ b/en-US/System_Administrators_Guide.ent @@ -1,12 +1,12 @@  <!ENTITY PRODUCT "Fedora Documentation"> <!ENTITY BOOKID "system-administrator's-guide"> -<!ENTITY YEAR "2012"> +<!ENTITY YEAR "2013"> <!ENTITY HOLDER "Red Hat, Inc. and others"> <!ENTITY BUGZILLA '<ulink url="https://bugzilla.redhat.com/enter_bug.cgi?product=&PRODUCT;&component...;" />'>  <!ENTITY MAJOROS "Fedora"> -<!ENTITY MAJOROSVER "Fedora 17"> +<!ENTITY MAJOROSVER "Fedora 18"> <!ENTITY OSORG "The Fedora Project"> -<!ENTITY PKGOS "fc17"> +<!ENTITY PKGOS "fc18">

10 years, 10 months

1
0
0 / 0

[system-administrators-guide] Improving the explanation of rtcsync directive & 11 minute mode.

by stephenw

commit 1d9d24d94ff9cfbbe6af3ee2e9800160c1058600 Author: Stephen Wadeley <swadeley(a)redhat.com> Date: Mon Jul 1 14:28:36 2013 +0200 Improving the explanation of rtcsync directive & 11 minute mode. en-US/Configuring_NTP_using_the_Chrony_suite.xml | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) --- diff --git a/en-US/Configuring_NTP_using_the_Chrony_suite.xml b/en-US/Configuring_NTP_using_the_Chrony_suite.xml index 57c11c0..b903cb9 100644 --- a/en-US/Configuring_NTP_using_the_Chrony_suite.xml +++ b/en-US/Configuring_NTP_using_the_Chrony_suite.xml @@ -866,7 +866,7 @@ This is the estimated error bounds on Freq (again in parts per million). </para> <para> - In &MAJOROS;, the real-time clock should not be manually adjusted as this would interfere with <application>chrony</application>'s need to measure the rate at which the real-time clock drifts if it was adjusted at random intervals. By default, <application>rtcsync</application> will inform the kernel the system clock is synchronized and the kernel will update the real-time clock in 11 minute intervals. + In &MAJOROS;, the real-time clock should not be manually adjusted as this would interfere with <application>chrony</application>'s need to measure the rate at which the real-time clock drifts if it was adjusted at random intervals. By default, the <application>rtcsync</application> directive is present in the <filename>/etc/chrony.conf</filename> file. This will inform the kernel the system clock is kept synchronized and the kernel will update the real-time clock every 11 minutes. </para> </section> </section>

10 years, 10 months

1
0
0 / 0

[install-guide] BZ#977749 - updated screenshots across the book for F19, removed a couple of unnecessary ones

by pbokoc

commit 15501008f4bc91d63a8ada4f61e6f559ed5ff954 Author: Petr Bokoc <pbokoc(a)redhat.com> Date: Mon Jul 1 12:57:14 2013 +0200 BZ#977749 - updated screenshots across the book for F19, removed a couple of unnecessary ones en-US/Account_Configuration_common-figure-1.xml | 2 +- en-US/Adding_Partitions-x86.xml | 2 +- en-US/Complete_common-figure-1.xml | 2 +- en-US/Create_Btrfs-x86.xml | 2 +- en-US/Create_LVM-x86.xml | 2 +- en-US/Create_Software_RAID-x86.xml | 2 +- en-US/Disk_Partitioning_Setup_common-figure-1.xml | 2 +- en-US/Disk_Partitioning_Setup_common-figure-2.xml | 2 +- en-US/Disk_Partitioning_Setup_common-figure-3.xml | 2 +- en-US/Encrypt_common-figure-1.xml | 2 +- en-US/Graphical_Installation_install-hub.xml | 2 +- en-US/Installation_Source-figure-1.xml | 2 +- en-US/Installing_Packages_common-figure-2.xml | 2 +- en-US/Key_Board_Configuration-x86.xml | 2 +- en-US/Language_Configuration-x86.xml | 2 +- en-US/Language_Support-x86.xml | 2 +- en-US/Netconfig_common-figure-1.xml | 2 +- en-US/Package_Selection-quickstart.xml | 2 +- en-US/Package_Selection-x86.xml | 2 +- en-US/Progress_Hub_common-figure-2.xml | 2 +- en-US/Reclaim_Space_common-figure-1.xml | 2 +- en-US/Specialized_Storage_Devices-x86.xml | 6 +++--- ...Specialized_Storage_Devices_common-figure-2.xml | 2 +- en-US/Time_Zone_common-figure-1.xml | 2 +- en-US/Write_changes_to_disk_common-figure-1.xml | 2 +- en-US/X86_Bootloader.xml | 2 +- en-US/firstboot-systemuser.xml | 14 +++++++------- en-US/images/accountconfig/rootpassword.png | Bin 11332 -> 19136 bytes en-US/images/boot/boot_screen.png | Bin 3846 -> 3477 bytes en-US/images/diskpartitioning/ddmain.png | Bin 34848 -> 42217 bytes en-US/images/diskpartitioning/write_changes.png | Bin 56984 -> 60639 bytes en-US/images/diskpartsetup/disk-setup.png | Bin 62038 -> 69784 bytes en-US/images/diskpartsetup/reclaim-space.png | Bin 128091 -> 119538 bytes .../images/firstboot/fb-createuser-usermanager.png | Bin 26854 -> 31772 bytes en-US/images/firstboot/fb-createuser.png | Bin 30124 -> 29339 bytes .../installationsource/installationsource.png | Bin 46443 -> 46769 bytes en-US/images/kbdconfig/keyboard.png | Bin 24156 -> 35323 bytes en-US/images/langselection/langselection-GUI.png | Bin 70009 -> 73007 bytes .../images/langselection/langselection-hub-GUI.png | Bin 65570 -> 73298 bytes en-US/images/netconfig/networkconfig.png | Bin 34495 -> 35707 bytes en-US/images/pkgselection/installing-packages.png | Bin 139391 -> 83054 bytes en-US/images/pkgselection/pkg-group.png | Bin 96768 -> 112580 bytes en-US/images/preinstallhub/preinstall_hub.png | Bin 59504 -> 66460 bytes en-US/images/reboot/reboot.png | Bin 24637 -> 31387 bytes en-US/images/timezone/timezone.png | Bin 278602 -> 175013 bytes 45 files changed, 35 insertions(+), 35 deletions(-) --- diff --git a/en-US/Account_Configuration_common-figure-1.xml b/en-US/Account_Configuration_common-figure-1.xml index 4b81f29..c6038fc 100644 --- a/en-US/Account_Configuration_common-figure-1.xml +++ b/en-US/Account_Configuration_common-figure-1.xml @@ -7,7 +7,7 @@ <title>Root Password</title> <mediaobject> <imageobject> - <imagedata fileref="images/accountconfig/rootpassword.png" format="PNG" width="444" /> + <imagedata fileref="images/accountconfig/rootpassword.png" format="PNG" scalefit="0" /> </imageobject> <textobject> <para> diff --git a/en-US/Adding_Partitions-x86.xml b/en-US/Adding_Partitions-x86.xml index af8d873..3d28f17 100644 --- a/en-US/Adding_Partitions-x86.xml +++ b/en-US/Adding_Partitions-x86.xml @@ -15,7 +15,7 @@ <title>Partitioning on x86, AMD64, and Intel 64 Systems</title> <mediaobject> <imageobject> - <imagedata fileref="images/diskpartitioning/ddmain.png" format="PNG" width="444" /> + <imagedata fileref="images/diskpartitioning/ddmain.png" format="PNG" scalefit="0" /> </imageobject> <textobject> <para> diff --git a/en-US/Complete_common-figure-1.xml b/en-US/Complete_common-figure-1.xml index 182a40e..be38e51 100644 --- a/en-US/Complete_common-figure-1.xml +++ b/en-US/Complete_common-figure-1.xml @@ -5,7 +5,7 @@ ]> <figure float="0" id="fig-reboot"><title>Packages installed</title> <mediaobject> - <imageobject><imagedata fileref="images/reboot/reboot.png" format="PNG" width="444"/></imageobject> + <imageobject><imagedata fileref="images/reboot/reboot.png" format="PNG" scalefit="0" /></imageobject> <textobject><para> The menu presented when the desktop loads, offering the choice to try Fedora or install it to the hard drive. </para> diff --git a/en-US/Create_Btrfs-x86.xml b/en-US/Create_Btrfs-x86.xml index 7ec5625..b9d9da4 100644 --- a/en-US/Create_Btrfs-x86.xml +++ b/en-US/Create_Btrfs-x86.xml @@ -22,7 +22,7 @@ <title>Configure a Btrfs volume</title> <mediaobject> <imageobject> - <imagedata fileref="images/diskpartitioning/btrfs.png" format="PNG" width="444" /> + <imagedata fileref="images/diskpartitioning/btrfs.png" format="PNG" width="660" /> </imageobject> <textobject> <para> diff --git a/en-US/Create_LVM-x86.xml b/en-US/Create_LVM-x86.xml index 6f8e592..64fa8af 100644 --- a/en-US/Create_LVM-x86.xml +++ b/en-US/Create_LVM-x86.xml @@ -14,7 +14,7 @@ <title>Configure a logical volume</title> <mediaobject> <imageobject> - <imagedata fileref="images/diskpartitioning/lvm-pv.png" format="PNG" width="444" /> + <imagedata fileref="images/diskpartitioning/lvm-pv.png" format="PNG" width="660" /> </imageobject> <textobject> <para> diff --git a/en-US/Create_Software_RAID-x86.xml b/en-US/Create_Software_RAID-x86.xml index 8d9454a..7ec136c 100644 --- a/en-US/Create_Software_RAID-x86.xml +++ b/en-US/Create_Software_RAID-x86.xml @@ -13,7 +13,7 @@ <title>Create a software RAID device</title> <mediaobject> <imageobject> - <imagedata fileref="images/diskpartitioning/software-raid.png" format="PNG" width="444" /> + <imagedata fileref="images/diskpartitioning/software-raid.png" format="PNG" width="660" /> </imageobject> <textobject> <para> diff --git a/en-US/Disk_Partitioning_Setup_common-figure-1.xml b/en-US/Disk_Partitioning_Setup_common-figure-1.xml index 7289905..79ff2e4 100644 --- a/en-US/Disk_Partitioning_Setup_common-figure-1.xml +++ b/en-US/Disk_Partitioning_Setup_common-figure-1.xml @@ -7,7 +7,7 @@ <title>Disk Partitioning Setup</title> <mediaobject> <imageobject> - <imagedata fileref="images/diskpartsetup/disk-setup.png" format="PNG" width="444" /> + <imagedata fileref="images/diskpartsetup/disk-setup.png" format="PNG" scalefit="0" /> </imageobject> <textobject> <para> diff --git a/en-US/Disk_Partitioning_Setup_common-figure-2.xml b/en-US/Disk_Partitioning_Setup_common-figure-2.xml index 214261b..08f1a58 100644 --- a/en-US/Disk_Partitioning_Setup_common-figure-2.xml +++ b/en-US/Disk_Partitioning_Setup_common-figure-2.xml @@ -7,7 +7,7 @@ <title>Installation Options dialog - sufficient space</title> <mediaobject> <imageobject> - <imagedata fileref="images/diskpartsetup/install-options.png" format="PNG" width="444" /> + <imagedata fileref="images/diskpartsetup/install-options.png" format="PNG" scalefit="0" /> </imageobject> <textobject> <para> diff --git a/en-US/Disk_Partitioning_Setup_common-figure-3.xml b/en-US/Disk_Partitioning_Setup_common-figure-3.xml index 5000c63..0d5c44a 100644 --- a/en-US/Disk_Partitioning_Setup_common-figure-3.xml +++ b/en-US/Disk_Partitioning_Setup_common-figure-3.xml @@ -7,7 +7,7 @@ <title>Installation Options dialog - insufficient space</title> <mediaobject> <imageobject> - <imagedata fileref="images/diskpartsetup/install-options-reclaim.png" format="PNG" width="444" /> + <imagedata fileref="images/diskpartsetup/install-options-reclaim.png" format="PNG" scalefit="0" /> </imageobject> <textobject> <para> diff --git a/en-US/Encrypt_common-figure-1.xml b/en-US/Encrypt_common-figure-1.xml index 601fc89..d88d317 100644 --- a/en-US/Encrypt_common-figure-1.xml +++ b/en-US/Encrypt_common-figure-1.xml @@ -7,7 +7,7 @@ <title> Enter passphrase for encrypted partition </title> <mediaobject> <imageobject> - <imagedata fileref="images/encrypt/passphrase.png" format="PNG" width="444" /> + <imagedata fileref="images/encrypt/passphrase.png" format="PNG" scalefit="0" /> </imageobject> <textobject> <para> diff --git a/en-US/Graphical_Installation_install-hub.xml b/en-US/Graphical_Installation_install-hub.xml index 5add350..5892ea2 100644 --- a/en-US/Graphical_Installation_install-hub.xml +++ b/en-US/Graphical_Installation_install-hub.xml @@ -14,7 +14,7 @@ <title>The Installation Summary Menu</title> <mediaobject> <imageobject> - <imagedata fileref="images/preinstallhub/preinstall_hub.png" format="PNG" width="444" /> + <imagedata fileref="images/preinstallhub/preinstall_hub.png" format="PNG" scalefit="0" /> </imageobject> <textobject> <para> diff --git a/en-US/Installation_Source-figure-1.xml b/en-US/Installation_Source-figure-1.xml index 988028d..376bc9b 100644 --- a/en-US/Installation_Source-figure-1.xml +++ b/en-US/Installation_Source-figure-1.xml @@ -7,7 +7,7 @@ <title>Installation source</title> <mediaobject> <imageobject> - <imagedata fileref="images/installationsource/installationsource.png" format="PNG" width="444" /> + <imagedata fileref="images/installationsource/installationsource.png" format="PNG" scalefit="0" /> </imageobject> <textobject> <para> diff --git a/en-US/Installing_Packages_common-figure-2.xml b/en-US/Installing_Packages_common-figure-2.xml index 05dafdf..5a49090 100644 --- a/en-US/Installing_Packages_common-figure-2.xml +++ b/en-US/Installing_Packages_common-figure-2.xml @@ -7,7 +7,7 @@ <title>Packages completed</title> <mediaobject> <imageobject> - <imagedata fileref="images/pkgselection/installing-packages.png" format="PNG" width="444" /> + <imagedata fileref="images/pkgselection/installing-packages.png" format="PNG" scalefit="0" /> </imageobject> <textobject> <para> diff --git a/en-US/Key_Board_Configuration-x86.xml b/en-US/Key_Board_Configuration-x86.xml index e5261a1..055701a 100644 --- a/en-US/Key_Board_Configuration-x86.xml +++ b/en-US/Key_Board_Configuration-x86.xml @@ -19,7 +19,7 @@ <title>Keyboard Configuration</title> <mediaobject> <imageobject> - <imagedata fileref="images/kbdconfig/keyboard.png" format="PNG" width="444" /> + <imagedata fileref="images/kbdconfig/keyboard.png" format="PNG" scalefit="0" /> </imageobject> <textobject> <para> diff --git a/en-US/Language_Configuration-x86.xml b/en-US/Language_Configuration-x86.xml index 9fdcb9d..e043f9f 100644 --- a/en-US/Language_Configuration-x86.xml +++ b/en-US/Language_Configuration-x86.xml @@ -21,7 +21,7 @@ <title>Language Configuration</title> <mediaobject> <imageobject> - <imagedata fileref="images/langselection/langselection-GUI.png" format="PNG" width="444" /> + <imagedata fileref="images/langselection/langselection-GUI.png" format="PNG" scalefit="0" /> </imageobject> <textobject> <para> diff --git a/en-US/Language_Support-x86.xml b/en-US/Language_Support-x86.xml index 77e6edb..c09ac7c 100644 --- a/en-US/Language_Support-x86.xml +++ b/en-US/Language_Support-x86.xml @@ -16,7 +16,7 @@ <title>Language Support</title> <mediaobject> <imageobject> - <imagedata fileref="images/langselection/langselection-hub-GUI.png" format="PNG" width="444" /> + <imagedata fileref="images/langselection/langselection-hub-GUI.png" format="PNG" scalefit="0" /> </imageobject> <textobject> <para> diff --git a/en-US/Netconfig_common-figure-1.xml b/en-US/Netconfig_common-figure-1.xml index 00a0b7e..ac4d5b9 100644 --- a/en-US/Netconfig_common-figure-1.xml +++ b/en-US/Netconfig_common-figure-1.xml @@ -7,7 +7,7 @@ <title>Network configuration</title> <mediaobject> <imageobject> - <imagedata fileref="images/netconfig/networkconfig.png" format="PNG" width="444" /> + <imagedata fileref="images/netconfig/networkconfig.png" format="PNG" scalefit="0" /> </imageobject> <textobject> <para> diff --git a/en-US/Package_Selection-quickstart.xml b/en-US/Package_Selection-quickstart.xml index 0e4b0ee..5c9b804 100644 --- a/en-US/Package_Selection-quickstart.xml +++ b/en-US/Package_Selection-quickstart.xml @@ -18,7 +18,7 @@ <title>Software Selection</title> <mediaobject> <imageobject> - <imagedata fileref="images/pkgselection/pkg-group.png" format="PNG" width="444" /> + <imagedata fileref="images/pkgselection/pkg-group.png" format="PNG" scalefit="0" /> </imageobject> <textobject> <xi:include href="Package_Selection_common-imagecap-1.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> diff --git a/en-US/Package_Selection-x86.xml b/en-US/Package_Selection-x86.xml index acf5094..285bad5 100644 --- a/en-US/Package_Selection-x86.xml +++ b/en-US/Package_Selection-x86.xml @@ -19,7 +19,7 @@ <title>Software Selection</title> <mediaobject> <imageobject> - <imagedata fileref="images/pkgselection/pkg-group.png" format="PNG" width="444" /> + <imagedata fileref="images/pkgselection/pkg-group.png" format="PNG" scalefit="0" /> </imageobject> <textobject> <xi:include href="Package_Selection_common-imagecap-1.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> diff --git a/en-US/Progress_Hub_common-figure-2.xml b/en-US/Progress_Hub_common-figure-2.xml index d2057dd..883aa9f 100644 --- a/en-US/Progress_Hub_common-figure-2.xml +++ b/en-US/Progress_Hub_common-figure-2.xml @@ -7,7 +7,7 @@ <title>Installing packages</title> <mediaobject> <imageobject> - <imagedata fileref="images/pkgselection/installing-packages.png" format="PNG" width="444" /> + <imagedata fileref="images/pkgselection/installing-packages.png" format="PNG" scalefit="0" /> </imageobject> <textobject> <para> diff --git a/en-US/Reclaim_Space_common-figure-1.xml b/en-US/Reclaim_Space_common-figure-1.xml index 2b0fd17..b6f8c93 100644 --- a/en-US/Reclaim_Space_common-figure-1.xml +++ b/en-US/Reclaim_Space_common-figure-1.xml @@ -7,7 +7,7 @@ <title>Reclaim disk space from existing filesystems</title> <mediaobject> <imageobject> - <imagedata fileref="images/diskpartsetup/reclaim-space.png" format="PNG" width="444" /> + <imagedata fileref="images/diskpartsetup/reclaim-space.png" format="PNG" scalefit="0" /> </imageobject> <textobject> <para> diff --git a/en-US/Specialized_Storage_Devices-x86.xml b/en-US/Specialized_Storage_Devices-x86.xml index 1ab7b37..0c4d7db 100644 --- a/en-US/Specialized_Storage_Devices-x86.xml +++ b/en-US/Specialized_Storage_Devices-x86.xml @@ -6,9 +6,9 @@ <section id="sect-Storage_Device_Selection_Screen-x86"> <xi:include href="Specialized_Storage_Devices_common-title.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />  <xi:include href="Specialized_Storage_Devices_common-para-1.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> -  <xi:include href="Specialized_Storage_Devices_common-figure-4.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> -  <xi:include href="Specialized_Storage_Devices_common-figure-5.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> -  <xi:include href="Specialized_Storage_Devices_common-figure-1.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> +  +  +   <xi:include href="Specialized_Storage_Devices_common-para-2.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />  <xi:include href="Specialized_Storage_Devices_common-variablelist-1.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />  <para> diff --git a/en-US/Specialized_Storage_Devices_common-figure-2.xml b/en-US/Specialized_Storage_Devices_common-figure-2.xml index 264b900..ec9b43d 100644 --- a/en-US/Specialized_Storage_Devices_common-figure-2.xml +++ b/en-US/Specialized_Storage_Devices_common-figure-2.xml @@ -7,7 +7,7 @@ <title>The Storage Devices Search Tab</title> <mediaobject> <imageobject> - <imagedata fileref="images/storagedevices/searchstoragedevices.png" format="PNG" width="444" /> + <imagedata fileref="images/storagedevices/searchstoragedevices.png" format="PNG" /> </imageobject> <textobject> <para> diff --git a/en-US/Time_Zone_common-figure-1.xml b/en-US/Time_Zone_common-figure-1.xml index d024ea9..19ccb0b 100644 --- a/en-US/Time_Zone_common-figure-1.xml +++ b/en-US/Time_Zone_common-figure-1.xml @@ -7,7 +7,7 @@ <title>Configuring the Time Zone</title> <mediaobject> <imageobject> - <imagedata fileref="images/timezone/timezone.png" format="PNG" width="444" /> + <imagedata fileref="images/timezone/timezone.png" format="PNG" scalefit="0" /> </imageobject> <textobject> <para> diff --git a/en-US/Write_changes_to_disk_common-figure-1.xml b/en-US/Write_changes_to_disk_common-figure-1.xml index cbbc071..8103853 100644 --- a/en-US/Write_changes_to_disk_common-figure-1.xml +++ b/en-US/Write_changes_to_disk_common-figure-1.xml @@ -7,7 +7,7 @@ <title>Ready to install</title> <mediaobject> <imageobject> - <imagedata fileref="images/diskpartitioning/write_changes.png" format="PNG" width="444" /> + <imagedata fileref="images/diskpartitioning/write_changes.png" format="PNG" width="660" /> </imageobject> <textobject> <para> diff --git a/en-US/X86_Bootloader.xml b/en-US/X86_Bootloader.xml index 1fda868..ec75c88 100644 --- a/en-US/X86_Bootloader.xml +++ b/en-US/X86_Bootloader.xml @@ -96,7 +96,7 @@ <title>Summary of selected disks</title> <mediaobject> <imageobject> - <imagedata fileref="images/x86-bootloader/x86-bootloader.png" format="PNG" width="444" /> + <imagedata fileref="images/x86-bootloader/x86-bootloader.png" format="PNG" scalefit="0" /> </imageobject> <textobject> <para> diff --git a/en-US/firstboot-systemuser.xml b/en-US/firstboot-systemuser.xml index 6d13e65..033d62a 100644 --- a/en-US/firstboot-systemuser.xml +++ b/en-US/firstboot-systemuser.xml @@ -12,14 +12,14 @@ Create a user account for yourself with this screen. Always use this account to log in to your Fedora system, rather than using the <systemitem class="username">root</systemitem> account. </para> - <figure float="0"><title>Firstboot create user screen</title> + <figure float="0"><title>The Create User screen</title> <mediaobject> - <imageobject><imagedata fileref="images/firstboot/fb-createuser.png" format="PNG" width="444"/></imageobject> + <imageobject><imagedata fileref="images/firstboot/fb-createuser.png" format="PNG" scalefit="0" /></imageobject> <textobject><para> - Firstboot create user screen + The Create User screen </para> </textobject> - </mediaobject> + </mediaobject> </figure> @@ -36,11 +36,11 @@ To create additional users or customise your first user account, click <guibutton>Advanced</guibutton> to open the <application>User Manager</application>. </para> - <figure float="0" condition="install-guide"><title>User Manager</title> + <figure float="0" condition="install-guide"><title>Advanced User Configuration</title> <mediaobject> - <imageobject><imagedata fileref="images/firstboot/fb-createuser-usermanager.png" format="PNG" width="444"/></imageobject> + <imageobject><imagedata fileref="images/firstboot/fb-createuser-usermanager.png" format="PNG" scalefit="0" /></imageobject> <textobject><para> - Firstboot user manager screen + Advanced User Configuration </para> </textobject> </mediaobject> diff --git a/en-US/images/accountconfig/rootpassword.png b/en-US/images/accountconfig/rootpassword.png index 3000975..b3d812a 100644 Binary files a/en-US/images/accountconfig/rootpassword.png and b/en-US/images/accountconfig/rootpassword.png differ diff --git a/en-US/images/boot/boot_screen.png b/en-US/images/boot/boot_screen.png index 8752608..56bdca0 100644 Binary files a/en-US/images/boot/boot_screen.png and b/en-US/images/boot/boot_screen.png differ diff --git a/en-US/images/diskpartitioning/ddmain.png b/en-US/images/diskpartitioning/ddmain.png index 4cb827d..9226a0a 100644 Binary files a/en-US/images/diskpartitioning/ddmain.png and b/en-US/images/diskpartitioning/ddmain.png differ diff --git a/en-US/images/diskpartitioning/write_changes.png b/en-US/images/diskpartitioning/write_changes.png index 60d3ece..7225801 100644 Binary files a/en-US/images/diskpartitioning/write_changes.png and b/en-US/images/diskpartitioning/write_changes.png differ diff --git a/en-US/images/diskpartsetup/disk-setup.png b/en-US/images/diskpartsetup/disk-setup.png index 0d36f11..2a007ea 100644 Binary files a/en-US/images/diskpartsetup/disk-setup.png and b/en-US/images/diskpartsetup/disk-setup.png differ diff --git a/en-US/images/diskpartsetup/reclaim-space.png b/en-US/images/diskpartsetup/reclaim-space.png index 6f30d9f..23cc71f 100644 Binary files a/en-US/images/diskpartsetup/reclaim-space.png and b/en-US/images/diskpartsetup/reclaim-space.png differ diff --git a/en-US/images/firstboot/fb-createuser-usermanager.png b/en-US/images/firstboot/fb-createuser-usermanager.png index 01c75fb..7b66cbd 100644 Binary files a/en-US/images/firstboot/fb-createuser-usermanager.png and b/en-US/images/firstboot/fb-createuser-usermanager.png differ diff --git a/en-US/images/firstboot/fb-createuser.png b/en-US/images/firstboot/fb-createuser.png index 7a9a088..6ed84f3 100644 Binary files a/en-US/images/firstboot/fb-createuser.png and b/en-US/images/firstboot/fb-createuser.png differ diff --git a/en-US/images/installationsource/installationsource.png b/en-US/images/installationsource/installationsource.png index 9dea80f..a798d62 100644 Binary files a/en-US/images/installationsource/installationsource.png and b/en-US/images/installationsource/installationsource.png differ diff --git a/en-US/images/kbdconfig/keyboard.png b/en-US/images/kbdconfig/keyboard.png index 2ca248e..e9044e8 100644 Binary files a/en-US/images/kbdconfig/keyboard.png and b/en-US/images/kbdconfig/keyboard.png differ diff --git a/en-US/images/langselection/langselection-GUI.png b/en-US/images/langselection/langselection-GUI.png index 106cba9..80291bb 100644 Binary files a/en-US/images/langselection/langselection-GUI.png and b/en-US/images/langselection/langselection-GUI.png differ diff --git a/en-US/images/langselection/langselection-hub-GUI.png b/en-US/images/langselection/langselection-hub-GUI.png index 63a8f1a..20e2d7b 100644 Binary files a/en-US/images/langselection/langselection-hub-GUI.png and b/en-US/images/langselection/langselection-hub-GUI.png differ diff --git a/en-US/images/netconfig/networkconfig.png b/en-US/images/netconfig/networkconfig.png index 3e38ec9..600dfd0 100644 Binary files a/en-US/images/netconfig/networkconfig.png and b/en-US/images/netconfig/networkconfig.png differ diff --git a/en-US/images/pkgselection/installing-packages.png b/en-US/images/pkgselection/installing-packages.png index e5cf103..33c0fa6 100644 Binary files a/en-US/images/pkgselection/installing-packages.png and b/en-US/images/pkgselection/installing-packages.png differ diff --git a/en-US/images/pkgselection/pkg-group.png b/en-US/images/pkgselection/pkg-group.png index e521b83..ccde876 100644 Binary files a/en-US/images/pkgselection/pkg-group.png and b/en-US/images/pkgselection/pkg-group.png differ diff --git a/en-US/images/preinstallhub/preinstall_hub.png b/en-US/images/preinstallhub/preinstall_hub.png index 6a7bb71..ae67ba3 100644 Binary files a/en-US/images/preinstallhub/preinstall_hub.png and b/en-US/images/preinstallhub/preinstall_hub.png differ diff --git a/en-US/images/reboot/reboot.png b/en-US/images/reboot/reboot.png index 0f5dcaa..96fccd0 100644 Binary files a/en-US/images/reboot/reboot.png and b/en-US/images/reboot/reboot.png differ diff --git a/en-US/images/timezone/timezone.png b/en-US/images/timezone/timezone.png index a0e5508..6a26b9f 100644 Binary files a/en-US/images/timezone/timezone.png and b/en-US/images/timezone/timezone.png differ

10 years, 10 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 July 2013