> Have you considered creating an FAQ? For me, we have a FAQ, "man" pages, on-line web documentation, and documentation in the config files. There will always

> Have you considered creating an FAQ? For me, we have a FAQ, "man" pages, on-line web documentation, and documentation in the config files. There will always be some idiot who is incapable of reading any documentation. My personal favorite is a debugging error messages which is something like: Failed reading file X: no permissions. Please check that file X is owned by user U and writeable by group G" People post such messages to the mailing list about once a month, asking "What does that mean?" There is no good answer which will satisfy them. If you tell them that the message is self-explanatory, they get mad at you for not explaining it. If you ignore there messages, they re-post repeatedly, asking "Why doesn't anyone help me?" There's a subset of people who just shouldn't be using software.