From: Barry Kelly <bkelly.ie@gmail.com>
To: cygwin@cygwin.com
Subject: Re: cygpath unable to translate the *nix path to an NTFS junction point
Date: Sun, 16 Jan 2011 23:18:35 +0000
Message-ID: <dvu6j6l799sjtd2l6qqmkfo6krgriu4hpk@4ax.com>
References: <AANLkTik5e=pvzaqW+Rxq33NQu1AyaAq3uLmZD3Cb8s5N@mail.gmail.com> <20101123095529.GZ18309@calimero.vinschen.de>
In-Reply-To: <20101123095529.GZ18309@calimero.vinschen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

Corinna Vinschen wrote:

> > This leaves cygpath completely unable to translate the original path
> > of an NTFS junction.  This is proving to be a problem for me (I'm
> > trying to use the output of cygpath for the equivalent of a backtick
> > operation in another script...)
>=20
> Sorry if I don't get your problem.  The resulting path is correct, isn't
> it?  Cygwin handles junction points as symlinks.=20

This is the problem. Junction points aren't really like symlinks;
they're much more transparent (more hard-like) in the Windows ecosystem,
as very little software is designed to understand them. Junctions are,
however, often used to allocate space from some drives to subtrees in
other drives. This is normally completely transparent; but Cygwin
reading junctions as symlinks breaks it.

I'm currently using a rewritten cygpath just to get around this problem.
My cygpath just uses actual symlinks (created with ln -s or similar) and
mount points to do the conversion, and disregards junctions.

-- Barry

--=20
http://blog.barrkel.com/

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