4 ms·
> Man, but have you personally tried to disable it? Sure. It's just a one line change in the configuration file (/etc/apt/apt.conf.d/50unattended-upgrades). Or
by rlpb 1y ago
> Man, but have you personally tried to disable it?
Sure. It's just a one line change in the configuration file (/etc/apt/apt.conf.d/50unattended-upgrades). Or, if you're doing a mass deployment, just don't install the unattended-upgrades package.
> figure out what other dark pattern canonical came up with
The mechanism is inherited from Debian. It isn't Canonical's architecture.
If you want to hack internals to do things in a more complicated way, then that's up to you, but you can't then complain that it's unnecessarily complicated.
- ptsneves 1y ago> Sure. It's just a one line change in the configuration file (/etc/apt/apt.conf.d/50unattended-upgrades). Or, if you're doing a mass deployment, just don't install the unattended-upgrades package. That answer shows you have not seen that pattern fail.When that fails or is overwritten by an update, remember my comment. Ironically you just added another way to configure a simple thing, proving my point.