jkt         05/12/21 13:01:38

  Modified:    xml/htdocs/doc/en/handbook hb-net-modules.xml
  Log:
  coding style fixes, *no content change*

Revision  Changes    Path
1.9       +39 -40    xml/htdocs/doc/en/handbook/hb-net-modules.xml

file : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-net-modules.xml?rev=1.9&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-net-modules.xml?rev=1.9&content-type=text/plain&cvsroot=gentoo
diff : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-net-modules.xml.diff?r1=1.8&r2=1.9&cvsroot=gentoo

Index: hb-net-modules.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-net-modules.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- hb-net-modules.xml  7 Sep 2005 19:00:28 -0000       1.8
+++ hb-net-modules.xml  21 Dec 2005 13:01:38 -0000      1.9
@@ -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-modules.xml,v 1.8 
2005/09/07 19:00:28 jkt Exp $ -->
+<!-- $Header: 
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-net-modules.xml,v 1.9 
2005/12/21 13:01:38 jkt Exp $ -->
 
 <sections>
 
@@ -16,18 +16,17 @@
 <body>
 
 <p>
-We now support modular networking scripts, which means we can easily
-add support for new interface types and configuration modules while keeping
-compatibility with existing ones.
+We now support modular networking scripts, which means we can easily add 
support
+for new interface types and configuration modules while keeping compatibility
+with existing ones.
 </p>
 
 <p>
-Modules load by default if the package they need is installed.  If
-you specify a module here that doesn't have its package installed
-then you get an error stating which package you need to install.
-Ideally, you only use the modules setting when you have two or more
-packages installed that supply the same service and you need to prefer
-one over the other.
+Modules load by default if the package they need is installed.  If you specify 
a
+module here that doesn't have its package installed then you get an error
+stating which package you need to install. Ideally, you only use the modules
+setting when you have two or more packages installed that supply the same
+service and you need to prefer one over the other.
 </p>
 
 <pre caption="Module preference">
@@ -51,8 +50,8 @@
 <body>
 
 <p>
-We provide two interface handlers presently: ifconfig and iproute2.
-You need one of these to do any kind of network configuration.
+We provide two interface handlers presently: ifconfig and iproute2. You need 
one
+of these to do any kind of network configuration.
 </p>
 
 <p>
@@ -70,8 +69,8 @@
 
 <p>
 As both ifconfig and iproute2 do very similar things we allow their basic 
-configuration to work with each other. For example both the below code 
-snippets work regardless of which module you are using.
+configuration to work with each other. For example both the below code snippets
+work regardless of which module you are using.
 </p>
 
 <pre caption="ifconfig and iproute2 examples">
@@ -158,8 +157,8 @@
 </table>
      
 <p>
-If you have more than one DHCP client installed, you need to specify which
-one to use - otherwise we default to dhcpcd if available.
+If you have more than one DHCP client installed, you need to specify which one
+to use - otherwise we default to dhcpcd if available.
 </p>
 
 <p>
@@ -189,8 +188,8 @@
 </pre>
 
 <note>
-dhcpcd, udhcpc and pump send the current hostname to the DHCP server by
-default so you don't need to specify this anymore.
+dhcpcd, udhcpc and pump send the current hostname to the DHCP server by default
+so you don't need to specify this anymore.
 </note>
 
 </body>
@@ -239,14 +238,14 @@
 <body>
 
 <p>
-APIPA tries to find a free address in the range 169.254.0.0-169.254.255.255
-by arping a random address in that range on the interface. If no reply is
-found then we assign that address to the interface.
+APIPA tries to find a free address in the range 169.254.0.0-169.254.255.255 by
+arping a random address in that range on the interface. If no reply is found
+then we assign that address to the interface.
 </p>
 
 <p>
-This is only useful for LANs where there is no DHCP server and you don't
-connect directly to the internet and all other computers use APIPA.
+This is only useful for LANs where there is no DHCP server and you don't 
connect
+directly to the internet and all other computers use APIPA.
 </p>
 
 <p>
@@ -273,9 +272,9 @@
 </p>
 
 <p>
-Bonding is used to increase network bandwidth. If you have two network
-cards going to the same network, you can bond them together so your
-applications see just one interface but they really use both network cards.
+Bonding is used to increase network bandwidth. If you have two network cards
+going to the same network, you can bond them together so your applications see
+just one interface but they really use both network cards.
 </p>
 
 <pre caption="bonding configuration in /etc/conf.d/net">
@@ -302,10 +301,10 @@
 </p>
 
 <p>
-Bridging is used to join networks together. For example, you may have a
-server that connects to the internet via an ADSL modem and a wireless
-access card to enable other computers to connect to the internet via the
-ADSL modem. You could create a bridge to join the two interfaces together.
+Bridging is used to join networks together. For example, you may have a server
+that connects to the internet via an ADSL modem and a wireless access card to
+enable other computers to connect to the internet via the ADSL modem. You could
+create a bridge to join the two interfaces together.
 </p>
 
 <pre caption="Bridge configuration in /etc/conf.d/net">
@@ -341,10 +340,10 @@
 <body>
 
 <p>
-You don't need to emerge anything for changing the MAC address of your
-interface if you change to a specific address. However, if you need to
-change to a random address or a random address of a given type then you
-need to emerge net-analyzer/macchanger.
+You don't need to emerge anything for changing the MAC address of your 
interface
+if you change to a specific address. However, if you need to change to a random
+address or a random address of a given type then you need to emerge
+net-analyzer/macchanger.
 </p>
 
 <pre caption="MAC Address change example">
@@ -374,8 +373,8 @@
 <body>
 
 <p>
-You don't need to emerge anything for tunnelling as the interface handler
-can do it for you.
+You don't need to emerge anything for tunnelling as the interface handler can 
do
+it for you.
 </p>
 
 <pre caption="Tunnelling configuration in /etc/conf.d/net">
@@ -400,10 +399,10 @@
 </p>
 
 <p>
-Virtual LAN is a group of network devices that behave as if they were
-connected to a single network segment - even though they may not be.
-VLAN members can only see members of the same VLAN even though they may
-share the same physical network.
+Virtual LAN is a group of network devices that behave as if they were connected
+to a single network segment - even though they may not be. VLAN members can 
only
+see members of the same VLAN even though they may share the same physical
+network.
 </p>
 
 <pre caption="VLAN configuration in /etc/conf.d/net">



-- 
[email protected] mailing list

Reply via email to