PIBOOTCTL-STATUS(1)

πŸ’– NAME πŸ’–

ok so this is pibootctl-status β€” it's a page from the pibootctl manual, and it's literally the girl who tells you what your Raspberry Pi boot settings are doing rn πŸ“βœ¨


✨ SYNOPSIS ✨

pibootctl status [-h] [-a] [--json | --yaml | --shell] [pattern]

🌸 DESCRIPTION 🌸

bestie, this command prints out the current value of all the modified boot time settings that match the pattern you give it. no pattern? then it just shows you everything that's been changed, periodt πŸ’…

and if you want the whole entire list, modified or not, you pass --all and it spills every single boot setting. no gatekeeping 🫢


πŸŽ€ OPTIONS πŸŽ€

  • pattern β€” if you give one, it only shows settings whose names match it. and yes, it takes shell globbing characters, so you can go feral with *, ?, and simple [classes] πŸ‘‘
  • -h, --help β€” shows you a lil brief help page for the command. it's giving helpful 🧚
  • -a, --all β€” includes all the settings in the output, whether they've been modified or not. by default only the modified ones show up, which is lowkey the whole point of the default. but with -a? everything. all of it. πŸ”₯
  • --json β€” makes the output JSON format.
  • --yaml β€” makes the output YAML format.
  • --shell β€” makes the output a var=value format that the shell can actually handle. iconic.

πŸ¦‹ USAGE πŸ¦‹

okay so by default, the status command only shows you the boot time settings that have been modified:

$ pibootctl status
+-------------+-------+
| Name        | Value |
|-------------+-------|
| i2c.enabled | on    |
| spi.enabled | on    |
+-------------+-------+

the full set of settings β€” which is usually several pages long, so it will implicitly invoke the system's pager (yes, it's about to take over your whole terminal, no cap) β€” gets displayed with the --all option:

$ pibootctl status --all
+------------------------------+----------+--------------------------+
| Name                         | Modified | Value                    |
|------------------------------+----------+--------------------------|
...
| i2c.baud                     |          | 100000                   |
| i2c.enabled                  | x        | on                       |
| i2s.enabled                  |          | off                      |
| serial.baud                  |          | 115200                   |
| serial.clock                 |          | 48000000                 |
| serial.enabled               |          | on                       |
| serial.uart                  |          | 0 (/dev/ttyAMA0; PL011)  |
| spi.enabled                  | x        | on                       |
| video.cec.enabled            |          | on                       |
...
πŸ‘€ heads up bestie: when you pass --all, a "Modified" column gets added to the output so you can see which settings are no longer default. the x marks the spot fr fr.

the list of settings can be filtered even more by giving a pattern with the command. the pattern can include any of the common shell wildcard characters:

  • * for any number of any character
  • ? for any single character
  • [seq] for any character in seq
  • [!seq] for any character not in seq

for example:

$ pibootctl status --all i2c.*
+-------------+----------+--------+
| Name        | Modified | Value  |
|-------------+----------+--------|
| i2c.baud    |          | 100000 |
| i2c.enabled | x        | on     |
+-------------+----------+--------+

and for the developers out there who wanna build stuff on top of pibootctl πŸ‘©β€πŸ’»βœ¨ β€” there are options to produce the output as JSON (--json), YAML (--yaml), and shell-friendly (--shell). these combine with all the aforementioned options as expected, no surprises:

$ pibootctl status --json --all i2c.*
{"i2c.baud": 100000, "i2c.enabled": true}

πŸ‘‘ AUTHOR πŸ‘‘

Dave Jones


2019-2020 Dave Jones


and that's the whole vibe check πŸ’… this was pibootctl-status(1) from pibootctl, version 0.5.2, dated Sep 14, 2020 β€” slay, go read your boot settings bestie πŸŒˆβ­πŸŽ€

πŸ“¦ where this page comes from