The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Larry McVoy <lm@mcvoy.com>
To: Ken Thompson <ken@google.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] In Memoriam: J.F.Ossanna
Date: Tue, 27 Nov 2018 18:57:39 -0800	[thread overview]
Message-ID: <20181128025739.GA5701@mcvoy.com> (raw)
In-Reply-To: <CAG=a+rhFd--aL6UDus4woGc_1YHLzmj+2j1EscQ=z_HH4xEU5w@mail.gmail.com>

As a long time roff fan (I still use it, yes, I've learned LaTex, I much
prefer roff), I'm hugely bummed that Joe left us so early.  I feel like
there would be more fun stories, like Ken's story.

If I remember correctly, he wrote the first (Unix *) version of roff in
PDP-11 assembly, right?  Granted, PDP-11 assembly is perhaps the most 
pleasant assembly ever, but it is still assembly.  Roff is a non-trivial
program, I can't say that I've every written anything remotely that big
in assembly (the only thing I'm proud of is writing swtch() in VAX, 68K,
and some other CPU that I can't remember, but that was tiny, hard to get
right, but tiny).  I've got mad respect for what he did, I feel like the
whole roff thing doesn't get enough respect.  It wasn't just roff, though
that started it, it was pic (I *love* pic), eqn, all the other filters
that go down to roff.  For lmbench I wrote my own grap like tools 
because grap wasn't open source.

I was talking to Marc Donner, a Morgan Stanley techy (since moved on
to google and who knows where) about why I liked roff.  At the time
I had built webroff which took roff -ms input and made websites.
Marc pointed out that the reason I liked roff was, for the most part,
it didn't say how to do something (that was buried in the macros),
it said what you wanted to do.

Ken, if you have more Joe stories I'd love to hear them, I feel like
I missed out on a cool person.

(*) I know that nroff was "new run off" and it came from somewhere,
MIT?  Some old system, but it wasn't invented in Unix.  That said,
I've never seen docs for the previous system and I kinda think Joe
took it to the next level.  If you haven't studied the docs and
written macros, you should.  It's a pretty neat system.

On Tue, Nov 27, 2018 at 03:08:36PM -0800, Ken Thompson via TUHS wrote:
> joe was much more than that. he knew how
> to play the system. example:
> out of whole cloth, he invented a form to
> order a teletype and opx (bell labs extension)
> installed in the home. he then filled out the
> form for each of the unix-room dennisons.
> there was a phone call from a confused
> clerk, and then we all got teletypes and
> data sets at home. as an aside, the opx
> came with free watts (long distance which
> was very expensive in those days.)
> 
> 
> On Tue, Nov 27, 2018 at 1:47 PM, Dave Horsfall <dave@horsfall.org> wrote:
> > We lost J.F. Ossanna on this day in 1977; he had a hand in developing Unix,
> > and was responsible for "roff" and its descendants.  Remember him, the next
> > time you see "jfo" in Unix documentation.
> >
> > -- Dave

-- 
---
Larry McVoy            	     lm at mcvoy.com             http://www.mcvoy.com/lm 

  reply	other threads:[~2018-11-28  2:58 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-27 21:47 Dave Horsfall
2018-11-27 23:08 ` Ken Thompson via TUHS
2018-11-28  2:57   ` Larry McVoy [this message]
2018-11-28  4:48     ` Ken Thompson via TUHS
2018-11-28 14:44       ` Dan Cross
2018-11-28 17:08       ` Paul Winalski
2018-11-28 19:03         ` WIlliam Cheswick
2018-11-28 19:04         ` WIlliam Cheswick
2018-11-28 17:57       ` Earl Baugh
2018-11-28 18:23       ` ron minnich
2018-11-29 17:54       ` [TUHS] [OT] azel - was " Toby Thain
2018-11-29 17:57         ` Warner Losh
     [not found]         ` <CAG=a+rhvgikmvEPS_Z-umK2XPYfaxHmov_3QZuD0GcE97BN1qw@mail.gmail.com>
2018-11-29 20:11           ` Toby Thain
2018-11-28  5:22     ` [TUHS] " Fabio Scotoni
2018-11-28  9:20 ` Donald ODona
2018-11-29  3:54 ` Dave Horsfall
2018-11-28 13:09 Noel Chiappa
2019-11-27 20:53 Dave Horsfall
2019-11-28  0:06 ` Warner Losh
2019-11-28  0:43   ` Finn O'Leary
2019-11-28 17:16     ` ron
2019-11-28 17:18       ` ron
2019-11-28  0:46   ` David Arnold
2019-11-28  3:43 ` Larry McVoy
2019-11-30 17:45   ` Finn O'Leary
2019-11-28  9:19 ` Thomas Paulsen

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=20181128025739.GA5701@mcvoy.com \
    --to=lm@mcvoy.com \
    --cc=ken@google.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).