Re: rename("symlink-to-dir/", "name") behavior

[Eric Blake]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to Geoff Clare on 1/28/2008 2:57 AM:
|>
|> My strict reading of the current wording in draft 4 does not permit Linux'
|> behavior (even though it is more useful, in my opinion), since the
|> trailing slash on B/ means that the old argument names a directory by the
|> rewritten path resolution rules in XBD 4.12 (line 3008).
|
| Right.  The behaviour on Solaris and FreeBSD is the one required
| by the standard.  It is also the behaviour on all certified UNIX03 and
| POSIX01 systems because a test for it is included in the tests for
| rename() in The Open Group's UNIX03/POSIX01 test suite.
|
| (I just checked, and Linux does indeed fail the test, which reports an
| unexpected ENOTDIR error.)
|
| Linux also gives ENOTDIR for rmdir("B/"), instead of removing A and
| leaving B as a broken link as the standard requires.

However, I find the Linux behavior (for rename at least) much friendlier,
and would like to see the standard permit that behavior.  So it sounds
like when I write the aardvark, that both behaviors need to be permitted,
rather than declaring existing behavior of UNIX03/POSIX01 invalid.

- --
Don't work too hard, make some time for fun as well!

Eric Blake             address@hidden
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHndh/84KuGfSFAYARAtUBAJ4lqYlp5xLOj9W7v384vUe2OZYosgCdFLZ5
q0W4aghdl2d61b1nJLI1BSM=
=JUv2
-----END PGP SIGNATURE-----