From: Phil Blundell <pb@pbcl.net>
To: Qi.Chen@windriver.com
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/8] initscripts: add setup-commands.sh
Date: Sat, 09 Nov 2013 23:00:34 +0000 [thread overview]
Message-ID: <1384038034.3798.46.camel@x121e.pbcl.net> (raw)
In-Reply-To: <74d67107ced2e10a00bc2ff9b84d42a7376fabae.1383974819.git.Qi.Chen@windriver.com>
On Sat, 2013-11-09 at 13:28 +0800, Qi.Chen@windriver.com wrote:
> +for dir in /usr/bin /usr/sbin; do
> + if [ ! -e $dir ]; then
> + if [ "$VERBOSE" != "no" ]; then
> + echo "WARN: $dir missing, setting up links to busybox"
> + fi
> + mkdir -p $dir
> + for suffix in ".nosuid" ".suid" ""; do
> + if [ ! -e /etc/busybox.links${suffix} ]; then
> + continue
> + fi
> + usr_commands=`grep "$dir" /etc/busybox.links${suffix}`
> + for command in $usr_commands; do
> + ln -sf /bin/busybox${suffix} $command
> + done
This seems slightly bogus for a number of reasons:
1. initscript doesn't obviously rdepend on busybox so it's not obvious
that the latter will always be available;
2. it should probably be using ${base_bindir} and ${bindir} rather than
hardcoding absolute paths.
3. the whole idea of creating a shadow "/usr/bin" underneath what's
meant to be a mountpoint seems rather dubious to me.
4. this seems like distro policy and not something that really belongs
in oe-core at all. For systems where ${bindir} and ${base_bindir} are
on the same filesystem (or even are the same directory) this script will
just make bootup slower without achieving anything useful.
p.
next prev parent reply other threads:[~2013-11-09 22:01 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-09 5:28 [PATCH 0/8] Fixes about unsafe-references QA warnings Qi.Chen
2013-11-09 5:28 ` [PATCH 1/8] udev: fix dependency and location of udevadm Qi.Chen
2013-11-09 22:54 ` Phil Blundell
2013-11-11 2:18 ` ChenQi
2013-11-11 10:53 ` Phil Blundell
2013-11-11 11:28 ` ChenQi
2013-11-09 5:28 ` [PATCH 2/8] initscripts: add setup-commands.sh Qi.Chen
2013-11-09 23:00 ` Phil Blundell [this message]
2013-11-11 2:52 ` ChenQi
2013-11-11 11:53 ` Phil Blundell
2013-11-11 12:40 ` ChenQi
2013-11-11 14:49 ` Phil Blundell
2013-11-11 16:13 ` Mark Hatle
2013-11-11 12:12 ` Burton, Ross
2013-11-11 12:53 ` ChenQi
2013-11-11 16:15 ` Mark Hatle
2013-11-09 5:28 ` [PATCH 3/8] zlib: install into base_libdir Qi.Chen
2013-11-09 5:28 ` [PATCH 4/8] kmod: install libkmod " Qi.Chen
2013-11-09 5:28 ` [PATCH 5/8] udev: fix unsafe reference by installing libgudev in libdir Qi.Chen
2013-11-09 5:28 ` [PATCH 6/8] insane.bbclass: make the checking stricter for unsafe references in scripts Qi.Chen
2013-11-09 5:28 ` [PATCH 7/8] iputils: fix program location and QA warning Qi.Chen
2013-11-09 5:28 ` [PATCH 8/8] busybox: install ping6 into bindir by default Qi.Chen
2013-11-11 11:12 ` [PATCH 0/8] Fixes about unsafe-references QA warnings Burton, Ross
2013-11-11 11:23 ` ChenQi
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=1384038034.3798.46.camel@x121e.pbcl.net \
--to=pb@pbcl.net \
--cc=Qi.Chen@windriver.com \
--cc=openembedded-core@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.