QuestionQ47

VerifiedDevices, Linux Filesystems, Filesystem Hierarchy Standard

When evaluating the use of hard links, which are valid reasons to avoid using hard links?

Explanation

Hard links are directory entries that refer to the same inode, and an inode exists within one filesystem. Consequently, a hard link cannot refer to a file on a different filesystem; a symbolic link is required when crossing filesystem boundaries. The linked names share the file’s metadata and contents, so they do not have separate ownership, permissions, ACLs, or copied data.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!