Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/18/84; site brl-tgr.ARPA Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!think!harvard!seismo!brl-tgr!tgr!Anw%maths.nottingham.ac.uk@UCL-CS.ARPA From: Anw%maths.nottingham.ac.uk@UCL-CS.ARPA Newsgroups: net.unix-wizards Subject: Re: /tmp versus temporary file types Message-ID: <2397@brl-tgr.ARPA> Date: Thu, 24-Oct-85 15:45:47 EDT Article-I.D.: brl-tgr.2397 Posted: Thu Oct 24 15:45:47 1985 Date-Received: Sat, 26-Oct-85 04:09:55 EDT Sender: news@brl-tgr.ARPA Lines: 9 > A null path component already has a meaning (same as "."). Well, yes, more-or-less; "the null file name refers to the current directory" [The UNIX Time-Sharing System], and repeated slashes are ignored, but (a) is this anything but a kludge so that "/" works? and (b) apart from "/", has anyone ever used this facility in real-life? V7 (but not some other systems) even allows "fred///" as a synonym for "fred" (an ordinary file); I can see no reason why this, and "///tmp//" and so on, should not be errors.