Re: LINK a symbolic link?

New Message Reply About this list Date view Thread view Subject view Author view Attachment view

From: Neil Brown (neilb@cse.unsw.edu.au)
Date: 11/26/01-06:46:44 PM Z


From: Neil Brown <neilb@cse.unsw.edu.au>
Date: Tue, 27 Nov 2001 11:46:44 +1100 (EST)
Message-ID: <15362.57972.120059.962298@esther.cse.unsw.edu.au>
Subject: Re: LINK a symbolic link?

On Monday November 26, shepler@eng.sun.com wrote:
> On Mon, Peter ?strand wrote:
> > 
> > Is it valid to LINK a symbolic link? The Linux server currently returns 
> > NFS4ERR_SYMLINK in this case, but NFS4ERR_SYMLINK is not listed as a valid 
> > error for LINK in the draft specification. 
> 
> The type of the source object for the LINK operation can be a symbolic
> link.  The server should allow the LINK to succeed.

I don't think that is reasonable.  What is the server filesystem
simply does not support hard links on symlinks.

The file system use by the Domain/OS filesystem on apollo
workstations (anyone remember those?) did not support hardlinks on
symlinks though it did support hardlinks of files.

I think the server should be able to fail hardlinks on symlinks much
as it can on directories.  Maybe NFS4ERR_NOTSUPP or similar would be
appropriate.

NeilBrown


> 
> -- 
> Spencer


New Message Reply About this list Date view Thread view Subject view Author view Attachment view

This archive was generated by hypermail 2.1.2 : 03/04/05-01:49:21 AM Z CST