Repository navigation
omamobile-firstboot 0.1.7: avoid repeated systemd reloads - #839
quatrixone wants to merge 1 commit into
Conversation
43fc9d3 to
f058914
Compare
|
Thank you for this, and for saying plainly what has and hasn't run. Both findings are real ones from a phone with a live console, and the condition is carefully written: it only skips systemd's setup for answers that validate, the placeholder and a broken file keep today's behaviour, and nothing from the answers reaches the journal. Since it is a draft, three things on direction rather than a full review:
I haven't run anything for this round; CI is green on this head. |
Enable and mask first-boot services without reloading systemd after each change. The units already enabled in the image stay active; first-session checks for bluetooth and systemd-timesyncd remain pending on devices. AI assistance: Codex. Signed-off-by: quatrixone <quatrix1@gmail.com>
f058914 to
06b5e07
Compare
|
I reworked this draft to keep only the
|
This PR keeps only the shared first-boot service enable/mask change.
It uses
--no-reloadso systemd does not reload after every unit change.The image already enables NetworkManager, networkd, resolved, sshd and sddm;
bluetooth, systemd-timesyncd and ufw are first enabled here.
Checks:
packages/omamobile-firstboot/test/all,tools/pr-check origin/main.Device comparison is pending: capture bluetooth and systemd-timesyncd active
state in the first session with and without this change. The Dipper
systemd.firstboot=offfix is device-specific in #714. This PR remains draftuntil the requested device checks are recorded.