swift 05/06/14 09:47:20 Modified: xml/htdocs/doc/en/handbook hb-net-advanced.xml Log: Coding style, first run, no content change
Revision Changes Path 1.5 +72 -72 xml/htdocs/doc/en/handbook/hb-net-advanced.xml file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-net-advanced.xml?rev=1.5&content-type=text/x-cvsweb-markup&cvsroot=gentoo plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-net-advanced.xml?rev=1.5&content-type=text/plain&cvsroot=gentoo diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-net-advanced.xml.diff?r1=1.4&r2=1.5&cvsroot=gentoo Index: hb-net-advanced.xml =================================================================== RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-net-advanced.xml,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- hb-net-advanced.xml 13 Jun 2005 07:03:41 -0000 1.4 +++ hb-net-advanced.xml 14 Jun 2005 09:47:20 -0000 1.5 @@ -2,9 +2,9 @@ <!DOCTYPE sections SYSTEM "/dtd/book.dtd"> <!-- The content of this document is licensed under the CC-BY-SA license --> -<!-- See http://creativecommons.org/licenses/by-sa/2.0 --> +<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> -<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-net-advanced.xml,v 1.4 2005/06/13 07:03:41 swift Exp $ --> +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-net-advanced.xml,v 1.5 2005/06/14 09:47:20 swift Exp $ --> <sections> @@ -27,36 +27,35 @@ </p> <table> - <tr> - <th>Command</th> - <th>Description</th> - </tr> - <tr> - <ti>null</ti> - <ti>Do nothing</ti> - </tr> - <tr> - <ti>noop</ti> - <ti> - If the interface is up and there is an address then abort configuration - successfully - </ti> - </tr> - <tr> - <ti>an IPv4 or IPv6 address</ti> - <ti>Add the address to the interface</ti> - </tr> - <tr> - <ti> - dhcp, adsl or apipa<br/> - (or a custom command from a 3rd party module) - </ti> - <ti> - Run the module which provides the command. For example "dhcp" will - run a module that provides dhcp which can be one of either dhcpcd, - udhcpc, dhclient or pump. - </ti> - </tr> +<tr> + <th>Command</th> + <th>Description</th> +</tr> +<tr> + <ti>null</ti> + <ti>Do nothing</ti> +</tr> +<tr> + <ti>noop</ti> + <ti> + If the interface is up and there is an address then abort configuration + successfully + </ti> +</tr> +<tr> + <ti>an IPv4 or IPv6 address</ti> + <ti>Add the address to the interface</ti> +</tr> +<tr> + <ti> + dhcp, adsl or apipa (or a custom command from a 3rd party module) + </ti> + <ti> + Run the module which provides the command. For example "dhcp" will + run a module that provides dhcp which can be one of either dhcpcd, + udhcpc, dhclient or pump. + </ti> +</tr> </table> <p> @@ -101,7 +100,7 @@ aliases are created for each extra address. So with the above two examples you will get interfaces eth0, eth0:1 and eth0:2. You cannot do anything special with these interfaces as the kernel and other -programs will just treat eth0:1 and eth0:2 as eth0 +programs will just treat eth0:1 and eth0:2 as eth0. </note> <impo> @@ -111,7 +110,7 @@ <note> <uri link="?part=4&chap=3#apipa">APIPA</uri> and -<uri link="?part=4&chap=3#dhcp">DHCP</uri> are discussed later +<uri link="?part=4&chap=3#dhcp">DHCP</uri> are discussed later. </note> </body> @@ -121,44 +120,45 @@ <title>Network Dependencies</title> <body> -<p>Init scripts in <path>/etc/init.d</path> can depend on a specific network +<p> +Init scripts in <path>/etc/init.d</path> can depend on a specific network interface or just net. "net" can be defined in <path>/etc/conf.d/rc</path> to mean different things using the <c>RC_NET_STRICT_CHECKING</c> variable. </p> <table> - <tr> - <th>Value</th> - <th>Description</th> - </tr> - <tr> - <ti>none</ti> - <ti>The net service is always considered up</ti> - </tr> - <tr> - <ti>no</ti> - <ti> - This basically means that at least one net.* service besides net.lo - 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>lo</ti> - <ti> - This is the same as the 'no' option, but net.lo 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>yes</ti> - <ti> - For this ALL network interfaces MUST be up for the 'net' service to - be considered up. - </ti> - </tr> +<tr> + <th>Value</th> + <th>Description</th> +</tr> +<tr> + <ti>none</ti> + <ti>The net service is always considered up</ti> +</tr> +<tr> + <ti>no</ti> + <ti> + This basically means that at least one net.* service besides net.lo + 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>lo</ti> + <ti> + This is the same as the 'no' option, but net.lo 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>yes</ti> + <ti> + For this ALL network interfaces MUST be up for the 'net' service to + be considered up. + </ti> +</tr> </table> <p> @@ -203,11 +203,11 @@ <p> However, there is no hard and fast rule that states interface names must be -ethx. In fact, many wireless interfaces have names like wlanx, rax as well as ethx. -Also, some user defined interfaces such as bridges can be given any name, such -as foo. To make life more interesting, wireless Access Points can have names with -non alpha-numeric characters in them - this is important because you can configure -networking parameters per ESSID. +ethx. In fact, many wireless interfaces have names like wlanx, rax as well as +ethx. Also, some user defined interfaces such as bridges can be given any name, +such as foo. To make life more interesting, wireless Access Points can have +names with non alpha-numeric characters in them - this is important because +you can configure networking parameters per ESSID. </p> -- [email protected] mailing list
