Parity on 4.x BSD UNIX ports
Brandon Allbery
allbery at ncoast.UUCP
Sun Apr 24 04:48:40 AEST 1988
As quoted from <11057 at mimsy.UUCP> by chris at mimsy.UUCP (Chris Torek):
+---------------
| In article <12952 at brl-adm.ARPA> cpw%sneezy at lanl.gov (C. Philip Wood) writes:
| >... It appears that there are only two choices [for] output, odd or
| >even parity. ... our site has chosen to require its hosts to not
| >generate parity. ... there are some vendor terminals and emulators
|
| great force' :-) ). Berkeley CSRG are working on a POSIX-like tty
| interface, which will no doubt fix all this, but that is not likely to
| emerge for some time. Sun may provide something useful soon, what with
| their AT&T deal. Some vendors (e.g., Pyramid) provide a SysV interface
+---------------
[Just in case anyone's interested...]
System V has independent parity handling on input and output, with the
exception that the same parity setting (odd or even) must be used for both
if parity is enabled.
Input modes: inpck check parity on input
istrip strip parity before passing to program
parmrk mark parity errors with out-of-band characters
(or special character escapes)
ignpar if set, parity errors are ignored; otherwise they
are passed on as NUL (ASCII 0)
Control modes: parenb enable output parity generation
parodd if set, odd parity is used for parenb and inpck;
otherwise, even parity is used
(Someone answer me a dumb question: what good is parity checking on a pty?)
--
Brandon S. Allbery, moderator of comp.sources.misc
{well!hoptoad,uunet!marque,cbosgd,sun!mandrill}!ncoast!allbery
Delphi: ALLBERY MCI Mail: BALLBERY
More information about the Comp.unix.wizards
mailing list