From: Clem Cole <clemc@ccc.com>
To: Warner Losh <imp@bsdimp.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] MASSCOMP MC-500 Guide to Writing a Unix Device Driver
Date: Mon, 29 Apr 2019 10:45:50 -0400 [thread overview]
Message-ID: <CAC20D2NXmwpdjmHabeUav+4UzB0YMjcY0CHALarhAfod=kr7gA@mail.gmail.com> (raw)
In-Reply-To: <CANCZdfo1FMorKD_X31vEz45zsa9PSzhLd0kwtKnyW7pK1P3wCQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2746 bytes --]
Warner,
I should have copies of it, I'm also in email contact with both Tom T. (aka
tjt - who is someone I reference often on this list) and Janet (Tom often
weekly).
As for history, until Janet created that document for Masscomp, nothing
existed other than a short paper I believe Dennis wrote for V6 and updated
for V7. Cliff and Tom A had spent hours in Tom and my shared office
picking our brains. What they came up with was not quite right (to be
polite) and tjt attempted to fix it - which at least was technically
correct. Janet has the head of Masscomp's documentation group, re-wrote
Tom's version to make it easier to understand. I should have the version
in my files [Janet might even have the original troff sources].
When Tim O'Reilly (who had been writing a lot of our doc under contract and
started to do the original 'nutshell' series) cut a deal to take the
documentation he was writing for us 'out of Masscomp' and publish it (thus
creating the original X-Windows documentation and the first real hit for
ORA), precedent had been set.
Shortly after, Tom and I had left for Belmont, ney Stellar, and Janet and
Tom decided to redo it as a book.
ᐧ
On Mon, Apr 29, 2019 at 9:50 AM Warner Losh <imp@bsdimp.com> wrote:
> Greetings,
>
> I'm trying to find the predecessor to "Writing a UNIX Device Driver, J.
> Egan & T. Teixeira, 1st ed, 1988". In the preface, it says:
>
> "This book is based on a MASSCOMP manual, Guide to Writing a Unix Device
> Driver. The first version that MASSCOMP published as part of the
> documentation set for the MC-500 was based on preliminary drafts prepared
> for MASSCOMP by Cliff Cary and Tom Albough of Creare R&D."
>
> I checked bit keepers and found nothing.
>
> I was wondering if people on this list know of this manual, have a copy,
> etc. In general, I'm looking for pre-SysV driver manuals. I can find all
> kinds of SysV driver books (some of which cover 4.2BSD or 4.3BSD as well),
> but nothing for System III or V7 unix. There were a lot of early systems
> that were based on ports of V7 to different architectures that were then
> updated to System III or System V (at least according to the big chart of
> unix history and some wikipedia entries, which may be just repeating
> marketing schlock and not reflect actual reality).
>
> As part of a talk I'm putting together on the 40th anniversary of V7, I
> wanted to have a bit of history for things we still have in unix today
> (like strategy) and things that successors to unix have added or left
> behind (like the packet mux in V7 that was tossed aside for either STREAMS
> or netinet from BSD, though packet muxing to userland is back with DPDK).
>
> Warner
>
[-- Attachment #2: Type: text/html, Size: 5823 bytes --]
next prev parent reply other threads:[~2019-04-29 14:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-29 13:49 Warner Losh
2019-04-29 14:45 ` Clem Cole [this message]
2019-04-29 14:53 ` Larry McVoy
2019-04-29 14:38 Norman Wilson
2019-04-29 14:53 ` Warner Losh
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='CAC20D2NXmwpdjmHabeUav+4UzB0YMjcY0CHALarhAfod=kr7gA@mail.gmail.com' \
--to=clemc@ccc.com \
--cc=imp@bsdimp.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).