In Unix-like systems, hard links and symbolic links are fundamental tools for efficient file management.ย They offer convenience by allowing a file to appear in multiple directories without true content replication.
๐ฏ๐๐๐
๐ณ๐๐๐๐:
A hard link is a mirror reflection of an original file, created using the `ln` command. Think of it as a twin of the original, where both have identical attributes and content. Any modification in one is instantly mirrored in the other.
If you delete one, the other remains unaffected and intact. The system keeps track of hard links through a component called “i-node,” which also keeps a count of these links. When this count drops to zero, meaning all hard links and the original file are deleted, the system clears out the space they occupied. All hard links are on equal footing; no one link is superior.
However, hard links come with restrictions: Hard links must reside in the same file system as their original file because they rely on i-node numbers, unique only within a specific file system. Directories can’t have hard links, preventing potential confusion like circular links.
Syntax:
ln original.txt link.txt
๐บ๐๐๐๐๐๐๐ (๐บ๐๐๐) ๐ณ๐๐๐๐:
Symbolic links, created using the `ln -s` command, are shortcuts pointing to the actual file. They can have a path that’s either direct (absolute) or in relation to their location (relative). Unlike hard links, symbolic links don’t share the same status.
They act independently and don’t affect the original file’s link count. If the original file is deleted, the symbolic link remains but becomes ineffective, turning into a “dangling link.” Since symbolic links point to filenames rather than i-node numbers, they can link files across different file systems.
Also, unlike hard links, symbolic links can point to directories. Typically, when assessing permissions for operations on a symbolic link, the system refers to the permissions of the original file it points to, not the symbolic link itself.
Syntax:
ln -s original.txt shortcut.txt
๐พ๐๐๐ ๐๐ ๐๐๐ ๐๐๐๐
๐๐๐๐๐ ๐๐๐
๐๐๐๐ ๐๐๐๐๐?
Hard links:
When you want to create multiple directory entries for a file without duplicating the file’s content.
When you need to ensure that even if one of the links is deleted, the file content remains accessible through the other links.
Soft links:
When you want to create a reference to a file that resides on another filesystem.
When you want to link to directories.
When you want a link that can be easily identified and managed as a link (since it’s a separate type of file).
Their usage can also be seen in these situations:
Hard Link:
Resource Optimization: – f there are multiple instances of an application or module that use the same resources (e.g., libraries, binaries), hard links can help in reducing the storage footprint by linking to the same inode for identical resources.
Image Creation for Deployment: When creating images for mass deployment on multiple embedded devices, hard links can be used for common files across different versions or configurations of the image. This makes the image creation process more efficient and the resulting image smaller.
Multiversion Software: Embedded devices that need to maintain multiple versions of software or firmware for rollback purposes can use hard links for components that remain unchanged between versions.
Cache Management: In systems with caching mechanisms, if a cached item is to be available in multiple cache directories, hard links can be used instead of duplicating the cache item.
SoftLink:
Boot Selection: Some embedded devices support multiple boot modes or kernels. Symbolic links can be used to select which kernel or boot image to use at startup, allowing for features like recovery modes or test kernels.
Linking to Volatile Storage: Soft links can point to locations in volatile storage (like RAM disks or tmpfs) where temporary data is stored. This can help in reducing wear on non-volatile storage mediums like flash memory.
Device Pointers: In dynamic device management, where devices can be hot-swapped or where device naming might change across reboots, symbolic links can be used to provide consistent device pointers. For instance, /dev/modem might be a symbolic link pointing to the current modem device, even if its actual device name changes.
Fallback Mechanisms: In systems where a fallback is needed if a primary resource fails or is unavailable, a symbolic link can initially point to the primary resource and be quickly switched to a backup or secondary resource when needed.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
An Article by: Yashwanth Naidu Tikkisetty
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
