[cloud-guide] minor restructuring, fixing markup
by Pete Travis
commit c8e6e0a8090bb36deef0d250cc057e539dbfff63
Author: Pete Travis <immanetize(a)fedoraproject.org>
Date: Wed Oct 30 22:27:35 2013 -0600
minor restructuring, fixing markup
en-US/Introduction.xml | 28 ++++++++++++++++------------
1 files changed, 16 insertions(+), 12 deletions(-)
---
diff --git a/en-US/Introduction.xml b/en-US/Introduction.xml
index 01ea046..10053d6 100644
--- a/en-US/Introduction.xml
+++ b/en-US/Introduction.xml
@@ -16,11 +16,10 @@
There are various types of cloud services. The service models are defined by
how much of the computing stack is provided as a service, and how much is
provided to the user as a capabilty.</para>
- </section>
<section>
<title>Infrastructure as a Service</title>
<para>
- Infrastructure as a Service, or IaaS, is a service model that provides machine level resources to the user. The "infrastructure" consists of configurable storage, network connectivity, processing power, and a basic operating system image. The user then can configure the operating system to suit their needs, without the overhead required for management of the hardware and virtualization technology the operating system runs on.
+ Infrastructure as a Service (IaaS) is a service model that provides machine level resources to the user. The "infrastructure" consists of configurable storage, network connectivity, processing power, and a basic operating system image. The user then can configure the operating system to suit their needs, without the overhead required for management of the hardware and virtualization technology the operating system runs on.
</para>
<para>
Fedora works at the infrastructure layer, using Kernel Virtual Machine, or KVM technology, libvirt management tools, and more to provide hosting and failover suport for virtual machines.
@@ -29,7 +28,7 @@
<section>
<title>Platform as a Service</title>
<para>
- With the Platform as a Service, or Paas, service model, even more of the resources are provided as a service. The "platform" includes computing resources, a configured operating system, and services and software required by the user's application. The user is then only responsible for their application. For example, a mediawiki deployment would include PHP, a database server, a web server, and mediawiki itself, all preconfigured. The user then only has to take care of administrative work, like defining policies and user roles or populating the wiki with content.
+ With the Platform as a Service (PaaS) service model, even more of the resources are provided as a service. The "platform" includes computing resources, a configured operating system, and services and software required by the user's application. The user is then only responsible for their application. For example, a mediawiki deployment would include PHP, a database server, a web server, and mediawiki itself, all preconfigured. The user then only has to take care of administrative work, like defining policies and user roles or populating the wiki with content.
</para>
<para>
Fedora works at the platform layer, using OpenStack technology to provide a dynamic, scalable platform.
@@ -38,25 +37,30 @@
<section>
<title>Software as a Service</title>
<para>
- In the Software as a Service, or Saas, model, the service provider handles even configuration and management of the application. The user primarily acts as a consumer of the software, often on a subscription basis.
+ In the Software as a Service (Saas) model, the service provider handles even configuration and management of the application. The user primarily acts as a consumer of the software, often on a subscription basis.
</para>
<para>
Fedora offers a wide range of software, web applications and development tools that can be leveraged to enable a SaaS endeavor.
</para>
</section>
- <example>
- <title>Understanding Iaas, Paas, and Saas: Email in the Cloud</title>
- <para>
- Email communication is vital to modern communication, and a good example of functionality that might be partially or wholly provided as a service. Examine how an organization might handle email in the cloud:
- </para>
- <para>
+ <section>
+ <title>Understanding Iaas, Paas, and Saas: Email in the Cloud</title>
+
+ <example>
+ <title>Understanding Iaas, Paas, and Saas: Email in the Cloud</title>
+ <para>
+ Email communication is vital to modern communication, and a good example of functionality that might be partially or wholly provided as a service. Examine how an organization might handle email in the cloud:
+ </para>
+ <para>
<emphasis>IaaS</emphasis>: The organization deploys mailservers on virtual machines. The maintenance and management of the mailservers and underlying operating system is still their responsibility, but they don't have the overhead of purchasing hardware, dealing with hardware or network failure, or managing storage.
</para>
<para>
- <emphasis>PaaS</emphasis>: The organization manages mailservers that are provided as a service. They are still responsible for management tasks, like configuration of the mailserver and user management, but they don't have to worry about the operating system or mailserver software.
+ <emphasis>PaaS</emphasis>: The organization manages mailservers that are provided as a service. They are still responsible for management tasks, like configuration of the mailserver and user management, but they don't have to worry about the operating system or mailserver platform.
</para>
<para>
<emphasis>SaaS</emphasis>: The organization receives all mail services as a service. They are responsible only for providing usage policies or similar information; all support and maintenance are handled by the service provider.
</para>
- </example>
+ </example>
+ </section>
+ </section>
</section>
9 years, 10 months
[release-notes] fixing typo
by Pete Travis
commit 48ce512b540e035f84d6212732aa6920c796b10f
Author: Pete Travis <immanetize(a)fedoraproject.org>
Date: Wed Oct 30 21:59:54 2013 -0600
fixing typo
en-US/File_Systems.xml | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
---
diff --git a/en-US/File_Systems.xml b/en-US/File_Systems.xml
index 1a7772f..7eadc1e 100644
--- a/en-US/File_Systems.xml
+++ b/en-US/File_Systems.xml
@@ -22,7 +22,7 @@
<note>
<title>Make backups!</title>
<para>
- Always back up your data before making low level changes, such as migrating to a bcache device. Until tools like <ulink url="https://github.com/g2p/blocks">blocks</ulink> are packaged for Fedora, users are advised to implement bcache by creating clean bcache devices and populating thier filesystems from a recent backup.
+ Always back up your data before making low level changes, such as migrating to a bcache device. Until tools like <ulink url="https://github.com/g2p/blocks">blocks</ulink> are packaged for Fedora, users are advised to implement bcache by creating clean bcache devices and populating their filesystems from a recent backup.
</para>
</note>
<para>
9 years, 10 months
[release-notes] added admonition for bcache best practices based on feedback from change owner
by Pete Travis
commit 63b483d7269743078609eaec74662f3fc57a71da
Author: Pete Travis <immanetize(a)fedoraproject.org>
Date: Wed Oct 30 21:30:24 2013 -0600
added admonition for bcache best practices based on feedback from change owner
en-US/File_Systems.xml | 11 +++++++----
1 files changed, 7 insertions(+), 4 deletions(-)
---
diff --git a/en-US/File_Systems.xml b/en-US/File_Systems.xml
index 0917485..1a7772f 100644
--- a/en-US/File_Systems.xml
+++ b/en-US/File_Systems.xml
@@ -17,8 +17,14 @@
<see>bcache</see>
</indexterm>
<para>
- Fedora 20 offers experimental support for adding solid state drives as fast, transparent caches to traditional rotating storage. Filesystems on the cache-backed block devices offer both speed and volume. The cache can be added to fresh or existing standard partitions and LVM storage.
+ Fedora 20 offers experimental support for adding solid state drives (SSDs) as fast, transparent caches to traditional rotating storage (HDDs). Filesystems on the SSD cached block devices offer both the speed of SSDs and volume of HDDs. Both traditional and LVM partitioning schemes can benefit from this functionality.
</para>
+ <note>
+ <title>Make backups!</title>
+ <para>
+ Always back up your data before making low level changes, such as migrating to a bcache device. Until tools like <ulink url="https://github.com/g2p/blocks">blocks</ulink> are packaged for Fedora, users are advised to implement bcache by creating clean bcache devices and populating thier filesystems from a recent backup.
+ </para>
+ </note>
<para>
Learn more about this functionality, called <firstterm>bcache</firstterm>, from:
<simplelist>
@@ -34,9 +40,6 @@
<member>
<ulink url="https://fedoraproject.org/wiki/Test_Day:2013-10-13_SSD_Cache" />
</member>
- <member>
- <ulink url="https://github.com/g2p/blocks" />
- </member>
</simplelist>
</para>
9 years, 10 months
[release-notes] updating google-noto-fonts info per BZ#1023858
by Pete Travis
commit 1d281c3387613d64496a530f46bdee9d528bebfe
Author: Pete Travis <immanetize(a)fedoraproject.org>
Date: Wed Oct 30 21:02:58 2013 -0600
updating google-noto-fonts info per BZ#1023858
en-US/I18n.xml | 79 ++++++++++++++++++++++++++-----------------------------
1 files changed, 37 insertions(+), 42 deletions(-)
---
diff --git a/en-US/I18n.xml b/en-US/I18n.xml
index 5a4b075..ced420d 100644
--- a/en-US/I18n.xml
+++ b/en-US/I18n.xml
@@ -18,7 +18,7 @@
<systemitem>ibus-rime</systemitem> is a new Rime input method engine for Linux/IBus.
</para>
<para>
- <systemitem>ibus-typing-booster</systemitem>, <systemitem>latn-post</systemitem>, <systemitem>latn-pre</systemitem> input methods are not blacklisted anymore.
+ <systemitem>ibus-typing-booster</systemitem>, <systemitem>latn-post</systemitem>, and <systemitem>latn-pre</systemitem> input methods are not blacklisted anymore.
</para>
</section>
<section id="i18n-fonttools">
@@ -45,48 +45,43 @@
<productname>mph-2b-damase-fonts</productname> is a new package. Mark Williamson's MPH 2B Damase is a free font for many non-Latin scripts encoding.
</para>
<para>
- <productname>google-noto-fonts</productname> script coverage is increased. Now it has additional subpackages listed as below:
+ <productname>google-noto-fonts</productname> script coverage is increased. It now has support for additional scripts, as listed below:
<simplelist>
- <member>google-noto-sans-avestan-fonts</member>
- <member>google-noto-sans-bengali-fonts</member>
- <member>google-noto-sans-bengali-ui-fonts</member>
- <member>google-noto-sans-brahmi-fonts</member>
- <member>google-noto-sans-carian-fonts</member>
- <member>google-noto-sans-cherokee-fonts</member>
- <member>google-noto-sans-coptic-fonts</member>
- <member>google-noto-sans-deseret-fonts</member>
- <member>google-noto-sans-egyptian-hieroglyphs-fonts</member>
- <member>google-noto-sans-glagolitic-fonts</member>
- <member>google-noto-sans-gujarati-fonts</member>
- <member>google-noto-sans-gujarati-ui-fonts</member>
- <member>google-noto-sans-hanunno-fonts</member>
- <member>google-noto-sans-imperial-aramaic-fonts</member>
- <member>google-noto-sans-kaithi-fonts</member>
- <member>google-noto-sans-kannada-fonts</member>
- <member>google-noto-sans-kannada-ui-fonts</member>
- <member>google-noto-sans-kayah-li-fonts</member>
- <member>google-noto-sans-kharoshthi-fonts</member>
- <member>google-noto-sans-lisu-fonts</member>
- <member>google-noto-sans-lycian-fonts</member>
- <member>google-noto-sans-lydian-fonts</member>
- <member>google-noto-sans-malayalam-fonts</member>
- <member>google-noto-sans-malayalam-ui-fonts</member>
- <member>google-noto-sans-mandaic-fonts</member>
- <member>google-noto-sans-meeteimayek-fonts</member>
- <member>google-noto-sans-nko-fonts</member>
- <member>google-noto-sans-old-south-arabian-fonts</member>
- <member>google-noto-sans-old-turkic-fonts</member>
- <member>google-noto-sans-osmanya-fonts</member>
- <member>google-noto-sans-phoenician-fonts</member>
- <member>google-noto-sans-shavian-fonts</member>
- <member>google-noto-sans-symbols-fonts</member>
- <member>google-noto-sans-tagalog-fonts</member>
- <member>google-noto-sans-tai-tham-fonts</member>
- <member>google-noto-sans-tai-viet-fonts</member>
- <member>google-noto-sans-telugu-fonts</member>
- <member>google-noto-sans-telugu-ui-fonts</member>
- <member>google-noto-sans-ugaritic-fonts</member>
- <member>google-noto-sans-vai-fonts</member>
+ <member>Avestan</member>
+ <member>Bengali</member>
+ <member>Brahmi</member>
+ <member>Carian</member>
+ <member>Cherokee</member>
+ <member>Coptic</member>
+ <member>Deseret</member>
+ <member>Egyptian Hieroglyphs</member>
+ <member>Glagolitic</member>
+ <member>Gujarati</member>
+ <member>Hanunno</member>
+ <member>Imperial Aramaic</member>
+ <member>Kaithi</member>
+ <member>Kannada</member>
+ <member>KayahLi</member>
+ <member>Kharoshthi</member>
+ <member>Lisu</member>
+ <member>Lycian</member>
+ <member>Lydian</member>
+ <member>Malayalam</member>
+ <member>Mandaic</member>
+ <member>Meeteimayek</member>
+ <member>Nko</member>
+ <member>Old-south-Arabian</member>
+ <member>Old Turkic</member>
+ <member>Osmanya</member>
+ <member>Phoenician</member>
+ <member>Shavian</member>
+ <member>Symbols</member>
+ <member>Tagalog</member>
+ <member>Tai Tham</member>
+ <member>Tai Viet</member>
+ <member>Telugu</member>
+ <member>Ugaritic</member>
+ <member>Vai</member>
</simplelist>
</para>
<para>
9 years, 10 months
[system-administrators-guide] Bug 1011418 - alias bondN bonding not required for bonding configuration
by stephenw
commit 5272ada1f8a0ed4f77054b1b52774dabebbcac18
Author: Stephen Wadeley <swadeley(a)redhat.com>
Date: Wed Oct 30 21:21:57 2013 +0100
Bug 1011418 - alias bondN bonding not required for bonding configuration
en-US/Network_Interfaces.xml | 8 +-------
en-US/Working_with_Kernel_Modules.xml | 6 +-----
2 files changed, 2 insertions(+), 12 deletions(-)
---
diff --git a/en-US/Network_Interfaces.xml b/en-US/Network_Interfaces.xml
index 41f4757..39d2f02 100644
--- a/en-US/Network_Interfaces.xml
+++ b/en-US/Network_Interfaces.xml
@@ -1828,13 +1828,7 @@ USERCTL=no</programlisting>
<para>
In this example, replace <replaceable>N</replaceable> with the numerical value for the interface.
</para>
- <para>
- For a channel bonding interface to be valid, the kernel module must be loaded. To ensure that the module is loaded when the channel bonding interface is brought up, create a new file as root named <filename><replaceable>bonding</replaceable>.conf</filename> in the <filename class="directory">/etc/modprobe.d/</filename> directory. Note that you can name this file anything you like as long as it ends with a <filename class="extension">.conf</filename> extension. Insert the following line in this new file:
- </para>
- <programlisting>alias bond<replaceable>N</replaceable> bonding</programlisting>
- <para>
- Replace <replaceable>N</replaceable> with the interface number, such as <literal>0</literal>. For each configured channel bonding interface, there must be a corresponding entry in your new <filename>/etc/modprobe.d/<replaceable>bonding</replaceable>.conf</filename> file.
- </para>
+
<important>
<title>Put all bonding module parameters in ifcfg-bondN files</title>
<para>
diff --git a/en-US/Working_with_Kernel_Modules.xml b/en-US/Working_with_Kernel_Modules.xml
index 40c70b5..5900909 100644
--- a/en-US/Working_with_Kernel_Modules.xml
+++ b/en-US/Working_with_Kernel_Modules.xml
@@ -563,11 +563,7 @@ fi</programlisting>
<orderedlist
continuation="restarts"
inheritnum="ignore">
- <listitem>
- <para>As <systemitem class="username">root</systemitem>, create a new file named <filename><replaceable>bonding</replaceable>.conf</filename> in the <filename>/etc/modprobe.d/</filename> directory. Note that you can name this file anything you like as long as it ends with a <filename>.conf</filename> extension. Insert the following line in this new file:</para>
- <screen>alias bond<replaceable>N</replaceable> bonding</screen>
- <para>Replace <replaceable>N</replaceable> with the interface number, such as <command>0</command>. For each configured channel bonding interface, there must be a corresponding entry in your new <filename>/etc/modprobe.d/<replaceable>bonding</replaceable>.conf</filename> file.</para>
- </listitem>
+
<listitem>
<para>Configure a channel bonding interface as outlined in <xref
linkend="s2-networkscripts-interfaces-chan"/>.</para>
9 years, 10 months
[system-administrators-guide] Fixing links and titles to use title case en-US/Configuring_NTP_Using_ntpd.xml
by stephenw
commit 4fbe3cf623b31a8ae99df53caecafddb9d5bf455
Author: Stephen Wadeley <swadeley(a)redhat.com>
Date: Wed Oct 30 20:55:42 2013 +0100
Fixing links and titles to use title case
en-US/Configuring_NTP_Using_ntpd.xml
en-US/Configuring_NTP_Using_ntpd.xml | 15 +++++++--------
1 files changed, 7 insertions(+), 8 deletions(-)
---
diff --git a/en-US/Configuring_NTP_Using_ntpd.xml b/en-US/Configuring_NTP_Using_ntpd.xml
index 287837c..457a9bc 100644
--- a/en-US/Configuring_NTP_Using_ntpd.xml
+++ b/en-US/Configuring_NTP_Using_ntpd.xml
@@ -16,7 +16,6 @@
<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. Logs are used to investigate service and security issues and so timestamps made on different systems must be made by synchronized clocks to be of real value. As systems and networks become increasingly faster, there is a corresponding need for clocks with greater accuracy and resolution. In some countries there are legal obligations to keep accurately synchronized clocks. Please see <citetitle pubwork="webpage">www.ntp.org</citetitle> for more information. In Linux systems, <systemitem class="protocol">NTP</systemitem> is implemented by a daemon running in user space. The default <systemitem class="protocol">NTP</systemitem> user space daemon in &MAJOROSVER; is <systemitem class="service">chronyd</systemitem>. It must be disabled if you want to use the <systemitem class="service">ntpd</systemitem> daemon. See <xref linkend=
"ch-Configuring_NTP_Using_the_chrony_Suite" /> for information on <application>chrony</application>.
</para>
-
<para>
The user space daemon updates the system clock, which is a software clock running in the kernel. Linux uses a software clock as its system clock for better resolution than the typical embedded hardware clock referred to as the <quote><firstterm>Real Time Clock</firstterm></quote> <acronym>(RTC)</acronym>. See the <filename>rtc(4)</filename> and <filename>hwclock(8)</filename> man pages for information on hardware clocks. The system clock can keep time by using various clock sources. Usually, the <firstterm>Time Stamp Counter</firstterm> (<acronym>TSC</acronym>) is used. The TSC is a CPU register which counts the number of cycles since it was last reset. It is very fast, has a high resolution, and there are no interrupts. On system start, the system clock reads the time and date from the RTC. The time kept by the RTC will drift away from actual time by up to 5 minutes per month due to temperature variations. Hence the need for the system clock to be constantly synchroni
zed with external time references and to update the RTC on system shut down. When the system clock is being synchronized by <systemitem class="service">ntpd</systemitem>, the kernel will in turn update the RTC every 11 minutes automatically.
</para>
@@ -140,7 +139,7 @@
</section>
<section id="s1-Understanding_the_drift_file">
- <title>Understanding The Drift File</title>
+ <title>Understanding the Drift File</title>
<para>
The drift file is used to store the frequency offset between the system clock running at its nominal frequency and the frequency required to remain in synchronization with UTC. If present, the value contained in the drift file is read at system start and used to correct the clock source. Use of the drift file reduces the time required to achieve a stable and accurate time. The value is calculated, and the drift file replaced, once per hour by <systemitem class="daemon">ntpd</systemitem>. The drift file is replaced, rather than just updated, and for this reason the drift file must be in a directory for which the <systemitem class="daemon">ntpd</systemitem> has write permissions.
</para>
@@ -151,7 +150,7 @@
<title>UTC, Timezones, and DST</title>
<para>
- As <systemitem class="protocol">NTP</systemitem> is entirely in UTC (Universal Time, Coordinated), Timezones and DST (Daylight Saving Time) are applied locally by the system. The file <filename>/etc/localtime</filename> is a copy of, or symlink to, a zone information file from <filename>/usr/share/zoneinfo</filename>. The RTC may be in localtime or in UTC, as specified by the 3rd line of <filename>/etc/adjtime</filename>, which will be one of LOCAL or UTC to indicate how the RTC clock has been set. Users can easily change this setting using the checkbox <guilabel>System Clock Uses UTC</guilabel> in the <application>Date and Time</application> graphical configuration tool. See <xref linkend="ch-Configuring_the_Date_and_Time" /> for information on how to use that tool. Running the RTC in UTC is recommended to avoid various problems when daylight saving time is changed.
+ As <systemitem class="protocol">NTP</systemitem> is entirely in UTC (Universal Time, Coordinated), Timezones and DST (Daylight Saving Time) are applied locally by the system. The file <filename>/etc/localtime</filename> is a copy of, or symlink to, a zone information file from <filename>/usr/share/zoneinfo</filename>. The RTC may be in localtime or in UTC, as specified by the 3rd line of <filename>/etc/adjtime</filename>, which will be one of LOCAL or UTC to indicate how the RTC clock has been set. Users can easily change this setting using the checkbox <guilabel>System Clock Uses UTC</guilabel> in the <application>Date and Time</application> graphical configuration tool. See <xref linkend="ch-Configuring_the_Date_and_Time" /> for information on how to use that tool. Running the RTC in UTC is recommended to avoid various problems when daylight saving time is changed.
</para>
<para>
The operation of <systemitem class="service">ntpd</systemitem> is explained in more detail in the man page <filename>ntpd(8)</filename>. The resources section lists useful sources of information. See <xref linkend="s1-ntpd_additional-resources"/>.
@@ -304,7 +303,7 @@ To check the status of <systemitem class="daemon">chronyd</systemitem>, issue th
<section id="s1-Checking_if_ntpd_is_installed">
- <title>Checking If the NTP Daemon Is Installed</title>
+ <title>Checking if the NTP Daemon is Installed</title>
<para>
To check if <systemitem class="service">ntpd</systemitem> is installed, enter the following command as root:
<screen>~]# <command>yum install ntp</command></screen>
@@ -339,7 +338,7 @@ unsynchronised
time server re-starting
polling server every 64 s</screen>
<screen>~]$ <command>ntpstat</command>
-synchronised to NTP server (10.5.26.10) at stratum 2
+synchronised to NTP server (10.5.26.10) at stratum 2
time correct to within 52 ms
polling server every 1024 s</screen>
</para>
@@ -369,7 +368,7 @@ synchronised to NTP server (10.5.26.10) at stratum 2
<section id="s2-Change_the_firewall_settings">
- <title>Change The Firewall Settings</title>
+ <title>Change the Firewall Settings</title>
<para>
To immediately change the current firewall settings, ensure the current view is set to <guilabel>Runtime Configuration</guilabel>. Alternatively, to edit the settings to be applied at the next system start, or firewall reload, select <guilabel>Permanent Configuration</guilabel> from the drop-down list.
</para>
@@ -383,7 +382,7 @@ synchronised to NTP server (10.5.26.10) at stratum 2
</section>
<section id="s2-Open_Ports_in_the_firewall_for_ntp_packets">
- <title>Open Ports In The Firewall For NTP Packets</title>
+ <title>Open Ports in the Firewall for NTP Packets</title>
<para>
To permit traffic through the firewall to a certain port, start the <application>firewall-config</application> tool and select the network zone whose settings you want to change. Select the <guilabel>Ports</guilabel> tab and the click the <guibutton>Add</guibutton> button on the right hand side. The <guilabel>Port and Protocol</guilabel> window opens.
</para>
@@ -543,7 +542,7 @@ synchronised to NTP server (10.5.26.10) at stratum 2
</para>
<para>
- This command configures a system to act as an <systemitem class="protocol">NTP</systemitem> broadcast server. The address used must be a broadcast or a multicast address. Broadcast address implies the <systemitem class="protocol">IPv4</systemitem> address <systemitem class="ipaddress">255.255.255.255</systemitem>. By default, routers do not pass broadcast messages. The multicast address can be an <systemitem class="protocol">IPv4</systemitem> Class D address, or an <systemitem class="protocol">IPv6</systemitem> address. The IANA has assigned <systemitem class="protocol">IPv4</systemitem> multicast address <systemitem class="ipaddress">224.0.1.1</systemitem> and <systemitem class="protocol">IPv6</systemitem> address <systemitem class="ipaddress">FF05::101</systemitem> (site local) to <systemitem class="protocol">NTP</systemitem>. Administratively scoped<systemitem class="protocol">IPv4</systemitem> multicast addresses can also be used, as described in <ulink url="
http://www.rfc-editor.org/info/rfc2365"><citetitle pubwork="webpage">RFC 2365 Administratively Scoped IP Multicast</citetitle></ulink>.
+ This command configures a system to act as an <systemitem class="protocol">NTP</systemitem> broadcast server. The address used must be a broadcast or a multicast address. Broadcast address implies the <systemitem class="protocol">IPv4</systemitem> address <systemitem class="ipaddress">255.255.255.255</systemitem>. By default, routers do not pass broadcast messages. The multicast address can be an <systemitem class="protocol">IPv4</systemitem> Class D address, or an <systemitem class="protocol">IPv6</systemitem> address. The IANA has assigned <systemitem class="protocol">IPv4</systemitem> multicast address <systemitem class="ipaddress">224.0.1.1</systemitem> and <systemitem class="protocol">IPv6</systemitem> address <systemitem class="ipaddress">FF05::101</systemitem> (site local) to <systemitem class="protocol">NTP</systemitem>. Administratively scoped<systemitem class="protocol">IPv4</systemitem> multicast addresses can also be used, as described in <ulink url="h
ttp://www.rfc-editor.org/info/rfc2365"><citetitle pubwork="webpage">RFC 2365 Administratively Scoped IP Multicast</citetitle></ulink>.
</para>
</section>
9 years, 10 months
[system-administrators-guide] Improving the language
by stephenw
commit 1975ebd8a4ba080307675aa6ea7ed1f7bd8982a9
Author: Stephen Wadeley <swadeley(a)redhat.com>
Date: Wed Oct 30 20:45:28 2013 +0100
Improving the language
en-US/Preface.xml | 8 ++++----
en-US/System_Administrators_Guide.xml | 2 +-
2 files changed, 5 insertions(+), 5 deletions(-)
---
diff --git a/en-US/Preface.xml b/en-US/Preface.xml
index fe0add4..5a14469 100644
--- a/en-US/Preface.xml
+++ b/en-US/Preface.xml
@@ -32,7 +32,7 @@
</listitem>
<listitem>
<para>
- Easily working with kernel modules and upgrading the kernel
+ Working with kernel modules and upgrading the kernel
</para>
</listitem>
</itemizedlist>
@@ -98,7 +98,7 @@
<term><xref linkend="part-Infrastructure_Services" /></term>
<listitem>
<para>
- This part provides information how to configure services and daemons, configure authentication, and enable remote logins.
+ This part provides information on how to configure services and daemons, configure authentication, and enable remote logins.
</para>
<para>
<xref linkend="ch-Services_and_Daemons" /> covers the configuration of the services to be run when a system is started, and provides information on how to start, stop, and restart the services on the command line using the <command>systemctl</command> utility.
@@ -165,7 +165,7 @@
<xref linkend="ch-abrt" /> concentrates on <application>ABRT</application>, a system service and a set of tools to collect crash data and send a report to the relevant issue tracker. Read this chapter to learn how to use <application>ABRT</application> on your system.
</para>
<para>
- <xref linkend="ch-OProfile" /> covers <application>OProfile</application>, a low overhead, system-wide performance monitoring tool. Read this chapter for information how to use <application>OProfile</application> on your system.
+ <xref linkend="ch-OProfile" /> covers <application>OProfile</application>, a low overhead, system-wide performance monitoring tool. Read this chapter for information on how to use <application>OProfile</application> on your system.
</para>
</listitem>
</varlistentry>
@@ -176,7 +176,7 @@
This part covers various tools that assist administrators with kernel customization.
</para>
<para>
- <xref linkend="ch-Manually_Upgrading_the_Kernel" /> provides important information how to manually update a kernel package using the <command>rpm</command> command instead of <command>yum</command>. Read this chapter if you cannot update a kernel package with the <application>Yum</application> package manager.
+ <xref linkend="ch-Manually_Upgrading_the_Kernel" /> provides important information on how to manually update a kernel package using the <command>rpm</command> command instead of <command>yum</command>. Read this chapter if you cannot update a kernel package with the <application>Yum</application> package manager.
</para>
<para>
<xref linkend="ch-Working_with_Kernel_Modules" /> explains how to display, query, load, and unload kernel modules and their dependencies, and how to set module parameters. Additionally, it covers specific kernel module capabilities such as using multiple Ethernet cards and using channel bonding. Read this chapter if you need to work with kernel modules.
diff --git a/en-US/System_Administrators_Guide.xml b/en-US/System_Administrators_Guide.xml
index 646459b..4f4ca8b 100644
--- a/en-US/System_Administrators_Guide.xml
+++ b/en-US/System_Administrators_Guide.xml
@@ -44,7 +44,7 @@
<title>Infrastructure Services</title>
<partintro>
<para>
- This part provides information how to configure services and daemons, configure authentication, and enable remote logins.
+ This part provides information on how to configure services and daemons, configure authentication, and enable remote logins.
</para>
</partintro>
<xi:include href="Services_and_Daemons.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
9 years, 10 months
[system-administrators-guide] Removing the ntpdate section. Deprecated.
by stephenw
commit 3361c423be92efa2a77c037ab0416ee56e4a49bf
Author: Stephen Wadeley <swadeley(a)redhat.com>
Date: Wed Oct 30 20:43:59 2013 +0100
Removing the ntpdate section. Deprecated.
en-US/Configuring_NTP_Using_ntpd.xml | 28 ----------------------------
1 files changed, 0 insertions(+), 28 deletions(-)
---
diff --git a/en-US/Configuring_NTP_Using_ntpd.xml b/en-US/Configuring_NTP_Using_ntpd.xml
index cfd651b..287837c 100644
--- a/en-US/Configuring_NTP_Using_ntpd.xml
+++ b/en-US/Configuring_NTP_Using_ntpd.xml
@@ -394,34 +394,6 @@ synchronised to NTP server (10.5.26.10) at stratum 2
</section>
-<section id="s1-Configure_ntpdate_servers">
- <title>Configure ntpdate Servers</title>
- <para>
- The purpose of the <systemitem class="daemon">ntpdate</systemitem> service is to set the clock during system boot. This can be used to ensure that the services started after <systemitem class="daemon">ntpdate</systemitem> will have the correct time and will not observe a jump in the clock. The use of <systemitem class="daemon">ntpdate</systemitem> and the list of step-tickers is considered deprecated and so <application>Red Hat Enterprise Linux 6</application> uses the <option>-g</option> option to the <command>ntpd</command> command by default and not <systemitem class="daemon">ntpdate</systemitem>. However, the <option>-g</option> option only enables <systemitem class="daemon">ntpd</systemitem> to ignore the offset limit of 1000s and attempt to synchronize the time. It does not guarantee the time will be correct when other programs or services are started. Therefore the <systemitem class="daemon">ntpdate</systemitem> service can be useful when <systemitem class="daemo
n">ntpd</systemitem> is disabled or if there are services which need to be started with the correct time and not observe a jump in the clock.
- </para>
- <para>
- To check if the <systemitem class="daemon">ntpdate</systemitem> service is enabled to run at system start, issue the following command:
- <screen>~]$ <command>chkconfig --list ntpdate</command>
-ntpdate 0:off 1:off 2:on 3:on 4:on 5:on 6:off</screen>
-</para>
-<para>
- To enable the service to run at system start, issue the following command as <systemitem class="username">root</systemitem>:
- <screen>~]# <command>chkconfig ntpdate on</command></screen>
-</para>
-
-<para>
- To configure <systemitem class="daemon">ntpdate</systemitem> servers, using a text editor running as root, edit <filename>/etc/ntp/step-tickers</filename> to include one or more host names as follows:
- <screen>clock1.example.com
-clock2.example.com</screen>
-The number of servers listed is not very important as <systemitem class="daemon">ntpdate</systemitem> will only use this to obtain the date information once when the system is starting. If you have an internal time server then use that host name for the first line. An additional host on the second line as a backup is sensible. The selection of backup servers and whether the second host is internal or external depends on your risk assessment. For example, what is the chance of any problem affecting the fist server also affecting the second server? Would connectivity to an external server be more likely to be available than connectivity to internal servers in the event of a network failure disrupting access to the first server?
-</para>
-
-<para>
- The <systemitem class="daemon">ntpdate</systemitem> service has a file that must contain a list of <systemitem class="protocol">NTP</systemitem> servers to be used on system start. It is recommend to have at last four servers listed to reduce the chance of a <quote>false ticker</quote> (incorrect time source) influencing the quality of the time offset calculation. However, publicly accessible time sources are rarely incorrect.</para>
-
-</section>
-
-
<section id="s1-Configure_NTP">
<title>Configure NTP</title>
<para>
9 years, 10 months
[system-administrators-guide] Should use the "repositories" rather than "repos" in the main text I think. en-US/Configuring_NT
by stephenw
commit a7d86d6371d3ba98a6d09a9ea49158b5ebc5e1b3
Author: Stephen Wadeley <swadeley(a)redhat.com>
Date: Wed Oct 30 20:41:35 2013 +0100
Should use the "repositories" rather than "repos" in the main text I think.
en-US/Configuring_NTP_Using_the_chrony_Suite.xml
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 b32cde3..8a0db6c 100644
--- a/en-US/Configuring_NTP_Using_the_chrony_Suite.xml
+++ b/en-US/Configuring_NTP_Using_the_chrony_Suite.xml
@@ -13,7 +13,7 @@
The user space daemon updates the system clock running in the kernel. The system clock can keep time by using various clock sources. Usually, the <firstterm>Time Stamp Counter</firstterm> (<acronym>TSC</acronym>) is used. The TSC is a CPU register which counts the number of cycles since it was last reset. It is very fast, has a high resolution, and there are no interrupts.
</para>
<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 system clock on systems that do not fit into the conventional permanently networked, always on, dedicated server category.
+There is a choice between the daemons <systemitem class="daemon">ntpd</systemitem> and <systemitem class="daemon">chronyd</systemitem>, which are available from the repositories 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 system clock 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>
9 years, 10 months
[system-administrators-guide] UK to USA spelling: en-US/Configuring_NTP_Using_the_chrony_Suite.xml synchronisation >> synchron
by stephenw
commit 175767f957cb54b5be7ca96cba03cc3029894462
Author: Stephen Wadeley <swadeley(a)redhat.com>
Date: Wed Oct 30 20:40:57 2013 +0100
UK to USA spelling: en-US/Configuring_NTP_Using_the_chrony_Suite.xml
synchronisation >> synchronization
synchronise >> synchronize
en-US/Configuring_NTP_Using_the_chrony_Suite.xml | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
---
diff --git a/en-US/Configuring_NTP_Using_the_chrony_Suite.xml b/en-US/Configuring_NTP_Using_the_chrony_Suite.xml
index b5bf5f2..b32cde3 100644
--- a/en-US/Configuring_NTP_Using_the_chrony_Suite.xml
+++ b/en-US/Configuring_NTP_Using_the_chrony_Suite.xml
@@ -39,7 +39,7 @@ There is a choice between the daemons <systemitem class="daemon">ntpd</systemite
</listitem>
<listitem>
<para>
- <systemitem class="daemon">chronyd</systemitem> can usually synchronise the clock faster and with better time accuracy.
+ <systemitem class="daemon">chronyd</systemitem> can usually synchronize the clock faster and with better time accuracy.
</para>
</listitem>
<listitem>
@@ -373,7 +373,7 @@ The format of the syntax is:
<term>stratumweight</term>
<listitem>
<para>
- The <command>stratumweight</command> directive sets how much distance should be added per stratum to the synchronisation distance when <systemitem class="daemon">chronyd</systemitem> selects the synchronization source from available sources.</para>
+ The <command>stratumweight</command> directive sets how much distance should be added per stratum to the synchronization distance when <systemitem class="daemon">chronyd</systemitem> selects the synchronization source from available sources.</para>
<para>
The format of the syntax is:
<screen>stratumweight <replaceable>dist-in-seconds</replaceable></screen>
9 years, 10 months