From: Grant Grundler <grundler@dsl2.external.hp.com>
To: "Rafael E. Herrera" <raffo@neuronet.pitt.edu>
Cc: parisc-linux <parisc-linux@lists.parisc-linux.org>
Subject: Re: [parisc-linux] Is it worth keeping a dual CPU K250
Date: Thu, 02 May 2002 14:41:13 -0600 [thread overview]
Message-ID: <20020502204113.4746C482B@dsl2.external.hp.com> (raw)
In-Reply-To: Message from "Rafael E. Herrera" <raffo@neuronet.pitt.edu> of "Thu, 02 May 2002 15:15:13 EDT." <3CD19041.8080704@neuronet.pitt.edu>
"Rafael E. Herrera" wrote:
> It is extremely noisy and the size of a small refrigerator. Do you think
> it is worth keeping?
I don't...but I expect Ryan (rbrad) to disagree with me...but it's
helluva faster than the PDPs some people are keeping alive.
I've stopped mucking with HW that I can't lift into a rack by myself. ;^)
Someday I'll break that rule when an N-class gets donated...
grant
next prev parent reply other threads:[~2002-05-02 20:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-02 19:15 [parisc-linux] Is it worth keeping a dual CPU K250 Rafael E. Herrera
2002-05-02 20:41 ` Grant Grundler [this message]
2002-05-03 13:42 ` Matthew Wilcox
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=20020502204113.4746C482B@dsl2.external.hp.com \
--to=grundler@dsl2.external.hp.com \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=raffo@neuronet.pitt.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