9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: geoff@x.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Running Version 2 along with Version 3
Date: Tue, 30 Jan 2001 16:41:01 -0500	[thread overview]
Message-ID: <20010130214223.92FEF19A02@mail.cse.psu.edu> (raw)

>i believe the phrase 'like pulling teeth' was used in reference to
>getting certain information from certain vendors.

I believe pulling teeth is easier, you just need a good set of pliers
and a strong arm.  Maybe a chisel and hammer in the worst case.
Getting the necessary information or permission to distribute it
from Sun or SGI was nearly impossible when I (and others) tried to
do it (and not just for Plan 9).  It's possible that application
of sufficient heaps of gold, NDAs or both might have eased things.
Sun and SGI insiders did point people at /usr/include, wherein
there was hardware documentation found nowhere else.

The situation these days is somewhat different.  US legislation
such as the Digital Millenium Copyright Act has muddied the legality
of reverse engineering such as disassembling ROMs.  SGI has got
even more secretive (I'm told that at least one university with
a properly-executed source-code licence for Irix 6.something
can't get said source from SGI).  On the other hand, Solaris 8 source
is allegedly freely available under what they call `community source'
terms; I haven't examined it to see if that includes the interesting
bits like bootstrapping, running the MMU(s) and the kernel memory map.
Plus the `L' word seems to enable Jedi mind-tricks against vendors
(`I'm writing a Linux driver for your harware.  Give me your hardware
documentation.'  `You're writing a Linux driver.  I'll give you the
hardware documentation.').  Even SGI are doing Linux ports.
And as forsyth and others have observed, the various free Unixes
and Linux have already extracted a good deal of information about
hardware from vendors or other sources.


             reply	other threads:[~2001-01-30 21:41 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-30 21:41 geoff [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-01-31 15:07 rob pike
2001-01-30 19:24 forsyth
2001-01-30 14:30 rob pike
2001-01-30 14:59 ` Mike Acar
2001-01-30 18:23   ` Boyd Roberts
2001-01-30 18:42     ` Mike Acar
2001-01-30 18:43     ` Christian Smith
2001-01-31 10:20 ` Bobby Dimmette
2001-01-30 10:51 forsyth
2001-01-30 14:23 ` Mike Acar
2001-01-29 19:35 rob pike
2000-06-20 14:51 presotto
2001-01-29 18:30 ` splite
2001-01-29 18:52   ` Mike Acar
2001-01-29 19:29     ` Boyd Roberts
2000-06-20 13:58 Bill Gunshannon

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=20010130214223.92FEF19A02@mail.cse.psu.edu \
    --to=geoff@x.bell-labs.com \
    --cc=9fans@cse.psu.edu \
    /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).