9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Tharaneedharan Vilwanathan <vdharani@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] What does your fileserver consist of?
Date: Wed,  9 Nov 2016 21:41:09 -0800	[thread overview]
Message-ID: <CAN-HoCnKgJMY6gmKQW0mhApguAj8juv1N1AS43t2Gr=87LtKQQ@mail.gmail.com> (raw)
In-Reply-To: <CAPd04b4-vb1J0fjZR0rfU_x+2UDzQLfGy4CKEUGtmA178-otDQ@mail.gmail.com>

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

Yes, good idea!

dharani

On Wed, Nov 9, 2016 at 9:21 PM, James A. Robinson <jim.robinson@gmail.com>
wrote:

> Ah, I'm not familiar with those. I ended up buying a fairly old board, but
> one I knew would work (for everything) with the plan 9 kernels. I got a
> Supermicro X7SPA-H-D525, and while it isn't amazingly zippy (11 sec to
> build /sys/src/9/pc) it seems to be fast enough to be a file server.
>
> Jim
>
> On Sun, Nov 6, 2016 at 14:00 Tharaneedharan Vilwanathan <
> vdharani@gmail.com> wrote:
>
>> Assuming cost is not an issue, wouldn't intel Avoton based board be good
>> for this?
>>
>> Regards
>> dharani
>>
>>
>> On Sat, Oct 22, 2016 at 2:40 PM, Steve Simon <steve@quintile.net> wrote:
>>
>> hi,
>>
>> mine is the older model which is not passively cooled, a fan is needed
>> (not to hand so i have no part numbers).
>>
>> it has a 40mm cpu fan but that is all. the fan died (got very noisy) and i
>> replaced it but that was the only unreliable part of the server.
>>
>> -steve
>>
>>
>> > On 22 Oct 2016, at 22:06, Steven Stallion <sstallion@gmail.com> wrote:
>> >
>> > Stock heatsink with chassis cooling. I've had no issues since I've
>> > started using them back in 2012:
>> > http://plan9.bell-labs.com/sources/contrib/stallion/venti/fs.jpg
>> >
>> > On Sat, Oct 22, 2016 at 1:21 PM, James A. Robinson
>> > <jim.robinson@gmail.com> wrote:
>> >> For you folks with an Intel Atom D525 based motherboard
>> >> in your fileserver, do you run with a fanless? Use heatsink?
>> >> Use a fan? Use liquid cooling? Use a quantum heat sink?
>> >>
>> >> Jim
>> >>
>>
>>
>>

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

      reply	other threads:[~2016-11-10  5:41 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-12  0:33 James A. Robinson
2016-10-12  5:27 ` Tyga
2016-10-12  9:20   ` Sergey Zhilkin
2016-10-12  9:22     ` Sergey Zhilkin
2016-10-12  9:48 ` Richard Miller
2016-10-12 14:46 ` Steven Stallion
2016-10-12 15:31 ` California Electric
2016-10-12 18:13   ` Steve Simon
2016-10-12 18:26 ` Brantley Coile
2016-10-12 22:38   ` James A. Robinson
2016-10-12 22:39     ` Brantley Coile
2016-10-12 23:19       ` Jules Merit
2016-10-13 15:54       ` James A. Robinson
2016-10-22 18:21         ` James A. Robinson
2016-10-22 21:06           ` Steven Stallion
2016-10-22 21:40             ` Steve Simon
2016-11-06 21:58               ` Tharaneedharan Vilwanathan
2016-11-10  5:21                 ` James A. Robinson
2016-11-10  5:41                   ` Tharaneedharan Vilwanathan [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='CAN-HoCnKgJMY6gmKQW0mhApguAj8juv1N1AS43t2Gr=87LtKQQ@mail.gmail.com' \
    --to=vdharani@gmail.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).