The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Kevin Bowling <kevin.bowling@kev009.com>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Documenter's Workbench versions
Date: Sun, 6 Mar 2022 18:02:44 -0700	[thread overview]
Message-ID: <CAK7dMtA=ysP4GRwmbVu-5YimfjypqLjebfoa6PE2NQWFKHkpfg@mail.gmail.com> (raw)

I am reading some UNIX text processing books and am interested in the
lineage of Documenter's Workbench.

I see documentation of 1.0 (i.e
https://archive.org/details/sysv-dwb/page/n5/mode/2up)
I see a copy of 2.0 for 3B2 (i.e.
https://archives.loomcom.com/3b2/software/Documenters_Workbench/)

From there things get a little less clear, it seems like we jump to
3.2 with SysVR3.2?

Then there is a 3.3 version https://github.com/n-t-roff/DWB3.3

One of my books from the late 80s references 3.4 available as a source
code purchase independent of UNIX.

Then it appears SGI might have had a 4.x strain?  (i.e.
https://archive.org/details/sgi_Documenters_Workbench_4.1.3)

Heirloom is derived from OpenSolaris which is derived from?

Can anyone firm this lineage up a bit; and is 4.x an SGI thing or what
(I extracted the image, the relnotes inside might as well not exist).

Regards,
Kevin

             reply	other threads:[~2022-03-07  1:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-07  1:02 Kevin Bowling [this message]
2022-03-07  2:42 ` Larry McVoy
2022-03-07 13:28 ` Jaap Akkerhuis
2022-03-07 16:55   ` Kevin Bowling
2022-03-10 17:21     ` ozan yigit
2022-03-07 20:57 ` Kevin Bowling
2022-03-09 22:30   ` Andrew Diller
2022-03-10  0:44     ` Kevin Bowling
2022-03-10  2:17       ` Andrew Diller
2022-03-10  1:10   ` Dan Plassche
2022-03-14  0:17     ` Dan Plassche
2022-03-13  5:24 ` Warren Toomey
2022-03-09  2:06 Douglas McIlroy
2022-03-09  9:41 ` Jaap Akkerhuis

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='CAK7dMtA=ysP4GRwmbVu-5YimfjypqLjebfoa6PE2NQWFKHkpfg@mail.gmail.com' \
    --to=kevin.bowling@kev009.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).