net: clean up documentation for up_before_preup
This commit is contained in:
parent
20f612080c
commit
26ceddae5e
@ -1103,15 +1103,16 @@
|
|||||||
# ${IFACE} is set to the interface being brought up/down
|
# ${IFACE} is set to the interface being brought up/down
|
||||||
# ${IFVAR} is ${IFACE} converted to variable name bash allows
|
# ${IFVAR} is ${IFACE} converted to variable name bash allows
|
||||||
#
|
#
|
||||||
# For historical & compatbility reasons, preup is actually normally called in
|
# For historical and compatibility reasons, preup is actually normally called
|
||||||
# the follow sequence: up ; preup ; up
|
# in the following sequence: up ; preup ; up.
|
||||||
# In that case, the first up causes the kernel to initialize the device, so
|
# 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
|
# that it is available for use in the preup function. However, for some
|
||||||
# hardware, eg CAN devices, some configuration is needed before trying to up
|
# hardware, e.g. CAN devices, some configuration is needed before trying to up
|
||||||
# the interface will actually work. For such harware, there are the
|
# the interface will actually work. For such hardware, the
|
||||||
# 'up_before_preup' variables, that skips the first up call.
|
# up_before_preup variables will allow skipping the first up call if set
|
||||||
#up_before_preup_IFVAR=no
|
# to yes.
|
||||||
#up_before_preup=no
|
#up_before_preup_IFVAR="NO"
|
||||||
|
#up_before_preup="NO"
|
||||||
|
|
||||||
#preup() {
|
#preup() {
|
||||||
# # Test for link on the interface prior to bringing it up. This
|
# # Test for link on the interface prior to bringing it up. This
|
||||||
|
Loading…
Reference in New Issue
Block a user