>Number:         5265
>Category:       misc
>Synopsis:       the order of tty flags in /etc/ttys changes behavior
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    misc-bug-people (Misc Bug People)
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Apr  8 08:35:01 1998
>Last-Modified:
>Originator:     Jon Buller
>Organization:
none
>Release:        1.3.1
>Environment:
stock NetBSD-1.3/pc532 being upgraded to 1.3.1
		(to make a binary distribution)
System: NetBSD bullbox 1.3.1 NetBSD 1.3.1 (BULLBOX) #0: Sun Mar 29 00:26:43 CST 1998 jonb@bullbox:/usr/src/sys/arch/pc532/compile/BULLBOX pc532


>Description:
	put the following line in /etc/ttys on your 1.3.1 PC532: [8-)]
    tty02	"/usr/libexec/getty std.57600"	unknown	on crtscts local

	init will startup getty for the line, but it will not be
	useful.  In particular, I have this hooked up to a Mac
	running ZTerm, and was getting all characters echoed as
	"`" characters at 57600.  Stepping ZTerm down to 9600 made
	all characters echo properly, but no login banner, etc.
	Exchanging "crtscts" with "local" made everything work
	fine.

	The manpage refers to "rtscts" and that works, but if
	"crtscts" is going to blow everything out of the water, it
	should at least warn you that it's doing that.  Preferably,
	it should warn you about the bad argument and move on to
	the next.

>How-To-Repeat:
	see Description
>Fix:
	workaround is to put mispelled or bogus arguments at the
	end of the list.  I just discovered this last night, and
	may get the time to look into it, but perhaps not...
>Audit-Trail:
>Unformatted: