In message <20050901024144.GV6862@bcd.geek.com.au>, Daniel Carosone writes:

>On Wed, Aug 31, 2005 at 09:37:31PM -0400, Steven M. Bellovin wrote:
>
>> I checked the permissions and directory names for everything under
>> /emul/linux on the failing machine and one where it works.  The failing=
>=20
>> machine has /emul/linux/usr/pkg, but I didn't see anything under it=20
>> that looked relevant.
>
>So, it may just be the existence of that directory; a linux binary
>doing the equivalent of "cd /usr/pkg" will wind up in different places
>depending on whether /emul/linux/usr/pkg exists.
>
>Perhaps the easiest test would be to see whether creating that dir on
>the working machine breaks acroread (and likewise for any likely
>subdirs, if that's not it).

Ah -- excellent catch.  It turns out that it's the existence of
/emul/linux/usr/pkg/bin that causes the problem.  Having just
/emul/linux/usr/pkg doesn't cause any trouble.

It's getting late; I'll do some ktraces tomorrow to understand exactly 
what the problem is before I file a PR.

		--Steven M. Bellovin, http://www.cs.columbia.edu/~smb