Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!apple!amdcad!sun!pitstop!sundc!seismo!uunet!mcvax!enea!erbe.se!prc From: prc@ERBE.SE (Robert Claeson) Newsgroups: comp.arch Subject: Re: Operating Systems (Re: archimedes) Message-ID: <343@maxim.ERBE.SE> Date: 30 Nov 88 08:37:42 GMT References: <12633@steinmetz.ge.com> <6191@killer.DALLAS.TX.US> <12655@steinmetz.ge.com> Organization: ERBE DATA AB Lines: 19 In article <12655@steinmetz.ge.com>, davidsen@steinmetz.ge.com (William E. Davidsen Jr) writes: > One of the real shortcomings in many operating systems is the lack of > "append" permission, or lack of enforcement of it. There are many cases > in which a program should log its execution, but in many environments > there is no way to insure that the file is not modified. I wrote a > little error logging daemon which read stuff from a pipe, just to get by > this limitation in UNIX. I don't see a similar way to allow anyone to > add a file to a directory but not delete files. Maybe all permissions should be set on the object (ie, file system entry) it protects, so that a file has read, write, execute, delete, and append permissions, rather than giving delete permissions for files at the directory level (write)? Yes, this sounds much like VMS, Multics, etc, but those OS'es has their good spots... -- Robert Claeson ERBE DATA AB rclaeson@ERBE.SE