Language Selection

English French German Italian Portuguese Spanish

the futility of termcap in Linux

Filed under

Let's stop a moment and examine the futility of termcap in Linux.
Back in the 1970's Unix systems used to output to various hardware devices. First there were teletypes (most often the ASR-33, because they could be bought cheaply secondhand and refurbished by hobbyists). Teletypes were printers with keyboards attached, hooked up to a serial cable. Everything sent to the serial cable was printed with ink on paper, and the keys pressed by the user were sent the other way along the serial cable for the computer too read.

Note: we're not even talking dot-matrix printers here, the ink ribbon was generally struck by a daisy wheel or similar, so there was no possibility of bitmapped graphics. The characters were struck by good old metal type, dating back to Gutenberg.

This is what "tty" is an abbreviation for: teletype. The Unix console infrastructure still thinks in terms of serial ports connected to printers with keyboards attached. Newline and linefeed being separate characters, waiting until a full line of text is typed before processing it, inability to programmatically read back what was written. Even the ctrl-G "bell" character rang an actual metal BELL. These machines not only needed their ink ribons replaced, they needed to be periodically cleaned, oiled, and various pieces tightened and straightened because they rattled apart. It was almost steampunk.

Then in the 1970's "glass tty" devices were introduced, which connected the serial cable to a box with a CRT and keyboard, instead of printer and keyboard. This new style of terminal was a drop-in replacement for teletypes.

rest here

More in Tux Machines

Leftovers: Gaming

Fedora: The Latest

Leftovers: KDE

  • ocs-client GSoC
    So my GSoC is coming to its end. I have no cool screenshots to upload this time and I have no new great features to talk about, in fact Caludio and I manly focused on bugfixing and testing. We have spent time also discussing about possible changes and improvements to the current OCS protocol. So is the client ready do be lunched? In short I would say that no, not yet.. although most of its features are implemented and it is usable, it is still an “under construction” project, we both still have to make some important decisions to make it usable to everyone.
  • The Fiber Engine Poll, Updates, and Breeze
  • Bringing Akonadi Next up to speed
    and refactoring it again, to make sure the codebase remains as clean as possible. The result of that is that an implementation of a simple resource only takes a couple of template instantiations, apart from code that interacts with the datasource (e.g. your IMAP Server) which I obviously can’t do for the resource.
  • New linter integration plugins for KDevelop
  • Artikulate Plans for Randa
    Language learning is often considered as the task of memorizing new vocabulary and understanding the new grammar rules. Yet for most, the most challenging part is to actually get used to speak the new language. This is a problem that Artikulate approaches with a simple idea: to learn the correct pronunciation of a word or even a longer phrase, the learner listens to a native speaker recording, repeats and recordings it, and finally compares both recordings to improve herself/himself with the next try.

Tails 1.5.1 is out

Tails, The Amnesic Incognito Live System, version 1.5.1, is out. This is an emergency release, triggered by an unscheduled Firefox release meant to fix critical security issues. Read more