[deployment-guide/comm-rel: 16/26] Added a chapter outline to the introduction.

[dsilas]

commit 6fbca30551d6a664e4fefbdaf2bc800229daa684
Author: Jaromir Hradilek 
Date:   Thu Jun 17 11:02:35 2010 +0200

Added a chapter outline to the introduction.

en-US/Controlling_Access_to_Services.xml |    5 ++++-
 1 files changed, 4 insertions(+), 1 deletions(-)
---
diff --git a/en-US/Controlling_Access_to_Services.xml b/en-US/Controlling_Access_to_Services.xml
index 968883e..93f5b4c 100644
--- a/en-US/Controlling_Access_to_Services.xml
+++ b/en-US/Controlling_Access_to_Services.xml
@@ -6,10 +6,13 @@
   <para>
     Maintaining security on your system is extremely important, and one approach for this task is to manage access to system services carefully. Your system may need to provide open access to particular services (for example, <command>httpd</command> if you are running a web server). However, if you do not need to provide a service, you should turn it off to minimize your exposure to possible bug exploits.
   </para>
+  <para>
+    This chapter explains the concept of runlevels, and describes how to set the default one. It also covers the setup of the services to be run in each of them using three different utilities: the <application>Service Configuration</application> graphical application, the <application>ntsysv</application> text user interface, and the <application>chkconfig</application> command line tool.
+  </para>
   <important lang="en-US,as-IN,bn-IN,gu-IN,hi-IN,kn-IN,ml-IN,mr-IN,or-IN,pa-IN,si-LK,ta-IN,te-IN">
     <title>Important</title>
     <para>
-      When you allow access for new services, always remember that both the firewall and <application>SELinux</application> need to be configured as well. One of the most common mistakes committed when configuring a new service is neglecting to implement the necessary firewall configuration and SELinux policies to allow access for it. Refer to <citetitle pubwork="book">Security Guide: A Guide to Securing Red Hat Enterprise Linux</citetitle> for more information.
+      When you allow access for new services, always remember that both the firewall and <application>SELinux</application> need to be configured as well. One of the most common mistakes committed when configuring a new service is neglecting to implement the necessary firewall configuration and SELinux policies to allow access for it. Refer to <citetitle pubwork="book">Security Guide: A Guide to Securing Red Hat Enterprise Linux</citetitle> (see <xref linkend="s1-services-additional-resources" />) for more information.
     </para>
   </important>
   <section id="s1-services-runlevels">