The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: erik@ono-sendai.com (Erik Berls)
Subject: [TUHS] The evolution of Unix facilities and architecture
Date: Wed, 10 May 2017 16:09:09 -0700	[thread overview]
Message-ID: <CAEFkZw-ygO1mD22_cpCbxN7Ms_QP3znoukkgP+JMb-C2xv1oLw@mail.gmail.com> (raw)
In-Reply-To: <20170510143813.YrQ5R%steffen@sdaoden.eu>

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

groff came into NetBSD (of which, FreeBSD 1.0 incorporated a
pre-release NetBSD 0.8 tarball), with the 386bsd + patchkit initial
import.  Sun Mar 21 09:45:37 1993 UTC, by cgd.  It was upgraded to
groff release 1.08 about 4 months later, by jtc.

Source: NetBSD’s cvsweb


-----Original Message-----
From: Steffen Nurpmeso <steffen@sdaoden.eu>
Reply: tuhs at minnie.tuhs.org <tuhs at minnie.tuhs.org>
Date: May 10, 2017 at 2:16:16 PM
To: Diomidis Spinellis <dds at aueb.gr>
Cc: tuhs at minnie.tuhs.org <tuhs at minnie.tuhs.org>
Subject:  Re: [TUHS] The evolution of Unix facilities and architecture

> Yes, hi,
>
> Diomidis Spinellis wrote:
> |I've made available on GitHub a series of tables showing the evolution
> |of Unix facilities (as documented in the man pages) over the system's
> |lifetime [1] and two diagrams where I attempted to draw the
> |corresponding architecture [2]. I've also documented the process in a
> |short blog post [3]. I'd welcome any suggestions for corrections and
> |improvements you may have, particularly for the architecture diagrams.
> |
> |[1] https://dspinellis.github.io/unix-history-man/
>
> i am confident groff was part of (Free)BSD even before it was
> released. That is, i have used groff with FreeBSD 4.9 (?) base
> systems onwards, and i know from the CSRG history that they worked
> to get there. (It is not part of the repo, though, it is only
> deduced. I still don't have the McKusick CD's, shame on me.)
>
> |[2] https://dspinellis.github.io/unix-architecture/
> |[3] https://www.spinellis.gr/blog/20170510/
>
> --steffen
> |
> |Ralph says i must not use signatures which spread the light!
>

--
Erik Berls


  reply	other threads:[~2017-05-10 23:09 UTC|newest]

Thread overview: 77+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-10 14:08 Diomidis Spinellis
2017-05-10 14:38 ` Steffen Nurpmeso
2017-05-10 23:09   ` Erik Berls [this message]
2017-05-11 12:40     ` Steffen Nurpmeso
2017-05-11  0:49 ` Clem Cole
2017-05-11 14:07 Noel Chiappa
2017-05-11 14:21 ` Larry McVoy
2017-05-11 16:17   ` Clem Cole
2017-05-11 17:11     ` Michael Kjörling
2017-05-11 21:44       ` Dave Horsfall
2017-05-11 22:06         ` Warner Losh
2017-05-12  6:24         ` Hellwig Geisse
2017-05-12 21:12           ` Dave Horsfall
2017-05-12 23:25             ` Hellwig Geisse
2017-05-11 16:15 ` Clem Cole
2017-05-11 16:52   ` Warner Losh
2017-05-11 17:12     ` Clem Cole
2017-05-11 20:37       ` Ron Natalie
2017-05-11 22:25         ` Larry McVoy
2017-05-11 22:30           ` Ron Natalie
2017-05-11 23:47           ` Dave Horsfall
2017-05-11 23:48             ` Ron Natalie
2017-05-12  0:21               ` Larry McVoy
2017-05-12  2:42                 ` Warner Losh
2017-05-12  0:16             ` Larry McVoy
2017-05-12  1:41               ` Wesley Parish
2017-05-12  1:05             ` Toby Thain
2017-05-12  8:17               ` Michael Kjörling
2017-05-12 13:56                 ` Tim Bradshaw
2017-05-12 14:22                   ` Michael Kjörling
2017-05-12 14:30                   ` Larry McVoy
2017-05-12 15:11                     ` Tim Bradshaw
2017-05-12 15:52                     ` Chet Ramey
2017-05-12 16:21                       ` Warner Losh
2017-05-12  8:15             ` Harald Arnesen
2017-05-14  4:30           ` Theodore Ts'o
2017-05-14 17:40             ` Clem Cole
2017-05-11 17:08 Noel Chiappa
2017-05-11 21:34 ` Dave Horsfall
2017-05-12 15:12 Noel Chiappa
2017-05-12 15:17 ` Clem Cole
2017-05-12 15:18   ` Clem Cole
2017-05-12 15:46     ` Clem Cole
2017-05-12 18:43 Doug McIlroy
2017-05-12 18:56 ` Dan Cross
2017-05-12 19:43   ` Clem Cole
2017-05-12 20:06     ` Clem Cole
2017-05-12 20:40       ` Jeremy C. Reed
2017-05-12 21:29         ` Clem Cole
2017-05-12 21:29   ` Ron Natalie
2017-05-12 23:30 Noel Chiappa
2017-05-12 23:38 ` Dave Horsfall
2017-05-12 23:52   ` Random832
2017-05-13  0:26     ` Dave Horsfall
2017-05-13  0:48       ` Random832
2017-05-13  0:22 ` Clem Cole
2017-05-13  0:23   ` Clem Cole
2017-05-13  0:44 Noel Chiappa
2017-05-13  0:51 ` Random832
2017-05-13  0:55   ` Dave Horsfall
2017-05-13  1:17   ` Chris Torek
2017-05-13 15:25   ` Steve Simon
2017-05-13 16:55     ` Clem Cole
2017-05-13 17:19       ` William Pechter
2017-05-14 12:55         ` Derek Fawcus
2017-05-14 22:12           ` Dave Horsfall
2017-05-15  1:24             ` Nemo
2017-05-15 18:00               ` Steve Johnson
2017-05-16 22:33                 ` Ron Natalie
2017-05-16 23:13                   ` Arthur Krewat
2017-05-16 23:18                     ` Ron Natalie
2017-05-13 23:01     ` Dave Horsfall
2017-05-13  1:25 Noel Chiappa
2017-05-14 21:44 Noel Chiappa
2017-05-16 13:20 Noel Chiappa
2017-05-16 13:46 ` Clem Cole
     [not found] <mailman.1.1494986402.2329.tuhs@minnie.tuhs.org>
2017-05-19 14:31 ` David

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=CAEFkZw-ygO1mD22_cpCbxN7Ms_QP3znoukkgP+JMb-C2xv1oLw@mail.gmail.com \
    --to=erik@ono-sendai.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).