docs-commits October 2014

docs-commits@lists.fedoraproject.org

9 participants
171 discussions

[install-guide] Updating descriptions of logvol --size and --percent in Kickstart
by pbokoc 31 Oct '14

31 Oct '14

commit eef1623392c75e7cc94772b77f5fc04334e85f84 Author: Petr Bokoc <pbokoc(a)redhat.com> Date: Fri Oct 31 17:07:05 2014 +0100 Updating descriptions of logvol --size and --percent in Kickstart en-US/Kickstart_Syntax_Reference.xml | 23 ++++++++++++++--------- 1 files changed, 14 insertions(+), 9 deletions(-) --- diff --git a/en-US/Kickstart_Syntax_Reference.xml b/en-US/Kickstart_Syntax_Reference.xml index 3d8bd93..e0ab490 100644 --- a/en-US/Kickstart_Syntax_Reference.xml +++ b/en-US/Kickstart_Syntax_Reference.xml @@ -1185,39 +1185,44 @@ <term><option>--size=</option></term> <listitem> <para> - The minimum size of the logical volume in megabytes. This option is mandatory when creating a new logical volume, and optional if you are reusing an existing logical volume using the <option>--useexisting</option> or <option>--noformat</option> option. + The size of the logical volume in megabytes. This option can not be used together with the <option>--percent=</option> option. </para> </listitem> </varlistentry> <varlistentry> - <term><option>--maxsize=</option></term> + <term><option>--percent=</option></term> <listitem> <para> - The maximum size in megabytes when the logical volume is set to grow. Specify an integer value here such as <literal>500</literal> (do not include the unit). + Specify the amount by which to grow the logical volume, as a percentage of the free space in the volume group after any statically-sized logical volumes are taken into account. This option can not be used together with the <option>--size=</option> and <option>--grow</option> options. </para> + <important> + <para> + When creating a new logical volume, you must either specify its size statically using the <option>--size=</option> option, or as a percentage of remaining free space using the <option>--percent=</option> option. You can not use both of these options on the same logical volume. + </para> + </important> </listitem> </varlistentry> <varlistentry> - <term><option>--recommended</option></term> + <term><option>--maxsize=</option></term> <listitem> <para> - Use this option when creating a <systemitem>swap</systemitem> logical volume to determine the size of this volume automatically, based on your system's hardware. For details about the recommended scheme, see <remark>TODO: xref to section with partitioning recommendations</remark> + The maximum size in megabytes when the logical volume is set to grow. Specify an integer value here such as <literal>500</literal> (do not include the unit). </para> </listitem> </varlistentry> <varlistentry> - <term><option>--resize</option></term> + <term><option>--recommended</option></term> <listitem> <para> - Resize an existing logical volume. If you use this option, you must also specify <option>--useexisting</option> and <option>--size</option>. + Use this option when creating a <systemitem>swap</systemitem> logical volume to determine the size of this volume automatically, based on your system's hardware. For details about the recommended scheme, see <remark>TODO: xref to section with partitioning recommendations</remark> </para> </listitem> </varlistentry> <varlistentry> - <term><option>--percent=</option></term> + <term><option>--resize</option></term> <listitem> <para> - Specify the amount by which to grow the logical volume, as a percentage of the free space in the volume group after any statically-sized logical volumes are taken into account. This option must be used in conjunction with the <option>--size</option> and <option>--grow</option> options. + Resize an existing logical volume. If you use this option, you must also specify <option>--useexisting</option> and <option>--size</option>. </para> </listitem> </varlistentry>

1 0

[install-guide] Updating description of logvol --recommended in Kickstart
by pbokoc 31 Oct '14

31 Oct '14

commit 2116a18238640a45132c1d7b0c6a86faff8ed73e Author: Petr Bokoc <pbokoc(a)redhat.com> Date: Fri Oct 31 16:57:21 2014 +0100 Updating description of logvol --recommended in Kickstart en-US/Kickstart_Syntax_Reference.xml | 5 +---- 1 files changed, 1 insertions(+), 4 deletions(-) --- diff --git a/en-US/Kickstart_Syntax_Reference.xml b/en-US/Kickstart_Syntax_Reference.xml index 0901a9d..3d8bd93 100644 --- a/en-US/Kickstart_Syntax_Reference.xml +++ b/en-US/Kickstart_Syntax_Reference.xml @@ -1106,9 +1106,6 @@ <literal>swap --recommended</literal> </programlisting> <para> - The size assigned will be effective but not precisely calibrated for your system. - </para> - <para> To determine the size of the swap partition automatically but also allow extra space for your system to hibernate, use the <option>--hibernation</option> option: </para> <programlisting> @@ -1204,7 +1201,7 @@ <term><option>--recommended</option></term> <listitem> <para> - Determine the size of the logical volume automatically. For details about the recommended scheme, see <remark>TODO: xref to section with partitioning recommendations</remark> + Use this option when creating a <systemitem>swap</systemitem> logical volume to determine the size of this volume automatically, based on your system's hardware. For details about the recommended scheme, see <remark>TODO: xref to section with partitioning recommendations</remark> </para> </listitem> </varlistentry>

1 0

[system-administrators-guide] typos and formatting improvements
by stephenw 30 Oct '14

30 Oct '14

commit 904d8119dabebe5afd6155e6790c294e298217a3 Author: Stephen Wadeley <swadeley(a)redhat.com> Date: Thu Oct 30 22:17:46 2014 +0100 typos and formatting improvements in en-US/Mail_Servers.xml en-US/Mail_Servers.xml | 53 +++++++++++++---------------------------------- 1 files changed, 15 insertions(+), 38 deletions(-) --- diff --git a/en-US/Mail_Servers.xml b/en-US/Mail_Servers.xml index d24427a..614f47b 100644 --- a/en-US/Mail_Servers.xml +++ b/en-US/Mail_Servers.xml @@ -129,11 +129,11 @@ ln -s '/usr/lib/systemd/system/dovecot' '/etc/systemd/system/multi-user.target.w </note> </listitem> </orderedlist> - <para>Unlike <systemitem class="protocol">SMTP</systemitem>, both <systemitem class="protocol">IMAP</systemitem> and <systemitem class="protocol">POP3</systemitem> require connecting clients to authenticate using a username and password. By default, passwords for both protocols are passed over the network unencrypted.</para> + <para>Unlike <systemitem class="protocol">SMTP</systemitem>, both <systemitem class="protocol">IMAP</systemitem> and <systemitem class="protocol">POP3</systemitem> require connecting clients to authenticate using a user name and password. By default, passwords for both protocols are passed over the network unencrypted.</para> <para>To configure <systemitem class="protocol">SSL</systemitem> on <command>dovecot</command>:</para> <itemizedlist> <listitem> - <para>Edit the <filename>/etc/pki/dovecot/dovecot-openssl.conf</filename> configuration file as you prefer. However, in a typical installation, this file does not require modification.</para> + <para>Edit the <filename>/etc/pki/dovecot/dovecot-openssl.cnf</filename> configuration file as you prefer. However, in a typical installation, this file does not require modification.</para> </listitem> <listitem> <para>Rename, move or delete the files <filename>/etc/pki/dovecot/certs/dovecot.pem</filename> and <filename>/etc/pki/dovecot/private/dovecot.pem</filename>.</para> @@ -249,11 +249,7 @@ ln -s '/usr/lib/systemd/system/dovecot' '/etc/systemd/system/multi-user.target.w <para>To improve security, Postfix uses a modular design, where small processes with limited privileges are launched by a <firstterm>master</firstterm> daemon. The smaller, less privileged processes perform very specific tasks related to the various stages of mail delivery and run in a changed root environment to limit the effects of attacks.</para> <para>Configuring Postfix to accept network connections from hosts other than the local computer takes only a few minor changes in its configuration file. Yet for those with more complex needs, Postfix provides a variety of configuration options, as well as third party add-ons that make it a very versatile and full-featured MTA.</para> <para>The configuration files for Postfix are human readable and support upward of 250 directives. Unlike Sendmail, no macro processing is required for changes to take effect and the majority of the most commonly used options are described in the heavily commented files.</para> -  + <section id="s3-email-mta-postfix-default"> <title>The Default Postfix Installation</title> @@ -261,7 +257,7 @@ ln -s '/usr/lib/systemd/system/dovecot' '/etc/systemd/system/multi-user.target.w <primary>Postfix</primary> <secondary>default installation</secondary> </indexterm> - <para>The Postfix executable is <filename>/usr/sbin/postfix</filename>. This daemon launches all related processes needed to handle mail delivery.</para> + <para>The Postfix executable is <filename>postfix</filename>. This daemon launches all related processes needed to handle mail delivery.</para> <para>Postfix stores its configuration files in the <filename>/etc/postfix/</filename> directory. The following is a list of the more commonly used files:</para> <itemizedlist> <listitem> @@ -404,7 +400,7 @@ search_base = dc=<replaceable>example</replaceable>, dc=<replaceable>com</replac <para> Before using Sendmail, the default MTA has to be switched from Postfix. For more information how to switch the default MTA refer to <xref linkend="s1-email-mta"/>. </para> - <para>The Sendmail executable is <filename>/usr/sbin/sendmail</filename>.</para> + <para>The Sendmail executable is <filename>sendmail</filename>.</para> <para>Sendmail's lengthy and detailed configuration file is <filename>/etc/mail/sendmail.cf</filename>. Avoid editing the <filename>sendmail.cf</filename> file directly. To make configuration changes to Sendmail, edit the <filename>/etc/mail/sendmail.mc</filename> file, back up the original <filename>/etc/mail/sendmail.cf</filename> file, and use the following alternatives to generate a new configuration file:</para> <itemizedlist> <listitem> @@ -444,12 +440,12 @@ search_base = dc=<replaceable>example</replaceable>, dc=<replaceable>com</replac This will update <filename>virtusertable.db</filename>, <filename>access.db</filename>, <filename>domaintable.db</filename>, <filename>mailertable.db</filename>, <filename>sendmail.cf</filename>, and <filename>submit.cf</filename>.</para> <para> To update all the database files listed above and to update a custom database file, use a command in the following format: -<synopsis><command>make <replaceable>name>.db</replaceable> all</command></synopsis> +<synopsis><command>make <replaceable>name.db</replaceable> all</command></synopsis> where <replaceable>name</replaceable> represents the name of the custom database file to be updated.</para> <para> To update a single database, use a command in the following format: -<synopsis><command>make <replaceable>name>.db</replaceable></command></synopsis> -where <replaceable>name>.db</replaceable> represents the name of the database file to be updated.</para> +<synopsis><command>make <replaceable>name.db</replaceable></command></synopsis> +where <replaceable>name.db</replaceable> represents the name of the database file to be updated.</para> <para> You may also restart the <systemitem class="service">sendmail</systemitem> service for the changes to take effect by running:</para> <screen>~]# <command>systemctl restart sendmail</command></screen> @@ -560,7 +556,7 @@ FEATURE('ldap_routing')dnl</programlisting> </note> <para>Next, recreate the <filename>/etc/mail/sendmail.cf</filename> file by running the <command>m4</command> macro processor and again restarting Sendmail. See <xref linkend="s3-email-mta-sendmail-changes"/> for instructions.</para> - <para>For more information on <systemitem class="protocol">LDAP</systemitem>, refer to <xref + <para>For more information on <systemitem class="protocol">LDAP</systemitem>, see <xref linkend="s1-OpenLDAP" />.</para> </section> </section> @@ -606,7 +602,7 @@ FEATURE('ldap_routing')dnl</programlisting> </listitem> <listitem> <para> - <emphasis>user options</emphasis> — Contains information, such as username and password, necessary to authenticate and check for email using a specified email server.</para> + <emphasis>user options</emphasis> — Contains information, such as user name and password, necessary to authenticate and check for email using a specified email server.</para> </listitem> </itemizedlist> <para>Global options appear at the top of the <filename>.fetchmailrc</filename> file, followed by one or more server options, each of which designate a different email server that Fetchmail should check. User options follow server options for each user account checking that email server. Like server options, multiple user options may be specified for use with a particular server as well as to check multiple email accounts on the same server.</para> @@ -841,25 +837,8 @@ poll mail.domain2.com <indexterm> <primary><application>Mail Transport Agent Switcher</application></primary> </indexterm> -  -  + + <indexterm> <primary>Mail User Agent</primary> </indexterm> <indexterm> @@ -887,9 +866,7 @@ poll mail.domain2.com <figure float="0" id="fig-switchmail"> - <title> - <application>Mail Transport Agent Switcher</application> - </title> + <title><application>Mail Transport Agent Switcher</application></title> <mediaobject> <imageobject> <imagedata @@ -1308,7 +1285,7 @@ connect = 110 [imaps] accept = 993 connect = 143</programlisting> - <para>Once you start <command>stunnel</command> with the created configuration file using the <command>/usr/bin/stunnel /etc/stunnel/mail.conf</command> command, it will be possible to use an <systemitem class="protocol">IMAP</systemitem> or a <systemitem class="protocol">POP</systemitem> email client and connect to the email server using SSL encryption.</para> + <para>Once you start <command>stunnel</command> with the created configuration file using the <command>stunnel /etc/stunnel/mail.conf</command> command, it will be possible to use an <systemitem class="protocol">IMAP</systemitem> or a <systemitem class="protocol">POP</systemitem> email client and connect to the email server using SSL encryption.</para> <para>For more information on <command>stunnel</command>, see the <filename>stunnel(8)</filename> man page or the documents in the <filename class="directory">/usr/share/doc/stunnel/</filename> directory.</para> </section> </section> @@ -1383,7 +1360,7 @@ connect = 143</programlisting> </listitem> <listitem> <para> - <filename>/usr/share/doc/spamassassin/</filename> — Contains a large amount of information pertaining to SpamAssassin.</para> + <filename class="directory">/usr/share/doc/spamassassin/</filename> — Contains a large amount of information pertaining to SpamAssassin.</para> </listitem> </itemizedlist> </listitem>

1 0

[system-administrators-guide] Removing significance="normal" from indexterm
by stephenw 30 Oct '14

30 Oct '14

commit 9d0fd4c2cd666b3f790346e5c3b57bf99bf6c21e Author: Stephen Wadeley <swadeley(a)redhat.com> Date: Thu Oct 30 22:16:33 2014 +0100 Removing significance="normal" from indexterm Has no benefit and makes my diff compares harder as not used in my other docs. en-US/Mail_Servers.xml | 265 +++++++++++++++-------------------------------- 1 files changed, 85 insertions(+), 180 deletions(-) --- diff --git a/en-US/Mail_Servers.xml b/en-US/Mail_Servers.xml index 2bfc83b..d24427a 100644 --- a/en-US/Mail_Servers.xml +++ b/en-US/Mail_Servers.xml @@ -9,8 +9,7 @@ <section id="s1-email-protocols"> <title>Email Protocols</title> - <indexterm - significance="normal"> + <indexterm> <primary>email</primary> <secondary>protocols</secondary> </indexterm> @@ -24,8 +23,7 @@ <section id="s3-email-protocols-smtp"> <title>SMTP</title> - <indexterm - significance="normal"> + <indexterm> <primary>email</primary> <secondary>protocols</secondary> <tertiary>SMTP</tertiary> @@ -43,8 +41,7 @@ <section id="s3-email-protocols-pop"> <title>POP</title> - <indexterm - significance="normal"> + <indexterm> <primary>email</primary> <secondary>protocols</secondary> <tertiary>POP</tertiary> @@ -84,8 +81,7 @@ <section id="s3-email-protocols-imap"> <title>IMAP</title> - <indexterm - significance="normal"> + <indexterm> <primary>email</primary> <secondary>protocols</secondary> <tertiary>IMAP</tertiary> @@ -101,8 +97,7 @@ <section id="s3-mail-server-dovecot"> <title>Dovecot</title> - <indexterm - significance="normal"> + <indexterm> <primary>email</primary> <secondary>mail server</secondary> <tertiary>Dovecot</tertiary> @@ -157,8 +152,7 @@ ln -s '/usr/lib/systemd/system/dovecot' '/etc/systemd/system/multi-user.target.w <section id="s1-email-types"> <title>Email Program Classifications</title> - <indexterm - significance="normal"> + <indexterm> <primary>email</primary> <secondary>program classifications</secondary> </indexterm> @@ -166,19 +160,16 @@ ln -s '/usr/lib/systemd/system/dovecot' '/etc/systemd/system/multi-user.target.w <section id="s2-email-types-mta"> <title>Mail Transport Agent</title> - <indexterm - significance="normal"> + <indexterm> <primary>email</primary> <secondary>types</secondary> <tertiary>Mail Transport Agent</tertiary> </indexterm> - <indexterm - significance="normal"> + <indexterm> <primary>Mail Transport Agent</primary> <see>email</see> </indexterm> - <indexterm - significance="normal"> + <indexterm> <primary>MTA</primary> <see>Mail Transport Agent</see> </indexterm> @@ -192,19 +183,16 @@ ln -s '/usr/lib/systemd/system/dovecot' '/etc/systemd/system/multi-user.target.w <section id="s2-email-types-mda"> <title>Mail Delivery Agent</title> - <indexterm - significance="normal"> + <indexterm> <primary>email</primary> <secondary>types</secondary> <tertiary>Mail Delivery Agent</tertiary> </indexterm> - <indexterm - significance="normal"> + <indexterm> <primary>Mail Delivery Agent</primary> <see>email</see> </indexterm> - <indexterm - significance="normal"> + <indexterm> <primary>MDA</primary> <see>Mail Delivery Agent</see> </indexterm> @@ -214,19 +202,16 @@ ln -s '/usr/lib/systemd/system/dovecot' '/etc/systemd/system/multi-user.target.w <section id="s2-email-types-mua"> <title>Mail User Agent</title> - <indexterm - significance="normal"> + <indexterm> <primary>email</primary> <secondary>types</secondary> <tertiary>Mail User Agent</tertiary> </indexterm> - <indexterm - significance="normal"> + <indexterm> <primary>Mail User Agent</primary> <see>email</see> </indexterm> - <indexterm - significance="normal"> + <indexterm> <primary>MUA</primary> <see>Mail User Agent</see> </indexterm> @@ -253,13 +238,11 @@ ln -s '/usr/lib/systemd/system/dovecot' '/etc/systemd/system/multi-user.target.w <section id="s2-email-mta-postfix"> <title>Postfix</title> - <indexterm - significance="normal"> + <indexterm> <primary>email</primary> <secondary>Postfix</secondary> </indexterm> - <indexterm - significance="normal"> + <indexterm> <primary>Postfix</primary> </indexterm> <para>Originally developed at IBM by security expert and programmer Wietse Venema, Postfix is a Sendmail-compatible MTA that is designed to be secure, fast, and easy to configure.</para> @@ -274,8 +257,7 @@ ln -s '/usr/lib/systemd/system/dovecot' '/etc/systemd/system/multi-user.target.w <section id="s3-email-mta-postfix-default"> <title>The Default Postfix Installation</title> - <indexterm - significance="normal"> + <indexterm> <primary>Postfix</primary> <secondary>default installation</secondary> </indexterm> @@ -381,26 +363,22 @@ search_base = dc=<replaceable>example</replaceable>, dc=<replaceable>com</replac <section id="s2-email-mta-sendmail"> <title>Sendmail</title> - <indexterm - significance="normal"> + <indexterm> <primary>email</primary> <secondary>Sendmail</secondary> </indexterm> - <indexterm - significance="normal"> + <indexterm> <primary>Sendmail</primary> </indexterm> <para>Sendmail's core purpose, like other MTAs, is to safely transfer email among hosts, usually using the <systemitem class="protocol">SMTP</systemitem> protocol. Note that Sendmail is considered deprecated and users are encouraged to use Postfix when possible. See <xref linkend="s2-email-mta-postfix" /> for more information.</para> <section id="s3-email-mta-sendmail-purpose"> <title>Purpose and Limitations</title> - <indexterm - significance="normal"> + <indexterm> <primary>Sendmail</primary> <secondary>purpose</secondary> </indexterm> - <indexterm - significance="normal"> + <indexterm> <primary>Sendmail</primary> <secondary>limitations</secondary> </indexterm> @@ -412,8 +390,7 @@ search_base = dc=<replaceable>example</replaceable>, dc=<replaceable>com</replac <section id="s3-email-mta-sendmail-default"> <title>The Default Sendmail Installation</title> - <indexterm - significance="normal"> + <indexterm> <primary>Sendmail</primary> <secondary>default installation</secondary> </indexterm> @@ -486,13 +463,11 @@ where <replaceable>name>.db</replaceable> represents the name of the database <section id="s3-email-mta-sendmail-changes"> <title>Common Sendmail Configuration Changes</title> - <indexterm - significance="normal"> + <indexterm> <primary>Sendmail</primary> <secondary>common configuration changes</secondary> </indexterm> - <indexterm - significance="normal"> + <indexterm> <primary>Sendmail</primary> <secondary>with UUCP</secondary> </indexterm> @@ -524,13 +499,11 @@ where <replaceable>name>.db</replaceable> represents the name of the database <section id="s3-email-sendmail-changes-masquerading"> <title>Masquerading</title> - <indexterm - significance="normal"> + <indexterm> <primary>Sendmail</primary> <secondary>aliases</secondary> </indexterm> - <indexterm - significance="normal"> + <indexterm> <primary>Sendmail</primary> <secondary>masquerading</secondary> </indexterm> @@ -549,8 +522,7 @@ MASQUERADE_AS(example.com)dnl</programlisting> <section id="s3-email-sendmail-stopping-spam"> <title>Stopping Spam</title> - <indexterm - significance="normal"> + <indexterm> <primary>Sendmail</primary> <secondary>spam</secondary> </indexterm> @@ -572,8 +544,7 @@ MASQUERADE_AS(example.com)dnl</programlisting> <section id="s3-email-mta-sendmail-ldap"> <title>Using Sendmail with LDAP</title> - <indexterm - significance="normal"> + <indexterm> <primary>Sendmail</primary> <secondary>LDAP and</secondary> </indexterm> @@ -596,13 +567,11 @@ FEATURE('ldap_routing')dnl</programlisting> <section id="s2-email-mta-fetchmail"> <title>Fetchmail</title> - <indexterm - significance="normal"> + <indexterm> <primary>email</primary> <secondary>Fetchmail</secondary> </indexterm> - <indexterm - significance="normal"> + <indexterm> <primary>Fetchmail</primary> </indexterm> <para>Fetchmail is an MTA which retrieves email from remote servers and delivers it to the local MTA. Many users appreciate the ability to separate the process of downloading their messages located on a remote server from the process of reading and organizing their email in an MUA. Designed with the needs of dial-up users in mind, Fetchmail connects and quickly downloads all of the email messages to the mail spool file using any number of protocols, including <systemitem class="protocol">POP3</systemitem> and <systemitem class="protocol">IMAP</systemitem>. It can even forward email messages to an <systemitem class="protocol">SMTP</systemitem> server, if necessary.</para> @@ -617,16 +586,12 @@ FEATURE('ldap_routing')dnl</programlisting> <section id="s3-email-mda-fetchmail-configuration"> <title>Fetchmail Configuration Options</title> - <indexterm - significance="normal"> + <indexterm> <primary>Fetchmail</primary> <secondary>configuration options</secondary> </indexterm> - <indexterm - significance="normal"> - <primary> - <filename>.fetchmailrc</filename> - </primary> + <indexterm> + <primary><filename>.fetchmailrc</filename></primary> </indexterm> <para>Although it is possible to pass all necessary options on the command line to check for email on a remote server when executing Fetchmail, using a <filename>.fetchmailrc</filename> file is much easier. Place any desired configuration options in the <filename>.fetchmailrc</filename> file for those options to be used each time the <command>fetchmail</command> command is issued. It is possible to override these at the time Fetchmail is run by specifying that option on the command line.</para> <para>A user's <filename>.fetchmailrc</filename> file contains three classes of configuration options:</para> @@ -666,17 +631,13 @@ poll mail.domain2.com <section id="s3-email-mda-fetchmail-configuration-global"> <title>Global Options</title> - <indexterm - significance="normal"> + <indexterm> <primary>Fetchmail</primary> <secondary>configuration options</secondary> <tertiary>global options</tertiary> </indexterm> - <indexterm - significance="normal"> - <primary>ch-email - <filename>.fetchmailrc</filename> - </primary> + <indexterm> + <primary>ch-email <filename>.fetchmailrc</filename></primary> <secondary>global options</secondary> </indexterm> <para>Each global option should be placed on a single line after a <command>set</command> action.</para> @@ -699,17 +660,13 @@ poll mail.domain2.com <section id="s3-email-mda-fetchmail-configuration-server"> <title>Server Options</title> - <indexterm - significance="normal"> + <indexterm> <primary>Fetchmail</primary> <secondary>configuration options</secondary> <tertiary>server options</tertiary> </indexterm> - <indexterm - significance="normal"> - <primary> - <filename>.fetchmailrc</filename> - </primary> + <indexterm> + <primary><filename>.fetchmailrc</filename></primary> <secondary>server options</secondary> </indexterm> <para>Server options must be placed on their own line in <filename>.fetchmailrc</filename> after a <command>poll</command> or <command>skip</command> action.</para> @@ -745,17 +702,13 @@ poll mail.domain2.com <section id="s3-email-fetchmail-configuration-user"> <title>User Options</title> - <indexterm - significance="normal"> + <indexterm> <primary>Fetchmail</primary> <secondary>configuration options</secondary> <tertiary>user options</tertiary> </indexterm> - <indexterm - significance="normal"> - <primary> - <filename>.fetchmailrc</filename> - </primary> + <indexterm> + <primary><filename>.fetchmailrc</filename></primary> <secondary>user options</secondary> </indexterm> <para>User options may be placed on their own lines beneath a server option or on the same line as the server option. In either case, the defined options must follow the <command>user</command> option (defined below).</para> @@ -804,8 +757,7 @@ poll mail.domain2.com <section id="s3-email-mda-fetchmail-commands"> <title>Fetchmail Command Options</title> - <indexterm - significance="normal"> + <indexterm> <primary>Fetchmail</primary> <secondary>command options</secondary> </indexterm> @@ -815,8 +767,7 @@ poll mail.domain2.com <section id="s3-email-mda-fetchmail-commands-info"> <title>Informational or Debugging Options</title> - <indexterm - significance="normal"> + <indexterm> <primary>Fetchmail</primary> <secondary>command options</secondary> <tertiary>informational</tertiary> @@ -844,8 +795,7 @@ poll mail.domain2.com <section id="s3-email-mda-fetchmail-commands-special"> <title>Special Options</title> - <indexterm - significance="normal"> + <indexterm> <primary>Fetchmail</primary> <secondary>command options</secondary> <tertiary>special</tertiary> @@ -876,27 +826,20 @@ poll mail.domain2.com <section id="s2-email-switchmail"> <title>Mail Transport Agent (MTA) Configuration</title> - <indexterm - significance="normal"> + <indexterm> <primary>Mail Transport Agent</primary> <see>MTA</see> </indexterm> - <indexterm - significance="normal"> + <indexterm> <primary>MTA</primary> <secondary>setting default</secondary> </indexterm> - <indexterm - significance="normal"> + <indexterm> <primary>MTA</primary> - <secondary>switching with <application>Mail Transport Agent Switcher</application> - </secondary> + <secondary>switching with <application>Mail Transport Agent Switcher</application></secondary> </indexterm> - <indexterm - significance="normal"> - <primary> - <application>Mail Transport Agent Switcher</application> - </primary> + <indexterm> + <primary><application>Mail Transport Agent Switcher</application></primary> </indexterm>  - <indexterm - significance="normal"> <primary>Mail User Agent</primary> </indexterm> - <indexterm - significance="normal"> + <indexterm> <primary>MUA</primary> </indexterm> <para>A <firstterm>Mail Transport Agent</firstterm> (MTA) is essential for sending email. A <firstterm>Mail User Agent</firstterm> (MUA) such as <application>Evolution</application>, <application>Thunderbird</application>, and <application>Mutt</application>, is used to read and compose email. When a user sends an email from an MUA, the message is handed off to the MTA, which sends the message through a series of MTAs until it reaches its destination.</para> <para>Even if a user does not plan to send email from the system, some automated tasks or system programs might use the <command>mail</command> command to send email containing log messages to the <systemitem class="username">root</systemitem> user of the local system.</para> - <indexterm - significance="normal"> + <indexterm> <primary>sendmail</primary> </indexterm> - <indexterm - significance="normal"> + <indexterm> <primary>postfix</primary> </indexterm> <para>&MAJOROSVER; provides two MTAs: Postfix and Sendmail. If both are installed, Postfix is the default MTA. Note that Sendmail is considered deprecated in MAJOROS;.</para> @@ -940,11 +878,8 @@ poll mail.domain2.com <!--<para>The <application>Mail Transport Agent Switcher</application> allows for the selection of either <command>sendmail</command>, or <command>postfix</command> as the default MTA for the system.</para> <para>You should install the <package>system-switch-mail</package> package to use the text-based version of the <application>Mail Transport Agent Switcher</application> program. If you want to use the graphical version, install the <package>system-switch-mail-gnome</package> package.</para> <para>To start the <application>Mail Transport Agent Switcher</application>, select <guimenu>System</guimenu> (the main menu on the panel) > <guimenu>Administration</guimenu> > <guimenuitem>Mail Transport Agent Switcher</guimenuitem>, or type the command <command>system-switch-mail</command> at a shell prompt (for example, in an XTerm or GNOME terminal).</para> - <indexterm - significance="normal"> - <primary> - <application>Mail Transport Agent Switcher</application> - </primary> + <indexterm> + <primary><application>Mail Transport Agent Switcher</application></primary> <secondary>starting in text mode</secondary> </indexterm> <para>The program automatically detects if the X Window System is running. If it is running, the program starts in graphical mode as shown in <xref @@ -976,13 +911,11 @@ poll mail.domain2.com <title>Mail Delivery Agents</title> <para>&MAJOROS; includes two primary MDAs, Procmail and <command>mail</command>. Both of the applications are considered LDAs and both move email from the MTA's spool file into the user's mailbox. However, Procmail provides a robust filtering system.</para> <para>This section details only Procmail. For information on the <command>mail</command> command, consult its man page (<command>man mail</command>).</para> - <indexterm - significance="normal"> + <indexterm> <primary>email</primary> <secondary>Procmail</secondary> </indexterm> - <indexterm - significance="normal"> + <indexterm> <primary>Procmail</primary> </indexterm> <para>Procmail delivers and filters email as it is placed in the mail spool file of the localhost. It is powerful, gentle on system resources, and widely used. Procmail can play a critical role in delivering email to be read by email client applications.</para> @@ -993,16 +926,12 @@ poll mail.domain2.com <section id="s2-email-procmail-configuration"> <title>Procmail Configuration</title> - <indexterm - significance="normal"> + <indexterm> <primary>Procmail</primary> <secondary>configuration</secondary> </indexterm> - <indexterm - significance="normal"> - <primary> - <filename>.procmailrc</filename> - </primary> + <indexterm> + <primary><filename>.procmailrc</filename></primary> </indexterm> <para>The Procmail configuration file contains important environmental variables. These variables specify things such as which messages to sort and what to do with the messages that do not match any recipes.</para> <para>These environmental variables usually appear at the beginning of the <filename>~/.procmailrc</filename> file in the following format:</para> @@ -1066,8 +995,7 @@ INCLUDERC=$MAILDIR/spam.rc</screen> <section id="s2-email-procmail-recipes"> <title>Procmail Recipes</title> - <indexterm - significance="normal"> + <indexterm> <primary>Procmail</primary> <secondary>recipes</secondary> </indexterm> @@ -1087,14 +1015,12 @@ INCLUDERC=$MAILDIR/spam.rc</screen> <section id="s2-email-procmail-recipes-delivering"> <title>Delivering vs. Non-Delivering Recipes</title> - <indexterm - significance="normal"> + <indexterm> <primary>Procmail</primary> <secondary>recipes</secondary> <tertiary>delivering</tertiary> </indexterm> - <indexterm - significance="normal"> + <indexterm> <primary>Procmail</primary> <secondary>recipes</secondary> <tertiary>non-delivering</tertiary> @@ -1106,8 +1032,7 @@ INCLUDERC=$MAILDIR/spam.rc</screen> <section id="s3-email-procmail-recipes-flags"> <title>Flags</title> - <indexterm - significance="normal"> + <indexterm> <primary>Procmail</primary> <secondary>recipes</secondary> <tertiary>flags</tertiary> @@ -1172,8 +1097,7 @@ INCLUDERC=$MAILDIR/spam.rc</screen> <section id="s3-email-procmail-recipes-lockfile"> <title>Specifying a Local Lockfile</title> - <indexterm - significance="normal"> + <indexterm> <primary>Procmail</primary> <secondary>recipes</secondary> <tertiary>local lockfiles</tertiary> @@ -1184,14 +1108,12 @@ INCLUDERC=$MAILDIR/spam.rc</screen> <section id="s3-email-procmail-recipes-special"> <title>Special Conditions and Actions</title> - <indexterm - significance="normal"> + <indexterm> <primary>Procmail</primary> <secondary>recipes</secondary> <tertiary>special conditions</tertiary> </indexterm> - <indexterm - significance="normal"> + <indexterm> <primary>Procmail</primary> <secondary>recipes</secondary> <tertiary>special actions</tertiary> @@ -1236,8 +1158,7 @@ INCLUDERC=$MAILDIR/spam.rc</screen> <section id="s3-email-procmail-recipes-examples"> <title>Recipe Examples</title> - <indexterm - significance="normal"> + <indexterm> <primary>Procmail</primary> <secondary>recipes</secondary> <tertiary>examples</tertiary> @@ -1271,19 +1192,16 @@ tuxlug</screen> <section id="s3-email-mda-spam"> <title>Spam Filters</title> - <indexterm - significance="normal"> + <indexterm> <primary>Procmail</primary> <secondary>recipes</secondary> <tertiary>SpamAssassin</tertiary> </indexterm> - <indexterm - significance="normal"> + <indexterm> <primary>SpamAssassin</primary> <secondary>using with Procmail</secondary> </indexterm> - <indexterm - significance="normal"> + <indexterm> <primary>email</primary> <secondary>spam</secondary> <tertiary>filtering out</tertiary> @@ -1327,8 +1245,7 @@ tuxlug</screen> id="s2-email-security"> <title>Securing Communication</title> <para>Popular MUAs included with &MAJOROS;, such as <application>Evolution</application> and <application>Mutt</application> offer SSL-encrypted email sessions.</para> - <indexterm - significance="normal"> + <indexterm> <primary>email</primary> <secondary>security</secondary> </indexterm> @@ -1336,8 +1253,7 @@ tuxlug</screen> <section id="s3-email-security-clients"> <title>Secure Email Clients</title> - <indexterm - significance="normal"> + <indexterm> <primary>email</primary> <secondary>security</secondary> <tertiary>clients</tertiary> @@ -1348,17 +1264,13 @@ tuxlug</screen> <section id="s3-email-security-servers"> <title>Securing Email Client Communications</title> - <indexterm - significance="normal"> + <indexterm> <primary>email</primary> <secondary>security</secondary> <tertiary>servers</tertiary> </indexterm> - <indexterm - significance="normal"> - <primary> - <command>stunnel</command> - </primary> + <indexterm> + <primary><command>stunnel</command></primary> </indexterm> <para>Offering SSL encryption to <systemitem class="protocol">IMAP</systemitem> and <systemitem class="protocol">POP</systemitem> users on the email server is a simple matter.</para> <para>First, create an SSL certificate. This can be done in two ways: by applying to a <firstterm>Certificate Authority</firstterm> (<firstterm>CA</firstterm>) for an SSL certificate or by creating a self-signed certificate.</para> @@ -1404,23 +1316,19 @@ connect = 143</programlisting> <section id="s1-email-additional-resources"> <title>Additional Resources</title> - <indexterm - significance="normal"> + <indexterm> <primary>email</primary> <secondary>additional resources</secondary> </indexterm> - <indexterm - significance="normal"> + <indexterm> <primary>Sendmail</primary> <secondary>additional resources</secondary> </indexterm> - <indexterm - significance="normal"> + <indexterm> <primary>Procmail</primary> <secondary>additional resources</secondary> </indexterm> - <indexterm - significance="normal"> + <indexterm> <primary>Fetchmail</primary> <secondary>additional resources</secondary> </indexterm> @@ -1428,8 +1336,7 @@ connect = 143</programlisting> <section id="s2-email-installed-docs"> <title>Installed Documentation</title> - <indexterm - significance="normal"> + <indexterm> <primary>email</primary> <secondary>additional resources</secondary> <tertiary>installed documentation</tertiary> @@ -1485,8 +1392,7 @@ connect = 143</programlisting> <section id="s2-email-useful-websites"> <title>Useful Websites</title> - <indexterm - significance="normal"> + <indexterm> <primary>email</primary> <secondary>additional resources</secondary> <tertiary>useful websites</tertiary> @@ -1532,8 +1438,7 @@ connect = 143</programlisting> <section id="s2-email-related-books"> <title>Related Books</title> - <indexterm - significance="normal"> + <indexterm> <primary>email</primary> <secondary>additional resources</secondary> <tertiary>related books</tertiary>

1 0

[release-notes] Updated the entry for Allwinner sunxi ARM SoC Support.
by Simon Clark 30 Oct '14

30 Oct '14

commit aee53d23e9965b9cdc9570cebad81bc424d25fe3 Author: Simon Clark <simon.richard.clark(a)gmail.com> Date: Thu Oct 30 12:38:58 2014 +0000 Updated the entry for Allwinner sunxi ARM SoC Support. en-US/ARM.xml | 6 ++++++ 1 files changed, 6 insertions(+), 0 deletions(-) --- diff --git a/en-US/ARM.xml b/en-US/ARM.xml index c853410..5b7b6d6 100644 --- a/en-US/ARM.xml +++ b/en-US/ARM.xml @@ -31,5 +31,11 @@ Remix</ulink>. With the release of F21, these sunxi SoCs are now supported directly in the official Fedora ARM images, without the need for a Remix.</para> + <note> + <title>Serial console only</title> + <para>HDMI video output from these sunxi devices is not yet + supported in Fedora ARM. A serial console should be used + instead.</para> + </note> </section> </section>

1 0

[release-notes] Typo
by Simon Clark 29 Oct '14

29 Oct '14

commit 9bd4fedba01e943e489f6111260bacf47afef108 Author: Simon Clark <simon.richard.clark(a)gmail.com> Date: Wed Oct 29 22:21:08 2014 +0000 Typo en-US/ARM.xml | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) --- diff --git a/en-US/ARM.xml b/en-US/ARM.xml index c3bc9ef..c853410 100644 --- a/en-US/ARM.xml +++ b/en-US/ARM.xml @@ -21,7 +21,7 @@ </section> <section id="allwinner-sunxi-arm-support"> <title>Allwinner sunxi (A10 / A13 / A20) ARM SoC - support</title> + Support</title> <para>Allwinner sunxi is a family of ARM system on a chip (SoC) devices. The sunxi A10, A13 and A20 SoCs are used in a number of popular, low cost ARM development boards and ARM mini

1 0

[release-notes] Added an entry for Allwinner sunxi ARM SoC Support.
by Simon Clark 29 Oct '14

29 Oct '14

commit e55c10e169d5a94f45209a39dbf519e0e12a6149 Author: Simon Clark <simon.richard.clark(a)gmail.com> Date: Wed Oct 29 22:14:26 2014 +0000 Added an entry for Allwinner sunxi ARM SoC Support. en-US/ARM.xml | 37 +++++++++++++++++++++++++------------ 1 files changed, 25 insertions(+), 12 deletions(-) --- diff --git a/en-US/ARM.xml b/en-US/ARM.xml index 35da467..c3bc9ef 100644 --- a/en-US/ARM.xml +++ b/en-US/ARM.xml @@ -1,22 +1,35 @@ -<?xml version='1.0' encoding='utf-8' ?> -<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +<?xml version='1.0' encoding='utf-8'?> +<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" + "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" +[ <!ENTITY % BOOK_ENTITIES SYSTEM "Release_Notes.ent"> %BOOK_ENTITIES; ]> - <section id="ARM"> <title>Fedora ARM</title> <para /> <section id="ARM-qemu-aarch64"> <title>Virtualizing AArch64</title> - <para> - The qemu project has been working to enable full AArch64 system emulation, provided by the <package>qemu-system-aarch64</package> package. - </para> - <para> - AArch64 VMs can now be run on x86 hosts using standard libvirt tools like <command>virsh</command>, <application>virt-manager</application>, and <command>virt-install</command>. - </para> + <para>The qemu project has been working to enable full AArch64 + system emulation, provided by the + <package>qemu-system-aarch64</package>package.</para> + <para>AArch64 VMs can now be run on x86 hosts using standard + libvirt tools like + <command>virsh</command>, + <application>virt-manager</application>, and + <command>virt-install</command>.</para> + </section> + <section id="allwinner-sunxi-arm-support"> + <title>Allwinner sunxi (A10 / A13 / A20) ARM SoC + support</title> + <para>Allwinner sunxi is a family of ARM system on a chip (SoC) + devices. The sunxi A10, A13 and A20 SoCs are used in a number + of popular, low cost ARM development boards and ARM mini + computers. Previously, Fedora ARM has been supported on these + devices through a + <ulink url="http://fedoraproject.org/wiki/Architectures/ARM/F19/Remixes#Allwinner_A10_.…"> + Remix</ulink>. With the release of F21, these sunxi SoCs are + now supported directly in the official Fedora ARM images, + without the need for a Remix.</para> </section> - </section> - -

1 0

[release-notes] Amended the entry for Improved Ivy Packaging.
by Simon Clark 29 Oct '14

29 Oct '14

commit 71e4fdd487d3ebbbeeadd7aac9a4d883ab817719 Author: Simon Clark <simon.richard.clark(a)gmail.com> Date: Wed Oct 29 12:29:42 2014 +0000 Amended the entry for Improved Ivy Packaging. en-US/Development_Java.xml | 13 +++++-------- 1 files changed, 5 insertions(+), 8 deletions(-) --- diff --git a/en-US/Development_Java.xml b/en-US/Development_Java.xml index 03e82ab..274211a 100644 --- a/en-US/Development_Java.xml +++ b/en-US/Development_Java.xml @@ -52,14 +52,11 @@ </section> <section id="improved-ivy-packaging"> <title>Improved Ivy Packaging</title> - <para>This change aims to improve the process for packaging - Java software that uses Apache Ivy to manage build - dependencies. Currently, it is packaged manually. Dependencies - must be symlinked manually, all files have to be explicitly - installed and there are no auto-requires. This change intends - to simplify Ivy packaging in a similar way to that which was - done for Maven packaging. In particular, the following - improvements have been implemented:</para> + <para>The way of packaging Java software that uses Apache Ivy + to manage build dependencies has been improved in a similar way + to the Maven packaging updates in previous Fedora releases. In + particular, the following improvements have been + implemented:</para> <itemizedlist> <listitem> <para>automatic resolution of Ivy artifacts,</para>

1 0

[release-notes] Revised SSSD GPO Access Control entry.
by Simon Clark 28 Oct '14

28 Oct '14

commit 1f51fa44c8f7b05c62322a275c4ef7b1fce2bd47 Author: Simon Clark <simon.richard.clark(a)gmail.com> Date: Tue Oct 28 21:45:38 2014 +0000 Revised SSSD GPO Access Control entry. en-US/Security.xml | 35 +++++++++++++++++------------------ 1 files changed, 17 insertions(+), 18 deletions(-) --- diff --git a/en-US/Security.xml b/en-US/Security.xml index 7aa05b1..a6d667a 100644 --- a/en-US/Security.xml +++ b/en-US/Security.xml @@ -9,27 +9,26 @@ <title>Security</title> <para /> <section id="sssd-gpo-access-control"> - <title>sssd GPO-Based Access Control</title> - <para>sssd now supports centrally managed, host-based access + <title>SSSD GPO-Based Access Control</title> + <para>SSSD now supports centrally managed, host-based access control in an Active Directory (AD) environment, using Group Policy Objects (GPOs).</para> <para>GPO policy settings are commonly used to manage - host-based access control in an AD environment. The two - specific GPO policy settings ("Allow Log On Locally" and "Deny - Log On Locally") essentially serve as a whitelist and blacklist - of domain users and groups and they are consulted to determine - whether logon access to a particular domain computer should be - granted. When dealing with GPOs, there is typically a - management piece (used to specify the policy settings) and a - client-side processing piece (used to retrieve and enforce the - policy settings). Since the two policy settings of interest - already exist in AD, administrators can continue to use - existing mechanisms to specify the whitelist and blacklist - (e.g. Group Policy Management Console, or GPMC). As such, this - change is related only to the retrieval and enforcement of - policy settings. This change only affects SSSD's AD provider. - It has no effect on any other SSSD providers (e.g. IPA - provider).</para> + host-based access control in an AD environment. SSSD supports + local logons, remote logons, service logons and more. Each of + these standard GPO security options can be mapped to any PAM + service, allowing administrators to comprehensively configure + their systems.</para> + <para>This enhancement to SSSD is related only to the retrieval + and enforcement of AD policy settings. Administrators can + continue to use the existing AD tool set to specify policy + settings.</para> + <para>The new functionality only affects SSSD's AD provider and + has no effect on any other SSSD providers (e.g. IPA provider). + By default, SSSD's AD provider will be installed in + "permissive" mode, so that it won't break upgrades. + Administrators will need to set "enforcing" mode manually (see + sssd-ad(5)).</para> <para>More information about this change can be found at: <ulink url="https://fedorahosted.org/sssd/wiki/DesignDocs/ActiveDirectoryGPOIntegration" /></para> </section>

1 0

[release-notes: 2/2] Merge branch 'master' of ssh://git.fedorahosted.org/git/docs/release-notes
by Pete Travis 28 Oct '14

28 Oct '14

commit 330fc50766d5e4bf4989df715b46be8118172a08 Merge: 12217c2 ae2a6cc Author: Pete Travis <immanetize(a)fedoraproject.org> Date: Mon Oct 27 21:53:41 2014 -0600 Merge branch 'master' of ssh://git.fedorahosted.org/git/docs/release-notes en-US/Database_Servers.xml | 3 +++ en-US/Security.xml | 35 +++++++++++++++++++++++++++++------ 2 files changed, 32 insertions(+), 6 deletions(-) ---

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

docs-commits October 2014