Select the THREE statements that are true about links on a Linux filesystem.
LPIC-1 Exam 101-500, objective 104. Devices, Linux filesystems, filesystem hierarchy standard hard
Machine-checked — no person has signed for it. This question was read against the source cited below by an automated pass, which found no contradiction. That is a weaker claim than it sounds: the same kind of process wrote the question, so it can confirm its own mistake.
Treat it as a good draft rather than as settled fact, and read the source below before you rely on it. It is not used in mock exams here — only questions a person has signed for are.
How these questions are written — where each question comes from, what the verification ledger records, and what happens when one is found wrong.
The options
Choose 3.
Correct A hard link and the name it was created from refer to the same inode.
True. That is the definition of a hard link: another directory entry for one inode. `ls -i` shows both names sharing an inode number.
Not correct A hard link may point at a file on another mounted filesystem.
False. Inode numbers are unique only within a single filesystem, so `ln` across a mount point fails with 'Invalid cross-device link'. Use ln -s instead.
Correct A symbolic link may point at a target on a different filesystem.
True. A symlink stores a path string, which the kernel resolves at access time, so nothing constrains it to one filesystem — or even to an existing target.
Not correct A symbolic link keeps resolving to the data after its target is deleted.
False. It becomes a dangling link: the path it stores no longer exists, so opening it fails with 'No such file or directory' even though the link itself is plainly visible in ls.
Correct Deleting the name a hard link was created from leaves the data accessible through the link.
True. Every hard link is equally the file. Removing one name only decrements the inode's link count.
Why
Hard links share an inode: same data, same permissions, same link count, confined to one filesystem, and normally not permitted on directories. Symbolic links are small files holding a path: they may cross filesystems, may point at directories, may dangle, and carry their own (usually irrelevant) permission bits. Use `ls -l` to spot the arrow of a symlink and the link count of a hard-linked file.
Where this comes from
- Cited
- LPI exam objective 104.6
- What it says
- Create and identify hard and symbolic links and know their differences.
Practise this
Reading one question is not practice. The trainer will draw a short set from objective 104 and space the ones you get wrong.
More questions on this objective
- A new disk /dev/sdb has no partition table at all. Which command writes an empty GPT partition table onto it without dropping you into an interactive editor? machine-checked
- You need the partition /dev/sdc1 on a USB stick to carry a FAT32 filesystem so that Windows machines can read and write it. Which command creates it? machine-checked
- You have just run `mkswap /dev/sdb2`. Which command makes the kernel start using that swap area immediately, without a reboot? machine-checked
- Why is it dangerous to run e2fsck against an ext4 filesystem that is currently mounted read-write? machine-checked
- On an ext4 filesystem at /dev/sda1 you want an automatic check to be forced after every 30 mounts. Which command sets that? machine-checked
- `df -h /var` reports the filesystem 100% full, but `du -sh /var` accounts for only about half that space. Nothing is hidden under a mount point. What is the most likely explanation? machine-checked
All questions on Devices, Linux filesystems, filesystem hierarchy standard