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] Re: Lions commentary
Date: Wed, 05 Jul 2023 16:10:43 +0000	[thread overview]
Message-ID: <Q6mWtwxMu0vGg8dT5diHQwmcs5-wPiG7JC4MfW74tigrwrUn06ffRSxCwBqO1j7kV-9BIPn_cUpbUskMcJ4H1oKbQQCQB7bCENVCfJNStWk=@protonmail.com> (raw)
In-Reply-To: <CAFH29tpxAvRY-jWn1onb+6UX5LDX+rDzDRcJvPPWGWP5Gf75zQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1734 bytes --]

I think this is a great community engagement activity. That said, can't do the printing myself. I'll throw myself out there as a potential customer though, I have the print version they did many many years later but it'd be cool to have one of the samizdat copies. To whoever does speak for this and start producing volumes, you've got your first customer!

- Matt G.

P.S. Are the typesetter sources for the commentary preserved anywhere? The typesetting style is very, very much like a small Bell System Teletype 28 training course document that I want to see about recreating as sources, might be able to take some pointers from the commentary.
------- Original Message -------
On Wednesday, July 5th, 2023 at 7:01 AM, Rich Salz <rich.salz@gmail.com> wrote:

> I have a copy of Lions's "A Commentary on the UNIX Operating System" It is an n-th generation photocopy that I've had for some number of decades. It also has the source code, as I guess all of those copies did back in the day. I could just recycle the paper -- it's yellowed with age -- but I'd rather pay it forward and ship it to someone who promises to make copies for others who want it. This is also on bitsavers, so you're only doing this to preserve the sense of history in passing photocopies around.
>
> I'll take bids on how many copies you'll provide. I'll post the winning bid (without their address), so that the community can pressureXXXXXX ensure they meet their commitment. I'll send it out by the end of the week.
>
> I will give preference to US/Canada domestic addresses since that is easier for me. How much preference is left to my discretion. :)
>
> I hope this doesn't make me sound like a jerk; it's intended to be lighthearted community service.

[-- Attachment #2: Type: text/html, Size: 2497 bytes --]

  reply	other threads:[~2023-07-05 16:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-05 14:01 [TUHS] " Rich Salz
2023-07-05 16:10 ` segaloco via TUHS [this message]
2023-07-05 17:59   ` [TUHS] " Clem Cole

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='Q6mWtwxMu0vGg8dT5diHQwmcs5-wPiG7JC4MfW74tigrwrUn06ffRSxCwBqO1j7kV-9BIPn_cUpbUskMcJ4H1oKbQQCQB7bCENVCfJNStWk=@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).