diff options
| author | Paul Menzel <pmenzel@molgen.mpg.de> | 2019-04-23 17:11:51 +0200 |
|---|---|---|
| committer | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2019-04-24 16:13:02 +0200 |
| commit | 1fa3ba909605c13761af69ae0ba1653292b6e730 (patch) | |
| tree | 77d2ac883492a1dc5de6ff4f5b0cc9c36e1babba | |
| parent | aba5472979168a47e426b06e720a4b0d50a56bfa (diff) | |
| download | systemd-1fa3ba909605c13761af69ae0ba1653292b6e730.tar.gz | |
NEWS: List getty@tty1.service as not being enabled anymore
Fixes: https://github.com/systemd/systemd/issues/12345
| -rw-r--r-- | NEWS | 5 |
1 files changed, 3 insertions, 2 deletions
@@ -242,8 +242,9 @@ CHANGES WITH 242: a different layout of the bootloader partitions (for example grub2). * During package installation (with `ninja install`), we would create - symlinks for systemd-networkd.service, systemd-networkd.socket, - systemd-resolved.service, remote-cryptsetup.target, remote-fs.target, + symlinks for getty@tty1.service, systemd-networkd.service, + systemd-networkd.socket, systemd-resolved.service, + remote-cryptsetup.target, remote-fs.target, systemd-networkd-wait-online.service, and systemd-timesyncd.service in /etc, as if `systemctl enable` was called for those units, to make the system usable immediately after installation. Now this is not |