🚀 go-pugleaf

dawson@willard.waffle.atl.ga.us writes:
>swhite@tybse1.uucp (William C. "Spike" White) writes:
>> The other tricky thing is that TELNET sessions are NOT 8-bit clear paths, lik
>> what UUCP's 'g' protocol expects.  I had to specify to use UUCP's 'e' protoco
>> which expects a 7-bit path.  The 'e' protocol does little or no error-checkin
>> I think.  This wasn't a problem for me, since I was directly connected to the
>> terminal server's port.  Your mileage may vary.

This won't work. 'e' assumes an 8-bit clean connection error-free connection
(like uucpd/IP). You probably meant 'f', which has heavy error-checking and
is 7-bit. And BTW, do NOT count on a direct connection to the ts providing you
with an error-free link. It won't. 99.9999%, maybe, but that's not the same,
and the first time you lose a newsbatch you'll regret it.

>Some telnet implementations do support an 8-bit clear mode... you have to
>explicitly ask for it.  I think the syntax under SunOS is something like
>"telnet -8" ...

Even then you're not in the clear. They may still handle certain control
characters as telnet commands. (In fact, I'm not sure about this, but it may
not be possible to avoid this in any real telnet implementation. See my
posting today in comp.dcom.servers about Annex III <-> Sun Sparc2.)

>> So you're BOTH right :-)

Um.

:-)

---
Alexis Rosen   Owner/Sysadmin,
PANIX Public Access Unix & Internet, NYC.
alexis@panix.com
{cmcl2,uunet}!panix!alexis