From 26ceddae5e48bac07c82d754bd005df01492fa4f Mon Sep 17 00:00:00 2001 From: William Hubbs Date: Wed, 28 Dec 2011 10:41:07 -0600 Subject: net: clean up documentation for up_before_preup --- doc/net.example.Linux.in | 19 ++++++++++--------- 1 file changed, 10 insertions(+), 9 deletions(-) diff --git a/doc/net.example.Linux.in b/doc/net.example.Linux.in index d48983e..fd14134 100644 --- a/doc/net.example.Linux.in +++ b/doc/net.example.Linux.in @@ -1103,15 +1103,16 @@ # ${IFACE} is set to the interface being brought up/down # ${IFVAR} is ${IFACE} converted to variable name bash allows # -# For historical & compatbility reasons, preup is actually normally called in -# the follow sequence: up ; preup ; up -# In that case, the first up causes the kernel to initialize the device, so -# that it is available for use in the preup function. However, for some other -# hardware, eg CAN devices, some configuration is needed before trying to up -# the interface will actually work. For such harware, there are the -# 'up_before_preup' variables, that skips the first up call. -#up_before_preup_IFVAR=no -#up_before_preup=no +# For historical and compatibility reasons, preup is actually normally called +# in the following sequence: up ; preup ; up. +# The first up causes the kernel to initialize the device, so +# that it is available for use in the preup function. However, for some +# hardware, e.g. CAN devices, some configuration is needed before trying to up +# the interface will actually work. For such hardware, the +# up_before_preup variables will allow skipping the first up call if set +# to yes. +#up_before_preup_IFVAR="NO" +#up_before_preup="NO" #preup() { # # Test for link on the interface prior to bringing it up. This -- cgit v1.2.3