<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
The rule is if the patch is affecting files in the sys/-dir only, a
build-kernel.sh will do, if any thing else you will have to do a
build-release.sh. However, flashboot only contains a subset of the
OpenBSD distribution, so as Yannick said, read up on if you need to
apply the patch before you put the effort into upgrading your system.<br>
<br>
Regards, Rickard.<br>
<br>
Yannick Gravel wrote:
<blockquote cite="mid:4790B03B.3060408@ygunit.net" type="cite">
<pre wrap="">Russel,
It depands...
For OpenBSD 4.2, errata 004 and 005 are for the kernel, so
build-kernel.sh is sufficient there but for the errata 001 and 002 that
are in user-space, you need to do the build-release.sh before. So with
that in mind, for the next errata, have a look at the patch, you'll
figure out what need to be done.
Cheers
Y.
Russell Sutherland wrote:
</pre>
<blockquote type="cite">
<pre wrap="">When a new patch is released, is it necessary to do a
"build-release.sh" operation?
Or is a patch followed by a "build-kernel.sh" sufficient?
</pre>
</blockquote>
<pre wrap=""><!---->
_______________________________________________
flashboot mailing list
<a class="moz-txt-link-abbreviated" href="mailto:flashboot@mindrot.org">flashboot@mindrot.org</a>
<a class="moz-txt-link-freetext" href="https://lists.mindrot.org/mailman/listinfo/flashboot">https://lists.mindrot.org/mailman/listinfo/flashboot</a>
</pre>
</blockquote>
</body>
</html>