--NY6JkbSqL3W9mApi
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Mon, Apr 29, 2013 at 04:08:22PM -0600, Brett Glass wrote:
> Please be advised that, when using freebsd-update(8) to install the patch=
for
> this security problem, freebsd-update will move the current kernel to /bo=
ot/kernel.old,
> and install a new GENERIC kernel in /boot/kernel, even if you have built =
a custom
> kernel and created a copy of the GENERIC kernel in /boot/GENERIC.=20
>=20
> The kernel in /boot/GENERIC is NOT updated, nor are the modules in that d=
irectory
> updated. What's more, if you did not build modules for your custom kernel=
, you
> will not get copies of the updated NFS modules.
>=20
> This is probably not the behavior most users who have built custom kernel=
s will
> want or expect. (I would have hoped that the GENERIC kernel, its modules,=
and the
> kernel sources would be updated and that I'd be reminded to rebuild my cu=
stom kernel
> if necessary.)
>=20
This has _always_ been the case with freebsd-update(8).
Glen
--NY6JkbSqL3W9mApi
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (FreeBSD)
iQEcBAEBCAAGBQJRfz57AAoJEFJPDDeguUaj6ZgH/1eBAaIrofVAo304Zr220ADN
KUB2z0ez+qJaxrahu3T89I4F/ZkxCu4FoKWgWiiFPBnOPRZpAfF1lL3NypB7rb+5
Z6m4a9pXmYzOS7LadqKvO3GdVEmRp633k6jf7A1Bb72jIeLiHsi+87gZ995l/NLZ
LphfN8TS77K5tkOXc6AQeq6PnY5Yu8Ap+inxeQaX4REjHirnYMy6q7a5fkfpknlY
TF+pw9PU8eVWJEHWo3/3Z2oDk6ymGFkZQW/Op4yEHvWfItMWihHAH1FYj2dt8quA
D5BWH4FQCfr+8N9w2NO+xRi1/moGEzNHhEKiPiiO/BjYc51Crs/EOiJ0HJQKcEM=
=JyQZ
-----END PGP SIGNATURE-----
--NY6JkbSqL3W9mApi--