[deployment-guide/comm-rel: 3/26] Removed all tabs.

dsilas dsilas at fedoraproject.org
Mon Jun 21 11:41:47 UTC 2010


commit 5093558e6d521167a6bb4e3573f4a287b5ec2e05
Author: Jaromir Hradilek <jhradile at redhat.com>
Date:   Fri Jun 11 12:25:31 2010 +0200

    Removed all tabs.
    
    I have replaced all '\t' characters with two spaces to preserve the
    overall document formatting and correct indentation.

 en-US/Console_Access.xml |   30 +++++++++++++++---------------
 1 files changed, 15 insertions(+), 15 deletions(-)
---
diff --git a/en-US/Console_Access.xml b/en-US/Console_Access.xml
index 341fd92..e713065 100644
--- a/en-US/Console_Access.xml
+++ b/en-US/Console_Access.xml
@@ -133,7 +133,7 @@
       <primary>console</primary>
       <secondary>making files accessible from</secondary>
     </indexterm>
-		<!--TBD6: /etc/security/console.perms.d/* are obsolete directories for Fedora 12-->
+    <!--TBD6: /etc/security/console.perms.d/* are obsolete directories for Fedora 12-->
     <para>The default settings for individual device classes and permission definitions are defined in <filename>/etc/security/console.perms.d/50-default.perms</filename>. To edit file and device permissions, it is advisable to create a new default file in <filename>/etc/security/console.perms.d/</filename> containing your preferred settings for a specified set of files or devices. The name of the new default file must begin with a number higher than 50 (for example, <filename>51-default.perms</filename>) in order to override <filename>50-default.perms</filename>.</para>
     <para>To do this, create a new file named <filename>51-default.perms</filename> in <filename>/etc/security/console.perms.d/</filename>:</para>
     <screen>
@@ -145,8 +145,8 @@
     <screen>&lt;scanner&gt;=/dev/scanner /dev/usb/scanner*</screen>
     <para>Of course, you must use the appropriate name for the device. Ensure that <filename>/dev/scanner</filename> is really your scanner and not some other device, such as your hard drive.</para>
     <para>Once you have properly defined a device or file, the second step is to specify its <firstterm>permission definitions</firstterm>. The second section of <filename>/etc/security/console.perms.d/50-default.perms</filename> defines this, with lines similar to the following:</para>
-		<!-- RHEL5:  	ddomingo at redhat.com: above replaces below
-		<para>Once you have properly defined a device or file, the second step is to define what is done with it. Look in the last section of <filename>/etc/security/console.perms</filename> for lines similar to the following:</para> -->
+    <!-- RHEL5:    ddomingo at redhat.com: above replaces below
+    <para>Once you have properly defined a device or file, the second step is to define what is done with it. Look in the last section of <filename>/etc/security/console.perms</filename> for lines similar to the following:</para> -->
     <screen>&lt;console&gt; 0660 &lt;floppy&gt; 0660 root.floppy &lt;console&gt; 0600 &lt;sound&gt; 0640 root &lt;console&gt; 0600 &lt;cdrom&gt; 0600 root.disk</screen>
     <para>To define permissions for a scanner, add a line similar to the following in <filename>51-default.perms</filename>:</para>
     <screen>
@@ -203,28 +203,28 @@
     </indexterm>
     <para>In the PAM configuration file, an application can be configured to use the <firstterm>pam_timestamp</firstterm> module to remember (or cache) a successful authentication attempt. When an application is started and proper authentication is provided (the root password), a timestamp file is created. By default, a successful authentication is cached for five minutes. During this time, any other application that is configured to use <filename>pam_timestamp</filename> and run from the same session is automatically authenticated for the user — the user does not have to enter the root password again.</para>
     <para>This module is included in the <filename>pam</filename> package. To enable this feature, add the following lines to your PAM configuration file in <filename>etc/pam.d/</filename>:</para>
-		<!-- RHEL5:  	ddomingo at redhat.com: above replaces below, less awkwardness
-		<para>This module is included in the <filename>pam</filename> package. To enable this feature, the PAM configuration file in <filename>etc/pam.d/</filename> must include the following lines:</para>
-		 -->
+    <!-- RHEL5:    ddomingo at redhat.com: above replaces below, less awkwardness
+    <para>This module is included in the <filename>pam</filename> package. To enable this feature, the PAM configuration file in <filename>etc/pam.d/</filename> must include the following lines:</para>
+     -->
     <screen>auth include config-util account include config-util session include config-util</screen>
-		<!-- RHEL5:   ddomingo at redhat.com: above replaces below
+    <!-- RHEL5:   ddomingo at redhat.com: above replaces below
 <screen>auth sufficient /lib/security/pam_timestamp.so session optional /lib/security/pam_timestamp.so</screen> -->
     <para>These lines can be copied from any of the <filename>/etc/pam.d/system-config-<replaceable>*</replaceable>
       </filename> configuration files. Note that these lines must be added <emphasis>below</emphasis> any other <computeroutput>auth sufficient</computeroutput>
       <computeroutput>session optional</computeroutput> lines in your PAM configuration file.</para>
-		<!-- RHEL5:  	ddomingo at redhat.com: above replaces below, less awkwardness
-		<para>The first line that begins with <computeroutput>auth</computeroutput> should be after any other <computeroutput>auth sufficient</computeroutput> lines, and the line that begins with
-			<computeroutput>session</computeroutput> should be after any other <computeroutput>session optional</computeroutput> lines.</para>
-		  -->
+    <!-- RHEL5:    ddomingo at redhat.com: above replaces below, less awkwardness
+    <para>The first line that begins with <computeroutput>auth</computeroutput> should be after any other <computeroutput>auth sufficient</computeroutput> lines, and the line that begins with
+      <computeroutput>session</computeroutput> should be after any other <computeroutput>session optional</computeroutput> lines.</para>
+      -->
     <para>If an application configured to use <filename>pam_timestamp</filename> is successfully authenticated from the <!-- RHEL5:  <guimenu>Main Menu Button</guimenu> (on the Panel) -->Applications (the main menu on the panel), the
-			<inlinemediaobject>
-				<imageobject>
-					<imagedata
+      <inlinemediaobject>
+        <imageobject>
+          <imagedata
             fileref="images/pam-icon.png"
             format="PNG"/>
         </imageobject>
       </inlinemediaobject>
-			 icon is displayed in the notification area of the panel if you are running the <application>GNOME</application> or <application>KDE</application> desktop environment. After the authentication expires (the default is five minutes), the icon disappears.</para>
+       icon is displayed in the notification area of the panel if you are running the <application>GNOME</application> or <application>KDE</application> desktop environment. After the authentication expires (the default is five minutes), the icon disappears.</para>
     <para>The user can select to forget the cached authentication by clicking on the icon and selecting the option to forget authentication.</para>
   </section>
   <section


More information about the docs-commits mailing list