> I copied the root (/) partition with the new partition at /dev/sdb5
> mounted as /newroot, using
> # cp -ax / /newroot
>
> I checked that /proc, /dev, and /sys are there, and empty. I recall
> there are some other steps necessary.
/dev needs at least the entries console and null, and tty1 for splash
things (I think). You could create them like this:
mknod c 5 1 /dev/console
mknod c 1 3 /dev/null
mknod c 4 1 /dev/tty1
Or copy over your original /dev directory (without the stuff udev added)
from the old system:
mount -o bind / /mnt
cp -a /mnt/dev /newroot/
Wonko
I have done this in the past. I usually boot the CD, make mount points
for old and new, then mount the old and new that I want to copy. Then I
do a cp -av /path/to/old /path/to/new/ and let it copy. This can take
quite a bit of time tho. It seems those little bitty files take the
longest. Maybe omitting the -v option would help on that?
Once you get it copied over, edit your fstab file as needed on the new
side and install the bootloader as well. After that, it usually just works.
Dale
:-) :-)
P. S. Sorry for not including some fancy tarball stuff. ;-)
If it needs to be then sure. I usually move things file wise with cp
then move things physically in the case as well. My OS is always on
hda. The grub config is on hda1 and grub bootloader is on the MBR of
hda as well. So, I don't have to edit grub on mine. I do boot once by
using the edit feature of grub, just to make sure before I move things
physically.
You do have to plan these things tho. Wouldn't hurt to write down on
paper where everything is and don't erase anything until you are sure
your ducks are in a row. Maybe even write notes on the drive with a
post it note.
Dale
:-) :-)
Just restore your latest backup to the new partition, then edit /etc/fstab
to specify the proper layout. Easy - I do it often.
--
Rgds
Peter
A good idea. If for some reason you don't have disk image
backups...grab something like system rescue cd, and partimage the
whole drive and the restore from it...
~daid
Okay, I just can't resist asking this nosy question: Why do you need to
restore from backup "often"?
> Okay, I just can't resist asking this nosy question: Why do you need to
> restore from backup "often"?
I'm going through a transient at the moment, having more-or-less given up on
trying to keep KDE-3 and not being ready for KDE-4 (or vice-versa). I've
been trying a few other distros, and even Gnome (shows what a parlous state
Gentoo's in; I couldn't imagine ever considering Gnome six months ago).
So I've had cause several times to change my disk layout, and although it
consumes time the easy way is to make a backup and then restore to the new
layout.
This is a toy box, after all. If I can't fiddle with it when I feel like it,
what's the point of having it? :-)
On the other hand, I suspect a hardware problem of causing k3b:4 to be
unable to find the CD drives, the BIOS to report 2992MB RAM instead of 4096
and several BIOS settings to have been changed without my knowledge. That's
driving me towards considering replacing the whole system. It's six years
old now so it doesn't owe me anything. In the end I may revert to something
like my original Gentoo layout and stay with it.
--
Rgds
Peter
Maybe not in line with the OP, but I had the same issue last month
with using kde3 and needing to switch. I tried kde4, but my video
card is garbage and I didn't want to tinker to find the reason X was
so slow....
I went for Xfce and have been quite happy. Things run even faster now!
~daid
> I went for Xfce and have been quite happy. Things run even faster
> now!
Yes, I'm just installing it on my home server to replace KDE. Looks
quite usable now, though it wasn't a few years ago when I last tried it.
This desktop might even find itself running Ubuntu. Now there's an
about-face!
--
Rgds
Peter
Marcus