Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!decwrl!sun!pitstop!texsun!convex!uunet!mcvax!kth!enea!maxim!prc
From: prc@maxim.ERBE.SE (Robert Claeson)
Newsgroups: comp.unix.questions
Subject: Re: File Write Permission Rules
Keywords: file write permission rules
Message-ID: <502@maxim.ERBE.SE>
Date: 13 Feb 89 17:15:18 GMT
References: <306@wubios.wustl.edu> <9627@smoke.BRL.MIL>
Organization: ERBE DATA AB
Lines: 24

In article <9627@smoke.BRL.MIL>, gwyn@smoke.BRL.MIL (Doug Gwyn ) writes:
> In article <306@wubios.wustl.edu> david@wubios.wustl.edu (David J. Camp) writes:
> >My question is:  What is the (historical or otherwise) justification for
> >this rule?  It seems wrong.  I would have required write permission to
> >the file itself in order that it be removed.

> I don't know what you think of when you say "file", so let's talk
> about inodes instead.  One does NOT need to "write" (i.e. modify)
> the contents of an inode in order to remove the link to it from
> another (directory) inode, but one DOES need to be able to modify
> the directory inode.

I think that what David meant is that it would make more sense to let
all objects in the file system have its own attributes, instead of
relying on the directory permissions for some things. And I agree --
it certainly makes more sense to have a "delete" attribute on a file,
which must be set in order for me to remove it. And I'd like to add
an "append" attribute to the list.

-- 
Robert Claeson, ERBE DATA AB, P.O. Box 77, S-175 22 Jarfalla, Sweden
"No problems." -- Alf
Tel: +46 758-202 50  EUnet:    rclaeson@ERBE.SE  uucp:   uunet!erbe.se!rclaeson
Fax: +46 758-197 20  Internet: rclaeson@ERBE.SE  BITNET: rclaeson@ERBE.SE