From: Fernando Meira <fmeira@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] how to control portage space usage
Date: Wed, 10 Aug 2005 00:35:28 +0200 [thread overview]
Message-ID: <a3c2e88b0508091535175dfccc@mail.gmail.com> (raw)
In-Reply-To: <42F91E3E.4000102@planet.nl>
[-- Attachment #1: Type: text/plain, Size: 1687 bytes --]
On 8/9/05, Holly Bostick <motub@planet.nl> wrote:
>
> Fernando Meira schreef:
>
> > I've been looking for comments about this process... and I got a little
> > bit scared.
> > In my case, i have (in order):
> > - /dev/hda1 - 9.8G windows
> > - /dev/hda2 - EXTENDED
> > - /dev/hda5 - 23G share
> > - /dev/hda3 - 512Mb swap
> > - /dev/hda4 - 4.6G gentoo
> >
> > So, am I wrong or is it impossible to merge hda1 and hda4 with hda5 in
> > between?
> > I could rearrange swap and even create /boot, but I wont be able to move
> > (at least at the time being) my share partition.
> > If I'm right, then what are my choices?
>
> Honestly, I'm not quite sure why you feel the driving need to merge
> anything.
>
> *You are a Linux user. You can mount partitions wherever you want.*
Of course... so obvious and I realize it before...
I don't think you can "merge" hda1 and hda4 without setting up LVM, but
> there's no reason that you can't boot from a LiveCD, mount the
> newly-empty hda1 to /mnt/temp, rsync the contents of /usr (or /var, or
> whatever) to that partition, rename the current /var (or /usr, or
> whatever) folder to var(usr).tmp, then edit your fstab to mount hda1 to
> /var.
Ok, so what would be the best way? Since the current partition is quite
limited (4.6G), I would need to "move" (mount) there something that worth
the 10G. Mounting /home and pointing $PORTAGE_TMPDIR and $DISTDIR to that
partition would be a good idea? Or split it into 2 (or 3) smaller parts and
mount there /usr and /var (and /home or other)... this now is just to find a
better way to use the available space.
Thanks for the help.
Fernando.
[-- Attachment #2: Type: text/html, Size: 2275 bytes --]
next prev parent reply other threads:[~2005-08-09 22:42 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
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 [this message]
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=a3c2e88b0508091535175dfccc@mail.gmail.com \
--to=fmeira@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