Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-Id:	<3.0.5.32.20050502232204.00b52180@incoming.verizon.net>
X-Sender:	phumblet AT incoming DOT verizon DOT net
Date:	Mon, 02 May 2005 23:22:04 -0400
To:	cygwin AT cygwin DOT com
From:	"Pierre A. Humblet" <Pierre DOT Humblet AT ieee DOT org>
Subject:	mkdir -p and network drives
Mime-Version:	1.0

According to the Cygwin Faq,

*********
Why doesn't `mkdir -p' work on a network share?
Unfortunately, you cannot do something like this: 

bash$ mkdir -p //MACHINE/Share/path/to/new/dir
mkdir: cannot create directory `//MACHINE': No such file or directory

This is because mkdir checks for the existence of each directory on the path,
creating them as necessary. Since `//MACHINE' is not a directory (you can't cd
to it either), mkdir tries to create it, and fails. 
**********

This behavior would be fine with me, but the latest mkdir (GNU coreutils)
5.3.0
creates /MACHINE/Share/path/to/new/dir and returns 0

Pierre




--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -