The Linux that cloud, DevOps and security engineers use every day on a modern systemd and bash system: files and permissions, processes and services, shell scripts, text tools, disks and finding performance problems.
You’re reading a free preview. Sign up to see every topic and question — and to play this deck as games.
Where things live on a Linux system, how absolute and relative paths work, and how inodes, hard links and symbolic links relate to each other.
40 total questions
Card #1
What is an inode?
Card #2
Where is a file's name actually stored?
Card #3
What is a hard link?
1. On Linux, `ln /data/report.csv ~/report.csv` fails with "Invalid cross-device link". /data is a separate disk. Why?
2. Which of these can't you create a hard link to on Linux, even as root?
3. A file has two hard links: notes.txt and backup/notes.txt. You run `rm notes.txt`. What happens to the data?
1. The ___ command prints a file's inode number, size, permissions and its access, modify and change times.
Hint: A four-letter command, short for status.
2. `cd ___` switches back to the directory you were in before your last cd.
Hint: A single punctuation mark, the one flags start with.
3. To list files including hidden ones, whose names start with a dot, run `ls ___`.
Hint: One flag, for all.
