Raimundas wrote: > Some remarks on this: > 1) Do not try to copy /proc - this is the directory which is being > created while the system is runing. Just create it with > mkdir proc > 2) Do not copy /mnt directory directly - thie way you will get to a > closed cyscle - will try to copy thea;ready copied content > to itself (e.g. /mnt/<newdisk> to /mnt/<newdisk>/mnt/<newdisk>) - you do > not need that for sure. > 3) You can ommit copying such directory as /temp and other temporary > directories... Why waste time and > space - you'll get lots of this temporary stuff later. > All the rest will be fine. Jus DO NOT forget to install lilo or grub > properly to the disk with the copied content > before disconnecting the old disk.
Thanks Raymund, I clearly left out some details that people might wonder about. I think the cp command I gave should work fine for these reasons: 1) When proc gets mounted I believe that the kernel masks whatever is currently in that directory, which is usually empty. someone please correct me if I am wrong about this. In this case the copied data would basically become disk slack, but nothing noticeable. 2) I should've mentioned that the user ensure that all mounted devices in /mnt be unmounted first, except for the disk being copied to, of course. the cp tool is smart enough to not get caught in any recursive copy loops, and will safely ignore /mnt/<<newdisk>> when it comes across it, since /mnt/<<newdisk>> is also the destination. 3) some systems clean out /tmp regularly so it isn't necessary that you do this manually. Dave _______________________________________________ clug-talk mailing list [EMAIL PROTECTED] http://clug.ca/mailman/listinfo/clug-talk_clug.ca
