From 1875db4ff6cdbed45f4375a2cc04f2fe55f25a32 Mon Sep 17 00:00:00 2001 From: William Hubbs Date: Wed, 28 Dec 2011 11:17:58 -0600 Subject: net: document up_before_preup for BSD --- doc/net.example.BSD.in | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/doc/net.example.BSD.in b/doc/net.example.BSD.in index 2329fa2..585f73d 100644 --- a/doc/net.example.BSD.in +++ b/doc/net.example.BSD.in @@ -388,6 +388,17 @@ # # ${IFACE} is set to the interface being brought up/down # ${IFVAR} is ${IFACE} converted to variable name bash allows +# +# 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() { # # Remember to return 0 on success -- cgit v1.2.3