From: splite@purdue.edu
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Running Version 2 along with Version 3
Date: Mon, 29 Jan 2001 13:30:33 -0500 [thread overview]
Message-ID: <20010129133033.B9247@sigint.cs.purdue.edu> (raw)
In-Reply-To: <200006201451.KAA23603@cse.psu.edu>; from presotto@plan9.bell-labs.com on Tue, Jun 20, 2000 at 10:51:37AM -0400
On Tue, Jun 20, 2000 at 10:51:37AM -0400, presotto@plan9.bell-labs.com wrote:
> [...]
>
> Of course, you could just port the new system to the Sun hardware.
> It shouldn't be that difficult with both the new and old in hand.
> We didn't because we don't really use suns, most of our old processors
> are mips.
As nobody seems to have done it yet, I thought I'd have a go at a SPARC
(sun4c) port of 3rd ed. I do have a 2nd ed. license, but I'm a bit worried
about "contaminating" a 3rd ed. port by looking at or incorporating 2nd ed.
source. Should I be?
Of course, if somebody has already done the port, so much the better...
next prev parent reply other threads:[~2001-01-29 18:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-20 14:51 presotto
2001-01-29 18:30 ` splite [this message]
2001-01-29 18:52 ` Mike Acar
2001-01-29 19:29 ` Boyd Roberts
-- strict thread matches above, loose matches on Subject: below --
2001-01-31 15:07 rob pike
2001-01-30 21:41 geoff
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 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=20010129133033.B9247@sigint.cs.purdue.edu \
--to=splite@purdue.edu \
--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).