From owner-freebsd-questions@FreeBSD.ORG Sat Aug 14 00:33:16 2004 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 5292E16A4CE for ; Sat, 14 Aug 2004 00:33:16 +0000 (GMT) Received: from sccrmhc12.comcast.net (sccrmhc12.comcast.net [204.127.202.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1059B43D39 for ; Sat, 14 Aug 2004 00:33:16 +0000 (GMT) (envelope-from r1w3h@yahoo.com) Received: from [192.168.1.4] (c-24-18-196-187.client.comcast.net[24.18.196.187]) by comcast.net (sccrmhc12) with ESMTP id <2004081400331501200pgh3pe>; Sat, 14 Aug 2004 00:33:15 +0000 From: Rob Hancock To: "Freebsd-Questions" Date: Fri, 13 Aug 2004 17:29:28 -0700 User-Agent: KMail/1.6.2 MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <200408131729.28284.r1w3h@yahoo.com> Subject: Best way to keep large ports uptodate X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Aug 2004 00:33:16 -0000 Hello everyone, I'm a recent convert from debian based systems. I must say that I am very happy with freebsd so far. Currently I've been using portupgrade to keep all my ports current, and it works great. With very large ports such as KDE/base/libs/etc it takes several hours to compile on my little 600MHz laptop. Is there a way to keep the previously compiled objects around so when I upgrade the next time only the changes have to be recompiled? Or am I better off just waiting until major updates and doing a clean compile then? Also, top isn't showing any percentages as far as user, cpu, nice etc. I remember reading that it is usually caused by world/kernel not being compiled and installed together. However I did just that...rebuilt world, kernel and installed per the handbook. This is with 4.10p2. Only thing I can think of is that I have CPUTYPE as I686 in my custom kernel and as p3 in /etc/make.conf. Should I try changing /etc/make.conf to I686? The computer is a 600MHz p3. -Rob