linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry McVoy <lm@bitmover.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "Øystein Haare" <oyhaare@online.no>, linux-kernel@vger.kernel.org
Subject: Re: Via chipset
Date: Tue, 7 Aug 2001 16:47:40 -0700	[thread overview]
Message-ID: <20010807164740.U23718@work.bitmover.com> (raw)
In-Reply-To: <997225828.10528.4.camel@eagle> <E15UGOw-0004H2-00@the-village.bc.nu>
In-Reply-To: <E15UGOw-0004H2-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Wed, Aug 08, 2001 at 12:36:42AM +0100

This is a reoccurring question on this (and many other) list[s].  It seems
like someone ought to maintain a database of boards that are known to work
and what they are used for.  For example,  lots of people say "such and such
works for me" but what they don't say is "I only have 1 disk and 1 CDROM and
nothing else".

I've had fairly good luck with just about any board as long as I don't 
beat on the IDE on a VIA chipset board.  I switched all my servers over
to 3ware Escalades to get off the IDE; that helped tremendously but it
adds about $400 to a system (3ware card and you will probably want a 
better PS and cooling, so maybe more).

Yeah, I know, if I'm whining I should volunteer the space.  OK, I'll do the
following: if someone starts gathering the data in a simple way (see below)
then I'll archive it all in a database and make it accessible via the web.
If you are interested in doing this, which means you write the script that
gathers the info, contact me offline and we'll set it up.

The data format I want is simple.  Imagine a perl script gathering the
info into an associative array, the key is the field name like "cpu" or
"motherboard" etc., and the value is the value, like "AMD K7" or "ASUS A7V".
It would be good to have a set of required fields so people can query 
across those fields, but there need not be any limit on how many fields and
all fields need not be present in all records.  

Once you have that, I can send you some code that will shlep over that data
to me and I have tools here that will eat it and store it into a database.
Our bugdatabase is lot like this, it's a fairly trivial change to support
this as a sort of bugdatabase like thing.
-- 
---
Larry McVoy            	 lm at bitmover.com           http://www.bitmover.com/lm 

  reply	other threads:[~2001-08-07 23:47 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-07 23:10 Via chipset Øystein Haare
2001-08-07 18:46 ` Bobby D. Bryant
2001-08-07 23:16 ` Dan Hollis
2001-08-07 23:36 ` Alan Cox
2001-08-07 23:47   ` Larry McVoy [this message]
2001-08-08  9:16     ` Janne Pänkälä
2001-08-08 16:09     ` Marco Colombo
2001-08-15  3:25   ` Maxwell Spangler
2001-08-15 11:48     ` Alan Cox
2001-08-15 12:28       ` Bobby D. Bryant
2001-08-15 19:59       ` Dan Hollis
2001-08-15 20:16         ` Alan Cox
2001-08-15 20:27           ` Dan Hollis
2001-08-15 20:32             ` Alan Cox
2001-08-15 21:50               ` Bryan O'Sullivan
2001-08-16 15:35           ` Bob Martin
2001-08-16 21:09             ` Dan Hollis
2001-08-17  3:04               ` Adrian V. Bono
2001-08-20 22:52                 ` Bob Martin
2001-08-08  1:54 ` Ignacio Vazquez-Abrams
2001-08-15 16:46 Ryan C. Bonham
     [not found] <no.id>
2001-08-15 16:09 ` Alan Cox
2001-08-16 16:02 ` Alan Cox
2001-09-12 18:49 VIA chipset Marco Colombo
2001-09-12 19:22 ` Alan Cox
2001-09-12 20:06 ` Jussi Laako
2001-09-12 20:13   ` Marco Colombo
2001-09-12 20:55     ` Anders Peter Fugmann
2001-09-14 17:29     ` Jussi Laako
2001-10-05 10:20 amit yajurvedi
2001-10-15 11:09 grouch
     [not found] <Pine.LNX.4.10.10110151147340.23528-100000@coffee.psychology.mcmaster.ca>
2001-10-15 19:01 ` grouch
     [not found] <Pine.LNX.4.10.10110151554040.23528-100000@coffee.psychology.mcmaster.ca>
2001-10-15 20:31 ` grouch
     [not found] <Pine.LNX.4.10.10110151635040.23528-100000@coffee.psychology.mcmaster.ca>
2001-10-15 21:22 ` grouch
2001-10-17 11:45 grouch

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=20010807164740.U23718@work.bitmover.com \
    --to=lm@bitmover.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oyhaare@online.no \
    /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;
as well as URLs for NNTP newsgroup(s).