Xref: utzoo comp.sys.pyramid:317 comp.unix.wizards:14548
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!unmvax!pprg.unm.edu!hc!lll-winken!lll-lcc!pyramid!csg
From: csg@pyramid.pyramid.com (Carl S. Gutekunst)
Newsgroups: comp.sys.pyramid,comp.unix.wizards
Subject: Re: Is SVR2 /bin/sh backwards compatible to v7?
Message-ID: <57985@pyramid.pyramid.com>
Date: 5 Feb 89 22:01:34 GMT
References: <165@apmpyr.nzapmb.co.nz> <57653@pyramid.pyramid.com> <1044@vsi.COM>
Organization: Pyramid Technology Corp., Mountain View, CA
Lines: 11

In article <1044@vsi.COM> friedl@vsi.COM (Stephen J. Friedl) writes:
>In the Sys V Rel 3 shell, test(1) uses stat(2) rather than access(2) to
>determine accessibility of the mentioned file (not just for directories).

Yup. Which is why directories in which you have permission to create new files
return "writable" under SVR3 test(1) (seems obvious, doesn't it?), but direc-
tories always return non-writable under BSD test(1). Proper suid behavior is
nice, too, although I'd argue that suid shells are just too dangerous for most
applications, especially when you have to be portable.

<csg>