From owner-freebsd-current@FreeBSD.ORG Wed Feb 23 13:36:02 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 02DB716A4CE for ; Wed, 23 Feb 2005 13:36:02 +0000 (GMT) Received: from tower.berklix.org (bsd.bsn.com [194.221.32.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1D73A43D45 for ; Wed, 23 Feb 2005 13:36:01 +0000 (GMT) (envelope-from jhs@berklix.org) Received: from js.berklix.net (p549A356A.dip.t-dialin.net [84.154.53.106]) (authenticated bits=0) by tower.berklix.org (8.12.9p2/8.12.9) with ESMTP id j1NDZrYS014221; Wed, 23 Feb 2005 14:35:54 +0100 (CET) (envelope-from jhs@tower.berklix.net) Received: from fire.jhs.private (fire.jhs.private [192.168.91.41]) by js.berklix.net (8.12.11/8.12.11) with ESMTP id j1NDacJ4015335; Wed, 23 Feb 2005 14:36:48 +0100 (CET) (envelope-from jhs@tower.berklix.net) Received: from fire.jhs.private (localhost [127.0.0.1]) by fire.jhs.private (8.13.1/8.13.1) with ESMTP id j1NDZ7Z0046813; Wed, 23 Feb 2005 14:35:32 +0100 (CET) (envelope-from jhs@fire.jhs.private) Message-Id: <200502231335.j1NDZ7Z0046813@fire.jhs.private> To: chet.ramey@case.edu In-Reply-To: Message from Chet Ramey <050222210500.AA14687.SM@caleb.ins.cwru.edu> Date: Wed, 23 Feb 2005 14:35:07 +0100 From: "Julian H. Stacey" cc: vova@fbsd.ru cc: freebsd-current@freebsd.org cc: andreas.kohn@gmx.net Subject: Re: cd into // works? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Feb 2005 13:36:02 -0000 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.