From owner-freebsd-questions Mon Apr 7 10:58:48 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA26921 for questions-outgoing; Mon, 7 Apr 1997 10:58:48 -0700 (PDT) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA26915 for ; Mon, 7 Apr 1997 10:58:46 -0700 (PDT) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.5/8.6.12) with SMTP id KAA08681; Mon, 7 Apr 1997 10:58:33 -0700 (PDT) Date: Mon, 7 Apr 1997 10:58:33 -0700 (PDT) From: Doug White X-Sender: dwhite@localhost Reply-To: Doug White To: spork cc: questions@freebsd.org Subject: Re: BIG /usr... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 7 Apr 1997, spork wrote: > I'm sitting at a workstation upgraded from 2.1.7 to 2.2, and /usr is > around 490M... If I recall correctly, it grew about 200-ish megs after > the upgrade. I've poked around for things, but /usr/local is a seperate > partition where I keep stuff that I add myself, and /usr/ports/distfiles > is all cleaned of old tarballs. Is there something in the source tree > that can be blown away? I'm at a loss... Odd hunch, check /usr/tmp. Also, experiment with du and find which directories are your big hogs. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major