The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: ron@ronnatalie.com (Ronald Natalie)
Subject: [TUHS] Control-T (was top)
Date: Thu, 24 May 2018 10:50:03 -0400	[thread overview]
Message-ID: <DF20553B-A166-485F-8965-E3AC0ECB91FA@ronnatalie.com> (raw)
In-Reply-To: <CAC20D2NkAYBCq2xF-2aO6ep-zvdBy1J=a5PszcviO2JN1hzu8g@mail.gmail.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1217 bytes --]


Another related creeping featurism was the integration of the control-T feature that was prevalent in many of the DEC 10/20 OSs.
When Mike Muuss was doing some scheduling tweaks he decided that being able to list out all the processes on the terminal with a few parameters (he had the weighted load averages at the top of the list).
It became real handy for me when I set out to reverse engineer how the Csh used job control as well.

For those who aren’t old time kernel hacks, there are two structures associated with every process.   The “proc” structure has essential things like uid/gid and memory sizes and priority.   The proc structure always was resident making it ripe pickings for control-T.    More detailed information including the stack of the process (and hence the command line arguments), were in the user structure.    While the user structure of the currently running process was always resident (and on the PDP-11 at 140000, which meant you could use the display register to display the UID to figure out who the CPU hog was).    This made it harder for the “ps”-like things to get.    I finally relented and put a copy of the first few bytes of the arg list in the proc structure.




  parent reply	other threads:[~2018-05-24 14:50 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-24 12:20 [TUHS] History of top Noel Chiappa
2018-05-24 14:09 ` Clem Cole
2018-05-24 14:43   ` Ronald Natalie
2018-05-24 14:50   ` Ronald Natalie [this message]
2018-05-24 15:01     ` [TUHS] Control-T (was top) Clem Cole
2018-05-24 15:48       ` Lars Brinkhoff
2018-05-24 15:08     ` Arthur Krewat
2018-05-28 22:32       ` Paul Winalski
2018-05-28 23:11         ` Clem cole
2018-05-28 23:32           ` Arthur Krewat
2018-05-29  1:12         ` Dave Horsfall
2018-05-28 10:31 ` [TUHS] History of top Lars Brinkhoff
2018-05-29  2:55 [TUHS] Control-T (was top) Noel Chiappa
2018-05-29 17:10 ` Paul Winalski
2018-05-29 18:49 Noel Chiappa
2018-05-30  1:05 ` Dave Horsfall
2018-05-29 21:21 Norman Wilson
2018-05-30  9:06 ` arnold
     [not found] <mailman.1.1527559201.18622.tuhs@minnie.tuhs.org>
2018-05-29 22:45 ` Johnny Billquist
2018-05-30  0:19   ` Clem cole
2018-05-30  0:20     ` Clem cole
2018-05-30 22:10     ` Johnny Billquist
2018-05-30 23:14       ` Pete Turnbull
2018-05-30  1:10   ` Dave Horsfall
     [not found] <mailman.1.1527732002.17884.tuhs@minnie.tuhs.org>
2018-05-31 15:02 ` Johnny Billquist
2018-05-31 21:42   ` Nemo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DF20553B-A166-485F-8965-E3AC0ECB91FA@ronnatalie.com \
    --to=ron@ronnatalie.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).