On Wed, May 16, 2018 at 12:34:57PM +0200, Harald Dunkel wrote:
> Thanx for the patch, but I wonder how I can create a syspatch from
> it?
You can't. The syspatch utility only installs officially signed
syspatches and you don't have the signing key.
> If I patch, build and install stable from source, then my hosts
> are cut off from the syspatch scheme. That would be highly painful.
You don't need to build all of stable. Apply the patch to a stable tree
(it applies from /usr/src/sys) and build a GENERIC.MP kernel as
described in release(8). This will provide you in particular with fixes
for all the errata that we had so far.
However, don't install this kernel with 'make install', but do a simple
cp obj/bsd /bsd.tdb
from the kernel build directory instead. The -stable userland you
already have installed will work just fine with your custom kernel.
Reboot into bsd.tdb and run it for a while to see if this fixes your
crash.
Yes, while you're running this kernel, syspatch will not be available to
you and /bsd.tdb will not be randomized at boot time. But having a
running kernel without syspatch surely is preferable over a crashing
kernel with syspatch :)
Once we know that this patch fixes your problem we will consider whether
it should become a syspatch.
Should such a patch be published, you can then reboot into /bsd which
will hopefully be stable long enough for you to install the desired
syspatches and head back to normal. Until then, you will need to
maintain your own -stable kernel, i.e., recompile whenever an erratum is
published.
