On 07/11/2021 08:44, Sebastien Marie wrote:
You didn't need to remove the previous;
you could have just updated the source you had.
running cvs update (with -r OPENBSD_7_0) is a possibility, but
removing files and reinstall is another. Nothing wrong here.

Actually I did try a CVS update first, before nuking/reinstalling. That's when I first saw the error, so I kinda started over.


for the errata; still fine.
For errate to 7.0? If you have a -current system for sysupgrade
and only updated to the 7.0 errata, the source you have in /usr/src
is behind what you have installed.
sysupgrade (when used without specific options) is used to upgrade a
system from one release to next release.

If you are on 6.9 (-release or -stable) and run `doas sysupgrade', you
will get a 7.0 system (and not -current).


That's what I'd expect, and I did indeed run sysupgrade without specific options. Nonetheless I seem to have wound up with -current when I would have expected -stable:

# dmesg | grep OpenBSD
OpenBSD 6.9-stable (GENERIC.MP) #0: Mon Aug 23 21:44:18 BST 2021
OpenBSD 6.9-stable (GENERIC.MP) #0: Sun Oct 31 10:03:46 GMT 2021
OpenBSD 6.9-stable (GENERIC.MP) #0: Sun Oct 31 10:03:46 GMT 2021
OpenBSD 7.0-current (RAMDISK_CD) #71: Fri Nov  5 10:13:26 MDT 2021
OpenBSD 7.0-current (GENERIC.MP) #72: Fri Nov  5 10:08:43 MDT 2021
OpenBSD 7.0-stable (GENERIC.MP) #0: Sat Nov  6 13:30:45 GMT 2021
OpenBSD 7.0-stable (GENERIC.MP) #0: Sat Nov  6 16:15:08 GMT 2021
OpenBSD 7.0-stable (GENERIC.MP) #0: Sat Nov  6 19:53:47 GMT 2021

I have no idea how this can have happened. I would dearly love to understand what I did wrong.

(The last 3 lines are, presumably, because I rebuilt the kernel after re-installing the source. But I now have a mismatch. Maybe my best bet is to stay with -current on this machine.)

Thanks for your responses.

Steve

--

--------------------------------------------------
          Steve Fairhead
fivetrees ltd - for the complete music service
   www: http://www.fivetrees.com
--------------------------------------------------

Reply via email to