Current-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: 'getty' printing delay tokens in -current and netbsd-6

While transmitting a capability element that is supposed to indicate a
delay is obviously wrong, performing actual NUL padding seems like a step
backward to me.  Is this what netbsd-5's (and earlier) getty did?  If so,
I was blissfully ignorant of this and it rather invalidates my concern.

Is it that much more complex to teach getty to honor delay attributes by
actually waiting?  (I know, I know, "So, where are your patches?".)

As to whether pad/delay is needed anymore, I have no doubt that someone,
somewhere (such as myself) has one or more terminals where such attributes
are relevant and will expect it to Just Work(tm) when he hooks it up
rather than be Astonished by spurious output.  (A friend has an ASR-33
that we've been trying to get working again... ;)

|/"\ John D. Baker, KN5UKS               NetBSD     Darwin/MacOS X
|\ / jdbaker[snail]mylinuxisp[flyspeck]com    OpenBSD            FreeBSD
| X  No HTML/proprietary data in email.   BSD just sits there and works!
|/ \ GPGkeyID:  D703 4A7E 479F 63F8 D3F4  BD99 9572 8F23 E4AD 1645

Home | Main Index | Thread Index | Old Index