Automatic Updates
Usually distros are designed not to automatically update software. This approach makes sense with servers and enterprise workstations. This approach does not make sense with home and non technical users.
Most distros are designed to provide some kind of notification mechanism to inform users of updates. While a notification system is a good start, non technical users lack the skills and knowledge to discern what to do with those notifications other than accept them or ignore them.
Considering that most computer users are familiar with Windows, come from that environment, and that most users are not technically savvy, an auto update mechanism not only makes sense, but is needed. Without automatic updates many users never will update at all. The prospect of learning to review updates is frightening and these users will ignore the problem.
The Microsoft folks have implemented automatic updates in Windows 10. While there is standing to argue that these intentions are not fully noble, the home and non enterprise users do not care. They admit they do not know anything about computers and rather not be bothered by evaluating updates. Automatic updates makes sense to these users.
Most computer users come from a Windows background, or have only used Windows in their work environment where an IT person configures and controls the system, including updates. These users cannot and will not deal with trying to review and evaluate updates.
Most of the time that simple option is unavailable to Linux users. Linux users also have little need to worry about trusting updates. Nothing has ever happened in the Linux ecosystem to justify a need to evaluate updates based on trust. There are no arguable nefarious reasons for updates.
A typical counter argument used by developers against automatic updates is the potential for regressions.
Most non technical users do not follow forums, mail lists, and RSS notifications. Most non technical users are unaware of such help avenues. Most users have no way of knowing whether an update will introduce a regression. That knowledge and skill level does not exist.
Yes, sometimes an update introduces a regression. Recently I ran into a regression in Fedora 22 with systemd. While annoying, the bug is far from destructive.
I do not recall on my systems where a security-only patch caused a regression.
Unlike proprietary operating systems, package updates with Linux distros are trusted and overwhelmingly bug free. Security patches seldom, no, rarely introduce bugs or problems. Ignoring the geek factor, there is no reason that at least security updates cannot be updated automatically.
Tech savvy users and sysadmins can disable automatic updates. Trying to encourage the majority of users to do likewise is like teaching pigs to sing — a waste of developer time and frustrating to the pig. Despite the counter argument, providing an auto update option requires less support from developers and a more secure system for users.
Another counter argument is automatic updates presume unlimited bandwidth. That is a reasonable counter argument, especially with people faced with data caps. Yet the argument holds only for distro release updates, not for common weekly updates that amount to megabytes of data rather than gigabytes required by release updates. Yet even with this counter argument at least security updates should be automated.
There should be an option for automatic updates. No, not a cron job, which requires using a terminal. A simple GUI check box. The default should favor non technical users. Tech savvy users and sysadmins can disable the option in less than five seconds.
A single check box.
Because Linux remains mostly a self-installed operating system, installer apps should include the option to configure automatic updates.
Posted: Category: Usability Tagged: General
Next: Linux Mint Update Notifier
Previous: Yum to Dnf