On Sun, Oct 08, 2017 at 05:27:09PM +0200, Sebastian Benoit wrote: > Robert Peichaer(rob...@peichaer.org) on 2017.10.08 09:56:15 +0000: > > Up to now, the upgrade procedure from one to the next release meant > > that you had to manually download and verify the new ramdisk kernel. > > > > What about if you just needed to boot into the existing bsd.rd and > > it would support downloading and verifying the bsd.rd of the next > > release? > > Why put this into the installer and not into a script on the system? > With this, it takes an extra reboot, just to get bsd.rd. > > (In my case the number one mistake i make when upgrading is that i sleep > through the boot> prompt timeout, so this gives me 2 chances ;)). > > Also, you would have to type > > Server directory? [pub/OpenBSD/6.2/amd64] pub/OpenBSD/6.3/amd64 > > by hand. Could this automatically be the next version? > > /B.
You're assuming release-to-release... the more common scenario for most of us is snapshot suddenly bumping keys and version. As far as I'm concerned, I've already rebooted, and suddenly I figure out the bsd.rd on THAT machine does not know the correct key. Being able to grab/verify the new bsd.rd will save me from one reboot to full userland and whatever verification script I have.
