Re:COBOL programmers answer call
by DonHopkins on Saturday April 11, 2020 @05:09AM
(#22840580)
At UMD, Chris Torek hacked ^T support to the 4.2 BSD tty driver, inspired by TOPS-10/TWENEX's interrupt character that displayed the system load, current running job, etc.
But the first version didn't have any de-bouncing, and would process each and every ^T it got immediately (each of which had a lot of overhead), so on a hardwired terminal you could hold the keys down and it would autorepeat really fast, bringing the entire system to its knees, while you could even watch the load go up and up and up!
And of course whenever the system got slow, everybody would naturally start typing ^T at once to see what was going on, making it even worse.
That was a Heisenbug, where the act of measuring affects what's being measured, with an exacerbating positive feedback loop. He fixed the problem by rate-limiting it to once a second.
Re:COBOL programmers answer call
by goatinaboat on Saturday April 11, 2020 @02:46AM
(#22840049)
VMS systems on LAT networks only received a packet/interrupt per line from the terminal, that’s how they were able to support many times more users than Unix contemporaries.
Unix can be configured this way —- it used to be the default, with # as the rubout character and @ the line delete character. It’s still in the tty driver and can be useful when programming from a teletype (tty)
Re:COBOL programmers answer call
by goatinaboat on Saturday April 11, 2020 @03:49AM
(#22840277)
I learnt something today - thanks. I’ve never seen a Unix system configured like that, in over 25 years of doing this!
That system was inherited from Multics, but the limited number of interactive computers in those days were primarily used from printing terminals which couldn’t actually erase a character so all of them had some such facility.
thank goodness. I remember it was common that the login screen on a terminal would be configured for # as backspace while backspace would actually DO a backspace but be entered into the buffer.
I suspect it was a remnant of hardcopy terminals
"It generates an interrupt every time you press a key!"