public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Riley <oscar@the-rileys.net>
To: Jeff Epler <jepler@inetnebr.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Defective Red Hat Distribution poorly represents Linux
Date: Wed, 22 Nov 2000 15:35:39 -0500	[thread overview]
Message-ID: <3A1C2E18.4A68FEBF@the-rileys.net> (raw)
In-Reply-To: <Pine.LNX.4.30.0011212330130.3193-100000@toor.thn.htu.se> <3A1B028B.94F3A221@the-rileys.net> <20001121212820.A4625@potty.housenet>

Jeff Epler wrote:
> Well, a copy of that document *is* the first hit for a google search on
> 'linux signal 11 faq'
>         http://www.google.com/search?q=linux+signal+11+faq
> 
> In other words, someone who does the slightest bit of research will
> find the answer.

Perhaps, but if a new user starts using linux and his/her machine is
randomly crashing (not always showing the number 11 anywhere in the
error messages, mind you) the first thing they look for won't be "linux
signal 11 faq".  They'd look for something like "random linux crashes"
or "constant linux crashes" or something to that effect.  Try these on
for size...

<http://www.google.com/search?q=random+linux+crashes>
This one goes six entries before it even comes upon a similar hardware
problem (though to be fair, the report of this problem was far more
intelligent than the one that started this thread) and that is full of
stack traces and cryptic things that a newbie wouldn't even pretend to
understand.  A few years ago, I would have run away screaming from that report.

<http://www.google.com/search?q=constant+linux+crashes>
The first link from this search points to a forum on linuxsucks.org. 
Not what we want newbies looking at...  Some of the posts on the forum
bemoan the lack of documentation for linux.

I think the "slightest bit of research" is a lot different for
experienced Linux users than for those who come from Windoze or MacOS. 
Someone suggested to me that one could put such info on the default page
of the brower in the distribution (the one on the local disk in case of
RedHat, etc), perhaps in the "troubleshooting" section.  That sounds
like a good idea to me.

It also occurs to me that a discussion of documentation belongs on
another list unless it pertains to kernel documentation.  I'll try to
make this my last post.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-11-22 21:07 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-20 13:53 Defective Red Hat Distribution poorly represents Linux Charles Turner, Ph.D.
2000-11-20 14:00 ` Mohammad A. Haque
2000-11-20 14:05 ` Andreas Jaeger
2000-11-20 14:10 ` Tigran Aivazian
2000-11-20 16:13   ` Bernhard Rosenkraenzer
2000-11-20 17:18     ` Tigran Aivazian
2000-11-20 18:19       ` Mohammad A. Haque
2000-11-20 21:11       ` Ben Ford
2000-11-20 18:04   ` Charles Turner, Ph.D.
2000-11-20 18:22     ` John Jasen
2000-11-20 18:44       ` Mohammad A. Haque
2000-11-20 20:32       ` Horst von Brand
2000-11-21 21:08         ` David Riley
2000-11-21 20:43           ` Gérard Roudier
2000-11-21 21:46           ` Bob Lorenzini
2000-11-21 21:50           ` Jeff Epler
2000-11-21 22:27             ` David Riley
2000-11-21 22:31               ` Richard Torkar
2000-11-21 23:17                 ` David Riley
2000-11-22  3:28                   ` Jeff Epler
2000-11-22 20:35                     ` David Riley [this message]
2000-11-22 11:02                   ` Richard Torkar
2000-11-23  1:40               ` Was:Defective Red Hat Distribution poorly represents Linux, running with failed hardware? Richard.Reynolds
2000-11-21 21:52           ` Defective Red Hat Distribution poorly represents Linux Horst von Brand
2000-11-21 22:04           ` David Lang
2000-11-21 21:34             ` David Riley
2000-11-21 22:01               ` Horst von Brand
2000-11-21 22:11                 ` Dan Hollis
2000-11-21 22:21                 ` Gerd Knorr
2000-11-21 22:21               ` David Lang
2000-11-20 21:16       ` Ben Ford
2000-11-21  0:41         ` Fort David
2000-11-20 19:37     ` Mohammad A. Haque
2000-11-20 19:42       ` Andre Hedrick
2000-11-20 19:52       ` Paul Fulghum
2000-11-20 23:01         ` spam
2000-11-20 14:16 ` Gregory Maxwell
2000-11-20 14:50 ` Whiner spams linux-kernel (Re: Defective Red Hat Distribution poorly represents Linux) Jes Sorensen
2000-11-20 15:48 ` Defective Red Hat Distribution poorly represents Linux Bernhard Rosenkraenzer
2000-11-20 17:00 ` Werner Almesberger
2000-11-20 17:31 ` Jeff V. Merkey
2000-11-20 19:33 ` Frank van Maarseveen
2000-11-22 17:26   ` Anthony Liu
2000-11-20 20:15 ` Igmar Palsenberg
2000-11-21  5:53   ` Albert D. Cahalan
2000-11-21  8:16     ` Peter Samuelson

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=3A1C2E18.4A68FEBF@the-rileys.net \
    --to=oscar@the-rileys.net \
    --cc=jepler@inetnebr.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