Given that you would need to include a file on the filesystem being created anyway, it seems better to me to just write an override. This all happens on a top-level squashfs anyway, so anything that happens in that squashfs will not be copied over to the final system during installation.
The actual contents of the service file matter little, what we have in subiquity already would work just fine. This isn't so much a bug for the subiquity deb package though... but the subiquity snap does not ship subiquity-debug (more or less on purpose). I think a "cleaner" way to handle this, given how systemd works, would be to have our getty do: ExecStart=-/bin/echo "Press enter to activate this shell" ExecStart=-/usr/bin/agetty --wait-cr --autologin ubuntu --noclear %I $TERM This would have the benefit of getting to a shell as 'ubuntu' rather than root (so much closer to a real live session, what it pretty much is); if it works. To be tested. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1680285 Title: provide better experience on vt2+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1680285/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
