--- xml/htdocs/doc/en/handbook/hb-net-advanced.xml	2009/02/13 04:40:27	1.15
+++ xml/htdocs/doc/en/handbook/hb-net-advanced.xml	2011/08/14 16:12:13	1.16
@@ -4,7 +4,7 @@
 <!-- The content of this document is licensed under the CC-BY-SA license -->
 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
 
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-net-advanced.xml,v 1.15 2009/02/13 04:40:27 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-net-advanced.xml,v 1.16 2011/08/14 16:12:13 swift Exp $ -->
 
 <sections>
 
@@ -13,8 +13,8 @@
 before we learn about modular networking.
 </abstract>
 
-<version>8.1</version>
-<date>2009-02-12</date>
+<version>9</version>
+<date>2011-08-13</date>
 
 <section>
 <title>Advanced Configuration</title>
@@ -128,44 +128,23 @@
 
 <p>
 Init scripts in <path>/etc/init.d</path> can depend on a specific network
-interface or just net. <c>net</c> can be defined in <path>/etc/conf.d/rc</path>
-to mean different things using the <c>RC_NET_STRICT_CHECKING</c> variable.
+interface or just net. All network interfaces in Gentoo's init system provide
+what is called <e>net</e>.
 </p>
 
-<table>
-<tr>
-  <th>Value</th>
-  <th>Description</th>
-</tr>
-<tr>
-  <ti><c>none</c></ti>
-  <ti>The <path>net</path> service is always considered up</ti>
-</tr>
-<tr>
-  <ti><c>no</c></ti>
-  <ti>
-    This basically means that at least one <path>net.*</path> service besides
-    <path>net.lo</path> must be up.  This can be used by notebook users that
-    have a WIFI and a static NIC, and only wants one up at any given time to
-    have the net service seen as up.
-  </ti>
-</tr>
-<tr>
-  <ti><c>lo</c></ti>
-  <ti>
-    This is the same as the <c>no</c> option, but <path>net.lo</path> is also
-    counted. This should be useful to people that do not care about any specific
-    interface being up at boot.
-  </ti>
-</tr>
-<tr>
-  <ti><c>yes</c></ti>
-  <ti>
-    For this ALL network interfaces MUST be up for the <path>net</path> service
-    to be considered up.
-  </ti>
-</tr>
-</table>
+<p>
+If, in <path>/etc/rc.conf</path>, <c>rc_depend_strict="YES"</c> is set, then all
+network interfaces that provide net must be active before a dependency on "net"
+is assumed to be met. In other words, if you have a <path>net.eth0</path> and
+<path>net.eth1</path> and an init script depends on "net", then both must be
+enabled.
+</p>
+
+<p>
+On the other hand, if <c>rc_depend_strict="NO"</c> is set, then the "net"
+dependency is marked as resolved the moment at least one network interface is
+brought up.
+</p>
 
 <p>
 But what about <path>net.br0</path> depending on <path>net.eth0</path> and
@@ -176,21 +155,19 @@
 </p>
 
 <p>
-The answer is making your own <c>depend()</c> function in
+The answer is defining an <c>rc_need_</c> setting in
 <path>/etc/conf.d/net</path>.
 </p>
 
 <pre caption="net.br0 dependency in /etc/conf.d/net">
-<comment># You can use any dependency (use, after, before) as found in current scripts</comment>
-depend_br0() {
-  need net.eth0 net.eth1
-}
+rc_need_br0="net.eth0 net.eth1"
 </pre>
 
 <p>
 For a more detailed discussion about dependency, consult the section <uri
 link="?part=2&amp;chap=4#doc_chap4">Writing Init Scripts</uri> in the Gentoo
-Handbook.
+Handbook. More information about <path>/etc/rc.conf</path> is available as
+comments within that file.
 </p>
 
 </body>