Gueven Bay wrote:
Hi dear LFS devs,
I am one of the - I think - many silent readers of LFS-dev.
Normally I only read to gain insight how you develop (or better: write)
the book but now I want to write some words here.
Part of the problem, too, is that many of them *just don't read*. The
answers to the questions they ask are right there in the book. Granted,
with some it's a matter of a simple oversight - they missed a paragraph
or so, which is easy to do when you're trying to follow instructions
while reading a book.
But with others it's easy to tell that this is a pattern for them. They
just don't read. When they have a question, they don't look for the
answer themselves. They pop into IRC or send a support question to list
upon list until some gullible person (like me!) hands them an answer.
(Most often a simple google search on the question would have provided
the answer in the first two or three links).
Once someone has handed them an answer, the only thing they've learned
is 'Here is someone that will help me any time I have a question or
problem!'. So then they send that nice support-guru email upon email
(either privately or publicly) until they've sapped them of answers or
energy. *Why* they do this is beyond me, because it really is a lot
less work to read the book in the first place, or google for the answer
yourself.
What the current support staff *should* do is verify that the users have
1) read the FAQ 2) searched the mailing lists 3) searched google, before
answering their questions. Of course, for those users we already know
and who have a history of asking intelligent questions or only asking
them after they've done some research, we can extend a little extra leeway.
--
JH
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
