From: Sascha Hauer <s.hauer@pengutronix.de>
To: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 2/3] defaultenv-2: introduce /env/rc.d
Date: Tue, 13 Jan 2015 09:25:46 +0100 [thread overview]
Message-ID: <20150113082546.GC23940@pengutronix.de> (raw)
In-Reply-To: <1421130070-31704-2-git-send-email-plagnioj@jcrosoft.com>
On Tue, Jan 13, 2015 at 07:21:09AM +0100, Jean-Christophe PLAGNIOL-VILLARD wrote:
> as we now will use symlink on /env/rc.d to specify init order
>
> the script will be store in /env/init
>
> so any board can overwrite them or add script that need to run before a
> default one
Boards can overwrite scripts without links. Numbering the files seems
good because it makes the execution order more predictable and easier to
put a script between two other scripts.
But why links? On Linux PCs this allows to separate distribution
provided scripts from their actual (site specific) execution. Also
the same scripts can be executed from different runlevels.
On barebox I see no good reason for links. There is only one runlevel
in barebox and if I don't want to execute a script I can just remove it.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2015-01-13 8:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-13 6:19 [PATCH 0/3] defaultenv2: introduce init order Jean-Christophe PLAGNIOL-VILLARD
2015-01-13 6:21 ` [PATCH 1/3] defaultenv-2: fix misplace NV dir in env Jean-Christophe PLAGNIOL-VILLARD
2015-01-13 6:21 ` [PATCH 2/3] defaultenv-2: introduce /env/rc.d Jean-Christophe PLAGNIOL-VILLARD
2015-01-13 8:25 ` Sascha Hauer [this message]
2015-01-13 8:29 ` Jean-Christophe PLAGNIOL-VILLARD
2015-01-13 9:12 ` Jan Lübbe
2015-01-13 9:22 ` Jean-Christophe PLAGNIOL-VILLARD
2015-01-13 6:21 ` [PATCH 3/3] defaultenv-2: create a specific defaultenv for splash Jean-Christophe PLAGNIOL-VILLARD
2015-01-13 8:11 ` [PATCH 1/3] defaultenv-2: fix misplace NV dir in env Sascha Hauer
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=20150113082546.GC23940@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=plagnioj@jcrosoft.com \
/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