From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] About Plan9 on small systems
Date: Sat, 18 Jul 2009 19:53:17 -0400 [thread overview]
Message-ID: <f2a0fb6d6b06691146bbd7819001bc20@quanstro.net> (raw)
In-Reply-To: <509071940907181623o51712d81y31dcc1b0e0983e0f@mail.gmail.com>
On Sat Jul 18 19:24:31 EDT 2009, anothy@gmail.com wrote:
> inferno's got lighter requirements in some ways, but has
> the same class of CPU requirements (more or less). if you
> have something lighter than that in mind, you might not get
> plan 9 but the ideas could still be useful. ask google about
> "styx on a brick" for an example of using styx (9p by
> another name) on a really small embedded device to
> export underlying capabilities.
the big difference is that inferno requires no mmu.
these days i think the bright line would be 32-bit cpus.
it would be quite difficult to get either one of them
working well on a 8- or 16-bit cpu.
- erik
prev parent reply other threads:[~2009-07-18 23:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-18 20:50 Adriano Verardo
2009-07-18 20:57 ` John Floren
2009-07-18 23:23 ` Anthony Sorace
2009-07-18 23:53 ` erik quanstrom [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=f2a0fb6d6b06691146bbd7819001bc20@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).