delorie.com/archives/browse.cgi | search |
X-Recipient: | archive-cygwin AT delorie DOT com |
DomainKey-Signature: | a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id |
:list-unsubscribe:list-subscribe:list-archive:list-post | |
:list-help:sender:content-type:mime-version:subject:from | |
:in-reply-to:date:content-transfer-encoding:message-id | |
:references:to; q=dns; s=default; b=uESWwDpIpoX63X7wbqQlupBviSjQ | |
lk1fy+0w3mmH3R0VJmGxUiYtMOtrST9FnFtrVhslOZsTKIzIKNvzjGUa/HS2PLSo | |
akZ7Uwr8OK3ebELcSVYL4tW51XW+eqoco1sX/K2WpchJtx1zfRq4ZuEzFKMx3N55 | |
DSDy6RPhoh/Qr5w= | |
DKIM-Signature: | v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id |
:list-unsubscribe:list-subscribe:list-archive:list-post | |
:list-help:sender:content-type:mime-version:subject:from | |
:in-reply-to:date:content-transfer-encoding:message-id | |
:references:to; s=default; bh=4ngWnVrQuRVCONHa3GiZOpY9rHM=; b=oK | |
vbPHWHVBe0FJ/iZ2dSytlKB7qZAecb3+jzh/ccg2T2+qBm9P5AUMBMMEurjWpaSo | |
0ReS0/BCYBdV7IqthYoN+kjPv/3dJ91s99YCTjaVRF2+T8EsI6Z6EMFbcKP+lgBD | |
Orl6UjPGyqDHCs1yZefyuPaLJh6EJjq2s6PVOc4D8= | |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Id: | <cygwin.cygwin.com> |
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 |
Authentication-Results: | sourceware.org; auth=none |
X-Virus-Found: | No |
X-Spam-SWARE-Status: | No, score=1.1 required=5.0 tests=AWL,BAYES_50,KAM_LAZY_DOMAIN_SECURITY,RP_MATCHES_RCVD autolearn=no version=3.3.2 |
X-HELO: | etr-usa.com |
Mime-Version: | 1.0 (Mac OS X Mail 8.2 \(2104\)) |
Subject: | Re: Error accessing mapped drive >2TB? |
From: | Warren Young <wyml AT etr-usa DOT com> |
In-Reply-To: | <20151023092007.GF5319@calimero.vinschen.de> |
Date: | Fri, 23 Oct 2015 16:04:03 -0600 |
Message-Id: | <0F9378A1-6890-42CE-BD19-578167F116AA@etr-usa.com> |
References: | <CA+2x6-L_pqdN6PHE0c15hcmrmB66Z75Hz95cH+dbcn4yXuVZNg AT mail DOT gmail DOT com> <712A87EA-64C7-4033-BE7F-39C8C8D527EB AT etr-usa DOT com> <20151021100328 DOT GL5319 AT calimero DOT vinschen DOT de> <CB8461F5-FB0E-44D8-81BB-B52DD02AD400 AT etr-usa DOT com> <20151021162254 DOT GC19868 AT calimero DOT vinschen DOT de> <169BF9F6-FF26-4073-9CC4-786882EFBAE9 AT etr-usa DOT com> <20151022083446 DOT GW5319 AT calimero DOT vinschen DOT de> <B8DBF0B5-51A9-4833-92D5-CA9E08B27DEC AT etr-usa DOT com> <20151023092007 DOT GF5319 AT calimero DOT vinschen DOT de> |
To: | cygwin AT cygwin DOT com |
X-IsSubscribed: | yes |
X-MIME-Autoconverted: | from quoted-printable to 8bit by delorie.com id t9NM4LnB030299 |
On Oct 23, 2015, at 3:20 AM, Corinna Vinschen wrote: > > Well, it was *you* asking "How could we prove that the problem is the > Apple SMB server?" I was just trying to help. If that's not desired, > I don't have to. I shouldn’t have suggested attacking the problem at the SMB protocol layer to begin with. That requires the sort of expertise that the Samba and Apple developers have, and I doubt I can get access to either. Since I’m not going to go and acquire such expertise myself just to answer the question, it’s a hopeless line of inquiry. Instead, it would be better if we can refine the Windows API C code we’ve been playing with to show the problem. Then I can attach it to an Apple bug report. I’m sure they like STCs, too. :) I’ve made the suggested changes to the program, here: http://pastebin.com/uZdDZPgi Is that enough to take to Apple? I mean, does this let them wiggle out and say, “You’re doing it wrong”? >>>>> HANDLE handle = CreateFile ("P:\\", ...); >>>> >>>> I guess I’m not seeing what values to pass to CreateFile() >>> >>> Opening a directory requires to use the FILE_FLAG_BACKUP_SEMANTICS >>> flag. >> >> Yes, silly me for not guessing that Windows requires that I tell it I >> am about to do a backup before I attempt to open a directory for >> reading. What was so wrong about the design of opendir() that MS had >> to reinvent it this way? > > Think DOS/early Windows. CreateFile was not meant to open directories > to perform a directory search I was reacting more to the revelation that Windows has workarounds for the known-problematic file access semantics, and that they’re specifically labeled as “for backup programs” when in reality they’re just ad hoc post facto fixes to a poorly thought out initial design. They’ve reinvented Unix, poorly. -- 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
webmaster | delorie software privacy |
Copyright 2019 by DJ Delorie | Updated Jul 2019 |