Mark Knecht <[email protected]> [10-09-11 20:40]: > On Sat, Sep 11, 2010 at 8:23 AM, <[email protected]> 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
