From: Alexander Dahl <post@lespocky.de>
To: ptxdist@pengutronix.de
Subject: [ptxdist] [PATCH] busybox: add more empty folders for ifupdown
Date: Mon, 30 Jul 2012 18:32:55 +0200 [thread overview]
Message-ID: <1343665975-13416-1-git-send-email-post@lespocky.de> (raw)
Hei there,
After upgrading to busybox v1.20.1 ifupdown complains about two
missing folders if-pre-down.d and if-post-up.d. This patch just
adds two lines for creating those empty folders.
Note: for initmethod systemd the same folders are created. As far as I
could see ifupdown is part of busybox. Is this very ifupdown used
together with systemd? Then these folders have to be added there, too.
Greets
Alex
Signed-off-by: Alexander Dahl <post@lespocky.de>
---
rules/initmethod-bbinit.make | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/rules/initmethod-bbinit.make b/rules/initmethod-bbinit.make
index b71d1af..f59c321 100644
--- a/rules/initmethod-bbinit.make
+++ b/rules/initmethod-bbinit.make
@@ -60,8 +60,10 @@ ifdef PTXCONF_INITMETHOD_BBINIT_ETC_INITD_NETWORKING
@$(call install_alternative, initmethod-bbinit, 0, 0, 0644, /etc/network/interfaces, n)
@$(call install_copy, initmethod-bbinit, 0, 0, 0755, /etc/network/if-down.d)
@$(call install_copy, initmethod-bbinit, 0, 0, 0755, /etc/network/if-up.d)
+ @$(call install_copy, initmethod-bbinit, 0, 0, 0755, /etc/network/if-pre-down.d)
@$(call install_copy, initmethod-bbinit, 0, 0, 0755, /etc/network/if-post-down.d)
@$(call install_copy, initmethod-bbinit, 0, 0, 0755, /etc/network/if-pre-up.d)
+ @$(call install_copy, initmethod-bbinit, 0, 0, 0755, /etc/network/if-post-up.d)
endif
ifdef PTXCONF_INITMETHOD_BBINIT_ETC_INITD_RT_SET_BANDWIDTH
--
1.7.2.5
--
ptxdist mailing list
ptxdist@pengutronix.de
next reply other threads:[~2012-07-30 16:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-30 16:32 Alexander Dahl [this message]
2012-09-03 15:29 ` Michael Olbrich
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=1343665975-13416-1-git-send-email-post@lespocky.de \
--to=post@lespocky.de \
--cc=ptxdist@pengutronix.de \
/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