From: Stan Sieler <sieler@allegro.com>
To: willy@thepuffingroup.com
Cc: andrew@neep.com.au (Andrew Shugg), parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] Value of an old K-class server?
Date: Thu, 2 Mar 2000 10:15:41 -0800 (PST) [thread overview]
Message-ID: <200003021815.KAA29182@opus.allegro.com> (raw)
In-Reply-To: <20000302120851.S9944@thepuffingroup.com> from "willy@thepuffingroup.com" at Mar 02, 2000 12:08:51 PM
Re:
> `CPU types', you'll see that Stan Sieler is going to be disappointed that
> he hung on to his 834, but his 705 will work nicely as it's a PA-7000
> (PCX-S).
We keep the 9000/834 as our HP-UX 10.10 test machine...
last year, it was turned on for about 10 days (out of 365).
This year, we haven't turned it on yet :)
No...I don't intend to run Linux on it...too slow!
--
Stan Sieler sieler@allegro.com
www.allegro.com/sieler/wanted/index.html www.allegro.com/sieler
next prev parent reply other threads:[~2000-03-02 19:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-29 17:06 [parisc-linux] Value of an old K-class server? Andrew Shugg
2000-02-29 14:57 ` Robert Womack
2000-02-29 17:24 ` willy
2000-02-29 23:20 ` Grant Grundler
2000-02-29 23:48 ` Andrew Shugg
2000-02-29 21:03 ` Robert Womack
2000-03-01 0:17 ` willy
2000-03-02 13:02 ` Andrew Shugg
2000-03-02 17:08 ` willy
2000-03-02 18:15 ` Stan Sieler [this message]
2000-03-01 4:35 ` Sandy Harris
[not found] ` <38BCA09A.9ABADBD0@cln.etc.bc.ca>
2000-03-05 23:01 ` Sandy Harris
2000-03-05 23:24 ` Barrie Spence
2000-03-06 2:22 ` [parisc-linux] Value of an old K-class server T. Martin
2000-03-06 11:47 ` Frank Benke
2000-03-07 0:00 ` Barrie Spence
2000-02-29 18:06 ` [parisc-linux] Value of an old K-class server? rob hoppe
-- strict thread matches above, loose matches on Subject: below --
2000-02-29 23:55 Mike Hibler
2000-03-02 17:01 Mike Hibler
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=200003021815.KAA29182@opus.allegro.com \
--to=sieler@allegro.com \
--cc=andrew@neep.com.au \
--cc=parisc-linux@thepuffingroup.com \
--cc=willy@thepuffingroup.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.