Xref: utzoo comp.unix.questions:9248 comp.bugs.4bsd:991
Path: utzoo!attcan!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!pasteur!ames!amdahl!pacbell!hoptoad!unisoft!mtxinu!sybase!bosco!ben
From: ben@bosco.UUCP (ben ullrich)
Newsgroups: comp.unix.questions,comp.bugs.4bsd
Subject: Re: another unix joke
Keywords: rmdir joke
Message-ID: <1049@sybase.sybase.com>
Date: 15 Sep 88 04:50:57 GMT
References: <8488@smoke.ARPA> <26090@ucbvax.BERKELEY.EDU>
Sender: news@sybase.sybase.com
Reply-To: sybase!ben@sun.COM (ben ullrich)
Organization: sybase, inc., emeryville, ca
Lines: 27

In article <26090@ucbvax.BERKELEY.EDU> bostic@ucbvax.BERKELEY.EDU (Keith Bostic) writes:
]In article <8488@smoke.ARPA>, gwyn@smoke.ARPA (Doug Gwyn ) writes:
]> More UNIX jokes, from 4.3BSD:
]> 
]> $ mkdir foo/
]> mkdir: foo/: No such file or directory
]> $ mkdir foo
]> $ rmdir foo/
]> rmdir: foo/: Is a directory
]
]Though I'm not sure what you're trying say, the behavior you're
]objecting to is correct.  As the NULL pathname is, by convention,
]the equivalent of ".", "foo/" is the same as "foo/.". Creating
]or removing "foo/." is illegal.  While it is arguable that the
]returned error should be different, or perhaps explicitly documented,
]4BSD is doing the right thing.  As POSIX 1003.1 does not support
]the equivalence of the NULL path and ".", the problem will die a
]natural death.

yeesh! it was only a amusing sort of anomaly; lighten up!
no one is ``objecting'' or purporting any ``arguable'' behavior!


...ben
--
ben ullrich				<something silly re: disclaimer>
sybase, inc.
emeryville, ca		{pyramid,pacbell,sun.com,mtxinu,capmkt}!sybase!ben