Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 alpha 4/15/85; site munnari.OZ
Path: utzoo!watmath!clyde!burl!ulysses!gatech!seismo!munnari!kre
From: kre@munnari.OZ (Robert Elz)
Newsgroups: net.unix-wizards
Subject: Re: 4.2bsd Oddity (BUG?)
Message-ID: <1023@munnari.OZ>
Date: Mon, 16-Dec-85 16:43:41 EST
Article-I.D.: munnari.1023
Posted: Mon Dec 16 16:43:41 1985
Date-Received: Tue, 17-Dec-85 07:48:00 EST
References: <721@brl-tgr.ARPA> <729@brl-tgr.ARPA>
Organization: Comp Sci, Melbourne Uni, Australia
Lines: 23

In article <729@brl-tgr.ARPA>, gwyn@brl-tgr.ARPA (Doug Gwyn <gwyn>) writes:
> The owner of the parent directory should be able to "mv"
> the subdirectory elsewhere ...

I assume that Doug chose the words "should be able" very carefully.
This cannot be done of course, as to move a directory, you have to
change its back pointer (".."), and that involves writing in the (child)
directory, which means that you have to have write permission in there...

[Aside: I know that manipulating directories is a root only function,
and root has permission to do anything, all that is irrelevant, the
setuid programs that implement this, or the kernel sys calls that
replaced them in 4.2, implement the same protection checks].

This is a logical outcome of the file system protection design,
to change it would break some of the regularity of the whole
thing.  Whether that's important in this case is another matter
entirely.  This is also not a 4.2 "problem", this has existed in
all of the research unix versions, since v5 at least.  I have no
idea what USG/USDL may have done in this area, but I suspect its
probably the same in the Sys N releases too.

Robert Elz	seismo!munnari!kre	kre%munnari.oz@seismo.css.gov