Problems with System V Release 2.1 on 68010

[Chris Torek]

In article <412 at hropus.UUCP> ka at hropus.UUCP (Kenneth Almquist) writes:
>[`#! /bin/sh' is] a Berkeley feature.  One weakness is that if
>you are running /bin/sh and invoke a shell procedure which begins
>with "#!/bin/sh", the kernel will exec /bin/sh even though /bin/sh
>is already running, so there is a cost to this approach.

The /bin/sh that is already running would have to fork to run
the script anyway, so this `cost' really amounts to the extra
code in the kernel required to perform this indirection.

>... I believe that providing an access system call without a
>corresponding eaccess system call was a mistake.

It seems to me that, rather than providing one new system call, we
should instead generalise `access':  have it take a uid.  Only root
should be able to determine access for values other than u.u_ruid
and u.u_euid, of course.
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 1415)
UUCP:	seismo!umcp-cs!chris
CSNet:	chris at umcp-cs		ARPA:	chris at mimsy.umd.edu