The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: don@DonHopkins.com (Don Hopkins)
Subject: Unix witticisms
Date: Sat, 7 Oct 2017 14:21:40 +0200	[thread overview]
Message-ID: <A27C4E20-36B3-4114-8239-4609318F8AD7@gmail.com> (raw)
In-Reply-To: <001001d33f14$bbfe0900$33fa1b00$@ronnatalie.com>

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

We used to use “rms” as a verb, to log in to somebody else’s account with a well known password, as in “I rms’ed into the box and rebooted it.”

-Don


> On 7 Oct 2017, at 04:33, Ron Natalie <ron at ronnatalie.com> wrote:
> 
> "Roff is the simplest of the run off programs but is utterly frozen " appeared in the V6 man pages.
> 
> This led to a whole slew (at least at JHU) comments in program documents about being "utterly frozen."
> The large freshman "Models and Simulation" class used basic plus and a special command called "lnmns" was created to link the necessary files into the user's home dir.
> Our docs said that "lnmns was the simplenst of the transcendental programs but is utterly frozen."
> 
> For those who know nroff/troff, we had fun in that our senior programmer "Michael John Muuss" wrote a macro package called tmac.jm which was invoked with nroff -mjm (his initials).
> This lead to all kinds of jokes including calling lnmns "bill" after its programmers.
> 
> Many years later there was a proposal to rename the concept of freeware "Flugelware" after some guy named "Flugel" who alledgedly came up with the idea.
> I suggested that we call the C compiler "Ritchie" after its creator.    I got an immediate reponse from dmr telling me to nip that idea in the bud.
> 
> 



  parent reply	other threads:[~2017-10-07 12:21 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-04  8:30 Wesley Parish
2017-10-05  9:22 ` Don Hopkins
2017-10-05 14:26   ` Ron Natalie
2017-10-05 14:37     ` Dan Cross
2017-10-05 15:33       ` Ron Natalie
2017-10-05 17:11         ` [TUHS] " ron minnich
2017-10-05 19:06           ` A. P. Garcia
2017-10-05 14:48     ` Jon Steinhart
2017-10-05 23:28       ` Robert Brockway
2017-10-06  1:01         ` Steve Simon
2017-10-06  1:33           ` Bakul Shah
2017-10-07  8:51     ` Russell Page
2017-10-07 13:22       ` Don Hopkins
2017-10-07 13:30         ` Ron Natalie
2017-10-07 13:34           ` Don Hopkins
2017-10-07 14:12         ` Larry McVoy
2017-10-07 14:21       ` Steffen Nurpmeso
2017-10-05 10:43 ` Russell Page
2017-10-05 10:54   ` Steve Nickolas
2017-10-05 22:38   ` Greg 'groggy' Lehey
2017-10-05 10:53 ` Tom Ivar Helbekkmo
2017-10-06 16:01 ` Dario Niedermann
2017-10-06 16:48   ` George Michaelson
2017-10-06 16:54     ` Warner Losh
2017-10-06 22:25       ` Dave Horsfall
2017-10-06 22:58         ` jason-tuhs
2017-10-06 23:28           ` Dave Horsfall
2017-10-07  2:33     ` Ron Natalie
2017-10-07  2:40       ` George Michaelson
2017-10-07  2:48         ` Ron Natalie
2017-10-07  2:55           ` George Michaelson
2017-10-07  2:59             ` George Michaelson
2017-10-07 12:21       ` Don Hopkins [this message]
2017-10-07 14:17 Noel Chiappa

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=A27C4E20-36B3-4114-8239-4609318F8AD7@gmail.com \
    --to=don@donhopkins.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).