PIBOOTCTL-LOAD(1)

✨ PIBOOTCTL-LOAD ✨

okay bestie, so this is the pibootctl-load page from the pibootctl manual, section 1, and it's literally the glow-up-your-boot-config command 🎀

---

🌸 NAME 🌸

pibootctl-load — bestie, it's a page in the pibootctl manual, that's the whole name section, we love a low-effort moment 💅

---

🦋 SYNOPSIS 🦋

pibootctl load [-h] [--no-backup] name

---

💖 DESCRIPTION 💖

It overwrites the boot configuration you're running right now with one you saved earlier. Swaps it out. Out with the old (well, out with the new, actually, in with the old) 🫶

---

✨ OPTIONS ✨

• name — the name of the boot configuration you wanna restore, queen 👑
• -h, --help — pops up a lil brief help page for the command, no cap 💅
• --no-backup — tells it don't take an automatic backup of your current boot configuration if one doesn't exist yet. Bold. Iconic. Risky 😭

---

🌈 USAGE 🌈

So load is the one you call when you want to replace your current boot configuration with one you stored earlier. Under the hood it's genuinely just unpacking the PKZIP (yes, the file format, [that zip thing](https://en.wikipedia.org/wiki/Zip_(file_format)) — I'm keeping the link, it's in the original, iykyk) of the stored boot configuration straight into the boot partition, and it just bulldozes over whatever files were already sitting there 😌

If your current boot configuration was never stored (with the save command, its bff), then an automatically named backup gets saved first, before anything gets overwritten:

$ sudo pibootctl save default
$ sudo pibootctl set video.hdmi0.group=1 video.hdmi0.mode=4
$ sudo pibootctl load default
Backed up current configuration in backup-20200310-095646

See that backup-20200310-095646? That's your safety net, bestie 🧚 and you can dodge the whole thing with the --no-backup option if you're feeling chaotic.

WARNING: ⚠️ okay so, the command is written to guarantee that no files will ever be left half-written — files get unpacked to a temporary filename and then atomically moved into their final location, overwriting any existing file. Slay. BUT — and this is the big but, listen — the utility cannot guarantee that if an error happens, the configuration as a whole isn't half-written (i.e. that one or more files failed to unpack). In other words: if it fails, you cannot assume your boot configuration is consistent. Not even a little. It's giving chaos, and not the fun kind 💀

---

💜 AUTHOR 💜

Dave Jones 🌸 (the legend himself)

---

🎀 COPYRIGHT 🎀

2019-2020 Dave Jones

---

and that's the whole page, bestie!! pibootctl version 0.5.2, dated Sep 14, 2020 — go forth and restore your configs responsibly, mwah 💅💖✨