From: sweh.womble@spuddy.UUCP (Stephen Harris) Subject: 99.5 Kernel breaks serial logins Date: 25 Feb 1993 19:31:47 GMT
In article <1993Feb17.221646.4634@primerd.prime.com> cummings@hammer.prime.com writes:
[In article <729894051snxwomble@spuddy.UUCP>, I write:]
> > Possible alternate method: run the getty on /dev/cua# where the device
> > cua# had major 5, and minor the same as ttyS#
>
> NO! Don't do this! the cua* devices are for dialout! The ttyS* devices are
> the right ones to use for gettys and logins. If you are trying to use a
> serial line for both dialin AND dialout, the getty should run on ttyS* and
> the dialout software should use cua*. Each device will block (or fail) if
> the other is in use.
This is totally correct - the getty *should* be run on ttyS? devices, but
in the case I was replying to, there was a terminal plugged into the serial
line, so the device was only going to be connected to be "dialin" only, thus
it wouldn't hurt to run the getty on the cua? line....unless the kernel
complains elsewhere???? [is it possible for device 5,64 to be a control
terminal?]
I did suggest primarily that connecting pins 8 and 20 was the correct
solution, as you also point out later, and that running the getty on cua? was
a *possible* alternate method.
Stephen Harris
sweh.womble@spuddy.uucp ...!uknet!axion!spuddy!sweh.womble
* Meow! Call Spuddy the Cat for Usenet access in the UK. Call 0203 364436 *