On Sunday 08 January 2006 01:07, Randall R Schulz wrote:
Well, it does not behave like a hard link, either. For one thing, hard links (directory entries) are just
pairs, and the file system in which the inode number is looked up is implicitly that of the directory containing the directory entry from which the inode number was read.
I said it behaved like one, I didn't say it was one. And it does behave like one
Besides, for files (inodes) with no directory entries referring to them, it's the internal reference count on the kernel-resident inode structure that prevents reclamation of the inode and its resources (disk blocks), not a faked up directory entry in the proc pseudo-file system.
huh? When the "faked up" entry in /proc is created it increments the counter in the inode structure. Where is the contradiction?