From: jqb AT netcom DOT com (Jim Balter) Subject: Re: Minor bug and a question 12 Feb 1997 14:08:45 -0800 Approved: cygnus DOT gnu-win32 AT cygnus DOT com Distribution: cygnus Message-ID: <3301AE7C.5921.cygnus.gnu-win32@netcom.com> References: <01BC18D5 DOT F530AD80 AT gater DOT krystalbank DOT msk DOT ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 3.01Gold (WinNT; I) Original-To: Sergey Okhapkin Original-CC: "gnu-win32 AT cygnus DOT com" Original-Sender: owner-gnu-win32 AT cygnus DOT com Sergey Okhapkin wrote: > > Jim Balter wrote: > > > send it on to you. However, in reference to the original comment, there > > > are facilities in win32 to support hard links. > > > > Ok, but it is still NTFS-specific, and thus cannot be depended upon > > by gnu-win32. > > Why? Winsup code may create hard links on NTFS partitions and make a copy of file (as it works now) on FAT partitions. The context of ths discussion was a suggestion that foo and foo.exe be links instead of bash taking foo to mean foo.exe. That's a design decision that is affected by the cost of making a link. You can't assume that links are cheap; that's what I mean by "depend upon". I didn't say that you can't implement links as hard links on NTFS, you just can't DEPEND UPON the result of ln foo bar creating a hard link rather than a copy. -- - For help on using this list, send a message to "gnu-win32-request AT cygnus DOT com" with one line of text: "help".