On Mon, Jul 03, 2017 at 01:05:19PM +0300, Kapetanakis Giannis wrote:
> On 03/07/17 12:45, Paul de Weerd wrote:
> > On Mon, Jul 03, 2017 at 11:52:09AM +0300, Kapetanakis Giannis wrote:
> > | Hi,
> > | 
> > | I've got this today after applying Jul 2 snapshot
> > | 
> > | sha256: cannot open /var/db/kernel.SHA256: No such file or directory
> > | sha256: /bsd does not exist in /var/db/kernel.SHA256
> > | 
> > | upgrade was "without the install kernel"
> > | https://www.openbsd.org/faq/upgrade61.html#NoInstKern
> > 
> > That is for moving from 6.0 to 6.1, for 6.1 to current snapshots, you
> > should add a step `sha256 /bsd > /var/db/kernel.SHA256` and reboot
> > (twice!).  See this ( http://marc.info/?t=149807250200002&r=1&w=2 )
> > thread for some more details.
> > 
> > Paul 'WEiRD' de Weerd
> 
> I'm using the upgrade 6.0->6.1 just for the kernel info and untar (copy paste)
> Then I use -current info.
> 
> Could you please add something about it in -current
> https://www.openbsd.org/faq/current.html
> 
> So it should be something like this?
> #part1
> put new kernels
> extract new .tgz
> #part2
> sha256 -h /var/db/kernel.SHA256 /bsd
> cd /usr/share/compile/GENERIC.MP (replace kernel version here)
> make newbsd
> make newinstall
> reboot (once)
> 
> I did #part2 after the upgrade
> ?

This is a dangerous way to do it: you're running the new userland on an
old kernel.  In particular, this approach will very likely spell trouble
for a 6.1 -> 6.2 upgrade. These are among the reasons why I suggest what
I suggested (with two reboots).

The manual upgrade method is generally not recommended and not really a
supported way to run -current. Therefore, I don't think I want to add
something to current.html.

Reply via email to