From: Rob Landley <rob@landley.net>
To: "Edgar E. Iglesias" <edgar.iglesias@axis.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] -chroot and -su options.
Date: Fri, 14 Mar 2008 10:26:45 -0500 [thread overview]
Message-ID: <200803141026.45682.rob@landley.net> (raw)
In-Reply-To: <20080314140857.GE17978@edgar.se.axis.com>
On Friday 14 March 2008 09:08:57 Edgar E. Iglesias wrote:
> > Even then, attempting to deal with things like symlinks that point to
> > absolute paths would be quite a headache, and considering the default
> > busybox install does exactly that, it's not exactly an unheard of corner
> > case...
>
> Hmm, our (axis) version of busybox uses relative paths for all symbolic
> links. It might be patched though, I haven't dug very deep. But otherwise
> yes, absolute symbolic links need to be considered with the sysroot
> approach.
It might help if you make "--sysroot" a synonym for "-L" and _document_ that
it affects all application emulation syscalls. But also document that it's
not a full solution. (In addition to relative paths, remember that symlinks
can resolve to other symlinks, and that every path component can be a symlink
so in a path like "one/two/three" if "two" is a symlink
to "../walrus/fruitbasket" and "walrus" is another symlink....
Implementing "readlink -f" isn't trivial. I should know, I worked out how to
do it properly for toybox but haven't had time yet.)
Probably the easiest thing to do for the moment is have both the --chroot and
the --sysroot options.
> Best regards
Rob
--
"One of my most productive days was throwing away 1000 lines of code."
- Ken Thompson.
next prev parent reply other threads:[~2008-03-14 15:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-04 0:28 [Qemu-devel] [PATCH] -chroot and -su options Rob Landley
2008-03-04 11:22 ` Edgar E. Iglesias
2008-03-05 6:51 ` Rob Landley
2008-03-05 7:54 ` Edgar E. Iglesias
2008-03-06 6:47 ` Rob Landley
2008-03-14 14:08 ` Edgar E. Iglesias
2008-03-14 15:26 ` Rob Landley [this message]
2008-03-14 16:06 ` Anderson Lizardo
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=200803141026.45682.rob@landley.net \
--to=rob@landley.net \
--cc=edgar.iglesias@axis.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).