summaryrefslogtreecommitdiff
path: root/presets
diff options
context:
space:
mode:
authorLennart Poettering <lennart@poettering.net>2020-04-02 17:01:34 +0200
committerLennart Poettering <lennart@poettering.net>2020-04-02 17:04:59 +0200
commitaade0c3b6e6f7a6d860cbcaf48a1d6dc02f4f460 (patch)
tree1f8007ae665b2dc76fcf9e0d744b5c2a330a06e4 /presets
parent0fc659eea9aef031d1aa6cf729f3927abcfcb922 (diff)
downloadsystemd-aade0c3b6e6f7a6d860cbcaf48a1d6dc02f4f460.tar.gz
Revert "units: make systemd-repart.service installable"
This reverts commit 7e1ed1f3b29162df25064b33dc55ac8cf432bb0b. systemd-repart is not a user service that should be something people enable/disable, instead it should just work if there's configuration for it. It's like systemd-tmpfiles, systemd-sysusers, systemd-load-modules, systemd-binfmt, systemd-systemd-sysctl which are NOPs if they have no configuration, and thus don't hurt, but cannot be disabled since they are too deep part of the OS. This doesn't mean people couldn't disable the service if they really want to, there's after all "systemctl mask" and build-time disabling, but those are OS developer facing instead of admin facing, that's how it should be. Note that systemd-repart is in particular an initrd service, and so far enable/disable state of those is not managed anyway via "systemctl enable/disable" but more what dracut decides to package up and what not.
Diffstat (limited to 'presets')
-rw-r--r--presets/90-systemd.preset1
1 files changed, 0 insertions, 1 deletions
diff --git a/presets/90-systemd.preset b/presets/90-systemd.preset
index db61ef12d3..6beedf79e7 100644
--- a/presets/90-systemd.preset
+++ b/presets/90-systemd.preset
@@ -19,7 +19,6 @@ enable getty@.service
enable systemd-timesyncd.service
enable systemd-networkd.service
enable systemd-resolved.service
-enable systemd-repart.service
enable systemd-homed.service
enable systemd-userdbd.socket