On Mon, Apr 05, 2004 at 10:25:42PM +0300, A. Alper ATICI wrote: >On Fri, Apr 02, 2004 at 11:55:52AM -0500, Nicholas Wourms wrote: >>To diverge, and I know Corinna will tell me to submit a patch, but I >>think the problem this raises is worth discussing. Even if we are >>using NT/2k/XP/2k3, we still could be using fat32 filesystem. So, >>another approach to fix this problem would be to extend the "managed" >>mount api. That is, put Cygwin in charge of maintaining an internal >>accounting of hard links which is agnostic to the filesystem being >>used. U/Win has had this approach for years now, so we know its >>possible. Of course, it be nice if old man Korn would let us see the >>source ;-). Just a thought. > >I've just had a look at U/Win to observe how it does hard links. It >creates a .links hidden folder in root directory to keep a file, about >50 bytes in size, for each hard linking file which are actually 0 byte >in size from FAT's point of view. When I dump that 50-byte file, half >of it contains the full pathname of the linking file; first 2 bytes of >the other half changes when the linking file is in another directory I >guess, maybe I can guess more after spending another hour or so, but >that's not the point here. The point is there's not anything >mysterious, FAT-hack or similar in this implementation. I'd wish >Cygwin implemented hard links by extending its shortcuts to include >related meta data, unless U/Win compatibility is a concern for Cygwin.
This really isn't a discussion that belongs on cygwin-apps. Please move to the main cygwin list.
