Re: hardlink to symlink behaviour [was: Re: MKXORG=yes on Linux: nbmtree: existing entry for `libXaw.so', type `link' does not match type `file']

[Thor Lancelot Simon <tls%rek.tjls.com@localhost>]

On Tue, Sep 30, 2008 at 02:59:32PM +0200, Joerg Sonnenberger wrote:
> On Tue, Sep 30, 2008 at 01:59:15PM +0200, Hubert Feyrer wrote:
> > Digging a bit more into this, it's related to the difference in handling  
> > hardlink to symlinks. On NetBSD, it seems that you get a link to the  
> > target file these days[1], while on Linux you get a link to the  
> > symlink[2]. ISTR that NetBSD used to behave like Linux there - is this  
> > really intended?
> 
> NetBSD behaves like POSIX and always has.

Does POSIX actually specify this?  The difference probably stems from
whether or not the symlink consumes an inode: on 4.3BSD and prior, it
always did, and on 4.4 and NetBSD it does not (or is arranged to look
as if it does not, in a few uncommon cases, IIRC).

-- 
Thor Lancelot Simon                                        
tls%rek.tjls.com@localhost
    "Even experienced UNIX users occasionally enter rm *.* at the UNIX
     prompt only to realize too late that they have removed the wrong
     segment of the directory structure." - Microsoft WSS whitepaper