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 From: "Paul Derbyshire" To: cygwin@cygwin.com Date: Thu, 8 Aug 2002 02:56:52 -0400 MIME-Version: 1.0 Subject: Re: Symlink Question Reply-to: derbyshire@globalserve.net Message-ID: <3D51DDF4.13800.95FCA9E@localhost> Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body ------- Forwarded message follows ------- From: Paul Derbyshire To: cygwin@cygwin.com Subject: Re: Symlink Question (was: Re: Mysterious gdb behavior) Send reply to: derbyshire@globalserve.net Date sent: Tue, 6 Aug 2002 22:10:49 -0400 On 6 Aug 2002 at 22:55, Max Bowsher wrote: > However, since this question intrigued me, I did that myself: > > Cygwin creates its shortcuts by writing to the .lnk file itself (not through the > official Windows COM interfaces). Specifically, it requires that the shortcut > header be a specific sequence of bytes. A newly created windows shortcut does > not match this, presumably due to the introduction of fields that were always > null at the time when this bit of Cygwin was written. Peculiar. > Also, Cygwin .lnk symlinks should have the read-only attribute set to be > recognized as such. As I said I did make the attributes and other user-visible properties of the file identical. That included setting it read-only. > The situation becomes even more complicated on NTFS, when the symlink info is > stored in an EA, as well. In a what? ------- End of forwarded message ------- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/