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!linus!philabs!prls!amdimage!amdcad!decwrl!ucbvax!info-vax From: info-vax@ucbvax.ARPA Newsgroups: fa.info-vax Subject: new scheme for determining UIC of a created file Message-ID: <9417@ucbvax.ARPA> Date: Sun, 28-Jul-85 22:08:34 EDT Article-I.D.: ucbvax.9417 Posted: Sun Jul 28 22:08:34 1985 Date-Received: Tue, 30-Jul-85 05:36:39 EDT Sender: daemon@ucbvax.ARPA Organization: University of California at Berkeley Lines: 12 From: Andy Davenport In DECs defense: As a system manager, I find that the new scheme for determining the UIC that a new file will be given does just what I want it to do 99 percent of the time. With version 3.x I routinely got complaints from users that a file I had left in their directory for them was inaccessable. I had of course forgotten to SET FILE/OWN=PARENT. I or my co-workers would routinely leave a new version of SYLOGIN.COM inaccessable. Sure it was inattention on my part but the new scheme is better (in my humble opinion). Besides, attribute inheritance is what was universally requested through user input (SIR etc).