jkt 05/12/21 12:20:43 Modified: xml/htdocs/doc/en/handbook hb-net-advanced.xml Log: coding style fixes, *no content change*
Revision Changes Path 1.10 +28 -31 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.10&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.10&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.9&r2=1.10&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.9 retrieving revision 1.10 diff -u -r1.9 -r1.10 --- hb-net-advanced.xml 21 Dec 2005 11:49:14 -0000 1.9 +++ hb-net-advanced.xml 21 Dec 2005 12:20:43 -0000 1.10 @@ -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.9 2005/12/21 11:49:14 jkt Exp $ --> +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-net-advanced.xml,v 1.10 2005/12/21 12:20:43 jkt Exp $ --> <sections> @@ -16,10 +16,10 @@ <body> <p> -The config_eth0 variable is the heart of an interface's configuration. -It's a high level instruction list for configuring the interface (eth0 in -this case). Each command in the instruction list is performed sequentially. -The interface is deemed OK if at least one command works. +The config_eth0 variable is the heart of an interface's configuration. It's a +high level instruction list for configuring the interface (eth0 in this case). +Each command in the instruction list is performed sequentially. The interface is +deemed OK if at least one command works. </p> <p> @@ -51,9 +51,9 @@ 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. + 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> @@ -98,9 +98,9 @@ <note> When using the ifconfig module and adding more than one address, interface 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. +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. </note> <impo> @@ -109,8 +109,8 @@ </impo> <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#apipa">APIPA</uri> and <uri +link="?part=4&chap=3#dhcp">DHCP</uri> are discussed later. </note> </body> @@ -137,35 +137,33 @@ <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. + 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. + 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. + For this ALL network interfaces MUST be up for the 'net' service to be + considered up. </ti> </tr> </table> <p> -But what about net.br0 depending on net.eth0 and net.eth1? -net.eth1 may be a wireless or ppp device that needs configuration before it -can be added to the bridge. -This cannot be done in <path>/etc/init.d/net.br0</path> as that's a symbolic -link to net.lo +But what about net.br0 depending on net.eth0 and net.eth1? net.eth1 may be a +wireless or ppp device that needs configuration before it can be added to the +bridge. This cannot be done in <path>/etc/init.d/net.br0</path> as that's a +symbolic link to net.lo </p> <p> @@ -180,10 +178,9 @@ </pre> <p> -For a more detailed discussion about dependency, consult the section -<uri -link="?part=2&chap=4#doc_chap4">Writing -Init Scripts</uri> in the Gentoo Handbook. +For a more detailed discussion about dependency, consult the section <uri +link="?part=2&chap=4#doc_chap4">Writing Init Scripts</uri> in the Gentoo +Handbook. </p> </body> -- [email protected] mailing list
