From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Freeing up disk space problem!!
Date: Tue, 28 Feb 2012 11:57:59 +0000 [thread overview]
Message-ID: <201202281158.12102.michaelkintzios@gmail.com> (raw)
In-Reply-To: <CALMtN6wNY5K4350=Sd3UyPsPmnf64tjHpTJsrz+28cgJ2pXyeA@mail.gmail.com>
[-- Attachment #1: Type: Text/Plain, Size: 1301 bytes --]
On Tuesday 28 Feb 2012 11:37:44 trevor donahue wrote:
> Hi everyone,
> I'm experiencing a major problem right now. I've been using gentoo for
> several months now and I simply lllooove it!
> So here's the thing. When I use gentoo for a long time, even without
> updating the current pack of installed software (emerge -uD world), I am
> left without disk space... In situations like this I start deleting
> /var/tmp/*, /tmp/*, /usr/portage/distfiles/*, maybe do even a
> revdep-rebuild to fix something, but even then I'm left with no more then
> 100 mb, which obviously is not enough ...
> So this time I googled a bit and I deleted all the /usr/share/doc/ and this
> left me with 2.5 gb of space (wow).
>
> So the questions are ... in cases like this, what should be done? what is
> storing this much space? logs?
Gentoo takes up more space than a conventional binary distro because of
portage and source files in /usr/portage/distfiles.
Look at eclean to help you remove old package files no longer installed.
Also look at logrotate to help you automatically rotate, compress and delete
old(er) log files.
As a matter of good practice I always fit /var/ on a different partition to
guard against logs going overboard and running out of space.
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-02-28 11:59 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 11:37 [gentoo-user] Freeing up disk space problem!! trevor donahue
2012-02-28 11:52 ` Alan McKinnon
2012-02-28 13:37 ` William Kenworthy
2012-02-28 11:57 ` Mick [this message]
2012-02-28 11:59 ` [gentoo-user] " Nikos Chantziaras
2012-02-28 12:24 ` [gentoo-user] " YoYo Siska
2012-02-28 12:50 ` trevor donahue
2012-02-28 13:25 ` Neil Bothwick
2012-02-28 13:01 ` Alex Schuster
2012-02-28 13:27 ` Neil Bothwick
2012-02-28 23:25 ` Alex Schuster
2012-02-29 0:32 ` Neil Bothwick
2012-02-29 1:05 ` Alex Schuster
2012-02-29 6:22 ` Neil Bothwick
2012-02-29 9:29 ` Alan McKinnon
2012-02-29 9:57 ` Neil Bothwick
2012-02-29 10:40 ` Alan McKinnon
2012-02-29 11:08 ` Neil Bothwick
2012-02-29 12:11 ` Alan McKinnon
2012-03-01 0:59 ` Frank Steinmetzger
2012-03-01 9:54 ` Neil Bothwick
2012-02-29 23:59 ` [gentoo-user] " walt
2012-03-01 0:43 ` Pandu Poluan
2012-02-29 0:48 ` [gentoo-user] " Dale
2012-02-29 1:01 ` Alex Schuster
2012-02-29 2:38 ` Dale
2012-02-29 6:17 ` Neil Bothwick
2012-02-29 7:10 ` Dale
2012-02-29 7:49 ` J. Roeleveld
2012-02-29 9:23 ` Alan McKinnon
2012-03-01 1:09 ` Frank Steinmetzger
2012-03-01 8:26 ` Alan McKinnon
2012-02-29 9:53 ` Neil Bothwick
2012-02-29 9:19 ` Alan McKinnon
2012-02-29 14:44 ` Dale
2012-02-29 7:43 ` J. Roeleveld
2012-02-29 13:06 ` Daddy
2012-02-29 14:44 ` Dale
2012-02-28 16:14 ` James Broadhead
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201202281158.12102.michaelkintzios@gmail.com \
--to=michaelkintzios@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox