From owner-freebsd-questions@FreeBSD.ORG Wed Feb 2 15:57:54 2005 Return-Path: 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 1CD0116A4D1 for ; Wed, 2 Feb 2005 15:57:54 +0000 (GMT) Received: from orchid.homeunix.org (avq147.neoplus.adsl.tpnet.pl [83.27.50.147]) by mx1.FreeBSD.org (Postfix) with ESMTP id 85D7C43D49 for ; Wed, 2 Feb 2005 15:57:52 +0000 (GMT) (envelope-from freebsd@orchid.homeunix.org) Received: from [192.168.1.66] (blackacidevil.orchid.homeunix.org [192.168.1.66]) (authenticated bits=0) by orchid.homeunix.org (8.13.1/8.13.1) with ESMTP id j12FvnHV022154 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 2 Feb 2005 16:57:50 +0100 (CET) (envelope-from freebsd@orchid.homeunix.org) Message-ID: <4200F87F.6070205@orchid.homeunix.org> Date: Wed, 02 Feb 2005 16:57:51 +0100 From: Karol Kwiatkowski User-Agent: Mozilla Thunderbird 1.0 (X11/20050114) X-Accept-Language: en-us, en MIME-Version: 1.0 To: saravanan ganapathy References: <20050202144907.18974.qmail@web51709.mail.yahoo.com> In-Reply-To: <20050202144907.18974.qmail@web51709.mail.yahoo.com> X-Enigmail-Version: 0.90.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.81, clamav-milter version 0.81b on orchid.homeunix.org X-Virus-Status: Clean cc: freebsd-questions@freebsd.org Subject: Re: keeping freebsd uptodate - doubt X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd@orchid.homeunix.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Feb 2005 15:57:54 -0000 saravanan ganapathy wrote: > What is the recommended period to update the ports? Someone else should comment on that, but I think updating (cvsup) ports tree once a week should be often enough to track changes and rare enough to not overload mirrors. That applies to single desktop machine, if you're using more machines / servers it's probably better to setup local mirror for that. As for installed ports, I think you should update installed port when: 1. there are security patches available (a must) 2. there is a new version available with new features / better performance / etc (but only if you need/want the new functionality) ad1: You have already installed portaudit which takes care of security warnings. Have a look at daily "security run output" emails. For example, today I got: > [snip] > Checking for a current audit database: > > Database created: Tue Feb 1 02:40:19 CET 2005 > > Checking for packages with security vulnerabilities: > > Affected package: perl-5.8.5 > Type of problem: perl -- File::Path insecure file/directory permissions. > Reference: > [snip] Then I went to http://www.freebsd.org/ports/index.html, saw it has been already updated in ports, fired up cvsup... ad2: When such event occurs (say, new version of KDE) just update ports tree and do a portupgrade. > Is there any announcements for any port update? So > that I can manually update the ports. I think http://www.freshports.org/ or http://www.freebsd.org/ports/index.html could be what you want. > Is portupgrade contains the security patches also? I'm not sure what that means. Portupgrade simply updates a port, it takes all patches provided by port manager, applies them, compile, etc. (in case of building from source). So, if there are any security patches for a port, yes, portupgrade will take care of them. Hope that helps, Karol -- Karol Kwiatkowski