X-Spam-Check-By: sourceware.org Date: Mon, 19 Dec 2005 13:12:26 +0100 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: setup/symlinks/gcc/chown question Message-ID: <20051219121226.GF2965@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20051218202027.GC2965@calimero.vinschen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2i Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk 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 Dec 18 15:51, Karl M wrote: > Hi All... > > It appears to be file permissions related. The link being broken looks like > it is because the read only bit on the shortcut file (the .lnk file) is > getting turned off. Even though this first getfacl shows write access, the > read only box in the windows properties is checked. after the chown -h the > windows properties box says not a valid link. After the chmod -R 755, the > windows properties shows it as a valid shortcut, but the read only box is > unchecked. After a chmod -R 555, the read only box is checked and Cygwin > thinks it is a symlink again. > [...] Still, I can't reproduce this. I tried all variations I could think of, but I couldn't break the symlink using Cygwin coreutils chmod and chown tools. The only way I was able to break the symlink was by using the native Windows tool "attrib" to reset the readonly bit. Are you sure you're using Cygwin's chmod/chown? Did you try to run them under strace and see what happens? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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/