Re: How to report problems (was: Request for Flames)
Greg, Actually, I used your page (or its predecessor, it looks different now) back when I started. ;) I'd like to do something more detailed on each type of problem. Eventually, I'd like to turn this into a troubleshooting helper for the most common problems. But information gathering is the first step. Yes, "troubleshooting wizards" might be beneath FreeBSD's target market, but with the sort of questions we get on -questions -- or even -hackers -- I think it would be worthwhile. Anything to slow the growth of the mailing lists. ==ml To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Request for Flames
Folks,
I'm writing a series of web pages on how to ask for help on the
FreeBSD mailing lists.
From time to time, some innocent newbie wanders in here asking a
question with far too little information. ("CVSup/pn0/sio.c doesn't
work. Why not?")
On occasion, you folks have taken the time to write detailed notes
describing the exact information you need to solve these problems.
(On other occasions, said newbie is seen around town: a little bit
here, a little bit there... but that's another problem.)
I'me searched the mail archives looking for these messages, and am
having difficulty finding them. (It's difficult to search for "That
message where Bill Paul told a newbie in excruciating detail what he
needed to fix the problem, and what would happen to the next newbie
who asked this question without providing this information.") Lots of
questions, very few detailed answers.
If any of you have copies of messages that you have previously sent,
describing what information you need to solve a particular problem, I
would appreciate it if you would forward these to me. I'll use this
information to write another guide.
For an example of what I'm trying to do, take a look at:
http://www.blackhelicopters.org/~dispatch/report/nic.html
My eventual goal is to have something like this for every troublesome
part of the system. Hopefully newbies will either read these and give
the proper information, or go away and leave us alone. ;)
Thanks,
==ml
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Request for Flames
Michael Lucas wrote: If any of you have copies of messages that you have previously sent, describing what information you need to solve a particular problem, I would appreciate it if you would forward these to me. I'll use this information to write another guide. I guess I ought to see what you already have, but... well, I'm lazy, and not connected right now. :-) Whatever you do, *please* make a mention of the sections in the handbook that deal precisely with this kind of stuff! -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] "I always feel generous when I'm in the inner circle of a conspiracy to subvert the world order and, with a small group of allies, just defeated an alien invasion. Maybe I should value myself a little more?" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
How to report problems (was: Request for Flames)
On Tuesday, 12 October 1999 at 11:08:50 -0400, Michael Lucas wrote:
Folks,
I'm writing a series of web pages on how to ask for help on the
FreeBSD mailing lists.
From time to time, some innocent newbie wanders in here asking a
question with far too little information. ("CVSup/pn0/sio.c doesn't
work. Why not?")
That's a *good* one. Take a look at
http://www.lemis.com/questions.html for some alternatives.
On occasion, you folks have taken the time to write detailed notes
describing the exact information you need to solve these problems.
(On other occasions, said newbie is seen around town: a little bit
here, a little bit there... but that's another problem.)
I'me searched the mail archives looking for these messages, and am
having difficulty finding them. (It's difficult to search for "That
message where Bill Paul told a newbie in excruciating detail what he
needed to fix the problem, and what would happen to the next newbie
who asked this question without providing this information.") Lots of
questions, very few detailed answers.
If any of you have copies of messages that you have previously sent,
describing what information you need to solve a particular problem, I
would appreciate it if you would forward these to me. I'll use this
information to write another guide.
For an example of what I'm trying to do, take a look at:
http://www.blackhelicopters.org/~dispatch/report/nic.html
Looks good. You probably need to structure it differently (for
example, have a link to things like OS revision and kernel config,
which will be needed in most cases).
Greg
--
See complete headers for address, home page and phone numbers
finger [EMAIL PROTECTED] for PGP public key
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
