From owner-freebsd-questions  Mon Apr  7 09:49:56 1997
Return-Path: <owner-questions>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id JAA22811
          for questions-outgoing; Mon, 7 Apr 1997 09:49:56 -0700 (PDT)
Received: from super-g.inch.com (super-g.com [204.178.32.161])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA22805
          for <questions@freebsd.org>; Mon, 7 Apr 1997 09:49:52 -0700 (PDT)
Received: from localhost (spork@localhost) by super-g.inch.com (8.8.5/8.6.9) with SMTP id MAA27590 for <questions@freebsd.org>; Mon, 7 Apr 1997 12:59:17 -0400 (EDT)
Date: Mon, 7 Apr 1997 12:59:17 -0400 (EDT)
From: spork <spork@super-g.com>
X-Sender: spork@super-g.inch.com
To: questions@freebsd.org
Subject: BIG /usr...
Message-ID: <Pine.BSF.3.95.970407125642.27420B-100000@super-g.inch.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

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...

Charles