I’ve just released Endless OS 6.0.10. It includes:
RPi Kernel
Introduce new EOS OSTree branch for Raspberry Pi 4B/400 & 5/500/500+. To have better hardware support, it includes Raspberry Pi Linux kernel, instead of the common EOS Linux kernel. This change only effects the new RPi system installation. The original deployment keeps as it is.
I don’t know if you remember the problem I had with version 6.0.9. Unfortunately, 6.0.10 seems to have the same flaw. I solved it by doing a rollback using the pkexec eos-rollback command. Unfortunately, however, despite turning off automatic updates, Endless continues to revert the boot systems, so I always find myself having to reissue the above command every 2-3 boots. So I ask: is there a way to avoid this? Thanks for your help.
There are, regrettably, two automatic update mechanisms which I don’t think are linked. Which did you turn off?
App Center has a toggle for automatic updates, which affects both automatic app updates (which it is solely responsible for) and also OS updates driven by the app center itself.
There is a system service, eos-autoupdater.service, which runs on a timer, eos-autoupdater.timer. This runs regardless of the setting in App Center
If you really want to be sure that no OS updates run at all, run this command:
systemctl mask --now eos-updater.service
This will completely disable the OS updater. You can reënable it later with:
systemctl unmask --now eos-updater.service
If you want a more subtle option, you can instead:
Disable automatic updates in the App Center GUI
Configure eos-autoupdater to poll for OS updates but not download or apply them, with the following command:
sed -e 's/LastAutomaticStep=./LastAutomaticStep=1/' \
/usr/share/eos-updater/eos-autoupdater.conf \
| sudo tee /etc/eos-updater/eos-autoupdater.conf
This copies the default config file from /usr/share/eos-updater/eos-autoupdater.conf to /etc/eos-updater/eos-autoupdater.conf, changing the LastAutomaticStep line from the default 3 (poll, fetch and apply OS updates to 1 (poll for updates but neither fetch nor apply them).
Thank you very much for your comprehensive reply. The solution of allowing users to search for updates but leaving the decision to install them up to them is very interesting. I think this behavior could be managed more easily by adding the option in the appropriate section of the Endless configuration.