1 |
jkt 05/12/21 13:01:38 |
2 |
|
3 |
Modified: xml/htdocs/doc/en/handbook hb-net-modules.xml |
4 |
Log: |
5 |
coding style fixes, *no content change* |
6 |
|
7 |
Revision Changes Path |
8 |
1.9 +39 -40 xml/htdocs/doc/en/handbook/hb-net-modules.xml |
9 |
|
10 |
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 |
11 |
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 |
12 |
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 |
13 |
|
14 |
Index: hb-net-modules.xml |
15 |
=================================================================== |
16 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-net-modules.xml,v |
17 |
retrieving revision 1.8 |
18 |
retrieving revision 1.9 |
19 |
diff -u -r1.8 -r1.9 |
20 |
--- hb-net-modules.xml 7 Sep 2005 19:00:28 -0000 1.8 |
21 |
+++ hb-net-modules.xml 21 Dec 2005 13:01:38 -0000 1.9 |
22 |
@@ -4,7 +4,7 @@ |
23 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
24 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
25 |
|
26 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-net-modules.xml,v 1.8 2005/09/07 19:00:28 jkt Exp $ --> |
27 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-net-modules.xml,v 1.9 2005/12/21 13:01:38 jkt Exp $ --> |
28 |
|
29 |
<sections> |
30 |
|
31 |
@@ -16,18 +16,17 @@ |
32 |
<body> |
33 |
|
34 |
<p> |
35 |
-We now support modular networking scripts, which means we can easily |
36 |
-add support for new interface types and configuration modules while keeping |
37 |
-compatibility with existing ones. |
38 |
+We now support modular networking scripts, which means we can easily add support |
39 |
+for new interface types and configuration modules while keeping compatibility |
40 |
+with existing ones. |
41 |
</p> |
42 |
|
43 |
<p> |
44 |
-Modules load by default if the package they need is installed. If |
45 |
-you specify a module here that doesn't have its package installed |
46 |
-then you get an error stating which package you need to install. |
47 |
-Ideally, you only use the modules setting when you have two or more |
48 |
-packages installed that supply the same service and you need to prefer |
49 |
-one over the other. |
50 |
+Modules load by default if the package they need is installed. If you specify a |
51 |
+module here that doesn't have its package installed then you get an error |
52 |
+stating which package you need to install. Ideally, you only use the modules |
53 |
+setting when you have two or more packages installed that supply the same |
54 |
+service and you need to prefer one over the other. |
55 |
</p> |
56 |
|
57 |
<pre caption="Module preference"> |
58 |
@@ -51,8 +50,8 @@ |
59 |
<body> |
60 |
|
61 |
<p> |
62 |
-We provide two interface handlers presently: ifconfig and iproute2. |
63 |
-You need one of these to do any kind of network configuration. |
64 |
+We provide two interface handlers presently: ifconfig and iproute2. You need one |
65 |
+of these to do any kind of network configuration. |
66 |
</p> |
67 |
|
68 |
<p> |
69 |
@@ -70,8 +69,8 @@ |
70 |
|
71 |
<p> |
72 |
As both ifconfig and iproute2 do very similar things we allow their basic |
73 |
-configuration to work with each other. For example both the below code |
74 |
-snippets work regardless of which module you are using. |
75 |
+configuration to work with each other. For example both the below code snippets |
76 |
+work regardless of which module you are using. |
77 |
</p> |
78 |
|
79 |
<pre caption="ifconfig and iproute2 examples"> |
80 |
@@ -158,8 +157,8 @@ |
81 |
</table> |
82 |
|
83 |
<p> |
84 |
-If you have more than one DHCP client installed, you need to specify which |
85 |
-one to use - otherwise we default to dhcpcd if available. |
86 |
+If you have more than one DHCP client installed, you need to specify which one |
87 |
+to use - otherwise we default to dhcpcd if available. |
88 |
</p> |
89 |
|
90 |
<p> |
91 |
@@ -189,8 +188,8 @@ |
92 |
</pre> |
93 |
|
94 |
<note> |
95 |
-dhcpcd, udhcpc and pump send the current hostname to the DHCP server by |
96 |
-default so you don't need to specify this anymore. |
97 |
+dhcpcd, udhcpc and pump send the current hostname to the DHCP server by default |
98 |
+so you don't need to specify this anymore. |
99 |
</note> |
100 |
|
101 |
</body> |
102 |
@@ -239,14 +238,14 @@ |
103 |
<body> |
104 |
|
105 |
<p> |
106 |
-APIPA tries to find a free address in the range 169.254.0.0-169.254.255.255 |
107 |
-by arping a random address in that range on the interface. If no reply is |
108 |
-found then we assign that address to the interface. |
109 |
+APIPA tries to find a free address in the range 169.254.0.0-169.254.255.255 by |
110 |
+arping a random address in that range on the interface. If no reply is found |
111 |
+then we assign that address to the interface. |
112 |
</p> |
113 |
|
114 |
<p> |
115 |
-This is only useful for LANs where there is no DHCP server and you don't |
116 |
-connect directly to the internet and all other computers use APIPA. |
117 |
+This is only useful for LANs where there is no DHCP server and you don't connect |
118 |
+directly to the internet and all other computers use APIPA. |
119 |
</p> |
120 |
|
121 |
<p> |
122 |
@@ -273,9 +272,9 @@ |
123 |
</p> |
124 |
|
125 |
<p> |
126 |
-Bonding is used to increase network bandwidth. If you have two network |
127 |
-cards going to the same network, you can bond them together so your |
128 |
-applications see just one interface but they really use both network cards. |
129 |
+Bonding is used to increase network bandwidth. If you have two network cards |
130 |
+going to the same network, you can bond them together so your applications see |
131 |
+just one interface but they really use both network cards. |
132 |
</p> |
133 |
|
134 |
<pre caption="bonding configuration in /etc/conf.d/net"> |
135 |
@@ -302,10 +301,10 @@ |
136 |
</p> |
137 |
|
138 |
<p> |
139 |
-Bridging is used to join networks together. For example, you may have a |
140 |
-server that connects to the internet via an ADSL modem and a wireless |
141 |
-access card to enable other computers to connect to the internet via the |
142 |
-ADSL modem. You could create a bridge to join the two interfaces together. |
143 |
+Bridging is used to join networks together. For example, you may have a server |
144 |
+that connects to the internet via an ADSL modem and a wireless access card to |
145 |
+enable other computers to connect to the internet via the ADSL modem. You could |
146 |
+create a bridge to join the two interfaces together. |
147 |
</p> |
148 |
|
149 |
<pre caption="Bridge configuration in /etc/conf.d/net"> |
150 |
@@ -341,10 +340,10 @@ |
151 |
<body> |
152 |
|
153 |
<p> |
154 |
-You don't need to emerge anything for changing the MAC address of your |
155 |
-interface if you change to a specific address. However, if you need to |
156 |
-change to a random address or a random address of a given type then you |
157 |
-need to emerge net-analyzer/macchanger. |
158 |
+You don't need to emerge anything for changing the MAC address of your interface |
159 |
+if you change to a specific address. However, if you need to change to a random |
160 |
+address or a random address of a given type then you need to emerge |
161 |
+net-analyzer/macchanger. |
162 |
</p> |
163 |
|
164 |
<pre caption="MAC Address change example"> |
165 |
@@ -374,8 +373,8 @@ |
166 |
<body> |
167 |
|
168 |
<p> |
169 |
-You don't need to emerge anything for tunnelling as the interface handler |
170 |
-can do it for you. |
171 |
+You don't need to emerge anything for tunnelling as the interface handler can do |
172 |
+it for you. |
173 |
</p> |
174 |
|
175 |
<pre caption="Tunnelling configuration in /etc/conf.d/net"> |
176 |
@@ -400,10 +399,10 @@ |
177 |
</p> |
178 |
|
179 |
<p> |
180 |
-Virtual LAN is a group of network devices that behave as if they were |
181 |
-connected to a single network segment - even though they may not be. |
182 |
-VLAN members can only see members of the same VLAN even though they may |
183 |
-share the same physical network. |
184 |
+Virtual LAN is a group of network devices that behave as if they were connected |
185 |
+to a single network segment - even though they may not be. VLAN members can only |
186 |
+see members of the same VLAN even though they may share the same physical |
187 |
+network. |
188 |
</p> |
189 |
|
190 |
<pre caption="VLAN configuration in /etc/conf.d/net"> |
191 |
|
192 |
|
193 |
|
194 |
-- |
195 |
gentoo-doc-cvs@g.o mailing list |