Re: hard links to files on other filesystems disallowed: why?

The Natural Philosopher <tnp@xxxxxxxxxxxxxxx> wrote in news:hlpfid$b1j$3
@news.albasani.net:

There is a structural reason.

Hard links are duplicate directory entries actually on the disk.

They cannot refer to another disk.


Thanks for the explanations guys. I think I understand how it is done. Buy
nothing in these explainations precludes why the links cannot point to a
inode on another filesystem that is also mounted. If two filessytems are
both mounted all storage on them is pretty much identical in terms of
inodes etc. , right? Or maybe I don't see the obvious....

--
Rahul
.

Relevant Pages

  • Re: hard links to files on other filesystems disallowed: why?
    ... Hard links are duplicate directory entries actually on the disk. ... The directory entry contains the inode number in this filesystem. ...
    (comp.os.linux.misc)
  • Re: hard links to files on other filesystems disallowed: why?
    ... This would have to be a new, special filesystem UUID generated when the ... No. hard links have a dual set of pointers-- from the file names to the ... number) so if you delete A you do not delete the inode. ... the disk became unavailable. ...
    (comp.os.linux.misc)
  • Re: Hard links (and Snow Leopard services)
    ... zoara wrote: ... to a file are just directory entries with the same inode number. ... I think it was Apple's use of hard links for directories that originally ... knowing they're taking up no more disk space than ...
    (uk.comp.sys.mac)
  • Re: hard links to files on other filesystems disallowed: why?
    ... Hard links are duplicate directory entries actually on the disk. ... Buy nothing in these explainations precludes why the links cannot point to a inode on another filesystem that is also mounted. ...
    (comp.os.linux.misc)
  • unnecessary disk writes for named pipe inodes (2.4.21)
    ... evidence of a kernel infelicity. ... The written-out inode is identical to that already on ... On laptops the needless disk use is particularly harmful. ... userv creates a bunch of named pipes in /var/run/userv for each call, ...
    (Linux-Kernel)