4 ms·
I read about the "sysupgrade" tool and concluded that the upgrade to 6.7 in another 6 months will be awfully seamless... But I see from this that they backporte
by asveikau 7y ago
I read about the "sysupgrade" tool and concluded that the upgrade to 6.7 in another 6 months will be awfully seamless... But I see from this that they backported the tool as a syspatch for 6.5! So from 6.5 we will be able to do syspatch && sysupgrade to get to 6.6. Sounds nice.
- protomyth 7y agoTried on one of my machines. Seems to work fine. You still do the delete file step manually but that's minor. This is going to save a lot of effort on certain machines.
- asveikau 7y agoHow does it handle sysmerge? Do you need to do that after it finishes? Or does it do the merges before reboot? I will play around with it in a few hours.
- brynet 7y agoSome things will get merged automatically by the first run of sysmerge(8) after upgrade, if the machine is remote you should be able to run. $ doas dmesg -s -s ... This can be used to review rc(8) system startup messages. That should tell you if you need to run sysmerge manually, but well, it also doesn't hurt to do that every time anyway.
- kelp 7y agoYou can also do sysupgrade -s to follow current snapshots, and then you get a rolling release OpenBSD without build world.
- snvzz 7y ago>So from 6.5 we will be able to do syspatch && sysupgrade to get to 6.6. Sounds nice. Do note the steps before starting and the config file changes in the release notes need to be run through manually, before sysupgrade. And after the new version boots, pkg_add -u.