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 [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
