* [gentoo-doc-cvs] cvs commit: hb-net-advanced.xml
@ 2005-12-21 11:49 Jan Kundrat
0 siblings, 0 replies; 4+ messages in thread
From: Jan Kundrat @ 2005-12-21 11:49 UTC (permalink / raw
To: gentoo-doc-cvs
jkt 05/12/21 11:49:14
Modified: xml/htdocs/doc/en/handbook hb-net-advanced.xml
Log:
missing period, *no content change*
Revision Changes Path
1.9 +2 -2 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.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-advanced.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-advanced.xml.diff?r1=1.8&r2=1.9&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.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- hb-net-advanced.xml 14 Aug 2005 05:42:05 -0000 1.8
+++ hb-net-advanced.xml 21 Dec 2005 11:49:14 -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-advanced.xml,v 1.8 2005/08/14 05:42:05 fox2mike Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-net-advanced.xml,v 1.9 2005/12/21 11:49:14 jkt Exp $ -->
<sections>
@@ -169,7 +169,7 @@
</p>
<p>
-The answer is making your own depend() function in <path>/etc/conf.d/net</path>
+The answer is making your own depend() function in <path>/etc/conf.d/net</path>.
</p>
<pre caption="net.br0 dependency in /etc/conf.d/net">
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 4+ messages in thread
* [gentoo-doc-cvs] cvs commit: hb-net-advanced.xml
@ 2005-12-22 19:55 Jan Kundrat
0 siblings, 0 replies; 4+ messages in thread
From: Jan Kundrat @ 2005-12-22 19:55 UTC (permalink / raw
To: gentoo-doc-cvs
jkt 05/12/22 19:55:49
Modified: xml/htdocs/doc/en/handbook hb-net-advanced.xml
hb-net-functions.xml hb-net-management.xml
hb-net-modules.xml hb-net-start.xml
hb-net-wireless.xml
Log:
#116267, hb-net-*: adding <c>s, <path>s, proper capitalization,...
Revision Changes Path
1.11 +49 -44 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.11&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.11&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.10&r2=1.11&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.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- hb-net-advanced.xml 21 Dec 2005 12:20:43 -0000 1.10
+++ hb-net-advanced.xml 22 Dec 2005 19:55:49 -0000 1.11
@@ -4,22 +4,22 @@
<!-- 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.10 2005/12/21 12:20:43 jkt Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-net-advanced.xml,v 1.11 2005/12/22 19:55:49 jkt Exp $ -->
<sections>
-<version>1.3</version>
-<date>2005-08-14</date>
+<version>1.4</version>
+<date>2005-12-22</date>
<section>
<title>Advanced Configuration</title>
<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 <c>config_eth0</c> variable is the heart of an interface configuration. It's
+a high level instruction list for configuring the interface (<c>eth0</c> 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>
@@ -32,11 +32,11 @@
<th>Description</th>
</tr>
<tr>
- <ti>null</ti>
+ <ti><c>null</c></ti>
<ti>Do nothing</ti>
</tr>
<tr>
- <ti>noop</ti>
+ <ti><c>noop</c></ti>
<ti>
If the interface is up and there is an address then abort configuration
successfully
@@ -48,12 +48,13 @@
</tr>
<tr>
<ti>
- dhcp, adsl or apipa (or a custom command from a 3rd party module)
+ <c>dhcp</c>, <c>adsl</c> or <c>apipa</c> (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 <c>dhcp</c> will run
+ a module that provides DHCP which can be one of either <c>dhcpcd</c>,
+ <c>udhcpc</c>, <c>dhclient</c> or <c>pump</c>.
</ti>
</tr>
</table>
@@ -96,16 +97,17 @@
</pre>
<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.
+When using the <c>ifconfig</c> 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 <c>eth0</c>, <c>eth0:1</c> and <c>eth0:2</c>.
+You cannot do anything special with these interfaces as the kernel and other
+programs will just treat <c>eth0:1</c> and <c>eth0:2</c> as <c>eth0</c>.
</note>
<impo>
-The fallback order is important! If we did not specify the "null" option then
-the "apipa" command would only be run if the "noop" command failed.
+The fallback order is important! If we did not specify the <c>null</c> option
+then the <c>apipa</c> command would only be run if the <c>noop</c> command
+failed.
</impo>
<note>
@@ -121,8 +123,8 @@
<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.
+interface or just net. <c>net</c> 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>
@@ -131,43 +133,46 @@
<th>Description</th>
</tr>
<tr>
- <ti>none</ti>
- <ti>The net service is always considered up</ti>
+ <ti><c>none</c></ti>
+ <ti>The <path>net</path> service is always considered up</ti>
</tr>
<tr>
- <ti>no</ti>
+ <ti><c>no</c></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 <path>net.*</path> service besides
+ <path>net.lo</path> 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><c>lo</c></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 <c>no</c> option, but <path>net.lo</path> 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><c>yes</c></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 <path>net</path> 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 <path>net.br0</path> depending on <path>net.eth0</path> and
+<path>net.eth1</path>? <path>net.eth1</path> 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
+<path>net.lo</path>.
</p>
<p>
-The answer is making your own depend() function in <path>/etc/conf.d/net</path>.
+The answer is making your own <c>depend()</c> function in
+<path>/etc/conf.d/net</path>.
</p>
<pre caption="net.br0 dependency in /etc/conf.d/net">
@@ -195,7 +200,7 @@
<c>variable_${interface|mac|essid|apmac}</c>. For example, the variable
<c>dhcpcd_eth0</c> holds the value for dhcpcd options for eth0 and
<c>dhcpcd_essid</c> holds the value for dhcpcd options when any interface
-connects to the essid "essid".
+connects to the ESSID "essid".
</p>
<p>
@@ -211,13 +216,13 @@
The downside of all this is that Gentoo uses bash variables for networking -
and bash cannot use anything outside of English alpha-numerics. To get around
this limitation we change every character that is not an English alpha-numeric
-into a _ character.
+into a <c>_</c> character.
</p>
<p>
Another downside of bash is the content of variables - some characters need to
-be escaped. This can be achived by placing the \ character in front of the
-character that needs to be escaped. The following list of characters needs
+be escaped. This can be achived by placing the <c>\</c> character in front of
+the character that needs to be escaped. The following list of characters needs
to be escaped in this way: <c>"</c>, <c>'</c> and <c>\</c>.
</p>
1.7 +22 -22 xml/htdocs/doc/en/handbook/hb-net-functions.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-net-functions.xml?rev=1.7&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-net-functions.xml?rev=1.7&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-net-functions.xml.diff?r1=1.6&r2=1.7&cvsroot=gentoo
Index: hb-net-functions.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-net-functions.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- hb-net-functions.xml 21 Dec 2005 13:27:46 -0000 1.6
+++ hb-net-functions.xml 22 Dec 2005 19:55:49 -0000 1.7
@@ -4,34 +4,34 @@
<!-- 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-functions.xml,v 1.6 2005/12/21 13:27:46 jkt Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-net-functions.xml,v 1.7 2005/12/22 19:55:49 jkt Exp $ -->
<sections>
-<version>1.1</version>
-<date>2005-06-14</date>
+<version>1.2</version>
+<date>2005-12-22</date>
<section>
<title>Standard function hooks</title>
<body>
<p>
-Four functions can be defined which will be called surrounding the start/stop
-operations. The functions are called with the interface name first so that one
-function can control multiple adapters.
+Four functions can be defined which will be called surrounding the
+<c>start</c>/<c>stop</c> operations. The functions are called with the
+interface name first so that one function can control multiple adapters.
</p>
<p>
-The return values for the preup and predown functions should be 0 (success) to
-indicate that configuration or deconfiguration of the interface can continue.
-If preup returns a non-zero value, then interface configuration will be aborted.
-If predown returns a non-zero value, then the interface will not be allowed to
-continue deconfiguration.
+The return values for the <c>preup()</c> and <c>predown()</c> functions should
+be 0 (success) to indicate that configuration or deconfiguration of the
+interface can continue. If <c>preup()</c> returns a non-zero value, then
+interface configuration will be aborted. If <c>predown()</c> returns a non-zero
+value, then the interface will not be allowed to continue deconfiguration.
</p>
<p>
-The return values for the postup and postdown functions are ignored since
-there's nothing to do if they indicate failure.
+The return values for the <c>postup()</c> and <c>postdown()</c> functions are
+ignored since there's nothing to do if they indicate failure.
</p>
<p>
@@ -97,7 +97,7 @@
<note>
This will not work with WPA Supplicant - but the <c>${ESSID}</c> and
-<c>${ESSIDVAR}</c> variables are available in the postup() function.
+<c>${ESSIDVAR}</c> variables are available in the <c>postup()</c> function.
</note>
<p>
@@ -107,15 +107,15 @@
</p>
<p>
-The return values for the preassociate function should be 0 (success) to
-indicate that configuration or deconfiguration of the interface can continue.
-If preassociate returns a non-zero value, then interface configuration will be
-aborted.
+The return values for the <c>preassociate()</c> function should be 0 (success)
+to indicate that configuration or deconfiguration of the interface can continue.
+If <c>preassociate()</c> returns a non-zero value, then interface configuration
+will be aborted.
</p>
<p>
-The return value for the postassociate function is ignored since there's nothing
-to do if it indicates failure.
+The return value for the <c>postassociate()</c> function is ignored since
+there's nothing to do if it indicates failure.
</p>
<p>
@@ -157,8 +157,8 @@
</pre>
<note>
-<c>${ESSID}</c> and <c>${ESSIDVAR}</c> are unavailable in predown() and
-postdown() functions.
+<c>${ESSID}</c> and <c>${ESSIDVAR}</c> are unavailable in <c>predown()</c> and
+<c>postdown()</c> functions.
</note>
</body>
1.6 +5 -5 xml/htdocs/doc/en/handbook/hb-net-management.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-net-management.xml?rev=1.6&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-net-management.xml?rev=1.6&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-net-management.xml.diff?r1=1.5&r2=1.6&cvsroot=gentoo
Index: hb-net-management.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-net-management.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- hb-net-management.xml 21 Dec 2005 13:34:15 -0000 1.5
+++ hb-net-management.xml 22 Dec 2005 19:55:49 -0000 1.6
@@ -4,12 +4,12 @@
<!-- 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-management.xml,v 1.5 2005/12/21 13:34:15 jkt Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-net-management.xml,v 1.6 2005/12/22 19:55:49 jkt Exp $ -->
<sections>
-<version>1.1</version>
-<date>2005-06-14</date>
+<version>1.2</version>
+<date>2005-12-22</date>
<section>
<title>Network Management</title>
@@ -27,8 +27,8 @@
</p>
<note>
-This document only talks about ifplugd, but there are alternatives you can
-look into like quickswitch.
+This document only talks about <c>ifplugd</c>, but there are alternatives you
+can look into like <c>quickswitch</c>.
</note>
</body>
1.10 +48 -49 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.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-modules.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-modules.xml.diff?r1=1.9&r2=1.10&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.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- hb-net-modules.xml 21 Dec 2005 13:01:38 -0000 1.9
+++ hb-net-modules.xml 22 Dec 2005 19:55:49 -0000 1.10
@@ -4,12 +4,12 @@
<!-- 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.9 2005/12/21 13:01:38 jkt Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-net-modules.xml,v 1.10 2005/12/22 19:55:49 jkt Exp $ -->
<sections>
-<version>1.4</version>
-<date>2005-09-07</date>
+<version>1.5</version>
+<date>2005-12-22</date>
<section>
<title>Network Modules</title>
@@ -50,14 +50,14 @@
<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: <c>ifconfig</c> and
+<c>iproute2</c>. You need one of these to do any kind of network configuration.
</p>
<p>
-ifconfig is the current Gentoo default and it's included in the system profile.
-iproute2 is a more powerful and flexible package, but it's not included by
-default.
+<c>ifconfig</c> is the current Gentoo default and it's included in the system
+profile. <c>iproute2</c> is a more powerful and flexible package, but it's not
+included by default.
</p>
<pre caption="To install iproute2">
@@ -68,9 +68,9 @@
</pre>
<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.
+As both <c>ifconfig</c> and <c>iproute2</c> do very similar things we allow
+their basic configuration to work with each other. For example both the below
+code snippet work regardless of which module you are using.
</p>
<pre caption="ifconfig and iproute2 examples">
@@ -93,13 +93,13 @@
Gateway, etc) from a DHCP server. This means that if there is a DHCP server
running on the network, you just have to tell each client to use DHCP and it
sets up the network all by itself. Of course, you will have to configure for
-other things like wireless, ppp or other things if required before you can use
+other things like wireless, PPP or other things if required before you can use
DHCP.
</p>
<p>
-DHCP can be provided by dhclient, dhcpcd, pump or udhcpc. Each DHCP module has
-its pros and cons - here's a quick run down.
+DHCP can be provided by <c>dhclient</c>, <c>dhcpcd</c>, <c>pump</c> or
+<c>udhcpc</c>. Each DHCP module has its pros and cons - here's a quick run down.
</p>
<table>
@@ -110,8 +110,8 @@
<th>Cons</th>
</tr>
<tr>
- <ti>dhclient</ti>
- <ti>net-misc/dhcp</ti>
+ <ti><c>dhclient</c></ti>
+ <ti><c>net-misc/dhcp</c></ti>
<ti>
Made by ISC, the same people who make the BIND DNS software. Very
configurable
@@ -122,8 +122,8 @@
</ti>
</tr>
<tr>
- <ti>dhcpcd</ti>
- <ti>net-misc/dhcpcd</ti>
+ <ti><c>dhcpcd</c></ti>
+ <ti><c>net-misc/dhcpcd</c></ti>
<ti>
Long time Gentoo default, no reliance on outside tools
</ti>
@@ -133,8 +133,8 @@
</ti>
</tr>
<tr>
- <ti>pump</ti>
- <ti>net-misc/pump</ti>
+ <ti><c>pump</c></ti>
+ <ti><c>net-misc/pump</c></ti>
<ti>
Lightweight, no reliance on outside tools
</ti>
@@ -144,10 +144,10 @@
</ti>
</tr>
<tr>
- <ti>udhcpc</ti>
- <ti>net-misc/udhcp</ti>
+ <ti><c>udhcpc</c></ti>
+ <ti><c>net-misc/udhcp</c></ti>
<ti>
- Lightweight - smallest dhcp client around, made for embedded systems
+ Lightweight - smallest DHCP client around, made for embedded systems
</ti>
<ti>
Unproven - no distro uses it by default, cannot define a timeout beyond 3
@@ -158,24 +158,25 @@
<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.
+to use - otherwise we default to <c>dhcpcd</c> if available.
</p>
<p>
-To send specific options to the dhcp module, use module_eth0="..."
-<e>(change module to the DHCP module you're using - ie dhcpcd_eth0)</e>
+To send specific options to the DHCP module, use <c>module_eth0="..."</c>
+<e>(change module to the DHCP module you're using - ie <c>dhcpcd_eth0</c>)</e>
</p>
<p>
We try and make DHCP relatively agnostic - as such we support the following
-commands using the dhcp_eth0 variable. The default is not to set any of them
+commands using the <c>dhcp_eth0</c> variable. The default is not to set any of
+them:
</p>
<ul>
- <li>release - releases the IP address for re-use</li>
- <li>nodns - don't overwrite /etc/resolv.conf</li>
- <li>nontp - don't overwrite /etc/ntp.conf</li>
- <li>nonis - don't overwrite /etc/yp.conf</li>
+ <li><c>release</c> - releases the IP address for re-use</li>
+ <li><c>nodns</c> - don't overwrite <path>/etc/resolv.conf</path></li>
+ <li><c>nontp</c> - don't overwrite <path>/etc/ntp.conf</path></li>
+ <li><c>nonis</c> - don't overwrite <path>/etc/yp.conf</path></li>
</ul>
<pre caption="Sample DHCP configuration in /etc/conf.d/net">
@@ -188,8 +189,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.
+<c>dhcpcd</c>, <c>udhcpc</c> and <c>pump</c> send the current hostname to the
+DHCP server by default so you don't need to specify this anymore.
</note>
</body>
@@ -207,13 +208,13 @@
</pre>
<warn>
-baselayout-1.11.x supports PPPOE only. Hopefully future versions will support
-PPPOA.
+<c>baselayout-1.11.x</c> supports PPPoE only. Hopefully future versions will
+support PPPoA.
</warn>
<p>
-Now we need to instruct configure eth0 to be an ADSL interface and enter our
-username.
+Now we need to instruct configure <c>eth0</c> to be an ADSL interface and enter
+our username.
</p>
<pre caption="Configure eth0 for ADSL">
@@ -223,7 +224,7 @@
<p>
Finally you need to define your username and password in
-<path>/etc/ppp/pap-secrets</path>
+<path>/etc/ppp/pap-secrets</path>.
</p>
<pre caption="sample /etc/ppp/pap-secrets">
@@ -249,7 +250,7 @@
</p>
<p>
-For APIPA support, emerge net-misc/iputils or net-analyzer/arping
+For APIPA support, emerge <c>net-misc/iputils</c> or <c>net-analyzer/arping</c>.
</p>
<pre caption="APIPA configuration in /etc/conf.d/net">
@@ -268,7 +269,7 @@
<body>
<p>
-For link bonding/trunking emerge net-misc/ifenslave
+For link bonding/trunking emerge <c>net-misc/ifenslave</c>.
</p>
<p>
@@ -297,7 +298,7 @@
<body>
<p>
-For bridging support emerge net-misc/bridge-utils
+For bridging support emerge <c>net-misc/bridge-utils</c>.
</p>
<p>
@@ -328,9 +329,8 @@
</pre>
<impo>
-For using some bridge setups, you may need to consult the
-<uri link="?part=4&chap=2#variable_name">variable name</uri>
-documentation.
+For using some bridge setups, you may need to consult the <uri
+link="?part=4&chap=2#variable_name">variable name</uri> documentation.
</impo>
</body>
@@ -343,7 +343,7 @@
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.
+<c>net-analyzer/macchanger</c>.
</p>
<pre caption="MAC Address change example">
@@ -395,7 +395,7 @@
<body>
<p>
-For VLAN support, emerge net-misc/vconfig
+For VLAN support, emerge <c>net-misc/vconfig</c>.
</p>
<p>
@@ -421,9 +421,8 @@
</pre>
<impo>
-For using some VLAN setups, you may need to consult the
-<uri link="?part=4&chap=2#variable_name">variable name</uri>
-documentation.
+For using some VLAN setups, you may need to consult the <uri
+link="?part=4&chap=2#variable_name">variable name</uri> documentation.
</impo>
</body>
1.5 +8 -8 xml/htdocs/doc/en/handbook/hb-net-start.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-net-start.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-start.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-start.xml.diff?r1=1.4&r2=1.5&cvsroot=gentoo
Index: hb-net-start.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-net-start.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- hb-net-start.xml 14 Jul 2005 10:22:46 -0000 1.4
+++ hb-net-start.xml 22 Dec 2005 19:55:49 -0000 1.5
@@ -4,12 +4,12 @@
<!-- 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-start.xml,v 1.4 2005/07/14 10:22:46 fox2mike Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-net-start.xml,v 1.5 2005/12/22 19:55:49 jkt Exp $ -->
<sections>
-<version>1.2</version>
-<date>2005-07-14</date>
+<version>1.3</version>
+<date>2005-12-22</date>
<section>
<title>Getting started</title>
@@ -18,18 +18,18 @@
<note>
This document assumes that you have correctly configured your kernel, its
modules for your hardware and you know the interface name of your hardware.
-We also assume that you are configuring eth0, but it could also be
-eth1, wlan0, etc.
+We also assume that you are configuring <c>eth0</c>, but it could also be
+<c>eth1</c>, <c>wlan0</c>, etc.
</note>
<note>
-This document requires you are running baselayout-1.11.11 or better.
+This document requires you are running <c>baselayout-1.11.11</c> or better.
</note>
<p>
To get started configuring your network card, you need to tell the Gentoo RC
-system about it. This is done by creating a symbolic link from <c>net.lo</c>
-to <c>net.eth0</c> in <path>/etc/init.d</path>
+system about it. This is done by creating a symbolic link from
+<path>net.lo</path> to <path>net.eth0</path> in <path>/etc/init.d</path>.
</p>
<pre caption="Symlinking net.eth0 to net.lo">
1.7 +65 -66 xml/htdocs/doc/en/handbook/hb-net-wireless.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-net-wireless.xml?rev=1.7&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-net-wireless.xml?rev=1.7&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/hb-net-wireless.xml.diff?r1=1.6&r2=1.7&cvsroot=gentoo
Index: hb-net-wireless.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-net-wireless.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- hb-net-wireless.xml 21 Dec 2005 13:16:02 -0000 1.6
+++ hb-net-wireless.xml 22 Dec 2005 19:55:49 -0000 1.7
@@ -4,42 +4,43 @@
<!-- 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-wireless.xml,v 1.6 2005/12/21 13:16:02 jkt Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-net-wireless.xml,v 1.7 2005/12/22 19:55:49 jkt Exp $ -->
<sections>
-<version>1.2</version>
-<date>2005-08-02</date>
+<version>1.3</version>
+<date>2005-12-22</date>
<section>
<title>Introduction</title>
<body>
<p>
-Currently we support wireless setup either by wireless-tools or wpa_supplicant.
-The important thing to remember is that you configure for wireless networks on a
-global basis and not an interface basis.
+Currently we support wireless setup either by <c>wireless-tools</c> or
+<c>wpa_supplicant</c>. The important thing to remember is that you configure for
+wireless networks on a global basis and not an interface basis.
</p>
<p>
-wpa_suppliant is the best choice, but it does not support all drivers. For a
-list of supported drivers, <uri
+<c>wpa_suppliant</c> is the best choice, but it does not support all drivers.
+For a list of supported drivers, <uri
link="http://hostap.epitest.fi/wpa_supplicant">read the wpa_supplicant
-site</uri>. Also, wpa_supplicant can currently only connect to SSID's that
-you have configured for.
+site</uri>. Also, <c>wpa_supplicant</c> can currently only connect to SSID's
+that you have configured for.
</p>
<p>
-wireless-tools supports nearly all cards and drivers, but it cannot connect to
-WPA only Access Points.
+<c>wireless-tools</c> supports nearly all cards and drivers, but it cannot
+connect to WPA only Access Points.
</p>
<warn>
-The linux-wlan-ng driver is not supported by baselayout at this time. This is
-because linux-wlan-ng have their own setup and configuration which is completely
-different to everyone else's. The linux-wlan-ng devs are rumoured to be changing
-their setup over to wireless-tools - when this happens you may use linux-wlan-ng
-with baselayout.
+The <c>linux-wlan-ng</c> driver is not supported by <c>baselayout</c> at this
+time. This is because <c>linux-wlan-ng</c> have their own setup and
+configuration which is completely different to everyone else's. The
+<c>linux-wlan-ng</c> devs are rumoured to be changing their setup over to
+<c>wireless-tools</c> - when this happens you may use <c>linux-wlan-ng</c>
+with <c>baselayout</c>.
</warn>
</body>
@@ -59,14 +60,14 @@
</pre>
<impo>
-You have to have CONFIG_PACKET enabled in your kernel for wpa_supplicant to
-work.
+You have to have <c>CONFIG_PACKET</c> enabled in your kernel for
+<c>wpa_supplicant</c> to work.
</impo>
<p>
Now we have to configure <path>/etc/conf.d/net</path> to so that we prefer
-wpa_supplicant over wireless-tools (if both are installed, wireless-tools is the
-default).
+<c>wpa_supplicant</c> over <c>wireless-tools</c> (if both are installed,
+<c>wireless-tools</c> is the default).
</p>
<pre caption="configure /etc/conf.d/net for wpa_supplicant">
@@ -79,18 +80,18 @@
</pre>
<note>
-If you're using the host-ap driver you will need to put the card in Managed mode
-before it can be used with wpa_supplicant correctly. You can use
+If you're using the host-ap driver you will need to put the card in <e>Managed
+mode</e> before it can be used with <c>wpa_supplicant</c> correctly. You can use
<e>iwconfig_eth0="mode managed"</e> to achieve this in
<path>/etc/conf.d/net</path>.
</note>
<p>
-That was simple wasn't it? However, we still have to configure wpa_supplicant
-itself which is a bit more tricky depending on how secure the Access Points are
-that you are trying to connect to. The below example is taken and simplified
-from <path>/etc/wpa_supplicant.conf.example</path> which ships with
-wpa_supplicant.
+That was simple wasn't it? However, we still have to configure
+<c>wpa_supplicant</c> itself which is a bit more tricky depending on how secure
+the Access Points are that you are trying to connect to. The below example is
+taken and simplified from <path>/etc/wpa_supplicant.conf.example</path> which
+ships with <c>wpa_supplicant</c>.
</p>
<pre caption="an example /etc/wpa_supplicant.conf">
@@ -258,37 +259,37 @@
<th>Description</th>
</tr>
<tr>
- <ti>any</ti>
+ <ti><c>any</c></ti>
<ti>Default behaviour</ti>
</tr>
<tr>
- <ti>preferredonly</ti>
+ <ti><c>preferredonly</c></ti>
<ti>We will only connect to visible APs in the preferred list</ti>
</tr>
<tr>
- <ti>forcepreferred</ti>
+ <ti><c>forcepreferred</c></ti>
<ti>
We will forceably connect to APs in the preferred order if they are not
found in a scan
</ti>
</tr>
<tr>
- <ti>forcepreferredonly</ti>
+ <ti><c>forcepreferredonly</c></ti>
<ti>
Do not scan for APs - instead just try to connect to each one in order
</ti>
</tr>
<tr>
- <ti>forceany</ti>
+ <ti><c>forceany</c></ti>
<ti>Same as forcepreferred + connect to any other available AP</ti>
</tr>
</table>
<p>
-Finally we have some blacklist_aps and unique_ap selection. blacklist_aps works
-in a similar way to preferred_aps. unique_ap is a yes or no value that says if a
-second wireless interface can connect to the same Access Point as the first
-interface.
+Finally we have some <c>blacklist_aps</c> and <c>unique_ap</c> selection.
+<c>blacklist_aps</c> works in a similar way to <c>preferred_aps</c>.
+<c>unique_ap</c> is a yes or no value that says if a second wireless interface
+can connect to the same Access Point as the first interface.
</p>
<pre caption="blacklist_aps and unique_ap example">
@@ -369,64 +370,63 @@
<th>Description</th>
</tr>
<tr>
- <ti>iwconfig_eth0</ti>
+ <ti><c>iwconfig_eth0</c></ti>
<ti/>
- <ti>See the iwconfig man page for details on what to send iwconfig</ti>
+ <ti>See the iwconfig man page for details on what to send <c>iwconfig</c></ti>
</tr>
<tr>
- <ti>iwpriv_eth0</ti>
+ <ti><c>iwpriv_eth0</c></ti>
<ti/>
- <ti>See the iwpriv man page for details on what to send iwpriv</ti>
+ <ti>See the iwpriv man page for details on what to send <c>iwpriv</c></ti>
</tr>
<tr>
- <ti>sleep_scan_eth0</ti>
- <ti>0</ti>
+ <ti><c>sleep_scan_eth0</c></ti>
+ <ti><c>0</c></ti>
<ti>
The number of seconds to sleep before attempting to scan. This is needed
when the driver/firmware needs more time to active before it can be used.
</ti>
</tr>
<tr>
- <ti>sleep_associate_eth0</ti>
- <ti>5</ti>
+ <ti><c>sleep_associate_eth0</c></ti>
+ <ti><c>5</c></ti>
<ti>
The number of seconds to wait for the interface to associate with the
Access Point before moving onto the next one
</ti>
</tr>
<tr>
- <ti>associate_test_eth0</ti>
- <ti>MAC</ti>
+ <ti><c>associate_test_eth0</c></ti>
+ <ti><c>MAC</c></ti>
<ti>
- Some drivers do not reset the MAC address associated with to an
- invalid one when they loose or attempt to associate.
- Some drivers do not reset the quality level when they loose
- or attempt assocciation.
- Valid settings are MAC, quality and all.
+ Some drivers do not reset the MAC address associated with to an invalid one
+ when they loose or attempt to associate. Some drivers do not reset the
+ quality level when they loose or attempt assocciation. Valid settings are
+ <c>MAC</c>, <c>quality</c> and <c>all</c>.
</ti>
</tr>
<tr>
- <ti>scan_mode_eth0</ti>
+ <ti><c>scan_mode_eth0</c></ti>
<ti/>
<ti>
Some drivers have to scan in ad-hoc mode, so if scanning fails
- try setting ad-hoc here
+ try setting <c>ad-hoc</c> here
</ti>
</tr>
<tr>
- <ti>iwpriv_scan_pre_eth0</ti>
+ <ti><c>iwpriv_scan_pre_eth0</c></ti>
<ti/>
<ti>
- Sends some iwpriv commands to the interface before scanning.
- See the iwpriv man page for more details
+ Sends some <c>iwpriv</c> commands to the interface before scanning.
+ See the iwpriv man page for more details.
</ti>
</tr>
<tr>
- <ti>iwpriv_scan_post_eth0</ti>
+ <ti><c>iwpriv_scan_post_eth0</c></ti>
<ti/>
<ti>
- Sends some iwpriv commands to the interface after scanning.
- See the iwpriv man page for more details
+ Sends some <c>iwpriv</c> commands to the interface after scanning.
+ See the iwpriv man page for more details.
</ti>
</tr>
</table>
@@ -439,9 +439,9 @@
<body>
<p>
-Someones when you connect to ESSID1 you need a static IP and when you connect to
-ESSID2 you need DHCP. Infact most module variables we can change per ESSID.
-Here's how we do this.
+Someones when you connect to <e>ESSID1</e> you need a static IP and when you
+connect to <e>ESSID2</e> you need DHCP. Infact most module variables we can
+change per ESSID. Here's how we do this.
</p>
<note>
@@ -449,9 +449,8 @@
</note>
<impo>
-You <e>will</e> need to consult the
-<uri link="?part=4&chap=2#variable_name">variable name</uri>
-documentation.
+You <e>will</e> need to consult the <uri
+link="?part=4&chap=2#variable_name">variable name</uri> documentation.
</impo>
<pre caption="override network settings per ESSID">
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 4+ messages in thread* [gentoo-doc-cvs] cvs commit: hb-net-advanced.xml
@ 2005-12-21 12:20 Jan Kundrat
0 siblings, 0 replies; 4+ messages in thread
From: Jan Kundrat @ 2005-12-21 12:20 UTC (permalink / raw
To: gentoo-doc-cvs
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>
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 4+ messages in thread* [gentoo-doc-cvs] cvs commit: hb-net-advanced.xml
@ 2005-08-14 5:42 Shyam Mani
0 siblings, 0 replies; 4+ messages in thread
From: Shyam Mani @ 2005-08-14 5:42 UTC (permalink / raw
To: gentoo-doc-cvs
fox2mike 05/08/14 05:42:05
Modified: xml/htdocs/doc/en/handbook hb-net-advanced.xml
Log:
#102392 - Fixing link to make sure it doesn't not point to x86 always. Thanks to pclouds for reporting.
Revision Changes Path
1.8 +5 -4 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.8&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.8&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.7&r2=1.8&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.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- hb-net-advanced.xml 14 Jun 2005 10:16:47 -0000 1.7
+++ hb-net-advanced.xml 14 Aug 2005 05:42:05 -0000 1.8
@@ -4,12 +4,12 @@
<!-- 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.7 2005/06/14 10:16:47 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-net-advanced.xml,v 1.8 2005/08/14 05:42:05 fox2mike Exp $ -->
<sections>
-<version>1.2</version>
-<date>2005-06-14</date>
+<version>1.3</version>
+<date>2005-08-14</date>
<section>
<title>Advanced Configuration</title>
@@ -181,7 +181,8 @@
<p>
For a more detailed discussion about dependency, consult the section
-<uri link="/doc/en/handbook/handbook-x86.xml?part=2&chap=4#doc_chap4">Writing
+<uri
+link="?part=2&chap=4#doc_chap4">Writing
Init Scripts</uri> in the Gentoo Handbook.
</p>
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2005-12-22 19:56 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-12-21 11:49 [gentoo-doc-cvs] cvs commit: hb-net-advanced.xml Jan Kundrat
-- strict thread matches above, loose matches on Subject: below --
2005-12-22 19:55 Jan Kundrat
2005-12-21 12:20 Jan Kundrat
2005-08-14 5:42 Shyam Mani
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox