From: meino.cramer@gmx.de
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Moving / around...
Date: Sat, 11 Sep 2010 20:47:17 +0200 [thread overview]
Message-ID: <20100911184717.GA5507@solfire> (raw)
In-Reply-To: <AANLkTik-Rik7B57tSAO_CEEisUuTob3P-OmXM7dE+qKj@mail.gmail.com>
Mark Knecht <markknecht@gmail.com> [10-09-11 20:40]:
> On Sat, Sep 11, 2010 at 8:23 AM, <meino.cramer@gmx.de> wrote:
> <SNIP>
> >>
> >> Why not mount /dev/sda10 as root and be done with it.? No need to move anything.
> >
> > ...because data access at the outer partitions are faster than those
> > in the middle...
> >
>
> OK, assuming it's really measurable in real life, but I'll point out
> that you don't necessarily have to 'copy' data from partition to
> partition to achieve that. I've used gparted to first delete what you
> are terming /dev/sda3, then enlarge /dev/sda10 toward the side of the
> drive where you want it, then shrink sda10 when you get it there.
> Takes a lot of time but works for a dummy like me, and no need to mess
> with fstab, etc., because it just remains sda10.
>
> Granted, that simple example assumes there's nothing in the middle. If
> there is then I typically shrink and move it also.
>
> Not an ideal solution, but it works.
>
> But the point remains that you can probably exist with both installs
> on the drive for some _long_ period of time before you ever get around
> to these steps for the sake of performance. Certainly don't get rid of
> the working 32-bit install before you are _completely_ sure the 64-bit
> is working.
>
> - Mark
>
Hi Mark,
sorry, but with gparted & Co, I made some experiences which let me
leave those tools alone. Maybe the problem sits right in front of my
monitor, but...
In my case, there is "something in the middle", thats why it is
/dev/sda3 and /dev/sd10 and not /dev/sda3 and /dev/sd4...
So things getting even more complex and especially complexer
than "cp" and friends...
Is there any "automagical check" whic does some basic checking, to
find the biggest bugs in a fresh 64bit-installation?
(Beside those, which are identical on 32bit and 64bit -- like emerge
and such...) ?
Best regards,
mcc
next prev parent reply other threads:[~2010-09-11 18:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-11 8:13 [gentoo-user] Moving / around meino.cramer
2010-09-11 9:08 ` Alex Schuster
2010-09-11 12:19 ` meino.cramer
2010-09-11 14:53 ` Mark Knecht
2010-09-11 15:23 ` meino.cramer
2010-09-11 16:19 ` Mark Knecht
2010-09-11 18:47 ` meino.cramer [this message]
2010-09-11 21:14 ` Alex Schuster
2010-09-12 2:26 ` meino.cramer
2010-09-12 11:40 ` Alex Schuster
2010-09-11 12:28 ` Neil Bothwick
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=20100911184717.GA5507@solfire \
--to=meino.cramer@gmx.de \
--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