Date: Sun, 02 Oct 2011 12:10:07 +0100 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: freebsd-security@freebsd.org Subject: Re: FreeBSD Security Advisory FreeBSD-SA-11:05.unix Message-ID: <4E88468F.2080503@infracaninophile.co.uk> In-Reply-To: <201110020453.WAA24453@lariat.net> References: <201110010410.p914Ap3F001617@chilled.skew.org> <4E86A12E.3070600@FreeBSD.org> <808B16DD-6AC6-438D-B2AE-895C5875EFC5@anduin.net> <CADLo839PqMoo-jTvNOZYdyKmrHfKKFNZq2YTRDr3MbKp45FxEA@mail.gmail.com> <201110020453.WAA24453@lariat.net>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig5A7E62BBF62CA10731E4A0D6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
On 02/10/2011 05:53, Brett Glass wrote:
> Another question. Suppose one has built a custom kernel (as I always
> do). Does FreeBSD-update update the kernel sources such that I can do a=
> simple "make buildkernel installkernel"? Or do I also have to csup my
> kernel sources to some specific tag and rebuild? If so, how do I know
> which tag?
Yes -- freebsd-update will update your system sources. Unless you've
specifically told it not to. In general, if you're using
freebsd-update(8) you shouldn't need to use csup(1) for the system bits,
and vice-versa.
If you are using csup alongside freebsd-update, then just update to the
latest available on whichever RELEASE branch you are tracking. So for
8.2-RELEASE-p3, the tag in your supfile should be RELENG_8_2. But that
really shouldn't be necessary.
Still unsure? The advisory will detail which of the system sources have
been modified and give details of the revision numbers for the files on
all the affected branches. It's easy to just read the files concerned
and compare contents of the $FreeBSD$ tag to what's in the advisory.
Cheers,
Matthew
--=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
--------------enig5A7E62BBF62CA10731E4A0D6
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/
iEYEARECAAYFAk6IRpYACgkQ8Mjk52CukIzOXgCgh4v8dc1+bieTnXRFjQRg/dOv
7NsAnRbiD+Lck7/iZBQ9LVPH/C9YMLfD
=8ouz
-----END PGP SIGNATURE-----
--------------enig5A7E62BBF62CA10731E4A0D6--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4E88468F.2080503>