Re: Security Branches

From: Alexandr Kovalenko (never@nevermind.kiev.ua)
Date: 07/30/02


Date: Tue, 30 Jul 2002 18:46:46 +0300
From: Alexandr Kovalenko <never@nevermind.kiev.ua>
To: William Allmendinger <allmenwf@udmercy.edu>

Hello, William Allmendinger!

On Tue, Jul 30, 2002 at 11:21:12AM -0400, you wrote:

> Please excuse what is possiblly a very easy question. How
> does one find out what the latest security branch is for a
> particular release? In the advisory for reslov, it states to
> upgrade you system to the latest security branch,
> 4.5-RELEASE-p7. How do I find out if this is the latest one
> to upgrade/install from. I can't move to 4.6 yet due to an
> isue with the boot loader and scsi, waiting for 6.1 to see
> if it has a fix. These are production systems and I need
> them as secure and stable as possible. Thanks.
Just track RELENG_4_5 branch.

P.S. Moving to freebsd-questions as it is FAQ.

-- 
NEVE-RIPE
Ukrainian FreeBSD User Group
http://uafug.org.ua/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message


Relevant Pages

  • Security Branches
    ... In the advisory for reslov, ... upgrade you system to the latest security branch, ... These are production systems and I need ...
    (FreeBSD-Security)
  • Re: Security Branches
    ... WA> Please excuse what is possiblly a very easy question. ... WA> upgrade you system to the latest security branch, ... These are production systems and I need ...
    (FreeBSD-Security)
  • Re: Packages available for different FreeBSD versions
    ... Andrew Gould wrote: ... It's reasonable for people who update and build their own software image to do some level of qualification of the result, before deploying this to production systems. ... Whether you track -STABLE or the security branch for your initial release ought to be determined more by your preferences to minimize the scope of OS updates versus your desire for relevant new functionality. ...
    (freebsd-questions)
  • Re: buildworld failed for RELENG_5_1
    ... a known problem with a fix available but not quite applicable ... to the security branch. ... A work around (IIRC) was to upgrade with ...
    (freebsd-stable)