On Fri, 22 Jul 2022 07:57:13 +0000, nia wrote:
> On Thu, Jul 21, 2022 at 01:45:45PM +0200, Hauke Fath wrote:
>> On 7/16/22 11:49 AM, nia wrote:
>>> The problem is that your NetBSD 9 sandbox identifies as NetBSD 9.99 in
>>> uname, so the check to enable the fix for this problem fails. If you
>>> have a different NetBSD version in a chroot, you need to use
>>> pkgtools/libkver to fix the kernel version.
>>
>> I guess this also applies for a -9 system running a -current kernel?
>
> Yeah, we're lacking a good userland versioning scheme for NetBSD,
> and this is one of the symptoms, unfortunately.
>
> I wonder if the workaround is safe to enable on CURRENT for now,
> to save others running into the same problem.
Well, provided the (newer) kernel has backward compatibility, what
determines the "system version" is really the system headers and
libraries, not the kernel API. So one might want to look at
/etc/release
There's also the output of sys_info, which should give a more fine-grained idea of what's in userland