From: Lars Brinkhoff <lars@nocrew.org>
To: "Ron Natalie" <ron@ronnatalie.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Job Control and other terminal fun
Date: Tue, 31 Jan 2023 09:51:25 +0000 [thread overview]
Message-ID: <7wilgn821u.fsf@junk.nocrew.org> (raw)
In-Reply-To: <em1f78b3ec-49c7-401e-a757-4accda19f4fb@e41218a5.com> (Ron Natalie's message of "Mon, 30 Jan 2023 16:31:52 +0000")
Ron Natalie wrote:
> The Berkeley job control was an interesting hack.
Just to add some historical context, Berkeley job control was added by
James Kulp. He had previously used ITS and copied those features pretty
much as-is: ^Z does the same thing; bg and fg are named differently but
work the same.
> A lot of this dates back from the old “tty” days (or at least crt
> terminals that were still alphanumeric). Even the concept of putting
> a job in the background with & is really a feature of trying to
> multiplex multiple tasks on the same dumb terminal.
Indeed ITS got started in 1967 with users interacting through teletypes.
Later CRT terminals were added, but the terse user interface persisted.
prev parent reply other threads:[~2023-01-31 9:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 16:31 [TUHS] " Ron Natalie
2023-01-30 16:39 ` [TUHS] " Chet Ramey
2023-01-30 17:00 ` Ralph Corderoy
2023-01-30 21:00 ` Steffen Nurpmeso
2023-01-31 9:51 ` Lars Brinkhoff [this message]
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=7wilgn821u.fsf@junk.nocrew.org \
--to=lars@nocrew.org \
--cc=ron@ronnatalie.com \
--cc=tuhs@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).