From: cliff white <cliffw@osdl.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: davidw@dedasys.com, linux-kernel@vger.kernel.org
Subject: Re: Linux Incompatibility List
Date: Mon, 23 Aug 2004 13:45:13 -0700 [thread overview]
Message-ID: <20040823134513.7ee62d81.cliffw@osdl.org> (raw)
In-Reply-To: <1093207525.25067.12.camel@localhost.localdomain>
On Sun, 22 Aug 2004 21:45:27 +0100
Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> On Sul, 2004-08-22 at 21:48, David N. Welton wrote:
> > A "compatibility list" is going to be pretty big, and hard to keep up
> > to date. My thinking is that keeping track of a few notable things
> > that don't work is easier than running after all the stuff that does.
>
> Its already been kicked around on the Fedora list to actually build such
> a database automatically. I've seen similar Debian proposals a long time
> ago. That means some time post install you'd let the user
> fire up a system report tool which would ask things like
>
> "Does sound work"
>
> and then fire off PCI id/rating info to a central site. That would help
> deal with the data collection much as the Debian folks collect package
> popularity statistics.
>
> > I suppose some sort of vote system could be put in place so that the 1
> > guy who didn't get the hardware to work gets outvoted by the 10 who
> > did, but there is more incentive to hit the button when you are
> > irritated than when everything 'just worked'.
>
> If you get enough data then the deviation tells you how varied and how
> reliable the opinions are likely to be, all this implies databases not
> WIki however
>
This sounds very interesting indeed. We (OSDL) have been talking about how to
extend our testing into the ISV space, and how to supply useful data. This
type of post-install, post-test 'i look like this, and this runs' data capture
would be real useful, especially if we could capture software info also.
Who else was interested in this?
cliffw
>
> Alan
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
--
The church is near, but the road is icy.
The bar is far, but i will walk carefully. - Russian proverb
next prev parent reply other threads:[~2004-08-23 20:49 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-21 19:41 David N. Welton
2004-08-21 20:16 ` Joseph Pingenot
2004-08-21 20:20 ` Wakko Warner
2004-08-21 20:31 ` Lee Revell
2004-08-21 20:51 ` Wakko Warner
2004-08-21 21:06 ` Jan-Benedict Glaw
2004-08-21 21:11 ` Lee Revell
2004-08-21 21:16 ` Lee Revell
2004-08-22 14:30 ` Tonnerre
2004-08-22 14:45 ` Michael Buesch
2004-08-24 15:17 ` Jan-Benedict Glaw
2004-08-24 17:41 ` Michael Buesch
2004-08-21 21:18 ` Francois Romieu
2004-08-21 22:01 ` Wakko Warner
2004-08-21 23:53 ` Andrew Miklas
2004-08-23 3:54 ` Gianni Tedesco
2004-08-25 5:59 ` Andrew Miklas
2004-08-25 7:21 ` Gianni Tedesco
2004-08-29 1:42 ` Andrew Miklas
2004-08-29 3:21 ` Gianni Tedesco
2004-08-29 21:04 ` Andrew Miklas
2004-08-22 5:29 ` Jonathan Bastien-Filiatrault
2004-08-22 1:56 ` James Courtier-Dutton
2004-08-22 6:36 ` Jonathan Bastien-Filiatrault
2004-08-22 4:15 ` Kyle Moffett
2004-08-22 5:58 ` Lee Revell
2004-08-22 8:05 ` Geert Uytterhoeven
2004-08-22 12:07 ` R. J. Wysocki
2004-08-22 12:32 ` Gene Heskett
2004-08-24 21:30 ` Hamie
2004-08-22 15:25 ` Tonnerre
2004-08-22 11:10 ` Alan Cox
2004-08-22 12:42 ` Dave Jones
2004-08-23 6:31 ` Eric W. Biederman
2004-08-21 21:20 ` David N. Welton
2004-08-21 22:03 ` Wakko Warner
2004-08-22 0:18 ` Rutger Nijlunsing
2004-08-21 20:22 ` David N. Welton
2004-08-22 11:14 ` Alan Cox
2004-08-22 15:08 ` Joseph Pingenot
2004-08-22 20:48 ` David N. Welton
2004-08-22 20:45 ` Alan Cox
2004-08-23 20:45 ` cliff white [this message]
[not found] ` <200408221045.29316.mbuesch@freenet.de>
2004-08-22 20:34 ` David N. Welton
2004-08-22 21:24 ` David N. Welton
2004-08-25 7:41 ` Helge Hafting
2004-08-25 7:49 ` David N. Welton
2004-08-31 7:28 ` Helge Hafting
2004-08-31 10:21 ` David N. Welton
2004-08-22 4:19 linux
2004-08-22 13:05 ` Wakko Warner
2004-08-22 16:43 ` Horst von Brand
2004-08-22 22:42 ` Robin Rosenberg
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=20040823134513.7ee62d81.cliffw@osdl.org \
--to=cliffw@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davidw@dedasys.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®