Attachment 75272 Details for Bug 116267 – hb-net-functions.patch

[patch] hb-net-functions.patch

hb-net-functions.patch (text/plain), 3.30 KB, created by Jan Kundrát (RETIRED) on 2005-12-21 05:32:41 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Jan Kundrát (RETIRED)

Created: 2005-12-21 05:32:41 UTC

Size: 3.30 KB

patch

obsolete

>Index: doc/en/handbook/hb-net-functions.xml
>===================================================================
>RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-net-functions.xml,v
>retrieving revision 1.6
>diff -u -b -B -r1.6 hb-net-functions.xml
>--- doc/en/handbook/hb-net-functions.xml	21 Dec 2005 13:27:46 -0000	1.6
>+++ doc/en/handbook/hb-net-functions.xml	21 Dec 2005 13:32:17 -0000
>@@ -8,30 +8,30 @@
> 
> <sections>
> 
>-<version>1.1</version>
>-<date>2005-06-14</date>
>+<version>1.2</version>
>+<date>2005-12-21</date>
> 
> <section>
> <title>Standard function hooks</title>
> <body>
> 
> 
>-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.
> 
> 
> 
>-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.
> 
> 
> 
>-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.
> 
> 
> 
>@@ -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>
> 
> 
>@@ -107,15 +107,15 @@
> 
> 
> 
>-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.
> 
> 
> 
>-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.
> 
> 
> 
>@@ -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>

Actions: View | Diff

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