From: Patrick Ohly <patrick.ohly@intel.com>
To: OpenEmbedded <openembedded-core@lists.openembedded.org>
Subject: update-alternatives + absolute links
Date: Tue, 09 Feb 2016 12:03:39 +0100 [thread overview]
Message-ID: <1455015819.17004.21.camel@intel.com> (raw)
Hello!
I noticed that toybox's switch_root has problems handling /sbin/init
-> /lib/systemd/systemd. Apparently it tries to check permissions with
stat() before switching the root, and at that point resolving the
symlink fails.
Are there reasons for preferring absolute paths as link target? Using
relative paths would avoid the problem, and also make it easier to
investigate the content of the rootfs on the build host.
Is that something that would have to be fixed in the different
virtual/update-alternatives providers? I'm using opkg-utils at the
moment.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
next reply other threads:[~2016-02-09 11:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-09 11:03 Patrick Ohly [this message]
2016-02-09 14:42 ` update-alternatives + absolute links Patrick Ohly
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=1455015819.17004.21.camel@intel.com \
--to=patrick.ohly@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox