X-Spam-Check-By: sourceware.org
Date: Tue, 1 May 2007 10:58:21 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: [Ping Python maintainer]: enhancement request
Message-ID: <20070501145821.GH17841@trixie.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <f137va$5ar$1 AT sea DOT gmane DOT org> <20070501120623 DOT GA3824 AT tishler DOT net> <f17e9m$gql$1 AT sea DOT gmane DOT org> <46374055 DOT 9080803 AT byu DOT net> <f17h3p$vjg$1 AT sea DOT gmane DOT org> <20070501142258 DOT GE17841 AT trixie DOT casa DOT cgf DOT cx> <f17iv2$6nd$1 AT sea DOT gmane DOT org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <f17iv2$6nd$1@sea.gmane.org>
User-Agent: Mutt/1.5.11
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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

On Tue, May 01, 2007 at 03:30:59PM +0100, Thorsten Kampe wrote:
>* 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...

It doesn't matter what DIR displays.

I don't think it's fruitful to spend a lot of time worrying about how
the non-POSIX, non-LINUX, MS-DOS shell interacts with the more advanced
things that Cygwin does.  <broken record>The whole point of Cygwin is
to make things better so that you don't have to use MS-DOS tools</broken record>.

Anyway, I'm only still typing because I'm trying to make sure that there
are no misconceptions in this thread which will come back to haunt in
the future.  I don't think that a hard link is the way to go unless
someone wants to fix setup.exe.

cgf

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