Which THREE of these statements about the /proc and /sys pseudo-filesystems are true?
LPIC-1 Exam 101-500, objective 101. System architecture 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 /proc/cpuinfo describes the processors the kernel detected, including their model and supported flags
True. /proc/cpuinfo is generated by the kernel on read and is the usual place to check core count, model name and CPU feature flags such as vmx or svm.
Correct /sys exposes the kernel device model, so device attributes and the driver bound to each device are visible as a directory tree
True. sysfs is structured by kernel objects: buses, devices, classes and modules, which is why udev and tools such as lsblk read it.
Correct Writing to files under /proc/sys changes kernel tunables on the running system
True. /proc/sys is the sysctl interface, so echoing 1 into /proc/sys/net/ipv4/ip_forward has the same effect as sysctl -w net.ipv4.ip_forward=1, until the next reboot.
Not correct /proc is an ordinary on-disk filesystem, so its contents survive a reboot
False. procfs is virtual and generated in memory by the kernel; nothing under /proc is stored on disk and nothing there persists across a reboot.
Not correct The entries under /sys/class must be created by the administrator before a device can be used
False. The kernel populates sysfs automatically as devices are registered. Administrators read those entries, and udev rules match on them, but nobody creates them by hand.
Why
Both filesystems are virtual and exist only in memory. The rough division of labour: /proc is older and process-centric plus a grab bag of system information (/proc/<pid>, /proc/meminfo, /proc/interrupts, /proc/modules) and carries the sysctl tunables in /proc/sys; /sys is the newer, strictly structured view of the kernel's device model, which is what udev is built on. Changes made by writing to either are lost at reboot unless recorded in /etc/sysctl.conf or /etc/sysctl.d.
Where this comes from
- Cited
- LPI exam objective 101.1
- What it says
- Using the /proc and /sys filesystems to determine and configure hardware and kernel settings.
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