Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 26 May 2004 13:43:57 +0100
From:      Colin Percival <colin.percival@wadham.ox.ac.uk>
To:        "Petr Holub" <hopet@ics.muni.cz>
Cc:        cperciva@daemonology.net
Subject:   RE: FreeBSD Port: freebsd-update-1.5
Message-ID:  <6.1.0.6.1.20040526133755.03ad0258@popserver.sfu.ca>
In-Reply-To: <0b1401c4431d$dbefe0a0$2603fb93@KLOBOUCEK>
References:  <6.1.0.6.1.20040526131102.03c3e0f0@popserver.sfu.ca> <0b1401c4431d$dbefe0a0$2603fb93@KLOBOUCEK>

next in thread | previous in thread | raw e-mail | index | archive | help
At 13:34 26/05/2004, Petr Holub wrote:
>> (Systems running FreeBSD 5.2-* are upgraded
>> in two steps -- first to FreeBSD 5.2.1-RELEASE, and then to
>> include all the more recent fixes.)
>
>-su-2.05b# uname -a
>FreeBSD xxxx.xxxx.xxxx.cz 5.2-RELEASE FreeBSD 5.2-RELEASE #9: Thu Feb 12
                           ^^^^^^^^^^^
>The following files are affected by security
>fixes, but have not been updated because they
>have been modified locally:
>
>/boot/kernel/kernel
 ^^^^^^^^^^^^^^^^^^^

  As long as you continue to run a 5.2-RELEASE kernel, FreeBSD Update
is just going to try to update your system to 5.2.1-RELEASE.  Run
# freebsd-update --branch crypto fetch
# freebsd-update install
to update your system to 5.2.1-RELEASE, reboot, and then run FreeBSD
Update to get the updates since 5.2.1-RELEASE.
  Or, if you want a non-GENERIC kernel, cvsup and build one with all
the latest RELENG_5_2 kernel security fixes (and a 5.2.1- name).

Colin Percival




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6.1.0.6.1.20040526133755.03ad0258>