From owner-freebsd-questions@FreeBSD.ORG Thu Aug 28 22:31:49 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8F099AA7 for ; Thu, 28 Aug 2014 22:31:49 +0000 (UTC) Received: from avasout07.plus.net (avasout07.plus.net [84.93.230.235]) by mx1.freebsd.org (Postfix) with ESMTP id 23DB51B37 for ; Thu, 28 Aug 2014 22:31:48 +0000 (UTC) Received: from curlew.milibyte.co.uk ([84.92.153.232]) by avasout07 with smtp id kNXf1o002516WCc01NXg52; Thu, 28 Aug 2014 23:31:40 +0100 X-CM-Score: 0.00 X-CNFS-Analysis: v=2.1 cv=HpH4GijS c=1 sm=1 tr=0 a=lfSX4pPLp9EkufIcToJk/A==:117 a=lfSX4pPLp9EkufIcToJk/A==:17 a=D7rCoLxHAAAA:8 a=0Bzu9jTXAAAA:8 a=OOzCJWdBeL0A:10 a=tCmXSjse0tcA:10 a=ZTb9aqGL9YkA:10 a=8nJEP1OIZ-IA:10 a=q56oFxeYAAAA:8 a=HxDZK998E2Is4rjs28MA:9 a=wPNLvfGTeEIA:10 Received: from curlew.lan ([192.168.1.13]) by curlew.milibyte.co.uk with esmtp (Exim 4.83) (envelope-from ) id 1XN8EE-0001dJ-Bs for freebsd-questions@freebsd.org; Thu, 28 Aug 2014 23:31:39 +0100 From: Mike Clarke To: freebsd-questions@freebsd.org Date: Thu, 28 Aug 2014 23:31:37 +0100 Message-ID: <1516592.A8M2VIF6ck@curlew.lan> User-Agent: KMail/4.12.5 (FreeBSD/9.3-RELEASE; KDE/4.12.5; amd64; ; ) In-Reply-To: <53FF8E28.2010308@hiwaay.net> References: <53FF8675.2070009@hiwaay.net> <53FF8860.8000405@gmail.com> <53FF8E28.2010308@hiwaay.net> MIME-Version: 1.0 X-SA-Exim-Connect-IP: 192.168.1.13 X-SA-Exim-Mail-From: jmc-freebsd2@milibyte.co.uk X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on curlew.lan X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham autolearn_force=no version=3.4.0 Subject: Re: Ports question .... Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="iso-8859-1" X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on curlew.milibyte.co.uk) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Aug 2014 22:31:49 -0000 On Thursday 28 August 2014 15:16:40 William A. Mahaffey III wrote: > I think that is what I am asking .... To be more precise, how often > should I check to see if it is updated, weekly, monthly, other .... > I guess that is the nub of the question .... It's largely down to what's most convenient for you. There's a lot to be said for the "If it ain't broke don't mend it" philosophy. If everything's working fine on your system and you don't need the latest and greatest new feature recently added to one of your ports then there's no real need to keep updating them. If a port has just been updated to fix some freshly discovered security issue then you need to upgrade it ASAP. Running the periodic script from ports-mgmt/portaudit is a good way of being kept up to date with new vulnerabilities affecting ports installed on your system. There could be a delay before a new version of a vulnerable port is available. You can check what the latest revision level of a port is by looking it up at . After running portsnap you can run "pkg version -vIL=" to see a list of which ports have version numbers which differ from the latest. You need to maintain all your ports in a consistent state, upgrading just one port can lead to dependency problems so it's worth using ports-mgmt/portmaster after running portsnap, this can upgrade all affected ports. If you only upgrade your ports when required by security issues then you may find that there are lots of ports with newer versions so, to reduce the workload, you might prefer to upgrade rather more frequently than waiting until a security issue requires it. Sometimes you will need to give some ports individual attention before running a bulk upgrade. Check for this by seeing if any of your ports are mentioned in /usr/ports/UPDATING - you only need to check entries dated later than the last time you did an upgrade and take whatever action is advised there. If you pay attention to /usr/ports/UPDATING then portmaster will usually upgrade all affected ports without problems but sometimes you come across a situation that it can't handle and you might need to deal with the problematic port yourself. -- Mike Clarke