Support basic hard-link semantics at least to the level that AFS supports it: . hard link emulation on top of inode emulation in fusex . full support (access/create/remove) currently only from fusex . only intra-directory hard-links Hard links persist in the EOS file system. In absence of an inode layer links are implemented similar to symlinks and record the target file's id in an attribute. Similarly, the link count is maintained in an attribute in the target file. When removed, the target is kept around under an invisible name (and the link count decreased), and finally removed when the link count goes to zero. The goal is to make eos with fusex as functional equivalent to AFS as possible, in this case enabling certain utilities used by e.g. rpmbuild. Initially, hard links are hence only functional from fusex and trigger errors when accessed from the eos console, xrdcp, etc... This could be improved given a valid use case.