From: "pobox.com" <gak@pobox.com>
To: Ron Natalie <ron@ronnatalie.com>
Cc: tuhs@tuhs.org
Subject: Re: [TUHS] /usr/bin/1
Date: Tue, 3 Nov 2020 08:00:39 -0800 [thread overview]
Message-ID: <D2260C32-2BC0-47B4-AF8B-BAEAE4C0E107@pobox.com> (raw)
In-Reply-To: <ema06dc50b-3a79-44ad-abdf-44b7c649a699@r1.local>
[-- Attachment #1: Type: text/plain, Size: 1230 bytes --]
On Nov 3, 2020, at 7:40 AM, Ron Natalie <ron@ronnatalie.com> wrote:
> This memory just came back to me. There was a UNIX disribution (PWB/UNIX?) that had a program called 1.
> It printed tis quaint bit of propaganda.
>
> One Bell System. It works.
>
> This was fine until one day I’m at work in a big bull pen computer room when Bernie, one of my co-workers, shouts.
> “What’s all this Bell System crud in the editor?”
>
> My reaction is, “Well, it’s all Bell System crud.” I walk over to his terminal and find he is typing 1 repeatedly at the shell prompt and getting the above message. (This was back in the old /bin/ed days where 1 got you to the top of the file). I had to point out he wasn’t in the editor.
>
> Later that day, the program was changed to say:
>
> You’re not in the editor, Bernie.
>
> This I think made it into one of the BRL releases and occassionally got inquiries as to who Bernie is.
Yes, PWB/UNIX.
I seem to recall it also had /usr/bin/flog. You pass it a process ID as argument, and it was supposed to make the process work harder. (I can't remember the exact wording on the web page. In fact, I could be confused about it being in PWB.)
[-- Attachment #2: Type: text/html, Size: 6965 bytes --]
next prev parent reply other threads:[~2020-11-03 16:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-03 15:40 Ron Natalie
2020-11-03 15:53 ` Clem Cole
2020-11-03 16:00 ` pobox.com [this message]
2020-11-03 20:56 ` John Cowan
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=D2260C32-2BC0-47B4-AF8B-BAEAE4C0E107@pobox.com \
--to=gak@pobox.com \
--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).