9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "James A. Robinson" <jimr@highwire.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] NEC building Raspberry Pi 3s into its displays
Date: Tue, 18 Oct 2016 16:44:10 +0000	[thread overview]
Message-ID: <CAPd04b7BOfnkctHZSSOg1bDOXCSQD1PzBbgbY_dQS5bsyYx_7g@mail.gmail.com> (raw)
In-Reply-To: <ef3e276a-775a-ad14-6696-c0b9892712f0@rwth-aachen.de>

[-- Attachment #1: Type: text/plain, Size: 1054 bytes --]

Good point, thank you.  The reason I keep talking about the RPi
is that I know it's (mostly) supported and I can buy it from a reseller
that I (mostly) trust. :)

I was looking at putting together a system for a file server, and I've
come to the conclusion that I'll have to build it myself, based on what
has been written here and online about what is supported.  If I could
have just purchased a specific model of computer pre-built, I would
have done that.  20 years ago it was fun to build my own plan 9 cluster
from parts I assembled, these days I'm not as into that as I used to be!

Jim

On Tue, Oct 18, 2016 at 8:56 AM Michael Kockmeyer <
Michael.kockmeyer@rwth-aachen.de> wrote:

> I'm seeing that the PI is getting lot's of attention here on 9fans.
>
> I use a Fujitsu thin client as terminal. These (and other vendors) can
> be bought on ebay extremly cheaply (half the price of a PI or cheaper),
> have nice case, Gigabit ethernet, enough USB ports, decent cpu power,
> replaceable and upgradable ram and a PCI slot.
>

[-- Attachment #2: Type: text/html, Size: 1565 bytes --]

      reply	other threads:[~2016-10-18 16:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-15  2:15 Jim Robinson
2016-10-15  9:10 ` Richard Miller
2016-10-15 13:19   ` James A. Robinson
2016-10-15 15:40     ` Steven Stallion
2016-10-18 15:53 ` Michael Kockmeyer
2016-10-18 16:44   ` James A. Robinson [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=CAPd04b7BOfnkctHZSSOg1bDOXCSQD1PzBbgbY_dQS5bsyYx_7g@mail.gmail.com \
    --to=jimr@highwire.org \
    --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).