From: David Arnold <davida@pobox.com>
To: UNIX Heritage Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Lions notes, early history
Date: Mon, 2 Nov 2020 18:59:23 +1100 [thread overview]
Message-ID: <359CCDCB-2739-4FDA-8404-16C1B88410EE@pobox.com> (raw)
In-Reply-To: <AB114045-86E0-4FE5-93C1-4DCD6F2776C0@humeweb.com>
[-- Attachment #1: Type: text/plain, Size: 2315 bytes --]
The UNSW Library Appears to have a copy in their storage, accessible by special request. It has a copyright date of “c1977” so it’s not the later “properly” published edition.
https://primoa.library.unsw.edu.au/primo-explore/fulldisplay?vid=UNSWS&docid=UNSW_ALMA21116225050001731&query=any,contains,John%20lions&_ga=2.60871272.51366765.1604303632-102727300.1604303632
d
> On 2 Nov 2020, at 18:44, Andrew Hume <andrew@humeweb.com> wrote:
>
> i was a TA for the course which used this as a textbook.
> my memory is little faded on this (it was on the other side of my stroke),
> but i believe they were perfect bound (cloth strip and glue) and had
> two different colors for the covers (i want to say orange and red).
> they might have been just stapled but they were thick enough that staples
> might have been insufficient.
>
> i certainly remember john printing them off on the DEC printer.
>
> as for the permissions, i can’t recall anything at the time (this was about 45 years ago),
> but do remember the fuss at the Labs when Bell Labs started printing their own
> high security copies just a couple of years later.
>
> andrew hume
>
>> On Nov 1, 2020, at 9:07 PM, Greg 'groggy' Lehey <grog@lemis.com> wrote:
>>
>> Warner Losh and I have been discussing the early history of John
>> Lions' "A commentary on the Sixth Edition UNIX Operating System".
>> I've been hosting Warren Toomey's version (with some correction of
>> scan errors) at http://www.lemis.com/grog/Documentation/Lions/ for
>> some years now, and my understanding had been that the book hadn't
>> been published, just photocopied, until Warren posted it on
>> alt.folklore.computers in 1994. But now it seems that the "book" had
>> been published by UNSW when Lions held the course, and only later was
>> the license revoked. Does anybody have any insights? What
>> restrictions were there on its distribution? What was the format?
>> Was it a real book, or just bound notes?
>>
>> Greg
>> --
>> Sent from my desktop computer.
>> Finger grog@lemis.com for PGP public key.
>> See complete headers for address and phone numbers.
>> This message is digitally signed. If your Microsoft mail program
>> reports problems, please read http://lemis.com/broken-MUA
>
[-- Attachment #2: Type: text/html, Size: 4199 bytes --]
next prev parent reply other threads:[~2020-11-02 8:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-02 5:07 Greg 'groggy' Lehey
2020-11-02 5:21 ` Warner Losh
2020-11-02 9:51 ` Warren Toomey
2020-11-02 10:26 ` Ed Bradford
2020-11-02 11:04 ` arnold
2020-11-03 1:16 ` Greg 'groggy' Lehey
2020-11-02 7:21 ` Andrew Hume
2020-11-02 7:59 ` David Arnold [this message]
2020-11-02 14:26 ` Clem Cole
2020-11-02 21:17 ` Dave Horsfall
2020-11-02 16:25 Norman Wilson
2020-11-02 17:16 ` arnold
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=359CCDCB-2739-4FDA-8404-16C1B88410EE@pobox.com \
--to=davida@pobox.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).