TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

The TTY demystified

161 点作者 iveney将近 13 年前

7 条评论

sgt将近 13 年前
Linus Akesson is quite a character, and you can certainly spend some time on his website. Be sure to check out his chip music <a href="http://www.linusakesson.net/music/chipmusic.php" rel="nofollow">http://www.linusakesson.net/music/chipmusic.php</a> and especially the piano music paired with chip tunes; <a href="http://www.linusakesson.net/music/piano.php" rel="nofollow">http://www.linusakesson.net/music/piano.php</a>
评论 #4067632 未加载
ChuckMcM将近 13 年前
Hmm, I should send him pictures of the guts of my ASR-33 a "real" teletype, aka tty. :-)<p>And for the record it is much safer to pronounce it 't-t-y' rather than 'titty' as one professor at school was fond of doing. I was in the unfortunate situation of being in a meeting to analyze image data where he said "Ok, everyone grab a titty and lets get to work." Sigh.<p>According to Gordon Bell, one of Digital Equipment's top engineers, originally the consoles that computer companies first built used typewriters from the typewriter companies. Unfortunately the typewriters were found to be unreliable as they were not designed for continual typing. So they took a "cheap" teletype from Teletype corporation (which had made Teletype machines that ran 24/7/365) the model 33 and used that. Even though it was the 'cheap, lightweight' version of a Teletype it was 100x more reliable than the typewriters it replaced. Only IBM stuck with their Selectric typewriters as consoles (but they were the manufacturer of the Selectric so they could beef them up accordingly, and they could change the font with a type ball).
leppie将近 13 年前
Blocked by Fortiguard, and reported.<p>Edit: To clarify. It was blocked. I reported this 'false positive' to Fortiguard to remove it from their list. They normally clear it in 24 hours.
评论 #4063217 未加载
评论 #4063219 未加载
peterwwillis将近 13 年前
<i>"We have already seen that a TTY device may be configured to give certain data bytes a special treatment. In the default configuration, for instance, a received ^C byte won't be handed off to the application through read(2), but will instead cause a SIGINT to be delivered to the foreground job. In a similar way, it is possible to configure the TTY to react on a stop flow byte and a start flow byte. These are typically ^S (ASCII code 19) and ^Q (ASCII code 17) respectively. Old hardware terminals transmit these bytes automatically, and expect the operating system to regulate its flow of data accordingly. This is called flow control, and it's the reason why your xterm sometimes appears to lock up when you accidentally press ^S."</i><p>A 12-year-old mystery to me is finally solved.
评论 #4065512 未加载
stcredzero将近 13 年前
I'm old enough to have hung out with others breaking into mainframes to play Star Wars inspired text games on printed-paper TTYs. (I was in grade school at the time.)
评论 #4066776 未加载
drudru11将近 13 年前
One thing missing... all the bugs and misinterpretations in all the various unixes around this stuff :-)
jvehent将近 13 年前
OOhhhh ! `kill -l` !!!