Am 25.09.2014 um 18:53 schrieb William G. Scott:
(About 10 years ago I found a hard link to a then nonexistent ksh behaved properly whereas a symbolic link for whatever reason didn’t).
A hardlink is nothing more than another name for the same file. When ksh was deleted, the system has just deleted that one NAME of the file, but it stayed there under the other name (sh). That's the reason why you can't create hardlinks across filesystem borders. BTW: You can identify hardlinked files by looking at
A symlink, OTOH, is just a NEW (special) file, pointing to another file which may exist or not.