So far we conditioned the logic that issues ansi sequences for resetting the TTY based on whether something is a pty is not (under the assumption we need no reset on ptys, since they are shortlived). This is simply wrong though. The pty that a container getty is invoked on is generally long-lived: as long as the container is up, and it will be reused between getty instances/sessions all the time. In such a case we really should reset properly. Let's instead make the logic dependent on whether TERM is set to anything other than "dumb". The previous commit made sure we always set TERM in a sensible way in systemd-run, hence this *explicit* logic sounds like a much better choice now, as it mea
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
