public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: James Broadhead <jamesbroadhead@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Freeing up disk space problem!!
Date: Tue, 28 Feb 2012 16:14:47 +0000	[thread overview]
Message-ID: <CA+hid6H-QCVH49V5Dxgx2b1hnzjUF652GNkqs1HNGRoHa_FjRg@mail.gmail.com> (raw)
In-Reply-To: <CALMtN6wNY5K4350=Sd3UyPsPmnf64tjHpTJsrz+28cgJ2pXyeA@mail.gmail.com>

On 28 February 2012 11:37, trevor donahue <donahue.trevor@gmail.com> wrote:
> 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 ...

Lots of good advice already, but I thought that I'd chime in to
suggest that you use `eclean` to free up space in distfiles, but only
removing downloaded files which aren't going to be used again. This
means that you don't need to re-download if you re-merge, and lightens
server load.

Another obvious suggestion: unless you're on a very constrained
system, consider re-partitioning to give yourself more root space -- I
very happily ran gentoo inside ~7 GiB for a very long time without
needing to shuffle things about. I recently bought one of these and a
16GiB SD card to quickly add space to my HTPC without disassembly (and
warranty-voiding).
http://www.dealextreme.com/p/kawau-world-s-smallest-microsd-transflash-tf-sd-sdhc-usb-2-0-card-reader-keychain-25558



      parent reply	other threads:[~2012-02-28 16:16 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
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 [this message]

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=CA+hid6H-QCVH49V5Dxgx2b1hnzjUF652GNkqs1HNGRoHa_FjRg@mail.gmail.com \
    --to=jamesbroadhead@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