mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Satchell <satch@fluent-access.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>, pf-kernel@mirkwood.net (PinkFreud)
Cc: linux-kernel@vger.kernel.org
Subject: Re: Are we going too fast?
Date: Mon, 13 Aug 2001 10:16:35 -0700	[thread overview]
Message-ID: <4.3.2.7.2.20010813101336.00bb0e40@mail.fluent-access.com> (raw)
In-Reply-To: <E15WHVE-0007N6-00@the-village.bc.nu>
In-Reply-To: <Pine.LNX.4.20.0108130303120.1037-100000@eriador.mirkwood.net>

At 02:11 PM 8/13/01 +0100, Alan Cox wrote:
> > Should development continue on the latest and supposedly greatest
> > drivers?  Or should the existing bugs be fixed first?  I've got at least
> > three up there that need taking care of, and I'm sure others on this list
> > have found more.  3 seperate crashes on 3 seperate installs on 3 seperate
> > boxes - that's 100% failure rate.  If I get 100% failure on my installs,
> > what are others seeing?
>
>Near enough 0%. But then I try and avoid buying broken chipsets.

Back in the old 2.0 days there was a couple of HOWTOs that discussed what 
hardware worked and didn't work under Linux.  I remember using the 
Ethernet-HOWTO as a "shopping list" when going to ham fests, "Wierd Stuff", 
and similar consignment/surplus/boneyard houses.  Have these HOWTOs been 
maintained?

(I've noticed that a number of very, very useful HOWTOs have fallen into 
the "unmaintained" category.)

I happen to think that "stories around the campfire" are fine, but with an 
OS like Linux we should have the "Campfire FAQ"...  :)

Satch


  parent reply	other threads:[~2001-08-13 17:17 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-13  7:43 PinkFreud
2001-08-13  8:52 ` Brian
2001-08-13  8:55 ` Francois Romieu
2001-08-14  4:21   ` Pete Toscano
2001-08-14 12:48     ` Alan Cox
2001-08-14 13:03       ` usb-uhci + SMP -> bad Andre Pang
2001-08-14 16:01         ` Russell Cattelan
2001-08-14 22:30       ` Are we going too fast? Paul G. Allen
2001-08-13 10:03 ` Gérard Roudier
2001-08-13 10:29   ` Justin Guyett
2001-08-13 12:56     ` Andrzej Krzysztofowicz
2001-08-13 16:54     ` Gérard Roudier
2001-08-13 10:09 ` Chris Wilson
2001-08-13 11:09   ` szonyi calin
2001-08-13 13:11 ` Alan Cox
2001-08-14 18:51   ` Anders Larsen
2001-08-14 20:29     ` Anders Larsen
2001-08-13 13:46 ` hugang
2001-08-13 13:55 ` Anton Altaparmakov
2001-08-13 17:16 ` Stephen Satchell [this message]
2001-08-13 21:01 ` A warning (was: Re: Are we going too fast?) Nico Schottelius
2001-08-13 17:53 Are we going too fast? PinkFreud
2001-08-13 20:27 ` Gérard Roudier
2001-08-13 18:46 Per Jessen
2001-08-14 13:58 ` Andrew Scott
2001-08-14 19:54 ` David Ford
2001-08-13 18:53 Petr Vandrovec
     [not found] <fa.l9dq0tv.7gqnhh@ifi.uio.no>
     [not found] ` <fa.g70as7v.1722ipv@ifi.uio.no>
2001-08-13 19:14   ` John Weber
2001-08-13 21:07 PinkFreud
2001-08-13 21:20 ` Alan Cox
2001-08-13 21:41   ` Rog�rio Brito
2001-08-14  0:56   ` Ben Ford
2001-08-14  7:34   ` Peter Wächtler
2001-08-14  2:24 ` David Ford
2001-08-14  4:19   ` Nicholas Knight
2001-08-14 12:49     ` Alan Cox
2001-08-14 22:27       ` Paul G. Allen
2001-08-13 21:36 PinkFreud
2001-08-14  7:57 ` Helge Hafting
2001-08-13 21:44 PinkFreud
2001-08-14  0:04 ` PinkFreud
2001-08-14  7:24   ` Francois Romieu
2001-08-15 23:24   ` Dr. Kelsey Hudson
2001-08-14 16:25 PinkFreud
2001-08-14 16:32 PinkFreud
2001-08-14 19:47 Per Jessen
2001-08-14 20:07 Per Jessen
2001-08-14 20:20 Per Jessen
     [not found] <no.id>
2001-08-13 20:24 ` Alan Cox
2001-08-13 21:06   ` Anthony Barbachan
2001-08-14 20:47 ` Alan Cox
2001-08-15  0:07   ` PinkFreud
2001-08-15 20:13 Roy Murphy
2001-08-16 21:42 PinkFreud

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=4.3.2.7.2.20010813101336.00bb0e40@mail.fluent-access.com \
    --to=satch@fluent-access.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pf-kernel@mirkwood.net \
    /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

Powered by JetHome