From: Douglas McIlroy <douglas.mcilroy@dartmouth.edu>
To: Dan Cross <crossd@gmail.com>
Cc: segaloco <segaloco@protonmail.com>,
The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Lions' Commentary Revisions?
Date: Mon, 4 Mar 2024 15:23:18 -0500 [thread overview]
Message-ID: <CAKH6PiVU0O+q_xE+KHt2ssZ-xKjuApBm7wtFFpZECmPq9o_Twg@mail.gmail.com> (raw)
In-Reply-To: <CAEoi9W5nr8_86t=7ZQdHBRXuPmBxXg52=v3ButrmMgSWOmh6EQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1224 bytes --]
>> I'm curious, is anyone aware of any attempts to revise John Lions's UNIX
>> Commentary for versions beyond the Sixth Edition?
> As I understand it, this was prohibited for 7th Edition
It would be OK now, for the 7th edition source has been released, free of
the trade-secret constraint.
On Mon, Mar 4, 2024 at 1:46 PM Dan Cross <crossd@gmail.com> wrote:
> On Mon, Mar 4, 2024 at 1:41 PM segaloco via TUHS <tuhs@tuhs.org> wrote:
> > 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?
>
> As I understand it, this was prohibited for 7th Edition and later by
> restrictions inserted into licenses for those versions. I don't know
> exactly how, as I'm not a lawyer.
>
> In terms of modern adaptations, there are commentaries for the Plan 9
> (3rd Edition) source code that are similar to Lions, and the xv6
> pedagogical system is accompanied by a similar commentary.
>
> - Dan C.
>
[-- Attachment #2: Type: text/html, Size: 1739 bytes --]
prev parent reply other threads:[~2024-03-04 20:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 18:40 [TUHS] " segaloco via TUHS
2024-03-04 18:45 ` [TUHS] " Dan Cross
2024-03-04 20:23 ` Douglas McIlroy [this message]
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=CAKH6PiVU0O+q_xE+KHt2ssZ-xKjuApBm7wtFFpZECmPq9o_Twg@mail.gmail.com \
--to=douglas.mcilroy@dartmouth.edu \
--cc=crossd@gmail.com \
--cc=segaloco@protonmail.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).