> -----Original Message-----
> From: Mladen Turk [mailto:[email protected]]
> Sent: donderdag 28 juli 2011 22:07
> To: Bert Huijben
> Subject: Re: Researched and adapted pre-vista/2008 windows symlinks
>
> On 07/28/2011 09:22 PM, Bert Huijben wrote:
> >
> >>
> >> So just asking, should we adopt this, before I start to work on it?
> >
>
> Attached a working solution :)
> The APR-zing should be quite simple
>
>
> > I don't think we should implement 'fake symlinks' for Windows as
> suggested here (and a few times on the Subversion list). That deliberately
> introduce a compatibility problem with the real symlinks that are supported
> on Windows Vista and later. And because we use an alternative symlink, we
> would have to maintain the not-real-thing forever and can't start supporting
> the real thing. And normal Windows applications would do everything in a
> different way.
> >
>
> FYI on Vista+ symlinks *are* Junction points. Their limit is still 32 per dir.
> It just happens Microsoft created an nice API for making them.
F:\tst>dir
Volume in drive F is Projects
Volume Serial Number is 8817-32E5
Directory of F:\tst
28-07-2011 22:12 <DIR> .
28-07-2011 22:12 <DIR> ..
28-07-2011 22:10 <SYMLINKD> dirlink [subdir]
28-07-2011 22:11 3 file
28-07-2011 22:12 <SYMLINK> filelink [file]
28-07-2011 22:11 <JUNCTION> junction [F:\tst\subdir]
28-07-2011 22:10 <DIR> subdir
2 File(s) 3 bytes
5 Dir(s) 97.194.647.552 bytes free
F:\tst>
How can dir see the difference if they are supposed to be the same thing?
My documentation says (if I remember correctly) they are stored in completely
different ways: One as a specific NTFS object type and one as a reparse point
with external data.
Bert
