9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Jack Johnson <fragment@nas.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] ports ...
Date: Thu,  5 Jun 2003 08:29:26 -0700	[thread overview]
Message-ID: <Pine.BSI.4.05L.10306050808530.20981-100000@cleese.nas.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0306042230580.16158-100000@maxroach.lanl.gov>

On Wed, 4 Jun 2003, ron minnich wrote:
> I noticed somebody asking about the MIPS and SPARC ports.
>
> Hey, you want to do a port, do something interesting like the K8 ...

It's funny the dichotomy about the porting issue.  Some people
like/want/need to use new hardware and others like/want/need to
resuscitate older hardware.  Linux has this legacy hardware support for
which (I think) they do an increasingly poorer job of supporting (NetBSD
probably does a better job of continuing support).  So, for everybody,
recent hardware tends to get decent support for a while, then a kind of
"recovery support" where the popular items get fixed when they break under
version x, then you get the trailing stuff where popular hardware from
five generations ago is free or nearly free and there's a request or push
for new support for legacy hardware.

Plan 9 always intrigued me with its thin workstation concept, where the
workstation can be so-so to barely bearable but always supported by decent
(or exceptional) file/cpu servers.

So, I suppose I'm just rambling, but my vote is equally split between
SPARC and K8.

-Jack



      parent reply	other threads:[~2003-06-05 15:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-05  4:31 ron minnich
2003-06-05  4:59 ` Christopher Nielsen
2003-06-05 13:18   ` David Presotto
2003-06-24 13:53     ` Christopher Nielsen
2003-06-24 14:17       ` boyd, rounin
2003-06-24 17:15         ` Douglas A. Gwyn
2003-06-24 20:33           ` boyd, rounin
2003-06-24 20:38             ` Joel Salomon
2003-06-05 14:11 ` jmk
2003-06-05 15:29 ` Jack Johnson [this message]

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=Pine.BSI.4.05L.10306050808530.20981-100000@cleese.nas.com \
    --to=fragment@nas.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).