From: "Ronald G. Minnich" <rminnich@lanl.gov>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] sparc64 -- unstable
Date: Wed, 12 Jan 2005 12:35:00 -0700 [thread overview]
Message-ID: <Pine.LNX.4.58.0501121233420.3521@bluesteel.lanl.gov> (raw)
In-Reply-To: <Pine.BSI.4.58.0501120915320.10670@malasada.lava.net>
On Wed, 12 Jan 2005, Tim Newsham wrote:
> Hi, I put up a copy of my sources for the ultrasparc for anyone
> adventurous enough to try it out. The sources are at /n/sources/newsham
> along with a short note on how to run it.
well, that's pretty impressive. I wonder if we could get a rought estimate
of the amount of work it took to do this port. You did the compiler,
right? Compiler, drivers, mach code, etc. -- it would be fascinating to
see the relative effort of this vs. something like BSD. My experience is,
given a new architecture, that Unix systems take just a bit longer than I
think you took ...
ron
next prev parent reply other threads:[~2005-01-12 19:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-12 19:22 Tim Newsham
2005-01-12 19:35 ` Ronald G. Minnich [this message]
2005-01-12 21:24 ` Tim Newsham
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.LNX.4.58.0501121233420.3521@bluesteel.lanl.gov \
--to=rminnich@lanl.gov \
--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).