Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
From: "Paul Derbyshire" <derbyshire AT globalserve DOT net>
To: cygwin AT cygwin DOT com
Date: Thu, 8 Aug 2002 02:56:52 -0400
MIME-Version: 1.0
Subject: Re: Symlink Question
Reply-to: derbyshire AT globalserve DOT 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 <derbyshire AT globalserve DOT net>
To:             	cygwin AT cygwin DOT com
Subject:        	Re: Symlink Question (was: Re: Mysterious gdb 
behavior)
Send reply to:  	derbyshire AT globalserve DOT 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/