4 ms·
http://man.openbsd.org/syspatch.8 http://man.openbsd.org/syspatch.8 Thanks for highlighting this. For me, OpenBSD releases needed so few fixes that keeping the
by parfe 9y ago
http://man.openbsd.org/syspatch.8 http://man.openbsd.org/syspatch.8
Thanks for highlighting this. For me, OpenBSD releases needed so few fixes that keeping the system up to date wrapped around, and become more of a hassle to deal with! I'd get an email and have to manually rebuild something. Watching yet another flood of compiler output started feeling like a huge waste of time, despite only happening once every month or two.
For personal use, on debian I set a cron job and forget it. This utility hits the sweet spot to get me running OpenBSD again.
- adamrt 9y agoYou may already be familiar with but just in case: https://wiki.debian.org/UnattendedUpgrades https://wiki.debian.org/UnattendedUpgrades You can specify the types of updates to auto install (ie I use security updates only automatically).
- currysausage 9y agoI keep running into a weird issue where my Debian servers won't shut down ("A start job is running for Unattended Upgrades") when I enable unattended upgrades as described at [1]. It is especially weird since my Debian systems are otherwise pretty bare-bones, yet the issue occurs on several of them. The solutions listed on Stack Exchange [2] seem rather hacky. [1] https://wiki.debian.org/UnattendedUpgrades#automatic_call_via_.2Fetc.2Fapt.2Fapt.conf.d.2F20auto-upgrades https://wiki.debian.org/UnattendedUpgrades#automatic_call_vi... [2] http://unix.stackexchange.com/questions/293804/debian-a-start-job-is-running-for-unattended-upgrades http://unix.stackexchange.com/questions/293804/debian-a-star...
- voltagex_ 9y agoThat's particularly nasty (and an aspect of systemd that I really don't like). I'm not sure this has been reported before / correctly: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837155 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837155 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=719597 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=719597 Maybe give the maintainers a prod with a link to that thread?