Go to file

Thomas Stallinger 68b5c701cd docs: early_command doesn't work on Ubiquity; fix boot menu default direction

d-i preseed/early_command produced no trace anywhere (no log, no
syslog/installer-debug mention) -- Ubiquity runs its install steps via
its own Python plugin system (plugininstall.py), not the classic
debian-installer shell components that early_command/late_command are
bound to. Decided not to build a custom Ubiquity plugin or a
pre-ubiquity live-filesystem hook for this; organizational,
install-time-fixed parameters (partitioning, filesystem, branding) go
back to being baked into the personalized preseed at ISO-generation
time in the portal instead.

Also fixes a real safety bug in the test boot menus: the destructive
auto-install entry was the default (would run automatically on
timeout). Corrected to the opposite -- default is "boot from local
disk" (safe, nothing happens), the destructive install requires
actively selecting it from the menu. Verified in both the UEFI
grub.cfg and the BIOS isolinux config.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

2026-08-01 11:59:25 +02:00

adr

docs: early_command doesn't work on Ubiquity; fix boot menu default direction

2026-08-01 11:59:25 +02:00

architecture

docs: early_command doesn't work on Ubiquity; fix boot menu default direction

2026-08-01 11:59:25 +02:00