How do I tar to another computer?
in [General Linux]
|
From: jellybean stonerfish on 7 Jun 2010 02:44 On Sun, 06 Jun 2010 22:10:45 -0700, Todd wrote: >>> $ yum search rsh >>> ... >>> ========================= Matched: rsh ========================= ... >>> rsh-server.i386 : Servers for remote access commands (rsh, rlogin, >>> rcp). >>> >>> Thank you! >>> >>> -T >>> >>> p.s. and when I am done: >>> rpm -e rsh-server >> >> Let us know if it works for your transfer. > > Will do! (I may be a few month before the customer goes with the > quote.) > > -T That will give you time to figure out how to send your tarball over telnet. I set up a server, and connect in with: telnet -l js server | tee saveit After the password, I did: tar -cf - PATH exit Hoping to edit away the garbage from "saveit" leaving the tarball. It didn't work. It locked somewhere in the middle. I also tried piping "tar"'s output through "od" to make it 7bit friendly, but it still stopped about halfway through. Looking at "saveit", it appeared that some of the plain text files in PATH came through before it stopped. I deleted saveit, and uninstalled the telenet server in frustration. Thinking back on it, I should have done more testing before giving up. A couple of questions I will try to answer are "Does telnet have a limit on how much data it can send in one session?" and "Why did my transfer lock?" I probably will reinstall telnetd and try it again. Starting with one small file first, instead of a large direcory. If I get it to work with one file, or more, I will come back here and brag that I can use 40 year old technology.
From: unruh on 7 Jun 2010 14:02 On 2010-06-07, jellybean stonerfish <stonerfish(a)geocities.com> wrote: > On Sun, 06 Jun 2010 22:10:45 -0700, Todd wrote: > >>>> $ yum search rsh >>>> ... >>>> ========================= Matched: rsh ========================= ... >>>> rsh-server.i386 : Servers for remote access commands (rsh, rlogin, >>>> rcp). >>>> >>>> Thank you! >>>> >>>> -T >>>> >>>> p.s. and when I am done: >>>> rpm -e rsh-server >>> >>> Let us know if it works for your transfer. >> >> Will do! (I may be a few month before the customer goes with the >> quote.) >> >> -T > > That will give you time to figure out how to send your tarball over > telnet. > I set up a server, and connect in with: > telnet -l js server | tee saveit > > After the password, I did: > tar -cf - PATH > exit > > Hoping to edit away the garbage from "saveit" leaving the tarball. > It didn't work. It locked somewhere in the middle. I also tried piping > "tar"'s output through "od" to make it 7bit friendly, but it still > stopped about halfway through. Looking at "saveit", it appeared that > some of the plain text files in PATH came through before it stopped. I > deleted saveit, and uninstalled the telenet server in frustration. > Thinking back on it, I should have done more testing before giving up. A > couple of questions I will try to answer are "Does telnet have a limit on > how much data it can send in one session?" and "Why did my transfer > lock?" I probably will reinstall telnetd and try it again. Starting > with one small file first, instead of a large direcory. If I get it to > work with one file, or more, I will come back here and brag that I can > use 40 year old technology. > I have this hammer and this screw and I keep having trouble screwing in the screw with the hammer. telnet is NOT for transfering files. ftp, rcp, rsync are. Use the appropritate tool and quit trying to make something work that was never intended for that job.
From: jellybean stonerfish on 7 Jun 2010 14:54 On Mon, 07 Jun 2010 18:02:59 +0000, unruh wrote: > > I have this hammer and this screw and I keep having trouble screwing in > the screw with the hammer. > > telnet is NOT for transfering files. ftp, rcp, rsync are. Use the > appropritate tool and quit trying to make something work that was never > intended for that job. I am not doing it to transfer files, I am doing it for the fun.
From: Rikishi42 on 8 Jun 2010 13:52 On 2010-06-06, John Hasler <jhasler(a)newsguy.com> wrote: > Rikishi42 writes: >> Or did I miss out on something? > > The machine is running Caldera Linux. That means that it is probably > older than rsync. Got it. :-) -- Any time things appear to be going better, you have overlooked something.
From: unruh on 8 Jun 2010 14:09
On 2010-06-08, Rikishi42 <skunkworks(a)rikishi42.net> wrote: > On 2010-06-06, John Hasler <jhasler(a)newsguy.com> wrote: >> Rikishi42 writes: >>> Or did I miss out on something? >> >> The machine is running Caldera Linux. That means that it is probably >> older than rsync. > > Got it. :-) So? That means he does not have rsync installed already. But he can install it! But he seems singularly unwilling to tell us what IS on that machine. ftp, rcp, Or if necessary, just remove the disk from the old computer, put it into a usb external case and copy the stuff over on the new computer. > > |