The Random Thread

Does anyone know the historical basis for the ^T ^O keys? This function has to be written into various user programs and it takes effort to maintain these, etc. I'm just curious to know more about the reasoning behind these? I find them convenient at times but they seem specific to FreeBSD and perhaps to older UNIX.

I like them a lot. Getting a progress report without having to ask for them at startup is convenient.

Only problem is that some people are tempted to use printf in the signal handler, which is not legal.
 
In FreeBSD there is a convention where one can type ^T or ^O (Control-T, Control-O) in the midst of the run of various programs (will use DD as an example). ^T will request some sort of runtime statistics from the program and ^O will temporarily suspend output to the terminal.

These two are in addition to the much more widely used ^S and ^Q, ^U, etc. As far as I can tell only FreeBSD still supports ^T and ^O. These keys don't do anything in any Linux I've used.

Does anyone know the historical basis for the ^T ^O keys? This function has to be written into various user programs and it takes effort to maintain these, etc. I'm just curious to know more about the reasoning behind these? I find them convenient at times but they seem specific to FreeBSD and perhaps to older UNIX.
Check out pages 7 (^O) and 20 (^T) of the following 1975 DECsystem-10 manual. DECsystem-10 was not Unix (as far as I know), and yet it incorporated these commands, which seem to be part of an earlier set of terminal conventions. Anyway, the document is what's cooler.

 
Back
Top