How do I tar to another computer?
in [General Linux]
|
From: John Hasler on 3 Jun 2010 13:15 unruh writes: > Yee gads. Imagine doing this for 10000 files with most being binary > files, with potential file corruption problems. Imagine taking an hour to write a script to do it, including error-checking and retries. > It is like using a nailfile to tear down an office block. If it's what you've got it's what you've got. There have been hints that he may have ftp but since he won't tell us what is installed on the machine we must assume he has only telnet. -- John Hasler jhasler(a)newsguy.com Dancing Horse Hill Elmwood, WI USA
From: Robert Heller on 3 Jun 2010 13:43 At Thu, 3 Jun 2010 15:02:50 +0000 (UTC) jellybean stonerfish <stonerfish(a)geocities.com> wrote: > > On Thu, 03 Jun 2010 09:29:57 -0500, Robert Heller wrote: > > > Yes. FTP should be entirely suffiecent. Since tar is also said to be > > available on the old box, the OP actually has all he needs. These two > > alone should be all the OP needs. He will need to install a ftp server > > on the new CentOS box: 'yum install vsftpd' will do that. Then he needs > > to do some configuration of vsftpd to allow incoming non-anonymous ftp > > with write ability. He will then be 'golden'. > > > > > > If his old box has ftp > I figured it did not, as that should have been an obvious solution. ftp, like tar is quite old -- almost any UNIX system from the stone age should have at least a basic version of tar and a basic ftp client. If so (and this is very likely), then the op just needs to do: tar archive.tar files-and-directories-he-needs-tranfered ftp newbox (login as a user on the newbox, making sure vsftpd is running and is setup to allow said user.) ftp> put archive.tar ftp> quit I'm assuming that the two machines are on some (private) LAN. If this must go over the pubic Internet, the OP should create a disposable (unprivilaged!) account on the newbox, and once the files have been transfered, disable that account and close up (or shutdown) vsftpd. > > -- Robert Heller -- 978-544-6933 Deepwoods Software -- Download the Model Railroad System http://www.deepsoft.com/ -- Binaries for Linux and MS-Windows heller(a)deepsoft.com -- http://www.deepsoft.com/ModelRailroadSystem/
From: Robert Heller on 3 Jun 2010 13:43 At Thu, 3 Jun 2010 14:59:54 +0000 (UTC) jellybean stonerfish <stonerfish(a)geocities.com> wrote: > > On Thu, 03 Jun 2010 13:34:41 +0000, Kenny McCormack wrote: > > >>>> tar should work over telnet > >>>> > >>>> > >>> Sounds perfect. How do I pipe (if that is the correct term) a tar > >>> ball over a telnet session? > >> > >>I don't have a telnet server up to connect to, so I cant test it, and > >>never have, but I thought telnet allowed you to log on and get a command > >>line interface to the system. Can you telnet in, and get a command > >>line, or am I totally confused. > >> > >> > > telnet does not have any built-in automatic way to transfer files. Nor, > > in fact, does ssh - but that is another thread. > > With ssh I can do this from boxA: > ssh someone(a)boxB | tee saveit > After I get connected to boxB, in the remote shell, I could do: > cat somefile > exit > Then back on boxA I will have a file, saveit, containing somefile. > saveit may need to be edited to remove the motd and PS1 that the remote > shell would add. I wouldn't do this myself, as I know how to use scp, > but I have done it, just to see it work. > > I assume, (maybe a bad thing) that from the new box the OP could do: > telnet remotebox | tee saveit > And in the telnet sessiion on the remote box execute: > tar --create --file - path > exit > Then fix the file saveit on the new box. No, telnet does not work that way. > > This may be a brutish way to do it, but I am a construction worker, and > it still is softer than a hammer. > > -- Robert Heller -- 978-544-6933 Deepwoods Software -- Download the Model Railroad System http://www.deepsoft.com/ -- Binaries for Linux and MS-Windows heller(a)deepsoft.com -- http://www.deepsoft.com/ModelRailroadSystem/
From: AZ Nomad on 3 Jun 2010 14:23 On Thu, 03 Jun 2010 16:27:39 GMT, unruh <unruh(a)wormhole.physics.ubc.ca> wrote: >On 2010-06-03, Pascal Hambourg <boite-a-spam(a)plouf.fr.eu.org> wrote: >> unruh a ?crit : >>> >>> ftp is fine. >>> The problem is that you do not know that the transfer went OK as ftp >>> does not checking. >> >> md5sum on each end comes in handy. >It does, but running md5sum on 10000 files manually is way worse than >having it done automatically by rsync. you only have to md5sum the tar file.
From: Todd on 3 Jun 2010 16:08
On 06/02/2010 09:45 AM, General Schvantzkoph wrote: > On Wed, 02 Jun 2010 09:22:22 -0700, Todd wrote: > >> On 06/02/2010 05:18 AM, Kenny McCormack wrote: >> >>> netcat is all you need! >>> >>> >> The computer is *ancient*. I can not tell how anything gets on or off >> of it. I just cn not take a modem compiles piece of software and >> install it on the dinosaur. > > I thought you said that you have FTP on the system, if you do then that's > your simplest solution. I've never heard of a *nix system that didn't > have the basic command line FTP client on it. I said I *thought it did*. Watch the weasel words. I will have to check. The thing only has a 10 GB hard drive. A lot of the stuff we are use to are missing. |