From: Matthieu Delahaye <delahaym@esiee.fr>
To: Grant Grundler <grundler@dsl2.external.hp.com>
Cc: Matthew Wilcox <willy@debian.org>, parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] STI framebuffer and PINE
Date: Tue, 16 Jul 2002 09:29:12 +0200 [thread overview]
Message-ID: <3D33CB48.6050208@esiee.fr> (raw)
In-Reply-To: 20020715215022.A8251485D@dsl2.external.hp.com
Grant Grundler wrote:
>Matthew Wilcox wrote:
>
>
>>But the K class hardware is not well supported. Lan and Console
>>are the only two devices which really work; the SCSI cards don't use the
>>normal NCR/Symbios chips but a proprietary chip instead.
>>
>>
>
>Not entirely correct. K-class has both HSC (GSC follow-on) and HP-PB "slots".
>IIRC, the built-in SCSI is HSC based. But you are right in that all the HP-PB
>crud isn't supported.
>
>
>
>>Hmm.. anyone want to do a `testimonials' section on the website which
>>lists peoples (successful ;-) experiences with using PA/Linux in
>>production environments?
>>
>>
>
>ESIEE folks have that already in their "what's supported" HW listing.
>Please see the ESIEE "puffin" site for where to submit them.
>
>
I don't think Matthew wath thinking about that. This HW list gives just
an indication if this is working or not.
What I understand here is a list of something like:
I currently use a B132 in production environment since November, 2001.
It provides a CVS server, apache with PHP and a postgresql database.
The kernel is pretty old (2.4.14-32), but the only shutdown (and end of
services) I had to notice where caused by powerfailure.
Use of Php is quite recent.
Matthew, does these (real) example correspond to your suggestion?
>
>
>[...]
>
>hth,
>grant
>_______________________________________________
>parisc-linux mailing list
>parisc-linux@lists.parisc-linux.org
>http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
>
>
>
>
next prev parent reply other threads:[~2002-07-16 7:29 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-14 9:17 Re: [parisc-linux] STI framebuffer and PINE Stephan Trajkoff
2002-07-14 9:39 ` [parisc-linux] Re: " Martin Schulze
2002-07-14 9:50 ` [parisc-linux] " Ralf Hildebrandt
2002-07-14 11:32 ` Ralf Hildebrandt
2002-07-15 13:20 ` Matthew Wilcox
2002-07-15 13:27 ` Stephan Trajkoff
2002-07-15 13:31 ` Ralf Hildebrandt
2002-07-15 14:37 ` Alan Cox
2002-07-15 13:33 ` Ralf Hildebrandt
2002-07-15 13:39 ` Matthew Wilcox
2002-07-15 14:57 ` Alan Cox
2002-07-15 13:55 ` Matthew Wilcox
2002-07-15 15:42 ` Alan Cox
2002-07-15 21:50 ` Grant Grundler
2002-07-16 7:29 ` Matthieu Delahaye [this message]
2002-07-16 10:12 ` testimonials (was Re: [parisc-linux] STI framebuffer and PINE) Thibaut VARENE
2002-07-16 11:36 ` [parisc-linux] STI framebuffer and PINE Matthew Wilcox
2002-07-15 23:03 ` [parisc-linux] 2.4.19 merge Grant Grundler
2002-07-16 0:23 ` Alan Cox
2002-07-15 23:30 ` Rafael E. Herrera
2002-07-16 10:31 ` Alan Cox
2002-07-16 15:17 ` Randolph Chung
2002-07-16 6:40 ` Grant Grundler
-- strict thread matches above, loose matches on Subject: below --
2002-07-14 6:52 [parisc-linux] STI framebuffer and PINE Stephan Trajkoff
2002-07-14 8:12 ` Ralf Hildebrandt
2002-07-15 12:55 ` Matthew Wilcox
2002-07-15 13:24 ` Ralf Hildebrandt
2002-07-15 13:28 ` Stephan Trajkoff
2002-07-14 10:56 ` Helge Deller
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=3D33CB48.6050208@esiee.fr \
--to=delahaym@esiee.fr \
--cc=grundler@dsl2.external.hp.com \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=willy@debian.org \
/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