[deployment-guide/comm-rel: 23/74] Wrote the Setting Up the Typing Break section.
by dsilas
commit 37637c56c485db61d71ed0d222f9a481e521092d
Author: Jaromir Hradilek <jhradile(a)redhat.com>
Date: Thu Jun 24 11:58:09 2010 +0200
Wrote the Setting Up the Typing Break section.
en-US/Keyboard_Configuration.xml | 17 ++++++++++++++++-
1 files changed, 16 insertions(+), 1 deletions(-)
---
diff --git a/en-US/Keyboard_Configuration.xml b/en-US/Keyboard_Configuration.xml
index e775ee3..826f0d7 100644
--- a/en-US/Keyboard_Configuration.xml
+++ b/en-US/Keyboard_Configuration.xml
@@ -107,7 +107,10 @@
</figure>
</section>
<section id="s1-keyboard-break">
- <title>Setting up a typing break</title>
+ <title>Setting Up a Typing Break</title>
+ <para>
+ Typing for a long period of time can be not only tiresome, but it can also increase the risk of serious health problems, such as the carpal tunnel syndrome. One way of preventing this is to configure the system to enforce the typing break. Simply select <menuchoice><guimenu>System</guimenu><guisubmenu>Preferences</guisubmenu><guimenuitem>Keyboard</guimenuitem></menuchoice> from the panel, click the <guilabel>Typing Break</guilabel> tab, and check the <guilabel>Lock screen to enforce typing break</guilabel> box.
+ </para>
<figure id="fig-keyboard-break">
<title>Typing Break Properties</title>
<mediaobject>
@@ -119,6 +122,9 @@
</textobject>
</mediaobject>
</figure>
+ <para>
+ To increase or decrease the amount of time you want to be allowed to type before the break is enforced, click the up or down button next to the <guilabel>Work interval lasts</guilabel> label respectively. You can do the same with the <guilabel>Break interval lasts</guilabel> setting to alter the length of the break itself. Finally, check the <guilabel>Allow postponing of breaks</guilabel> if you want to be able to delay the break in case you need to finish the work. The changes take effect immediately.
+ </para>
<figure id="fig-keyboard-break-take">
<title>Taking a break</title>
<mediaobject>
@@ -130,5 +136,14 @@
</textobject>
</mediaobject>
</figure>
+ <para>
+ Next time you reach the time limit, you will be presented with a screen advising you to take a break, and a clock displaying the remaining time. If you enabled it, the <guibutton>Postpone Break</guibutton> button will be located at the bottom right corner of the screen.
+ </para>
+ <note>
+ <title>Note: Use This Option Wisely</title>
+ <para>
+ Although it can reduce the risk of a wrist injury, enforcing the typing break can also cause troubles on its own. Having to struggle with a locked screen every time you want to finish a sentence can interrupt the natural flow of your thoughts, not to mention decrease your productivity.
+ </para>
+ </note>
</section>
</chapter>
13 years, 10 months
[deployment-guide/comm-rel: 22/74] Email: mhlavink: fix /etc/dovecot/dovecot.conf
by dsilas
commit 308a002e03f666b9c23894b848f53a4eb67988b5
Author: Douglas Silas <dhensley(a)redhat.com>
Date: Thu Jun 24 11:45:54 2010 +0200
Email: mhlavink: fix /etc/dovecot/dovecot.conf
en-US/Email.xml | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
---
diff --git a/en-US/Email.xml b/en-US/Email.xml
index 1a468ad..a014ccf 100644
--- a/en-US/Email.xml
+++ b/en-US/Email.xml
@@ -113,7 +113,7 @@
continuation="restarts"
inheritnum="ignore">
<listitem>
- <para>Edit <filename>/etc/dovecot.conf</filename> to make sure protocols variable contains pop3. For example:</para>
+ <para>Edit <filename>/etc/dovecot/dovecot.conf</filename> to make sure protocols variable contains pop3. For example:</para>
<screen>protocols = imap imaps pop3 pop3s
</screen>
</listitem>
@@ -351,7 +351,7 @@
<para>To add the desired functionality to Sendmail, edit the <filename>/etc/mail/sendmail.mc</filename> file as the root user. Once you are finished, restart the <application>Sendmail</application> service and, if the <package>m4</package> package is installed, the m4 macro processor will automatically generate a new <filename>sendmail.cf</filename> configuration file:</para>
<screen>
<command>service sendmail restart</command>
- </screen>
+ </screen>
<!--mlichvar: also happens automatically
When finished, use the <command>m4</command> macro processor to generate a new <filename>sendmail.cf</filename> by executing the following command:</para>
<screen>
13 years, 10 months
[deployment-guide/comm-rel: 20/74] Merge branch 'master' of git+ssh://git.engineering.redhat.com/srv/git/users/dhensley/Deployment_Guid
by dsilas
commit 4d5084fe5459f3a69e01cd841d252cbee05af6be
Merge: bab4105... 8e932ac...
Author: Martin Prpic <mprpic(a)redhat.com>
Date: Wed Jun 23 17:10:24 2010 +0200
Merge branch 'master' of git+ssh://git.engineering.redhat.com/srv/git/users/dhensley/Deployment_Guide
en-US/Console_Access.xml | 154 +--
en-US/Controlling_Access_to_Services.xml | 882 ++++++++++----
en-US/General_Parameters_and_Modules.xml | 56 +-
en-US/Keyboard_Configuration.xml | 178 ++-
en-US/Network_Configuration.xml | 1226 +++++++++++--------
en-US/Network_Interfaces.xml | 16 +-
en-US/PackageKit.xml | 83 +-
en-US/RPM.xml | 93 +-
en-US/SSSD.xml | 501 ++++++---
en-US/Yum.xml | 143 ++-
.../Network_Configuration-NM-All_applet_states.png | Bin 0 -> 11378 bytes
...work_Configuration-NM-Connect_automatically.png | Bin 0 -> 19915 bytes
...Configuration-NM-Editing_Wired_Connection_1.png | Bin 0 -> 56373 bytes
...figuration-NM-Editing_Wireless_Connection_1.png | Bin 0 -> 76055 bytes
...iguration-NM-Wireless_Auto_Connections_List.png | Bin 0 -> 83527 bytes
...uration-NM-Wireless_authentication_required.png | Bin 0 -> 70411 bytes
..._Configuration-NM_applet-signal_strength_75.png | Bin 0 -> 2292 bytes
...ntrolling-access-to-services-authentication.png | Bin 0 -> 19489 bytes
.../controlling-access-to-services-ntsysv.png | Bin 0 -> 110269 bytes
...ng-access-to-services-service_configuration.png | Bin 0 -> 146999 bytes
...rolling-access-to-services-service_disabled.png | Bin 0 -> 864 bytes
...trolling-access-to-services-service_enabled.png | Bin 0 -> 912 bytes
...trolling-access-to-services-service_running.png | Bin 0 -> 707 bytes
...rolling-access-to-services-service_selected.png | Bin 0 -> 617 bytes
...trolling-access-to-services-service_stopped.png | Bin 0 -> 734 bytes
...trolling-access-to-services-service_unknown.png | Bin 0 -> 725 bytes
...ontrolling-access-to-services-service_wrong.png | Bin 0 -> 697 bytes
.../keyboard-configuration-applet-addition.png | Bin 0 -> 18519 bytes
.../keyboard-configuration-applet-observation.png | Bin 0 -> 15341 bytes
.../keyboard-configuration-applet-selection.png | Bin 0 -> 115084 bytes
en-US/images/keyboard-configuration-break-take.png | Bin 0 -> 75595 bytes
en-US/images/keyboard-configuration-break.png | Bin 0 -> 171411 bytes
.../images/keyboard-configuration-layouts-new.png | Bin 0 -> 29253 bytes
.../keyboard-configuration-layouts-prioritize.png | Bin 0 -> 5071 bytes
.../keyboard-configuration-layouts-separate.png | Bin 0 -> 6495 bytes
.../images/keyboard-configuration-layouts-test.png | Bin 0 -> 45470 bytes
en-US/images/keyboard-configuration-layouts.png | Bin 0 -> 154144 bytes
en-US/images/keyboardconfig.png | Bin 10487 -> 0 bytes
en-US/images/ntsysv.png | Bin 15885 -> 0 bytes
en-US/images/serviceconf.png | Bin 27775 -> 0 bytes
40 files changed, 2123 insertions(+), 1209 deletions(-)
---
13 years, 10 months
[deployment-guide/comm-rel: 19/74] added the authconfig tool section
by dsilas
commit bab41052945b8e10b556e6b7b5862d5c9c18fc79
Author: Martin Prpic <mprpic(a)redhat.com>
Date: Wed Jun 23 17:08:44 2010 +0200
added the authconfig tool section
en-US/.markdown | 1 +
en-US/Authentication_Configuration.xml | 280 +++++++++++++++++++++++++++++++-
2 files changed, 275 insertions(+), 6 deletions(-)
---
diff --git a/en-US/.markdown b/en-US/.markdown
new file mode 100644
index 0000000..8b13789
--- /dev/null
+++ b/en-US/.markdown
@@ -0,0 +1 @@
+
diff --git a/en-US/Authentication_Configuration.xml b/en-US/Authentication_Configuration.xml
index 95e64b1..6015c71 100644
--- a/en-US/Authentication_Configuration.xml
+++ b/en-US/Authentication_Configuration.xml
@@ -1,10 +1,278 @@
<?xml version='1.0'?>
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
]>
-<chapter
- id="ch-Authentication_Configuration">
+<chapter id="ch-Authentication_Configuration">
<title>Authentication Configuration</title>
- <xi:include
- xmlns:xi="http://www.w3.org/2001/XInclude"
- href="SSSD.xml" />
-</chapter>
+ <section id="sect-The_Authentication_Configuration_Tool">
+ <title>The Authentication Configuration Tool</title>
+ <indexterm significance="normal">
+ <primary>
+ <application>Authentication Configuration Tool</application>
+ </primary>
+ </indexterm>
+ <indexterm significance="normal">
+ <primary>authentication</primary>
+ </indexterm>
+ <para>When a user logs in to a &MAJOROS; system, the username and password combination must be verified, or <firstterm>authenticated</firstterm>, as a valid and active user. Sometimes the information to verify the user is located on the local system, and other times the system defers the authentication to a user database on a remote system.</para>
+ <para>The <application>Authentication Configuration Tool</application> provides a graphical interface for configuring user information retrieval from LDAP, NIS, and Winbind user account databases. This tool also allows you to configure Kerberos to be used as the authentication protocol when using LDAP or NIS.</para>
+ <note>
+ <title>Note</title>
+ <para>If you configured a medium or high security level during installation (or with the <application>Security Level Configuration Tool</application>), then the firewall will prevent NIS (Network Information Service) authentication. <remark>Is this still true?</remark>
+ </para>
+ </note>
+ <indexterm significance="normal">
+ <primary>
+ <command>system-config-authentication</command>
+ </primary>
+ <see>
+ <application>Authentication Configuration Tool</application>
+ </see>
+ </indexterm>
+ <indexterm significance="normal">
+ <primary>
+ <command>authconfig</command>
+ </primary>
+ <see>
+ <application>Authentication Configuration Tool</application>
+ </see>
+ </indexterm>
+ <para>To start the graphical version of the <application>Authentication Configuration Tool</application> from the desktop, select the System (on the panel) > <guimenuitem>Administration</guimenuitem> > <guimenuitem>Authentication</guimenuitem> or type the command <command>system-config-authentication</command> at a shell prompt (for example, in an <application>XTerm</application> or a <application>GNOME</application> terminal).</para>
+ <important>
+ <title>Important</title>
+ <para>After exiting the authentication program, any changes you made take effect immediately.</para>
+ </important>
+ <section id="sect-The_Authentication_Configuration_Tool-Identity_and_Authentication">
+ <title>Identity & Authentication</title>
+ <para>
+ The <guilabel>Identity & Authentication</guilabel> tab allows you to configure how users should be authenticated, and has several options for each method of authentication. To select which user account database should be used, select an option from the drop-down list.
+ </para>
+ <para>
+ The following list explains what each option configures:
+ </para>
+ <bridgehead>LDAP</bridgehead>
+ <para>The <guilabel>LDAP</guilabel> option instructs the system to retrieve user information via LDAP. It contains the following specifications:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <guilabel>LDAP Search Base DN</guilabel> — Specifies that user information should be retrieved using the listed Distinguished Name (DN).</para>
+ </listitem>
+ <listitem>
+ <para>
+ <guilabel>LDAP Server</guilabel> — Specifies the IP address of the <systemitem class="service">LDAP</systemitem>server.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <guilabel>Use TLS to encrypt connections</guilabel> — When enabled, <systemitem class="protocol">Transport Layer Security</systemitem> will be used to encrypt passwords sent to the <systemitem class="service">LDAP</systemitem> server. The <guibutton>Download CA Certificate</guibutton> option allows you to specify a URL from which to download a valid <firstterm>CA (Certificate Authority) Certificate</firstterm>. A valid CA Certificate must be in PEM (Privacy Enhanced Mail) format.</para>
+ <important>
+ <title>Important</title>
+ <para>
+ The <guilabel>Use TLS to encrypt connections</guilabel> option must not be ticked if an <systemitem class="protocol">ldaps://</systemitem> server address is specified in the <guilabel>LDAP Server</guilabel> field.
+ </para>
+ </important>
+ <para>For more information about CA Certificates, refer to <citetitle pubwork="section">Section 22.8.2, "An Overview of Certificates and Security"</citetitle> in the <citetitle>Deployment Guide</citetitle><!--TBD6: link to the Section 22.8.2, “An Overview of Certificates and Security” section of the Deployment Guide -->.</para>
+ </listitem>
+ </itemizedlist>
+ <para>The <filename>openldap-clients</filename> package must be installed for this option to work.</para>
+ <para>For more information about LDAP, refer to <citetitle pubwork="chapter">Chapter 25, "Lightweight Directory Access Protocol (LDAP)"</citetitle> in the <citetitle>Deployment Guide</citetitle><!-- TBD6: link to the Chapter 25, "Lightweight Directory Access Protocol (LDAP)" chapter in DG. -->
+ </para>
+ <para>
+ LDAP provides the following methods of authentication:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <guilabel>Kerberos password</guilabel> — This option enables Kerberos authentication. It contains the following specifications:
+ <itemizedlist>
+ <listitem>
+ <para>
+ <guilabel>Realm</guilabel> — Configures the realm for the Kerberos server. The realm is the network that uses Kerberos, composed of one or more KDCs and a potentially large number of clients.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <guilabel>KDCs</guilabel> — Defines the Key Distribution Centers (KDC), which are servers that issue Kerberos tickets.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <guilabel>Admin Servers</guilabel> — Specifies the administration server(s) running <command>kadmind</command>.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ <para>
+ The <guimenu>Kerberos Settings</guimenu> dialog also allows you to use DNS to resolve hosts to realms and locate KDCs for realms.
+ </para>
+ <para>
+ The <filename>krb5-libs</filename> and <filename>krb5-workstation</filename> packages must be installed for this option to work. For more information about Kerberos, refer to <citetitle pubwork="section">Section 43.6, “Kerberos”</citetitle> in the <citetitle>Deployment Guide</citetitle><!-- TBD6: link to the Section 43.6, “Kerberos” section in DG -->.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <guilabel>LDAP password</guilabel> — This option instructs standard PAM-enabled applications to use LDAP authentication with options specified in the User Account Configuration of LDAP. When using this option, you must provide an <systemitem class="protocol">ldaps://</systemitem> server address or use TLS for LDAP authentication.
+ </para>
+ </listitem>
+ </itemizedlist>
+
+ <bridgehead>NIS</bridgehead>
+ <para>
+ The <guilabel>NIS</guilabel> option configures the system to connect to an NIS server (as an NIS client) for user and password authentication. To configure this option, specify the NIS domain and NIS server. If the NIS server is not specified, the daemon attempts to find it via broadcast.
+ </para>
+ <para>The <package>ypbind</package> package must be installed for this option to work. If the NIS user account databse is used, the <systemitem class="daemon">portmap</systemitem> and <systemitem class="daemon">ypbind</systemitem> services are started and are also enabled to start at boot time.</para>
+ <para>For more information about NIS, refer to <citetitle pubwork="section">"Section 43.2.3, Securing NIS"</citetitle> in the <citetitle>Deployment Guide</citetitle><!-- TBD6: link to Section 43.2.3, “Securing NIS” section of the DG -->.</para>
+ <para>
+ NIS provides the following methods of authentication:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <guilabel>Kerberos password</guilabel> — This option enables Kerberos authentication. For more information about configuration of the Kerberos authentication method, refer to previous section on LDAP<!-- TBD6: link to the Kerberos password option in the previous section on LDAP -->
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <guilabel>NIS password</guilabel> — TODO <remark>How does NIS password authenticate? Does it store password info on the NIS server and access that?</remark>
+ </para>
+ </listitem>
+ </itemizedlist>
+
+ <bridgehead>Winbind</bridgehead>
+ <para>The <guilabel>Winbind</guilabel> option configures the system to connect to a Windows Active Directory or a Windows domain controller. User information from the specified directory or domain controller can then be accessed, and server authentication options can be configured. It contains the following specifications:</para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <guilabel>Winbind Domain</guilabel> — Specifies the Windows Active Directory or domain controller to connect to.</para>
+ </listitem>
+ <listitem>
+ <para>
+ <guilabel>Security Model</guilabel> — Allows you to select a security model, which configures how clients should respond to Samba. The drop-down list allows you to select any of the following:
+ <itemizedlist>
+ <listitem>
+ <para>
+ <guilabel>ads</guilabel> — This mode instructs Samba to act as a domain member in an Active Directory Server (ADS) realm. To operate in this mode, the <filename>krb5-server</filename> package must be installed, and Kerberos must be configured properly.</para>
+ </listitem>
+ <listitem>
+ <para>
+ <guilabel>domain</guilabel> — In this mode, Samba will attempt to validate the username/password by authenticating it through a Windows NT Primary or Backup Domain Controller, similar to how a Windows NT Server would.</para>
+ </listitem>
+ <listitem>
+ <para>
+ <guilabel>server</guilabel> — In this mode, Samba will attempt to validate the username/password by authenticating it through another SMB server (for example, a Windows NT Server). If the attempt fails, the <guilabel>user</guilabel> mode will take effect instead.</para>
+ </listitem>
+ <listitem>
+ <para>
+ <guilabel>user</guilabel> — This is the default mode. With this level of security, a client must first log in with a valid username and password. Encrypted passwords can also be used in this security mode.</para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <guilabel>Winbind ADS Realm</guilabel> — When the <guilabel>ads</guilabel> Security Model is selected, this allows you to specify the ADS Realm the Samba server should act as a domain member of.</para>
+ </listitem>
+ <listitem>
+ <para>
+ <guilabel>Winbind Domain Controllers</guilabel> — Use this option to specify which domain controller <command>winbind</command> should use. For more information about domain controllers, please refer to <citetitle pubwork="section">Section 20.6.3, "Domain Controller"</citetitle>of the<citetitle>Deployment Guide</citetitle> <!-- TBD6: link to Section 20.6.3, “Domain Controller” section of the DG-->
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <guilabel>Template Shell</guilabel> — When filling out the user information for a Windows NT user, the <command>winbindd</command> daemon uses the value chosen here to to specify the login shell for that user.</para>
+ </listitem>
+ <listitem>
+ <para>
+ <guilabel>Allow offline login</guilabel> — TODO <remark>What does this option do?</remark>
+ </para>
+ </listitem>
+ </itemizedlist>
+
+
+ <para>For more information about the <command>winbindd</command> service, refer to <citetitle pubwork="section">Section 20.2, "Samba Daemons and Related Services"</citetitle> in the <citetitle>Deployment Guide</citetitle>. <!--TBD6 : linke to section Section 20.2, “Samba Daemons and Related Services” in the DG -->
+ </para>
+ <para>
+ Winbind provides only one method of authentication, <guilabel>Winbind password</guilabel>. This method of authentication uses the options specified in the User Account Configuration of Winbind to connect to a Windows Active Directory or a Windows domain controller.
+ </para>
+
+ </section>
+ <section id="sect-The_Authentication_Configuration_Tool-Advanced_Options">
+ <title>Advanced Options</title>
+ <para>
+ The Advanced Options tab allows you to configure the following:
+ </para>
+ <bridgehead>Local Authentication Options</bridgehead>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <guilabel>Enable fingerprint reader support</guilabel> — By checking this option, you enable fingerprint authentication to log in by scanning your finger with the fingerprint reader.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <guilabel>Enable local access control</guilabel> — When enabled, <filename>/etc/security/access.conf</filename> is consulted for authorization of a user.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <guilabel>Password Hashing Algorithm</guilabel> — This option lets you specify which hashing or cryptographic algorithm should be used to encrypt locally stored passwords.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <bridgehead>Other Authentication Options</bridgehead>
+ <para>
+ <guilabel>Create home directories on the first login</guilabel> — When enabled, a home directory of a user is created automatically on his first login if it does not already exist.
+ </para>
+ <bridgehead>Smart Card Authentication Options</bridgehead>
+ <para>
+ <guilabel>Enable smart card support</guilabel> — This option enables smart card authentication. Smart card authentication allows you to log in using a certificate and a key associated with a smart card.
+ </para>
+ <para>
+ When the <guilabel>Enable smart card support</guilabel> option is checked, the following options can be specified:
+ <itemizedlist>
+ <listitem>
+ <para>
+ <guilabel>Card Removal Action</guilabel> — This option defines what action the system performs when the card is removed from the card reader during an active session. Two alternatives are available:
+ <itemizedlist>
+ <listitem>
+ <para>
+ <guilabel>Ignore</guilabel> — The card removal is ignored and the system continues to function as normal.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <guilabel>Lock</guilabel> — The current session is immediately locked.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <guilabel>Require smart card login</guilabel> — Requires the user to login and authenticate with a smart card. It essentially disables any other type of password authentication. This option should not be selected until after you have successfully logged in using a smart card.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ <para>
+ The <package>pam_pkcs11</package> and the <package>coolkey</package> packages must be installed for this option to work. For more information about smart cards, refer to <citetitle pubwork="section">section "4.1. Enabling Smart Card Login on Red Hat Enterprise Linux</citetitle>of the<citetitle>Managing Smart Cards with the Enterprise Security Client</citetitle> guide<!-- TBD6: link to: section "4.1. Enabling Smart Card Login on Red Hat Enterprise Linux" of the "Managing Smart Cards with the Enterprise Security Client" guide found on http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Enterprise_L... or section "2.3.2. Getting Started with your new Smart Card" of the "Security Guide" found on http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Enterprise_L...
y_Guide/#sect-Security_Guide-Single_Sign_on_SSO-->
+
+ </para>
+ </section>
+ <section id="sect-The_Authentication_Configuration_Tool-Command_Line_Version">
+ <title>Command Line Version</title>
+ <para>
+ The <application>Authentication Configuration Tool</application> can also be run as a command line tool with no interface. The command line version can be used in a configuration script or a kickstart script. The authentication options are summarized in <!--<xref linkend="tb-authconfig-cmd-line"/>-->.
+ </para>
+ <note>
+ <title>Tip</title>
+ <para>These options can also be found in the <command>authconfig</command> man page or by typing <command>authconfig --help</command> at the shell prompt.</para>
+ </note>
+ <remark>I have some questions about the commands listed under "authconfig --help". Is there a need for a "--enablemd5" option if the option "--passalgo=<descrypt|bigcrypt|md5|sha256|sha512>" chooses the algorithm to be used? Same goes for some commands that are not present in the new GUI, like "--enablesmbauth" (and all SMB related commands), "--enablehesiod" or "--enablewins". Are these features you can still use but are not present in the GUI? </remark>
+
+ </section>
+ </section>
+
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="SSSD.xml" />
+ </chapter>
+
13 years, 10 months
[deployment-guide/comm-rel: 18/74] Merge branch 'jarek'
by dsilas
commit 8e932ac9d278fe43221a82db69e161497a6bee82
Merge: 5d7246f... 21902df...
Author: Douglas Silas <dhensley(a)redhat.com>
Date: Wed Jun 23 16:53:17 2010 +0200
Merge branch 'jarek'
en-US/Controlling_Access_to_Services.xml | 2 +-
en-US/Keyboard_Configuration.xml | 178 ++++++++++++++------
.../keyboard-configuration-applet-addition.png | Bin 0 -> 18519 bytes
.../keyboard-configuration-applet-observation.png | Bin 0 -> 15341 bytes
.../keyboard-configuration-applet-selection.png | Bin 0 -> 115084 bytes
en-US/images/keyboard-configuration-break-take.png | Bin 0 -> 75595 bytes
en-US/images/keyboard-configuration-break.png | Bin 0 -> 171411 bytes
.../images/keyboard-configuration-layouts-new.png | Bin 0 -> 29253 bytes
.../keyboard-configuration-layouts-prioritize.png | Bin 0 -> 5071 bytes
.../keyboard-configuration-layouts-separate.png | Bin 0 -> 6495 bytes
.../images/keyboard-configuration-layouts-test.png | Bin 0 -> 45470 bytes
en-US/images/keyboard-configuration-layouts.png | Bin 0 -> 154144 bytes
en-US/images/keyboardconfig.png | Bin 10487 -> 0 bytes
13 files changed, 130 insertions(+), 50 deletions(-)
---
13 years, 10 months
[deployment-guide/comm-rel: 17/74] Merge branch 'flo'
by dsilas
commit 5d7246f9d080f18941ce74ef7c38feceb76e513a
Merge: 5ebf33b... 260b4cb...
Author: Douglas Silas <dhensley(a)redhat.com>
Date: Wed Jun 23 16:53:12 2010 +0200
Merge branch 'flo'
Conflicts:
en-US/RPM.xml
en-US/PackageKit.xml | 87 +++++++++++++++++++++++++++++++----------------
en-US/RPM.xml | 91 ++++++++++++++++++++++++++------------------------
en-US/Yum.xml | 4 +--
3 files changed, 105 insertions(+), 77 deletions(-)
---
diff --cc en-US/RPM.xml
index f1eecde,481111a..39cb83c
--- a/en-US/RPM.xml
+++ b/en-US/RPM.xml
@@@ -27,7 -27,8 +27,8 @@@
<para>When installing a package, ensure it is compatible with your operating system and processor architecture. This can usually be determined by checking the package name. Many of the following examples show RPM packages compiled for the AMD64/Intel 64 computer architectures; thus, the RPM file name ends in <filename>x86_64.rpm</filename>.</para>
</important>
<para>During upgrades, RPM handles configuration files carefully, so that you never lose your customizations—something that you cannot accomplish with regular <filename>.tar.gz</filename> files.</para>
- <para>For the developer, RPM allows you to take software source code and package it into source and binary packages for end users. This process is quite simple and is driven from a single file and optional patches that you create. This clear delineation between <firstterm>pristine</firstterm> sources and your patches along with build instructions eases the maintenance of the package as new versions of the software are released.</para>
- <para>For the developer, RPM allows you to take software source code and package it into source and binary packages for end users.<indexterm><primary>packages</primary><secondary>RPM</secondary><tertiary>source and
++ <para>For the developer, RPM allows you to take software source code and package it into source and binary packages for end users.<indexterm><primary>packages</primary><secondary>RPM</secondary><tertiary>source and
+ binary packages</tertiary></indexterm> This process is quite simple and is driven from a single file and optional patches that you create. This clear delineation between <firstterm>pristine</firstterm> sources and your patches along with build instructions eases the maintenance of the package as new versions of the software are released.</para>
<note>
<title>Note</title>
<para>Because RPM makes changes to your system, you must be logged in as root to install, remove, or upgrade an RPM package.</para>
@@@ -71,11 -72,9 +72,8 @@@
<section
id="s1-rpm-using">
<title>Using RPM</title>
- <indexterm>
- <primary>RPM</primary>
- <secondary>using</secondary>
- </indexterm>
- <para>RPM is able to upgrade and install, uninstall query, and verify RPM packages, as well as preserve configuration file changes. This section provides an overview of all of these functions. For complete details and options, try <command>rpm --help</command> or <command>man rpm</command>. You can also refer to <xref
-
+ <para>RPM has five basic modes of operation<indexterm><primary>RPM</primary><secondary>basic modes</secondary>
+ </indexterm> (not counting package building): installing, uninstalling, upgrading, querying, and verifying. This section contains an overview of each mode. For complete details and options, try <command>rpm --help</command> or <command>man rpm</command>. You can also refer to <xref
linkend="s1-rpm-additional-resources"/> for more information on RPM.</para>
<section
id="s2-rpm-finding">
@@@ -94,7 -95,7 +94,7 @@@
url="http://fedoraproject.org/wiki/EPEL"/> for details on EPEL RPM packages.</para>
</listitem>
<listitem>
-- <para>Unofficial, third-party repositories not affiliated Red Hat also provide RPM packages.</para>
++ <para>Unofficial, third-party repositories not ahffiliated Red Hat also provide RPM packages.</para>
<important>
<title>Important</title>
<para>When considering third-party repositories for use with your &MAJOROS; system, pay close attention to the repository's web site with regard to package compatibility before adding the repository as a package source. Alternate package repositories may offer different, incompatible versions of the same software, including packages already included in the &MAJOROS; repositories.</para>
13 years, 10 months
[deployment-guide/comm-rel: 16/74] RPM: edit comment
by dsilas
commit 5ebf33b5f9eb34cba779cd13faac87f3c66228b7
Author: Douglas Silas <dhensley(a)redhat.com>
Date: Wed Jun 23 16:50:44 2010 +0200
RPM: edit comment
en-US/RPM.xml | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
---
diff --git a/en-US/RPM.xml b/en-US/RPM.xml
index 69baad6..f1eecde 100644
--- a/en-US/RPM.xml
+++ b/en-US/RPM.xml
@@ -105,7 +105,7 @@
url="http://www.redhat.com/apps/support/errata/"/>
</para>
</listitem>
- <!-- TBD6: re-include for RHEL
+ <!-- TBD6: re-include for RHEL once RHN chapter is incorporated
<listitem>
<para>Red Hat Network — Refer to <xref
linkend="ch-rhnetwork"/> for more details on Red Hat Network.</para>
13 years, 10 months
[deployment-guide/comm-rel: 15/74] Replaced the link with a TBD6 comment.
by dsilas
commit 21902df8cb4b5ab92a264b84665de98eead0d5c2
Author: Jaromir Hradilek <jhradile(a)redhat.com>
Date: Wed Jun 23 16:00:50 2010 +0200
Replaced the link with a TBD6 comment.
Since the final version of the referred book is not staged yet and its
future location is unknown, I have replaced the link with a comment
containing the description of what is to be done before the release.
en-US/Controlling_Access_to_Services.xml | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
---
diff --git a/en-US/Controlling_Access_to_Services.xml b/en-US/Controlling_Access_to_Services.xml
index 9027d71..927d943 100644
--- a/en-US/Controlling_Access_to_Services.xml
+++ b/en-US/Controlling_Access_to_Services.xml
@@ -639,7 +639,7 @@ wpa_supplicant (pid 1227) is running...</screen>
<variablelist>
<varlistentry>
<term>
- <citetitle pubwork="book">Security Guide</citetitle> — <ulink url="http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6.0/html/Securi..." />
+ <citetitle pubwork="book">Security Guide</citetitle> <!-- TBD6: link to: title page of Security Guide -->
</term>
<listitem>
<para>
13 years, 10 months
[deployment-guide/comm-rel: 14/74] Wrote the Adding the Keyboard Layout Indicator chapter.
by dsilas
commit 9a72326bf0d9bc2ecef91b7342863432c7bebc77
Author: Jaromir Hradilek <jhradile(a)redhat.com>
Date: Wed Jun 23 15:50:15 2010 +0200
Wrote the Adding the Keyboard Layout Indicator chapter.
en-US/Keyboard_Configuration.xml | 9 +++++++++
1 files changed, 9 insertions(+), 0 deletions(-)
---
diff --git a/en-US/Keyboard_Configuration.xml b/en-US/Keyboard_Configuration.xml
index 7b0754e..e775ee3 100644
--- a/en-US/Keyboard_Configuration.xml
+++ b/en-US/Keyboard_Configuration.xml
@@ -63,6 +63,9 @@
</section>
<section id="s1-keyboard-indicator">
<title>Adding the Keyboard Layout Indicator</title>
+ <para>
+ If you want to see what keyboard layout you are currently using, or you would like to switch between different layouts with a single mouse click, add the <application>Keyboard Indicator</application> applet to the panel. To do so, right-click the empty space on the main panel, and select the <guimenuitem>Add to Panel...</guimenuitem> option from the pulldown menu.
+ </para>
<figure id="fig-keyboard-indicator-addition">
<title>Adding a new applet</title>
<mediaobject>
@@ -74,6 +77,9 @@
</textobject>
</mediaobject>
</figure>
+ <para>
+ You will be presented with a list of available applets. Scroll through the list (or start typing <quote>keyboard</quote> to the search field at the top of the window), select <guimenuitem>Keyboard Indicator</guimenuitem>, and click the <guibutton>Add</guibutton> button.
+ </para>
<figure id="fig-keyboard-indicator-selection">
<title>Selecting the <application>Keyboard Indicator</application></title>
<mediaobject>
@@ -85,6 +91,9 @@
</textobject>
</mediaobject>
</figure>
+ <para>
+ The applet appears immediately, displaying the shortened name of the country the current layout is associated with. To display the actual variant, hover the pointer over the applet icon.
+ </para>
<figure id="fig-keyboard-indicator-observation">
<title>The <application>Keyboard Indicator</application> applet</title>
<mediaobject>
13 years, 10 months