On 8/2/07, Ken Moffat <[EMAIL PROTECTED]> wrote: > On Wed, Aug 01, 2007 at 02:53:59PM -0700, Dan Nicholson wrote: > > On 7/30/07, Ken Moffat <[EMAIL PROTECTED]> wrote: > > > > I got those failures on a single run (using jhalfs). I'm not sure > > what's causing the errors, but what's failing is `test -r /dev/fd/0' > > and `test -r /dev/stdin' (look at tests/test.right for the output that > > it's diffing to above). > > > > So, I suspect this has something to do with the su to the nobody user > > and how su handles these devices. But the last time I thought about > > this it hurt my head. It may have something even more to do with how > > our scripts are handling the user switching.
These files both end up being symlinks to /dev/pts/0 (or whatever pts device you logged into) - and the perms for this are root:~# ls -l /dev/fd/0 lrwx------ 1 root root 64 2007-08-02 14:30 /dev/fd/0 -> /dev/pts/0 root:~# ls -l /dev/stdin lrwxrwxrwx 1 root root 15 2007-08-03 02:22 /dev/stdin -> /proc/self/fd/0 root:~# ls -l /proc/self/fd/0 lrwx------ 1 root root 64 2007-08-02 14:30 /proc/self/fd/0 -> /dev/pts/0 root:~# ls -l /dev/pts/0 crw--w---- 1 root tty 136, 0 2007-08-02 14:30 /dev/pts/0 so the nobody user won't be able to read these devices. Not sure how you would work around that, unless you use login instead of su to start the nobody user doing the testing (which will change ownership of /dev/pts/x and hence the tests will pass) -- -- - Steve Crosby -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
