Message-ID: <4AF39A7F.7010000@cygwin.com>
Date: Thu, 05 Nov 2009 22:39:43 -0500
From: "Larry Hall (Cygwin)" <reply-to-list-only-lh AT cygwin DOT com>
Reply-To: cygwin AT cygwin DOT com
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.21) Gecko/20090320 Remi/2.0.0.21-1.fc8.remi Lightning/0.9 Thunderbird/2.0.0.21 Mnenhy/0.7.5.0
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: NTFS Symlinks (reparse point) redux
References: <4AF357E1 DOT 4010106 AT tlinx DOT org> <20091105230119 DOT GB2699 AT ednor DOT casa DOT cgf DOT cx> <4AF39229 DOT 6050204 AT tlinx DOT org>
In-Reply-To: <4AF39229.6050204@tlinx.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

On 11/05/2009 10:04 PM, Linda Walsh wrote:
>      If people get used to symlinks being around as they are
> on unix, then such a 'privilege' might become a common place
> configuration -- thus my desire to see cygwin be able to at least
> recognize and treat them as symlinks (first and foremost), with
> 'creating' them left open for some future possibility if they
> become more prevalent.

If someday there's actually good support for something that can be used
in Windows as symlinks are in Linux/Unix, I expect there will be lots of
interest in getting them fully supported in Cygwin.  We're not there yet.

> I can easily live with linkd/delrp, myself
> at this point, but I would really appreciate visual aids in recognizing
> them and where they link to -- like an "ls -l" of a dir showing me the
> path of such a symlink -- EVEN if it was a Winpath.  That'd be
> an "instant" clue that it was a reparse-symlink and not a conventional
> cygwin ".lnk" symlink....
>
>      Is that more 'palatable' with that suggestion?

Let's see.  So you'd like Cygwin to make changes to recognize reparse
points, even though there'd be no way to manipulate them and would not
point to a POSIX path.  That seems like allot of extra complication to the
already complicated and slow path handling code to support a questionable
Windows feature that many people won't be able to use in Windows.  And,
of course, if we were to do as you suggest, we'd then get questions about
how to *make* one of those, why it can't be done, and how come they don't
contain POSIX paths too.  Hm, I'm having trouble seeing the real benefit here
to the Cygwin community.  That said, I (and I expect others) would *love* for
Windows to have *real* symlinks without all these hokey restrictions. MS has
been taking swings at this for years now and, in my view, keeps failing to
connect.  I think we have to fight the temptation to see reparse points as
something that they're not.

-- 
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
216 Dalton Rd.                          (508) 893-9889 - FAX
Holliston, MA 01746

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

--
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