Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@debian.org>
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: Fri, 3 May 2002 14:42:57 +0100	[thread overview]
Message-ID: <20020503144257.H2591@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <3CD19041.8080704@neuronet.pitt.edu>; from raffo@neuronet.pitt.edu on Thu, May 02, 2002 at 03:15:13PM -0400

On Thu, May 02, 2002 at 03:15:13PM -0400, Rafael E. Herrera wrote:
> Hi,
> 
> We have an HP K250 dual 160 MHz CPU machine in one of the rooms here. It 
> was never fully used, since the OS media and support costs were very high.
> 
> They are considering pitching it. Can one install palinux on this box?

For the moment, you need Christoph Plattner's serial console driver and
some modification to the install image.  See the mailing list archives
for more details (hmm, anyone want to put together a K-class installing
howto?)

> It is extremely noisy and the size of a small refrigerator. Do you think 
> it is worth keeping?

Depends how much you're willing to hack around.  K class support won't be
as smooth as the other machines for some time.  Some of the devices may
never end up being supported (though centronics, single ended scsi, lan
and keyboard should all work already).  Looking at the K250 in the HWDB,
the Skunk Centronics & SCSI card, the GeckoBOA card, the Eole CAP/MUX and
the GSY Core FW-SCSI will probably end up being supported, but probably
not the Interphase 100BaseTX NIO card.  My crystal ball is second-rate,
however, and when I say `eventually', I mean `in a year or two'.

-- 
Revolutions do not require corporate support.

      parent reply	other threads:[~2002-05-03 13:42 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
2002-05-03 13:42 ` Matthew Wilcox [this message]

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=20020503144257.H2591@parcelfarce.linux.theplanet.co.uk \
    --to=willy@debian.org \
    --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