From 74ce7a360547f286e1c14a2434627595fce8e787 Mon Sep 17 00:00:00 2001
From: Manuel Canales Esparcia <manuel@linuxfromscratch.org>
Date: Thu, 12 May 2005 20:07:13 +0000
Subject: [PATCH] Tagged etcshells.xml

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@4172 af4574ff-66df-0310-9fd7-8a98e5e911e0
---
 postlfs/config/etcshells.xml | 55 +++++++++++++++++++-----------------
 1 file changed, 29 insertions(+), 26 deletions(-)

diff --git a/postlfs/config/etcshells.xml b/postlfs/config/etcshells.xml
index 3732cf1902..ce81d12941 100644
--- a/postlfs/config/etcshells.xml
+++ b/postlfs/config/etcshells.xml
@@ -6,39 +6,42 @@
 ]>
 
 <sect1 id="postlfs-config-shells" xreflabel="The /etc/shells File">
-<sect1info>
-<othername>$LastChangedBy$</othername>
-<date>$Date$</date>
-</sect1info>
-<?dbhtml filename="etcshells.html"?>
-<title>The /etc/shells File</title>
-<indexterm zone="postlfs-config-shells">
-<primary sortas="e-etc-shells">/etc/shells</primary>
-</indexterm>
+  <?dbhtml filename="etcshells.html"?>
 
-<para>The <filename>shells</filename> file contains a list of 
-login shells on the system. Applications use this file to determine
-whether a shell is valid. For each shell a single line should be
-present, consisting of the shell's path, relative to root.</para>
+  <sect1info>
+    <othername>$LastChangedBy$</othername>
+    <date>$Date$</date>
+  </sect1info>
 
-<para>For example, this file is consulted by <command>chsh</command> to
-determine whether a normal user may change the login shell for her
-own account. If the command name is not listed, the user will be denied of
-change.</para>
+  <title>The /etc/shells File</title>
 
-<para>It is a requirement for applications such as
-<application><acronym>GDM</acronym></application> which does not populate the 
-face browser if it can't find <filename>/etc/shells</filename> or 
-<acronym>FTP</acronym> daemons which traditionally disallow access to users 
-with shells not included in this file.</para>
+  <indexterm zone="postlfs-config-shells">
+    <primary sortas="e-etc-shells">/etc/shells</primary>
+  </indexterm>
 
-<screen><userinput><command>cat &gt; /etc/shells &lt;&lt; "EOF"</command>
-# Begin /etc/shells
+  <para>The <filename>shells</filename> file contains a list of 
+  login shells on the system. Applications use this file to determine
+  whether a shell is valid. For each shell a single line should be
+  present, consisting of the shell's path, relative to root.</para>
+
+  <para>For example, this file is consulted by <command>chsh</command> 
+  to determine whether a normal user may change the login shell for her
+  own account. If the command name is not listed, the user will be denied of
+  change.</para>
+
+  <para>It is a requirement for applications such as
+  <application>GDM</application> which does not populate the 
+  face browser if it can't find <filename>/etc/shells</filename> or 
+  FTP daemons which traditionally disallow access to users 
+  with shells not included in this file.</para>
+
+<screen role="root"><userinput>cat &gt; /etc/shells &lt;&lt; "EOF"
+<literal># Begin /etc/shells
 
 /bin/sh
 /bin/bash
 
-# End /etc/shells
-<command>EOF</command></userinput></screen>
+# End /etc/shells</literal>
+EOF</userinput></screen>
 
 </sect1>