On Wed, Mar 26, 2008 at 10:02:10PM +0000, David Laight wrote: > On Thu, Mar 20, 2008 at 06:53:42PM -0700, Bill Stouder-Studenmund wrote: > > > > I thought the idea was that an in-emulation symlink starts at /emul/foo. > > If it is /../blah, the /.. part lets the symlink escape the emulation. > > Lets say that /emul/foo/usr/lib is a symlink to /lib and I'm running a > program in emulation foo. > What do I get when I: > 1) opendir /usr/lib > 2) cd to /emul/foo/usr and opendir ./lib > 3) opendir /emul/foo/usr/lib > (assuming /emul/foo/emul/foo doesn't exist) > 4) A non-emulation program opens /emul/foo/usr/lib > > For the first 2 the desired effect has to be to open /emul/foo/lib. > The latter 2 are non-obvious! Agreed. And I think what I suggested (well, what I meant to suggest at least) would give /emul/foo/lib for 1, 2, and 3. For #4, I think you'd get /lib. Take care, Bill
Attachment:
pgp9YqdVAzZ34.pgp
Description: PGP signature