pengyos-update apply runs on the system you're updating from, so it wrote the new slot's
grub.cfg using the old version's template. 26.10.52 put the screen last on the kernel line, and
a machine updated to 26.10.52 still booted with the old order. Now pengyos-update confirm,
which runs at every boot once the system has started cleanly, renders the boot menu with the
running system's own code. It keeps the machine's kernel arguments, writes only when something
actually changed, and leaves a grub.cfg it can't read alone. Checked on the ThinkPad: the new
confirm, run by hand, rewrote what 26.10.51 had written, and the next boot showed its status on
screen.
On containers: Buildroot installed only the system podman.service and .socket, so
systemctl --user enable --now podman.socket failed with "Unit podman.socket does not exist",
which is what Docker-compatible tools ask for. The image now ships podman's user units, plus the
system podman-restart and auto-update ones (all disabled, as upstream ships them). Before this,
nothing brought a --restart=always container back after a reboot.
Two smaller things from the same testing: pengyos-vm create --image grows the disk to 20 GB by
default, because a Core VM kept the image's 1 GB root and had 362 MB free; and a forwarded port
now tells you to open it in the guest, since a PengyOS guest is default-deny and --forward
8080:80 answered nothing until pengyos-firewall allow 80 ran inside it.
And one rule written down. Asked on a Desktop to flash two USB sticks, Pengy in the web UI
downloaded and verified the images, then couldn't write them: pengy-web@.service had
NoNewPrivileges=yes, and ProtectSystem=strict would have kept /usr, /etc and /boot
read-only even as root. Both are off the unit. Principle 11 in docs/principles.md says why: Pengy
is never sandboxed. It reaches root through the user's own sudo password, the same way it would at
a terminal, and who can reach it is the user's call.