X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org From: "Dave Korn" To: References: <20080204150853.GD5866@calimero.vinschen.de> <20080204205620.GA2720@ednor.casa.cgf.cx> <02fb01c86795$9aeb5080$2e08a8c0@CAM.ARTIMI.COM> <20080205133450.GB307@calimero.vinschen.de> Subject: RE: CIFS symlinks on network share break Cygwin Date: Tue, 5 Feb 2008 13:48:21 -0000 Message-ID: <032c01c867fd$c573da30$2e08a8c0@CAM.ARTIMI.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <20080205133450.GB307@calimero.vinschen.de> Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On 05 February 2008 13:35, Corinna Vinschen wrote: > What exactly happens with the perms? Are you using CYGWIN=smbntsec? Yep, and it doesn't help. It's solely down to the secureshare stuff not presenting through the standard NT api; it's only visible by using the shell extension dll. (... which makes me wonder, could we possibly leverage that to do some useful work for us in these situations...?) cheers, DaveK -- Can't think of a witty .sigline today.... -- 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/