For a Server owner: drive health is readable, there's a wg command, and temperatures are visible. For a Desktop
owner: an AppImage or a manylinux Python package gets further before it fails.
Every edition carried BusyBox's crontab and crond, but nothing started crond and there was no
spool. crontab -e accepted jobs that never ran. Agents reach for cron first and reported those
jobs as scheduled, which is a worse failure than the tool being missing. Both applets are compiled
out; crontab and at are now stubs that print the systemd-timer equivalent, a unit pair,
systemd-run, and a cron-to-OnCalendar table, then exit 127. An incremental build kept symlinks
to applets BusyBox no longer builds, which hid the stub, so the core post-build removes those links
too.
Set against the Server's own user stories, the previous Server lacked things the Desktop had picked
up. The kernel gained Intel CPU and drive temperatures, nvme-hwmon, RAPL, the iTCO and sp51000
hardware watchdogs, the Hyper-V drivers with hv_utils and VMGENID (a Generation 2 VM couldn't see
its own disk), and the xe driver for Battlemage and Lunar Lake transcoding. The packages came
down from the Desktop layer to the Server's: smartmontools and nvme-cli so you can read SMART and
NVMe health, wireguard-tools because the WireGuard module was there but there was no wg to make a
key, ethtool, and the xe firmware. board/server/features-required.txt fails the build if any of it
goes missing, because that's exactly how these things quietly disappear.
Prebuilt apps stopped dying at load. Measured on the previous release, Chromium needed NSS/NSPR and
libXcomposite, and a Qt 6.5+ app that doesn't bundle libxcb-cursor fails with a platform-plugin
error because Qt dlopens it. The Desktop now ships NSS/NSPR, libsecret (the keyring client, backed by
oo7), the rest of the X client stack (Xcomposite, Xcursor, Xinerama, Xft, Xpm, XScrnSaver) and the
xcb-util family. Codecs, ICU, SDL and GTK2 stay out: apps bundle those. This does not make Chromium
a supported browser engine on PengyOS; it makes an AppImage that expects a desktop distro get as far
as its own code. Manylinux wheels were the other half: uv add opencv-python failed at import on
libGL.so.1, so libGL and libEGL now come from libglvnd's dispatch libraries with no GL driver
behind them.
Two smaller fixes for people who build: pengyos-appimage was rewritten around how AppImages are
actually used here, run in place, with inspect, integrate to put one in the app launcher and
check to name the libraries it needs that the system doesn't have; it had been parsing a metadata
trailer the format doesn't have. And running the build inside a distrobox on an installed PengyOS
Desktop turned up two holes in our own tooling, a missing qemu-system-gui (QEMU exits immediately
without its SDL display, so the Desktop boot check fails) and a test that read the container's
kernel command line instead of the machine's and so mistook an installed system for a live boot.