OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
From: Kevin Kinsey, DaleCo, S.P. (kdkdaleco.biz)
Date: Tue Jul 02 2002 - 18:00:25 CDT

  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

    ----- Original Message -----
    From: "Wincent Colaiuta" <wincentcolaiutamac.com>
    To: <freebsd-securityFreeBSD.ORG>
    Sent: Tuesday, July 02, 2002 12:22 PM
    Subject: Re: security fixes

    El Tuesday, 2 July, 2002, a las 05:37 AM, Kevin Kinsey, DaleCo, S.P.
    escribió:

    > Some people read the warning about -STABLE in
    > the Handbook (that I quoted earlier) and decide only
    > to run -RELEASE and patch security fixes, and
    > there is a cvs tag for this, called RELENG_4_x.
    > This is where a little confusion comes in, because
    > after a while they quit patching the older releases.

    ]So on production systems track RELENG_4_6 now, and when that stops being
    ]updated, start tracking RELENG_4_7, and so on.... I can't see any
    ]problems with that. That way you're tracking the security fixes and
    ]critical patches, and then when you need to you're upgrading your entire
    ]system in safe way.
    ]
    ]I think the advice to not track STABLE on production machines is good.
    ]Sure, STABLE is mostly exactly that: STABLE. But there are always going
    ]to be exceptions... The last thing you want is a machine that won't boot
    ]after something went wrong and you have to pay $$$ to get access to the
    ]datacentre and rescue the machine...
    ]
    ]Cheers
    ]Wincent

    Nothing wrong with your advice either. Although in my world, if
    anyone's server quits responding, I've got a red carpet straight to the box
    as soon as I can get there...

    I'm in the 'small' world, though; to each his own....<OT>Wincent, are
    you in anyway related to a famous drummer? </OT>

    Kevin Kinsey

    To Unsubscribe: send mail to majordomoFreeBSD.org
    with "unsubscribe freebsd-security" in the body of the message