The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Finn O'Leary <finnoleary@inventati.org>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] In Memoriam: J.F.Ossanna
Date: Thu, 28 Nov 2019 00:43:31 +0000	[thread overview]
Message-ID: <c99256a6c908b079aed4ef9e94ece518@inventati.org> (raw)
In-Reply-To: <CANCZdfrTrjqw4-C9UOezgB6jqGD9LMOW1SwYpu+ADMnz4naGdQ@mail.gmail.com>

Wikipedia[0] lists his name as Joseph F. Ossanna, so they don't seem to 
know either

https://en.wikipedia.org/wiki/Joe_Ossanna

- finn

On 2019-11-28 00:06, Warner Losh wrote:
> What do the J and F stand for?
> 
> Warner
> 
> On Wed, Nov 27, 2019, 1:54 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.
>> 
>> He also accomplished a lot more, too much to summarise here.
>> 
>> -- Dave
>> 

  reply	other threads:[~2019-11-28  0:53 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-27 20:53 Dave Horsfall
2019-11-28  0:06 ` Warner Losh
2019-11-28  0:43   ` Finn O'Leary [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2018-11-28 13:09 Noel Chiappa
2018-11-27 21:47 Dave Horsfall
2018-11-27 23:08 ` Ken Thompson via TUHS
2018-11-28  2:57   ` Larry McVoy
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-28  5:22     ` Fabio Scotoni
2018-11-28  9:20 ` Donald ODona
2018-11-29  3:54 ` Dave Horsfall

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=c99256a6c908b079aed4ef9e94ece518@inventati.org \
    --to=finnoleary@inventati.org \
    --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).