Date: Wed, 23 Feb 2005 14:35:07 +0100 From: "Julian H. Stacey" <jhs@berklix.org> To: chet.ramey@case.edu Cc: andreas.kohn@gmx.net Subject: Re: cd into // works? Message-ID: <200502231335.j1NDZ7Z0046813@fire.jhs.private> In-Reply-To: Message from Chet Ramey <chet@caleb.ins.cwru.edu> <050222210500.AA14687.SM@caleb.ins.cwru.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Chet Ramey wrote: > > >due to a typo, I typed > > > > > >[klamath] ~>cd // > > > > > >today. Okay, I'm used to the shell[1] changing any // into /, so I > > >expected to get to /. Now, I got there, but pwd/$PWD still have "//" in > > >them? > > This is from the bash FAQ: > > E10) Why does `cd //' leave $PWD as `//'? > > POSIX.2, in its description of `cd', says that *three* or more leading > slashes may be replaced with a single slash when canonicalizing the > current working directory. > > This is, I presume, for historical compatibility. Certain versions of > Unix, and early network file systems, used paths of the form > //hostname/path to access `path' on server `hostname'. I recall PCS Cadmus supported eg /../other_hostname/usr/other_person (on Unix Graphics workstations with proprietary networking extension). - Julian Stacey Net & Sys Eng Consultant, Munich http://berklix.com Mail in Ascii (Html=Spam). Ihr Rauch = mein allergischer Kopfschmerz.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200502231335.j1NDZ7Z0046813>