On Sat, Aug 04, 2007 at 09:34:15AM -0700, Dan Nicholson wrote: > > I believe I found a way to "fix" the error which doesn't require > changing the permissions of the host's pseudo-terms: tie stdin to > /dev/null when running the tests. Basically, this prevents the stdin > test from doing anything useful. If you look closely, though, the > stdout and stderr tests aren't doing anything either, though, because > they've been tied to a log file. So, I say we just go all the way and > make the terminal tests useless (especially since we're running them > through su, which is probably not the intended way). > > su-tools nobody -s /bin/bash -c "make tests" </dev/null > That feels much safer than using chown on /dev/stdin. But how do we explain it in the text ? "This test won't work when run like this, so we make it succeed by doing nothing useful" might raise a lot of questions about the point of testsuites in the minds of some of our readers ;)
ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
