From: Robert Heller on
At Thu, 3 Jun 2010 13:34:41 +0000 (UTC) gazelle(a)shell.xmission.com (Kenny McCormack) wrote:

>
> In article <hu7b9b$nl1$1(a)speranza.aioe.org>,
> jellybean stonerfish <stonerfish(a)geocities.com> wrote:
> >On Wed, 02 Jun 2010 09:23:40 -0700, Todd wrote:
> >
> >>>> Speaking of telnet, I remember years ago something called sz and rz.
> >>>> I wonder if they will work over telnet?
> >>>
> >>> 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.

openssh (and most ssh 'packages') include scp and/or sftp, both of which
are file transfer programs. Also ssh can be pipelined with tools that
can transfer or archive files (cat, dd, tar, cpio, etc.).

>
> I've heard that it is possible to wedge some other protocol into telnet
> (e.g., sz/rz) and transfer files that way, but as the goal here seems to
> be extreme simplicity, it seems we probably can't go down that path.

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'.

>

--
Robert Heller -- Get the Deepwoods Software FireFox Toolbar!
Deepwoods Software -- Linux Installation and Administration
http://www.deepsoft.com/ -- Web Hosting, with CGI and Database
heller(a)deepsoft.com -- Contract Programming: C/C++, Tcl/Tk


From: jellybean stonerfish on
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.

This may be a brutish way to do it, but I am a construction worker, and
it still is softer than a hammer.

From: jellybean stonerfish on
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.

From: unruh on
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.

From: unruh on
On 2010-06-03, 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.
>
> 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.


>