The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: segaloco via TUHS <tuhs@tuhs.org>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Lions' Commentary Revisions?
Date: Mon, 04 Mar 2024 18:40:40 +0000	[thread overview]
Message-ID: <dYEq0MutYeLtnX1_AD8dYy3QnJSZMBYv3xMkwpWCuc_DiQGZsARgMLugn7XxARkOz0-mwRDfqtrt4IGQjaz0q_xLphZKSdvfl60hzoBoQ-A=@protonmail.com> (raw)

I hope everyone's having a lovely tail end of whichever season is gracing your
hemisphere.  Had some surprise snow this morning up in the NW corner of the US,
hoping it bodes well for a mild summer.

I'm curious, is anyone aware of any attempts to revise John Lions's UNIX
Commentary for versions beyond the Sixth Edition?  Having finished my
disassembly of the classic video game Dragon Quest this past year, I'm now doing
some planning for a similar work and have considered practicing the art a little
by doing some diffing of V6 and V7 and feeling out the process by putting down
some revisions, that way I've got some of the flow and kinks worked out before I
start on my own "Commentary on Dragon Quest" manuscript.  I'd hate to double up
on something someone else has already done though, so if V7 for instance has
gotten this treatment, then perhaps focusing on PWB or the CB-UNIX kernel would
minimize the potential rehashing.

Also if anyone has any thoughts, suggestions, etc. from their own experiences
working up very detailed source-level documentation of a large software product,
I'd certainly be interested, as I know this is going to turn into quite the
sprawling undertaking once I really get going, especially if I try and work in
the differences between the Japanese and U.S. releases (of which there are many.)

- Matt G.

             reply	other threads:[~2024-03-04 18:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-04 18:40 segaloco via TUHS [this message]
2024-03-04 18:45 ` [TUHS] " Dan Cross
2024-03-04 20:23   ` Douglas McIlroy

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='dYEq0MutYeLtnX1_AD8dYy3QnJSZMBYv3xMkwpWCuc_DiQGZsARgMLugn7XxARkOz0-mwRDfqtrt4IGQjaz0q_xLphZKSdvfl60hzoBoQ-A=@protonmail.com' \
    --to=tuhs@tuhs.org \
    --cc=segaloco@protonmail.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).