Date: Fri, 18 Nov 2011 20:50:14 +0000 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: freebsd-questions@freebsd.org Subject: Re: 8.2-RELEASE-p4 Message-ID: <4EC6C506.2090206@infracaninophile.co.uk> In-Reply-To: <4EC6BC2F.5030907@bio.umass.edu> References: <005301cca2b7$add11f20$09735d60$@co.ke> <4EC13877.3070704@bio.umass.edu> <4EC6BC2F.5030907@bio.umass.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig925EE7951DDE7CC4A57D16BF
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
On 18/11/2011 20:12, Tom Carpenter wrote:
> Is it not possible/not intended for kernels to be updated via
> freebsd-update? If kernels can be updated via freebsd-update
> will there be a release of an fix/update that will allow systems
> to be patched/updated to -p4 or later?
freebsd-update will certainly update your kernel for you, so long as you
are using a standard GENERIC kernel from the install media or from a
previous freebsd-update iteration.
If you compile your own kernel, then freebsd-update will patch the
kernel sources, but leave you to rebuild and reinstall your customized
kernel.
I don't know about the -p4 update. By rights it should have involved
updating the kernel by one or other of the two methods shown. So far
however, we've seen two reports questioning that[*] and none saying that
the -p4 update did in fact update the kernel. Which is suspicious, but
hardly conclusive.
Cheers,
Matthew
[*] Stranger things have happened than admins compiling their own
GENERIC kernels and then mistakenly thinking they were actually using
the standard one from the install media[+]. Seeing a positive "it
updated for me" would settle the question definitively.
[+] Not that I believe for one minute that anyone in this thread is
sufferring from that sort of memory lapse.
--=20
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
JID: matthew@infracaninophile.co.uk Kent, CT11 9PW
--------------enig925EE7951DDE7CC4A57D16BF
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.16 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk7GxQ0ACgkQ8Mjk52CukIyzkQCbBpRlWiPUR/AqRURmfrqBX9fM
vaUAoICcsPYIZ5GUZr9MBimxVv5s4w1x
=xINs
-----END PGP SIGNATURE-----
--------------enig925EE7951DDE7CC4A57D16BF--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4EC6C506.2090206>