auto configuration systems

[Tom H]

On Fri, Apr 14, 2017 at 10:47 AM, Ralf Mardorf <silver.bullet at zoho.com> wrote:
> On Fri, 14 Apr 2017 08:25:04 -0400, Tom H wrote:
>>
>> Anyway, whether on Arch or Ubuntu, if a service is installed and not
>> enabled and another depends on it, it'll be auto-started (unless you
>> mask it, but the latter's an extra step).
>
> That is wrong! This only happens for Ubuntu and not for Arch Linux.

The rationale for "systemctl mask ..." as opposed to "systemctl disable
..." is that, with the latter, a service can be disabled but can be
started as a dependency.

This is similar to "/etc/modprobe.conf" and "/etc/modprobe.d/" where:

- if you use "blacklist foo", foo won't be loaded but it can be loaded
manually or as a dependency

- if you use "install bar /bin/true", bar won't be loaded