This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Problems with mkdir under 1.7
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Tue, 1 Jun 2010 09:57:27 +0200
- Subject: Re: Problems with mkdir under 1.7
- References: <AANLkTinzwewZXcs_Yilrk7SNu7SPaP8jzIajpEF7iDmm@mail.gmail.com> <20100531122034.GG16885@calimero.vinschen.de> <AANLkTin2EQP2liO1TiVFtNvi2IiWyDsXd-yACt692NU2@mail.gmail.com>
- Reply-to: cygwin at cygwin dot com
On May 31 19:36, Dave Hylands wrote:
> On Mon, May 31, 2010 at 5:20 AM, Corinna Vinschen
> <corinna-BEEP@BEEP.BEEP> wrote:
http://cygwin.com/acronyms/#PCYMTNQREAIYR
> > On May 28 11:33, Dave Hylands wrote:
> >> I've discovered a problem with mkdir under 1.7.x that worked fine under 1.5.x.
> >> [...]
> >> This one fails:
> >> mkdir -p //dfs-name/dfs-share/dir/newdir
> >> mkdir: cannot create directory '//dfs-name': No such file or directory
> >>
> >> This used to work fine under 1.5.x, so I assume it's a new bug.
> >
> > I don't know. I created two DFS namespaces on my 2008 server machine,
> > one domain namespace, one standalone namespace, and I can do the
> > aforementioned mkdir -p just fine in both namespaces.
>
> OK - I guess it's time to start debugging then....
That would be nice, given that you have easy access to the problematic
environment. I found another problem when accessing the DFS shares from
Windows 7 which seems to affect not only Cygwin but also Windows
Explorer. While it's not a Cygwin problem per se, an unwelcome side
effect in Cygwin is a crash due to an overwritten stack. I'll look into
avoiding the crash at least.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple