emo/openrc
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

net: clean up documentation for up_before_preup

Browse Source
This commit is contained in:
William Hubbs
2011-12-28 10:41:07 -06:00
parent 20f612080c
commit 26ceddae5e
1 changed files with 10 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
doc/net.example.Linux.in
View File

@@ -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