From: Bakul Shah <bakul@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Intel NUCs and Plan 9?
Date: Thu, 9 Jul 2015 09:11:47 -0700 [thread overview]
Message-ID: <C00BF30F-99B3-4CEF-8103-CD77E3709918@bitblocks.com> (raw)
In-Reply-To: <201507091516.t69FGEbW023926@freefriends.org>
Last night my gateway machine fans making final dying for real sounds and I need a replacement. It's a T42 which was already half dead when I repurposed it to this duty and it has worked for four years. I have RPi2, Beaglebone black etc. But in the end I decided to buy a used T60 for $100.
> On Jul 9, 2015, at 8:16 AM, arnold@skeeve.com wrote:
>
> Raspberry pi isn't what I want.
>
> I want to be able to compile / do serious development and being able
> to run Linux would also help. I'm not comfortable moving outside of
> Intel architecture and I want the horsepower I can get out of a Haswell
> or Broadwell.
>
> Thanks,
>
> Arnold
>
> Shingo Onobori <onoborishingo@gmail.com> wrote:
>
>> Is the Raspberry Pi2 bad choice?
>>
>> http://www.plan9.bell-labs.com/wiki/plan9/download/
>>
>>> On 2015/07/09 21:18, arnold@skeeve.com wrote:
>>> Does anyone have experience using Intel NUCs with Plan 9? I'm looking
>>> at http://www.amazon.com/Intel-Next-Unit-Computing-NUC5i3RYK/dp/B00S1ISFOQ/ref=sr_1_9?s=pc&ie=UTF8&qid=1436443454&sr=1-9&keywords=intel+nuc
>>> which is a Broadwell Core i3.
>>>
>>> Other recommendations for low-cost, small form factor boxes to run
>>> Plan 9 would be welcome, preferably with links (:-).
>>>
>>> Thanks,
>>>
>>> Arnold
>
>
next prev parent reply other threads:[~2015-07-09 16:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-09 12:18 arnold
2015-07-09 14:24 ` Shingo Onobori
2015-07-09 15:16 ` arnold
2015-07-09 16:11 ` Bakul Shah [this message]
2015-07-09 16:13 ` Steve Simon
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=C00BF30F-99B3-4CEF-8103-CD77E3709918@bitblocks.com \
--to=bakul@bitblocks.com \
--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).