9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Bakul Shah <bakul@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Hardware recommandations for new CPU and file servers
Date: Thu,  6 Jun 2013 00:31:15 -0700	[thread overview]
Message-ID: <20130606073115.324D9B827@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Thu, 06 Jun 2013 08:48:14 +0200." <72c31ebd1a9f4752ae4ed8c80ac5c562@proxima.alt.za>

On Thu, 06 Jun 2013 08:48:14 +0200 lucio@proxima.alt.za wrote:
> > What capacity and features were you looking for?
>
> I'm looking to eliminate the 220V circuit between UPS and PSU
> altogether, I believe it to be archaic and inefficient.  I'm also
> looking for multiple inputs, so that eventually it will be possible to
> connect the PSU directly to solar panels as well as to any available
> generator (this is Africa: lots of sun, but the demand for electricity
> outstrips the supply).

You might want to google "living off the grid" (which, I am
sure, makes people in the poorer nations laugh). You should be
able to find stuff about 12V appliances, DC-DC converters,
etc. etc.

> I've done some homework and I'm not happy with commercial offerings as
> available here.  I'm looking for a circuit that can be built by an
> amateur and will power a single conventional desktop computer (let's
> say 300W), while at the same time it can be scaled to supply as many
> such desktops as needed.  Given the handful of DC supplies required by
> the average motherboard, the idea of stacking PSUs makes a lot of
> sense to me.

But what is the market? In places with very unreliable
electric supply people either make do without electricity or
if it is affordable use diesel generators (and now roof
mounted solar panels with inverters).

On the RaspberryPi.org site there is an article about setting
up RaspberryPi computers in a rural school in Ghana.  I think
something like that may be a more appropriate solution.  You
can find relatively simple designs for low power supplies but
generating 300W will be nontrivial. Particularly if you are
want to build many....

Still, a laudable goal. Have you checked out various
do-it-yourself sites?



  reply	other threads:[~2013-06-06  7:31 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-05 18:52 Aram Hăvărneanu
2013-06-05 19:06 ` erik quanstrom
2013-06-05 19:48   ` cinap_lenrek
2013-06-05 19:51     ` erik quanstrom
2013-06-05 20:35       ` cinap_lenrek
2013-06-05 20:49         ` erik quanstrom
2013-06-05 20:09 ` Skip Tavakkolian
2013-06-05 21:12   ` Steven Stallion
2013-06-05 21:03 ` Bakul Shah
2013-06-06 13:21   ` Richard Miller
2013-06-06 16:49     ` hiro
2013-06-05 21:09 ` Steve Simon
2013-06-06  5:17 ` lucio
2013-06-06  5:34   ` Matthew Veety
2013-06-06  5:46     ` lucio
2013-06-06  6:34   ` Bakul Shah
2013-06-06  6:48     ` lucio
2013-06-06  7:31       ` Bakul Shah [this message]
2013-06-06  8:47         ` lucio
2013-06-06  8:51         ` lucio
2013-06-07  9:19 ` [9fans] Hardware recommandations for new CPU and visphatesjava

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=20130606073115.324D9B827@mail.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).