> On 24 Sep 2020, at 13:52, Sebastien Marie <sema...@online.fr> wrote:
> 
> On Thu, Sep 24, 2020 at 12:47:30PM +0200, Mischa wrote:
>>> 
>>> One quirk of the archive: It just creates a directory every night, no
>>> matter if a snap was built or not, you can check with what(1) if you
>>> actually have a different kernel to the one you already tested.
>> 
>> for i in $(jot -w %02d 15 10); do ftp -o bsd.rd-${i} 
>> https://ftp.hostserver.de/archive/2020-09-${i}-0105/snapshots/amd64/bsd.rd; 
>> done
>> 
>> The build from the 15th is the first showing this issue, the one of the 14th 
>> is fine.
>> 
>> tx# what /bsd.rd-15
>> /bsd.rd-15:
>>        OpenBSD 6.8-beta (RAMDISK_CD) #65: Sun Sep 13 03:09:57 MDT 2020
>>        PD KSH v5.2.14 99/07/13.2
>>        $OpenBSD: cert.pem,v 1.21 2020/06/01 18:53:53 sthen Exp $
>> 
> 
> Could you provide the what /bsd.rd-14 too ?
> 
> Downloading 
> https://ftp.hostserver.de/archive/2020-09-14-0105/snapshots/amd64/bsd.rd
> and https://ftp.hostserver.de/archive/2020-09-15-0105/snapshots/amd64/bsd.rd 
> , I have
> the same file.
> 
> $ sha256 -b bsd.rd-14 bsd.rd-15
> SHA256 (bsd.rd-14) = wfNVV8gKxUP8gJvozr73T2bbz2uuKCX7p7JeS3kmTj8=
> SHA256 (bsd.rd-15) = wfNVV8gKxUP8gJvozr73T2bbz2uuKCX7p7JeS3kmTj8=
> 
> Is it is the same on your side too ? if yes, it means hypervisor
> doesn't have constant behaviour.

I upgraded my -current host to the latest release and created two VMs, one 
running 6.7-stable and one 6.8-current.
Rebooted each VM in bsd.rd around 10 times and on 6.8 I don’t see this 
happening at all.

On 6.7 I indeed see inconsistent behaviour, but never showed itself as obvious 
then the last couple of weeks.
It is happening with both 6.7 as well as 6.8 bsd.rd, I needed to try more times 
to see this happening.

Somewhere in between 6.7 -> 6.8 it seems this issue has been addressed.

Thank you all for sharing your insights and help.
Will keep this host running -current for the foreseeable future, if anybody 
needs a VM for testing/breaking let me know.

Mischa

PS: I love the fact ctrl-l is working in ksh vi mode! Thank you for doing that!

Reply via email to