Hi, --- Mark Knecht <markknecht(a)comcast.net> wrote: If it's a one time kind of job, from the machine with the data on it 'scp foo username@machinename:/home/username/destination/' or from remote 'scp username@machinename:/home/username/filename .' will copy to the directory from which you execute the command. If you need to mirror then a .bashrc function in conjunction with a script can help: mirror () { ~/bin/rsync-clients } #!/bin/bash #rsync mirror of daddy:/raid0/studio/clients, do not delete local files which don't exist at the source--daddy:/..., follow links outside the source directory, cp links to local destination directory--do not create link structure or copy to that destination on local--parker.multitrack.us:/mirror/studio/clients/LINK, #kill with ctrl-c, --partial allows resuming of session #remove trailing /clients from destination rsync --rsh=ssh --times --perms --owner --verbose --progress --compress --recursive --stats --partial --copy-links --delete --temp-dir=/mirror/tmp --bwlimit=0 studio@step:/home/studio/clients/mirror/studio Please do experiment with some test data. Despite the description of what that script should do I don't recall whether I changed the flags. ron I don't __________________________________ Do you Yahoo!? Exclusive Video Premiere - Britney Spears http://launch.yahoo.com/promos/britneyspears/

On Wed, Oct 29, 2003 at 07:46:49PM -0800, Mark Knecht wrote: if you don't have NFS support in your kernels and don't want to bother, rsync is easy to install and use. Locally, it might transfer a bit faster if you use it with rsh instead of ssh (you set this with the RSYNC_RSH environment variable as per the rsync manpage). NFS isn't too hard, though. google will find you some tutorials. -- Paul Winkler http://www.slinkp.com Look! Up in the sky! It's MEGABOT PICKLE! (random hero from isometric.spaceninja.com)

Hi, If this is a one-time move, which I suspect it is. Then ftp is by far the easiest way. If there are no ftp-servers running on your machines(this will be self evident when you try to connect from the other machine), they are probably preinstalled, start it via the appropriate /etc/init.d/<script> and then run an ftp client from the other machine. gftp seems to come with many new distributions, plain ftp in a console works also (should always be installed). /Robert torsdagen den 30 oktober 2003 04.46 skrev Mark Knecht:

Mark, On the machine that you want to be the source (as root): edit /etc/exports and add the line: /source_partition destination_system(rw) where source_partition is the file system that you wish to share and destination system is the name of the destination system (as shown in /etc/hosts) or its IP address (192.168.0.whatever). (rw) gives read and write access to the destination system. Then enter the following: chkconfig portmap on chkconfig nfs on /etc/rc.d/init.d/portmap start /etc/rc.d/init.d/nfs start On the destination system (as root): chkconfig portmap on chkconfig nfs on chkconfig amd on /etc/rc.d/init.d/portmap start /etc/rc.d/init.d/nfs start /etc/rc.d/init.d/amd start At this point, if you do: cd /net/source_system ls you should see the source_partition. I'm not sure if chkconfig is available on all systems. It is on RH. On a RH system you can also use "sevice nfs start" instead of "/etc/rc.d/init.d/nfs start". The chkconfig lines make these services start on boot so if you only want to do it once don't do that on either system. amd is the automounter daemon. All of this assumes that you have your network cards configured so that each machine can see the other. It's also handy to have the name and IP address of each machine in the /etc/hosts file. Jan On Wed, 2003-10-29 at 21:46, Mark Knecht wrote: