Gentoo Archives: gentoo-doc-cvs

From: Jan Kundrat <jkt@×××××××××××.org>
To: gentoo-doc-cvs@l.g.o
Subject: [gentoo-doc-cvs] cvs commit: hb-net-advanced.xml
Date: Wed, 21 Dec 2005 12:20:53
Message-Id: 200512211220.jBLCKiqw025454@robin.gentoo.org
1 jkt 05/12/21 12:20:43
2
3 Modified: xml/htdocs/doc/en/handbook hb-net-advanced.xml
4 Log:
5 coding style fixes, *no content change*
6
7 Revision Changes Path
8 1.10 +28 -31 xml/htdocs/doc/en/handbook/hb-net-advanced.xml
9
10 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
11 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
12 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
13
14 Index: hb-net-advanced.xml
15 ===================================================================
16 RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-net-advanced.xml,v
17 retrieving revision 1.9
18 retrieving revision 1.10
19 diff -u -r1.9 -r1.10
20 --- hb-net-advanced.xml 21 Dec 2005 11:49:14 -0000 1.9
21 +++ hb-net-advanced.xml 21 Dec 2005 12:20:43 -0000 1.10
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-advanced.xml,v 1.9 2005/12/21 11:49:14 jkt Exp $ -->
27 +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-net-advanced.xml,v 1.10 2005/12/21 12:20:43 jkt Exp $ -->
28
29 <sections>
30
31 @@ -16,10 +16,10 @@
32 <body>
33
34 <p>
35 -The config_eth0 variable is the heart of an interface's configuration.
36 -It's a high level instruction list for configuring the interface (eth0 in
37 -this case). Each command in the instruction list is performed sequentially.
38 -The interface is deemed OK if at least one command works.
39 +The config_eth0 variable is the heart of an interface's configuration. It's a
40 +high level instruction list for configuring the interface (eth0 in this case).
41 +Each command in the instruction list is performed sequentially. The interface is
42 +deemed OK if at least one command works.
43 </p>
44
45 <p>
46 @@ -51,9 +51,9 @@
47 dhcp, adsl or apipa (or a custom command from a 3rd party module)
48 </ti>
49 <ti>
50 - Run the module which provides the command. For example "dhcp" will
51 - run a module that provides dhcp which can be one of either dhcpcd,
52 - udhcpc, dhclient or pump.
53 + Run the module which provides the command. For example "dhcp" will run a
54 + module that provides dhcp which can be one of either dhcpcd, udhcpc,
55 + dhclient or pump.
56 </ti>
57 </tr>
58 </table>
59 @@ -98,9 +98,9 @@
60 <note>
61 When using the ifconfig module and adding more than one address, interface
62 aliases are created for each extra address. So with the above two examples you
63 -will get interfaces eth0, eth0:1 and eth0:2.
64 -You cannot do anything special with these interfaces as the kernel and other
65 -programs will just treat eth0:1 and eth0:2 as eth0.
66 +will get interfaces eth0, eth0:1 and eth0:2. You cannot do anything special with
67 +these interfaces as the kernel and other programs will just treat eth0:1 and
68 +eth0:2 as eth0.
69 </note>
70
71 <impo>
72 @@ -109,8 +109,8 @@
73 </impo>
74
75 <note>
76 -<uri link="?part=4&amp;chap=3#apipa">APIPA</uri> and
77 -<uri link="?part=4&amp;chap=3#dhcp">DHCP</uri> are discussed later.
78 +<uri link="?part=4&amp;chap=3#apipa">APIPA</uri> and <uri
79 +link="?part=4&amp;chap=3#dhcp">DHCP</uri> are discussed later.
80 </note>
81
82 </body>
83 @@ -137,35 +137,33 @@
84 <tr>
85 <ti>no</ti>
86 <ti>
87 - This basically means that at least one net.* service besides net.lo
88 - must be up. This can be used by notebook users that have a wifi and
89 - a static nic, and only wants one up at any given time to have the
90 - net service seen as up.
91 + This basically means that at least one net.* service besides net.lo must be
92 + up. This can be used by notebook users that have a wifi and a static nic,
93 + and only wants one up at any given time to have the net service seen as up.
94 </ti>
95 </tr>
96 <tr>
97 <ti>lo</ti>
98 <ti>
99 - This is the same as the 'no' option, but net.lo is also counted.
100 - This should be useful to people that do not care about any specific
101 - interface being up at boot.
102 + This is the same as the 'no' option, but net.lo is also counted. This should
103 + be useful to people that do not care about any specific interface being up
104 + at boot.
105 </ti>
106 </tr>
107 <tr>
108 <ti>yes</ti>
109 <ti>
110 - For this ALL network interfaces MUST be up for the 'net' service to
111 - be considered up.
112 + For this ALL network interfaces MUST be up for the 'net' service to be
113 + considered up.
114 </ti>
115 </tr>
116 </table>
117
118 <p>
119 -But what about net.br0 depending on net.eth0 and net.eth1?
120 -net.eth1 may be a wireless or ppp device that needs configuration before it
121 -can be added to the bridge.
122 -This cannot be done in <path>/etc/init.d/net.br0</path> as that's a symbolic
123 -link to net.lo
124 +But what about net.br0 depending on net.eth0 and net.eth1? net.eth1 may be a
125 +wireless or ppp device that needs configuration before it can be added to the
126 +bridge. This cannot be done in <path>/etc/init.d/net.br0</path> as that's a
127 +symbolic link to net.lo
128 </p>
129
130 <p>
131 @@ -180,10 +178,9 @@
132 </pre>
133
134 <p>
135 -For a more detailed discussion about dependency, consult the section
136 -<uri
137 -link="?part=2&amp;chap=4#doc_chap4">Writing
138 -Init Scripts</uri> in the Gentoo Handbook.
139 +For a more detailed discussion about dependency, consult the section <uri
140 +link="?part=2&amp;chap=4#doc_chap4">Writing Init Scripts</uri> in the Gentoo
141 +Handbook.
142 </p>
143
144 </body>
145
146
147
148 --
149 gentoo-doc-cvs@g.o mailing list