From: jqb AT netcom DOT com (Jim Balter) Subject: Re: Buglist 5 Apr 1997 08:13:51 -0800 Sender: daemon AT cygnus DOT com Approved: cygnus DOT gnu-win32 AT cygnus DOT com Distribution: cygnus Message-ID: <3345C2A5.D63.cygnus.gnu-win32@netcom.com> References: <009B24E0 DOT 05B6EC20 DOT 13406 AT ifk20 DOT mach DOT uni-karlsruhe DOT de> X-Mailer: Mozilla 3.01Gold (WinNT; I) MIME-Version: 1.0 Original-To: dahms AT ifk20 DOT mach DOT uni-karlsruhe DOT de Original-CC: iverson AT cisco DOT com, gnu-win32 AT cygnus DOT com Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Original-Sender: owner-gnu-win32 AT cygnus DOT com dahms AT ifk20 DOT mach DOT uni-karlsruhe DOT de wrote: > > Hi Tim, you wrote: > > : . Bash doesn't understand drive letters, multi-dot relative paths > : (eg. "cd ..."), or UNC pathnames (eg. //host/resource). > > What is a multi-dot path, please? I never saw ... only know . and .. > Under Unix ... has no reserved meaning, and AFAIK neither under NT. Under win32, paths consisting of only dots, with the exception of . and .., are illegal. This is along with a number of other illegal characters and combinations, including such winners as mkdir -p "abcde/xyz/con/ffo/bar" hanging as it tries to do I/O to the "con" device; lots of fun when you untar a 500Meg tar tape from some other system that was designed on less ad hoc principles. -- - For help on using this list, send a message to "gnu-win32-request AT cygnus DOT com" with one line of text: "help".