Why can't hard links be created across different mounted filesystems, but symbolic links can?
hard📝 Conceptual Q10 of 15
Linux CLI - File and Directory Operations
Why can't hard links be created across different mounted filesystems, but symbolic links can?
ABecause hard links require root privileges across filesystems.
BBecause symbolic links are stored in memory, not on disk.
CBecause hard links point to inodes which are unique per filesystem; symbolic links store paths and can cross filesystems.
DBecause symbolic links are faster to create than hard links.
Step-by-Step Solution
Solution:
Step 1: Understand inode uniqueness
Inodes are unique identifiers for files within a single filesystem and cannot reference files on other filesystems.
Step 2: Understand symbolic link behavior
Symbolic links store a pathname as data, so they can point to files anywhere, including other filesystems.
Final Answer:
Because hard links point to inodes which are unique per filesystem; symbolic links store paths and can cross filesystems. -> Option C
Quick Check:
Hard links limited by inode scope; symbolic links store paths = Because hard links point to inodes which are unique per filesystem; symbolic links store paths and can cross filesystems. [OK]
Quick Trick:Hard links limited by inode; symbolic links store paths [OK]
Common Mistakes:
Thinking symbolic links are stored in memory
Assuming hard links need special privileges
Confusing speed with capability
Master "File and Directory Operations" in Linux CLI
9 interactive learning modes - each teaches the same concept differently