From: Arthur Krewat <krewat@kilonet.net>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] keyboards and command names
Date: Wed, 5 Feb 2020 18:40:43 -0500 [thread overview]
Message-ID: <8b706ef6-dbf0-27ba-c343-b693f4c5c8f3@kilonet.net> (raw)
In-Reply-To: <alpine.BSF.2.21.9999.2002060907060.33501@aneurin.horsfall.org>
Have't seen mention of TOPS-10, or TOPS-20 for that matter... shortening
commands was a great time saver. Problem was, next time they added a
command, muscle memory had to relearn.
On 2/5/2020 5:20 PM, Dave Horsfall wrote:
> On Wed, 5 Feb 2020, Harald Arnesen wrote:
>
>> Norsk Data's OS Sintran was the same, except that "COLD-START"
>> (reboot the OS) was defined twice, so you had to spell it out in full.
>
> CDC's KRONOS also allowed abbreviated commands; I grew quite fond of
> typing "COMMO" for "COMMON" (attach to the system's common area) and
> "POO" for "POOL" (can't remember what that does, and my books are long
> gone).
>
> Cough cough... The above sequence was how you broke into KRONOS:
>
> COMMON SYSTEM
> POOL SYSTEM
> (quickly interrupt it)
>
> Get the timing right, and you were in supervisor mode (or whatever it
> was called). I remember when I was in the terminal room happily
> hacking away,
> when the shift supervisor and the centre manager happened to walk in,
> exclaiming "Security is pffft!". Terrified, I casually leaned over the
> Duckwriter pretending to look for something, to obscure just what I'd
> been typing...
>
> I dimly recall that you could log off other users by (somehow) sending
> a ^D to their terminal, but I could be confusing that with something
> else (this was decades ago).
>
> -- Dave
>
next prev parent reply other threads:[~2020-02-05 23:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-05 15:05 Rich Morin
2020-02-05 15:30 ` Jaap Akkerhuis
2020-02-05 15:47 ` John P. Linderman
2020-02-05 16:18 ` Clem Cole
2020-02-05 21:03 ` Andrew Newman
2020-02-05 21:59 ` Harald Arnesen
2020-02-05 22:20 ` Dave Horsfall
2020-02-05 23:40 ` Arthur Krewat [this message]
2020-02-10 17:11 ` Paul Winalski
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=8b706ef6-dbf0-27ba-c343-b693f4c5c8f3@kilonet.net \
--to=krewat@kilonet.net \
--cc=tuhs@minnie.tuhs.org \
/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).