Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/3/84; site security.UUCP Path: utzoo!linus!security!jjg From: jjg@security.UUCP (Jeff Glass) Newsgroups: net.unix-wizards Subject: Re: null pathnames Message-ID: <993@security.UUCP> Date: Mon, 11-Nov-85 12:19:27 EST Article-I.D.: security.993 Posted: Mon Nov 11 12:19:27 1985 Date-Received: Tue, 12-Nov-85 22:39:28 EST References: <2397@brl-tgr.ARPA> <742@whuxl.UUCP> <65@hadron.UUCP> Reply-To: jjg@security.UUCP (Jeff Glass) Organization: MITRE Corp., Bedford, Ma. Lines: 22 Summary: >> 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. One use I have found for this is in correcting pathname errors with the csh history mechanism: % /usr/local/lib/uucp/uucico ... /usr/local/lib/uucp/uucico: Command not found. % ^local^ /usr//lib/uucp/uucico ... % /jeff -- security!jjg@mitre-bedford.ARPA (MIL) {allegra,ihnp4,utzoo,philabs,uw-beaver}!linus!security!jjg (UUCP)