Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "Bill Halchin" <bhalchin@hotmail.com>
To: ralf@oss.sgi.com, marc@mucom.co.il
Cc: brett@madhouse.org, bleggett@sofamordanek.com,
	linux@cthulhu.engr.sgi.com, linux-mips@fnet.fr,
	linux-mips@vger.rutgers.edu
Subject: Re: Linux on O2?
Date: Sat, 19 Feb 2000 16:29:01 PST	[thread overview]
Message-ID: <20000220002901.38070.qmail@hotmail.com> (raw)

This is precisely why I gave up on this project. I could not get any
documentation, no machine access (if you don't already have). In my
opinion, SGI Linux project must address this problem if they want to
attract "outsiders", i.e. people who are currently outside the SGI
user community, but what to contribute to a very interesting (!!)Open
Source project.


Regards,

Bill Halchin


>From: Ralf Baechle <ralf@oss.sgi.com>
>To: Marc Esipovich <marc@mucom.co.il>
>CC: Ralf Baechle <ralf@oss.sgi.com>, brett <brett@madhouse.org>,        
>Bruce Leggett <bleggett@sofamordanek.com>, linux@cthulhu.engr.sgi.com,      
>   linux-mips@fnet.fr, linux-mips@vger.rutgers.edu
>Subject: Re: Linux on O2?
>Date: Sun, 20 Feb 2000 00:14:45 +0100
>
>On Sat, Feb 19, 2000 at 06:30:22AM -0200, Marc Esipovich wrote:
>
> > > > Im still wainting to hear anything about the indigo i hear alot of 
>talk
> > > > about the indigo2 but nothing about the original blue boxes
> > >
> > > The problem is that the origin docs are gone by now and SGI can't
> > > just go and ship the IRIX source to hackers ...
> >
> > Wow, what do you mean gone by now?  are you saying there's no chance in
> > hell to obtain the documentation?  it can't be gone.
>
>Remember that SGI is a company that designs a large fraction of a system.
>So the designers of some piece of hardware and it's direct users, the
>kernel programmers have close to each other.  For a lot of chips
>documentation never is written or at least never the same way so it would
>be the case for chips that would be marketed as such.  It's obvious that
>this isn't good at all for Free Software where the access to high
>quality documentation is crucial.
>
>So now imagine what has happened to all the knowledge about a machine
>during the decade after it was developed?  The product's development
>finishes, it get's marketed, the OS for gets some final bugfixes and
>even later it gets phased out.  Silence.  Meanwhile the brains behind
>the machine leave the company, tapes and paper go to some dark room
>where nobody still remembers them and the machine gets forgotten.
>
>Slow death of a computer ...
>
>   Ralf

______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com

             reply	other threads:[~2000-02-20  0:43 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-20  0:29 Bill Halchin [this message]
2000-02-20  1:01 ` Linux on O2? Ralf Baechle
  -- strict thread matches above, loose matches on Subject: below --
2000-02-29 18:39 jallan
2000-02-29 18:39 ` jallan
2000-03-01  8:11 ` Richard
2000-03-01 14:40   ` James A Simmons
2000-02-29  3:05 Bastiaan.N.Veelo
2000-02-29  3:39 ` James Simmons
2000-03-01  1:56 ` Ralf Baechle
2000-02-18  0:52 Bruce Leggett
2000-02-18  1:14 ` brett
2000-02-18  1:32   ` William J. Earl
2000-02-18  1:42     ` brett
2000-02-18  2:53   ` Ralf Baechle
2000-02-18 22:13     ` brett
2000-02-18 23:32     ` William J. Earl
2000-02-19  0:03       ` Ralf Baechle
2000-02-19  3:42         ` William J. Earl
2000-02-19 12:29         ` Harald Koerfgen
2000-02-19 21:00           ` Brian D. Moffet
2000-02-19  8:30     ` Marc Esipovich
2000-02-19 23:14       ` Ralf Baechle
2000-02-20 19:11         ` Geert Uytterhoeven
2000-02-20 21:05           ` Ralf Baechle
2000-02-20 21:05             ` Ralf Baechle
2000-02-20 22:32             ` Richard
2000-02-20 23:03               ` Ralf Baechle
2000-02-21 19:44                 ` Richard

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=20000220002901.38070.qmail@hotmail.com \
    --to=bhalchin@hotmail.com \
    --cc=bleggett@sofamordanek.com \
    --cc=brett@madhouse.org \
    --cc=linux-mips@fnet.fr \
    --cc=linux-mips@vger.rutgers.edu \
    --cc=linux@cthulhu.engr.sgi.com \
    --cc=marc@mucom.co.il \
    --cc=ralf@oss.sgi.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