This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Problems with cygwin cvs over ssh.
- From: Sven Köhler <skoehler at upb dot de>
- To: cygwin at cygwin dot com
- Cc: corinna-cygwin at cygwin dot com
- Date: Sat, 04 Feb 2006 05:22:43 +0100
- Subject: Re: Problems with cygwin cvs over ssh.
- References: <ad2655cb0601250431w10c79e29t@mail.gmail.com> <dr8moj$3le$1@sea.gmane.org> <Pine.GSO.4.63.0601251554180.839@access1.cims.nyu.edu> <dr8r9d$mcs$1@sea.gmane.org> <Pine.GSO.4.63.0601251653430.839@access1.cims.nyu.edu> <dr927o$h87$1@sea.gmane.org> <Pine.GSO.4.63.0601251907330.839@access1.cims.nyu.edu> <dre28b$3et$1@sea.gmane.org> <Pine.GSO.4.63.0601271635150.27873@access1.cims.nyu.edu> <20060128085200.GB15572@calimero.vinschen.de>
>> Right. I missed the "." in the original message. The change that
>> prompted this behavior seems to be
>> <http://cygwin.com/ml/cygwin-cvs/2005-q3/msg00224.html>. I'm assuming the
>> motivation for this patch was to duplicate Linux's behavior (which doesn't
>> allow trailing "." in a path passed to mkdir).
>
> Indeed. Eric mentioned that the coreutils testsuite tests thsi behaviour
> explicitely. Since there's not much impact speedwise, we just added
> appropriate checks to be POIX compatible here.
I want to state, that cygwin might return the wrong error-code! Instead
of "file already exists" it returns "no such file or directory".
Cygwin's bahaviour:
$ mkdir /tmp/.
mkdir: cannot create directory `/tmp/.': No such file or directory
Linux' behaviour:
# mkdir /tmp/.
mkdir: cannot create directory `/tmp/.': File exists
Indeed, strace shows me, that on Linux mkdir() returns EEXIST in the
case of a mkdir("/tmp/.")-call. Cygwin doesn't seem to do it this way,
it seems to return ENOENT which would not be Linux-like ;-)
Unfortunatly i don't understand the output of cygwin's strace and cannot
check, what the mkdir("/tmp/.") returns there. Does anybody have a clue?
Sven
--
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/