Master Hard and Soft Links in Linux: When and How to Use Them

In Linux there are two types of file links: hard links and soft (symbolic) links. Hard links point directly to a file's inode, while soft links store a pathname to the target, similar to a Windows shortcut.

To create a hard link you use the ln command: ln [options] source_file target_file Each file has an inode that uniquely identifies it. Hard links share the same inode, so they must reside on the same filesystem and cannot be created for directories. Multiple hard links can point to the same inode, giving a file several names.

Example output of ls -i shows identical inode numbers for the original file and its hard link, confirming they reference the same data. Deleting one hard link removes only that name; the file remains accessible through any remaining hard links as long as at least one link exists.

Directories cannot be hard linked because it could create cycles in the directory tree, making path resolution ambiguous.

Hard links are useful for quick file recovery: if a file is accidentally deleted, any remaining hard link still points to the data, allowing you to retrieve the content without needing backups.

Soft links are created with a similar command: ln -s [options] source_path target_path Soft links store the path to the target and can span different filesystems. They may also point to non‑existent files, resulting in a dangling (dead) link. Deleting the original file leaves the soft link in the directory, but attempts to follow it will fail.

When a soft link points to a missing target, the system may report “Too many levels of symbolic links.” Using absolute paths instead of relative ones avoids this error.

Practical uses of soft links include shortening long command paths by linking them into a convenient directory, and sharing large library files among multiple cross‑compilation toolchains without duplicating data, thereby saving disk space.

Overall, while hard links have limited scenarios, soft links are widely used for flexibility across filesystems and for managing complex directory structures.