On Sun, May 17, 2015, at 08:08 AM, Peter Leber wrote:
> I want to build a test system based on OpenBSD 5.7 which updates
> in an automated fashion.
> The goal is to have a remotely located machine which runs OpenBSD 5.7
> and is constantly updated. While restarting the machine remotely via SSH
> is perfectly fine to me, I do not want to access the machine locally in
> order to interrupt the automatic reboot in order to trigger the manual
> upgrading process. I'm fine with following -stable and -current alike.
> 
> I recognize that there's m:tier's binary patching service 
> (https://stable.mtier.org), but the packages are signed
> by m:tier rather than the OpenBSD project. While following m:tier's
> binary patches is a good compromise to me, it's not a perfect solution.
> I'm perfectly fine with running the -current flavour of OpenBSD feature-
> and stability-wise, but I did not have the success of remotely triggering
> a script, rebooting the machine and have an up and running updated
> machine.
> While I did find the autoinstall(8) feature, which, since 5.7, should be
> able to trigger an automatic upgrade if the file /auto_upgrade.conf is
> present, I did not see an effect in the bootup messages on the virtual
> machine I'm using for testing things out.
> Furthermore, I did find a tool named snap, aiming at making running 
> -current more enjoyable (see https://github.com/qbit/snap), but it does
> also seem to be relying on the user to manually start the upgrading
> process on system reboot, if I got everything correctly.

Author of snap here. It depends, you can have it run things
automatically for you.. or it can just install the sets. By default it
will only install the sets.

It's specifically designed to run with no external dependencies (nothing
needs to be installed from ports) and can be run from cron. If you do
use it via cron don't forget to run sysmerge!

Let me know if you have any questions :D

> 
> Is there someone aware of a procedure which could help me solving my
> problem?
> I thank you very much in advance.
> 
> Peter

Reply via email to