One of the things you need for kernel relink is abot 1G of disk space under /usr/share/relink.
If you dont want to reinstall, check the files /usr/libexec/reorder_kernel and /etc/rc to see how it all works. That'll give you the idea which files are used and where they come from...
In fact, when you extract base during install, it also extracts kernel sources into the right place. You can try to use tar to extract ONLY that... etc.
But reinstall will give you much less trouble. You can use manual upgrade procedure described at openbsd.org. Or some parts of it, if you want to experiment.
Отправлено из Yahoo Почты для Android
вт, 2 авг. 2022 в 17:04 Stuart Henderson<stu.lists@spacehopper.org> написал(-а): On 2022-08-02, Nick Holland <nick@holland-consulting.net> wrote:
> On 7/29/22 7:29 AM, Nicolas wrote:
>> The computer seems to run fine. I don't know if that error message is
>> important.
>
> The message is important in that the kernel re-link process is a
> really cool bit of OpenBSD security, which isn't working for you
> right now. Which leave you still in the position of being much
> more secure than Linux, but still worth fixing. :)
>
> Without this feature working, you are running the exact same kernel
> every time you boot. Like most other OSs...
Also syspatch will not be able to apply kernel patches.
> I'm thinking booting off bsd.rd and "upgrading" the system to the
> same version you are running now would probably fix the problem
> by bringing everything back in sync (I'm assuming you are running
> 7.1-release, if you are running a snapshot, just run "sysupgrade"
> and move to a new snapshot).
Agreed. (and run syspatch again afterwards).
No comments:
Post a Comment