Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.ARPA
Path: utzoo!watmath!clyde!cbosgd!cbdkc1!desoto!packard!ihnp1!ihnp4!mhuxn!mhuxr!ulysses!ucbvax!info-vax
From: info-vax@ucbvax.ARPA
Newsgroups: fa.info-vax
Subject: File ownership under VMS 4.x
Message-ID: <9524@ucbvax.ARPA>
Date: Thu, 1-Aug-85 00:52:44 EDT
Article-I.D.: ucbvax.9524
Posted: Thu Aug  1 00:52:44 1985
Date-Received: Fri, 2-Aug-85 05:56:02 EDT
Sender: daemon@ucbvax.ARPA
Organization: University of California at Berkeley
Lines: 24

From: <#D15%DDATHD21.BITNET@WISCVM.ARPA>

I believe that the new file-ownership mechanism under VMS 4.x
is the revenge of the DEC 10/20 people for not longer developing
their systems (they used this mechanism for centuries and
they couldn't understand that people were happy with the old
VMS method).

I would appreciate if I could choose between the old and the
new mechanism (SYSGEN parameter ???) because I love the old
method.

The new method has some advantages but one serious disadvantage:
when I analyse a problem for another user and I produce a lot
of output using **his** diskquota, I may overdraft his quota
because I have the EXQUOTA privilege in the SYSTEM account. In this
case the poor boy/girl can loose a lot of batch jobs before **my**
files are deleted.

---> **I** want to own **my** files and **I** don't want to own
     the garbage of **any** privileged user in the system.


Martin