Joe Zeff joe@zeff.us writes:
In systemd, a service that's disabled won't be directly started at boot, but another service can still start it either at boot or later.
That means that the service is *not* disabled.
To keep a service from being started by systemd under any circumstances, you need to mask it.
And that means that it is disabled.
I think that the idea is to make a distinction between services that are only started when something needs them and services that aren't started at all.
I don't mind this idea. Yet when I disable something, I expect it to be disabled.