[Ping Python maintainer]: enhancement request

Thorsten Kampe thorsten@thorstenkampe.de
Tue May 1 14:46:00 GMT 2007

* Christopher Faylor (Tue, 1 May 2007 10:22:58 -0400)
> On Tue, May 01, 2007 at 02:59:20PM +0100, Thorsten Kampe wrote:
> >* Eric Blake (Tue, 01 May 2007 07:27:49 -0600)
> >>According to Thorsten Kampe on 5/1/2007 7:11 AM:
> >>>Both things are actually the same under Cygwin (tested on my FAT32
> >>>flash drive and under Windows XP NTFS).
> >>
> >>True only for FAT and FAT32, which don't support hard links at all.
> >>
> >>>NTFS supports hard links but these are likely not the same as the Unix
> >>>hard links
> >>
> >>Actually, NTFS hard links are supported, and cygwin uses them
> >>(setup.exe, however, currently does not, so making a hard link in a
> >>package won't matter, since setup.exe turns it into a copy anyway).
> >>
> >>>and Cygwin ln does not create the Windows ones.
> >>
> >>Actually, cygwin ln resorts to whatever cygwin1.dll does in the link()
> >>syscall, and in the case of an NTFS drive, this creates an NTFS hard
> >>link.
> >
> >You are right.  Unfortunately you cannot "see" hard links in Cmd or 4NT
> >"dir" output (while softlinks are displayed as junctions).
> That's incorrect.  DIR does display hard links, at least on XP.

It displays the file but no information that this is "only" a hard 
link. With ls you have "-i" to check the inode...


Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

More information about the Cygwin mailing list