From owner-freebsd-questions@FreeBSD.ORG Thu Feb 9 01:51:02 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DB3F216A420 for ; Thu, 9 Feb 2006 01:51:02 +0000 (GMT) (envelope-from chris@chrismaness.com) Received: from ns1.internetinsite.com (ns1.internetinsite.com [208.179.97.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9121D43D46 for ; Thu, 9 Feb 2006 01:51:02 +0000 (GMT) (envelope-from chris@chrismaness.com) Received: from [192.168.4.2] (68-190-198-174.dhcp.ccmn.ca.charter.com [68.190.198.174]) by ns1.internetinsite.com (8.13.4/8.13.4) with ESMTP id k191p1uw011343; Wed, 8 Feb 2006 17:51:02 -0800 (PST) (envelope-from chris@chrismaness.com) Message-ID: <43EAA005.8080101@chrismaness.com> Date: Wed, 08 Feb 2006 17:51:01 -0800 From: Chris Maness User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kris Kennaway References: <43EA9782.7060708@chrismaness.com> <20060209014116.GA63776@xor.obsecurity.org> In-Reply-To: <20060209014116.GA63776@xor.obsecurity.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: Tracking Security in Ports and Base System X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Feb 2006 01:51:03 -0000 Kris Kennaway wrote: >On Wed, Feb 08, 2006 at 05:14:42PM -0800, Chris Maness wrote: > > >>Newbie question: >> >>How should I set up cvsup to just track security updates for ports. >> >> > >You can't, but you can track the entire thing and use portaudit to >identify ports in need of security upgrade. > >Kris > How would I keep from upgrading EVERYTHING when I track the whole tree. I just fixed a FreeBSD equivalent of DLL hell when I synced the tree. I now understand portupgrade -r so I can probably avoid that nasty expireience again. This is a production server, and I don't want to hose it up. Thanks for the Help Chris Maness