How do I tar to another computer?
in [General Linux]
|
From: The Natural Philosopher on 3 Jun 2010 18:43 John Hasler wrote: > The Natural Philosopher writes: >> Not binary, no. > > He should have uuencode. well as long as he has a compiler, all things are possible. I dint think even typing in an TFTP client source code is THAT big a job. For example.
From: jellybean stonerfish on 3 Jun 2010 19:08 On Thu, 03 Jun 2010 16:31:10 +0000, unruh wrote: >> 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. >> >> This may be a brutish way to do it, but I am a construction worker, and >> it still is softer than a hammer. > > Yee gads. Imagine doing this for 10000 files with most being binary > files, with potential file corruption problems. It is like using a > nailfile to tear down an office block. Duh, you give it a path to the directory of the files you want to save, you don't do it for each file. It probably doesn't matter, as (if Robert Heller is correct) telnet doesn't work that way.
From: jellybean stonerfish on 3 Jun 2010 19:22 On Thu, 03 Jun 2010 12:43:19 -0500, Robert Heller wrote: >> 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. As I said I don't have a telnet server up to test it. What does telnet do? On wikipedia I read "Most often, a user will be telnetting to a Unix- like server system or a network device such as a router and obtain a login prompt to a command line text interface" I interpret that as "you telnet in and get a command prompt." Is that wrong? If you do get a command prompt, then how come you can't tar to standard output and save it? What am I missing? Maybe something to do with \377 or the NULL after CR ?
From: The Natural Philosopher on 3 Jun 2010 20:29 jellybean stonerfish wrote: > On Thu, 03 Jun 2010 12:43:19 -0500, Robert Heller wrote: > >>> 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. > > As I said I don't have a telnet server up to test it. What does telnet > do? On wikipedia I read "Most often, a user will be telnetting to a Unix- > like server system or a network device such as a router and obtain a > login prompt to a command line text interface" I interpret that as "you > telnet in and get a command prompt." Is that wrong? > > If you do get a command prompt, then how come you can't tar to standard > output and save it? > > What am I missing? > > Maybe something to do with \377 or the NULL after CR ? > > > the fact that telnet is a (vt100, 7 bit?) terminal emulator, not a raw binary transfer medium. > >
From: Robert Heller on 3 Jun 2010 20:45
At Thu, 3 Jun 2010 23:22:51 +0000 (UTC) jellybean stonerfish <stonerfish(a)geocities.com> wrote: > > On Thu, 03 Jun 2010 12:43:19 -0500, Robert Heller wrote: > > >> 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. > > As I said I don't have a telnet server up to test it. What does telnet > do? On wikipedia I read "Most often, a user will be telnetting to a Unix- > like server system or a network device such as a router and obtain a > login prompt to a command line text interface" I interpret that as "you > telnet in and get a command prompt." Is that wrong? No. > > If you do get a command prompt, then how come you can't tar to standard > output and save it? Save it where? If you redirect telnet's stdout, you get not only the tar output dumped to stdout, but the whole rest of the session's stdout, including the login prompts and shell I/O. And you have to login in 'Stevie Wonder' mode (eg blind). You can't pass the login info and shell command(s) on telnet's command line, nor suppress the shell and login output to stdout/stderr. You end up with a mess. Telnet is like slogin. What you would want is rsh (which is like ssh). Normally, rshd, like telnetd is NOT installed on modern UNIX/Linux systems, since it is a horrible security risk (plain text passwords!). Ssh and slogin have pretty much replaced rsh and telnet. The OP's old, old machine does not openssh installed. It might actually have rsh installed, but it would actually be easier to just use ftp, not because it is more secure, but because it might be easier to install and setup a ftp deamon on the target system. (There is a small possiblity that there is a ftp deamon running on the old box, which would make things even easier.) > > What am I missing? > > Maybe something to do with \377 or the NULL after CR ? No, see above. > > > > > > -- 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/ |