Attachment 75266 Details for Bug 116267 – hb-net-advanced.patch

[patch] hb-net-advanced.patch

hb-net-advanced.patch (text/plain), 6.92 KB, created by Jan Kundrát (RETIRED) on 2005-12-21 04:53:05 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Jan Kundrát (RETIRED)

Created: 2005-12-21 04:53:05 UTC

Size: 6.92 KB

patch

obsolete

>Index: doc/en/handbook/hb-net-advanced.xml
>===================================================================
>RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-net-advanced.xml,v
>retrieving revision 1.10
>diff -u -b -B -r1.10 hb-net-advanced.xml
>--- doc/en/handbook/hb-net-advanced.xml	21 Dec 2005 12:20:43 -0000	1.10
>+++ doc/en/handbook/hb-net-advanced.xml	21 Dec 2005 12:52:16 -0000
>@@ -8,18 +8,18 @@
> 
> <sections>
> 
>-<version>1.3</version>
>-<date>2005-08-14</date>
>+<version>1.4</version>
>+<date>2005-12-21</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>
>

Actions: View | Diff

Attachments on bug 116267: 75265 | 75266 | 75267 | 75270 | 75271 | 75272 | 75273 | 76467 | 76483