Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!munnari!otc!metro!basser!boyd
From: boyd@basser.oz (Boyd Roberts)
Newsgroups: comp.unix.wizards
Subject: Re: /bin/test and stat(2)
Message-ID: <1076@basser.oz>
Date: Tue, 13-Oct-87 23:38:22 EDT
Article-I.D.: basser.1076
Posted: Tue Oct 13 23:38:22 1987
Date-Received: Fri, 16-Oct-87 22:37:04 EDT
References: <9479@brl-adm.ARPA> <29056@sun.uucp> <15069@topaz.rutgers.edu> <1036@basser.oz> <6532@brl-smoke.ARPA>
Reply-To: boyd@basser.oz (Boyd Roberts)
Organization: Dept of Comp Sci, Uni of Sydney, Australia
Lines: 25

In article <6532@brl-smoke.ARPA> gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>) writes:
>In article <1036@basser.oz> boyd@basser.oz (Boyd Roberts) writes:
>>I see ``.'' in every directory.
>
>You haven't looked at enough directories, then, particularly using
>distributed network file systems.

Since when has your ``network file system'' supported UNIX semantics?
We are, after all, talking about UNIX file-system semantics.  UNIX
directory semantics state that there's a ``.'' and a ``..''.  Both versions
of ``mkdir'' (the program & the system call) ensure that these two entries
are created WITH the directory.

So, what does your ``network file system'' do?  Is it a UNIX file-system?

I mean, where IS the beef?


As for the ``test ""'' nonsense, RTFM.  Ever used ${dir-.}?



Boyd Roberts			boyd@basser.oz

``When the going gets wierd, the wierd turn pro...''