problem with mkdir -p on network-path
Thu Nov 16 05:28:00 GMT 2000
On Wednesday 8 Nov 00, Andrej Borsenkow writes:
> > I use bash and fileutils from the latest distribution
> > on Windows-NT 4.0 SP5.
> > There is a domain server "GIS1" with a directory "GIS10".
> > The directory //GIS1/GIS10/UT/software/GAA_31 exists,
> > but not //GIS1/GIS10/UT/software/GAA_31/xxx.
> > mkdir -p //GIS1/GIS10/UT/software/GAA_31/xxx
> > delivers
> > mkdir: cannot create directory `//GIS1': No such host or network path
> > Question:
> > Why tries mkdir to create the directory which already exists?
> mkdir -p checks if every component of path exists and is directory. //GIS1 is
> _not_ directory (in the common sense). It is network server. And even
> //GIS1/GIS10 is not a directory - it is share on network server.
> I have no idea, how to check for existence of network server. Alternatively,
> mkdir -p could just skip //server and start with //server/share - this check
> is O.K.:
> mw1g017@MW1G17C% [[ -d //itsrm2 ]] && print yes!
> mw1g017@MW1G17C% [[ -d //itsrm2/Microsoft ]] && print yes!
Should mkdir be fixed to work across network shares, or shall I add
this to the FAQ?
Want to unsubscribe from this list?
Send a message to email@example.com
More information about the Cygwin