A "hard link" is another name for an existing file; the link and
Original are indistinguishable. Technically speaking, they share
Same inode, And the inode contains all the information about
File -- indeed, it is not incorrect to say that the inode _ is _ the file.
On all existing implementations, you cannot make a hard link to
Directory, and hard links cannot cross file system boundaries. (These
Restrictions are not mandated by POSIX, however .)
"Symbolic Links" ("symlinks" for short), on the other hand, are a
special file type (which not all kernels support: system V Release 3
(and older) systems lack symlinks) in which the link file actually
refers to a different file, by name. when most operations (opening,
reading, writing, and so on) are passed the symbolic link file, the
kernel automatically "dereferences" the link and operates on the target
of the link. but some operations (e.g ., removing) work on the Link
file itself, rather than on its target. * Note Symbolic Links:
(libc) symbolic links.