1c9500c2b7
This adds TTYReset=yes to all units which run directly on the TTY. We already had this in place for the gettys, but this adds it for the rest that basically has StandardInput=tty + StandardOutput=tty set. Originally, for these tools it wasn't necessary to reset the TTY, because we after all already reset /dev/console very very early on once, during PID1's early initialization, and hence there's no real reason to do it again for these early boot services. But that's actually not right, because since #36666 the TTY we reset from PID 1 is typically /dev/console but the TTY those services are invoked on is typically the resolved version of that, i.e. wherever that points. Now you might think: if one is just an alias to the other, why does it matter to reset this again? Well, because it's only a half-assed alias, and as it turns out WIOCSWINSZ is not propagated from one to the other, i.e the terminal dimesions we initialize for /dev/console don't propagate to whatever that points to. One option to address that would be to immediately propagate this down ourselves (or to fix the kernel for it), but it felt safer to simply do the reset again before the use, after all these one one-off services, and there's no point in optimizing much here. Moreover, its probably safer to give the guarantee that when the firstboot stuff (which after all queries for pws to set) runs it definitely certainly guaranteed has a properly reset terminal.
System and Service Manager
Details
Most documentation is available on systemd's web site.
Assorted, older, general information about systemd can be found in the systemd Wiki.
Information about build requirements is provided in the README file.
Consult our NEWS file for information about what's new in the most recent systemd versions.
Please see the Code Map for information about this repository's layout and content.
Please see the Hacking guide for information on how to hack on systemd and test your modifications.
Please see our Contribution Guidelines for more information about filing GitHub Issues and posting GitHub Pull Requests.
When preparing patches for systemd, please follow our Coding Style Guidelines.
If you are looking for support, please contact our mailing list, join our IRC channel #systemd on libera.chat or Matrix channel
Stable branches with backported patches are available in the stable repo.
We have a security bug bounty program sponsored by the Sovereign Tech Fund hosted on YesWeHack
Repositories with distribution packages built from git main are available on OBS