Date: Mon, 7 Apr 1997 14:49:50 -0400 (EDT) From: spork <spork@super-g.com> To: Doug White <dwhite@resnet.uoregon.edu> Cc: questions@freebsd.org Subject: Re: BIG /usr... Message-ID: <Pine.BSF.3.95.970407144907.27615B-100000@super-g.inch.com> In-Reply-To: <Pine.BSF.3.96.970407105803.8644F-100000@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
I just posted another message that points in the right direction, but here's a du output for posterity. /usr/local/ is a different partition... super-g /usr --># du -d1 -k 222767 ./local 11630 ./bin 1915 ./include 73867 ./lib 104 ./libdata 4717 ./libexec 101 ./mdec 3768 ./sbin 31133 ./share 156431 ./src 1666 ./games 107372 ./obj 52329 ./ports 514 ./tmp 1571 ./sup 669886 . On Mon, 7 Apr 1997, Doug White wrote: > 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 >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.95.970407144907.27615B-100000>