cp -r is not a recursive copy. You have to use cp -R.
On Thu, 10 Feb 2000, Ray Olszewski wrote:
> I've written the advice below from memory. Would others please read through
> it and try to catch any details I've forgotten?
>
> At 06:23 PM 2/10/00 -0500, Liz Dunbar wrote:
> >Progress on the new 20GB second disk - partitions work on only the second
> >try, thanks everybody for your clear and patient directions. Now,
> >1. How do I get the website (about 900 pages) that's currently on dev/hda3
> >in /home/webmaster and its many subdirectories (mostly) to the new hdb2
> >intact? Or, can part of the website stay on hda3 and part of it be on hdb2?
>
> It depends a bit on the details, but the following should be one way to do
> it. I assume "work" means the partitions are mountable (have ext2
> filesystems on them).
>
> 0. Temporarily kill the webserver (so there will be no accesses to the
> filesystem while you are doing the next steps.
>
> 1. "mount /dev/hdb2 /mnt" [or any other temporary mountpoint that's free]
>
> 2. "cp -r /home/webmaster/* /mnt/" [ the -r makes it a recursive copy ...
> goes through the subdirectory tree]
>
> 3. "umount /mnt"
>
> 4. "mount /dev/hdb2 /home/webmaster"
>
> 5. Restart the Webserver.
>
> 6. Add a line to /etc/fstab to automount the new partition as part of the
> initialization done at boot time. The line is approximately as follows:
>
> /dev/hdb2 /home/webmaster ext2 defaults 0 1
>
> Make sure it is after any line that mounts something on the mount point
> /home (if your system is set up with a separate /home partition.
>
> Reminder: there is still an inaccessible copy of your Web stuff on the old
> drive, in directory /home/webmaster . The mount has higher priority, so the
> directory will lead to the mounted filesystem, not its old contents. But
> they are there as a backup. Once you are sure all has transferrred well, you
> can remove the old copy by umounting the hdb2 filesystem, cd'ing to the
> directory, and rm'ing the files.
>
> You can divide the Website between old and new locations, but setting it up
> is more complicated, done basically via symlinks.
>
> >2. Do I need to do anything to make the website accessible in the new
> >location with the same URL?
>
> Not if you take this approach. The new drive location will appear in the
> same place in the filesystem.
>
> ------------------------------------"Never tell me the odds!"---
> Ray Olszewski -- Han Solo
> Palo Alto, CA [EMAIL PROTECTED]
> ----------------------------------------------------------------
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
> the body of a message to [EMAIL PROTECTED]
> Please read the FAQ at http://www.linux-learn.org/faqs
>
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.linux-learn.org/faqs
