9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: geoff@x.bell-labs.com geoff@x.bell-labs.com
Subject: [9fans] hardware documentation (was Plan 9 future)
Date: Sat, 13 May 2000 03:01:49 -0400	[thread overview]
Message-ID: <20000513070149.QaIYK4RhQH1uXzLf9upe3b5YpsGn265Guc6VDU0UiDA@z> (raw)

Mr. Choat wrote:
> Exactly, the reason it was 'open' then was there was no real competition.

No, hardware documentation was `open' because there was competition
among peripherals vendors and good documentation was a competitive
advantage (there's no need to reveal all details of a controller's
implementation, merely the interface to it and enough
theory-of-operation to drive it).

> The licensing agreements were still there. If you don't believe it then
> try to explain the comments on pp. xi or the back cover of,
> Lion's Commentary on Unix, 6th ed.

These comments all refer to software (Unix) licences; they have
nothing to do with (non-existent) hardware documentation licences nor
fees for same.  I wrote Unix device drivers before working for Bell
Labs.  I don't recall ever encountering (or even hearing from others
about) licence fees for hardware documentation.  Perhaps when hardware
documentation got scarce later, somebody took a bribe for providing it
illicitly and called the bribe a `licence fee'?  :-)





             reply	other threads:[~2000-05-13  7:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-13  7:01 geoff [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-05-15  8:51 Douglas
2000-05-13 18:19 Anthony
2000-05-13 16:55 Digby
2000-05-13 16:23 Digby
2000-05-12 18:10 Anthony
2000-05-12 17:38 jmk
2000-05-12 16:32 Anthony
2000-05-12 12:58 Jim
2000-05-12 12:34 presotto
2000-05-12  5:59 geoff

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=20000513070149.QaIYK4RhQH1uXzLf9upe3b5YpsGn265Guc6VDU0UiDA@z \
    --to=geoff@x.bell-labs.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).