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=-0.8 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,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 f2d0d617 for ; Mon, 29 Apr 2019 13:50:16 +0000 (UTC) Received: by minnie.tuhs.org (Postfix, from userid 112) id 622FB94924; Mon, 29 Apr 2019 23:50:15 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id 6CE0E948F1; Mon, 29 Apr 2019 23:49:35 +1000 (AEST) Authentication-Results: minnie.tuhs.org; dkim=fail reason="signature verification failed" (2048-bit key; unprotected) header.d=bsdimp-com.20150623.gappssmtp.com header.i=@bsdimp-com.20150623.gappssmtp.com header.b="P6stYp4p"; dkim-atps=neutral Received: by minnie.tuhs.org (Postfix, from userid 112) id 3F7A5948F1; Mon, 29 Apr 2019 23:49:33 +1000 (AEST) Received: from mail-qk1-f196.google.com (mail-qk1-f196.google.com [209.85.222.196]) by minnie.tuhs.org (Postfix) with ESMTPS id 7945E948F0 for ; Mon, 29 Apr 2019 23:49:32 +1000 (AEST) Received: by mail-qk1-f196.google.com with SMTP id d5so5911082qko.12 for ; Mon, 29 Apr 2019 06:49:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=jJhBQ1nPppjbtwj7jyzcAwi07cnWDtrLHc88Vk5t/6M=; b=P6stYp4p/5EAkIb0cUujYK7a9eCoAdIcNDN/hNPUG67Rwz9MAvn0OJI7NjR/NaeGyv 24bc5sIx6Pemv2ji+obvTZuZYuSsrtJ2bt/DyR9ij5BPtXg+P8zUDDqkevPrT+IAqc3d eUmlOdPB554d9C3qV0ZC1GFZH/a1oTeurtJxnhSumHQOIWVkKyB9cRZmsSwv3TBUg4xK BP5PiKl/OfCtvC6M9j9o+4JnRUf5jsbVkMjbaaQOueb84Vfc8MkdC7gV/pIlq9D6xope 2OHpK+GZAZn9MDGYRJFgWzOtBXMYBJs2sN4mPzF4O022Iq1uLi+MYrG2+CckJ5l4kOkB vwYg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=jJhBQ1nPppjbtwj7jyzcAwi07cnWDtrLHc88Vk5t/6M=; b=Y7+8yWkUce82uqUH24Oy8UVEihNG1NIjyUUuNLLCpZuIGwmgxywX4/23y+b9d0yI1/ DfAKBkPPSW8hoIstgYgpgoqMe9RyPI+SD911k2OMypN1grzHNXCaeOuNtD64+2yxx5xi 1vYq+cGzEqfDh9nbZYlr1u9uZA25lPdFSTk5JGUn71iqbL8eP9LyngKZ9AF3YpaAf39F mdzIYcRoOFj4CwsuYVgkU69o7QSyXChaIu7iiEpE9TnxD0H+hg4APbtgoOvldrykup/l Njv6BtcuaOTvSp/oVLeYgBPpYmgbf9ayx1ANdNJEYJ7aOyXsOh09IcWizn9SSd2Le/ic l5WQ== X-Gm-Message-State: APjAAAXe3kkPcoYh9/xkpfV0z7M2fV6R0gsuDRp3/68P9ZiwoDQgaI50 Q/XnzrzEJ62RtgFqI7ks/tR8xABg5o+yjbEohWGiGIj1ACo= X-Google-Smtp-Source: APXvYqxO65bUHKd4rgBeYEU8vMHdbZaBAR6drZvk8Xrv7GbcJKiMI4lhApCKV1UNWva7YUVL09+DgZFtH3hgo4NScjI= X-Received: by 2002:a05:620a:34b:: with SMTP id t11mr34920467qkm.279.1556545770631; Mon, 29 Apr 2019 06:49:30 -0700 (PDT) MIME-Version: 1.0 From: Warner Losh Date: Mon, 29 Apr 2019 07:49:19 -0600 Message-ID: To: The Eunuchs Hysterical Society Content-Type: multipart/alternative; boundary="000000000000bc4b970587ab8d54" Subject: [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: , Errors-To: tuhs-bounces@minnie.tuhs.org Sender: "TUHS" --000000000000bc4b970587ab8d54 Content-Type: text/plain; charset="UTF-8" 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 --000000000000bc4b970587ab8d54 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Greetings,

I'm trying to find the p= redecessor to "Writing a UNIX Device Driver, J. Egan & T. Teixeira, 1st ed, 19= 88". In the preface, it says:

"This book is base= d on a MASSCOMP manual, Guide to Writing a Unix Device Driver.=C2=A0 The fi= rst version that MASSCOMP published as part of the documentation set for th= e MC-500 was based on preliminary drafts prepared for MASSCOMP=C2=A0 by Cli= ff Cary and Tom Albough of Creare R&D."

I checked bit keepe= rs 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 whi= ch 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 differe= nt 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, whi= ch may be just repeating marketing schlock and not reflect actual reality).=

As part of a talk I'm putting together on the 40th annive= rsary 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 ST= REAMS or netinet from BSD, though packet muxing to userland is back with DP= DK).

Warner
--000000000000bc4b970587ab8d54--