dennis@hpirs.HP.COM (Dennis D. Lee) (04/29/88)
I have a question about HDB uucp:
In line.c, inside the routine fixline(), there is the following line:
ttbuf.c_cflag = speed;
What this is doing is configuring the line for dialout. Should the '='
be '|=' instead ? It seems the '=' assignment will cause the other tty
attributes ( namely, PARENB and PARODD ) be cleared. What will happen
when we are dialing to a system that is using parity ?
How does uucp in general, deal with the 8th bit ? Where is it doing that?
Any idea on this is appreicated.
Dennis D. Lee
hpda!dennisbob@cloud9.UUCP (Bob Toxen) (05/03/88)
In article <4210003@hpirs.HP.COM>, dennis@hpirs.HP.COM (Dennis D. Lee) writes: > > I have a question about HDB uucp: > In line.c, inside the routine fixline(), there is the following line: > ttbuf.c_cflag = speed; > ... [what about] when we are dialing to a system that is using parity ? > How does uucp in general, deal with the 8th bit ? Where is it doing that? Many UUCICOs cannot dial into systems that require parity (such as OUR non- native UNIX system). 4.2BSD supposedly allows one to specify parity, but it isn't in Sun's UUCICO. I hacked our UUCICO to allow specifying parity. Some UUCICOs will accept 8 bits in send strings so that if you do your own parity generation, e.g. "he\314\314o" for hello it will work. I have the table if anyone wants it. Not all UUCICOs accept \(3 octal digits). Have the called system's uucp account & password be such that the parity bit for all characters is 0. -- Bob Toxen {ucbvax!ihnp4,harvard,cloud9!es}!anvil!cavu!bob Stratus Computer, Marlboro, MA Pilot to Copilot: What's a mountain goat doing way up here in a cloud bank?