Bug 76226

	The local.9600 definition in /etc/gettytab uses binary termios(4)
	definitions to define the tty state.  Both the actual field content
	and preceeding comments indicate that parity is disabled but getty
	internally simulates even-parity because the 'np' flag is not
	specified.

	This behaviour is mentioned in gettytab(5) (though not in association
	with the 'np' flag definition) but is somewhat counter-intuitative.
	If the termios state is explicitly set to no parity, that it what
	I expect to see.

Fix: 

The quick fix is to add 'np' to the local.9600 definition in
	/etc/gettytab.

	I believe a better fix would be to copy the PARENB flag from the
	relevant c0/c1/c2 into NP unless NP is explicitly set.
How-To-Repeat: 	Start a getty using local.9600 eg using the following /etc/ttys line:
ttyd0	"/usr/libexec/getty local.9600"	dialup	on secure
	Connect a serial terminal set to CS8, no parity to ttyd0 (or whatever)
	Note that the login banner is written as 7-bit even parity.
	Type input and note that the input is echoed as 7-bit even parity.
	Hit return twice to exec login and note that the second login: prompt
	is generated with 8-bit no parity.