From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: [9fans] big endian plan 9 machine?
Date: Sun, 13 Jan 2013 12:08:03 -0500 [thread overview]
Message-ID: <72c71b92615e572ef369df5b329b5010@kw.quanstro.net> (raw)
as it turns out there are a lot of crazy little bugs in the system
due to running for so long on 32-bit machines. i'm sure that
we're in a similar situation with endianness, but perhaps even
worse.
to keep everybody honest, i'd like to dig up some sort of plausable
big-endian machine. since the point here is to swat bugs, not
write a new kernel, i would be especially nice if a kernel already
existed. another big bonus would be hardware that still exists and
doesn't require a soldering iron to keep running. :-)
- erik
next reply other threads:[~2013-01-13 17:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-13 17:08 erik quanstrom [this message]
2013-01-13 17:28 ` Charles Forsyth
2013-01-13 17:45 ` erik quanstrom
2013-01-13 18:02 ` Charles Forsyth
2013-01-13 18:00 ` Lyndon Nerenberg
2013-01-13 18:43 ` Charles Forsyth
2013-01-13 18:48 ` erik quanstrom
2013-01-13 18:51 ` John Floren
2013-01-13 19:06 ` Richard Miller
2013-01-13 19:21 ` John Floren
2013-01-13 22:20 ` David Arnold
2013-01-14 1:44 ` erik quanstrom
2013-01-14 8:16 ` Richard Miller
2013-01-15 1:56 ` Bakul Shah
2013-01-15 1:37 ` Bakul Shah
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=72c71b92615e572ef369df5b329b5010@kw.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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).