From: "Michael Kintzios" <michaelkintzios@lycos.co.uk>
To: <gentoo-user@lists.gentoo.org>
Subject: RE: [gentoo-user] how to control portage space usage
Date: Mon, 8 Aug 2005 14:00:49 +0100 [thread overview]
Message-ID: <F49BE7328A1DA246AFC5C2CDDB86D9170D4790@BCV0X134EXC0005> (raw)
In-Reply-To: <Pine.LNX.4.63.0508081312220.23712@vuosaari.hai.fi>
> -----Original Message-----
> From: Tero Grundstrm [mailto:tero@vuosaari.hai.fi]
> Sent: 08 August 2005 11:21
> To: gentoo-user@lists.gentoo.org
> Subject: RE: [gentoo-user] how to control portage space usage
>
> On Mon, 8 Aug 2005, Michael Kintzios wrote:
>
> >> -----Original Message-----
> >> From: Tero Grundstrm [mailto:tero@vuosaari.hai.fi]
> >> Sent: 08 August 2005 08:46
> >> To: gentoo-user@lists.gentoo.org
> >> Subject: Re: [gentoo-user] how to control portage space usage
> >>
[snip]
> > You could have a separate /usr or /usr/portage partition so
> that when/if
> > it runs out of space, your system continues to run despite
> the emerge
> > coming to a halt.
>
> I don't don't know if this is very practical, atleast without
> a volume
> manager.
>
> Besides, isn't this taken care of by the filesystem already?
> I know that
> ext2/3 preserve a persentage of the partition size for root
> especially for
> these cases.
Well, it has been practical enough for *my* needs. For a while I was
running Gentoo on a small partition and having run aground on a couple
of cases with a seized system during some mammoth emerge, I decided to
set up a separate /usr partition. Thereafter, I was able to recover
future incidents without having to boot the LiveCD. As you say, if
someone is going to alter partition sizes often then LVM is the way to
go. On the other hand if you have a good idea on how big your
/usr/portage is or needs to be then my suggestion is a simple enough
solution.
--
Regards,
Mick
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-08-08 13:09 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-07 21:06 [gentoo-user] how to control portage space usage motub
2005-08-07 21:38 ` Fernando Meira
2005-08-07 22:04 ` Francisco J. A. Ares
2005-08-08 8:03 ` Neil Bothwick
2005-08-08 8:09 ` W.Kenworthy
2005-08-07 22:20 ` Tero Grundstr�m
2005-08-07 22:45 ` Fernando Meira
2005-08-08 7:45 ` Tero Grundstr�m
2005-08-08 9:30 ` Neil Bothwick
2005-08-08 9:44 ` Tero Grundstr�m
2005-08-08 9:53 ` Michael Kintzios
2005-08-08 10:20 ` Tero Grundstr�m
2005-08-08 13:00 ` Michael Kintzios [this message]
2005-08-08 13:13 ` Neil Bothwick
2005-08-08 18:23 ` Fernando Meira
2005-08-08 19:10 ` Neil Bothwick
2005-08-08 18:03 ` Fernando Meira
2005-08-08 10:48 ` Sean Reiser
2005-08-08 18:17 ` Fernando Meira
2005-08-08 18:54 ` Sean Reiser
2005-08-08 19:08 ` Luke Albers
2005-08-09 17:44 ` Fernando Meira
2005-08-09 18:25 ` Sean Reiser
2005-08-09 21:00 ` Fernando Meira
2005-08-09 21:21 ` Holly Bostick
2005-08-09 22:35 ` Fernando Meira
2005-08-08 13:43 ` Richard Fish
2005-08-08 18:34 ` Fernando Meira
-- strict thread matches above, loose matches on Subject: below --
2005-08-07 20:22 Fernando Meira
2005-08-07 20:50 ` Rumen Yotov
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=F49BE7328A1DA246AFC5C2CDDB86D9170D4790@BCV0X134EXC0005 \
--to=michaelkintzios@lycos.co.uk \
--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