From: Chris Friesen <cfriesen@nortelnetworks.com>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Tomas Carnecky <tom@dbservice.com>, linux-kernel@vger.kernel.org
Subject: Re: Kernel thoughts of a Linux user
Date: Thu, 18 Nov 2004 15:15:11 -0600 [thread overview]
Message-ID: <419D10DF.4040902@nortelnetworks.com> (raw)
In-Reply-To: <Pine.LNX.4.53.0411182146060.29376@yvahk01.tjqt.qr>
Jan Engelhardt wrote:
> So they could make themselves a favor and run something like seti@home.
That does consume more energy than just sitting at idle. I've seen some
estimates of how much it costs to run seti 24/7 rather than just sit idle, and
the price was something like $80/year.
Chris
next prev parent reply other threads:[~2004-11-18 21:18 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-18 17:59 Kernel thoughts of a Linux user Gerold J. Wucherpfennig
2004-11-18 18:50 ` Greg KH
2004-11-18 20:00 ` Tomas Carnecky
2004-11-18 20:46 ` Jan Engelhardt
2004-11-18 20:52 ` Tomas Carnecky
2004-11-18 21:05 ` Jan Engelhardt
2004-11-18 21:15 ` Chris Friesen [this message]
2004-11-18 21:17 ` Jan Engelhardt
2004-11-18 21:29 ` Chris Friesen
2004-11-19 12:02 ` Paulo Marques
2004-11-19 12:05 ` Jan Engelhardt
2004-11-20 2:14 ` Alan Cox
2004-11-22 8:07 ` Helge Hafting
2004-11-22 8:38 ` Jan Engelhardt
2004-11-24 10:23 ` Helge Hafting
2004-11-22 11:17 ` Tomas Carnecky
2004-11-24 10:20 ` Helge Hafting
2004-11-24 11:31 ` Tomas Carnecky
2004-11-28 19:10 ` Helge Hafting
2004-11-19 5:04 ` H. Peter Anvin
-- strict thread matches above, loose matches on Subject: below --
2004-11-20 10:31 Gerold J. Wucherpfennig
2004-11-21 18:29 ` Greg KH
2004-11-22 21:33 ` Gerold J. Wucherpfennig
2004-11-22 18:40 ` Greg KH
2004-11-22 18:52 ` Måns Rullgård
2004-11-22 9:54 Adam J. Richter
2004-11-22 14:54 Adam J. Richter
2004-11-22 20:21 ` Maneesh Soni
2004-11-22 15:32 Adam J. Richter
2004-12-14 18:02 Jan Engelhardt
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=419D10DF.4040902@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tom@dbservice.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.