- rework this section a little by including an info which applies to

the current state of how the things are done
- add a new paragraph covering the fact that rc.conf is read by sh(1)

PR:		docs/157894
Reviewed by:	gavin, simon, Niclas Zeising

en_US.ISO8859-1/books/handbook/config/chapter.sgml

@@ -252,30 +252,27 @@
     <para>A number of strategies may be applied in clustered
       applications to separate site-wide configuration from
       system-specific configuration in order to keep administration
-      overhead down.  The recommended approach is to place site-wide
-      configuration into another file,
-      such as <filename>/etc/rc.conf.site</filename>, and then include
-      this file into <filename>/etc/rc.conf</filename>, which will
-      contain only system-specific information.</para>
-
-    <para>As <filename>rc.conf</filename> is read by &man.sh.1; it is
-      trivial to achieve this.  For example:</para>
+      overhead down.  The recommended approach is to place
+      system-specific configuration into the
+      <filename>/etc/rc.conf.local</filename> file.  For
+      example:</para>
 
     <itemizedlist>
-      <listitem><para>rc.conf:</para>
-<programlisting>	. /etc/rc.conf.site
-	hostname="node15.example.com"
-	network_interfaces="fxp0 lo0"
-	ifconfig_fxp0="inet 10.1.1.1"</programlisting></listitem>
-      <listitem><para>rc.conf.site:</para>
-<programlisting>	defaultrouter="10.1.1.254"
-	saver="daemon"
-	blanktime="100"</programlisting></listitem>
+      <listitem><para><filename>/etc/rc.conf</filename>:</para>
+
+      <programlisting>sshd_enable="YES"
+keyrate="fast"
+defaultrouter="10.1.1.254"</programlisting></listitem>
+
+      <listitem><para><filename>/etc/rc.conf.local</filename>:</para>
+
+<programlisting>hostname="node1.example.org"
+ifconfig_fxp0="inet 10.1.1.1/8"</programlisting></listitem>
     </itemizedlist>
 
-    <para>The <filename>rc.conf.site</filename> file can then be
+    <para>The <filename>rc.conf</filename> file can then be
       distributed to every system using <command>rsync</command> or a
-      similar program, while the <filename>rc.conf</filename> file
+      similar program, while the <filename>rc.conf.local</filename> file
       remains unique.</para>
 
     <para>Upgrading the system using &man.sysinstall.8;
@@ -283,6 +280,13 @@
       <filename>rc.conf</filename>
       file, so system configuration information will not be lost.</para>
 
+    <tip>
+      <para>The <filename>/etc/rc.conf</filename> configuration file
+	is parsed by &man.sh.1;.  This allows system operators to
+	add a certain amount of logic to this file, which may help to
+	create very complex configuration scenarios.  Please see
+	&man.rc.conf.5; for further information on this topic.</para>
+    </tip>
   </sect1>
 
   <sect1 id="configtuning-appconfig">