paul@vixie.UUCP (06/11/87)
I'm sending this out a second time because I think it got eaten by a neighbor the first time. If you've seen it before, my apologies. In article <6969@mimsy.UUCP> chris@mimsy.UUCP (Chris Torek) writes: >[...] I once borrowed someone else's tip session. I >discovered that ^A acted as a caps-lock, and that one had to type >^P twice to send one. It was obvious that ^P was being used as an >escape character (it *is* DLE, Data Link Escape, after all). I >considered this obnoxious enough that I never used it again. [...] This seems to have been added in 4.3; at least, I never noticed this in the 4.2 version. I was sufficiently disgusted with the ^A and ^P behaviour that I hacked tip to have two new variables: 'set noforce' (or :nf: in the /etc/remote file) means: don't do the ^P stuff, just treat ^P as a normal character 'set noraise' (or :nr: in remote) means: don't do the ^A/CAPSLOCK stuff, normal character, etc. The changes were simple, and I could post diffs. The man page doesn't mention many of the variables in the source, and the man page for remote(5) doesn't mention a different set of things. I thought of updating the man pages, but the task overwhelmed me. I'd like to post the whole thing. Is this BSD-only code? What are the licensing hassles if it is? Obviously if it's ATT-derived, I can only post diffs, but what about BSD-pure stuff? Chris? You answered the last question about BSD policies -- got a quick answer to this one? -- Paul A Vixie Esq 329 Noe Street {ptsfa, crash, hoptoad, ucat}!vixie!paul San Francisco ptsfa!vixie!paul@ames.ames.arc.nasa.gov CA 94116 paul@vixie.UUCP (415) 864-7013 -- Paul A Vixie Esq 329 Noe Street {ptsfa, crash, hoptoad, ucat}!vixie!paul San Francisco ptsfa!vixie!paul@ames.ames.arc.nasa.gov CA 94116 paul@vixie.UUCP (415) 864-7013
waldorf@venice.SEDD.TRW.COM (jerry waldorf) (02/13/90)
I want to transfer compressed files from a vax to a sun using tip. I can connect up to the vax and ~t filename with text files. That is I can download ascii files. But when I download .Z files the whole thing gets hosed. The files don't turn up correct on the other system. I can't find anything that explicitly says that tip will only transfer ascii files in the man page, so I am hoping there is a way to do it. Any help will be greatly apreciated. Please send responces to waldorf@venice.sedd.trw.com Thanks in advance.
sysnmc@magic706.chron.com (Matt Cohen) (02/18/90)
In UNIX-WIZARDS Digest V9#067, jerry waldorf <waldorf@venice.sedd.trw.com> writes: > I want to transfer compressed files from a vax to a sun >using tip. I can connect up to the vax and ~t filename with >text files. That is I can download ascii files. But when I download > .Z files the whole thing gets hosed. The problem, I believe, is that tip is simply doing a "cat file" on the remote system and then putting whatever comes back into a file. The unprintable characters are garbaging up the output and tip is not getting anything remotely like your file. There are two solutions. The first is to use some other file transfer program that has a binary mode. Good examples are kermit or better yet, xmodem/ymodem/zmodem. These are available at your favorite comp.sources.unix archive or I can send you a copy. The second option is to use uuencode, which encodes binary using only printable ASCII. You get tip to uuencode the file on the remote system and decode it on the local one. While in tip, type "~|". Tip will respond with "~Local command?". Assuming the file is called myfile, ~Local command? uudecode List command for remote system? uuencode myfile myfile Using tip this way is signifigantly slower, since uuencoded files are 35% larger. Also, tip has no error detection/correction apart from any automatically provided by your modem, so if you get line hits during transmission part of your file will be garbaged. If you suspect line noise, you can try getting the file twice and doing a diff. Good luck! Matt Cohen UUCP: ...!uunet!chron!sysnmc Dept. of Info. & Tech. Resources AT&T: +1 713 220 7023 The Houston Chronicle FAX : +1 713 220 7722 801 Texas Avenue, Houston, TX 77002 "The opinions above are most likely "Houston's Leading Information Source" those of my employer."
romain@pyramid.pyramid.com (Romain Kang) (02/22/90)
Another option that was not mentioned was to use btoa/atob in the same manner as uuencode/uudecode. btoa expands data 25% vs 35% for uuencode, which could be a significant difference for you. The sources for btoa/atob come with the compress distribution.