Select the THREE items that a typical Linux installation keeps in /boot.
LPIC-1 Exam 101-500, objective 101. System architecture easy
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 The compressed kernel image, named something like vmlinuz-6.1.0-13-amd64
Correct. The boot loader must be able to read the kernel image before any normal filesystem is mounted, so it lives here, versioned by kernel release.
Correct The initramfs image, named something like initrd.img-6.1.0-13-amd64
Correct. It sits beside the kernel it belongs to, because the boot loader loads the pair together.
Correct The boot loader's generated menu, grub/grub.cfg
Correct. GRUB 2 keeps its configuration and modules in /boot/grub (or /boot/grub2), which is also why /boot must remain readable by the loader.
Not correct The loadable modules belonging to the running kernel
Wrong. Modules live under /lib/modules/<kernel version>/ on the root filesystem. Any module needed before that filesystem is mounted is copied into the initramfs instead.
Not correct fstab, the table of filesystems to mount at boot
Wrong. fstab is /etc/fstab. It is read by userspace after the root filesystem is already mounted, so it has no reason to be in /boot.
Why
The filesystem hierarchy reserves /boot for the static files the boot loader itself needs, which is why it is often a small separate partition, sometimes on plain ext4 even when the rest of the system uses LVM or encryption. Everything the loader must read before the kernel runs goes there; everything read after the root filesystem is mounted belongs in /etc or /lib. Kernel configuration files (config-<version>) and symbol maps (System.map-<version>) are usually present too, one set per installed kernel.
Where this comes from
- Cited
- manual page hier(7)
Practise this
Reading one question is not practice. The trainer will draw a short set from objective 101 and space the ones you get wrong.
More questions on this objective
- You have a module file for a network driver on disk but the driver is not loaded. Which command reports the module's description, license, its dependencies and the parameters it accepts, without loading it into the kernel? machine-checked
- A module was loaded together with several modules it depends on. Which command unloads that module and then also unloads the dependencies that are left with a use count of zero? machine-checked
- You are filing a hardware bug report and the maintainer asks for the raw PCI vendor and device ID numbers rather than the human-readable names lspci normally prints. Which lspci option produces the numeric IDs? machine-checked
- A USB device is not getting the device node you expect. You want to watch, live, the kernel uevents and the resulting udev events as you unplug and replug it. Which command does that? machine-checked
- On a traditional BIOS PC, the firmware has completed its power-on self test and selected the hard disk as the boot device. What happens next? machine-checked
- A systemd-based machine fails during a normal boot because a service hangs. At the boot loader menu you want to edit the kernel command line for this one boot so the system comes up in single-user rescue mode instead. Which parameter do you append? machine-checked