- 論壇徽章:
- 0
|
本版帖子命名要求
以下摘自comp.unix.shell的"welcome";
可供諸位發(fā)貼參考.
----
...
What Information Should I Include?
It's hard to include too much information. There are hundreds of
different systems out there, and they all have less in common
than you might think. If you have a problem and are posting an
article, please be sure to mention:
o A descriptive subject line. Many people will decide whether
to read your article solely on the basis of the subject line,
so it should be a good statement of your problem.
NOT GOOD | GOOD
"Help" "How do I port csh scripts to ksh?"
"Csh question" "csh dumps core when I use '$<'"
o What computer you are using, what specific version of the
operating system it uses, and to what shell the question
pertains. For instance,
SunOS 4.0.1, Sun 3/50, tcsh 6.00.03
4.3BSD-tahoe, Vax 11/780, rc 1.0
SVR3.2, 3b2, sh 4.2
o If possible, the *exact* text of any error message you
may have encountered.
WRONG | RIGHT
"My csh script doesn't run" "When I type 'scriptname', I get
sh: scriptname: This isn't a shell script.
What does this mean? It isn't in
the man page. This is using crash 3.14
under Mueslix 9.3 on a Fax 68086502"
It's a good idea to post unrelated questions in separate articles,
so that people can keep different discussions separate. It's also
a *very* good idea to include a line or two like this:
" lease mail your answers to me and I'll summarize what I get
and post the results to comp.unix.shell."
This prevents many identical responses from different users to the
same question from clogging up the newsgroup. And make sure
you really summarize what you get - don't just concatenate
all the mail you've received.
It's also a good idea to read comp.unix.shell for at least a couple
of weeks after you post your article to see what followup articles
are posted.
Should I Post an Answer to a Question?
It's very tempting to post an answer to a question you read on the net,
especially when you think "Aha, finally - a question I can answer!"
Consider though that when a simple question is asked, such as the
sort answered in the companion articles, many other people around the
world already know the answer and may be posting their own reply.
In order to avoid dozens of replies to simple questions, please
wait a day or so and see if anyone else has already answered
the question. If you have something special to contribute, please
do so, but make sure you're not duplicating something someone else has
already done.
You should feel free to reply to any question >by email<. Even if
the user gets 200 responses to his question, at least the load on the
rest of the net is minimized.
What About Posting Source Code?
Posting small amounts of example code is fine (use comp.sources.unix to
distribute complete programs) - but please make sure that your code
runs (or at least compiles) properly. Don't just type it in while
editing your posting and hope it will work, no matter how sure you are
that it will. We all make mistakes.
What About Those People
Who Continue to Ask Stupid or Frequently Asked Questions
In Spite of The Frequently Asked Questions Document?
Just send them a polite mail message, possibly referring them to this document.
There is no need to flame them on the net - it's busy enough as it is.
...
--- |
|
免費(fèi)注冊(cè)
發(fā)表于 2003-01-15 11:22
發(fā)表于 2003-01-17 18:53
