9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: jmk@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: Inferno on OLPC? (was Re: [9fans] *poof*)
Date: Fri, 16 Jun 2006 11:35:27 -0400	[thread overview]
Message-ID: <33428f89a838accd212b187998d20cbe@plan9.bell-labs.com> (raw)
In-Reply-To: <a4e6962a0606160630p6a7d1cf6h3ad971a07829a9f4@mail.gmail.com>

One of the interesting things to come out of the excellent
presentation at Usenix was that there are people out there
who know things like how much power you can get out of a child
at various ages, etc.

How many 8-year old children == 1 pit pony?

We could work out how long and how many children it would
take to compile Linux on this maybe by starting with the time
and power taken to compile it on some known machine.

On Fri Jun 16 09:30:48 EDT 2006, ericvh@gmail.com wrote:
> On 6/16/06, rog@vitanuova.com <rog@vitanuova.com> wrote:
> > > The other issue is that, evidently, you can't build inferno under inferno.
> >
> > are there sufficient resources on the OLPC to build (say) Linux inside Linux?
> >
> 
> The right question is, at 10-15W per child, how long will it take a
> child with a crank to power a full Linux build....
> 
> Of course, no local disk may also be a factor there....
> 
>           -eric


  parent reply	other threads:[~2006-06-16 15:35 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-01  5:22 [9fans] *poof* Russ Cox
2006-06-01  5:35 ` lucio
2006-06-01  6:14   ` geoff
2006-06-01  7:11 ` LiteStar numnums
2006-06-01 12:50   ` andrey mirtchovski
2006-06-01 12:52     ` andrey mirtchovski
2006-06-01 12:56     ` Ronald G Minnich
2006-06-01 15:54       ` Skip Tavakkolian
2006-06-01 19:03         ` Ronald G Minnich
2006-06-14 21:58           ` Inferno on OLPC? (was Re: [9fans] *poof*) csant
2006-06-14 23:05             ` C H Forsyth
2006-06-15 15:07             ` Ronald G Minnich
2006-06-16 12:35               ` quanstro
2006-06-16 13:08                 ` rog
2006-06-16 13:30                   ` Eric Van Hensbergen
2006-06-16 15:19                     ` Ronald G Minnich
2006-06-16 16:40                       ` Wes Kussmaul
2006-06-16 15:35                     ` jmk [this message]
2006-06-16 16:25                       ` Micah Stetson
2006-06-18 22:57                       ` andrew.simmons
2006-06-19  0:27                         ` quanstro
2006-06-19  1:44                         ` Jack Johnson
2006-06-16 15:19                   ` Ronald G Minnich
2006-06-16 15:39                     ` jmk
2006-06-01 20:31         ` [9fans] *poof* Jim McKie
2006-06-01 20:34     ` Christoph Lohmann
2006-06-01 20:43       ` Francisco J Ballesteros
2006-06-01 20:47         ` Christoph Lohmann
2006-06-01 22:28       ` Latchesar Ionkov
2006-06-01 22:40         ` Christoph Lohmann
2006-06-02  0:24           ` David Leimbach
2006-06-02  6:14             ` [9fans] 9pcf panic arisawa
2006-06-02  8:47               ` arisawa
2006-06-01 16:08 ` [9fans] *poof* Russ Cox
2006-06-02 10:07   ` uriel
2006-06-02 10:31     ` uriel
2006-06-02 14:55     ` Jim McKie
2006-06-02 15:38       ` user local
2006-06-02 20:25       ` Christoph Lohmann
2006-06-02 21:34         ` Francisco J Ballesteros
2006-06-03 14:33           ` Jim McKie
2006-06-03  2:05         ` Russ Cox
2006-06-03 11:18         ` Steve Simon
2006-06-03 22:46           ` geoff
2006-06-04 20:04             ` 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=33428f89a838accd212b187998d20cbe@plan9.bell-labs.com \
    --to=jmk@plan9.bell-labs.com \
    --cc=9fans@cse.psu.edu \
    /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).