home *** CD-ROM | disk | FTP | other *** search
/ ftp.pasteur.org/FAQ/ / ftp-pasteur-org-FAQ.zip / FAQ / news-newusers-intro < prev    next >
Encoding:
Text File  |  1998-05-11  |  18.6 KB  |  405 lines

  1. Newsgroups: news.newusers.questions,news.answers
  2. Path: senator-bedfellow.mit.edu!bloom-beacon.mit.edu!news.kodak.com!news-nysernet-16.sprintlink.net!news.sprintlink.net!128.122.253.90!newsfeed.nyu.edu!news.idt.net!ix.netcom.com!felan
  3. From: felan@netcom.com (Leanne Phillips)
  4. Subject: Welcome to news.newusers.questions! (weekly posting)
  5. Message-ID: <news-newusers-intro_894818116@netcom.com>
  6. Followup-To: news.newusers.questions
  7. Summary: READ THIS BEFORE POSTING TO THIS NEWSGROUP
  8. Sender: felan@netcom10.netcom.com
  9. Supersedes: <news-newusers-intro_894205906@netcom.com>
  10. Reply-To: felan@netcom.com
  11. Organization: Netcom On-Line Services
  12. Date: Sun, 10 May 1998 16:35:17 GMT
  13. Approved: news-answers-request@MIT.Edu
  14. Expires: Mon, 18 May 1998 04:35:16 GMT
  15. Lines: 387
  16. Xref: senator-bedfellow.mit.edu news.newusers.questions:658832 news.answers:129757
  17.  
  18. Archive-name: news-newusers-intro
  19. Version: $Id: news-newusers-intro,v 1.28 1995/10/21 11:50:24 felan Exp $
  20.  
  21. Changes: A pointer to several FAQ archives has been added.  Many or most
  22. FAQs for various newsgroups will be available on these archives.  The
  23. pointers are in the form of URLs.
  24.  
  25.   Welcome to the news.newusers.questions newsgroup!  According to the
  26. "List of Active Newsgroups" posting in news.lists, the purpose of this
  27. newsgroup is "Q & A for users new to the Usenet."  So if you've got
  28. questions about the USENET, this is the place to post them!
  29.  
  30.  
  31.          Get to know news.announce.newusers.
  32.  
  33.  
  34.   However, before you do that, there is another newsgroup with which
  35. you should become acquainted.  The news.announce.newusers newsgroup
  36. contains (once again according to the "List of Active Newsgroups"
  37. posting) "Explanatory postings for new users."  Its purpose is to
  38. provide a base set of information with which all participants in the
  39. USENET should be familiar in order to make the USENET a better place
  40. for all of us.
  41.  
  42.   If you have not already done so, you are strongly encouraged to read
  43. the introductory postings in news.announce.newusers before posting any
  44. messages to any newsgroup.  In particular, the following postings in
  45. that newsgroup might be considered the "mandatory course" for new
  46. users:
  47.  
  48.     A Primer on How to Work With the Usenet Community
  49.     Answers to Frequently Asked Questions about Usenet
  50.     Emily Postnews Answers Your Questions on Netiquette
  51.     Hints on writing style for Usenet
  52.     Rules for posting to Usenet
  53.     What is Usenet?
  54.  
  55. Available in news.lists, rather than news.announce.newusers (these are
  56. also available in news.answers):
  57.  
  58.     Alternative Newsgroup Hierarchies, Part I
  59.     Alternative Newsgroup Hierarchies, Part II
  60.     List of Active Newsgroups, Part I
  61.     List of Active Newsgroups, Part II
  62.     List of Moderators for Usenet
  63.     List of Periodic Informational Postings, Part 1/20
  64.     List of Periodic Informational Postings, Part 2/20
  65.     List of Periodic Informational Postings, Part 3/20
  66.             .
  67.             .
  68.             .
  69.     List of Periodic Informational Postings, Part 18/20
  70.     List of Periodic Informational Postings, Part 19/20
  71.     List of Periodic Informational Postings, Part 20/20
  72.     Publicly Accessible Mailing Lists, Part 1/14
  73.     Publicly Accessible Mailing Lists, Part 2/14
  74.     Publicly Accessible Mailing Lists, Part 3/14
  75.     Publicly Accessible Mailing Lists, Part 4/14
  76.     Publicly Accessible Mailing Lists, Part 5/14
  77.     Publicly Accessible Mailing Lists, Part 6/14
  78.     Publicly Accessible Mailing Lists, Part 7/14
  79.     Publicly Accessible Mailing Lists, Part 8/14
  80.     Publicly Accessible Mailing Lists, Part 9/14
  81.     Publicly Accessible Mailing Lists, Part 10/14
  82.     Publicly Accessible Mailing Lists, Part 11/14
  83.     Publicly Accessible Mailing Lists, Part 12/14
  84.     Publicly Accessible Mailing Lists, Part 13/14
  85.     Publicly Accessible Mailing Lists, Part 14/14
  86.     Regional Newsgroup Hierarchies, Part I (*)
  87.     Regional Newsgroup Hierarchies, Part II (*)
  88.     Regional Newsgroup Hierarchies, Part III (*)
  89.  
  90.  (*) Note that as of December 21, 1992, the "Regional Newsgroup
  91.      Hierarchies" postings are unavailable.  However, their maintainer
  92.      does plan to resume posting them at some point in the future,
  93.      hence their inclusion in this list.
  94.  
  95. Finally, note that before posting in any newsgroup, you should read
  96. the group for a while in order to become familiar with what is
  97. acceptable in it and to make sure that you have seen and read the FAQ
  98. posting(s) for the newsgroup, if there is/are any.
  99.  
  100.   The articles in news.announce.newusers are posted in such a way that
  101. each version should stay around at each site until the new version is
  102. posted.  However, some sites are configured incorrectly so that this
  103. does not occur.  If the articles listed above do not appear in the
  104. news.announce.newusers newsgroup at your site, you can get copies of
  105. them using the instructions appended to the end of this message.
  106.  
  107.  
  108.               Get to know news.answers.
  109.  
  110.  
  111.   The news.answers newsgroup contains a collection of all (well, it's
  112. *supposed* to contain all of them, but it's still missing quite a few)
  113. of the periodic informational postings that appear on the USENET.  You
  114. probably won't want to sit down and read through every posting in
  115. news.answers from beginning to end, especially since postings will be
  116. repeated periodically and many of them will concern topics in which you
  117. have no interest.  However, news.answers is a good place to "browse the
  118. wealth of the USENET."  Since the periodic informational postings in the
  119. various newsgroups tend to be the "distilled wisdom" of those
  120. newsgroups, news.answers might be considered the distilled wisdom of
  121. the USENET.  Glancing at the articles in it will give you a good idea
  122. of the breadth of information embodied in the USENET.
  123.  
  124.  
  125.        Get to know what other newsgroups are out there.
  126.  
  127.  
  128.   There is no well-defined limit on what questions belong in this
  129. newsgroup and what questions do not.  However, it is to your advantage
  130. to know when there is a more appropriate newsgroup for you to post
  131. particular questions in, because when you choose the appropriate
  132. newsgroup, more people who can answer your question will see it.
  133.  
  134.   For example, if you have a question about a UNIX command and that
  135. question is not related to the USENET or to accessing NetNews, it
  136. would probably be more appropriate in comp.unix.questions than in
  137. news.newusers.questions.  Furthermore, since many experienced UNIX
  138. users read comp.unix.questions, you are more likely to get a useful
  139. response if you post there.
  140.  
  141.   There's a posting to help you find the right place to post: "How to find
  142. the right place to post (FAQ)" posted to news.announce.newusers.
  143.  
  144.  
  145.       It's often a good idea to try to get help locally.
  146.  
  147.  
  148.   Many questions that are asked by new USENET users concern details
  149. about their particular site that no one else is going to know about.
  150. Furthermore, new users often don't know what information to provide
  151. when asking their questions, so several exchanges are necessary before
  152. the people helping out have enough information to be able to give a
  153. conclusive answer.  Finally, it's often easier to learn something when
  154. you're a new user by having it shown to you, in person, while sitting
  155. in front of a terminal.
  156.  
  157.   For this reason, it is often a good idea to try to get help locally
  158. with your questions before you post them to news.newusers.questions
  159. (or to any other newsgroup, for that matter).  After you've been
  160. participating in the USENET for a while, you'll get an intuitive feel
  161. for what questions really belong in postings, and what questions are
  162. probably answerable by someone at your site.  If you don't feel you've
  163. reached that point, it's probably a good idea to try to get answers to
  164. pretty much ALL of your questions locally before posting.
  165.  
  166.   Note that "getting help locally" includes checking available local
  167. documentation for whatever you are trying to do.  If you are having a
  168. problem with the "rn" newsreader, for example, try looking for
  169. information in the rn man page (type "man rn", and if it doesn't work
  170. find someone who knows what's going on and ask them why "man rn"
  171. doesn't display the rn man page).
  172.  
  173.   Remember that posting to the USENET uses resources.  You may not pay
  174. for your posting, but other people are.  If you post a question that
  175. people outside your site CAN'T answer, or that people inside your site
  176. CAN answer with minimal effort, the resources consumed by your posting
  177. were consumed needlessly.
  178.  
  179.  
  180.    If you DO decide to ask a question in news.newusers.questions...
  181.  
  182.  
  183.   If, after checking the postings in news.announce.newusers to see if
  184. your question is answered there, and after looking to see if there is
  185. a more appropriate group in which to post it, and after trying to get
  186. help locally, you still think your question belongs in
  187. news.newusers.questions, then go right ahead and post it.
  188.  
  189.   However, you should keep in mind when preparing your question that
  190. the people who will be reading it and trying to help you are not
  191. mind-readers.  We don't know what your site is like.  There are
  192. thousands of sites on the USENET, and they're all just a little bit
  193. different, so the more details you can provide when asking your
  194. question, the more likely it is that people will be able to help you.
  195.  
  196.   Try to provide the following information when posting a question.
  197. If you don't know the answers to some of these questions, then try to
  198. find them out from someone at your site and save them so that you can
  199. use them when posting questions in the future:
  200.  
  201. 1. What kind of machine are you working on?  For example: Macintosh,
  202.    VAX, DECstation, IBM PC, PC compatible (which one), Cray, RS/6000.
  203. 2. What operating system is it running?  For example: MacOS, MS-DOS,
  204.    UNIX, VM/CMS, VMS.
  205. 3. What version of the operating system?  For example: MacOS 7.0,
  206.    Ultrix 4.2 UNIX, BSD 4.3, etc.
  207. 4. What news reader (or whatever program you are having trouble with)
  208.    are you using?  What command do you type to start up whatever
  209.    program is giving you trouble?
  210. 5. What version of the program is it?
  211. 6. If you are trying to interpret some sort of error, what exactly did
  212.    you type to provoke the error, what was the exact error, and how is
  213.    the actual error different from what you expected to happen?  For
  214.    example, if you're trying to figure out why a mail message bounced,
  215.    what address did you send the mail to, and what error message came
  216.    back in the bounced message?
  217. 7. What have you done to try to find the answer to your question
  218.    before posting?  If you've tried different possible answers
  219.    already, exactly what have you tried, and what was the result?
  220. 8. If you have checked the documentation and cannot understand the
  221.    answer it gives to your question, then what exactly about the
  222.    answer it gives don't you understand?  If there is documentation
  223.    available and you haven't checked it, why not?
  224.  
  225. If you're not sure whether a particular piece of information will be
  226. helpful, include it.  It can't hurt to provide extra information
  227. (unless, of course, that information takes up several hundred lines of
  228. text :-), and it may just be the key to the solution of your problem.
  229.  
  230.  
  231.                    Credits
  232.  
  233.  
  234.   Comments about, suggestions about or corrections to this posting are
  235. welcomed.  If you would like to ask me to change this posting in some
  236. way, the method I appreciate most is for you to actually make the
  237. desired modifications to a copy of the posting, and then to send me
  238. the modified posting, or a context diff between my posted version and
  239. your modified version (if you do the latter, make sure to include in
  240. your mail the "Version:" line from my posted version).  Submitting
  241. changes in this way makes dealing with them easier for me and helps to
  242. avoid misunderstandings about what you are suggesting.
  243.  
  244.   The following people assisted in the creation of this article:
  245.  
  246.     Stan Brown <brown@NCoast.ORG>
  247.     Dan_Jacobson@ATT.COM
  248.     Tony Mountifield <tony@mwuk.UUCP>
  249.     Leanne Phillips <phillips@syrinx.umd.edu>
  250.     Ellen Keyne Seebacher <elle@midway.uchicago.edu>
  251.  
  252. This article was originally written by:
  253.     Jonathan Kamens, <jik@security.ov.com>.
  254. ======== 
  255. These three URLs all point at various FAQ archives, although I have only
  256. limited experience with them myself:
  257.  
  258. http://www.cis.ohio-state.edu/hypertext/faq/usenet/FAQ-List.html
  259. http://www.cs.ruu.nl/cgi-bin/faqwais
  260. http://www.lib.ox.ac.uk/internet/news/faq/by_group.index.html
  261.  
  262. There is a list of sites that archive FAQs, available in the "Introduction
  263. to the *.answers newsgroups" document (ftp'able from
  264. rtfm.mit.edu:/pub/usenet/news.answers/news-answers/introduction).
  265.  
  266. The postings listed above are available via anonymous ftp from
  267. rtfm.mit.edu (18.181.0.24) in the files:
  268.  
  269. /pub/usenet/news.answers/usenet/primer/part1
  270. /pub/usenet/news.answers/usenet/faq/part1
  271. /pub/usenet/news.answers/usenet/emily-postnews/part1
  272. /pub/usenet/news.answers/usenet/writing-style/part1
  273. /pub/usenet/news.answers/usenet/posting-rules/part1
  274. /pub/usenet/news.answers/usenet/what-is/part1
  275. /pub/usenet/news.answers/usenet/social-newsgroups/part1
  276. /pub/usenet/news.answers/usenet/creating-newsgroups/part1
  277. /pub/usenet/news.answers/internet/network-info/part1
  278. /pub/usenet/news.answers/news-announce/introduction/part1
  279. /pub/usenet/news.answers/news-answers/introduction
  280. /pub/usenet/news.answers/usenet/software/part1
  281. /pub/usenet/news.answers/active-newsgroups/part1
  282. /pub/usenet/news.answers/active-newsgroups/part2
  283. /pub/usenet/news.answers/alt-hierarchies/part1
  284. /pub/usenet/news.answers/alt-hierarchies/part2
  285. /pub/usenet/news.answers/moderator-list/part1
  286. /pub/usenet/news.answers/periodic-postings/part1
  287. /pub/usenet/news.answers/periodic-postings/part2
  288. /pub/usenet/news.answers/periodic-postings/part3
  289. /pub/usenet/news.answers/periodic-postings/part4
  290. /pub/usenet/news.answers/periodic-postings/part5
  291. /pub/usenet/news.answers/periodic-postings/part6
  292. /pub/usenet/news.answers/periodic-postings/part7
  293. /pub/usenet/news.answers/periodic-postings/part8
  294. /pub/usenet/news.answers/periodic-postings/part9
  295. /pub/usenet/news.answers/periodic-postings/part10
  296. /pub/usenet/news.answers/periodic-postings/part11
  297. /pub/usenet/news.answers/periodic-postings/part12
  298. /pub/usenet/news.answers/periodic-postings/part13
  299. /pub/usenet/news.answers/periodic-postings/part14
  300. /pub/usenet/news.answers/periodic-postings/part15
  301. /pub/usenet/news.answers/periodic-postings/part16
  302. /pub/usenet/news.answers/periodic-postings/part17
  303. /pub/usenet/news.answers/periodic-postings/part18
  304. /pub/usenet/news.answers/periodic-postings/part19
  305. /pub/usenet/news.answers/periodic-postings/part20
  306. /pub/usenet/news.answers/mail/mailing-lists/part01
  307. /pub/usenet/news.answers/mail/mailing-lists/part02
  308. /pub/usenet/news.answers/mail/mailing-lists/part03
  309. /pub/usenet/news.answers/mail/mailing-lists/part04
  310. /pub/usenet/news.answers/mail/mailing-lists/part05
  311. /pub/usenet/news.answers/mail/mailing-lists/part06
  312. /pub/usenet/news.answers/mail/mailing-lists/part07
  313. /pub/usenet/news.answers/mail/mailing-lists/part08
  314. /pub/usenet/news.answers/mail/mailing-lists/part09
  315. /pub/usenet/news.answers/mail/mailing-lists/part10
  316. /pub/usenet/news.answers/mail/mailing-lists/part11
  317. /pub/usenet/news.answers/mail/mailing-lists/part12
  318. /pub/usenet/news.answers/mail/mailing-lists/part13
  319. /pub/usenet/news.answers/mail/mailing-lists/part14
  320. /pub/usenet/news.answers/mail/mailing-lists/part15
  321. /pub/usenet/news.answers/mail/mailing-lists/part16
  322. /pub/usenet/news.answers/mail/mailing-lists/part17
  323. /pub/usenet/news.answers/mail/mailing-lists/part18
  324. /pub/usenet/news.answers/mail/mailing-lists/part19
  325. /pub/usenet/news.answers/mail/mailing-lists/part20
  326. /pub/usenet/news.answers/mail/mailing-lists/part21
  327. /pub/usenet/news.answers/regional-hierarchies/part1
  328. /pub/usenet/news.answers/regional-hierarchies/part2
  329. /pub/usenet/news.answers/regional-hierarchies/part3
  330.  
  331.  
  332. They are also available from mail-server@rtfm.mit.edu by
  333. sending a mail message containing any or all of:
  334.  
  335. send usenet/news.answers/usenet/primer/part1
  336. send usenet/news.answers/usenet/faq/part1
  337. send usenet/news.answers/usenet/emily-postnews/part1
  338. send usenet/news.answers/usenet/writing-style/part1
  339. send usenet/news.answers/usenet/posting-rules/part1
  340. send usenet/news.answers/usenet/what-is/part1
  341. send usenet/news.answers/usenet/social-newsgroups/part1
  342. send usenet/news.answers/alt-hierarchies/part1
  343. send usenet/news.answers/alt-hierarchies/part2
  344. send usenet/news.answers/usenet/creating-newsgroups/part1
  345. send usenet/news.answers/internet/network-info/part1
  346. send usenet/news.answers/news-announce/introduction/part1
  347. send usenet/news.answers/news-answers/introduction
  348. send usenet/news.answers/active-newsgroups/part1
  349. send usenet/news.answers/active-newsgroups/part2
  350. send usenet/news.answers/moderator-list/part1
  351. send usenet/news.answers/periodic-postings/part1
  352. send usenet/news.answers/periodic-postings/part2
  353. send usenet/news.answers/periodic-postings/part3
  354. send usenet/news.answers/periodic-postings/part4
  355. send usenet/news.answers/periodic-postings/part5
  356. send usenet/news.answers/periodic-postings/part6
  357. send usenet/news.answers/periodic-postings/part7
  358. send usenet/news.answers/periodic-postings/part8
  359. send usenet/news.answers/periodic-postings/part9
  360. send usenet/news.answers/periodic-postings/part10
  361. send usenet/news.answers/periodic-postings/part11
  362. send usenet/news.answers/periodic-postings/part12
  363. send usenet/news.answers/periodic-postings/part13
  364. send usenet/news.answers/periodic-postings/part14
  365. send usenet/news.answers/periodic-postings/part15
  366. send usenet/news.answers/periodic-postings/part16
  367. send usenet/news.answers/periodic-postings/part17
  368. send usenet/news.answers/periodic-postings/part18
  369. send usenet/news.answers/periodic-postings/part19
  370. send usenet/news.answers/periodic-postings/part20
  371. send usenet/news.answers/mail/mailing-lists/part01
  372. send usenet/news.answers/mail/mailing-lists/part02
  373. send usenet/news.answers/mail/mailing-lists/part03
  374. send usenet/news.answers/mail/mailing-lists/part04
  375. send usenet/news.answers/mail/mailing-lists/part05
  376. send usenet/news.answers/mail/mailing-lists/part06
  377. send usenet/news.answers/mail/mailing-lists/part07
  378. send usenet/news.answers/mail/mailing-lists/part08
  379. send usenet/news.answers/mail/mailing-lists/part09
  380. send usenet/news.answers/mail/mailing-lists/part10
  381. send usenet/news.answers/mail/mailing-lists/part11
  382. send usenet/news.answers/mail/mailing-lists/part12
  383. send usenet/news.answers/mail/mailing-lists/part13
  384. send usenet/news.answers/mail/mailing-lists/part14
  385. send usenet/news.answers/mail/mailing-lists/part15
  386. send usenet/news.answers/mail/mailing-lists/part16
  387. send usenet/news.answers/mail/mailing-lists/part17
  388. send usenet/news.answers/mail/mailing-lists/part18
  389. send usenet/news.answers/mail/mailing-lists/part19
  390. send usenet/news.answers/mail/mailing-lists/part20
  391. send usenet/news.answers/mail/mailing-lists/part21
  392. send usenet/news.answers/regional-hierarchies/part1
  393. send usenet/news.answers/regional-hierarchies/part2
  394. send usenet/news.answers/regional-hierarchies/part3
  395. send usenet/news.answers/usenet/software/part1
  396.  
  397.  
  398. Send a message containing "help" to the server to get general
  399. information about the mail server.
  400.  
  401.  
  402. You can get an up-to-date copy of this posting by getting the file
  403. "/pub/usenet/news.answers/news-newusers-intro" or by sending the
  404. command "send usenet/news.answers/news-newusers-intro".
  405.