From: "William Hubbs" <williamh@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/openrc:master commit in: doc/
Date: Wed, 28 Dec 2011 17:18:19 +0000 (UTC) [thread overview]
Message-ID: <1875db4ff6cdbed45f4375a2cc04f2fe55f25a32.WilliamH@gentoo> (raw)
commit: 1875db4ff6cdbed45f4375a2cc04f2fe55f25a32
Author: William Hubbs <williamh <AT> gentoo <DOT> org>
AuthorDate: Wed Dec 28 17:17:58 2011 +0000
Commit: William Hubbs <williamh <AT> gentoo <DOT> org>
CommitDate: Wed Dec 28 17:17:58 2011 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/openrc.git;a=commit;h=1875db4f
net: document up_before_preup for BSD
---
doc/net.example.BSD.in | 11 +++++++++++
1 files changed, 11 insertions(+), 0 deletions(-)
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
next reply other threads:[~2011-12-28 17:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-28 17:18 William Hubbs [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-10-28 19:32 [gentoo-commits] proj/openrc:master commit in: doc/ William Hubbs
2012-10-22 14:43 William Hubbs
2012-10-16 19:16 William Hubbs
2012-06-07 4:20 William Hubbs
2012-03-19 20:54 Robin H. Johnson
2012-03-19 20:19 Robin H. Johnson
2012-02-18 23:16 William Hubbs
2011-12-28 16:41 William Hubbs
2011-11-14 18:36 William Hubbs
2011-11-12 20:33 Mike Frysinger
2011-03-29 7:57 Robin H. Johnson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1875db4ff6cdbed45f4375a2cc04f2fe55f25a32.WilliamH@gentoo \
--to=williamh@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox