From owner-freebsd-questions@FreeBSD.ORG Mon Feb 8 17:38:50 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 889741065692 for ; Mon, 8 Feb 2010 17:38:50 +0000 (UTC) (envelope-from tundra@tundraware.com) Received: from ozzie.tundraware.com (ozzie.tundraware.com [75.145.138.73]) by mx1.freebsd.org (Postfix) with ESMTP id 420338FC12 for ; Mon, 8 Feb 2010 17:38:49 +0000 (UTC) Received: from [192.168.0.2] (viper.tundraware.com [192.168.0.2]) (authenticated bits=0) by ozzie.tundraware.com (8.14.4/8.14.4) with ESMTP id o18HccjG002348 (version=TLSv1/SSLv3 cipher=DHE-DSS-CAMELLIA256-SHA bits=256 verify=NO) for ; Mon, 8 Feb 2010 11:38:38 -0600 (CST) (envelope-from tundra@tundraware.com) Message-ID: <4B704C2C.2020103@tundraware.com> Date: Mon, 08 Feb 2010 11:38:52 -0600 From: Tim Daneliuk User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1 MIME-Version: 1.0 To: FreeBSD Mailing List X-Enigmail-Version: 1.0.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.3 (ozzie.tundraware.com [75.145.138.73]); Mon, 08 Feb 2010 11:38:39 -0600 (CST) X-TundraWare-MailScanner-Information: Please contact the ISP for more information X-TundraWare-MailScanner-ID: o18HccjG002348 X-TundraWare-MailScanner: Found to be clean X-TundraWare-MailScanner-From: tundra@tundraware.com X-Spam-Status: No Subject: Follow Up Question On Upgrading And Ports 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: Mon, 08 Feb 2010 17:38:50 -0000 My ordinary practice with production FreeBSD machines is to: - Regularly (weekly), update the sources, rebuild and reinstall world and kernels. - Regularly (several times a week), do a 'portupgrade -arR' - Somewhat frequently do a 'pkgdb -F' IOW, I keep the OS, kernels, and ports fairly up-to-date. However, per the thread on the proper updating method a few days ago, I just ran 'make delete-old' and 'make delete-old-libs' for the first time ever. After a reboot the system started grumbling about not being able to find libssl.so.4. I reinstalled the compat5,6,7 ports and all is well again. Running 'make delete-old-libs' seems to no longer want to get rid of libssl.so.4. This leads to my questions: 1) With all the regular portupgrades I do, why is libssl.so.4 even being used any more? Isn't this a relic from the FBSD 4.x branch? 2) Why did the initial 'make delete-old-libs' clobber this file, but after the compat reinstalls, the same command no longer cares? 3) If I do an in-place upgrade to 8.x (I'll probably wait until 8.1) and immediately follow it with a 'portupgrade -arR', will I be guaranteed that every port will be migrated to the very latest 8.x libs? Thanks, -- ---------------------------------------------------------------------------- Tim Daneliuk tundra@tundraware.com PGP Key: http://www.tundraware.com/PGP/