🚀 go-pugleaf

In article <78934@ut-emx.uucp> dll@ccwf.cc.utexas.edu (Don Loflin) writes:
>>We do our backups by mounting the OS/2 drives on a SCO UNIX machine
>>and running TAR under UNIX.  We found that we had to reduce the buffer
>>sizes to 1024 bytes before it would work.  We didn't need to go as low
>>as 512 bytes.  It's not quick though.  We are hoping to use an OS/2
>>TAR with IBM TCP/IP's rexec or rsh as a better method for the backups.
>
>If you are looking for a TAR to use with the TCP/IP rexec or rsh, get
>the version of Gnu TAR included with the GTAK100.ZOO stuff.  It supports
>long filenames, extended attributes, and comes with a COMPRESS, which it
>can pipe its output through.
>
>The "Other" version of GNU TAR may or may not support EAs, but it does
>support long filenames, I believe.

This sounds great, although preliminary tests have been unable to
redirect the input of OS/2 TCPIP's rsh or rexec.  I try a command
under OS/2 like:

       dir /s \*.* | rsh machine -l user hd

This should display a hex dump of my OS/2 root directory on my OS/2
screen.  It does nothing.  And when I type a whole lot of stuff on the
OS/2 keyboard I get a hex dump of my key presses.  I've tried all the
options on rsh and rexec and nothing allows redirection of the input.
It's most frustrating.  So if that simple example doesn't work, how am
I going to get TAR to work ????

Is this a known bug in IBM's TCPIP ????

-- 
Paul Andrew   PaulA@hal.pec.co.nz    Production Engineering (NZ) Ltd.
Ph. +64 652 8189     (hi mom!)       P.O. Box 308, Marton, New Zealand