From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,HTML_FONT_LOW_CONTRAST, HTML_MESSAGE,MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.2 Received: from minnie.tuhs.org (minnie.tuhs.org [45.79.103.53]) by inbox.vuxu.org (OpenSMTPD) with ESMTP id 804ecab7 for ; Mon, 29 Apr 2019 14:46:43 +0000 (UTC) Received: by minnie.tuhs.org (Postfix, from userid 112) id 3091F948F2; Tue, 30 Apr 2019 00:46:42 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id 4E752948F1; Tue, 30 Apr 2019 00:46:20 +1000 (AEST) Authentication-Results: minnie.tuhs.org; dkim=pass (1024-bit key; unprotected) header.d=ccc.com header.i=@ccc.com header.b="d2aE1Nlq"; dkim-atps=neutral Received: by minnie.tuhs.org (Postfix, from userid 112) id 05641948F1; Tue, 30 Apr 2019 00:46:19 +1000 (AEST) Received: from mail-wr1-f68.google.com (mail-wr1-f68.google.com [209.85.221.68]) by minnie.tuhs.org (Postfix) with ESMTPS id D0790948F0 for ; Tue, 30 Apr 2019 00:46:17 +1000 (AEST) Received: by mail-wr1-f68.google.com with SMTP id a9so16473290wrp.6 for ; Mon, 29 Apr 2019 07:46:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ccc.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=hW2eYT+3XScB0ikac4LJnMrkRy6UMVxNE9VkmZh1q34=; b=d2aE1Nlq4c7Th0F+18cM8/9EumuQtQ6Ovx0Iodkn03KpjFW/HJ060YZLTD0bnyT8Tx 9JRsPhuovdCcuG6FFrHY/EjkudNTlPKpVkywPYtQzt+LhMW886qZ3kdz02Noxe7rufDR XZDkavswrVt7oy+iaM+nJFrpg02sT7xnJG5y8= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=hW2eYT+3XScB0ikac4LJnMrkRy6UMVxNE9VkmZh1q34=; b=Sk+kvoGo2vW8ylXfyll6EDQA5jCe3My7DCVaJyXZpc0cZZqVjpCUBX5sjowPhTVNJb rEez3Xrnmyt8MQ5BXe439TDZagmFHp7d/FrUtaPN/ALbqBKY/1loOmo0+JSKd9KH0/on 6FM7nSsonKA+SlL1mUYCEiolr5nR9ErrOSUDl7UMkTr7HzPK/GeMhmyg5NsftncF0Al3 YY9CcGzJgxl7M3fUvRPMYqSctVlOUY3dQ89hW0Sr6rfjrJcriJd0d1Z3wxJyOzRyp5gq bcc0tWITy8E3/o9ik5c4R2qqIZAvaYPTwHgHdS+3LATi1K29AqchtrPUxk6wJC/x1xr7 +quA== X-Gm-Message-State: APjAAAVA179+yrBvUUyMTfJHvcQIikd3JdF2cz959Q8ls5TLlDPBvlhM CvGkamSywcUU2mgsiInqlIVJmoebdmDYsDVB0kuWcfVCCdtI1Q== X-Google-Smtp-Source: APXvYqzppF4JjV8Lu6SUa0/6wsLVZoEE79tPVKdscQ7B/mAgr3vk7G1NYe6oVAtwNou/Px5j72EddaZE1e2CIfMyq8Q= X-Received: by 2002:a5d:4a87:: with SMTP id o7mr22759598wrq.207.1556549176200; Mon, 29 Apr 2019 07:46:16 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Clem Cole Date: Mon, 29 Apr 2019 10:45:50 -0400 Message-ID: To: Warner Losh Content-Type: multipart/alternative; boundary="000000000000b928e30587ac58c6" Subject: Re: [TUHS] MASSCOMP MC-500 Guide to Writing a Unix Device Driver X-BeenThere: tuhs@minnie.tuhs.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: The Unix Heritage Society mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: The Eunuchs Hysterical Society Errors-To: tuhs-bounces@minnie.tuhs.org Sender: "TUHS" --000000000000b928e30587ac58c6 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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. =E1=90=A7 On Mon, Apr 29, 2019 at 9:50 AM Warner Losh 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 STREAM= S > or netinet from BSD, though packet muxing to userland is back with DPDK). > > Warner > --000000000000b928e30587ac58c6 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
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).=C2=A0 =C2=A0<= /div>

As for history, until Janet created t= hat document for Masscomp, nothing existed other than a short paper I belie= ve Dennis wrote for V6 and updated for V7.=C2=A0 =C2=A0Cliff and Tom A had = spent hours in Tom and my shared office picking our brains.=C2=A0 What they= came up with was not quite right (to be polite) and tjt attempted to fix i= t - which at least was technically correct.=C2=A0 =C2=A0Janet has the head = of Masscomp's documentation group, re-wrote Tom's version to make i= t easier to understand.=C2=A0 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 bee= n set.

Shortly af= ter, Tom and I had left for Belmont, ney Stellar, and Janet and Tom decided= to redo it as a book.
3D""=E1=90=A7

On Mon, Apr 29,= 2019 at 9:50 AM Warner Losh <imp@bsdi= mp.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.=C2=A0 Th= e first version that MASSCOMP published as part of the documentation set fo= r the MC-500 was based on preliminary drafts prepared for MASSCOMP=C2=A0 by= Cliff Cary and Tom Albough of Creare R&D."

=
I checked bit k= eepers and found nothing.

I was wondering if people on this li= st know of this manual, have a copy, etc. In general, I'm looking for p= re-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 uni= x. There were a lot of early systems that were based on ports of V7 to diff= erent architectures that were then updated to System III or System V (at le= ast according to the big chart of unix history and some wikipedia entries, = which may be just repeating marketing schlock and not reflect actual realit= y).

As part of a talk I'm putting together on the 40th ann= iversary 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
--000000000000b928e30587ac58c6--