From: arumble@extro.ucc.su.OZ.AU (Anthony Rumble) Subject: Re: Good comm program? Date: Mon, 20 Jul 1992 08:53:40 GMT
torvalds@klaava.Helsinki.FI (Linus Benedict Torvalds) writes:
>In article <1992Jul17.142447.16334@athena.mit.edu> chchen@stat.fsu.edu writes:
>>
>>3.kermit is good but no rz, sz. I have tried to use them in kermit's
>> command line (! rz) but it seems that rz can not find the com port
>> , just waiting there.
>The way I have rz/sz set up is to get one of the newer versions that
>open "/dev/tty" explicitly in rbsb.c, and change that open to
>"/dev/modem". After that, you can link /dev/modem to whatever device
>you use, and rz/sz will happily use it directly. The normal rz/sz
>behaviour requires the communication program to know about controlling
>terminals, and setting it up correctly for rz/sz.
>Additionally, making /tmp/rzlog and /tmp/szlog (usually symbolic) links
>to /dev/tty means you get the verbose output to the screen: at a kermit
>session I just type "^\ C" to get to the kermit prompt, and then "! rz
>-vv" to receive using zmodem (or "! sz -bvv xxxx" to send). After
>having set up things like the above, I get a nice verbose output (thanks
>to the 'vv' flags) of how far the down/up-load has progressed.
Just comment out the part in the SZ/RZ.c code where it
reopens stderr as /tmp/rzlog
Then it works perfectly..
-- Anthony Rumble aka SmilieZ "Anything is possible.. If there is enuf money in it"