From: Graeme Gregory <dp@xora.org.uk>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Cleaning up SDK/Toolchain
Date: Mon, 22 Oct 2007 22:02:55 +0100 [thread overview]
Message-ID: <20071022220255.497852be@cimmeria> (raw)
In-Reply-To: <1193077473.6088.68.camel@localhost.localdomain>
> > That would be a better approach. Graeme, do you still want to have a
> > shot at implementing a unionfs based approach?
>
> Hmm. Does that need root privs?
>
Not what I was thinking, which was to do a union via LD_PRELOAD
basically redirecting open and its friends. I once saw a program that
did this trick tomorrow I shall try and dig it out, and try and give
it a few simple tests.
Graeme
next prev parent reply other threads:[~2007-10-22 21:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-17 13:25 Cleaning up SDK/Toolchain Michael 'Mickey' Lauer
2007-10-18 9:39 ` Koen Kooi
2007-10-18 11:59 ` Richard Purdie
2007-10-18 13:44 ` Koen Kooi
2007-10-18 17:30 ` Koen Kooi
2007-10-22 11:39 ` Koen Kooi
2007-10-22 14:36 ` Richard Purdie
2007-10-22 15:34 ` Koen Kooi
2007-10-22 16:43 ` Graeme Gregory
2007-10-22 18:24 ` Richard Purdie
2007-10-22 20:46 ` Leon Woestenberg
2007-10-22 21:02 ` Graeme Gregory [this message]
2007-10-23 2:33 ` mwester
2007-10-24 20:34 ` Koen Kooi
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=20071022220255.497852be@cimmeria \
--to=dp@xora.org.uk \
--cc=openembedded-devel@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