Create links instead of copies to save space and build flexible file layouts. 02.04.2026 | reading time: 2 min The `ln` command creates two flavors of links: hard links that share the same inode and symbolic links that point to a pathname; this short guide shows how to use both to avoid duplication and to craft flexible file layouts. Hands-on: hard versus symbolic Make a small example to see the difference: ```bash\necho "Hello" > original.txt\nls -li original.txt\nln original.txt hardlink.txt\nln -s original.txt symlink.txt\nls -li original.txt hardlink.txt symlink.txt\necho "Added via hardlink" >> hardlink.txt\ncat original.txt\nreadlink symlink.txt\n``` Practical tips and constraints Hard links point to the same inode so changing one changes the other and the link count increases; they cannot span different filesystems and you normally cannot create directory hard links; symbolic links are small pathname files, can cross filesystems and can become "broken" if the target is removed; useful options include `-s` to make symlinks, `-f` to force replacement and `--relative` to create relative symlinks that survive moves. Inspecting and finding links To reveal what kind of link you have, use `readlink` to print a symlink's target, `stat` to show inode and link count for hard links and `find -samefile` to locate other hard links to the same data; combine these when debugging deployments or dotfile setups. Next steps and practice Try converting duplicate copies into links in a safe test folder and observe inode numbers and link counts; then explore scripts that create links for deployment, backups or shared storage and consider studying for CompTIA Linux+ or LPIC-1 to deepen skills, with intensive exam preparation available at bitsandbytes.academy. Join Bits & Bytes Academy First class LINUX exam preparation. filesystem utilities storage
