I can think of
- ftp
- nfs
- ssh
- rcp
any other ways? Comments?
NOTE: these two servers are inside LAN, the copying is not over the Internet
|
I can think of
any other ways? Comments? NOTE: these two servers are inside LAN, the copying is not over the Internet |
|||||||||||||
|
|
Two more:
|
|||||
|
|
rsync, it's better if you need to sync every day two remote folders, don't waste bandwith (transfer only changed chunks). |
||||
|
|
|
SMTP. No, seriously: I had a situation ages ago on a badly adminned Sun-centric network where this was the only port that didn't hangup when it received more than 50K or so. So I wrote a script that telnet 25'd tarballs around. It was silly, but it worked. "Maliciously incompetent" was the term my officemate used about the admin. |
||||
|
|
|
Print out the file, then manually type it in on the other computer. Bring a lot of coffee! |
||||
|
I occasionaly use |
|||||
|
|
I find rsync and scp very functional, but not expressive. If you want to express yourself technically, I recommend a combination of However, a true artist would use a protocol like RFC 1159, A Standard for the Transmission of IP Datagrams on Avian Carriers, or perhaps even write their own protocol. |
|||||
|
|
Use ssh. Set up public key authentication, then on the receiving computer do Or you can just use email. |
||||
|
|
|
TFTP. It's more popular nowadays for things like loading firmware on VoIP phones but it was once common for booting headless workstations. |
||||
|
|
|
There's always 'Laplink' over serial or parallel (extra speed for power users!), or am I showing my age here? Oh and some linux's support DLC over SDLC and X.25 too |
||||
|
|
|
Under unix the proper way to copy a file is to create your own protocol and compile a command to carry out the requested function. Any other command that already exists that might perform that function is probably not exactly the way that you'll want it done. An excellent reference about this phenomenon is in this PDF. Enjoy! |
||||
|
|