From:	jason_zions AT interix DOT com (Jason Zions)
Subject:	RE: b19,20: ln -d - hard links .. ?
13 Nov 1998 09:30:44 -0800 :
Message-ID:	<31AA903A2A1FD111A06300805F4B6D64021262BE.cygnus.gnu-win32@ssi2.interix.com>
Mime-Version:	1.0
To:	"'Alex Madarasz'" <madarasz AT erols DOT com>, gnu-win32 AT cygnus DOT com

Unfortunately, the NTFS v3 reparse point mechanism is pretty weak (only one
reparse client can intercept a given reparse point) and the "symbolic link"
mechanism does not follow UNIX semantics (when encountering a symbolic link
reparse point on a remote fileserver, the remote server interprets the link
rather than passing the link contents back to the client for local
interpretation).

The limitations on NTFSv3 reparse points are sufficiently severe that they
can't safely be used to provide real UNIX-style symlinks. Very depressing.

Jason

-----Original Message-----
From: Alex P. Madarasz, Jr. [mailto:madarasz AT erols DOT com]
Sent: Thursday, November 12, 1998 3:01 AM

> NTFS supports hard links. The only exposed Win32 interface to them is
> BackupWrite, as you describe.

Until you get to NT5, thankfully, where MS has _finally_ added a Win32 call
for 
hard links, and where reparse points hold the promise of even "better" 
emulation of Unix-like filesystem features.  See the November MSJ :

 <http://www.microsoft.com/msj/1198/NTFS/NTFS.htm>
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -