On Fri, Aug 18, 2000 at 08:53:29PM +0200, Sven Burgener wrote > On Fri, Aug 18, 2000 at 10:38:20AM +1200, Dan Griffiths wrote: > > This command will take care of duplicating everything including device > > files and permissions: > > find <source dir> -mount | cpio -dumpv <target dir> > > I have a (bigger) SCSI disk that I want to move my system onto. > (Currently my system lives on a smaller IDE disk) > > I created a /boot, a swap and a / partition on /dev/sda: > > # fdisk -l /dev/sda > Disk /dev/sda: 255 heads, 63 sectors, 131 cylinders > Units = cylinders of 16065 * 512 bytes > > Device Boot Start End Blocks Id System > /dev/sda1 * 1 3 24066 83 Linux > /dev/sda2 4 11 64260 82 Linux swap > /dev/sda3 12 131 963900 83 Linux > > I next mkXX'ed them and mounted /boot and / under the two mount > points /mnt/newboot and /mnt/newslash, respectively. > > After that, I did the command described above to copy over everything. > > Next, I adjusted /mnt/newslash/etc/fstab to reflect the new disk. I > also adjusted lilo.conf accordingly and ran > lilo -C /mnt/newslash/etc/lilo.conf. >
This step may cause you trouble. Unless you used paths like /mnt/newslash/vmlinuz in /mnt/newslash/etc/lilo.conf then lilo will be pointing to your old kernel/other files; this shouldn't be a problem the first time you boot, but you'll need to run lilo again to get things sorted and stable. > Now, I suppose if I boot up next time, this should work just fine, > correct? I can't actually test this right now as I am recompiling a > kernel on a different box that I ssh'ed to from this box... :) > > So, does anyone have any suggestions / comments on this topic? > While many BIOS/SCSI combinations play nicely together, many combinations also have real and sometimes intractable issues over booting. In your position I'd probably make a boot floppy, just in case. John P. -- [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.mdt.net.au/~john Debian Linux admin & support:technical services
