A colleague added a kernel argument at the boot loader menu and you want to confirm that the running kernel actually received it. Type the full path of the virtual file that shows the command line the running kernel was started with.

LPIC-1 Exam 101-500, objective 101. System architecture medium

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.

Answer

Type the answer.

Accepted answer

Case sensitive — Linux is, and grading LS as ls would teach a falsehood.

Why

The boot loader passes a single command-line string to the kernel, and the kernel exposes exactly that string, verbatim, as /proc/cmdline for the life of the boot. It is the authoritative answer to what the kernel was told, whereas the boot loader configuration only says what it would be told at the next boot. Arguments the kernel does not recognise are not errors: those in key=value form are passed on to PID 1 as environment variables and the rest as its arguments, and PID 1 may also read the string for itself, which is how systemd picks up parameters such as systemd.unit=.

Where this comes from

Cited
manual page proc(5)

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.

Practise LPIC-1 Exam 101-500

More questions on this objective

All questions on System architecture

Practise LPIC-1 Exam 101-500