Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com To: Eric Blake Cc: "Pierre A. Humblet" , cygwin@cygwin.com, bug-coreutils@gnu.org Subject: Re: mkdir -p and network drives References: <3.0.5.32.20050502232204.00b52180@incoming.verizon.net> <42777719.8090103@byu.net> <8764xym6vf.fsf@penguin.cs.ucla.edu> <427A147D.2030109@byu.net> From: Paul Eggert Date: Thu, 05 May 2005 09:35:53 -0700 In-Reply-To: <427A147D.2030109@byu.net> (Eric Blake's message of "Thu, 05 May 2005 06:41:33 -0600") Message-ID: <87acn9aavq.fsf@penguin.cs.ucla.edu> User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.4 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Eric Blake writes: > //MACHINE currently generates ENOENT, whether or not there is a > server on the network with that name, and mkdir(2), stat(2), and > chdir(2) with an argument of "//MACHINE" fail. That's certainly a hassle. Let's not worry about going through zillions of lines of application code working around that incompatibility. Let's get Cygwin fixed instead. > By the way, the coreutils anon CVS mirror syncronization > appears to be hung again, It'll probably get resynced in a week or so. The CVS administrator is on vacation. In theory you can recover the current state by applying all the patches I've sent out via bug-coreutils. -- 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/