Exercise 2: journalctl -p err, Explained via Chapter 2 — Possible Solution
====================================================================

WHAT journalctl -p err ACTUALLY DOES
------------------------------
Per this chapter, it filters the systemd journal down to "only entries
at 'err' priority or worse" - meaning it shows err-level entries and
everything more severe than err, excluding anything less severe
(warning, notice, info, debug).

WHY CHAPTER 2's SYSLOG SCALE MAKES THIS IMMEDIATELY READABLE
------------------------------
Per this chapter, "journalctl -p accepts the exact same syslog
severity keywords (and numbers) covered in Chapter 2." Chapter 2 already
established that syslog's scale runs from 0 (Emergency, most severe)
to 7 (Debug, least severe), with "err" sitting at severity 3. Knowing
that scale means "err or worse" is immediately understandable as "err
and everything with a lower/more-severe number" (err, crit, alert,
emerg) - the exact same "lower number is worse, and this filter
means that number or lower" logic already learned in Chapter 2, just
applied through a command-line flag instead of a table.

WHY THIS ISN'T SOMETHING TO MEMORIZE SEPARATELY
------------------------------
Per this chapter's own tip box, the point is that -p err "already
makes sense" once the syslog scale is known - it's "the same '0
through 7, lower is worse' filter applied directly at the command
line," not a new, unrelated concept that happens to share some words
with Chapter 2's material.

WHY THIS WORKS AS AN ANSWER
------------------------------
It correctly explains what the flag filters (err and more severe),
and correctly connects that behavior directly back to Chapter 2's own
numbered severity scale rather than treating the two as unrelated facts.