> 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.
oh you want a script #!/bin/sh ftp -o /bsd.rd https://ftp.openbsd.org/pub/OpenBSD/6.3/amd64/bsd.rd but oh, signature check against what signature +1 is easy. more than +1 is difficult. The proposed diff is trying to solve 3 different problems. 1. you have booted into an old bsd.rd, and discover it is useless for doing the upgrade. an old bsd.rd does not know exactly how to install sets from a future release. 2. might as well use that bsd.rd to install newer bsd.rd, right? 3. but by default, it installs /bsd also, which could be a hazard in case the upgrade sequence gets aborted. that new /bsd may be ABI incompatible. so rpe's diff skips /bsd 4. if only going +1 release, it is possible to perform a signature check, more than that isn't easy. What is happening here doesn't block the writing of a script. I've seen talk of such a script, but I haven't seen one. Perhaps because >+1 isn't so easy.
